Data cutover method and device, medium and product

Abstract

The invention provides a data cutover method and device, a medium and a product, relates to the technical field of communication, and aims to solve the problem that a controller with a single structure is relatively high in safety risk. The data cutover method comprises the steps of obtaining first business data of a first controller in response to a data cutover instruction; converting the first business data into target business data which can be processed by a second controller; the first controller and the second controller are heterogeneous controllers; and cutover the target business data to the second controller.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data cutover method, device, medium and product. Background Art

[0002] With the development of communication technology, Software Defined Network (SDN) is widely used in the communication field as an innovative network architecture. SDN can communicate with network devices based on a centralized control plane by using standardized interfaces to achieve unified management of network devices.

[0003] In general SDN, the control layer usually uses a single-structure controller to interact with network devices.

[0004] However, the risk of using a single-structure controller is relatively concentrated. When a controller fails, the control capability of the entire network will be affected, resulting in network service interruption. Therefore, the security risk of using a single-structure controller is relatively high. Summary of the invention

[0005] The embodiments of the present disclosure provide a data cutover method, device, medium and product, aiming to solve the problem of high security risks of controllers with a single structure.

[0006] In order to achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, a data cutover method is provided, including: in response to a data cutover instruction, obtaining first business data of a first controller; converting the first business data into target business data processable by a second controller; the first controller and the second controller are heterogeneous controllers; and cutover the target business data to the second controller.

[0008] Optionally, the target business data includes: business data in the first business data that is different from the second business data of the second controller; and cutting over the target business data to the second controller includes: cutting over the business data in the first business data that is different from the second business data to the second controller.

[0009] Optionally, the data cutover method further includes: acquiring first resource data of the first controller; converting the first resource data into target resource data that can be used by the second controller; and cutover the target resource data to the second controller.

[0010] Optionally, the data cutover method further includes: receiving a first service request; the first service request includes: data characteristics of the requested data; the data characteristics include at least one of the following: timeliness of the data, data volume; and determining a generation frequency of the data cutover instruction based on the data characteristics.

[0011] Optionally, the data cutover method further includes: generating a data cutover instruction when a failure occurs in the first controller.

[0012] Optionally, the data cutover method also includes: receiving a second service request; controlling the first controller and the second controller to process the second service request when the first controller and the second controller operate normally; and controlling the other controller to process the second service request when one of the first controller and the second controller fails.

[0013] Optionally, the data cutover method further includes: acquiring backup data of the first business data; backing up the backup data to a first standby controller; and the first controller and the first backup controller are isomorphic controllers.

[0014] In a second aspect, a data cutover device is provided, which includes: a communication unit and a processing unit; the communication unit is used to obtain first business data of a first controller in response to a data cutover instruction; the processing unit is used to convert the first business data into target business data that can be processed by a second controller; the first controller and the second controller are heterogeneous controllers; the processing unit is also used to cutover the target business data to the second controller.

[0015] Optionally, the target business data includes: business data in the first business data that is different from the second business data of the second controller; and a processing unit specifically configured to: cutover the business data in the first business data that is different from the second business data to the second controller.

[0016] Optionally, the communication unit is further used to obtain first resource data of the first controller; the processing unit is further used to convert the first resource data into target resource data that can be used by the second controller; the processing unit is further used to cutover the target resource data to the second controller.

[0017] Optionally, the communication unit is further used to receive a first service request; the first service request includes: data characteristics of the requested data; the data characteristics include at least one of the following: timeliness of the data, data volume; the processing unit is further used to determine the generation frequency of the data cutover instruction based on the data characteristics.

[0018] Optionally, the processing unit is further configured to generate a data cutover instruction when a failure occurs in the first controller.

[0019] Optionally, the communication unit is further used to receive a second business request; the processing unit is further used to control the first controller and the second controller to process the second business request when the first controller and the second controller are operating normally; the processing unit is further used to control the other controller to process the second business request when one of the first controller and the second controller fails.

[0020] Optionally, the communication unit is further used to obtain backup data of the first business data; the processing unit is further used to back up the backup data to the first backup controller; the first controller and the first backup controller are isomorphic controllers.

[0021] In a third aspect, a data cutover device is provided, comprising a memory and a processor; the memory is used to store computer execution instructions, and the processor and the memory are connected via a bus; when the data cutover device is running, the processor executes the computer execution instructions stored in the memory, so that the data cutover device executes the data cutover method of the first aspect.

