Method and apparatus for managing large-scale energy storage resources

Abstract

Disclosed in the present invention are a method and apparatus for managing large-scale energy storage resources. In the present application, a data operation instruction is received to execute a query, addition, modification or deletion operation on a resource data table, and a basic version information table and a version history record table are synchronously updated, so as to maintain a resource model data version management system that is decoupled from service data. The system can record in detail an identifier, a name and a creation date of each resource, and a starting value and an ending value of a version number of each resource, while tracking the time and version number for each data change. In the present application, resource data and service data are highly decoupled, and version control is performed, such that the efficiency and accuracy of data management are improved, thereby solving the problem in the prior art of it not being possible to flexibly manage large-scale energy storage resources.

Description

A method and device for large-scale energy storage resource management Technical Field

[0001] This invention relates to the field of large-scale energy storage resource management, and in particular to a method and apparatus for large-scale energy storage resource management. Background Technology

[0002] In the construction of large-scale energy storage systems, energy storage resources typically require version rollback functionality. When the system switches to a specific point in time, the energy storage resources need to be able to revert to their state at that specific time, meaning the quantity, attributes, and other information of the energy storage resources must correspond to that point in time. To meet this requirement, most current systems typically tightly couple energy storage resource data with business data, binding the energy storage resource data to the corresponding business data at a specific time to form a complete dataset. This leads to difficulties in energy storage resource management and makes it unmaintainable. Over time, a large amount of redundant energy storage resource data accumulates, especially in advanced predictive analytics functions where multiple sets of duplicate resource data may be generated daily, resulting in exponential growth in data volume. This poses a significant challenge to the storage costs of system construction, rendering existing technologies incapable of flexibly managing large-scale energy storage resources. Summary of the Invention

[0003] This invention provides a method and apparatus for large-scale energy storage resource management to solve the problem that existing technologies cannot flexibly manage large-scale energy storage resources.

[0004] Firstly, this application provides a method for large-scale energy storage resource management, including:

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

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

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

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

[0009] The data in the preset version basic information table includes the first start version number, the first end version number, the first version number increment, and the first creation date;

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

[0011] This application enables precise manipulation of resource data tables by receiving data operation instructions, including query, add, modify, and delete commands. Simultaneously, it updates the basic version information table and version history table, ensuring data consistency and integrity. By decoupling resource data from business data, this application not only improves maintainability but also reduces data redundancy and lowers storage costs through version control. When executing data operation instructions, this application first performs corresponding add, delete, modify, and query operations in the resource data table, and then synchronously updates the basic version information table and version history table, recording detailed operation information and version changes. By meticulously recording the history of each data change, this application improves data traceability, enabling rapid problem location and data recovery when needed. Furthermore, by controlling the growth and termination of version numbers, this application effectively avoids unnecessary data duplication, optimizing data storage capacity. Therefore, by highly decoupling resource data from business data and implementing version control, this application improves the efficiency and accuracy of data management, addressing the problem of inflexible management of large-scale energy storage resources in existing technologies.

[0012] In a preferred embodiment of the first aspect, the step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

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

[0014] The first preset time for obtaining the queried data;

[0015] Based on the preset version history table and the first preset time, query all first records in the preset version history table whose first change time is less than or equal to the first preset time;

[0016] Based on the first record, determine the maximum value in the first change time in the preset version history table, and obtain the change version number of the maximum value;

[0017] Based on the version number of the maximum value, retrieve the first resource data corresponding to the version number of the maximum value from the preset resource data table.

[0018] In this preferred embodiment, when the data operation instruction is to query data, this application first determines the preset time point for the query, and then accurately finds all change records up to that time point through a preset version history table. By filtering out the largest 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 and accuracy of query operations, but also enhances data traceability and system transparency by maintaining a clear change history. In addition, this query mechanism also facilitates subsequent data analysis, audit tracking, and fault diagnosis, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data retrieval, enhances the reliability of data management, and optimizes the user experience of system operation.

[0019] In a preferred embodiment of the first aspect, the step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

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

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

[0022] Based on the date of the second resource data, retrieve all second records from the preset version history table that have a first change time less than or equal to the date of the second resource data;

[0023] Based on the second record, obtain the first maximum change version number from the preset version history table;

[0024] Based on the first maximum change version number, obtain the second end version number of the first maximum change version number from the version basic information table;

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

[0026] Add a new record of the second resource data to the preset version history 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, this application provides an efficient data consistency assurance mechanism for large-scale energy storage resource management by precisely controlling the updates of version information and historical records. When new data is added, the system first determines the specific date of the added data and then searches for all previous change records in a preset version history table to obtain the current maximum version number and the corresponding end version number. This process ensures the continuity and accuracy of version numbers. Subsequently, the system adds new resource data to a preset resource data table and updates the preset version history table, recording the detailed information of the added data and the new version number. The beneficial effects of this method are that it not only maintains a clear data change history trajectory, facilitating future queries and audits, but also enhances data consistency and reliability by ensuring that each data addition strictly follows the version control process. In addition, explicit version control also helps to improve the automation level of data management and reduce human error, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data management, enhances data traceability, and improves system stability.

[0028] In a preferred embodiment of the first aspect, the step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

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

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

[0031] In the preset version history table, query the third record in the first change time that is less than or equal to the time of the modified data, and then query the second maximum change version number in the third record;

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

[0033] Add 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 maximum 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] Add a new record of the modified data to the preset version history table; wherein, the third change time of the modified data record is the time of the data modification, the third change version number of the modified data record is the second maximum change version number plus one, and the third creation date of the modified data record is the date of the data modification.

[0035] In this preferred embodiment, this application achieves precise management of large-scale energy storage resources by synchronously updating the basic version information table and a preset version history table when resource data changes. Specifically, when modifying resource data, the system first queries the current version number increment and end version number to ensure the continuity of version control. Subsequently, the system finds the latest version record in the preset version history table, determining the version number baseline for the modification operation. By updating the end version number in the preset resource data table and adding a new resource information record with the new version number, the system ensures that each modification is accurately recorded and tracked. Finally, the newly added record in the preset version history table further ensures the traceability of changes. The beneficial effects of this method are that it not only improves the accuracy and reliability of data management and 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 data to a specific version, thus playing a crucial role in the operation and maintenance of the power system and significantly improving the overall stability and maintenance efficiency of the system.

[0036] In a preferred embodiment of the first aspect, the step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

[0037] When the data manipulation command is to delete data;

[0038] Obtain the third largest change version number from the preset version history table, where the first change time is less than or equal to the date of the deleted data;

[0039] In the preset version history table, the end version number of the deleted data is updated to the third largest change version number;

[0040] Add a new record of the deleted data to the preset version history table; wherein, the fourth change date of the record of the deleted data is the date of deletion of the 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, this application achieves effective management of large-scale energy storage resources by updating a 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 resource data's lifecycle. In addition, the system adds a new record to the preset version history table, recording 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, ensures data consistency and integrity, and enhances the traceability and transparency of the system by maintaining a detailed version history, providing strong support for the stable operation and efficient maintenance of the power system.

[0042] Secondly, this application provides a large-scale energy storage resource management device. The large-scale energy storage resource management device 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 on the preset resource data table according to the data operation instructions, and modify the data in the preset version basic information table and the preset version history table.

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

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

[0047] The data in the preset version basic information table includes the first start version number, the first end version number, the first version number increment, and the first creation date;

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

[0049] This device utilizes two modules that work in a coordinated manner to better manage large-scale energy storage data. By receiving data operation commands, including query, add, modify, and delete, this application achieves precise operations on the resource data table, while simultaneously updating the version basic information table and version history table, ensuring data consistency and integrity. By decoupling resource data from business data, this application not only improves maintainability but also reduces data redundancy and lowers storage costs through version control. When executing data operation commands, this application first performs corresponding add, delete, modify, and query operations in the resource data table, and then synchronously updates the version basic information table and version history table, recording detailed operation information and version changes. By meticulously recording the history of each data change, this application improves data traceability, enabling rapid problem location and data recovery when needed. Furthermore, by controlling the growth and termination of version numbers, this application effectively avoids unnecessary data duplication, optimizing data storage capacity. Therefore, by highly decoupling resource data from business data and implementing version control, this application improves the efficiency and accuracy of data management, addressing the problem of the inability to flexibly manage large-scale energy storage resources in existing technologies.

[0050] As a preferred embodiment of the second aspect, the step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

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

[0052] The first preset time for obtaining the queried data;

[0053] Based on the preset version history table and the first preset time, query all first records in the preset version history table whose first change time is less than or equal to the first preset time;

[0054] Based on the first record, determine the maximum value in the first change time in the preset version history table, and obtain the change version number of the maximum value;

[0055] Based on the version number of the maximum value, retrieve the first resource data corresponding to the version number of the maximum value from the preset resource data table.

[0056] In this preferred embodiment, when the data operation instruction is to query data, this application first determines the preset time point for the query, and then accurately finds all change records up to that time point through a preset version history table. By filtering out the largest 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 and accuracy of query operations, but also enhances data traceability and system transparency by maintaining a clear change history. In addition, this query mechanism also facilitates subsequent data analysis, audit tracking, and fault diagnosis, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this 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 step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

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

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

[0060] Based on the date of the second resource data, retrieve all second records from the preset version history table that have a first change time less than or equal to the date of the second resource data;

[0061] Based on the second record, obtain the first maximum change version number from the preset version history table;

[0062] Based on the first maximum change version number, obtain the second end version number of the first maximum change version number from the version basic information table;

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

[0064] Add a new record of the second resource data to the preset version history 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, this application provides an efficient data consistency assurance mechanism for large-scale energy storage resource management by precisely controlling the updates of version information and historical records. When new data is added, the system first determines the specific date of the added data and then searches for all previous change records in a preset version history table to obtain the current maximum version number and the corresponding end version number. This process ensures the continuity and accuracy of version numbers. Subsequently, the system adds new resource data to a preset resource data table and updates the preset version history table, recording the detailed information of the added data and the new version number. The beneficial effects of this method are that it not only maintains a clear data change history trajectory, facilitating future queries and audits, but also enhances data consistency and reliability by ensuring that each data addition strictly follows the version control process. In addition, explicit version control also helps to improve the automation level of data management and reduce human error, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data management, enhances data traceability, and improves system stability.

[0066] As a preferred embodiment of the second aspect, the step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

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

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

[0069] In the preset version history table, query the third record in the first change time that is less than or equal to the time of the modified data, and then query the second maximum change version number in the third record;

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

[0071] Add 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 maximum 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] Add a new record of the modified data to the preset version history table; wherein, the third change time of the modified data record is the time of the data modification, the third change version number of the modified data record is the second maximum change version number plus one, and the third creation date of the modified data record is the date of the data modification.

[0073] In this preferred embodiment, this application achieves precise management of large-scale energy storage resources by synchronously updating the basic version information table and a preset version history table when resource data changes. Specifically, when modifying resource data, the system first queries the current version number increment and end version number to ensure the continuity of version control. Subsequently, the system finds the latest version record in the preset version history table, determining the version number baseline for the modification operation. By updating the end version number in the preset resource data table and adding a new resource information record with the new version number, the system ensures that each modification is accurately recorded and tracked. Finally, the newly added record in the preset version history table further ensures the traceability of changes. The beneficial effects of this method are that it not only improves the accuracy and reliability of data management and 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 data to a specific version, thus playing a crucial 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 step of operating on a preset resource data table and modifying data in a preset version basic information table and a preset version history table according to the data operation instructions specifically includes:

[0075] When the data manipulation command is to delete data;

[0076] Obtain the third largest change version number from the preset version history table, where the first change time is less than or equal to the date of the deleted data;

[0077] In the preset version history table, the end version number of the deleted data is updated to the third largest change version number;

[0078] Add a new record of the deleted data to the preset version history table; wherein, the fourth change date of the record of the deleted data is the date of deletion of the 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, this application achieves effective management of large-scale energy storage resources by updating a 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 resource data's lifecycle. In addition, the system adds a new record to the preset version history table, recording 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, ensures data consistency and integrity, and enhances the traceability and transparency of the system by maintaining a detailed version history, providing strong support for the stable operation and efficient maintenance of the power system. Attached Figure Description

[0080] Figure 1: A flowchart illustrating an embodiment of the large-scale energy storage resource management method provided in this application;

[0081] Figure 2: A schematic diagram of the structure of an embodiment of the initialization version basic information table provided in this application;

[0082] Figure 3: A schematic diagram of the structure of an embodiment of the initialization version history table provided in this application;

[0083] Figure 4: A schematic diagram of the structure of an embodiment of creating a version history table provided in this application;

[0084] Figure 5: A schematic diagram of the structure of an embodiment of the basic information table of the version of the initialization energy storage power station information provided in this application;

[0085] Figure 6: A schematic diagram of the structure of an embodiment of the version history table for initializing energy storage power station information provided in this application;

[0086] Figure 7: A schematic diagram of the structure of an embodiment of the initial data table for creating energy storage power station information provided in this application;

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

[0088] Figure 9: A schematic diagram of the structure of an embodiment of the version history table of the newly added energy storage power station information provided in this application;

[0089] Figure 10: A schematic diagram of the structure of an embodiment of the energy storage power station table data table for the newly added energy storage power station information provided in this application;

[0090] Figure 11: A schematic diagram of the structure of an embodiment of the basic information table of the modified energy storage power station information provided in this application;

[0091] Figure 12: A schematic diagram of the structure of an embodiment of the version history table of the modified energy storage power station information provided in this application;

[0092] Figure 13: A schematic diagram of the structure of an embodiment of the modified energy storage power station information table provided in this application;

[0093] Figure 14: A schematic diagram of the structure of an embodiment of the basic information table of the deleted energy storage power station information provided in this application;

[0094] Figure 15: A schematic diagram of the structure of an embodiment of the version history table of deleted energy storage power station information provided in this application;

[0095] Figure 16: A schematic diagram of the structure of an embodiment of the energy storage power station table data table with deleted energy storage power station information provided in this application;

[0096] Figure 17: A schematic diagram of an embodiment of the large-scale energy storage resource management device provided in this application. Detailed Implementation

[0097] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0098] Example 1

[0099] Please refer to Figure 1, which illustrates a method for large-scale energy storage resource management according to 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, while providing a complete lifecycle management system for the resource model. It also provides version control functions for adding, deleting, modifying, and querying 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 first needs to acquire a series of power system data, namely: identifying the resource model data that needs to be managed; the sources of resource model data mainly include, but are not limited to, CIME files, DT files, and other system databases in the power industry; based on the characteristics of the power industry, the resource data that typically needs to be managed mainly includes, but is not limited to, physical equipment in the distribution, transmission, and generation links; finally, based on the characteristics of the system, identifying which resource data needs to be version controlled. The principle for version control is generally to determine whether the resource data needs to be retrospectively updated based on time when it is added, modified, or deleted. If retrospective updates are required, then version control is necessary.

[0103] Secondly, the resource data collected and organized from the resource model is converted into unified and standardized resource model data and entered into the database tables. A standardized resource model should include, but is not limited to, information such as a unique resource identifier, resource name, and resource creation date. Resource data requiring version control should also include start and end version numbers. The database table design should conform to the third normal form and allow for the dynamic addition of resource attributes. Dynamic addition, deletion, and modification of resource attributes should not be restricted, and the database should meet scalability requirements.

[0104] Then create and initialize two tables that need to be version controlled: a version history table and a version basic information table.

[0105] More specifically, the creation of two tables that require version control is as follows:

[0106] (1) Create a version basic information table: This table stores basic information about the version number. The table fields include:

[0107] Initial version number: The initial version number, typically 1. The initial version number of the data record in the resource data table.

[0108] End version number value: The largest version number value, usually a power of 2.

[0109] Version number increment: The increment of the version number value is 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 shown in Figure 2.

[0112] (2) Create a version history table: This table stores record information for all versions during the version control process. Records are made during version initialization and each version change. Table fields include:

[0113] Change time: The specific time when version control was implemented.

[0114] Version number: The version number corresponding to the change time. Resource data for 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 shown in Figure 3.

[0117] More specifically, the initialization of the two tables that require version control is as follows:

[0118] Initialize the records of the version management type table: Initialize one basic version information record and one version history record: The initial data for the basic version information record is: start version number value = 1, end version number value = 9223372036854775807, version number increment = 1, creation date = current creation date (2023 / 06 / 12); The initial data for the version history record is: change time = current time (e.g., 2023 / 06 / 12 15:00:00), change version number = 1 (i.e., the start version number value initialized in the "Basic Version Information Table"), creation date = current creation date (2023 / 06 / 12).

[0119] More specifically, after creating and initializing the version basic information table and the version history table, the process also includes:

[0120] Create resource data tables: Based on the resource data obtained in the previous step, identify which types of resource data require version management, including: energy storage power station information, energy storage power station PCS information, energy storage power station battery stack information, energy storage power station disconnector information, energy storage power station transformer information, energy storage power station bus information, etc. Create resource model tables for each type of resource data. Each resource model table must include the following fields: unique resource identifier, resource name, resource creation date, start version number, and end version number. Other optional fields in the resource model table are the respective attributes of each type of resource data.

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

