Configuration management and control method and device of network element equipment and computer equipment

Abstract

The invention relates to a configuration management and control method and device of network element equipment and computer equipment. The method comprises the following steps: acquiring a service operation and maintenance request and southbound configuration data, and decoding the service operation and maintenance request to obtain service data; converting the southbound configuration data and the business data into recognizable configuration objects through a configuration perception conversion strategy of an account checking platform, and recognizing a configuration change set through a configuration object comparison strategy of the account checking platform based on the recognizable configuration objects; and based on the configuration change set, through a configuration processing strategy of the account checking platform, generating a network element device configuration adjustment scheme, and based on the network element device configuration adjustment scheme, performing configuration adjustment processing on each network element device of the service operation and maintenance request. By adopting the method, the configuration management and control effect of the network element equipment can be comprehensively improved.

Description

Technical Field

[0001] This application relates to the field of communication architecture and controller technology, and in particular to a configuration and management method, apparatus and computer device for network element devices. Background Technology

[0002] The control plane is the central hub of the SDN control system. Architecturally, it can be divided into northbound and southbound components. The northbound component, called the controller, is responsible for interacting with the cloud management platform and the southbound component. However, the current architecture lacks a southbound component that supports heterogeneous devices; this function is currently handled by the controller. As network scale expands and configuration protocols and forwarding devices are continuously upgraded, the controller needs to add additional functions to differentiate between configuration protocols and device architectures. If the differences between devices are too large, it will directly affect the controller's business logic, doubling the workload of the entire R&D-testing chain and increasing the probability of failure. Secondly, the controller determines whether a configuration already exists on the device by traversing the configuration data of each attribute in the configuration model. If it exists, it will not be configured; otherwise, it will be configured. This leads to issues with the accuracy of configuration distribution and performance and operational overhead from maintaining references. Therefore, improving the performance and accuracy of the controller during network element configuration distribution, while optimizing the compatibility of the southbound component with heterogeneous devices, is a current research focus.

[0003] Existing technology categorizes candidate path information into managed and unmanaged path information, distributing managed path information to routers via routing protocols and unmanaged path information via the netconf protocol. However, this method essentially provides a special solution for route distribution, failing to cover more forwarding configuration types. Furthermore, the configuration distribution process using the netconf protocol still relies on a strategy of synchronous rollback and manual intervention. For large-scale and complex network scenarios, this undoubtedly leads to significant operational costs, resulting in poor configuration management of network elements. Summary of the Invention

[0004] Therefore, it is necessary to provide a configuration and management method, device, computer equipment, computer-readable storage medium, and computer program product for network element devices to address the above-mentioned technical problems.

[0005] Firstly, this application provides a configuration management method for network element devices, including:

[0006] Obtain business operation and maintenance requests and southbound configuration data, and decode the business operation and maintenance requests to obtain various business data;

[0007] The southbound configuration data and the business data are transformed into identifiable configuration objects through the configuration awareness conversion strategy of the reconciliation platform. Based on the identifiable configuration objects, the configuration change set is identified through the configuration object comparison strategy of the reconciliation platform.

[0008] Based on the configuration change set, a network element device configuration adjustment plan is generated through the configuration processing strategy of the reconciliation platform, and based on the network element device configuration adjustment plan, the configuration adjustment processing is performed on each network element device of the service operation and maintenance request.

[0009] Optionally, the decoding process of the business operation and maintenance request to obtain various business data includes:

[0010] The business operation and maintenance request is decoded to obtain the business object corresponding to the business operation and maintenance request.

[0011] Based on the business object, resource data and business data corresponding to the business operation and maintenance request are generated through a forwarding resource allocation strategy.

[0012] Optionally, the step of converting the southbound configuration data and the business data into identifiable configuration objects through the configuration-aware conversion strategy of the reconciliation platform includes:

[0013] Based on the aforementioned southbound configuration data, the aforementioned southbound configuration data is atomically processed through the network element configuration model corresponding to the aforementioned southbound configuration data to obtain the first identifiable configuration object corresponding to the aforementioned southbound configuration data;

[0014] Based on the aforementioned service data, the network element configuration model corresponding to each service data is used to atomically process the service data to obtain the second identifiable configuration object corresponding to each service data.

[0015] Optionally, the step of identifying the configuration change set based on each of the identifiable configuration objects, through the configuration object comparison strategy of the reconciliation platform, includes:

[0016] Identify the first configuration type corresponding to each of the first identifiable configuration objects, and identify the second configuration type corresponding to each of the second identifiable configuration objects;

[0017] Based on the first configuration type corresponding to each of the first identifiable configuration objects, and the second configuration type corresponding to each of the second identifiable configuration objects, the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type are identified;

[0018] Based on the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type, the configuration anomaly information of each abnormal identifiable configuration object is identified by a similar comparison strategy, and the associated information of each abnormal identifiable configuration object is identified.

[0019] The configuration exception information of each of the aforementioned exception-identifiable configuration objects, as well as the associated information of each of the aforementioned exception-identifiable configuration objects, are used as a configuration change set.

[0020] Optionally, the step of generating a network element device configuration adjustment scheme based on the configuration change set and through the configuration processing strategy of the reconciliation platform includes:

