A data tracing method and system for remote nuclear containment of a battery

Abstract

The application discloses a data tracing method and system for remote battery capacity check, and relates to the technical field of power operation and maintenance data tracing, which comprises the following steps: receiving capacity check request data, extracting capacity check starting elements, performing field integrity check and starting access check on the capacity check starting elements, when the check is passed, solidifying the capacity check starting elements into capacity check starting reference records in a preset fixed field order, performing field splicing and abstract processing on the capacity check starting reference records, generating a capacity check task fingerprint, when the check is not passed, forming a starting check failure record and blocking the generation of the capacity check task fingerprint and the discharge issuing, and collecting capacity check operation data of corresponding battery groups after the capacity check task fingerprint enters a capacity check device with the remote capacity check task.

Description

Technical Field

[0001] This invention relates to the field of power supply operation and maintenance data traceability technology, and in particular to a data traceability method and system for remote capacity verification of batteries. Background Technology

[0002] With the continuous improvement of digital operation and maintenance levels in communication power supplies, data centers, substations, and rail transit backup power systems, battery pack capacity verification is gradually shifting from on-site manual operation to remote centralized management and control. Remote capacity verification typically relies on capacity verification devices, battery monitoring units, and operation and maintenance platforms to collect and record data on battery pack voltage, current, individual cell status, discharge process, and alarm events. It also completes the distribution of capacity verification tasks, operation monitoring, process recording, and report output through a networked approach. This technology can reduce on-site operational workload, improve the automation level of battery pack capacity testing, and provide a data foundation for subsequent operation and maintenance analysis.

[0003] However, existing methods have some shortcomings. There is a lack of stable correspondence between the capacity activation conditions and the actual execution process. Capacity activation requests, device reception records, operating data and capacity activation reports are easily stored in a scattered manner, making it difficult to correspond the discharge object, discharge constraints and activation access status to the actual discharge process item by item. In addition, capacity activation operation data is mostly stored in the form of logs or historical tables, making it difficult to form a continuous traceability structure around capacity activation stage changes, state switching, discharge execution changes and alarm events. It is not easy to locate the location of anomalies, alarm response status and sampling continuity, which affects the verification of capacity activation process and the traceability of responsibility. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a data traceability method for remote capacity verification of batteries to solve the problems of unstable capacity verification tasks and difficulty in tracing process anomalies.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: In a first aspect, the present invention provides a data traceability method for remote capacity verification of storage batteries, comprising: receiving capacity verification request data, extracting capacity verification start-up elements, performing field integrity verification and start-up access verification on the capacity verification start-up elements, and when the verification passes, solidifying the capacity verification start-up elements into a capacity verification start-up baseline record according to a preset fixed field order, and performing field splicing and summary processing on the capacity verification start-up baseline record to generate a capacity verification task fingerprint; when the verification fails, forming a start-up verification failure record, and blocking the generation and discharge issuance of the capacity verification task fingerprint; after the capacity verification task fingerprint enters the capacity verification device along with the remote capacity verification task, collecting the capacity verification operation data of the corresponding battery group, and generating a capacity verification status judgment result based on the group voltage data, group current data, and individual battery status data in the capacity verification operation data, and combining the capacity verification operation data and the capacity verification data... The status determination results are associated with the sampling time sequence, capacity stage, and capacity task fingerprint to generate segmented traceability data. The segmented traceability data is arranged according to the sampling time sequence, forming mandatory traceability nodes at task reception, start verification completion, discharge start, discharge stop, and task end. Traceability nodes are also formed when the capacity stage changes, the capacity status determination result changes, the discharge execution status changes, alarm events occur, and sampling interruptions occur. Adjacent traceability nodes are associated through stage summaries to form a capacity process traceability chain, and actual execution records are collected from the capacity process traceability chain. The consistency of the actual execution records and the capacity start benchmark records corresponding to the capacity task fingerprint are verified to obtain the task execution verification result. The task execution verification result is then indexed and bound to the capacity process traceability chain to generate a remote capacity traceability report for the battery.

[0007] As a preferred embodiment of the data traceability method for remote capacity verification of batteries described in this invention, the capacity verification start-up elements include the capacity verification object, capacity verification device identifier, capacity verification discharge constraint, remote operation mode status, battery pack float charging status, discharge parameter confirmation result, and operation verification result. The nuclear discharge constraints include discharge current, discharge duration, termination voltage, and termination conditions.

[0008] As a preferred embodiment of the data traceability method for remote capacity verification of batteries according to the present invention, the specific steps for generating the capacity verification task fingerprint are as follows: Arrange the capacity start-up elements according to a preset fixed field order to form ordered start-up element data; Summarize the sequential start-up element data to obtain a start-up content summary value that does not include the generation time of the baseline record; The sequential start-up element data, start-up content summary value and benchmark record generation time are linked to form the capacity start-up benchmark record; The preset fixed field order is as follows: capacity object, capacity device identifier, capacity discharge constraint, remote operation mode status, battery pack float charge status, discharge parameter confirmation result, and operation verification result. Field splicing units are generated for the fields in the capacity approval start-up baseline record. Each field splicing unit includes a field name, field type identifier, length value, and field value. The field splicing units are connected in a fixed field order to form the start-up baseline splicing data. The start-up baseline splicing data is then processed to generate the capacity approval task fingerprint.

[0009] As a preferred embodiment of the data traceability method for remote capacity assessment of batteries according to the present invention, the specific steps for generating the capacity assessment status determination result are as follows: The state determination parameters required for battery pack state determination are determined based on the pre-stored core capacity configuration data. The state determination parameters are used to characterize the voltage conditions, current conditions and time conditions in the battery pack state determination. During the execution of the remote nuclear capacity task, the current sampling time is first determined based on the nuclear capacity operation data to determine whether it belongs to a state situation that needs to be determined first. The state situation that needs to be determined first includes at least one of the abnormal state, nuclear capacity state and power outage discharge state. If the current sampling time belongs to a state situation that needs to be determined first, the battery pack state corresponding to the current sampling time is determined from the abnormal state, the state of ... If the current sampling time does not belong to the state situation that needs to be determined first, the battery pack state is determined according to the correspondence between the group voltage data, group current data and state judgment parameters, and the determined battery pack state is used as the core capacity state judgment result.

[0010] As a preferred embodiment of the data traceability method for remote capacity assessment of batteries according to the present invention, the specific steps for generating segmented traceability data are as follows: Establish a correspondence between the nuclear capacity task fingerprint and the nuclear capacity operation data, nuclear capacity status judgment result, sampling time and nuclear capacity stage. The nuclear capacity stage includes the task reception stage, the start verification stage, the nuclear capacity discharge stage, the nuclear capacity stop stage and the nuclear capacity end stage. Using the core capacity stage as the basis for segmentation, data with the same core capacity stage and continuous sampling time sequence are grouped into the same stage data segment; Arrange the data segments of each stage under the same core capacity task fingerprint according to the stage start sampling time to generate segmented traceability data.

[0011] As a preferred embodiment of the data traceability method for remote capacity assessment of batteries according to the present invention, the specific steps for forming a traceability node are as follows: Compare the data corresponding to adjacent sampling times. When at least one of the following changes, the sampling time is taken as the traceability trigger position and a traceability node is formed at the traceability trigger position. Each traceability node records the fingerprint of the capacity control task, the node sampling time, the type of triggering event, the state before triggering, and the state after triggering. The state before triggering and the state after triggering include the capacity control stage, the capacity control status determination result, the discharge execution status, the alarm event status, and the sampling continuity status.

[0012] As a preferred embodiment of the data traceability method for remote capacity verification of batteries according to the present invention, the specific steps for forming the capacity verification process traceability chain are as follows: The traceability nodes and stage summaries under the same core capacity task fingerprint are connected continuously according to the sampling time sequence, so that the traceability nodes can locate the start and end positions of the data segments corresponding to the stage summaries, thus forming a core capacity process traceability chain; When there is no traceability node, a missing stage summary, a missing forced traceability node, or a traceability node and a stage summary cannot be continuously connected according to the sampling time sequence under the same core capacity task fingerprint, an abnormal record is generated by forming a traceability chain. The stage summary refers to the data summary between adjacent traceability nodes, which is used to record the stage start and end time, group voltage changes, group current changes, individual battery status changes, alarm events, and sampling interruptions between adjacent traceability nodes.

[0013] As a preferred embodiment of the data traceability method for remote capacity verification of batteries according to the present invention, the specific steps for obtaining the task execution verification result are as follows: The actual execution records and the capacity initiation baseline records are combined according to the corresponding capacity task fingerprints to form the data to be verified; Based on the data to be verified, the consistency of the actual verification object, discharge execution process, remote operation status and start access status of this remote verification with the verification start benchmark record is verified. The alarm protection response and sampling continuity are verified with the corresponding traceability nodes and stage summaries in the verification process traceability chain to obtain the task execution verification results. The actual execution record refers to the record of this remote approval process obtained from the approval process traceability chain.

[0014] As a preferred embodiment of the data traceability method for remote capacity assessment of batteries according to the present invention, the specific steps for generating the remote capacity assessment traceability report for batteries are as follows: Establish a correlation between each verification item in the task execution verification result and the corresponding content in the capacity traceability chain; When no traceability chain for the same capacity task fingerprint is found, the corresponding traceability node is missing, or multiple traceability chains for the same capacity task fingerprint are found, an abnormal record is generated by binding the report index and marked as incomplete traceability in the remote capacity traceability report for the battery. When there are verification failures in the task execution verification results, the reason for the verification failure, the corresponding sampling time, the corresponding verification stage, and the corresponding traceability node are written into the index binding relationship; After completing the index binding, a remote battery capacity traceability report is generated.

[0015] Secondly, the present invention provides a data traceability system for remote capacity verification of batteries, comprising: a startup fingerprint module, a segmented traceability module, a traceability chain module, and a verification report module; the startup fingerprint module is used to receive capacity verification request data, extract capacity verification startup elements, perform field integrity verification and startup access verification on the capacity verification startup elements, and when the verification passes, solidify the capacity verification startup elements into a capacity verification startup benchmark record according to a preset fixed field order, and perform field splicing and summary processing on the capacity verification startup benchmark record to generate a capacity verification task fingerprint; when the verification fails, a startup verification failure record is formed, and the generation of the capacity verification task fingerprint and the discharge issuance are blocked; the segmented traceability module is used to collect the capacity verification operation data of the corresponding battery pack after the capacity verification task fingerprint enters the capacity verification device with the remote capacity verification task, and generate a capacity verification status judgment based on the group voltage data, group current data, and individual battery status data in the capacity verification operation data. The system determines the results by associating the capacity operation data and capacity status judgment results with the capacity stage and capacity task fingerprint according to the sampling time sequence, capacity stage, and capacity task fingerprint to generate segmented traceability data. The traceability chain module arranges the segmented traceability data according to the sampling time sequence, forming mandatory traceability nodes at task reception, start verification completion, discharge start, discharge stop, and task end. It also forms traceability nodes when the capacity stage changes, the capacity status judgment result changes, the discharge execution status changes, alarm events occur, and sampling interruptions occur. Adjacent traceability nodes are associated through stage summaries to form a capacity process traceability chain, and the actual execution records are collected from the capacity process traceability chain. The verification report module verifies the consistency between the actual execution records and the capacity start benchmark records corresponding to the capacity task fingerprint to obtain the task execution verification results. It then indexes and binds the task execution verification results to the capacity process traceability chain to generate a remote capacity traceability report for the battery.

[0016] The beneficial effects of this invention are as follows: By solidifying the remote capacity verification startup information into a capacity verification startup baseline record and generating a capacity verification task fingerprint that runs through the entire process of task issuance, execution, and report generation, the startup basis of each capacity verification task is stably correlated with the actual execution result, avoiding unclear task attribution and data mixing; by extracting key changes during the execution process to form traceability nodes and connecting them with stage summaries to form a capacity verification process traceability chain, and then binding the verification results to the corresponding traceability position, abnormal processes and execution deviations can be continuously restored, quickly located, and reviewed, thereby improving the integrity of remote capacity verification data traceability, verification reliability, and report credibility. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart of a data traceability method for remote capacity verification of batteries.

[0019] Figure 2 This is a schematic diagram of a data traceability system for remote capacity verification of batteries.

[0020] Figure 3 Build a flowchart for the nuclear capacity process traceability chain.

[0021] Figure 4 A flowchart for generating verification and traceability reports.

[0022] Figure 5 This is a comparison chart of the time distribution data for anomaly location. Detailed Implementation

[0023] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0024] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0025] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0026] Reference Figures 1-5 As one embodiment of the present invention, this embodiment provides a data traceability method for remote capacity verification of storage batteries, comprising the following steps: S1. Receive capacity request data, extract capacity initiation elements, perform field integrity verification and initiation access verification on the capacity initiation elements. If the verification passes, solidify the capacity initiation elements into a capacity initiation baseline record according to a preset fixed field order, and perform field splicing and summary processing on the capacity initiation baseline record to generate a capacity task fingerprint. If the verification fails, form an initiation verification failure record and block the generation and discharge of the capacity task fingerprint.

[0027] S1.1 Receive the capacity request data, and take the data in the capacity request data that represents the target, execution device, discharge boundary and start-up access conditions of this remote capacity start-up as capacity start-up elements. Perform field integrity verification and format normalization on the capacity start-up elements to form capacity start-up element data.

[0028] It should be noted that after receiving the capacity approval request data, the capacity approval object, capacity approval device identifier, capacity approval discharge constraint, remote operation mode status, battery pack float charge status, discharge parameter confirmation result and operation verification result are extracted from the capacity approval request data as capacity approval start-up elements.

[0029] The capacity start-up elements are sequentially subjected to field integrity verification and format normalization. The field integrity verification includes: verifying whether the capacity object and capacity device identifier have field values, and verifying whether there is a correspondence between the two based on the pre-stored capacity configuration data; verifying whether the capacity discharge constraints include discharge current, discharge duration, termination voltage, and termination conditions; verifying whether the remote operation mode status indicates that the capacity device is in remote operation mode, verifying whether the battery pack float charge status indicates that the battery pack is in float charge state, and verifying whether the discharge parameter confirmation result and operation verification result are both passed; when all verifications are satisfied, the capacity start-up element that has passed the integrity verification is obtained.

[0030] If the capacity verification object is missing, the capacity verification device identifier is missing, there is no corresponding relationship between the capacity verification object and the capacity verification device identifier, the capacity verification discharge constraints lack any of the following: discharge current, discharge duration, termination voltage, and termination conditions, or the remote operation mode status, battery pack float charging status, discharge parameter confirmation results, and operation verification results do not meet the start-up access requirements, a start-up verification failure record will be generated. The start-up verification failure record includes the capacity verification request reception time, capacity verification object, capacity verification device identifier, fields that failed verification, and the reason for failure. After a start-up verification failure record is generated, the capacity verification start-up element will not be fixed as a capacity verification start-up baseline record, a capacity verification task fingerprint will not be generated, and the discharge issuance of this remote capacity verification task will be blocked.

[0031] The capacity configuration data includes the correspondence between the capacity object and the capacity device identifier, the number of individual battery cells, the individual floating charge voltage configuration value, the individual equalization charge voltage configuration value, the floating charge current configuration value, the current limit value used to determine the end of pre-charging, the target charging current used to control the pre-charging process, the pre-charging duration limit value, and the pre-charging current drop-off value.

[0032] The format of the capacity start-up elements that have passed the integrity verification is normalized. The field values ​​of the capacity object are normalized to the battery pack object identifier, the field values ​​of the capacity device identifier are normalized to the equipment identifier, and the capacity discharge constraints are normalized to constraint fields arranged according to discharge current, discharge duration, termination voltage, and termination conditions. The units of measurement for discharge current, discharge duration, and termination voltage are also unified. The remote operation mode status and battery pack float charge status are normalized to valid or invalid status fields, and the discharge parameter confirmation results and operation verification results are normalized to pass or fail result fields, forming capacity start-up element data with a consistent field structure.

[0033] S1.2. Arrange the capacity approval element data in a predetermined order according to the preset fixed field order, and solidify the ordered capacity approval element data into a capacity approval benchmark record, so that the capacity approval benchmark record can represent the conditions for the start of this remote capacity approval.

[0034] It should be noted that the preset fixed field order is as follows: capacity object, capacity device identifier, capacity discharge constraint, remote operation mode status, battery pack float charge status, discharge parameter confirmation result, and operation verification result.

[0035] When sorting the data of capacity approval start-up elements, the capacity approval object, capacity approval device identifier, capacity approval discharge constraint, remote operation mode status, battery pack float charge status, discharge parameter confirmation result, and operation verification result are arranged in a fixed field order, and the field name, field value, and field order of each field are retained to form ordered start-up element data. By fixing the field order, capacity approval request data from different sources have a consistent data structure after the format normalization process is completed, avoiding the impact of the same start-up content on the subsequent summary processing results due to differences in field arrangement.

[0036] The sequential startup element data is digested to obtain a startup content summary value. The startup content summary value does not include the baseline record generation time and is used to compare whether the startup content of different remote capacity control tasks is consistent. The sequential startup element data, startup content summary value and the baseline record generation time of this remote capacity control task are bound to form a capacity control startup baseline record. The capacity control startup baseline record is used to fix the capacity control object, capacity control device identifier, capacity control discharge constraints, startup access status and startup content summary value at the time of this remote capacity control startup, and is not rewritten as the running data changes during the capacity control execution process.

[0037] S1.3 Perform field concatenation and summary processing on the capacity startup baseline record to generate a capacity task fingerprint for the corresponding capacity startup baseline record.

[0038] It should be noted that when concatenating fields in the capacity start-up baseline record, field concatenation units are generated according to the fixed field order in the capacity start-up baseline record. Each field concatenation unit includes a field name, a field type identifier, a length value, and a field value. The field type identifier is used to distinguish between object identifiers, equipment identifiers, constraint fields, status fields, result fields, and time fields. The length value is the byte length of the field value after unified encoding, used to determine the start and end positions of the field value in the concatenated data. For the discharge current, discharge duration, and termination voltage in the capacity discharge constraints, the measurement units and numerical formats after format normalization are used in the field concatenation. The field concatenation units are connected sequentially according to the fixed field order to form the start-up baseline concatenation data.

[0039] For example, the start-up baseline splicing data can be represented as: Capacity Object | Object Identifier | Length Value | BAT-G01; Capacity Device Identifier | Equipment Identifier | Length Value | CT48-21-001; Capacity Discharge Constraint | Constraint Field | Length Value | Discharge Current = 100.00A, Discharge Duration = 120min, Termination Voltage = 43.20V, Termination Condition = Stop when Termination Voltage is Reached; Remote Operation Mode Status | Status Field | Length Value | Valid; Battery Pack Float Charge Status | Status Field | Length Value | Valid; Discharge Parameter Confirmation Result | Result Field | Length Value | Passed; Operation Verification Result | Result Field | Length Value | Passed; Baseline Record Generation Time | Time Field | Length Value | 2026-01-03T10:00:00+08:00.

[0040] The "|" symbol is used to distinguish the content of fields within the same field concatenation unit, while the ";" symbol is used to distinguish adjacent field concatenation units. The examples are only for illustrating the field concatenation method and do not limit the specific field values.

[0041] When performing digest processing on the startup baseline concatenated data, Chinese characters, English letters, numbers, unit symbols, separators, and time characters in the startup baseline concatenated data are uniformly converted into UTF-8 encoded byte sequences. Then, a preset digest algorithm is used to calculate the digest of the UTF-8 encoded byte sequences to obtain a digest value of fixed length, and the digest value is used as the fingerprint of the core capacity task.

[0042] The digest processing rules include digest algorithm identifier, encoding format, digest output length, and digest character output format. The digest processing rules are written into the capacity control startup baseline record and distributed to the capacity control device and report generation end along with the capacity control task fingerprint, so that the task distribution end, capacity control device, and report generation end generate and verify the capacity control task fingerprint according to the same digest processing rules. The digest algorithm can be the SM3 digest algorithm.

[0043] S2. After the capacity verification task fingerprint enters the capacity verification device along with the remote capacity verification task, it collects the capacity verification operation data of the corresponding battery pack, and generates the capacity verification status judgment result based on the group voltage data, group current data and individual battery status data in the capacity verification operation data. The capacity verification operation data and capacity verification status judgment result are associated with the capacity verification task fingerprint according to the sampling time sequence, capacity verification stage and capacity verification task fingerprint to generate segmented traceability data.

[0044] S2.1 After the verification task fingerprint enters the verification device along with the remote verification task, the verification device binds the verification task fingerprint with the reception time, verification object and verification device identifier of the remote verification task to form a task reception record.

[0045] It should be noted that the nuclear capacity device determines the reception time of the remote nuclear capacity task. The reception time is the time record formed when the nuclear capacity device receives the remote nuclear capacity task. The reception time is correlated with the nuclear capacity task fingerprint to determine the start time when the remote nuclear capacity task corresponding to the current nuclear capacity task fingerprint enters the nuclear capacity device.

[0046] The capacity verification device binds the capacity verification object and the capacity verification device identifier to the capacity verification task fingerprint. The capacity verification object is used to identify the battery pack to which this remote capacity verification task is directed, and the capacity verification device identifier is used to identify the capacity verification device that performs this remote capacity verification task. The capacity verification device verifies whether the capacity verification object belongs to the capacity verification device corresponding to the capacity verification device identifier based on the capacity verification configuration data. When there is a correspondence between the capacity verification object and the capacity verification device identifier, the capacity verification task fingerprint, the reception time, the capacity verification object and the capacity verification device identifier are combined to form a task reception record.

[0047] If there is no corresponding relationship between the nuclear capacity object and the nuclear capacity device identifier, the nuclear capacity device will generate a task reception anomaly record. The task reception anomaly record includes the nuclear capacity task fingerprint, reception time, nuclear capacity object, nuclear capacity device identifier, and the reason for the object-device mismatch. After generating the task reception anomaly record, the nuclear capacity device will not initiate this remote nuclear capacity discharge and will write the task reception anomaly record back to the subsequent traceability report.

[0048] S2.2 The capacity verification device determines the corresponding battery pack based on the task reception record and continuously collects capacity verification operation data during the remote capacity verification task execution. Based on the pack voltage data, pack current data and individual cell status data, it determines the battery pack status from float charging, pre-charging, capacity verification, power outage discharge, abnormal, equalization charging, discharge and static states. The capacity verification operation data and the corresponding status judgment results are marked according to the sampling time sequence and capacity verification stage to form time-series stage operation data.

[0049] It should be noted that the capacity verification device determines the battery pack corresponding to this remote capacity verification based on the task reception record, and uses this battery pack as the object of capacity verification operation data collection. During the execution of the remote capacity verification task, the capacity verification device continuously collects capacity verification operation data according to the sampling time. The capacity verification operation data includes pack voltage data, pack current data, individual cell status data, discharge execution data, and alarm event data. Among them, the pack current data is used to characterize the current direction and current magnitude of the battery pack, the discharge execution data is used to characterize whether the capacity verification discharge is started, continues, and stops, and the alarm event data is used to characterize the system alarms, pack alarms, and individual cell alarms generated during the capacity verification process.

[0050] Before determining the status of the battery pack, the status determination parameters are determined based on the approved capacity configuration data. These parameters include the float charge voltage threshold, float charge current threshold, equalization charge voltage threshold, pre-charge current threshold, pre-charge current setpoint, pre-charge duration threshold, and pre-charge current drop-off value. The float charge voltage threshold and equalization charge voltage threshold can be determined using the following formula: ; ; in, Indicates the first The floating charge voltage threshold corresponding to the next remote capacity task; Indicates the first The number of individual battery cells corresponding to each remote capacity mission; Indicates the first The single-unit floating charge voltage configuration value corresponding to the next remote core capacity task; Indicates the first The equalization charge voltage threshold corresponding to each remote capacity task; Indicates the first The single-unit equalization charge voltage configuration value corresponding to the next remote core capacity task; This indicates the index of the remote core capacity task.

[0051] Among them, the float charge voltage threshold is obtained by multiplying the number of battery cells in the battery pack by the float charge voltage configuration value of each cell, the equalization charge voltage threshold is obtained by multiplying the number of battery cells in the battery pack by the equalization charge voltage configuration value of each cell, and the float charge current threshold, precharge current threshold, precharge current setting value, precharge duration threshold and precharge current drop difference value are respectively taken from the corresponding configuration values ​​in the core capacity configuration data.

[0052] The status determination parameters in the capacity configuration data are derived from the battery manufacturer's maintenance procedures, capacity device configuration table, site rated voltage level, and on-site setting records. When the configuration values ​​from the sources are inconsistent, the configuration table that has already taken effect in the capacity device before the issuance of this remote capacity allocation task shall prevail. The float charge voltage threshold and equalization charge voltage threshold are calculated from the number of individual battery cells and the corresponding individual cell voltage configuration values. The float charge current threshold, precharge current threshold, precharge current setting value, precharge duration threshold, and precharge current drop difference value are determined by the corresponding configuration items in the capacity device configuration table and are not reset using temporary empirical values.

[0053] For example, for a 48V communication battery pack composed of 24 2V individual cells, when the individual cell float charge voltage configuration value is 2.25V, the float charge voltage threshold is 54.00V; when the individual cell equalization charge voltage configuration value is 2.35V, the equalization charge voltage threshold is 56.40V; the float charge current threshold, pre-charge current threshold, pre-charge current setting value, pre-charge duration threshold, and pre-charge current drop-off value can be determined by the corresponding configuration items, and the values ​​are only used to illustrate the determination method of the state judgment parameters and do not limit the specific values.

[0054] When determining the status of the battery pack, the main status is determined in the following order: abnormal status, full capacity status, power outage discharge status, pre-charge status, equalization charge status, discharge status, float charge status, and resting status, so that each sampling moment corresponds to one main status determination result. At the same time, a concurrent status marker is formed based on the alarm event data, discharge execution data, and pack current direction at the same sampling moment. The concurrent status marker is used to record abnormal content, full capacity discharge content, and power outage discharge content that occur simultaneously outside of the main status. When there is at least one abnormal content among communication abnormality, Hall connection abnormality, pack module abnormality, and individual cell abnormality alarm, the battery pack status is determined to be abnormal. When the discharge execution data indicates that the current remote full capacity discharge is being executed, the battery pack status is determined to be full capacity. When the alarm event data indicates that the rectifier is undervoltage and the pack current direction indicates that the battery pack is supplying power to the load, the battery pack status is determined to be power outage discharge.

[0055] When the discharge execution data indicates that the remote core capacity discharge is in progress and there is also abnormal content, the main state is determined according to priority, and the abnormality in the core capacity is recorded in the concurrent state flag; when the discharge execution data indicates that the remote core capacity discharge is in progress and the alarm event data indicates a power outage discharge, the main state is determined according to priority, and the power outage discharge in the core capacity is recorded in the concurrent state flag; the main state is used to ensure the uniqueness of the state determination result, and the concurrent state flag is used to retain the composite operating facts at the same sampling time.

[0056] The battery pack status is determined using the following formula: ; ; ; ; ; in, Indicates the first The next remote capacity refactoring task was in Battery pack status at each sampling time; Indicates the candidate state; , , and These represent float charging, equalizing charging, discharging, and stationary states, respectively. Indicates the first The next remote capacity refactoring task was in Each sampling time corresponds to a candidate state Judgment margin; This indicates a specific sampling time. Indicates the first The next remote capacity refactoring task was in Group voltage at each sampling time; Indicates the first The next remote capacity refactoring task was in The current at each sampling time is used, with positive values ​​indicating the charging direction and negative values ​​indicating the discharging direction. Indicates the first The floating charge current threshold corresponding to the next remote capacity task; This indicates that the candidate state with the largest decision margin is selected. This indicates taking the smaller value among the terms within the parentheses; This indicates the absolute value of the group current.

[0057] When the battery pack enters the charging process after the core discharge is completed but the current conditions for switching to float charging are not met, the battery pack is determined to be in pre-charging mode. The current conditions for switching to float charging include any of the following: the charging current is less than the pre-charging current threshold; the pre-charging duration is greater than the pre-charging duration threshold; and the charging current is less than the difference current value determined by the difference between the pre-charging current setpoint and the pre-charging current drop-off value. The difference current value can be determined by the following formula: ; in, Indicates the first The differential current value corresponding to the next remote core capacity task; Indicates the first Precharge current setting value corresponding to the next remote capacity task; Indicates the first The difference in pre-charge current drop corresponding to the next remote capacity mission.

[0058] When the pre-charge current setting value is greater than the pre-charge current drop difference value, the difference current value is determined according to the difference between the pre-charge current setting value and the pre-charge current drop difference value; when the pre-charge current setting value is not greater than the pre-charge current drop difference value, a pre-charge configuration abnormality record is formed, and the difference current value is not used to determine whether to switch to float charging.

[0059] When the absolute value of the group current is greater than the float charging current threshold, the direction of the group current indicates charging, and the group voltage is higher than the equalizing charging voltage threshold, the battery group is determined to be in the equalizing charging state; when the absolute value of the group current is greater than the float charging current threshold and the direction of the group current indicates discharging, the battery group is determined to be in the discharging state; when the absolute value of the group current does not exceed the float charging current threshold and the group voltage is not lower than the float charging voltage threshold, the battery group is determined to be in the float charging state; when the absolute value of the group current does not exceed the float charging current threshold and the group voltage is lower than the float charging voltage threshold, the battery group is determined to be in the quiescent state.

[0060] After obtaining the status determination result, the corresponding nuclear capacity operation data, status determination result, sampling time and nuclear capacity stage at each sampling time are marked to form time-series stage operation data; among them, the nuclear capacity stage is determined according to the execution process of the remote nuclear capacity task, including the task reception stage, the start verification stage, the nuclear capacity discharge stage, the nuclear capacity stop stage and the nuclear capacity end stage.

[0061] S2.3. Associate the time-series stage operation data with the core capacity task fingerprint corresponding to the task reception record, and collect the time-series stage operation data in segments according to the core capacity stage to generate segmented traceability data corresponding to the core capacity task fingerprint.

[0062] It should be noted that after the time-series phase operation data is formed, the core capacity task fingerprint corresponding to the task receiving record is used as the task attribution mark, and a correspondence is established with the core capacity operation data, status judgment result, sampling time and core capacity phase in the time-series phase operation data, forming time-series phase operation data with core capacity task fingerprint, so that the sampling data under the same remote core capacity task can be matched through the core capacity task fingerprint.

[0063] When segmenting and aggregating time-series stage operation data with kernel capacity task fingerprints, the kernel capacity stage is used as the segmentation basis. Time-series stage operation data with the same and continuous kernel capacity stage in the sampling time series are aggregated into the same stage data segment. When the same kernel capacity stage is separated by other kernel capacity stages in the sampling time series, different stage data segments are formed according to the order of appearance to avoid non-continuous data being aggregated into the same stage data segment.

[0064] Each stage data segment includes the core capacity task fingerprint, core capacity stage, stage start sampling time, stage end sampling time, core capacity operation data and status judgment results arranged by sampling time within the core capacity stage; if there is alarm event data within the current core capacity stage, the alarm event data will be included in the current stage data segment according to the corresponding sampling time.

[0065] Arrange the data segments of each stage under the same capacity task fingerprint according to the starting sampling time of the stage to generate segmented traceability data corresponding to the capacity task fingerprint.

[0066] S3. Arrange the segmented traceability data according to the sampling time sequence, and form a mandatory traceability node at task reception, start verification completion, discharge start, discharge stop and task end. Traceability nodes are also formed when the capacity stage changes, the capacity status judgment result changes, the discharge execution status changes, alarm events occur and sampling interruptions occur. Adjacent traceability nodes are associated through stage summaries to form a capacity process traceability chain, and the actual execution records are collected from the capacity process traceability chain.

[0067] Figure 3 This is used to illustrate the construction process of the nuclear capacity process traceability chain. After the segmented traceability data is arranged according to the nuclear capacity task fingerprint and sampling time sequence, traceability nodes are formed at the locations of task reception, start verification completion, discharge start, discharge stop, task end, nuclear capacity stage changes, status judgment result changes, discharge execution status changes, alarm event occurrences, and sampling interruption occurrences. The data between adjacent traceability nodes form a stage summary, and are connected in the order of the previous traceability node, stage summary, and subsequent traceability node to obtain the nuclear capacity process traceability chain.

[0068] S3.1 Arrange the segmented traceability data corresponding to the core capacity task fingerprint in sequence according to the sampling time sequence to form time sequence traceability data.

[0069] It should be noted that the segmented traceability data includes multiple stage data segments under the same nuclear capacity task fingerprint. Each stage data segment contains the stage start sampling time, the stage end sampling time, and the nuclear capacity operation data and status judgment results arranged by sampling time within that nuclear capacity stage.

[0070] When arranging segmented traceability data sequentially, the fingerprint of the capacity control task is used to determine all the stage data segments corresponding to this remote capacity control, and the order between stage data segments is determined according to the start sampling time of each stage data segment; for stage data segments with the same start sampling time, the order is determined according to the end sampling time of the stage and the arrangement order of the stage data segments in the segmented traceability data, so that the stage data segments under the same capacity control task fingerprint have a definite temporal position.

[0071] After determining the order of data segments, the existing sampling time order within each data segment is retained. The core capacity operation data, status judgment results, sampling time, core capacity stage, and existing alarm event data in each data segment are then continuously organized according to the sampling time to form time-series traceability data covering this remote core capacity process.

[0072] S3.2. Take the changes in the core capacity stage, the changes in the core capacity status determination result, the changes in the discharge execution status, and the occurrence of alarm events in the time-series traceability data as traceability trigger events, form traceability nodes at the corresponding positions of the traceability trigger events, and record the core capacity stage, battery pack status, discharge execution status, alarm event status, and sampling continuity status before and after the traceability node. Perform summary processing on the data between adjacent traceability nodes to form node traceability data associated through stage summaries.

[0073] It should be noted that, according to the chronological order of sampling time, the time-series tracing data corresponding to adjacent sampling times are compared; the tracing trigger strength between adjacent sampling times is calculated using the following formula, and it is determined whether a tracing node has been formed: ; ; ; in, Indicates the first The next remote capacity refactoring task was in The traceability trigger strength at each sampling moment; Indicates the first The next remote capacity refactoring task was in The core capacity phase at each sampling time; Indicates the first The next remote capacity refactoring task was in Discharge execution status at each sampling time; Indicates the first The next remote capacity refactoring task was in Alarm event status at each sampling time; Indicates the first The next remote capacity refactoring task was in The result of the traceability trigger judgment at each sampling moment; This represents the difference determination function, which takes the value 1 when the two inputs are inconsistent and takes the value 0 when they are consistent.

[0074] If the current and subsequent sampling times are different in terms of the core capacity stage, it is determined that a core capacity stage change has occurred; if the current and subsequent sampling times are different in terms of the state determination result, it is determined that a core capacity state determination result change has occurred; if the discharge execution data at the current and subsequent sampling times changes in the state representing discharge initiation, discharge continuation, and discharge termination, it is determined that a discharge execution state change has occurred; if the alarm event data at the current and subsequent sampling times changes from no alarm to alarm, or at least one of the alarm event type, alarm object, or alarm state changes, it is determined that an alarm event has occurred.

[0075] When at least one of the following situations is identified: change in capacity stage, change in capacity status determination result, change in discharge execution status, and occurrence of alarm event, the corresponding sampling time is used as the traceability trigger position, and a traceability node is formed at the traceability trigger position. Each traceability node records the capacity task fingerprint, node sampling time, trigger event type, capacity stage before trigger, capacity stage after trigger, battery pack status before trigger, battery pack status after trigger, discharge execution status before trigger, discharge execution status after trigger, alarm event status before trigger, and alarm event status after trigger.

[0076] In addition to forming traceability nodes based on traceability trigger events, mandatory traceability nodes are formed at task reception, start verification completion, discharge start, discharge stop, and task end. When the start verification fails, a mandatory traceability node is formed at the moment of start verification failure. The mandatory traceability node is used to fix the beginning and end boundaries and key execution boundaries of this remote capacity approval task, and is not limited by whether the status changes or whether an alarm event occurs.

[0077] When the time interval between consecutive sampling times exceeds the allowable time range corresponding to the data acquisition configuration of the nuclear capacity device, a sampling interruption is determined to have occurred, and the location corresponding to the sampling interruption is used as the traceability trigger location to form an independent traceability node; the traceability node records the sampling interruption start time, sampling interruption end time, nuclear capacity stage to which it belongs, and sampling resumption time.

[0078] The sampling continuity status is determined based on the time interval between adjacent sampling times; the data acquisition configuration of the capacity device includes configuring the sampling period, clock synchronization allowable error, and communication delay allowable error; when the time interval between adjacent sampling times is within the allowable time range jointly determined by the configured sampling period, clock synchronization allowable error, and communication delay allowable error, the sampling continuity status is continuous; when the time interval between adjacent sampling times exceeds the allowable time range, the sampling continuity status is interrupted, and the start and end times of the interruption, the capacity stage to which it belongs, and the resumption time of sampling are recorded; the sampling continuity status is written to the corresponding traceability node.

[0079] Using the time-series tracing data between two adjacent tracing nodes as the data to be summarized, stage summary processing is performed on the data to be summarized. Stage summary processing includes: determining the start and end sampling times between adjacent tracing nodes, statistically analyzing the capacity stage, battery pack status, discharge execution status, alarm event status, and sampling continuity status within this time range, and forming a stage summary based on the group voltage data, group current data, and individual battery status data within this time range. The stage summary includes the stage start and end times, group voltage variation range, group current variation range, individual battery status change records, alarm event records, and sampling interruption records. Adjacent tracing nodes are associated with the corresponding stage summaries to form node tracing data.

[0080] S3.3. Organize the node traceability data continuously according to the sampling time sequence to form a traceability chain of the traceability process corresponding to the traceability task fingerprint, and collect the actual execution record of this remote traceability from the traceability chain of the traceability process, so that the actual execution record and the traceability task fingerprint can be corresponded.

[0081] It should be noted that when organizing node traceability data continuously, the node traceability data under the same core capacity task fingerprint is arranged according to the node sampling time, and connected according to the correspondence between the previous traceability node, the stage summary and the next traceability node. The traceability node is used to locate the start and end positions of the data segment corresponding to the stage summary, and the stage summary is used to characterize the core capacity operation process between two traceability nodes. According to this connection method, all node traceability data under the same core capacity task fingerprint are continuously organized to form a core capacity process traceability chain.

[0082] If there is no traceability node, a missing forced traceability node, or a missing stage summary under the same capacity task fingerprint, or if the traceability node and the stage summary cannot be continuously connected according to the sampling time sequence, a normal capacity process traceability chain will not be generated, and a traceability chain generation anomaly record will be formed. The traceability chain generation anomaly record includes the capacity task fingerprint, anomaly type, missing traceability node content, missing stage summary content, and sampling time position that cannot be continuously connected.

[0083] The actual execution records of this remote capacity verification are collected from the capacity verification process traceability chain. The actual execution records include the actual capacity verification object, the actual discharge execution status, the remote operation mode status, the alarm response status, and the sampling continuity. Among them, the actual capacity verification object is determined according to the capacity verification object corresponding to the capacity verification task fingerprint in the capacity verification process traceability chain; the actual discharge execution status is determined according to the changes in the discharge execution status in the capacity verification process traceability chain and the stage summary corresponding to the capacity verification discharge stage; the remote operation mode status is determined according to the operation mode status recorded in the capacity verification operation data; the alarm response status is determined according to the traceability node after the alarm event occurs, the changes in the discharge execution status, and the status judgment results corresponding to the abnormal status; and the sampling continuity is determined according to the sampling continuity status recorded by each traceability node and the sampling discontinuity records in the stage summary.

[0084] The alarm response information includes the time of alarm event occurrence, alarm event type, alarm object, protection action record, and discharge stop result. Among them, the protection action record is used to characterize the protection processing content formed by the nuclear capacity device after the occurrence of the alarm event, and the discharge stop result is used to characterize whether the nuclear capacity discharge stops when the alarm event type requires the discharge to be stopped.

[0085] Establish a correspondence between the actual execution record and the approval task fingerprint, so that the actual execution record can be mapped to the approval process traceability chain through the approval task fingerprint.

[0086] Figure 5This diagram illustrates the differences in anomaly location time distribution between the comparison method and the present invention under different anomaly types. The horizontal axis corresponds to four types of traceability triggering scenarios: changes in core capacity stage, changes in state determination results, changes in discharge execution state, and the occurrence of alarm events. The box-line distribution represents the discreteness of location time in multiple simulation experiments. Figure 5 It is evident that the solution of this invention has a shorter location time and a more concentrated distribution under various anomalies, indicating that by forming a traceability chain for the core process through traceability nodes and stage summaries, the abnormal process can be located to the corresponding sampling time, core process and traceability node, thereby improving the efficiency of anomaly review and the reliability of traceability.

[0087] Figure 5 The previous comparison method refers to querying the abnormal location one by one using ordinary capacity logs or historical data tables. This method does not form traceability nodes at key change locations, nor does it connect adjacent traceability nodes through stage summaries. Therefore, it is necessary to backtrack a lot of original records when locating anomalies. The solution of this invention is to use traceability nodes, stage summaries, and capacity process traceability chains to locate anomalies. This allows the time of anomaly occurrence, the capacity stage to which it belongs, and the corresponding traceability location to be directly located, thereby shortening the anomaly location time and reducing the amount of data to be reviewed.

[0088] Figure 5 The experimental data were obtained from multiple sets of remote nuclear capacity simulation tasks and historical nuclear capacity record playback tasks. Each set of tasks included nuclear capacity request data, nuclear capacity operation data, discharge execution data, alarm event data, and traceability report data. The present invention and the control method used the same task dataset for processing and statistically analyzed the anomaly location time under different anomaly types to compare the data traceability effect under different traceability methods.

[0089] It should also be noted that existing technologies typically store data by time using capacity logs or historical data tables, which makes it difficult to reflect the continuous relationship between stage changes, state transitions, discharge execution changes, and alarm events. This solution organizes segmented traceability data according to the sampling time sequence, forms traceability nodes at key change locations, and associates adjacent traceability nodes with stage summaries to form a capacity process traceability chain. It can clearly locate discharge initiation, discharge termination, state changes, alarm occurrence, and sampling interruption, reducing the workload of searching through original logs one by one, and ensuring that the actual execution records correspond to the capacity task fingerprint, providing a basis for subsequent consistency verification and traceability report generation.

[0090] S4. Verify the consistency between the actual execution record and the capacity launch baseline record corresponding to the capacity task fingerprint to obtain the task execution verification result. Then, index and bind the task execution verification result with the capacity process traceability chain to generate a remote capacity traceability report for the battery.

[0091] Figure 4This module is used to demonstrate the execution verification and traceability report generation process. The verification report module uses the fingerprint of the capacity approval task as the corresponding marker, and combines the actual execution record and the capacity approval start-up baseline record to form the data to be verified. It performs consistency verification on the actual capacity approval object, discharge execution process, remote operation status and start-up access status. When there are verification failure items or index binding anomalies, the corresponding reasons, sampling time, capacity approval stage and traceability node are written into the report index, and finally a remote capacity approval traceability report for the battery is generated.

[0092] S4.1 Using the fingerprint of the capacity-controlled task as the corresponding marker, the actual execution record is matched with the capacity-controlled startup baseline record to form data to be verified, so that the data to be verified contains both startup conditions and execution process content.

[0093] It should be noted that the corresponding nuclear capacity task fingerprint of the actual execution record is used as the corresponding marker to find the nuclear capacity startup baseline record with the same nuclear capacity task fingerprint; when the actual execution record and the nuclear capacity startup baseline record have the same nuclear capacity task fingerprint, it is determined that the two belong to the same remote nuclear capacity task.

[0094] The start-up conditions are defined as follows: the start-up object, start-up device identifier, start-up discharge constraints, remote operation mode status, battery pack float charge status, discharge parameter confirmation results, and operation verification results in the start-up baseline record. The execution process is defined as follows: the actual start-up object, actual discharge execution status, remote operation mode status, alarm response status, and sampling continuity in the actual execution record. The start-up conditions and execution process are combined according to the start-up task fingerprint to form the data to be verified. The data to be verified is used to verify the consistency of the start-up conditions and execution process under the same start-up task fingerprint.

[0095] If no corresponding baseline record with the same baseline task fingerprint as the actual execution record is found, the actual execution record is marked as missing baseline record, and the missing baseline record status is written into the data to be verified. If multiple baseline records with the same baseline task fingerprint are found, the baseline record whose generation time is no later than the reception time in the task reception record and is closest to that reception time is selected as the object to be verified, and a duplicate record mark is written into the data to be verified.

[0096] S4.2. Based on the data to be verified, perform consistency verification on the actual capacity objects, actual discharge execution status, remote operation mode status, start-up access status, alarm protection response status, and sampling continuity in the actual execution record. Among them, the start-up access status is used to verify whether the battery pack meets the requirements of float charge status and remote operation mode when discharge starts. The alarm protection response status is used to verify whether a protection action record corresponding to the alarm event type is formed after the alarm event occurs, and to verify whether a discharge stop result is formed when the alarm event type requires the discharge to be stopped. The task execution verification result is formed based on the consistency verification result.

[0097] It should be noted that when performing consistency verification based on the data to be verified, the start-up conditions in the capacity start-up baseline record are used as the verification baseline, and the execution process in the actual execution record is used as the verification object. If there is a missing baseline record in the data to be verified, the task execution verification result is marked as a missing baseline. If there is a duplicate record mark in the data to be verified, the duplicate record mark is written into the task execution verification result, and the consistency verification between the selected capacity start-up baseline record and the actual execution record continues.

[0098] When performing consistency verification on the actual capacity-controlled object, the capacity-controlled object and capacity-controlled device identifier in the capacity-controlled initiation baseline record are compared with the actual capacity-controlled object and capacity-controlled device identifier in the actual execution record. If the capacity-controlled object is consistent, the capacity-controlled device identifier is consistent, and the correspondence between the two is established, the actual capacity-controlled object verification is determined to be successful; otherwise, the actual capacity-controlled object verification is determined to be unsuccessful, and the inconsistency is recorded.

[0099] When performing consistency verification on the start-up access status, verify whether the remote operation mode status, battery pack float charge status, discharge parameter confirmation result, and operation verification result in the capacity start-up benchmark record are valid. Also verify whether the remote operation mode status at the corresponding sampling time before discharge start in the actual execution record is remote operation mode and whether the battery pack status is float charge. If all the contents are satisfied, the start-up access status verification is determined to be passed; otherwise, the start-up access status verification is determined to be failed, and the unsatisfied access items are recorded.

[0100] When verifying the consistency of actual discharge execution, the capacity discharge constraints in the capacity start-up benchmark record are compared with the discharge execution data in the actual execution record. The verification includes whether the actual discharge started after passing the start-up access state, whether the difference between the actual discharge current and the discharge current requirement is within the preset current allowable deviation range, whether the difference between the actual discharge duration and the discharge duration requirement is within the preset duration allowable deviation range, whether the difference between the group voltage at the time of actual discharge stop and the termination voltage requirement is within the preset voltage allowable deviation range, and whether the reason for actual discharge stop meets the termination condition requirements. If all the contents are met, the actual discharge execution is determined to have passed the verification. If the contents are not met and there is no protective early termination, the actual discharge execution is determined to have failed the verification, and the corresponding discharge execution abnormality is recorded.

[0101] The termination voltage requirement is used to characterize the group voltage that should reach the termination voltage in the nuclear capacity discharge constraint when the remote nuclear capacity discharge stops. When the difference between the group voltage at the actual discharge stop and the termination voltage requirement is within the preset voltage allowable deviation range, the termination voltage verification is determined to be passed. When the difference between the group voltage at the actual discharge stop and the termination voltage requirement exceeds the preset voltage allowable deviation range, the termination voltage verification is determined to be failed, and the sampling time, nuclear capacity stage and corresponding traceability node are written into the discharge execution anomaly content.

[0102] Before calculating the actual discharge execution deviation, verify the sampling time set, discharge current requirements, discharge duration requirements, and termination voltage requirements for the capacity discharge stage. If the sampling time set for the capacity discharge stage is empty, the number of sampling times is 0, or there are empty values, 0 values, or non-positive values ​​in the discharge current requirements, discharge duration requirements, and termination voltage requirements, do not calculate the actual discharge execution deviation. Mark the actual discharge execution status as insufficient discharge execution data or abnormal capacity discharge constraints, and determine the corresponding verification item as failing and pending review.

[0103] The actual discharge execution deviation is calculated using the following formula, and the verification result of the actual discharge execution is determined based on the actual discharge execution deviation: ; ; in, Indicates the first The actual discharge execution deviation of the second remote nuclear capacity mission; Indicates the first Set of sampling moments during the nuclear capacity discharge phase of the secondary remote nuclear capacity mission; express The number of sampling times in the data; This indicates the discharge current requirement in nuclear discharge constraints. Indicates the actual discharge duration; This indicates the discharge duration requirement within the nuclear discharge constraint. This indicates the group voltage at the point when the actual discharge stops; This indicates the termination voltage requirement in nuclear discharge constraints. Indicates the actual reason for the discharge stopping; This indicates the termination condition in nuclear discharge constraint; This indicates the verification result of the actual discharge execution. A value of 1 indicates that the verification passed, and a value of 0 indicates that the verification failed. Indicates the first The preset discharge execution deviation threshold corresponds to the next remote capacity task.

[0104] Before setting the preset discharge execution deviation threshold, verify whether the discharge current requirement, discharge duration requirement, and termination voltage requirement are all valid positive values. If any requirement is empty, 0, or non-positive, an abnormal record of the capacity discharge constraint is generated, the normal preset discharge execution deviation threshold is not generated, and the actual discharge execution result is determined to be unsuccessful and pending review.

[0105] The steps for setting the preset discharge execution deviation threshold include: obtaining the discharge current requirement, discharge duration requirement, and termination voltage requirement corresponding to this remote capacity control task from the capacity configuration data; determining the allowable current deviation, allowable duration deviation, and allowable voltage deviation based on the current sampling accuracy, discharge current control accuracy, voltage sampling accuracy, sampling time recording accuracy, and discharge stop response time of the capacity control device; and summing the ratios of the allowable current deviation to the discharge current requirement, the allowable duration deviation to the discharge duration requirement, and the allowable voltage deviation to the termination voltage requirement to obtain the preset discharge execution deviation threshold.

[0106] The preset discharge execution deviation threshold can be determined by the following formula: ; in, Indicates the first The allowable current deviation for this remote nuclear capacity mission; Indicates the first Discharge current requirements for this remote nuclear capacity mission; Indicates the first Allowable time deviation for each remote capacity control task; Indicates the first Discharge duration requirements for each remote nuclear capacity mission; Indicates the first The permissible voltage deviation corresponding to this remote nuclear capacity mission; Indicates the first Termination voltage requirements for this remote nuclear capacity mission.

[0107] For example, for a remote capacity approval task of a 48V battery pack with a discharge current requirement of 100A, a discharge duration requirement of 120min, and a termination voltage requirement of 43.20V, if the allowable deviation of the current sampling error and discharge current control fluctuation of the capacity approval device is 2A, the allowable deviation of the duration corresponding to the sampling time recording error and discharge stop response time is 1min, and the allowable deviation of the voltage sampling error and discharge stop action lag is 0.5V, then the preset discharge execution deviation threshold is: ; Considering the differences in sampling accuracy among different nuclear capacity devices and the short-term fluctuations during the discharge execution process, the preset discharge execution deviation threshold can be set to 0.05 for example.

[0108] When the actual discharge execution deviation does not exceed the preset discharge execution deviation threshold and the actual discharge stop reason meets the termination conditions, the actual discharge execution is verified as passed, and the discharge stop type is marked as normal termination. When the protection action corresponding to the alarm event type requires stopping the discharge, and a protection action record and discharge stop result are generated after the alarm event occurs, the discharge stop type is marked as protective early termination, and the stop result is included in the alarm protection response verification. It is not directly determined as an abnormal discharge execution because the actual discharge stop reason is inconsistent with the original termination conditions. When the actual discharge execution deviation exceeds the preset discharge execution deviation threshold and there is no protective early termination situation, the actual discharge execution is verified as failed.

[0109] When verifying the consistency of the remote operation mode status, the remote operation mode status is verified at the corresponding sampling times before discharge starts, during discharge execution, and when discharge stops. If the remote operation mode is maintained at all sampling times, the remote operation mode status verification is determined to be passed. If a local operation mode or a locked operation mode exists, the remote operation mode status verification is determined to be failed, and the corresponding sampling time is recorded.

[0110] When verifying the consistency of alarm protection response, locate the alarm event occurrence time and alarm event type in the actual execution record, and determine the maximum allowable response time corresponding to the alarm event type based on the protection strategy or alarm level configuration of the capacity device; verify the traceability node, stage summary, protection action record, and discharge execution status change corresponding to the alarm event occurrence; when an alarm event occurs, form a protection action record corresponding to the alarm event type within the maximum allowable response time, and form a stop discharge result within the maximum allowable response time when the alarm event type requires stopping discharge, thus confirming that the alarm protection response verification is passed; if no corresponding record is formed or the formation time exceeds the maximum allowable response time, confirm that the alarm protection response verification is failed, and record the alarm event occurrence time, alarm event type, missing response content, and response timeout content.

[0111] When verifying the consistency of sampling continuity, the sampling continuity status in the actual execution record and the sampling interruption record in the stage summary are verified. If the adjacent sampling time intervals in each capacity stage meet the data acquisition configuration of the capacity device and there is no sampling interruption record in the stage summary, the sampling continuity verification is determined to be passed. Otherwise, the sampling continuity verification is determined to be failed, and the start and end time of the sampling interruption and the capacity stage to which it belongs are recorded.

[0112] After verification, the verification results of the actual capacity object, the actual discharge execution, the remote operation mode status, the start access status, the alarm protection response, and the sampling continuity are summarized to form the task execution verification results.

[0113] S4.3. Index and bind the task execution verification results with the capacity verification process traceability chain according to the capacity verification task fingerprint, and generate a remote capacity verification traceability report for the battery.

[0114] It should be noted that the fingerprint of the verification task in the task execution verification result is used as the index to determine the verification process traceability chain with the same verification task fingerprint; when the task execution verification result and the verification process traceability chain have the same verification task fingerprint, it is determined that the two correspond to the same remote verification task.

[0115] If no traceability chain with the same capacity task fingerprint is found, or if multiple traceability chains correspond to the same capacity task fingerprint, or if the traceability node that needs to be associated with the task execution verification result is missing, a report index binding anomaly record will be generated. The report index binding anomaly record includes the capacity task fingerprint, anomaly type, missing traceability chain content, missing traceability node content, and duplicate traceability chain marker. After the report index binding anomaly record is generated, the corresponding task will be marked as incompletely traceable in the battery remote capacity traceability report.

[0116] Establish a correlation between each verification item in the task execution verification result and the corresponding content in the capacity verification process traceability chain; specifically, the verification result of the actual capacity verification object is associated with the capacity verification object in the capacity verification process traceability chain; the verification result of the actual discharge execution status is associated with the capacity discharge stage, the change of discharge execution status and the corresponding stage summary; the verification result of the remote operation mode status is associated with the traceability node that records the remote operation mode status; the verification result of the start access status is associated with the traceability node and stage summary before the discharge start; the verification result of the alarm protection response status is associated with the traceability node corresponding to the alarm event, the change of discharge execution status and the status judgment result corresponding to the abnormal status; and the verification result of sampling continuity is associated with the sampling continuity status and the sampling discontinuity record.

[0117] When there are verification failures in the task execution verification results, the reason for the verification failure, the corresponding sampling time, the corresponding capacity stage, and the corresponding traceability node are written into the index binding relationship. When there are missing baselines, duplicate record markings, intermittent sampling records, missing alarm response content, or response timeout content, the corresponding status is written into the index binding relationship along with the capacity task fingerprint, and also written into the abnormal location content of the battery remote capacity traceability report. If the corresponding traceability node is missing, the location is determined according to the corresponding sampling time to the relevant stage summary. If the corresponding stage summary is missing, a replacement location record is formed according to the corresponding sampling time and capacity stage, and the missing traceability node is marked in the abnormal location content.

[0118] After index binding is completed, a remote battery capacity verification report is generated. The report includes task identification, start-up baseline, process traceability, execution verification, and anomaly location information. Task identification includes the capacity verification task fingerprint, the verification object, the capacity verification device identifier, and the task reception time. Start-up baseline includes capacity discharge constraints, remote operation mode status, battery pack float charging status, discharge parameter confirmation results, and operation verification results. Process traceability includes traceability nodes, stage summaries, and actual execution records. Execution verification includes the pass status and reasons for failure for each verification item. Anomaly location includes verification failure items, alarm events, sampling interruption records, and the corresponding sampling time, capacity verification stage, and traceability node.

[0119] This embodiment also provides a data traceability system for remote capacity verification of storage batteries, including: a start fingerprint module, a segmented traceability module, a traceability chain module, and a verification report module; The fingerprint module is used to receive capacity request data, extract capacity initiation elements, perform field integrity verification and initiation access verification on the capacity initiation elements. When the verification is successful, the capacity initiation elements are solidified into capacity initiation baseline records according to a preset fixed field order. The capacity initiation baseline records are then processed by field concatenation and summary to generate capacity task fingerprints. When the verification fails, an initiation verification failure record is generated, and the generation and discharge of capacity task fingerprints are blocked. The segmented traceability module is used to collect the corresponding battery pack's capacity operation data after the capacity task fingerprint enters the capacity device with the remote capacity task. Based on the group voltage data, group current data and individual battery status data in the capacity operation data, the capacity status judgment result is generated. The capacity operation data and capacity status judgment result are associated with the capacity task fingerprint according to the sampling time sequence, capacity stage and capacity task fingerprint to generate segmented traceability data. The traceability chain module is used to arrange segmented traceability data according to the sampling time sequence, forming mandatory traceability nodes at task reception, start verification completion, discharge start, discharge stop, and task end. It also forms traceability nodes when the capacity stage changes, the capacity status judgment result changes, the discharge execution status changes, alarm events occur, and sampling interruptions occur. Adjacent traceability nodes are associated through stage summaries to form a capacity process traceability chain, and actual execution records are collected from the capacity process traceability chain. The verification report module is used to verify the consistency between the actual execution record and the capacity launch baseline record corresponding to the capacity task fingerprint, obtain the task execution verification result, and index and bind the task execution verification result with the capacity process traceability chain to generate a remote capacity traceability report for the battery.

[0120] Reference Figure 2 , Figure 2 The module relationships of the data traceability system for remote battery capacity approval are shown. The startup fingerprint module generates the capacity approval start-up baseline record and the capacity approval task fingerprint. The segmented traceability module associates the capacity approval operation data, capacity approval status judgment results and capacity approval task fingerprint to form segmented traceability data. The traceability chain module forms the capacity approval process traceability chain based on traceability nodes and stage summaries. The verification report module verifies the consistency between the actual execution record and the capacity approval start-up baseline record and generates a remote battery capacity approval traceability report.

[0121] In summary, this invention improves the completeness, reliability, and credibility of remote capacity verification by: solidifying the remote capacity verification initiation information into a capacity verification initiation baseline record and generating a capacity verification task fingerprint that runs through the entire process of task issuance, execution, and report generation, ensuring a stable correspondence between the initiation basis of each capacity verification task and the actual execution result, thus avoiding unclear task attribution and data mixing; extracting key changes during execution to form traceability nodes, and connecting them with stage summaries to form a capacity verification process traceability chain, and then binding the verification results to the corresponding traceability position, enabling abnormal processes and execution deviations to be continuously restored, quickly located, and verified.

