A data cutover method, apparatus, medium, and product

Abstract

This application provides a data cutover method, apparatus, medium, and product, relating to the field of communication technology, to address the significant security risks associated with controllers employing a single architecture. The data cutover method includes: in response to a data cutover command, acquiring first service data from a first controller; converting the first service data into target service data that can be processed by a second controller; wherein the first controller and the second controller are heterogeneous controllers; and cutting over the target service data to the second controller.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data cutover method, apparatus, medium and product. Background Technology

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

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

[0004] However, the risks associated with a single-structure controller are concentrated. When the controller fails, the control capability of the entire network is affected, leading to network service interruption. Therefore, controllers with a single structure pose a significant security risk. Summary of the Invention

[0005] This disclosure provides a data cutover method, apparatus, medium, and product, aiming to address the significant security risks associated with controllers employing a single architecture.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] In a first aspect, a data cutover method is provided, comprising: in response to a data cutover command, acquiring first service data from a first controller; converting the first service data into target service data that can be processed by a second controller; wherein the first controller and the second controller are heterogeneous controllers; and cutting over the target service data to the second controller.

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

[0009] Optionally, the data cutover method further includes: acquiring first resource data from the first controller; converting the first resource data into target resource data that can be used by the second controller; and cutting over 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 the generation frequency of data cutover instructions based on the data characteristics.

[0011] Optionally, the data cutover method may also include generating a data cutover command in the event of a failure of the first controller.

[0012] Optionally, the data cutover method further 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 are operating normally; and controlling the other controller to process the second service request if one of the first controller and the second controller fails.

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

[0014] Secondly, a data cutover device is provided, comprising: a communication unit and a processing unit; the communication unit is configured to acquire first service data from a first controller in response to a data cutover command; the processing unit is configured to convert the first service data into target service data that can be processed by a second controller; the first controller and the second controller are heterogeneous controllers; the processing unit is further configured to cut over the target service data to the second controller.

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

[0016] Optionally, the communication unit is further configured to acquire first resource data from the first controller; the processing unit is further configured to convert the first resource data into target resource data that can be used by the second controller; and the processing unit is further configured to cut over the target resource data to the second controller.

[0017] Optionally, the communication unit is further configured 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 configured to determine the generation frequency of the data cutover instruction based on the data characteristics.

[0018] Optionally, the processing unit is also configured to generate data cutover instructions in the event of a failure of the first controller.

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

[0020] Optionally, the communication unit is further configured to acquire backup data of the first service data; the processing unit is further configured to back up the backup data to the first backup controller; the first controller and the first backup controller are homogeneous controllers.

[0021] Thirdly, a data cutover device is provided, including a memory and a processor; the memory is used to store computer-executed instructions, and the processor is connected to the memory via a bus; when the data cutover device is running, the processor executes the computer-executed instructions stored in the memory, so that the data cutover device performs the data cutover method of the first aspect.

[0022] The data cutover device can be an electronic device or a component of an electronic device, such as a chip system within the electronic device. The chip system supports the electronic device in implementing the functions involved in the first aspect and any of its possible implementations, such as acquiring and determining the data and / or information involved in the aforementioned data cutover method. The chip system includes chips, but may also include other discrete devices or circuit structures.

[0023] Fourthly, a computer-readable storage medium is provided, comprising computer-executable instructions that, when executed on a computer, cause the computer to perform the data cutover method described in the first aspect.

[0024] Fifthly, a computer program product is also provided, comprising a computer program or instructions that, when executed on a data cutover device, cause the data cutover device to perform the data cutover method as described in the first aspect above.

[0025] It should be noted that the aforementioned computer instructions may be stored, in whole or in part, on a computer-readable storage medium. This computer-readable storage medium may be packaged together with the processor of the data cutover device, or it may be packaged separately from the processor of the data cutover device; this application does not limit this.

[0026] The descriptions of the second, third, fourth, and fifth aspects of this application can be referenced to the detailed description of the first aspect.

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

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

[0029] Based on any of the above aspects, embodiments of this application provide a data cutover method. In response to a data cutover command, firstly, first service data of a first controller is acquired; then, the first service data is converted into target service data that can be processed by a second controller. The first controller and the second controller are heterogeneous controllers. Next, the target service data is cutovered to the second controller.

