Multi-dimensional monitoring method and system for charging station management

Abstract

The application is suitable for the technical field of data processing, and provides a charging station management method and system for multi-dimensional monitoring, comprising: acquiring charging pile attribute information corresponding to each charging pile in a charging station, charging gun type information corresponding to each charging gun, and device state information corresponding to each charging gun, to construct device state data; determining state change results of each charging gun, and performing legality verification to generate corresponding abnormal early warning information; generating corresponding order data according to the state change results of each charging gun, and storing the order data and the device state data of the corresponding charging gun in association; and performing device linkage control on the corresponding charging gun based on the abnormal early warning information and the corresponding order data. Through the above scheme, the problems of untimely abnormal order processing, low charging resource allocation accuracy and low device linkage control efficiency when the charging gun has state abnormalities, state conflicts or abnormal persistence are solved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a multi-dimensional monitoring method and system for managing charging stations. Background Technology

[0002] With the popularization of new energy vehicles, the construction scale of charging stations is constantly expanding. Charging stations are usually equipped with multiple charging piles and multiple charging guns to meet the charging needs of different vehicles. Existing charging station management platforms can usually perform basic monitoring of the charging pile operation status, charging order information, and equipment network status, and realize functions such as charging management, order management, and abnormal alarms based on the corresponding equipment data, thereby improving the operation and management capabilities of charging stations.

[0003] However, in the existing charging station management process, due to the lack of an effective correlation analysis mechanism between the charging gun's operating status, order execution status, and equipment network status, it is difficult to identify the actual operating situation corresponding to the abnormal status in a timely manner when the charging gun has abnormal status, status conflict, or continuous abnormality. This further leads to problems such as untimely processing of abnormal orders, low accuracy of charging resource allocation, and low efficiency of equipment linkage control. Summary of the Invention

[0004] This invention provides a charging station management method and system with multi-dimensional monitoring to solve the problems of untimely processing of abnormal orders, low accuracy of charging resource allocation, and low efficiency of equipment linkage control when charging guns experience abnormal status, status conflicts, or persistent abnormalities.

[0005] In a first aspect, embodiments of this application provide a multi-dimensional monitoring method for charging station management, comprising: acquiring charging pile attribute information, charging gun type information, and equipment status information of each charging pile within the charging station; constructing equipment status data based on the charging pile attribute information, the charging gun type information, and the equipment status information; acquiring the current operating status of each charging gun; determining the status change result of the corresponding charging gun based on the current operating status of the same charging gun at different time nodes; verifying the legality of the status change result through a preset status transition rule; generating corresponding abnormal warning information when the status change result fails the legality verification or the duration of the corresponding operating status exceeds a preset duration threshold; generating corresponding order data based on the status change result of each charging gun; associating and storing the order data with the equipment status data of the corresponding charging gun; and performing equipment linkage control on the corresponding charging gun based on the abnormal warning information and the corresponding order data to adjust the order acceptance status, reservation status, or resource allocation status of the corresponding charging gun.

[0006] Optionally, the step of obtaining the charging pile attribute information, the charging gun type information, and the equipment status information corresponding to each charging pile in the charging station includes: obtaining the operation attribute field corresponding to each charging pile, and identifying the operation attribute of each charging pile based on the operation attribute field to obtain the charging pile attribute information; obtaining the gun type configuration field corresponding to each charging gun, and identifying the gun type type of each charging gun based on the gun type configuration field to obtain the charging gun type information; sending a status acquisition command to the control unit of each charging gun, and receiving the network connection status data and equipment operation status data returned by each charging gun to obtain the equipment status information.

[0007] Optionally, the step of constructing device status data based on the charging pile attribute information, the charging gun type information, and the device status information includes: associating the charging pile attribute information, the charging gun type information, and the device status information according to the device affiliation relationship between the charging station, the charging pile, and the charging gun; integrating the operation attribute identifier, gun type identifier, network connection status data, and device operation status data corresponding to each charging gun into a corresponding device status record; and aggregating each device status record according to the corresponding charging pile identifier and charging station identifier to obtain device status data.

[0008] Optionally, the current operating state includes charging state, discharging state, fault state, reserved state, occupied state, idle state, and offline state.

[0009] Optionally, the step of determining the state change result of the corresponding charging gun based on the current operating state of the same charging gun at different time nodes includes: obtaining the current operating state of the same charging gun at the current time node and the historical operating state at the previous time node; when the current operating state is inconsistent with the historical operating state, determining the state transition path from the historical operating state to the current operating state as the state change result of the corresponding charging gun.

[0010] Optionally, the preset state transition rules include a set of legal state transition paths corresponding to each running state; the step of validating the state change result using the preset state transition rules includes: matching the state change result with the set of legal state transition paths; when the state change result exists in the set of legal state transition paths, determining that the state change result passes the validity check; otherwise, determining that the state change result fails the validity check.

[0011] Optionally, the abnormal warning information includes state transition abnormal warning information and state timeout abnormal warning information; wherein, the state transition abnormal warning information indicates that the state change result of the corresponding charging gun has not passed the legality verification, and the state timeout abnormal warning information indicates that the duration of the corresponding operating state exceeds the corresponding preset duration threshold.

[0012] Optionally, the step of generating corresponding order data based on the state change results of each charging gun includes: generating corresponding order data based on the state change results of each charging gun, and obtaining the order execution status corresponding to each order data; obtaining the device operation status data and charging business data corresponding to each charging gun, and performing a consistency check on the current operation status of the corresponding charging gun based on the order execution status, the device operation status data, and the charging business data; generating corresponding state conflict information when the current operation status of the corresponding charging gun is inconsistent with the order execution status, or when the charging business data does not meet the operation conditions of the corresponding operation status; correcting the current operation status of the corresponding charging gun based on the state conflict information, and updating the corresponding order data based on the corrected operation status.

[0013] Optionally, the step of performing device linkage control on the corresponding charging gun based on the abnormal warning information and the corresponding order data includes: obtaining abnormal warning information corresponding to each charging gun, and classifying each abnormal warning information based on the charging pile identifier of the corresponding charging gun; counting the number of abnormal warning information and the abnormal duration of each charging gun under the same charging pile; when the number of abnormal warning information under the same charging pile exceeds a preset number threshold, or the abnormal duration exceeds a preset duration threshold, determining the corresponding charging pile as an associated abnormal charging pile; switching the target charging gun associated with the order data of each charging gun under the associated abnormal charging pile, and performing pause order acceptance control or pause reservation control on the associated abnormal charging pile; and reallocating the charging resources corresponding to other non-abnormal charging guns based on the migrated order data.

[0014] Secondly, this application provides a multi-dimensional monitoring charging station management system, including: a data acquisition module, used to acquire charging pile attribute information, charging gun type information, and equipment status information corresponding to each charging pile in the charging station, and construct equipment status data based on the charging pile attribute information, the charging gun type information, and the equipment status information; a legality verification module, used to acquire the current operating status of each charging gun, and determine the status change result of the corresponding charging gun according to the current operating status of the same charging gun at different time nodes, and perform legality verification on the status change result through a preset status transition rule; an anomaly warning module, used to generate corresponding anomaly warning information when the status change result fails the legality verification, or the duration of the corresponding operating status exceeds a preset duration threshold; an order generation module, used to generate corresponding order data according to the status change result of each charging gun, and associate and store the order data with the equipment status data of the corresponding charging gun; and a linkage control module, used to perform equipment linkage control on the corresponding charging gun based on the anomaly warning information and the corresponding order data, so as to adjust the order acceptance status, reservation status, or resource allocation status of the corresponding charging gun.

[0015] In one solution provided by the aforementioned method and system, device status data is constructed by acquiring charging pile attribute information, charging gun type information, and device status information. The status change results are then determined by combining the current operating status at different time points, enabling dynamic monitoring of the charging gun's operating status changes. By utilizing preset state transition rules to verify the legality of the status change results and generating abnormal warning information based on the operating status duration, the accuracy of abnormal status identification is improved. By generating order data based on the status change results and associating and storing the order data with the device status data, the accuracy of the correspondence between order status and device operating status is improved. Furthermore, by performing device linkage control on the corresponding charging gun based on the abnormal warning information and the corresponding order data, the response efficiency of charging resource adjustment and device control under abnormal conditions is improved. This addresses the problems of untimely abnormal order processing, low accuracy of charging resource allocation, and low efficiency of device linkage control when the charging gun experiences abnormal status, state conflicts, or persistent abnormalities. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. 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.

[0017] Figure 1This is a schematic diagram of the structure of an operating system in one embodiment of the present invention; Figure 2 This is a flowchart illustrating a multi-dimensional monitoring charging station management method according to an embodiment of the present invention. Figure 3 This is a schematic diagram of the process for constructing device status data in one embodiment of the present invention; Figure 4 This is a schematic diagram of the ownership hierarchy of charging station equipment in one embodiment of the present invention; Figure 5 This is a schematic diagram of the legal migration path of the charging gun's operating state in one embodiment of the present invention; Figure 6 This is a schematic diagram of the order data generation and status consistency verification process in one embodiment of the present invention; Figure 7 This is a flowchart illustrating the abnormal linkage control and charging resource redistribution in one embodiment of the present invention. Figure 8 This is a schematic diagram of the structure of a multi-dimensional monitoring charging station management system according to an embodiment of the present invention. Detailed Implementation

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

[0019] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or collections thereof. It should also be understood that, as used in this specification and the appended claims, the term "and / or" refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0020] Furthermore, in the description of this invention and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0021] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of the invention include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0022] It should be understood that the sequence number of each step in the following embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0023] To illustrate the technical solution of the present invention, specific embodiments are described below.

[0024] In existing charging station management, charging stations are often equipped with multiple charging piles and charging guns. Different charging guns generate corresponding equipment operating status, order execution status, and network connection status during operation. Due to the frequent changes in the operating status of different charging guns and the lack of an effective correlation analysis mechanism between different order data and equipment status, it is difficult to accurately identify the true operating status of a charging gun when abnormal state migration, state conflicts, or persistent abnormalities occur. Furthermore, the lack of a linkage processing mechanism between abnormal charging gun status and order data prevents timely adjustment of abnormal orders, easily leading to problems such as abnormal charging resource occupancy, abnormal reservation status, and abnormal equipment order acceptance status. This reduces the efficiency of equipment linkage control and the accuracy of charging resource allocation during charging station operation.

[0025] To address the aforementioned issues, this application proposes a multi-dimensional monitoring method for charging station management. This method constructs equipment status data by acquiring charging pile attribute information, charging gun type information, and equipment status information for each charging gun within the charging station. Based on the current operating status at different time points, the method determines the status change results for the corresponding charging guns. The method then verifies the legality of these status change results using preset status transition rules. If a status change fails the legality verification or the corresponding operating status continuously times out, a corresponding abnormal warning is generated. Simultaneously, order data is generated based on the status change results for each charging gun, and this order data is associated with and stored in conjunction with the corresponding charging gun's equipment status data. Finally, based on the abnormal warning information and the corresponding order data, equipment linkage control is executed on the corresponding charging guns, thereby improving the accuracy of charging gun abnormal status identification, the accuracy of the correspondence between order status and equipment status, and the efficiency of charging resource allocation.

[0026] This invention provides a multi-dimensional monitoring method for charging station management, which can be applied to applications such as... Figure 1 The operating environment shown includes a server and terminal devices, wherein the terminal devices communicate with the server via a network or bus.

[0027] In practical applications, the server receives equipment operation data, network connection data, and order execution data uploaded by each charging pile and charging gun in the charging station. It analyzes the current operating status changes of each charging gun, identifies abnormal status changes of the corresponding charging gun based on preset status transition rules, and performs order acceptance status adjustment, reservation status adjustment, and charging resource allocation control on the corresponding charging gun according to the abnormal status change results and order data, so as to realize the linkage management between different charging guns in the charging station.

[0028] The operating environment can be a terminal device, which refers to a device that corresponds to the server and provides local data processing functions for the user. This terminal device includes personal computers, laptops, smartphones, tablets, and portable wearable devices.

[0029] The operating environment can also be a server, which can be a standalone server or a server cluster consisting of multiple servers. The server can internally deploy a status acquisition module, a status verification module, an order processing module, and an equipment linkage control module to achieve data processing, status analysis, and linkage control for each charging gun within the charging station.

[0030] In one embodiment, such as Figure 2 As shown, a multi-dimensional monitoring method for charging station management is provided, which is then applied to... Figure 1Taking the operating environment in [the document] as an example, the following steps are included: S10: Obtain the charging pile attribute information, the charging gun type information, and the equipment status information of each charging gun in the charging station, and construct equipment status data based on the charging pile attribute information, the charging gun type information, and the equipment status information.

[0031] The server sends equipment information retrieval commands to the control units corresponding to each charging pile within the charging station to obtain the operational attribute fields for each charging pile, and generates corresponding charging pile attribute information based on these fields. Simultaneously, the server sends gun type configuration retrieval commands to the control units corresponding to each charging gun to obtain the gun type configuration fields for each charging gun, and generates corresponding charging gun type information based on these fields. The server also sends status acquisition commands to the control units corresponding to each charging gun via a preset communication protocol to obtain network connection status data and equipment operation status data for each charging gun, and generates corresponding equipment status information based on this data. The server associates the charging pile attribute information, charging gun type information, and equipment status information according to the equipment affiliation relationships between the charging station, charging piles, and charging guns. It integrates the operational attribute identifier, gun type identifier, network connection status data, and equipment operation status data for each charging gun into corresponding equipment status records, and then aggregates these records according to the corresponding charging pile identifier and charging station identifier to generate equipment status data. The preset communication protocol can be OCPP, MQTT, or Modbus.

