Dynamic data set management system

Abstract

The invention relates to the technical field of power system relay protection, and provides a dynamic data set management system, which comprises an automatic generation module for writing persistent data set information dynamically created by a client into a persdataset.json file according to a user-defined format; the analysis module is used for converting data set information in the persdataset.json file into a program language to be used by the server side communication module; the maintenance module is used for adding and deleting a data set in the persdataset.json file or adding a new member to the data set; and the server side communication module interacts with the client side based on the program language converted by the analysis module. According to the method, the dynamic management of the persistent data set can be realized according to the request of the client, the flexibility is high, the independence is good, and the compatibility is strong. According to the method, the persistent data set is managed by adopting the independent file, the original model file of the device is not influenced, the independence is good, and the compatibility is strong.

Description

Technical Field

[0001] The present invention relates to the technical field of power system relay protection, and in particular to a dynamic data set management system. Background Art

[0002] In recent years, power automation technology has developed rapidly, and complex and changing application scenarios have put forward higher requirements for relay protection devices. During operation, the device needs to respond to the client's request to dynamically create and delete data sets, and at the same time meet the function of maintaining persistent data sets after the device loses power. Traditional relay protection devices have the following shortcomings in dynamic data set management:

[0003] Most traditional relay protection devices do not support dynamic data set services.

[0004] A few relay protection devices that support dynamic data set services lack centralized management of persistent data sets and do not support the function of maintaining the data set after power failure. Summary of the invention

[0005] The purpose of the present invention is to solve at least one technical problem in the background technology and provide a dynamic data set management system.

[0006] To achieve the above object, the present invention provides a dynamic data set management system, comprising:

[0007] Automatically generate a module to write the persistent dataset information dynamically created by the client into the pers_dataset.json file in a custom format;

[0008] Parsing module, which converts the dataset information in the pers_dataset.json file into programming language for use by the server-side communication module;

[0009] Maintenance module, add, delete or append new members to datasets in the pers_dataset.json file;

[0010] The server-side communication module interacts with the client based on the program language converted by the parsing module.

[0011] According to one aspect of the present invention, in the automatic generation module, the persistent data set information dynamically created by the client is written into the pers_dataset.json file in a custom format, including:

[0012] Convert the persistent data set information dynamically created by the client into JSON language format;

[0013] Create the pers_dataset.json file and write the dataset information in JSON format into the file.

[0014] According to one aspect of the present invention, the number of data sets and the number of members in each data set in the pers_dataset.json file are stored in corresponding key values.

[0015] According to one aspect of the present invention, the parsing module converts the dataset information in the JSON language format in the pers_dataset.json file into a program language, and creates a corresponding dataset in the JSON language format in the embedded device.

[0016] According to one aspect of the present invention, the maintenance module adds or deletes data sets in the pers_dataset.json file, appends members to a single data set, and modifies the key value of the corresponding number of data sets or the key value of the number of members in a data set based on a request from a client to create or delete a data set, to ensure that the actual number of data sets or the number of members in a data set is consistent with the corresponding key value.

[0017] According to one aspect of the present invention, the server-side communication module interacts with the client using a dynamic data set service of a communication protocol;

[0018] Among them, dynamic dataset services include: create dataset service and delete dataset service.

[0019] According to the solution of the present invention, the present invention provides a dynamic data set management method based on the DL / T860 standard, which can realize dynamic management of persistent data sets according to the request of the client, with high flexibility, good independence and strong compatibility.

[0020] According to the solution of the present invention, the present invention uses independent files to manage persistent data sets, has no impact on the original model files of the device, has good independence and strong compatibility.

[0021] The persistent data set management file of the present invention uses JSON, a lightweight data exchange format, which has cross-platform characteristics and improves readability and scalability.

[0022] The present invention expands the communication service capability of the relay protection device. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 A schematic diagram showing an architecture of a dynamic data set management system according to an embodiment of the present invention;

