A looped network topology relationship checking method, device, equipment and medium

Abstract

The application discloses a kind of loop network topological relation checking method, device, equipment and medium, including by preset model data constructs line model array set and operating library model;Iterate the equipment model in line model array set, determine loop network switch and outgoing line switch;According to loop network switch and outgoing line switch, generate loop network path;According to each switch code in loop network path, the current equipment in operating library model is matched and checked one by one, and generates loop network checking result;Obtain the feeder group switch queue information corresponding to loop network switch code, generate feeder checking result according to feeder group switch queue information and target switch equipment in loop network path;According to the equipment data of knowledge base data, loop network checking result, feeder checking result and loop network path, generate data report.It solves the problem that due to the large number of lines and complex structure, the loop network topological relation checking work of graph model exists difficult to find and process abnormal connection relationship in a short time.

Description

Technical Field

[0001] This invention relates to the field of ring network topology verification technology, and in particular to a method, apparatus, equipment and medium for verifying ring network topology relationships. Background Technology

[0002] In recent years, with the continuous development of the electricity market and the continuous progress of information technology, the role and status of the power grid dispatch automation system have become increasingly important. The power grid dispatch automation system is an important guarantee for ensuring the safe and stable operation of the power grid, and the line architecture topology diagram of the power grid dispatch automation system also plays a key role in the daily monitoring and fault handling of the power grid.

[0003] Currently, existing power grid dispatch automation systems suffer from problems such as inadequate GIS map management and lax process review by operation and maintenance units. These issues lead to abnormal topology connections and inconsistencies between ring network diagrams and actual GIS maps when importing GIS maps into the power grid dispatch automation system. Furthermore, the large number and complexity of lines make it difficult to quickly identify and resolve abnormal connections when verifying the ring network topology of the maps. Summary of the Invention

[0004] This invention provides a method, apparatus, device, and medium for verifying ring network topology relationships, which solves the technical problem that it is difficult to find and process abnormal connection relationships in a short time due to the large number of lines and complex structure in the verification of ring network topology relationships in diagrams.

[0005] This invention provides a method for verifying the topology of a ring network, comprising:

[0006] Acquire preset model data and construct a set of line model arrays and runtime library models;

[0007] Traverse the equipment models in the line model array set, determine the ring network switch, and determine the outgoing switch according to the line models on both sides of the ring network switch;

[0008] Perform recursive calculations on the connection relationships of the ring network switch and the outgoing switch to generate the ring network path;

[0009] According to the switch codes in the ring network path, the current devices in the runtime model are matched and verified one by one to generate the corresponding ring network verification results.

[0010] Obtain the feeder group switch queue information corresponding to the ring network switch code, and generate the corresponding feeder verification result based on the feeder group switch queue information and the target switch equipment in the ring network path;

[0011] Acquire knowledge base data, and generate a data report based on the knowledge base data, the ring network verification results, the feeder verification results, and the equipment data of the ring network path.

[0012] Optionally, the step of performing a recursive operation on the connection relationship between the ring network switch and the outgoing switch to generate the ring network path includes:

[0013] Read the downstream device of the outgoing switch, determine whether the downstream device is the ring network switch, and record the number of recursions with a preset step size;

[0014] When the lower-level device is not the ring network switch and the number of recursions is less than a preset threshold, determine whether there is a secondary device of the same level as the lower-level device;

[0015] If no secondary device of the same level as the lower-level device exists, then the target device of the lower-level device is read, and the target device is determined to be the new lower-level device.

[0016] A ring network path is generated when the new lower-level device is the ring network switch, the lower-level device is the ring network switch, or the lower-level device is not the ring network switch and the number of recursions is greater than a preset threshold.

[0017] Optionally, when there is a secondary device at the same level as the lower-level device, the secondary device is read and it is determined whether the secondary device has been traversed.

[0018] If the secondary device has been traversed, then jump to the step of determining whether there is a secondary device of the same level as the lower-level device when the lower-level device is not the ring network switch and the number of recursions is less than a preset number threshold.

[0019] If the secondary device is not traversed, the process jumps to the next lower device for reading the outgoing switch, determining whether the next lower device is the ring network switch, and recording the number of recursions with a preset step size.

[0020] Optionally, after the step of performing a recursive operation on the connection relationship between the ring network switch and the outgoing switch to generate the ring network path, the following steps are included:

[0021] Determine whether the device queue length of the ring network path is greater than a preset queue length threshold;

[0022] When the device queue length of the ring network path is greater than the preset queue length threshold, the ring network path is determined to be identified normally.

[0023] When the device queue length of the ring network path is less than a preset queue length threshold, the ring network path identification is determined to be abnormal.

[0024] Optionally, the step of matching and verifying each current device in the runtime model according to the switch codes in the ring network path to generate the corresponding ring network verification result includes:

[0025] According to the switch codes in the ring network path, the current devices in the runtime model are matched and verified one by one.

[0026] When the switch code in the ring network path is compatible with any of the current devices, obtain the connection device queue connected to the current device, and read the runtime connection code array associated with the connection device queue;

[0027] Traverse the runtime connection code array and determine whether there is an associated device in the ring network path that corresponds to the runtime connection code array;

[0028] If there is no associated device in the ring network path that corresponds to the runtime connection code array, or if the switch code in the ring network path is not compatible with each of the current devices, then an abnormal device connection result is generated.

[0029] When there is an associated device in the ring network path that corresponds to the runtime connection code array, a normal device connection result is generated.

[0030] Optionally, the step of obtaining the feeder group switch queue information corresponding to the ring network switch code, and generating the corresponding feeder verification result based on the feeder group switch queue information and the target switching equipment in the ring network path, includes:

[0031] Obtain the feeder group switch queue information corresponding to the ring network switch code, traverse the feeder group switch queue information and determine multiple feeder group switch codes;

[0032] Determine whether there is a target switching device in the ring network path that is associated with the switch code of each feeder group;

[0033] When there is a target switching device associated with the switch code of each feeder group in the ring network path, read the order array associated with the target switching device and determine whether the order array increases or decreases sequentially.

[0034] When the order array increases or decreases sequentially, a normal feeder verification result is generated;