[0022] The data cutover device may be an electronic device, or a part of an electronic device, such as a chip system in an electronic device. The chip system is used to support the electronic device to implement the functions involved in the first aspect and any possible implementation thereof, for example, to obtain and determine the data and / or information involved in the above-mentioned data cutover method. The chip system includes a chip, and may also include other discrete devices or circuit structures.

[0023] In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium comprising computer execution instructions, and when the computer execution instructions are executed on a computer, the computer executes the data cutover method described in the first aspect.

[0024] In a fifth aspect, a computer program product is also provided. The computer program product includes a computer program or instructions. When the computer instructions are executed on the data cutover device, the data cutover device executes the data cutover method as described in the first aspect above.

[0025] It should be noted that the above computer instructions may be stored in whole or in part on a computer-readable storage medium, wherein the computer-readable storage medium may be packaged together with the processor of the data cutover device, or may be packaged separately from the processor of the data cutover device, which is not limited in the embodiments of the present application.

[0026] The description of the second, third, fourth and fifth aspects of the present application can refer to the detailed description of the first aspect.

[0027] In the embodiments of the present application, the name of the data cutover device does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear with other names. For example, the receiving unit may also be called a receiving module, a receiver, etc. As long as the functions of each device or functional module are similar to those of the present application, they fall within the scope of the claims of the present application and their equivalent technologies.

[0028] The technical solution provided by this application brings at least the following beneficial effects:

[0029] Based on any of the above aspects, an embodiment of the present application provides a data cutover method. In response to a data cutover instruction, first, first business data of a first controller is obtained, and then the first business data is converted into target business data that can be processed by a second controller. The first controller and the second controller are heterogeneous controllers. Then, the target business data is cutover to the second controller.

[0030] As can be seen from the above, the present application adopts a heterogeneous controller, and in response to a data cutover instruction, converts the first business data in the first controller into target business data that can be processed by the second controller, and cuts over the target business data to the second controller. In this way, the heterogeneous controller is adopted, and the data in the heterogeneous controller is cutover, which reduces the security risk.

[0031] The beneficial effects of the first, second, third, fourth and fifth aspects of the present application can all be referred to the analysis of the above beneficial effects, which will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A schematic diagram of the structure of an SDN system provided in an embodiment of the present application;

[0033] Figure 2 A schematic diagram of a hardware structure of a communication device provided in an embodiment of the present application;

[0034] Figure 3 A flowchart of a data cutover method provided in an embodiment of the present application;

[0035] Figure 4 A flowchart of another data cutover method provided in an embodiment of the present application;

[0036] Figure 5 A flowchart of another data cutover method provided in an embodiment of the present application;

[0037] Figure 6 A flowchart of another data cutover method provided in an embodiment of the present application;

[0038] Figure 7 A flowchart of another data cutover method provided in an embodiment of the present application;

[0039] Figure 8 A flowchart of another data cutover method provided in an embodiment of the present application;

[0040] Fig. 9 A schematic diagram of a flow chart of a switching controller provided in an embodiment of the present application;

[0041] Fig.10A flowchart of another data cutover method provided in an embodiment of the present application;

[0042] Fig.11 A schematic diagram of the structure of a data cutover device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0044] It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0045] In order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and order of execution.

[0046] Before introducing the data cutover method provided by the present application in detail, a brief introduction to the application scenarios and implementation environment involved in the present application is first given.

[0047] First, a brief introduction to the application scenarios involved in this application is given.

[0048] As described in the background technology, with the development of communication technology, SDN is widely used in the communication field as an innovative network architecture. SDN can be based on a centralized control plane and communicate with network devices (network devices can be network devices from different manufacturers) by using standardized interfaces (including: Command Line Interface (CLI), Network Configuration Protocol (NetConf), Border Gateway Protocol (BGP)), to achieve unified management and automated configuration of network devices, simplify network management and speed up the deployment of network services.

[0049] SDN usually adopts a layered architecture, including: business application layer, orchestration management layer and control layer.

[0050] Among them, the business application layer is used to provide network services, which include: providing a user interface to users and processing business logic.

[0051] The orchestration management layer is used to orchestrate and manage network resources and manage the life cycle of network services.

[0052] The control layer is used to centrally control the network, interact directly with network devices, and formulate and implement network policies based on the network data of network devices (configuration instructions can also be issued).

[0053] The control layer in general SDN usually uses a single-structure controller to interact with network devices.

[0054] However, the risk of using a single-structure controller (i.e., a controller from a single supplier) is relatively concentrated. When a controller fails, the control capability of the entire network using SDN will be affected, resulting in network service interruption. Therefore, the security risk of using a single-structure controller is relatively high.