[0030] As can be seen from the above, this application employs a heterogeneous controller. In response to a data cutover command, it converts the first service data in the first controller into target service data that can be processed by the second controller, and then cuts over the target service data to the second controller. Thus, by using a heterogeneous controller and cutting over the data within it, security risks are reduced.

[0031] The beneficial effects of the first, second, third, fourth, and fifth aspects of this application can all be referred to in the analysis of the above-mentioned beneficial effects, and will not be repeated here. Attached Figure Description

[0032] Figure 1 This is a schematic diagram of the structure of an SDN system provided in an embodiment of this application;

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

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

[0035] Figure 4 A flowchart illustrating yet another data cutover method provided in this application embodiment;

[0036] Figure 5 A flowchart illustrating yet another data cutover method provided in this application embodiment;

[0037] Figure 6 A flowchart illustrating yet another data cutover method provided in this application embodiment;

[0038] Figure 7 A flowchart illustrating yet another data cutover method provided in this application embodiment;

[0039] Figure 8 A flowchart illustrating yet another data cutover method provided in this application embodiment;

[0040] Figure 9 A flowchart illustrating a switching controller provided in an embodiment of this application;

[0041] Figure 10A flowchart illustrating yet another data cutover method provided in this application embodiment;

[0042] Figure 11 This is a schematic diagram of a data cutover device provided in an embodiment of this application. Detailed Implementation

[0043] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0044] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0045] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.

[0046] Before providing a detailed introduction to the data cutover method provided in this application, let's briefly introduce the application scenarios and implementation environment involved in this application.

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

[0048] As described in the background section, with the development of communication technology, SDN, as an innovative network architecture, has been widely used in the field of communication. SDN can communicate with network devices (which can be from different vendors) based on a centralized control plane using standardized interfaces (including Command Line Interface (CLI), Network Configuration Protocol (NetConf), and Border Gateway Protocol (BGP)). This enables unified management and automated configuration of network devices, simplifies network management, and accelerates the deployment of network services.

[0049] SDN typically employs a layered architecture, including: the business application layer, the orchestration management layer, and the control layer.

[0050] The business application layer is used to provide network services, including providing user interfaces and processing business logic.

[0051] The orchestration management layer is used to orchestrate and manage network resources, as well as manage the lifecycle of network services.

[0052] The control layer is used for centralized control of the network, interacts directly with network devices, and formulates and implements network policies based on the network data of the network devices (it can also issue configuration commands).

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

[0054] However, the risks of using a single-structure controller (i.e., a controller from a single vendor) are concentrated. When the controller fails, the control capabilities of the entire SDN-based network are affected, leading to network service interruption. Therefore, the security risks of using a single-structure controller are relatively high.

[0055] When a controller with a single architecture is used, the security of the entire network is threatened in extreme situations (such as when the controller has a security vulnerability). Because the control point of the network is centralized, an attack can quickly find an entry point to destroy the network, and the solution provided by the vendor cannot quickly and effectively restore the network.

[0056] In addition, a controller with a single architecture will be too dependent on a single vendor (i.e., vendor lock-in), which will limit the breadth of technology choices and the openness of SDN, making it difficult to meet the requirements of network diversification and large-scale deployment (i.e., facing scalability challenges). In particular, as the network scales up, it cannot meet the growing data processing needs, thus limiting the network's scalability.

[0057] Controllers with a single architecture also rely on the technology updates and upgrades of the controller, and cannot promptly adopt the latest technologies to solve problems.

[0058] Furthermore, relying on a single supplier for a long time leads to a lack of competition among controller suppliers, which may result in a decline in controller quality and malicious price gouging, making it impossible to guarantee the quality and price of controller products.

[0059] To address the aforementioned issues, this application provides a data cutover method. First, in response to a data cutover command, firstly, first service data from a first controller is acquired. Then, the first service data is converted into target service data that can be processed by a second controller. The first and second controllers are heterogeneous controllers. Next, the target service data is cutovered to the second controller.

[0060] As can be seen from the above, this application employs a heterogeneous controller. In response to a data cutover command, it converts the first service data in the first controller into target service data that can be processed by the second controller, and then cuts over the target service data to the second controller. Thus, by using a heterogeneous controller and cutting over the data within it, security risks are reduced.