[0021] Based on the configuration exception information of each of the aforementioned exception-identifiable configuration objects, a configuration adjustment strategy for each of the aforementioned exception-identifiable configuration objects is generated through a configuration correction strategy.

[0022] Based on the association information of each of the aforementioned identifiable configuration objects, identify the network element device corresponding to each of the aforementioned identifiable configuration objects;

[0023] The configuration adjustment strategy for each of the aforementioned abnormal identifiable configuration objects shall be used as the configuration adjustment scheme for the network element devices corresponding to each of the aforementioned abnormal identifiable configuration objects, and the configuration adjustment scheme for all network element devices shall be used as the network element device configuration adjustment scheme.

[0024] Optionally, the step of adjusting the configuration of each network element device in the service operation and maintenance request based on the network element device configuration adjustment scheme includes:

[0025] In the resource pool, locate the device address of each of the aforementioned network element devices;

[0026] Based on the configuration adjustment scheme of each network element device, and according to the device address of each network element device, the configuration adjustment and distribution process is carried out on each network element device through the high-speed cloud configuration adjustment strategy, so as to complete the configuration distribution requirements of each network element device corresponding to the service operation and maintenance request.

[0027] Secondly, this application also provides a configuration control device for network element equipment, including:

[0028] The acquisition module is used to acquire business operation and maintenance requests and various southbound configuration data, and to decode the business operation and maintenance requests to obtain various business data.

[0029] The identification module is used to convert the southbound configuration data and the business data into identifiable configuration objects through the configuration awareness conversion strategy of the reconciliation platform, and to identify the configuration change set based on the identifiable configuration objects through the configuration object comparison strategy of the reconciliation platform.

[0030] The configuration module is used to generate a network element device configuration adjustment plan based on the configuration change set and the configuration processing strategy of the reconciliation platform, and to perform configuration adjustment processing on each network element device of the service operation and maintenance request based on the network element device configuration adjustment plan.

[0031] Optionally, the acquisition module is specifically used for:

[0032] The business operation and maintenance request is decoded to obtain the business object corresponding to the business operation and maintenance request.

[0033] Based on the business object, resource data and business data corresponding to the business operation and maintenance request are generated through a forwarding resource allocation strategy.

[0034] Optionally, the identification module is specifically used for:

[0035] Based on the aforementioned southbound configuration data, the aforementioned southbound configuration data is atomically processed through the network element configuration model corresponding to the aforementioned southbound configuration data to obtain the first identifiable configuration object corresponding to the aforementioned southbound configuration data;

[0036] Based on the aforementioned service data, the network element configuration model corresponding to each service data is used to atomically process the service data to obtain the second identifiable configuration object corresponding to each service data.

[0037] Optionally, the identification module is specifically used for:

[0038] Identify the first configuration type corresponding to each of the first identifiable configuration objects, and identify the second configuration type corresponding to each of the second identifiable configuration objects;

[0039] Based on the first configuration type corresponding to each of the first identifiable configuration objects, and the second configuration type corresponding to each of the second identifiable configuration objects, the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type are identified;

[0040] Based on the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type, the configuration anomaly information of each abnormal identifiable configuration object is identified by a similar comparison strategy, and the associated information of each abnormal identifiable configuration object is identified.

[0041] The configuration exception information of each of the aforementioned exception-identifiable configuration objects, as well as the associated information of each of the aforementioned exception-identifiable configuration objects, are used as a configuration change set.

[0042] Optionally, the configuration module is specifically used for:

[0043] Based on the configuration exception information of each of the aforementioned exception-identifiable configuration objects, a configuration adjustment strategy for each of the aforementioned exception-identifiable configuration objects is generated through a configuration correction strategy.

[0044] Based on the association information of each of the aforementioned identifiable configuration objects, identify the network element device corresponding to each of the aforementioned identifiable configuration objects;

[0045] The configuration adjustment strategy for each of the aforementioned abnormal identifiable configuration objects shall be used as the configuration adjustment scheme for the network element devices corresponding to each of the aforementioned abnormal identifiable configuration objects, and the configuration adjustment scheme for all network element devices shall be used as the network element device configuration adjustment scheme.

[0046] Optionally, the configuration module is specifically used for:

[0047] In the resource pool, locate the device address of each of the aforementioned network element devices;

[0048] Based on the configuration adjustment scheme of each network element device, and according to the device address of each network element device, the configuration adjustment and distribution process is carried out on each network element device through the high-speed cloud configuration adjustment strategy, so as to complete the configuration distribution requirements of each network element device corresponding to the service operation and maintenance request.

[0049] Thirdly, this application provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the method described in any one of the first aspects.

[0050] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the method described in any one of the first aspects.

[0051] Fifthly, this application provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the method described in any one of the first aspects.

