Charging equipment detection method and device, electronic equipment and readable storage medium

Abstract

The embodiment of the invention provides a charging equipment detection method and device, electronic equipment and a readable storage medium, and relates to the technical field of computers. According to the embodiment of the invention, the message data reported by the target charging equipment in the charging task can be received, the receiving state of each message type in the preset type set is determined according to the received message data, and the equipment state corresponding to the target charging equipment is determined according to the receiving state of each message type. Therefore, according to the embodiment of the invention, the equipment state corresponding to the target charging equipment can be remotely and quickly determined only by judging whether the corresponding message data is received or not, operation and maintenance personnel do not need to carry out field detection, the state of the charging equipment is timely and effectively detected, and the detection efficiency of the charging equipment is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a charging device detection method, device, electronic device and readable storage medium. Background Art

[0002] With the continuous increase of new energy devices, the number of charging devices is also increasing to meet the charging needs of new energy devices. Among them, abnormal detection of charging devices is an important part of the management process of charging devices.

[0003] In the related art, when a charging device is abnormal, it is generally necessary for operation and maintenance personnel to conduct on-site inspection to obtain the specific problem of the charging device. However, on-site inspection often consumes a lot of time, resulting in low detection efficiency of the charging device. Therefore, how to detect the status of the charging device in a timely and effective manner is an urgent problem to be solved. Summary of the invention

[0004] In view of this, the embodiments of the present application provide a charging device detection method, apparatus, electronic device and readable storage medium to timely and effectively detect the status of the charging device and improve the detection efficiency of the charging device.

[0005] In a first aspect, a charging device detection method is provided, the method comprising:

[0006] Receive the message data reported by the target charging device during the charging task.

[0007] The receiving status of each message type in the predetermined type set is determined according to the received message data, and the message types in the predetermined type set at least include a charging start callback message, a charging callback message and a charging task settlement message.

[0008] According to the reception status of each message type, a device status corresponding to the target charging device is determined.

[0009] In some embodiments, the method further comprises:

[0010] In response to a charging task being triggered and the charging task being a new task, a message identification code corresponding to the charging task is created, wherein the message identification code includes multiple identification bits, and the identification bits are at least used to identify the receiving status of each message type in the predetermined type set, and the number of the identification bits is greater than or equal to the number of message types in the predetermined type.

[0011] In some embodiments, determining the reception status of each message type in the predetermined type set according to the received message data includes:

[0012] In response to receiving the message data, according to the message type corresponding to the received message data, the corresponding identification bit in the message identification code is updated from a not received state to a received state.

[0013] In some embodiments, determining the device status corresponding to the target charging device according to the reception status of each message type includes:

[0014] In response to the receiving status of the charging start callback message and the charging callback message being a non-received status, it is determined that the device status corresponding to the target charging device is a startup no response exception.

[0015] In response to the receiving status of the charging start callback message being a received status and the receiving status of the charging callback message being a not received status, it is determined that the device status corresponding to the target charging device is a startup failure exception.

[0016] In response to the receiving status of the charging callback message being a received status and the receiving status of the charging task settlement message being a not received status, it is determined that the device status corresponding to the target charging device is an end no response exception.

[0017] In response to the charging callback message and the charging task settlement message being received in a received state, it is determined that the device state corresponding to the target charging device is a pending state.

[0018] In some embodiments, the charging task settlement message includes at least the charging power corresponding to the target charging device and the remaining power corresponding to the charged device when the charging task is completed.

[0019] The determining, according to the reception status of each message type, the device status corresponding to the target charging device comprises:

[0020] In response to the device status being a pending state and the charging power being 0, the device status corresponding to the target charging device is updated to be abnormal and unable to charge.

[0021] In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being less than a predetermined power threshold, the device state corresponding to the target charging device is updated to a gun-tripping abnormality.

[0022] In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being greater than or equal to a predetermined power threshold, the device state corresponding to the target charging device is updated to a normal state.

[0023] In some embodiments, the message types in the predetermined type set also include a charging start message and a charging end callback message.

[0024] In some embodiments, the method further comprises:

[0025] In response to any message type in the predetermined type set being a multi-protocol message having a plurality of different protocol standards, each identification bit corresponding to the multi-protocol message is merged to compress the message identification code.

[0026] In some embodiments, the method further comprises:

[0027] The device status corresponding to the target charging device is displayed.

[0028] In some embodiments, the method further comprises:

[0029] According to the predetermined type set, the message data reported by the target charging device in the charging task is filtered to determine the message data after the filtering process.

[0030] In a second aspect, a charging device detection device is provided, the device comprising:

[0031] The message receiving module is configured to receive message data reported by the target charging device during the charging task.

[0032] The message determination module is configured to determine the receiving status of each message type in a predetermined type set according to the received message data, wherein the message types in the predetermined type set at least include a charging start callback message, a charging callback message and a charging task settlement message.

[0033] The device status determination module is configured to determine the device status corresponding to the target charging device according to the reception status of each message type.

[0034] In some embodiments, the apparatus further comprises:

[0035] A message identification code creation module is configured to execute, in response to a charging task being triggered and the charging task being a new task, creating a message identification code corresponding to the charging task, wherein the message identification code includes multiple identification bits, and the identification bits are at least used to identify the receiving status of each message type in the predetermined type set, and the number of the identification bits is greater than or equal to the number of message types in the predetermined type.

[0036] In some embodiments, the message determination module is specifically configured to perform:

[0037] In response to receiving the message data, according to the message type corresponding to the received message data, the corresponding identification bit in the message identification code is updated from a not received state to a received state.

