CN117272974A

CN117272974A - Verification method and device for SCL (substation configuration file) of intelligent substation and related equipment

Info

Publication number: CN117272974A
Application number: CN202311130080.8A
Authority: CN
Inventors: 王珠峰; 陈培训; 孔凡坊; 屠德然; 陈庆会; 吴旭鹏; 王瑞; 邓潘; 钟薇薇; 郑小城; 阮声然; 曹坤; 詹武; 姜友棋; 王大进
Original assignee: Wenzhou Power Supply Co of State Grid Zhejiang Electric Power Co Ltd; Power Construction of Wenzhou
Current assignee: Wenzhou Power Supply Co of State Grid Zhejiang Electric Power Co Ltd; Power Construction of Wenzhou
Priority date: 2023-09-04
Filing date: 2023-09-04
Publication date: 2023-12-22

Abstract

The invention is applicable to the technical field of intelligent substation equipment, and relates to a verification method, a device and related equipment of an intelligent substation SCL file, wherein the method comprises the following steps: acquiring SCL files of terminals of all suppliers in the intelligent substation; performing multi-object integrity verification on the SCL file of each provider terminal to obtain a verification result corresponding to each verification object; based on a plurality of verification results of multi-object integrity verification on the SCL file of each supplier terminal, determining whether the SCL file of the supplier terminal meets a preset verification standard. The SCL file of each supplier terminal in the intelligent substation is subjected to multi-object integrity verification based on the expansion characteristic of the SCL verification algorithm, so that the integrity verification of the SCL file is realized, and the interoperability of the multi-supplier terminal in the substation is ensured.

Description

Verification method and device for SCL (substation configuration file) of intelligent substation and related equipment

Technical Field

The invention is suitable for the technical field of intelligent substation equipment, and particularly relates to a verification method and device for an intelligent substation SCL file and related equipment.

Background

Along with the construction of a national strong intelligent power grid, the requirements of a transformer substation on the intellectualization, the information digitization, the standardization and the application interactivity of the total station equipment are higher and higher, and basic functions of total station information acquisition, measurement, control, protection, monitoring and the like are automatically completed according to terminal IEDs (intelligent electronic devices) of all suppliers through an SA (substation automation) system, so that the automation of equipment operation is realized, and the production management efficiency is improved. The success of SA systems depends on the effective interoperability of the provider end IEDs within the substation, and to achieve this goal, it must be ensured that the SCL (substation configuration description language) profile of each provider end IED complies with the IEC61850 standard.

The SCL configuration file is used for exchanging configuration data among configuration tools of the provider terminals, describes input/output data, communication connection and intelligent substation configuration conditions of the IED, and enables the IED to be automatically and accurately configured in the engineering construction process. In some existing technologies, a learner develops functional analysis and structural design of an SCL configuration tool based on a syntax structure and a hierarchical object model of the SCL, and achieves all functions of IED configuration. But can lead to frequent SCL file changes on substation IEDs replacement or upgrade. A learner also puts forward a method for describing a language description model of the substation configuration in IEC61850, compares the differences of SCL configuration files of the substation, discusses the use rule of the SCL configuration files of the substation in actual substation engineering, but does not analyze SCL configuration file verification, namely does not realize integrity verification of the SCL configuration files, and cannot guarantee interoperability of multi-provider terminal equipment in the substation.

Disclosure of Invention

Aiming at the problem that in the prior art, integrity verification is not realized when SCL configuration files of a transformer substation are verified, and interoperability of multi-supplier terminal equipment in the transformer substation is low, the invention provides a method, a device and related equipment for verifying SCL files of the intelligent transformer substation.

In a first aspect, the embodiment of the present invention provides a technical solution that: a verification method of an intelligent substation SCL file comprises the following steps:

acquiring SCL files of terminals of all suppliers in the intelligent substation;

performing multi-object integrity verification on the SCL file of each provider terminal to obtain a verification result corresponding to each verification object; based on a plurality of verification results of multi-object integrity verification on the SCL file of each supplier terminal, determining whether the SCL file of the supplier terminal meets a preset verification standard.

Further, the multi-object integrity verification includes performing a pattern verification on the SCL file of the provider terminal, and the step of performing a pattern verification on the SCL file of the provider terminal includes:

Performing attribute verification, element verification and constraint verification on the SCL file of the provider terminal according to SCL mode preset rules by a framework checking engine;

judging whether the SCL file has a mode verification error according to the verification results of the attribute verification, the element verification and the constraint verification, wherein each element comprises a unique attribute;

if the pattern verification error exists, generating a verification error guide comprising unique attributes of the element;

acquiring element correction data obtained after correction according to the verification error guide, and verifying again through the architecture inspection engine according to the element correction data;

if the mode verification error does not exist, judging that the mode verification of the SCL file of the supplier terminal passes.

Further, the multi-object integrity verification further includes performing information model verification on the SCL file of the provider terminal, and the step of performing information model verification on the SCL file of the provider terminal includes:

extracting a provider terminal definition object from the SCL file of the provider terminal through a UML data model;

generating information verification rules according to MICS files, and constructing a provider terminal definition rule database according to the information verification rules according to the UML data model;

Constructing a target rule database according to the extracted provider terminal definition object and the SCL file of the provider terminal; performing information model verification on the provider terminal definition rule database and the target rule database through an SCL verification engine;