[0052] The aforementioned network element device configuration management method, apparatus, and computer equipment acquire service operation and maintenance requests and southbound configuration data, and decode the service operation and maintenance requests to obtain various service data. The southbound configuration data and the service data are then transformed into identifiable configuration objects using the configuration awareness conversion strategy of the reconciliation platform. Based on these identifiable configuration objects, a configuration change set is identified using the configuration object comparison strategy of the reconciliation platform. Based on the configuration change set, a network element device configuration adjustment plan is generated using the configuration processing strategy of the reconciliation platform. Based on this plan, configuration adjustment processing is performed on each network element device in the service operation and maintenance request. The execution entity in this solution is the controller, which only needs to focus on resource allocation and service orchestration. It then focuses on service-based decomposition and configuration reconciliation through the reconciliation platform, and on the connection and data transmission with the same network element device through protocol nodes. This greatly simplifies the controller logic, eliminating the cumbersome netconf configuration construction and distribution / rollback process, while enhancing scalability and enabling seamless compatibility with different network element devices. The reconciliation platform designed in this solution has a simple logic, requiring no attention to the specific operations of any particular business. It builds and compares configurations at the granular level of high-speed instances between clouds based on existing business data, which is far more concise than the current method where the controller orchestrates and distributes configurations simultaneously. Furthermore, the reconciliation platform directly reads the actual configuration of network elements, handling scenarios where multiple services share configurations without relying on any configuration counts or ref data. This provides unparalleled accuracy compared to previous configuration or retry methods, allowing the controller to escape the vicious cycle of increasing data discrepancies between upper and lower layers over system runtime. Through its powerful and accurate reconciliation capabilities, it not only ensures the accuracy of new business configurations but also corrects existing configurations within the same high-speed instance in the cloud. Over time, this creates a virtuous cycle, continuously improving the consistency between control plane and forwarding plane data, ultimately achieving complete consistency and maintaining it long-term. This comprehensively improves the configuration management and control effectiveness of network element devices. Attached Figure Description

[0053] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0054] Figure 1 This is a system architecture diagram of the configuration management system for network element devices in one embodiment;

[0055] Figure 2This is a flowchart illustrating the configuration control method for network element devices in one embodiment;

[0056] Figure 3 This is a flowchart illustrating an example of configuration management for network element devices in one embodiment;

[0057] Figure 4 This is a structural block diagram of the configuration control device for a network element in one embodiment;

[0058] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0059] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0060] The configuration management method for network element devices provided in this application can be applied to a configuration management system for network element devices. The system architecture diagram is as follows: Figure 1As shown, the system includes a controller, reconciliation platform, protocol stack, tool layer, and basic system. The controller in this method is the execution entity of the system, serving as the central hub of the SDN control system. SDN employs a centralized control plane and a distributed forwarding plane, with the two planes separated. The control plane uses a control-forwarding communication interface to centrally control network devices on the forwarding plane and provides flexible programmability. This controller can be applied to terminals, including but not limited to various personal computers, laptops, and mid-range computers. The terminal only needs to focus on resource allocation and service orchestration, then uses the reconciliation platform to focus on service-based decomposition and configuration reconciliation, and uses protocol nodes to focus on the establishment and data transmission of connections with network elements. This greatly simplifies the controller logic, eliminating the cumbersome netconf configuration construction and distribution / rollback process, while enhancing scalability and enabling seamless compatibility with different network elements. The reconciliation platform designed in this solution has simple logic, requiring no attention to the specific operations of any particular service. Furthermore, it performs high-speed inter-cloud instance-level configuration construction and comparison based on existing service data, which is far more concise than the current method where the controller performs orchestration and decomposition / distribution simultaneously. Meanwhile, the reconciliation platform directly reads the actual configuration of network elements, handling scenarios where multiple services share configurations without relying on any configuration counts or ref data. Compared to previous configuration or retry methods, it offers unparalleled accuracy. This allows the controller to escape the vicious cycle where data discrepancies between upper and lower layers increase with system uptime. Through its powerful and accurate reconciliation capabilities, it not only ensures the accuracy of new service configurations but also corrects existing configurations across high-speed instances within the same cloud. Over time, this creates a virtuous cycle, continuously improving the consistency between control plane and forwarding plane data, ultimately achieving complete consistency and maintaining it long-term. This comprehensively improves the configuration management and control effectiveness of network element devices.

[0061] In one exemplary embodiment, such as Figure 2 As shown, a configuration and management method for network element devices is provided. Taking the application of this method to a terminal as an example, the method includes the following steps S201 to S203. Wherein:

[0062] Step S201: Obtain business operation and maintenance requests and southbound configuration data, and decode the business operation and maintenance requests to obtain the business data.

[0063] In this embodiment, the terminal responds to a user's request by obtaining a service operation and maintenance request issued by the user. This service operation and maintenance request can be a service request or an operation and maintenance request; for example, a cross-domain connection creation request, or a system operation and maintenance request. Then, the terminal receives the request from the southbound proxy, extracts the network element device and configuration messages from the request body, and obtains the southbound configuration data. Finally, the terminal decodes the service operation and maintenance request using a preset request decoding and resource allocation strategy, allocates the resource data and service data required by the service operation and maintenance request, and extracts the service data. The specific allocation process will be described in detail later.

[0064] Step S202: Convert all southbound configuration data and all business data into identifiable configuration objects through the configuration awareness conversion strategy of the reconciliation platform, and identify the set of configuration changes based on each identifiable configuration object through the configuration object comparison strategy of the reconciliation platform.