[0035] If the order array is not sequentially increasing and sequentially decreasing, then a feeder verification anomaly result is generated and the anomaly location is recorded;

[0036] If there is no target switching device associated with the switch code of each feeder group in the ring network path, a feeder verification anomaly result is generated and the missing target switching device is recorded.

[0037] Optionally, the step of acquiring knowledge base data and generating a data report based on the knowledge base data, the ring network verification results, the feeder verification results, and the equipment data of the ring network path includes:

[0038] Acquire knowledge base data and construct a knowledge base using the knowledge base data;

[0039] Extract the abnormal results corresponding to the ring network verification results and the feeder verification results respectively, and determine the error type based on the abnormal results;

[0040] Match the error type with the preset exception types in the knowledge base one by one;

[0041] When the error type matches any of the preset exception types, obtain the processing solution associated with the preset exception type and record the exception result and the processing solution;

[0042] When the error type does not match any of the preset exception types, the exception result is recorded;

[0043] A data report is generated based on the abnormal results, the processing plan, and the device data of the device model.

[0044] A second aspect of the present invention provides a ring network topology verification device, comprising:

[0045] The data acquisition module is used to acquire preset model data and construct a line model array set and a runtime model;

[0046] The traversal model module is used to traverse the equipment models in the line model array set, determine the ring network switch, and determine the outgoing line switch according to the line models on both sides of the ring network switch.

[0047] The recursive operation module is used to perform recursive operation on the connection relationship of the ring network switch and the outgoing switch to generate the ring network path;

[0048] The matching data module is used to perform matching and verification on each current device in the runtime model according to the switch codes in the ring network path, and generate the corresponding ring network verification results.

[0049] The encoding module is used to acquire feeder group switch queue information corresponding to the ring network switch code, and generate corresponding feeder verification results based on the feeder group switch queue information and the target switch equipment in the ring network path.

[0050] The data report generation module is used to acquire knowledge base data and generate a data report based on the knowledge base data, the ring network verification results, the feeder verification results, and the equipment data of the ring network path.

[0051] A third aspect of the present invention provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the ring network topology verification method as described in any of the preceding claims.

[0052] The fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed, implements the ring network topology verification method as described in any of the preceding claims.

[0053] As can be seen from the above technical solutions, the present invention has the following advantages:

[0054] The process involves acquiring preset model data to construct a line model array set and a runtime model; traversing the device models in the line model array set to determine ring network switches and outgoing switches based on the line models on both sides of the ring network switches; performing recursive connection relationship operations on the ring network switches and outgoing switches to generate ring network paths; matching and verifying each current device in the runtime model according to the switch codes in the ring network path to generate corresponding ring network verification results; acquiring feeder group switch queue information corresponding to the ring network switch codes, and generating corresponding feeder verification results based on the feeder group switch queue information and the target switch devices in the ring network path; acquiring knowledge base data, and generating a data report based on the knowledge base data, the ring network verification results, the feeder verification results, and the device data of the ring network path. This method solves the problem of difficulty in quickly finding and processing abnormal connection relationships in the ring network topology verification work due to the large number of lines and complex structures, effectively improving the efficiency of ring network topology verification work, reducing the workload of staff, and improving the accuracy of the topology of the diagram model. Attached Figure Description

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

[0056] Figure 1 This is a flowchart illustrating the steps of a ring network topology verification method provided in Embodiment 1 of the present invention.

[0057] Figure 2This is a flowchart illustrating the steps of a ring network topology verification method provided in Embodiment 2 of the present invention.

[0058] Figure 3 This is a flowchart illustrating an application example of ring network path analysis in a ring network topology verification method provided in Embodiment 2 of the present invention.

[0059] Figure 4 This is a flowchart illustrating an application example of recursive operation analysis of connection relationships in a ring network topology verification method provided in Embodiment 2 of the present invention.

[0060] Figure 5 The flowchart is an application example of runtime verification analysis in a ring network topology verification method provided in Embodiment 2 of the present invention;

[0061] Figure 6 A flowchart illustrating an application example of FA self-healing feeder group analysis in a ring network topology verification method provided in Embodiment 2 of the present invention;

[0062] Figure 7 This is a structural block diagram of a ring network topology verification device provided in Embodiment 3 of the present invention. Detailed Implementation

[0063] This invention provides a method, apparatus, device, and medium for verifying ring network topology relationships, which addresses the technical problem that the verification of ring network topology relationships in graphical models is difficult to find and process abnormal connections in a short time due to the large number of lines and complex structures.

[0064] To make the objectives, features, and advantages of this invention more apparent and understandable, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described below are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0065] Please see Figure 1 , Figure 1 The flowchart illustrates the steps of a ring network topology verification method provided in this embodiment of the invention.

[0066] This invention provides a method for verifying the topology of a ring network, comprising:

[0067] Step 101: Obtain preset model data and construct a line model array set and a runtime model.

[0068] The preset model data refers to all the data of the distribution network map model of the GIS system and the OCS system. The OCS system is the database of the power grid dispatch automation system; the GIS system is the GIS model of the distribution network dispatch automation system, which is an XML file used by the distribution network system to describe the connection relationship and equipment model.

[0069] It should be noted that by reading XML file data from the GIS system through the Qt platform, leveraging the ample memory resources of current computers and the ability of hash lists to quickly retrieve values ​​using keys, all devices are read into memory using their GISIDs as keys and model data as values, resulting in various model arrays. Each XML file identifies each element using a GISID. For model arrays within the same file, the GISID of the line information within that file is used as the key for model classification and storage. Separate key-value mappings are performed for commonly used substations, power supply stations, and ring network equipment. This method allows for rapid retrieval of key equipment information, including switches and disconnectors, using line GISIDs and device GISIDs, and rapid acquisition of management unit attributes through the management unit GISID set in the equipment settings. This provides crucial support and efficiency improvements for model analysis and calculation, and ring network path calculation. Here, Qt platform refers to the cross-platform C++ graphical user interface application development framework developed by Qt Company; GISID refers to the unique identifier assigned to a device in the GIS model file, which is the first attribute defined in the model.

