Equipment self-repairing method, device and system, equipment and readable storage medium

Abstract

The invention provides an equipment self-repairing method, device and system, equipment and a readable storage medium, which are applied to the technical field of self-repairing, and the method comprises the following steps: receiving data information of charging equipment reported after operation and maintenance equipment collects from a maintenance station; and screening data with software information from the data information according to a preset screening method to obtain a charging message of the charging equipment. And inputting the charging message into a fault prediction model, and predicting fault data of the charging equipment. Based on the fault data, determining a repair task matched with the fault data; the repairing task comprises a repairing strategy and repairing starting time. And repairing the charging equipment corresponding to the charging message by using the repairing strategy at the repairing starting time, so that the self-repairing efficiency of the charging pile equipment can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of device self-repair, and in particular to a device self-repair method and apparatus, system, device, and readable storage medium. Background Art

[0002] At present, the operation and maintenance of charging piles can be divided into two aspects: operation and maintenance. That is, it is necessary to ensure the normal operation of the charging piles and to regularly maintain the charging piles. In terms of charging pile maintenance, with the vigorous development of the electric vehicle charging industry, charging piles are encountering more and more problems. When the charging pile is damaged, the operation and maintenance personnel are required to inspect and identify the cause of the charging pile failure, which increases the operation and maintenance cost of the charging pile. At the same time, even if the charging pile may not be damaged, the operation and maintenance personnel are required to be on site, which affects the operation and maintenance efficiency of the charging pile.

[0003] Therefore, there is an urgent need for a device self-repair method and apparatus, system, device, and readable storage medium to improve the self-repair efficiency of charging pile equipment. Summary of the invention

[0004] The purpose of this application is to provide a device self-repair method and apparatus, system, device, and readable storage medium to improve the self-repair efficiency of charging pile equipment.

[0005] In a first aspect, an embodiment of the present application provides a method for self-repairing a device, the method comprising: receiving data information of a charging device collected and reported by an operation and maintenance device from a maintenance station. According to a preset screening method, data with software information is filtered out from the data information to obtain a charging message of the charging device. The charging message is input into a fault prediction model to predict the fault data of the charging device. Based on the fault data, a repair task matching the fault data is determined. The repair task includes a repair strategy and a start repair time. At the start repair time, the charging device corresponding to the charging message is repaired using the repair strategy.

[0006] The device self-repair method provided in the embodiment of the present application can filter out charging messages from the data information after receiving the data information reported by the operation and maintenance equipment, and determine the repair task matching the charging message based on the charging message. By automatically creating repair tasks and executing corresponding repair strategies, it is convenient to handle faults caused by non-hardware damage on site, improve equipment availability, improve operation and maintenance work efficiency, and realize preliminary automated operation and maintenance.

[0007] In a possible implementation method, the training process of the fault prediction model includes: obtaining a historical fault data set and a historical charging message set of the charging device; the historical fault data set in the historical fault data set has a one-to-one correspondence with the historical charging messages in the historical charging message set; randomly forming a training set using any historical fault data in the historical fault data set and the historical charging messages corresponding to the historical fault data; for any historical fault data in the training set and the historical charging messages corresponding to the historical fault data, determining the historical fault characteristics according to the historical fault data, and determining the historical message characteristics according to the historical charging messages; the historical fault characteristics include the historical fault source type, the historical fault type and the historical fault cause; the historical message characteristics are used to represent the abnormal change rate of the historical fault data in a preset time period; the historical message characteristics include the historical fault time, the historical charging current and the historical battery temperature; according to the historical fault characteristics and the historical message characteristics, determining the fault prediction model; the fault prediction model is used to represent the one-to-one correspondence between the historical fault data and the historical charging messages.

[0008] A possible implementation method is that the device self-repair method provided in the embodiment of the present application also includes: randomly forming a test set using any historical fault data in the historical fault data set and historical charging messages corresponding to the historical fault data one by one; evaluating and adjusting the fault prediction model using any historical fault data in the test set and historical charging messages corresponding to the historical fault data, and updating the fault prediction model.

[0009] In a possible implementation, the charging message includes an alarm code. Based on the fault data, determining a repair task that matches the fault information includes: determining, according to the alarm code, a charging pile corresponding to the alarm code. Obtaining at least one control device corresponding to the charging pile. Obtaining version information of the charging pile and version information of at least one control device. Determining a repair task that matches the fault data based on the version information of the charging pile and the version information of at least one control device.

