A network element device configuration data collection method based on configuration change event awareness and related device

Abstract

The application discloses a kind of based on configuration change event perception network element equipment configuration data acquisition method and related equipment, the application is realized by the configuration change event driven by network element equipment, when network management system perceives that network element equipment occurs configuration change, real-time query obtains the configuration content of the part of network element equipment change, increment update is carried out to configuration data, and the full-amount configuration data is obtained by merging incremental configuration data with initial configuration data, can significantly improve the timeliness of configuration data acquisition, reduce system load, reduce configuration acquisition time, realize real-time synchronous response to network element configuration data;By the submission mode of network element equipment, determine the configuration change event perception detection process to be executed, can be respectively optimized to different submission modes such as manual submission mode and automatic submission mode of network element equipment, improve the adaptability to network element equipment.The application is widely applied in network technology field.

Description

Technical Field

[0001] This invention relates to the field of network technology, and in particular to a method and related equipment for collecting network element configuration data based on configuration change event awareness. Background Technology

[0002] In communication network systems, the configuration management of network elements such as routers and switches is a core task to ensure stable network operation. The network management system needs to obtain the current configuration of network elements in a timely and accurate manner to support key operations such as fault location, version rollback, and compliance auditing.

[0003] The current mainstream configuration collection method in the industry is "periodic full collection": the network management system sends a full configuration query command to all network elements through a preset period (e.g., once a day). After the network elements return complete configuration data, the network management system overwrites the original data to complete the update.

[0004] This method currently has the following significant drawbacks: 1. Poor real-time performance: After a configuration change, it takes until the next data collection cycle for the network management system to detect it. The delay time can reach the maximum of the cycle (e.g., 1 day), which cannot meet the real-time requirements of scenarios such as fault repair and emergency configuration adjustment. 2. High resource consumption: When there are many network elements (such as thousands of units) or a large amount of configuration data for a single network element (such as tens of thousands of instructions), the full data transmission consumes a lot of bandwidth, and the network management system needs to repeatedly process "unchanged redundant configurations", consuming hardware resources such as CPU and memory. 3. Inefficiency: The full data collection process is fixed (it is executed regardless of whether the configuration has changed), which causes the system to do useless work during "no change period". The collection efficiency is negatively correlated with the network scale and is difficult to adapt to large network scenarios.

[0005] In summary, the existing "periodic full data collection" method can no longer meet the requirements of modern communication networks for "real-time, efficient, and low-power" configuration management, and a brand-new configuration data collection method is urgently needed. Summary of the Invention

[0006] To address at least one of the aforementioned technical problems, the present invention aims to provide a method and related equipment for collecting network element configuration data based on configuration change event awareness.

[0007] On one hand, embodiments of the present invention include a method for collecting network element device configuration data based on configuration change event awareness, the method comprising the following steps: The submission modes supported by the network element devices are being tested. Based on the submission mode, the corresponding configuration change event awareness and detection process is executed to detect the incremental configuration data of the network element device; The incremental configuration data is merged with the initial configuration data to obtain the full configuration data.

[0008] Furthermore, the submission modes supported by the detection network element device include: The network element device is tested; It is determined that the network element device supports manual submission mode, automatic submission mode, or hybrid submission mode.

[0009] Further, the step of detecting incremental configuration data of the network element device by executing the corresponding configuration change event awareness and detection process according to the submission mode includes: When the network element device supports manual submission mode, a first configuration change event detection process is executed; the first configuration change event detection process includes the following steps: A subscription request is sent to the network element device through the Simple Network Management Protocol (SMMP) trap module to establish a continuous listening relationship with the network element device; Configuration change notifications are obtained through the Simple Network Management Protocol (SMLP) trap module; these notifications are generated by the network element after receiving configuration from maintenance personnel. The configuration change notification is sent to the Kafka module via the Simple Network Management Protocol Trap module. The change perception synchronization module receives the configuration change notification forwarded by the Kafka module. The change awareness and synchronization module, in response to the configuration change notification, queries the network element device to obtain the incremental configuration data.

[0010] Further, the step of detecting incremental configuration data of the network element device by executing the corresponding configuration change event awareness and detection process according to the submission mode includes: When the network element device supports automatic submission mode, a second configuration change event awareness and detection process is executed; the second configuration change event awareness and detection process includes the following steps: The telemetry plug-in module sends a subscription request to the network element device and establishes a data reporting channel with the network element device. By changing the sensing synchronization module, the main reference point and comparison interval of the network element device are set, and the initial configuration data of the network element device is obtained. The change awareness and synchronization module updates the local current configuration data of the network element device in real time; the local current configuration data is generated by the network element device after receiving configuration from the operation and maintenance personnel. The telemetry plug-in module receives real-time data from the network element device. When a first configuration difference notification is received at the first comparison time, the first configuration difference notification is encapsulated into a Kafka message and sent to the Kafka module. The first configuration difference notification is generated by the network element device after receiving configuration from the operation and maintenance personnel. By changing the perception synchronization module, the Kafka message forwarded by the Kafka module is received, and a backup reference point is set for the network element device. The telemetry plug-in module receives real-time data from the network element device. When a second configuration difference notification is received at the second comparison time, the second configuration difference notification is encapsulated into a Kafka message and sent to the Kafka module. The second configuration difference notification is generated by the network element device after receiving configuration from the operation and maintenance personnel. The first configuration difference notification and the second configuration difference notification are compared, and the incremental configuration data is determined based on the comparison result.

