A software processing method, device, electronic device and storage medium

Abstract

The present application is applicable to the field of software technology, and provides a software processing method, device, electronic device and storage medium. The transmission method is applied to a target device, and the transmission method includes: obtaining reference software information recorded by a server, wherein the reference software information is software information of software in the target device that is within the payment validity period; comparing the actual software information of the software in the target device with the reference software information, and determining abnormal software in the target device that is not within the payment validity period; deleting the execution file of the abnormal software, wherein the execution file is used to run the software service of the abnormal software. The embodiments of the present application can prevent users from using software after a refund, and prevent the manufacturer from losing profits due to malicious refunds by individual users.

Description

Technical Field

[0001] The present application belongs to the field of software technology, and in particular, relates to a software processing method, device, electronic device and storage medium. Background Art

[0002] Electronic device manufacturers or software design manufacturers often provide users with software installed on electronic devices to meet the different functional needs of users. Among them, there are often some paid software. In order to more conveniently meet the user's usage needs, users can often purchase software services online on electronic devices.

[0003] However, there are some individual users who immediately request a service refund after purchasing or upgrading software services. This practice greatly damages the interests of manufacturers. Summary of the invention

[0004] The embodiments of the present application provide a software processing method, device, electronic device and storage medium, which can prevent users from using refunded software and prevent the manufacturer's profit loss due to malicious refunds by individual users.

[0005] A first aspect of an embodiment of the present application provides a software processing method, which is applied to a target device. The processing method includes:

[0006] Acquire reference software information recorded by the server, wherein the reference software information is software information of software in the target device that is within the payment validity period;

[0007] Comparing the actual software information of the software in the target device with the reference software information to determine abnormal software in the target device that is not within the payment validity period;

[0008] The execution file of the abnormal software is deleted, where the execution file is used to run the software service of the abnormal software.

[0009] In some embodiments of the present application, the comparing the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the payment validity period includes: detecting whether the software in the target device is within the payment validity period; if not, comparing the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the payment validity period.

[0010] In some embodiments of the present application, the reference software information includes a reference version of the software in the target device that is within the payment validity period, and the actual software information includes the actual version of the software in the target device; comparing the actual software information of the software in the target device with the reference software information to determine abnormal software in the target device that is not within the payment validity period includes: comparing the reference version with the actual version, and treating the software whose actual version is higher than the reference version as the abnormal software.

[0011] In some embodiments of the present application, the reference software information includes a reference software identifier of software in the target device that is within a payment validity period, and the actual software information includes an actual software identifier of the software in the target device; comparing the actual software information of the software in the target device with the reference software information to determine abnormal software in the target device that is not within a payment validity period includes: comparing the reference software identifier with the actual software identifier, and treating the software for which there is no corresponding reference software identifier as the abnormal software.

[0012] In some embodiments of the present application, obtaining the reference software information recorded by the server includes: sending an acquisition request to the server, the acquisition request carrying the system identifier of the target device; and receiving the reference software information fed back by the server according to the system identifier.

[0013] In some embodiments of the present application, there are multiple execution files; deleting the execution files of the abnormal software includes: obtaining the storage path, storage name and deletion priority of each execution file; and deleting the execution files in sequence according to the storage path and storage name of each execution file in the order of the deletion priority.

[0014] In some implementations of the present application, the processing method further includes: detecting the duration of time that the target device is not connected to the Internet; if the duration of time that the target device is not connected to the Internet is greater than a duration threshold, stopping the software in the target device.

[0015] A second aspect of an embodiment of the present application provides a software processing device, which is configured in a target device, and the processing device includes:

[0016] An information acquisition unit, used to acquire reference software information recorded by a server, wherein the reference software information is software information of software in the target device that is within a paid validity period;

[0017] An information comparison unit, used to compare the actual software information of the software in the target device with the reference software information, and determine abnormal software in the target device that is not within the payment validity period;

[0018] The software processing unit is used to delete the execution file of the abnormal software, wherein the execution file is used to run the software service of the abnormal software.

[0019] A third aspect of an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0020] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0021] A fifth aspect of an embodiment of the present application provides a computer program product, which, when executed on an electronic device, enables the electronic device to implement the steps of the method.

[0022] In the implementation manner of the present application, the target device obtains the reference software information recorded by the server and compares the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the payment validity period, and then deletes the execution file of the abnormal software, so that the user cannot run the abnormal software in the target device that is not within the payment validity period, thereby avoiding the user from using the software after the refund, and preventing the manufacturer from losing profits due to malicious refunds by individual users. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 It is a schematic diagram of an implementation flow of a software processing method provided in an embodiment of the present application;

