Offline configuration method and system based on SDN controller, and controller and medium

By introducing configuration queues and task deduplication strategies into the SDN network and detecting the online status of devices, the high availability problem when devices are offline is solved, the fault tolerance and configuration efficiency of the system are improved, and dual high availability of the data plane and the control plane is achieved.

WO2024227355A1PCT designated stage expired Publication Date: 2024-11-07CHINA TELECOM CLOUD TECH CO LTD

Patent Information

Application Number
PCT/CN2023/142694
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-12-13
Filing Date
2023-12-28
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Existing SDN networks suffer from low system efficiency when devices are offline. Configuration tables are only applicable to persistent scenarios. The underlying modules are coupled with user modules, resulting in poor fault tolerance and an inability to achieve true high availability and maintainability.

Method used

By deploying control nodes, protocol nodes, database nodes, MQ services, and network element devices in the SDN network, device clusters are formed based on geographical classification. A minimum number of available devices is set, configuration queues and task deduplication strategies are introduced, and the online status of devices is detected. This enables offline processing and scheduled repair of configuration tasks, reducing the interaction between the control plane and devices.

Benefits of technology

It achieves high availability when devices are offline, reduces system failures, improves the consumption efficiency of the configuration queue, and achieves dual high availability on both the data plane and the control plane, reducing the impact of single points of failure perceived by customers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023142694_07112024_PF_FP_ABST
    Figure CN2023142694_07112024_PF_FP_ABST
Patent Text Reader

Abstract

The present invention belongs to the field of cloud computing. Disclosed are an offline configuration method and system based on an SDN controller, and a controller and a medium. The method comprises: performing node deployment in an SDN; setting the minimum number of available devices of each regional network element device cluster; a user initiating a service request, and after receiving the request, a control node verifying a corresponding regional network element device cluster of service data on the basis of a cluster availability verification rule; after the verification is completed, splitting the service request by means of an SDN controller, so as to obtain configuration task data, and performing task deduplication; storing the configuration task data in a database, detecting an online state of a corresponding network element device, and storing the configuration task data in a configuration queue of the corresponding network element device; and reading the configuration task data from the configuration queue, and performing consumption on the basis of the online state of the corresponding network element device. By means of the technical solution of the present invention, dual high availability of a cloud gateway cluster in a data plane and a management and control plane is achieved, thereby reducing system faults and service payment failures.
Need to check novelty before this filing date? Find Prior Art

Description

Offline configuration method, system, controller and medium based on SDN controller Technical Field

[0001] The present invention belongs to the field of cloud computing, and in particular relates to an offline configuration method, system, controller and medium based on an SDN controller. Background Art

[0002] SDN is an emerging network architecture that separates network control from forwarding functions, enabling programmable control. This architecture shifts the control layer from network devices to external computing devices, making the underlying infrastructure transparent and abstract to applications and network services. The network can be viewed as a logical or virtual entity.

[0003] In a public cloud, each region may host multiple VPCs. These VPCs connect to the same tenant's VPCs in the same or different regions through a cloud gateway device connected to that region. Therefore, as the backbone router of the SDN network, the cloud gateway carries a large amount of traffic from PE devices to the cloud and between VPCs on the cloud. Therefore, the availability of the cloud gateway becomes a bottleneck for the stability of the SDN system.

[0004] To ensure stable and reliable data plane operation, cloud gateways in each region are typically designed for high availability. Cloud gateways correspond to one or more underlying gateway clusters. These devices may be deployed on separate physical servers or share a server with other gateway devices. They may be located in the same region or across regions for high availability. Each cluster is independent, with its own public network management IP address and a separate NETCONF connection to the control layer. The control layer's protocol nodes maintain NETCONF channels within the cluster, and the control node ensures member configuration consistency. Currently, due to device anomalies or network fluctuations, one or two members in a cluster may occasionally go offline. In these cases, the control node will intercept service requests and return a failure message, citing the cluster's abnormal status. This approach ensures cluster configuration consistency but ignores the need for high device availability. In this case, the cluster should be able to support service operations and traffic flow. If the entire system is locked down due to a single device anomaly, true high availability is not achieved and fault tolerance and maintainability are reduced.