judging whether the information model verification has errors according to the information model verification result;

if the information model verification errors exist, acquiring information model correction data, and re-verifying based on the information model correction data;

if the information model verification has no error, judging that the information model verification passes.

Further, the multi-object integrity verification further includes an IET consistency verification on the SCL file of the provider terminal, and the step of IET consistency verification on the SCL file of the provider terminal includes:

converting an original IED file through an XML converter, wherein the IED file comprises object information of an SCL file, and the object information comprises substation site information;

inputting the converted IED file and the SCL file into a grammar consistency engine for verification, and judging whether the converted IED file is consistent with the SCL file or not;

If the syntax of the converted IED file is inconsistent with that of the SCL file, IET consistency correction data generated based on the data with inconsistent syntax is obtained for re-syntax consistency verification;

and if the syntax of the converted IED file is consistent with that of the SCL file, converting the SCL file through an XLSX converter, and outputting an IET file with the syntax consistent with that of the SCL file.

Further, the multi-object integrity verification further includes performing CSV consistency verification on the SCL file of the provider terminal, and the step of performing CSV consistency verification on the SCL file of the provider terminal includes:

reading a CSV file from an online IED file;

inputting the CSV file and the SCL file into a CSV consistency verification engine for verification, and judging whether the information in the CSV file and the information in the SCL file are consistent according to a CSV consistency verification result;

if the information in the CSV file is inconsistent with the information in the SCL file, acquiring CSV consistency correction data generated according to the CSV consistency verification result, and re-verifying according to the CSV consistency correction data;

and if the CSV file is consistent with the information in the SCL file, judging that the CSV consistency verification of the CSV file and the SCL file is passed.

Further, the multi-object integrity verification further includes UCA-IUG program verification on the SCL file of the provider terminal, and the step of UCA-IUG program verification on the SCL file of the provider terminal includes: selecting a test case, and constructing a mapping relation between the test case and a rule database, wherein the rule database is constructed based on an SCL mode model and an SCL data model;

inputting the SCL file and the rule database into a master verification engine, verifying the UCA-IUG program of the SCL file by the master verification engine, and judging whether the UCA-IUG program has errors according to the UCA-IUG program verification result;

if the UCA-IUG program has errors, acquiring the UCA-IUG program correction data for re-verification;

if the UCA-IUG program has no error, the UCA-IUG program is judged to pass verification.

Further, the multi-object integrity verification further includes performing a user-defined rule verification on the SCL file of the provider terminal, and the step of performing a user-defined rule verification on the SCL file of the provider terminal includes:

determining a verification rule database according to an IEC61850 standard architecture and a UML data model;

Determining a user rule according to a model test realization consistency statement source;

user rule verification is carried out on the user rule according to the verification rule database, and whether the user rule is consistent with the standard in the verification rule database is judged;

if the rules are inconsistent, revising and re-verifying the verification rule database and the user rules according to the data with inconsistent rules;

if the SCL files are consistent with the verification rule database, inputting the SCL files of different types and the verification rule database into an SCL verification engine for verification, wherein the types of the SCL files comprise an ICD file, a CID file and an IID file;

judging whether SCL files of all types meet all rules of the verification rule database according to verification results corresponding to files of different types;

if not, acquiring rule definition correction data of the SCL file, and re-verifying according to the rule definition correction data by the SCL verification engine;

and if so, judging that the SCL file meets the user-defined rule.

In a second aspect, the embodiment of the present invention further provides a technical solution: an intelligent substation SCL file verifying device, the device includes:

The data acquisition module is used for acquiring SCL files of all the supplier terminals in the intelligent substation;

the data verification module is used for performing multi-object integrity verification on the SCL file of each provider terminal to obtain a verification result corresponding to each verification object;

and the result judging module is used for determining whether the SCL file of each supplier terminal accords with a preset verification standard or not based on a plurality of verification results of multi-object integrity verification on the SCL file of each supplier terminal.

In a third aspect, the embodiment of the present invention further provides a technical solution: a computer device, comprising: the method for verifying the intelligent substation SCL file according to any one of the above embodiments comprises a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps in the method for verifying the intelligent substation SCL file are implemented when the processor executes the computer program.

In a fourth aspect, the embodiment of the present invention further provides a technical solution: a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps in the method of verifying an intelligent substation SCL file according to any of the above embodiments.

The SCL file verification method for the intelligent substation has the beneficial effects that multi-object integrity verification is carried out on SCL files of all supplier terminals in the intelligent substation by means of the expansion characteristic of an SCL verification algorithm, the integrity verification of the SCL files is achieved, and therefore interoperability of multiple supplier terminals in the substation is guaranteed.

The foregoing summary is merely an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more fully understood, and in order that the same or additional objects, features and advantages of the present invention may be more fully understood.

Drawings

Other features, objects and advantages of the present invention will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures.

Fig. 1 is a step flowchart of a verification method of an intelligent substation SCL file provided by an embodiment of the present invention;

Fig. 2 is a schematic diagram of an SCL architecture in an intelligent substation according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a standard engineering flow using SCL files according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of the functional model and the information model of peer to peer TC provided by an embodiment of the present invention;

fig. 5 is a flowchart of an SCL file verification algorithm according to an embodiment of the present invention;

FIG. 6 is a flow chart of pattern verification provided by an embodiment of the present invention;