[0032] For example, the server retrieves the "External Operation Identifier" field of the operation attribute corresponding to charging pile A01, and generates the corresponding charging pile attribute information based on this field; the server retrieves the "DC Type Identifier" field of the gun type configuration corresponding to charging gun G01, and generates the corresponding charging gun type information based on this field; the server sends a status acquisition command to charging gun G01 via the OCPP protocol, receives the network connection status data "Online" and the equipment operation status data "Idle Status" returned by charging gun G01, and generates the corresponding equipment status information. The server integrates the charging pile attribute information "External Operation", the charging gun type information "DC Type", the network connection status data "Online", and the equipment operation status data "Idle Status" into the corresponding equipment status record, and aggregates them according to the charging pile identifier "A01" and the charging station identifier "ST01" to generate the corresponding equipment status data.

[0033] S20: Obtain the current operating status of each charging gun, and determine the state change result of the corresponding charging gun according to the current operating status of the same charging gun at different time nodes, and verify the legality of the state change result through preset state transition rules.

[0034] The server sends status query commands to the control units corresponding to each charging gun according to a preset collection cycle, and receives the current operating status of each charging gun at the current time node. The server reads the historical operating status of the same charging gun at the previous time node from the status record cache and compares the current operating status with the historical operating status. When the current operating status is inconsistent with the historical operating status, the server determines the state transition path between the historical operating status and the current operating status as the state change result of the corresponding charging gun. The server pre-establishes a set of legal state transition paths, which is generated based on the business flow relationship between different operating states. For example, the idle state can transition to the reserved state, the occupied state, or the charging state, and the charging state can transition to the idle state or the fault state. The server matches the state change result with the set of legal state transition paths. When the state change result exists in the set of legal state transition paths, the state change result is determined to have passed the legality check; when the state change result does not exist in the set of legal state transition paths, the state change result is determined to have failed the legality check.

[0035] For example, at 10:00, the server retrieves the historical operating status "Idle" for charging gun G01, and at 10:05, it retrieves the current operating status "Charging" for charging gun G01. The server determines "Idle → Charging" as the corresponding state change result. Since the set of valid state transition paths contains a "Idle → Charging" state transition path, the state change result passes the validity check. If the server retrieves the current operating status "Offline" for charging gun G01 at 10:10, the server determines "Charging → Offline" as the corresponding state change result; if the set of valid state transition paths does not contain a "Charging → Offline" state transition path, the state change result fails the validity check.

[0036] The current operating status includes charging, discharging, fault, reserved, occupied, idle and offline status. The preset state transition rules include a set of legal state transition paths between each operating status.

[0037] S30: When the state change result fails the validity check, or the duration of the corresponding running state exceeds the preset duration threshold, generate the corresponding abnormal warning information.

[0038] The server obtains the status change results and duration of the corresponding operating state for each charging gun, and matches the validity verification results of the status change results with preset anomaly judgment rules. When the status change result fails the validity verification, the server generates a corresponding status transition anomaly warning message; when the duration of the corresponding operating state exceeds the preset duration threshold for the corresponding operating state, the server generates a corresponding status timeout anomaly warning message. The preset duration threshold is configured based on the normal business duration corresponding to different operating states. For example, the preset duration threshold for the reservation state is 30 minutes, the preset duration threshold for the occupied state is 20 minutes, and the preset duration threshold for the fault state is 10 minutes. The server integrates the charging gun identifier, the corresponding charging pile identifier, the corresponding charging station identifier, the anomaly type, and the anomaly generation time into the corresponding anomaly warning message.

[0039] For example, if the server detects that the status change result "charging status → offline status" corresponding to the charging gun with the number G01 fails the validity check, it will generate the corresponding status transition anomaly warning information, and the anomaly type field will be "illegal status transition anomaly"; if the server detects that the charging gun with the number G02 has been running continuously in the "reservation status" for 45 minutes, exceeding the preset duration threshold of 30 minutes corresponding to the reservation status, it will generate the corresponding status timeout anomaly warning information, and the anomaly type field will be "reservation timeout anomaly".

[0040] S40: Generate corresponding order data based on the status change results of each charging gun, and associate and store the order data with the device status data of the corresponding charging gun.

[0041] The server obtains the status change results for each charging gun and generates corresponding order data based on a preset correspondence between status changes and order types. This preset correspondence is configured based on the business execution logic corresponding to different status change results; for example, "Idle state → Charging state" corresponds to a charging order, "Idle state → Discharging state" corresponds to a discharging order, "Idle state → Reservation state" corresponds to a reservation order, and "Charging state → Occupied state" corresponds to a placeholder order. The server obtains the order execution status corresponding to each order data, as well as the device operating status data and charging business data for each charging gun. The charging business data includes charging current data, charging power data, and order duration data. The server performs a consistency check on the current operating status of the corresponding charging gun based on the order execution status, device operating status data, and charging business data. When the current operating status is inconsistent with the order execution status, or when the charging business data does not meet the operating conditions of the corresponding operating status, the server generates corresponding status conflict information. The server corrects the current operating status of the corresponding charging gun based on the status conflict information and updates the corresponding order data based on the corrected operating status.

[0042] For example, if the server detects that the status change of the charging gun with the number G01 is "idle state → charging state", then the corresponding charging order will be generated; if the server detects that the order execution status of the charging gun with the number G02 is "charging in progress", but the corresponding device operation status data is "idle state", and the charging current data is 0A and the charging power data is 0kW, then the server will generate the corresponding status conflict information, correct the current operation status from "charging state" to "idle state", and update the corresponding order data to "abnormal termination state".

[0043] S50: Based on abnormal warning information and corresponding order data, perform device linkage control on the corresponding charging gun to adjust the order acceptance status, reservation status or resource allocation status of the corresponding charging gun.

[0044] The server acquires abnormal warning information corresponding to each charging gun and categorizes these warnings based on the charging pile identifier of the corresponding charging gun. The server counts the number of abnormal warnings and their duration for each charging gun under the same charging pile, and compares the results with preset quantity and duration thresholds. When the number of abnormal warnings under the same charging pile exceeds the preset quantity threshold, or the duration exceeds the preset duration threshold, the server identifies the corresponding charging pile as an associated abnormal charging pile. The server switches the target charging gun associated with the order data for each charging gun under the associated abnormal charging pile and sends a pause order acceptance control command or a pause reservation control command to the control unit corresponding to the associated abnormal charging pile. The server also reallocates charging resources for other non-abnormal charging guns based on the migrated order data. The preset quantity threshold is configured based on the allowed number of abnormal charging guns under the same charging pile, for example, a preset quantity threshold of 2; the preset duration threshold is configured based on the allowed duration of the abnormality, for example, a preset duration threshold of 15 minutes.

[0045] For example, if the server detects that three charging guns under charging pile A01 have generated abnormal warning messages, and the abnormal duration of two of these charging guns exceeds 15 minutes, then the server identifies charging pile A01 as an associated abnormal charging pile. The server switches the reservation order originally associated with charging gun G01 to the non-abnormal charging gun G05, and sends a pause order acceptance control command to the control unit corresponding to charging pile A01. Based on the migrated order data, the server adjusts the reservation priority corresponding to charging gun G05 to the highest priority and reallocates the corresponding charging resources.

