Large-scale energy storage resource management method and device

Abstract

The invention discloses a large-scale energy storage resource management method and device. According to the resource model data version management system, the query, addition, modification or deletion operation on the resource data table is executed by receiving the data operation instruction, and the version basic information table and the version historical record table are synchronously updated, so that the resource model data version management system decoupled from the service data is maintained. The system can record the identification, the name, the creation date and the start and end values of the version number of each resource in detail, and track the time and the version number of each data change. According to the method and the device, the resource data and the business data are highly decoupled, and version control is performed, so that the efficiency and the accuracy of data management are improved, and the problem that large-scale energy storage resources cannot be flexibly managed in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of large-scale energy storage resource management, and in particular to a large-scale energy storage resource management method and device. Background Art

[0002] In the process of building a large-scale energy storage system, energy storage resources usually need to have a version backtracking function. When the system switches to a specific time point, the energy storage resources need to be able to be restored to the state at the specific time point normally, that is, the quantity, attributes and other information of the energy storage resources need to correspond to the specific time point. In order to meet the resource version backtracking function, the current practice of most systems is to tightly couple the energy storage resource data with the business data, that is, the energy storage resource data is bound to the business data corresponding to the specific time to form a complete set of data. This makes the management of energy storage resources difficult and unmaintainable. As time goes by, there is a lot of redundancy in the energy storage resource data. Especially in some advanced predictive analysis functions, multiple copies of large amounts of duplicate resource data may be generated in a day. The amount of data is growing exponentially, which poses a great challenge to the storage cost of system construction, resulting in the inability of existing technologies to flexibly manage large-scale energy storage resources. Summary of the invention

[0003] The present invention provides a large-scale energy storage resource management method and device to solve the problem in the prior art that large-scale energy storage resources cannot be flexibly managed.

[0004] In a first aspect, the present application provides a large-scale energy storage resource management method, including:

[0005] Receiving data operation instructions; wherein the data operation instructions include querying data, adding data, modifying data or deleting data;

[0006] According to the data operation instruction, the preset resource data table is operated, and the data in the preset version basic information table and the preset version history record table are modified;

[0007] The preset resource data table is used to store resource model data decoupled from business data, and the preset version basic information table and the preset version history record table are used to record version information of the preset resource data table;

[0008] The first resource data of the preset resource data table includes a first resource flag, a first resource name, a first creation date, a first start version number and a first end version number;

[0009] The data of the preset version basic information table includes a first starting version number, a first ending version number, a first version number increment, and a first creation date;

[0010] The data of the preset version history record table includes a first change time, a first change version number and a first creation date.

[0011] The present application realizes accurate operation of the resource data table by receiving data operation instructions including query, addition, modification and deletion, and updates the basic version information table and the version history record table at the same time, ensuring the consistency and integrity of the data. The present application not only improves maintainability by decoupling resource data from business data, but also reduces data redundancy and storage costs through version control. When executing data operation instructions, the present application first performs corresponding addition, deletion, modification and query operations in the resource data table, and then synchronously updates the basic version information table and the version history record table to record the detailed information and version changes of the operation. The present application improves the traceability of the data by recording the history of each data change in detail, so that problems can be quickly located and data can be restored when needed. In addition, by controlling the growth and end of the version number, the present application effectively avoids unnecessary duplication of data and optimizes the amount of data storage. Therefore, the present application improves the efficiency and accuracy of data management by highly decoupling resource data from business data and performing version control, so as to solve the problem that large-scale energy storage resources cannot be flexibly managed in the prior art.

[0012] As a preferred embodiment of the first aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0013] When the data operation instruction is to query data;

[0014] Acquire a first preset time of the query data;

[0015] According to a preset version history record table and a first preset time, query the preset version history record table for all first records whose first change time is less than or equal to the first preset time;

[0016] According to the first record, determining a maximum value in the first change time in the preset version history record table, and obtaining a change version number of the maximum value;

[0017] According to the changed version number of the maximum value, the first resource data corresponding to the changed version number of the maximum value is retrieved from a preset resource data table.

[0018] In this preferred embodiment, when the data operation instruction is to query data, the present application first determines the preset time point of the query, and then accurately finds all change records up to that time point through the preset version history record table. By screening out the maximum version number whose change time is less than or equal to the preset time, the system can ensure that the provided data is an accurate snapshot of the user's query time. This method not only improves the response speed of the query operation and the accuracy of the data, but also enhances the traceability of the data and the transparency of the system by maintaining a clear change history record. In addition, this query mechanism also facilitates the subsequent data analysis, audit tracking and troubleshooting of the system, thereby playing a vital role in the operation and maintenance of the power system. Therefore, the present application improves the accuracy and efficiency of data retrieval, enhances the reliability of data management, and optimizes the user experience of system operation.

[0019] As a preferred embodiment of the first aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0020] When the data operation instruction is to add new data;

[0021] Acquire second resource data of the newly added data;

[0022] According to the date of the second resource data, obtaining in a preset version history record table all second records whose first change time is less than or equal to the date of the second resource data;

[0023] According to the second record, obtaining a first maximum changed version number in a preset version history record table;

[0024] According to the first maximum changed version number, obtaining a second end version number of the first maximum changed version number in the version basic information table;

[0025] Adding the second resource data to the preset resource data table; wherein the value of the start version number of the second resource data is the value of the maximum change version number, and the value of the end version number of the second resource data is the value of the second end version number;

[0026] A record of the second resource data is added to the preset version history record table; wherein the second creation date of the record of the second resource data is the date of the second resource data, and the second change version number of the record of the second resource data is the value of the first maximum change version number plus one.

[0027] In this preferred embodiment, the present application provides an efficient data consistency guarantee mechanism for large-scale energy storage resource management by accurately controlling the update of version information and historical records. When new data is added, the system first determines the specific date of the new data, and searches for all previous change records in the preset version history record table based on this to obtain the current maximum change version number and the corresponding end version number. This process ensures the continuity and accuracy of the version number. Subsequently, the system adds new resource data to the preset resource data table, and updates the preset version history record table to record the detailed information and new version number of the new data. The beneficial effect of this method is that it not only maintains a clear historical track of data changes, which is convenient for future queries and audits, but also enhances the consistency and reliability of data by ensuring that each data addition is strictly carried out in accordance with the version control process. In addition, clear version control also helps to improve the automation level of data management and reduce human errors, thereby playing a vital role in the operation and maintenance of power systems. Therefore, the present application improves the accuracy and efficiency of data management, enhances the traceability of data and the stability of the system.

[0028] As a preferred embodiment of the first aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0029] When the data operation instruction is to modify data;

[0030] Query the version number increment and the end version number of the modified data in the preset version basic information table;

[0031] Searching the preset version history record table for a third record whose first change time is less than or equal to the time of modifying the data, and searching the third record for the second largest change version number;

[0032] Update the information of the modified data in a preset resource data table; wherein the end version number of the modified data is modified to the second largest change version number plus one;

[0033] Adding the second resource information of the modified data to the preset resource data table; wherein the start version number of the second resource information is the second largest change version number plus one, and the end version number of the second resource information is the end version number of the modified data;

[0034] A record of the modified data is newly added to the preset version history record table; wherein, the third change time of the record of the modified data is the time when the data was modified, the third change version number of the record of the modified data is the second largest change version number plus one, and the third creation date of the record of the modified data is the date of the modified data.

