CN113625680A - Diagnostic software processing method and device and computer equipment - Google Patents
Diagnostic software processing method and device and computer equipment Download PDFInfo
- Publication number
- CN113625680A CN113625680A CN202110789048.5A CN202110789048A CN113625680A CN 113625680 A CN113625680 A CN 113625680A CN 202110789048 A CN202110789048 A CN 202110789048A CN 113625680 A CN113625680 A CN 113625680A
- Authority
- CN
- China
- Prior art keywords
- software
- diagnostic
- target
- preset time
- time period
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 31
- 238000003745 diagnosis Methods 0.000 claims description 37
- 238000004590 computer program Methods 0.000 claims description 23
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 238000009434 installation Methods 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
Abstract
The application is applicable to the technical field of vehicle diagnosis software management, and provides a diagnosis software processing method, a diagnosis software processing device and computer equipment, wherein the diagnosis software processing device comprises the following steps: acquiring the report uploading times of the installed diagnostic software in a preset time period; determining target diagnosis software, wherein the report uploading times of the target diagnosis software in the preset time period meet a preset standard; deleting the target diagnostic software. By the method, the probability of mistakenly deleting the target diagnosis software by the user can be reduced.
Description
Technical Field
The present application belongs to the technical field of vehicle diagnosis software management, and in particular, to a diagnostic software processing method, apparatus, computer device, and computer-readable storage medium.
Background
With the increase of the economic level, more and more individuals own the vehicle (such as a household car), and the vehicle always has certain faults in the running process.
At present, the failure diagnosis of a vehicle is mainly performed by a diagnostic apparatus. Specifically, different diagnostic software is installed in the diagnostic device, each of which is capable of diagnosing a vehicle of a corresponding vehicle type. While the user may need to delete part of the diagnostic software installed on the diagnostic device during the use of the diagnostic device, there may be cases where the diagnostic software is deleted by mistake during the deletion.
Disclosure of Invention
The embodiment of the application provides a diagnostic software processing method, a diagnostic software processing device, computer equipment and a computer readable storage medium, and can solve the problem of mistaken deletion of diagnostic software of diagnostic equipment.
In a first aspect, an embodiment of the present application provides a diagnostic software processing method, which is applied to a first diagnostic device, and includes:
acquiring the report uploading times of the installed diagnostic software in a preset time period;
determining target diagnosis software, wherein the report uploading times of the target diagnosis software in the preset time period meet a preset standard;
deleting the target diagnostic software.
Optionally, after the determining the target diagnostic software, the method further comprises:
acquiring the report uploading times of target diagnosis software on second diagnosis equipment in the preset time period, wherein the second diagnosis equipment is diagnosis equipment in a target region;
the delete target diagnostic software comprising:
and if the number of times of uploading reports of the target diagnosis software on the second diagnosis equipment in the preset time period, which exceeds a preset proportion, meets the preset standard, the first diagnosis equipment deletes the target diagnosis software.
Optionally, the deleting the target diagnostic software includes:
generating a list to be deleted according to the target diagnosis software and prompting a user;
receiving a selection instruction of the user, wherein the selection instruction is used for selecting corresponding target diagnosis software in the list to be deleted;
and deleting the selected target diagnosis software.
Optionally, before obtaining the number of report uploads of the installed diagnostic software within a preset time period, the method includes:
obtaining available memory of the first diagnostic equipment;
the acquiring the report uploading times of the installed diagnostic software in a preset time period comprises the following steps:
and if the available memory is smaller than a preset memory threshold value, acquiring the report uploading times of the installed diagnostic software in a preset time period.
Optionally, the ending date of the preset time period is the current date, and the time length of the preset time period is a preset duration.
Optionally, the preset criteria include: the number of report uploads is below a first threshold.
Optionally, before obtaining the number of report uploads of the installed diagnostic software within a preset time period, the method includes:
acquiring the starting-up times in the preset time period;
and determining the first threshold value according to the starting-up times.
In a second aspect, an embodiment of the present application provides a diagnostic software processing apparatus, which is applied to a first diagnostic device, and includes:
the acquisition module is used for acquiring the report uploading times of the installed diagnostic software in a preset time period;
the determining module is used for determining target diagnosis software, and the report uploading times of the target diagnosis software in the preset time period meet a preset standard;
and the deleting module is used for deleting the target diagnosis software.
In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the method according to any one of the first aspect when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the method according to any one of the first aspect.
In a fifth aspect, the present application provides a computer program product, which when executed on a computer device, causes the computer device to implement the method of any one of the above first aspects.
Compared with the prior art, the embodiment of the application has the advantages that:
in the embodiment of the application, the first diagnostic device determines target diagnostic software of which the report uploading times meet a preset standard in a preset time period according to the acquired report uploading times, and deletes the target diagnostic software. Only the target diagnosis software with report uploading times meeting the preset standard in the preset time period is deleted, and the report uploading times can accurately reflect the use condition of the diagnosis software, so that the probability of mistakenly deleting the diagnosis software can be reduced by only deleting the target diagnosis software, and the condition that the diagnosis equipment cannot be used due to insufficient memory can be effectively prevented because the corresponding memory can be released after the target diagnosis software is deleted.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.
FIG. 1 is a system architecture diagram of a diagnostic software process provided by an embodiment of the present application;
FIG. 2 is a flow chart of a diagnostic software processing method provided by an embodiment of the present application;
fig. 3 is a block diagram of a diagnostic software processing apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise.
The first embodiment is as follows:
at present, when a user needs to diagnose a certain vehicle, it is necessary to install diagnostic software corresponding to the vehicle type of the vehicle in a diagnostic device in advance, and then diagnose the vehicle by using the diagnostic software. In practical application, after a user purchases a diagnosis device, the diagnosis software corresponding to each vehicle type is usually downloaded first, and after the memory of the diagnosis device is insufficient, some diagnosis software is manually deleted. However, in the manual deletion process of the user, some commonly used diagnostic software may be deleted by mistake, so that inconvenience is brought to subsequent diagnosis.
In order to solve the above technical problem, an embodiment of the present application provides a diagnostic software processing method. First, the first diagnostic device obtains the report uploading times (i.e. the times of uploading reports to the server) of the installed diagnostic software in a preset time period, and then deletes the diagnostic software corresponding to the report uploading times meeting the preset standard. Since the diagnostic software corresponding to the number of times of uploading the report satisfying the preset criterion is deleted instead of any diagnostic software, the probability of the diagnostic software being deleted by mistake can be reduced.
Fig. 1 is a system architecture diagram of a diagnostic software process according to an embodiment of the present application. In fig. 1, the system architecture includes a server, a first diagnostic device and a second diagnostic device, where the first diagnostic device and the second diagnostic device refer to two independent diagnostic devices, which may be functionally identical independent diagnostic devices. In the embodiment of the application, after the diagnosis software in the first diagnosis device and the second diagnosis device diagnoses the vehicle, the generated diagnosis reports are uploaded to the server. Since the first diagnostic device and the second diagnostic device both upload the generated diagnostic reports to the server, the server can count the number of times of uploading the reports of each diagnostic software in the first diagnostic device (or the second diagnostic device). It should be noted that, in practical cases, there are a plurality of second diagnostic devices (only one is shown in fig. 1), and this is not a limitation.
The diagnostic software processing method provided by the embodiment of the present application is described below with reference to the drawings.
Fig. 2 shows a flowchart of a diagnostic software processing method provided in an embodiment of the present application, where the processing method is applied to a first diagnostic device, and is detailed as follows:
and step S21, acquiring the report uploading times of the installed diagnosis software in a preset time period.
The starting date and the ending date of the preset time period can be set manually or automatically by the first diagnostic equipment.
For example, the start date of the preset time period may be set as the installation date of the diagnostic software.
Since the diagnostic software obtains one report after performing a diagnosis on the vehicle, and uploads the obtained report to the server, that is, the number of times of uploading the report is accumulated to 1 every time the report is uploaded, in this embodiment, the first diagnostic device may search the record of the report that is uploaded to the server by each installed diagnostic software to obtain the number of times of uploading the report of each diagnostic software. Or, the first diagnostic device requests the server for the number of times of uploading the report of the diagnostic software installed in the first diagnostic device, and then receives the number of times of uploading the report of each diagnostic software of the first diagnostic device from the server.
In this embodiment, each time the diagnostic software performs a diagnosis, the corresponding report upload times are accumulated to 1, so that the number of times the diagnostic software uploads a report to the server (i.e., the number of times the report is uploaded instead of the number of times the diagnostic software is started) can accurately reflect the number of times the diagnostic software is used.
And step S22, determining target diagnosis software, wherein the report uploading times of the target diagnosis software in a preset time period meet a preset standard.
The preset criteria relate to the number of times of uploading reports, for example, the preset criteria include: the number of reporting uploads is lower than a first threshold, for example, the first threshold may be set to 5 times, and of course, may also be set to 4 or 6, etc., which is not limited herein.
In some embodiments, if the number of times of uploading the report of the diagnostic software does not meet the preset standard, the first diagnostic device displays a prompt message of the diagnostic software which does not need to be deleted. Since the prompt information of the "diagnosis software not to be deleted" is displayed, it is convenient for the user to know that the first diagnosis device does not recommend the diagnosis software to be deleted, and the user can delete the corresponding diagnosis software by manually selecting the diagnosis software to be deleted.
In some embodiments, different diagnostic software may be set to correspond to the same first threshold, and since different diagnostic software all correspond to the same threshold, the corresponding target diagnostic software can be quickly screened according to the first threshold.
In some embodiments, different diagnostic software may be set for different first thresholds, taking into account that the frequency of faults occurring in different vehicle models is generally different. For example, if the number of times of report upload of diagnostic software a per year is X in the historical period, and the number of times of report upload of diagnostic software B per year is Y in the historical period, and X is not equal to Y, the first threshold value set for diagnostic software a is X and the first threshold value set for diagnostic software B is Y. Different first threshold values are set for different diagnostic software, so that more accurate target diagnostic software can be screened when the corresponding diagnostic software is subsequently screened according to the first threshold values corresponding to different diagnostic software.
In step S23, the target diagnostic software is deleted.
In this embodiment, the first diagnostic apparatus deletes the target diagnostic software installed therein.
In the embodiment of the application, the first diagnostic device determines target diagnostic software of which the report uploading times meet a preset standard in a preset time period according to the acquired report uploading times, and deletes the target diagnostic software. Only the target diagnosis software with report uploading times meeting the preset standard in the preset time period is deleted, and the report uploading times can accurately reflect the use condition of the diagnosis software, so that the probability of mistakenly deleting the diagnosis software can be reduced by only deleting the target diagnosis software, and the condition that the diagnosis equipment cannot be used due to insufficient memory can be effectively prevented because the corresponding memory can be released after the target diagnosis software is deleted.
In some embodiments, in order to further reduce the probability that the diagnostic software is deleted by mistake, after step S22, the method includes:
and acquiring the report uploading times of target diagnosis software on second diagnosis equipment in a preset time period, wherein the second diagnosis equipment is diagnosis equipment in a target region.
Correspondingly, step S23 includes:
and if the number of times of uploading reports of the target diagnosis software on the second diagnosis equipment exceeding the preset proportion in the preset time period meets the preset standard, the first diagnosis equipment deletes the target diagnosis software.
In this embodiment, the target region generally refers to the same region (or country) as the region (or country) where the first diagnostic device is located, for example, when the country where the first diagnostic device is located is china, the number of times of uploading the report of the second diagnostic device located in china within a preset time period is obtained. Since the number of times of report uploading of the target diagnostic software of the diagnostic device (i.e., the second diagnostic device) in the target region in the same time period also satisfies the preset standard, which indicates that the usage of the target diagnostic software in the second diagnostic device is similar to that in the first diagnostic device, whether the target diagnostic software is finally deleted or not is selected in combination with the usage of the target diagnostic software in the first diagnostic device and the second diagnostic device, and the probability that the target diagnostic software is deleted by mistake can be further reduced.
In some embodiments, in order to ensure that the target software deleted by the first diagnostic device is the diagnostic software that the user wishes to delete, step S23 includes:
and A1, generating a list to be deleted according to the target diagnosis software and prompting a user.
In this embodiment, the generated list to be deleted includes unique identifiers of the target diagnostic software, for example, names or icons of the target diagnostic software, and the unique identifier of each target diagnostic software corresponds to one selection box. After the list to be deleted is generated, the deletion list can be directly popped up to prompt a user to select diagnostic software to be deleted, or prompt information for prompting the user to select the diagnostic software to be deleted is generated, if the prompt information is character information, the prompt information is displayed, and if the prompt information is voice information, the voice information is broadcasted.
And A2, receiving a selection instruction of a user, wherein the selection instruction is used for selecting corresponding target diagnosis software in the list to be deleted.
In this embodiment, when the user clicks on the selection box next to the target diagnosis software, the selection box will take the shape of "v" inside, or the background color inside the selection box will be filled from pure white to pure black to indicate that the target diagnosis software corresponding to the selection box is selected. It should be noted that, after the target diagnosis software is selected, if the user clicks the selection box corresponding to the target diagnosis software again, the target diagnosis software will not be selected again.
And A3, deleting the selected target diagnosis software.
In this embodiment, after the user selects the target diagnostic software to be deleted, a confirmation prompt box may pop up, if the first diagnostic device determines that the user clicks a "yes" button in the confirmation prompt box, the selected target diagnostic software is deleted, and if the first diagnostic device determines that the user clicks a "no" button in the confirmation prompt box, the selected target diagnostic software is not deleted, and the generated list to be deleted is closed, or the state of the selected target diagnostic software is reset from the selected state to the non-selected state.
In the above-described a1 to A3, the first diagnostic device prompts the user to select the target diagnostic software that the first diagnostic device actually desires to delete before deleting the target diagnostic software, and finally deletes only the target diagnostic software selected by the user, so that the above-described processing ensures that all the target diagnostic software that the first diagnostic device finally deletes is the target diagnostic software that the first diagnostic device considers to be deletable and that the user also considers to be deletable, and the probability of the target diagnostic software being deleted by mistake can be reduced.
In some embodiments, step S21 is preceded by:
available memory of the first diagnostic device is obtained.
Correspondingly, step S21 includes:
and if the available memory is smaller than a preset memory threshold value, acquiring the report uploading times of the installed diagnostic software in a preset time period.
In this embodiment, the available memory may be determined by subtracting the used memory of the first diagnostic device from the total memory of the first diagnostic device. The first diagnostic equipment obtains the report uploading times of the diagnostic software only when the memory of the first diagnostic equipment is small, namely, the first diagnostic equipment can automatically judge whether the diagnostic software needs to be deleted or not, so that the installed diagnostic software of the first diagnostic equipment can be reserved as far as possible when the memory is large, and therefore when a user needs to use a certain diagnostic software, the user does not need to reinstall the diagnostic software, and the good experience of the user is improved. And when the memory is small, the memory is vacated as much as possible, so that the utilization rate of the memory of the first diagnostic equipment is favorably improved.
In some embodiments, the end date of the preset time period may be set as the current date, and the time length of the preset time period is set as the preset time length. Thus, after the user sets the preset time period, the first diagnostic device can determine the preset time period by combining the current date. Because the current date is used as the end date of the preset time period, the obtained report uploading times are the latest report uploading times, namely, the report uploading times which accurately reflect the condition that the corresponding diagnostic software is used in the near future can be obtained, and therefore the probability that the diagnostic software is deleted by mistake is further reduced in the follow-up process.
In some embodiments, the first diagnostic device counts a distribution rule of time for each target diagnostic software to upload a diagnostic report from the installation time to the current time, determines a time interval for the first diagnostic software of the first diagnostic device to upload two adjacent diagnostic reports according to the distribution rule, and prompts the user to change the preset time length if the preset time length input by the user is judged to be less than the time interval, so that the preset time length is greater than the time interval.
The distribution rule includes report uploading time of each diagnosis report, time interval between report uploading time of two adjacent diagnosis reports, and the like. And counting the time interval between the uploading moments of any two adjacent diagnosis reports, then calculating the average value of each time interval, and taking the average value as the time interval for the target diagnosis software to upload the two adjacent diagnosis reports. And if the first diagnostic equipment judges that the preset time length input by the user is less than the counted time interval, sending a prompt. The preset time length input by the user is not less than the preset time length input by the first diagnostic equipment, so that the time when the target diagnostic software is used can be covered as much as possible, namely, the accuracy of the subsequently obtained report uploading times can be improved through the setting, and the fact that whether the corresponding diagnostic software needs to be deleted or not is more accurately evaluated according to the report uploading times subsequently is guaranteed. For example, suppose that a diagnostic software uploads a diagnostic report respectively on 5 days 6 months, 6 days 7 months and 5 days 8 months, that is, the time interval for uploading two adjacent diagnostic reports by the diagnostic software is 30 days, if the start date of the preset time period is 6 days 8 months and the end date is 20 days 8 months, the above rule shows that the diagnostic software is probably not used in the time period between 6 days 8 months and 20 days 8 months, so the counted number of uploading reports is usually wrong. That is, since the preset time duration (14 days) input by the user is shorter than the time interval (30 days), the accuracy of the counted number of times (0 times) of uploading the report is low.
In some embodiments, the first threshold is a dynamic value, that is, before step S21, the method includes:
and B1, acquiring the starting times in the preset time period.
And B2, determining a first threshold value according to the startup times.
Considering that the diagnostic software can only execute the corresponding diagnostic function when the first diagnostic device is in the on state, in this embodiment, the first threshold is set in relation to the number of times the first diagnostic device is turned on. Since the first threshold is set in association with the number of times of turning on the first diagnostic device, the set first threshold is made more accurate. For example, when the user is not using the first diagnostic device when the user is on vacation (maintenance company) or the first device is being maintained, and therefore, the diagnostic software installed in the first diagnostic device is not necessarily used, and in this case, the adjustment of the first threshold value can make the target diagnostic software determined later more accurate.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Example two:
fig. 3 shows a block diagram of a diagnostic software processing apparatus provided in the embodiment of the present application, which is applied to a first diagnostic device, corresponding to the diagnostic software processing method in the first embodiment.
The diagnostic software processing device 3 includes: a report uploading times obtaining module 31, a target diagnosis software determining module 32 and a target diagnosis software deleting module 33. Wherein:
and a report upload number acquiring module 31, configured to acquire a report upload number of the installed diagnostic software in a preset time period.
The starting date and the ending date of the preset time period can be set manually or automatically by the first diagnostic equipment.
For example, the start date of the preset time period may be set as the installation date of the diagnostic software.
For example, the end date of the preset time period may be set as the current date, and the time length of the preset time period may be set as the preset time length.
In some embodiments, the diagnostic software processing means 3 comprise:
the preset duration change prompting module is used for counting a distribution rule of time from the installation time to the current time of each target diagnosis software for uploading the diagnosis reports, determining a time interval between the uploading of the first diagnosis software of the first diagnosis equipment to two adjacent diagnosis reports according to the distribution rule, and prompting a user that the preset duration needs to be changed if the preset duration input by the user is judged to be smaller than the time interval so that the preset duration is larger than the time interval.
And the target diagnosis software determining module 32 is used for determining target diagnosis software, and the report uploading times of the target diagnosis software in a preset time period meet a preset standard.
Wherein, this preset standard includes: the number of reporting uploads is lower than a first threshold, for example, the first threshold may be set to 5 times, and of course, may also be set to 4 or 6, etc., which is not limited herein.
In some embodiments, the diagnostic software processing means 3 comprise:
and the no-recommendation prompting module is used for displaying prompting information including the diagnosis software which is not recommended to be deleted if the report uploading times of the diagnosis software do not meet the preset standard.
In some embodiments, different diagnostic software may be set for the same first threshold.
In some embodiments, different diagnostic software may be set for different first thresholds, taking into account that the frequency of faults occurring in different vehicle models is generally different.
And the target diagnosis software deleting module 33 is used for deleting the target diagnosis software.
In the embodiment of the application, the first diagnostic device determines target diagnostic software of which the report uploading times meet a preset standard in a preset time period according to the acquired report uploading times, and deletes the target diagnostic software. Only the target diagnosis software with report uploading times meeting the preset standard in the preset time period is deleted, and the report uploading times can accurately reflect the use condition of the diagnosis software, so that the probability of mistakenly deleting the diagnosis software can be reduced by only deleting the target diagnosis software, and the condition that the diagnosis equipment cannot be used due to insufficient memory can be effectively prevented because the corresponding memory can be released after the target diagnosis software is deleted.
In some embodiments, the diagnostic software processing apparatus 3 further includes:
and the report uploading frequency acquisition module of the second diagnostic equipment is used for acquiring the report uploading frequency of the target diagnostic software on the second diagnostic equipment in a preset time period, and the second diagnostic equipment is diagnostic equipment in the target region.
Correspondingly, the target diagnosis software deleting module 33 includes:
and if the number of times of uploading reports of the target diagnosis software on the second diagnosis equipment exceeding the preset proportion in the preset time period meets the preset standard, the first diagnosis equipment deletes the target diagnosis software.
In some embodiments, the target diagnosis software deleting module 33 includes: the device comprises a list to be deleted generating unit, a selection instruction receiving unit and a deleting unit. Wherein:
and the list to be deleted generating unit is used for generating a list to be deleted according to the target diagnosis software and prompting a user.
And the selection instruction receiving unit is used for receiving a selection instruction of a user, and the selection instruction is used for selecting corresponding target diagnosis software in the list to be deleted.
And the deleting unit is used for deleting the selected target diagnosis software.
In some embodiments, the diagnostic software processing means 3 comprise:
and the available memory acquisition module is used for acquiring the available memory of the first diagnostic equipment.
Correspondingly, the report upload frequency obtaining module 31 is specifically configured to:
and if the available memory is smaller than a preset memory threshold value, acquiring the report uploading times of the installed diagnostic software in a preset time period.
In some embodiments, the end date of the preset time period is the current date, and the time length of the preset time period is a preset time length.
In some embodiments, the preset criteria include: the number of reported uploads is below a first threshold.
In some embodiments, the diagnostic software processing means 3 comprise:
and the starting-up frequency acquisition module is used for acquiring the starting-up frequency in a preset time period.
And the first threshold value determining module is used for determining a first threshold value according to the starting times.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
Example three:
fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 4, the computer device 4 of this embodiment includes: at least one processor 40 (only one processor is shown in fig. 4), a memory 41, and a computer program 42 stored in the memory 41 and executable on the at least one processor 40, wherein the steps in the first embodiment are realized when the computer program 42 is executed by the processor 40.
The computer device may include, but is not limited to, a processor 40, a memory 41. Those skilled in the art will appreciate that fig. 4 is merely an example of the computer device 4 and does not constitute a limitation of the computer device 4, and may include more or less components than those shown, or combine certain components, or different components, such as input output devices, network access devices, etc.
The Processor 40 may be a Central Processing Unit (CPU), and the Processor 40 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
An embodiment of the present application further provides a network device, where the network device includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, the processor implementing the steps of any of the various method embodiments described above when executing the computer program.
The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.
The embodiment of the present application provides a computer program product, which when running on a diagnostic device, enables the diagnostic device to implement the steps in the first method embodiment.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A diagnostic software processing method, applied to a first diagnostic device, comprising:
acquiring the report uploading times of the installed diagnostic software in a preset time period;
determining target diagnosis software, wherein the report uploading times of the target diagnosis software in the preset time period meet a preset standard;
deleting the target diagnostic software.
2. The diagnostic software processing method as set forth in claim 1, comprising, after said determining the target diagnostic software:
acquiring the report uploading times of target diagnosis software on second diagnosis equipment in the preset time period, wherein the second diagnosis equipment is diagnosis equipment in a target region;
the delete target diagnostic software comprising:
and if the number of times of uploading reports of the target diagnosis software on the second diagnosis equipment in the preset time period, which exceeds a preset proportion, meets the preset standard, the first diagnosis equipment deletes the target diagnosis software.
3. The diagnostic software processing method as set forth in claim 1, wherein said deleting the target diagnostic software comprises:
generating a list to be deleted according to the target diagnosis software and prompting a user;
receiving a selection instruction of the user, wherein the selection instruction is used for selecting corresponding target diagnosis software in the list to be deleted;
and deleting the selected target diagnosis software.
4. The diagnostic software processing method as set forth in claim 1, wherein said obtaining the number of report uploads of the installed diagnostic software within a preset time period comprises:
obtaining available memory of the first diagnostic equipment;
the acquiring the report uploading times of the installed diagnostic software in a preset time period comprises the following steps:
and if the available memory is smaller than a preset memory threshold value, acquiring the report uploading times of the installed diagnostic software in a preset time period.
5. The diagnostic software processing method as set forth in claim 1, wherein the end date of the preset time period is a current date, and the time length of the preset time period is a preset time length.
6. The diagnostic software processing method as set forth in claim 1, wherein the preset criteria include: the number of report uploads is below a first threshold.
7. The diagnostic software processing method as set forth in claim 6, wherein said obtaining the number of report uploads of the installed diagnostic software within a preset time period comprises:
acquiring the starting-up times in the preset time period;
and determining the first threshold value according to the starting-up times.
8. A diagnostic software processing apparatus, applied to a first diagnostic device, comprising:
the acquisition module is used for acquiring the report uploading times of the installed diagnostic software in a preset time period;
the determining module is used for determining target diagnosis software, and the report uploading times of the target diagnosis software in the preset time period meet a preset standard;
and the deleting module is used for deleting the target diagnosis software.
9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110789048.5A CN113625680A (en) | 2021-07-13 | 2021-07-13 | Diagnostic software processing method and device and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110789048.5A CN113625680A (en) | 2021-07-13 | 2021-07-13 | Diagnostic software processing method and device and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113625680A true CN113625680A (en) | 2021-11-09 |
Family
ID=78379637
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110789048.5A Pending CN113625680A (en) | 2021-07-13 | 2021-07-13 | Diagnostic software processing method and device and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113625680A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101563672A (en) * | 2006-12-18 | 2009-10-21 | 株式会社爱可信 | Application updating management terminal device, system and program |
| US20150373107A1 (en) * | 2012-10-02 | 2015-12-24 | Nextbit Systems, Inc. | Managing applications on an electronic device |
| CN107179930A (en) * | 2017-06-12 | 2017-09-19 | 广东小天才科技有限公司 | Method and device is recommended in one kind application unloading |
| CN107247606A (en) * | 2017-05-24 | 2017-10-13 | 努比亚技术有限公司 | Application management method, device and computer-readable recording medium |
| CN107493386A (en) * | 2017-08-22 | 2017-12-19 | 广东小天才科技有限公司 | A kind of application management method, application program management device and intelligent terminal |
| CN111024405A (en) * | 2019-11-28 | 2020-04-17 | 深圳市元征科技股份有限公司 | Automobile diagnosis method, related device and system |
| CN111474921A (en) * | 2020-04-29 | 2020-07-31 | 深圳市元征科技股份有限公司 | Configuration method of automobile diagnosis software and related equipment |
| WO2020206691A1 (en) * | 2019-04-12 | 2020-10-15 | 深圳市欢太科技有限公司 | Application processing method and apparatus, storage medium, and electronic device |
-
2021
- 2021-07-13 CN CN202110789048.5A patent/CN113625680A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101563672A (en) * | 2006-12-18 | 2009-10-21 | 株式会社爱可信 | Application updating management terminal device, system and program |
| US20150373107A1 (en) * | 2012-10-02 | 2015-12-24 | Nextbit Systems, Inc. | Managing applications on an electronic device |
| CN107247606A (en) * | 2017-05-24 | 2017-10-13 | 努比亚技术有限公司 | Application management method, device and computer-readable recording medium |
| CN107179930A (en) * | 2017-06-12 | 2017-09-19 | 广东小天才科技有限公司 | Method and device is recommended in one kind application unloading |
| CN107493386A (en) * | 2017-08-22 | 2017-12-19 | 广东小天才科技有限公司 | A kind of application management method, application program management device and intelligent terminal |
| WO2020206691A1 (en) * | 2019-04-12 | 2020-10-15 | 深圳市欢太科技有限公司 | Application processing method and apparatus, storage medium, and electronic device |
| CN111024405A (en) * | 2019-11-28 | 2020-04-17 | 深圳市元征科技股份有限公司 | Automobile diagnosis method, related device and system |
| CN111474921A (en) * | 2020-04-29 | 2020-07-31 | 深圳市元征科技股份有限公司 | Configuration method of automobile diagnosis software and related equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107909330B (en) | Workflow data processing method and device, storage medium and computer equipment | |
| CN113127338A (en) | Firmware testing method, server and computer readable storage medium | |
| CN111488088B (en) | Equipment state identification method and device and intelligent terminal | |
| CN103593465A (en) | Method and device for diagnosing abnormality of application popularization channel | |
| CN109814531B (en) | Automatic diagnosis method and system based on cloud platform and related equipment | |
| CN113504772A (en) | Vehicle fault processing method and device and vehicle diagnosis equipment | |
| CN111708584A (en) | Vehicle diagnosis method and device, diagnosis equipment and storage medium | |
| CN110634021A (en) | Big data based vehicle estimation method, system, device and readable storage medium | |
| CN110371022B (en) | Battery matching method and device and vehicle-mounted equipment | |
| CN111798580B (en) | Authority configuration method, device, system, server, terminal and storage medium | |
| EP3609153B1 (en) | Maintenance equipment management method, server and computer-readable storage medium | |
| CN113625680A (en) | Diagnostic software processing method and device and computer equipment | |
| CN110308901A (en) | Handle data variable method, apparatus, equipment and storage medium in front end page | |
| CN114281361A (en) | Software processing method and device, electronic equipment and storage medium | |
| CN114004915A (en) | Picture editing method, device, equipment and storage medium | |
| CN109191701B (en) | Power metering method, system and server | |
| CN114495558B (en) | Parking space information processing method, detained vehicle platform and unified platform | |
| CN106941413B (en) | Service management method and device | |
| CN111524361A (en) | Method and device for processing vehicle in-out signals | |
| CN110597700A (en) | Server testing method and device | |
| CN112613745B (en) | Recorder management method, recorder management system, storage medium and electronic equipment | |
| CN116301456B (en) | Windows client login test management method, device and system | |
| CN112083960B (en) | Basic input/output system setting method | |
| CN115571072B (en) | Head-up display mode conversion method and device, electronic equipment and storage medium | |
| CN115113908A (en) | Method, terminal, computer device and storage medium for updating application programs in batch |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20221010 Address after: 518000 Guangdong province Shenzhen Longgang District Bantian Street five and Avenue North 4012 Yuan Zheng Industrial Park. Applicant after: LAUNCH TECH Co.,Ltd. Address before: 518000 522, headquarters office building of Yuanzheng technology plant, No. 4012, North Wuhe Avenue, Bantian street, Longgang District, Shenzhen, Guangdong Province Applicant before: Shenzhen Yuanzheng Future Automobile Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211109 |
|
| RJ01 | Rejection of invention patent application after publication |