A diagnostic file backup method and related device

Abstract

The application provides a diagnostic file backup method and related equipment, a server receives user behavior data uploaded by an automobile diagnostic device in real time, including a diagnostic file ID opened by a user and vehicle type information. When a data analysis instruction is received, it is determined whether the number of non-repeated diagnostic file IDs is greater than N, N being the number of files that can be accommodated in the backup space corresponding to the automobile diagnostic device in the server. If it is greater than N, the top N diagnostic file IDs with the highest occurrence frequency are extracted from the user behavior data, target diagnostic file IDs are filtered based on this, and are sent to the automobile diagnostic device, so that the corresponding diagnostic file is uploaded to the backup space. If it is not greater than N, target vehicle type information is extracted from the vehicle type information and is sent to the automobile diagnostic device, so that all opened diagnostic files are uploaded first, and then diagnostic files corresponding to the target vehicle type information are uploaded until the backup space is full, thereby achieving the purpose of improving the filtering efficiency.

Description

Technical Field

[0001] This invention relates to the field of file backup technology, and more specifically to a diagnostic file backup method and related equipment. Background Technology

[0002] Currently, diagnostic files generated by automotive diagnostic equipment during the diagnostic process (such as diagnostic reports and diagnostic process playback files) can only be stored in the local storage of the diagnostic equipment. This data is easily lost when users need to replace the automotive diagnostic equipment.

[0003] In existing technology, diagnostic files are backed up using a backup server before replacing automotive diagnostic equipment, and then downloaded again after the equipment is replaced. However, due to the large number of automotive diagnostic equipment, the backup server cannot provide full backup space for each device; the backup space provided to each device is fixed (typically 1GB). For automotive diagnostic equipment that already stores a large number of diagnostic files, the current method involves manually selecting important files and uploading them to the backup server. Since the equipment already stores a large number of files, manual selection is inefficient. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a diagnostic file backup method and related equipment to improve screening efficiency.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] The first aspect of this invention discloses a diagnostic file backup method applied to a server, the server being connected to an automotive diagnostic device, the server having a pre-set backup space corresponding to the automotive diagnostic device, the method comprising:

[0007] The system receives user behavior data uploaded by the vehicle diagnostic device in real time. This user behavior data is uploaded to the server in real time by the vehicle diagnostic device when the user opens a locally saved diagnostic file. The user behavior data includes vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user.

[0008] When a data analysis instruction is received from the vehicle diagnostic device, it is determined whether the number of uniquely counted diagnostic file IDs in each user behavior data is greater than N; N is the number of diagnostic files that the backup space can currently hold.

[0009] If so, extract the top N diagnostic file IDs with the highest frequency from each of the user behavior data;

[0010] Based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, multiple target diagnostic file IDs are filtered from the diagnostic file IDs contained in each user behavior data.

[0011] Each of the target diagnostic file IDs is sent to the vehicle diagnostic device, so that the vehicle diagnostic device uploads the diagnostic file corresponding to each of the target diagnostic file IDs to the backup space;

[0012] If not, extract one or more target vehicle information from the vehicle information contained in each of the user behavior data, and send each of the target vehicle information to the vehicle diagnostic device, so that the vehicle diagnostic device uploads all the opened diagnostic files to the backup space, and after all the opened diagnostic files have been uploaded, uploads the diagnostic files corresponding to the target vehicle information until the backup space is full.

[0013] Optionally, the step of filtering multiple target diagnostic file IDs from the diagnostic file IDs contained in each of the user behavior data based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy includes:

[0014] Among the N most frequently occurring diagnostic file IDs, the number of diagnostic file IDs whose frequency is less than or equal to a frequency threshold is counted to obtain the target number.

[0015] Determine whether the ratio of the target quantity to N is greater than a preset ratio;

[0016] If not, then all of the N most frequently occurring diagnostic file IDs will be used as the target diagnostic file ID;

[0017] If so, then extract the top K most frequently occurring vehicle models from each of the user behavior data as candidate vehicle models; K is a preset positive integer;

[0018] For each candidate vehicle model, the corresponding user behavior data are sorted from earliest to latest according to the receiving time. The diagnostic file IDs are extracted from each corresponding user behavior data in the sorted order until J diagnostic file IDs are extracted. The extracted J diagnostic file IDs are then used as the target diagnostic file IDs. J is a preset positive integer, and J×K=N.

[0019] Optionally, one or more target vehicle model information can be extracted from the vehicle model information contained in each user behavior data. The extracted target vehicle model information includes:

[0020] From each of the user behavior data, extract the top M most frequently occurring vehicle model information as the target vehicle model information; M is a preset positive integer.

[0021] Optionally, the method further includes:

[0022] When a space analysis command is received from the vehicle diagnostic device, the number of diagnostic files that the backup space corresponding to the vehicle diagnostic device can currently hold is analyzed, and the number of diagnostic files that the backup space can currently hold is sent to the vehicle diagnostic device.

[0023] A second aspect of this invention discloses a diagnostic file backup method applied to an automotive diagnostic device, wherein the automotive diagnostic device is connected to a server, and the server has a preset backup space corresponding to the automotive diagnostic device. The method includes:

[0024] When a user opens a locally saved diagnostic file, user behavior data is uploaded to the server in real time; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user;

[0025] In response to a user's upload operation, determine whether the backup space is sufficient to store all locally stored diagnostic files;

[0026] If not, a data analysis command is sent to the server;

[0027] Upon receiving the target diagnostic file IDs sent by the server, upload the diagnostic files corresponding to each target diagnostic file ID to the backup space;

[0028] When one or more target vehicle model information is received from the server, all opened diagnostic files are uploaded to the backup space. After all opened diagnostic files have been uploaded, the diagnostic files corresponding to the target vehicle model information are uploaded until the backup space is full.

[0029] Optionally, in response to a user's upload operation, determining whether the backup space is sufficient to store all locally saved diagnostic files includes:

[0030] In response to the user's upload operation, a space analysis command is sent to the server, causing the server to analyze the number of diagnostic files that the backup space corresponding to the vehicle diagnostic device can currently hold, and send the number of diagnostic files that the backup space can currently hold to the vehicle diagnostic device;

[0031] Based on the number of diagnostic files that the backup space can currently hold and the total number of diagnostic files stored locally, determine whether the backup space is sufficient to store all the locally stored diagnostic files.

[0032] Optionally, the method further includes:

[0033] If the backup space is not full after all the diagnostic files corresponding to the target vehicle information have been uploaded, then each of the remaining unuploaded diagnostic files will be uploaded based on its creation time until the backup space is full.

[0034] Optionally, the method further includes:

[0035] If the backup space is sufficient to store all locally saved diagnostic files, then upload all locally saved diagnostic files to the backup space.

[0036] A third aspect of this invention discloses a diagnostic file backup device applied to a server, the server being connected to an automotive diagnostic device, the server having a pre-set backup space corresponding to the automotive diagnostic device, the device comprising:

[0037] The receiving unit is used to receive user behavior data uploaded by the vehicle diagnostic device in real time; the user behavior data is uploaded to the server in real time by the vehicle diagnostic device when the user opens a locally saved diagnostic file; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user;

[0038] The first judgment unit is used to determine, when receiving a data analysis instruction sent by the vehicle diagnostic device, whether the number of non-repeating diagnostic file IDs in each user behavior data is greater than N; N is the number of diagnostic files that the backup space can currently accommodate.

[0039] The first filtering unit is configured to: if the number of non-repeating diagnostic file IDs in each user behavior data is greater than N, then extract the N most frequently occurring diagnostic file IDs from each user behavior data; based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, filter multiple target diagnostic file IDs from each diagnostic file ID contained in each user behavior data; and send each target diagnostic file ID to the vehicle diagnostic device, so that the vehicle diagnostic device uploads the diagnostic file corresponding to each target diagnostic file ID to the backup space.

[0040] The second filtering unit is configured to extract one or more target vehicle information from the vehicle information contained in each of the user behavior data if the number of non-repeating diagnostic file IDs in each of the user behavior data is not greater than N, and send each of the target vehicle information to the vehicle diagnostic device, so that the vehicle diagnostic device uploads all the opened diagnostic files to the backup space, and after all the opened diagnostic files have been uploaded, uploads the diagnostic file corresponding to the target vehicle information until the backup space is full.

[0041] A fourth aspect of this invention discloses a diagnostic file backup device applied to an automotive diagnostic device, wherein the automotive diagnostic device is connected to a server, and the server has a preset backup space corresponding to the automotive diagnostic device. The device includes:

[0042] The first upload unit is used to upload user behavior data to the server in real time when the user opens a locally saved diagnostic file; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user;

[0043] The second judgment unit is used to respond to the user's upload operation and determine whether the backup space is sufficient to store all locally stored diagnostic files;

[0044] The sending unit is configured to send a data analysis instruction to the server if the backup space is sufficient to store all locally stored diagnostic files.

[0045] The second uploading unit is used to upload the diagnostic files corresponding to each target diagnostic file ID to the backup space when it receives each target diagnostic file ID sent by the server.

[0046] The third uploading unit is used to upload all the opened diagnostic files to the backup space when it receives one or more target vehicle information sent by the server, and after all the opened diagnostic files have been uploaded, it uploads the diagnostic files corresponding to the target vehicle information until the backup space is full.

[0047] A diagnostic file backup method and related equipment based on the above embodiments of the present invention are applied to a server. The server is connected to an automotive diagnostic device, and the server has a preset backup space corresponding to the automotive diagnostic device. The method includes: receiving user behavior data uploaded by the automotive diagnostic device in real time; the user behavior data is uploaded to the server in real time by the automotive diagnostic device when a user opens a locally saved diagnostic file; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user; when a data analysis instruction is received from the automotive diagnostic device, it is determined whether the number of non-repeating diagnostic file IDs in each user behavior data is greater than N; N is the number of diagnostic files that the backup space can currently hold; if so, the most frequently occurring top-ranking diagnostic file IDs are extracted from each user behavior data. N diagnostic file IDs are given. Based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, multiple target diagnostic file IDs are filtered from the diagnostic file IDs contained in each of the user behavior data. Each target diagnostic file ID is sent to the vehicle diagnostic device, causing the vehicle diagnostic device to upload the diagnostic file corresponding to each target diagnostic file ID to the backup space. If not, one or more target vehicle model information is extracted from each vehicle model information contained in each of the user behavior data, and each target vehicle model information is sent to the vehicle diagnostic device, causing the vehicle diagnostic device to upload all opened diagnostic files to the backup space. After all opened diagnostic files have been uploaded, the diagnostic file corresponding to the target vehicle model information is uploaded until the backup space is full. In this solution, the server connects to the vehicle diagnostic device. When the user opens a diagnostic file, the vehicle diagnostic device uploads user behavior data to the server in real time. Therefore, when the user is about to replace the vehicle diagnostic device and the backup space allocated to the vehicle diagnostic device is limited, the server filters important diagnostic files based on user behavior data, causing the vehicle diagnostic device to upload important diagnostic files for backup, thereby improving the filtering efficiency. Attached Figure Description

[0048] 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.

[0049] Figure 1 This is an architecture diagram of a diagnostic file backup system disclosed in an embodiment of the present invention;

[0050] Figure 2 This is a flowchart of a diagnostic file backup method disclosed in an embodiment of the present invention;

[0051] Figure 3 This is a flowchart of another diagnostic file backup method disclosed in an embodiment of the present invention;

[0052] Figure 4 This is a schematic diagram of the backup function interface of the vehicle diagnostic server disclosed in an embodiment of the present invention;

[0053] Figure 5 This is a structural diagram of a diagnostic file backup device disclosed in an embodiment of the present invention;

[0054] Figure 6 This is a structural diagram of another diagnostic file backup device disclosed in an embodiment of the present invention. Detailed Implementation

[0055] 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.

[0056] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover a 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 limitation, 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.

[0057] As the background technology indicates, in existing technologies, diagnostic files are backed up using a backup server before replacing automotive diagnostic equipment, and then downloaded again after the equipment is replaced. However, due to the large number of automotive diagnostic equipment, the backup server cannot provide full backup space for each device; the backup space provided to each device is fixed (typically 1GB). For automotive diagnostic equipment that already stores a large number of diagnostic files, the current method involves manually selecting important files and uploading them to the backup server. Since the equipment already stores a large number of files, manual selection is inefficient.

[0058] Therefore, this invention discloses a diagnostic file backup method and related equipment. In this solution, a server is connected to an automotive diagnostic device. When a user opens a diagnostic file, the automotive diagnostic device uploads user behavior data to the server in real time. Thus, when a user is about to replace the automotive diagnostic device and the backup space allocated to the automotive diagnostic device is limited, the server filters out important diagnostic files based on the user behavior data, enabling the automotive diagnostic device to upload important diagnostic files for backup, thereby improving the filtering efficiency.

[0059] like Figure 1 The diagram shown is an architecture diagram of a diagnostic file backup system disclosed in an embodiment of the present invention. The system includes: a server 1 and one or more automotive diagnostic devices 2.

[0060] Server 1 is connected to each vehicle diagnostic device 2, and server 1 has a backup space for each vehicle diagnostic device 2.

[0061] It should be noted that the vehicle diagnostic device 2 will save a large number of diagnostic files during the diagnostic process. These diagnostic files include diagnostic report files and diagnostic process playback files. The number of diagnostic files stored in the vehicle diagnostic device 2 will vary depending on the frequency and duration of each user's use of the device.

[0062] The backup space is used to back up the diagnostic files in the old vehicle diagnostic device 2 when the user needs to replace it. Due to the limited space on server 1, the backup space allocated to each vehicle diagnostic device 2 is fixed (e.g., 1GB).

[0063] For automotive diagnostic devices 2 that store a small number of diagnostic files, all files can be uploaded to the corresponding backup space for backup. However, automotive diagnostic devices 2 that store a large number of diagnostic files face the problem of insufficient upload space. In this case, it is necessary to back up the more important diagnostic files.

[0064] Based on the diagnostic file backup system disclosed in the above embodiments of the present invention, such as Figure 2 The diagram shown is a flowchart of a diagnostic file backup method disclosed in an embodiment of the present invention. This method is applied to server 1 in the aforementioned diagnostic file backup system and mainly includes the following steps:

[0065] Step S201: Receive user behavior data uploaded by the vehicle diagnostic equipment in real time.

[0066] The user behavior data is uploaded to the server in real time by the vehicle diagnostic equipment when the user opens a locally saved diagnostic file; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user.

[0067] It should be noted that a vehicle model can be diagnosed many times using automotive diagnostic equipment, generating a diagnostic file each time. Each diagnostic file corresponds to a unique diagnostic file ID and contains the corresponding diagnostic file ID and vehicle model information.

[0068] Automotive diagnostic equipment contains a diagnostic application (i.e., a diagnostic APK). This application has a data tracking function. When a user opens a diagnostic file, it packages the diagnostic file ID and vehicle model information contained in the file into user behavior data and uploads the user behavior data to the server in real time. This data serves as the basis for subsequent screening of important diagnostic files.

[0069] Understandably, the space occupied by a single piece of user behavior data is very small, far less than the space occupied by a diagnostic file. Therefore, the server can store user behavior data uploaded by many automotive diagnostic devices.