[0055] When using a single-structure controller, in the face of extreme situations (such as security vulnerabilities in the controller), the security of the entire network will be threatened (because the control points of the network are concentrated, attacks can quickly find entry points to destroy the network), and the solutions provided by the supplier cannot quickly and effectively restore the network.

[0056] In addition, a controller with a single structure will be too dependent on a single supplier (i.e., supplier lock-in), which will limit the breadth of technology choices and the openness of SDN, and will be difficult to meet the requirements of network diversification and large-scale deployment (i.e., facing scalability challenges). Especially as the scale of the network expands, it will be unable to meet the growing data processing needs, limiting the scalability of the network.

[0057] A controller with a single structure will also rely on the technical update and upgrade of the controller, and cannot adopt the latest technology to solve the problem in time.

[0058] Moreover, long-term reliance on a single supplier will lead to a lack of competition among controller suppliers, the quality of the controller may decline, the price of the controller may be maliciously raised, and the product quality and price of the controller cannot be guaranteed.

[0059] In response to the above problems, an embodiment of the present application provides a data cutover method. First, in response to a data cutover instruction, first, first business data of a first controller is obtained, and then the first business data is converted into target business data that can be processed by a second controller. The first controller and the second controller are heterogeneous controllers. Then, the target business data is cutover to the second controller.

[0060] As can be seen from the above, the present application adopts a heterogeneous controller, and in response to a data cutover instruction, converts the first business data in the first controller into target business data that can be processed by the second controller, and cuts over the target business data to the second controller. In this way, the heterogeneous controller is adopted, and the data in the heterogeneous controller is cutover, which reduces the security risk.

[0061] Secondly, heterogeneous controller deployment allows the network to be flexibly expanded to adapt to network environments of different scales and requirements.

[0062] Thirdly, the use of heterogeneous controllers can reduce dependence on a single supplier, increase network compatibility and selectivity, and help build a more open and competitive market environment.

[0063] Furthermore, the data cutover method described above simplifies the network management process and improves the operation efficiency of the controller.

[0064] The implementation environment of the above data cutover method may be the SDN system provided in this application.

[0065] Figure 1 FIG. 1 shows a schematic diagram of the structure of the SDN system provided in the embodiment of the present application. Figure 1 As shown, the SDN system includes: a business system module 101, a data cutover device (also called a unified orchestrator) 102, a first controller 103, a second controller 104 and a network device 105.

[0066] The service system module 101 is in communication connection with the data cutover device 102 , and the data cutover device is connected to the first controller 103 and the second controller 104 respectively.

[0067] The first controller 103 and the second controller 104 are in communication connection with the network device 105 .

[0068] In practical applications, the first controller 103 and the second controller 104 can be connected to any number of network devices 105. For ease of understanding, Figure 1 A network device 105 is taken as an example for description.

[0069] The service system module 101 is used to send a service request to the first controller 103 and the second controller 104 through the data cutover device 102 .

[0070] The data cutover device 102 is used to coordinate and manage the first controller 103 and the second controller 104 .

[0071] The first controller 103 and the second controller 104 are used to process service requests and send services to network devices.

[0072] The operating system of the first controller 103 and the second controller 104 may be a Linux operating system or a Community Enterprise Operating System (CentOS).

[0073] The network device 105 is used to provide network device configuration and process services.

[0074] Optionally, the physical devices of the data cutover device 102 and the network device 105 may be servers, terminals, or other types of electronic devices, which is not limited in the embodiments of the present application.

[0075] Optionally, the entity devices of the first controller 103 and the second controller 104 may be servers.

[0076] Optionally, the above-mentioned terminal may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing device connected to a wireless modem. The wireless terminal may communicate with one or more core networks via a radio access network (RAN). The wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, or a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a radio access network, such as a mobile phone, a tablet computer, a laptop computer, a netbook, a personal digital assistant (PDA).

[0077] Optionally, the above-mentioned server can be a server in a server cluster (consisting of multiple servers), or a chip in the server, or a system on a chip in the server, or can be implemented by a virtual machine (VM) deployed on a physical machine, which is not limited in the embodiments of the present application.

[0078] The data cutover equipment in the SDN system includes: Figure 2 The following are the components included. Figure 2 Taking the communication device shown in the figure as an example, the hardware structure of the data cutover equipment is introduced.