[0025] Figure 2 It is a schematic diagram of a specific implementation flow of a software processing method provided in an embodiment of the present application;

[0026] Figure 3 is a structural diagram of a software processing device provided in an embodiment of the present application;

[0027] Figure 4 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are protected by the present application.

[0029] At present, there are some individual users who immediately request a service refund after purchasing or upgrading the service software. This practice greatly damages the interests of the manufacturers.

[0030] In response to the above problems, the present application proposes a software processing method that can forcibly start the local program of the device to clean up the executable files of software for which no usage permission is granted, so that users cannot run abnormal software that is not within the paid validity period, thereby ensuring that the service software in the electronic device is consistent with the service software normally obtained by the user.

[0031] In order to illustrate the technical solution of the present application, a specific embodiment is provided below for illustration.

[0032] Figure 1 A schematic diagram of the implementation flow of a software processing method provided in an embodiment of the present application is shown. The method can be applied to a target device and is suitable for situations where it is necessary to prevent users from using software after a refund, so as to prevent the manufacturer from losing profits due to malicious refunds by individual users.

[0033] The target device may be an on-board diagnostics (OBD) system, which is usually composed of sensors, control computers and other hardware and can monitor the operation of the vehicle. The target device may also be other electronic devices that can install paid software.

[0034] Specifically, the software processing method may include the following steps S101 to S103.

[0035] Step S101, obtaining reference software information recorded by the server.

[0036] The reference software information is software information of software in the target device that is within the payment validity period, and may include but is not limited to reference versions of software in the target device that is within the payment validity period, reference software identifiers, etc.

[0037] Specifically, in some embodiments of the present application, the reference software information may be recorded in the server in the form of a list. The server may update the reference software information recorded in the software list each time it receives purchase information or refund information. In response to the user's refund operation, the server may obtain the version before the user's payment, and update the reference software version of the software pointed to by the refund information back to the version before the payment. If there is no version before the user's payment, the reference software identifier of the software may be deleted from the list.

[0038] In some implementations, the server may assign a unique system identifier to each target device, such as a system name, a system identification number (Identity document, ID), etc., and maintain a corresponding software list for each target device.

[0039] Correspondingly, the target device may send an acquisition request to the server, carrying its own system identifier in the acquisition request, and then receive the reference software information fed back by the server according to the system identifier.

[0040] Step S102, comparing the actual software information of the software in the target device with the reference software information to determine abnormal software in the target device that is not within the payment validity period.

[0041] In the implementation of the present application, the target device can obtain the configuration file of each software and then read the actual software information of the software. If the user performs a refund operation after the upgrade, the actual software information of the software in the target device will be inconsistent with the reference software information because the reference software information recorded in the server is sent and updated. If the user does not perform a refund operation, the actual software information of the software in the target device will be consistent with the reference software information. Therefore, by comparing the actual software information of the software in the target device with the reference software information, it is possible to determine the abnormal software in the target device that is not within the payment validity period.

[0042] Step S103, deleting the execution file of the abnormal software.

[0043] The above-mentioned execution file can be used to run the software service of the abnormal software. That is to say, after the abnormal software is determined, the execution file of the abnormal software can be deleted, thereby making the software unable to run normally.

[0044] In the implementation manner of the present application, the target device obtains the reference software information recorded by the server and compares the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the payment validity period, and then deletes the execution file of the abnormal software, so that the user cannot run the abnormal software in the target device that is not within the payment validity period, thereby avoiding the user from using the software after the refund, and preventing the manufacturer from losing profits due to malicious refunds by individual users.

[0045] Specifically, in some embodiments of the present application, the target device can detect whether the software in the target device is within the paid validity period; if so, it means that all the software in the target device is within the paid validity period, and no exception processing is required, and the user can use the software in the target device normally.

[0046] If it is detected that the software in the target device is not within the paid validity period, it means that there is software in the target device that is not within the paid validity period. Accordingly, it is necessary to compare the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the paid validity period, so as to prevent users from using abnormal software that is not within the paid validity period.

[0047] For example, user A purchased an onboard diagnostic device and configured one year of mainstream vehicle model software at the same time. The software upgrade and update service is valid until December 20, 2020. If the current date is December 10, 2020, the software in the target device is within the paid validity period, and no exception processing is required, and the user can use the software in the target device normally. If the current date is December 30, 2020, there is software in the target device that is not within the paid validity period, and it is necessary to determine the abnormal software in the target device that is not within the paid validity period.