[0010] In a possible implementation, the repair task includes a first repair action and a second repair action. The repair task is determined based on the version information of the charging pile and the version information of at least one control device, including: determining the device series and product type to which the charging pile belongs based on the version information of the charging pile. Determine the execution condition and the start repair time corresponding to the repair task based on the device series and product type of the charging pile. When the version information of all control devices in at least one control device meets the execution condition, the first repair action is performed on all control devices at the start repair time. When the first control device meets the execution condition and other control devices other than the first control device in at least one control device do not meet the execution condition, the second repair action is performed on the first control device at the start repair time. The first control device is any control device among the at least one control device.

[0011] In a possible implementation manner, the execution condition includes: the version corresponding to the version information is lower than the preset version.

[0012] In a possible implementation, the device self-repair method provided in the embodiment of the present application further includes: determining a basic repair time and a repair time offset of the repair task according to the repair action in the repair task, and adding the basic repair time and the repair time offset to determine the start time of the repair.

[0013] A possible implementation method is to repair the charging pile using a repair strategy, including: obtaining a task cache of the charging pile. The task cache includes historical repair strategies of the charging pile within a preset time period. When there is no repair strategy in the historical repair strategies, or when there is a repair strategy in the historical repair strategies and the charging pile is successfully repaired after executing the repair strategy, the repair strategy is used to repair the charging pile.

[0014] A possible implementation manner is to filter out the charging message from the data information, including: filtering out the data with software information from the data information according to a preset filtering method to obtain the charging message.

[0015] In a possible implementation, the preset screening methods include: regular expression matching, keyword screening, and structured query language.

[0016] In a second aspect, an embodiment of the present application provides a device self-repairing apparatus, which includes: a receiving module, a screening module, a processing module, and a repairing module.

[0017] Among them, the receiving module is used to receive the data information of the charging equipment collected and reported by the operation and maintenance equipment from the maintenance station.

[0018] The screening module is used to screen out the data with software information from the data information according to a preset screening method to obtain the charging message of the charging device.

[0019] A processing module is used to determine a repair task matching the charging message based on the charging message; the repair task includes a repair strategy and a start time for repairing.

[0020] The repair module is used to repair the charging device corresponding to the charging message by using the repair strategy at the start repair time.

[0021] In a third aspect, the present application provides a device self-repairing device, which has the function of implementing the device self-repairing method of the first aspect or any possible implementation method. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0022] In a fourth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer can execute the device self-repair method of the first aspect or any possible implementation method.

[0023] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the device self-repair method of the first aspect or any possible implementation manner.

[0024] Among them, the technical effects brought about by any design method in the second to fifth aspects can refer to the technical effects brought about by different possible implementation methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the specific implementation methods of the present application or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0026] Figure 1 A schematic diagram of the structure of a device self-repair device provided in an embodiment of the present application; Figure 2 A schematic diagram of a structure of a device self-repair system provided in an embodiment of the present application; Figure 3 A schematic diagram of a process flow of a device self-repair method provided in an embodiment of the present application; Figure 4 A specific example diagram of a device self-repair method provided in an embodiment of the present application; Figure 5 Another specific example diagram of a device self-repair method provided in an embodiment of the present application; Figure 6 Another schematic diagram of a process flow of a device self-repair method provided in an embodiment of the present application; Figure 7 A structural schematic diagram of a device self-repairing device provided in an embodiment of the present application; Figure 8 Another structural schematic diagram of a device self-repair system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0028] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0029] At present, in terms of charging pile maintenance, with the booming development of the electric vehicle charging industry, charging piles are encountering more and more problems. When a charging pile is damaged, operation and maintenance personnel are required to inspect and identify the cause of the charging pile failure, which increases the operation and maintenance costs of the charging pile. At the same time, even if the charging pile may not be damaged, operation and maintenance personnel are still required to be on site, which affects the operation and maintenance efficiency of the charging pile.

[0030] Based on this, an embodiment of the present application provides a method for self-repair of equipment, which includes: receiving data information of charging equipment collected and reported by operation and maintenance equipment from a maintenance station. According to a preset screening method, data with software information is filtered out from the data information to obtain a charging message of the charging equipment. The charging message is input into a fault prediction model to predict the fault data of the charging equipment. Based on the fault data, a repair task matching the number of faults is determined. The repair task includes a repair strategy and a start repair time. At the start repair time, the charging device corresponding to the charging message is repaired using the repair strategy.