[0061] Secondly, heterogeneous controller deployment allows the network to expand flexibly to adapt to network environments of different sizes and needs.

[0062] Furthermore, using heterogeneous controllers can reduce dependence on a single vendor, increase network compatibility and selectivity, and help build a more open and competitive market environment.

[0063] Furthermore, the aforementioned data cutover method simplifies the network management process and improves the operational efficiency of the controller.

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

[0065] Figure 1 A schematic diagram of the SDN system provided in an embodiment of this application is shown. Figure 1 As shown, the SDN system includes: a business system module 101, a data cutover device (also known as a unified orchestrator) 102, a first controller 103, a second controller 104, and a network device 105.

[0066] The business system module 101 is communicatively connected to the data cutover device 102, which is connected to the first controller 103 and the second controller 104 respectively.

[0067] The first controller 103 and the second controller 104 are communicatively connected to the network device 105.

[0068] In practical applications, the first controller 103 and the second controller 104 can connect to any number of network devices 105. For ease of understanding, Figure 1 Let's take a network device 105 as an example for explanation.

[0069] The business system module 101 is used to send business requests 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 systems of the first controller 103 and the second controller 104 can be either Linux or CentOS.

[0073] 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 can be servers, terminals, or other types of electronic devices, and this application embodiment does not limit them.

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

[0076] Optionally, the aforementioned terminal may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, 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-embedded, or vehicle-mounted mobile device that exchanges voice and / or data with the radio access network, such as a mobile phone, tablet computer, laptop computer, netbook, or personal digital assistant (PDA).

[0077] Optionally, the server mentioned above can be one of the servers in a server cluster (composed of multiple servers), a chip in the server, a system-on-a-chip in the server, or a virtual machine (VM) deployed on a physical machine. This application embodiment does not limit this.

[0078] Data cutover devices in SDN systems include, for example, Figure 2 The components included. The following are examples. Figure 2 Taking the communication device shown as an example, the hardware structure of the data cutover device is introduced.

[0079] Figure 2 The diagram shown is a hardware structure schematic of a communication device provided in an embodiment of this 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 are connected via the bus 24.

[0080] Processor 21 is the control center of the communication device. It can be a single processor or a collective term for multiple processing elements. For example, 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 one embodiment, processor 21 may include one or more CPUs, for example Figure 2 CPU0 and CPU1 are shown in the diagram.

[0082] The memory 22 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0083] In one possible implementation, the memory 22 can exist independently of the processor 21. The memory 22 can be connected to the processor 21 via a bus 24 and is used to store instructions or program code. When the processor 21 calls and executes the instructions or program code stored in the memory 22, it can implement the data cutover method provided in the following embodiments of this application.

[0084] In this embodiment, the software programs stored in memory 22 differ for each communication device, resulting in different functions implemented by the communication devices. The functions performed by each device will be described in conjunction with the following flowcharts.

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

[0086] Communication interface 23 is used for connecting the communication device to other devices via a communication network, such as Ethernet, wireless access network, wireless local area network (WLAN), etc. Communication interface 23 may include a receiving unit for receiving data and a transmitting unit for sending data.

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

[0088] It should be pointed out that, Figure 2 The structure shown 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 illustrated, or combine certain components, or have different component arrangements.

[0089] The data cutover method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

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

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

[0092] In one possible implementation, the data cutover device, in response to a data cutover command, acquires first service data from a first controller, so as to cut over the first service data from the first controller to a second controller for processing. Therefore, the data cutover device needs to acquire the first service data from the first controller.

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

[0094] The first type of business data includes: network data (e.g., web browsing data, file download data, video data, audio data), network device Internet Protocol (IP), network device ports, and service type.

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

[0096] Among them, the first controller and the second controller are heterogeneous controllers.

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

[0098] In one possible implementation, after acquiring the first service data, the data cutover device needs to convert the first service data into target service data that can be processed by the second controller. In this way, the data cutover device can cut over the first service data to the second controller so that the second controller can read and process the target service data.

[0099] Specifically, first, the data cutover device parses the first business data. Then, the data cutover device converts the parsed first business data into a unified format and structure. Next, the data cutover device standardizes the first business data converted into a unified format and structure according to the data interface of the second controller, assembling it into target business data that the second controller can process.

[0100] S303, Transfer the target service data to the second controller.