[0048] Specifically, in some embodiments of the present application, the reference software information may include a reference version of the software in the target device that is within the paid validity period, and the actual software information may include the actual version of the software in the target device. The target device may compare the reference version with the actual version to determine whether the actual version is higher than the reference version. If the actual version is higher than the reference version, it means that the user has refunded the software after updating the software that is higher than the reference version. Therefore, the software with an actual version higher than the reference version can be regarded as abnormal software that is not within the paid validity period. If the actual version is lower than or equal to the reference version, it means that the software is within the paid validity period and can be used normally by the user.

[0049] For example, the validity period of software B in the target device of user A is December 20, 2020, the corresponding reference version is version 2.0, and the actual version of the software in the target device is version 3.0. If version 3.0 is higher than version 2.0, that is, user A upgraded the software to version 3.0 after December 20, 2020, and performed a service refund operation, then the software B can be confirmed as abnormal software.

[0050] In other embodiments of the present application, the above-mentioned reference software information may include the reference software identifier of the software in the target device that is within the payment validity period, and the actual software information may include the actual software identifier of the software in the target device. The target device may compare the reference software identifier with the actual software identifier to determine whether the actual software quantity is consistent with the software quantity recorded on the server. If the actual software quantity is inconsistent with the software quantity recorded on the server, it means that the user has refunded the software after updating the software that does not have the corresponding reference software identifier. Therefore, the software that does not have the corresponding reference software identifier can be regarded as abnormal software that is not within the payment validity period. If the actual software quantity is consistent with the software quantity recorded on the server, it means that there is no software that does not have the corresponding reference software identifier.

[0051] For example, user A only purchased software B in the target device, and the corresponding reference software identifier only has the identifier of software B, while the actual software identifiers of the software in the target device include the software identifiers of software B and software C, indicating that the actual number of software is greater than the number of software recorded on the server, that is, the user purchased software C and then executed the service refund operation for software C. At this time, the software C can be confirmed as abnormal software.

[0052] It should be noted that the target device can verify the software identifier and the software version at the same time, and when the target device contains multiple software, the actual software version of each software can be verified in turn.

[0053] If abnormal software is detected, the target device can call a local program to delete the executable software.

[0054] In some embodiments of the present application, there may be multiple execution files, and the target device may obtain the storage path, storage name, and deletion priority of each execution file, and then delete the execution files in sequence according to the order of deletion priority based on the storage path and storage name of each execution file.

[0055] Specifically, the above-mentioned execution files may include the license file, data files and other configuration files for the program to run. Among them, the deletion priority of the license file is the highest. The target device can delete the license file first according to the storage path and storage name pre-recorded by the staff, and then delete the data files and other configuration files. Since deletion takes a certain amount of time, deleting the license file first can ensure that the user stops using abnormal software as soon as possible.

[0056] It should be noted that the target device may execute the above processing method each time it connects to the network, or execute the above processing method at a certain time period.

[0057] In order to prevent users from being unable to use the software after a refund by disconnecting from the Internet, the target device can also detect the length of time the target device has been disconnected from the Internet. If the length of time the target device has been disconnected from the Internet is greater than a time threshold, the software in the target device will be stopped.

[0058] The duration threshold may be set according to actual conditions, for example, may be set to one month.

[0059] That is to say, if the user has not connected the target device to the Internet, then when the offline time exceeds the time threshold, the user will not be able to use the software in the target device. When the user connects the target device to the Internet before the offline time exceeds the time threshold, the target device can delete the executable file of the abnormal software according to the processing method provided in this application.

[0060] For example, assume that user A purchased an on-board diagnostic device and configured a year's worth of mainstream vehicle model software. The software upgrade service is valid until December 20, 2020. User A learned that the existing vehicle model software had added new functions. In order to meet the latest vehicle model diagnosis needs, he renewed the vehicle model software through online payment on the on-board diagnostic device, and the paid validity period of the vehicle model software was extended to January 10, 2022. He immediately downloaded the latest version of the software and applied for a refund. After receiving the refund information, the server will update the reference software information. During this period, after user A connects the on-board diagnostic device to the Internet, the on-board diagnostic device will force the local clearing task to delete the execution files of the abnormal software in user A's on-board diagnostic device. If user A chooses not to connect to the Internet at all times, and the time without connecting to the Internet is greater than the time threshold, the on-board diagnostic device will also prohibit the software from running.