[0065] In this embodiment, the terminal converts all southbound configuration data and business data into identifiable configuration objects using the configuration awareness conversion strategy of the reconciliation platform. Based on these identifiable configuration objects, the terminal identifies configuration change sets using the reconciliation platform's configuration object comparison strategy. This step involves the terminal instructing the reconciliation platform designed in this solution to process the data. The reconciliation platform primarily reads the configuration objects of the configuration data and business data, then identifies anomalies in each configuration object, thereby adjusting the configuration objects accordingly. The specific identification process will be explained in detail later. This reconciliation platform functions as both an independent operation and maintenance component and a business node, providing four reconciliation dimensions: full device / device + inter-cloud high-speed instance / resource pool + inter-cloud high-speed instance / device + multi-cloud high-speed instance, and four operation types: read-only / add / delete / overwrite. As an independent operation and maintenance component, the reconciliation platform supports automatic / manual reconciliation functions. It can manually trigger the acquisition of real-time results or automatically initiate business reconciliation for specified customers according to a schedule, outputting abnormal data through the alarm platform.

[0066] Step S203: Based on the configuration change set, generate a network element device configuration adjustment plan through the configuration processing strategy of the reconciliation platform, and perform configuration adjustment processing on each network element device for the service operation and maintenance request based on the network element device configuration adjustment plan.

[0067] In this embodiment, the terminal generates a network element device configuration adjustment scheme based on the configuration change set and the configuration processing strategy of the reconciliation platform. This step involves the terminal instructing the reconciliation platform designed in this scheme to process the configuration, and the network element device configuration adjustment scheme is a scheme for adjusting the configuration of the network element objects corresponding to the configuration objects obtained above.

[0068] Then, based on the network element device configuration adjustment scheme, the terminal performs configuration adjustment processing on each network element device in the business operation and maintenance request. This configuration adjustment process includes adjusting the configuration data of each network element device, retrieving the adjusted configuration data from the terminal, and then performing inter-cloud high-speed instance granular reconciliation and configuration distribution to meet the network element device configuration distribution requirements. In other words, this step includes the reconciliation platform adjusting configuration data and the terminal distributing configurations to the network element devices. The specific execution process will be explained in detail later. The inter-cloud high-speed (Express Connect) provides users with a high-speed, secure, and stable network capability to quickly build cross-regional resource pool VPCs. By creating an inter-cloud high-speed instance, then creating a cloud gateway in the region requiring interconnection, connecting the network instances that need interconnection to the cloud gateway, and finally configuring bandwidth between the cross-regional cloud gateways requiring interconnection, private network interconnection between cross-domain network instances can be quickly achieved. During this process, the underlying orchestrator and controller will distribute cloud and cross-domain VXLAN and static route configurations, ultimately enabling virtual machines of different network instances to interconnect.

[0069] In another embodiment, in the event of a southbound configuration failure during a business request, this solution implements a two-level retry repair mechanism in the reconciliation platform, which is divided into two stages based on the retry frequency:

[0070] (1) Each phase lasts 20 seconds and is retried once, for a total of three times;

[0071] (2) The second stage is 5 minutes, and the test is repeated once for a total of 30 times.

[0072] The two retry phases are device-level, aiming to reduce frequent reads of device configuration. Under normal device conditions, retries can succeed on the first attempt; however, entering the second phase indicates a device anomaly requiring manual intervention from the network element, which may take 5-10 minutes. Retrying every 20 seconds during this period is unnecessary. Once the network element has restarted, the second-phase retry process can resume. Based on this theory, a specific cloud-to-high-speed request might directly enter the second-phase retry, entirely depending on the current device status.

[0073] Implementation details: The terminal maintains two ConcurrentHashMaps for two-stage retry queues. The key is the device IP address, and the value is the Node object to be retried. Each retry transforms and transparently transmits the Node information to the batch reconciliation interface. This interface of the reconciliation platform reconciles the incoming device with the set of cloud high-speed IDs and distributes or deletes configurations based on the reconciliation results.

[0074] Finally, the system returns the cloud highway ID that successfully matches the configuration. After receiving the response, the controller parses the cloud highway ID and removes it from the Node. If the current Node's cloud highway ID set is empty after removal, it means the device has successfully retried; otherwise, it means there are still incorrect configurations under the EC (Elastic Compute Service) and it will wait for the next retry. The node's `count` attribute is incremented by 1 after each retry. If the retry count is reached and the device still reports an error, the reconciliation platform will output a high-level error message to the alarm platform, reminding operations personnel to intervene as soon as possible.