[0070] Based on the above, all data in the distribution network map model includes power supply stations, substations, feeders, switches, disconnectors, and line sections. Specifically, the distribution network map model data from the GIS system is constructed into a line model array set, which includes container models and equipment models. Container models include power supply stations, substations, and feeders; equipment models include switches, disconnectors, line sections, busbars, and transformers. The distribution network map model data from the OCS system is constructed into a runtime model, which includes FA self-healing feeder groups. This step involves designing a minimal model structure group that can cache the power grid model and connection relationships, discarding single-endpoint models unrelated to connection relationships, such as towers, displays, and instrument transformers.

[0071] In this embodiment of the invention, preset model data is obtained, and a line model array set and a runtime library model are constructed.

[0072] Step 102: Traverse the equipment models in the line model array set, determine the ring network switch, and determine the outgoing line switch based on the line models on both sides of the ring network switch.

[0073] In this embodiment of the invention, the equipment models in the line model array are traversed to determine the ring network switch and the outgoing line switch is determined according to the line models on both sides of the ring network switch.

[0074] Step 103: Perform recursive calculations on the connection relationships of the ring network switches and outgoing switches to generate the ring network path.

[0075] It should be noted that, starting with the outgoing switch as the initial device and the ring network switch as the target device, the connection relationship is searched using a model connection relationship lookup algorithm and based on the connection relationship of the line model array set. The connection relationship is then recursively calculated on the ring network switch and the outgoing switch to generate the ring network path.

[0076] In this embodiment of the invention, a recursive operation on the connection relationship is performed on the ring network switch and the outgoing switch to generate the ring network path.

[0077] Step 104: According to the switch codes in the ring network path, perform matching and verification on each current device in the runtime model to generate the corresponding ring network verification results.

[0078] It should be noted that the OCS system model uses the relational database reading module component of the Qt platform to complete the database reading. According to the switch codes in the ring network path, it matches and verifies the current devices in the runtime model one by one to generate the corresponding ring network verification results. Here, the switch code refers to the switch code of each switch device in the ring network path.

[0079] In this embodiment of the invention, the current devices in the runtime model are matched and verified one by one according to the switch codes in the ring network path to generate the corresponding ring network verification results.

[0080] Step 105: Obtain the feeder group switch queue information corresponding to the ring network switch code, and generate the corresponding feeder verification result based on the feeder group switch queue information and the target switch equipment in the ring network path.

[0081] The feeder group switch queue information refers to the automated switch queue information of the FA self-healing feeder group.

[0082] In this embodiment of the invention, feeder group switch queue information corresponding to the ring network switch code is obtained, and corresponding feeder verification results are generated based on the feeder group switch queue information and the target switch equipment in the ring network path.

[0083] Step 106: Obtain knowledge base data, and generate a data report based on the knowledge base data, ring network verification results, feeder verification results, and equipment data of the ring network path.

[0084] In this embodiment of the invention, knowledge base data is acquired, and a data report is generated based on the knowledge base data, ring network verification results, feeder verification results, and equipment data of the ring network path.

[0085] In this embodiment of the invention, preset model data is acquired to construct a line model array set and a runtime model; the equipment models in the line model array set are traversed to determine the ring network switch and the outgoing line switch is determined according to the line models on both sides of the ring network switch; recursive operation on the connection relationship is performed on the ring network switch and the outgoing line switch to generate the ring network path; according to the switch codes in the ring network path, the current equipment in the runtime model is matched and verified one by one to generate the corresponding ring network verification result; the feeder group switch queue information corresponding to the ring network switch code is acquired, and the corresponding feeder verification result is generated according to the feeder group switch queue information and the target switch equipment in the ring network path; knowledge base data is acquired, and a data report is generated according to the knowledge base data, the ring network verification result, the feeder verification result, and the equipment data of the ring network path. This solves the problem that due to the large number of lines and the complexity of the structure, it is difficult to find and process abnormal connection relationships in the ring network topology relationship verification work of the diagram model in a short time, effectively improving the efficiency of the ring network topology relationship verification work, reducing the workload of staff, and improving the accuracy of the diagram model topology.

[0086] Please see Figure 2 , Figure 2 The flowchart illustrates the steps of a ring network topology verification method provided in Embodiment 2 of the present invention.

[0087] This invention provides a method for verifying the topology of a ring network, comprising:

[0088] Step 201: Obtain preset model data and construct a line model array set and a runtime model.

[0089] In this embodiment of the invention, the specific implementation process of step 201 is similar to that of step 101, and will not be repeated here.

[0090] Step 202: Traverse the equipment models in the line model array set, determine the ring network switch, and determine the outgoing line switch based on the line models on both sides of the ring network switch.

[0091] It should be noted that, firstly, the line model array set is traversed, and the device of type ring network switch in the device model of the line model array set is identified. The names of the two sides of the line recorded by the ring network switch device are read, and the corresponding two-side line models are obtained according to the two-side line names. The line switches are then identified in the two-side line models respectively.

[0092] In this embodiment of the invention, the equipment models in the line model array are traversed to determine the ring network switch and the outgoing line switch is determined according to the line models on both sides of the ring network switch.

[0093] Step 203: Perform recursive calculations on the connection relationships of the ring network switches and outgoing switches to generate the ring network path.

[0094] It should be noted that the model connection relationship lookup algorithm is used to recursively search for the connection relationship of the starting device. The recursive operation is terminated when one of the following three boundaries is reached: the next lower-level device is the target device, the connection relationship endpoint is encountered, or the number of recursions exceeds the limit. If the target device is found, the device model is returned; otherwise, 0 is returned and the operation cache is cleared.

[0095] Furthermore, step 203 may include the following sub-steps:

[0096] Step S31: Read the downstream device of the outgoing switch, determine whether the downstream device is a ring network switch and preset the step size to record the number of recursions.

[0097] It should be noted that in the initial stage, the outgoing switch is used as the starting device and the ring network switch is used as the target device. The device nodes that have a connection relationship from the starting device to the target device are obtained, that is, the device queue composed of each subordinate device, the starting device and the target device, and the step size is preset to record the number of recursions.

[0098] In this embodiment of the invention, the downstream device of the outgoing switch is read, it is determined whether the downstream device is a ring network switch, and the recursion count is recorded with a preset step size.

[0099] Step S32: When the next-level device is not a ring network switch and the number of recursions is less than the preset number threshold, determine whether there is a secondary device of the same level as the next-level device.