[0061] In order to ensure normal use by users, the target device can provide users with a rollback version function after deleting the execution file of the abnormal software. Figure 2 As shown, the above software processing method may further include the following steps S201 to S203.

[0062] Step S201, generating a software list of software within the payment validity period according to the reference software information.

[0063] Step S202: receiving a download operation triggered by a user.

[0064] The download operation mentioned above refers to any one or more software in the software list.

[0065] Step S203: download the software pointed to by the download operation.

[0066] That is, in some embodiments of the present application, after obtaining the reference software information recorded by the server, the target device can generate a software list of software within the paid validity period according to the reference version, reference software identifier and other information, and display the software list. The user can select any one or more software according to the software list and trigger a download operation. After receiving the download operation triggered by the user, the target device can download the software pointed to by the download operation.

[0067] At this time, the user can download and use the software within the paid validity period, which may include the software currently within the paid validity period and the old version of the software within the last normal paid validity period.

[0068] In addition, in some embodiments of the present application, the above-mentioned target device can also record the number of times abnormal software appears. When the number of times abnormal software appears is greater than the number threshold, it means that the user often performs malicious refund operations, and the software in the target device can be stopped.

[0069] The number threshold can be set according to actual conditions, for example, it can be set to 3.

[0070] It should be noted that, for the sake of simplicity of description, the aforementioned method embodiments are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited to the described order of actions, because according to the present application, certain steps can be performed in other orders.

[0071] like Figure 3 FIG. 1 is a schematic diagram of the structure of a software processing device 300 provided in an embodiment of the present application, wherein the software processing device 300 is configured on a target device.

[0072] Specifically, the software processing device 300 may include:

[0073] The information acquisition unit 301 is used to acquire the reference software information recorded by the server, wherein the reference software information is the software information of the software in the target device that is within the payment validity period;

[0074] An information comparison unit 302 is used to compare the actual software information of the software in the target device with the reference software information to determine abnormal software in the target device that is not within the payment validity period;

[0075] The software processing unit 303 is used to delete the execution file of the abnormal software, where the execution file is used to run the software service of the abnormal software.

[0076] In some embodiments of the present application, the above-mentioned information comparison unit 302 can also be specifically used to: detect whether the software in the target device is within the payment validity period; if not, compare the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the payment validity period.

[0077] In some embodiments of the present application, the above-mentioned reference software information may include a reference version of the software in the target device that is within the payment validity period, and the actual software information may include the actual version of the software in the target device; the above-mentioned information comparison unit 302 can also be specifically used to: compare the reference version with the actual version, and treat the software whose actual version is higher than the reference version as the abnormal software.

[0078] In some embodiments of the present application, the above-mentioned reference software information may include a reference software identifier of software in the target device that is within the payment validity period, and the actual software information may include an actual software identifier of the software in the target device; the above-mentioned information comparison unit 302 may also be specifically used to: compare the reference software identifier with the actual software identifier, and treat the software that does not have a corresponding reference software identifier as the abnormal software.

[0079] In some implementations of the present application, the information acquisition unit 301 may also be specifically used to: send an acquisition request to the server, the acquisition request carrying the system identifier of the target device; and receive the reference software information fed back by the server according to the system identifier.

[0080] In some embodiments of the present application, there are multiple execution files; the software processing unit 303 can also be specifically used to: obtain the storage path, storage name and deletion priority of each execution file; and delete the execution files in sequence according to the storage path of each execution file and the storage name of each execution file in the order of the deletion priority.

[0081] In some embodiments of the present application, the software processing unit 303 may also be specifically used to: detect the offline time of the target device; if the offline time is greater than a time threshold, stop running the software in the target device.

[0082] In some embodiments of the present application, the above-mentioned software processing unit 303 can also be specifically used to: generate a software list of software that is within the payment validity period based on the reference software information; receive a download operation triggered by a user, and the download operation points to any one or more software in the software list; and download the software pointed to by the download operation.

[0083] It should be noted that, for the convenience and simplicity of description, the specific working process of the software processing device 300 can be referred to Figure 1 to Figure 2 The corresponding process of the method will not be repeated here.

[0084] like Figure 4 , which is a schematic diagram of an electronic device provided in an embodiment of the present application, wherein the electronic device may be a vehicle-mounted terminal device, or other terminal devices capable of installing paid software.