[0038] In some embodiments, the device status determination module is specifically configured to execute:

[0039] In response to the receiving status of the charging start callback message and the charging callback message being a non-received status, it is determined that the device status corresponding to the target charging device is a startup no response exception.

[0040] In response to the receiving status of the charging start callback message being a received status and the receiving status of the charging callback message being a not received status, it is determined that the device status corresponding to the target charging device is a startup failure exception.

[0041] In response to the receiving status of the charging callback message being a received status and the receiving status of the charging task settlement message being a not received status, it is determined that the device status corresponding to the target charging device is an end no response exception.

[0042] In response to the charging callback message and the charging task settlement message being received in a received state, it is determined that the device state corresponding to the target charging device is a pending state.

[0043] In some embodiments, the charging task settlement message includes at least the charging power corresponding to the target charging device and the remaining power corresponding to the charged device when the charging task is completed.

[0044] The device status determination module is specifically configured to execute:

[0045] In response to the device status being a pending state and the charging power being 0, the device status corresponding to the target charging device is updated to be abnormal and unable to charge.

[0046] In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being less than a predetermined power threshold, the device state corresponding to the target charging device is updated to a gun-tripping abnormality.

[0047] In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being greater than or equal to a predetermined power threshold, the device state corresponding to the target charging device is updated to a normal state.

[0048] In some embodiments, the message types in the predetermined type set also include a charging start message and a charging end callback message.

[0049] In some embodiments, the apparatus further comprises:

[0050] The compression module is configured to execute, in response to any message type in the predetermined type set being a multi-protocol message with multiple different protocol standards, merging processing on each identification bit corresponding to the multi-protocol message to compress the message identification code.

[0051] In some embodiments, the apparatus further comprises:

[0052] The display module is configured to display the device status corresponding to the target charging device.

[0053] In some embodiments, the apparatus further comprises:

[0054] The filtering module is configured to perform filtering processing on the message data reported by the target charging device in the charging task according to the predetermined type set, and determine the message data after filtering processing.

[0055] In a third aspect, an embodiment of the present application provides an electronic device, comprising a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method described in the first aspect.

[0056] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the method described in the first aspect is implemented.

[0057] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the method described in the first aspect.

[0058] The embodiment of the present application can receive the message data reported by the target charging device in the charging task, and then determine the reception status of each message type in the predetermined type set according to the received message data, and determine the device status corresponding to the target charging device according to the reception status of each message type. Therefore, the embodiment of the present application can quickly determine the device status corresponding to the target charging device remotely only by whether the corresponding message data is received, without the need for operation and maintenance personnel to perform on-site detection, thereby achieving timely and effective detection of the status of the charging device and improving the detection efficiency of the charging device. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The above and other purposes, features and advantages of the embodiments of the present application will become more apparent through the following description of the embodiments of the present application with reference to the accompanying drawings, in which:

[0060] Figure 1 A schematic diagram of a charging scenario provided in an embodiment of the present application;

[0061] Figure 2 This is a flow chart of a charging device detection method according to an embodiment of the present application;

[0062] Figure 3This is a schematic diagram of each charging stage in the charging process and the message data involved in each charging stage according to an embodiment of the present application;

[0063] Figure 4 A schematic diagram of message identification coding according to an embodiment of the present application;

[0064] Figure 5 A flowchart of another charging device detection method according to an embodiment of the present application;

[0065] Figure 6 A schematic diagram of a process for compressing a message identification code according to an embodiment of the present application;

[0066] Figure 7 A flowchart for determining the device status according to an embodiment of the present application;

[0067] Figure 8 A schematic diagram of the correspondence between the message identification code and the device status in an embodiment of the present application;

[0068] Fig. 9 Another flow chart for determining the device status according to an embodiment of the present application;

[0069] Fig.10 A schematic diagram of a display interface of an embodiment of the present application;

[0070] Fig.11 This is a schematic diagram of the structure of a charging device detection device according to an embodiment of the present application;

[0071] Fig.12 A schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0072] The present application is described below based on embodiments, but the present application is not limited to these embodiments. In the detailed description of the present application below, some specific details are described in detail. It is possible for those skilled in the art to fully understand the present application without the description of these details. In order to avoid confusing the essence of the present application, known methods, processes, flows, components and circuits are not described in detail.

[0073] In addition, persons of ordinary skill in the art will appreciate that the drawings provided herein are for illustration purposes and are not necessarily drawn to scale.

[0074] Unless the context clearly requires otherwise, the words "include", "comprising" and the like throughout this application should be interpreted as including rather than exclusive or exhaustive; that is, as meaning "including but not limited to".

[0075] In the description of this application, it should be understood that the terms "first", "second", etc. are used for descriptive purposes only and cannot be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, "multiple" means two or more. In addition, the schemes described in this specification and the embodiments, if involving the processing of personal information, will be processed on the premise of having a legal basis (for example, with the consent of the subject of personal information, or necessary for the performance of a contract, etc.), and will only be processed within the prescribed or agreed scope. The user's refusal to process personal information other than the necessary information required for basic functions will not affect the user's use of basic functions.

