A diagnostic record generation method, apparatus, device, and medium

Abstract

The application discloses a kind of diagnostic record generation method, device, equipment and medium, applied to server end, involve computer technical field, method includes: receiving the current diagnostic state data that first equipment is based on preset rule sent;Determine the first diagnostic state data in current diagnostic state data indicating the current state of first equipment is start remote diagnosis, and determine the second diagnostic state data in current diagnostic state data indicating the current state of first equipment is end remote diagnosis;Diagnostic start state data in first diagnostic state data and diagnostic end state data in second diagnostic state data are generated based on diagnostic record.The generation of diagnostic record is converted to server end by first equipment in the application, prevent the record generated by first equipment from being unable to upload to server end, improve the generation and acquisition success rate of remote diagnosis record.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for generating diagnostic records. Background Technology

[0002] In remote diagnostics services, remote diagnostic records serve as credentials for both B-end and C-end users to perform remote diagnostic operations (B-end refers to diagnostic equipment used by technicians, and C-end refers to diagnostic equipment used by vehicle owners). These records document task information, equipment information, diagnostic start and end times, and network communication data volume. Remote diagnostic records are crucial for resolving customer disputes, analyzing equipment problems, and recording technician workload. Currently, the B-end device uploads the remote diagnostic record to the server upon completion of the diagnostic process. However, during remote diagnostics, issues such as network anomalies, power outages, or user device plugging / unplugging can cause upload failures.

[0003] In conclusion, improving the success rate of remote diagnostic record retrieval is an urgent problem to be solved. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a method, apparatus, device, and medium for generating diagnostic records, which can improve the success rate of obtaining remote diagnostic records. The specific solution is as follows:

[0005] In a first aspect, this application discloses a method for generating diagnostic records, characterized in that it is applied to a server side and includes:

[0006] Receive current diagnostic status data sent by the first device based on preset rules;

[0007] Determine the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnostics, and determine the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnostics;

[0008] A diagnostic record is generated based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data.

[0009] Optionally, the current diagnostic status data includes a status value; the status value is used to indicate at least whether the first device has started remote diagnostics, ended remote diagnostics, or is in the process of remote diagnostics.

[0010] Optionally, determining the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnostics includes:

[0011] If the current state of the first device is determined to be the end of remote diagnosis based on the state value in the latest received current diagnostic state data, then the latest received current diagnostic state data is used as the second diagnostic state data indicating that the first device has ended remote diagnosis.

[0012] Alternatively, if no diagnostic status data is acquired within a preset time period, and the current status of the first device is determined to be in the process of remote diagnosis based on the status value in the latest received current diagnostic status data, then the latest received current diagnostic status data is used as the second diagnostic status data indicating that the first device has ended remote diagnosis.

[0013] Optionally, receiving the current diagnostic status data sent by the first device based on preset rules includes:

[0014] Receive current diagnostic status data sent by the first device at preset time intervals.

[0015] Optionally, receiving the current diagnostic status data sent by the first device based on preset rules includes:

[0016] Receive current diagnostic status data sent by the first device based on preset rules, and record all the current diagnostic status data in the local first database;

[0017] Accordingly, generating a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data includes:

[0018] Record the diagnosis start status data in the first diagnostic status data and the diagnosis end status data in the second diagnostic status data to the local second database;

[0019] A diagnostic record is generated based on the diagnostic start status data and the diagnostic end status data in the second database.

[0020] Optionally, the diagnostic start status data includes a first device ID, a diagnostic task identifier, a remote diagnostic start time, and a data volume at the start of the remote diagnostic process; the diagnostic end status data includes the first device ID, the diagnostic task identifier, the remote diagnostic end time, and a data volume at the end of the remote diagnostic process.

[0021] Accordingly, generating a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data includes:

[0022] The remote diagnosis duration is calculated based on the remote diagnosis start time and the remote diagnosis end time, and the total remote diagnosis data volume is calculated based on the data volume at the start of the remote diagnosis and the data volume at the start of the remote diagnosis.