[0122] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A data traceability method for remote capacity verification of storage batteries, characterized in that: include: Receive capacity request data, extract capacity initiation elements, perform field integrity verification and initiation access verification on capacity initiation elements. If the verification passes, solidify the capacity initiation elements into capacity initiation baseline records according to preset fixed field order, and perform field splicing and summary processing on capacity initiation baseline records to generate capacity task fingerprints. If the verification fails, form an initiation verification failure record, and block the generation and discharge of capacity task fingerprints. After the capacity assessment task fingerprint enters the capacity assessment device along with the remote capacity assessment task, it collects the capacity assessment operation data of the corresponding battery pack, and generates the capacity assessment status judgment result based on the group voltage data, group current data and individual battery status data in the capacity assessment operation data. The capacity assessment operation data and capacity assessment status judgment result are associated with the capacity assessment task fingerprint according to the sampling time sequence, capacity assessment stage and capacity assessment task fingerprint to generate segmented traceability data. The segmented traceability data is arranged according to the sampling time sequence. Forced traceability nodes are formed at task reception, start verification completion, discharge start, discharge stop and task end. Traceability nodes are also formed when the capacity stage changes, the capacity status judgment result changes, the discharge execution status changes, alarm events occur and sampling interruptions occur. Adjacent traceability nodes are associated through stage summaries to form a capacity process traceability chain. Actual execution records are collected from the capacity process traceability chain. The consistency of the actual execution record and the corresponding capacity launch baseline record of the capacity task fingerprint are verified to obtain the task execution verification result. The task execution verification result is then indexed and bound to the capacity process traceability chain to generate a remote capacity traceability report for the battery.

2. The data traceability method for remote capacity verification of storage batteries as described in claim 1, characterized in that, The elements for starting up the nuclear capacity include the nuclear capacity object, the nuclear capacity device identifier, the nuclear capacity discharge constraint, the remote operation mode status, the battery pack float charge status, the discharge parameter confirmation result, and the operation verification result. The nuclear discharge constraints include discharge current, discharge duration, termination voltage, and termination conditions.

3. The data traceability method for remote capacity verification of storage batteries as described in claim 2, characterized in that, The specific steps for generating the kernel capacity task fingerprint are as follows: Arrange the capacity start-up elements according to a preset fixed field order to form ordered start-up element data; Summarize the sequential start-up element data to obtain a start-up content summary value that does not include the generation time of the baseline record; The sequential start-up element data, start-up content summary values ​​and baseline record generation time are linked to form the capacity start-up baseline record; The preset fixed field order is as follows: capacity object, capacity device identifier, capacity discharge constraint, remote operation mode status, battery pack float charge status, discharge parameter confirmation result, and operation verification result. Field splicing units are generated for the fields in the capacity approval start-up baseline record. Each field splicing unit includes a field name, field type identifier, length value, and field value. The field splicing units are connected in a fixed field order to form the start-up baseline splicing data. The start-up baseline splicing data is then processed to generate the capacity approval task fingerprint.

4. The data traceability method for remote capacity verification of storage batteries as described in claim 1, characterized in that, The specific steps for generating the nuclear capacity status determination result are as follows: The state determination parameters required for battery pack state determination are determined based on the pre-stored core capacity configuration data. The state determination parameters are used to characterize the voltage conditions, current conditions and time conditions in the battery pack state determination. During the execution of the remote nuclear capacity task, the current sampling time is first determined based on the nuclear capacity operation data to determine whether it belongs to a state situation that needs to be determined first. The state situation that needs to be determined first includes at least one of the abnormal state, nuclear capacity state and power outage discharge state. If the current sampling time belongs to a state situation that needs to be determined first, the battery pack state corresponding to the current sampling time is determined from the abnormal state, the state of ... If the current sampling time does not belong to the state situation that needs to be determined first, the battery pack state is determined according to the correspondence between the group voltage data, group current data and state judgment parameters, and the determined battery pack state is used as the core capacity state judgment result.

5. The data traceability method for remote capacity verification of storage batteries as described in claim 4, characterized in that, The specific steps for generating segmented traceability data are as follows: Establish a correspondence between the nuclear capacity task fingerprint and the nuclear capacity operation data, nuclear capacity status judgment result, sampling time and nuclear capacity stage. The nuclear capacity stage includes the task reception stage, the start verification stage, the nuclear capacity discharge stage, the nuclear capacity stop stage and the nuclear capacity end stage. Using the core capacity stage as the basis for segmentation, data with the same core capacity stage and continuous sampling time sequence are grouped into the same stage data segment; Arrange the data segments of each stage under the same core capacity task fingerprint according to the stage start sampling time to generate segmented traceability data.

6. The data traceability method for remote capacity verification of storage batteries as described in claim 1, characterized in that, The specific steps for forming a traceability node are as follows: Compare the data corresponding to adjacent sampling times. When at least one of the following changes, the sampling time is taken as the traceability trigger position and a traceability node is formed at the traceability trigger position. Each traceability node records the fingerprint of the capacity control task, the node sampling time, the type of triggering event, the state before triggering, and the state after triggering. The state before triggering and the state after triggering include the capacity control stage, the capacity control status determination result, the discharge execution status, the alarm event status, and the sampling continuity status.

7. The data traceability method for remote capacity verification of storage batteries as described in claim 1, characterized in that, The specific steps for forming the nuclear capacity traceability chain are as follows: The traceability nodes and stage summaries under the same core capacity task fingerprint are connected continuously according to the sampling time sequence, so that the traceability nodes can locate the start and end positions of the data segments corresponding to the stage summaries, thus forming a core capacity process traceability chain; When there is no traceability node, a missing stage summary, a missing forced traceability node, or a traceability node and a stage summary cannot be continuously connected according to the sampling time sequence under the same core capacity task fingerprint, an abnormal record is generated by forming a traceability chain. The stage summary refers to the data summary between adjacent traceability nodes, which is used to record the stage start and end time, group voltage changes, group current changes, individual battery status changes, alarm events, and sampling interruptions between adjacent traceability nodes.

8. The data traceability method for remote capacity verification of storage batteries as described in claim 7, characterized in that, The specific steps to obtain the task execution verification result are as follows: The actual execution records and the capacity initiation baseline records are combined according to the corresponding capacity task fingerprints to form the data to be verified; Based on the data to be verified, the consistency of the actual verification object, discharge execution process, remote operation status and start access status of this remote verification with the verification start benchmark record is verified. The alarm protection response and sampling continuity are verified with the corresponding traceability nodes and stage summaries in the verification process traceability chain to obtain the task execution verification results. The actual execution record refers to the record of this remote approval process obtained from the approval process traceability chain.

9. The data traceability method for remote capacity verification of storage batteries as described in claim 8, characterized in that, The specific steps for generating the remote capacity traceability report for the storage battery are as follows: Establish a correlation between each verification item in the task execution verification result and the corresponding content in the capacity traceability chain; When no traceability chain for the same capacity task fingerprint is found, the corresponding traceability node is missing, or multiple traceability chains for the same capacity task fingerprint are found, an abnormal record is generated by binding the report index and marked as incomplete traceability in the remote capacity traceability report for the battery. When there are verification failures in the task execution verification results, the reason for the verification failure, the corresponding sampling time, the corresponding verification stage, and the corresponding traceability node are written into the index binding relationship; After completing the index binding, a remote battery capacity traceability report is generated.

10. A data traceability system for remote capacity assessment of storage batteries, based on the data traceability method for remote capacity assessment of storage batteries according to any one of claims 1 to 9, characterized in that, include: Start the fingerprint module, segmented traceability module, traceability chain module, and verification report module; The fingerprint module is used to receive capacity request data, extract capacity initiation elements, perform field integrity verification and initiation access verification on the capacity initiation elements. When the verification is successful, the capacity initiation elements are solidified into capacity initiation baseline records according to a preset fixed field order. The capacity initiation baseline records are then processed by field concatenation and summary to generate capacity task fingerprints. When the verification fails, an initiation verification failure record is generated, and the generation and discharge of capacity task fingerprints are blocked. The segmented traceability module is used to collect the corresponding battery pack's capacity operation data after the capacity task fingerprint enters the capacity device with the remote capacity task. Based on the group voltage data, group current data and individual battery status data in the capacity operation data, the capacity status judgment result is generated. The capacity operation data and capacity status judgment result are associated with the capacity task fingerprint according to the sampling time sequence, capacity stage and capacity task fingerprint to generate segmented traceability data. The traceability chain module is used to arrange segmented traceability data according to the sampling time sequence, forming mandatory traceability nodes at task reception, start verification completion, discharge start, discharge stop, and task end. It also forms traceability nodes when the capacity stage changes, the capacity status judgment result changes, the discharge execution status changes, alarm events occur, and sampling interruptions occur. Adjacent traceability nodes are associated through stage summaries to form a capacity process traceability chain, and actual execution records are collected from the capacity process traceability chain. The verification report module is used to verify the consistency between the actual execution record and the capacity launch baseline record corresponding to the capacity task fingerprint, obtain the task execution verification result, and index and bind the task execution verification result with the capacity process traceability chain to generate a remote capacity traceability report for the battery.

Images