[0079] Figure 2 , which is a schematic diagram of a hardware structure of a communication device provided in an embodiment of the present application. The communication device includes a processor 21, a memory 22, a communication interface 23, and a bus 24. The processor 21, the memory 22, and the communication interface 23 can be connected via a bus 24.

[0080] The processor 21 is the control center of the communication device, which can be a processor or a general term for multiple processing elements. For example, the processor 21 can be a general-purpose central processing unit (CPU) or other general-purpose processors. Among them, the general-purpose processor can be a microprocessor or any conventional processor.

[0081] As an embodiment, the processor 21 may include one or more CPUs, such as Figure 2 CPU0 and CPU1 are shown in the figure.

[0082] The memory 22 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0083] In a possible implementation, the memory 22 may exist independently of the processor 21, and the memory 22 may be connected to the processor 21 via a bus 24 to store instructions or program codes. When the processor 21 calls and executes the instructions or program codes stored in the memory 22, the data cutover method provided in the following embodiments of the present application can be implemented.

[0084] In the embodiment of the present application, for the communication device, the software programs stored in the memory 22 are different, so the functions implemented by the communication device are different. The functions performed by each device will be described in conjunction with the following flowchart.

[0085] In another possible implementation, the memory 22 may also be integrated with the processor 21 .

[0086] The communication interface 23 is used for the communication device to connect with other devices through a communication network, and the communication network may be Ethernet, wireless access network, wireless local area network (WLAN), etc. The communication interface 23 may include a receiving unit for receiving data and a sending unit for sending data.

[0087] The bus 24 may be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0088] It should be pointed out that Figure 2 The structure shown in the figure does not constitute a limitation on the communication device, except Figure 2 In addition to the components shown, the communication device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0089] The data cutover method provided in the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0090] The data cutover method provided in the embodiment of the present application is applied to Figure 1 The data cutover device 102 in the data cutover system shown in FIG. Figure 3 As shown, the data cutover method provided in the embodiment of the present application includes:

[0091] S301. In response to a data cutover instruction, obtain first service data of a first controller.

[0092] In one practicable manner, the data cutover device obtains the first service data of the first controller in response to the data cutover instruction, so as to cutover the first service data in the first controller to the second controller, and the second controller processes the first service data. Therefore, the data cutover device needs to obtain the first service data of the first controller.

[0093] Combination Figure 1 , the data cutover device can obtain the first service data from the first controller.

[0094] The first service data includes: network data (eg, web browsing data, file downloading data, video data, audio data), network device Internet Protocol (IP), network device port, and service type.

[0095] S302: Convert the first business data into target business data that can be processed by the second controller.

[0096] The first controller and the second controller are heterogeneous controllers.

[0097] The first controller and the second controller are from different suppliers.

[0098] In one achievable method, after obtaining the first business data, the data cutover device needs to convert the first business data into target business data that can be processed by the second controller. In this way, the data cutover device can cutover the first business data to the second controller so that the second controller can read and process the target business data.

[0099] Specifically, first, the data cutover device parses the first service data. Then, the data cutover device converts the parsed first service data into a unified format and structure. Next, the data cutover device normalizes the first service data converted into a unified format and structure according to the data interface of the second controller, and assembles the target service data that can be processed by the second controller.

[0100] S303: Cut over the target service data to the second controller.

[0101] In one practicable manner, the data cutover device needs to cutover the target service data to the second controller, so that the second controller can process the target service data and ensure the consistency and integrity of the data in the first controller and the second controller.

[0102] In some embodiments, the target business data includes: business data in the first business data that is different from the second business data of the second controller.

[0103] Cutting over the target service data to the second controller specifically includes: cutting over service data in the first service data that is different from the second service data to the second controller.

[0104] In one practicable manner, the target service data that the data cutover device cuts over to the second controller is service data in the first service data that is different from the second service data in the second controller, thereby avoiding data duplication and improving data cutover efficiency.

[0105] Optionally, the data cutover device may also construct a service data verification framework, and use an efficient data comparison algorithm to compare the first service data and the second service data, to ensure that the target service data cutover by the data cutover device is complete and error-free.

[0106] Optionally, the data cutover device may further cross-verify the comparison result between the first service data and the second service data with preset target service data to check the consistency between the preset target service data and the service rules.

[0107] Optionally, the interface between the first controller and the second controller may be a northbound interface (eg, a Representational State Transfer Application Programming Interface (REST API)) or a southbound interface.

[0108] Optionally, during the data cutover process, strict security measures (including access restrictions, encrypted communications, and security audits) are implemented to protect the network from attacks.