[0023] A diagnostic record is generated based on the first device ID, the diagnostic task identifier, the remote diagnostic start time, the remote diagnostic end time, the remote diagnostic duration, and the total amount of remote diagnostic data.

[0024] Optionally, the current diagnostic status data may further include diagnostic status data indicating that the first device is in an idle state, and diagnostic status data indicating that the first device is performing diagnostic configuration; the diagnostic configuration indicates configuring the first device and the second device.

[0025] Secondly, this application discloses a diagnostic record generation device, characterized in that it is applied to a server side and includes:

[0026] The data acquisition module is used to receive the current diagnostic status data sent by the first device based on preset rules;

[0027] The data determination module is used to determine the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnosis, and to determine the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnosis;

[0028] The diagnostic record generation module is used to generate a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data.

[0029] Thirdly, this application discloses an electronic device, including:

[0030] Memory, used to store computer programs;

[0031] A processor is configured to execute the computer program to implement the aforementioned disclosed method for generating diagnostic records.

[0032] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned diagnostic record generation method.

[0033] As can be seen, this application receives current diagnostic status data sent by the first device based on preset rules on the server side; determines a first diagnostic status data indicating that the first device has started remote diagnosis, and determines a second diagnostic status data indicating that the first device has ended remote diagnosis; and generates a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data. Therefore, this application obtains the current diagnostic status data of the first device in real time and determines the first diagnostic status data indicating that the first device's current state is the start of remote diagnosis and the second diagnostic status data indicating that the first device's current state is the end of remote diagnosis, in order to calculate the diagnostic record. This shifts the generation of the diagnostic record from the first device to the server side, preventing the records generated by the first device from failing to upload to the server, and improving the success rate of obtaining remote diagnostic records. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0035] Figure 1 This is a flowchart of a diagnostic record generation method disclosed in this application;

[0036] Figure 2 This is a flowchart of a specific diagnostic record generation method disclosed in this application;

[0037] Figure 3 This is a schematic diagram of the structure of a diagnostic record generation device disclosed in this application;

[0038] Figure 4 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

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

[0040] In remote diagnostics services, remote diagnostic records serve as credentials for both B-end and C-end users to perform remote diagnostic operations (B-end refers to diagnostic equipment used by technicians, and C-end refers to diagnostic equipment used by vehicle owners). These records document task information, equipment information, diagnostic start and end times, and network communication data volume. Remote diagnostic records are crucial for resolving customer disputes, analyzing equipment problems, and recording technician workload. Currently, the B-end device uploads the remote diagnostic record to the server upon completion of the diagnostic process. However, during remote diagnostics, issues such as network anomalies, power outages, or user device plugging / unplugging can cause upload failures.

[0041] Therefore, this application proposes a diagnostic record generation scheme that can improve the success rate of remote diagnostic record acquisition.

[0042] This application discloses a diagnostic record generation method applied to a server-side application; see [link to relevant documentation]. Figure 1 As shown, the method includes:

[0043] Step S11: Receive the current diagnostic status data sent by the first device based on preset rules.

[0044] In this embodiment of the application, before receiving the current diagnostic status data sent by the first device based on preset rules, the method further includes: after the first device is powered on, establishing a connection between the server and the first device so that the first device can perform login verification on the server.

[0045] In this embodiment of the application, the first device is a B-end device.

[0046] In this embodiment of the application, receiving the current diagnostic status data sent by the first device based on a preset rule includes: receiving the current diagnostic status data sent by the first device based on a preset time interval. The preset time interval can be 5 seconds, and is not specifically limited here.

[0047] Step S12: Determine the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnostics, and determine the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnostics.

[0048] In this embodiment of the application, receiving the current diagnostic status data sent by the first device based on preset rules includes: receiving the current diagnostic status data sent by the first device based on preset rules, and recording all the current diagnostic status data in a local first database. It should be noted that the local database stores all the current diagnostic status data so that it can be retrieved and viewed from the first database when needed later.