[0076] With the continuous promotion of new energy, the number and types of new energy equipment are increasing. At present, new energy equipment is mainly powered by batteries. When the battery is exhausted, the new energy equipment needs to be charged in time. Furthermore, in order to meet the charging needs of new energy equipment, the number of charging devices is also increasing. Among them, since the current charging equipment can be set in various scenarios, the charging equipment will be affected by many external factors such as human factors, charged equipment factors and weather factors and abnormal conditions will occur. For example, the abnormal conditions of the charging equipment may include startup failure, inability to charge, gun jumping, no response to startup and no response to termination. When the charging equipment has the above abnormal conditions, it may affect the normal use of the charging equipment. Therefore, timely detection of abnormalities in the charging equipment can effectively improve the maintenance efficiency of the charging equipment. In other words, abnormal detection of charging equipment is an important part of the process of managing charging equipment.

[0077] In the related art, when a charging device is abnormal, it is generally necessary for operation and maintenance personnel to conduct on-site inspection to obtain the specific problem of the charging device. However, on-site inspection often consumes a lot of time, resulting in low detection efficiency of the charging device. Therefore, how to detect the status of the charging device in a timely and effective manner is an urgent problem to be solved.

[0078] In order to solve the above problems, the embodiment of the present application provides a charging device detection method, which can be applied to electronic devices, and the electronic devices can be terminal devices or servers. Among them, the terminal device can be a smart phone, a tablet computer or a personal computer (PC), etc., and the server can be a single server, a server cluster configured in a distributed manner, or a cloud server.

[0079] For example, Figure 1 As shown, Figure 1 1 is a schematic diagram of a charging scenario according to an embodiment of the present application, the scenario includes a server 11, a charging device 12 and a charged device 13. The server 11 is an electronic device for executing a charging device detection method.

[0080] In a charging process, the user can obtain the corresponding information of the charging device 12 by scanning the QR code of the charging device 12 through a mobile device (such as a smart phone or tablet computer), or input the device code of the charging device 12 through the mobile device, and generate a charging request according to the information. Further, the user can send the charging request to the server 11 through the mobile device, so that the server 11 verifies the charging request and sends a charging start message to the charging device 12 after the verification is passed.

[0081] After receiving the charging start message sent by the server 11, the charging device 12 can charge the charged device 13 and report corresponding message data to the server 11 at each charging stage. Accordingly, the server 11 can receive the message data reported by the charging device 12 at each charging stage, and determine the device state 14 corresponding to the charging device 12 based on the message data at each charging stage.

[0082] Specifically, the server 11 can receive the message data reported by the target charging device (i.e., the charging device 12) in the charging task through the charging device detection method of the embodiment of the present application, determine the reception status of each message type in the predetermined type set according to the received message data, and quickly determine the device status 14 corresponding to the target charging device according to the reception status of each message type. It can be seen that the embodiment of the present application can quickly determine the device status corresponding to the target charging device remotely only by whether the corresponding message data is received, without the need for operation and maintenance personnel to perform on-site detection, thereby realizing timely and effective detection of the status of the charging device and improving the detection efficiency of the charging device.

[0083] Need to explain, Figure 1 This is only an example of a charging scenario in an embodiment of the present application. In actual applications, the server 11 used to execute the charging device detection method may also be other applicable electronic devices (such as a smart phone, a tablet computer or a personal computer, etc.), and the charged device 13 may include an electric car, an electric motorcycle, an electric tricycle and any other applicable charged device.

[0084] The following will describe in detail a charging device detection method provided by an embodiment of the present application in combination with a specific implementation method. Figure 2 As shown, the specific steps are as follows:

[0085] In step S100, message data reported by a target charging device in a charging task is received.

[0086] The charging task is the task corresponding to the user's charging request, and the target charging device can report message data of different message types in different charging stages.

[0087] For each charging stage in the charging process (i.e., charging task) and the message data involved in each charging stage, such as Figure 3 As shown, each charging stage in the charging process may include a starting stage 31 , a charging stage 32 , a stopping stage 33 and a charging end stage 34 .

[0088] The startup phase 31 starts when the charging device receives the charging startup message (or the charging service platform sends the charging startup message) and ends when the charging device sends the charging startup callback message. Among them, the charging startup message includes the startup command generated by the charging service platform, which can be used to instruct the charging device to start charging. The charging startup callback message is a message returned by the charging device to the charging service platform after the charging is successfully started, which can be used to inform the charging service platform that the charging startup is successful. In other words, the startup phase 31 is the stage in which the charging device responds to the startup command (i.e., the charging startup message).

[0089] The charging stage 32 starts from when the charging device sends a charging start callback message, until the charging service platform sends a charging end message, or until the charging end condition is met (for example, the power of the charged device reaches 100% or reaches a predetermined threshold). In the charging stage 32, the charging device can periodically report charging callback messages to the service platform so that the service platform can obtain relevant information about the charging device and the charged device during the charging process. For example, the charging device can report a charging callback message to the service platform every 1 minute, 5 minutes, or 10 minutes in the charging stage 32. The charging callback message may include the charging power of the charging device in this charging task, the remaining power of the charged device in this charging task, the charging current, the charging voltage, and other information.

[0090] The stopping stage 33 starts when the charging device receives the charging end message (or the charging service platform sends the charging end message) and ends when the charging device sends the charging end callback message. The charging end message includes the end command generated by the charging service platform, which can be used to instruct the charging device to stop charging. In addition, since the charging device can also automatically end charging when the charging end condition is met (for example, the power of the charged device reaches 100% or reaches a predetermined threshold), the stopping stage 33 does not exist in this case. In other words, if the charging device automatically ends charging when the charging end condition is met, the charging device can skip Figure 3 In the stage marked by the middle dotted line, a charging end callback message is directly sent to the charging service platform.