[0101] In one possible implementation, the data cutover device needs to cut over 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 and second controllers.

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

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

[0104] In one feasible approach, the target service data that the data cutover device cuts to the second controller is service data that is different from the second service data in the second controller within the first service data. This avoids data duplication and improves the efficiency of data cutover.

[0105] Optionally, the data cutover equipment can also build a business data verification framework, using efficient data comparison algorithms to compare the first business data and the second business data, ensuring that the target business data cut over by the data cutover equipment is complete and error-free.

[0106] Optionally, the data cutover device can also cross-validate the comparison results of the first business data and the second business data with the preset target business data to check the consistency between the preset target business data and the business rules.

[0107] Optionally, the interface between the first controller and the second controller can be a northbound interface (e.g., 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 communication, and security auditing) should be implemented to prevent network attacks.

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

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

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

[0112] In some embodiments, combined with Figure 3 ,like Figure 4 As shown, the data cutover method also includes:

[0113] S401, Obtain the first resource data of the first controller.

[0114] In one feasible approach, the data cutover device needs to first transfer the first resource data from the first controller to the second controller. Only when the second controller possesses the first resource data can it process the business data in the first controller. Therefore, the data cutover device needs to acquire the first resource data from 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 definitions, 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 possible implementation, after acquiring 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 cut over the first resource data to the second controller so that the second controller can read and apply the target resource data.

[0119] Specifically, firstly, the data cutover device parses the first resource data. Then, the data cutover device converts the parsed first resource data into a unified format and structure, and standardizes the converted first resource data according to the data interface of the second controller, assembling it into target resource data that the second controller can process.

[0120] S403, Transfer target resource data to the second controller.

[0121] In one feasible approach, the data cutover device needs to cut over the target resource data to the second controller. This ensures the consistency and integrity of the resource data in the first and second controllers, so that the second controller can subsequently process the target business data based on 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 can also compare the comparison results of the first and second service data with the actual configuration parameters to ensure the accuracy of the target service data at the physical layer.

[0124] As can be seen from the above, the data cutover method described above can ensure the consistency of business 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 flowchart illustrating the data cutover method is shown.

[0126] First, the data cutover device calls the first controller to obtain the first resource data and first service data from the first controller. Then, the data cutover device calls the second controller to obtain the network device configuration (also known as the second resource data) from the network device. Next, the data cutover device calls the second controller to perform the data cutover. Then, the data cutover device compares the first resource data (including the network device configuration) with the second resource data, and the first service data with 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 cut over and integrated into the database.

[0127] Optionally, before performing data cutover, the data cutover device must first initialize the controller's state and detect the controller's state to ensure that the controller is in a stable and operable state, capable of processing business data and distributing network requests.

[0128] Optionally, network administrators can perform upgrades and deployments on the controller, including software updates and configuration adjustments, to improve the controller's network performance, compatibility, and security.

[0129] In some embodiments, combined with Figure 4 ,like Figure 6 As shown, the data cutover method also includes:

[0130] S601, Receive the first service request.

[0131] In one possible implementation, the first and second controllers are used to process business data, and the data cutover device can determine the data cutover frequency based on business requests. Therefore, the data cutover device can first receive a first business request to determine the generation frequency of data cutover instructions based on the data characteristics requested by the business request.

[0132] Combination Figure 1 The data cutover device can receive business requests issued by the business system modules.

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

[0134] S602. Determine the generation frequency of data cutover instructions based on data characteristics.

[0135] In one feasible approach, the data cutover device can determine the generation frequency of data cutover instructions based on the data characteristics of the data requested by the service request. This ensures that the data between the first controller and the second controller remains highly consistent in terms of time and content.

[0136] For example, when data timeliness is high, data cutover instructions are generated more frequently. Conversely, when data timeliness is low, data cutover instructions are generated less frequently.

[0137] As another example, when the data volume is large, the data cutover command is generated more frequently. Conversely, when the data volume is small, the data cutover command is generated less frequently.

[0138] As another example, when the data is time-sensitive and the data volume is small, the data cutover command is generated more frequently. Conversely, when the data is less time-sensitive and the data volume is large, the data cutover command is generated more frequently.

[0139] Optionally, when the data cutover device generates a data cutover command for the first time, the data cutover device can cut over all data (including business data and resource data) from the first control device to the second control device (which can also be called full synchronization).