[0049] In this embodiment, the current diagnostic status data further includes diagnostic status data indicating that the first device is in an idle state, and diagnostic status data indicating that the first device is performing diagnostic configuration; the diagnostic configuration refers to configuring the first device and the second device. The second device is a C-end device.

[0050] Step S13: Generate a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data.

[0051] In this embodiment, generating a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data includes: recording the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data to a local second database; and generating a diagnostic record based on the diagnostic start status data and the diagnostic end status data in the second database. It should be noted that the first database stores a large amount of data and has a slow response time; therefore, a second database is needed to store the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data to improve response speed. It should be noted that the second database is a Redis database, and the first database is a MySQL database.

[0052] As can be seen, this application receives current diagnostic status data sent by the first device based on preset rules on the server side; determines first diagnostic status data indicating the start of remote diagnostics by the first device, and determines second diagnostic status data indicating the end of remote diagnostics by the first device; and generates a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data. Therefore, this application shifts the generation of diagnostic records from the first device to the server side, preventing records generated by the first device from failing to be uploaded to the server, and improving the success rate of remote diagnostic record generation and retrieval.

[0053] This application discloses a specific method for generating diagnostic records, applied on the server side. Compared to the previous embodiment, this embodiment further explains and optimizes the technical solution. See also... Figure 2 As shown, it specifically includes:

[0054] Step S21: Receive the current diagnostic status data sent by the first device based on preset rules.

[0055] In this embodiment, the current diagnostic status data includes, but is not limited to, status values, B-end device ID (Identification) (first device ID), task identifier (task ID), remote duration, latency, data volume, voltage, and time; the data volume refers to information data. It should be noted that the status values ​​include 0, 1, 2, 3, and 4; when the status value is 0, it indicates that the first device is currently in an idle state; when the status value is 1, it indicates that the first device is currently in the process of starting remote diagnostics; when the status value is 2, it indicates that the first device is currently in the process of performing remote diagnostics; when the status value is 3, it indicates that the first device is currently in the process of ending remote diagnostics; and when the status value is 4, it indicates that the first device is currently in the process of configuring diagnostics. It should be noted that the corresponding first device ID and second device ID can be determined based on the task identifier.

[0056] It should be noted that when there is no remote diagnostic task on the B end, the B end is in an idle state with a status value of 0; when the B end and C end are successfully configured and start remote diagnostics, the status value is 1; when the B end and C end are in the process of remote diagnostics, the status value is 2; when the B end and C end finish remote diagnostics, the status value is 3; when there is no remote diagnostic task on the B end, the B end is in an idle state with a status value of 0.

[0057] In this embodiment of the application, the current diagnostic status data includes a status value; the status value is used to indicate at least whether the first device has started remote diagnosis, the first device has ended remote diagnosis, or the first device is performing remote diagnosis.

[0058] Step S22: Determine the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnostics.

[0059] In this embodiment of the application, if the current state of the first device is determined to be "starting remote diagnosis" based on the state value in the current diagnostic state data, then the current diagnostic state data is used as the first diagnostic state data indicating that the first device has started remote diagnosis. Specifically, if the state value in the current diagnostic state data is 0, then the current state of the first device is "starting remote diagnosis," and the current diagnostic state data is used as the first diagnostic state data indicating that the first device has started remote diagnosis.

[0060] Step S23: If the current state of the first device is determined to be the end of remote diagnosis based on the state value in the latest received current diagnostic state data, then the latest received current diagnostic state data is used as the second diagnostic state data indicating that the first device has ended remote diagnosis.

[0061] In one specific embodiment, if the status value in the latest received current diagnostic status data is 3, then the current status of the first device is determined to be the end of remote diagnostics, and the latest received current diagnostic status data is used as the second diagnostic status data indicating that the first device has ended remote diagnostics.

[0062] Step S24: If no diagnostic status data is acquired within the preset time period, and the current status of the first device is determined to be in the process of remote diagnosis based on the status value in the latest received current diagnostic status data, then the latest received current diagnostic status data is used as the second diagnostic status data indicating that the first device has ended remote diagnosis.

[0063] In another specific embodiment, if no diagnostic status data is obtained within a preset time period after obtaining the latest received current diagnostic status data, and the status value in the latest received current diagnostic status data is 2, then the current status of the first device is remote diagnosis in progress, and the latest received current diagnostic status data is used as the second diagnostic status data indicating that the first device has ended remote diagnosis. It should be noted that the preset time is determined according to the connection timeout time set by the server, including but not limited to 5 minutes, and is not specifically limited here.

[0064] In summary, this application considers both the case where the first device completes the diagnosis normally and the case where the first device fails to complete the diagnosis normally, so that a diagnosis record can be generated for both cases. The case where the first device completes the diagnosis normally corresponds to the content of step S23, and the case where the first device fails to complete the diagnosis normally corresponds to the content of step S24. It should be noted that the remote diagnosis is ended and the second diagnosis status data is determined by the two methods in steps S23 and S24, so that a diagnosis record can be generated for both cases where the diagnosis is completed normally and cases where the diagnosis is not completed normally.

[0065] Step S25: Generate a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data.

[0066] In this embodiment of the application, the diagnostic start status data includes a first device ID, a diagnostic task identifier, a remote diagnostic start time, and a data volume at the start of the remote diagnostic process; the diagnostic end status data includes the first device ID, the diagnostic task identifier, the remote diagnostic end time, and a data volume at the end of the remote diagnostic process.

[0067] In this embodiment, generating a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data includes: calculating the remote diagnostic duration based on the remote diagnostic start time and the remote diagnostic end time, and calculating the total remote diagnostic data volume based on the data volume at the start of the remote diagnostic and the data volume at the start of the remote diagnostic; generating a diagnostic record based on the first device ID, the diagnostic task identifier, the remote diagnostic start time, the remote diagnostic end time, the remote diagnostic duration, and the total remote diagnostic data volume. It should be noted that the total remote diagnostic duration = remote diagnostic end time - remote diagnostic start time; the total remote diagnostic data volume = data volume at the end of the remote diagnostic - data volume at the start of the remote diagnostic.

[0068] It should be noted that the diagnostic completion status data may also include voltage, and the diagnostic record may also include voltage. It should also be noted that the voltage is generally a constant value.

[0069] As can be seen, this application receives current diagnostic status data sent by the first device based on preset rules; determines the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnostics; if the current status of the first device is determined to be the end of remote diagnostics based on the status value in the latest received current diagnostic status data, then the latest received current diagnostic status data is used as the second diagnostic status data; if no diagnostic status data is obtained within a preset time period, and the current status of the first device is determined to be the in progress of remote diagnostics based on the status value in the latest received current diagnostic status data, then the latest received current diagnostic status data is used as the second diagnostic status data indicating the end of remote diagnostics; and generates a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data. Therefore, this application shifts the generation of diagnostic records from the first device to the server, preventing records generated by the first device from failing to be uploaded to the server, thus improving the success rate of generating and obtaining remote diagnostic records; this application considers both cases where the first device completes the diagnostics normally and cases where the first device fails to complete the diagnostics normally, enabling the generation of diagnostic records to be generated regardless of whether the diagnostics are completed normally or not.

[0070] Accordingly, this application also discloses a diagnostic record generation device, applied on the server side, see [link to relevant documentation]. Figure 3 As shown, the device includes:

[0071] Data acquisition module 11 is used to receive current diagnostic status data sent by the first device based on preset rules;

[0072] The data determination module 12 is used to determine the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnosis, and to determine the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnosis;

[0073] The diagnostic record generation module 13 is used to generate a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data.