[0091] The charging end phase 34 starts from when the charging device sends a charging end callback message, and ends when the charging device sends a charging task settlement message, or ends after a predetermined time (e.g., 60 seconds, 90 seconds, 120 seconds, 5 minutes, 10 minutes, 1 hour, 12 hours, 24 hours, etc.) has passed since the charging end callback message was sent. The charging task settlement message includes settlement-related information of the current charging task, for example, the charging task settlement message may include the charging power of this charging task, the consumption time of this charging task, the remaining power of the charged device at the end of this charging task, and the relevant fees that the user needs to pay, etc.

[0092] In step S200, the receiving status of each message type in the predetermined type set is determined according to the received message data.

[0093] Among them, the message types in the predetermined type set include at least a charging start callback message, a charging callback message, and a charging task settlement message. The receiving state may include a received state and a non-received state. The received state indicates that the electronic device executing the charging device detection method has actually received the message data of the corresponding message type, and the non-received state indicates that the electronic device has not received the message data of the corresponding message type.

[0094] In an optional implementation, since the target charging device can report multiple message data, the embodiment of the present application can filter the message data reported by the target charging device to extract valid information. Specifically, the embodiment of the present application can filter the message data reported by the target charging device in the charging task according to a predetermined type set to determine the message data after filtering. Optionally, the predetermined type set can also include a charging start message and a charging end callback message.

[0095] By filtering the message data, the embodiment of the present application can effectively extract the message data used for charging device detection and improve the efficiency of charging device detection.

[0096] Furthermore, with respect to the process of determining whether message data has been received, the embodiment of the present application may set corresponding determination rules for each type of message data to determine message data that has not been received.

[0097] For example, for the charging start callback message, since the charging start callback message is the message data used to respond to the start command (i.e., the charging start message), the embodiment of the present application can set a response time threshold (for example, 60 seconds, 90 seconds, or 120 seconds). If the target charging device does not return the corresponding charging start callback message within the response time threshold after receiving the charging start message, the embodiment of the present application can determine that the receiving status of the charging start callback message is a non-received status.

[0098] Similarly, for charging callback messages and charging task settlement messages, the embodiments of the present application can also set corresponding response time thresholds (the response time thresholds can be the same or different). If the target charging device does not return the corresponding message data within the response time threshold, the embodiments of the present application can determine that the receiving status of the message data is a non-received status.

[0099] In step S300, the device status corresponding to the target charging device is determined according to the reception status of each message type.

[0100] According to the receiving status of each message type, the embodiment of the present application can quickly determine the charging stage in which the target charging device has an abnormality, and then quickly determine the device status corresponding to the target charging device. Figure 3 In the charging stage shown, if the electronic device executing the charging device detection method does not receive the charging start callback message and the charging callback message, it indicates that the target charging device did not normally respond to the charging start message sent by the electronic device in the startup stage 31, that is, the device state corresponding to the target charging device at this time is the startup no response exception. For another example, if the electronic device actually receives the charging start callback message, but does not receive the charging callback message, it indicates that the communication between the target charging device and the electronic device is normal, but there is no normal feedback of the charging callback message in the charging stage 32, that is, the target charging device did not start the corresponding charging action at this time, and therefore, the device state corresponding to the target charging device is the startup failure exception.

[0101] The embodiment of the present application can receive the message data reported by the target charging device in the charging task, and then determine the reception status of each message type in the predetermined type set according to the received message data, and determine the device status corresponding to the target charging device according to the reception status of each message type. Therefore, the embodiment of the present application can quickly determine the device status corresponding to the target charging device remotely only by whether the corresponding message data is received, without the need for operation and maintenance personnel to perform on-site detection, thereby achieving timely and effective detection of the status of the charging device and improving the detection efficiency of the charging device.

[0102] In an optional implementation, the embodiment of the present application can identify the receiving status of each message type through a message identification code. Specifically, the embodiment of the present application can create a message identification code corresponding to the charging task in response to the charging task being triggered and the charging task being a newly created task. In other words, the embodiment of the present application can create a corresponding message identification code for each newly created charging task to identify the receiving status of each message type in the charging task.

[0103] Among them, the message identification code may include multiple identification bits, and the identification bits are at least used to identify the receiving status of each message type in the predetermined type set. The number of identification bits is greater than or equal to the number of message types in the predetermined type. For example, if the message types in the predetermined type set include charging start callback messages, charging callback messages, and charging task settlement messages, the number of identification bits in the message identification code is greater than or equal to 3. In addition, since the message identification code is created when a new charging task is created, each identification bit is set to a non-receiving state when the message identification code is created.

[0104] For example, Figure 4 As shown, Figure 4 A schematic diagram of a message identification code, wherein: Figure 4 The message identification code shown includes 8 identification bits (i.e., identification bit 41 to identification bit 48). Identification bit 41 can be used as a reserved bit in the message identification code to facilitate the expansion of the message identification code, and identification bits 42 to identification bits 48 can correspond to different message data respectively.

[0105] The number "0" in the identification bit can be used to indicate the unreceived state, that is, the corresponding message data has not been received, and the number "1" in the identification bit can be used to indicate the received state, that is, the corresponding message data has been received. Figure 4 As shown, each identification bit is set to an unreceived state ("0") when the message identification code is created. When the electronic device receives the message data corresponding to the identification bit 45, the identification bit 45 can be updated from the unreceived state ("0") to the received state ("1").