[0035] In this preferred embodiment, the present application realizes the precise management of large-scale energy storage resources by synchronously updating the basic version information table and the preset version history record table when the resource data changes. Specifically, when modifying the resource data, the system first queries the current version number growth rate and the end version number to ensure the continuity of version control. Subsequently, the system finds the latest version record in the preset version history record table and determines the version number benchmark of the modification operation. By updating the end version number in the preset resource data table and adding a resource information record with a new version number, the system ensures that each modification is accurately recorded and tracked. Finally, the newly added records in the preset version history record table further ensure the traceability of the changes. The beneficial effect of this method is that it not only improves the accuracy and reliability of data management, avoids conflicts and inconsistencies between data versions, but also enhances the transparency and auditing capabilities of the system through detailed historical records. In addition, this refined version control mechanism helps to quickly locate and roll back to a specific version of data, thereby playing a vital role in the operation and maintenance of the power system, and significantly improving the overall stability and maintenance efficiency of the system.

[0036] As a preferred embodiment of the first aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0037] When the data operation instruction is to delete data;

[0038] Obtaining the third largest changed version number whose first change time is less than or equal to the date of deleting the data in a preset version history record table;

[0039] In a preset version history record table, updating the end version number of the deleted data to the third largest changed version number;

[0040] A record of the deleted data is newly added in the preset version history record table; wherein the fourth change date of the record of the deleted data is the date of the deleted data, and the fourth change version number of the deleted data is the third maximum change version number plus one.

[0041] In this preferred embodiment, the present application realizes the effective management of large-scale energy storage resources by updating the preset version history record table when performing the deletion operation. Specifically, when deleting resource data, the system first searches the preset version history record table for all records whose change time is less than or equal to the deletion operation date to determine the current maximum change version number. This step ensures that the system can identify the accurate version benchmark corresponding to the deletion operation. Subsequently, the system updates the end version number of the resource data to this maximum change version number, clearly marking the end point of the life cycle of the resource data. In addition, the system adds a new record to the preset version history record table to record the specific version number and date of the deletion operation. This newly added record not only provides a basis for future data recovery and auditing, but also ensures the integrity and continuity of the version history. The present application improves the accuracy of data management, ensures the consistency and integrity of data, and at the same time, by maintaining a detailed version history record, enhances the traceability and transparency of the system, and provides strong support for the stable operation and efficient maintenance of the power system.

[0042] In a second aspect, the present application provides a large-scale energy storage resource management device, which includes a receiving module and an operating module.

[0043] The receiving module is used to receive data operation instructions; wherein the data operation instructions include querying data, adding data, modifying data or deleting data;

[0044] The operation module is used to operate the preset resource data table according to the data operation instruction, and modify the data in the preset version basic information table and the preset version history record table;

[0045] The preset resource data table is used to store resource model data decoupled from business data, and the preset version basic information table and the preset version history record table are used to record version information of the preset resource data table;

[0046] The first resource data of the preset resource data table includes a first resource flag, a first resource name, a first creation date, a first start version number and a first end version number;

[0047] The data of the preset version basic information table includes a first starting version number, a first ending version number, a first version number increment, and a first creation date;

[0048] The data of the preset version history record table includes a first change time, a first change version number and a first creation date.

[0049] The device uses two modules to divide the work and coordinate the work to better manage the large-scale energy storage data. The application realizes the precise operation of the resource data table by receiving data operation instructions including query, addition, modification and deletion, and updates the basic information table of the version and the history record table of the version to ensure the consistency and integrity of the data. The application not only improves the maintainability by decoupling the resource data from the business data, but also reduces the data redundancy and storage cost through version control. When executing the data operation instruction, the application first performs the corresponding addition, deletion, modification and query operations in the resource data table, and then synchronously updates the basic information table of the version and the history record table of the version to record the detailed information and version changes of the operation. The application improves the traceability of the data by recording the history of each data change in detail, so that the problem can be quickly located and the data can be restored when needed. In addition, by controlling the growth and end of the version number, the application effectively avoids unnecessary duplication of data and optimizes the data storage capacity. Therefore, the application improves the efficiency and accuracy of data management by highly decoupling the resource data from the business data and performing version control, so as to solve the problem that the large-scale energy storage resources cannot be flexibly managed in the prior art.

[0050] As a preferred embodiment of the second aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0051] When the data operation instruction is to query data;

[0052] Acquire a first preset time of the query data;

[0053] According to a preset version history record table and a first preset time, query the preset version history record table for all first records whose first change time is less than or equal to the first preset time;

[0054] According to the first record, determining a maximum value in the first change time in the preset version history record table, and obtaining a change version number of the maximum value;

[0055] According to the changed version number of the maximum value, the first resource data corresponding to the changed version number of the maximum value is retrieved from a preset resource data table.

[0056] In this preferred embodiment, when the data operation instruction is to query data, the present application first determines the preset time point of the query, and then accurately finds all change records up to that time point through the preset version history record table. By screening out the maximum version number whose change time is less than or equal to the preset time, the system can ensure that the provided data is an accurate snapshot of the user's query time. This method not only improves the response speed of the query operation and the accuracy of the data, but also enhances the traceability of the data and the transparency of the system by maintaining a clear change history record. In addition, this query mechanism also facilitates the subsequent data analysis, audit tracking and troubleshooting of the system, thereby playing a vital role in the operation and maintenance of the power system. Therefore, the present application improves the accuracy and efficiency of data retrieval, enhances the reliability of data management, and optimizes the user experience of system operation.

[0057] As a preferred embodiment of the second aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0058] When the data operation instruction is to add new data;

[0059] Acquire second resource data of the newly added data;

[0060] According to the date of the second resource data, obtaining in a preset version history record table all second records whose first change time is less than or equal to the date of the second resource data;

[0061] According to the second record, obtaining a first maximum changed version number in a preset version history record table;

[0062] According to the first maximum changed version number, obtaining a second end version number of the first maximum changed version number in the version basic information table;

[0063] Adding the second resource data to the preset resource data table; wherein the value of the start version number of the second resource data is the value of the maximum change version number, and the value of the end version number of the second resource data is the value of the second end version number;

[0064] A record of the second resource data is added to the preset version history record table; wherein the second creation date of the record of the second resource data is the date of the second resource data, and the second change version number of the record of the second resource data is the value of the first maximum change version number plus one.

[0065] In this preferred embodiment, the present application provides an efficient data consistency guarantee mechanism for large-scale energy storage resource management by accurately controlling the update of version information and historical records. When new data is added, the system first determines the specific date of the new data, and searches for all previous change records in the preset version history record table based on this to obtain the current maximum change version number and the corresponding end version number. This process ensures the continuity and accuracy of the version number. Subsequently, the system adds new resource data to the preset resource data table, and updates the preset version history record table to record the detailed information and new version number of the new data. The beneficial effect of this method is that it not only maintains a clear historical track of data changes, which is convenient for future queries and audits, but also enhances the consistency and reliability of data by ensuring that each data addition is strictly carried out in accordance with the version control process. In addition, clear version control also helps to improve the automation level of data management and reduce human errors, thereby playing a vital role in the operation and maintenance of power systems. Therefore, the present application improves the accuracy and efficiency of data management, enhances the traceability of data and the stability of the system.

[0066] As a preferred embodiment of the second aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0067] When the data operation instruction is to modify data;

[0068] Query the version number increment and the end version number of the modified data in the preset version basic information table;

[0069] Searching the preset version history record table for a third record whose first change time is less than or equal to the time of modifying the data, and searching the third record for the second largest change version number;