[0070] Step S202: When a data analysis command is received from the vehicle diagnostic equipment, determine whether the number of unique diagnostic file IDs in each user behavior data is greater than N. If yes, proceed to step S203; otherwise, proceed to step S206.

[0071] Where N is the number of diagnostic files that the backup space can currently hold. Generally, the size of diagnostic files is fixed, so the number of diagnostic files that the backup space can currently hold can be calculated based on the current remaining size of the backup space.

[0072] In step S202, the diagnostic file ID that is not counted repeatedly means that when multiple user behavior data contain the same diagnostic file ID (i.e., the user opens the same diagnostic file multiple times), it is only counted as one.

[0073] For example, suppose there are 3 user behavior data, which contain diagnostic file IDs: 123, 123 and 321. Among the 3 user behavior data, the number of diagnostic file IDs that are not counted repeatedly is 2, that is, the two 123 are counted as one, and 321 is counted as one, for a total of 2.

[0074] It should be noted that if the number of unique diagnostic file IDs in each user behavior data is greater than N, it means that the current backup space is insufficient to store all the diagnostic files opened by the user. Therefore, steps S203 to S205 need to be executed to filter out the important target diagnostic file IDs and send them to the vehicle diagnostic device, so that the vehicle diagnostic device uploads the diagnostic files corresponding to each target diagnostic file ID to the backup space.

[0075] If the number of unique diagnostic file IDs in each user behavior data is less than or equal to N, it means that the current backup space is sufficient to store all diagnostic files opened by the user. After storing all the diagnostic files opened by the user, the backup space may not be full, and there are still a large number of unopened diagnostic files in the vehicle diagnostic device that have not been uploaded to the backup space. In order to make full use of the backup space, step S206 is executed to filter out important target vehicle information and send it to the vehicle diagnostic device, so that the vehicle diagnostic device can upload unopened diagnostic files based on the target vehicle information until the backup space is full.

[0076] Step S203: Extract the top N diagnostic file IDs with the highest frequency from each user behavior data.

[0077] Where N is the number of diagnostic files that the backup space can currently hold.

[0078] Understandably, the higher the frequency of the diagnostic file ID in various user behavior data, the more times the user opens the corresponding diagnostic file, and the higher its importance.

[0079] Assuming N is 2, and further assuming that in each user behavior data, diagnostic file ID: 123 appears 5 times, diagnostic file ID: 321 appears 3 times, and diagnostic file ID: 213 appears 1 time, then the N diagnostic file IDs with the highest frequency are 123 and 321.

[0080] Step S204: Based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, filter multiple target diagnostic file IDs from the diagnostic file IDs contained in each user behavior data.

[0081] In the specific implementation of step S204, among the top N diagnostic file IDs with the highest frequency, the number of diagnostic file IDs with a frequency less than or equal to the frequency threshold is counted to obtain the target number.

[0082] Determine whether the ratio of the target quantity to N is greater than the preset ratio.

[0083] If not, then the top N most frequent diagnostic file IDs will all be used as the target diagnostic file IDs.

[0084] If so, then extract the top K most frequently occurring vehicle models from each user behavior data as candidate vehicle models.

[0085] For each candidate vehicle model, the corresponding user behavior data is sorted from earliest to latest according to the receiving time. Diagnostic file IDs are extracted from each user behavior data in the sorted order until J diagnostic file IDs are extracted. The extracted J diagnostic file IDs are then used as the target diagnostic file ID.

[0086] Where K and J are preset positive integers, J×K=N to ensure that the backup space is fully loaded and improve the utilization rate of the spare space.

[0087] It should be noted that among the top N diagnostic file IDs with the highest frequency, some may only appear two or three times. These diagnostic file IDs that only appear two or three times cannot reflect the importance of the corresponding diagnostic file.

[0088] If diagnostic file IDs that appear only two or three times account for a certain percentage of the top N most frequent diagnostic file IDs, then it cannot be determined whether the diagnostic files corresponding to these N diagnostic file IDs are important. In this case, it is necessary to filter out the target vehicle model information and provide it to the vehicle diagnostic equipment to ensure that the uploaded diagnostic files are important.

[0089] If the proportion of these target diagnostic file IDs, which may only appear two or three times, in the top N most frequent diagnostic file IDs does not reach a certain level, then it can be confirmed that the diagnostic files corresponding to these N diagnostic file IDs are important. Therefore, all of the top N most frequent diagnostic file IDs are used as target diagnostic file IDs.

[0090] Step S205: Send each target diagnostic file ID to the vehicle diagnostic device, so that the vehicle diagnostic device uploads the diagnostic file corresponding to each target diagnostic file ID to the backup space.

[0091] Step S206: Extract one or more target vehicle information from the vehicle information contained in each user behavior data, and send each target vehicle information to the vehicle diagnostic equipment, so that the vehicle diagnostic equipment uploads all opened diagnostic files to the backup space, and after all opened diagnostic files have been uploaded, uploads the diagnostic files corresponding to the target vehicle information until the backup space is full.