[0046] Among them, the abnormal warning information includes state transition abnormal warning information and state timeout abnormal warning information. The state transition abnormal warning information indicates that the state change result of the corresponding charging gun has not passed the legality verification, and the state timeout abnormal warning information indicates that the duration of the corresponding operating state exceeds the corresponding preset duration threshold.

[0047] In this embodiment, device status data is constructed by acquiring charging pile attribute information, charging gun type information, and device status information. The status change result of the corresponding charging gun is determined by combining the current operating status at different time points. The legality of the status change result is verified by using preset status transition rules, which can improve the accuracy of identifying abnormal charging gun status. By generating corresponding order data based on the status change result and verifying the consistency of the current operating status by combining device operating status data and charging business data, the correspondence between order data and device operating status can be improved. By executing device linkage control based on abnormal warning information and corresponding order data, the efficiency of charging resource allocation and device linkage control under abnormal conditions can be improved.

[0048] In one embodiment, such as Figure 3 As shown, step S10 involves obtaining the attribute information of each charging pile in the charging station, the type information of each charging gun, and the device status information of each charging gun. Specifically, this includes the following steps: S11: Obtain the operation attribute fields corresponding to each charging pile, and identify the operation attributes of each charging pile based on the operation attribute fields to obtain the charging pile attribute information; wherein, the operation attribute fields include internal operation identifiers and external operation identifiers.

[0049] The server sends attribute read commands to the control units corresponding to each charging pile within the charging station and receives the operation attribute fields returned by each charging pile. The operation attribute fields are stored using a preset field structure, which includes a charging pile identifier field, an operation type field, and an operation permission field. The operation type field indicates the operational openness scope of the corresponding charging pile, and the operation permission field indicates the types of users allowed to access the corresponding charging pile. The server reads the field value in the operation type field and performs operation attribute identification processing on the corresponding charging pile based on the field value. When the corresponding field value of the operation type field is "0", the corresponding charging pile is identified as an internal operation identifier; when the corresponding field value of the operation type field is "1", the corresponding charging pile is identified as an external operation identifier. The server combines the charging pile identifier, operation attribute identifier, and operation permission field to generate the corresponding charging pile attribute information.

[0050] For example, the server sends an attribute read command to charging pile A01 and receives the operation attribute fields returned by charging pile A01. The operation type field has a value of "1", and the operation permission field has a value of "public user". Based on the operation type field value of "1", the server identifies charging pile A01 as an external operation identifier and integrates the charging pile identifier "A01", the operation attribute identifier "external operation", and the operation permission field "public user" into the corresponding charging pile attribute information. The server sends an attribute read command to charging pile A02 and receives the operation attribute fields returned by charging pile A02. The operation type field has a value of "0". The server identifies charging pile A02 as an internal operation identifier and generates the corresponding charging pile attribute information.

[0051] S12: Obtain the gun type configuration field corresponding to each charging gun, and identify the gun type type of each charging gun based on the gun type configuration field to obtain the charging gun type information; wherein, the gun type configuration field includes DC type identifier and AC type identifier.

[0052] The server sends a charging gun configuration read command to the control unit corresponding to each charging gun and receives the charging gun configuration fields returned by each charging gun. The charging gun configuration fields include a charging gun identifier field, an output current type field, a rated output power field, and an interface specification field. The output current type field indicates the output current type of the corresponding charging gun. The server reads the field value corresponding to the output current type field and performs charging gun type identification processing based on the field value. When the value of the output current type field is "DC", the corresponding charging gun is identified as a DC type identifier; when the value of the output current type field is "AC", the corresponding charging gun is identified as an AC type identifier. The server combines the charging gun identifier, charging gun type identifier, rated output power field, and interface specification field to generate the corresponding charging gun type information.

[0053] For example, the server sends a charging gun configuration read command to charging gun number G01, and receives the charging gun configuration fields returned by charging gun number G01. In this field, the output current type field has a value of "DC", the rated output power field has a value of "120kW", and the interface specification field has a value of "national standard dual-gun interface". Based on the output current type field value of "DC", the server identifies charging gun number G01 as a DC type identifier, and integrates the charging gun identifier "G01", the charging gun type identifier "DC type", the rated output power field "120kW", and the interface specification field "national standard dual-gun interface" into the corresponding charging gun type information. The server sends a charging gun configuration read command to charging gun number G02, receives the output current type field value of "AC" returned by charging gun number G02, and identifies charging gun number G02 as an AC type identifier.

[0054] S13: Send a status acquisition command to the control unit of each charging gun, and receive network connection status data and equipment operation status data returned by each charging gun to obtain equipment status information.

[0055] The server sends status acquisition commands to the control units corresponding to each charging gun according to a preset acquisition cycle, and receives network connection status data and device operation status data returned by each charging gun through a preset communication protocol. The preset acquisition cycle is configured based on the charging station's operation data refresh frequency; for example, the preset acquisition cycle is 5 seconds. The preset communication protocol uses OCPP, MQTT, or Modbus protocols. Network connection status data includes online status data, offline status data, and communication latency data; device operation status data includes current operation status fields, device temperature fields, output voltage fields, and output current fields. The server parses the network connection status data and device operation status data, and generates corresponding device status information based on the parsing results.

[0056] For example, the server sends a status acquisition command to the charging gun numbered G01 at a preset acquisition cycle of 5 seconds, and receives network connection status data and device operation status data returned by the charging gun numbered G01 via the OCPP protocol. The network connection status data includes the online status data "Online" and the communication latency data "35ms"; the device operation status data includes the current operation status field "Charging", the device temperature field "42℃", the output voltage field "750V", and the output current field "160A". The server parses each field and generates the corresponding device status information. When the server sends a status acquisition command to the charging gun numbered G03, if no data is received for three consecutive acquisition cycles, the server marks the network connection status data of the charging gun numbered G03 as offline status data and generates the corresponding device status information.

[0057] In this embodiment, by acquiring the operation attribute fields corresponding to each charging pile and generating corresponding charging pile attribute information, it is possible to achieve classified management of charging piles of different operation types; by acquiring the gun type configuration fields corresponding to each charging gun and generating corresponding charging gun type information, it is possible to achieve classified identification of charging guns of different gun types; by collecting network connection status data and equipment operation status data corresponding to each charging gun to generate equipment status information, it is possible to improve the completeness of charging gun operation status monitoring; furthermore, by performing unified structured processing on the operation attribute fields, gun type configuration fields, and equipment operation status data, it is possible to improve the accuracy of data association in the process of constructing equipment status data.

[0058] In one embodiment, such as Figure 4 As shown, step S10, which involves constructing device status data based on charging pile attribute information, charging gun type information, and device status information, specifically includes the following steps: S14: Associate charging pile attribute information, charging gun type information, and equipment status information according to the equipment ownership relationship between charging stations, charging piles, and charging guns.