[0070] Update the information of the modified data in a preset resource data table; wherein the end version number of the modified data is modified to the second largest change version number plus one;

[0071] Adding the second resource information of the modified data to the preset resource data table; wherein the start version number of the second resource information is the second largest change version number plus one, and the end version number of the second resource information is the end version number of the modified data;

[0072] A record of the modified data is newly added to the preset version history record table; wherein, the third change time of the record of the modified data is the time when the data was modified, the third change version number of the record of the modified data is the second largest change version number plus one, and the third creation date of the record of the modified data is the date of the modified data.

[0073] In this preferred embodiment, the present application realizes the precise management of large-scale energy storage resources by synchronously updating the basic version information table and the preset version history record table when the resource data changes. Specifically, when modifying the resource data, the system first queries the current version number growth rate and the end version number to ensure the continuity of version control. Subsequently, the system finds the latest version record in the preset version history record table and determines the version number benchmark of the modification operation. By updating the end version number in the preset resource data table and adding a resource information record with a new version number, the system ensures that each modification is accurately recorded and tracked. Finally, the newly added records in the preset version history record table further ensure the traceability of the changes. The beneficial effect of this method is that it not only improves the accuracy and reliability of data management, avoids conflicts and inconsistencies between data versions, but also enhances the transparency and auditing capabilities of the system through detailed historical records. In addition, this refined version control mechanism helps to quickly locate and roll back to a specific version of data, thereby playing a vital role in the operation and maintenance of the power system, and significantly improving the overall stability and maintenance efficiency of the system.

[0074] As a preferred embodiment of the second aspect, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0075] When the data operation instruction is to delete data;

[0076] Obtaining the third largest changed version number whose first change time is less than or equal to the date of deleting the data in a preset version history record table;

[0077] In a preset version history record table, updating the end version number of the deleted data to the third largest changed version number;

[0078] A record of the deleted data is newly added in the preset version history record table; wherein the fourth change date of the record of the deleted data is the date of the deleted data, and the fourth change version number of the deleted data is the third maximum change version number plus one.

[0079] In this preferred embodiment, the present application realizes the effective management of large-scale energy storage resources by updating the preset version history record table when performing the deletion operation. Specifically, when deleting resource data, the system first searches the preset version history record table for all records whose change time is less than or equal to the deletion operation date to determine the current maximum change version number. This step ensures that the system can identify the accurate version benchmark corresponding to the deletion operation. Subsequently, the system updates the end version number of the resource data to this maximum change version number, clearly marking the end point of the life cycle of the resource data. In addition, the system adds a new record to the preset version history record table to record the specific version number and date of the deletion operation. This newly added record not only provides a basis for future data recovery and auditing, but also ensures the integrity and continuity of the version history. The present application improves the accuracy of data management, ensures the consistency and integrity of data, and at the same time, by maintaining a detailed version history record, enhances the traceability and transparency of the system, and provides strong support for the stable operation and efficient maintenance of the power system. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] Figure 1 : A flow chart of an embodiment of a large-scale energy storage resource management method provided in this application;

[0081] Figure 2 : A structural diagram of an embodiment of the initialization version basic information table provided by the present application;

[0082] Figure 3 : A structural diagram of an embodiment of an initialization version history record table provided by the present application;

[0083] Figure 4 : A structural diagram of an embodiment of creating a version history record table provided by the present application;

[0084] Figure 5 : A structural diagram of an embodiment of a basic information table for initializing energy storage power station information provided by the present application;

[0085] Figure 6 : A structural diagram of an embodiment of a version history record table for initializing energy storage power station information provided by the present application;

[0086] Figure 7 : A structural diagram of an embodiment of an energy storage power station table initial data table for creating energy storage power station information provided by the present application;

[0087] Figure 8 : A structural diagram of an embodiment of a basic information table of a newly added energy storage power station information provided in this application;

[0088] Fig. 9 : A structural diagram of an embodiment of a version history record table of newly added energy storage power station information provided by the present application;

[0089] Fig.10 : A structural diagram of an embodiment of an energy storage power station table data table of the newly added energy storage power station information provided by the present application;

[0090] Fig.11 : A structural diagram of an embodiment of a modified basic information table of the energy storage power station information provided by the present application;

[0091] Fig.12 : A structural diagram of an embodiment of a modified version history record table of energy storage power station information provided by the present application;

[0092] Fig.13 : A structural diagram of an embodiment of a data table of an energy storage power station table of the modified energy storage power station information provided by the present application;

[0093] Fig.14 : A structural diagram of an embodiment of a basic information table of a version of energy storage power station information after deletion provided by the present application;

[0094] Fig.15 : A structural diagram of an embodiment of a version history record table of energy storage power station information after deletion provided by the present application;

[0095] Fig.16 : A structural diagram of an embodiment of an energy storage power station table data table of the deleted energy storage power station information provided by the present application;

[0096] Fig.17 : A structural diagram of an embodiment of a large-scale energy storage resource management device provided in this application. DETAILED DESCRIPTION

[0097] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0098] Embodiment 1

[0099] Please refer to Figure 1 , which is a large-scale energy storage resource management method provided by an embodiment of the present invention.

[0100] In this embodiment, the process of the large-scale energy storage resource management method in this application is described in detail through steps S01-S02.

[0101] This application extracts resource data from business data for separate management and maintenance, and provides a complete lifecycle management for the resource model, providing version control functions for the addition, deletion, modification, and query of energy storage resources, avoiding multiple duplicate resource data in one day, and solving the problem of exponential growth of resource data over time, thereby reducing system construction costs.

[0102] Before conducting large-scale energy storage management, this application must first obtain a series of power system data, namely: sort out which resource model data need to be managed; the source of resource model data mainly includes but is not limited to c ime files, dt files, and other system databases in the power industry; according to the characteristics of the power industry, the resource data that usually need to be managed mainly includes but is not limited to physical equipment in the distribution, transmission, and power generation links; finally, according to the characteristics of the system, identify which resource data need to be version controlled. The principle of version control is generally to determine whether the resource data needs to be traced back according to time when the resource data is added, modified, or deleted. If traceback is required, version control is required.

[0103] Secondly, the resource data collected and sorted by the resource model is converted into unified, standardized resource model data and entered into the database table. The standardized, unified and standard resource model should include but not be limited to the resource unique identifier, resource name, resource creation date and other information. The resource data that needs to be version controlled should also include the start version number and the end version number information; the design of the database table should meet the requirements of the third normal form, and resource attributes can be added dynamically. The dynamic addition, deletion, modification and other operations of resource attributes should not be restricted to meet the scalability requirements.

[0104] Then create and initialize two tables that need version control, one is the version history table and the other is the version basic information table.

[0105] More specifically, the two tables that need to be version controlled are created as follows:

[0106] (1) Create a basic version information table: save the basic information of the version number. The table fields include:

[0107] Starting version number value: the initial version number value, usually 1. The initial version number value of the data record in the resource data table.

[0108] End version number value: the maximum version number value, generally 2 to the power of n.

[0109] Version number increase rate: The increase rate of the version number value, generally 1, that is, it increases by 1 each time.

[0110] Creation Date: The current creation date.

[0111] The specific fields of the version basic information table are as follows Figure 2 shown.

[0112] (2) Create a version history table: Save the record information of all versions in the version control process. The table records the information when the version is initialized and each time the version changes. The table fields include:

[0113] Change time: The specific time when version control is performed.