[0106] Therefore, the embodiment of the present application can quickly determine the device status corresponding to the target charging device through the status of each identification bit in the message identification code, that is, through the distribution status of "0" and "1" in the message identification code, without the need for operation and maintenance personnel to perform on-site detection, thereby achieving timely and effective detection of the status of the charging device and improving the detection efficiency of the charging device. It should be noted that "0" and "1" in the message identification code are only an example of the embodiment itself. In actual applications, the embodiment of the present application can also characterize the status of the identification bit in other ways. For example, the embodiment of the present application can characterize the unreceived state by "1" and the received state by "0". For another example, the embodiment of the present application can also characterize the unreceived state and the received state by letters.

[0107] In an optional implementation, in combination with the above message identification code, such as Figure 5 As shown, the above step S200 may include the following steps:

[0108] In step S210, in response to receiving the message data, according to the message type corresponding to the received message data, the corresponding identification bit in the message identification code is updated from the unreceived state to the received state.

[0109] by Figure 3 Taking the charging task settlement message in as an example, if the embodiment of the present application receives the charging task settlement message within a certain time after receiving the charging end callback message, the embodiment of the present application can update the identification bit corresponding to the charging task settlement message in the message identification code from the unreceived state to the received state. If the embodiment of the present application does not receive the charging task settlement message within a certain time after receiving the charging end callback message, the embodiment of the present application can maintain the unreceived state of the identification bit. Among them, the above-mentioned certain time can be the duration corresponding to the charging end stage 34, or it can be a pre-set response time threshold.

[0110] Furthermore, after updating the message identification code, the embodiment of the present application can quickly determine the device status corresponding to the target charging device based on the distribution status of "0" and "1" in the message identification code, without the need for operation and maintenance personnel to conduct on-site inspections, thereby achieving timely and effective detection of the status of the charging device and improving the detection efficiency of the charging device.

[0111] In an optional implementation, the message types in the predetermined type set of the embodiment of the present application may also include a charging start message and a charging end callback message.

[0112] Correspondingly, the message identification code may also include identification bits corresponding to the charging start message and the charging end callback message. By setting the charging start message and the charging end callback message in the predetermined type set (that is, setting the identification bits corresponding to the charging start message and the charging end callback message in the message identification code), the embodiment of the present application can effectively expand the message types in the predetermined type set and improve the scalability of charging device detection.

[0113] In an optional implementation, in response to any message type in the predetermined type set being a multi-protocol message with multiple different protocol standards, the embodiment of the present application may also merge the identification bits corresponding to the multi-protocol message to compress the message identification code.

[0114] Among them, as the message protocol is continuously updated, some message data will have different protocol standards in the old and new protocols. In other words, message data with different protocol standards in the old and new protocols is a multi-protocol message. Figure 3Taking the message data of each charging stage shown as an example, the charging start message is usually sent according to the national standard command "instruction 7", the charging start callback message is usually sent according to the national standard command "instruction 8" or the national standard command "instruction 108-event 3", the charging callback message is usually sent according to the national standard command "instruction 104", the charging end callback message is usually sent according to the national standard command "instruction 12" or the national standard command "instruction 108-event 4", and the charging task settlement message is usually sent according to the national standard command "instruction 202". It can be seen that in the above-mentioned message data, the charging start callback message and the charging end callback message correspond to multiple different protocol standards respectively, that is, the charging start callback message and the charging end callback message are multi-protocol messages.

[0115] Furthermore, the embodiment of the present application can merge the identification bits corresponding to the multi-protocol messages to compress the message identification code.

[0116] For example, Figure 6 The message identification code shown includes 8 identification bits (identification bit 611-identification bit 618), wherein identification bit 611 is a reserved bit, identification bit 612 is the identification bit corresponding to "instruction 7", identification bit 613 is the identification bit corresponding to "instruction 8", identification bit 614 is the identification bit corresponding to "instruction 108-event 3", identification bit 615 is the identification bit corresponding to "instruction 104", identification bit 616 is the identification bit corresponding to "instruction 12", identification bit 617 is the identification bit corresponding to "instruction 108-event 4", and identification bit 618 is the identification bit corresponding to "instruction 202".

[0117] Among them, "Instruction 8" and "Instruction 108-Event 3" are both charging start callback messages, and "Instruction 12" and "Instruction 108-Event 4" are both charging end callback messages, that is, the charging start callback message and the charging end callback message are multi-protocol messages. Further, the embodiment of the present application can merge the identification bit 613 and the identification bit 614 to determine the merged identification bit 621. At the same time, the embodiment of the present application can also merge the identification bit 616 and the identification bit 617 to determine the merged identification bit 622. Optionally, the embodiment of the present application can also be as follows Figure 6 The method shown deletes the identification bit 611 (reserved bit) to further compress the message identification code. It should be understood that the embodiment of the present application can also retain the reserved bit to increase the scalability of the message identification code.

[0118] By compressing the message identification code, the embodiment of the present application can effectively reduce the repeated information in the message identification code, increase the readability of the message identification code, and improve the efficiency of charging device detection.

[0119] In an optional embodiment, if Figure 7 As shown, the above step S300 may include the following steps:

[0120] In step S310, in response to the fact that the receiving status of the charging start callback message and the charging callback message is a non-received status, it is determined that the device status corresponding to the target charging device is a startup no response exception.

[0121] In this case, the embodiment of the present application does not receive the charging start callback message and the charging callback message reported by the target charging device. Figure 3 It can be seen from the content shown that after sending the charging start message, if the target charging device does not return the corresponding charging start callback message and charging callback message, it means that the target charging device does not respond to the charging start message, that is, at this time, the target charging device has a startup no response exception.