[0100] It should be noted that when a downstream device of the outgoing switch is read, if the downstream device is not a ring network device (i.e., the target device), the recursion count is compared with a preset threshold. If the downstream device is not a ring network device and the recursion count is less than the preset threshold, it is then determined whether there is a secondary device of the same level as the downstream device. A secondary device refers to a device of the same type or level as the downstream device. That is, the device queue may contain multiple downstream devices connected to the outgoing switch. In this embodiment of the invention, the preset threshold can be set as needed and is not specifically limited here.

[0101] In this embodiment of the invention, when the next-level device is not a ring network switch and the number of recursions is less than a preset threshold, it is determined whether there is a secondary device of the same level as the next-level device.

[0102] Step S33: If there is no secondary device at the same level as the lower-level device, read the target device of the lower-level device and determine the target device as the new lower-level device.

[0103] It should be noted that when there is no secondary device at the same level as the lower-level device, the target device of the lower-level device is read, that is, the target device connected to the lower-level device is read and the target device is determined to be the new lower-level device.

[0104] In this embodiment of the invention, if there is no secondary device at the same level as the lower-level device, the target device of the lower-level device is read and the target device is determined to be the new lower-level device.

[0105] Step S34: When the new downstream device is a ring network switch, or the downstream device is not a ring network switch and the number of recursions is greater than the preset number threshold, a ring network path is generated.

[0106] It should be noted that after determining that the target device is a new subordinate device, it is determined whether the new subordinate device is a ring network switch. If the new subordinate device is a ring network switch, the subordinate device is a ring network switch, or the subordinate device is not a ring network switch and the number of recursions is greater than the preset number of times threshold, a ring network path is generated. If the subordinate device is not a ring network switch and the number of recursions is greater than the preset number of times threshold, a ring network path is generated and the ring network path acquisition failure is recorded.

[0107] In this embodiment of the invention, a ring network path is generated when the new lower-level device is a ring network switch, the lower-level device is a ring network switch, or the lower-level device is not a ring network switch and the number of recursions is greater than a preset threshold number.

[0108] Step S35: When there is a secondary device at the same level as the lower-level device, read the secondary device and determine whether the secondary device has been traversed.

[0109] It should be noted that if there is a secondary device at the same level as the lower-level device, that is, if there are other lower-level devices, the secondary device is read and it is determined whether the secondary device has been traversed.

[0110] In this embodiment of the invention, when there is a secondary device at the same level as the lower-level device, the secondary device is read and it is determined whether the secondary device has been traversed.

[0111] Step S36: If the secondary device has been traversed, then jump to the step of determining whether there is a secondary device of the same level as the lower-level device when the lower-level device is not a ring network switch and the number of recursions is less than the preset number threshold.

[0112] It should be noted that if the secondary device has been traversed, the process will jump to the step of determining whether there is a secondary device of the same level as the lower-level device when the lower-level device is not a ring network switch and the number of recursions is less than the preset threshold. That is, it will continue to determine whether there are other lower-level devices.

[0113] In this embodiment of the invention, if the secondary device has been traversed, the process jumps to the step of determining whether there is a secondary device of the same level as the lower-level device when the lower-level device is not a ring network switch and the number of recursions is less than a preset threshold.

[0114] Step S37: If the secondary device has not been traversed, jump to the step of reading the downstream device of the outgoing switch, determining whether the downstream device is a ring network switch and recording the number of recursions with a preset step size.

[0115] It should be noted that if the secondary device is not traversed, the process jumps to the next lower device that reads the outgoing switch, determines whether the lower device is a ring network switch and records the number of recursions with a preset step size, and continues to determine whether the secondary device is a ring network switch.

[0116] In this embodiment of the invention, if the secondary device is not traversed, the process jumps to the next lower device for reading the outgoing switch, determines whether the next lower device is a ring network switch, and records the number of recursions with a preset step size.

[0117] Step 204: Determine whether the device queue length of the ring network path is greater than the preset queue length threshold.

[0118] It should be noted that the device queue, consisting of interconnected device nodes, that leads from the starting device to the target device (i.e., the ring network path) is obtained. When generating the ring network path and recording it as a failure to obtain the ring network path, the entire device queue only contains the starting device and the target device, and its queue length must be equal to 2. Therefore, the ring network path can only be considered successfully obtained if the queue length is greater than 2. In this embodiment of the invention, the preset queue length is set to 2.

[0119] In this embodiment of the invention, it is determined whether the device queue length of the ring network path is greater than a preset queue length threshold.

[0120] Step 205: When the device queue length of the ring network path is greater than the preset queue length threshold, the ring network path identification is determined to be normal.

[0121] It should be noted that when the device queue length of the ring network path is greater than the preset queue length threshold, the ring network path is considered to be recognized normally, that is, the ring network path is considered to be successfully obtained.

[0122] In this embodiment of the invention, when the device queue length of the ring network path is greater than a preset queue length threshold, the ring network path identification is determined to be normal.

[0123] Step 206: When the device queue length of the ring network path is less than the preset queue length threshold, the ring network path identification is determined to be abnormal.

[0124] It should be noted that when the device queue length of the ring network path is less than the preset queue length threshold, the ring network path identification is deemed abnormal, that is, the generated ring network path only has the starting device and the target device, and the ring network path acquisition is deemed to have failed.

[0125] In this embodiment of the invention, when the device queue length of the ring network path is less than a preset queue length threshold, the ring network path identification is determined to be abnormal.

[0126] Step 207: According to the switch codes in the ring network path, perform matching and verification on each current device in the runtime model to generate the corresponding ring network verification results.

[0127] It should be noted that, by combining experience in manual connection verification and adopting a one-way verification method, the efficiency of connection verification has been effectively improved.

[0128] Furthermore, step 207 may include the following sub-steps:

[0129] Step S71: According to the switch codes in the ring network path, perform matching and verification on each current device in the runtime model.

[0130] It should be noted that, according to the switch codes in the ring network path, the current devices in the runtime model are matched and verified one by one. That is, the calculation is performed in the direction from the outgoing switch to the ring network switch, and the current devices associated with each switch code are verified to see if they exist in the runtime model. Here, the switch code refers to the GISID of all switching devices in the ring network path.

[0131] In this embodiment of the invention, the current devices in the runtime model are matched and verified one by one according to the switch codes in the ring network path.

[0132] Step S72: When the switch code in the ring network path is compatible with any current device, obtain the connection device queue connected to the current device, and read the runtime connection code array associated with the connection device queue.

[0133] It should be noted that when a switch code matches any current device in the runtime model, the queue of connected devices connected to that current device and within the runtime model is retrieved. The runtime connection code array associated with the connected device queue is then read using the device code of the current device. Here, the device code of the current device refers to the current device's DEVID, and the runtime connection code array refers to the runtime's connection DEVID array. DEVID is a unique identifier assigned to a device by the runtime model, and it is the first attribute defined in the data model.

[0134] In this embodiment of the invention, when the switch code in the ring network path is compatible with any current device, the connection device queue connected to the current device is obtained, and the runtime connection code array associated with the connection device queue is read.

[0135] Step S73: Traverse the runtime connection code array and determine whether there is an associated device in the ring network path that corresponds to the runtime connection code array.

[0136] It should be noted that the runtime connection code array is traversed, and the corresponding subordinate device connected to the current device can be found in the ring network path based on whether the runtime connection code array can be found. In other words, the hierarchical relationship between each device in the ring network path and each device in the runtime model is compared to see if they correspond.

[0137] In this embodiment of the invention, the runtime connection code array is traversed to determine whether there is an associated device in the ring network path that corresponds to the runtime connection code array.

[0138] Step S74: When there is no associated device in the ring network path that corresponds to the runtime connection code array, or when the switch code in the ring network path does not match any of the current devices, an abnormal device connection result is generated.

[0139] It should be noted that the abnormal results of device connection relationships include abnormal results of connection relationships of superior devices and abnormal results of connection relationships of current devices. When there is no associated device in the ring network path that corresponds to the connection code array of the runtime library, that is, when it is impossible to find an associated device connected to the current device in the ring network path based on the connection code array of the runtime library, an abnormal result of connection relationship of current device is generated. When the switch codes in the ring network path do not match any of the current devices, that is, when it is impossible to find the corresponding current device in the runtime library model based on each switch code, an abnormal result of connection relationship of superior devices is generated.

[0140] In this embodiment of the invention, when there is no associated device in the ring network path corresponding to the runtime connection code array or when the switch code in the ring network path is not compatible with each current device, an abnormal device connection result is generated.

[0141] Step S75: When there is an associated device in the ring network path that corresponds to the runtime connection code array, a normal device connection result is generated.

[0142] It should be noted that when there are associated devices in the ring network path that correspond to the runtime connection code array, that is, when the hierarchical relationship between each device in the ring network path and each device in the runtime model is correct, the generated device connection relationship will be normal.

[0143] In this embodiment of the invention, when there is an associated device in the ring network path that corresponds to the runtime connection code array, a normal device connection result is generated.

[0144] Step 208: Obtain the feeder group switch queue information corresponding to the ring network switch code, and generate the corresponding feeder verification result based on the feeder group switch queue information and the target switch equipment in the ring network path.

[0145] Furthermore, step 208 may include the following sub-steps:

[0146] Step S81: Obtain the feeder group switch queue information corresponding to the ring network switch code, traverse the feeder group switch queue information and determine multiple feeder group switch codes.

[0147] It should be noted that by traversing each ring network path, the switch queue information of the corresponding FA self-healing feeder group is obtained through the GISID of the ring network switch in the ring network path, i.e., the ring network switch code. Then, the switch queue information of the FA self-healing feeder group is traversed to determine the switch codes of multiple feeder groups.

[0148] In this embodiment of the invention, feeder group switch queue information corresponding to the ring network switch code is obtained, the feeder group switch queue information is traversed, and multiple feeder group switch codes are determined.

[0149] Step S82: Determine whether there are target switching devices in the ring network path that are associated with the switch codes of each feeder group.

[0150] It should be noted that the corresponding target switching equipment is located in the ring network path according to the switch code of each feeder group.

[0151] In this embodiment of the invention, it is determined whether there is a target switching device in the ring network path that is associated with the switch code of each feeder group.

[0152] Step S83: When there is a target switching device associated with the switch code of each feeder group in the ring network path, read the order array associated with the target switching device and determine whether the order array increases or decreases sequentially.

[0153] It should be noted that when there are target switching devices associated with the switch codes of each feeder group in the ring network path, that is, the switching devices corresponding to the switch codes of each feeder group of the FA self-healing feeder group can be found in the ring network path, the order array associated with the target switching device is read and the order array is further determined to increase or decrease sequentially.

[0154] In this embodiment of the invention, when there is a target switching device associated with the switch code of each feeder group in the ring network path, the order array associated with the target switching device is read and compared to determine whether the order array increases or decreases sequentially.

[0155] Step S84: When the sequence array increases or decreases sequentially, a normal feeder verification result is generated.

[0156] In this embodiment of the invention, when the order array increases or decreases sequentially, a normal feeder verification result is generated.

[0157] Step S85: When the order array is not sequentially increasing or decreasing, generate a feeder verification anomaly result and record the anomaly location.

[0158] It should be noted that when the order array is not sequentially increasing or decreasing, i.e. when the order array is out of order, a feeder verification error result is generated and the error location is recorded.

[0159] In this embodiment of the invention, when the order array is not sequentially increasing and sequentially decreasing, a feeder verification anomaly result is generated and the anomaly location is recorded.

[0160] Step S86: When there is no target switchgear associated with the switch code of each feeder group in the ring network path, generate a feeder verification anomaly result and record the missing target switchgear.

[0161] It should be noted that if there is no target switchgear associated with the switch codes of each feeder group in the ring network path, it indicates that the feeder group of FA self-healing is abnormal, and feeder verification abnormal results are generated and the missing target switchgear is recorded.

[0162] Step 209: Obtain knowledge base data, and generate a data report based on the knowledge base data, ring network verification results, feeder verification results, and equipment data of the ring network path.

[0163] Furthermore, step 209 may include the following sub-steps:

[0164] Step S91: Obtain knowledge base data and construct a knowledge base using the knowledge base data.