FIG. 7 is a flow chart of information model verification provided by an embodiment of the present invention;

FIG. 8 is a flow chart of IET consistency verification provided by an embodiment of the invention;

FIG. 9 is a schematic diagram of an online IED extracted CSV file provided by an embodiment of the invention;

FIG. 10 is a flow chart of CSV consistency verification provided by an embodiment of the invention;

FIG. 11 is a flowchart of UCA-IUG program verification provided by an embodiment of the present invention;

FIG. 12 is a flow chart of user-defined rule validation provided by an embodiment of the present invention;

fig. 13 is a schematic structural diagram of a verification device for an intelligent substation SCL file according to an embodiment of the present invention;

fig. 14 is a schematic structural diagram of a computer device according to an embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings and examples, it being understood that the detailed description herein is merely a preferred embodiment of the present invention, which is intended to illustrate the present invention, and not to limit the scope of the invention, as all other embodiments obtained by those skilled in the art without making any inventive effort fall within the scope of the present invention.

Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts operations (or steps) as a sequential process, many of the operations (or steps) can be performed in parallel, concurrently, or at the same time. Furthermore, the order of the operations may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures; the processes may correspond to methods, functions, procedures, subroutines, and the like.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. It should also be understood that, in various embodiments of the present invention, the sequence number of each process does not mean the order of execution, and the order of execution of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

It should be understood that in the present invention, "plurality" means two or more. "and/or" is merely a variable relationship describing an associated object, meaning that there may be three relationships, e.g., and/or B, may represent: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. "comprising A, B and C", "comprising A, B, C" means that all three of A, B, C comprise, "comprising A, B or C" means that one of the three comprises A, B, C, and "comprising A, B and/or C" means that any 1 or any 2 or 3 of the three comprises A, B, C.

It should be understood that in the present invention, "B corresponding to a", "a corresponding to B", or "B corresponding to a" means that B is associated with a, from which B can be determined. Determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information. The matching of A and B is that the similarity of A and B is larger than or equal to a preset threshold value.

Example 1

Referring to fig. 1, fig. 1 is a flowchart illustrating steps of a method for verifying an SCL file of an intelligent substation according to an embodiment of the present invention. A verification method of an intelligent substation SCL file comprises the following steps:

S1, acquiring SCL files of terminals of all suppliers in an intelligent substation;

s2, performing multi-object integrity verification on the SCL file of each provider terminal to obtain a verification result corresponding to each verification object;

s3, based on a plurality of verification results of multi-object integrity verification on the SCL file of each supplier terminal, determining whether the SCL file of the supplier terminal meets a preset verification standard.

Referring to fig. 2, this embodiment specifically describes an SCL architecture in an intelligent substation. The SCL object model consists of three basic parts: substation model, IED model, and communication model. The substation model is used to describe switchyard installations and connections on a single-wire level. The substation model is an object hierarchy structure containing elements/sub-elements of a substation, voltage levels, intervals, devices and sub-devices. The IED model is also a hierarchical model describing the configuration of the IED, and is capable of specifying services that the IED can provide and access to a list of access points for information models in the IED, which are typically composed of servers, LD (logical devices), LN (logical nodes), DO (data objects) and DA (data attributes). Wherein the server is an object of the IED, representing the externally visible behaviour of the device and specifying a communication model for access to the communication system, the LD comprised in the server of the IED is composed of information generated by a set of domain-specific application LNs, each LN containing mandatory, conditional or optional DO of the respective DA. A plurality of LNs may constitute one LD, and a plurality of LDs may constitute one server, representing communication visible behavior of the IED. In addition, a special model like data set is used to represent ordered DO and DA sets, allowing efficient access to the hierarchical information model. Because the IED model is aware of which data is accessible through a certain AP (access point) of the IED, the communication model only describes the logical connection between the IED and the IED AP through the virtual network.

As shown in connection with fig. 2, the interval E1Q1 of the substation model includes a circuit breaker CB1, an electronic current transformer ECT1, an electronic voltage transformer EVT1, and a transmission line L1. In the IED model section, the pins (protection IEDs) include two APs (ap_pin_1 and ap_pin_2) for the process bus and the station bus, from which ap_pin_2 a hierarchical information model containing servers, LD, LN, DO, DA, etc. can be accessed. The communication model leads out a subnet through an incoming line bus and comprises four IEDs: ap_pied_2, ap_cied_2 (control IED), ap_bied_2 (breaker IED), and ap_mu_2 (merging unit), respectively. Ap_pin_2 contains address parameters, physical connections and a GSE (generic substation event) control block with address. In order to support data exchange between various configuration tools from different provider terminals, the IEC61850 authentication standard specifies SCL files of various types, respectively: CID (IED description of configuration), ICD (IED capability description), SSD (substation specification description), SCD (substation configuration description), IID (instantiated IED description) and SED (system exchange description) are used to handle IED modification and configuration data exchange after configuration between different projects, respectively.

Referring to fig. 3, fig. 3 is a schematic diagram of a standard engineering flow using SCL files. When the SCL file of each supplier terminal in the intelligent substation is obtained, first, the SSD file including the substation single line diagram and the required LN is derived from the system specification tool of each supplier terminal in the substation, and the ICD file describing the IED function is derived from the IED configuration tool dedicated to the supplier terminal. And then an SSD file and an ICD file are imported through a system configuration tool to create an SCD file, wherein the SCD file comprises all IED descriptions, a communication configuration part and a substation description part. And then importing corresponding SCD files into an IED configuration tool special for each provider terminal, and extracting information required by the IED for creating the CID file. Finally, the IED configuration is automatically completed by using a CID file, the CID file represents the requirements of substation automation on the IED, and the IED can be correctly and even automatically configured through a standard SCL file and an engineering flow.

