CN109683923B - Method and system for checking configuration file version of power distribution automation system - Google Patents
Method and system for checking configuration file version of power distribution automation system Download PDFInfo
- Publication number
- CN109683923B CN109683923B CN201710968831.1A CN201710968831A CN109683923B CN 109683923 B CN109683923 B CN 109683923B CN 201710968831 A CN201710968831 A CN 201710968831A CN 109683923 B CN109683923 B CN 109683923B
- Authority
- CN
- China
- Prior art keywords
- configuration
- version
- file
- checking
- terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 88
- 238000009826 distribution Methods 0.000 title claims abstract description 49
- 230000008569 process Effects 0.000 claims abstract description 66
- 238000012795 verification Methods 0.000 claims description 135
- 230000008859 change Effects 0.000 claims description 69
- 238000004891 communication Methods 0.000 claims description 27
- 125000004122 cyclic group Chemical group 0.000 claims description 13
- 230000000051 modifying effect Effects 0.000 claims description 8
- 230000009471 action Effects 0.000 claims description 4
- 238000013499 data model Methods 0.000 claims description 4
- 238000005259 measurement Methods 0.000 claims description 4
- 239000007787 solid Substances 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 abstract description 3
- 230000006870 function Effects 0.000 description 28
- 230000006399 behavior Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 11
- 238000007726 management method Methods 0.000 description 9
- 238000004590 computer program Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 239000000284 extract Substances 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 230000004069 differentiation Effects 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method and a system for checking a configuration file version of a power distribution automation system, which comprises the steps of checking a file version of a substation configuration file SCD in the process of upgrading from a low version to a high version; and tracing and checking the previous-level historical version of the CID version of the terminal configuration file. The technical scheme provided by the invention checks the forward/reverse versions of different configuration files, ensures that the configuration process can be traced back, finds errors in the evolution process of the configuration version in time, improves the accuracy of the configuration content of the file, reduces the manual check cost and improves the automatic operation and maintenance efficiency of power distribution.
Description
Technical Field
The invention belongs to the technical field of distribution automation, and particularly relates to a method and a system for checking a configuration file version of a distribution automation system.
Background
At present, a novel distribution automation terminal supporting the IEC61850 standard and the plug-and-play function gradually starts to be put into operation on trial, and the subsequent problems of terminal operation, maintenance and configuration also become daily work applied to a distribution automation system. In order to adapt to the construction and application modes of different power distribution automation systems, a new generation power distribution automation system of the IEC61850 standard is adopted to optimize and improve the original standardized configuration process, feeder configuration files are introduced, a configuration system architecture with a three-layer configuration file structure integrating system configuration, feeder configuration and terminal configuration is formed, the configuration file types are more complex, and the conversion and strong coupling relationship among the different-layer configuration files brings a lot of difficulties to the version management of the configuration files.
At present, related researches on version differentiation analysis, version management, integrated management and control, full-life cycle management, version comparison and verification, version authority management and the like of a substation configuration file SCD are carried out in the power transformation field, so that the problem of version management of the configuration file of an intelligent substation is solved from a local or global perspective, the focus is mostly on version management of the substation system configuration file SCD and a terminal configuration file CID, however, in view of the practical characteristics of the difference of an intelligent station and a power distribution automation system, especially the topological structure of a power distribution feeder line, frequent change of an operation mode, a fault differentiation processing mode and the like, the method cannot be directly used for type object and version management of the distribution automation system configuration file.
Disclosure of Invention
The invention provides a method and a system for checking a configuration file version of a power distribution terminal, which are used for solving the problems of approval and verification of the configuration file version and upgrading management of the configuration file version of a large-scale power distribution terminal by a power distribution master station.
The invention provides a checking method of a distribution automation system configuration file version, which comprises the following steps of;
verifying the file version of the SCD in the process of upgrading the low version to the high version;
and tracing and checking the previous-level historical version of the CID version of the terminal configuration file.
The tracing and checking the previous-stage historical version of the terminal configuration file CID version comprises the following steps:
s2.1: acquiring a terminal configuration file CID of the current power distribution terminal and performing CRC (cyclic redundancy check) on the CID, wherein the step S2.2 is executed when the CID passes the verification, otherwise, judging whether the CID does not pass for 3 times continuously, if so, interrupting the verification, otherwise, prompting an error, and repeating the step S2.1;
s2.2: generating a new terminal configuration file CID, analyzing the new terminal configuration file CID and the old terminal configuration file CID, performing version tracing verification, and downloading the new terminal configuration file CID if the version tracing verification is passed;
the version tracing check comprises the following steps:
s3.1: comparing whether the version information of the new and old terminal configuration files CID is consistent, if so, executing S3.2, otherwise, terminating the configuration flow;
s3.2: comparing the configuration version parameter information of the CID of the new and old terminal configuration files, if at least one of the configuration version parameter information is different, executing S3.3, otherwise, terminating the configuration flow;
s3.3: comparing the CID of the new and old terminal configuration files to obtain new and changed contents, comparing the new contents to check whether the structures of the new and old terminal configuration files are consistent with the structures of the corresponding parts of the ICD of the terminal function description file, checking if the structures are consistent, and otherwise prompting an alarm; and checking the changed contents item by item according to the configuration updating table, finishing verification if all the changed contents pass the checking, and otherwise prompting an alarm.
The configuration version parameter information includes: the semantic data model DatamodelSemantic, communication behavior information communicative behavior, device information Settings, and Configuration information Configuration.
The checking the file version in the process of upgrading the SCD low version of the transformer substation configuration file to the SCD high version comprises the following steps: any one or more of configuration loop 1 verification, configuration loop 2 verification, configuration loop 3 verification and configuration loop 4 verification.
The configuration loop 1 is used for verifying the change of the substation configuration file SCD caused by the change of the terminal function description file ICD and comprises the following steps:
s6.1: acquiring a new terminal function description file ICD, performing CRC on the ICD, terminating the configuration process if the CRC does not pass, and executing S6.2 if the CRC passes;
s6.2: performing version verification on the terminal function description file ICD, if the version verification fails, terminating the configuration process, and if the version verification passes, executing S6.3;
s6.3: analyzing a terminal function description file ICD, extracting equipment ID and manufacturer information, searching a terminal configuration file CID of the current operating equipment according to the ID, analyzing the terminal configuration file CID, comparing the IED element contents of the terminal function description file ICD and the terminal configuration file CID, acquiring change information of the IED element contents, identifying modified and newly added elements, and extracting model configuration version parameter information;
s6.4: completing the configuration of a substation configuration file SCD, generating a new terminal configuration file CID, analyzing the new terminal configuration file CID, extracting IED element content of the new terminal configuration file CID, matching with change information of the IED element content acquired by S6.3, feeding back error information if the matching result is inconsistent, and interrupting verification; if the matching is consistent and no new elements exist, comparing the model configuration version parameter information of the CID of the new and old terminal configuration files, if the result is consistent, checking and passing, otherwise, prompting an alarm; and if the matching is consistent and the newly added elements exist, comparing the model configuration version parameter information of the new and old terminal configuration files CID, if the model configuration version parameter value of the new version terminal configuration file CID is higher than the model configuration version parameter value of the old version terminal configuration file CID, the verification is passed, and otherwise, prompting an alarm.
The step of verifying the SCD change of the substation configuration file caused by the IID change of the terminal instantiation description file by the configuration loop 2 comprises the following steps:
s7.1: reading a terminal instantiation description file IID of a terminal, performing CRC (cyclic redundancy check) on the terminal instantiation description file IID, and terminating a configuration process if the terminal instantiation description file IID does not pass the CRC; if the verification is passed, executing S7.2;
s7.2: analyzing the terminal instantiation description file IID, searching the currently-operating terminal configuration file CID, respectively extracting data set Dataset elements, DOI elements, DAI elements, private Privitae element information and configuration attribute CF parameter values of the terminal instantiation description file IID and the terminal configuration file CID, comparing, and identifying newly-added and updated elements;
s7.3: and updating the SCD of the substation configuration file, generating a terminal configuration file CID, comparing the terminal configuration file CID with the newly added and updated elements identified by the S7.2, if the comparison result is consistent, the version of the configuration attribute CF is updated, and the historical version of the newly generated terminal configuration file CID is the same as the version of the old terminal configuration file CID, passing the verification, otherwise, prompting an alarm and checking the verification process.
The configuration loop 3 is used for verifying the change of the substation configuration file SCD caused by the change of the SSD in the system specification description file and comprises the following steps:
s8.1: acquiring a new system specification description file SSD, performing CRC (cyclic redundancy check) on the system specification description file SSD, terminating a configuration process if the CRC does not pass, and executing S8.2 if the CRC passes;
s8.2: performing version verification on the newly generated system specification description file SSD, if the verification fails, terminating the configuration flow, and if the verification passes, executing S8.3;
s8.3: analyzing an SSD (solid State disk) of a new system specification description file and an SSD of an old system specification description file, sequentially comparing information of a voltage level element, all equipment, a connection point and an end point under a feeder line element, and marking changed elements;
s8.4: generating a new substation configuration file SCD, sequentially checking whether the comparison result between topology change information in the substation configuration file SCD and S8.3 is consistent, if so, checking, executing S8.5, and if not, prompting an alarm and re-checking the configuration process;
s8.5: and traversing the Substation substtation element according to the feeder ID of the SCD to generate a feeder configuration file FCD.
The verification of the configuration loop 4 for the SCD self-updating of the substation configuration file comprises the following steps:
analyzing a substation configuration file SCD, reconfiguring communication network element information, updating link overtime parameter information, adding and deleting equipment data set content, modifying a control block value, enabling/disabling a control block, reconfiguring IED element content, modifying an action parameter value, updating a protection fixed value and a remote measurement dead zone value, generating a new substation configuration file SCD, comparing the new and old substation configuration files SCD, checking whether the communication behavior parameter value is updated, if the communication behavior parameter value of the new substation configuration file SCD is higher than that of the old version, and the version information value of the new substation configuration file SCD is equal to that of the old substation configuration file SCD, passing verification 1, otherwise failing verification, and prompting an alarm; comparing the new and old substation configuration files SCD, checking whether the constant value parameter value is updated, if the constant value parameter value of the new substation configuration file SCD is higher than the old constant value parameter value and the version information value of the new substation configuration file SCD is equal to the version information value of the old substation configuration file SCD, passing the verification 2, otherwise, failing to pass the verification, and prompting an alarm; if both checks 1 and 2 pass, then configuration loop 4 passes the check.
The CRC check includes: and calculating the CRC check code of the configuration file and comparing the CRC check code with the check code carried by the configuration file, wherein if the result is inconsistent, the check is not passed, and if the result is consistent, the check is passed.
The version verification comprises the following steps:
analyzing the configuration file, extracting the content of the History element, comparing whether the version and revision version attribute information is consistent with the version record of the file, if not, checking is not passed, and if so, checking is passed.
The IED element content includes: logical device information LD, logical node information LN, data object information DO, and data attribute information DA.
The invention provides a checking system for a distribution automation system configuration file version, which comprises:
SCD check module: verifying the file version of the SCD in the process of upgrading the low version to the high version;
a CID checking module: and tracing and checking the previous-level historical version of the CID version of the terminal configuration file.
The CID checking module comprises:
a CRC check submodule: acquiring a terminal configuration file CID of the current power distribution terminal, performing CRC (cyclic redundancy check) on the CID, judging whether the CRC continuously makes mistakes for 3 times, if so, interrupting the CRC, otherwise, prompting an alarm and performing CRC again;
and a version tracing check submodule: and generating a new terminal configuration file CID, analyzing the new terminal configuration file CID and the old terminal configuration file CID, performing version tracing verification, and downloading the new configuration file if the version tracing verification is passed.
The SCD checking module comprises:
the first verification submodule is used for verifying a configuration loop 1, and the configuration loop 1 is used for verifying the SCD change of the substation configuration file caused by the ICD change of the terminal function description file;
the second checking submodule is used for checking a configuration loop 2, and the checking of the configuration loop 2 is used for checking the SCD change of the substation configuration file caused by the IID change of the terminal instantiation description file;
the third verification submodule is used for verifying a configuration loop 3, and the verification of the configuration loop 3 is used for verifying the SCD change of the substation configuration file caused by the SSD change of the system specification description file;
and the fourth checking submodule is used for checking a configuration loop 4, and the checking of the configuration loop 4 is used for checking the SCD self-updating of the substation configuration file.
Compared with the closest prior art, the technical scheme provided by the invention has the following beneficial effects:
the technical scheme provided by the invention is used for managing the type object and the version of the configuration file of the distribution automation system, forward checking of the file version in the process of upgrading from a low version to a high version is adopted for the SCD of the substation configuration file, source tracing and reverse checking are carried out on the previous-level historical version of the CID version of the terminal configuration file, and forward/reverse version checking is carried out on different configuration files, so that the configuration process can be traced back, errors in the evolution process of the configuration version can be found in time, the manual checking cost is reduced, and the operation and maintenance efficiency of the distribution automation is improved;
according to the technical scheme provided by the invention, the reverse check combining the CRC check and the version tracing check is used for improving the accuracy of the file configuration content;
according to the technical scheme provided by the invention, any one or more of configuration loops 1, 2, 3 and 4 are adopted for checking the SCD of the substation configuration file, so that the comprehensiveness of the checking is ensured, and the accuracy of the file configuration content is improved.
Drawings
Fig. 1 is a schematic diagram illustrating a method for checking a configuration file version of a distribution automation system according to the present invention;
FIG. 2 is a diagram of a power distribution terminal profile transformation relationship according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a configuration file verification process according to an embodiment of the present invention;
FIG. 4 is a flow chart of forward verification of a substation configuration file SCD according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a CID reverse verification process of a terminal profile according to an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the attached drawing figures:
the configuration file types of the invention comprise:
1) SCD file: substation configuration file for describing distribution network
2) SSD file: and the system specification description file is used for describing the global distribution feeder topology.
3) FCD file: a feeder configuration file describing a local distribution feeder topology.
4) ICD file: and the terminal function description file is provided by the equipment manufacturer.
5) CID file: and the terminal configuration file is generated by the terminal configuration tool according to the SCD file.
6) IID file: and the terminal instantiates a description file which is generated when the power distribution operation mode, the network reconstruction, the state change and the reconfiguration of the power distribution equipment are carried out.
The configuration files describe the power distribution network object by using an SCL language, the logic model and the configuration information of the terminal or the system are covered, and the conversion relation among the configuration files is shown in figure 2. The header part of the configuration file defines a History element for recording file version change process information, including a current file version number and a historical file version number, and performs configuration version tracking by adopting a model configuration version, a fixed value parameter version, a Configuration (CF) attribute variable version and a communication configuration version parameter.
The configuration file version checking is divided into forward checking and reverse checking. Forward checking refers to file version upgrading checking in the process of upgrading a configuration file from a low version to a high version; the reverse check refers to a source tracing check for tracing the previous historical version of the current configuration file version. The SCD describes the global configuration information of the power distribution automation system, and comprises file information description, power distribution network topology description, communication network description, terminal function configuration information description and data object definition information. As shown in fig. 3, the SCD is used as a hub link in the configuration process, changes of ICD, IID, and SSD files cause changes of SCD files, and changes of SCD files generate new CID and FCD files, so that a configuration version of the distribution automation system adopts a forward check mode to ensure global uniqueness of configuration information of the distribution automation system. The CID file is used for describing the function and configuration information of a certain power distribution terminal and guiding the terminal to actually operate. The content of the CID file is derived from the SCD file and is a subset of the SCD file, and the checking mode mainly adopts reverse checking mainly based on tracing. In order to ensure that the file content change version is updated in real time, each configuration file is provided with a CRC check code, and the check code algorithm is uniform. And other configuration files are used as procedural files, and version change verification is mainly performed in a CRC mode.
As shown in fig. 1, the present invention provides a method for checking a configuration file version of a power distribution automation system, including;
verifying the file version of the SCD in the process of upgrading the low version to the high version;
and tracing and checking the previous-level historical version of the CID version of the terminal configuration file.
The tracing and checking the previous-stage historical version of the terminal configuration file CID version comprises the following steps:
s2.1: acquiring a terminal configuration file CID of the current power distribution terminal and performing CRC (cyclic redundancy check) on the CID, wherein the step S2.2 is executed when the CID passes the verification, otherwise, judging whether the CID does not pass for 3 times continuously, if so, interrupting the verification, otherwise, prompting an error, and repeating the step S2.1;
s2.2: generating a new terminal configuration file CID, analyzing the new terminal configuration file CID and the old terminal configuration file CID, performing version tracing verification, and downloading the new terminal configuration file CID if the version tracing verification is passed;
the version tracing check comprises the following steps:
s3.1: comparing whether the version information of the new and old terminal configuration files CID is consistent, if so, executing S3.2, otherwise, terminating the configuration flow;
s3.2: comparing the configuration version parameter information of the CID of the new and old terminal configuration files, if at least one of the configuration version parameter information is different, executing S3.3, otherwise, terminating the configuration flow;
s3.3: and comparing the CID of the new and old terminal configuration files to obtain the new and changed contents: checking whether the structures of the newly added content and the corresponding parts of the terminal function description file ICD are consistent, if so, checking, and otherwise, prompting an alarm; and checking the changed contents item by item according to the configuration updating table, finishing verification if all the changed contents pass the checking, and otherwise prompting an alarm.
The configuration version parameter information includes: the semantic data model DatamodelSemantic, communication behavior information communicative behavior, device information Settings, and Configuration information Configuration.
The checking the file version in the process of upgrading the SCD low version of the transformer substation configuration file to the SCD high version comprises the following steps: any one or more of configuration loop 1 verification, configuration loop 2 verification, configuration loop 3 verification and configuration loop 4 verification.
The configuration loop 1 is used for verifying the change of the substation configuration file SCD caused by the change of the terminal function description file ICD and comprises the following steps:
s6.1: acquiring a new terminal function description file ICD, performing CRC on the ICD, terminating the configuration process if the CRC does not pass, and executing S6.2 if the CRC passes;
s6.2: performing version verification on the terminal function description file ICD, if the version verification fails, terminating the configuration process, and if the version verification passes, executing S6.3;
s6.3: analyzing a terminal function description file ICD, extracting equipment ID and manufacturer information, searching a terminal configuration file CID of the current operating equipment according to the ID, analyzing the terminal configuration file CID, comparing the IED element contents of the terminal function description file ICD and the terminal configuration file CID, acquiring change information of the IED element contents, identifying modified and newly added elements, and extracting model configuration version parameter information;
s6.4: completing the configuration of a substation configuration file SCD, generating a new terminal configuration file CID, analyzing the new terminal configuration file CID, extracting IED element content of the new terminal configuration file CID, matching with change information of the IED element content acquired by S6.3, feeding back error information if the matching result is inconsistent, and interrupting verification; if the matching is consistent and no new elements exist, comparing the model configuration version parameter information of the CID of the new and old terminal configuration files, if the result is consistent, checking and passing, otherwise, prompting an alarm; and if the matching is consistent and the newly added elements exist, comparing the model configuration version parameter information of the new and old terminal configuration files CID, if the model configuration version parameter value of the new version terminal configuration file CID is higher than the model configuration version parameter value of the old version terminal configuration file CID, the verification is passed, and otherwise, prompting an alarm.
The step of verifying the SCD change of the substation configuration file caused by the IID change of the terminal instantiation description file by the configuration loop 2 comprises the following steps:
s7.1: reading a terminal instantiation description file IID of a terminal, performing CRC (cyclic redundancy check) on the terminal instantiation description file IID, and terminating a configuration process if the terminal instantiation description file IID does not pass the CRC; if the verification is passed, executing S7.2;
s7.2: analyzing the terminal instantiation description file IID, searching the currently-operating terminal configuration file CID, respectively extracting data set Dataset elements, DOI elements, DAI elements, private Privitae element information and configuration attribute CF parameter values of the terminal instantiation description file IID and the terminal configuration file CID, comparing, and identifying newly-added and updated elements;
s7.3: and updating the SCD of the substation configuration file, generating a terminal configuration file CID, comparing the terminal configuration file CID with the newly added and updated elements identified by the S7.2, if the comparison result is consistent, the version of the configuration attribute CF is updated, and the historical version of the newly generated terminal configuration file CID is the same as the version of the old terminal configuration file CID, passing the verification, otherwise, prompting an alarm and checking the verification process.
The configuration loop 3 is used for verifying the change of the substation configuration file SCD caused by the change of the SSD in the system specification description file and comprises the following steps:
s8.1: acquiring a new system specification description file SSD, performing CRC (cyclic redundancy check) on the system specification description file SSD, terminating a configuration process if the CRC does not pass, and executing S8.2 if the CRC passes;
s8.2: performing version verification on the newly generated system specification description file SSD, if the verification fails, terminating the configuration flow, and if the verification passes, executing S8.3;
s8.3: analyzing an SSD (solid State disk) of a new system specification description file and an SSD of an old system specification description file, sequentially comparing information of a voltage level element, all equipment, a connection point and an end point under a feeder line element, and marking changed elements;
s8.4: generating a new substation configuration file SCD, sequentially checking whether the comparison result between topology change information in the substation configuration file SCD and S8.3 is consistent, if so, checking, executing S8.5, and if not, prompting an alarm and re-checking the configuration process;
s8.5: and traversing the Substation substtation element according to the feeder ID of the SCD to generate a feeder configuration file FCD.
The verification of the configuration loop 4 for the SCD self-updating of the substation configuration file comprises the following steps:
analyzing a substation configuration file SCD, reconfiguring communication network element information, updating link overtime parameter information, adding and deleting equipment data set content, modifying a control block value, enabling/disabling a control block, reconfiguring IED element content, modifying an action parameter value, updating a protection fixed value and a remote measurement dead zone value, generating a new substation configuration file SCD, comparing the new and old substation configuration files SCD, checking whether the communication behavior parameter value is updated, if the communication behavior parameter value of the new substation configuration file SCD is higher than that of the old version, and the version information value of the new substation configuration file SCD is equal to that of the old substation configuration file SCD, passing verification 1, otherwise failing verification, and prompting an alarm; comparing the new and old substation configuration files SCD, checking whether the constant value parameter value is updated, if the constant value parameter value of the new substation configuration file SCD is higher than the old constant value parameter value and the version information value of the new substation configuration file SCD is equal to the version information value of the old substation configuration file SCD, passing the verification 2, otherwise, failing to pass the verification, and prompting an alarm; if both checks 1 and 2 pass, then configuration loop 4 passes the check.
The CRC check includes: and calculating the CRC check code of the configuration file and comparing the CRC check code with the check code carried by the configuration file, wherein if the result is inconsistent, the check is not passed, and if the result is consistent, the check is passed.
The version verification comprises the following steps:
analyzing the configuration file, extracting the content of the History element, comparing whether the version and revision version attribute information is consistent with the version record of the file, if not, checking is not passed, and if so, checking is passed.
The IED element content includes: logical device information LD, logical node information LN, data object information DO, and data attribute information DA.
Based on the same concept, the invention provides a checking system for a distribution automation system configuration file version, which comprises the following steps:
SCD check module: verifying the file version of the SCD in the process of upgrading the low version to the high version;
a CID checking module: and tracing and checking the previous-level historical version of the CID version of the terminal configuration file.
The CID checking module comprises:
a CRC check submodule: acquiring a terminal configuration file CID of the current power distribution terminal, performing CRC (cyclic redundancy check) on the CID, judging whether the CRC continuously makes mistakes for 3 times, if so, interrupting the CRC, otherwise, prompting an alarm and performing CRC again;
and a version tracing check submodule: and generating a new terminal configuration file CID, analyzing the new terminal configuration file CID and the old terminal configuration file CID, performing version tracing verification, and downloading the new configuration file if the version tracing verification is passed.
The SCD checking module comprises:
the first verification submodule is used for verifying a configuration loop 1, and the configuration loop 1 is used for verifying the SCD change of the substation configuration file caused by the ICD change of the terminal function description file;
the second checking submodule is used for checking a configuration loop 2, and the checking of the configuration loop 2 is used for checking the SCD change of the substation configuration file caused by the IID change of the terminal instantiation description file;
the third verification submodule is used for verifying a configuration loop 3, and the verification of the configuration loop 3 is used for verifying the SCD change of the substation configuration file caused by the SSD change of the system specification description file;
and the fourth checking submodule is used for checking a configuration loop 4, and the checking of the configuration loop 4 is used for checking the SCD self-updating of the substation configuration file.
The version tracing check submodule comprises:
the first comparison unit is used for comparing whether the version information of the CID of the new and old terminals is consistent or not, and if the version information of the CID of the new and old terminals is inconsistent, the configuration process is terminated;
the second comparison unit is used for comparing the configuration version parameter information of the CID of the new and old terminals, if the configuration version parameter information is the same, otherwise, the configuration process is terminated;
a third comparison unit, which is used for comparing the new and old terminal configuration files CID to obtain new and changed contents, comparing the new contents to check whether the structures of the new and old terminal configuration files CID and the corresponding parts of the terminal function description file ICD are consistent, if so, checking, otherwise, prompting an alarm; and checking the changed contents item by item according to the configuration updating table, finishing checking if all the changed contents pass the checking, and otherwise prompting an alarm.
The configuration version parameter information includes: the semantic data model DatamodelSemantic, communication behavior information communicative behavior, device information Settings, and Configuration information Configuration.
The first check submodule includes:
the first CRC unit is used for acquiring a new terminal function description file ICD, performing CRC on the ICD, and terminating the configuration flow if the CRC does not pass;
the first version verification unit is used for performing version verification on the terminal function description file ICD, and if the version verification fails, the configuration flow is terminated;
the identification unit is used for analyzing a terminal function description file ICD, extracting equipment ID and manufacturer information, searching a terminal configuration file CID of the current in-transit equipment according to the ID, analyzing the terminal configuration file CID, comparing the IED element contents of the terminal function description file ICD and the terminal configuration file CID, acquiring change information of the IED element contents, identifying modified and newly added elements, and extracting model configuration version parameter information;
IED element verification unit: completing the configuration of a substation configuration file SCD, generating a new terminal configuration file CID, analyzing the new terminal configuration file CID, extracting IED element content of the new terminal configuration file CID and the obtained change information of the IED element content for matching, and if the matching result is inconsistent, feeding back error information and interrupting verification; if the matching is consistent and no new elements exist, comparing the model configuration version parameter information of the CID of the new and old terminal configuration files, if the result is consistent, checking and passing, otherwise, prompting an alarm; and if the matching is consistent and the newly added elements exist, comparing the model configuration version parameter information of the new and old terminal configuration files CID, if the model configuration version parameter value of the new version terminal configuration file CID is higher than the model configuration version parameter value of the old version terminal configuration file CID, the verification is passed, and otherwise, prompting an alarm.
The second check sub-module includes:
the second CRC unit is used for acquiring a new system specification description file SSD, performing CRC on the system specification description file SSD, and terminating the configuration process if the CRC does not pass;
the second version verification unit is used for performing version verification on the newly generated system specification description file SSD, and if the verification fails, the configuration flow is terminated;
the second identification unit is used for analyzing the SSD (solid State disk) of the new and old system specification description files, sequentially comparing the voltage level elements with the information of all devices, connection points and end points under the feeder line elements, and marking the changed elements;
the information checking unit is used for generating a new substation configuration file SCD, sequentially checking whether the comparison result between the topology change information in the substation configuration file SCD and the second identification unit is consistent, if the comparison result is consistent, the verification is passed, if the comparison result is inconsistent, an alarm is prompted, and the configuration process is rechecked;
and the traversing unit is used for traversing the Substation substtation element according to the feeder ID of the SCD to generate a feeder configuration file FCD.
The third check submodule includes:
the third CRC check unit is used for reading a terminal instantiation description file IID of the terminal, performing CRC check on the terminal instantiation description file IID, and terminating the configuration flow if the check fails;
the third identification unit is used for analyzing the terminal instantiation description file IID, searching the currently-operating terminal configuration file CID, respectively extracting data set Dataset elements, DOI elements, DAI elements, private Privitae element information and configuration attribute CF parameter values of the terminal instantiation description file IID and the terminal configuration file CID, comparing the data set Dataset elements, the DOI elements, the DAI elements, the private Privitae element information and the configuration attribute CF parameter values, and identifying newly-added and updated elements;
and the first comparison unit is used for updating the SCD (substation configuration document) to generate a terminal configuration document CID, comparing the terminal configuration document CID with the newly added and updated elements of the identifier, if the comparison result is consistent, the version of the configuration attribute CF is updated, and the historical version of the newly generated terminal configuration document CID is the same as the version of the old terminal configuration document CID, passing the verification, otherwise, prompting the alarm.
The fourth check submodule includes:
the configuration unit is used for analyzing a substation configuration file SCD, reconfiguring communication network element information, updating link overtime parameter information, adding and deleting equipment data set content, modifying control block values, enabling/disabling control blocks, reconfiguring IED element content, modifying action parameter values, updating protection fixed values and remote measurement dead zone values, and generating a new substation configuration file SCD;
the second comparison unit is used for comparing the new and old substation configuration files SCD and checking whether the communication behavior parameter value is updated, if the communication behavior parameter value of the new substation configuration file SCD is higher than that of the old version, and the version information value of the new substation configuration file SCD is equal to that of the old substation configuration file SCD, the verification 1 is passed, otherwise, the verification is not passed, and an alarm is prompted; and comparing the new and old substation configuration files SCD, checking whether the constant value parameter value is updated, if the constant value parameter value of the new substation configuration file SCD is higher than the old constant value parameter value and the version information value of the new substation configuration file SCD is equal to the version information value of the old substation configuration file SCD, passing the verification 2, otherwise, failing to pass the verification, prompting an alarm, and passing the verification if both the verification 1 and the verification 2 pass the verification.
The CRC check includes: and calculating the CRC check code of the configuration file and comparing the CRC check code with the check code carried by the file, wherein if the result is inconsistent, the check is not passed, and if the result is consistent, the check is passed.
The version verification comprises the following steps:
analyzing the configuration file, extracting the content of the History element, comparing whether the attribute information of version and revision are consistent with the version record of the file, if not, checking is not passed, and if so, checking is passed.
The IED element content includes: logical device information LD, logical node information LN, data object information DO, and data attribute information DA.
Example (b):
as shown in fig. 4, the SCD file forward checking process:
the reasons (forward check trigger) for the change of the version of the SCD file include the following 4 classes:
ICD file change: terminal manufacturers upgrade software programs of on-the-spot terminals, add or update terminal functions to cause ICD file changes, and the ICD file changes mainly occur in a model part. The configuration loop is as follows: ICD → SCD, as illustrated by loop 1 in FIG. 2.
Ssd file change: and the distribution line topology is updated due to reasons such as power distribution network reconstruction or operation mode change. The configuration loop is as follows: SSD → SCD, as illustrated by loop 2 in FIG. 2.
IID file change: and updating the version change of the configuration file caused by the terminal configuration information at the site side. Configuring a loop: IID → SCD, as illustrated by loop 3 in FIG. 2.
Scd self-refresh: the distribution automation system administrator modifies the fixed value parameter values, communication parameter values, reconfigures the data set, reports SCD file updates caused by control block trigger parameters, etc. Configuration loop 4: SCD → SCD, as illustrated by loop 4 in FIG. 2.
The above factors can trigger the system configuration flow to cause the SCD file change process, either alone or in combinations, where each combination can be broken down into a superposition of configuration loops 1, 2, 3, 4. The SCD file verification process is decomposed into verification of the above configuration loops.
As shown in fig. 3, CID 'represents the CID file of the latest version reserved by the system before configuration is incomplete, SSD' represents the SSD file of the latest version reserved by the system before configuration is incomplete, and device.
I. Configuring a loop 1 verification process:
1) a system administrator acquires a new ICD file from the database, calculates the CRC check code of the ICD file and compares the CRC check code with the check code of the file, if the result is inconsistent, the check is not passed, and the configuration process is terminated; and if the file version is consistent with the file version, starting file version checking and entering the process 2).
2) And analyzing the ICD file by the system configuration tool to extract the content of the History element, and comparing whether the version and version attribute information is consistent with the ICD version record of the database. If the inconsistency is not consistent, the verification is not passed, and the configuration flow is terminated; if the comparison result is consistent, the process 3) is entered.
3) Analyzing the ICD file, extracting equipment ID and manufacturer information, searching the CID file of the current equipment in transit according to the ID, analyzing the CID file, comparing the contents of IED elements, acquiring the change information of all LD, LN, DO and DA, and identifying modified or newly added elements; and extracting the parameter information of the model configuration version.
4) And (3) the system configuration tool completes the SCD file configuration, generates a new CID file, analyzes the CID file, extracts the IED element content, and acquires all the LD, LN, DO and DA element information to match with the information acquired in the step 3). If the matching results are not consistent, feeding back error information, and checking by manual intervention; if the matching is consistent and no new elements exist, comparing the new CID file model with the old CID file model to configure version parameters, if the result is consistent, checking the version parameters, and otherwise, prompting an alarm; and if the matching is consistent and the newly added elements exist, comparing the model configuration version parameters of the new CID file with the model configuration version parameters of the old CID file, and if the model configuration version parameter values of the new CID file are higher than the model configuration version parameter values of the old CID file, the verification is passed, otherwise, an alarm is prompted.
Configuration loop 2 verification process:
1) the distribution automation system acquires an SSD file from the PMS, calculates a CRC check code of the SSD file and compares the CRC check code with a check code carried by the file, if the result is inconsistent, the check is not passed, and the configuration process is terminated; and if the file version is consistent with the file version, starting file version checking and entering the process 2). It should be noted that, when the PMS system pushes the transaction information, the existing topology map is updated, and if the topology verification passes, the SSD file is directly updated, and the SCD file is automatically generated.
2) And analyzing the SSD file by the system configuration tool to extract the content of the History element, and comparing whether the version and version attribute information is consistent with the SSD version change record or not. If the inconsistency is not consistent, the verification is not passed, and the configuration flow is terminated; if the comparison result is consistent, the process 3) is entered.
3) The configuration tool analyzes the new SSD file and the old SSD file, sequentially compares the VotageLevel element, all equipment under the feeder Circuit element, the connection point connectivityNode and the Terminal information, and marks the changed elements.
4) And the system configuration tool completes the configuration process, generates a new SCD file, sequentially checks whether the topology change information in the SCD file is consistent with the comparison result according to the step 3), passes the check if the topology change information is consistent with the comparison result, prompts an alarm if the topology change information is inconsistent with the comparison result, and rechecks the configuration process.
5) And the SCD version passes the verification, and the FCD file is regenerated by traversing the substtation element according to the feeder line ID.
Configuration loop 3 verification process:
1) the power distribution automation system reads the IID file of the terminal, calculates the CRC check code of the IID file and compares the CRC check code with the check code carried by the file, if the results are inconsistent, the check is not passed, and the configuration process is terminated; and if the file version is consistent with the file version, starting file version checking and entering the process 2).
2) And the configuration tool analyzes the IID file and searches the CID file currently in operation, extracts the data set Dataset element, the DOI element, the DAI element, the private Privitae element information and the configuration attribute CF parameter value, compares the data set Dataset element, the DOI element, the DAI element, the private Privitae element information and the configuration attribute CF parameter value, and identifies the newly added or updated element.
3) The master station updates the SCD file to generate a CID file, compares the newly added and updated elements identified in the step 3) and updates the CF version with the same comparison result, if the version of the newly generated CID file is updated and the historical version is the same as the version of the old CID file, the verification is passed, otherwise, an alarm is prompted, and the verification process is checked.
Configuration loop 4 verification process:
1) the system configuration tool analyzes the SCD file, reconfigures Communication element information of the Communication network, updates the overtime parameter information of the link, adds and deletes the content of the equipment data set, modifies the value of the control block, enables/disables the control block and the like, and generates a new SCD file. And comparing the new SCD file with the old SCD file, checking whether the communication behavior parameter value is updated, judging whether the new SCD communication behavior parameter value is higher than the old SCD communication behavior parameter value, judging whether the version value of the new SCD communication behavior parameter is equal to the version value of the old SCD communication behavior parameter value, if so, checking is passed, and otherwise, prompting an alarm.
2) The system configuration tool analyzes the SCD file, reconfigures the IED element content, modifies the action parameter value, updates the protection constant value, telemeters the dead zone value and the like, and generates a new SCD file. And comparing the new SCD file with the old SCD file, checking whether the fixed value parameter value is updated, judging whether the new SCD fixed value parameter value is higher than the old version fixed value parameter value, judging whether the version value of the new SCD file is equal to the old version value, if so, checking is passed, and otherwise, prompting an alarm.
As shown in fig. 5, the CID file reverse checking process:
the forward checking process is version checking of system configuration triggered by a known reason, and when the system configuration process is completed to generate an SCD file, the system configuration tool sends the SCD to the configuration tool of each terminal to generate a CID file. And reverse checking is required before the terminal is issued. The checking process is as follows:
1) a terminal configuration tool acquires a terminal configuration file CID (device.cid) in the current power distribution terminal through a GetFile service; and (3) calculating a CRC (cyclic redundancy check) code, wherein the CRC code and the device.cid are consistent to enter 2), otherwise, prompting an error, recalling the file and calculating the CRC code, and if the error is continuously made for 3 times, manually performing intervention processing.
2) And the terminal Configuration tool analyzes the CID file and the device.cid file, extracts version, revison, DatamodelSemantic, communication Behavior, Settings and Configuration element information, and performs version tracing.
The information of the CID file revison is consistent with the information of the device.cid file version;
at least one of Configuration version parameter information DatamodelSemantic, communicative behavior, Settings and Configuration of the cid file and the device.cid file is different.
c. And comparing the CID file with the device.cid file, checking whether the structures of the newly added content and the corresponding part of the ICD file are consistent, checking if the structures of the newly added content and the corresponding part of the ICD file are consistent, and otherwise, prompting an alarm. And checking the changed part item by item according to the configuration updating table, finishing checking if all the changed items are checked to be passed, and prompting an alarm if not.
3) And 2) completely passing the checking result, and downloading the configuration file when the CID file passes the checking.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting the scope of protection thereof, and although the present application is described in detail with reference to the above embodiments, those of ordinary skill in the art should understand that: numerous variations, modifications, and equivalents will occur to those skilled in the art upon reading the present application and are within the scope of the claims appended hereto.
Claims (11)
1. A method for checking a configuration file version of a power distribution automation system is characterized by comprising an SCD checking module:
the first verification submodule is used for verifying a configuration loop 1, and the configuration loop 1 is used for verifying the SCD change of the substation configuration file caused by the ICD change of the terminal function description file;
the second checking submodule is used for checking a configuration loop 2, and the checking of the configuration loop 2 is used for checking the SCD change of the substation configuration file caused by the IID change of the terminal instantiation description file;
the third verification submodule is used for verifying a configuration loop 3, and the verification of the configuration loop 3 is used for verifying the SCD change of the substation configuration file caused by the SSD change of the system specification description file;
the fourth verification submodule is used for verifying a configuration loop 4, and the verification of the configuration loop 4 is used for verifying the SCD self-updating of the substation configuration file;
the checking method comprises the following steps:
verifying the file version of the SCD in the process of upgrading the low version to the high version;
performing source tracing and checking on a previous-level historical version of the CID version of the terminal configuration file;
the tracing and checking the previous-stage historical version of the terminal configuration file CID version comprises the following steps:
s2.1: acquiring a terminal configuration file CID of the current power distribution terminal and performing CRC (cyclic redundancy check) on the CID, wherein the step S2.2 is executed when the CID passes the verification, otherwise, judging whether the CID does not pass for 3 times continuously, if so, interrupting the verification, otherwise, prompting an error, and repeating the step S2.1;
s2.2: generating a new terminal configuration file CID, analyzing the new terminal configuration file CID and the old terminal configuration file CID, performing version tracing verification, and downloading the new terminal configuration file CID if the version tracing verification is passed;
the version tracing check comprises the following steps:
s3.1: comparing whether the version information of the new and old terminal configuration files CID is consistent, if so, executing S3.2, otherwise, terminating the configuration flow;
s3.2: comparing the configuration version parameter information of the CID of the new and old terminal configuration files, if at least one of the configuration version parameter information is different, executing S3.3, otherwise, terminating the configuration flow;
s3.3: comparing the CID of the new and old terminal configuration files to obtain new and changed contents, comparing the new contents to check whether the structures of the new and old terminal configuration files are consistent with the structures of the corresponding parts of the ICD of the terminal function description file, checking if the structures are consistent, and otherwise prompting an alarm; and checking the changed contents item by item according to the configuration updating table, finishing verification if all the changed contents pass the checking, and otherwise prompting an alarm.
2. The method of claim 1, wherein the configuration version parameter information comprises: the semantic data model DatamodelSemantic, communication behavior information communicative behavior, device information Settings, and Configuration information Configuration.
3. The method for checking the version of the configuration file according to claim 1, wherein the checking the version of the file in the process of upgrading the SCD low version of the substation configuration file to the SCD high version comprises: any one or more of configuration loop 1 verification, configuration loop 2 verification, configuration loop 3 verification and configuration loop 4 verification.
4. The method of claim 3, wherein the configuration loop 1 checking for changes to the substation configuration file SCD caused by changes to the terminal function description file ICD comprises:
s6.1: acquiring a new terminal function description file ICD, performing CRC on the ICD, terminating the configuration process if the CRC does not pass, and executing S6.2 if the CRC passes;
s6.2: performing version verification on the terminal function description file ICD, if the version verification fails, terminating the configuration process, and if the version verification passes, executing S6.3;
s6.3: analyzing a terminal function description file ICD, extracting equipment ID and manufacturer information, searching a terminal configuration file CID of the current operating equipment according to the ID, analyzing the terminal configuration file CID, comparing the IED element contents of the terminal function description file ICD and the terminal configuration file CID, acquiring change information of the IED element contents, identifying modified and newly added elements, and extracting model configuration version parameter information;
s6.4: completing the configuration of a substation configuration file SCD, generating a new terminal configuration file CID, analyzing the new terminal configuration file CID, extracting IED element content of the new terminal configuration file CID, matching with change information of the IED element content acquired by S6.3, feeding back error information if the matching result is inconsistent, and interrupting verification; if the matching is consistent and no new elements exist, comparing the model configuration version parameter information of the CID of the new and old terminal configuration files, if the result is consistent, checking and passing, otherwise, prompting an alarm; and if the matching is consistent and the newly added elements exist, comparing the model configuration version parameter information of the new and old terminal configuration files CID, if the model configuration version parameter value of the new version terminal configuration file CID is higher than the model configuration version parameter value of the old version terminal configuration file CID, the verification is passed, and otherwise, prompting an alarm.
5. The method for checking the version of the configuration file according to claim 3, wherein the checking of the configuration loop 2 for checking the change of the SCD of the substation configuration file caused by the change of the IID of the terminal instantiation description file comprises:
s7.1: reading a terminal instantiation description file IID of a terminal, performing CRC (cyclic redundancy check) on the terminal instantiation description file IID, and terminating a configuration process if the terminal instantiation description file IID does not pass the CRC; if the verification is passed, executing S7.2;
s7.2: analyzing the terminal instantiation description file IID, searching the currently-operating terminal configuration file CID, respectively extracting data set Dataset elements, DOI elements, DAI elements, private Privitae element information and configuration attribute CF parameter values of the terminal instantiation description file IID and the terminal configuration file CID, comparing, and identifying newly-added and updated elements;
s7.3: and updating the SCD of the substation configuration file, generating a terminal configuration file CID, comparing the terminal configuration file CID with the newly added and updated elements identified by the S7.2, if the comparison result is consistent, the version of the configuration attribute CF is updated, and the historical version of the newly generated terminal configuration file CID is the same as the version of the old terminal configuration file CID, passing the verification, otherwise, prompting an alarm and checking the verification process.
6. The method for checking the version of the configuration file according to claim 3, wherein the checking, by the configuration loop 3, the change of the substation configuration file SCD caused by the change of the SSD in the system specification description file comprises:
s8.1: acquiring a new system specification description file SSD, performing CRC (cyclic redundancy check) on the system specification description file SSD, terminating a configuration process if the CRC does not pass, and executing S8.2 if the CRC passes;
s8.2: performing version verification on the newly generated system specification description file SSD, if the verification fails, terminating the configuration flow, and if the verification passes, executing S8.3;
s8.3: analyzing an SSD (solid State disk) of a new system specification description file and an SSD of an old system specification description file, sequentially comparing information of a voltage level element, all equipment, a connection point and an end point under a feeder line element, and marking changed elements;
s8.4: generating a new substation configuration file SCD, sequentially checking whether the comparison result between topology change information in the substation configuration file SCD and S8.3 is consistent, if so, checking, executing S8.5, and if not, prompting an alarm and re-checking the configuration process;
s8.5: and traversing the Substation substtation element according to the feeder ID of the SCD to generate a feeder configuration file FCD.
7. The configuration file version checking method according to claim 3, wherein the checking by the configuration loop 4 for the substation configuration file SCD self-update comprises:
analyzing a substation configuration file SCD, reconfiguring communication network element information, updating link overtime parameter information, adding and deleting equipment data set content, modifying a control block value, enabling/disabling a control block, reconfiguring IED element content, modifying an action parameter value, updating a protection fixed value and a remote measurement dead zone value, generating a new substation configuration file SCD, comparing the new and old substation configuration files SCD, checking whether the communication behavior parameter value is updated, if the communication behavior parameter value of the new substation configuration file SCD is higher than that of the old version, and the version information value of the new substation configuration file SCD is equal to that of the old substation configuration file SCD, passing verification 1, otherwise failing verification, and prompting an alarm; comparing the new and old substation configuration files SCD, checking whether the constant value parameter value is updated, if the constant value parameter value of the new substation configuration file SCD is higher than the old constant value parameter value and the version information value of the new substation configuration file SCD is equal to the version information value of the old substation configuration file SCD, passing the verification 2, otherwise, failing to pass the verification, and prompting an alarm; if both checks 1 and 2 pass, then configuration loop 4 passes the check.
8. The method of any of claims 1, 4, 5, and 6, wherein the CRC check comprises: and calculating the CRC check code of the configuration file and comparing the CRC check code with the check code carried by the configuration file, wherein if the result is inconsistent, the check is not passed, and if the result is consistent, the check is passed.
9. The method of any of claims 4 or 6, wherein the version checking comprises:
analyzing the configuration file, extracting the content of the History element, comparing whether the version and revision version attribute information is consistent with the version record of the file, if not, checking is not passed, and if so, checking is passed.
10. The profile version checking method according to claim 4 or 7, wherein the IED element content comprises: logical device information LD, logical node information LN, data object information DO, and data attribute information DA.
11. A system for checking a distribution automation system configuration file version, comprising:
SCD check module: verifying the file version of the SCD in the process of upgrading the low version to the high version;
a CID checking module: performing source tracing and checking on a previous-level historical version of the CID version of the terminal configuration file;
the CID checking module comprises:
a CRC check submodule: acquiring a terminal configuration file CID of the current power distribution terminal, performing CRC (cyclic redundancy check) on the CID, judging whether the CRC continuously makes mistakes for 3 times, if so, interrupting the CRC, otherwise, prompting an alarm and performing CRC again;
and a version tracing check submodule: generating a new terminal configuration file CID, analyzing the new terminal configuration file CID and the old terminal configuration file CID, performing version tracing verification, and downloading the new configuration file if the version tracing verification is passed;
the SCD check module comprises:
the first verification submodule is used for verifying a configuration loop 1, and the configuration loop 1 is used for verifying the SCD change of the substation configuration file caused by the ICD change of the terminal function description file;
the second checking submodule is used for checking a configuration loop 2, and the checking of the configuration loop 2 is used for checking the SCD change of the substation configuration file caused by the IID change of the terminal instantiation description file;
the third verification submodule is used for verifying a configuration loop 3, and the verification of the configuration loop 3 is used for verifying the SCD change of the substation configuration file caused by the SSD change of the system specification description file;
and the fourth checking submodule is used for checking a configuration loop 4, and the checking of the configuration loop 4 is used for checking the SCD self-updating of the substation configuration file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710968831.1A CN109683923B (en) | 2017-10-18 | 2017-10-18 | Method and system for checking configuration file version of power distribution automation system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710968831.1A CN109683923B (en) | 2017-10-18 | 2017-10-18 | Method and system for checking configuration file version of power distribution automation system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109683923A CN109683923A (en) | 2019-04-26 |
| CN109683923B true CN109683923B (en) | 2021-12-03 |
Family
ID=66183395
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710968831.1A Active CN109683923B (en) | 2017-10-18 | 2017-10-18 | Method and system for checking configuration file version of power distribution automation system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109683923B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112181519A (en) * | 2020-09-25 | 2021-01-05 | 中国建设银行股份有限公司 | Data processing method, device, equipment and storage medium |
| CN112287648A (en) * | 2020-10-27 | 2021-01-29 | 国电南瑞科技股份有限公司 | SCD-based substation monitoring system data point table generation and synchronization method |
| CN112711319B (en) * | 2020-12-29 | 2024-02-27 | 杭州迪普科技股份有限公司 | Digital power supply control method and device, electronic equipment and storage medium |
| CN115150431A (en) * | 2022-06-22 | 2022-10-04 | 重庆长安汽车股份有限公司 | Finished vehicle MCU remote debugging system, method and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105138752A (en) * | 2015-08-13 | 2015-12-09 | 国网安徽省电力公司 | Differentiation comparison and display method for SCD documents in intelligent substation with historical retrospect function |
| CN105184189A (en) * | 2015-08-26 | 2015-12-23 | 国家电网公司 | Online control and management system for intelligent substation SCD file |
| CN105930170A (en) * | 2016-05-12 | 2016-09-07 | 国网辽宁省电力有限公司鞍山供电公司 | SCD file semantic version management method based on comparison analysis results |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9886292B2 (en) * | 2015-10-26 | 2018-02-06 | Dell Products L.P. | Making user profile data portable across platforms |
-
2017
- 2017-10-18 CN CN201710968831.1A patent/CN109683923B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105138752A (en) * | 2015-08-13 | 2015-12-09 | 国网安徽省电力公司 | Differentiation comparison and display method for SCD documents in intelligent substation with historical retrospect function |
| CN105184189A (en) * | 2015-08-26 | 2015-12-23 | 国家电网公司 | Online control and management system for intelligent substation SCD file |
| CN105930170A (en) * | 2016-05-12 | 2016-09-07 | 国网辽宁省电力有限公司鞍山供电公司 | SCD file semantic version management method based on comparison analysis results |
Non-Patent Citations (1)
| Title |
|---|
| "湖北电网智能变电站SCD文件管控系统设计";文博，吴迪等;《湖北电力》;20170731(第7期);第45-52页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109683923A (en) | 2019-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109683923B (en) | Method and system for checking configuration file version of power distribution automation system | |
| CN106951694B (en) | Adaptive modeling method for online monitoring system of secondary equipment of power system | |
| CN101888655B (en) | Method and device for configuring network element data in template way in network management system | |
| CN105740140A (en) | Software system failure diagnosis method, server and system | |
| CN107193917B (en) | IID-based total station system configuration file lossless data updating method | |
| CN107394892B (en) | Method and system for determining debugging range of interval change of intelligent substation | |
| CN109446155B (en) | Intelligent station description file import and export configuration method and system | |
| CN112287648A (en) | SCD-based substation monitoring system data point table generation and synchronization method | |
| CN104993589A (en) | Model sharing method between power distribution main station and terminal | |
| CN102609520A (en) | Method for exporting model data of substation by filtering | |
| CN105488293B (en) | A kind of method and system configuring virtual terminator line in SCD | |
| US10776313B2 (en) | Converting source objects to target objects | |
| CN107247827B (en) | Virtual terminal model modeling and automatic wiring method based on machine learning | |
| CN109636664A (en) | A kind of distribution system, distribution main website and its point table model update method | |
| US20220277119A1 (en) | A System and Method for Generating a Holistic Digital Twin | |
| CN117272974A (en) | Verification method and device for SCL (substation configuration file) of intelligent substation and related equipment | |
| CN115510842A (en) | Transformer substation model full-data verification method based on new-generation secondary system | |
| CN109271350A (en) | A kind of database and information point table automatic comparison and synchronous method based on telemechanical communication | |
| CN116186192A (en) | SCD file verification method and device based on standard virtual terminal loop expert database | |
| CN113553728A (en) | Method and system for generating intelligent substation station control layer application system model | |
| CN109684879B (en) | Universal monitoring method and system for domestic software and hardware equipment | |
| CN109710809B (en) | Automatic SCD file virtual terminal connection method based on expert database | |
| WO2015184750A1 (en) | Data maintenance method and device of network element device | |
| CN105354144A (en) | Method and system for automatically testing consistency of business support system information models | |
| CN109858050B (en) | Data model generation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |