Device Point Data Management Method and System in Energy Storage System

Abstract

The present application relates to a method and system for managing device point data. According to the comparison results of the difference between the data acquisition time and the current system time and the N-1 aging node values in sequence, the data is written into one of the N caches with different importance levels. The smaller the difference, the higher the priority of writing into the cache with a higher importance level. In this way, the data can be stored in a hierarchical manner according to the data acquisition time. Once new data is written into the cache, the business scenario unit is notified, and all business scenarios related to the data can be found. When the newly written data meets all the usage constraint conditions of at least one business scenario, the newly written data is used to perform business calculations on the business scenarios that meet all the usage constraint conditions to drive the update of business scenario data. In this way, it is realized to obtain and apply data with different timeliness according to different business scenarios, which not only has strong timeliness, but also can realize the aggregation of point data according to different business scenarios.

Description

Technical Field

[0001] This application relates to the technical field of energy storage system data management, and particularly to a method and system for managing device point data in an energy storage system. Background Art

[0002] In an energy storage system, it is necessary to collect point data of devices such as BMS, PCS, fire protection, air conditioning, cameras, etc. The point data of each device is separately stored in different library tables. The energy storage system updates the latest collected point data to a real-time table or cache as real-time data, and at the same time stores the data in a historical library table as historical data. When relevant point data is used in a business scenario, the point data will be queried from the corresponding library table and then directly displayed or secondarily processed and calculated according to the scenario requirements. Real-time data is generally used in business scenarios for displaying the latest dynamic data, such as dynamic data on a configuration diagram large screen. Historical data is generally used for data statistics, such as line chart display of years, months, and days.

[0003] However, due to the mechanism of point data push, the traditional method of managing device point data lacks timeliness and personalized push for different business scenarios. First, the point data required by the business scenario is all passively obtained from the cache or library table, rather than the point data being actively pushed to the relevant business scenario when the real-time change occurs. Second, the push method of point data is to set a fixed timeliness threshold, without setting a personalized timeliness push scheme for different business scenarios, and different timeliness data cannot be obtained according to the specific business scenario. Summary of the Invention

[0004] Based on this, in view of the problem that the traditional method of managing device point data in an energy storage system lacks timeliness and personalized push for different business scenarios due to the mechanism of point data push, it is necessary to provide a method and system for managing device point data in an energy storage system.

[0005] On the one hand, this application provides a method for managing device point data in an energy storage system, and the method for managing device point data in the energy storage system includes:

[0006] Judge whether a piece of device point data is received;

[0007] If a piece of device point data is received, obtain the device point data and simultaneously obtain the device point information attached to the device point data;

[0008] Read the data acquisition time in the device point information;

[0009] Obtain the difference between the data acquisition time and the current system time, and write the device point data into one of the N caches with different importance levels according to the comparison results of the difference between the data acquisition time and the current system time and the N - 1 time - effective node values in sequence; the smaller the difference between the data acquisition time and the current system time, the higher the priority of writing into the cache with a higher importance level; N is a positive integer;

[0010] As time goes by, control the device point data to flow from the cache with a higher importance level to the cache with a lower importance level;

[0011] Judge whether there is at least one cache written with new device point data;

[0012] If there is at least one cache written with new device point data, then retrieve the business scenario rule table;

[0013] Select a newly written device point data;

[0014] Judge whether the newly written device point data meets all the usage constraint conditions of at least one business scenario in the business scenario rule table;

[0015] If the newly written device point data meets all the usage constraint conditions of at least one business scenario in the business scenario rule table, then apply the newly written device point data to perform business calculations in the business scenario that meets all the usage constraint conditions;

[0016] If the newly written device point data does not meet all the usage constraint conditions of at least one business scenario in the business scenario rule table, then issue an alarm message;

[0017] Return the selected newly written device point data until all the newly written device point data have been processed.

[0018] On the other hand, the present application also provides a device point data management system, including:

[0019] A management unit for executing the device point data management method in the energy storage system mentioned above;

[0020] A storage unit connected to the management unit, including multiple caches with different importance levels;

[0021] A business scenario unit connected to the management unit.

[0022] The present application relates to a method and system for managing device point data. The data collection time of the received device point data is read by a management unit. The device point data is written into one of N caches of different importance levels through the comparison result of the difference between the data collection time and the current system time and N-1 time node values ​​in sequence. The smaller the difference, the higher the priority of writing into the cache with a higher importance level. In this way, the device point data can be cached and stored in layers according to the early or late data collection time. Once the cache writes new data, the business scenario unit is notified to find all business scenarios related to the device point data. When the newly written device point data meets all the usage constraints of at least one business scenario in the business scenario rule table, the newly written device point data is applied to perform business calculations on the business scenarios that meet all the usage constraints to drive the business scenario data update. In this way, it is possible to obtain and apply data of different timeliness according to different business scenarios. Not only is the timeliness strong, but also point data aggregation can be achieved according to different business scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 This is a flowchart of steps S100 to S200 in a method for managing device point data in an energy storage system provided in one embodiment of the present application.

[0024] Figure 2 This is a flowchart of S200 to S370 in a method for managing device point data in an energy storage system provided in one embodiment of the present application.

[0025] Figure 3 A schematic diagram of the structural framework of a device point data management system in an energy storage system provided in one embodiment of the present application.

[0026] Figure 4 A schematic diagram of the structural framework of a device point data management system in an energy storage system provided in yet another embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of this application more clear, the following is a further detailed description of this application in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain this application and are not used to limit this application.

[0028] The present application provides a method for managing device point data in an energy storage system. It should be noted that the method for managing device point data in an energy storage system provided by the present application is applicable to the management of point data of any type of device in the energy storage system.

[0029] In addition, the execution subject of the device location data management method provided in this application for the energy storage system is not limited. Optionally, the execution subject of the device location data management method provided in this application for the energy storage system can be a device location data management system. Specifically, the execution subject of the device location data management method provided in this application for the energy storage system can be the management unit in the device location data management system.

[0030] As Figure 1 and Figure 2 shown, in an embodiment of this application, the device location data management method includes:

[0031] S110, determine whether a piece of device location data is received.

[0032] S120, if a piece of device location data is received, obtain the device location data, and synchronously obtain the device location information attached to the device location data.

[0033] S130, read the data acquisition time in the device location information.

[0034] S140, calculate the difference between the data acquisition time and the current system time, and write the device location data into one of the N caches with different importance levels according to the comparison result of sequentially comparing the difference between the data acquisition time and the current system time and N - 1 aging node values. The smaller the difference between the data acquisition time and the current system time, the higher the priority of writing into the cache with a higher importance level. N is a positive integer.

[0035] S200, as time goes by, control the device location data to flow from the cache with a higher importance level to the cache with a lower importance level.

[0036] S310, determine whether there is at least one cache written with new device location data.

[0037] S320, if there is at least one cache written with new device location data, retrieve the business scenario rule table.

[0038] S330, select a piece of newly written device location data.

[0039] S340, determine whether the newly written device location data meets all the usage constraint conditions of at least one business scenario in the business scenario rule table.

[0040] S350, if the newly written device location data meets all the usage constraint conditions of at least one business scenario in the business scenario rule table, apply the newly written device location data to perform business calculations in the business scenario that meets all the usage constraint conditions.

[0041] S360, if the newly written device point data does not meet all the usage constraint conditions of at least one business scenario in the business scenario rule table, an alarm message is issued.

[0042] S370, return to S330, that is, return the selected newly written device point data until all the newly written device point data has been processed.

[0043] Specifically, the device point data management system is communicatively connected to the data acquisition devices (not shown in the figure) provided on each device. When the data acquisition device acquires the point data of the device, it will be sent to the device point data management system for processing. The device point data management system first executes S100, that is, determines whether the device point data is received normally. The device point data management system can also be communicatively connected to a host computer (not shown in the figure). If it cannot be received, the possible reasons are that the communication between the device point data management system and the data acquisition device is poor, or the data is abnormal. At this time, an alarm message is sent to the host computer.

[0044] The device can include BMS (battery management system, BMS, battery management system) devices, PCS (Power Conversion System, PCS, energy storage converter system) devices, fire protection devices, air conditioning devices, camera devices, DIDO devices, temperature devices, humidity devices, etc.

[0045] The point data of the PCS device can include current, voltage, power, cumulative charge amount, cumulative discharge amount, etc.

[0046] The point data of the energy storage unit (such as the stack, RACK) can include SOC. The point data of the M meter device (METER) can include the cumulative charge amount and the cumulative discharge amount.

[0047] Optionally, S110 for determining whether a piece of device point data is received includes:

[0048] S111, receive a piece of device point data sent by the data acquisition device.

[0049] S112, perform filtering processing on the device point data, and determine whether the device point data passes the filtering processing.

[0050] S113, if the device point data passes the filtering processing, it is confirmed that the device point data has been received.

[0051] S114, if the device point data does not pass the filtering processing, it is not considered that the device point data has been received, and the device point data that does not pass the filtering processing is deleted.

[0052] Among them, the filtering process of the device point data in S112 can be specifically carried out through a filtering rule table. The filtering rule table is shown in Table 1. For example, the filtering threshold in the power point of PCS1 in Table 1 is set to "X > 1000 || X < -1000", where X in the expression represents the currently collected device point data. If the data that meets the filtering condition will be filtered, that is, deleted. Then only the data within -1000 to 1000 will be retained. This can prevent the appearance of a mutation curve on a line chart. This filtered data will be saved as abnormal data and an alarm message will be generated. The alarm message can be used for fault analysis.

[0053] Table 1 - Filtering Rule Table

[0054]

[0055] In an embodiment of the present application, a point template is set for each point of each device type. The point template realizes the definition and classification of device point data by attaching device point labels to the device point data, so as to distinguish between device point data. The device point label includes two pieces of information, device number information and point number information. The uniqueness of the device point data is determined by the device number + point number. For example, for the device PCS1 in Table 1, its power point is defined as "PCS1.TAG000003", where "PCS1" is the device number information and "TAG000003" is the point number information. A point refers to a data collected by a device. For example, voltage and current respectively correspond to two different points.

[0056] The meaning of S340 to S360 is that when the cache of a certain level changes, it notifies the business scenario unit related to the corresponding level to drive the update of business scenario data. By listening to the changes in the point cache of Redis, the point cache change message will be published to the MQ queue. After the business scenario unit subscribes to this cache change message, it will update the data according to the scene rule agreement. The scene rule defines the constraints of cache level, point priority principle, scene alarm threshold, whether the over-alarm threshold is available, and the filtering threshold of the service layer. Only the data that meets all the constraints of a business scenario will participate in the business scenario calculation. This will be explained in combination with the constraint conditions of the business scenario configured in Table 2:

[0057] Table 2 - Definition Table of Business Scenario Constraint Conditions

[0058]

[0059] Cache level: It means that the calculation of the business scenario can only be triggered when the point data meeting this cache level changes. For example, "primary, secondary" means that when data is written or updated to the primary cache or secondary cache, it meets one of the conditions for triggering the calculation of the business scenario.

[0060] Point priority principle: It means which one should be preferred to participate in the calculation when point data of two different devices can both participate in the calculation of the scenario business. For example, "METER1.TAG00125 >PCS1.TAG000029" means that in the energy storage charging and discharging scenario, the point for calculating the electricity quantity should preferably use the point data of the electricity meter device for calculation. If the electricity meter device is not installed, the point data of the PCS device can be used for substitution calculation.

[0061] Whether the scenario alarm threshold and the over-alarm threshold are available: These two constraint conditions act in combination. When the point data exceeds the scenario alarm threshold and the "whether the over-alarm threshold is available" is set to "yes", then the point data also meets one of the conditions for triggering the business scenario. As long as it exceeds the scenario alarm threshold, an alarm will be generated.

[0062] Secondary service layer filtering threshold: Those that meet the expression will be filtered out, indicating that they do not meet the conditions for triggering the business scenario. For example, "X>1000" means that when the point data is greater than 1000, the calculation of the business scenario cannot be triggered and an alarm will be generated. It can be understood that S111 - S114 is the first filtering, and the filtering in Table 2 is the second filtering (abbreviated as secondary filtering).

[0063] Only when all the conditions in the scenario rules are met simultaneously can the calculation of the business scenario be triggered to drive the update of the business scenario data.

[0064] In this embodiment, the management unit reads the data acquisition time of the received device point data, and based on the comparison results of the difference between the data acquisition time and the current system time and the values of N - 1 aging nodes in sequence, writes the device point data into one of the N caches with different importance levels. The smaller the difference, the higher the priority of writing into the cache with a higher importance level. This enables the device point data to be stored in a cache layer according to the early or late data acquisition time. Once new data is written into the cache, the business scenario unit is notified, and all business scenarios related to the device point data can be found. When the newly written device point data meets all the usage constraint conditions of at least one business scenario in the business scenario rule table, the newly written device point data is used to perform business calculations on the business scenarios that meet all the usage constraint conditions to drive the update of the business scenario data. In this way, it is realized to obtain and apply data with different timeliness according to different business scenarios, which not only has strong timeliness, but also can achieve the aggregation of point data according to different business scenarios.

[0065] In one embodiment of the present application, S140 includes obtaining the difference between the data acquisition time and the current system time, and based on the comparison result of sequentially comparing the difference between the data acquisition time and the current system time with N - 1 aging node values, writing the device point data into one of the caches with N different importance levels, including:

[0066] S141, determining whether the difference between the data acquisition time and the current system time is greater than 0.

[0067] S142, if the difference between the data acquisition time and the current system time is greater than 0, further determining whether the difference between the data acquisition time and the current system time is less than the first - level aging node value.

[0068] S143, if the difference between the data acquisition time and the current system time is less than the first - level aging node value, writing the device point data into the first - level cache.

[0069] S144, if the difference between the data acquisition time and the current system time is greater than or equal to the first - level aging node value, further determining whether the difference between the data acquisition time and the current system time is less than the second - level aging node value.

[0070] S145, if the difference between the data acquisition time and the current system time is less than the second - level aging node value, writing the device point data into the second - level cache.

[0071] S146, if the difference between the data acquisition time and the current system time is greater than or equal to the second - level aging node value, writing the device point data into the third - level cache.

[0072] Specifically, if the difference between the data acquisition time and the current system time is less than or equal to 0, it is considered that the collected device point data is abnormal data. The possible reasons are that the current system time record of the server is incorrect or the acquisition program is incorrect, and an alarm message is sent to the host computer.

[0073] Optionally, the first - level aging node value and the second - level aging node value can be comprehensively determined according to different device types and different point types. That is to say, the first - level aging node value and the second - level aging node value are determined according to two factors. One factor is the type of the device, and the other factor is the type of the point. This is because different points of different devices have different timeliness requirements. Some points of some devices have higher timeliness requirements for data, while some points of some devices have lower timeliness requirements for data.

[0074] Optionally, the first - level aging node value and the second - level aging node value can be set according to a fixed multiple of the acquisition frequency corresponding to the device type and point type.

[0075] Optionally, the first-level aging node value is set to 2 times the time period consumed for collecting data once at the collection frequency of the point data corresponding to the corresponding device type and point type, and the first-level aging node value is 6 times the time period consumed for collecting data once at the collection frequency of the point data corresponding to the corresponding device type and point type. For example, the collection frequency of the cumulative charge of PCS1 device is 30 seconds per time, then the first-level aging node value can be set to 60 seconds, and the second-level aging node value can be set to 180 seconds.

[0076] Optionally, when executing S142 to determine whether the difference between the data collection time and the current system time is less than the first-level aging node value, and when executing S144 to determine whether the difference between the data collection time and the current system time is less than the second-level aging node value, the device aging node value definition table stored locally in the device point data management system can be retrieved to obtain the first-level aging node values and the second-level aging node values of different points of different devices. The device aging node value definition table is shown in Table 3.

[0077] Table 3 - Device Aging Node Value Definition Table

[0078]

[0079] Still taking the cumulative charge of PCS1 device as an example, if the data collection time of a piece of cumulative charge data of PCS1 device is 09:05:05 on March 14, 2025, and the current system time is 09:05:35 on March 14, 2025, the difference between the data collection time and the current system time is 30 seconds. By checking Table 3, it is known that the first-level aging node value is 60 seconds and the second-level aging node value is 180 seconds. It can be seen that 0 - 60 seconds will be written into the first-level cache, 60 - 180 seconds will be written into the second-level cache, and those greater than 180 seconds will be written into the third-level cache. Then 30 seconds falls within the range of 0 - 60 seconds. Therefore, this piece of cumulative charge data of PCS1 device is written into the first-level cache.

[0080] When executing S142 to write device point data into the first-level cache, S145 to write device point data into the second-level cache, and S146 to write device point data into the third-level cache, the write operation is a write when there is no data corresponding to the device point tag in the cache, or an overwrite (i.e., update) when there is data corresponding to the device point tag in the cache. The overwrite (i.e., update) when there is data corresponding to the device point tag in the cache means that when there is data corresponding to the device point tag in the same cache, only the device point data with the latest data acquisition time is retained. For example, when writing PSC1.TAG000001 data with a data acquisition time of 09:05:05 on March 14, 2025 into the first-level cache, it is found that there is also a PSC1.TAG000001 data with a data acquisition time of 09:04:05 on March 14, 2025 in the first-level cache. Then, at this time, the PSC1.TAG000001 data with a data acquisition time of 09:05:05 on March 14, 2025 is retained, and the PSC1.TAG000001 data with a data acquisition time of 09:04:05 on March 14, 2025 is deleted. This is "overwrite".

[0081] That is to say, each cache with different importance levels can store at most one piece of data with the same device point tag respectively. For example, the first-level cache can have a PSC1.TAG000001 data with a data acquisition time of 09:04:05 on March 14, 2025. At the same time, the second-level cache can have a PSC1.TAG000001 data with a data acquisition time of 09:06:05 on March 14, 2025, and the third-level cache can have a PSC1.TAG000001 data with a data acquisition time of 09:08:05 on March 14, 2025. However, each cache cannot have two pieces of PSC1.TAG000001 data at the same time.

[0082] When writing into the cache, the storage structure table can also be updated. The storage structure table is stored locally in the device point data management system. The storage structure table is shown in Table 4.

[0083] Table 4 - Storage Structure Table

[0084]

[0085] In this embodiment, the device point data is hierarchically managed according to timeliness. Through two levels of timeliness, the point data cache is divided into three caches with different importance levels: the first-level cache, the second-level cache, and the third-level cache. After the device point data is collected, it will be stored in the corresponding-level cache according to timeliness, which facilitates the subsequent mutual transfer of each piece of device point data between caches with different importance levels according to the data timeliness rules.

[0086] In an embodiment of the present application, after determining whether there is at least one cache written with new device point data, the following steps are further included:

[0087] S381, if there is at least one cache written with new device point data, generate a failure time tag that matches the importance level of the cache, so that for caches with different importance levels, the failure times of the device point data are also different.

[0088] S382, determine whether the cache to which the newly written device point data belongs is the cache with the lowest importance level.

[0089] S383, if the cache to which the newly written device point data belongs is not the cache with the lowest importance level, attach a failure time tag to the newly written device point data.

[0090] Specifically, the failure time tag and the aging node value can define the point data failure time TX of a device point data. Since the point data is stored in caches with different importance levels, the point data failure time TX of the point data in different caches is also different.

[0091] In this embodiment, the reason for executing S382 is that the cache with the lowest importance level does not set the point data failure time TX. Therefore, the device point data newly written into the cache with the lowest importance level does not need to be attached with a failure time tag. Taking the first-level cache, second-level cache, and third-level cache as examples, the first-level cache has the highest importance level, the second-level cache has the second highest importance level, and the third-level cache has the lowest importance level. Therefore, the newly written device point data in the third-level cache is not attached with a failure time tag, and the newly written device point data in the second-level cache and the first-level cache are both attached with failure time tags.

[0092] In this embodiment, when any cache other than the cache with the lowest importance level newly writes a device point data, by attaching a failure time tag to the newly written device point data, the failure situation of the device point data can be monitored through the failure time tag, which is convenient for controlling the transfer of the device point data from the cache with a high importance level to the cache with a low importance level as time goes by.

[0093] In an embodiment of the present application, the value of the failure time tag is equal to the difference between the aging node value corresponding to the importance level of the cache and the data acquisition time of the newly written device point data.

[0094] Specifically, for example, when the device location data of the first-level cache is written or updated, the location data expiration time TX of the device location data is set at the same time. TX = the first-level aging node value - the data acquisition time of the device location data, indicating that the device location data written or updated this time will expire after TX time.

[0095] In this embodiment, by setting the value of the expiration time tag to be equal to the difference between the aging node value corresponding to the importance level of the cache and the data acquisition time of the newly written device location data, it is ensured that the sum of the expiration time and the data acquisition time of the device location data is exactly the first-level aging node value, guaranteeing the natural transfer of the device location data among caches of different importance levels.

[0096] In an embodiment of the present application, S200 includes:

[0097] S210, each cache traverses all the device location data stored in itself, and determines whether there is at least one device location data that has expired based on the expiration time tag of the device location data.

[0098] S220, if there is at least one device location data that has expired, then obtain all the device location data that has expired.

[0099] S230, select one device location data that has expired.

[0100] S240, determine whether the cache to which the device location data that has expired belongs is the cache with the lowest importance level.

[0101] S250, if the cache to which the device location data that has expired belongs is not the cache with the lowest importance level, then delete the device location data that has expired in the current cache, and transfer the device location data that has expired to the next-level cache with a lower importance level, and return to S230 until all the device location data that has expired has been processed, that is, select one device location data that has expired until all the device location data that has expired has been processed.

[0102] Specifically, the significance of executing S240 is that if the cache to which the device location data that has expired belongs is the cache with the lowest importance level, there is no need to perform data transfer anymore, and the data will always remain in the cache with the lowest importance level without moving. However, if the cache to which the device location data that has expired belongs is not the cache with the lowest importance level, data transfer is performed.

[0103] S250 is the specific step of data transfer. Optionally, the monitoring of the expiration time can be implemented through the redis function. The data transfer of S250 is implemented based on the SETEX command of Redis. For example, "SETEX LEVEL1.PCS1.TAG000001 5100.21,1728442665" means writing the data of the point "PCS1.TAG000001" and the acquisition time into the first-level cache, and setting the expiration time of the device point data to 5 seconds. Redis will automatically clear the device point data in this first-level cache after 5 seconds. By listening to the cache expiration notification of Redis, the energy storage system can obtain the device point data cleared by the first-level cache. Specifically, by inheriting the Key Expiration Event Message Listener class in the redis source code, the expiration notification and the expired device point data can be obtained.

[0104] In this embodiment, by judging whether a failure phenomenon occurs based on the expiration time tag of the device point data, deleting the device point data with the failure phenomenon in the current cache, and transferring the device point data with the failure phenomenon to the next-level cache with a lower importance level, the natural transfer of the device point data from the cache with a higher importance level to the cache with a lower importance level can be realized.

[0105] In an embodiment of the present application, S250 includes, that is, deleting the device point data with the failure phenomenon in the current cache, and transferring the device point data with the failure phenomenon to the next-level cache with a lower importance level, and returning to select a device point data with the failure phenomenon until all the device point data with the failure phenomenon are processed, including:

[0106] S251, obtaining the device point label of the device point data with the failure phenomenon.

[0107] S252, obtaining whether there is device point data with the same device point label in the next-level cache with a lower importance level of the current cache.

[0108] S253, if there is no device point data with the same device point label in the next-level cache with a lower importance level of the current cache, deleting the device point data with the failure phenomenon in the current cache, and transferring the device point data with the failure phenomenon to the next-level cache with a lower importance level of the current cache, and returning to S230, that is, returning to select a device point data with the failure phenomenon.

[0109] S254a. If there is device point data with the same device point label in the cache with a lower importance level at the next level of the current cache, obtain the data collection time of the device point data that has the failure phenomenon in the current cache, and use this data collection time as the first collection time.

[0110] S254b. Obtain the data collection time of the device point data with the same device point label in the cache with a lower importance level at the next level of the current cache, and use this data collection time as the second collection time.

[0111] S254c. Determine whether the first collection time is later than the second collection time.

[0112] S254d. If the first collection time is later than the second collection time, delete the device point data that has the failure phenomenon in the current cache, and transfer the device point data that has the failure phenomenon to the cache with a lower importance level at the next level of the current cache, and return to S230, that is, return to selecting one device point data that has the failure phenomenon.

[0113] S254e. If the first collection time is earlier than the second collection time, delete the device point data that has the failure phenomenon in the current cache, and return to S230, that is, return to selecting one device point data that has the failure phenomenon.

[0114] Specifically, the device point data with the same device point label in S252 refers to two different device point data of the same point of the same type of device that appear simultaneously in different caches, and both pieces of data have the same device point label.

[0115] If there is no device point data with the same device point label in the cache with a lower importance level at the next level, directly transfer the device point data that has the failure phenomenon to the cache with a lower importance level at the next level of the current cache.

[0116] If there is device point data with the same device point label in the cache with a lower importance level at the next level, then the collection times of the two are required, and the one with the later collection time is retained and migrated to the cache with a lower importance level at the next level.

[0117] In this embodiment, when the failed data is transferred to the cache with a lower importance level at the next level, when there is a data conflict of the same device point label, the data with the later collection time is retained, which can ensure that even if the device point data fails, the data retained in each cache is of the best quality.

[0118] In an embodiment of the present application, after S240, that is, after determining whether the cache to which the device point data with a failure phenomenon belongs is the cache with the lowest importance level, the following is further included:

[0119] S261, if the cache to which the device point data with a failure phenomenon belongs is the cache with the lowest importance level, then determine whether there is other device point data with the same device point label in the current cache except the device point data with the failure phenomenon.

[0120] S262, if there is other device point data with the same device point label in the current cache except the device point data with the failure phenomenon, then retain the device point data with the latest data acquisition time under this device point label, and delete the remaining device point data except the device point data with the latest data acquisition time under this device point label.

[0121] Specifically, the data in the cache with the lowest importance level will never become invalid and will always be retained.

[0122] Optionally, the invalid data retained in the cache with the lowest importance level can be marked as offline data and displayed in red or other colors different from the data in other caches during data analysis.

[0123] In this embodiment, by setting that the data in the cache with the lowest importance level will never become invalid, the integrity of the data in the cache is ensured. Without losing any data, it can ensure that the caches with higher importance levels in the front will not retain invalid data and are more lightweight.

[0124] In an embodiment of the present application, the following is further included:

[0125] S410, send a data retrieval request to the cache.

[0126] S420, select a device point label.

[0127] S430, take the current system time as the current snapshot moment, and obtain the device point data in the cache that is closest to the current system time for this device point label as the snapshot data at the current snapshot moment and store it in the troubleshooting database.

[0128] S440, return to S420 until all device point labels have been processed, that is, return to the step of selecting a device point label until all device point labels have been processed.

[0129] S450, after a preset time period, return to the step of sending a data retrieval request to the cache.

[0130] Specifically, when the system is troubleshooting problems, it is necessary to restore the historical data of all device points for a period of time before and after a certain fault time point to facilitate problem analysis and location. Since the collection times of various devices in the energy storage system are not fixed, it is necessary to cache and record all point data at a certain moment through the device point cache to form a point data snapshot at this time point for subsequent troubleshooting.

[0131] The setting of the preset time period is to set the snapshot frequency, reduce the computing power pressure and the storage pressure of the troubleshooting database.

[0132] In this embodiment, by using the current system time as the current snapshot moment and obtaining the device point data closest to the current system time of the device point label in the cache as the snapshot data at the current snapshot moment and storing it in the troubleshooting database, all device point data at the current snapshot moment can be retained for subsequent troubleshooting.

[0133] In an embodiment of the present application, S430 includes, that is, using the current system time as the current snapshot moment and obtaining the device point data closest to the current system time of the device point label in the cache as the snapshot data at the current snapshot moment and storing it in the troubleshooting database, including:

[0134] S431, traverse caches of multiple different importance levels, and obtain the device point data closest to the current system time of the device point label in each cache of importance level. S432, determine whether the obtained device point data is obtained from the cache with the lowest importance level.

[0135] S433, if the obtained device point data is obtained from the cache with the lowest importance level, then attach an offline data label to the obtained device point data.

[0136] S434, if the obtained device point data is not obtained from the cache with the lowest importance level, then attach an online data label to the obtained device point data.

[0137] S435, store the device point data attached with the online data label and / or the offline data label as the snapshot data at the current snapshot moment in the troubleshooting database.

[0138] Specifically, when the device point data is stored in the cache, a snapshot of the device point data is also taken and stored in the troubleshooting database.

[0139] In this embodiment, since there is only one piece of device point data under one device point label in each cache, but the device point data in each cache snapshot is unique. However, the device point data under the same device point label may exist in each cache of different importance level caches. Therefore, it can be understood that it is unique within the cache and not unique between caches. For example, in the architecture of the first-level cache, the second-level cache, and the third-level cache, the snapshot data at the current snapshot moment may be 1, may be 2 pieces of data, or may be 3 pieces of data (one in each of the three caches), but there will not be 4 pieces of data.

[0140] In this embodiment, an additional online data label can indicate that the device point data is reliable, and an additional offline data label can indicate that the device point data is unreliable.

[0141] It should be noted that all the warning messages and alarm information mentioned in this application can be displayed on the display interface or the monitoring interface of the device point data management system, and can also be sent to the host computer to implement the reporting function.

[0142] This application also provides a device point data management system.

[0143] For the sake of concise writing, all the units or devices mentioned in this application are numbered in the embodiments of the device point data management system, and are not numbered in the embodiments of the foregoing device point data management method.

[0144] As Figure 3 shown, in an embodiment of this application, the device point data management system includes a management unit 100, a storage unit 200, and a service scenario unit 300.

[0145] Specifically, the management unit 100 is used to execute the device point data management method in the energy storage system mentioned in at least one of the foregoing embodiments.

[0146] The storage unit 200 is connected to the management unit 100. The storage unit 200 includes multiple caches 210 of different importance levels. The service scenario unit 300 is connected to the management unit 100.

[0147] As Figure 4 shown, in an embodiment of this application, the storage unit 200 includes a first-level cache 210, a second-level cache 220, and a third-level cache 230. The importance level of the first-level cache 210 > the importance level of the second-level cache 220 > the importance level of the third-level cache 230.

[0148] The cache can be a part of the local storage unit 200. The cache can be a Redis cache, which is a third-party open-source cache middleware, and its data is in the computer memory. Programs can read and write data from it very efficiently.

[0149] The technical features of the above-described embodiments can be combined arbitrarily, and there is no limitation on the execution order of the method steps. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0150] The above-described embodiments only represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the patent of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A method for managing equipment point data in an energy storage system, characterized in that: The method comprises: Determine whether a piece of device point data is received; If a piece of equipment point data is received, the equipment point data is obtained, and the equipment point information attached to the equipment point data is simultaneously obtained; Read the data collection time in the device point information; Obtain the difference between the data collection time and the current system time, and write the device point data into one of N caches of different importance levels according to the comparison result of the difference between the data collection time and the current system time and N-1 time-effect node values ​​in sequence; the smaller the difference between the data collection time and the current system time, the higher the priority of writing into the cache with a higher importance level; N is a positive integer; As time goes by, the control device point data flows from the cache with a higher importance level to the cache with a lower importance level; Determine whether there is at least one cache into which new device point data is written; If there is at least one cache into which new device point data is written, the business scenario rule table is retrieved; Select a newly written device point data; Determine whether the newly written equipment point data meets all usage constraints of at least one business scenario in the business scenario rule table; If the newly written device point data meets all usage constraints of at least one business scenario in the business scenario rule table, the newly written device point data is applied to perform business calculations in the business scenario that meets all usage constraints; If the newly written equipment point data does not meet all the usage constraints of at least one business scenario in the business scenario rule table, an alarm message is issued; Return to the selection of a newly written device point data until all the newly written device point data are processed.

2. The method for managing equipment point data in an energy storage system according to claim 1, characterized in that: The step of obtaining the difference between the data collection time and the current system time, and writing the device point data into one of N caches of different importance levels according to the comparison result of the difference between the data collection time and the current system time and N-1 time-effect node values ​​in sequence, comprises: Determine whether the difference between the data collection time and the current system time is greater than 0; If the difference between the data collection time and the current system time is greater than 0, then further determine whether the difference between the data collection time and the current system time is less than the first-level timeliness node value; If the difference between the data collection time and the current system time is less than the first-level time-effectiveness node value, the device point data is written into the first-level cache; If the difference between the data collection time and the current system time is greater than or equal to the first-level timeliness node value, then further determine whether the difference between the data collection time and the current system time is less than the second-level timeliness node value; If the difference between the data collection time and the current system time is less than the secondary timeliness node value, the device point data is written into the secondary cache; If the difference between the data collection time and the current system time is greater than or equal to the secondary timeliness node value, the device point data is written into the third-level cache.

3. The method for managing equipment point data in an energy storage system according to claim 1, characterized in that: After determining whether there is at least one cache into which new device point data is written, the method further includes: If there is at least one cache into which new device point data is written, an expiration time tag matching the importance level of the cache is generated, so that the expiration time of the device point data is different for different importance levels of the caches; Determine whether the cache to which the newly written device point data belongs is the cache with the lowest importance level; If the cache to which the newly written device point data belongs is not the cache with the lowest importance level, an expiration time tag is added to the newly written device point data.

4. The method for managing equipment point data in an energy storage system according to claim 3, characterized in that: The value of the expiration time tag is equal to the difference between the aging node value corresponding to the cache importance level and the data collection time of the newly written device point data.

5. The method for managing equipment point data in an energy storage system according to claim 4, characterized in that: The control device point data is transferred from a cache with a high importance level to a cache with a low importance level over time, including: Each cache traverses all the device point data stored in itself, and determines whether at least one device point data has failed based on the expiration time tag of the device point data; If at least one device point data has a failure phenomenon, then all device point data that have a failure phenomenon are obtained; Select a device point data that produces a failure phenomenon; Determine whether the cache to which the device point data that causes the failure phenomenon belongs is the cache with the lowest importance level; If the cache to which the equipment point data causing the failure phenomenon belongs is not the cache with the lowest importance level, the equipment point data causing the failure phenomenon will be deleted from the current cache, and the equipment point data causing the failure phenomenon will be transferred to the next level cache with a lower importance level, and the selected equipment point data causing the failure phenomenon will be returned until all the equipment point data causing the failure phenomenon have been processed.

6. The method for managing equipment point data in an energy storage system according to claim 5, characterized in that: The device point data that will cause the failure phenomenon is deleted from the current cache, and the device point data that will cause the failure phenomenon is transferred to the next level of cache with a lower importance level, and the device point data that will cause the failure phenomenon is selected is returned until all the device point data that will cause the failure phenomenon are processed, including: Obtain the device point label of the device point data that causes the failure phenomenon; Get whether there is device point data with the same device point tag in the next-level cache with a lower importance level than the current cache; If there is no device point data with the same device point label in the cache of the next level with a lower importance level of the current cache, the device point data that has caused the failure phenomenon is deleted from the current cache, and the device point data that has caused the failure phenomenon is transferred to the cache of the next level with a lower importance level of the current cache, and the device point data that has caused the failure phenomenon is selected and returned; If there is device point data with the same device point tag in a cache of a lower level of importance than the current cache, then the data collection time of the device point data that has failed in the current cache is obtained, and the data collection time is used as the first collection time; Obtain the data collection time of the device point data with the same device point tag in the next-level cache with a lower importance level than the current cache, and use the data collection time as the second collection time; Determining whether the first collection time is later than the second collection time; If the first acquisition time is later than the second acquisition time, the device point data that generates the failure phenomenon is deleted from the current cache, and the device point data that generates the failure phenomenon is transferred to a cache of a lower importance level of the next level of the current cache, and the device point data that generates the failure phenomenon is selected and returned; If the first acquisition time is earlier than the second acquisition time, the device point data that generates the failure phenomenon is deleted from the current cache, and the selected device point data that generates the failure phenomenon is returned.

7. The method for managing equipment point data in an energy storage system according to claim 6, characterized in that: After determining whether the cache to which the device point data that generates the failure phenomenon belongs is the cache with the lowest importance level, the method further includes: If the cache to which the device point data that has caused the failure phenomenon belongs is the cache with the lowest importance level, it is determined whether there is other device point data with the same device point tag in the current cache except for the device point data that has caused the failure phenomenon; If there are other device point data with the same device point tag in the current cache except the device point data that has failed, the device point data with the latest data collection time under the device point tag will be retained, and the remaining device point data except the device point data with the latest data collection time under the device point tag will be deleted.

8. The method for managing equipment point data in an energy storage system according to claim 7, characterized in that: Also includes: Send a request to the cache to retrieve data; Select a device point tag; The current system time is used as the current snapshot time, and the device point data of the device point tag in the cache that is closest to the current system time is obtained and stored as the snapshot data of the current snapshot time in the troubleshooting database; Return to the step of selecting a device point tag until all device point tags are processed; After a preset time period, the process returns to the step of sending a request to the cache to retrieve data.

9. The method for managing equipment point data in an energy storage system according to claim 8, characterized in that: The method of taking the current system time as the current snapshot moment, obtaining the device point data of the device point tag in the cache closest to the current system time and storing it in the troubleshooting database as the snapshot data of the current snapshot moment, includes: Traverse multiple caches of different importance levels, and obtain the device point data of the device point tag closest to the current system time in the cache of each importance level; Determine whether the acquired device point data is obtained from the cache with the lowest importance level; If the acquired device point data is acquired from the cache with the lowest importance level, an offline data tag is added to the acquired device point data; If the acquired device point data is not acquired from the cache with the lowest importance level, an online data tag is added to the acquired device point data; The device point data with online data tags and / or offline data tags attached thereto are stored in the troubleshooting database as snapshot data at the current snapshot moment.

10. A device point data management system, characterized in that: include: A management unit, configured to execute the device point data management method in the energy storage system according to any one of claims 1 to 9; A storage unit, connected to the management unit, including a plurality of caches of different importance levels; The business scenario unit is connected to the management unit.

Images