[0122] S01: Receive data operation instructions; wherein, the data operation instructions include querying data, adding data, modifying data, or deleting data.

[0123] S02: According to the data operation instructions, operate on the preset resource data table and modify the data in the preset version basic information table and the preset version history table.

[0124] As a preferred embodiment of Embodiment 1, the step of operating on a preset resource data table according to the data operation instructions and modifying the data in a preset version basic information table and a preset version history table specifically includes:

[0125] Resource model management allows for the querying, adding, modifying, and deleting of resource models. Resource model management should not be affected by other business data and should maintain high cohesion and loose coupling. When other business processes interact with resource model management, they should be able to retrieve resource model data without providing any business data. Resource model operations mainly include the following:

[0126] Query: Querying the specific resource data corresponding to a specified date mainly includes the following steps: ① Retrieve the data set in the version history table that is less than or equal to the specified date; ② Sort the retrieved data set by change time from largest to smallest, and retrieve the change version number field value of the record with the longest change time; ③ Retrieve records in the resource model data table that meet the condition: start version number <= change version number <= end version number; ④ Return the queried record set from step 3, which is the resource data corresponding to the specified date.

[0127] When the data operation command is to query data, this application first determines the preset time point for the query, and then accurately finds all change records up to that time point through a preset version history table. By filtering out the largest 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 moment. This method not only improves the response speed and accuracy of query operations, but also enhances data traceability and system transparency by maintaining a clear change history. Furthermore, this query mechanism facilitates subsequent data analysis, audit trails, and troubleshooting, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data retrieval, enhances the reliability of data management, and optimizes the user experience of system operation.

[0128] Adding a new resource record involves the following steps: ① Retrieve a set of records from the version history table that are less than or equal to the addition date. Sort the records by change time from largest to smallest and retrieve the change time. Also, retrieve the change version number field value of the record with the longest change time. ② Query the version basic information table to retrieve the version number increment value and the end version number field value. ③ Write the new resource data to the resource model data table. Set the starting version number to the change version number field value obtained in step one + 1, and the ending version number to the end version number field value obtained in step two. ④ Add a new record to the version history table. Set the change date to the current addition date and time, and the change version number to the change version number field value obtained in step one + 1.

[0129] This application provides an efficient data consistency assurance mechanism for large-scale energy storage resource management by precisely controlling the updates of version information and historical records. When new data is added, the system first determines the specific date of the new data and then searches a pre-set version history table for all previous change records to obtain the current maximum version number and the corresponding end version number. This process ensures the continuity and accuracy of version numbers. Subsequently, the system adds the new resource data to a pre-set resource data table and updates the pre-set version history table, recording the detailed information of the new data and the new version number. The benefits of this method are that it not only maintains a clear data change history, facilitating future queries and audits, but also enhances data consistency and reliability by ensuring that each data addition strictly follows the version control process. Furthermore, explicit version control helps improve the automation level of data management and reduces human error, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data management, enhances data traceability, and strengthens system stability.

[0130] Modification: Changing the attribute information of specified resource data, such as resource name, resource type, etc., mainly includes the following steps: ① Query the resource data to be changed based on conditions and date. See the previous step for specific query steps; ② Query the version basic information table to obtain the version number increment value and the end version number value; ③ Query the version history table to obtain the data set with dates less than or equal to the specified date. Sort the set according to the change date from largest to smallest, and obtain the record with the largest date and 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 in step 3 + 1, i.e., end version number = 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, i.e., start version number = change version number + 1, and the end version number is the maximum version number value in step 2, i.e., maximum version number = end version number. Set the resource data attributes to the changed resource data attributes; ⑥ Add a new data in the version history table. Set the change date to the current change date and time, and the change version number to the change version number field value obtained in step 3 + 1.

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

[0132] Deletion: When it is necessary to delete a resource data record, the main steps are as follows: ①: Query the resource data to be changed based on the conditions and date. See the query steps for details; ②: Query the version history table, obtain the data set in the table with a date less than or equal to the specified date, sort the set according to the change date from largest to smallest, 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 one to the change version number value obtained in step two; ④: Add a new data record in the version history table, with the change date being the current change date and time, and the change version number set to the change version number obtained in step two + 1.

[0133] This application achieves effective management of large-scale energy storage resources by updating a pre-set version history table during deletion operations. Specifically, when deleting resource data, the system first searches the pre-set version history table for all records whose change time is less than or equal to the deletion operation date to determine the current maximum 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 version number, clearly marking the end point of the resource data's lifecycle. In addition, the system adds a new record to the pre-set version history table, recording 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, ensures data consistency and integrity, and enhances the system's traceability and transparency by maintaining a detailed version history, providing strong support for the stable operation and efficient maintenance of the power system.

[0134] As a preferred embodiment of Embodiment 1, after operating on the preset resource data table according to the data operation instructions and modifying the data in the preset version basic information table and the preset version history table, the method further includes displaying resource data, specifically:

[0135] Resource model display and operation mainly utilize the various operational capabilities of the resource model management process to display resource model data. Resource model display can be carried out in a variety of ways, including, but not limited to, displaying resource data at various levels in list form, displaying hierarchical resource data in tree diagram form, and displaying resource data with topological relationships in topology diagram form in power industry. Resource model operation includes operations such as adding, modifying, and deleting resource model data.

[0136] As a preferred embodiment of Example 1, taking energy storage power station information modeling as an example, the process of power system resource modeling and version control 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: the version basic information table and the version history table. The initialization data can be seen in Figures 5, 6 and 7.

[0138] 2. The specific process for querying, adding, modifying, or deleting information about energy storage power stations is as follows:

[0139] Query: To find data for energy storage power stations with a change date of 2023 / 06 / 12 17:30, the main steps are as follows: ①: Query the data set in the version history table where the change date is <= 2023 / 06 / 12 17:30; ②: Sort the obtained data set by change time from largest to smallest, 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; ③: Based on the change version number value obtained in step 2, retrieve records in the energy storage power station table where the condition is: start version number <= 1 <= end version number; ④: Query the energy storage power station data for the specified date, specifically the data with id = station_1 and id = station_2.

[0140] Added: Added a new energy storage power station resource data entry, with the power station name being Hengyi Power Plant 1, the power station ID being station_3, and the addition date being 2023 / 06 / 13 15:30:00. The process mainly includes the following steps: ① Retrieve the set of records from the version history table whose change time is <= 2023 / 06 / 13 15:30:00 based on the addition date. Sort the retrieved records by change time from largest to smallest and obtain the change time. Then, retrieve the change version number field value of the record with the longest change time. According to the resource model initialization step, the change version number is 1; ② Query the version basic information table to obtain the version... The version number increment value and the end version number field value are known from the resource model initialization step to be 1 and 9223372036854775807; ③ Write the new 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 two + 1, and the end version number to the end version number field value obtained in step two; ④ Add a new data record to the version history table, set the change date to the current addition date and time, and set the change version number to the change version number field value obtained in step two + 1. The table data after the addition is shown in Figures 8, 9 and 10.

[0141] Modification: The name of Baohu Energy Storage Power Station 1 has been changed to Baohu Energy Storage Power Station 2, with the change time being 2023 / 06 / 13 15:40:00. The main steps are as follows: ① Query the resource data to be changed based on the conditions and date. See the previous step for details on the query operation. Query the records where the power station name is Baohu Energy Storage Power Station 1; ② Query the version basic information table to obtain the version number increment value and the end version number value. The version number increment is 1, and the end version number value is 9223372036854775807; ③ Obtain the set of records in the version history table with a change time <= 2023 / 06 / 13 15:40:00 based on the change date. Sort the obtained record set according to the change time from largest to smallest and obtain the change time. Then, obtain the change version number field value of the record with the longest change time. (The last part, "Additional steps," appears to be a separate, unrelated section and can be omitted.) ④ Set the end version number of the resource model data queried in step 1 to the change version number value in step 3, i.e., end version number = 2; ⑤ Add a new resource data in the energy storage power station table. The start version number of the new resource data is the change version number + 1, i.e., the start version number = 3, and the end version number is the end version number value in step 2, i.e., end version number = 9223372036854775807. The power station name is: Baohu Energy Storage Power Station 2, and the power station ID is: station_3; ⑥ Add a new data in the version history table. Set the change date to the current change date and time, and set the change version number to the change version number field value obtained in step 3 + 2, i.e., change version number 3. The change date is 2023 / 06 / 13 15:40:00. The data after the change is shown in Figures 11, 12, and 13.

[0142] Deletion: Delete the Hengyi Power Plant 1 data, with the deletion date being 2023 / 06 / 14 15:00:00. The main steps are as follows: ①: Query the resource data to be deleted based on the conditions and date; see the query steps for details. ②: Obtain the set of records in the version history table whose change time is <= 2023 / 06 / 14 15:00:00 based on the change date. Sort the obtained record set according to the change time from largest to smallest and obtain the change time. Then, obtain the change version number field value of the record with the longest change time; based on the modification process, 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 record to the version history table, with the change date being the current deletion date and time, and the change version number set to the change version number obtained in step two + 1, i.e., change version number 4. The table data after deletion is shown in Figures 14, 15, and 16.

[0143] This application enables precise manipulation of resource data tables by receiving data operation instructions, including query, add, modify, and delete commands. Simultaneously, it updates the basic version information table and version history table, ensuring data consistency and integrity. By decoupling resource data from business data, this application not only improves maintainability but also reduces data redundancy and lowers storage costs through version control. When executing data operation instructions, this application first performs corresponding add, delete, modify, and query operations in the resource data table, and then synchronously updates the basic version information table and version history table, recording detailed operation information and version changes. By meticulously recording the history of each data change, this application improves data traceability, enabling rapid problem location and data recovery when needed. Furthermore, by controlling the growth and termination of version numbers, this application effectively avoids unnecessary data duplication, optimizing data storage capacity. Therefore, by highly decoupling resource data from business data and implementing version control, this application improves the efficiency and accuracy of data management, addressing the problem of inflexible management of large-scale energy storage resources in existing technologies.

[0144] Example 2

[0145] Please refer to Figure 17, which shows a large-scale energy storage resource management device provided in an embodiment of this application.

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

[0147] This application extracts resource data from business data for separate management and maintenance, while providing a complete lifecycle management system for the resource model. It also provides version control functions for adding, deleting, modifying, and querying 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 first needs to acquire a series of power system data, namely: identifying the resource model data that needs to be managed; the sources of resource model data mainly include, but are not limited to, CIME files, DT files, and other system databases in the power industry; based on the characteristics of the power industry, the resource data that typically needs to be managed mainly includes, but is not limited to, physical equipment in the distribution, transmission, and generation links; finally, based on the characteristics of the system, identifying which resource data needs to be version controlled. The principle for version control is generally to determine whether the resource data needs to be retrospectively updated based on time when it is added, modified, or deleted. If retrospective updates are required, then version control is necessary.

[0149] Secondly, the resource data collected and organized from the resource model is converted into unified and standardized resource model data and entered into the database tables. A standardized resource model should include, but is not limited to, information such as a unique resource identifier, resource name, and resource creation date. Resource data requiring version control should also include start and end version numbers. The database table design should conform to the third normal form and allow for the dynamic addition of resource attributes. Dynamic addition, deletion, and modification of resource attributes should not be restricted, and the database should meet scalability requirements.