[0059] The server reads a pre-stored device topology table within the charging station and establishes device affiliation relationships between charging stations, charging piles, and charging guns based on this table. The device topology table includes charging station identifier, charging pile identifier, and charging gun identifier fields. The server associates charging pile attribute information, charging gun type information, and device status information according to the affiliation relationships where the same charging station identifier corresponds to multiple charging pile identifiers, and the same charging pile identifier corresponds to multiple charging gun identifiers, generating corresponding hierarchical association results.

[0060] For example, the server reads the device topology table, where the charging station identifier "ST01" corresponds to charging pile identifiers "A01" and "A02", and the charging pile identifier "A01" corresponds to charging gun identifiers "G01" and "G02". The server associates the charging pile attribute information corresponding to charging pile identifier "A01", the charging gun type information corresponding to charging gun identifier "G01", and the device status information corresponding to charging gun identifier "G01", and generates the corresponding hierarchical association results.

[0061] S15: Integrate the operational attribute identifier, gun type identifier, network connection status data, and device operation status data corresponding to each charging gun into the corresponding device status record.

[0062] The server integrates the data fields corresponding to each charging gun based on a preset data record structure. This preset data record structure includes fields for charging station identification, charging pile identification, charging gun identification, operational attribute identification, gun type identification, network connection status, current operating status, equipment temperature, output voltage, output current, and data acquisition time. The server writes the operational attribute identification, gun type identification, network connection status data, and equipment operating status data corresponding to the same charging gun into the corresponding fields to generate the corresponding equipment status record.

[0063] For example, the server integrates the charging station identifier "ST01", charging pile identifier "A01", charging gun identifier "G01", operation attribute identifier "external operation", gun type identifier "DC type", network connection status field "online", current operating status field "charging", equipment temperature field "42℃", output voltage field "750V", output current field "160A", and data acquisition time field "2026-05-25 10:05:00" into a device status record numbered R001.

[0064] S16: Aggregate the status records of each device according to the corresponding charging pile identifier and charging station identifier to obtain device status data.

[0065] The server groups the status records of each device based on the charging pile identifier and the charging station identifier, and counts the number of device status records, the number of online charging guns, the number of abnormal charging guns, and the number of charging in progress for each charging gun under the same charging pile. The server combines the statistical results with the corresponding device status records to generate the corresponding device status data. The server uses a hash index structure to build a mapping index for the charging station identifier and the charging pile identifier to improve the retrieval efficiency of device status data.

[0066] For example, the server reads the device status records corresponding to the charging station identifier "ST01". Among them, there are 2 device status records under the charging pile identifier "A01", with 2 online charging guns, 0 abnormal charging guns, and 1 charging in progress. The server combines the above statistical results with the corresponding device status records to generate the corresponding device status data and establishes a hash index mapping relationship for "ST01-A01".

[0067] In this embodiment, by associating charging pile attribute information, charging gun type information, and equipment status information according to the device affiliation relationship between charging stations, charging piles, and charging guns, the accuracy of the correspondence between equipment data at different levels can be improved; by integrating operational attribute identifiers, charging gun type identifiers, network connection status data, and equipment operation status data into corresponding equipment status records, the structuring degree of equipment status data can be improved; and by aggregating equipment status records according to corresponding charging pile identifiers and charging station identifiers, the unified management efficiency and status retrieval efficiency of equipment status data can be improved.

[0068] In one embodiment, step S20, which determines the state change result of the corresponding charging gun based on the current operating state of the same charging gun at different time points, specifically includes the following steps: S21: Obtain the current operating status of the same charging gun at the current time node and the historical operating status at the previous time node.

[0069] The server reads the current operating status of each charging gun according to a preset status acquisition cycle, and retrieves the historical operating status of the same charging gun at the previous time point from the status cache record area. The status cache record area uses a circular queue structure to store the historical operating status data for each charging gun. The circular queue structure includes a charging gun identifier field, an operating status field, and a status acquisition time field. The server matches the current operating status with the historical operating status based on the charging gun identifier and generates the corresponding status comparison result.

[0070] For example, at time node "10:10:00", the server reads the current operating status "charging" for charging gun number G01, and reads the historical operating status "idle" for charging gun number G01 at time node "10:05:00" from the status cache record area. The server matches the current operating status "charging" and the historical operating status "idle" based on the charging gun identifier "G01" and generates the corresponding status comparison result.

[0071] S22: When the current operating state is inconsistent with the historical operating state, the state transition path from the historical operating state to the current operating state is determined as the state change result of the corresponding charging gun.

[0072] The server performs a difference analysis on the state comparison results. When the current operating state is inconsistent with the historical operating state, the server generates a corresponding state transition path based on the historical and current operating states, and identifies the state transition path as the state change result of the corresponding charging gun. The server generates the state transition path using string concatenation, and the data structure of the state transition path includes a starting state field, a target state field, and a state change time field. The server writes the corresponding state change result into the state change record table.

[0073] For example, if the server detects that the historical operating state of charging gun G01 is "Idle" and the current operating state is "Charging", then the server generates a state transition path "Idle → Charging" and identifies this state transition path as the state change result for charging gun G01. The server writes the starting state field "Idle", the target state field "Charging", and the state change time field "2026-05-25 10:10:00" into the state change record table. If the server detects that the historical operating state and the current operating state of charging gun G02 are both "Reserved", then the server does not generate a state transition path and keeps the corresponding state change result unchanged.

[0074] In this embodiment, by acquiring the current and historical operating states of the same charging gun at different time points, continuous monitoring of the charging gun's operating state changes can be achieved; by generating corresponding state transition paths based on historical and current operating states, the accuracy of state change result identification can be improved; furthermore, by recording and storing the state change results, the state tracking capability during the state legality verification process can be improved.

[0075] In one embodiment, such as Figure 5 As shown, step S20, which involves validating the state change results using preset state transition rules, specifically includes the following steps: S23: Match the state change results with the set of legal state transition paths.

[0076] The server reads a pre-stored set of legal state transition paths and performs path matching based on the starting state field and target state field in the state change results. The set of legal state transition paths is stored using a state mapping table structure, which includes a starting state field, an allowed transition state field, a state transition priority field, and a business condition field. The business condition field indicates the operating conditions for the corresponding state transition path to be allowed to execute. For example, when transitioning from idle to charging, the network connection status data of the corresponding charging gun must be online, and the output voltage field in the device operating status data must be greater than a preset voltage threshold. The server matches the state change results with the set of legal state transition paths using a hash matching algorithm, employing a HashMap key-value matching algorithm. The server combines the starting state field and target state field from the state change results to generate a state matching key value and retrieves the corresponding state matching key value from the set of legal state transition paths to generate the corresponding path matching result.

[0077] For example, the server reads the status change result "Idle State → Charging State" for charging gun number G01 and generates a status matching key value "K1" for "Idle State → Charging State". The server reads the set of legal state transition paths, where the status mapping table contains the status matching key value "K1", the corresponding allowed transition state field is "Charging State", and the business condition fields include "Network connection status data = Online status data" and "Output voltage field ≥ 200V". The server detects that the network connection status data for charging gun number G01 is "Online status data" and the output voltage field is "750V", so it generates the corresponding path matching result. The server reads the status change result "Fault State → Charging State" for charging gun number G02 and generates a status matching key value "K2". Since the status matching key value "K2" does not exist in the set of legal state transition paths, the corresponding path matching result is determined to be a mismatch.