[0122] In step S320, in response to the reception status of the charging start callback message being the received status and the reception status of the charging callback message being the unreceived status, it is determined that the device status corresponding to the target charging device is a startup failure exception.

[0123] In this case, the embodiment of the present application actually receives the charging start callback message reported by the target charging device, but does not receive the charging callback message. Figure 3 It can be seen from the content shown that if the target charging device reports the charging start callback message but does not report the charging callback message, it means that the target charging device cannot normally start the charging stage 32, that is, at this time, the target charging device has a startup failure exception.

[0124] In step S330, in response to the reception status of the charging callback message being the received status and the reception status of the charging task settlement message being the unreceived status, it is determined that the device status corresponding to the target charging device is the end no response exception.

[0125] In this case, the embodiment of the present application actually receives the charging callback message reported by the target charging device, but does not receive the charging task settlement message. Figure 3 It can be seen from the content shown that if the target charging device reports the charging callback message but does not report the charging task settlement message, it means that the target charging device cannot normally settle the corresponding charging task in the charging end stage 34, that is, the target charging device has an abnormal end without response.

[0126] In step S340, in response to the receiving status of the charging callback message and the charging task settlement message being in the received status, it is determined that the device status corresponding to the target charging device is in the pending status.

[0127] In this case, the embodiment of the present application actually receives the charging callback message and the charging task settlement message. At this time, the target charging device may be in a normal state or an abnormal state. Therefore, the device state corresponding to the target charging device is a pending state.

[0128] In addition, if the embodiment of the present application creates a message identification code corresponding to the charging task, the embodiment of the present application can also determine the device status corresponding to the target charging device according to the identification bit in the message identification code.

[0129] like Figure 8 As shown, the first identification bit in the message identification code corresponds to the charging start callback message, the second identification bit in the message identification code corresponds to the charging callback message, and the third identification bit in the message identification code corresponds to the charging task settlement message. The "0" in the identification bit is used to represent the unreceived state, the "1" in the identification bit is used to represent the received state, and the "-" in the identification bit is used to represent any state, that is, the reception state corresponding to the "-" does not affect the result of the device state.

[0130] Depend on Figure 8 It can be seen that if the identification bits in the message identification code are "0", "0" and "-" in sequence, it indicates that the receiving status of the charging start callback message and the charging callback message is not received, that is, the device state corresponding to the target charging device in this case is the startup no response exception. If the identification bits in the message identification code are "1", "0" and "-" in sequence, it indicates that the receiving status of the charging start callback message is received, and the receiving status of the charging callback message is not received, that is, the device state corresponding to the target charging device in this case is the startup failure exception. If the identification bits in the message identification code are "-", "1" and "0" in sequence, it indicates that the receiving status of the charging callback message is received, and the receiving status of the charging task settlement message is not received, that is, the device state corresponding to the target charging device in this case is the end no response exception. If the identification bits in the message identification code are "-", "1" and "1" in sequence, it indicates that the receiving status of the charging callback message and the charging task settlement message is received, that is, the device state corresponding to the target charging device in this case is the pending state.

[0131] Therefore, through the corresponding identification bits in the message identification code, the embodiment of the present application can quickly determine the device status corresponding to the target charging device without the need for operation and maintenance personnel to perform on-site inspections, thereby achieving timely and effective detection of the status of the charging device and improving the detection efficiency of the charging device.

[0132] In an optional implementation, the charging task settlement message of the embodiment of the present application includes at least the charging power corresponding to the target charging device and the remaining power corresponding to the charged device when the charging task is completed. The charging power is the power charged by the target charging device to the charged device.

[0133] Further, such as Fig. 9 As shown, the above step S300 may include the following steps:

[0134] In step S350, in response to the device status being in a pending state and the charging power being 0, the device status corresponding to the target charging device is updated to be abnormal and unable to charge.

[0135] Among them, the unable to charge anomaly can be used to indicate a state in which the target charging device can be started normally but cannot normally deliver power to the charged device.

[0136] In step S360, in response to the device state being in a pending state, the charging power being greater than 0, and the remaining power being less than a predetermined power threshold, the device state corresponding to the target charging device is updated to a gun tripping abnormality.

[0137] Among them, the gun jump abnormality can be used to indicate that the target charging device can start normally and transfer power to the charged device normally, but the charging process is interrupted by external factors (such as the user actively stops charging, forcibly pulls out the charging gun, the target charging device stops suddenly, the target charging device stops safely, etc.). In addition, the predetermined power threshold can be an applicable value such as 85%, 90% or 95%.

[0138] In step S370, in response to the device state being in a pending state, the charging power being greater than 0, and the remaining power being greater than or equal to a predetermined power threshold, the device state corresponding to the target charging device is updated to a normal state.

[0139] Therefore, through the charging power and the remaining power, the embodiment of the present application can make further judgments on the target charging device in the pending state to determine the actual state of the target charging device.

[0140] It should be noted that the above steps S350-S370 may be a further processing process after step S340 (that is, after determining that the device state corresponding to the target charging device is in a pending state). In this case, the embodiment of the present application may execute steps S350-S370 after determining that the target charging device is in a pending state. In another case, the embodiment of the present application may directly replace step S340 with steps S350-S370, that is, omitting the step of determining that the device state corresponding to the target charging device is in a pending state, so that steps S350-S370 and steps S310-S330 are parallel steps.

[0141] In an optional implementation, after determining the device status corresponding to the target charging device, the embodiment of the present application may further display the device status corresponding to the target charging device.