[0114] Change version number: The change version number corresponding to the change time. The resource data of the corresponding date can be found through this version number.

[0115] Creation Date: The current creation date.

[0116] The specific fields of the version history table are as follows Figure 3 shown.

[0117] More specifically, the initialization of two tables that need to be version controlled is as follows:

[0118] Initialize the records of the version management type table: initialize a version basic information record and a version history record: the version basic information record initialization data is: start version number value = 1, end version number value = 9223372036854775807, version number increase rate = 1, creation date = current creation date (2023 / 06 / 12); the version history record initialization data is: change time = current time (such as 2023 / 06 / 12 15:00:00), change version number = 1 (that is, the start version number value initialized in the "Version Basic Information Table"), creation date = current creation date (2023 / 06 / 12).

[0119] More specifically, after creating and initializing the basic version information table and the version history record table, the following steps are further included:

[0120] Create a resource data table: Based on the resource data obtained from the previous step, sort out which types of resource data need to be versioned, including: energy storage power station information, energy storage power station PCS information, energy storage power station battery stack information, energy storage power station switch information, energy storage power station transformer information, energy storage power station bus information, etc. Create a resource model table for each type of resource data. Each resource model table field must contain: resource unique flag, resource name, resource creation date, start version number, end version number. Other optional fields in the resource model table are the respective attributes of each type of resource data.

[0121] Initialize the records of the resource data table: After collecting the resource data table, initialize the resource data table. The start version number and the end version number are the initialization values ​​of the "Version Basic Information Table". For example, the initial data of the energy storage power station information table is as follows: Figure 4 shown.

[0122] S01: receiving a data operation instruction; wherein the data operation instruction includes querying data, adding data, modifying data or deleting data.

[0123] S02: According to the data operation instruction, the preset resource data table is operated, and the data in the preset version basic information table and the preset version history record table are modified.

[0124] As a preferred embodiment of the first embodiment, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0125] Resource model management can manage the query, addition, modification, and deletion operations of resource models. The management of resource models should not be affected by other business data, and should be highly cohesive and loosely coupled. When other businesses interact with resource model management, resource model data can be queried without providing any business data. Resource model operations mainly include the following:

[0126] Query: Query the specific resource data corresponding to the specified date, mainly including the following steps: ①According to the specified date, obtain the data set in the version history record table that is less than or equal to the specified date; ②Sort the obtained data set by change time from large to small, and obtain the change version number field value of the record with the longest change time; ③According to the obtained change version number value, obtain the records in the resource model data table with the condition: start version number <= change version number <= end version number; ④Return to step 3 to query the record set, which is the resource data corresponding to the specified date.

[0127] When the data operation instruction is to query data, the present application first determines the preset time point of the query, and then accurately finds all change records up to that time point through the preset version history record table. By screening out the maximum version number whose change time is less than or equal to the preset time, the system can ensure that the provided data is an accurate snapshot of the user's query time. This method not only improves the response speed of the query operation and the accuracy of the data, but also enhances the traceability of the data and the transparency of the system by maintaining a clear change history record. In addition, this query mechanism also facilitates the subsequent data analysis, audit tracking and troubleshooting of the system, thereby playing a vital role in the operation and maintenance of the power system. Therefore, the present application improves the accuracy and efficiency of data retrieval, enhances the reliability of data management, and optimizes the user experience of system operation.

[0128] Add: Add a new resource data, mainly including the following steps: ①According to the added date, obtain the set of records in the version history record table that are less than or equal to the added date, sort the obtained record set according to the change time from large to small and obtain the change time, and obtain the change version number field value of the record with the longest change time; ②Query the version basic information table to obtain the version number growth rate value and the end version number field value; ③Write the new resource data into the resource model data table, set the start version number to the change version number field value obtained in step 1 + 1, and the end version number to the end version number field obtained in the second step; ④Add a new data in the version history record table, set the change date to the current added date time, and set the change version number to the change version number field value obtained in the first step + 1.

[0129] This application provides an efficient data consistency guarantee mechanism for large-scale energy storage resource management by accurately controlling the update of version information and historical records. When new data is added, the system first determines the specific date of the new data, and searches for all previous change records in the preset version history record table to obtain the current maximum change version number and the corresponding end version number. This process ensures the continuity and accuracy of the version number. Subsequently, the system adds new resource data to the preset resource data table and updates the preset version history record table to record the detailed information and new version number of the new data. The beneficial effect of this method is that it not only maintains a clear historical track of data changes, which is convenient for future queries and audits, but also enhances the consistency and reliability of data by ensuring that each data addition is strictly carried out in accordance with the version control process. In addition, clear version control also helps to improve the automation level of data management and reduce human errors, thereby playing a vital role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data management, enhances the traceability of data and the stability of the system.

[0130] Modification: Change the attribute information of the specified resource data, such as resource name, resource type and other data, mainly including the following steps: ① Query the resource data that needs to be changed according to the conditions and date. For specific queries, see the query steps in the previous link; ② Query the basic information table of the version to obtain the value of the version number increase and the end version number; ③ Query the version history table to obtain the data set in the table that is less than or equal to the specified date, sort the set from large to small according to the change date, obtain the record with the largest date after sorting, and obtain its change version number value; ④ Set the end version number of the resource model data queried in step 1 to the change version number value of the third step + 1, that is, the end version number = the change version number; ⑤ Add a new resource data in the resource data table, the start version number of the new resource data is the change version number + 1, that is, the start version number is = the change version number + 1, the end version number is the maximum version number value in the second step, that is, the maximum version number = the end version number, and the resource data attributes are set to the changed resource data attributes; ⑥ Add a new data in the version history table, set the change date to the current change date time, and set the change version number to the change version number field value obtained in the third step + 1.

[0131] This application realizes the precise management of large-scale energy storage resources by synchronously updating the basic version information table and the preset version history record table when the resource data changes. Specifically, when modifying resource data, the system first queries the current version number growth rate and the end version number to ensure the continuity of version control. Subsequently, the system finds the latest version record in the preset version history record table and determines the version number benchmark for the modification operation. By updating the end version number in the preset resource data table and adding a resource information record with a new version number, the system ensures that each modification is accurately recorded and tracked. Finally, the newly added records in the preset version history record table further ensure the traceability of the changes. The beneficial effect of this method is that it not only improves the accuracy and reliability of data management, avoids conflicts and inconsistencies between data versions, but also enhances the transparency and auditing capabilities of the system through detailed historical records. In addition, this refined version control mechanism helps to quickly locate and roll back to a specific version of data, thereby playing a vital role in the operation and maintenance of the power system, and significantly improving the overall stability and maintenance efficiency of the system.

[0132] Deletion: When a piece of resource data needs to be deleted, the following steps are mainly included: ①: Query the resource data that needs to be changed according to the conditions and dates. For specific queries, see the query steps; ② Query the version history table, obtain the data set in the table that is less than or equal to the specified date, and sort the set from large to small according to the change date. After sorting, obtain the record with the largest date and obtain its change version number value; ③ Set the end version number of the resource data obtained in step 1 to the change version number value obtained in step 2; ④ Add a new piece of data to the version history table, the change date is the current change date, and the change version number is set to the change version number obtained in step 2 + 1.