[0165] It should be noted that the knowledge base data is acquired and stored in the form of hash key-value pairs to construct the knowledge base. User-saved knowledge base data is simultaneously saved to memory and a knowledge base file. The knowledge base file is read into the runtime memory upon startup, thereby loading and updating the knowledge base.

[0166] In this embodiment of the invention, knowledge base data is acquired, and a knowledge base is constructed using the knowledge base data.

[0167] Step S92: Extract the abnormal results corresponding to the ring network verification results and feeder verification results respectively, and determine the error type based on the abnormal results.

[0168] In this embodiment of the invention, abnormal results corresponding to the ring network verification results and feeder verification results are extracted respectively, and the error type is determined based on the abnormal results.

[0169] Step S93: Match the error type with the preset exception types in the knowledge base one by one.

[0170] It should be noted that after determining the error type based on the abnormal results, the error type needs to be matched one by one with the preset abnormal types in the knowledge base to determine whether the error type exists in the knowledge base.

[0171] In this embodiment of the invention, the error type is matched one by one with the preset exception types in the knowledge base.

[0172] Step S94: When the error type matches any preset exception type, obtain the processing solution associated with the preset exception type and record the exception result and processing solution.

[0173] It should be noted that when the error type matches any preset exception type, the system will automatically match the processing solution associated with the preset exception type, record and display the exception result and the processing solution.

[0174] In this embodiment of the invention, when the error type matches any preset exception type, a processing solution associated with the preset exception type is obtained, and the exception result and processing solution are recorded. By automatically matching the topology relationship exception processing solution, a knowledge base of corresponding problem processing solutions is compiled for common topology relationship exception problems. The corresponding processing solution is automatically matched in the topology verification results, which facilitates maintenance personnel to quickly complete the problem processing.

[0175] Step S95: When the error type does not match any of the preset exception types, record the exception result.

[0176] It should be noted that when the error type does not match any of the preset exception types, that is, when the knowledge base does not store the error type and the corresponding handling solution, the exception result will be recorded and displayed.

[0177] In this embodiment of the invention, when the error type does not match any of the preset exception types, the exception result is recorded.

[0178] Step S96: Generate a data report based on the abnormal results, handling plan, and equipment data of the equipment model.

[0179] In this embodiment of the invention, a data report is generated based on the abnormal results, the processing plan, and the device data of the device model.

[0180] Please see Figures 3-6 , Figure 3 This is a flowchart illustrating an application example of ring network path analysis in a ring network topology verification method provided in Embodiment 2 of the present invention.

[0181] The process iterates through the device models in the line model array to obtain the ring network switch. Based on the ring network switch, it determines the line models on both sides and the outgoing line switches based on the line models on both sides. It takes the outgoing line switches and the ring network switch as input, reads the downstream devices of the outgoing line switches, and determines whether the downstream device is a ring network switch. If the downstream device is a ring network switch, it outputs the ring network path. If the downstream device is not a ring network switch, it compares the number of recursions with a preset threshold. If the number of recursions is greater than the preset threshold, it determines that the ring network path acquisition has failed; if the number of recursions is less than the preset threshold, it determines that the ring network path acquisition has failed. If a threshold number of iterations is set, the system checks if there are no more devices of the same level or type. If so, it checks if other devices of the same level or type exist. If so, it reads the device and checks if it has already been traversed. If it has, it returns to the step of checking for other devices of the same level or type. If it hasn't been traversed, it checks if the device is a ring switch. If no device of the same level exists, it reads the devices connected to the device, i.e., it reads the lower-level devices and checks if they are ring switches. After outputting the ring path,

[0182] Determine if the queue length of the ring network path is greater than 2. If the queue length of the ring network path is greater than 2, the ring network path identification is considered normal. If the queue length of the ring network path is less than 2, the ring network path identification is considered abnormal.

[0183] Obtain the GISID of the device in the ring network path. Based on the GISID, determine whether the current device corresponding to the GISID has been successfully obtained in the runtime model. If the current device is successfully obtained, continue to obtain the queue of connected devices connected to the current device in the runtime model. Traverse the DEVID array of the connected device queue and determine whether the lower-level device connected to the current device can be found in the ring network path, i.e., the associated device, based on the DEVID array. If the lower-level device connected to the current device cannot be found in the ring network path, the connection relationship of the current device is determined to be abnormal. If the lower-level device connected to the current device can be found in the ring network path, the connection relationship is determined to be normal. If the current device cannot be successfully obtained, the connection relationship of the upper-level device is determined to be abnormal.

[0184] The FA feeder group switch queue is obtained based on the GISID of the ring network switches in the ring network path. The FA feeder group switch queue is traversed to determine the switch queue information. Based on the switch queue information, it is determined whether the device corresponding to the switch queue information can be found in the ring network path, i.e., the target switch device. If the device corresponding to the switch queue information can be found in the ring network path, the order array of each device in the ring network path is obtained. The order array is verified to determine whether the order array increases or decreases sequentially. If the order array increases or decreases sequentially, the feeder verification result is considered normal. If the order array is out of order, i.e., it does not increase or decrease sequentially, the feeder verification result is considered abnormal and the abnormal position is recorded. If the device corresponding to the switch queue information cannot be found in the ring network path, the feeder verification result is considered abnormal and the missing device is recorded.

[0185] In this embodiment of the invention, preset model data is acquired to construct a line model array set and a runtime model; the equipment models in the line model array set are traversed to determine the ring network switch and the outgoing line switch is determined according to the line models on both sides of the ring network switch; recursive operation on the connection relationship is performed on the ring network switch and the outgoing line switch to generate the ring network path; according to the switch codes in the ring network path, the current equipment in the runtime model is matched and verified one by one to generate the corresponding ring network verification result; the feeder group switch queue information corresponding to the ring network switch code is acquired, and the corresponding feeder verification result is generated according to the feeder group switch queue information and the target switch equipment in the ring network path; knowledge base data is acquired, and a data report is generated according to the knowledge base data, the ring network verification result, the feeder verification result, and the equipment data of the ring network path. This solves the problem that due to the large number of lines and the complexity of the structure, it is difficult to find and process abnormal connection relationships in the ring network topology relationship verification work of the diagram model in a short time, effectively improving the efficiency of the ring network topology relationship verification work, reducing the workload of staff, and improving the accuracy of the diagram model topology.

