CN116821798B - Fault early warning server, method and computer storage medium - Google Patents

Abstract

The application relates to the technical field of automobiles, in particular to a fault early warning server, a fault early warning method and a computer storage medium, which are used for realizing efficient and accurate fault early warning. The fault early warning server is used for acquiring fault information of equipment to be detected, and extracting key data for describing a target message type of the fault information from the fault information; determining a target configuration item corresponding to the target message type, wherein the configuration item is used for describing fault elements of the equipment to be detected to be monitored; synthesizing the key data and the configuration data of the acquired target configuration item into data to be detected; and acquiring a target verification rule corresponding to the target message type, and triggering fault early warning if the data to be detected meets the target verification rule. According to the application, different configuration items and verification rules are set for different message types, so that the accuracy and the processing efficiency of fault early warning are improved.

Description

Fault early warning server, method and computer storage medium

Technical Field

The present application relates to the field of automotive technologies, and in particular, to a fault early warning server, a fault early warning method, and a computer storage medium.

Background

At present, when electric automobile charges through filling electric pile, fill electric pile and probably break down, the unusual scheduling condition of order, at this moment, if the unable timely perception of relevant operator will lead to filling electric pile and continue to operate under abnormal state, cause user negative experience and the waste of resource.

In the related art, when the charging pile is abnormal, abnormal information is reported to a server, after the server receives the abnormal information, the server only performs integral rule check once aiming at the abnormal information, and when equipment faults are determined, the related information of the charging pile is acquired and the faults are reported, but the accuracy rate of the fault detection in the mode is not high.

Therefore, how to realize efficient and accurate fault early warning becomes a problem to be solved urgently.

Disclosure of Invention

The embodiment of the application provides a fault early warning server, a fault early warning method and a computer storage medium, which are used for realizing efficient and accurate fault early warning.

The server for fault early warning provided by the embodiment of the application comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor is caused to execute the following steps:

acquiring a fault message of equipment to be detected, and extracting key data from the fault message, wherein the key data is used for describing a target message type of the fault message;

determining a target configuration item corresponding to the target message type, wherein the configuration item is used for describing a fault element of equipment to be detected to be monitored;

Acquiring configuration data of a target configuration item, and synthesizing key data and the configuration data into data to be detected;

And acquiring a target verification rule corresponding to the target message type, and triggering fault early warning if the data to be detected meets the target verification rule.

In some implementations, after the method executed by the processor forms the program, the hardware execution module corresponding to each program functional module may include: the system comprises a data extraction module, a configuration item determination module, a data synthesis module and a fault verification module:

The data extraction module is used for acquiring fault information of the equipment to be detected, extracting key data from the fault information, wherein the key data is used for describing a target message type of the fault information;

The configuration item determining module is used for determining a target configuration item corresponding to the target message type, wherein the configuration item is used for describing fault elements of equipment to be detected to be monitored;

the data synthesis module is used for acquiring the configuration data of the target configuration item and synthesizing the key data and the configuration data into data to be detected;

And the fault checking module is used for acquiring a target checking rule corresponding to the target message type, and triggering fault early warning if the data to be detected meets the target checking rule.

The method for fault early warning provided by the embodiment of the application comprises the following steps:

acquiring a fault message of equipment to be detected, and extracting key data from the fault message, wherein the key data is used for describing a target message type of the fault message;

determining a target configuration item corresponding to the target message type, wherein the configuration item is used for describing a fault element of equipment to be detected to be monitored;

Acquiring configuration data of a target configuration item, and synthesizing key data and the configuration data into data to be detected;

And acquiring a target verification rule corresponding to the target message type, and triggering fault early warning if the data to be detected meets the target verification rule.

A computer program product according to an embodiment of the present application includes a computer program that when executed by a processor implements a method of fault warning as described above.

Alternatively, the computer readable storage medium may be implemented as a computer program product, i.e. embodiments of the present application also provide a computer readable storage medium comprising a computer program which, when executed by a processor, implements a method of fault pre-warning as described in any of the above.

The electronic device provided by the embodiment of the application comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of any one of the fault early warning methods.

The application has the following beneficial effects:

The embodiment of the application provides a fault early warning server, a fault early warning method and a computer program product. In the application, the fault message of the equipment to be detected is not subjected to one-time integral rule check, but key data for describing the type of the target message to which the fault message belongs are firstly extracted from the fault message, and the detection rule is determined based on the associated data. Specifically, by classifying the fault messages of different types, different configuration items and verification rules are set for different message types, so that the message rules are more accurately matched; through multiple screening, the accuracy of fault early warning is improved, and the processing efficiency of fault messages is improved through classification processing.

Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application.

FIG. 1 is an alternative schematic diagram of an application scenario in an embodiment of the present application;

FIG. 2 is a flow chart of a method for fault pre-warning in accordance with an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating a fault early warning process according to an embodiment of the present application;

FIG. 4 is a flow chart illustrating a rule checking procedure according to an embodiment of the present application;