[0133] This application achieves effective management of large-scale energy storage resources by updating the preset version history table when performing a deletion operation. Specifically, when deleting resource data, the system first searches the preset version history table for all records whose change time is less than or equal to the deletion operation date to determine the current maximum change version number. This step ensures that the system can identify the accurate version baseline corresponding to the deletion operation. Subsequently, the system updates the end version number of the resource data to this maximum change version number, clearly marking the end point of the life cycle of the resource data. In addition, the system adds a new record to the preset version history table to record the specific version number and date of the deletion operation. This new record not only provides a basis for future data recovery and auditing, but also ensures the integrity and continuity of the version history. This application improves the accuracy of data management and ensures the consistency and integrity of the data. At the same time, by maintaining a detailed version history record, it enhances the traceability and transparency of the system, providing strong support for the stable operation and efficient maintenance of the power system.

[0134] As a preferred embodiment of the first embodiment, after operating the preset resource data table according to the data operation instruction and modifying the data in the preset version basic information table and the preset version history record table, it also includes displaying resource data, specifically:

[0135] Resource model display and operation mainly rely on various operation capabilities of resource model management to display resource model data. Resource model display can display resource model data in a diversified way. In the power industry, it generally includes but is not limited to displaying resource data at all levels in a list form, displaying resource data with a hierarchical structure in a tree diagram form, and displaying resource data with topological relationships in a topological diagram form; resource model operations include adding, modifying, deleting and other operations on resource model data.

[0136] As a preferred embodiment of the first embodiment, taking the energy storage power station information modeling as an example, the power system resource modeling and version control process is specifically as follows:

[0137] 1. Enter the information of the tables that must be initialized into the database. The tables that must be initialized include: version basic information table, version history table, and the initialization data is visible Figure 5 , Figure 6 and Figure 7 As shown;

[0138] 2. The specific process of querying, adding, modifying or deleting the energy storage power station information is as follows:

[0139] Query: To query the data of the energy storage power station with a date of 2023 / 06 / 12 17:30, there are mainly the following steps: ①: Query the data set with a change date <= 2023 / 06 / 12 17:30 in the version history record table; ② Sort the acquired data set by change time from large to small, and obtain the change version number field value of the record with the longest change time. According to the resource model initialization, the change version number value is 1; ③ According to the change version number value obtained in step 2, obtain the record with the condition of start version number <= 1 <= end version number in the energy storage power station table; ④ Query the energy storage power station data of the specified date as id=stat i on_1 and id=stat i on_2.

[0140] New: Add a new energy storage power station resource data, where the power station name is Hengyi Power Plant 1, the power station id is stat ion_3, and the added date is 2023 / 06 / 13 15:30:00. It mainly includes the following steps: ①According to the added date, obtain the change time in the version history table <= 2023 / 06 / 13 15:30:00, sort the acquired record set according to the change time from large to small and obtain the change time, and obtain the change version number field value of the record with the longest change time. According to the resource model initialization link, the change version number is 1; ② query the basic version information table, obtain the version number increment value and the end version number field value. According to the resource model initialization link, the version number increment value is 1 and the end version number field value is 9223372036854775807; ③ write the newly added energy storage power station into the energy storage power station table, set the start version number to the change version number field value obtained in step 2 + 1, and the end version number to the end version number field value obtained in the second step; ④ add a new data in the version history record table, set the change date to the current added date and time, and set the change version number to the change version number field value obtained in the second step + 1. The newly added table data is as follows Figure 8 , Fig. 9 and Fig.10 shown.

[0141] Modification: Change the name of Baohu Energy Storage Power Station 1 to Baohu Energy Storage Power Station 2, and the change time is: 2023 / 06 / 13 15:40:00; mainly includes the following steps: ① Query the resource data that needs to be changed according to the conditions and dates. For specific queries, see the query operation in the previous link, and query the records of the power station name as Baohu Energy Storage Power Station 1; ② Query the basic version information table to obtain the version number increase value and the end version number value. The version number increase value is 1, and the end version number value is 9223372036854775807; ③ According to the change date, obtain the record set with the change time <= 2023 / 06 / 13 15:40:00 in the version history record table, according to The acquired record set is sorted from large to small according to the change time and the change time is obtained, and the change version number field value of the record with the longest change time is obtained. According to the newly added link, the change version number is 2; ④ Set the end version number of the resource model data queried in step 1 to the change version number value in the third step, that is, the end version number = 2; ⑤ Add a new resource data to the energy storage power station table data, the start version number of the new resource data is the change version number + 1, that is, the start version number is = 3, and the end version number is the end version number value in the second step, that is, the end version number value = 9223372036854775807, the power station name is: Baohu Energy Storage Power Station 2, the power station id is: stat ion_3; ⑥ Add a new data to the version history record table, the change date is set to the current change date and time, the change version number is set to the change version number field value obtained in the third step + 2, that is, the change version number is 3, the change date is 2023 / 06 / 13 15:40:00, and the changed data is as follows Fig.11 , Fig.12 and Fig.13 shown.

[0142] Delete: Delete the data of Hengyi Power Plant 1, and the deletion date is 2023 / 06 / 14 15:00:00. It mainly includes the following steps: ①: Query the resource data to be deleted according to the conditions and date. For specific queries, see the query steps; ②According to the change date, obtain the record set with the change time <= 2023 / 06 / 1415:00:00 in the version history record table, sort the obtained record set from large to small according to the change time and obtain the change time, and obtain the change version number field value of the record with the longest change time. According to the modification link, the change version number is 3; ③Set the end version number of the Hengyi Power Plant 1 data obtained in step one to the change version number value obtained in step two; ④Add a new data to the version history record table, the change date is the current deletion date and time, and the change version number is set to the change version number obtained in step two + 1, that is, the change version number is 4. The data in the table after deletion is as follows Fig.14 , Fig.15 and Fig.16 shown.

[0143] The present application realizes accurate operation of the resource data table by receiving data operation instructions including query, addition, modification and deletion, and updates the basic version information table and the version history record table at the same time, ensuring the consistency and integrity of the data. The present application not only improves maintainability by decoupling resource data from business data, but also reduces data redundancy and storage costs through version control. When executing data operation instructions, the present application first performs corresponding addition, deletion, modification and query operations in the resource data table, and then synchronously updates the basic version information table and the version history record table to record the detailed information and version changes of the operation. The present application improves the traceability of the data by recording the history of each data change in detail, so that problems can be quickly located and data can be restored when needed. In addition, by controlling the growth and end of the version number, the present application effectively avoids unnecessary duplication of data and optimizes the amount of data storage. Therefore, the present application improves the efficiency and accuracy of data management by highly decoupling resource data from business data and performing version control, so as to solve the problem that large-scale energy storage resources cannot be flexibly managed in the prior art.

[0144] Embodiment 2

[0145] Please refer to Fig.17 , which is a large-scale energy storage resource management device provided in an embodiment of the present application.

[0146] In this embodiment, the large-scale energy storage resource management device includes a receiving module 10 and an operating module 20 .

[0147] This application extracts resource data from business data for separate management and maintenance, and provides a complete lifecycle management for the resource model, providing version control functions for the addition, deletion, modification, and query of energy storage resources, avoiding multiple duplicate resource data in one day, and solving the problem of exponential growth of resource data over time, thereby reducing system construction costs.

[0148] Before conducting large-scale energy storage management, this application must first obtain a series of power system data, namely: sort out which resource model data need to be managed; the source of resource model data mainly includes but is not limited to c ime files, dt files, and other system databases in the power industry; according to the characteristics of the power industry, the resource data that usually need to be managed mainly includes but is not limited to physical equipment in the distribution, transmission, and power generation links; finally, according to the characteristics of the system, identify which resource data need to be version controlled. The principle of version control is generally to determine whether the resource data needs to be traced back according to time when the resource data is added, modified, or deleted. If traceback is required, version control is required.