[0186] Please see Figure 7 , Figure 7 This is a structural block diagram of a ring network topology verification device provided in Embodiment 3 of the present invention.

[0187] The present invention provides a ring network topology verification device, comprising:

[0188] The data acquisition module 301 is used to acquire preset model data and construct a line model array set and a runtime model.

[0189] The traversal model module 302 is used to traverse the equipment models in the line model array set, determine the ring network switch, and determine the outgoing line switch based on the line models on both sides of the ring network switch.

[0190] The recursive operation module 303 is used to perform recursive operation on the connection relationship of the ring network switch and the outgoing switch to generate the ring network path.

[0191] The matching data module 304 is used to match and verify each current device in the runtime model according to the switch codes in the ring network path, and generate the corresponding ring network verification results.

[0192] The encoding module 305 is used to obtain the feeder group switch queue information corresponding to the ring network switch code, and generate the corresponding feeder verification result based on the feeder group switch queue information and the target switch equipment in the ring network path.

[0193] The data report generation module 306 is used to acquire knowledge base data and generate data reports based on the knowledge base data, ring network verification results, feeder verification results, and equipment data of the ring network path.

[0194] Furthermore, the recursive operation module 303 includes:

[0195] The "Read Sub-devices" submodule is used to read the sub-devices of the outgoing line switch, determine whether the sub-device is a ring network switch, and preset the step size to record the number of recursions.

[0196] The comparison threshold submodule is used to determine whether there is a secondary device of the same level as the lower-level device when the lower-level device is not a ring network switch and the number of recursions is less than a preset threshold.

[0197] The target device reading submodule is used to read the target device of the lower-level device if no secondary device of the same level as the lower-level device exists, and to determine the target device as the new lower-level device.

[0198] The ring network path generation submodule is used to generate a ring network path when the new downstream device is a ring network switch, the downstream device is a ring network switch, or the downstream device is not a ring network switch and the number of recursions exceeds a preset threshold.

[0199] Furthermore, it also includes:

[0200] The secondary device read module is used to read the secondary device when a secondary device of the same level as the lower-level device exists, and to determine whether the secondary device has been traversed.

[0201] The traversal judgment module is used to determine whether there is a secondary device of the same level as the lower-level device if the secondary device has been traversed.

[0202] The jump step module is used to jump to the next-level device that reads the outgoing switch if the secondary device has not been traversed, determine whether the next-level device is a ring network switch, and record the number of recursions with a preset step size.

[0203] Furthermore, it also includes:

[0204] The device queue determination module is used to determine whether the device queue length of the ring network path is greater than the preset queue length threshold.

[0205] The normal identification module is used to determine that the ring network path is identified normally when the device queue length of the ring network path is greater than a preset queue length threshold.

[0206] The anomaly identification module is used to determine that the ring network path is abnormal when the device queue length of the ring network path is less than a preset queue length threshold.

[0207] Furthermore, the matching data module 304 includes:

[0208] The matching and verification submodule is used to match and verify each current device in the runtime model according to the switch codes in the ring network path.

[0209] The Read Encoding Array submodule is used to obtain the connection device queue connected to the current device and read the runtime connection encoding array associated with the connection device queue when the switch encoding in the ring network path is compatible with any current device.

[0210] The Traverse Encoding Array submodule is used to traverse the runtime connection encoding array and determine whether there are associated devices in the ring network path that correspond to the runtime connection encoding array.

[0211] The submodule for generating abnormal results is used to generate abnormal results for device connection relationships when there is no associated device in the ring network path that corresponds to the connection code array of the runtime library, or when the switch codes in the ring network path are not compatible with each current device.

[0212] The "Generate Normal Results" submodule is used to generate normal results for device connection relationships when there are associated devices in the ring network path that correspond to the runtime connection code array.

[0213] Furthermore, the encoding module 305 includes:

[0214] The queue information acquisition submodule is used to acquire feeder group switch queue information corresponding to the ring network switch code, traverse the feeder group switch queue information, and determine multiple feeder group switch codes.

[0215] The switchgear detection submodule is used to determine whether there are target switchgear devices in the ring network path that are associated with the switch codes of each feeder group.

[0216] The order array reading submodule is used to read the order array associated with the target switchgear and determine whether the order array increases or decreases sequentially when there is a target switchgear associated with the switch codes of each feeder group in the ring network path.

[0217] The "Generate Feeder Normal Result" submodule is used to generate a feeder verification normal result when the order array increases or decreases sequentially.

[0218] The abnormal location recording submodule is used to generate feeder verification abnormal results and record the abnormal location when the order array is not sequentially increasing or decreasing.

[0219] The missing device recording submodule is used to generate feeder verification anomaly results and record the missing target switchgear when there is no target switchgear associated with the switch codes of each feeder group in the ring network path.

[0220] Furthermore, the data report generation module 306 includes:

[0221] The Knowledge Base Data Acquisition Submodule is used to acquire knowledge base data and construct the knowledge base using that data.

[0222] The results extraction submodule is used to extract the abnormal results corresponding to the ring network verification results and feeder verification results respectively, and determine the error type based on the abnormal results.

[0223] The Matching Type submodule is used to match error types with preset exception types in the knowledge base one by one.

[0224] The solution acquisition submodule is used to acquire the processing solution associated with any preset exception type and record the exception result and processing solution when the error type matches any preset exception type.

[0225] The exception recording submodule is used to record exception results when the error type does not match any of the preset exception types.

[0226] A data reporting submodule is built to generate data reports based on equipment data from anomaly results, handling solutions, and equipment models.