[0078] S24: If the state change result exists in the set of legal state transition paths, the state change result is determined to have passed the legality check; otherwise, the state change result is determined to have failed the legality check.

[0079] The server performs validity checks on the corresponding state change results based on the path matching results. When the path matching result is successful and the corresponding business condition field meets the corresponding operating conditions, the server determines that the corresponding state change result passes the validity check and writes a validity check identifier field into the state change record table. When the path matching result is unsuccessful, or the corresponding business condition field does not meet the corresponding operating conditions, the server determines that the corresponding state change result fails the validity check and generates a corresponding illegal state migration record. The illegal state migration record includes a charging gun identifier field, a starting state field, a target state field, an illegal reason field, and a verification time field. The server writes the illegal state migration record into the abnormal state record table.

[0080] For example, if the server detects that the status change result "Idle State → Charging State" for charging gun G01 exists in the set of valid state migration paths, and the corresponding business condition fields meet the operating conditions of "Network Connection Status Data = Online Status Data" and "Output Voltage Field ≥ 200V", then the server determines that the status change result for charging gun G01 passes the validity check and writes the validity check identifier field "1" into the status change record table. If the server detects that the status change result "Fault State → Charging State" for charging gun G02 does not exist in the set of valid state migration paths, then the server determines that the status change result for charging gun G02 fails the validity check and generates an illegal state migration record, where the illegal reason field corresponds to "Fault State is prohibited from directly migrating to Charging State".

[0081] In this embodiment, by matching the state change results with the set of legal state transition paths, the accuracy of the legality verification of the state change results can be improved; by adding a business condition field to the set of legal state transition paths, the correspondence between the state transition rules and the actual charging business can be improved; by generating illegal state transition records for state change results that fail the legality verification, the ability to track abnormal states and identify abnormal causes can be improved.

[0082] In one embodiment, such as Figure 6 As shown, step S40, which generates corresponding order data based on the status change results of each charging gun, specifically includes the following steps: S41: Generate corresponding order data based on the status change results of each charging gun, and obtain the order execution status corresponding to each order data.

[0083] The server reads the status change results for each charging gun and generates corresponding order data based on a preset correspondence between status changes and order types. This correspondence is stored in a mapping table structure, which includes a starting status field, a target status field, an order type field, and an order execution status field. The server retrieves the corresponding order type field based on the starting and target status fields in the status change results and generates the corresponding order data. The order data includes an order number field, an order type field, an order generation time field, a charging gun identifier field, a charging pile identifier field, and an order execution status field. The server obtains the order execution status corresponding to each order based on the order execution status field.

[0084] For example, the server reads the status change result "Idle → Charging" for charging gun number G01, and retrieves the corresponding order type field "Charging Order" and order execution status field "Executing" from the mapping table. The server generates the corresponding order data, where the order number field is "O20260525001", the order type field is "Charging Order", the order generation time field is "2026-05-25 10:20:00", the charging gun identifier field is "G01", the charging pile identifier field is "A01", and the order execution status field is "Executing". The server reads the status change result "Idle → Reservation" for charging gun number G03 and generates the corresponding reservation order.

[0085] S42: Obtain the device operation status data and charging business data corresponding to each charging gun. The charging business data includes charging current data, charging power data, and order duration data. Based on the order execution status, device operation status data, and charging business data, perform a consistency check on the current operation status of the corresponding charging gun.

[0086] The server acquires device operating status data and charging service data for each charging gun and performs consistency verification on the current operating status based on preset operating condition rules. These preset operating condition rules are stored in a rule judgment table structure, which includes an order execution status field, a corresponding operating status field, a minimum charging current threshold field, a minimum charging power threshold field, and a maximum order duration field. The server uses a rule engine algorithm, specifically the Drools rule engine algorithm, to perform rule matching on the order execution status, device operating status data, and charging service data. The server compares the order execution status field with the corresponding operating status field and compares the charging current data, charging power data, and order duration data with the corresponding threshold fields to generate a consistency verification result.

[0087] For example, the server retrieves the order execution status "in execution", current running status "charging", charging current data "160A", charging power data "120kW", and order duration data "15 minutes" for the charging gun with the number G01. The server reads the rule judgment table, where the running status field corresponding to "in execution" is "charging", the minimum charging current threshold field is "50A", and the minimum charging power threshold field is "20kW". The server detects that the current running status is consistent with the order execution status, and the charging current data "160A" is greater than the minimum charging current threshold "50A", and the charging power data "120kW" is greater than the minimum charging power threshold "20kW", therefore, the corresponding consistency check result is determined to be passed.

[0088] S43: When the current operating status of the corresponding charging gun is inconsistent with the order execution status, or when the charging business data does not meet the operating conditions of the corresponding operating status, generate the corresponding status conflict information.

[0089] The server performs status conflict identification processing on the corresponding charging gun based on the consistency verification results. When the current operating status is inconsistent with the order execution status, the server generates a status type conflict identifier; when the charging current data, charging power data, or order duration data does not meet the operating conditions of the corresponding operating status, the server generates a business data conflict identifier. The server integrates the status type conflict identifier, business data conflict identifier, charging gun identifier field, current operating status field, order execution status field, and conflict generation time field into status conflict information. The server uses a Boolean logic judgment algorithm to combine and judge different conflict conditions.

[0090] For example, if the server detects that the order execution status for charging gun G02 is "in execution" and the current running status is "idle," then the server generates a status type conflict identifier "status inconsistency conflict." If the server detects that the current running status for charging gun G03 is "charging," but the charging current data is "0A" and the charging power data is "0kW," which does not meet the operating conditions corresponding to the "charging" status, then the server generates a business data conflict identifier "business data anomaly conflict." The server integrates the corresponding conflict identifiers and related fields into status conflict information.

[0091] S44: Correct the current operating status of the corresponding charging gun based on the status conflict information, and update the corresponding order data based on the corrected operating status.

[0092] The server reads the status conflict information and performs status correction processing on the corresponding charging gun based on preset status correction rules. These preset status correction rules are stored in a correction rule table structure, which includes a conflict type field, a target correction status field, and an order update status field. The server retrieves the corresponding target correction status field based on the conflict type field in the status conflict information and corrects the current operating status of the corresponding charging gun to the target correction status. The server also synchronously updates the order execution status field, order end time field, and order exception identifier field in the corresponding order data.

[0093] For example, the server reads the status conflict information corresponding to charging gun number G02, where the conflict type field is "status inconsistency conflict". The server retrieves the corresponding target correction status field "idle state" and the order update status field "abnormal end state" from the correction rule table, and corrects the current running status of charging gun number G02 to "idle state". At the same time, it updates the order execution status field in the corresponding order data to "abnormal end state" and the order abnormality identifier field to "1". The server reads the status conflict information corresponding to charging gun number G03, where the conflict type field is "business data abnormal conflict", and corrects the current running status to "fault state".