[0149] Secondly, the resource data collected and sorted by the resource model is converted into unified, standardized resource model data and entered into the database table. The standardized, unified and standard resource model should include but not be limited to the resource unique identifier, resource name, resource creation date and other information. The resource data that needs to be version controlled should also include the start version number and the end version number information; the design of the database table should meet the requirements of the third normal form, and resource attributes can be added dynamically. The dynamic addition, deletion, modification and other operations of resource attributes should not be restricted to meet the scalability requirements.

[0150] Then create and initialize two tables that need version control, one is the version history table and the other is the version basic information table.

[0151] More specifically, the two tables that need to be version controlled are created as follows:

[0152] (1) Create a basic version information table: save the basic information of the version number. The table fields include:

[0153] Starting version number value: the initial version number value, usually 1. The initial version number value of the data record in the resource data table.

[0154] End version number value: the maximum version number value, generally 2 to the power of n.

[0155] Version number increase rate: The increase rate of the version number value, generally 1, that is, it increases by 1 each time.

[0156] Creation Date: The current creation date.

[0157] The specific fields of the version basic information table are as follows Figure 2 shown.

[0158] (2) Create a version history table: Save the record information of all versions in the version control process. The table records the information when the version is initialized and each time the version changes. The table fields include:

[0159] Change time: The specific time when version control is performed.

[0160] Change version number: The change version number corresponding to the change time. The resource data of the corresponding date can be found through this version number.

[0161] Creation Date: The current creation date.

[0162] The specific fields of the version history table are as follows Figure 3 shown.

[0163] More specifically, the initialization of two tables that need to be version controlled is as follows:

[0164] Initialize the records of the version management type table: initialize a version basic information record and a version history record: the version basic information record initialization data is: start version number value = 1, end version number value = 9223372036854775807, version number increase rate = 1, creation date = current creation date (2023 / 06 / 12); the version history record initialization data is: change time = current time (such as 2023 / 06 / 12 15:00:00), change version number = 1 (that is, the start version number value initialized in the "Version Basic Information Table"), creation date = current creation date (2023 / 06 / 12).

[0165] More specifically, after creating and initializing the basic version information table and the version history record table, the following steps are further included:

[0166] Create a resource data table: Based on the resource data obtained from the previous step, sort out which types of resource data need to be versioned, including: energy storage power station information, energy storage power station PCS information, energy storage power station battery stack information, energy storage power station switch information, energy storage power station transformer information, energy storage power station bus information, etc. Create a resource model table for each type of resource data. Each resource model table field must contain: resource unique flag, resource name, resource creation date, start version number, end version number. Other optional fields in the resource model table are the respective attributes of each type of resource data.

[0167] Initialize the records of the resource data table: After collecting the resource data table, initialize the resource data table. The start version number and the end version number are the initialization values ​​of the "Version Basic Information Table". For example, the initial data of the energy storage power station information table is as follows: Figure 4 shown.

[0168] The receiving module 10 is used to receive data operation instructions; wherein the data operation instructions include querying data, adding data, modifying data or deleting data.

[0169] The operation module 20 is used to operate the preset resource data table according to the data operation instruction, and modify the data in the preset version basic information table and the preset version history record table.

[0170] As a preferred embodiment of the second embodiment, the operation on the preset resource data table and the modification of the data in the preset version basic information table and the preset version history record table according to the data operation instruction are specifically as follows:

[0171] Resource model management can manage the query, addition, modification, and deletion operations of resource models. The management of resource models should not be affected by other business data, and should be highly cohesive and loosely coupled. When other businesses interact with resource model management, resource model data can be queried without providing any business data. Resource model operations mainly include the following:

[0172] Query: Query the specific resource data corresponding to the specified date, mainly including the following steps: ①According to the specified date, obtain the data set in the version history record table that is less than or equal to the specified date; ②Sort the obtained data set by change time from large to small, and obtain the change version number field value of the record with the longest change time; ③According to the obtained change version number value, obtain the records in the resource model data table with the condition: start version number <= change version number <= end version number; ④Return to step 3 to query the record set, which is the resource data corresponding to the specified date.

[0173] When the data operation instruction is to query data, the present application first determines the preset time point of the query, and then accurately finds all change records up to that time point through the preset version history record table. By screening out the maximum version number whose change time is less than or equal to the preset time, the system can ensure that the provided data is an accurate snapshot of the user's query time. This method not only improves the response speed of the query operation and the accuracy of the data, but also enhances the traceability of the data and the transparency of the system by maintaining a clear change history record. In addition, this query mechanism also facilitates the subsequent data analysis, audit tracking and troubleshooting of the system, thereby playing a vital role in the operation and maintenance of the power system. Therefore, the present application improves the accuracy and efficiency of data retrieval, enhances the reliability of data management, and optimizes the user experience of system operation.

[0174] Add: Add a new resource data, mainly including the following steps: ①According to the added date, obtain the set of records in the version history record table that are less than or equal to the added date, sort the obtained record set according to the change time from large to small and obtain the change time, and obtain the change version number field value of the record with the longest change time; ②Query the version basic information table to obtain the version number growth rate value and the end version number field value; ③Write the new resource data into the resource model data table, set the start version number to the change version number field value obtained in step 1 + 1, and the end version number to the end version number field obtained in the second step; ④Add a new data in the version history record table, set the change date to the current added date time, and set the change version number to the change version number field value obtained in the first step + 1.

[0175] This application provides an efficient data consistency guarantee mechanism for large-scale energy storage resource management by accurately controlling the update of version information and historical records. When new data is added, the system first determines the specific date of the new data, and searches for all previous change records in the preset version history record table to obtain the current maximum change version number and the corresponding end version number. This process ensures the continuity and accuracy of the version number. Subsequently, the system adds new resource data to the preset resource data table and updates the preset version history record table to record the detailed information and new version number of the new data. The beneficial effect of this method is that it not only maintains a clear historical track of data changes, which is convenient for future queries and audits, but also enhances the consistency and reliability of data by ensuring that each data addition is strictly carried out in accordance with the version control process. In addition, clear version control also helps to improve the automation level of data management and reduce human errors, thereby playing a vital role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data management, enhances the traceability of data and the stability of the system.

[0176] Modification: Change the attribute information of the specified resource data, such as resource name, resource type and other data, mainly including the following steps: ① Query the resource data that needs to be changed according to the conditions and date. For specific queries, see the query steps in the previous link; ② Query the basic information table of the version to obtain the value of the version number increase and the end version number; ③ Query the version history table to obtain the data set in the table that is less than or equal to the specified date, sort the set from large to small according to the change date, obtain the record with the largest date after sorting, and obtain its change version number value; ④ Set the end version number of the resource model data queried in step 1 to the change version number value of the third step + 1, that is, the end version number = the change version number; ⑤ Add a new resource data in the resource data table, the start version number of the new resource data is the change version number + 1, that is, the start version number is = the change version number + 1, the end version number is the maximum version number value in the second step, that is, the maximum version number = the end version number, and the resource data attributes are set to the changed resource data attributes; ⑥ Add a new data in the version history table, set the change date to the current change date time, and set the change version number to the change version number field value obtained in the third step + 1.