[0142] like Fig.10 As shown, the electronic device used to execute the charging device detection method in the embodiment of the present application can display the display interface 101 through its own display unit or an external display device (such as a display screen, a projector, etc.), and the display interface 101 may include a device information bar 1011 and a status bar 1012. Among them, the device information bar 1011 may include information of multiple charging devices (such as names, numbers, etc.), and the status bar 1012 may display the status corresponding to each charging device, which can be determined by the electronic device according to the charging device detection method. In addition, the status displayed in the status bar 1012 may be a brief information (i.e., only "normal" or "abnormal"), for example, if the device status corresponding to the target charging device is a normal state, the status displayed in the status bar 1012 of the target charging device may be "normal", and if the device status corresponding to the target charging device is any abnormal state (such as startup no response abnormality or startup failure abnormality, etc.), the status displayed in the status bar 1012 of the target charging device may be "abnormal".

[0143] Furthermore, the user can trigger the "View" control corresponding to the charging device through touch, voice control, or external device control (such as mouse control, keyboard control, etc.) to view the detailed status information corresponding to the charging device. Fig.10 As shown, the user can trigger the "view" control corresponding to the charging device 03 in any optional way to make the electronic device jump to display the display interface 102. The display interface 102 may at least include the device status corresponding to the charging device 03, and optionally, the display interface 102 may also include the message identification code corresponding to the charging device 03, the "repair" control, the "home page" control, and the return control and other related information and controls.

[0144] By displaying the device status of the target charging device on the display interface, users can quickly learn about the device status of the target charging device remotely without the need for operation and maintenance personnel to conduct on-site inspections, thereby achieving timely and effective detection of the status of the charging device and improving the detection efficiency of the charging equipment.

[0145] Based on the same technical concept, the embodiment of the present application also provides a charging device detection device, such as Fig.11 As shown, the apparatus includes: a message receiving module 111, a message determining module 112 and a device state determining module 113.

[0146] The message receiving module 111 is configured to receive message data reported by the target charging device during the charging task.

[0147] The message determination module 112 is configured to determine the receiving status of each message type in a predetermined type set according to the received message data, wherein the message types in the predetermined type set at least include a charging start callback message, a charging callback message and a charging task settlement message.

[0148] The device status determination module 113 is configured to determine the device status corresponding to the target charging device according to the reception status of each message type.

[0149] In some embodiments, the apparatus further comprises:

[0150] A message identification code creation module is configured to execute, in response to a charging task being triggered and the charging task being a new task, creating a message identification code corresponding to the charging task, wherein the message identification code includes multiple identification bits, and the identification bits are at least used to identify the receiving status of each message type in the predetermined type set, and the number of the identification bits is greater than or equal to the number of message types in the predetermined type.

[0151] In some embodiments, the message determination module 112 is specifically configured to perform:

[0152] In response to receiving the message data, according to the message type corresponding to the received message data, the corresponding identification bit in the message identification code is updated from a not received state to a received state.

[0153] In some embodiments, the device state determination module 113 is specifically configured to execute:

[0154] In response to the receiving status of the charging start callback message and the charging callback message being a non-received status, it is determined that the device status corresponding to the target charging device is a startup no response exception.

[0155] In response to the receiving status of the charging start callback message being a received status and the receiving status of the charging callback message being a not received status, it is determined that the device status corresponding to the target charging device is a startup failure exception.

[0156] In response to the receiving status of the charging callback message being a received status and the receiving status of the charging task settlement message being a not received status, it is determined that the device status corresponding to the target charging device is an end no response exception.

[0157] In response to the charging callback message and the charging task settlement message being received in a received state, it is determined that the device state corresponding to the target charging device is a pending state.

[0158] In some embodiments, the charging task settlement message includes at least the charging power corresponding to the target charging device and the remaining power corresponding to the charged device when the charging task is completed.

[0159] The device status determination module 113 is specifically configured to execute:

[0160] In response to the device status being a pending state and the charging power being 0, the device status corresponding to the target charging device is updated to be abnormal and unable to charge.

[0161] In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being less than a predetermined power threshold, the device state corresponding to the target charging device is updated to a gun-tripping abnormality.

[0162] In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being greater than or equal to a predetermined power threshold, the device state corresponding to the target charging device is updated to a normal state.

[0163] In some embodiments, the message types in the predetermined type set also include a charging start message and a charging end callback message.

[0164] In some embodiments, the apparatus further comprises:

[0165] The compression module is configured to execute, in response to any message type in the predetermined type set being a multi-protocol message with multiple different protocol standards, merging processing on each identification bit corresponding to the multi-protocol message to compress the message identification code.

[0166] In some embodiments, the apparatus further comprises:

[0167] The display module is configured to display the device status corresponding to the target charging device.

[0168] In some embodiments, the apparatus further comprises:

[0169] The filtering module is configured to perform filtering processing on the message data reported by the target charging device in the charging task according to the predetermined type set, and determine the message data after filtering processing.

[0170] The embodiment of the present application can receive the message data reported by the target charging device in the charging task, and then determine the reception status of each message type in the predetermined type set according to the received message data, and determine the device status corresponding to the target charging device according to the reception status of each message type. Therefore, the embodiment of the present application can quickly determine the device status corresponding to the target charging device remotely only by whether the corresponding message data is received, without the need for operation and maintenance personnel to perform on-site detection, thereby achieving timely and effective detection of the status of the charging device and improving the detection efficiency of the charging device.