[0031] The device self-repair method provided in the embodiment of the present application can filter out data with software information from the data information after receiving the data information reported by the operation and maintenance equipment after collecting from the maintenance station, obtain the charging message of the charging equipment, and determine the repair task matching the charging message based on the charging message. By automatically creating a repair task and executing the corresponding repair strategy at the start of the repair time, it is convenient to handle faults caused by non-hardware damage on site, improve equipment availability, improve operation and maintenance work efficiency, and realize preliminary automated operation and maintenance.

[0032] The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0033] On the one hand, a device self-repair method provided in an embodiment of the present application can be executed by a device self-repair device. Figure 1As shown, the device self-repairing device 100 may include: a processor 101 and a memory 102 . The memory 102 may be a memory in the processor 101 .

[0034] The processor 101 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0035] The memory 102 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct rambus RAM (DR RAM) or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but not limited thereto. The memory can be independent and connected to the processor 101 via a communication line. The memory 102 can also be integrated with the processor 101.

[0036] The memory 102 stores computer executable instructions for implementing the solution of the present application, and is executed under the control of the processor 101. The processor 101 is used to execute the computer executable instructions stored in the memory 102, thereby implementing the device self-repair method provided in the following embodiments of the present application.

[0037] On the one hand, the device self-repair method provided in the embodiment of the present application can be executed by a device self-repair system. Figure 2 As shown, the device self-repair system 200 may include: a device self-repair device 100 , an operation and maintenance device 201 , a first control device 202 , a second control device 203 , and a charging pile 204 .

[0038] The device self-repairing device 100 is used to filter out charging messages from the data information after the operation and maintenance device 201 reports the data information, determine the repair task matching the charging message based on the charging message, and execute the repair task.

[0039] The operation and maintenance device 201 may be a central control unit (CCU) for coordinating and managing various functions of the charging pile, including, for example, communication management, charging control, safety monitoring, billing and payment, status display and user interaction, data recording and uploading, etc.

[0040] Exemplarily, the operation and maintenance device 201 can be used to record data information of the first control device 202 or the stack control device 203 or the charging pile 204 , and report the data information to the equipment self-repairing device 100 .

[0041] The first control device 202 may be a protocol control device (PCU), which is responsible for parsing and executing the charging communication protocol to ensure that the charging pile can correctly interact with the operation and maintenance device 201 according to the corresponding charging communication protocol. For example, it may include communication protocol parsing, instruction execution, safety protection, status feedback, etc. One first control device 202 may correspond to one charging pile 204.

[0042] The second control device 203 may be a power distribution unit (PDU) for providing power management and protection for the charging pile 204. For example, it may be used to perform power distribution, current detection and protection, power factor correction, isolation and filtering, etc. One second control device 203 may correspond to one or more charging piles 204.

[0043] The charging station 204 is used to provide energy for the electric vehicle.

[0044] In one possible implementation method, the equipment self-repair system can be deployed in the operation and maintenance equipment 201, the first control device 202, the second control device 203, and the charging pile 204 that are on the white list in the charging station. The operation and maintenance equipment 201, the first control device 202, the second control device 203, and the charging pile 204 can be added to the white list by adding a mark that supports equipment self-repair in the data information. After the equipment self-repair device 100 receives the data information in the white list, it executes the equipment self-repair method provided in the embodiment of the present application.

[0045] It should be noted that the present application does not limit the number of the device self-repair device 100, the operation and maintenance device 201, the first control device 202, the second control device 203, and the charging pile 204. At the same time, the present application does not limit the direct connection method of the device self-repair device 100, the operation and maintenance device 201, the first control device 202, the second control device 203, and the charging pile 204. Figure 2 The connection method shown is only an illustration and is not intended to limit the specific scenario of the device self-repair system.

[0046] On the one hand, the embodiment of the present application provides a device self-repair method, which can be Figure 2 The device self-repair system 200 shown in FIG. Figure 1 The device shown is performed by the self-repair device 100. Figure 3 As shown, the method may include: S301, receiving data information of charging equipment collected and reported by operation and maintenance equipment from a maintenance station.

[0047] The data information of the charging equipment is composed of basic data. The basic data may be basic data of a maintenance station and basic data of the charging equipment. The maintenance station may be, for example, a charging station.

[0048] In one possible implementation, the equipment self-repair device first configures basic data, which includes product series data, equipment fault configuration list, equipment software version configuration, equipment fault repair configuration, and site equipment configuration.

[0049] Among them, product series data includes device type, product type, device series data, etc. The equipment fault configuration list includes device type, fault type, fault source type, fault cause, etc. The equipment software version configuration includes device type, product series, device series, version code, etc. The equipment fault repair configuration includes repair rules, etc. The station equipment configuration includes the charging station name, access status, centralized control address, CAN address, device type, device SN, device status, operation status, etc. of the charging station to which the charging pile belongs.

[0050] The operation and maintenance task can control the charging station and any equipment in the charging station to enable or disable the device self-repair function by maintaining the station whitelist. The operation and maintenance task can be collected using kettle and updated once a day. The charging station can be added, modified, deleted, and other operations can be performed daily.

[0051] Specifically, Figure 4 As shown, the operation and maintenance personnel can also use the equipment self-repair system to perform equipment fault subscription, charging order subscription, fault rule definition, task action construction, task action scheduling, task action execution, status / result monitoring, operation and maintenance work order query, etc. The operation and maintenance personnel can use the equipment self-repair system to perform equipment restart, upgrade confirmation, software upgrade, electronic unlocking, fault clearance, command feedback message queue, etc. The operation and maintenance personnel can also use the equipment self-repair system to perform station whitelist maintenance, fault rule maintenance, task list, action record, task statistics, task termination, operation and maintenance work order processing, etc.

[0052] In a possible implementation, the process of the equipment self-repairing device receiving the data information reported by the operation and maintenance device may be that the operation and maintenance device directly reports the data information of the control device, the charging pile or the electric vehicle to the equipment self-repairing device after detecting the data information.

[0053] Another possible implementation method is that the process of the equipment self-repair device receiving the data information reported by the operation and maintenance device can be that the equipment self-repair device sends a data information acquisition request at a preset time interval. After receiving the acquisition request, the operation and maintenance device reports all data information within the time interval to the equipment self-repair device. The data information is the data obtained by the operation and maintenance device from the control device, the charging pile or the electric vehicle.

[0054] S302: Filter out data with software information from the data information according to a preset filtering method to obtain a charging message of the charging device.

[0055] The preset screening method may include: regular expression matching, keyword screening, structured query language, etc., which are not limited in this application. The software information may include: software name, version number.

[0056] In one possible implementation, when the preset screening method is regular expression matching, data with software information is screened out from the data information according to the preset screening method to obtain a charging message, including: matching the data information using a regular expression. If the data information contains the software name or version number in the software information, it is determined that the data with software information is a charging message.

[0057] Another possible implementation method, when the preset screening method is keyword screening, the data containing software information is screened out from the data information according to the preset screening method to obtain a charging message, including: if the data information contains a keyword corresponding to the software name or version number in the software information, determining that the data containing the software information with the keyword is a charging message.

[0058] In another possible implementation, when the preset screening method is structured query language, data with software information is screened out from the data information according to the preset screening method to obtain a charging message, including: using a structured query statement to query the data information, screening out the data with software information from the data information, and obtaining the charging message. For example, using an SQL statement to query a database table corresponding to the data information, identifying a database field containing software information from the database table, and determining that the data with the database field containing software information is a charging message.

[0059] The charging message consists of a time mark, a message ID and message data. The time mark can be used to indicate the charging time, and the message data can include one or more of the charging state, charging current, charging temperature and charging voltage, which is not limited in this application.

[0060] S303: Input the charging message into a fault prediction model to predict fault data of the charging device.

[0061] Among them, the fault prediction model is used to represent the one-to-one correspondence between charging messages and fault data.

[0062] One possible implementation method is to input the charging status, charging time, charging message ID, charging current, charging temperature and charging voltage of the charging message into a fault prediction model, determine the message features corresponding to the charging message, input the message features into the fault prediction model, and predict the fault data of the charging device corresponding to the message features.

[0063] The fault data may include the fault source type, fault type, and fault cause, etc.

[0064] Exemplarily, when the charging code of the charging message is 132, the charging message is input into the fault prediction model, and the fault type corresponding to the charging code is alarm, the alarm code is 34, and the alarm name is PDU output short circuit fault.

[0065] In a possible implementation, the training process of the fault prediction model may include obtaining a historical fault data set and a historical charging message set of the charging device.

[0066] There is a one-to-one correspondence between the historical fault data set in the historical fault data set and the historical charging messages in the historical charging message set.

[0067] A training set is randomly formed using any historical fault data in the historical fault data set and historical charging messages corresponding to the historical fault data one by one.

[0068] For any historical fault data in the training set and the historical charging message corresponding to the historical fault data, the historical fault feature is determined according to the historical fault data, and the historical message feature is determined according to the historical charging message.

[0069] Among them, historical fault features include historical fault source type, historical fault type and historical fault cause. Historical message features are used to indicate the abnormal change rate of historical fault data in a preset time period. Historical message features include historical fault time, historical charging current and historical battery temperature.

[0070] According to the historical fault characteristics and historical message characteristics, a fault prediction model is determined. The fault prediction model is used to represent the one-to-one correspondence between historical fault data and historical charging messages.

[0071] Furthermore, any historical fault data in the historical fault data set and the historical charging messages corresponding to the historical fault data are used to randomly form a test set. Any historical fault data in the test set and the historical charging messages corresponding to the historical fault data are used to evaluate and adjust the fault prediction model, and update the fault prediction model.

[0072] Specifically, the historical fault data and historical charging messages are first preprocessed to remove invalid or erroneous data points, such as missing values ​​or outliers. The historical fault data and historical charging messages are formatted to ensure that the formats of the historical fault data and the formats of the historical charging messages are consistent. For the numerical data in the historical fault data and historical charging messages, standardization or normalization is performed to eliminate the impact of the dimension on the numerical data in the historical fault data and historical charging messages.

[0073] Extract historical fault features from historical fault data to obtain historical fault source type, historical fault type and historical fault cause. Extract historical message features from historical charging messages to obtain historical fault time, historical charging current and historical battery temperature, etc.

[0074] It should be noted that the historical message features may also include new features constructed based on the historical message features, such as the rate of change of the historical charging current within a preset period, etc., which is not limited in the present application.

[0075] The historical fault features and historical message features may also include numerical features, which are matched with the fault types and converted into fault codes.

[0076] Any historical fault data in the historical fault data set and the historical charging message corresponding to the historical fault data are used as a training set, and the historical fault features corresponding to the historical fault data and the historical message features corresponding to the historical charging message are input into the machine learning model to obtain the model parameters of the fault prediction model, which are used to represent the one-to-one correspondence between the historical fault data and the historical charging message.

[0077] Then, any historical fault data in the historical fault data set and the historical charging message corresponding to the historical fault data are used as a test set, and the performance of the fault prediction model is evaluated using methods such as cross-validation, and the model parameters of the fault prediction model are adjusted.

[0078] S304: Based on the fault data, determine a repair task matching the fault data.

[0079] The repair task includes a repair strategy and a start time for repair. The fault data includes a fault type, which may be in the form of an alarm code.

[0080] In a possible implementation, a charging pile corresponding to the alarm code is determined according to the alarm code. At least one control device corresponding to the charging pile is obtained. Version information of the charging pile and version information of the at least one control device are obtained. A repair task is determined according to the version information of the charging pile and the version information of the at least one control device.

[0081] In a possible implementation, the repair task may include a first repair action and a second repair action. According to the version information of the charging pile, determine the device series and product type to which the charging pile belongs. According to the device series and product type of the charging pile, determine the execution condition and the start repair time corresponding to the repair task. When the version information of all control devices in at least one control device meets the execution condition, the first repair action is performed on all control devices at the start repair time. When the first control device meets the execution condition and other control devices other than the first control device in at least one control device do not meet the execution condition, the second repair action is performed on the first control device at the start repair time. The first control device is one control device in at least one control device.

[0082] The execution condition may include: the version corresponding to the version information is lower than the preset version.

[0083] For example, as shown in Table 1, when the alarm code is 35 and the version information of the charging pile is group charging 2.0, it can be determined that the repair task at this time is to restart the PDU, and the upper limit of the restart number is once, and the upper limit of the restart number can be determined according to whether the charging order fails. When the alarm code is 35 and the version information of the charging pile is 3.0 / 4.0, it can be determined that the repair task at this time is to first determine the software version, confirm whether the CCU version to which the software version PDU belongs is too low, and whether the PCU version corresponding to the PDU is too low. If the CCU version to which the software version PDU belongs is too low or the PCU version corresponding to the PDU is too low, then upgrade to the latest version and report the fault.

[0084] Table 1

[0085] For example, Figure 5 As shown, after the device self-repair device predicts the fault data of the charging device, the fault data may include the device type as PDU, the device series as 0028, the product type as group charging 3.0, the fault name as relay abnormal alarm, and the fault type as device alarm. Based on the charging message, the task condition is determined as follows: when the CCU version <0181V201B00D00 and (the PCU version <0180V203800D00 or the PCU version 4 <0256V203B00D00), the CCU device is upgraded and repaired, and the CCU version is upgraded to 0181V301B00D00, and the repair time is limited to 24 hours. At the same time, the PCU version is upgraded to 0181V503B00D00, and the repair time is limited to 24 hours. When the CCU version <0181V201B00D00, the CCU is restarted and repaired, and the repair time is limited to 24 hours.

[0086] Among them, the device series can be determined according to the software version. For example, the software version is 0028V246B00D00, and the 0028 before V identifies the product series. Some device types are related to the product type, and some product types are also related to the manufacturer. The 246 before B after V is the major version, the 00 before D after B is the test version, and the 00 after D is the development version. The repair plan, judgment conditions, and high version judgment of the device software upgrade for equipment repair are related to the product series and major versions. The repair plan and repair action formulate different repair strategies according to the product series. The judgment conditions and verification of the software version upgrade need to parse the high and low software versions. The device self-repair method provided in the embodiment of the present application can also determine the cause of the fault according to the alarm code, and then determine the version of the corresponding device that can solve the cause in combination with the specific cause of the fault, and then use the version to upgrade the device.

[0087] In a possible implementation, a basic repair time and a repair time offset of the repair task are determined according to the repair action in the repair task, and the basic repair time and the repair time offset are added to determine the start time of the repair.

[0088] In this process, a repair time offset is added for the repair task, which can disperse the execution of multiple repair tasks at the same time, reduce the access to the database, and improve the system processing efficiency.

[0089] S305: At the start of the repair time, the charging device corresponding to the charging message is repaired using the repair strategy.

[0090] A possible implementation manner is to obtain a task cache of the charging pile. The task cache includes the historical repair strategies of the charging pile within a preset time period. When there is no repair strategy in the historical repair strategies, or when there is a repair strategy in the historical repair strategies and the charging pile is successfully repaired after executing the repair strategy, the repair strategy is used to repair the charging pile.

[0091] For example, according to the start time of repair and the repair strategy, the device command center SG is called and the command message is subscribed. The device command center will feedback the result after execution. If the repair is successful, it ends. If the repair fails, an operation and maintenance work order is generated and an operation and maintenance personnel are assigned to perform on-site operation and maintenance.

[0092] For example, Figure 6 As shown, firstly, the task MAC is constructed based on the power station internal code, centralized control address, CAN address, fault type, and alarm code, and the task is stored in the Redis cache. Based on the task, the current software version and the software version of the device to which it belongs are obtained, and the product series data, equipment fault configuration list, equipment software version configuration, equipment fault repair configuration, and station equipment configuration in the corresponding basic data are obtained from Doris. The condition calculation engine is called to determine each task condition, and the corresponding repair strategy is obtained, and the repair strategy is inserted into the Redis cache. When the Redis cache determines that there is no repair strategy in the historical repair strategy, or there is a repair strategy in the historical repair strategy and the charging pile is successfully repaired after executing the repair strategy, the repair strategy is used to repair the charging pile.

[0093] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the working principle of the device. It is understandable that in order to realize the above functions, the device self-repair device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0094] The embodiment of the present application can divide the functional modules of the device self-repairing device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or software functional module.

[0095] It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. Figure 7 A possible schematic diagram of the composition of the equipment self-repairing device involved in the above and embodiments is shown. Figure 7 As shown, the device self-repairing apparatus 700 may include: a receiving module 701 , a screening module 702 , a processing module 703 , and a repairing module 704 .

[0096] The receiving module 701 is used to support the equipment self-repairing device 700 to execute Figure 3 S301 in the device self-repair method shown.

[0097] The screening module 702 is used to support the device self-repairing device 700 to execute Figure 3 S302 in the device self-repair method shown.

[0098] Processing module 703, used to support the equipment self-repairing device 700 to execute Figure 3 S303 or S304 in the device self-repair method shown.

[0099] Repair module 704, used to support the device self-repair device 700 to execute Figure 3 S305 in the device self-repair method shown.

[0100] In a possible implementation, the device provided in the embodiment of the present application can also be used to obtain a historical fault data set and a historical charging message set of a charging device. The historical fault data set in the historical fault data set has a one-to-one correspondence with the historical charging message in the historical charging message set. A training set is randomly formed using any historical fault data in the historical fault data set and the historical charging message corresponding to the historical fault data. For any historical fault data in the training set and the historical charging message corresponding to the historical fault data, the historical fault characteristics are determined according to the historical fault data, and the historical message characteristics are determined according to the historical charging message. The historical fault characteristics include the historical fault source type, the historical fault type and the historical fault cause. The historical message characteristics are used to represent the abnormal change rate of the historical fault data in a preset time period. The historical message characteristics include the historical fault time, the historical charging current, and the historical battery temperature. According to the historical fault characteristics and the historical message characteristics, a fault prediction model is determined. The fault prediction model is used to represent the one-to-one correspondence between the historical fault data and the historical charging message.