FIG. 5 is a flow chart illustrating a process of fault alerting in accordance with an embodiment of the present application;

FIG. 6 is a schematic diagram of a possible record file according to an embodiment of the present application;

FIG. 7 is a schematic diagram of one possible alert notification in an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a fault pre-warning device according to an embodiment of the present application;

Fig. 9 is a schematic diagram of a hardware component of an electronic device to which an embodiment of the present application is applied;

fig. 10 is a schematic diagram of a hardware composition structure of another electronic device to which the embodiment of the present application is applied.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the technical solutions of the present application, but not all embodiments. All other embodiments, based on the embodiments described in the present document, which can be obtained by a person skilled in the art without any inventive effort, are within the scope of protection of the technical solution of the present application.

Some of the concepts involved in the embodiments of the present application are described below.

Charging pile: the charging pile is a charging device for providing energy supplement for the electric automobile, and the output end of the charging pile is provided with a charging plug (i.e. a charging gun) for charging the electric automobile.

Query Wrapper: the query builder provided by the MyBatis-Plus framework supports chained calls, but requires multiple method calls and object creation, and has relatively low flexibility.

SQL (Structured Query Language), structured query language) expression: refers to an expression consisting of keywords, functions, operators, constants, etc. in the SQL language, which is used to describe various conditions and computations in the SQL query statement. SQL expressions can be used in SELECT, WHERE, HAVING, ORDER BY, etc. statements for screening, computing, and ordering data.

Rule checking: and checking whether the reported fault message accords with a preset check rule, and if so, performing corresponding processing.

MQ (Message Queue): is an asynchronous communication scheme for transferring messages between different applications, and messages may be stored in a queue waiting for a recipient to acquire and process the messages. MQ messages typically have the following characteristics: high reliability, asynchronism, decoupling, etc.

The preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification, it being understood that the preferred embodiments described herein are for illustration and explanation only, and not for limitation of the present application, and embodiments of the present application and features of the embodiments may be combined with each other without conflict.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application. The application scenario diagram includes a plurality of device terminals 110 and a server 120.

In the embodiment of the present application, the device side 110 may be a charging pile, and when detecting that an abnormality occurs in operation, report a fault message to the server 120. The device side 110 may also be a server, which reports a fault message to the server 120 when detecting that an abnormal order exists.

The server 120 is connected to the plurality of device terminals 110, receives fault messages reported by the plurality of device terminals, and analyzes and processes the fault messages: classifying the message through the attributes such as the source of the message, the type of the message and the like, pulling the corresponding context information based on the classification corresponding to the fault message, checking whether the context information meets the rule according to the corresponding check rule, triggering the message alarm under the condition that the rule is met, sending the message suitcase to the associated object, and executing the related processing action under the condition that the processing action is required.

The server 120 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, a content delivery network (Content Delivery Network, CDN), basic cloud computing services such as big data and an artificial intelligent platform.

In an alternative embodiment, the device side 110 and the server 120 may communicate via a communication network.

In an alternative embodiment, the communication network is a wired network or a wireless network.

It should be noted that, the number of the device ends is not limited in practice, and the embodiment of the present application is not particularly limited.

The method for providing fault pre-warning according to the exemplary embodiment of the present application will be described with reference to the accompanying drawings in conjunction with the above-described application scenario, and it should be noted that the above-described application scenario is only shown for the convenience of understanding the spirit and principle of the present application, and the embodiment of the present application is not limited in any way in this respect.

As shown in fig. 2, a flowchart of a method for fault early warning provided in an embodiment of the present application is taken as an example, and a specific implementation process of the method includes steps S201 to S204 as follows:

step S201, a fault message of the equipment to be detected is obtained, and key data is extracted from the fault message.

Wherein the critical data is used to describe the target message type of the fault message.

Optionally, the device to be processed, that is, the device end 110, stores the fault message in the message queue when the device to be detected detects the fault, that is, the message queue stores: at least one fault message of the device to be detected is detected according to the time sequence. The server obtains the fault message of the device to be detected from the message queue of the device to be detected, and in some embodiments, when the server obtains the fault message from the message queue of the device to be detected, the fault message is sequentially obtained according to the arrangement order (i.e. the time sequence) of the fault messages in the message queue, and each time the server obtains a fault message, the fault early warning process described in steps S201-S204 is executed. Message queues can transfer messages between different applications, and by storing messages in the queues, data transmission reliability is improved.

Optionally, the fault message of the device to be detected carries data related to the message type (i.e. the key data), and after the fault message of the device to be detected is obtained, the key data is extracted from the fault message, so that a processing flow corresponding to the target message type is executed subsequently.

It should be noted that, the message type corresponding to the fault message may be set based on the requirement, which is not limited in the embodiment of the present application, and in an optional implementation manner, the message type of the fault message may be divided into a device message, a charging message, an operation and maintenance message, and so on.

In the embodiment of the application, since the server is connected with a plurality of equipment ends, the message body structure of the fault message reported by the equipment to be detected is not uniform, and for facilitating subsequent processing, the key data is integrated into a standard structure after the key data is extracted from the fault message, wherein the standard structure is predefined based on requirements, and the embodiment of the application does not limit the specific structure.

Step S202, determining a target configuration item corresponding to the target message type; the configuration item is used for describing fault elements of equipment to be detected to be monitored.

Optionally, in the embodiment of the present application, a first correspondence between a message type and a configuration item is preset, and a target configuration item corresponding to a target message type is determined based on the first correspondence.

In the embodiment of the application, the message type can comprise one level or a plurality of levels, and when the message type comprises only one level, the target configuration item corresponding to the target message type can be directly determined; when the message type includes a plurality of levels, in each adjacent two levels, the message type of the next level indicates: dividing the message type of the last level to obtain message sub-types; in every two adjacent levels, the configuration item corresponding to the message type of the next level represents: and dividing the configuration item set corresponding to the message type of the last level to obtain a configuration item subset. At this time, the first correspondence relationship includes: correspondence between message types and configuration items at each level.

In the embodiment of the application, the number of the levels included in the message type is not limited, and the message type can be set based on requirements. In an alternative embodiment, the message type includes two levels.

For example, while the primary message type of the fault message may be divided into device messages, charging messages, operation and maintenance messages, the device messages may be further divided into secondary message types (i.e., message sub-types of the primary message type): offline, fault, and hybrid control, charging messages can be further divided into secondary message types: order, billing, etc., the operation message may be further divided into secondary message types: configuration anomalies, operational anomalies, and operation-maintenance messages can be further divided into secondary message types: improper operation, etc.

In practice, different codes may be set for different message types, for example, a device message code of 1, a charging message code of 2, an operation message code of 3, an operation message code of 4, and further, offline, failure, and mixed control codes may be set to 11, 12, and 13. Meanwhile, the specific setting of the configuration items corresponding to the message types of each level is not limited in the embodiment of the application, and the configuration items can be set based on requirements. For example, when the type of the fault message is a charging message, the corresponding configuration item thereof may be set as the occurrence time of the fault, the description of the fault, and the like.

Specifically, when the message type includes a plurality of levels, the step S202 includes steps S2021 to S2022 (not shown in fig. 2):

step S2021: and determining a subset of configuration items corresponding to the next-level message type from the configuration item sets corresponding to the previous-level message types in sequence according to the order of the message types from high to low.

Step S2022: and taking the configuration items in the configuration item subset corresponding to the last-stage message type contained in the target message type as the target configuration items corresponding to the fault message.

By grading the message types and determining the subset of the configuration items step by step, the corresponding configuration items can be accurately determined, the follow-up rule verification and fault warning are facilitated, and the follow-up repeated query of the database due to inaccurate configuration items is avoided.

Step S203, the configuration data of the target configuration item is obtained, and the key data and the configuration data are synthesized into the data to be detected.

Optionally, the acquiring the configuration data of the target configuration item includes at least one step of:

extracting first configuration data of a target configuration item from the fault message;

And inquiring second configuration data of the target configuration item from the prestored equipment information of the equipment to be detected.

Specifically, in the embodiment of the present application, device information related to the device to be detected, for example, location information, identification, etc. of the device to be detected may be stored in advance. In addition, the fault message also carries fault related information, such as fault occurrence time, fault number, fault description and the like. When the configuration data of the target configuration item is acquired, the configuration data of the target configuration item can be acquired from the fault message and/or the equipment information. Configuration data is acquired through various ways, and the sufficiency of the acquired data is ensured.

In the embodiment of the application, the configuration data, namely the information related to the equipment to be detected, is added in the data to be detected, so that the rule check and the alarm message can be conveniently combined and sent for use later, and the resource waste caused by frequently acquiring the related data of the fault when the rule check is executed and the alarm message is generated is avoided.

Step S204, a target check rule corresponding to the target message type is obtained, and if the data to be detected meets the target check rule, fault early warning is triggered.

Optionally, in the embodiment of the present application, a second correspondence between the message type and the verification rule is preset, and based on the second correspondence, a target verification rule corresponding to the target message type is obtained.

In the embodiment of the application, the message type can comprise one level or a plurality of levels, and when the message type only comprises one level, the target check rule corresponding to the target message type can be directly determined; when the message type includes a plurality of levels, in each adjacent two levels, the message type of the next level indicates: dividing the message type of the last level to obtain message sub-types; in every two adjacent levels, the check rule corresponding to the message type of the next level represents: and dividing the check rule set corresponding to the message type of the last level to obtain a check rule subset. At this time, the second correspondence relationship includes: correspondence between message types and inspection rules for each level.

In the embodiment of the application, the specific setting of the verification rules in the (sub) set of the verification rules is not limited, and the setting can be performed based on requirements.

Specifically, when the message type includes a plurality of levels, the step S204 includes steps S2041 to S2042 (not shown in fig. 2):