[0094] In this embodiment, by generating corresponding order data based on state change results, the accuracy of the correspondence between the order generation process and the state change process can be improved; by combining order execution status, device operation status data and charging service data to perform consistency verification on the current operation status, the accuracy of device operation status identification can be improved; by generating state conflict information and performing state correction processing, the consistency between order data and device operation status and the ability to identify abnormal orders can be improved.

[0095] In one embodiment, such as Figure 7 As shown, step S50, which involves performing device linkage control on the corresponding charging gun based on the abnormal warning information and the corresponding order data, specifically includes the following steps: S51: Obtain abnormal warning information corresponding to each charging gun, and classify each abnormal warning information based on the charging pile identifier of the corresponding charging gun.

[0096] The server reads each abnormal warning message from the abnormal warning record table and extracts the charging gun identifier field, charging pile identifier field, abnormality type field, and abnormality generation time field from the corresponding abnormal warning message. The server groups and categorizes each abnormal warning message based on the charging pile identifier field and generates corresponding abnormality categorization results. The abnormality categorization results are stored using a linked list data structure, which includes the charging pile identifier field and a set of corresponding abnormal warning message nodes.

[0097] For example, the server reads the abnormal warning information corresponding to charging guns numbered G01, G02, and G03. The charging pile identifier field for charging guns numbered G01 and G02 is "A01", while the charging pile identifier field for charging gun numbered G03 is "A02". The server groups the abnormal warning information based on the charging pile identifier field and generates abnormal classification results for charging pile identifier "A01" and charging pile identifier "A02".

[0098] S52: Count the number of abnormal warning messages and the duration of abnormality for each charging gun under the same charging pile.

[0099] The server reads the set of abnormal warning information nodes from the corresponding abnormal classification results and counts the number of abnormal warning information for the same charging pile. The server calculates the duration of the corresponding abnormality based on the abnormality generation time field and the current time field. The server uses a time difference calculation algorithm, specifically a Unix timestamp difference algorithm, to calculate the abnormality duration. The server writes the statistical results to the abnormality statistics record table.

[0100] For example, the server reads the anomaly classification result corresponding to the charging pile identifier "A01" and detects 3 anomaly warning messages in the corresponding anomaly warning message node set. The server reads the corresponding anomaly generation time field "2026-05-25 10:00:00" and obtains the current time field "2026-05-25 10:20:00". Using the Unix timestamp difference calculation algorithm, the server calculates the corresponding anomaly duration to be 20 minutes. The server writes the number of anomaly warning messages "3" and the anomaly duration "20 minutes" into the anomaly statistics record table.

[0101] S53: When the number of abnormal warning messages under the same charging pile exceeds the preset number threshold, or the abnormal duration exceeds the preset duration threshold, the corresponding charging pile will be identified as an associated abnormal charging pile.

[0102] The server reads the number of abnormal warning messages and the duration of abnormal events from the abnormal statistics record table, and compares them with preset quantity thresholds and preset duration thresholds, respectively. The preset quantity threshold is configured based on the number of abnormal charging guns allowed to exist simultaneously on the same charging pile; for example, the preset quantity threshold is 2. The preset duration threshold is configured based on the allowed duration of abnormal events; for example, the preset duration threshold is 15 minutes. When the number of abnormal warning messages exceeds the preset quantity threshold, or the abnormal duration exceeds the preset duration threshold, the server identifies the corresponding charging pile as an associated abnormal charging pile and generates a corresponding associated abnormality identifier field.

[0103] For example, if the server detects that the number of abnormal warning messages corresponding to the charging pile identifier "A01" is "3", which is greater than the preset number threshold "2", and the abnormal duration is "20 minutes", which is greater than the preset duration threshold "15 minutes", then the server will identify the charging pile identifier "A01" as an associated abnormal charging pile and generate the associated abnormal identifier field "1".

[0104] S54: Switch the target charging gun associated with the order data of each charging gun under the associated abnormal charging pile, and implement pause order acceptance control or pause reservation control for the associated abnormal charging pile.

[0105] The server reads the order data corresponding to each charging gun under the associated abnormal charging pile and extracts the target charging gun identifier field from the order data. The server retrieves non-abnormal charging guns that are currently online and have not generated any abnormal warning information, and switches the target charging gun based on preset resource migration rules. These preset resource migration rules include gun type matching rules, rated output power matching rules, and current load priority rules. The server uses a greedy allocation algorithm to switch the target charging gun, specifically a minimum load priority greedy algorithm. The server sends a pause order acceptance control command or a pause reservation control command to the control unit corresponding to the associated abnormal charging pile.

[0106] For example, the server reads the reservation order corresponding to charging gun number G01 under charging pile identifier "A01", and detects that charging gun number G05 meets the conditions of online status, DC type, and lowest current load. Therefore, the server switches the target charging gun associated with the corresponding reservation order from number G01 to number G05 based on the minimum load priority greedy algorithm. The server sends a pause order acceptance control command to the control unit corresponding to charging pile identifier "A01" and updates the pause order acceptance status field to "on".

[0107] S55: Based on the migrated order data, the charging resources corresponding to other non-abnormal charging guns are reallocated.

[0108] The server reads the migrated order data and calculates the current load data, remaining reserved capacity data, and device operating status data for each non-abnormal charging gun. The server reallocates charging resources based on preset resource allocation rules, including priority rules for remaining reserved capacity, low load, and same-type charging guns. The server uses a weighted round-robin algorithm to reallocate charging resources. The server generates corresponding resource allocation results based on the load weight value and remaining reserved capacity weight value for different non-abnormal charging guns and updates the resource allocation field in the corresponding order data.

[0109] For example, the server reads data corresponding to non-abnormal charging guns numbered G05 and G06. Charging gun G05 has a current load of "30%" and a remaining reserved capacity of "5", while charging gun G06 has a current load of "70%" and a remaining reserved capacity of "2". Based on the Weighted RoundRobin algorithm, the server calculates that the resource allocation weight for charging gun G05 is higher than that for charging gun G06. Therefore, the server prioritizes allocating the migrated reserved orders to charging gun G05 and updates the resource allocation field in the corresponding order data.

[0110] In this embodiment, by classifying abnormal warning information based on charging pile identification and counting the number of abnormal warning information and the duration of abnormality, the accuracy of identifying associated abnormal charging piles can be improved; by performing switching processing on the target charging gun under associated abnormal charging piles, the efficiency of order migration under abnormal conditions can be improved; by reallocating the charging resources corresponding to non-abnormal charging guns based on the migrated order data, the utilization rate of charging resources and the efficiency of equipment linkage control in abnormal scenarios can be improved.

[0111] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0112] In one embodiment, a multi-dimensional monitoring charging station management system 10 is provided, which corresponds one-to-one with the multi-dimensional monitoring charging station management method described in the above embodiments. For example... Figure 8 As shown, the multi-dimensional monitoring charging station management system 10 includes a data acquisition module 11, a legality verification module 12, an anomaly early warning module 13, an order generation module 14, and a linkage control module 15. Detailed descriptions of each functional module are as follows: The data acquisition module 11 is used to acquire the charging pile attribute information, the charging gun type information, and the equipment status information of each charging gun in the charging station, and to construct equipment status data based on the charging pile attribute information, the charging gun type information, and the equipment status information.