[0011] Further, the step of comparing the first configuration difference notification with the second configuration difference notification, and determining the incremental configuration data based on the comparison result, includes: When the first configuration difference notification is the same as the second configuration difference notification, the primary reference point is replaced with the backup reference point for the network element device, and the first configuration difference notification is determined as the incremental configuration data.

[0012] Further, the step of comparing the first configuration difference notification with the second configuration difference notification, and determining the incremental configuration data based on the comparison result, includes: When the first configuration difference notification is different from the second configuration difference notification, the backup reference point is deleted and a new backup reference point is established for the network element device. The first configuration difference notification is replaced with the second configuration difference notification for the network element device, and the device waits for the third comparison time.

[0013] Further, the step of detecting incremental configuration data of the network element device by executing the corresponding configuration change event awareness and detection process according to the submission mode includes: When the network element device supports a hybrid submission mode, a third configuration change event detection process is executed; the third configuration change event detection process includes the following steps: The configuration type mapping table is sent to the network element device through the change perception synchronization module; When the network element device issues a key configuration, it triggers the execution of the first configuration change event perception and detection process; When the network element device issues a normal configuration, it triggers the execution of the second configuration change event perception and detection process.

[0014] On the other hand, embodiments of the present invention also include a network element device configuration data acquisition system based on configuration change event awareness. This system includes a Simple Network Management Protocol (SMMP) trap module, a change-aware synchronization module, a telemetry plug-in module, and a Kafka module. The system is used to perform the following steps: The submission modes supported by the network element devices are being tested. Based on the submission mode, the corresponding configuration change event awareness and detection process is executed to detect the incremental configuration data of the network element device; The incremental configuration data is merged with the initial configuration data to obtain the full configuration data.

[0015] On the other hand, embodiments of the present invention also include a computer device, including a memory and a processor, wherein the memory is used to store at least one program, and the processor is used to load at least one program to execute the network element device configuration data acquisition method based on configuration change event awareness in the embodiments.

[0016] On the other hand, embodiments of the present invention also include a computer-readable storage medium storing a processor-executable program, which, when executed by a processor, is used to perform the network element device configuration data acquisition method based on configuration change event awareness in the embodiments.

[0017] The beneficial effects of this invention are as follows: The network element device configuration data acquisition method based on configuration change event awareness in the embodiments detects incremental configuration data of network element devices by executing a configuration change event awareness detection process. This realizes configuration change event-driven processing by network element devices. When the network management system detects a configuration change in a network element device, it queries and obtains the configuration content of the changed part of the network element device in real time, performs incremental updates on the configuration data, and merges the incremental configuration data with the initial configuration data to obtain the full configuration data. This significantly improves the timeliness of configuration data acquisition, reduces system load, reduces configuration acquisition time, and achieves real-time synchronous response to network element configuration data. By determining the configuration change event awareness detection process to be executed according to the submission mode of the network element device, it can optimize different submission modes such as manual submission mode and automatic submission mode of the network element device, thereby improving the adaptability to network element devices. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the network management system in the embodiment; Figure 2 This is a schematic diagram illustrating the steps of the network element device configuration data acquisition method based on configuration change event awareness in the embodiment. Figure 3This is a flowchart illustrating the first configuration change event perception and detection process in the embodiment. Figure 4 This is a flowchart illustrating the second configuration change event perception and detection process in the embodiment. Figure 5 This is a schematic diagram illustrating the principle of the third configuration change event perception and detection process in the embodiment; Figure 6 This is a schematic diagram of the computer device in the embodiment. Detailed Implementation

[0019] Terminology Explanation: Network element (NE), also known as a network component, is a device with an independent network identifier, a complete protocol stack, and autonomous functional logic. It is capable of independently performing core network functions such as data forwarding, signal processing, protocol termination, or service carrying, and can be centrally operated and maintained by a network management system as an independent control entity. It is the basic physical or logical unit that constitutes the communication network topology and resource carrying system. Network element devices specifically include routers, switches, transmission equipment, etc. Simple Network Management Protocol Trap (SNMPTrap): A mechanism in which network elements proactively send simple event notifications to the network management system. Telemetry plugin: Telemetry, an efficient network data acquisition technology that proactively pushes data information through a "subscribe-report" model; Kafka: A high-throughput distributed message queuing system; Commit Mode, also known as configuration commit mode, is the core effective mechanism in the field of network element device configuration management. It defines the complete execution process and atomicity rules for configuration changes from operation and maintenance input / system issuance to writing to the running configuration and officially taking effect. This mechanism is a standard configuration management capability defined by the IETF NETCONF protocol (RFC 6241), and it is also the basic support for routing and transmission network elements to achieve atomic configuration changes and rollback. Commit Mode includes manual commit mode and automatic commit mode, etc. Manual commit mode: A configuration activation mechanism for network element devices. It requires manual execution of the "commi" (submit) operation to submit and activate multiple previously issued configuration commands. A unique commit-id is generated during the submission.