[0101] In a possible implementation, the device provided in the embodiment of the present application can also be used to randomly form a test set using any historical fault data in the historical fault data set and the historical charging messages corresponding to the historical fault data. The fault prediction model is evaluated and adjusted using any historical fault data in the test set and the historical charging messages corresponding to the historical fault data, and the fault prediction model is updated.

[0102] In a possible implementation, the device provided in the embodiment of the present application can also be used to determine the charging pile corresponding to the alarm code according to the alarm code. Obtain at least one control device corresponding to the charging pile. Obtain the version information of the charging pile and the version information of at least one control device. Determine the repair task matching the fault data according to the version information of the charging pile and the version information of at least one control device.

[0103] In a possible implementation, the device provided in the embodiment of the present application can also be used to determine the device series and product type to which the charging pile belongs based on the version information of the charging pile. According to the device series and product type of the charging pile, determine the execution conditions and the start repair time corresponding to the repair task. When the version information of all control devices in at least one control device meets the execution conditions, a first repair action is performed on all control devices at the start repair time. When the first control device meets the execution conditions and other control devices other than the first control device in at least one control device do not meet the execution conditions, a second repair action is performed on the first control device at the start repair time. The first control device is any control device among the at least one control device.

[0104] In a possible implementation, the apparatus provided in the embodiment of the present application can also be used to determine the basic repair time and the repair time offset of the repair task according to the repair action in the repair task, and add the basic repair time and the repair time offset to determine the start time of the repair.

[0105] In a possible implementation, the device provided in the embodiment of the present application can also be used to obtain a task cache of a charging pile. The task cache includes a historical repair strategy of the charging pile within a preset time period. When there is no repair strategy in the historical repair strategy, or when there is a repair strategy in the historical repair strategy and the charging pile is successfully repaired after executing the repair strategy, the repair strategy is used to repair the charging pile.

[0106] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0107] The device self-repairing device 700 provided in the embodiment of the present application is used to perform the above Figure 3 The device self-repair method shown can therefore achieve the same effect as the device self-repair method described above.

[0108] The present application also provides a device self-repairing device, which can be the device self-repairing device described in the above embodiment. Figure 1 The device self-repairing device 100 shown can execute the device self-repairing method and related steps in the above method embodiment.

[0109] An embodiment of the present application also provides a computer-readable storage medium having instructions stored thereon, which, when executed, execute the device self-repair method and related steps in the above method embodiment.

[0110] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer executes the device self-repair method and related steps in the above method embodiment.

[0111] In some embodiments, the methods described herein may be implemented as computer program instructions encoded in a machine-readable format on a computer-readable storage medium or encoded on other non-transitory media or articles of manufacture.

[0112] The present application also provides a device self-repair system 800, such as Figure 8 As shown, the device self-repair system 800 includes at least one processor 801 and at least one interface circuit 802 .

[0113] As an example, when the device self-repair system 800 includes a processor and an interface circuit, the processor may be Figure 8The processor 801 shown in the solid line frame (or the processor 801 shown in the dotted line frame) may be Figure 8 The interface circuit 802 shown in the solid line frame (or the interface circuit 802 shown in the dotted line frame). When the chip system 800 includes two processors and two interface circuits, the two processors include Figure 8 The processor 801 shown in the solid line frame and the processor 801 shown in the dotted line frame, the two interface circuits include Figure 8 The interface circuit 802 shown in the solid line frame and the interface circuit 802 shown in the dotted line frame are not limited to this.

[0114] The processor 801 and the interface circuit 802 may be interconnected via a line. For example, the interface circuit 802 may be used to receive a signal. In another example, the interface circuit 802 may be used to send a signal to another device (e.g., the processor 801). For example, the interface circuit 802 may read a computer instruction stored in a memory and send the computer instruction to the processor 801. The processor 801 executes the instruction and implements the various steps in the above embodiments in combination with the input and output devices, such as implementing Figure 3-Figure 6 Of course, the chip system may also include other discrete devices, which are not specifically limited in the embodiments of the present application.