[0075] Based on the above solution, the controller only needs to focus on resource allocation and service orchestration. Then, the reconciliation platform focuses on service-based decomposition and configuration reconciliation, and the protocol nodes focus on the connection establishment and data transmission with network elements. This greatly simplifies the controller logic, eliminating the cumbersome netconf configuration building and distribution / rollback process. Simultaneously, it enhances scalability, enabling seamless compatibility with different network elements. Furthermore, the reconciliation platform designed in this solution has simple logic, requiring no attention to the specific operations of any particular service. Moreover, it performs high-speed inter-cloud instance-level configuration building and comparison based on existing service data, which is far more concise than the current method where the controller performs orchestration and decomposition / distribution simultaneously. Meanwhile, the reconciliation platform directly reads the actual configuration of network elements, handling scenarios where multiple services share configurations without relying on any configuration counts or ref data. Compared to previous configuration or retry methods, it offers unparalleled accuracy. This allows the controller to escape the vicious cycle where data discrepancies between upper and lower layers increase with system uptime. Through its powerful and accurate reconciliation capabilities, it not only ensures the accuracy of new service configurations but also corrects existing configurations across high-speed instances within the same cloud. Over time, this creates a virtuous cycle, continuously improving the consistency between control plane and forwarding plane data, ultimately achieving complete consistency and maintaining it long-term. This comprehensively improves the configuration management and control effectiveness of network element devices.

[0076] Optionally, the business operation and maintenance request is decoded to obtain various business data, including: decoding the business operation and maintenance request to obtain the business object corresponding to the business operation and maintenance request; and generating various resource data and various business data corresponding to the business operation and maintenance request based on the business object and through a forwarding resource allocation strategy.

[0077] In this embodiment, the terminal decodes the service operation and maintenance request to obtain the corresponding service object. Then, based on the service object, the terminal generates resource data and service data corresponding to the service operation and maintenance request through a forwarding resource allocation strategy. Specifically, the forwarding resource allocation strategy involves the terminal allocating resources and services to the decoded service object, thereby obtaining resource data and service data for each service object.

[0078] Based on the above solution, by decoding the business operation and maintenance requests and configuring resources and services for each business object, the efficiency of resource configuration for business operation and maintenance requests is improved.

[0079] Optionally, the southbound configuration data and the business data are transformed into identifiable configuration objects through the configuration awareness conversion strategy of the reconciliation platform. This includes: based on the southbound configuration data, atomic processing is performed on the southbound configuration data through the network element configuration model corresponding to the southbound configuration data to obtain the first identifiable configuration object corresponding to the southbound configuration data; based on the business data, atomic processing is performed on the business data through the network element configuration model corresponding to the business data to obtain the second identifiable configuration object corresponding to the business data.

[0080] In this embodiment, the terminal, based on each southbound configuration data, performs atomic processing on each southbound configuration data using the network element configuration model corresponding to the southbound configuration data to obtain a first identifiable configuration object corresponding to each southbound configuration data. Then, based on each service data, the terminal performs atomic processing on each service data using the network element configuration model corresponding to each service data to obtain a second identifiable configuration object corresponding to each service data.

[0081] The southbound configuration data and various service data are respectively the configuration data in the DPDK device sysrepo or grpc-tgw-agent / p4-agent. Since the configuration models for different data differ, this solution presets network element configuration models for different data to perform different minimum-granularity configurations (atomic configurations). The network element configuration models for each data are as follows:

[0082] (1) Netconf: Uses the standard yang model and atomic configurations such as vxlan, bridge-domain, loopback, arp, etc.

[0083] (2) P4: Use custom interfaces and atomic configurations such as instance, route-table, route-entry, etc., which are closer to the business model.

[0084] (3) grpc-tgw-agent: Uses a custom interface, and the forwarding model is between the yang model and the business model.

[0085] Based on the above scheme, by configuring different data according to different minimum granularities, the accuracy of the minimum granularity configuration for different data is ensured.

[0086] Optionally, based on each identifiable configuration object, the configuration change set is identified through the configuration object comparison strategy of the reconciliation platform, including: identifying the first configuration type corresponding to each first identifiable configuration object, and identifying the second configuration type corresponding to each second identifiable configuration object; based on the first configuration type corresponding to each first identifiable configuration object, and identifying the second configuration type corresponding to each second identifiable configuration object, identifying the first identifiable configuration object group corresponding to each configuration type, and the second identifiable configuration object group corresponding to each configuration type; based on the first identifiable configuration object group corresponding to each configuration type, and the second identifiable configuration object group corresponding to each configuration type, the configuration anomaly information of each abnormal identifiable configuration object is identified through a similar comparison strategy, and the associated information of each abnormal identifiable configuration object is identified; the configuration anomaly information of each abnormal identifiable configuration object, and the associated information of each abnormal identifiable configuration object, are used as the configuration change set.

[0087] In this embodiment, the terminal identifies the first configuration type corresponding to each first identifiable configuration object and the second configuration type corresponding to each second identifiable configuration object. The configuration type corresponding to each configuration object represents the configuration method for different configuration objects.

[0088] Then, the terminal identifies the first configuration type corresponding to each first identifiable configuration object, and the second configuration type corresponding to each second identifiable configuration object, and identifies the first identifiable configuration object group corresponding to each configuration type, and the second identifiable configuration object group corresponding to each configuration type. This step involves grouping configuration objects with the same configuration method.