step S2041, determining a sub-set of check rules corresponding to the next-level message type contained in the target message type from the check rule sets corresponding to the previous-level message types in sequence according to the order of the message types from high to low;

step S2042, using the check rule in the check rule subset corresponding to the last-stage message type included in the target message type as the target check rule corresponding to the fault message.

By grading the message types and determining the check rule subsets step by step, the matched check rules are more accurate, and the accuracy of fault early warning is improved.

In another alternative embodiment, when the message type includes a plurality of levels in the step S202, the first correspondence relationship includes: when the corresponding relation between the message type and the configuration item of each level is set, the second corresponding relation can be set as the relation between the configuration item corresponding to the message type and the checking rule, namely, a corresponding checking rule set is set for the configuration item corresponding to the message type of the last level in advance, after the target configuration item corresponding to the target message type is determined, the checking rule in the checking rule set corresponding to the target configuration item is determined based on the relation between the configuration item and the checking rule, and the checking rule is used as the target checking rule.

Taking table 1 as an example, assume that the message types are classified into a primary message type and a secondary message type (the level corresponding to the secondary message type is lower than the primary message type), and among the target message types of the devices to be detected, the primary message type is device message type 1, the secondary message type is device failure message 11, and a relationship between the configuration items and the inspection rules is set.

In the implementation, firstly, determining a configuration item set 1 corresponding to the device message type 1 from the whole configuration item set based on a first-level message type (device message type 1) contained in a target message type; then, from the configuration item set 1, determining a configuration item subset 2 corresponding to a secondary message type (equipment fault message 11) contained in the target message type, and taking the configuration items in the configuration item subset 2, such as equipment fault recovery monitor 111 and the like, as target configuration items corresponding to the fault message; then, based on the configuration item subset 2, a corresponding check rule set (such as the equipment failure alarm rule 10001 in the following table) is found, and the target check rule is obtained therefrom.

Optionally, in the embodiment of the present application, the target verification rule includes reference values of a plurality of configuration items; and if the actual value of each configuration item in the data to be detected is consistent with the corresponding reference value, determining that the data to be detected meets the target check rule.

Specifically, in the embodiment of the application, the verification rule is constructed by adopting an SQL expression, and compared with a Query Wrapper used in the related technology, the SQL expression is a more mature verification mode, is easier to operate, is easier to understand in language, and can ensure the stability of the system; and the verification rules constructed by the SQL expression are configured in the database, so that the verification rules can be modified by modifying the database, flexible configuration is realized, the modification of codes is reduced, and meanwhile, the verification rules can be directly increased or decreased through the database. The current SQL check supports multiple expression processing such as =, and, in, like, etc.

Optionally, before determining the target verification rule based on the second correspondence and performing dynamic verification, the embodiment of the present application further needs to perform static verification on the fault message, specifically, inquire a message of a target message type from historical report messages of the device to be detected, if the message of the target message type is inquired, and if the number of the inquired messages reaches a set threshold, determining that the verification passes, and executing a step of subsequently determining the target verification rule; if the condition is not met, determining that the verification is not passed, and not executing the subsequent rule verification step, namely ending the fault early warning. Furthermore, in the embodiment of the application, a time range corresponding to the historical report message of the query can also be set, for example, the query is set in the historical report message within 24 hours from the current time.

It should be noted that, in the embodiment of the present application, the value of the set threshold is not limited, and may be set based on the requirement, for example, set to 3 times.

Optionally, when the fault early warning is triggered, at least one of the following steps is executed:

Generating a record file for recording the fault condition of the equipment to be detected based on the data to be detected, and storing the record file; specifically, the specific data recorded in the record file is not limited in the embodiment of the present application, and may be configured based on requirements, for example, information such as a type of a message recorded with a fault in the record file, a target verification rule, a location and a number of a device to be detected, and description of the fault is set.

Generating an alarm notification based on the data to be detected, and sending the alarm notification to an associated object of the equipment to be detected; the related objects are not limited to the user, the operator and the manager of the device to be detected, and can be configured based on requirements. The specific data recorded in the alarm notification and the sending mode are not limited, and the embodiment of the application can be configured based on requirements, for example, the position and the number of the equipment to be detected, the target verification rule, the occurrence time of the fault, the description of the fault and other information are recorded in the alarm notification; the sending mode of the alarm notification is set to be application software, a short message, a telephone and the like.

Determining a processing type corresponding to the fault type, and executing processing operation corresponding to the processing type; specifically, the above processing types include, but are not limited to, no processing, parameter adjustment (i.e., adjustment of an operation parameter of the device to be detected), or ending operation (i.e., ending operation of the device to be detected), and the like, and the processing operations corresponding to the parameter adjustment include, but are not limited to, issuing a work order, reducing current, reducing power, restarting the device, and the like. Aiming at faults, the embodiment of the application not only has the discovery capability, but also has the processing capability; when the fault early warning is triggered, corresponding processing operation is executed, so that the current business requirement is met, and the whole processing process is more complete.