[0020] Automatic commit mode: A configuration activation mechanism for network element devices, which automatically commits and activates each configuration command issued without requiring additional manual operation; commit-id: Commit identifier. A unique identifier generated by a network element device when manually committing a set of configuration commands in manual commit mode. It is used to associate the incremental configuration data corresponding to this commit to ensure that configuration changes are traceable. Baseline Point: A configuration snapshot node created on a network element device. The network element device records its full configuration at that moment, which serves as the benchmark for subsequent configuration difference comparisons.

[0021] Full configuration data: The complete set of network element device configurations at a certain moment.

[0022] Incremental configuration data: After a network element device undergoes a configuration change, only the changed configuration data is included, not the full configuration data.

[0023] This embodiment provides a method for collecting network element configuration data based on configuration change event awareness. This method can be applied to communication networks consisting of "N network elements + 1 network management system". In this embodiment, the network element types include, but are not limited to, routers, switches, and firewalls, and support "manual commit" or "automatic commit" configuration activation modes. The network management system is deployed on a centralized server (or server cluster) to realize real-time collection, storage, and updating of network element configuration data.

[0024] In this embodiment, the structure of the network management system is as follows: Figure 1 As shown. (Refer to...) Figure 1 The software architecture of this network management system consists of five core modules, which communicate asynchronously with each other via Kafka. The specific functions of these five core modules are shown in Table 1.

[0025] Table 1

[0026] Reference Figure 2 The method for collecting network element configuration data based on configuration change event awareness includes the following steps: S1. Detect the submission modes supported by the network element device; S2. Based on the submission mode, execute the corresponding configuration change event awareness and detection process to detect incremental configuration data of network element devices; S3. Merge the incremental configuration data with the initial configuration data to obtain the full configuration data.

[0027] In this embodiment, the network element device may support manual commit mode, automatic commit mode, or hybrid commit mode. Therefore, executing step S1 can determine one of the following commit modes: manual commit mode, automatic commit mode, or hybrid commit mode.

[0028] In step S2, different configuration change event awareness and detection processes are selected and executed according to different submission modes to detect incremental configuration data of network element devices.

[0029] In this embodiment, if step S1 determines that the network element device supports manual submission mode, then step S2 selects to execute the first configuration change event awareness and detection process. In this embodiment, the first configuration change event awareness and detection process executed for manual submission mode includes the following steps: S201A. Sends a subscription request to the network element device through the Simple Network Management Protocol Trap Module to establish a continuous listening relationship with the network element device; S202A. Obtain configuration change notifications through the Simple Network Management Protocol Trap Module; S203A. Sends configuration change notifications to the Kafka module via the Simple Network Management Protocol Trap module; S204A. Receive configuration change notifications forwarded by the Kafka module through the change perception synchronization module; S205A. In response to configuration change notifications, the change perception and synchronization module queries the network element devices to obtain incremental configuration data through the change perception and synchronization module.

[0030] In this embodiment, the first configuration change event perception and detection process, namely steps S201A-S205A, has the following attributes: Triggering condition: The network element device supports manual commit mode, and multiple configuration commands need to be manually executed to take effect.

[0031] Execution entities: network element device (DEVICE_A), Simple Network Management Protocol Trap module (SNMPTrap plugin module), Kafka module, configuration change awareness and synchronization module, and network management system center.

[0032] The process for steps S201A-S205A is as follows: Figure 3 As shown. (Refer to...) Figure 3 The specific steps are as follows: a. Process 1 (corresponding to step S201A): Subscribe to configuration change events The Simple Network Management Protocol Trap module (SNMPTrap plugin module) sends a "Trap subscription request" to the network element device (DEVICE_A), configures the Trap receiving address (i.e., the SNMP Trap plugin deployment address), and agrees that the "manual commit event" is the subscription object; the network element device (DEVICE_A) returns a "subscription successful" response, establishing a continuous listening relationship.

[0033] b. Process 2 (corresponding to step S202A): Issue the configuration and manually commit. Maintenance personnel issue multiple configuration commands (such as VLAN configuration and routing policies) to the network element device (DEVICE_A) via network management or CLI. After completion, they execute the "commit" command. After verifying the legality of the configuration, the network element device (DEVICE_A) generates a unique commit-id (such as "202509201030_A1B2"), records the incremental configuration data corresponding to the commit-id (containing only the commands for this change), and sends a "configuration change notification" (containing the unique identifier of DEVICE_A: for example, management IP 192.168.1.1; commit-id: 202509201030_A1B2) to the Simple Network Management Protocol Trap module (SNMPTrap plugin module).