[0150] Then create and initialize two tables that need to be version controlled: a version history table and a version basic information table.

[0151] More specifically, the creation of two tables that require version control is as follows:

[0152] (1) Create a version basic information table: This table stores basic information about the version number. The table fields include:

[0153] Initial version number: The initial version number, typically 1. The initial version number of the data record in the resource data table.

[0154] End version number value: The largest version number value, usually a power of 2.

[0155] Version number increment: The increment of the version number value is 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 shown in Figure 2.

[0158] (2) Create a version history table: This table stores record information for all versions during the version control process. Records are made during version initialization and each version change. Table fields include:

[0159] Change time: The specific time when version control was implemented.

[0160] Version number: The version number corresponding to the change time. Resource data for 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 shown in Figure 3.

[0163] More specifically, the initialization of the two tables that require version control is as follows:

[0164] Initialize the records of the version management type table: Initialize one basic version information record and one version history record: The initial data for the basic version information record is: start version number value = 1, end version number value = 9223372036854775807, version number increment = 1, creation date = current creation date (2023 / 06 / 12); The initial data for the version history record is: change time = current time (e.g., 2023 / 06 / 12 15:00:00), change version number = 1 (i.e., the start version number value initialized in the "Basic Version Information Table"), creation date = current creation date (2023 / 06 / 12).

[0165] More specifically, after creating and initializing the version basic information table and the version history table, the process also includes:

[0166] Create resource data tables: Based on the resource data obtained in the previous step, identify which types of resource data require version management, including: energy storage power station information, energy storage power station PCS information, energy storage power station battery stack information, energy storage power station disconnector information, energy storage power station transformer information, energy storage power station bus information, etc. Create resource model tables for each type of resource data. Each resource model table must include the following fields: unique resource identifier, resource name, resource creation date, start version number, and end version number. Other optional fields in the resource model table are the respective attributes of each type of resource data.

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