According to the method, by classifying the fault messages of different types, different configuration items and verification rules are set for different message types, so that the message rules are more accurately matched; through multiple screening, the accuracy of fault early warning is improved, and the processing efficiency of fault messages is improved through classification processing.

The following details the foregoing fault early warning process by a specific example with reference to fig. 3, where the fault early warning process specifically includes:

And a message reporting module: other service fault messages and fault messages of equipment (such as a charging pile) to be monitored are reported to a monitoring system (namely a server in the embodiment of the application) in an MQ mode.

In a specific embodiment, the device to be detected is a charging pile, and the reported fault message specifically comprises a fault Code of 5028, a fault state fault Stastus of 0, a charging gun identifier gun ID of 3 and a timestamp: "25377", message Type MESSAGE TYPE: "charge Stub", socket Type: "IOT", etc.

Message distribution module: the information distribution module in the monitoring platform determines the corresponding information type based on the received fault information (namely, extracts key data in the fault information), carries out information format arrangement, integrates the extracted data into an information body which can be processed by the monitoring system, distributes the information body to different alarm processors based on the information type, for example, the information related to equipment is sent to the equipment processor, and the information distributed to the processing is subjected to rule processing according to the parameter related to the equipment; a charge-related message may be sent to a charge processor or the like.

In a specific embodiment, the message body ALERT MESSAGE obtained after the message format arrangement specifically includes: device ID: "10021100002573", fault Code: "5028", fault state fault Stastus: "0", charging gun ID: "3", message Type (device message) msg Type: "1", message subtype (device fault message) msg Sub Type: "12".

And a data aggregation module: and determining a subset of configuration items corresponding to the next-level message type contained in the target message type from a set of configuration items corresponding to the previous-level message type in sequence according to the order from high to low of the message type corresponding to the fault message, determining a precise configuration item through multi-level screening until the last-level message type is inquired, searching for a context message to acquire corresponding configuration data, and aggregating the corresponding configuration data with key data to obtain data to be detected so as to prepare for the verification of the follow-up rules. For example, if the device to be detected reports a failure message of a charging anomaly, the module integrates configuration data extracted from the failure message with configuration data extracted from device information of the device to be detected, and in some embodiments, the device information of the device to be detected may include all charging anomaly messages recently received by the charging processor.

In a specific embodiment, a number of information related to the device, such as station Info (including location information of the device to be detected, device identification, etc.), fault description fault Desc, "vehicle control guidance fault in charging (dc pile use only)" etc. can be added through data aggregation, so as to be used in combination with subsequent rule check and alarm messages.

Rule matching module: the method comprises the steps of checking rule matching and checking rule acquisition, specifically, a rule matching module searches a matched checking rule set according to the message type, and acquires configuration information of the checking rules in the checking rule set.

In a specific embodiment, the rule matching module may obtain a check rule corresponding to the fault message, where the check rule may be one or more, for example, the fault message matches two check rules, a rule Name and a rule expression rule Exp may be obtained from the rule configuration, and at the same time, the check rule may be configured with a corresponding alarm rule, for example, an alarm message sending template MSG TEMPLATE, an alarm message group Id and so on.

Rule checking module: in the implementation, the rule checking module performs initial static check (i.e. code encoding strong check) firstly, and performs dynamic check after the static check passes, i.e. check based on a preconfigured SQL expression (i.e. target check rule), and after the static check passes, the subsequent alarm processing is triggered by performing combined matching check on the SQL expression and data to be checked.

In a specific embodiment, the rule of static verification may be: the condition is satisfied if three records are found within 24 hours in the database.

The dynamic verification rule may be: the search state is the station state info.status is online (i.e. 1), and the fault code is any one of 5028, 5052, 5054, 5000; if the station info.status=1 and the alert message.fault code=5028 can be found in the device to be detected, it is determined that the check rule is satisfied, the check is passed, and the subsequent alarm processing is triggered.

In the embodiment of the present application, when a plurality of verification rules are matched by the rule matching module, verification is performed sequentially based on each verification rule, and specific steps are as shown in fig. 4, including:

Step S401, carrying out static verification on data to be verified, and determining whether the verification is passed; if yes, executing step S402, and if no, executing step S405;

step S402, dynamically checking the data to be checked based on the current checking rule, determining whether the checking is passed, if yes, executing step S403, and if no, executing step S405;

Step S403, triggering an alarm;

Step S404, determining whether the current check rule is the last item in the matched multiple check rules, if so, executing step S405, otherwise, executing step S406;

step S405, ending the process;

Step S406, the next check rule in the plurality of check rules is used as the current check rule, and the step S401 is executed in a return mode.

And an alarm processing module: as shown in FIG. 5, the alert process includes recording, alerting, and action processing. Wherein:

Recording means: a record file for recording the fault condition of the device to be detected is generated based on the data to be detected, and stored, for example, record reservation is made on the relevant problems in the energy operation platform. Fig. 6 is a schematic diagram of a possible record file according to an embodiment of the present application, where, as shown in fig. 6, the record file may include: the method comprises the steps of message identification of fault messages, message types, check rules, message content (such as fault codes, fault descriptions, equipment identification of equipment to be detected, charging gun identification and occurrence time of faults), position information of the equipment to be detected (such as a station name) to which the equipment to be detected belongs, parking space numbers and message body types (such as equipment or orders and the like).

The alarm means: generating an alarm notification based on the data to be detected, and sending the alarm notification to an associated object of the equipment to be detected, so that the associated object can execute corresponding processing after receiving the alarm notification. Fig. 7 is a schematic diagram of a possible alarm notification provided by an embodiment of the present application, where, as shown in fig. 7, the alarm notification may include location information (such as a station name to which the device belongs) of the device to be detected, a fault code, a fault description, a device identifier of the device to be detected, a charging gun identifier, an occurrence time of a fault, a parking space number, and the like.

The action processing means: and determining a processing type corresponding to the fault type, and executing processing operation corresponding to the processing type, for example, directly closing the order of the order being charged.

Based on the same inventive concept, the server for fault early warning provided by the embodiment of the application comprises: a processor and a memory; wherein the memory is connected with the processor and is used for storing a computer program; the processor is configured to perform the following method:

Acquiring a fault message of equipment to be detected, and extracting key data from the fault message, wherein the key data is used for describing a target message type of the fault message;

Determining a target configuration item corresponding to a target message type, wherein the configuration item is used for describing a fault element of the equipment to be detected to be monitored;

Acquiring configuration data of the target configuration item, and synthesizing the key data and the configuration data into data to be detected;

and acquiring a target check rule corresponding to the target message type, and triggering fault early warning if the data to be detected meets the target check rule.

In some implementations, after the method executed by the processor forms the program, the hardware execution module corresponding to each program functional module may include: the system comprises a data extraction module, a configuration item determination module, a data synthesis module and a fault verification module.

As shown in fig. 8, the composition and structure of a fault pre-warning device 800 according to an embodiment of the present application are shown, where the fault pre-warning device includes a data extraction module 801, a configuration item determination module 802, a data synthesis module 803, and a fault verification module 804, where:

the data extraction module 801 is configured to obtain a fault message of a device to be detected, and extract key data from the fault message, where the key data is used to describe a target message type of the fault message;

A configuration item determining module 802, configured to determine a target configuration item corresponding to a target message type, where the configuration item is used to describe a fault element of a device to be detected to be monitored;

the data synthesis module 803 is configured to obtain configuration data of the target configuration item, and synthesize the key data and the configuration data into data to be detected;

The fault checking module 804 is configured to obtain a target checking rule corresponding to the target message type, and trigger fault early warning if the data to be detected meets the target checking rule.

Optionally, the message type includes a plurality of levels, and in each two adjacent levels, the message type of the next level indicates: dividing the message type of the last level to obtain message sub-types; in every two adjacent levels, the configuration item corresponding to the message type of the next level represents: dividing a configuration item set corresponding to the message type of the previous level to obtain a configuration item subset;

the configuration item determining module 802 is specifically configured to:

Sequentially determining a subset of configuration items corresponding to the next-level message type from the configuration item sets corresponding to the previous-level message types according to the order of the message types from high to low;

and taking the configuration items in the configuration item subset corresponding to the last-stage message type contained in the target message type as the target configuration items corresponding to the fault message.

Optionally, in each two adjacent levels, the check rule corresponding to the message type of the next level indicates: dividing a check rule set corresponding to the message type of the previous level to obtain a check rule subset;

the fault checking module 804 is specifically configured to:

Sequentially determining a check rule subset corresponding to the next-level message type contained in the target message type from check rule sets corresponding to the previous-level message types according to the order of the message types from high to low;

and taking the check rule in the corresponding check rule subset of the last-stage message type contained in the target message type as the target check rule corresponding to the fault message.

Optionally, the target verification rule includes reference values of a plurality of configuration items; and if the actual value of each configuration item in the data to be detected is consistent with the corresponding reference value, determining that the data to be detected meets the target check rule.

Optionally, the apparatus 800 further includes a static verification module, where before the fault verification module 804 is configured to determine the target verification rule corresponding to the target message type, the static verification module is configured to:

And determining that the information of the target information type is inquired in the historical report information of the equipment to be detected, and the number of the inquired information reaches a set threshold value.

Optionally, the data synthesis module 803 obtains configuration data of the target configuration item, including at least one of the following steps:

Extracting first configuration data of the target configuration item from the fault message;

and inquiring second configuration data of the target configuration item from the prestored equipment information of the equipment to be detected.

Optionally, when the fault verification module 804 triggers a fault pre-warning, at least one of the following steps is performed:

Generating a record file for recording the fault condition of the equipment to be detected based on the data to be detected, and storing the record file;

generating an alarm notification based on the data to be detected, and sending the alarm notification to an associated object of the equipment to be detected;