[0005] SDN systems require control nodes to synchronize routing across the entire network. This means that each business operation control node must handle a large number of devices. In real-world scenarios, device offlines in the target cluster are inevitable. While offline alarms and reconnection mechanisms ensure continuous connectivity between devices and protocol nodes, if an offline device fails to reconnect after exceeding a threshold, the process from alarm generation to manual processing and system service restoration still takes time. If a device experiences a serious failure and requires replacement, the duration of service interruption is unpredictable. Optimizing the NETCONF connection mechanism alone does not completely resolve the single point of failure issue. This indicates that the control system still lacks the capabilities to support device high availability, maintain cluster configuration consistency, and ensure cluster reliability.

[0006] Existing offline configuration solutions have the following defects:

[0007] 1. In scenarios where there are a large number of devices on the network and a large number of configuration requests, the system may be frequently locked due to devices going offline and then back online, affecting system efficiency. This makes it unsuitable for large-scale SDN networks.

[0008] 2. The configuration table only records previously successfully issued configurations and is only applicable to device configuration persistence scenarios and cannot be used in other scenarios.

[0009] 3. The underlying module and the user module are blocked synchronously, which is equivalent to being coupled together. Failure of the underlying configuration will be fed back to the user module and interrupt the service, and the fault tolerance of the entire system is poor.

[0010] Summary of the Invention

[0011] The purpose of the present invention is to provide an offline configuration method, system, controller and medium based on an SDN controller to solve the problems existing in the above-mentioned prior art.

[0012] To achieve the above objectives, the present invention provides an offline configuration method based on an SDN controller, comprising:

[0013] Step 1: Deploy control nodes, protocol nodes, DB nodes, MQ services, and network element devices in the SDN network;

[0014] Step 2: Classify the network element devices based on region, obtain network element device clusters in each region, and set the minimum number of available devices for each network element device cluster in the region;

[0015] Step 3: The control node creates a device configuration queue and a repair queue, and the protocol node creates a consumer and binds the configuration queue;

[0016] Step 4: The user initiates a service request using the portal website and sends the request to the control node through the interface. After receiving the request, the control node verifies the regional network element device cluster corresponding to the service data based on the cluster availability verification rule;

[0017] Step 5: After verification is completed, the service request is split through the SDN controller to obtain configuration task data and perform task deduplication on the configuration task data;

[0018] Step 6: storing the configuration task data in a database and initializing the state of the configuration task data;

[0019] Step 7: Detecting the online status of the corresponding network element device, and when the corresponding network element device is online, storing the configuration task data in the configuration queue of the corresponding network element device;

[0020] Step 8: Read the configuration task data from the configuration queue and detect the online status of the corresponding network element device. If the corresponding network element device is offline, initialize the status of the read configuration task data; if the corresponding network element device is online, the consumer consumes based on the read configuration task data.

[0021] Optionally, after receiving the request, the control node verifies the regional network element device cluster corresponding to the service data based on a cluster availability verification rule, specifically including:

[0022] Based on the cluster availability verification rules, the number of online devices in the corresponding regional network element device cluster of the business data is detected. If the number of online devices is less than the minimum number of available devices corresponding to the regional network element device cluster, the request is terminated and feedback is given to the upper layer; if the number of online devices is greater than or equal to the minimum number of available devices corresponding to the regional network element device cluster, step five is executed.

[0023] Optionally, obtaining configuration task data and performing task deduplication on the configuration task data specifically includes:

[0024] Obtain the key, configuration content, status update time and operation type of each configuration task data;

[0025] When there is configuration task data with the same key and operation type but different configuration content, duplicates are removed based on the status update time of the configuration task data;

[0026] When there is configuration task data with the same key but different operation types, deduplication is performed based on the expected value of the configuration task data and the actual task execution status.

[0027] Optionally, store the configuration task data in the database, including:

[0028] The configuration task data is stored in the task table in the database based on the configuration dependency order, ensuring that the tasks stored first are added to the configuration queue first.

[0029] Optionally, storing the configuration task data in a configuration queue of a corresponding network element device;

[0030] The status of the configuration task data in the database is regularly queried at the set time using a timed scanning method, the configuration task data after status initialization is added to the configuration queue of the corresponding network element device in chronological order, and the status of the configuration task data successfully added to the configuration queue is updated to TODO.