[0034] c. Step 3 (including processes 3.1-3.2, corresponding to steps S203A-S204A): Process and forward the change notification to the Kafka module. The Simple Network Management Protocol Trap module (SNMPTrap plugin module) receives "configuration change notifications", encapsulates them into Kafka messages according to a preset format (topic: manual_commit_topic; content: {"device_ip":"192.168.1.1","commit_id":"202509201030_A1B2","event_type":"manual_commit"}), and sends them to the Kafka module (Kafka).

[0035] d. Process 4 (including processes 4.1-4.4, corresponding to steps S203A-S204A): Query incremental configuration data The configuration change awareness and synchronization module listens to "manual_commit_topic". After receiving the message forwarded by the Kafka module, it sends an "incremental configuration query request" (carrying the commit-id) to the network element device (DEVICE_A) via the NETCONF protocol or CLI. The network element device (DEVICE_A) locates the corresponding incremental data based on the commit-id and returns it to the configuration change awareness and synchronization module.

[0036] e. Process 5 (corresponding to step S3): Merge and update all configurations The configuration change awareness and synchronization module encapsulates incremental data into an "update request" (including device_ip, commit-id, and incremental command) and pushes it to the network management system center module. The network management system center module queries the locally stored full configuration of DEVICE_A (CFG_FULL_OLD), merges the incremental command with CFG_FULL_OLD, generates the latest full configuration (CFG_FULL_NEW), overwrites the original data, and records the version (associated with commit-id).

[0037] In this embodiment, if step S1 determines that the network element device supports the automatic submission mode, then step S2 selects to execute the second configuration change event awareness and detection process. In this embodiment, the second configuration change event awareness and detection process executed for the automatic submission mode includes the following steps: S201B. Send a subscription request to the network element device through the telemetry plug-in module to establish a data reporting channel with the network element device; S202B. By changing the sensing synchronization module, the main reference point and comparison interval of the network element device are set, and the initial configuration data of the network element device is obtained. S203B. Updates the local current configuration data of network element devices in real time through the change perception synchronization module; S204B. Real-time data reception of network element devices is performed through the telemetry plug-in module. When the first configuration difference notification is received at the first comparison time, the first configuration difference notification is encapsulated into a Kafka message and sent to the Kafka module. S205B. By changing the sensing synchronization module, it receives the Kafka message forwarded by the Kafka module and sets a backup reference point for the network element device; S206B. Real-time data reception of network element devices is achieved through the telemetry plug-in module. When a second configuration difference notification is received at the second comparison time, the second configuration difference notification is encapsulated into a Kafka message and sent to the Kafka module. S207B. Compare the first configuration difference notification with the second configuration difference notification, and determine the incremental configuration data based on the comparison results.

[0038] In this embodiment, the second configuration change event perception and detection process, namely steps S201B-S207B, has the following attributes: Triggering conditions: The network element device supports automatic commit mode, which takes effect automatically after a single configuration command is issued. Compared with manual commit mode, care should be taken to avoid frequent change notifications.

[0039] Execution entities: Network element device (DEVICE_A), Telemetry plugin module, Kafka module, Configuration change awareness and synchronization module, and network management system center.

[0040] The process for S201B-S207B is as follows: Figure 4 As shown. (Refer to...) Figure 4 The specific steps are as follows: a. Process 1 (corresponding step S201B): Subscribe to configuration difference data The Simple Network Management Protocol Trap module (SNMPTrap plugin module) sends a "Telemetry subscription request" to the network element device (DEVICE_A) via the gRPC protocol, and configures the subscription parameters (data type: configuration difference; reporting period: consistent with the subsequent comparison interval T); the network element device (DEVICE_A) returns a "subscription successful" response, establishing a data reporting channel.

[0041] b. Process 2 (corresponding to step S202B): Set the comparison interval and create a reference point. The configuration change awareness and synchronization module sends a "set reference point configuration comparison interval command T" (e.g., set T=1 minute) to the network element device (DEVICE_A), and then sends a "create reference point" command. P i Request; Network element device (DEVICE_A) creates primary reference point P i Meanwhile, the network element device (DEVICE_A) records the full configuration CFG_ORI at this time and returns the "primary reference point". P i "Creation successful"; at the same time, the network management system central module stores the CFG_ORI of the network element device (DEVICE_A) at this time as the initial full configuration.

[0042] c. Process 3 (corresponding to step S203B): Issue configuration and automatically commit. Operations personnel issue one or more configuration commands (such as ACL rules and NAT configurations) to the network element device (DEVICE_A). After each command is issued, the network element device (DEVICE_A) automatically executes commit and takes effect, updating the local current configuration CFG_CUR in real time.