[0092] In step S205, the top M most frequently occurring vehicle models are extracted from each user behavior data as target vehicle model information; M is a preset positive integer.

[0093] It should be noted that if the number of unique diagnostic file IDs in each user behavior data is less than or equal to N, it means that the current backup space is sufficient to store all diagnostic files opened by the user. After storing all diagnostic files opened by the user, the backup space may not be full.

[0094] Automotive diagnostic equipment typically contains a large number of unopened diagnostic files that have not been uploaded to the backup space. Since these unopened diagnostic files lack corresponding user behavior data on the server, the target vehicle information involved in the most frequently opened diagnostic files can be determined using stored user behavior data. If the backup space is not full, the unopened diagnostic files corresponding to the target vehicle information are also backed up as important diagnostic files.

[0095] In one embodiment, when a space analysis command is received from the vehicle diagnostic device, the number of diagnostic files that the backup space corresponding to the vehicle diagnostic device can currently hold is analyzed, and the number of diagnostic files that the backup space can currently hold is sent to the vehicle diagnostic device. This allows the system to determine whether the backup space is sufficient to store all locally stored diagnostic files based on the number of diagnostic files that the backup space can currently hold and the total number of locally stored diagnostic files. If so, the vehicle diagnostic device directly uploads all locally stored diagnostic files to the backup space, without requiring the server to perform data analysis on user behavior data.

[0096] Based on the diagnostic file backup method disclosed in the above embodiments of the present invention, in this solution, the server is connected to the vehicle diagnostic device. When the user opens a diagnostic file, the vehicle diagnostic device uploads user behavior data to the server in real time. Thus, when the user is about to replace the vehicle diagnostic device and the backup space allocated to the vehicle diagnostic device is limited, the server filters out important diagnostic files based on the user behavior data, enabling the vehicle diagnostic device to upload important diagnostic files for backup, thereby improving the filtering efficiency.

[0097] Based on the diagnostic file backup system disclosed in the above embodiments of the present invention, such as Figure 3 The diagram shows another diagnostic file backup method disclosed in an embodiment of the present invention. This method is applied to the vehicle diagnostic server 2 in the aforementioned diagnostic file backup system.

[0098] like Figure 4 The diagram shown is a schematic of the backup function interface of the automotive diagnostic server disclosed in an embodiment of the present invention.

[0099] Clicking the top row of icons allows you to back up and upload diagnostic files; clicking the bottom row of icons allows you to download diagnostic files.

[0100] This method mainly includes the following steps:

[0101] Step S301: When a user opens a locally saved diagnostic file, upload the user's behavior data to the server in real time.

[0102] The user behavior data includes vehicle model information and diagnostic file ID contained in the diagnostic files opened by the user.

[0103] Step S302: In response to the user's upload operation, determine whether the backup space is sufficient to store all locally saved diagnostic files. If not, proceed to step S303; if yes, proceed to step S306.

[0104] In the specific implementation of step S302, in response to the user's upload operation, a space analysis command is sent to the server, so that the server analyzes the number of diagnostic files that the backup space corresponding to the vehicle diagnostic device can currently hold, and sends the number of diagnostic files that the backup space can currently hold to the vehicle diagnostic device; based on the number of diagnostic files that the backup space can currently hold and the number of all diagnostic files stored locally, it is determined whether the backup space is sufficient to store all the diagnostic files stored locally.

[0105] Step S303: Send a data analysis command to the server.

[0106] In step S303, a data analysis instruction is sent to the server, causing the server to perform data analysis on the user behavior data. For the specific data analysis process, please refer to the above embodiment of the present invention, which will not be repeated here.

[0107] Step S304: When the server sends the IDs of each target diagnostic file, upload the diagnostic file corresponding to each target diagnostic file ID to the backup space.

[0108] Step S305: When one or more target vehicle model information is received from the server, upload all opened diagnostic files to the backup space. After all opened diagnostic files have been uploaded, upload the diagnostic files corresponding to the target vehicle model information until the backup space is full.

[0109] In one embodiment, if the backup space is not full after all diagnostic files corresponding to the target vehicle information have been uploaded, then each of the remaining unuploaded diagnostic files is uploaded based on its creation time until the backup space is full.

[0110] Optionally, based on the creation time of each remaining unuploaded diagnostic file, the files can be uploaded sequentially from earliest to latest or from latest to earliest until the backup space is full.

[0111] Optionally, based on the creation time of each remaining unuploaded diagnostic file, upload each unuploaded diagnostic file that matches the time period selected by the user, until the backup space is full.

[0112] Step S306: Upload all locally saved diagnostic files to the backup space.

[0113] Based on the diagnostic file backup method disclosed in the above embodiments of the present invention, in this solution, the server is connected to the vehicle diagnostic device. When the user opens a diagnostic file, the vehicle diagnostic device uploads user behavior data to the server in real time. Thus, when the user is about to replace the vehicle diagnostic device and the backup space allocated to the vehicle diagnostic device is limited, the server filters out important diagnostic files based on the user behavior data, enabling the vehicle diagnostic device to upload important diagnostic files for backup, thereby improving the filtering efficiency.