[0031] Optionally, in the process of periodically querying the status of the configuration task data in the database at a set time in a timed scanning manner, the configuration task data whose status is not updated within the set time is cleared.

[0032] Optionally, the consumer consumes based on the read configuration task data, including:

[0033] Convert the read configuration task data into XML format data, lock the XML format data and send it to the corresponding network element device for configuration;

[0034] If the configuration is successful, the task status will be updated to success. If the configuration fails, the task status will be updated to fail. Tasks that fail no more than three times will be retried. If they still fail after three retries, the status of the configuration task data will be scanned based on the repair program, and the configuration task data with the fail status will be re-sent to the corresponding network element device for configuration. If the repair is successful, the task status will be updated to success. If the repair fails, an alarm message will be generated and feedback will be provided.

[0035] An offline configuration system based on an SDN controller includes: a network deployment configuration module for deploying control nodes, protocol nodes, DB nodes, MQ services, and network element devices in an SDN network; classifying the network element devices based on region, obtaining network element device clusters in each region, and setting a minimum number of available devices for each network element device cluster in each region; the control node creating a device configuration queue and a repair queue, and the protocol node creating a consumer and binding the configuration queue;

[0036] The service request module is used to enable users to initiate service requests through the portal website and send the request to the control node through the interface. After receiving the request, the control node verifies the corresponding regional network element device cluster of the service data based on the cluster availability verification rule; after the verification is completed, the SDN controller splits the service request to obtain configuration task data and deduplicates the configuration task data;

[0037] The task storage and distribution module is used to store the configuration task data in the database and initialize the status of the configuration task data; detect the online status of the corresponding network element device, and when the corresponding network element device is online, store the configuration task data in the configuration queue of the corresponding network element device;

[0038] The configuration module is used to read the configuration task data from the configuration queue, detect the online status of the corresponding network element device, and initialize the status of the read configuration task data if the corresponding network element device is offline; if the corresponding network element device is online, the consumer consumes based on the read configuration task data.

[0039] An SDN controller comprises: a processor and a memory communicatively connected to the processor;

[0040] The memory stores computer instructions; and the processor is used to implement the offline configuration method based on the SDN controller when executing the computer instructions.

[0041] A computer-readable storage medium stores computer instructions, which, when executed by a processor, are used to implement an offline configuration method based on an SDN controller as described above.

[0042] The technical effects of the present invention are:

[0043] The present invention allows operation and maintenance personnel to customize cluster availability conditions and customize alarm rules for cluster availability. When the device status in the cluster exceeds the threshold, messages can be pushed in time, so that operation and maintenance personnel can perceive the problem and repair it before the customer reports the problem. The present invention introduces a configuration queue in the process of configuration distribution to achieve application decoupling. At the same time, task deduplication strategy and offline pause strategy are added to reduce the interaction between the control plane and the device in the south, and speed up the consumption of the configuration queue. In conjunction with operation and maintenance mechanisms such as timed repair, expired task cleanup and failure alarms, a closed loop of the control plane abnormal process can be achieved; the cloud gateway cluster is achieved with dual high availability on the data plane and the control plane, so that customers cannot perceive single points of failure within the cluster, reducing system failures and business card slots. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0045] The accompanying drawings, which constitute part of this application, are intended to provide a further understanding of this application. The exemplary embodiments and descriptions of this application are intended to explain this application and do not constitute an improper limitation on this application. In the accompanying drawings:

[0046] FIG1 is a flowchart of offline configuration in an embodiment of the present invention;

[0047] FIG2 is a diagram of an SDN network deployment in an embodiment of the present invention;

[0048] FIG3 is a hierarchical architecture diagram of a control system in an embodiment of the present invention;

[0049] FIG4 is a flowchart of task state transition in an embodiment of the present invention;

[0050] FIG5 is a business process diagram according to an embodiment of the present invention;

[0051] FIG6 is a flow chart of configuration delivery in an embodiment of the present invention. DETAILED DESCRIPTION

[0052] Various exemplary embodiments of the present invention will now be described in detail. This detailed description should not be considered as limiting the present invention, but rather as a more detailed description of certain aspects, features, and embodiments of the present invention.