[0074] For more detailed information on the working process of each of the above modules, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0075] As can be seen, this application receives current diagnostic status data sent by the first device based on preset rules on the server side; determines first diagnostic status data indicating the start of remote diagnostics by the first device, and determines second diagnostic status data indicating the end of remote diagnostics by the first device; and generates a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data. Therefore, this application shifts the generation of diagnostic records from the first device to the server side, preventing records generated by the first device from failing to be uploaded to the server, and improving the success rate of remote diagnostic record generation and retrieval.

[0076] In one specific embodiment, the current diagnostic status data includes a status value; the status value is used to indicate at least whether the first device has started remote diagnostics, the first device has ended remote diagnostics, or the first device is performing remote diagnostics.

[0077] In one specific embodiment, the data determination module 12 includes:

[0078] The first data determining unit is configured to: if the current status of the first device is determined to be "end of remote diagnosis" based on the status value in the latest received current diagnostic status data, then use the latest received current diagnostic status data as the second diagnostic status data indicating that the first device has ended remote diagnosis; or, if no diagnostic status data is acquired within a preset time period, and the current status of the first device is determined to be "remote diagnosis in progress" based on the status value in the latest received current diagnostic status data, then use the latest received current diagnostic status data as the second diagnostic status data indicating that the first device has ended remote diagnosis.

[0079] In one specific embodiment, the data acquisition module 11 includes:

[0080] The first data acquisition module is used to receive current diagnostic status data sent by the first device based on a preset time interval.

[0081] In one specific embodiment, the data acquisition module 11 includes:

[0082] The second data acquisition unit is used to receive the current diagnostic status data sent by the first device based on preset rules, and record all the current diagnostic status data in the local first database;

[0083] Accordingly, the diagnostic record generation module 13 includes:

[0084] The first diagnostic record generation unit is used to record the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data to the local second database.

[0085] A diagnostic record is generated based on the diagnostic start status data and the diagnostic end status data in the second database.

[0086] In one specific embodiment, the diagnostic start status data includes a first device ID, a diagnostic task identifier, a remote diagnostic start time, and the amount of data at the start of the remote diagnostic process; the diagnostic end status data includes the first device ID, the diagnostic task identifier, the remote diagnostic end time, and the amount of data at the end of the remote diagnostic process.

[0087] Accordingly, the diagnostic record generation module 13 includes:

[0088] The second diagnostic record generation unit is used to calculate the remote diagnosis duration based on the remote diagnosis start time and the remote diagnosis end time, and to calculate the total remote diagnosis data volume based on the data volume at the start of the remote diagnosis and the data volume at the start of the remote diagnosis.

[0089] A diagnostic record is generated based on the first device ID, the diagnostic task identifier, the remote diagnostic start time, the remote diagnostic end time, the remote diagnostic duration, and the total amount of remote diagnostic data.

[0090] In one specific embodiment, the current diagnostic status data further includes diagnostic status data indicating that the first device is in an idle state, and diagnostic status data indicating that the first device is performing diagnostic configuration; the diagnostic configuration indicates configuring the first device and the second device.

[0091] Furthermore, embodiments of this application also provide an electronic device. Figure 4 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0092] Figure 4 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a display screen 23, an input / output interface 24, a communication interface 25, a power supply 26, and a communication bus 27. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the diagnostic record generation method disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0093] In this embodiment, the power supply 26 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 25 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 24 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0094] Furthermore, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored thereon may include computer programs 221, and the storage method may be temporary storage or permanent storage. The computer programs 221 may include, in addition to computer programs capable of performing the diagnostic record generation method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, computer programs capable of performing other specific tasks.

[0095] Furthermore, embodiments of this application also disclose a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned diagnostic record generation method.

[0096] For the specific steps of this method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0097] The various embodiments in this application are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. For the same or similar parts between the various embodiments, refer to each other. As for the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple, and relevant parts can be referred to in the method section.