[0113] The legality verification module 12 is used to obtain the current operating status of each charging gun, and determine the state change result of the corresponding charging gun according to the current operating status of the same charging gun at different time nodes, and perform legality verification on the state change result through preset state transition rules.

[0114] The anomaly warning module 13 is used to generate corresponding anomaly warning information when the result of the state change fails the legality check, or when the duration of the corresponding running state exceeds a preset duration threshold.

[0115] The order generation module 14 is used to generate corresponding order data based on the status change results of each charging gun, and to associate and store the order data with the device status data of the corresponding charging gun.

[0116] The linkage control module 15 is used to perform device linkage control on the corresponding charging gun based on abnormal warning information and corresponding order data, so as to adjust the order acceptance status, reservation status or resource allocation status of the corresponding charging gun.

[0117] It should be noted that the information interaction and execution process between the above systems / modules are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0118] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0119] The descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0120] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0121] In the embodiments provided in this application, it should be understood that the disclosed apparatus / devices and methods can be implemented in other ways. For example, the apparatus / device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0122] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0123] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A charging station management method with multi-dimensional monitoring, characterized in that, include: Obtain the charging pile attribute information, the charging gun type information, and the device status information of each charging gun in the charging station, and construct device status data based on the charging pile attribute information, the charging gun type information, and the device status information. The current operating status of each charging gun is obtained, and the state change result of the corresponding charging gun is determined according to the current operating status of the same charging gun at different time points. The legality of the state change result is verified by a preset state transition rule. When the state change result fails the legality check, or the duration of the corresponding running state exceeds the preset duration threshold, a corresponding abnormal warning message is generated; Based on the status change results of each charging gun, corresponding order data is generated, and the order data is associated with and stored with the device status data of the corresponding charging gun. Based on the abnormal warning information and the corresponding order data, the device linkage control is performed on the corresponding charging gun to adjust the order acceptance status, reservation status or resource allocation status of the corresponding charging gun.

2. The method as described in claim 1, characterized in that, The steps of obtaining the charging pile attribute information, the charging gun type information, and the device status information corresponding to each charging gun within the charging station include: Obtain the operation attribute fields corresponding to each charging pile, and identify the operation attribute of each charging pile based on the operation attribute fields to obtain the charging pile attribute information; Obtain the gun type configuration field corresponding to each charging gun, and identify the gun type type of each charging gun based on the gun type configuration field to obtain the charging gun type information; The system sends status acquisition commands to the control units of each charging gun and receives network connection status data and device operation status data returned by each charging gun to obtain device status information.

3. The method as described in claim 1, characterized in that, The step of constructing device status data based on the charging pile attribute information, the charging gun type information, and the device status information includes: The charging pile attribute information, the charging gun type information, and the device status information are associated according to the device affiliation relationship between the charging station, the charging pile, and the charging gun. The operational attribute identifier, gun type identifier, network connection status data, and device operation status data of each charging gun are integrated into the corresponding device status record. The status records of each device are aggregated according to the corresponding charging pile and charging station identifiers to obtain device status data.

4. The method as described in claim 1, characterized in that, The current operating status includes charging status, discharging status, fault status, reserved status, occupied status, idle status, and offline status.

5. The method as described in claim 1, characterized in that, The step of determining the state change result of the corresponding charging gun based on the current operating state of the same charging gun at different time points includes: Get the current running status of the same charging gun at the current time point and the historical running status at the previous time point; When the current operating state is inconsistent with the historical operating state, the state transition path from the historical operating state to the current operating state is determined as the state change result of the corresponding charging gun.

6. The method as described in claim 1, characterized in that, The preset state transition rules include a set of legal state transition paths corresponding to each running state; The step of validating the state change result using preset state transition rules includes: The state change result is matched with the set of legal state transition paths; If the state change result exists in the set of legal state transition paths, the state change result is determined to have passed the legality check; otherwise, the state change result is determined to have failed the legality check.

7. The method as described in claim 1, characterized in that, The abnormal warning information includes state transition abnormal warning information and state timeout abnormal warning information; The state transition anomaly warning information indicates that the state change result of the corresponding charging gun has not passed the legality verification, and the state timeout anomaly warning information indicates that the duration of the corresponding operating state exceeds the corresponding preset duration threshold.

8. The method as described in claim 1, characterized in that, The step of generating corresponding order data based on the state change results of each charging gun includes: Based on the status change results of each charging gun, generate corresponding order data and obtain the order execution status corresponding to each order data. Obtain the device operation status data and charging business data corresponding to each charging gun, and perform consistency verification on the current operation status of the corresponding charging gun based on the order execution status, the device operation status data and the charging business data; When the current operating status of the corresponding charging gun is inconsistent with the order execution status, or when the charging service data does not meet the operating conditions of the corresponding operating status, corresponding status conflict information is generated. Based on the state conflict information, the current operating state of the corresponding charging gun is corrected, and the corresponding order data is updated based on the corrected operating state.

9. The method as described in claim 1, characterized in that, The step of performing device linkage control on the corresponding charging gun based on the abnormal warning information and the corresponding order data includes: Obtain abnormal warning information corresponding to each charging gun, and classify each abnormal warning information based on the charging pile identifier of the corresponding charging gun; Statistical analysis of the number of abnormal warning messages and the duration of abnormality for each charging gun under the same charging pile; When the number of abnormal warning messages under the same charging pile exceeds the preset number threshold, or the abnormal duration exceeds the preset duration threshold, the corresponding charging pile will be identified as an associated abnormal charging pile. The target charging gun associated with the order data of each charging gun under the associated abnormal charging pile is switched, and the order acceptance or reservation is suspended for the associated abnormal charging pile. Based on the migrated order data, the charging resources corresponding to other non-abnormal charging guns are reallocated.

10. A charging station management system with multi-dimensional monitoring, characterized in that, include: The data acquisition module is used to acquire the charging pile attribute information, the charging gun type information, and the equipment status information of each charging gun in the charging station, and to construct equipment status data based on the charging pile attribute information, the charging gun type information, and the equipment status information. The legality verification module is used to obtain the current operating status of each charging gun, and determine the state change result of the corresponding charging gun according to the current operating status of the same charging gun at different time points, and perform legality verification on the state change result through preset state transition rules. An anomaly warning module is used to generate corresponding anomaly warning information when the state change result fails the legality check or the duration of the corresponding running state exceeds a preset duration threshold. The order generation module is used to generate corresponding order data based on the status change results of each charging gun, and to associate and store the order data with the device status data of the corresponding charging gun. The linkage control module is used to perform device linkage control on the corresponding charging gun based on the abnormal warning information and the corresponding order data, so as to adjust the order acceptance status, reservation status or resource allocation status of the corresponding charging gun.

Images