[0053] It should be understood that the terms described herein are intended only to describe particular embodiments and are not intended to limit the present invention. In addition, for numerical ranges herein, it should be understood that each intermediate value between the upper and lower limits of the range is also specifically disclosed. Each smaller range between any intermediate value within a stated value or stated range and any other stated value or intermediate value within the stated range is also encompassed by the present invention. The upper and lower limits of these smaller ranges may be independently included or excluded within the scope.

[0054] Unless otherwise indicated, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art. Although only preferred methods are described herein, any method similar or equivalent to that described herein may also be used in the practice or testing of the present invention. All documents mentioned in this specification are incorporated by reference to disclose and describe the methods associated with the documents. In the event of any conflict with any incorporated document, the contents of this specification shall prevail.

[0055] It will be apparent to those skilled in the art that various modifications and variations may be made to the specific embodiments of the present invention without departing from the scope or spirit of the invention. Other embodiments will be apparent to those skilled in the art from the present invention. The present description and examples are intended to be illustrative only.

[0056] The words “include,” “including,” “have,” “contain,” etc. used in this article are open-ended terms, meaning including but not limited to.

[0057] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0058] Example 1

[0059] As shown in Figures 1 to 6, this embodiment provides an offline configuration method based on an SDN controller, including: deploying a control node, a protocol node, a DB node, an MQ service, and network element devices in an SDN network; classifying the network element devices based on region, obtaining network element device clusters in each region, and setting a minimum number of available devices for each network element device cluster in each region; the control node creating a device configuration queue and a repair queue, and the protocol node creating a consumer and binding the configuration queue;

[0060] The user initiates a service request through the portal website and sends it to the control node through the interface. After receiving the request, the control node verifies the corresponding regional network element device cluster of the service data based on the cluster availability verification rules; after the verification is completed, the SDN controller splits the service request to obtain configuration task data and deduplicates the configuration task data;

[0061] The configuration task data is stored in a database, and the status of the configuration task data is initialized; the online status of the corresponding network element device is detected, and when the corresponding network element device is online, the configuration task data is stored in the configuration queue of the corresponding network element device; the configuration task data is read from the configuration queue, and the online status of the corresponding network element device is detected. If the corresponding network element device is offline, the status of the read configuration task data is initialized; if the corresponding network element device is online, the consumer consumes based on the read configuration task data.

[0062] An offline configuration system based on an SDN controller includes: a network deployment configuration module for deploying control nodes, protocol nodes, DB nodes, MQ services, and network element devices in an SDN network; classifying the network element devices based on region, obtaining network element device clusters in each region, and setting a minimum number of available devices for each network element device cluster in each region; the control node creating a device configuration queue and a repair queue, and the protocol node creating a consumer and binding the configuration queue;

[0063] The service request module is used to enable users to initiate service requests through the portal website and send the request to the control node through the interface. After receiving the request, the control node verifies the corresponding regional network element device cluster of the service data based on the cluster availability verification rule; after the verification is completed, the SDN controller splits the service request to obtain configuration task data and deduplicates the configuration task data;

[0064] The task storage and distribution module is used to store the configuration task data in the database and initialize the status of the configuration task data; detect the online status of the corresponding network element device, and when the corresponding network element device is online, store the configuration task data in the configuration queue of the corresponding network element device;

[0065] The configuration module is used to read the configuration task data from the configuration queue, detect the online status of the corresponding network element device, and initialize the status of the read configuration task data if the corresponding network element device is offline; if the corresponding network element device is online, the consumer consumes based on the read configuration task data.

[0066] An SDN controller comprises: a processor and a memory communicatively connected to the processor;

[0067] The memory stores computer instructions; and the processor is used to implement the offline configuration method based on the SDN controller when executing the computer instructions.

[0068] A computer-readable storage medium stores computer instructions, which, when executed by a processor, are used to implement an offline configuration method based on an SDN controller as described above.