[0109] Access restriction means implementing strict access control policies to ensure that only authorized users can access system resources.

[0110] Encrypted communication means encrypting sensitive data to protect data security.

[0111] Security auditing means recording all operations and changes for easy tracking and auditing.

[0112] In some embodiments, in combination Figure 3 ,like Figure 4 As shown, the data cutover method further includes:

[0113] S401. Acquire first resource data of a first controller.

[0114] In one possible implementation, the data cutover device needs to cutover the first resource data in the first controller to the second controller first, and the second controller can process the service data in the first controller only if the second controller has the first resource data. Therefore, the data cutover device needs to obtain the first resource data of the first controller first.

[0115] Combination Figure 1 , the data cutover device can obtain the first resource data from the first controller.

[0116] The first resource data includes: network configuration, traffic rules, policy definition and resource usage.

[0117] S402: Convert the first resource data into target resource data that can be used by the second controller.

[0118] In one achievable method, after obtaining the first resource data, the data cutover device needs to convert the first resource data into target resource data that can be used by the second controller. In this way, the data cutover device can cutover the first resource data to the second controller so that the second controller can read and apply the target resource data.

[0119] Specifically, first, the data cutover device parses the first resource data, then converts the parsed first resource data into a unified format and structure, and standardizes the first resource data converted into the unified format and structure according to the data interface of the second controller, and assembles them into target resource data that can be processed by the second controller.

[0120] S403: Cut over the target resource data to the second controller.

[0121] In one practicable manner, the data cutover device needs to cutover the target resource data to the second controller, so as to ensure the consistency and integrity of the resource data in the first controller and the second controller, so that the second controller can subsequently process the target business data according to the target resource data.

[0122] Optionally, after receiving the target resource data, the second controller needs to parse and verify the target resource data, and check and verify the configuration parameters and network device configuration data in the target resource data to ensure the correctness and security of the target resource data.

[0123] Optionally, the data cutover device may also compare the comparison result between the first service data and the second service data with the actual configuration parameters to ensure the accuracy of the target service data at the physical level.

[0124] As can be seen from the above, the data cutover method can ensure the consistency of service data between the first controller and the second controller, minimize the occurrence of configuration errors and network failures, and improve the efficiency and reliability of overall network management.

[0125] For example, Figure 5 A schematic flow chart of a data cutover method is shown.

[0126] First, the data cutover device calls the first controller to obtain the first resource data and the first service data of the first controller. Then, the data cutover device calls the second controller to obtain the network device configuration (also called the second resource data) from the network device. Next, the data cutover device calls the second controller to perform data cutover. Next, the data cutover device compares the first resource data (including: network device configuration) and the second resource data, the first service data and the second service data. If the comparison is successful (i.e., the second controller does not include the first service data and the first resource data), the data is cutovered into the database.

[0127] Optionally, before performing data cutover, the data cutover device first initializes the state of the controller and detects the state of the controller to ensure that the controller is in a stable and operational state and can process business data and distribute network requests.

[0128] Optionally, network administrators can upgrade and deploy controllers, including software updates and configuration adjustments, to improve the network performance, compatibility, and security of the controllers.

[0129] In some embodiments, in combination Figure 4 ,like Figure 6 As shown, the data cutover method further includes:

[0130] S601: Receive a first service request.

[0131] In one possible implementation, the first controller and the second controller are used to process service data, and the data cutover device can determine the frequency of data cutover according to the service request. Therefore, the data cutover device can first receive the first service request to determine the frequency of generating the data cutover instruction according to the data characteristics requested by the service request.

[0132] Combination Figure 1 , the data cutover device can receive the service request sent by the service system module.

[0133] The first service request includes: data characteristics of the requested data; the data characteristics include at least one of the following: timeliness and data volume of the data.

[0134] S602: Determine the frequency of generating data cutover instructions according to data characteristics.

[0135] In one practicable manner, the data cutover device may determine the frequency of generating the data cutover instruction according to the data characteristics of the data requested by the service request, thereby ensuring that the data between the first controller and the second controller remain highly consistent in terms of time and content.

[0136] For example, when the timeliness of data is high, the frequency of generating data cutover instructions is high. Correspondingly, when the timeliness of data is low, the frequency of generating data cutover instructions is low.

[0137] In another exemplary embodiment, when the data volume is large, the frequency of generating the data cutover instruction is high. Correspondingly, when the data volume is small, the frequency of generating the data cutover instruction is low.