[0227] In this embodiment of the invention, preset model data is acquired to construct a line model array set and a runtime model; the equipment models in the line model array set are traversed to determine the ring network switch and the outgoing line switch is determined according to the line models on both sides of the ring network switch; recursive operation on the connection relationship is performed on the ring network switch and the outgoing line switch to generate the ring network path; according to the switch codes in the ring network path, the current equipment in the runtime model is matched and verified one by one to generate the corresponding ring network verification result; the feeder group switch queue information corresponding to the ring network switch code is acquired, and the corresponding feeder verification result is generated according to the feeder group switch queue information and the target switch equipment in the ring network path; knowledge base data is acquired, and a data report is generated according to the knowledge base data, the ring network verification result, the feeder verification result, and the equipment data of the ring network path. This solves the problem that due to the large number of lines and the complexity of the structure, it is difficult to find and process abnormal connection relationships in the ring network topology relationship verification work of the diagram model in a short time, effectively improving the efficiency of the ring network topology relationship verification work, reducing the workload of staff, and improving the accuracy of the diagram model topology. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices, modules, and sub-modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0228] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0229] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0230] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0231] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0232] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for verifying the topology of a ring network, characterized in that, include: Acquire preset model data and construct a set of line model arrays and runtime library models; Traverse the equipment models in the line model array set, determine the ring network switch, and determine the outgoing switch according to the line models on both sides of the ring network switch; Perform recursive calculations on the connection relationships of the ring network switch and the outgoing switch to generate the ring network path; According to the switch codes in the ring network path, the current devices in the runtime model are matched and verified one by one to generate corresponding ring network verification results, including: According to the switch codes in the ring network path, the current devices in the runtime model are matched and verified one by one. When the switch code in the ring network path is compatible with any of the current devices, obtain the connection device queue connected to the current device, and read the runtime connection code array associated with the connection device queue; Traverse the runtime connection code array and determine whether there is an associated device in the ring network path that corresponds to the runtime connection code array; If there is no associated device in the ring network path that corresponds to the runtime connection code array, or if the switch code in the ring network path is not compatible with any of the current devices, then an abnormal device connection result is generated. When there is an associated device in the ring network path that corresponds to the runtime connection code array, a normal device connection result is generated. Obtain the feeder group switch queue information corresponding to the ring network switch code, and generate the corresponding feeder verification result based on the feeder group switch queue information and the target switchgear in the ring network path, including: Traverse the feeder group switch queue information and determine multiple feeder group switch codes; Determine whether there is a target switching device in the ring network path that is associated with the switch code of each feeder group; When there is a target switching device associated with the switch code of each feeder group in the ring network path, read the order array associated with the target switching device and determine whether the order array increases or decreases sequentially. When the order array increases or decreases sequentially, a normal feeder verification result is generated; If the order array is not sequentially increasing and sequentially decreasing, then a feeder verification anomaly result is generated and the anomaly location is recorded; If there is no target switching device associated with the switch code of each feeder group in the ring network path, a feeder verification anomaly result is generated and the missing target switching device is recorded. Acquire knowledge base data, and generate a data report based on the knowledge base data, the ring network verification results, the feeder verification results, and the equipment data of the ring network path.

2. The ring network topology verification method according to claim 1, characterized in that, The step of performing recursive calculations on the connection relationships of the ring network switch and the outgoing switch to generate the ring network path includes: Read the downstream device of the outgoing switch, determine whether the downstream device is the ring network switch, and record the number of recursions with a preset step size; When the lower-level device is not the ring network switch and the number of recursions is less than a preset threshold, determine whether there is a secondary device of the same level as the lower-level device; If no secondary device of the same level as the lower-level device exists, then the target device of the lower-level device is read, and the target device is determined to be the new lower-level device. A ring network path is generated when the new lower-level device is the ring network switch, the lower-level device is the ring network switch, or the lower-level device is not the ring network switch and the number of recursions is greater than a preset threshold.

3. The ring network topology verification method according to claim 2, characterized in that, Also includes: When a secondary device of the same level as the lower-level device exists, read the secondary device and determine whether the secondary device has been traversed. If the secondary device has been traversed, then jump to the step of determining whether there is a secondary device of the same level as the lower-level device when the lower-level device is not the ring network switch and the number of recursions is less than a preset threshold. If the secondary device is not traversed, the process jumps to the next lower device for reading the outgoing switch, determining whether the next lower device is the ring network switch, and recording the number of recursions with a preset step size.

4. The ring network topology verification method according to claim 1, characterized in that, After the step of performing recursive calculations on the connection relationships of the ring network switch and the outgoing switch to generate the ring network path, the following steps are included: Determine whether the device queue length of the ring network path is greater than a preset queue length threshold; When the device queue length of the ring network path is greater than the preset queue length threshold, the ring network path is determined to be identified normally. When the device queue length of the ring network path is less than a preset queue length threshold, the ring network path identification is determined to be abnormal.

5. The ring network topology verification method according to claim 1, characterized in that, The step of acquiring knowledge base data and generating a data report based on the knowledge base data, the ring network verification results, the feeder verification results, and the equipment data of the ring network path includes: Acquire knowledge base data and construct a knowledge base using the knowledge base data; Extract the abnormal results corresponding to the ring network verification results and the feeder verification results respectively, and determine the error type based on the abnormal results; Match the error type with the preset exception types in the knowledge base one by one; When the error type matches any of the preset exception types, obtain the processing solution associated with the preset exception type and record the exception result and the processing solution; When the error type does not match any of the preset exception types, the exception result is recorded; A data report is generated based on the abnormal results, the processing plan, and the device data of the device model.

6. A ring network topology verification device, applied to the ring network topology verification method of claim 1, characterized in that, include: The data acquisition module is used to acquire preset model data and construct a line model array set and a runtime model; The traversal model module is used to traverse the equipment models in the line model array set, determine the ring network switch, and determine the outgoing line switch according to the line models on both sides of the ring network switch. The recursive operation module is used to perform recursive operation on the connection relationship of the ring network switch and the outgoing switch to generate the ring network path; The matching data module is used to perform matching and verification on each current device in the runtime model according to the switch codes in the ring network path, and generate the corresponding ring network verification results. The encoding acquisition module is used to acquire feeder group switch queue information corresponding to the ring network switch code, and generate corresponding feeder verification results based on the feeder group switch queue information and the target switch equipment in the ring network path; The data report generation module is used to acquire knowledge base data and generate a data report based on the knowledge base data, the ring network verification results, the feeder verification results, and the equipment data of the ring network path.

7. An electronic device, characterized in that, The device includes a memory and a processor. The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the ring network topology verification method as described in any one of claims 1-5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed, it implements the ring network topology verification method as described in any one of claims 1-5.

Images