[0069] This embodiment allows operation and maintenance personnel to customize cluster availability conditions and customize alarm rules for cluster availability. When the device status in the cluster exceeds the threshold, it will push messages in a timely manner, allowing operation and maintenance personnel to perceive the problem and repair it before the customer reports the problem. This embodiment introduces a configuration queue in the process of configuration distribution to achieve application decoupling. At the same time, task deduplication strategy and offline suspension strategy are added to reduce the interaction between the control plane and the device in the south, and speed up the consumption of the configuration queue. In conjunction with operation and maintenance mechanisms such as scheduled repair, expired task cleanup and failure alarms, a closed loop of the control plane abnormal process can be achieved; the cloud gateway cluster is achieved with dual high availability on the data plane and the control plane, so that customers cannot perceive single points of failure within the cluster, reducing system failures and business card issues.

[0070] The specific implementation process of this embodiment is as follows:

[0071] Step 1: Deploy control nodes, protocol nodes, DB nodes, MQ services, and network elements in the SDN network;

[0072] Step 2: The controller manages the devices.

[0073] Step 3: After the device is online, the control node creates a device configuration queue and a repair queue, and the protocol node creates a consumer and binds it to the configuration queue.

[0074] Step 4: Set the minimum available device quantity N for the device clusters in each region through the operation and maintenance interface.

[0075] Step 5: The user发起 a service request using the portal website, requests to the control node through the northbound interface, and the control node responds after receiving the request.

[0076] Step 6: The control node verifies the cluster availability. If the number of online devices < N, the request is terminated and feedback is sent to the upper layer. If the number of online devices > N, the service process is started.

[0077] Step 7: The controller splits the service request into a set of configuration tasks, stores them in the DB in the order of configuration dependencies, and initializes the status as INTI. Since the devices have dependencies on the configuration order, it is necessary to ensure that the tasks stored in the library first are added to the configuration queue first. In this embodiment, a timed scanning method is used to periodically query the task table, and the tasks with the status of INTI are added to the message queue of the corresponding device in the order of time. If successful, the status is updated to TODO. If failed, wait for the next attempt.

[0078] Step 8: After all the configuration tasks are added to the message queue and stored in the library, the controller returns success to the upper layer.

[0079] Step 9: The consumer reads the tasks from the message queue for consumption. If the configuration is successful, the task status is updated to success. If the configuration fails, the task status is updated to fail. Tasks that fail no more than three times will be retried. If they still fail after three retries, they will not be retried anymore but wait for timed repair. After the repair program is started, it will scan the configuration table, resend the tasks with the status of fail in the table. If the repair is successful, the task status is updated to success. If the repair fails, an alarm is issued and manual intervention is requested.

[0080] Custom cluster availability verification rules: The current rule is that the control node requires all devices in the cluster to be online before it can continue to respond to business requests. This solution modifies the policy so that services can be delivered only when there are >= N (N>= 1) devices online in the cluster. Usually, when N is greater than 1, business configuration can be delivered and connectivity can be achieved. However, imagine that in some cases, the customer-side traffic is large and there is a large-scale failure in the cluster with only one device available. This scenario is a case of insufficient hard conditions. It is better to prioritize resolving the device group failure before launching the business. This solution provides manual support for operation and maintenance to modify the N value of each device cluster. Operation and maintenance personnel can set the minimum number of devices required for the cluster to be available based on the business traffic size and device performance of each resource pool / device cluster. Ensure that the underlying equipment of each business launched also has sufficient performance to carry it.

[0081] Using message queues to process configuration tasks: To ensure that devices can continue to receive service requests during configuration recovery, this embodiment uses a message queue-based configuration delivery method. When each device comes online, the control node creates a message queue to send configuration tasks. The protocol node initializes a consumer to respond to configuration tasks and deliver configurations to the device.

[0082] The messages in the message queue are a series of configuration data split from business requests. Each configuration data is a message, corresponding to a task. The task data is persisted in the DB database, as shown in Table 1:

[0083] Table 1 Task data

[0084] During the message generation and consumption process, some processing is performed on the task data:

[0085] Task deduplication: To prevent consumers from making duplicate purchases, reduce the number of interactions between protocol nodes and devices, and speed up queue consumption, configuration tasks are deduplicated based on config-key, config-content, and operation before being stored in the database. Because deduplication involves modifying the task data state, and to avoid concurrency issues during task data state transfer, this solution limits tasks with the same config-key to only one thread at a time for configuration distribution and database updates.