[0140] Optionally, when the data cutover device generates a data cutover command, it may only transmit the data that has changed (also known as incremental synchronization). That is, when the first service data and / or the first resource data in the first controller change, the data that has changed will be cut over 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 data merging, overwriting or rollback operations according to preset priorities and rule sets to ensure the eventual consistency of the data.

[0142] Optionally, the data cutover device can be set to cut over data at regular intervals, that is, the frequency of generating data cutover instructions is determined according to the data characteristics of the data requested by the business request.

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

[0144] Optionally, the data cutover equipment can perform data cutover during periods of low business activity to minimize the impact on the production environment.

[0145] Optionally, in the event of an unexpected termination during data cutover, breakpoint resume technology can be introduced. The data cutover device can record the synchronization progress and automatically resume synchronization from the point of interruption after the connection is restored, effectively avoiding the risks of repetitive work and data loss.

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

[0147] In some embodiments, combined with Figure 4 ,like Figure 7 As shown, the data cutover method also includes:

[0148] S701, In the event of a failure in the first controller, generate a data cutover command.

[0149] In one feasible implementation, the data cutover device can generate a data cutover command in the event of a failure in the first controller, enabling the second controller to acquire the first service data from the first controller. Thus, even if the first controller fails, the second controller can still process the first service data, and network service will not be interrupted.

[0150] In some embodiments, combined with Figure 4 ,like Figure 8 As shown, the data cutover method also includes:

[0151] S801, Receive the second service request.

[0152] In one possible implementation, the first controller and the second controller are used to process business data. The data cutover device can determine the controller to process the business request based on the failure status of the first controller and the second controller. Therefore, the data cutover device can receive the second business request.

[0153] S802, under normal operation of the first controller and the second controller, control the first controller and the second controller to process the second service request.

[0154] In one feasible approach, with the first and second controllers operating normally, the data cutover device can control the first and second controllers to process second service requests. This can improve the efficiency of network services and ensure the consistency of service data and resource data between the first and second controllers.

[0155] Optionally, the first and second controllers can operate in parallel.

[0156] The first and second controllers are two independent controllers, each with its own Central Processing Unit (CPU), internal storage, and interface with network devices. Because the first and second controllers are heterogeneous, with different hardware and software configurations, their joint management of the network improves network flexibility and adaptability.

[0157] Optionally, if 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, in the event of a failure of one of the first and second controllers, control the other controller to process the second service request.

[0159] In one feasible approach, if one of the first and second controllers fails, the other controller processes the second service request data, thus ensuring the continuity of network services.

[0160] Optionally, the second controller can serve as a backup controller for the first controller. The first controller is responsible for processing business data, while the second controller is responsible for receiving synchronization data (i.e., 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. If the first controller is found to be malfunctioning while the second controller is functioning normally, 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 operation of the first controller.

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

[0163] For example, Figure 9 A flowchart illustrating a switching controller is shown.

[0164] The data cutover device controls the first controller to process service data. If an anomaly is detected in the first controller, the data cutover device switches between the first and second controllers. The data cutover device also checks the status of the second controller. If the second controller is functioning normally, the data cutover device controls the second controller to process service data, and the second controller connects to the network equipment and sends services.

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

[0166] The controller switching process is as follows:

[0167] First, the first controller sends a state change notification to the second controller, instructing the second controller to prepare to take over the tasks of the first controller. Then, upon receiving the notification, the second controller performs an internal state check to confirm its capability to take over the tasks of the first controller. Next, the second controller officially becomes the new first controller and begins executing the distribution operation; the first controller becomes the second controller and receives synchronization data from the first controller. That is, the second controller (formerly the first controller) obtains data from the first controller (formerly the second controller). To ensure data consistency, the second controller (formerly the first controller) obtains the latest state information from the first controller (formerly the second controller) and performs data synchronization.

[0168] After the controller switchover is complete, the SDN system should send a notification to all external systems that depend on the first and second controllers, informing them of the current status.

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

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

[0171] Optionally, the data cutover device can obtain the controller's status information, including: health status, link quality, and traffic distribution.

[0172] The controller can provide a comprehensive view of network operation and maintenance. Relevant personnel can quickly determine the location of the controller problem based on the controller's status information, so as to optimize network performance and improve operation and maintenance efficiency.

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

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

[0175] As can be seen from the above, when cutting data, the data cutover device is based on a preset synchronization protocol, such as incremental synchronization based on timestamps (i.e., determining the generation frequency of data cutover commands) or real-time synchronization driven by events (i.e., in the event of a failure of the first controller).

[0176] In some embodiments, combined with Figure 4 ,like Figure 10 As shown, the data cutover method also includes:

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

[0178] In one feasible approach, the data cutover device can also acquire backup data of the first service data and back it up to the first backup controller, thus ensuring that the first service data is not lost during the data cutover process.

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

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

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

[0182] In one feasible approach, the data cutover device can also back up backup data to the first backup controller, thus ensuring that the first business data is not lost during the data cutover process.

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

[0184] Optionally, network administrators can adjust the configuration parameters of the first and second controllers based on their actual operating conditions to optimize network performance.

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

[0186] Optionally, network administrators can also learn and distribute the SDN system's operation manuals and technical documents to ensure the normal operation of the network.

[0187] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0188] This application embodiment can divide the data cutover device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0189] Figure 11 A schematic diagram of a data cutover device provided in an embodiment of this application is shown. Figure 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 acquire the first service data of the first controller in response to the data cutover command; the processing unit 1102 is used to convert the first service data into target service 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 cut over the target service data to the second controller.

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

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