[0177] This application realizes the precise management of large-scale energy storage resources by synchronously updating the basic version information table and the preset version history record table when the resource data changes. Specifically, when modifying resource data, the system first queries the current version number growth rate and the end version number to ensure the continuity of version control. Subsequently, the system finds the latest version record in the preset version history record table and determines the version number benchmark for the modification operation. By updating the end version number in the preset resource data table and adding a resource information record with a new version number, the system ensures that each modification is accurately recorded and tracked. Finally, the newly added records in the preset version history record table further ensure the traceability of the changes. The beneficial effect of this method is that it not only improves the accuracy and reliability of data management, avoids conflicts and inconsistencies between data versions, but also enhances the transparency and auditing capabilities of the system through detailed historical records. In addition, this refined version control mechanism helps to quickly locate and roll back to a specific version of data, thereby playing a vital role in the operation and maintenance of the power system, and significantly improving the overall stability and maintenance efficiency of the system.

[0178] Deletion: When a piece of resource data needs to be deleted, the following steps are mainly included: ①: Query the resource data that needs to be changed according to the conditions and dates. For specific queries, see the query steps; ② Query the version history table, obtain the data set in the table that is less than or equal to the specified date, and sort the set from large to small according to the change date. After sorting, obtain the record with the largest date and obtain its change version number value; ③ Set the end version number of the resource data obtained in step 1 to the change version number value obtained in step 2; ④ Add a new piece of data to the version history table, the change date is the current change date, and the change version number is set to the change version number obtained in step 2 + 1.

[0179] This application achieves effective management of large-scale energy storage resources by updating the preset version history table when performing a deletion operation. Specifically, when deleting resource data, the system first searches the preset version history table for all records whose change time is less than or equal to the deletion operation date to determine the current maximum change version number. This step ensures that the system can identify the accurate version baseline corresponding to the deletion operation. Subsequently, the system updates the end version number of the resource data to this maximum change version number, clearly marking the end point of the life cycle of the resource data. In addition, the system adds a new record to the preset version history table to record the specific version number and date of the deletion operation. This new record not only provides a basis for future data recovery and auditing, but also ensures the integrity and continuity of the version history. This application improves the accuracy of data management and ensures the consistency and integrity of the data. At the same time, by maintaining a detailed version history record, it enhances the traceability and transparency of the system, providing strong support for the stable operation and efficient maintenance of the power system.

[0180] As a preferred embodiment of the second embodiment, after operating the preset resource data table according to the data operation instruction and modifying the data in the preset version basic information table and the preset version history record table, it also includes displaying resource data, specifically:

[0181] Resource model display and operation mainly rely on various operation capabilities of resource model management to display resource model data. Resource model display can display resource model data in a diversified way. In the power industry, it generally includes but is not limited to displaying resource data at all levels in a list form, displaying resource data with a hierarchical structure in a tree diagram form, and displaying resource data with topological relationships in a topological diagram form; resource model operations include adding, modifying, deleting and other operations on resource model data.

[0182] As a preferred embodiment of the second embodiment, taking the energy storage power station information modeling as an example, the process of power system resource modeling and version control is specifically as follows:

[0183] 1. Enter the information of the tables that must be initialized into the database. The tables that must be initialized include: version basic information table, version history table, and the initialization data is visible Figure 5 , Figure 6 and Figure 7 As shown;

[0184] 2. The specific process of querying, adding, modifying or deleting the energy storage power station information is as follows:

[0185] Query: To query the data of the energy storage power station with a date of 2023 / 06 / 12 17:30, there are mainly the following steps: ①: Query the data set with a change date <= 2023 / 06 / 12 17:30 in the version history record table; ② Sort the acquired data set by change time from large to small, and obtain the change version number field value of the record with the longest change time. According to the resource model initialization, the change version number value is 1; ③ According to the change version number value obtained in step 2, obtain the record with the condition of start version number <= 1 <= end version number in the energy storage power station table; ④ Query the energy storage power station data of the specified date as id=stat i on_1 and id=stat ion_2.

[0186] New: Add a new energy storage power station resource data, where the power station name is Hengyi Power Plant 1, the power station id is station_3, and the added date is 2023 / 06 / 13 15:30:00. It mainly includes the following steps: ①According to the added date, obtain the change time in the version history table <= 2023 / 06 / 13 15:30:00, sort the acquired record set according to the change time from large to small and obtain the change time, and obtain the change version number field value of the record with the longest change time. According to the resource model initialization link, the change version number is 1; ② query the basic version information table, obtain the version number increment value and the end version number field value. According to the resource model initialization link, the version number increment value is 1 and the end version number field value is 9223372036854775807; ③ write the newly added energy storage power station into the energy storage power station table, set the start version number to the change version number field value obtained in step 2 + 1, and the end version number to the end version number field value obtained in the second step; ④ add a new data in the version history record table, set the change date to the current added date and time, and set the change version number to the change version number field value obtained in the second step + 1. The newly added table data is as follows Figure 8 , Fig. 9 and Fig.10 shown.

[0187] Modification: Change the name of Baohu Energy Storage Power Station 1 to Baohu Energy Storage Power Station 2, and the change time is: 2023 / 06 / 13 15:40:00; mainly includes the following steps: ① Query the resource data that needs to be changed according to the conditions and dates. For specific queries, see the query operation in the previous link, and query the records of the power station name as Baohu Energy Storage Power Station 1; ② Query the basic version information table to obtain the version number increase value and the end version number value. The version number increase value is 1, and the end version number value is 9223372036854775807; ③ According to the change date, obtain the record set with the change time <= 2023 / 06 / 13 15:40:00 in the version history record table, according to The acquired record set is sorted from large to small according to the change time and the change time is obtained, and the change version number field value of the record with the longest change time is obtained. According to the newly added link, the change version number is 2; ④ Set the end version number of the resource model data queried in step 1 to the change version number value in the third step, that is, the end version number = 2; ⑤ Add a new resource data to the energy storage power station table data, the start version number of the new resource data is the change version number + 1, that is, the start version number is = 3, and the end version number is the end version number value in the second step, that is, the end version number value = 9223372036854775807, the power station name is: Baohu Energy Storage Power Station 2, the power station id is: stat ion_3; ⑥ Add a new data to the version history record table, the change date is set to the current change date and time, the change version number is set to the change version number field value obtained in the third step + 2, that is, the change version number is 3, the change date is 2023 / 06 / 13 15:40:00, and the changed data is as follows Fig.11 , Fig.12 and Fig.13 shown.

[0188] Delete: Delete the data of Hengyi Power Plant 1, and the deletion date is 2023 / 06 / 14 15:00:00. It mainly includes the following steps: ①: Query the resource data to be deleted according to the conditions and date. For specific queries, see the query steps; ②According to the change date, obtain the record set with the change time <= 2023 / 06 / 1415:00:00 in the version history record table, sort the obtained record set from large to small according to the change time and obtain the change time, and obtain the change version number field value of the record with the longest change time. According to the modification link, the change version number is 3; ③Set the end version number of the Hengyi Power Plant 1 data obtained in step one to the change version number value obtained in step two; ④Add a new data to the version history record table, the change date is the current deletion date and time, and the change version number is set to the change version number obtained in step two + 1, that is, the change version number is 4. The data in the table after deletion is as follows Fig.14 , Fig.15 and Fig.16 shown.