[0098] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0099] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0100] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0101] The above provides a detailed description of a diagnostic record generation method, apparatus, device, and storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for generating diagnostic records, characterized in that, Applied to the server side, including: Receive current diagnostic status data sent by the first device based on preset rules; Determine the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnostics, and determine the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnostics; A diagnostic record is generated based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data; Wherein, determining the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnostics includes: If the current state of the first device is determined to be the end of remote diagnosis based on the state value in the latest received current diagnostic state data, then the latest received current diagnostic state data is used as the second diagnostic state data indicating that the first device has ended remote diagnosis. Alternatively, if no diagnostic status data is acquired within a preset time period, and the current status of the first device is determined to be in the process of remote diagnosis based on the status value in the latest received current diagnostic status data, then the latest received current diagnostic status data is used as the second diagnostic status data indicating that the first device has ended remote diagnosis.

2. The diagnostic record generation method according to claim 1, characterized in that, The current diagnostic status data includes a status value; the status value is used to indicate at least whether the first device has started remote diagnostics, ended remote diagnostics, or is in the process of remote diagnostics.

3. The diagnostic record generation method according to claim 1, characterized in that, The receipt of current diagnostic status data sent by the first device based on preset rules includes: Receive current diagnostic status data sent by the first device at preset time intervals.

4. The diagnostic record generation method according to claim 1, characterized in that, The receipt of current diagnostic status data sent by the first device based on preset rules includes: Receive current diagnostic status data sent by the first device based on preset rules, and record all the current diagnostic status data in the local first database; Accordingly, generating a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data includes: Record the diagnosis start status data in the first diagnostic status data and the diagnosis end status data in the second diagnostic status data to the local second database; A diagnostic record is generated based on the diagnostic start status data and the diagnostic end status data in the second database.

5. The diagnostic record generation method according to claim 1, characterized in that, The diagnostic start status data includes the first device ID, diagnostic task identifier, remote diagnostic start time, and data volume at the start of remote diagnostics; the diagnostic end status data includes the first device ID, the diagnostic task identifier, remote diagnostic end time, and data volume at the end of remote diagnostics. Accordingly, generating a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data includes: The remote diagnosis duration is calculated based on the remote diagnosis start time and the remote diagnosis end time, and the total remote diagnosis data volume is calculated based on the data volume at the start of the remote diagnosis and the data volume at the start of the remote diagnosis. A diagnostic record is generated based on the first device ID, the diagnostic task identifier, the remote diagnostic start time, the remote diagnostic end time, the remote diagnostic duration, and the total amount of remote diagnostic data.

6. The diagnostic record generation method according to any one of claims 1 to 5, characterized in that, The current diagnostic status data also includes diagnostic status data indicating that the first device is in an idle state, and diagnostic status data indicating that the first device is performing diagnostic configuration; the diagnostic configuration indicates configuring the first device and the second device.

7. A diagnostic record generation device, characterized in that, Applied to the server side, including: The data acquisition module is used to receive the current diagnostic status data sent by the first device based on preset rules; The data determination module is used to determine the first diagnostic status data in the current diagnostic status data that indicates the first device has started remote diagnosis, and to determine the second diagnostic status data in the current diagnostic status data that indicates the first device has ended remote diagnosis; The diagnostic record generation module is used to generate a diagnostic record based on the diagnostic start status data in the first diagnostic status data and the diagnostic end status data in the second diagnostic status data. Specifically, the data determination module is used to determine the current state of the first device as the end of remote diagnosis if the current state of the first device is determined to be the end of remote diagnosis based on the state value in the latest received current diagnostic state data. Alternatively, if no diagnostic status data is acquired within a preset time period, and the current status of the first device is determined to be in the process of remote diagnosis based on the status value in the latest received current diagnostic status data, then the latest received current diagnostic status data is used as the second diagnostic status data indicating that the first device has ended remote diagnosis.

8. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the diagnostic record generation method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, Used to store a computer program; wherein, when the computer program is executed by a processor, it implements the diagnostic record generation method as described in any one of claims 1 to 6.

Images