A charging station device monitoring method and system
Patent Information
- Application Number
- CN202211490105.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-25
- Publication Date
- 2026-08-18
- Estimated Expiration
- 2042-11-25
AI Technical Summary
[0003]现有的充电站设备监测方法,着重于充电桩故障的识别与预警等,并未对BMS(电池管理系统)运行记录及故障记录作进一步分析,会导致充电桩故障与电动汽车BMS故障不一致
[0028]本发明提供了一种充电站设备监测方法,其将充电桩BMS报文构建为B-tree结构数据,并与充电桩故障数据进行比对后,进行故障判断,保障了充电桩故障与BMS故障的一致性。
Smart Images

Figure CN116260242B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of charging station technology, and in particular relates to a method and system for monitoring charging station equipment. Background Technology
[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.
[0003] Existing charging station equipment monitoring methods focus on the identification and early warning of charging pile faults, but do not further analyze the operation records and fault records of BMS (Battery Management System), which can lead to inconsistencies between charging pile faults and electric vehicle BMS faults. Summary of the Invention
[0004] To address the technical problems mentioned above, this invention provides a charging station equipment monitoring method and system. The method constructs charging pile BMS messages into B-tree structured data and compares them with charging pile fault data to determine the fault, thus ensuring the consistency between charging pile faults and BMS faults.
[0005] To achieve the above objectives, the present invention adopts the following technical solution:
[0006] The first aspect of the present invention provides a method for monitoring charging station equipment, comprising:
[0007] Obtain the charging pile BMS message file stream;
[0008] After parsing the charging pile BMS message file stream, a B-tree structure data of the BMS message is established;
[0009] For each charging pile fault data in the charging pile fault set, based on the fault time, the leaf node is searched in the B-tree structure data of the BMS message, and the charging pile fault is determined based on the numerical item of the leaf node.
[0010] In the B-tree structure of the BMS message, the root node is a charging station. The end time of each charging record is taken as the key of the root node, and a pointer is used to point to the second-level child node. In the second-level child node, the charging record of the charging station is used as the node content, and the upload time of each BMS message is taken as the key of the second-level child node, and a pointer is used to point to the leaf node. In the leaf node, the upload time of the BMS message is used as the key, and the key name and key value in the BMS message are used as numeric items.
[0011] Furthermore, it also includes: for a certain charging pile fault data, finding the B-tree structure data of the BMS message corresponding to the charging pile fault data based on the device ID information.
[0012] Furthermore, before parsing the charging pile BMS message file stream, a CRC16 check is used to verify whether the data in the received charging pile BMS message file stream is correct.
[0013] Furthermore, before parsing the charging pile BMS message file stream, the charging pile BMS message file stream is deduplicated, and data frames with the same value in adjacent time periods are deleted, retaining only the first and last frames with the same value.
[0014] Furthermore, each charging pile fault data includes the device ID, fault time, fault type, and fault description.
[0015] Furthermore, after completing the fault diagnosis of the charging pile, the nodes in the B-tree structure data of the BMS message are deleted. The specific steps are as follows: find the second-level node where a certain keyword is located; delete the keyword at the second-level node level, and delete the leaf node pointed to by the pointer corresponding to the keyword.
[0016] Furthermore, the specific steps for finding the leaf node are as follows:
[0017] Determine if the fault time is within the key range of the root node. If so, continue searching along the second-level node pointed to by the pointer corresponding to the key; otherwise, the BMS daily operation report does not exist.
[0018] Determine if the fault time is within the key range of the secondary node. If so, continue searching along the leaf node pointed to by the pointer corresponding to the key; otherwise, the BMS daily operation report does not exist.
[0019] Determine if the fault time is within the keyword range of the leaf node. If so, read the numeric item of the leaf node; otherwise, the BMS daily operation report does not exist.
[0020] A second aspect of the present invention provides a charging station equipment monitoring system, comprising:
[0021] The message acquisition module is configured to acquire the message file stream of the charging pile BMS.
[0022] The tree building module is configured to: parse the charging pile BMS message file stream and then build the B-tree structure data of the BMS message;
[0023] The fault diagnosis module is configured to: for each charging pile fault data in the charging pile fault set, search for the leaf node in the B-tree structure data of the BMS message according to the fault time, and determine the charging pile fault based on the numerical item of the leaf node;
[0024] In the B-tree structure of the BMS message, the root node is a charging station. The end time of each charging record is taken as the key of the root node, and a pointer is used to point to the second-level child node. In the second-level child node, the charging record of the charging station is used as the node content, and the upload time of each BMS message is taken as the key of the second-level child node, and a pointer is used to point to the leaf node. In the leaf node, the upload time of the BMS message is used as the key, and the key name and key value in the BMS message are used as numeric items.
[0025] A third aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a charging station equipment monitoring method as described above.
[0026] A fourth aspect of the present invention provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of a charging station equipment monitoring method as described above.
[0027] Compared with the prior art, the beneficial effects of the present invention are:
[0028] This invention provides a method for monitoring charging station equipment, which constructs charging pile BMS messages into B-tree structured data, compares them with charging pile fault data, and then performs fault judgment, ensuring the consistency between charging pile faults and BMS faults.
[0029] This invention provides a method for monitoring charging station equipment. By analyzing the operation logs of the charging pile equipment, it verifies whether the charging equipment communicates normally with the BMS during operation, whether faults are recorded correctly, whether the fault alarm information is consistent with the BMS operation logs, and whether the output data during operation meets the standards, thus realizing technical supervision of the charging pile. Attached Figure Description
[0030] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.
[0031] Figure 1 This is a diagram showing the connection relationship between the cloud, edge computing devices, sensors, and terminal devices in Embodiment 1 of the present invention.
[0032] Figure 2 This is a flowchart of a charging station equipment monitoring method according to Embodiment 1 of the present invention;
[0033] Figure 3 This is a schematic diagram of the B-tree structure data in Embodiment 1 of the present invention;
[0034] Figure 4 This is a flowchart of the technical supervision and inspection process according to Embodiment 1 of the present invention;
[0035] Figure 5 This is a structural diagram of the cloud in Embodiment 1 of the present invention. Detailed Implementation
[0036] The present invention will be further described below with reference to the accompanying drawings and embodiments.
[0037] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.
[0038] Example 1
[0039] This embodiment provides a method for monitoring charging station equipment, applied in the cloud, which includes a cloud control center and a cloud data center, such as... Figure 1 As shown, the cloud control center is connected to the cloud data center, which in turn is connected to several edge devices. Each edge device is connected to various sensors and terminal devices within the station via wired or wireless communication.
[0040] This embodiment provides a method for monitoring charging station equipment, such as... Figure 2 As shown, the specific steps include the following:
[0041] Step 1: The data sensing layer collects the operating data of the charging station equipment.
[0042] Sensors and terminal devices constitute the data sensing layer. These sensors and terminal devices collect operational data from the charging station equipment on-site. The collected operational data mainly includes telemetry, remote signaling, and remote control data, which is sent to the edge device using a fixed-format and fixed-length hexadecimal encoding, such as "9812f456 7 401D6E0F0000FD", where 401D represents the equipment's output voltage value, 6E0F represents the equipment's output current value, and so on.
[0043] Step 2: The side-mounted equipment collects the charging station equipment operation data, preprocesses it, and uploads it to the cloud.
[0044] The edge-mounted device connects to various sensors and terminal devices within the station via wired or wireless communication, supports multiple interface methods and protocol types, and converts data into a unified protocol type.
[0045] The edge device adds a key, the received time as the message time, the sending device number, and the message type to the charging station equipment operation data (containing only values), forming a "key-value-time-type" format. This data is then temporarily stored and compressed before being packaged and uploaded to the cloud. Communication with the cloud is via wired or wireless means, using the MQTT protocol for data transmission.
[0046] The edge device mainly completes data reception, data storage, protocol conversion, message data formatting, initial message data cleaning, message data item supplementation, data compression, data encryption, data packaging and sending to the cloud.
[0047] Step 3: Cloud storage and data analysis for equipment technical supervision. Specifically, after parsing the charging pile BMS message file stream, a B-tree structure data of the BMS message is established; for each charging pile fault data in the charging pile fault set, the leaf node is found in the B-tree structure data of the BMS message according to the fault time, and the charging pile fault is determined according to the numerical item of the leaf node.
[0048] like Figure 5 As shown, the cloud is used to store data, clean data, and conduct technical supervision of the operation of charging equipment.
[0049] The charging pile BMS messages received in the cloud exist in the form of line records in a file stream.
[0050] Data cleaning includes: deduplicating the charging pile BMS message file stream, deleting data frames with the same value in adjacent time periods, and keeping only the first and last frames with the same value.
[0051] Message parsing is performed: CRC16 checksum is used to verify the correctness of the received charging pile BMS message file stream data. Message key-value parsing is performed: The received charging pile BMS message file stream is segmented based on punctuation marks and parsed line by line into the format of "key-value-time-type-device".
[0052] This process captures the latest complete charging message set from the start to the end of charging. A charging message (charging process message) contains multiple data frames. A complete charging process message includes a start frame, an end frame, and N lines of content frames. It should be noted that the first and end frames have different keywords; the key name is the variable name, and the key value is the variable value, for example, current: 5. The first message in a charging record is generally a BHM message (BMS handshake message) or the old international BRM message (BMS and vehicle identification message); the end message is generally a BST message (BMS stop charging message).
[0053] The message file stream is read line by line, each line is parsed, and the search for start and end message frame markers begins. If a start frame is encountered first, the next nearest start frame is found, and the end frame between the two start frames is also found. The message between this end frame and the second start frame is then recorded as a charging process message. If an end frame is encountered first, the next nearest start frame is found, and the message between this start frame and the end frame is captured as a charging process message. The start frame ID is read to determine if it has been analyzed. If it has, the segment is discarded, and the search for a start frame begins again. If there is no end frame between two consecutive start frames, the message is captured from the second start frame to the end of the first start frame, and this is marked as an abnormal end to the charging record.
[0054] Technical supervision of charging start-up: Technical supervision of the charging process is carried out based on the BMS charging protocol library.
[0055] The main algorithms in step 3 include:
[0056] Step 301: Establish a set of technical supervision items for the charging process. ,like:
[0057]
[0058] Where, x n This represents the nth data supervision item, where n = 1, 2, ..., k, and k represents the total number of data supervision items. The message types include: Charger Handshake Message (CHM), BMS Handshake Message (BHM), Charger Identification Message (CRM), BMS Identification Message (BRM), Power Battery Charging Parameter Message (BCP), and Charger Maximum Output Capacity Message (CML).
[0059] BMS charging ready message (BRO), charger output ready message (CRO), battery charging status message (BCS), charger charging status message (CCS), single battery voltage message (BMV), battery temperature message (BMT), battery reserve message (BSP), BMS charging stop message (BST), and charger charging stop message (CST).
[0060] Step 302: Create a set of charging station faults , of which each A charging station malfunction. .
[0061] Step 303: Parse the charging pile BMS message file stream into plaintext format, encode the characters using UTF-8, parse the data, segment it based on punctuation marks, form a key-value table, and establish the B-tree structure data of the BMS message.
[0062] Message segmentation and parsing process: Read a line of message and check if a key identifier, such as "@PT:", exists. If not, discard the line and proceed to the next line. If it exists, extract n characters from that position to form the line string S (different technical supervision item groups correspond to different lengths of n). Search for the key identifier "{" in line string S. If it exists, it indicates that the line is parsed data and requires further analysis; otherwise, discard the line and proceed to the next line. Continue searching for key identifiers in S, such as "complete packet". If it exists, it means S is a complete packet, and the message needs to be segmented according to a predefined position, i.e., obtain the key name S1 and its key value. If it does not exist, it means S is fragmented data, and the message S1 and V1 are segmented according to the fragmentation position.
[0063] The following examples represent S for complete packages and sub-packages, respectively:
[0064] Package No.: 2 Complete Package: B20E930B9001421900FFFFFFFFFF BCS: {"SPN3075":"Charging voltage measurement = 376.2V",……};
[0065] The key name S1 after parsing the complete package in the example is BCS, and the key value is in JSON format: {"SPN3075":"Charging voltage measurement value=376.2V",……};
[0066] Then read the values of each key in S1 in sequence and fill them into the B-tree.
[0067] Among them, such as Figure 3 As shown, the root node of the B-tree structure is a specific charging pile, including various file data. The end time of each charging service (charging record) is used as the key of the root node, pointing to second-level child nodes via pointers. Within each second-level child node, the content consists of a single charging process record for that charging pile (containing multiple BMS messages), including various data from the charging record. The upload time of each BMS message is used as the key of the second-level child node, pointing to leaf nodes via pointers. In each leaf node, the upload time of the BMS message is used as the key, and the key name and value from the BMS message are used as numeric items. A B-tree structure is established for each charging pile device to accelerate search and analysis. By associating the end time with the upload time, the child nodes and leaf nodes of this tree are linked in order of their time series values.
[0068] The B-tree structure data established in this embodiment is a multi-way balanced tree, which is ultimately built into an m (m>2) order B-tree structure data, where:
[0069] 1) Each node in the tree has at most m subtrees, that is, it contains at most m-1 keys;
[0070] 2) If the root node is not a terminal node, then there are at least two subtrees;
[0071] 3) All non-leaf nodes except the root node have at least [m / 2] subtrees, that is, at least [m / 2-1] keys;
[0072] 4) The structure of all non-leaf nodes is shown in Table 1.
[0073] Table 1. Structure of non-leaf nodes
[0074]
[0075] Among them, D i (i=1,2,…,n) represents the key value of the i-th non-leaf node, which is the primary key recorded in Table 1, and satisfies D1 <D2<…<D n Use time type; P i (i=0,1,…,n) is a pointer from the i-th non-leaf node to the root node of the subtree, storing the address information of the child nodes of the i-th non-leaf node; Data i (i=0,1,…,n) represents the data of the i-th non-leaf node, i.e., the data in Table 1 excluding the primary key; pointer P i-1 The key of all nodes in the pointed-to subtree is less than D. i P i The keys of all nodes in the pointed-to subtree are greater than D. i .
[0076] BMS message B-tree data insertion and update methods:
[0077] (1) Parse the charging process message data of the charging pile to obtain the charging pile file, charging end time, charging fault data, etc. Match the corresponding BMS message B-tree according to the device ID and other data in the charging pile file, and insert the charging end time as the key into the root node. If there is no corresponding BMS message B-tree, create a new BMS message B-tree, insert the charging pile file as data into the root node, and insert the charging end time as the new key into the root node.
[0078] (2) Parse the BMS message to obtain the upload time t and the BMS key names and values. Use the upload time t as the key to find a suitable insertion node. First, search in the root node key and compare in order. The specific process is as follows:
[0079] 1) If the root node key D i ≥t>D i-1 If D1≥t, then follow the pointer P iContinue to search for the specified secondary child node, where D i represents the i-th keyword in the root node, and P i represents the pointer corresponding to the i-th keyword in the root node; if the keyword D2 of the secondary node j =t, then add data to the leaf node pointed to by the pointer P2 j , and the data content is each BMS key name and key value; if the last keyword D2 of the secondary node m <t, then create a new secondary node, set the keyword content of the new node to t, create a new leaf node, and create a new pointer pointing to the new leaf node, where D2 j represents the j-th keyword in the secondary node, and P2 j represents the pointer corresponding to the j-th keyword in the secondary node; set the keyword content of the new leaf node to t, and the data content is each BMS key name and key value.
[0080] 2) If the last keyword of the root node <t, then add a keyword with the content t to the root node, create a new secondary node, and create a new pointer pointing to the new secondary node. Set the keyword content of the new node to t, create a new leaf node, and create a new pointer pointing to the new leaf node. Set the keyword content of the new leaf node to t, and the data content is each BMS key name and key value.
[0081] After the technical analysis, the corresponding data in the BMS message B-tree can be deleted. The method is as follows:
[0082] 1) Search for the secondary node where the keyword t is located;
[0083] 2) Delete the keyword t at the secondary node layer and delete the leaf node pointed to by the pointer.
[0084] Step 304. According to each charging pile fault data in the charging pile fault set , conduct technical supervision and inspection on the BMS message.
[0085] Read one item , and find the corresponding charging pile BMS message B-tree according to the equipment file and equipment ID information therein.
[0086] According to the fault time T n in it, search for the corresponding child node.
[0087] 1) If the root node keyword D i ≥T n >D i-1 , or D1≥T n , then follow the pointer P iThe search continues for the specified second-level child node; otherwise, the technical supervision result is returned as "BMS operation daily report does not exist". If the second-level node key is D2... j ≥T n >D j-1 , or D21≥T n Then along pointer P2 j The search continues on the specified leaf node; otherwise, the technical supervision result is returned as "BMS operation daily report does not exist"; if the last key of the secondary node is D2 m <T n If the technical supervision result is not found, the result will be "BMS daily operation report does not exist".
[0088] 2) Leaf node keyword D3 q ≥T n >D q-1 , or D31≥T n Then read the data (numeric item) of that leaf node; the last key of the leaf node is D3. m <T n If so, the technical supervision result returned will be "BMS daily operation report does not exist". Among them, D3 q This represents the q-th key in the leaf node.
[0089] 3) According to The fault types in the data are matched with the set of technical supervision items for the charging process. The technical supervision item in the B-tree. Technical supervision methods include: probabilistic features of matching key values, interval features, joint features, etc. All values are stored in the B-tree; the premise of technical supervision is to find the values in the B-tree before making a judgment.
[0090] ① Analysis of charging handshake BHM fault.
[0091] Fault location 1: Determine if the value of SPN2601 is greater than the charger's minimum voltage V1, such as 400V.
[0092] In all the data key names and key values read from the leaf nodes, find the corresponding key value for the key name "SPN2601", determine whether the value is greater than the charger's minimum voltage V1, and if it is greater than V1, record the device ID, SPN2601 value, and SPN2601 value time, etc., and output the data to the corresponding technical supervision document through the file stream.
[0093] Fault location 2: BHM message timeout, determine whether BMS sent BHM.
[0094] In all leaf nodes read, search for the corresponding key value for the key name "SPN2601". If it does not exist, output "Device ID" + "Failure Time" + "BMS Description (BMS did not send BHM)" to the corresponding technical supervision document via file stream.
[0095] ② Charging handshake CRM failure.
[0096] Fault Location 1: CRM Message Timeout - Determine if BMS sends CRM message.
[0097] In all the secondary nodes read, search for the key name "CRM" in all leaf nodes whose critical time is within the fault period. If it does not exist, output "Device ID" + "Fault Time" + "BMS Description (BMS did not send CRM)" to the corresponding technical supervision document via file stream.
[0098] Fault location 2: Determine if the BMS can identify it.
[0099] In all leaf nodes read, search for the key value of SPN2560 and determine whether the value contains a reserved identification code, such as "AA". If it does not exist, output "Device ID" + "Failure Time" + "BMS Description (BMS cannot recognize)" to the corresponding technical supervision document via file stream.
[0100] ③ If the charging configuration BCP is faulty, check if the value exceeds the limit, such as if the highest allowable value exceeds the maximum allowable value.
[0101] In all leaf nodes read, read the value of key name "SPN3073" and determine whether it is greater than the predefined maximum value, exceeds the range, or is greater than or less than the value of other key leaf nodes. If it is greater than / exceeds / greater than or less than, output "Device ID" + "Failure Time" + "BMS Description (Out of Limit)" to the corresponding technical supervision document through the file stream.
[0102] Fault location BCP: BCP current range over-limit judgment, read whether the value of key name "SPN3073" in the leaf node is greater than the value of key name "SPN2817" in the leaf node under the same secondary node. If it is greater, output "Device ID" + "Fault Time" + "BMS Description (Over-limit)" to the corresponding technical supervision document through file stream.
[0103] Fault location BCP: If the maximum allowable voltage of BCP is lower than the minimum output of the charger, check whether the value of key name "SPN2819" in the leaf node is less than the value of key name "SPN2825" in the leaf node under the same secondary node. If it is less, output "Device ID" + "Fault Time" + "BMS Description (Exceeding Limit)" to the corresponding technical supervision document through file stream.
[0104] ④ If the charging configuration BRO is faulty, check if there is a value containing the identification code, such as "00", in the leaf node following leaf node "SPN2829".
[0105] Read the time from leaf node “SPN2829”, read the subsequent leaf nodes to the end leaf node in time sequence, and determine whether the leaf node key value contains “00”. If so, output “Device ID” + “Fault Time” + “BMS Description (Charging Configuration BRO Fault)” to the corresponding technical supervision document through file stream.
[0106] Step 304, as follows Figure 4 As shown, the specific steps include: checking whether a fault message was uploaded when a fault occurred; searching for the key name in the charging message set to determine whether the corresponding "key-value" was uploaded, i.e., whether the fault value was uploaded; if not, recording the start frame time and marking it as an unqualified item; checking whether the value appearing in the message when a fault occurred matches the fault, including whether it is a fixed value and whether it is within the specified range; searching for the key name in the charging message set to determine whether the corresponding "key-value" was uploaded and whether the value is consistent with the specified value; checking whether the corresponding message was uploaded in the BMS messages within the first N seconds when a charging pile fault occurred; checking whether a message was uploaded + whether there was a response + time limit when a charging pile fault occurred; checking whether subsequent values were within the specified range when a charging pile fault occurred; checking whether the next process was normal after a charging pile fault occurred; and checking whether the change range of the equipment operating values was within the specified range.
[0107] Taking the monitoring of charging pile output power control technology as an example:
[0108] (1) Maximum rated deviation of output voltage A: 1% of the required output voltage.
[0109] (2) Output voltage control response rated time B: The response time shall not exceed 5s.
[0110] (2) Output voltage ripple adjustment: less than or equal to 0.5% of the required output voltage.
[0111] (4) Rated output voltage required for charging equipment: .
[0112] Telemetry Definition Table: Device Name - Rated Charging Voltage - Telemetry Value. The charging device selects the minimum value from the maximum supply voltage of the charging device, the rated input voltage of the BMS, and the rated capacity of the cable as the rated output voltage value, and uploads it to the cloud.
[0113] (5) Real-time output voltage of the charging equipment:
[0114] Telemetry definition table: Device name - Real-time voltage - Telemetry value. The charging device uses the real-time voltage during the charging process as the output voltage value and uploads it to the cloud.
[0115] (6) Rated voltage of charging equipment: .
[0116] Telemetry definition table: Device name - Device rated voltage - Telemetry value. Obtained from the maximum supply voltage of the charging device.
[0117] (7) Locate the measurement point status of “Device Name-Device Status-Remote Signaling Value” and determine whether calculation is required. A true status indicates that the device is charging and can be calculated.
[0118] Permissible range of steady-state voltage values:
[0119] Voltage deviation:
[0120] Maximum voltage:
[0121] Minimum voltage:
[0122] Output voltage fluctuation adjustment: ,in, Voltage indicating the end time, Voltage indicating the start time;
[0123] Controlling response time: ,in, This indicates the moment when the instruction execution is complete and the voltage changes. Indicates the time when the instruction was issued;
[0124] when ,and The predefined standard command response time is 5 seconds, which is acceptable; otherwise, it exceeds the limit and is recorded. ;
[0125] Output voltage fluctuation adjustment:
[0126] Choose any start time node in the message log that is not under technical supervision. During the time period, by From this moment on, remember The first time point Overshoot for ~ The maximum value of |actual voltage - V2| within the time period; when ,Record ; and record The start and end times.
[0127] Maximum deviation: when When, the maximum deviation of this adjustment is not calculated; when At that time, by From time point onwards, the maximum deviation for ~ The maximum value of |actual voltage - set value| within the time period.
[0128] when ,Record ; and record The start and end times.
[0129] Output , If the start and end times are equivalent to the corresponding technical supervision documents, it indicates that the output voltage fluctuation of the charging pile is abnormal.
[0130] After completing all the analysis items of the message log, the output technical supervision documents will be compiled to provide technical support for equipment inspection and maintenance.
[0131] This embodiment of a charging station equipment monitoring method analyzes the operation logs of the charging pile equipment to verify whether the charging equipment communicates normally with the BMS during operation, whether faults are recorded correctly, whether the fault alarm information is consistent with the BMS operation logs, and whether the output data during operation meets the standards, thereby achieving technical supervision of the charging pile.
[0132] Example 2
[0133] This embodiment provides a charging station equipment monitoring system, which specifically includes:
[0134] The message acquisition module is configured to acquire the message file stream of the charging pile BMS.
[0135] The tree building module is configured to: parse the charging pile BMS message file stream and then build the B-tree structure data of the BMS message;
[0136] The fault diagnosis module is configured to: for each charging pile fault data in the charging pile fault set, search for the leaf node in the B-tree structure data of the BMS message according to the fault time, and determine the charging pile fault based on the numerical item of the leaf node;
[0137] In the B-tree structure of the BMS message, the root node is a charging station. The end time of each charging record is taken as the key of the root node, and a pointer is used to point to the second-level child node. In the second-level child node, the charging record of the charging station is used as the node content, and the upload time of each BMS message is taken as the key of the second-level child node, and a pointer is used to point to the leaf node. In the leaf node, the upload time of the BMS message is used as the key, and the key name and key value in the BMS message are used as numeric items.
[0138] It should be noted that each module in this embodiment corresponds one-to-one with each step in Embodiment 1, and their specific implementation processes are the same, so they will not be repeated here.
[0139] Example 3
[0140] This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of a charging station equipment monitoring method as described in Embodiment 1 above.
[0141] Example 4
[0142] This embodiment provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps in the charging station equipment monitoring method described in Embodiment 1 above.
[0143] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.
[0144] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0145] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0146] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0147] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.
[0148] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A method for monitoring charging station equipment, characterized in that, include: Obtain the charging pile BMS message file stream; After parsing the charging pile BMS message file stream, a B-tree structure data of the BMS message is established; For each charging pile fault data in the charging pile fault set, based on the fault time, the leaf node is searched in the B-tree structure data of the BMS message, and the charging pile fault is determined based on the numerical item of the leaf node. In the B-tree structure of the BMS message, the root node is a charging pile, the end time of each charging record is taken as the key of the root node, and a pointer is used to point to the second-level child node; in the second-level child node, the charging record of the charging pile is taken as the node content, and the upload time of each BMS message is taken as the key of the second-level child node, and a pointer is used to point to the leaf node. In the leaf node, the upload time of the BMS message is used as the key, and the key name and key value in the BMS message are used as numeric items.
2. The method for monitoring charging station equipment as described in claim 1, characterized in that, Also includes: For a specific charging pile fault data, the B-tree structure data of the corresponding BMS message is found based on the device ID information.
3. The method for monitoring charging station equipment as described in claim 1, characterized in that, Before parsing the charging pile BMS message file stream, a CRC16 check is used to verify whether the data in the received charging pile BMS message file stream is correct.
4. The method for monitoring charging station equipment as described in claim 1, characterized in that, Before parsing the charging pile BMS message file stream, the charging pile BMS message file stream is deduplicated, and data frames with the same value in adjacent time periods are deleted, keeping only the first and last frames with the same value.
5. The method for monitoring charging station equipment as described in claim 1, characterized in that, Each charging pile fault data includes the device ID, fault time, fault type, and fault description.
6. The method for monitoring charging station equipment as described in claim 1, characterized in that, After completing the fault diagnosis of the charging pile, delete the node in the B-tree structure data of the BMS message. The specific steps are: find the second-level node where a certain keyword is located. Delete the key at the second-level node level and delete the leaf node pointed to by the pointer corresponding to the key.
7. The method for monitoring charging station equipment as described in claim 1, characterized in that, The specific steps for finding leaf nodes are as follows: Determine if the fault time is within the key range of the root node. If so, continue searching along the second-level node pointed to by the pointer corresponding to the key; otherwise, the BMS daily operation report does not exist. Determine if the fault time is within the key range of the secondary node. If so, continue searching along the leaf node pointed to by the pointer corresponding to the key; otherwise, the BMS daily operation report does not exist. Determine if the fault time is within the keyword range of the leaf node. If so, read the numeric item of the leaf node; otherwise, the BMS daily operation report does not exist.
8. A charging station equipment monitoring system, characterized in that, include: The message acquisition module is configured to acquire the message file stream of the charging pile BMS. The tree building module is configured to: parse the charging pile BMS message file stream and then build the B-tree structure data of the BMS message; The fault diagnosis module is configured to: for each charging pile fault data in the charging pile fault set, search for the leaf node in the B-tree structure data of the BMS message according to the fault time, and determine the charging pile fault based on the numerical item of the leaf node; In the B-tree structure of the BMS message, the root node is a charging pile, the end time of each charging record is taken as the key of the root node, and a pointer is used to point to the second-level child node; in the second-level child node, the charging record of the charging pile is taken as the node content, and the upload time of each BMS message is taken as the key of the second-level child node, and a pointer is used to point to the leaf node. In the leaf node, the upload time of the BMS message is used as the key, and the key name and key value in the BMS message are used as numeric items.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps in the charging station equipment monitoring method as described in any one of claims 1-7.
10. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the charging station equipment monitoring method as described in any one of claims 1-7.
Citation Information
Patent Citations
A method of recovering deleted data in APFS based on copy-on-write
CN110297781A
High-speed decoder for polar codes
US11012093B2