[0089] Next, based on the first identifiable configuration object group and the second identifiable configuration object group corresponding to each configuration type, the terminal identifies the configuration exception information of each abnormal identifiable configuration object through a similar comparison strategy, and identifies the associated information of each abnormal identifiable configuration object. This similar comparison strategy involves the terminal rewriting the `equals` and `hashCode` methods of the configuration objects. Then, the terminal identifies the differences between the rewritten configuration objects and the rewritten configuration objects, and uses the differences in these differences as configuration exception information. The associated information of each abnormal identifiable configuration object includes, but is not limited to, the network element device corresponding to the abnormal identifiable configuration object and its configuration data. The differences include, but are not limited to, deletion, residue, and inaccuracy.

[0090] Then, the terminal uses the configuration exception information of each identifiable configuration object and the associated information of each identifiable configuration object as a set of configuration changes.

[0091] Based on the above scheme, the reconciliation platform compares the configuration objects corresponding to different data through the same comparison strategy, and identifies the configuration abnormal information of each abnormal configuration object, thereby greatly simplifying the controller logic (2), eliminating the cumbersome netconf configuration construction and distribution / rollback process, while enhancing scalability and enabling seamless compatibility with different devices.

[0092] Optionally, based on the configuration change set, a network element device configuration adjustment plan is generated through the configuration processing strategy of the reconciliation platform. This includes: generating a configuration adjustment strategy for each identifiable configuration object based on the configuration anomaly information of each identifiable configuration object, through a configuration correction strategy; identifying the network element device corresponding to each identifiable configuration object based on the association information of each identifiable configuration object; using the configuration adjustment strategy of each identifiable configuration object as the configuration adjustment plan for the network element device corresponding to each identifiable configuration object, and using the configuration adjustment plans of all network element devices as the network element device configuration adjustment plan.

[0093] In this embodiment, the terminal generates a configuration adjustment strategy for each identifiable configuration object based on its configuration anomaly information and a configuration correction strategy. Then, the terminal identifies the network element device corresponding to each identifiable configuration object based on its association information. The configuration correction strategy includes correction methods corresponding to differentiating methods. The terminal directly queries the correction method corresponding to the differentiating method of each identifiable configuration object using the aforementioned correspondence and uses this correction method as the configuration adjustment strategy for that object. For example, the correction method for deletion is to add valid configuration, the correction method for remnants is to delete residual configuration, and the correction method for inaccuracy is to correct inaccurate configuration.

[0094] Then, the terminal uses the configuration adjustment strategy of each abnormal identifiable configuration object as the configuration adjustment scheme of the network element device corresponding to each abnormal identifiable configuration object, and uses the configuration adjustment scheme of all network element devices as the network element device configuration adjustment scheme.

[0095] Based on the above scheme, by efficiently identifying the configuration adjustment strategy for each abnormal identifiable configuration object, the efficiency of adjusting the configuration data of the network element devices corresponding to each abnormal identifiable configuration object is improved.

[0096] Optionally, based on the network element device configuration adjustment scheme, the configuration adjustment processing of each network element device in the service operation and maintenance request is performed, including: locating the device address of each network element device in the resource pool; and, based on the configuration adjustment scheme of each network element device, according to the device address of each network element device, performing configuration adjustment and distribution processing of each network element device through the cloud high-speed configuration adjustment strategy, thereby completing the configuration distribution requirements of each network element device corresponding to the service operation and maintenance request.

[0097] In this embodiment, the terminal locates the device addresses of each network element in the resource pool. Then, according to the configuration adjustment scheme of each network element, the terminal first adjusts the configuration data corresponding to each network element to obtain the target configuration data of each network element. Next, based on the target configuration data of each network element and according to the device addresses of each network element, the terminal performs configuration distribution processing on each network element using high-speed cloud-to-cloud configuration technology, fulfilling the configuration distribution requirements of each network element corresponding to the service operation and maintenance request.

[0098] Based on the above solution, the controller only needs to focus on resource allocation and business orchestration; the reconciliation platform only needs to focus on business decomposition and configuration reconciliation, thereby minimizing the risk of inconsistency between control plane and forwarding plane data. Through powerful and accurate reconciliation capabilities, it can not only ensure the accuracy of new business configurations, but also correct existing configurations under high-speed instances in the same cloud. Over the long term, this will form a virtuous cycle, ultimately improving the consistency between control plane data and forwarding plane data, and finally achieving complete consistency and maintaining it in the long term.

[0099] This application also provides an example of configuration management for network element devices, such as... Figure 3 As shown, the specific processing procedure includes the following steps:

[0100] Step S301: Obtain business operation and maintenance requests, as well as southbound configuration data.

[0101] Step S302: Decode the business operation and maintenance request to obtain the business object corresponding to the business operation and maintenance request.

[0102] Step S303: Based on the business object, generate the resource data and business data corresponding to the business operation and maintenance request through the forwarding resource allocation strategy.

[0103] Step S304: Based on each southbound configuration data, the network element configuration model corresponding to the southbound configuration data is used to perform atomic processing on each southbound configuration data to obtain the first identifiable configuration object corresponding to each southbound configuration data.

[0104] Step S305: Based on each service data, the network element configuration model corresponding to each service data is used to atomically process each service data to obtain the second identifiable configuration object corresponding to each service data.

[0105] Step S306: Identify the first configuration type corresponding to each first identifiable configuration object, and identify the second configuration type corresponding to each second identifiable configuration object.