More specifically, in the present application, the preset verification standard is an IEC61850 verification standard, where the IEC61850 verification standard is a public communication standard, and by a series of standardization of the device, the communication unification of the whole station is achieved. For verification, an IEC61850 communication network information model in an IEC61850 verification standard can be combined, and an integrated data model configuration of the multi-provider terminal IED can be built through mapping with a management database. The IEC61850 communication network information model may represent data that needs to be exchanged with other IEDs for communication purposes, and may be obtained based on an IEC61850 authentication standard through a MIB (management information base) mapping method. If the MIB object is a basic object for monitoring and notification, it can be represented by DO in an IEC61850 communication network information model; if the MIB object is a table consisting of a plurality of entries containing several basic objects, it can be represented by one LN class, and each entry in the table should be represented by a corresponding LN instance, a set of basic objects in the MIB will be modeled as one dataset.

The MIB is a virtual database containing a set of network objects that can be managed using a simple network management protocol. The MIB hierarchy can be conceptually organized as a tree structure with nodes of the tree representing different subdivisions of organization or function and leaves of the tree representing managed objects. The system group lists information such as the name and location of the monitored computer, and since nodes or leaves at the same level are numbered in sequence from left to right, each management object has a unique reference that indicates its path from the root node. In addition to these basic MIB subtrees, MIB extensions can be created and registered for different network protocols, in which managed objects are of four types: object type, notification type, object group, and sequence. An object type or notification type is a basic data type that defines a single object instance, while an object group is a complex data type that defines an ordered single object group, with a sequence specifying a table object that contains multiple related object instances. Specifically, in connection with fig. 4, an information model of peer TC (transparent clock) is described as an example. In a peer-to-peer TC system, when messages are separated, the master clock periodically sends a synchronization message containing the current time of the master clock, and then needs to calculate the total delay through the path to the slave clock, including the residence time in the switch, and the total time delay consists of 3 parts: 1. link delay between the master clock and the peer TC; 2. residence time in peer TC; 3. the link delay between the peer TC and the slave clock. Where two link delays may be measured by exchanging pdelay_req and pdelay_resp messages, which are performed by ports of the peer TCs, residence times may be measured by the peer TCs themselves, and respective DO and data sets obtained by MIB object mapping. The different mapping modes for the managed object types in the MIB are as follows:

1. MIB object type mapping: the object describes the clock identification of the local clock and is a generic mandatory attribute for all clocks. The object TwoStepFlag indicates whether the peer TC is a two-step clock, sends a follow_up message to inform the residence time of the synchronization message, and sends a pdelay_resp_follow_up message to inform the issuance time of the pdelay_resp message, as shown by the dotted line in fig. 4. 2. MIB notification type mapping: the object represents an event whether PTP (precision time protocol) service is stopped. Since the data type of the object is a boolean type and is a piece of status information, the object should be modeled in the IEC61850 information model as a DO called PTP service termination. 3. Object group mapping: the object group is modeled as 2 different data sets, namely a data set and alarm information in the IEC61850 information model.

More specifically, in order to maintain IEC 61850-based compatibility between multi-provider terminal devices, the SCL file of the above-described provider terminal details information of server objects, event reports, device settings, addresses, etc. In this embodiment, SCL verification includes using user interface tools to verify the syntax and semantics of all substation elements, communication network interconnections, and related data models specified in the SCL. The verification process is typically implemented at a construction stage prior to commissioning of the substation automation system, and in order to ensure complete plug and play interoperability, the verification can be repeated when new IEDs are added to the SCD file at any subsequent stage, helping to support and maintain consistency between devices in the substation automation system. The data model supported by SCL file needs to conform to the logic node classification of IEC61850-7-4 and the public data classification of IEC61850-7-3 respectively, and strictly adhere to the grammar rule of XML, and pass verification without any error.

More specifically, in the present embodiment, performing multi-object integrity verification may include performing pattern verification, information model verification, IET (IED engineering table) consistency verification, CSV (online comma separated value) consistency verification, UCA-IUG (utility communication architecture-international user group) program verification, user-defined rule verification on SCL files of respective provider terminals. The overall flow of the SCL file verification algorithm is shown in connection with FIG. 5, wherein IEC61850 verification criteria for pattern verification, information model verification, UCA-IUG program verification, and user-defined rule verification may be embodied in database rules, which are separately verified with the CSL file input SCL verification engine. The processes of mode verification, information model verification, UCA-IUG program verification and user-defined rule verification can be realized on line, when errors are judged to exist according to verification results of files of different types, the errors are fed back to one end of a tester in time, the tester corrects the errors according to the verification results, and then the corrected data are returned to an SCL verification engine for verification again until the verification results show that the errors do not exist. When the verification has errors, the verification result may include data having errors. The verification of the IET consistency verification and the CSV consistency verification can be performed on line, and the IET consistency verification judgment can be realized by inputting the IET file and the SCL file into a consistency check engine. Also, CSV consistency verification may be achieved by entering the CSV file and SCL file into a consistency check engine.