[0115] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0116] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0117] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0118] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0119] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0120] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A device self-repair method, characterized in that: Applied to the cloud, the method includes: Receive data information of charging equipment collected and reported by operation and maintenance equipment from maintenance stations; Filtering the data containing software information from the data information according to a preset filtering method to obtain a charging message of the charging device; Inputting the charging message into a fault prediction model to predict fault data of the charging device; Based on the fault data, determining a repair task matching the fault data; the repair task includes a repair strategy and a start time for repair; At the repair start time, the charging device corresponding to the charging message is repaired using the repair strategy.

2. The method according to claim 1, characterized in that The training process of the fault prediction model includes: Acquire a historical fault data set and a historical charging message set of the charging device; the historical fault data set in the historical fault data set and the historical charging messages in the historical charging message set have a one-to-one correspondence; Randomly forming a training set using any historical fault data in the historical fault data set and historical charging messages corresponding to the historical fault data one by one; For any historical fault data in the training set and the historical charging message corresponding to the historical fault data, determine the historical fault feature according to the historical fault data, and determine the historical message feature according to the historical charging message; the historical fault feature includes the historical fault source type, the historical fault type and the historical fault cause; the historical message feature is used to represent the abnormal change rate of the historical fault data in a preset time period; the historical message feature includes the historical fault time, the historical charging current and the historical battery temperature; The fault prediction model is determined according to the historical fault characteristics and the historical message characteristics; the fault prediction model is used to represent a one-to-one correspondence between the historical fault data and the historical charging messages.

3. The method according to claim 2, characterized in that The method further comprises: A test set is randomly formed using any historical fault data in the historical fault data set and historical charging messages corresponding to the historical fault data one by one; The fault prediction model is evaluated and adjusted by using any historical fault data in the test set and the historical charging message corresponding to the historical fault data, so as to update the fault prediction model.

4. The method according to claim 1, characterized in that The fault data includes an alarm code; and determining, based on the fault data, a repair task matching the fault data includes: According to the warning code, determining the charging pile corresponding to the warning code; Acquire at least one control device corresponding to the charging pile; Obtaining version information of the charging pile and version information of the at least one control device; The repair task matching the fault data is determined according to the version information of the charging pile and the version information of the at least one control device.

5. The method according to claim 4, characterized in that The repair task includes a first repair action and a second repair action; and determining the repair task according to the version information of the charging pile and the version information of the at least one control device includes: Determine the device series and product type to which the charging pile belongs according to the version information of the charging pile; Determine the execution conditions and start time of the repair task according to the equipment series and product type of the charging pile; When the version information of all control devices in at least one of the control devices meets the execution condition, performing the first repair action on all the control devices at the start repair time; When the first control device satisfies the execution condition and other control devices other than the first control device in at least one of the control devices do not satisfy the execution condition, the second repair action is performed on the first control device at the start repair time; the first control device is any control device in at least one of the control devices.

6. The method according to claim 5, characterized in that The execution condition includes: the version corresponding to the version information is lower than the preset version.

7. The method according to claim 5, characterized in that The method further comprises: Determine a basic repair time and a repair time offset of the repair task according to the repair action in the repair task; The basic repair time and the repair time offset are added to determine the start repair time.

8. The method according to claim 1, characterized in that The repairing the charging device corresponding to the charging message by using the repair strategy includes: Obtaining a task cache of a charging pile; the task cache includes a historical repair strategy of the charging pile within a preset time period; When the repair strategy does not exist in the historical repair strategies, or when the repair strategy exists in the historical repair strategies and the charging pile is successfully repaired after executing the repair strategy, the repair strategy is used to repair the charging pile.

9. The method according to claim 1, characterized in that: The preset screening methods include: regular expression matching, keyword screening, and structured query language.

10. A self-repairing device for equipment, characterized in that: Applied to the cloud, the device includes: A receiving module is used to receive data information of charging equipment collected and reported by operation and maintenance equipment from maintenance stations; A screening module, used to screen out data with software information from the data information according to a preset screening method, and obtain a charging message of the charging device; A processing module, configured to input the charging message into a fault prediction model to predict fault data of the charging device; based on the charging message, determine a repair task matching the charging message; the repair task includes a repair strategy and a start time for repair; The repair module is used to repair the charging device corresponding to the charging message by using the repair strategy at the start repair time.

11. A device self-repairing device, characterized in that: The device self-repairing device comprises a processor and a memory, wherein the memory stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the device self-repairing method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the device self-repair method according to any one of claims 1 to 9 is implemented.

13. A computer program product comprising a computer program / instructions, characterized in that When the computer program product / instructions are executed by a processor, the device self-repair method according to any one of claims 1 to 9 is implemented.

Images