[0138] In another exemplary embodiment, when the timeliness of data is high and the data volume is small, the frequency of generating data cutover instructions is high. When the timeliness of data is low and the data volume is large, the frequency of generating data cutover instructions is high.

[0139] Optionally, when the data cutover device generates the data cutover instruction for the first time, the data cutover device may cutover all data (including service data and resource data) in the first control device to the second control device (which may also be called full synchronization).

[0140] Optionally, when the data cutover device subsequently generates a data cutover instruction, the data cutover device may only transmit the changed data (also known as incremental synchronization), that is, when the first business data in the first controller and / or the first resource data changes, the changed data will be cutovered to the second controller to improve the cutover efficiency.

[0141] Optionally, the data cutover device can quickly locate the root cause of the problem when data inconsistency or conflict is detected, and automatically perform operations such as data merging, overwriting or rollback according to preset priorities and rule sets to ensure the ultimate consistency of the data.

[0142] Optionally, the data cutover device may be set to cutover data at a scheduled time, that is, determine the frequency of generating the data cutover instruction according to the data characteristics of the data requested by the service request.

[0143] Optionally, the data cutover device can also cutover data in real time.

[0144] Optionally, the data cutover device performs data cutover during low business peak hours to reduce the impact on the production environment.

[0145] Optionally, in case of unexpected termination of data cutover, breakpoint resume technology is introduced. The data cutover device can record the synchronization progress and automatically resume synchronization from the breakpoint after the connection is restored, effectively avoiding duplication of work and the risk of data loss.

[0146] As can be seen from the above, the data cutover device generates a data cutover instruction through the above method, optimizes the use of network resources and computing resources through intelligent scheduling, and realizes seamless connection of data between the first controller and the second controller.

[0147] In some embodiments, in combination Figure 4 ,like Figure 7 As shown, the data cutover method further includes:

[0148] S701: When a first controller fails, generate a data cutover instruction.

[0149] In one practicable manner, the data cutover device can generate a data cutover instruction when the first controller fails, so that the second controller obtains the first service data in the first controller. In this way, when the first controller fails, the second controller can process the first service data, and the network service will not be interrupted.

[0150] In some embodiments, in combination Figure 4 ,like Figure 8 As shown, the data cutover method further includes:

[0151] S801. Receive a second service request.

[0152] In one achievable manner, the first controller and the second controller are used to process service data, and the data cutover device can determine the controller for processing the service request according to the failure conditions of the first controller and the second controller, so the data cutover device can receive the second service request.

[0153] S802: When the first controller and the second controller operate normally, control the first controller and the second controller to process a second service request.

[0154] In one achievable manner, when the first controller and the second controller operate normally, the data cutover device can control the first controller and the second controller to process the second service request, thereby improving the efficiency of network services and ensuring the consistency of service data and resource data of the first controller and the second controller.

[0155] Optionally, the first controller and the second controller may operate in parallel.

[0156] The first controller and the second controller are two independent controllers, each of which has its own central processing unit (CPU), internal storage unit, and interface with network devices. Since the first controller and the second controller are heterogeneous controllers, the hardware configuration and software configuration of the first controller and the second controller are different. The first controller and the second controller jointly manage the network, which can improve the flexibility and adaptability of the network.

[0157] Optionally, when both the first controller and the second controller can process the second service request, the service status information is saved and the result is fed back to the service system module.

[0158] S803: When one of the first controller and the second controller fails, control the other controller to process a second service request.

[0159] In one practicable manner, when one of the first controller and the second controller fails, the other controller processes the second service request data, thereby ensuring the continuity of network services.

[0160] Optionally, the second controller can be used as a backup controller for the first controller. The first controller is responsible for processing service data, while the second controller is responsible for receiving synchronization data (ie, cutover data) from the first controller to maintain data consistency.

[0161] Optionally, the data cutover device monitors the first controller and the second controller in real time. When it is detected that the first controller fails and the second controller is normal, the data cutover device immediately switches the network service from the first controller to the second controller so that the second controller takes over the work of the first controller.

[0162] Specifically, when the business system module sends a network configuration or management request to the first controller, if the first controller cannot respond normally due to hardware failure, software error or network problem, and the data cutover device monitors that the status of the first controller is abnormal, the data cutover device will generate a data cutover instruction (also known as an automatic triggering of a failover mechanism) to switch the network service from the first controller to the second controller.

[0163] For example, Fig. 9 A schematic diagram of a process flow of a switching controller is shown.