In the embodiment of the invention, multi-object integrity verification is carried out on SCL files of all supplier terminals in the intelligent substation by means of the expansion characteristic of SCL verification algorithm, including pattern verification, information model verification, IET consistency verification, CSV consistency verification, UCA-IUG program verification and user definition rule verification are carried out on the SCL files, so that the integrity verification of the SCL files is realized, and the interoperability of the multi-supplier terminals in the substation is ensured; and the SCL verification algorithm automatically checks and verifies from the two aspects of IET consistency check and user-defined rule, so that the utility tool can be ensured to have stronger adaptability.

Preferably, in the step S2, the multi-object integrity verification includes performing a pattern verification on the SCL file of the provider terminal, and the multi-object integrity verification includes performing a pattern verification on the SCL file of the provider terminal, including:

s201, performing attribute verification, element verification and constraint verification on the SCL file of the provider terminal according to a preset rule of an SCL mode through a framework checking engine;

s202, judging whether the SCL file has a mode verification error according to the verification results of the attribute verification, the element verification and the constraint verification, wherein each element comprises a unique attribute;

S203, if a mode verification error exists, generating a verification error guide comprising unique attributes of the elements;

s204, acquiring element correction data obtained after correction according to the verification error guide, and verifying again through the architecture inspection engine according to the element correction data;

s205, if no mode verification error exists, judging that the mode verification of the SCL file of the supplier terminal is passed.

Specifically, the pattern verification refers to SCL pattern verification. The format of the SCL file should conform to the XML syntax rules and the valid SCL file should conform to the rules defined by the SCL schema. The SCL pattern is used to check the integrity of data, data structure and data correctness. Wherein data integrity means that the pattern verification process checks to ensure that all information required for the SCL pattern appears in the SCL file being tested; the data structure includes elements and attributes of the SCL file checked to ensure compliance with the SCL pattern; data correctness refers to checking an SCL file to ensure that the data matches the rules given in SCL pattern.

Referring to fig. 6, pattern verification first determines a pattern function based on a basic type of SCL, a communication model of SCL, an SCL data type template, etc.; determining an object needing to verify the SCL file based on the mode function, wherein the object comprises attribute verification, element verification and constraint verification; and then inputting the SCL file into a framework checking engine for attribute verification, element verification and constraint verification, and outputting verification results of the attribute verification, the element verification and the constraint verification. And judging whether the attribute, the element and the constraint of the SCL have errors according to the verification result. In the verification process, attribute verification, element verification and constraint verification may be performed sequentially, for example: and sequentially performing attribute verification, element verification and constraint verification. Of course, the attribute, the element and the constraint of the SCL file can be separated respectively, and the attribute, the element and the constraint are verified synchronously, so that the verification speed is higher.

Wherein the attribute verification comprises parsing all attributes of the elements in the SCL file, including information about the elements, and may occur 0 to 1 times in a given element in the SCL file. The above elements are basic building blocks of all XML-based files (SCLs containing data), each element contains a unique attribute, which is a tag that appears in the XML file, by means of which it is easy for the tester to quickly identify errors and to debug accordingly.

More specifically, in the case where there is a verification error, a verification error guide corresponding to the error source may be generated, and the verification error guide includes the unique attribute of the error element. Through the unique attribute, a tester can quickly and better acquire the error element for correction and debugging. The verification error guide can be used as a unique characteristic of an SCL verification algorithm, and error messages can be mapped to error rows in an actual SCL file through unique attributes, so that quick error identification and direct debugging of the SCL file are facilitated.

Preferably, in the step S2, the multi-object integrity verification further includes a step of performing information model verification on the SCL file of the provider terminal, and a step of performing information model verification on the SCL file of the provider terminal, including:

S206, extracting a provider terminal definition object from the SCL file of the provider terminal through a UML data model; generating information verification rules according to MICS files, and constructing a provider terminal definition rule database according to the information verification rules according to the UML data model;

s207, constructing a target rule database according to the extracted provider terminal definition object and the SCL file of the provider terminal;

s208, performing information model verification on the provider terminal definition rule database and the target rule database through an SCL verification engine;

s209, judging whether the information model verification has errors according to the information model verification result;

s210, if an information model verification error exists, acquiring information model correction data, and re-verifying based on the information model correction data;

s211, if the information model verification has no error, judging that the information model verification passes.

Specifically, as shown in fig. 7, in the present embodiment, standard data model verification is performed using the UML model. The UML model focuses on the description of abstract syntax/semantics by way of meta-model definition, and also incorporates the necessary semantic definitions to allow extensive model interchangeability between various tools, with built-in extensibility features, so that various individual items can extend the meta-model without any complexity. The main objective of the above UML model is to provide an easy-to-use visual modeling language for all users. The SCL file of the provider terminal may be subjected to provider terminal definition object extraction by the UML data model. The supplier terminal included in the MICS file defines an extended model, performs syntax and semantic verification according to the namespace rules in the IEC61850-7-1 standard, and if any inconsistency is found, transmits an error message to the tester.