[0043] d. Process 4 (including processes 4.1-4.4, corresponding to step S204B): Periodically compare and report differences. The time to reach the first reference point configuration comparison (e.g.) P i One minute after creation, the network element device (DEVICE_A) automatically compares CFG_CUR and CFG_ORI to identify the first difference. diff 1. The network element device (DEVICE_A) sends the first configuration difference notification (including device_ip: 192.168.1.1; reference point) to the telemetry plug-in module. P i First difference content diff 1) The telemetry plugin module encapsulates the first configuration difference notification into a Kafka message (topic: auto_commit_topic; content: {"device_ip":"192.168.1.1", "baseline":" P i “, “diff”:“ diff 1”}), sent to the Kafka module (Kafka).

[0044] e. Process 5 (corresponding step S205B): Create a backup reference point After receiving the Kafka message, the configuration change awareness and synchronization module sends a "Create Backup Baseline Request" to the network element device (DEVICE_A); the network element device (DEVICE_A) then creates the backup baseline. P i+1 The system returns "Backup reference point created successfully"; the configuration change awareness synchronization module is temporarily saved. diff 1 and P i+1 It will not be updated to the network management system.

[0045] f. Process 6 (including processes 6.1-6.7, corresponding to steps S206B-S207B): Secondary comparison and benchmark verification Reaching the second alignment time (e.g., the master reference point) P i Two minutes after creation, the network element device (DEVICE_A) compares the current CFG_CUR with CFG_ORI again to identify the second difference. diff 2. The telemetry plugin module reports to the Kafka module; the configuration change awareness synchronization module receives the second difference content. diff After step 2, compare the first difference content. diff Differences between 1 and 2 diff 2. The comparison results include "First Configuration Difference Notification (First Difference Content)". diff 1) Notification of differences with the second configuration (Second difference content) diff 2) Same as "or First configuration difference notification (first difference content)" diff 1) Notification of differences with the second configuration (Second difference content) diff 2) "Different", the following process will be implemented: a) Case 1 (corresponding to process 6.5): diff 1= diff 2 Judgment: No new configuration changes have occurred on network element device (DEVICE_A) within the past minute; backup baseline. P i+1 reliable; Operation: The configuration change awareness and synchronization module will send the first configuration difference notification (first difference content) diff 1) Push the incremental data to the network management system central module, and simultaneously issue a "reference point replacement command" (delete the old primary reference point) to the network element device (DEVICE_A). P i The original backup reference point P i+1 (Set as the primary baseline); the configuration change awareness synchronization module will notify the first configuration difference (first difference content) diff 1) Output as incremental configuration data.

[0046] b) Case 1 (corresponding to process 6.6): diff 1≠ diff 2 Judgment: Within the past minute, network element device (DEVICE_A) has undergone a new configuration change, due to the backup reference point. P i+1 If it was created within that period, then the system cannot determine the location of the network element device (DEVICE_A). P i+1 Full configuration at that time. Therefore, the backup reference point. P i+1 Unreliable; Operation: The configuration change sensing synchronization module sends a "Delete standby reference point" command to the network element device (DEVICE_A). P i+1 The instruction was given, and then a new backup reference point was created. P i+1 And update the record baseline. P i The changes are as follows diff 2 (Record it as new) diff 1) Wait for the next comparison cycle (the third comparison time, for example, after 1 minute), and repeat step 6 until... diff 1= diff 2.

[0047] In this embodiment, refer to Figure 3 and Figure 4 For the incremental configuration data output by the configuration change notification synchronization module, the network management system center executes step S3 to compare the incremental configuration data with the initial configuration CFG_ORI (i.e., the configuration at the time of creating the primary baseline). P i The full configuration at the time is merged to generate the full configuration CFG_FULL_NEW.

[0048] In this embodiment, if step S1 determines that the network element device supports the hybrid submission mode, then step S2 selects to execute the third configuration change event awareness and detection process. In this embodiment, the third configuration change event awareness and detection process executed for the automatic submission mode includes the following steps: S201C. Sends a configuration type mapping table to network element devices via the change perception synchronization module; S202C. When a network element device issues a critical configuration, it triggers the execution of the first configuration change event perception and detection process. S203C. When a network element device issues a normal configuration, it triggers the execution of the second configuration change event perception and detection process.

[0049] In this embodiment, the principle of steps S201C-S203C is as follows: Figure 5 As shown.

[0050] In this embodiment, the third configuration change event perception and detection process, namely steps S201C-S203C, has the following attributes: Scenario characteristics: Some network element devices support "hybrid commit" - critical configurations (such as system upgrades and interface IPs) need to be manually committed, while ordinary configurations (such as security policies and log configurations) support automatic commit, requiring changes in both modes to be handled simultaneously.

[0051] Execution entities: network element device (DEVICE_A), Simple Network Management Protocol Trap module (SNMPTrap plugin module), telemetry plugin module, Kafka module, configuration change awareness and synchronization module, and network management system center.