[0086] (1) If the same configuration is updated multiple times, the last update will prevail: For tasks with the same config-key and operation but different config-content, only the last task will be stored in the database and the status of all previously unexecuted tasks will be updated to cancel.

[0087] (2) Opposite operations on the same configuration cancel each other out: For tasks with opposite operation types for the same config-key, deduplication is performed based on the expected value of the configuration and the actual task execution status: For example, if a customer successively adds and then deletes a route, then his expected result is that the route does not exist on the device. At this time, it is necessary to check whether there is a pending route addition operation. If so, it means that the route has not yet been actually sent to the device, and the current status of the device is in line with expectations. At this time, it is necessary to try to cancel the task of adding the route, that is, change the status of the task to cancel. If the modification is successful, the task is successfully canceled, and the task of deleting the route does not need to be stored in the warehouse; if the modification fails, it means that the consumer is already executing this task, so regardless of whether the addition is successful, the task of deleting the route will be stored normally.

[0088] (3) The consumer verifies the message when consuming, that is, searches for the task according to the task-id. If no data is found or the task is canceled, the consumer directly returns a successful consumption without actually sending the configuration.

[0089] Offline pause: To avoid invalid consumption or message accumulation, the control node and protocol node suspend the configuration task queue and configuration distribution when they detect that the device is offline, and resume them after the device is online. After the producer generates task data, it will not add it to the message queue, but only store it in the database. For messages that already exist in the message queue when the device is offline, after the consumer obtains them, it will not distribute the configuration and will only update the task status to INIT.

[0090] Scheduled cleanup: Configuration tasks are persisted to the database, ensuring data is not lost across controller node restarts. To prevent message accumulation caused by excessive task data, this solution proposes a scheduled configuration data cleanup strategy. This strategy initiates a scheduled database scan and deletes configuration data that has not been updated for more than 10 minutes. This expiration time can be set differently for different device types or task types.

[0091] Scalability of this embodiment: In a production environment with many devices and tasks, MQ clusters can be deployed to reduce the pressure on MQ and avoid single points of failure. The specific deployment plan depends on the actual situation and will not be discussed in depth in this embodiment.

[0092] The control node of this embodiment can accurately identify devices with abnormal connection status and determine whether the cluster status is normal based on the policy; on the premise of confirming that the cluster is available, it skips the offline devices and only sends configurations to the online devices; the offline of one or more devices in the cluster of this embodiment will not interrupt the system service, that is, in the following two scenarios, the controller can still respond normally, and there will be no configuration or data confusion, and the device restarts during the service delivery process; the device goes from offline to online and in the configuration recovery phase, the controller receives a new service request; this embodiment supports the recovery of the configuration skipped during the offline period after the device status returns to normal; this embodiment can close the loop for abnormal phenomena in the configuration recovery process. The control node

[0093] The above description is merely a preferred embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. An offline configuration method based on an SDN controller, characterized in that: include: Step 1: Deploy control nodes, protocol nodes, DB nodes, MQ services and network element devices in the SDN network; Step 2: Classify the network element devices based on regions, obtain network element device clusters in each region, and set the minimum number of available devices for each network element device cluster in each region; Step 3: The control node creates a device configuration queue and a repair queue, and the protocol node creates a consumer and binds the configuration queue; Step 4: The user initiates a service request using the portal website and sends the request to the control node through the interface. After receiving the request, the control node verifies the corresponding regional network element device cluster of the service data based on the cluster availability verification rule; Step 5: After the verification is completed, the service request is split through the SDN controller to obtain configuration task data and perform task deduplication on the configuration task data; Step 6: storing the configuration task data in a database and initializing the state of the configuration task data; Step 7: Detecting the online status of the corresponding network element device, and when the corresponding network element device is online, storing the configuration task data in the configuration queue of the corresponding network element device; Step 8: Read the configuration task data from the configuration queue, detect the online status of the corresponding network element device, and if the corresponding network element device is offline, initialize the status of the read configuration task data; If the corresponding network element device is online, the consumer consumes based on the read configuration task data.