and determining a processing type corresponding to the fault type, and executing processing operation corresponding to the processing type.

Optionally, the data extraction module 801 is specifically configured to:

Sequentially obtaining fault messages of the equipment to be detected from a message queue of the equipment to be detected; wherein, the message queue stores: and detecting at least one fault message of the equipment to be detected according to the time sequence.

For convenience of description, the above parts are described as being functionally divided into modules (or units) respectively. Of course, the functions of each module (or unit) may be implemented in the same piece or pieces of software or hardware when implementing the present application.

Those skilled in the art will appreciate that the various aspects of the application may be implemented as a system, method, or program product. Accordingly, aspects of the application may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.

The embodiment of the application also provides electronic equipment based on the same conception as the embodiment of the method. In one embodiment, the electronic device may be a server, such as the server shown in FIG. 1. In this embodiment, the electronic device may be configured as shown in fig. 9, including a memory 901, a communication module 903, and one or more processors 902.

A memory 901 for storing a computer program executed by the processor 902. The memory 901 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, a program required for running an instant communication function, and the like; the storage data area can store various instant messaging information, operation instruction sets and the like.

The memory 901 may be a volatile memory (RAM) such as a random-access memory (RAM); the memory 901 may also be a nonvolatile memory (non-volatile memory), such as a read-only memory, a flash memory (flash memory), a hard disk (HARD DISK DRIVE, HDD) or a solid state disk (solid-state disk) (STATE DRIVE, SSD); or memory 901, is any other medium that can be used to carry or store a desired computer program in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory 901 may be a combination of the above memories.

The processor 902 may include one or more central processing units (central processing unit, CPUs) or digital processing units, or the like. And a processor 902, configured to implement the fault early warning method when calling the computer program stored in the memory 901.

The communication module 903 is used for communicating with a terminal device and other servers.

The specific connection medium between the memory 901, the communication module 903, and the processor 902 is not limited in the embodiment of the present application. The embodiment of the present application is shown in fig. 9, where the memory 901 and the processor 902 are connected by a bus 904, where the bus 904 is depicted in bold in fig. 9, and the connection between other components is merely illustrative, and not limiting. The bus 904 may be divided into an address bus, a data bus, a control bus, and the like. For ease of description, only one thick line is depicted in fig. 9, but only one bus or one type of bus is not depicted.

The memory 901 stores a computer storage medium in which computer executable instructions are stored for implementing the method for fault warning according to the embodiment of the present application. The processor 902 is configured to perform the method of fault pre-warning described above, as shown in fig. 2.

A computing device 1000 according to such an embodiment of the application is described below with reference to fig. 10. The computing device 1000 of fig. 10 is only one example and should not be taken as limiting the functionality and scope of use of embodiments of the present application.

As shown in fig. 10, the computing device 1000 is in the form of a general purpose computing device. Components of computing device 1000 may include, but are not limited to: the at least one processing unit 1001, the at least one memory unit 1002, a bus 1003 connecting the different system components (including the memory unit 1002 and the processing unit 1001).

Bus 1003 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, and a local bus using any of a variety of bus architectures.

The storage unit 1002 may include a readable medium in the form of volatile memory, such as Random Access Memory (RAM) 1021 and/or cache memory 1022, and may further include Read Only Memory (ROM) 1023.

Storage unit 1002 may also include program/utility 1025 having a set (at least one) of program modules 1024, such program modules 1024 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

The computing device 1000 may also communicate with one or more external devices 1004 (e.g., keyboard, pointing device, etc.), one or more devices that enable a user to interact with the computing device 1000, and/or any devices (e.g., routers, modems, etc.) that enable the computing device 1000 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1005. Moreover, computing device 1000 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, for example, the Internet, through network adapter 1006. As shown in fig. 10, the network adapter 1006 communicates with other modules for the computing device 1000 over the bus 1003. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computing device 1000, including, but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

Embodiments of the present application also provide a computer program product, where the methods of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product described above includes one or more computer programs or instructions. The above-described processes or functions of the present application are performed in whole or in part when the above-described computer programs or instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user device, a core network device, an OAM, or other programmable apparatus.

The computer readable storage medium may be implemented as a computer program product, i.e. embodiments of the application also provide a computer readable storage medium comprising a computer program which, when executed by a processor, implements a method of fault warning as described in any of the above.

The computer program or instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center by wired or wireless means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium such as a floppy disk, hard disk, magnetic tape; but also optical media such as digital video discs; but also semiconductor media such as solid state disks. The computer readable storage medium may be volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage medium.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having a computer-usable computer program embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program commands may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the commands executed by the processor of the computer or other programmable data processing apparatus produce means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program commands may also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the commands stored in the computer readable memory produce an article of manufacture including command means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims (9)

1. A server for fault warning, the server comprising a processor and a memory, wherein the memory stores a computer program which, when executed by the processor, causes the processor to perform the steps of:

Acquiring a fault message of equipment to be detected, and extracting key data from the fault message, wherein the key data is used for describing a target message type of the fault message; the equipment to be detected is a charging pile;

Determining a target configuration item corresponding to the target message type, wherein the configuration item is used for describing a fault element of the equipment to be detected to be monitored;

Acquiring configuration data of the target configuration item, and synthesizing the key data and the configuration data into data to be detected; wherein the obtaining the configuration data of the target configuration item comprises at least one of the following steps: extracting first configuration data of the target configuration item from the fault message, wherein the fault message comprises occurrence time of a fault, a fault number and a fault description; inquiring second configuration data of the target configuration item from prestored equipment information of the equipment to be detected, wherein the equipment information comprises position information and identification of the equipment to be detected;

acquiring a target verification rule corresponding to the target message type, and triggering fault early warning if the data to be detected meets the target verification rule;

Wherein the obtaining the configuration data of the target configuration item includes: determining a target configuration item corresponding to the target message type based on a first corresponding relation between the preset message type and the configuration item of each level;

The obtaining the target verification rule corresponding to the target message type comprises the following steps: and acquiring a target verification rule corresponding to the target message type based on a second corresponding relation between the preset message type of each level and the verification rule.

2. The server of claim 1, wherein in each adjacent two levels, the message type of the next level represents: dividing the message type of the last level to obtain message sub-types; in every two adjacent levels, the configuration item corresponding to the message type of the next level represents: dividing a configuration item set corresponding to the message type of the previous level to obtain a configuration item subset;

The processor is specifically configured to:

Sequentially determining a subset of configuration items corresponding to the next-level message type from the configuration item sets corresponding to the previous-level message types according to the order of the message types from high to low;

And taking the configuration items in the configuration item subset corresponding to the last-stage message type contained in the target message type as the target configuration items corresponding to the fault message.

3. The server of claim 1, wherein in each adjacent two levels, the message type of the next level represents: dividing the message type of the last level to obtain message sub-types; in every two adjacent levels, the check rule corresponding to the message type of the next level represents: dividing a check rule set corresponding to the message type of the previous level to obtain a check rule subset;

The processor is specifically configured to:

sequentially determining a check rule subset corresponding to the next-level message type contained in the target message type from check rule sets corresponding to the previous-level message types according to the order of the message types from high to low;

And taking the check rule in the check rule subset corresponding to the last-stage message type contained in the target message type as a target check rule corresponding to the fault message.

4. The server of claim 1, wherein the target verification rule includes reference values for a plurality of configuration items;

And if the actual value of each configuration item in the data to be detected is consistent with the corresponding reference value, determining that the data to be detected meets the target check rule.

5. The server of claim 1, wherein prior to the determining a target check rule corresponding to the target message type, the processor is further to:

and determining that the information of the target information type is inquired in the historical report information of the equipment to be detected, and the number of the inquired information reaches a set threshold value.

6. The server according to any one of claims 1 to 5, wherein when the processor triggers a fault pre-warning, at least one of the following steps is performed:

generating a record file for recording the fault condition of the equipment to be detected based on the data to be detected, and storing the record file;

generating an alarm notification based on the data to be detected, and sending the alarm notification to an associated object of the equipment to be detected;

And determining a processing type corresponding to the fault type, and executing processing operation corresponding to the processing type.

7. The server according to any one of claims 1 to 5, wherein the processor is specifically configured to:

sequentially obtaining fault messages of the equipment to be detected from a message queue of the equipment to be detected; wherein, the message queue stores: at least one fault message of the device to be detected is detected according to time sequence.

8. A method of fault warning, the method comprising:

Acquiring a fault message of equipment to be detected, and extracting key data from the fault message, wherein the key data is used for describing a target message type of the fault message; the equipment to be detected is a charging pile;

determining a target configuration item corresponding to the target message type; the configuration item is used for describing fault elements of the equipment to be detected to be monitored;

Acquiring configuration data of the target configuration item, and synthesizing the key data and the configuration data into data to be detected; wherein the obtaining the configuration data of the target configuration item comprises at least one of the following steps: extracting first configuration data of the target configuration item from the fault message, wherein the fault message comprises occurrence time of a fault, a fault number and a fault description; inquiring second configuration data of the target configuration item from prestored equipment information of the equipment to be detected, wherein the equipment information comprises position information and identification of the equipment to be detected;

acquiring a target verification rule corresponding to the target message type, and triggering fault early warning if the data to be detected meets the target verification rule;

Wherein the obtaining the configuration data of the target configuration item includes: determining a target configuration item corresponding to the target message type based on a first corresponding relation between the preset message type and the configuration item of each level;

The obtaining the target verification rule corresponding to the target message type comprises the following steps: and acquiring a target verification rule corresponding to the target message type based on a second corresponding relation between the preset message type of each level and the verification rule.

9. A computer program product comprising a computer program, characterized in that the method according to claim 8 is implemented when the computer program is executed by a processor.