[0052] Execution logic: The configuration change awareness and synchronization module has added "configuration type identification" logic, which can associate the corresponding data collection plugin (SNMP Trap / Telemetry) based on the content of the change. When executing steps S201C-S203C, the following process is specifically performed: 1. The configuration change awareness and synchronization module sends a "configuration type mapping table" to the network element (definition: critical configuration → manual commit, ordinary configuration → automatic commit). 2. When a network element issues critical configurations, it triggers a manual commit process (i.e., the first configuration change event detection process, i.e., steps S201A-S205A), and reports it through the Simple Network Management Protocol Trap module (SNMP Trap); 3. When a network element issues a normal configuration, it triggers an automatic commit process (i.e., the second configuration change event perception and detection process, i.e., steps S201B-S207B), and reports it through the telemetry plugin module. 4. After receiving the Kafka message, the configuration change awareness and synchronization module identifies the configuration type based on "event_type" (manual_commit / auto_commit) and executes the corresponding incremental query and baseline management logic accordingly. 5. The network management system center uniformly receives incremental data from both modes and merges them into the latest full configuration of the same network element, realizing unified management of "one system, two modes".

[0053] In this embodiment, it can be derived from... Figure 1 The network management system shown is a network element device configuration data acquisition system based on configuration change event awareness, which executes a network element device configuration data acquisition method based on configuration change event awareness.

[0054] The network element configuration data acquisition method in this embodiment is applicable to real-time configuration data acquisition scenarios for various types of network elements (routers, switches, firewalls, etc.) in large-scale communication networks (such as operator backbone networks and enterprise campus networks). It can also be applied to the operation and maintenance of new metropolitan area networks, ensuring service continuity by real-time monitoring of critical configurations (such as routing policies and interface IPs). It can capture manually committed critical configuration changes within seconds, meeting the real-time requirements of scenarios such as fault repair and traffic scheduling. Furthermore, the network element configuration data acquisition method in this embodiment can also be applied to specialized networks such as 5GC and IPRAN, thereby obtaining the current configuration of network elements in a timely and accurate manner to support critical operations such as fault location, version rollback, and compliance auditing.

[0055] Specifically, current related technologies use a "non-differential periodic acquisition" method, performing full data transmission regardless of whether the configuration has changed. In contrast, the network element device configuration data acquisition method in this embodiment uses an "event-driven incremental acquisition" method, which is triggered only when the configuration changes and only transmits the changed portion. By abandoning the traditional "timed full acquisition" method, the acquisition process is triggered by "configuration change events" actively reported by the network element (manually committed SNMP Trap notifications and automatically committed Telemetry difference data). Only incremental configuration data is acquired and transmitted, rather than full data, thereby achieving second-level / minute-level synchronization of configuration changes and solving the real-time problem of traditional methods. At the same time, it significantly reduces the amount of data transmission and the network management processing load, reducing hardware resource consumption.

[0056] Specifically, current related technologies do not distinguish between network element commit modes and uniformly adopt full data collection. However, the network element device configuration data collection method in this embodiment designs differentiated solutions based on the characteristics of manual and automatic commit modes, covering the configuration mechanisms of different network elements. Specifically, for the manual commit mode (multiple commands take effect uniformly, generating commit-id), SNMP Trap is used to subscribe to change notifications in real time and associate incremental data through commit-id. For the automatic commit mode (single command takes effect immediately, prone to frequent changes), Telemetry is used to periodically subscribe to configuration differences and avoid frequent reporting through benchmark comparison. Therefore, the differentiated collection technology implemented by the network element device configuration data collection method in this embodiment, which adapts to manual / automatic commit modes, can be compatible with the configuration activation modes of mainstream network elements on the market without modifying network element hardware / software, reducing the cost of solution implementation; at the same time, it avoids the frequent reporting storms in the automatic commit mode, ensuring system stability.

[0057] In summary, the network element device configuration data acquisition method in this embodiment can achieve the following effects: 1. Significantly improved real-time performance. In manual mode, SNMP Trap notifications are triggered within seconds after network element commit, and incremental data collection achieves second-level synchronization throughout the process; in automatic mode, through minute-level periodic T comparisons, the longest lag time is only minutes (far lower than the traditional 1-day cycle), meeting the real-time requirements for fault location and emergency adjustments; 2. Resource consumption is significantly reduced. Only incremental configuration data (typically 5%-10% of the total data, or even less) is transmitted, reducing bandwidth usage by more than 90%; at the same time, the network management system does not need to repeatedly process redundant configurations, and CPU and memory consumption are also significantly reduced. 3. Significantly improved operation and maintenance efficiency. Real-time configuration synchronization reduces fault location time from "hours" to "minutes," minimizing troubleshooting time; 4. Long-term resource cost savings. Reduce bandwidth costs, alleviate resource burden, and lower hardware costs.

[0058] A computer program can be written to execute the network element device configuration data acquisition method based on configuration change event awareness in this embodiment. Figure 6 In the computer device or storage medium shown, when the computer program is read and run, the network element device configuration data acquisition method based on configuration change event awareness and / or the network element device configuration data acquisition method based on configuration change event awareness in this embodiment is executed, thereby achieving the same technical effect as the network element device configuration data acquisition method based on configuration change event awareness and / or the network element device configuration data acquisition method based on configuration change event awareness in the embodiment.

[0059] It should be noted that, unless otherwise specified, when a feature is referred to as "fixed" or "connected" to another feature, it can be directly fixed or connected to the other feature, or indirectly fixed or connected to the other feature. Furthermore, the descriptions of "upper," "lower," "left," and "right" used in this disclosure are only relative to the relative positional relationships of the components of this disclosure in the accompanying drawings. The singular forms "a" and "the" used in this disclosure are also intended to include the plural forms, unless the context clearly indicates otherwise. Moreover, unless otherwise defined, all technical and scientific terms used in this embodiment have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this embodiment specification is only for describing particular embodiments and is not intended to limit the invention. The term "and / or" as used in this embodiment includes any combination of one or more of the associated listed items.

[0060] It should be understood that although various elements may be described in this disclosure using terms such as "second," "third," etc., these elements should not be limited to these terms. These terms are used only to distinguish elements of the same type from one another. For example, an element may also be referred to as a second element without departing from the scope of this disclosure, and similarly, a second element may also be referred to as an element. The use of any and all instances or exemplary language ("e.g.," "such as," etc.) provided in this embodiment is intended only to better illustrate embodiments of the invention and, unless otherwise required, does not impose a limitation on the scope of the invention.

[0061] It should be recognized that embodiments of the present invention can be implemented or carried out by computer hardware, a combination of hardware and software, or by computer instructions stored in a non-transitory computer-readable storage medium. The method can be implemented using standard programming techniques—including a non-transitory computer-readable storage medium configured with a computer program, wherein such a storage medium causes the computer to operate in a specific and predefined manner—according to the methods and drawings described in the specific embodiments. Each program can be implemented in a high-level procedural or object-oriented programming language to communicate with the computer system. However, if desired, the program can be implemented in assembly or machine language. In any case, the language can be a compiled or interpreted language. Furthermore, for this purpose, the program can run on a programmed application-specific integrated circuit (ASIC).

[0062] Furthermore, the procedures described in this embodiment can be performed in any suitable order unless otherwise indicated by this embodiment or otherwise obviously contradict the context. The procedures (or variations and / or combinations thereof) described in this embodiment can be executed under the control of one or more computer systems configured with executable instructions, and can be implemented by hardware or a combination thereof as code (e.g., executable instructions, one or more computer programs, or one or more applications) that commonly executes on one or more processors. A computer program includes a plurality of instructions executable by one or more processors.

[0063] Furthermore, the method can be implemented in any suitable type of computing platform, including but not limited to personal computers, minicomputers, mainframes, workstations, networked or distributed computing environments, standalone or integrated computer platforms, or in communication with charged particle tools or other imaging devices, etc. Aspects of the invention can be implemented as machine-readable code stored on a non-transitory storage medium or device, whether removable or integrated into a computing platform, such as a hard disk, optical read and / or write storage medium, RAM, ROM, etc., such that it is readable by a programmable computer, and when the storage medium or device is read by the computer, it can be used to configure and operate the computer to perform the processes described herein. Furthermore, the machine-readable code, or portions thereof, can be transmitted via wired or wireless networks. The invention of this embodiment includes these and other different types of non-transitory computer-readable storage media when such media comprises instructions or programs that implement the steps above in conjunction with a microprocessor or other data processor. When programmed according to the methods and techniques of the invention, the invention also includes the computer itself.

[0064] A computer program can be applied to input data to perform the functions of this embodiment, thereby transforming the input data to generate output data stored in non-volatile memory. The output information can also be applied to one or more output devices, such as a display. In a preferred embodiment of the invention, the transformed data represents physical and tangible objects, including specific visual depictions of physical and tangible objects generated on the display.

[0065] The above are merely preferred embodiments of the present invention. The present invention is not limited to the above-described embodiments. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention, as long as they achieve the technical effects of the present invention by the same means, should be included within the scope of protection of the present invention. Within the scope of protection of the present invention, the technical solutions and / or implementation methods can have various modifications and variations.

Claims

1. A method for collecting configuration data of network element devices based on configuration change event awareness, characterized in that, The method for collecting network element configuration data based on configuration change event awareness includes the following steps: The submission modes supported by the network element devices are being tested. Based on the submission mode, the corresponding configuration change event awareness and detection process is executed to detect the incremental configuration data of the network element device; The incremental configuration data is merged with the initial configuration data to obtain the full configuration data.