2. The offline configuration method according to claim 1, characterized in that: After receiving the request, the control node verifies the corresponding regional network element device cluster of the service data based on the cluster availability verification rule, specifically including: Based on the cluster availability verification rules, the number of online devices in the corresponding regional network element device cluster of the business data is detected. If the number of online devices is less than the minimum number of available devices corresponding to the regional network element device cluster, the request is terminated and feedback is given to the upper layer; if the number of online devices is greater than or equal to the minimum number of available devices corresponding to the regional network element device cluster, step five is executed.

3. The offline configuration method according to claim 1, characterized in that: Obtaining configuration task data and performing task deduplication on the configuration task data specifically includes: Obtain the key, configuration content, status update time and operation type of each configuration task data; When there are configuration task data with the same key and operation type but different configuration contents, Set the status update time of task data to deduplicate; When there is configuration task data with the same key but different operation types, deduplication is performed based on the expected value of the configuration task data and the actual task execution status.

4. The offline configuration method according to claim 1, characterized in that: Store configuration task data in the database, including: The configuration task data is stored in the task table in the database based on the configuration dependency order, ensuring that the tasks stored first are added to the configuration queue first.

5. The offline configuration method according to claim 1, characterized in that: Storing the configuration task data in a configuration queue of a corresponding network element device; The status of the configuration task data in the database is queried regularly at set times using a timed scanning method, the configuration task data after status initialization is added to the configuration queue of the corresponding network element device in chronological order, and the status of the configuration task data successfully added to the configuration queue is updated to TODO.

6. The offline configuration method according to claim 5, characterized in that: In the process of periodically querying the status of the configuration task data in the database at a set time in a timed scanning manner, the configuration task data whose status is not updated within the set time is cleared.

7. The offline configuration method according to claim 1, characterized in that: Consumers consume based on the read configuration task data, including: Convert the read configuration task data into XML format data, lock the XML format data and send it to the corresponding network element device for configuration; If the configuration is successful, the task status will be updated to success; if the configuration fails, the task status will be updated to fail. Tasks that fail no more than three times will be retried. If they still fail after three retries, the status of the configuration task data will be scanned based on the repair program, and the configuration task data with a status of fail will be re-sent to the corresponding network element device for configuration. If the repair is successful, the task status will be updated to success; if the repair fails, an alarm message will be generated and feedback will be given.

8. An offline configuration system based on SDN controller, characterized in that: include: Network deployment configuration module, used to deploy control nodes, protocol nodes, DB nodes, MQ services and network element devices in the SDN network; Classifying the network element devices based on regions, obtaining network element device clusters in each region and setting the minimum number of available devices for each network element device cluster in each region; The control node creates a device configuration queue and a repair queue, and the protocol node creates a consumer and binds the configuration queue; The service request module is used to enable users to initiate service requests through the portal website and request to The control node verifies the corresponding regional network element device cluster of the service data based on the cluster availability verification rule after receiving the request; After the verification is completed, the service request is split through the SDN controller to obtain configuration task data and perform task deduplication on the configuration task data; The task storage and delivery module is used to store the configuration task data into the database and initialize the status of the configuration task data; Detecting the online status of the corresponding network element device, and when the corresponding network element device is online, storing the configuration task data in the configuration queue of the corresponding network element device; A configuration module, used to read the configuration task data from the configuration queue, detect the online status of the corresponding network element device, and initialize the status of the read configuration task data if the corresponding network element device is offline; If the corresponding network element device is online, the consumer consumes based on the read configuration task data.

9. An SDN controller, characterized in that: include: A processor and a memory communicatively connected to the processor; The memory stores computer instructions; When executing the computer instructions, the processor is used to implement an offline configuration method based on an SDN controller as described in claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, they are used to implement an offline configuration method based on an SDN controller as described in claims 1 to 7.

Citation Information

Patent Citations

  • High-available architecture design method of SDN cluster controller

    CN106953744A

  • SDN operation and maintenance method, device and equipment and readable storage medium

    CN111142878A

  • Data processing method and system, storage medium and equipment

    CN116319988A

  • Data transmission method and device, equipment and storage medium

    CN117081921A

  • System and method for auto-clustering of clusterable services

    WO2022086996A1

Cited By

  • Metadata processing method, computer equipment, readable storage medium and program product

    CN120029830A

  • Metadata Processing Method, Computer Device, Readable Storage Medium and Program Product

    CN120029830B