[0024] Figure 2 This is a schematic diagram of the use process of the dynamic data set management system according to Embodiment 1 of the present invention. DETAILED DESCRIPTION

[0025] The present invention will now be discussed with reference to exemplary embodiments. It should be understood that the embodiments discussed are only to enable those skilled in the art to better understand and thus implement the present invention, rather than implying any limitation on the scope of the present invention.

[0026] As used herein, the term “including” and variations thereof are to be interpreted as open-ended terms meaning “including, but not limited to.” The term “based on” is to be interpreted as “based, at least in part, on.” The terms “one embodiment” and “an embodiment” are to be interpreted as “at least one embodiment.”

[0027] Figure 1 The following schematically shows the architecture of a dynamic data set management system according to an embodiment of the present invention. Figure 1 As shown, in this embodiment, the dynamic data set management system includes:

[0028] Automatically generate a module to write the persistent dataset information dynamically created by the client into the pers_dataset.json file in a custom format;

[0029] Parsing module, which converts the dataset information in the pers_dataset.json file into programming language for use by the server-side communication module;

[0030] Maintenance module, add, delete or append new members to datasets in the pers_dataset.json file;

[0031] The server-side communication module interacts with the client based on the program language converted by the parsing module.

[0032] Further, according to an embodiment of the present invention, in the automatic generation module, the persistent data set information dynamically created by the client is written into the pers_dataset.json file in a custom format, including:

[0033] Convert the persistent data set information dynamically created by the client into JSON language format;

[0034] Create the pers_dataset.json file (management file) and write the dataset information in JSON format into the file.

[0035] In this embodiment, when the pers_dataset.json file does not exist in the device (embedded device), the device generates a management file for the first time according to the persistent data set information dynamically created by the client through the automatic generation module.

[0036] In this embodiment, a lightweight data exchange format such as JSON is used, which has cross-platform characteristics and improves the readability and scalability of management files.

[0037] In this implementation, the pers_dataset.json file can exist independently of the cid / icd model of the device without affecting the original function.

[0038] Further, according to an embodiment of the present invention, the number of data sets in the pers_dataset.json file and the number of members in each data set are stored in the corresponding key value. With this arrangement, the user can compare the actual number of data sets in the file with the corresponding key value, or compare the number of members in the data set with the corresponding key value for error prevention.

[0039] Further, according to an embodiment of the present invention, the parsing module converts the dataset information in the JSON language format in the pers_dataset.json file into a programming language, and creates a corresponding dataset in the JSON language format in the embedded device to implement the power-off preservation function of the persistent dataset.

[0040] Furthermore, according to one embodiment of the present invention, the maintenance module adds or deletes data sets in the pers_dataset.json file, appends members to a single data set, and modifies the key value of the corresponding number of data sets or the key value of the number of members in a data set based on the client's request to create or delete data sets, to ensure that the actual number of data sets or the number of members in a data set is consistent with the corresponding key value.

[0041] Further, according to one embodiment of the present invention, the server-side communication module interacts with the client using a dynamic data set service of a communication protocol;

[0042] Among them, dynamic dataset services include: create dataset service and delete dataset service.

[0043] In this implementation, the server-side communication module is decoupled from the relevant functions of the persistent dataset management file (ie, the pers_dataset.json file), thereby ensuring the modularity and portability of the communication protocol.

[0044] According to the above scheme of the present invention, the present invention provides a dynamic data set management method based on the DL / T860 standard, which can realize dynamic management of persistent data sets according to the request of the client, with high flexibility, good independence and strong compatibility.

[0045] According to the above solution of the present invention, the present invention uses independent files to manage persistent data sets, which has no impact on the original model files of the device, has good independence and strong compatibility.

[0046] The persistent data set management file of the present invention uses JSON, a lightweight data exchange format, which has cross-platform characteristics and improves readability and scalability.

[0047] The present invention expands the communication service capability of the relay protection device.