[0193] Optionally, the communication unit 1101 is further configured 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 1102 is further configured to determine the generation frequency of the data cutover instruction based on the data characteristics.

[0194] Optionally, the processing unit 1102 is also configured to generate a data cutover instruction in the event of a failure of the first controller.

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

[0196] Optionally, the communication unit 1101 is further configured to acquire backup data of the first service data; the processing unit 1102 is further configured to back up the backup data to the first backup controller; the first controller and the first backup controller are homogeneous controllers.

[0197] This application also provides a computer-readable storage medium, which includes computer-executable instructions. When the computer-executable instructions are executed on a computer, the computer performs the data cutover method provided in the above embodiments.

[0198] This application also provides a computer program that 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 embodiments.

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

[0200] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above 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 the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and other division methods may exist in actual implementation. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms. Units described as separate components may or may not be physically separate; components shown as units may be one physical unit or multiple physical units, i.e., they may be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0202] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to general technology, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0203] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data cutover method, characterized in that, The method includes: In response to the data cutover command, the first service data of the first controller is obtained; The first service data is converted into target service data that can be processed by the second controller; the first controller and the second controller are heterogeneous controllers; the target service data includes: service data in the first service data that is different from the second service data of the second controller; The service data that is different from the second service data in the first service data is cut off to the second controller.

2. The method according to claim 1, characterized in that, The method further includes: Obtain the first resource data of the first controller; The first resource data is converted into target resource data that can be used by the second controller; The target resource data is cut over to the second controller.

3. The method according to claim 1, characterized in that, The method further includes: 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 generation frequency of the data cutover command is determined based on the data characteristics.

4. The method according to claim 1, characterized in that, The method further includes: In the event of a failure in the first controller, the data cutover command is generated.

5. The method according to claim 1, characterized in that, The method further includes: Receive the second service request; When the first controller and the second controller are operating normally, control the first controller and the second controller to process the second service request; In the event of a failure of one of the first and second controllers, the other controller is controlled to process the second service request.

6. The method according to claim 1, characterized in that, The method further includes: Obtain backup data of the first business data; The backup data is backed up to the first backup controller; the first controller and the first backup controller are homogeneous controllers.

7. A data cutover device, characterized in that, The device includes: 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 a data cutover command; The processing unit is used to convert the first service data into target service data that can be processed by the second controller; the first controller and the second controller are heterogeneous controllers; the target service data includes: service data in the first service data that is different from the second service data of the second controller. The service data that is different from the second service data in the first service data is cut off to the second controller.

8. A data cutover device, characterized in that, include: A processor and a memory; wherein the memory is used to store one or more programs, the one or more programs including computer-executable instructions, wherein when the device is running, the processor executes the computer-executable instructions stored in the memory to cause the device to perform the method of any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, When the computer-executable instructions stored in the computer-readable storage medium are executed by the processor of the data cutover device, the data cutover device is capable of performing the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 6.

Images