[0164] The data cutover device controls the first controller to process service data. When the first controller is detected to be abnormal, the data cutover device controller switches the first controller to the second controller. The data cutover device detects whether the state of the second controller is abnormal. When the state of the second controller is normal, the data cutover device controls the second controller to process service data, and the second controller connects to the network device and sends services.

[0165] Specifically, the data cutover device continuously monitors the network connection status (including delay and packet loss rate) between the first controller and the second controller. When a network anomaly is encountered or the number of failed downloads exceeds a preset threshold, the controller switching process is triggered and the number of failed downloads by the first controller is recorded.

[0166] The controller switching process is as follows:

[0167] First, the first controller sends a status change notification to the second controller, indicating that the second controller is ready to take over the tasks of the first controller. Then, after receiving the notification, the second controller performs an internal status check to confirm whether it has the ability to take over the tasks of the first controller. Then, the second controller officially becomes the new first controller and starts to execute the dispatch operation. The first controller becomes the second controller and receives the synchronization data of the first controller. That is, the second controller (formerly the first controller) obtains from the first controller (formerly the second controller). In order to ensure data consistency, the second controller (formerly the first controller) obtains the latest status information from the first controller (formerly the second controller) and performs data synchronization.

[0168] After the controller switch is completed, the SDN system should send notifications to all external systems that depend on the first and second controllers to inform them of their current status.

[0169] Optionally, the SDN system also needs to notify relevant staff (via email or SMS) of the current status of the first controller and the second controller.

[0170] Optionally, before and after the controller switching, the data cutover device needs to verify the data integrity of the first controller and the second controller to ensure that the data is not lost or damaged during the switching process.

[0171] Optionally, the data cutover device may obtain status information of the controller, including health status, link quality, and traffic distribution.

[0172] The controller can provide a comprehensive perspective for network operation and maintenance. Relevant staff can quickly determine the location of the controller problem based on the controller status information to optimize network performance and improve operation and maintenance efficiency.

[0173] Optionally, in the case where the network anomaly is temporary, the data cutover device attempts to restore the original configuration after a period of time to improve the flexibility and availability of the system.

[0174] Optionally, the data cutover equipment records the time, reason and result of each switchover to facilitate subsequent analysis and auditing.

[0175] From the above, it can be seen that when cutting over data, the data cutting device is based on a preset synchronization protocol, such as incremental synchronization based on timestamp (i.e. determining the frequency of generating data cutting instructions) or event-driven real-time synchronization (i.e. in the event of a failure of the first controller).

[0176] In some embodiments, in combination Figure 4 ,like Fig.10 As shown, the data cutover method further includes:

[0177] S1001. Obtain backup data of first business data.

[0178] In one practicable manner, the data cutover device may also obtain backup data of the first service data to back up the backup data to the first standby controller, thereby ensuring that the first service data will not be lost during the data cutover process.

[0179] Optionally, the data cutover device may also obtain backup data of the first resource data, including: existing network configuration, traffic rules, network policies, and resource usage.

[0180] S1002. Back up the backup data to the first standby controller.

[0181] The first controller and the first backup controller are isomorphic controllers.

[0182] In a feasible manner, the data cutover device may also back up the backup data to the first standby controller, so that it can be ensured that the first service data will not be lost during the data cutover process.

[0183] Optionally, the data cutover device may also back up the backup data of the first resource data of the first controller to the first standby controller.

[0184] Optionally, the network administrator may adjust the configuration parameters of the first controller and the second controller according to the actual operation conditions of the first controller and the second controller to optimize the network performance.

[0185] Optionally, network administrators can periodically check network health to prevent potential network problems.

[0186] Optionally, network administrators can also learn and deliver the operating manuals and technical documentation of the SDN system to ensure the normal operation of the network.

[0187] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to realize the above functions, it 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 units and 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 exceed the scope of the present application.

[0188] The embodiment of the present application can divide the functional modules of the data cutover 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. Optionally, 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.

[0189] Fig.11 FIG. 1 shows a schematic diagram of the structure of a data cutover device provided in an embodiment of the present application. Fig.11 As shown, the data cutover device includes: a communication unit 1101 and a processing unit 1102;

[0190] The communication unit 1101 is used to obtain the first business data of the first controller in response to the data cutover instruction; the processing unit 1102 is used to convert the first business data into target business data that can be processed by the second controller; the first controller and the second controller are heterogeneous controllers; the processing unit 1102 is also used to cutover the target business data to the second controller.