[0114] like Figure 5 The diagram shown is a structural diagram of a diagnostic file backup device disclosed in an embodiment of the present invention. It is applied to a server and is connected to an automotive diagnostic device. The server has a preset backup space corresponding to the automotive diagnostic device. The device includes: a receiving unit 501, a first judgment unit 502, a first filtering unit 503, and a second filtering unit 504.

[0115] The receiving unit 501 is used to receive user behavior data uploaded by the vehicle diagnostic equipment in real time. The user behavior data is uploaded to the server in real time by the vehicle diagnostic equipment when the user opens a locally saved diagnostic file. The user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user.

[0116] The first judgment unit 502 is used to determine, when receiving a data analysis instruction sent by the vehicle diagnostic equipment, whether the number of non-repeating diagnostic file IDs in each user behavior data is greater than N; N is the number of diagnostic files that the backup space can currently hold;

[0117] The first filtering unit 503 is used to extract the N most frequently occurring diagnostic file IDs from each user behavior data if the number of non-repeating diagnostic file IDs in each user behavior data is greater than N; based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, multiple target diagnostic file IDs are filtered from each diagnostic file ID contained in each user behavior data; and each target diagnostic file ID is sent to the vehicle diagnostic device, so that the vehicle diagnostic device uploads the diagnostic file corresponding to each target diagnostic file ID to the backup space.

[0118] The second filtering unit 504 is used to extract one or more target vehicle information from the vehicle information contained in each user behavior data if the number of non-repeating diagnostic file IDs in each user behavior data is not greater than N, and send each target vehicle information to the vehicle diagnostic device, so that the vehicle diagnostic device uploads all opened diagnostic files to the backup space, and after all opened diagnostic files have been uploaded, uploads the diagnostic file corresponding to the target vehicle information until the backup space is full.

[0119] Optionally, a first filtering unit 503, used to filter multiple target diagnostic file IDs from the diagnostic file IDs contained in various user behavior data based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, is specifically used for:

[0120] Among the N most frequently occurring diagnostic file IDs, count the number of diagnostic file IDs whose frequency is less than or equal to the frequency threshold to obtain the target number.

[0121] Determine whether the ratio of the target quantity to N is greater than a preset ratio;

[0122] If not, then the top N most frequent diagnostic file IDs will all be used as the target diagnostic file ID;

[0123] If so, extract the top K most frequently occurring vehicle models from each user behavior data as candidate vehicle models; K is a preset positive integer.

[0124] For each candidate vehicle model, the corresponding user behavior data is sorted from earliest to latest according to the receiving time. Diagnostic file IDs are extracted from each user behavior data in the sorted order until J diagnostic file IDs are extracted. The extracted J diagnostic file IDs are then used as the target diagnostic file IDs; J is a preset positive integer, J×K=N.

[0125] Optionally, a second filtering unit 504 for extracting one or more target vehicle information from the vehicle information contained in various user behavior data is specifically used for:

[0126] Extract the top M most frequently occurring vehicle models from various user behavior data as target vehicle models; M is a preset positive integer.

[0127] Optionally, the device may also include:

[0128] The space analysis unit is used to analyze the number of diagnostic files that the backup space of the vehicle diagnostic device can currently hold when it receives a space analysis command from the vehicle diagnostic device, and then send the number of diagnostic files that the backup space can currently hold to the vehicle diagnostic device.

[0129] Based on the diagnostic file backup device disclosed in the above embodiments of the present invention, in this solution, the server is connected to the vehicle diagnostic device. When the user opens a diagnostic file, the vehicle diagnostic device uploads user behavior data to the server in real time. Thus, when the user is about to replace the vehicle diagnostic device and the backup space allocated to the vehicle diagnostic device is limited, the server filters out important diagnostic files based on the user behavior data, enabling the vehicle diagnostic device to upload important diagnostic files for backup, thereby improving the filtering efficiency.

[0130] like Figure 6 This is a structural diagram of another diagnostic file backup device disclosed in an embodiment of the present invention. It is applied to an automotive diagnostic device, which is connected to a server. The server has a backup space corresponding to the automotive diagnostic device. The device includes: a first upload unit 601, a second judgment unit 602, a sending unit 603, a second upload unit 604, and a third upload unit 605.

[0131] The first upload unit 601 is used to upload user behavior data to the server in real time when the user opens a locally saved diagnostic file; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user;

[0132] The second judgment unit 602 is used to respond to the user's upload operation and determine whether the backup space is sufficient to store all locally saved diagnostic files;

[0133] The sending unit 603 is used to send a data analysis command to the server if the backup space is insufficient to store all the diagnostic files stored locally.

[0134] The second upload unit 604 is used to upload the diagnostic files corresponding to each target diagnostic file ID to the backup space when it receives each target diagnostic file ID sent by the server.

[0135] The third upload unit 605 is used to upload all opened diagnostic files to the backup space when it receives one or more target vehicle information sent by the server, and uploads the diagnostic files corresponding to the target vehicle information after all opened diagnostic files have been uploaded until the backup space is full.

[0136] Optionally, the second judgment unit 602 is specifically used for:

[0137] In response to the user's upload operation, a space analysis command is sent to the server, which then analyzes the number of diagnostic files that the backup space corresponding to the vehicle diagnostic device can currently hold, and sends the number of diagnostic files that the backup space can currently hold to the vehicle diagnostic device.

[0138] Based on the number of diagnostic files that the backup space can currently hold and the total number of diagnostic files stored locally, determine whether the backup space is sufficient to store all the locally stored diagnostic files.

[0139] Optionally, the device may also include:

[0140] The third upload unit is used to upload each of the remaining unuploaded diagnostic files based on their creation time, if the backup space is not full after all the diagnostic files corresponding to the target vehicle information have been uploaded, until the backup space is full.

[0141] Optionally, the device may also include:

[0142] The fourth upload unit is used to upload all locally stored diagnostic files to the backup space if the backup space is sufficient to store all locally stored diagnostic files.

[0143] Based on the diagnostic file backup device disclosed in the above embodiments of the present invention, in this solution, the server is connected to the vehicle diagnostic device. When the user opens a diagnostic file, the vehicle diagnostic device uploads user behavior data to the server in real time. Thus, when the user is about to replace the vehicle diagnostic device and the backup space allocated to the vehicle diagnostic device is limited, the server filters out important diagnostic files based on the user behavior data, enabling the vehicle diagnostic device to upload important diagnostic files for backup, thereby improving the filtering efficiency.

[0144] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0145] 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 implementations should not be considered beyond the scope of this invention.

[0146] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A diagnostic file backup method, characterized in that, The method is applied to a server connected to an automotive diagnostic device, the server having a pre-set backup space corresponding to the automotive diagnostic device, and includes: The system receives user behavior data uploaded by the vehicle diagnostic device in real time. This user behavior data is uploaded to the server in real time by the vehicle diagnostic device when the user opens a locally saved diagnostic file. The user behavior data includes vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user. When a data analysis instruction is received from the vehicle diagnostic device, it is determined whether the number of uniquely counted diagnostic file IDs in each user behavior data is greater than N; N is the number of diagnostic files that the backup space can currently hold. If so, extract the top N diagnostic file IDs with the highest frequency from each of the user behavior data; Based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, multiple target diagnostic file IDs are filtered from the diagnostic file IDs contained in each user behavior data. Each of the target diagnostic file IDs is sent to the vehicle diagnostic device, so that the vehicle diagnostic device uploads the diagnostic file corresponding to each of the target diagnostic file IDs to the backup space; If not, extract one or more target vehicle information from the vehicle information contained in each of the user behavior data, and send each of the target vehicle information to the vehicle diagnostic device, so that the vehicle diagnostic device uploads all the opened diagnostic files to the backup space, and after all the opened diagnostic files have been uploaded, uploads the diagnostic files corresponding to the target vehicle information until the backup space is full.

2. The method according to claim 1, characterized in that, The process of filtering multiple target diagnostic file IDs from the diagnostic file IDs contained in each user behavior data, based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, includes: Among the N most frequently occurring diagnostic file IDs, the number of diagnostic file IDs whose frequency is less than or equal to a frequency threshold is counted to obtain the target number. Determine whether the ratio of the target quantity to N is greater than a preset ratio; If not, then all of the N most frequently occurring diagnostic file IDs will be used as the target diagnostic file ID; If so, then extract the top K most frequently occurring vehicle models from each of the user behavior data as candidate vehicle models; K is a preset positive integer; For each candidate vehicle model, the corresponding user behavior data are sorted from earliest to latest according to the receiving time. The diagnostic file IDs are extracted from each corresponding user behavior data in the sorted order until J diagnostic file IDs are extracted. The extracted J diagnostic file IDs are then used as the target diagnostic file IDs. J is a preset positive integer, and J×K=N.

3. The method according to claim 1, characterized in that, From the vehicle information contained in various user behavior data, extract one or more target vehicle information, including: From each of the user behavior data, extract the top M most frequently occurring vehicle model information as the target vehicle model information; M is a preset positive integer.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When a space analysis command is received from the vehicle diagnostic device, the number of diagnostic files that the backup space corresponding to the vehicle diagnostic device can currently hold is analyzed, and the number of diagnostic files that the backup space can currently hold is sent to the vehicle diagnostic device.

5. A diagnostic file backup method, characterized in that, The method, applied to automotive diagnostic equipment connected to a server, wherein the server has a pre-set backup space corresponding to the automotive diagnostic equipment, includes: When a user opens a locally saved diagnostic file, user behavior data is uploaded to the server in real time; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user; In response to a user's upload operation, determine whether the backup space is sufficient to store all locally saved diagnostic files; If not, a data analysis command is sent to the server, which determines whether the number of unique diagnostic file IDs in each user behavior data is greater than N; N is the number of diagnostic files that the backup space can currently hold. If yes, the server extracts the N most frequently occurring diagnostic file IDs from each user behavior data. Based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, multiple target diagnostic file IDs are filtered from the diagnostic file IDs contained in each user behavior data. Each target diagnostic file ID is sent to the vehicle diagnostic device, causing the vehicle diagnostic device to upload the diagnostic file corresponding to each target diagnostic file ID to the backup space. If not, one or more target vehicle model information is extracted from each vehicle model information contained in each user behavior data, and each target vehicle model information is sent to the vehicle diagnostic device, causing the vehicle diagnostic device to upload all opened diagnostic files to the backup space. After all opened diagnostic files have been uploaded, the device uploads the diagnostic file corresponding to the target vehicle model information until the backup space is full. When the server sends each target diagnostic file ID, the diagnostic file corresponding to each target diagnostic file ID is uploaded to the backup space; When one or more target vehicle model information is received from the server, all opened diagnostic files are uploaded to the backup space. After all opened diagnostic files have been uploaded, the diagnostic files corresponding to the target vehicle model information are uploaded until the backup space is full.