[0085] The electronic device 4 may include: a processor 40, a memory 41, and a computer program 42 stored in the memory 41 and executable on the processor 40, such as a software processing program. When the processor 40 executes the computer program 42, the steps in the above-mentioned software processing method embodiments are implemented, such as Figure 1 Alternatively, when the processor 40 executes the computer program 42, the functions of each module / unit in the above-mentioned device embodiments are realized, for example Figure 3 The information acquisition unit 301, the information comparison unit 302 and the software processing unit 303 are shown.

[0086] The computer program may be divided into one or more modules / units, which are stored in the memory 41 and executed by the processor 40 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program in the electronic device.

[0087] For example, the computer program may be divided into: an information acquisition unit, an information comparison unit and a software processing unit.

[0088] The specific functions of each unit are as follows: an information acquisition unit, used to acquire reference software information recorded by a server, wherein the reference software information is software information of software in the target device that is within the payment validity period; an information comparison unit, used to compare actual software information of the software in the target device with the reference software information, and determine abnormal software in the target device that is not within the payment validity period; a software processing unit, used to delete the execution file of the abnormal software, wherein the execution file is used to run the software service of the abnormal software.

[0089] The electronic device may include, but is not limited to, a processor 40 and a memory 41. Those skilled in the art will appreciate that Figure 4 These are merely examples of electronic devices and do not constitute a limitation of the electronic device. The electronic device may include more or fewer components than those shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

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

[0091] The memory 41 may be an internal storage unit of the electronic device, such as a hard disk or memory of the electronic device. The memory 41 may also be an external storage device of the electronic device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Further, the memory 41 may also include both an internal storage unit of the electronic device and an external storage device. The memory 41 is used to store the computer program and other programs and data required by the electronic device. The memory 41 may also be used to temporarily store data that has been output or is to be output.

[0092] It should be noted that, for the convenience and brevity of description, the structure of the above electronic device can also refer to the specific description of the structure in the method embodiment, which will not be repeated here.

[0093] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0094] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0095] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

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

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

[0099] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0100] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A software processing method, characterized in that: Applied to the target device, the processing method includes: Acquire reference software information recorded by the server, the reference software information being software information of the target device within the payment validity period; the reference software information includes a reference version and a reference software identifier of the software of the target device within the payment validity period; Comparing the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the payment validity period; the actual software information includes the actual version and actual software identifier of the software in the target device; Deleting an execution file of the abnormal software, wherein the execution file is used to run the software service of the abnormal software; The step of comparing the actual software information of the software in the target device with the reference software information to determine the abnormal software in the target device that is not within the payment validity period includes: detecting whether the software in the target device is within the payment validity period; if not, comparing the reference version with the actual version, and treating the software whose actual version is higher than the reference version as the abnormal software; The method of comparing the actual software information of the software in the target device with the reference software information to determine abnormal software in the target device that is not within the payment validity period also includes: comparing the reference software identifier with the actual software identifier, and treating the software that does not have a corresponding reference software identifier as the abnormal software.

2. The software processing method according to claim 1, characterized in that: The obtaining of the reference software information recorded by the server includes: Sending an acquisition request to the server, wherein the acquisition request carries a system identifier of the target device; The reference software information fed back by the server according to the system identifier is received.

3. The software processing method according to claim 1, characterized in that: The number of the execution files is multiple; The deleting the execution file of the abnormal software includes: Obtaining the storage path, storage name and deletion priority of each of the executable files; The execution files are deleted in sequence according to the order of the deletion priority according to the storage paths and storage names of the execution files.

4. The software processing method according to any one of claims 1 to 3, characterized in that: The processing method also includes: Detecting the length of time the target device has been offline; If the offline time is longer than the time threshold, the software in the target device is stopped.

5. A software processing device, characterized in that: Configured in the target device, the processing device includes: An information acquisition unit, used to acquire reference software information recorded by a server, wherein the reference software information is software information of software in the target device that is within the payment validity period; the reference software information includes a reference version and a reference software identifier of the software in the target device that is within the payment validity period; An information comparison unit, used to compare the actual software information of the software in the target device with the reference software information, and determine the abnormal software in the target device that is not within the payment validity period; the actual software information includes the actual version and actual software identifier of the software in the target device; A software processing unit, used to delete an execution file of the abnormal software, wherein the execution file is used to run a software service of the abnormal software; The information comparison unit is used to detect whether the software in the target device is within the payment validity period; if not, the reference version is compared with the actual version, and the software whose actual version is higher than the reference version is regarded as the abnormal software; The information comparison unit is further used to compare the reference software identifier with the actual software identifier, and to regard the software that does not have a corresponding reference software identifier as the abnormal software.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images