Information verification rules are generated in connection with MICS (model implementation compliance declaration) files. According to the UML data model, a provider terminal definition rule database can be constructed according to the information verification rule, and a target rule database can be constructed according to the extracted provider terminal definition object and the SCL file of the provider terminal. The MICS file comprises an extension model defined by the provider terminal, and the information model verification comprises verification of validity of the extension model defined by the provider terminal, so that the MICS file not only needs to meet IEC61850 verification standards, but also can improve interoperability among multiple provider terminal devices.

More specifically, by inputting the supplier terminal definition rule database and the target rule database into the SCL verification engine for verification, since the supplier terminal definition extension model contained in the MICS file described above, and syntax and semantic verification can be performed according to the namespace rules in the UML model of IEC61850-7-1, if any inconsistency is found, an error message will be sent to the terminal on the tester side. The tester can correct according to the received error information, and then inputs corrected information model correction data into the SCL verification engine to continue the next verification. If the information model verification has no error, judging that the information model verification passes.

In the embodiment, the MICS file is used for verifying the specific supplier terminal, so that the possibility of errors caused by manual inspection can be prevented, errors caused by undetermined private data elements can be avoided, the algorithm adaptability is high, and convenience and rapidness are realized; and through UML model, can prove the object model definition of SCL file thoroughly more easily, have simplified the traditional method of manually deriving the data object definition in excel electronic form too.

Preferably, in the step S2, the multi-object integrity verification further includes IET consistency verification on the SCL file of the provider terminal, and the step of IET consistency verification on the SCL file of the provider terminal includes:

s212, converting an original IED file through an XML converter, wherein the IED file comprises object information of an SCL file, and the object information comprises substation site information;

s213, inputting the converted IED file and the SCL file into a grammar consistency engine for verification, and judging whether the converted IED file is consistent with the SCL file or not;

s214, if the syntax of the converted IED file is inconsistent with that of the SCL file, acquiring IET consistency correction data generated based on the data with inconsistent syntax, and performing re-syntax consistency verification;

S215, if the converted IED file is consistent with the grammar of the SCL file, converting the SCL file through an XLSX converter, and outputting an IET file consistent with the grammar of the SCL file.

Specifically, the IET file includes real substation site information of IED data configuration, so as to help the supplier terminal configure a new IED, adapt to an existing substation system, and manually record each change of IED functions or actual substation configuration when changing, expanding or adding, which is helpful for field staff to track update of a substation automation system. The IET file comprises an excel spreadsheet of data required for IED engineering, and the structure of the IET file is composed of IED names and structures, including detailed information of the data set definition, report control block definition (buffered and unbuffered) and Goose control block programmed by the supplier terminal. IED names are typically composed of a physical device name and an IP address to facilitate communication.

More specifically, since the plurality of provider terminals use SCL files to describe the functions of the various IEDs described based on IET, it is necessary to verify IET consistency to ensure interoperability. The algorithm of consistency verification between IET and SCL is shown in fig. 8, firstly, the original IED file is converted by the XML converter, and the data after format conversion and the SCL file are input into the excel table-based grammar consistency engine for verification. If the IET file is inconsistent with the SCL file, corresponding notification information is generated to a terminal on one side of the tester, and the tester carries out corresponding correction according to the received notification information to obtain IET consistency correction data. And then re-carrying out grammar consistency verification according to the IET consistency correction data, debugging the SCL file through a grammar consistency engine, and debugging the XLSX converter, wherein the XLSX converter is used for debugging the IET price. When the syntax of the IED file is consistent with that of the SCL file, the IED file is output to the XLSX converter through the XML converter, and finally the IET file is output through the XLSX converter. The resulting IET file obtained in the above manner will represent the correct data model information of the substation under consideration, and IET consistency verification extends the SCL verification functionality by checking the specific IET file used in the substation configuration.

Preferably, in the step S2, the multi-object integrity verification further includes CSV consistency verification on the SCL file of the provider terminal, and the step of CSV consistency verification on the SCL file of the provider terminal includes:

s216, reading a CSV file from an online IED file;

s217, inputting the CSV file and the SCL file into a CSV consistency verification engine for verification, and judging whether the information in the CSV file and the information in the SCL file are consistent according to a CSV consistency verification result;

s218, if the information in the CSV file is inconsistent with the information in the SCL file, acquiring CSV consistency correction data generated according to the CSV consistency verification result, and re-verifying according to the CSV consistency correction data;

s219, if the CSV file is consistent with the information in the SCL file, judging that the CSV consistency verification of the CSV file and the SCL file is passed.

Specifically, in order for a tester to be able to confirm whether the data model of the online IED conforms to the SCL file used in the design, in this embodiment, the CSV file may be exported by the online IED, and then the CSV file and the SCL file are subjected to consistency verification. As shown in fig. 9, each row in the IED file represents a row of data, each row of data having different data fields separated by a semicolon. As shown in fig. 10, the CSV consistency verification is performed by first reading a CSV file from an online IED file, where the CSV file is used to derive IED data, then importing the CSV file and the SCL file into a CSV consistency verification engine to perform verification, and determining whether information in the CSV file and the SCL file is consistent according to a CSV consistency verification result. If the CSV consistency verification result is inconsistent, the tester corrects the CSV consistency verification result, then inputs the CSV consistency correction data seat CSV file into a consistency verification engine to carry out CSV consistency verification with the SCL file until the maximum verification times are reached or verification is finished after the verification is passed. Where the IED data is derived from CSV files at a lower cost and therefore using much less bandwidth and storage than XML, it is easier to derive and import data than XML. Since the CSV file is a simple file format, it can be manipulated on the text file by any processing tool to maintain optimal interoperability.