[0171] Fig.12 Schematic diagram of an electronic device according to an embodiment of the present application. Fig.12 As shown, Fig.12 The electronic device shown is a general address query device, which includes a general computer hardware structure, which at least includes a processor 121 and a memory 122. The processor 121 and the memory 122 are connected via a bus 123. The memory 122 is suitable for storing instructions or programs executable by the processor 121. The processor 121 can be an independent microprocessor or a collection of one or more microprocessors. Thus, the processor 121 executes the instructions stored in the memory 122, thereby executing the method flow of the embodiment of the present application as described above to realize the processing of data and the control of other devices. The bus 123 connects the above-mentioned multiple components together, and at the same time connects the above-mentioned components to the display controller 124 and the display device and the input / output (I / O) device 125. The input / output (I / O) device 125 can be a mouse, a keyboard, a modem, a network interface, a touch input device, a somatosensory input device, a printer, and other devices known in the art. Typically, the input / output device 125 is connected to the system through an input / output (I / O) controller 126.

[0172] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices (equipment) or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may adopt a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0173] The present application is described with reference to flowcharts of methods, apparatuses (devices) and computer program products according to embodiments of the present application. It should be understood that each process in the flowchart can be implemented by computer program instructions.

[0174] These computer program instructions may be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device that implements the process Figure 1 A function specified in a process or multiple processes.

[0175] These computer program instructions may also be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce the instructions for implementing the process Figure 1 A device that specifies functions in a process or multiple processes.

[0176] Another embodiment of the present application relates to a non-volatile storage medium for storing a computer-readable program, wherein the computer-readable program is used for a computer to execute part or all of the above method embodiments.

[0177] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by specifying relevant hardware through a program, and the program is stored in a storage medium, including several instructions for a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute 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, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0178] Another embodiment of the present application relates to a computer program product, including a computer program / instruction, which can implement part or all of the above method embodiments when the computer program / instruction is executed by a processor.

[0179] That is, those skilled in the art can understand that the embodiments of the present application can specify relevant hardware (including the processor itself) through the processor executing a computer program product (computer program / instructions), thereby implementing all or part of the steps in the above-mentioned embodiment method.

[0180] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A charging device detection method, characterized in that: The method comprises: Receive message data reported by the target charging device during the charging task; Determine the receiving status of each message type in the predetermined type set according to the received message data, wherein the message types in the predetermined type set at least include a charging start callback message, a charging callback message, and a charging task settlement message; According to the reception status of each message type, a device status corresponding to the target charging device is determined.

2. The method according to claim 1, characterized in that The method further comprises: In response to a charging task being triggered and the charging task being a new task, a message identification code corresponding to the charging task is created, wherein the message identification code includes multiple identification bits, and the identification bits are at least used to identify the receiving status of each message type in the predetermined type set, and the number of the identification bits is greater than or equal to the number of message types in the predetermined type.

3. The method according to claim 2, characterized in that Determining the receiving status of each message type in the predetermined type set according to the received message data includes: In response to receiving the message data, according to the message type corresponding to the received message data, the corresponding identification bit in the message identification code is updated from a not received state to a received state.

4. The method according to claim 1, characterized in that: The determining, according to the reception status of each message type, the device status corresponding to the target charging device comprises: In response to the charging start callback message and the charging callback message being received in a non-received state, determining that the device state corresponding to the target charging device is a startup no response exception; In response to the receiving state of the charging start callback message being a received state, and the receiving state of the charging callback message being a not received state, determining that the device state corresponding to the target charging device is a startup failure exception; In response to the receiving status of the charging callback message being a received status, and the receiving status of the charging task settlement message being a not received status, determining that the device status corresponding to the target charging device is an end no response exception; In response to the charging callback message and the charging task settlement message being received in a received state, it is determined that the device state corresponding to the target charging device is a pending state.

5. The method according to claim 4, characterized in that The charging task settlement message at least includes the charging power corresponding to the target charging device and the remaining power corresponding to the charged device when the charging task is completed; The determining, according to the reception status of each message type, the device status corresponding to the target charging device comprises: In response to the device state being a pending state and the charging power being 0, updating the device state corresponding to the target charging device to an abnormal state of being unable to charge; In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being less than a predetermined power threshold, updating the device state corresponding to the target charging device to a gun-jumping abnormality; In response to the device state being a pending state, the charging power being greater than 0, and the remaining power being greater than or equal to a predetermined power threshold, the device state corresponding to the target charging device is updated to a normal state.

6. The method according to claim 1, characterized in that The message types in the predetermined type set also include a charging start message and a charging end callback message.

7. The method according to claim 2, characterized in that The method further comprises: In response to any message type in the predetermined type set being a multi-protocol message having a plurality of different protocol standards, each identification bit corresponding to the multi-protocol message is merged to compress the message identification code.

8. The method according to claim 1, characterized in that The method further comprises: The device status corresponding to the target charging device is displayed.

9. The method according to claim 1, characterized in that: The method further comprises: According to the predetermined type set, the message data reported by the target charging device in the charging task is filtered to determine the message data after the filtering process.

10. A charging equipment detection device, characterized in that: The device comprises: A message receiving module is configured to receive message data reported by a target charging device during a charging task; a message determination module, configured to determine the receiving status of each message type in a predetermined type set according to the received message data, wherein the message types in the predetermined type set at least include a charging start callback message, a charging callback message, and a charging task settlement message; The device status determination module is configured to determine the device status corresponding to the target charging device according to the reception status of each message type.

11. An electronic device comprising a memory and a processor, characterized in that: The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the 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 / instructions are executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images