[0106] Step S307: Based on the first configuration type corresponding to each first identifiable configuration object, identify the second configuration type corresponding to each second identifiable configuration object, identify the first identifiable configuration object group corresponding to each configuration type, and the second identifiable configuration object group corresponding to each configuration type.

[0107] Step S308: Based on the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type, the configuration exception information of each abnormal identifiable configuration object is identified through a similar comparison strategy, and the associated information of each abnormal identifiable configuration object is identified.

[0108] Step S309: The configuration exception information of each exception-identifiable configuration object and the associated information of each exception-identifiable configuration object are used as a configuration change set.

[0109] Step S310: Based on the configuration exception information of each exception-identifiable configuration object, generate a configuration adjustment strategy for each exception-identifiable configuration object through a configuration correction strategy.

[0110] Step S311: Based on the association information of each identifiable configuration object for an anomaly, identify the network element device corresponding to each identifiable configuration object for an anomaly.

[0111] Step S312: The configuration adjustment strategy of each abnormal identifiable configuration object is used as the configuration adjustment scheme of the network element device corresponding to each abnormal identifiable configuration object, and the configuration adjustment scheme of all network element devices is used as the network element device configuration adjustment scheme.

[0112] Step S313: Locate the device address of each network element in the resource pool.

[0113] Step S314: Based on the configuration adjustment scheme of each network element device, according to the device address of each network element device, the configuration adjustment and distribution process of each network element device is carried out through the high-speed configuration adjustment strategy between the cloud and the network element device to complete the configuration distribution requirements of each network element device corresponding to the service operation and maintenance request.

[0114] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0115] Based on the same inventive concept, this application also provides a network element configuration management device for implementing the above-described network element configuration management method. The solution provided by this device is similar to the implementation described in the above method. Therefore, the specific limitations in one or more network element configuration management device embodiments provided below can be found in the limitations of the network element configuration management method described above, and will not be repeated here.

[0116] In one exemplary embodiment, such as Figure 4 As shown, a configuration management device for a network element is provided, comprising: an acquisition module 410, an identification module 420, and a configuration module 430, wherein:

[0117] The acquisition module 410 is used to acquire business operation and maintenance requests and various southbound configuration data, and to decode the business operation and maintenance requests to obtain various business data.

[0118] The identification module 420 is used to convert the southbound configuration data and the business data into identifiable configuration objects through the configuration awareness conversion strategy of the reconciliation platform, and identify the configuration change set based on the identifiable configuration objects through the configuration object comparison strategy of the reconciliation platform.

[0119] The configuration module 430 is used to generate a network element device configuration adjustment plan based on the configuration change set and the configuration processing strategy of the reconciliation platform, and to perform configuration adjustment processing on each network element device of the service operation and maintenance request based on the network element device configuration adjustment plan.

[0120] Optionally, the acquisition module 410 is specifically used for:

[0121] The business operation and maintenance request is decoded to obtain the business object corresponding to the business operation and maintenance request.

[0122] Based on the business object, resource data and business data corresponding to the business operation and maintenance request are generated through a forwarding resource allocation strategy.

[0123] Optionally, the identification module 420 is specifically used for:

[0124] Based on the aforementioned southbound configuration data, the aforementioned southbound configuration data is atomically processed through the network element configuration model corresponding to the aforementioned southbound configuration data to obtain the first identifiable configuration object corresponding to the aforementioned southbound configuration data;

[0125] Based on the aforementioned service data, the network element configuration model corresponding to each service data is used to atomically process the service data to obtain the second identifiable configuration object corresponding to each service data.

[0126] Optionally, the identification module 420 is specifically used for:

[0127] Identify the first configuration type corresponding to each of the first identifiable configuration objects, and identify the second configuration type corresponding to each of the second identifiable configuration objects;

[0128] Based on the first configuration type corresponding to each of the first identifiable configuration objects, and the second configuration type corresponding to each of the second identifiable configuration objects, the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type are identified;

[0129] Based on the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type, the configuration anomaly information of each abnormal identifiable configuration object is identified by a similar comparison strategy, and the associated information of each abnormal identifiable configuration object is identified.

[0130] The configuration exception information of each of the aforementioned exception-identifiable configuration objects, as well as the associated information of each of the aforementioned exception-identifiable configuration objects, are used as a configuration change set.

[0131] Optionally, the configuration module 430 is specifically used for:

[0132] Based on the configuration exception information of each of the aforementioned exception-identifiable configuration objects, a configuration adjustment strategy for each of the aforementioned exception-identifiable configuration objects is generated through a configuration correction strategy.

[0133] Based on the association information of each of the aforementioned identifiable configuration objects, identify the network element device corresponding to each of the aforementioned identifiable configuration objects;

[0134] The configuration adjustment strategy for each of the aforementioned abnormal identifiable configuration objects shall be used as the configuration adjustment scheme for the network element devices corresponding to each of the aforementioned abnormal identifiable configuration objects, and the configuration adjustment scheme for all network element devices shall be used as the network element device configuration adjustment scheme.

[0135] Optionally, the configuration module 430 is specifically used for:

[0136] In the resource pool, locate the device address of each of the aforementioned network element devices;

[0137] Based on the configuration adjustment scheme of each network element device, and according to the device address of each network element device, the configuration adjustment and distribution process is carried out on each network element device through the high-speed cloud configuration adjustment strategy, so as to complete the configuration distribution requirements of each network element device corresponding to the service operation and maintenance request.

[0138] Each module in the configuration and control device of the aforementioned network element equipment can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0139] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 5 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a configuration and management method for network element devices. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0140] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0141] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of a configuration control method for a network element device.

[0142] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program being executed by a processor to implement the steps of a configuration control method for network element devices.

[0143] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of a configuration control method for network elements.

[0144] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0145] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0146] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0147] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A configuration control method for network element devices, characterized in that, The method includes: Obtain business operation and maintenance requests and southbound configuration data, and decode the business operation and maintenance requests to obtain various business data; The southbound configuration data and the business data are transformed into identifiable configuration objects through the configuration awareness conversion strategy of the reconciliation platform. Based on the identifiable configuration objects, the configuration change set is identified through the configuration object comparison strategy of the reconciliation platform. Based on the configuration change set, a network element device configuration adjustment plan is generated through the configuration processing strategy of the reconciliation platform, and based on the network element device configuration adjustment plan, the configuration adjustment processing is performed on each network element device of the service operation and maintenance request.

2. The method according to claim 1, characterized in that, The process of decoding the business operation and maintenance request to obtain various business data includes: The business operation and maintenance request is decoded to obtain the business object corresponding to the business operation and maintenance request. Based on the business object, resource data and business data corresponding to the business operation and maintenance request are generated through a forwarding resource allocation strategy.

3. The method according to claim 2, characterized in that, The process of converting the aforementioned southbound configuration data and business data into identifiable configuration objects through the configuration-aware conversion strategy of the reconciliation platform includes: Based on the aforementioned southbound configuration data, the aforementioned southbound configuration data is atomically processed through the network element configuration model corresponding to the aforementioned southbound configuration data to obtain the first identifiable configuration object corresponding to the aforementioned southbound configuration data; Based on the aforementioned service data, the network element configuration model corresponding to each service data is used to atomically process the service data to obtain the second identifiable configuration object corresponding to each service data.

4. The method according to claim 3, characterized in that, The process of identifying configuration change sets based on each identifiable configuration object, using the configuration object comparison strategy of the reconciliation platform, includes: Identify the first configuration type corresponding to each of the first identifiable configuration objects, and identify the second configuration type corresponding to each of the second identifiable configuration objects; Based on the first configuration type corresponding to each of the first identifiable configuration objects, and the second configuration type corresponding to each of the second identifiable configuration objects, the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type are identified; Based on the first identifiable configuration object group corresponding to each configuration type and the second identifiable configuration object group corresponding to each configuration type, the configuration anomaly information of each abnormal identifiable configuration object is identified by a similar comparison strategy, and the associated information of each abnormal identifiable configuration object is identified. The configuration exception information of each of the aforementioned exception-identifiable configuration objects, as well as the associated information of each of the aforementioned exception-identifiable configuration objects, are used as a configuration change set.

5. The method according to claim 4, characterized in that, Based on the configuration change set, and through the configuration processing strategy of the reconciliation platform, a network element device configuration adjustment scheme is generated, including: Based on the configuration exception information of each of the aforementioned exception-identifiable configuration objects, a configuration adjustment strategy for each of the aforementioned exception-identifiable configuration objects is generated through a configuration correction strategy. Based on the association information of each of the aforementioned identifiable configuration objects, identify the network element device corresponding to each of the aforementioned identifiable configuration objects; The configuration adjustment strategy for each of the aforementioned abnormal identifiable configuration objects shall be used as the configuration adjustment scheme for the network element devices corresponding to each of the aforementioned abnormal identifiable configuration objects, and the configuration adjustment scheme for all network element devices shall be used as the network element device configuration adjustment scheme.

6. The method according to claim 1, characterized in that, The configuration adjustment process for each network element device in the service operation and maintenance request, based on the network element device configuration adjustment scheme, includes: In the resource pool, locate the device address of each of the aforementioned network element devices; Based on the configuration adjustment scheme of each network element device, and according to the device address of each network element device, the configuration adjustment and distribution process is carried out on each network element device through the high-speed cloud configuration adjustment strategy, so as to complete the configuration distribution requirements of each network element device corresponding to the service operation and maintenance request.

7. A configuration control device for network element equipment, characterized in that, The device includes: The acquisition module is used to acquire business operation and maintenance requests and various southbound configuration data, and to decode the business operation and maintenance requests to obtain various business data. The identification module is used to convert the southbound configuration data and the business data into identifiable configuration objects through the configuration awareness conversion strategy of the reconciliation platform, and to identify the configuration change set based on the identifiable configuration objects through the configuration object comparison strategy of the reconciliation platform. The configuration module is used to generate a network element device configuration adjustment plan based on the configuration change set and the configuration processing strategy of the reconciliation platform, and to perform configuration adjustment processing on each network element device of the service operation and maintenance request based on the network element device configuration adjustment plan.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images