Preferably, in the step S2, the multi-object integrity verification further includes UCA-IUG program verification on the SCL file of the provider terminal, and the step of UCA-IUG program verification on the SCL file of the provider terminal includes:

s220, selecting a test case, and constructing a mapping relation between the test case and a rule database, wherein the rule database is constructed based on an SCL mode model and an SCL data model;

s221, inputting the SCL file and the rule database into a master verification engine, verifying the UCA-IUG program of the SCL file by the master verification engine, and judging whether the UCA-IUG program has errors according to the UCA-IUG program verification result;

s222, if the UCA-IUG program has errors, acquiring the UCA-IUG program correction data for re-verification; s223, if the UCA-IUG program has no error, judging that the UCA-IUG program passes verification.

Specifically, the UCA-IUG program verifies the smooth interoperability for multi-vendor terminals, and the verification flow is shown in FIG. 11. The process includes checking the SCL file using predefined rules in UCA-IUG consistency test criteria, wherein the predefined rules are derived based on a rules database, which may be constructed from an SCL pattern model and a data model, for example: and constructing a rule database according to the SCL mode model IEC61850-6 and the data model IEC 61850-7-3. The main task of UCA-IUG is to support testing of multi-vendor terminal equipment and applications to comply with IEC61850 standard. Both members and non-members tend to provide feedback on interoperability problems encountered during testing, and UCA-IUG develops test programs based on feedback information to ensure quality of the test procedure and interoperability results. If the UCA-IUG program verification has errors, generating error information corresponding to the error data and sending the error information to a terminal on the side of a tester, and after the tester corrects the error data, obtaining UCA-IUG program correction data and inputting the UCA-IUG program correction data into a main verification engine for further verification. The error existing in the UCA-IUG program verification process can be solved by directly debugging the file through a tester, and a third-party SCL editor is not needed.

Preferably, in the step S2, the multi-object integrity verification further includes performing a user-defined rule verification on the SCL file of the provider terminal, and the step of performing a user-defined rule verification on the SCL file of the provider terminal includes:

s224, determining a verification rule database according to an IEC61850 standard architecture and a UML data model;

s25, determining a user rule according to a consistency statement source realized by a model test;

s226, carrying out user rule verification on the user rule according to the verification rule database, and judging whether the user rule is consistent with the standard in the verification rule database;

s227, if the rules are inconsistent, revising and re-verifying the verification rule database and the user rules according to the data with inconsistent rules;

s228, if the SCL files are consistent with the verification rule database, inputting the SCL files of different types into an SCL verification engine for verification, wherein the types of the SCL files comprise an ICD file, a CID file and an IID file;

s229, judging whether SCL files of all types meet all rules of the verification rule database according to verification results corresponding to files of different types;

S230, if not, acquiring rule definition correction data of the SCL file, and re-verifying according to the rule definition correction data through the SCL verification engine;

and S231, if yes, judging that the SCL file meets the user-defined rule.

Specifically, as shown in fig. 12, the verification rule database is determined according to the IEC61850 standard architecture and the UML data model, the user rule is determined according to the model test to realize the consistency statement source, and then the user rule is verified according to the verification rule database. When the user rule does not meet the verification rule database, the verification rule database or the user rule is edited and adjusted according to the condition that the user rule does not meet the verification rule database, and then the adjusted user rule is verified. When the user rules satisfy the validation rule database, different types of SCL files may be entered into the SCL validation engine, including entering ICD files, CID files, and IID files. And verifying the ICD file, the CID file and the IID file according to the verification rule database which is matched and consistent with the user rule. And obtaining a verification result aiming at different types of files, determining whether the files of all types meet all rules of a verification rule database according to the verification result, generating prompt information according to data which does not meet the rules and sending the prompt information to a terminal on a tester side if the files of all types do not meet the rules, and then carrying out verification again after corresponding correction by the tester, and judging that the SCL file meets the user-defined rules when the verification is passed and the user-defined rules are verified. Thus, in embodiments of the present invention, verification by user-defined rules provides a tester with flexibility to check other SCLs that previously defined methods cannot access.

In summary, in the embodiment of the invention, by performing pattern verification, information model verification, IET consistency verification, CSV consistency verification, UCA-IUG program verification and user-defined rule verification on the SCL file of each supplier terminal in the intelligent substation by means of the expansion characteristic of the SCL verification algorithm, the integrity verification on the SCL file is realized, so that the interoperability of multiple supplier terminals in the substation is ensured. In addition, through SCL verification algorithm, from IET consistency check and user-defined rule two aspect system, automatic check and verification, can guarantee that the utility has stronger adaptability.

Example two

In the embodiment of the present invention, referring to fig. 13, a schematic structural diagram of an authentication device for an SCL file of an intelligent substation according to the embodiment of the present invention is shown. An authentication device M13 of an intelligent substation SCL file, comprising:

the data acquisition module M131 is used for acquiring SCL files of all the supplier terminals in the intelligent substation;

the data verification module M132 is configured to perform multi-object integrity verification on the SCL file of each provider terminal, so as to obtain a verification result corresponding to each verification object;

the result judging module M133 is configured to determine whether the SCL file of each provider terminal meets a preset verification standard based on a plurality of verification results of performing multi-object integrity verification on the SCL file of each provider terminal.