[0189] The device uses two modules to divide the work and coordinate the work to better manage the large-scale energy storage data. The application realizes the precise operation of the resource data table by receiving data operation instructions including query, addition, modification and deletion, and updates the basic information table of the version and the history record table of the version to ensure the consistency and integrity of the data. The application not only improves the maintainability by decoupling the resource data from the business data, but also reduces the data redundancy and storage cost through version control. When executing the data operation instruction, the application first performs the corresponding addition, deletion, modification and query operations in the resource data table, and then synchronously updates the basic information table of the version and the history record table of the version to record the detailed information and version changes of the operation. The application improves the traceability of the data by recording the history of each data change in detail, so that the problem can be quickly located and the data can be restored when needed. In addition, by controlling the growth and end of the version number, the application effectively avoids unnecessary duplication of data and optimizes the data storage capacity. Therefore, the application improves the efficiency and accuracy of data management by highly decoupling the resource data from the business data and performing version control, so as to solve the problem that the large-scale energy storage resources cannot be flexibly managed in the prior art.

[0190] The specific embodiments described above further illustrate the purpose, technical solutions and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. It is particularly pointed out that for those skilled in the art, any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for managing large-scale energy storage resources, characterized in that: include: Receiving data operation instructions; wherein the data operation instructions include querying data, adding data, modifying data or deleting data; According to the data operation instruction, the preset resource data table is operated, and the data in the preset version basic information table and the preset version history record table are modified; The preset resource data table is used to store resource model data decoupled from business data, and the preset version basic information table and the preset version history record table are used to record version information of the preset resource data table; The first resource data of the preset resource data table includes a first resource flag, a first resource name, a first creation date, a first start version number and a first end version number; The data of the preset version basic information table includes a first starting version number, a first ending version number, a first version number increment, and a first creation date; The data of the preset version history record table includes a first change time, a first change version number and a first creation date.

2. The large-scale energy storage resource management method according to claim 1, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to query data; Acquire a first preset time of the query data; According to a preset version history record table and a first preset time, query the preset version history record table for all first records whose first change time is less than or equal to the first preset time; According to the first record, determining a maximum value in the first change time in the preset version history record table, and obtaining a change version number of the maximum value; According to the changed version number of the maximum value, the first resource data corresponding to the changed version number of the maximum value is retrieved from a preset resource data table.

3. The large-scale energy storage resource management method according to claim 1, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to add new data; Acquire second resource data of the newly added data; According to the date of the second resource data, obtaining in a preset version history record table all second records whose first change time is less than or equal to the date of the second resource data; According to the second record, obtaining a first maximum changed version number in a preset version history record table; According to the first maximum changed version number, obtaining a second end version number of the first maximum changed version number in the version basic information table; Adding the second resource data to the preset resource data table; wherein the value of the start version number of the second resource data is the value of the maximum change version number, and the value of the end version number of the second resource data is the value of the second end version number; A record of the second resource data is added to the preset version history record table; wherein the second creation date of the record of the second resource data is the date of the second resource data, and the second change version number of the record of the second resource data is the value of the first maximum change version number plus one.

4. The large-scale energy storage resource management method according to claim 1, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to modify data; Query the version number increment and the end version number of the modified data in the preset version basic information table; Searching the preset version history record table for a third record whose first change time is less than or equal to the time of modifying the data, and searching the third record for the second largest change version number; Update the information of the modified data in a preset resource data table; wherein the end version number of the modified data is modified to the second largest change version number plus one; Adding the second resource information of the modified data to the preset resource data table; wherein the start version number of the second resource information is the second largest change version number plus one, and the end version number of the second resource information is the end version number of the modified data; A record of the modified data is newly added to the preset version history record table; wherein, the third change time of the record of the modified data is the time when the data was modified, the third change version number of the record of the modified data is the second largest change version number plus one, and the third creation date of the record of the modified data is the date of the modified data.

5. The large-scale energy storage resource management method according to claim 1, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to delete data; Obtaining the third largest changed version number whose first change time is less than or equal to the date of deleting the data in a preset version history record table; In a preset version history record table, updating the end version number of the deleted data to the third largest changed version number; A record of the deleted data is newly added in the preset version history record table; wherein the fourth change date of the record of the deleted data is the date of the deleted data, and the fourth change version number of the deleted data is the third maximum change version number plus one.

6. A large-scale energy storage resource management device, characterized in that: It includes a receiving module and an operating module; The receiving module is used to receive data operation instructions; wherein the data operation instructions include querying data, adding data, modifying data or deleting data; The operation module is used to operate the preset resource data table according to the data operation instruction, and modify the data in the preset version basic information table and the preset version history record table; The preset resource data table is used to store resource model data decoupled from business data, and the preset version basic information table and the preset version history record table are used to record version information of the preset resource data table; The first resource data of the preset resource data table includes a first resource flag, a first resource name, a first creation date, a first start version number and a first end version number; The data of the preset version basic information table includes a first starting version number, a first ending version number, a first version number increment, and a first creation date; The data of the preset version history record table includes a first change time, a first change version number and a first creation date.

7. The large-scale energy storage resource management device according to claim 6, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to query data; Acquire a first preset time of the query data; According to a preset version history record table and a first preset time, query the preset version history record table for all first records whose first change time is less than or equal to the first preset time; According to the first record, determining a maximum value in the first change time in the preset version history record table, and obtaining a change version number of the maximum value; According to the changed version number of the maximum value, the first resource data corresponding to the changed version number of the maximum value is retrieved from a preset resource data table.

8. The large-scale energy storage resource management device according to claim 6, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to add new data; Acquire second resource data of the newly added data; According to the date of the second resource data, obtaining in a preset version history record table all second records whose first change time is less than or equal to the date of the second resource data; According to the second record, obtaining a first maximum changed version number in a preset version history record table; According to the first maximum changed version number, obtaining a second end version number of the first maximum changed version number in the version basic information table; Adding the second resource data to the preset resource data table; wherein the value of the start version number of the second resource data is the value of the maximum change version number, and the value of the end version number of the second resource data is the value of the second end version number; A record of the second resource data is added to the preset version history record table; wherein the second creation date of the record of the second resource data is the date of the second resource data, and the second change version number of the record of the second resource data is the value of the first maximum change version number plus one.

9. The large-scale energy storage resource management device according to claim 6, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to modify data; Query the version number increment and the end version number of the modified data in the preset version basic information table; Searching the preset version history record table for a third record whose first change time is less than or equal to the time of modifying the data, and searching the third record for the second largest change version number; Update the information of the modified data in a preset resource data table; wherein the end version number of the modified data is modified to the second largest change version number plus one; Adding the second resource information of the modified data to the preset resource data table; wherein the start version number of the second resource information is the second largest change version number plus one, and the end version number of the second resource information is the end version number of the modified data; A record of the modified data is newly added to the preset version history record table; wherein, the third change time of the record of the modified data is the time when the data was modified, the third change version number of the record of the modified data is the second largest change version number plus one, and the third creation date of the record of the modified data is the date of the modified data.

10. The large-scale energy storage resource management device according to claim 6, characterized in that: The operation of the preset resource data table according to the data operation instruction and the modification of the data in the preset version basic information table and the preset version history record table are specifically as follows: When the data operation instruction is to delete data; Obtaining the third largest changed version number whose first change time is less than or equal to the date of deleting the data in a preset version history record table; In a preset version history record table, updating the end version number of the deleted data to the third largest changed version number; A record of the deleted data is newly added in the preset version history record table; wherein the fourth change date of the record of the deleted data is the date of the deleted data, and the fourth change version number of the deleted data is the third maximum change version number plus one.

Images