[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 on the preset resource data table according to the data operation instructions, and modify the data in the preset version basic information table and the preset version history table.

[0170] As a preferred embodiment of Embodiment Two, the step of operating on the preset resource data table according to the data operation instructions and modifying the data in the preset version basic information table and the preset version history table specifically includes:

[0171] Resource model management allows for the querying, adding, modifying, and deleting of resource models. Resource model management should not be affected by other business data and should maintain high cohesion and loose coupling. When other business processes interact with resource model management, they should be able to retrieve resource model data without providing any business data. Resource model operations mainly include the following:

[0172] Query: Querying the specific resource data corresponding to a specified date mainly includes the following steps: ① Retrieve the data set in the version history table that is less than or equal to the specified date; ② Sort the retrieved data set by change time from largest to smallest, and retrieve the change version number field value of the record with the longest change time; ③ Retrieve records in the resource model data table that meet the condition: start version number <= change version number <= end version number; ④ Return the queried record set from step 3, which is the resource data corresponding to the specified date.

[0173] When the data operation command is to query data, this application first determines the preset time point for the query, and then accurately finds all change records up to that time point through a preset version history table. By filtering out the largest 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 moment. This method not only improves the response speed and accuracy of query operations, but also enhances data traceability and system transparency by maintaining a clear change history. Furthermore, this query mechanism facilitates subsequent data analysis, audit trails, and troubleshooting, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data retrieval, enhances the reliability of data management, and optimizes the user experience of system operation.

[0174] Adding a new resource record involves the following steps: ① Retrieve a set of records from the version history table that are less than or equal to the addition date. Sort the records by change time from largest to smallest and retrieve the change time. Also, retrieve the change version number field value of the record with the longest change time. ② Query the version basic information table to retrieve the version number increment value and the end version number field value. ③ Write the new resource data to the resource model data table. Set the starting version number to the change version number field value obtained in step one + 1, and the ending version number to the end version number field value obtained in step two. ④ Add a new record to the version history table. Set the change date to the current addition date and time, and the change version number to the change version number field value obtained in step one + 1.

[0175] This application provides an efficient data consistency assurance mechanism for large-scale energy storage resource management by precisely controlling the updates of version information and historical records. When new data is added, the system first determines the specific date of the new data and then searches a pre-set version history table for all previous change records to obtain the current maximum version number and the corresponding end version number. This process ensures the continuity and accuracy of version numbers. Subsequently, the system adds the new resource data to a pre-set resource data table and updates the pre-set version history table, recording the detailed information of the new data and the new version number. The benefits of this method are that it not only maintains a clear data change history, facilitating future queries and audits, but also enhances data consistency and reliability by ensuring that each data addition strictly follows the version control process. Furthermore, explicit version control helps improve the automation level of data management and reduces human error, thus playing a crucial role in the operation and maintenance of power systems. Therefore, this application improves the accuracy and efficiency of data management, enhances data traceability, and strengthens system stability.

[0176] Modification: Changing the attribute information of specified resource data, such as resource name, resource type, etc., mainly includes the following steps: ① Query the resource data to be changed based on conditions and date. See the previous step for specific query steps; ② Query the version basic information table to obtain the version number increment value and the end version number value; ③ Query the version history table to obtain the data set with dates less than or equal to the specified date. Sort the set according to the change date from largest to smallest, and obtain the record with the largest date and 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 in step 3 + 1, i.e., end version number = 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, i.e., start version number = change version number + 1, and the end version number is the maximum version number value in step 2, i.e., maximum version number = end version number. Set the resource data attributes to the changed resource data attributes; ⑥ Add a new data in the version history table. Set the change date to the current change date and time, and the change version number to the change version number field value obtained in step 3 + 1.

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

[0178] Deletion: When it is necessary to delete a resource data record, the main steps are as follows: ①: Query the resource data to be changed based on the conditions and date. See the query steps for details; ②: Query the version history table, obtain the data set in the table with a date less than or equal to the specified date, sort the set according to the change date from largest to smallest, 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 one to the change version number value obtained in step two; ④: Add a new data record in the version history table, with the change date being the current change date and time, and the change version number set to the change version number obtained in step two + 1.

[0179] This application achieves effective management of large-scale energy storage resources by updating a pre-set version history table during deletion operations. Specifically, when deleting resource data, the system first searches the pre-set version history table for all records whose change time is less than or equal to the deletion operation date to determine the current maximum 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 version number, clearly marking the end point of the resource data's lifecycle. In addition, the system adds a new record to the pre-set version history table, recording 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, ensures data consistency and integrity, and enhances the system's traceability and transparency by maintaining a detailed version history, providing strong support for the stable operation and efficient maintenance of the power system.

[0180] As a preferred embodiment of Embodiment Two, after operating on the preset resource data table according to the data operation instructions and modifying the data in the preset version basic information table and the preset version history table, the method further includes displaying resource data, specifically:

[0181] Resource model display and operation mainly utilize the various operational capabilities of the resource model management process to display resource model data. Resource model display can be carried out in a variety of ways, including, but not limited to, displaying resource data at various levels in list form, displaying hierarchical resource data in tree diagram form, and displaying resource data with topological relationships in topology diagram form in power industry. Resource model operation includes operations such as adding, modifying, and deleting resource model data.

[0182] As a preferred embodiment of Example 2, taking 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: the version basic information table and the version history table. The initialization data can be seen in Figures 5, 6 and 7.

[0184] 2. The specific process for querying, adding, modifying, or deleting information about energy storage power stations is as follows:

[0185] Query: To find data for energy storage power stations with a change date of 2023 / 06 / 12 17:30, the main steps are as follows: ①: Query the data set in the version history table where the change date is <= 2023 / 06 / 12 17:30; ②: Sort the obtained data set by change time from largest to smallest, 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; ③: Based on the change version number value obtained in step 2, retrieve records in the energy storage power station table where the condition is: start version number <= 1 <= end version number; ④: Query the energy storage power station data for the specified date, specifically the data with id=station_1 and id=station_2.

[0186] Added: Added a new energy storage power station resource data entry, with the power station name being Hengyi Power Plant 1, the power station ID being station_3, and the addition date being 2023 / 06 / 13 15:30:00. The process mainly includes the following steps: ① Retrieve the set of records from the version history table whose change time is <= 2023 / 06 / 13 15:30:00 based on the addition date. Sort the retrieved records by change time from largest to smallest and obtain the change time. Then, retrieve the change version number field value of the record with the longest change time. According to the resource model initialization step, the change version number is 1; ② Query the version basic information table to obtain the version... The version number increment value and the end version number field value are known from the resource model initialization step to be 1 and 9223372036854775807; ③ Write the new 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 two + 1, and the end version number to the end version number field value obtained in step two; ④ Add a new data record to the version history table, set the change date to the current addition date and time, and set the change version number to the change version number field value obtained in step two + 1. The table data after the addition is shown in Figures 8, 9 and 10.

[0187] Modification: The name of Baohu Energy Storage Power Station 1 has been changed to Baohu Energy Storage Power Station 2, with the change time being 2023 / 06 / 13 15:40:00. The main steps are as follows: ① Query the resource data to be changed based on the conditions and date. See the previous step for details on the query operation. Query the records where the power station name is Baohu Energy Storage Power Station 1; ② Query the version basic information table to obtain the version number increment value and the end version number value. The version number increment is 1, and the end version number value is 9223372036854775807; ③ Obtain the set of records in the version history table with a change time <= 2023 / 06 / 13 15:40:00 based on the change date. Sort the obtained record set according to the change time from largest to smallest and obtain the change time. Then, obtain the change version number field value of the record with the longest change time. (The last part, "Additional steps," appears to be a separate, unrelated section and can be omitted.) ④ Set the end version number of the resource model data queried in step 1 to the change version number value in step 3, i.e., end version number = 2; ⑤ Add a new resource data in the energy storage power station table. The start version number of the new resource data is the change version number + 1, i.e., the start version number = 3, and the end version number is the end version number value in step 2, i.e., end version number = 9223372036854775807. The power station name is: Baohu Energy Storage Power Station 2, and the power station ID is: station_3; ⑥ Add a new data in the version history table. Set the change date to the current change date and time, and set the change version number to the change version number field value obtained in step 3 + 2, i.e., change version number 3. The change date is 2023 / 06 / 13 15:40:00. The data after the change is shown in Figures 11, 12, and 13.

[0188] Deletion: Delete the Hengyi Power Plant 1 data, with the deletion date being 2023 / 06 / 14 15:00:00. The main steps are as follows: ①: Query the resource data to be deleted based on the conditions and date; see the query steps for details. ②: Obtain the set of records in the version history table whose change time is <= 2023 / 06 / 14 15:00:00 based on the change date. Sort the obtained record set according to the change time from largest to smallest and obtain the change time. Then, obtain the change version number field value of the record with the longest change time; based on the modification process, 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 record to the version history table, with the change date being the current deletion date and time, and the change version number set to the change version number obtained in step two + 1, i.e., change version number 4. The table data after deletion is shown in Figures 14, 15, and 16.

[0189] This device utilizes two modules that work in a coordinated manner to better manage large-scale energy storage data. By receiving data operation commands, including query, add, modify, and delete, this application achieves precise operations on the resource data table, while simultaneously updating the version basic information table and version history table, ensuring data consistency and integrity. By decoupling resource data from business data, this application not only improves maintainability but also reduces data redundancy and lowers storage costs through version control. When executing data operation commands, this application first performs corresponding add, delete, modify, and query operations in the resource data table, and then synchronously updates the version basic information table and version history table, recording detailed operation information and version changes. By meticulously recording the history of each data change, this application improves data traceability, enabling rapid problem location and data recovery when needed. Furthermore, by controlling the growth and termination of version numbers, this application effectively avoids unnecessary data duplication, optimizing data storage capacity. Therefore, by highly decoupling resource data from business data and implementing version control, this application improves the efficiency and accuracy of data management, addressing the problem of the inability to flexibly manage large-scale energy storage resources in existing technologies.

[0190] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. In particular, it should be noted that any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention for those skilled in the art.

Claims

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

2. The method for large-scale energy storage resource management according to claim 1, characterized in that, The step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation instruction is to query data; The first preset time for obtaining the queried data; Based on the preset version history table and the first preset time, query all first records in the preset version history table whose first change time is less than or equal to the first preset time; Based on the first record, determine the maximum value in the first change time in the preset version history table, and obtain the change version number of the maximum value; Based on the version number of the maximum value, retrieve the first resource data corresponding to the version number of the maximum value from the preset resource data table.

3. The method for large-scale energy storage resource management according to claim 1, characterized in that, The step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation instruction is to add new data; Obtain the second resource data of the newly added data; Based on the date of the second resource data, retrieve all second records from the preset version history table that have a first change time less than or equal to the date of the second resource data; Based on the second record, obtain the first maximum change version number from the preset version history table; Based on the first maximum change version number, obtain the second end version number of the first maximum change version number from the version basic information table; Add the second resource data to the preset resource data table; wherein, the start version number of the second resource data is the value of the maximum change version number, and the end version number of the second resource data is the value of the second end version number; Add a new record of the second resource data to the preset version history 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 method for large-scale energy storage resource management according to claim 1, characterized in that, The step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation instruction is to modify data; Query the version number increment and end version number of the modified data in the preset version basic information table; In the preset version history table, query the third record in the first change time that is less than or equal to the time of the modified data, and then query the second maximum change version number in the third record; Update the information of the modified data in the preset resource data table; wherein, the end version number of the modified data is changed to the second maximum change version number plus one; Add 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 maximum change version number plus one, and the end version number of the second resource information is the end version number of the modified data; Add a new record of the modified data to the preset version history table; wherein, the third change time of the modified data record is the time of the data modification, the third change version number of the modified data record is the second maximum change version number plus one, and the third creation date of the modified data record is the date of the data modification.

5. The method for large-scale energy storage resource management according to claim 1, characterized in that, The step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation command is to delete data; Obtain the third largest change version number from the preset version history table, where the first change time is less than or equal to the date of the deleted data; In the preset version history table, the end version number of the deleted data is updated to the third largest change version number; Add a new record of the deleted data to the preset version history table; wherein, the fourth change date of the record of the deleted data is the date of deletion of the 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, Includes a receiving module and an operation 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 on the preset resource data table according to the data operation instructions, and modify the data in the preset version basic information table and the preset version history table. The preset resource data table is used to store resource model data after decoupling from business data, and the preset version basic information table and the preset version history table are used to record the version information of the preset resource data table. The first resource data in the preset resource data table includes a first resource identifier, a first resource name, a first creation date, a first start version number, and a first end version number; The data in the preset version basic information table includes the first start version number, the first end version number, the first version number increment, and the first creation date; The preset version history table includes the first change time, the first change version number, and the first creation date.

7. The large-scale energy storage resource management device according to claim 6, characterized in that, The step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation instruction is to query data; The first preset time for obtaining the queried data; Based on the preset version history table and the first preset time, query all first records in the preset version history table whose first change time is less than or equal to the first preset time; Based on the first record, determine the maximum value in the first change time in the preset version history table, and obtain the change version number of the maximum value; Based on the version number of the maximum value, retrieve the first resource data corresponding to the version number of the maximum value from the preset resource data table.

8. The large-scale energy storage resource management device according to claim 6, characterized in that, The step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation instruction is to add new data; Obtain the second resource data of the newly added data; Based on the date of the second resource data, retrieve all second records from the preset version history table that have a first change time less than or equal to the date of the second resource data; Based on the second record, obtain the first maximum change version number from the preset version history table; Based on the first maximum change version number, obtain the second end version number of the first maximum change version number from the version basic information table; Add the second resource data to the preset resource data table; wherein, the start version number of the second resource data is the value of the maximum change version number, and the end version number of the second resource data is the value of the second end version number; Add a new record of the second resource data to the preset version history 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 step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation instruction is to modify data; Query the version number increment and end version number of the modified data in the preset version basic information table; In the preset version history table, query the third record in the first change time that is less than or equal to the time of the modified data, and then query the second maximum change version number in the third record; Update the information of the modified data in the preset resource data table; wherein, the end version number of the modified data is changed to the second maximum change version number plus one; Add 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 maximum change version number plus one, and the end version number of the second resource information is the end version number of the modified data; Add a new record of the modified data to the preset version history table; wherein, the third change time of the modified data record is the time of the data modification, the third change version number of the modified data record is the second maximum change version number plus one, and the third creation date of the modified data record is the date of the data modification.

10. The large-scale energy storage resource management device according to claim 6, characterized in that, The step of operating on the preset resource data table according to the data operation instructions, and modifying the data in the preset version basic information table and the preset version history table, specifically involves: When the data manipulation command is to delete data; Obtain the third largest change version number from the preset version history table, where the first change time is less than or equal to the date of the deleted data; In the preset version history table, the end version number of the deleted data is updated to the third largest change version number; Add a new record of the deleted data to the preset version history table; wherein, the fourth change date of the record of the deleted data is the date of deletion of the data, and the fourth change version number of the deleted data is the third maximum change version number plus one.

Images