Optionally, the data verification module M132 is specifically configured to:

Optionally, the data verification module M132 is specifically further configured to:

reading a CSV file from an online IED file;

selecting a test case, and constructing a mapping relation between the test case and a rule database, wherein the rule database is constructed based on an SCL mode model and an SCL data model;

if the UCA-IUG program has no error, judging that the UCA-IUG program passes the verification

And if so, judging that the SCL file meets the user-defined rule.

In this embodiment, a verification device for an intelligent substation SCL file can implement steps in a method for verifying an intelligent substation SCL file in the foregoing embodiment, and can implement the same technical effects, which are not described herein in detail with reference to the description in the foregoing embodiment.

An embodiment of the present invention further provides a computer device, please refer to fig. 14, fig. 14 is a schematic structural diagram of the computer device provided in the embodiment of the present invention, and the computer device D14 includes: a processor D1401, a memory D1402, and a computer program stored on the memory D1402 and executable on the processor D1401.

The processor D1401 invokes the computer program stored in the memory D1402 to execute each step in the verification method of the intelligent substation SCL file provided by the embodiment of the present invention, which is not described herein.

The computer device provided by the embodiment of the invention can realize the steps in the verification method of the intelligent substation SCL file in the embodiment, and can realize the same technical effects, and the description in the embodiment is referred to and is not repeated here.

The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements each process and step in the verification method of the intelligent substation SCL file provided by the embodiment of the invention, and can implement the same technical effects, so that repetition is avoided and redundant description is omitted here.

It should be noted that, as will be understood by those skilled in the art, the electronic device in the embodiments of the present invention is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and its hardware includes, but is not limited to, a microprocessor, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a programmable gate array (Field-Programmable Gate Array, FPGA), a digital processor (Digital Signal Processor, DSP), an embedded device, and the like. The electronic device may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, and the like. The electronic equipment can perform man-machine interaction in a mode of a keyboard, a mouse, a remote controller, a touch pad or voice control equipment and the like.

The readable storage medium includes flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory may be an internal storage unit of the electronic device, such as a hard disk or a memory of the electronic device. In other embodiments, the memory may also be an external storage device of the electronic device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like. Of course, the memory may also include both internal storage units of the electronic device and external storage devices. In this embodiment, the memory is generally used to store an operating system and various application software installed in the electronic device, for example, a program code of an authentication method of an SCL file of an intelligent substation. In addition, the memory can be used to temporarily store various types of data that have been output or are to be output.

Those skilled in the art will appreciate that the implementation of all or part of the above-described procedures in the method embodiments may be implemented by a computer program to instruct related hardware, and the program may be stored in a computer readable storage medium, where the program, when executed, may include the procedures of the embodiment of the verification method of an intelligent substation SCL file as described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM) or the like.

The above embodiments are preferred embodiments of the method for verifying an SCL file of an intelligent substation according to the present invention, and are not limited to the embodiments, but the scope of the invention includes equivalent changes according to the shape and structure of the invention.

Claims

1. The verification method of the intelligent substation SCL file is characterized by comprising the following steps of:

2. A method of validating an SCL file of an intelligent substation according to claim 1, wherein said multi-object integrity validation comprises a pattern validation of said SCL file of a supplier terminal, said step of pattern validating said SCL file of a supplier terminal comprising:

3. A method of verifying an SCL file of an intelligent substation according to claim 1, wherein said multi-object integrity verification further comprises information model verification of said SCL file of a supplier terminal, said step of information model verification of said SCL file of a supplier terminal comprising:

Extracting a supplier definition object from the SCL file of the supplier terminal through a UML data model;

generating information verification rules according to MICS files, and constructing a supplier definition rule database according to the information verification rules according to the UML data model;

constructing a target rule database according to the extracted provider definition object and the SCL file of the provider terminal;

performing information model verification on the provider definition rule database and the target rule database through an SCL verification engine; judging whether the information model verification has errors according to the information model verification result;

4. A method of verifying an SCL file of an intelligent substation according to claim 1, wherein said multi-object integrity verification further comprises IET consistency verification of said SCL file of a supplier terminal, said step of IET consistency verification of said SCL file of a supplier terminal comprising:

5. A method of verifying an SCL file of an intelligent substation according to claim 1, wherein the multi-object integrity verification further comprises CSV consistency verification of the SCL file of a supplier terminal, the step of CSV consistency verification of the SCL file of a supplier terminal comprising:

reading a CSV file from an online IED file;

6. A method of verifying an SCL file of an intelligent substation according to claim 1, wherein said multi-object integrity verification further comprises UCA-IUG program verification of said SCL file of a supplier terminal, said step of UCA-IUG program verification of said SCL file of a supplier terminal comprising:

7. A method of validating an SCL file of an intelligent substation according to claim 1, wherein said multi-object integrity validation further comprises user-defined rule validation of said SCL file of a supplier terminal, said step of user-defined rule validation of said SCL file of a supplier terminal comprising:

and if so, judging that the SCL file meets the user-defined rule.

8. An intelligent substation SCL file's verifying attachment, its characterized in that, the device includes:

9. A computer device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps in a method of verifying an intelligent substation SCL file according to any one of claims 1-7 when the computer program is executed.

10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of a method for verifying an intelligent substation SCL file according to any of claims 1-7.