2. The method for collecting network element device configuration data based on configuration change event awareness according to claim 1, characterized in that, The submission modes supported by the detection network element device include: The network element device is tested; It is determined that the network element device supports manual submission mode, automatic submission mode, or hybrid submission mode.

3. The method for collecting network element device configuration data based on configuration change event awareness according to claim 2, characterized in that, The step of performing a corresponding configuration change event awareness and detection process based on the submission mode to detect the incremental configuration data of the network element device includes: When the network element device supports manual submission mode, a first configuration change event detection process is executed; the first configuration change event detection process includes the following steps: A subscription request is sent to the network element device through the Simple Network Management Protocol (SMMP) trap module to establish a continuous listening relationship with the network element device; Configuration change notifications are obtained through the Simple Network Management Protocol (SMLP) trap module; these notifications are generated by the network element after receiving configuration from maintenance personnel. The configuration change notification is sent to the Kafka module via the Simple Network Management Protocol Trap module. The change perception synchronization module receives the configuration change notification forwarded by the Kafka module. The change awareness and synchronization module, in response to the configuration change notification, queries the network element device to obtain the incremental configuration data.

4. The method for collecting network element device configuration data based on configuration change event awareness according to claim 3, characterized in that, The step of performing a corresponding configuration change event awareness and detection process based on the submission mode to detect the incremental configuration data of the network element device includes: When the network element device supports automatic submission mode, a second configuration change event awareness and detection process is executed; the second configuration change event awareness and detection process includes the following steps: The telemetry plug-in module sends a subscription request to the network element device and establishes a data reporting channel with the network element device. By changing the sensing synchronization module, the main reference point and comparison interval of the network element device are set, and the initial configuration data of the network element device is obtained. The change awareness and synchronization module updates the local current configuration data of the network element device in real time; the local current configuration data is generated by the network element device after receiving configuration from the operation and maintenance personnel. The telemetry plug-in module receives real-time data from the network element device. When a first configuration difference notification is received at the first comparison time, the first configuration difference notification is encapsulated into a Kafka message and sent to the Kafka module. The first configuration difference notification is generated by the network element device after receiving configuration from the operation and maintenance personnel. By changing the perception synchronization module, the Kafka message forwarded by the Kafka module is received, and a backup reference point is set for the network element device. The telemetry plug-in module receives real-time data from the network element device. When a second configuration difference notification is received at the second comparison time, the second configuration difference notification is encapsulated into a Kafka message and sent to the Kafka module. The second configuration difference notification is generated by the network element device after receiving configuration from the operation and maintenance personnel. The first configuration difference notification and the second configuration difference notification are compared, and the incremental configuration data is determined based on the comparison result.

5. The method for collecting network element device configuration data based on configuration change event awareness according to claim 4, characterized in that, The step of comparing the first configuration difference notification with the second configuration difference notification and determining the incremental configuration data based on the comparison result includes: When the first configuration difference notification is the same as the second configuration difference notification, the primary reference point is replaced with the backup reference point for the network element device, and the first configuration difference notification is determined as the incremental configuration data.

6. The method for collecting network element device configuration data based on configuration change event awareness according to claim 5, characterized in that, The step of comparing the first configuration difference notification with the second configuration difference notification and determining the incremental configuration data based on the comparison result includes: When the first configuration difference notification is different from the second configuration difference notification, the backup reference point is deleted and a new backup reference point is established for the network element device. The first configuration difference notification is replaced with the second configuration difference notification for the network element device, and the device waits for the third comparison time.

7. The method for collecting network element device configuration data based on configuration change event awareness according to any one of claims 3-6, characterized in that, The step of performing a corresponding configuration change event awareness and detection process based on the submission mode to detect the incremental configuration data of the network element device includes: When the network element device supports a hybrid submission mode, a third configuration change event detection process is executed; the third configuration change event detection process includes the following steps: The configuration type mapping table is sent to the network element device through the change perception synchronization module; When the network element device issues a key configuration, it triggers the execution of the first configuration change event perception and detection process; When the network element device issues a normal configuration, it triggers the execution of the second configuration change event perception and detection process.

8. A network element device configuration data acquisition system based on configuration change event awareness, characterized in that, The network element device configuration data acquisition system based on configuration change event awareness includes a Simple Network Management Protocol (SMLP) trap module, a change awareness synchronization module, a telemetry plug-in module, and a Kafka module; the network element device configuration data acquisition system based on configuration change event awareness is used to perform the following steps: The submission modes supported by the network element devices are being tested. Based on the submission mode, the corresponding configuration change event awareness and detection process is executed to detect the incremental configuration data of the network element device; The incremental configuration data is merged with the initial configuration data to obtain the full configuration data.

9. A computer device, characterized in that, It includes a memory and a processor, wherein the memory is used to store at least one program, and the processor is used to load at least one program to execute the network element device configuration data acquisition method based on configuration change event awareness as described in any one of claims 1-7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the network element device configuration data acquisition method based on configuration change event awareness as described in any one of claims 1-7.

Images