[0048] Based on the above solution of the present invention, the technical solution of the present invention is described in the following in the form of a specific embodiment in conjunction with the accompanying drawings.

[0049] Example 1

[0050] Combination Figure 1 and Figure 2 As shown, the dynamic data set management system based on the DL / T860 standard performs dynamic data set management, as follows:

[0051] First, automatically generate pers_dataset.json file function:

[0052] Here’s how to do it:

[0053] Open the client tool;

[0054] Enter the index of the dataset to be created, TEMPLATEPROT / LLN0.dyn1, add dataset members, and finally create the dataset;

[0055] Enter the index of the dataset to be created, TEMPLATEPROT / LLN0.dyn2, add dataset members, and finally create the dataset;

[0056] The client adds new members to the TEMPLATEPROT / LLN0.dyn1 data set;

[0057] The client deletes the TEMPLATEPROT / LLN0.dyn2 data set;

[0058] The client sends read dataset directory and read dataset value service requests to verify the correctness of the created dataset TEMPLATEPROT / LLN0.dyn1;

[0059] Use the debugging tool to connect to the protection device, upload the / tffs / lgh / pers_dataset.json file to the computer, and check the consistency of the dataset information in the file with the information seen by the client tool in Article 6.

[0060] Second, the persistent data set power-off preservation function:

[0061] Open the client tool;

[0062] Send read dataset directory and read dataset value service requests to the server to record the dynamically created persistent dataset information;

[0063] Power-off restart protection device;

[0064] Send read dataset directory and read dataset value service requests to the server, and compare the persistent dataset information replied by the server with the record before power failure.

[0065] Those skilled in the art will appreciate that the modules and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0066] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and equipment can refer to the corresponding processes in the aforementioned method implementation methods, and will not be repeated here.

[0067] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0068] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present invention.

[0069] In addition, each functional module in the embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0070] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the energy-saving signal sending / receiving method of each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical disks.

[0071] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with the technical features with similar functions disclosed in this application (but not limited to) by each other.

[0072] It should be understood that the size of the serial numbers of each step in the content of the invention and the implementation methods of the present invention does not absolutely mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the implementation methods of the present invention.

Claims

1. A dynamic data set management system, characterized in that: include: Automatically generate a module to write the persistent dataset information dynamically created by the client into the pers_dataset.json file in a custom format; Parsing module, which converts the dataset information in the pers_dataset.json file into programming language for use by the server-side communication module; Maintenance module, add, delete or append new members to datasets in the pers_dataset.json file; The server-side communication module interacts with the client based on the program language converted by the parsing module.

2. The dynamic data set management system according to claim 1, characterized in that: In the automatic generation module, the persistent dataset information dynamically created by the client is written to the pers_dataset.json file in a custom format, including: Convert the persistent data set information dynamically created by the client into JSON language format; Create the pers_dataset.json file and write the dataset information in JSON format to the file.

3. The dynamic data set management system according to claim 1, characterized in that: The number of data sets in the pers_dataset.json file and the number of members in each data set are stored in the corresponding key values.

4. The dynamic data set management system according to claim 1, characterized in that: The parsing module converts the dataset information in the JSON language format in the pers_dataset.json file into a program language, and creates a corresponding dataset in the JSON language format in the embedded device.

5. The dynamic data set management system according to claim 3, characterized in that: The maintenance module adds or deletes datasets in the pers_dataset.json file, appends members to a single dataset, and modifies the key value of the corresponding number of datasets or the key value of the number of members in a dataset according to the client's request to create or delete a dataset, to ensure that the actual number of datasets or the number of members in a dataset is consistent with the corresponding key value.

6. The dynamic data set management system according to any one of claims 1 to 5, characterized in that: The server-side communication module interacts with the client using a dynamic data set service of a communication protocol; Among them, dynamic dataset services include: create dataset service and delete dataset service.

Images