[0191] Optionally, the target business data includes: business data in the first business data that is different from the second business data of the second controller; the processing unit 1102 is specifically used to: cut over the business data in the first business data that is different from the second business data to the second controller.

[0192] Optionally, the communication unit 1101 is further used to obtain first resource data of the first controller; the processing unit 1102 is further used to convert the first resource data into target resource data that can be used by the second controller; the processing unit 1102 is further used to cutover the target resource data to the second controller.

[0193] Optionally, the communication unit 1101 is further used to receive a first business request; the first business request includes: data characteristics of the requested data; the data characteristics include at least one of the following: timeliness of the data, data volume; the processing unit 1102 is further used to determine the generation frequency of the data cutover instruction according to the data characteristics.

[0194] Optionally, the processing unit 1102 is further configured to generate a data cutover instruction when a failure occurs in the first controller.

[0195] Optionally, the communication unit 1101 is further used to receive a second business request; the processing unit 1102 is further used to control the first controller and the second controller to process the second business request when the first controller and the second controller are operating normally; the processing unit 1102 is further used to control the first controller and the second controller to process the second business request when one of the first controller and the second controller fails.

[0196] Optionally, the communication unit 1101 is further used to obtain backup data of the first business data; the processing unit 1102 is further used to back up the backup data to the first standby controller; the first controller and the first backup controller are isomorphic controllers.

[0197] The embodiment of the present application further provides a computer-readable storage medium, which includes computer-executable instructions. When the computer-executable instructions are executed on a computer, the computer executes the data cutover method provided in the above embodiment.

[0198] The embodiment of the present application also provides a computer program, which can be directly loaded into a memory and contains software code. After being loaded and executed by a computer, the computer program can implement the data cutover method provided in the above embodiment.

[0199] Those skilled in the art should be aware that in one or more of the above examples, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media can be any available media that can be accessed by general or special-purpose computers.

[0200] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0201] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation. 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 coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be a physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed in multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0202] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. If the 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 embodiment of the present application is essentially or the part that contributes to the general technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a ROM, a RAM, a disk, or an optical disk.

[0203] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A data cutover method, characterized in that: The method comprises: In response to the data cutover instruction, acquiring first service data of the first controller; converting the first service data into target service data processable by the second controller; the first controller and the second controller are heterogeneous controllers; The target service data is cutovered to the second controller.

2. The method according to claim 1, characterized in that The target business data includes: business data in the first business data that is different from the second business data of the second controller; and the step of cutting over the target business data to the second controller includes: The service data in the first service data that is different from the second service data is cut over to the second controller.

3. The method according to claim 1, characterized in that The method further comprises: Acquire first resource data of the first controller; converting the first resource data into target resource data usable by the second controller; The target resource data is cutovered to the second controller.

4. The method according to claim 1, characterized in that: The method further comprises: Receive a first service request; the first service request includes: data characteristics of the requested data; the data characteristics include at least one of the following: timeliness of the data, data volume; The frequency of generating the data cutover instruction is determined according to the data characteristics.

5. The method according to claim 1, characterized in that The method further comprises: In the event that the first controller fails, the data cutover instruction is generated.

6. The method according to claim 1, characterized in that The method further comprises: receiving a second service request; When the first controller and the second controller operate normally, controlling the first controller and the second controller to process the second service request; In the event that one of the first controller and the second controller fails, the other controller is controlled to process the second service request.

7. The method according to claim 1, characterized in that The method further comprises: Acquire backup data of the first business data; The backup data is backed up to a first standby controller; the first controller and the first backup controller are isomorphic controllers.

8. A data cutover device, characterized in that: The device comprises: a communication unit and a processing unit; The communication unit is used to obtain the first service data of the first controller in response to the data cutover instruction; The processing unit is used to convert the first business data into target business data that can be processed by the second controller; the first controller and the second controller are heterogeneous controllers; The processing unit is further used to cut over the target service data to the second controller.

9. A data cutover device, characterized in that: include: A processor and a memory; wherein the memory is used to store one or more programs, and the one or more programs include computer-executable instructions. When the device is running, the processor executes the computer-executable instructions stored in the memory to enable the device to perform the method described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: When the computer-executable instructions stored in the computer-readable storage medium are executed by a processor of a data cutover device, the data cutover device can execute the method according to any one of claims 1 to 7.

11. A computer program product, characterized in that The computer program product comprises: a computer program or instructions, and when the computer program or instructions are run on a computer, the computer is caused to perform the method according to any one of claims 1 to 7.

Images