6. The method according to claim 5, characterized in that, In response to a user's upload operation, determining whether the backup space is sufficient to store all locally saved diagnostic files includes: In response to the user's upload operation, a space analysis command is sent to the server, causing the server to analyze the number of diagnostic files that the backup space corresponding to the vehicle diagnostic device can currently hold, and send the number of diagnostic files that the backup space can currently hold to the vehicle diagnostic device; Based on the number of diagnostic files that the backup space can currently hold and the total number of diagnostic files stored locally, determine whether the backup space is sufficient to store all the locally stored diagnostic files.

7. The method according to claim 5, characterized in that, The method further includes: If the backup space is not full after all the diagnostic files corresponding to the target vehicle information have been uploaded, then each of the remaining unuploaded diagnostic files will be uploaded based on its creation time until the backup space is full.

8. The method according to any one of claims 5 to 7, characterized in that, The method further includes: If the backup space is sufficient to store all locally saved diagnostic files, then upload all locally saved diagnostic files to the backup space.

9. A diagnostic file backup device, characterized in that, The device is applied to a server, which is connected to an automotive diagnostic device. The server has a pre-set backup space corresponding to the automotive diagnostic device. The device includes: The receiving unit is used to receive user behavior data uploaded by the vehicle diagnostic device in real time; the user behavior data is uploaded to the server in real time by the vehicle diagnostic device when the user opens a locally saved diagnostic file; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user; The first judgment unit is used to determine, when receiving a data analysis instruction sent by the vehicle diagnostic device, whether the number of non-repeating diagnostic file IDs in each user behavior data is greater than N; N is the number of diagnostic files that the backup space can currently accommodate. The first filtering unit is configured to: if the number of non-repeating diagnostic file IDs in each user behavior data is greater than N, then extract the N most frequently occurring diagnostic file IDs from each user behavior data; based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, filter multiple target diagnostic file IDs from each diagnostic file ID contained in each user behavior data; and send each target diagnostic file ID to the vehicle diagnostic device, so that the vehicle diagnostic device uploads the diagnostic file corresponding to each target diagnostic file ID to the backup space. The second filtering unit is configured to extract one or more target vehicle information from the vehicle information contained in each user behavior data if the number of non-repeating diagnostic file IDs in each user behavior data is not greater than N, and send each target vehicle information to the vehicle diagnostic device, so that the vehicle diagnostic device uploads all opened diagnostic files to the backup space, and after all opened diagnostic files have been uploaded, uploads the diagnostic file corresponding to the target vehicle information until the backup space is full.

10. A diagnostic file backup device, characterized in that, An application in automotive diagnostic equipment, wherein the automotive diagnostic equipment is connected to a server, and the server has a pre-set backup space corresponding to the automotive diagnostic equipment, the device comprising: The first upload unit is used to upload user behavior data to the server in real time when the user opens a locally saved diagnostic file; the user behavior data includes: vehicle model information and diagnostic file ID contained in the diagnostic file opened by the user; The second judgment unit is used to respond to the user's upload operation and determine whether the backup space is sufficient to store all locally stored diagnostic files; The sending unit is configured to send a data analysis instruction to the server if the backup space is sufficient to store all locally stored diagnostic files. The server determines whether the number of non-repeating diagnostic file IDs in each user behavior data is greater than N, where N is the number of diagnostic files that the backup space can currently hold. If yes, the server extracts the N most frequently occurring diagnostic file IDs from each user behavior data. Based on the N most frequently occurring diagnostic file IDs and a preset filtering strategy, multiple target diagnostic file IDs are filtered from the diagnostic file IDs contained in each user behavior data. Each target diagnostic file ID is sent to the vehicle diagnostic device, causing the vehicle diagnostic device to upload the diagnostic file corresponding to each target diagnostic file ID to the backup space. If no, the server extracts one or more target vehicle model information from each vehicle model information contained in each user behavior data and sends each target vehicle model information to the vehicle diagnostic device, causing the vehicle diagnostic device to upload all opened diagnostic files to the backup space. After all opened diagnostic files have been uploaded, the server uploads the diagnostic file corresponding to the target vehicle model information until the backup space is full. The second uploading unit is used to upload the diagnostic files corresponding to each target diagnostic file ID to the backup space when it receives each target diagnostic file ID sent by the server. The third uploading unit is used to upload all the opened diagnostic files to the backup space when it receives one or more target vehicle information sent by the server, and after all the opened diagnostic files have been uploaded, it uploads the diagnostic files corresponding to the target vehicle information until the backup space is full.

Images