CN111475819B - Method and device for identifying abnormal terminal equipment, storage medium and electronic equipment - Google Patents
Method and device for identifying abnormal terminal equipment, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111475819B CN111475819B CN202010329084.9A CN202010329084A CN111475819B CN 111475819 B CN111475819 B CN 111475819B CN 202010329084 A CN202010329084 A CN 202010329084A CN 111475819 B CN111475819 B CN 111475819B
- Authority
- CN
- China
- Prior art keywords
- installation
- terminal equipment
- terminal device
- abnormal
- record file
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure relates to the technical field of computers, and provides a method and a device for identifying abnormal terminal equipment, a computer readable storage medium and electronic equipment, wherein the method comprises the following steps: acquiring an installation record file corresponding to a target application from a public directory of the terminal equipment; and judging whether the terminal equipment is abnormal terminal equipment or not according to the installation record file. The method and the device can judge whether the terminal equipment is abnormal terminal equipment or not through installing the record file, so that the efficiency of identifying the abnormal terminal equipment is improved, and system resources are saved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method for identifying an abnormal terminal device, an apparatus for identifying an abnormal terminal device, a computer readable storage medium, and an electronic device.
Background
With the development of internet technology, more and more unstable factors are in the network, and there are often some abnormal users who register a large number of accounts and use automation technology to impersonate normal users to benefit. For example, an abnormal user can avoid the detection of an application server by uninstalling and reinstalling the application or using an automation technology to modify the model or the IP of the terminal device and then logging in the application using a different account number.
In view of this, there is a need in the art to develop a new method and apparatus for identifying abnormal terminal devices.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure aims to provide a method for identifying an abnormal terminal device, an apparatus for identifying an abnormal terminal device, a computer-readable storage medium, and an electronic device, thereby improving the efficiency of identifying an abnormal terminal device at least to some extent.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.
According to an aspect of the present disclosure, there is provided a method of identifying an abnormal terminal device, the method comprising: acquiring an installation record file corresponding to a target application from a public directory of the terminal equipment; and judging whether the terminal equipment is abnormal terminal equipment or not according to the installation record file.
In some exemplary embodiments of the present disclosure, the method further comprises: and responding to an uninstalling instruction aiming at the target application, deleting an associated file corresponding to the target application in a private directory of the terminal equipment according to the uninstalling instruction, and reserving an installation record file corresponding to the target application in a public directory of the terminal equipment.
In some exemplary embodiments of the present disclosure, the installation record file includes one or more installation times; judging whether the terminal equipment is abnormal terminal equipment according to the installation record file, comprising: acquiring one or more installation times in the installation record file, and determining the installation times in a preset time according to each installation time; judging whether the installation times are larger than an installation times threshold value or not; and when the installation times are larger than the installation times threshold, judging that the terminal equipment is the abnormal terminal equipment.
In some exemplary embodiments of the present disclosure, the installation record file includes one or more terminal device models; judging whether the terminal equipment is abnormal terminal equipment according to the installation record file, comprising: acquiring one or more terminal equipment models in the installation record file, and determining the number of the models recorded on the terminal equipment according to each terminal equipment model; judging whether the model number is larger than a model number threshold; and when the model number is larger than the model number threshold, judging that the terminal equipment is the abnormal terminal equipment.
In some exemplary embodiments of the present disclosure, the installation record file includes one or more installation times and a terminal device model; judging whether the terminal equipment is abnormal terminal equipment according to the installation record file, comprising: acquiring one or more installation times in the installation record file, and determining the installation times in a preset time according to each installation time; acquiring one or more terminal equipment models in the installation record file, and determining the number of the models recorded on the terminal equipment according to each terminal equipment model; calculating the installation frequency in a weighting manner according to the installation times and the model number, and judging whether the installation frequency is larger than an installation frequency threshold value or not; and when the installation frequency is larger than the installation frequency threshold value, judging that the terminal equipment is the abnormal terminal equipment.
In some exemplary embodiments of the present disclosure, the method further comprises: judging whether an installation record file corresponding to the target application exists in the public directory; if the current installation time and the current terminal equipment model number are recorded in the installation record file, the installation record file corresponding to the target application is created in the public directory through the target application.
In some exemplary embodiments of the present disclosure, the method further comprises: marking the abnormal terminal equipment according to the unique identification of the abnormal terminal equipment, and marking an abnormal account according to account information corresponding to the abnormal terminal equipment and related to the target application.
In some exemplary embodiments of the present disclosure, the method further comprises: judging whether the private directory of the terminal equipment contains a first starting identifier corresponding to the target application or not; if yes, judging whether the terminal equipment is the abnormal terminal equipment according to the unique identifier of the terminal equipment; if not, the first starting identification is recorded in the private directory, and whether the terminal equipment is the abnormal terminal equipment is judged according to the installation record file.
In some exemplary embodiments of the present disclosure, determining whether the terminal device is the abnormal terminal device according to the unique identifier of the terminal device includes: comparing the unique identifier of the terminal equipment with the unique identifier of the abnormal terminal equipment; and when the unique identifier of the terminal equipment is consistent with the unique identifier of the abnormal terminal equipment, judging that the terminal equipment is the abnormal terminal equipment.
In some exemplary embodiments of the present disclosure, the method further comprises: and acquiring a number of installation times sample and a model number sample of other terminal equipment corresponding to the target application, and calculating the number of installation times threshold, the model number threshold and the installation frequency threshold according to the number of installation times sample and the model number sample.
In some exemplary embodiments of the present disclosure, the method further comprises: obtaining a frequency sample of installation of other terminal equipment corresponding to the target application, and determining the frequency threshold according to the frequency sample of installation through a first preset rule.
In some exemplary embodiments of the present disclosure, the method further comprises: and obtaining model number samples of other terminal equipment corresponding to the target application, and determining the model number threshold value according to the model number samples through a second preset rule.
In some exemplary embodiments of the present disclosure, the method further comprises: obtaining a number of installation times sample and a model number sample of other terminal equipment corresponding to the target application, calculating an installation frequency sample according to the number of installation times sample and the model number sample in a weighting mode, and determining the installation frequency threshold according to the installation frequency sample through a third preset rule.
According to an aspect of the present disclosure, there is provided an apparatus for identifying an abnormal terminal device, the apparatus including: the response module is used for acquiring an installation record file corresponding to the target application from the public directory of the terminal equipment; and the judging module is used for judging whether the terminal equipment is abnormal terminal equipment according to the installation record file.
According to an aspect of the present disclosure, there is provided a computer-readable medium having stored thereon a computer program which, when executed by a processor, implements a method of identifying an abnormal terminal device as described in the above embodiments.
According to one aspect of the present disclosure, there is provided an electronic device including: one or more processors; and a storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method of identifying an abnormal terminal device as described in the above embodiments.
As can be seen from the above technical solutions, the method and apparatus for identifying an abnormal terminal device, the computer-readable storage medium, and the electronic device in the exemplary embodiments of the present disclosure have at least the following advantages and positive effects:
According to the method for identifying the abnormal terminal equipment, on one hand, the installation record file corresponding to the target application is obtained from the public directory of the terminal equipment, so that the effectiveness of operation is improved, and the accuracy of identifying the abnormal terminal equipment is ensured; on the other hand, whether the terminal equipment is abnormal terminal equipment is judged according to the installation record file, so that a method for judging the abnormal terminal equipment is simplified, the efficiency of identifying the abnormal terminal equipment is improved, and the cost of system resources is saved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
Fig. 1 schematically illustrates a flow diagram for identifying an abnormal terminal device according to an embodiment of the present disclosure;
fig. 2 schematically illustrates a flowchart for identifying an abnormal terminal device according to an installation time in an installation record file according to an embodiment of the present disclosure;
Fig. 3 schematically illustrates a flowchart of identifying an abnormal terminal device according to a terminal device model in an installation record file according to an embodiment of the present disclosure;
Fig. 4 schematically illustrates a flowchart of identifying an abnormal terminal device according to an installation time and a terminal device model in an installation record file according to an embodiment of the present disclosure;
Fig. 5 schematically illustrates a flow diagram for identifying an abnormal terminal device according to a unique identification of the terminal device according to an embodiment of the present disclosure;
fig. 6 schematically illustrates a flow diagram for identifying an abnormal terminal device according to an embodiment of the present disclosure;
fig. 7 schematically illustrates a block diagram of an apparatus for identifying an abnormal terminal device according to an embodiment of the present disclosure;
FIG. 8 schematically illustrates a block diagram of an electronic device according to an embodiment of the disclosure;
Fig. 9 schematically illustrates a program product schematic according to an embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed aspects may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
In related art in the field, an application software server determines whether the terminal device is an abnormal terminal device according to information such as an IP, a unique identifier of the terminal device, and a terminal device model reported by application software, for example, whether the terminal device is an abnormal terminal device according to whether the same terminal device model or the same unique identifier of the terminal device logs in a large number of different accounts within a preset time. However, the terminal device can enable the application software to regenerate the unique identifier of the terminal device by uninstalling and reinstalling the application software, or enable the unique identifier of the terminal device and the terminal device model to be different when the application software calls the system api each time through a hook technology. Therefore, the accuracy of the method of judging an abnormal terminal device according to the above method is low.
Based on the problems existing in the related art, a method of identifying an abnormal terminal device is proposed in one embodiment of the present disclosure. Fig. 1 shows a schematic flow chart of identifying an abnormal terminal device, and as shown in fig. 1, the method for identifying an abnormal terminal device at least comprises the following steps:
step S110: acquiring an installation record file corresponding to a target application from a public directory of the terminal equipment;
step S120: and judging whether the terminal equipment is abnormal terminal equipment or not according to the installation record file.
On one hand, the method for identifying the abnormal terminal equipment in the embodiment of the disclosure improves the effectiveness of operation and ensures the accuracy of identifying the abnormal terminal equipment by acquiring the installation record file corresponding to the target application in the public directory of the terminal equipment; on the other hand, whether the terminal equipment is abnormal terminal equipment is judged according to the installation record file, so that a method for judging the abnormal terminal equipment is simplified, the efficiency of identifying the abnormal terminal equipment is improved, and the cost of system resources is saved.
It should be noted that, the method for identifying an abnormal terminal device provided by the exemplary embodiment of the present disclosure is generally performed by a server, and accordingly, the apparatus for identifying an abnormal terminal device is generally provided in the server. In other exemplary embodiments of the present disclosure, however, the terminal device may also have a similar function to the server, so as to perform the method for identifying an abnormal terminal device provided by the embodiment of the present invention.
In order to make the technical solution of the present disclosure clearer, each step of the method for identifying an abnormal terminal device will be described next.
In step S110, an installation record file corresponding to the target application is acquired in the public directory of the terminal device.
In an exemplary embodiment of the present disclosure, the public directory of the terminal device is an external storage space of the terminal device, and files in the external storage space are not deleted along with the uninstallation of the application software. The private directory of the terminal equipment is the internal storage space of the terminal equipment, and files in the internal storage space can be deleted along with the unloading of the application software.
In an exemplary embodiment of the present disclosure, in response to an installation instruction for a target application, a server creates an association file corresponding to the target application in a private directory of a terminal device according to the installation instruction, and creates an installation record file corresponding to the target application in a public directory of the terminal device. The installation instruction comprises an application identifier corresponding to the target application, and the installation instruction is formed according to an installation triggering operation for the target application, for example, the installation triggering operation comprises the steps that a user searches for the target application in an application software installation market of the terminal equipment, and clicks the target application to install the target application on the terminal equipment.
The association file of the target application comprises a first starting identifier corresponding to the target application, account information for logging in the target application and the like, and the installation record file of the target application comprises installation time and/or terminal equipment model and the like corresponding to the target application. Each time a target application is installed on a terminal device, an installation record is formed in an installation record file related to the target application in a public directory of the terminal device, the installation record comprises installation time and/or a terminal device model and the like, and an association record is formed in an association file related to the target application in a private directory, and the association record comprises a first starting identifier, account information for logging in the target application and the like. Therefore, the number of installation times and terminal device models corresponding to the target application may be one or plural, which is not particularly limited in the present disclosure.
In an exemplary embodiment of the present disclosure, in response to an uninstall instruction for a target application, deleting an association file corresponding to the target application in a private directory of a terminal device according to the uninstall instruction; and reserving an installation record file corresponding to the target application in the public directory of the terminal equipment. The uninstall instruction is formed according to an uninstall triggering operation aiming at the target application, for example, a user clicks the target application on the terminal device and selects an uninstall option.
In an exemplary embodiment of the present disclosure, it is determined whether an installation record file corresponding to a target application exists in a public directory of a terminal device; if the public directory does not contain the installation record file corresponding to the target application, the target application is installed on the terminal equipment for the first time, the installation record file corresponding to the target application is created in the public directory of the terminal equipment through the target application, and the current installation time and the current terminal equipment model are recorded in the installation record file; if the installation record file corresponding to the target application exists in the public directory, which indicates that the target application is not installed for the first time on the terminal equipment, the current installation time and the current terminal equipment model are recorded in the record file.
In step S120, it is determined whether the terminal device is an abnormal terminal device based on the installation record file.
In an exemplary embodiment of the present disclosure, a method for determining whether a terminal device is an abnormal terminal device according to an installation record file includes at least three kinds of following:
First, if a terminal device uninstalls and reinstalls a target application a plurality of times in a short time, the terminal device is likely to be an abnormal terminal device, and thus, whether the terminal device is an abnormal terminal device can be judged by installing the installation time in the record file. Fig. 2 is a schematic flow chart for identifying an abnormal terminal device according to the installation time in the installation record file, and as shown in fig. 2, whether the terminal device is an abnormal terminal device is judged according to the installation time in the installation record file, and the judging process is described in detail as follows:
In step S210, one or more installation times in the installation record file are acquired, and the number of installation times in the preset time is determined according to the installation time.
In an exemplary embodiment of the present disclosure, installation times within a preset time from a current time are obtained in one or more installation times, and the number of installation times is determined according to the number of installation times within the preset time, wherein the preset time may be defined according to practical situations, the preset time may be set to 1 hour, or may be set to 24 hours, or may be set to one week or one month, and a change of the preset time should be understood to be all within the scope of the present disclosure.
For example, assume that the installation time in the installation record file corresponding to the target application includes "2020.04.06:08:03; 2020.04.06 09:18;2020.04.06 10:10;2020.04.06 12:20;2020.04.07 08.30", the preset time is set to 12 hours, and the number of installation times in the preset time corresponding to the target application is 4.
In step S220, it is determined whether the number of installations is greater than the installation number threshold.
In an exemplary embodiment of the present disclosure, an installation number sample of other terminal devices corresponding to a target application is obtained, and an installation number threshold is determined according to the installation number sample through a first preset rule.
The first preset rule may take an average value of the installation number samples as an installation number threshold, or N times of the average value of the installation number samples as the installation number threshold, where the value of N may be set according to a specific situation, for example, N may be 5 or 10, where the value of N is not specifically limited in this disclosure.
In addition, the same method for determining the installation times of the target application in the terminal equipment is used for obtaining the installation times samples of other terminal equipment corresponding to the target application, and one terminal equipment corresponds to one installation times sample. The terminal device corresponding to the installation frequency sample may be selected at will from all terminal devices for installing the target application, or may be selected according to different areas, which is not specifically limited in the disclosure.
The number of the installation number samples may be set according to actual situations, may be determined according to the total number of terminal devices for installing the target application, and may also be set according to the release time of the target application, for example, the number of the installation number samples may be set to 50% -100% of the total number of the terminal devices, and the number of the installation number samples is not particularly limited in the disclosure.
In step S230, when the number of installations is greater than the threshold number of installations, it is determined that the terminal device is an abnormal terminal device.
In an exemplary embodiment of the present disclosure, when the number of installations is greater than the threshold number of installations, it is indicated that the terminal device is uninstalled and reinstalled the target application multiple times within a preset time, and thus, the terminal device is marked as an abnormal terminal device.
Second, since the terminal device model recorded in the installation record file is obtained by calling the api provided by the application system of the terminal device, the terminal device can make the terminal device model obtained by the server when the system api is called each time inconsistent through the hook technology. Therefore, it is possible to judge whether the terminal device is an abnormal terminal device by installing the terminal device model in the record file. Fig. 3 is a schematic flow chart of identifying an abnormal terminal device according to a terminal device model in an installation record file, and as shown in fig. 3, judging whether the terminal device is an abnormal terminal device according to the terminal device model in the installation record file, the judging process is described in detail as follows:
in step S310, one or more terminal device models in the installation record file are acquired, and the number of models recorded on the terminal device is determined according to the terminal device model.
In the exemplary embodiment of the present disclosure, one or more terminal device models in the installation record file may be the same or different, and thus, the terminal device models are compared, different terminal device models are recorded, and the number of models is counted.
In step S320, it is determined whether the model number is greater than a model number threshold.
In an exemplary embodiment of the present disclosure, a model number sample of other terminal devices corresponding to a target application is obtained, and a model number threshold is determined according to the model number sample through a second preset rule. The second preset rule may take an average value of the model number samples as a model number threshold, or may take M times of the average value of the model number samples as a model number threshold, where the value of M may be set according to a specific situation, for example, the value of M may be 2 or 5, and the value of M is not specifically limited in this disclosure.
In addition, the same method for determining the model number of the target application in the terminal equipment is used for obtaining model number samples of other terminal equipment corresponding to the target application, and one terminal equipment corresponds to one model number sample.
The terminal devices corresponding to the number of model samples may be selected at will from all terminal devices for installing the target application, or may be selected according to different areas, which is not specifically limited in the disclosure.
And, the number of the model number samples can be set according to actual conditions, can be determined according to the total number of terminal devices for installing the target application, and can also be set according to the release time of the target application, for example, the number of the model number samples can be set to be 50% -100% of the total number of the terminal devices, and the number of the model number samples is not particularly limited in the disclosure.
In step S330, when the number of models is greater than the threshold number of models, it is determined that the terminal device is an abnormal terminal device.
In an exemplary embodiment of the present disclosure, a number of models greater than the number of models threshold indicates that a plurality of terminal device models are used when installing the target application on the same terminal device, and the terminal device is marked as an abnormal terminal device.
Third, fig. 4 is a schematic flow chart of identifying an abnormal terminal device according to the installation time and the terminal device model in the installation record file, and as shown in fig. 4, it is determined whether the terminal device is an abnormal terminal device according to the installation time and the terminal device model in the installation record file, and the determination process is described in detail as follows:
In step S410, one or more installation times in the installation record file are acquired, and the number of installation times in the preset time is determined according to the installation time.
In an exemplary embodiment of the present disclosure, one or more installation times are obtained from the installation times within a preset time from the current time, and the number of installation times is determined according to the number of installation times within the preset time.
In step S420, one or more terminal device models in the installation record file are acquired, and the number of models recorded on the terminal device is determined according to the terminal device models.
In the exemplary embodiment of the present disclosure, one or more terminal device models in the installation record file may be the same or different, and thus, the terminal device models are compared, different terminal device models are recorded, and the number of models is counted.
In step S430, the installation frequency is calculated by weighting according to the number of installations and the number of models, and it is determined whether the installation frequency is greater than an installation frequency threshold.
In an exemplary embodiment of the present disclosure, the installation frequency is weighted according to the number of installations and the number of models. In practical application, the model number of the terminal equipment in the installation record file of the normal terminal equipment is not changed, if the model number of the terminal equipment is changed, the probability of being the abnormal terminal equipment is larger, and therefore the weighting proportion of the model number in the installation frequency can be set relatively larger. For example, the weight specific gravity of the number of installations is set to 20%, and the weight specific gravity of the number of models is set to 80%, although the weight specific gravity of the number of installations and the number of models may be set according to actual conditions, and the weight specific gravity may be updated with the lapse of time, which is not particularly limited in the present disclosure.
In an exemplary embodiment of the present disclosure, a number of installation times sample and a model number sample of other terminal devices corresponding to a target application are acquired, an installation frequency sample is calculated by weighting according to the number of installation times sample and the model number sample, and an installation frequency threshold is determined according to the installation frequency sample through a third rule.
The third preset rule may take an average value of the installation frequency samples as an installation frequency threshold, or may take R times of the average value of the installation frequency samples as an installation frequency threshold, where the value of R may be set according to a specific situation, for example, the value of R may be 3 or 8, and the value of R is not specifically limited in this disclosure.
In addition, the same method for determining the number of installation times and the number of types of the target application in the terminal equipment is used for obtaining the number of installation times samples and the number of types of other terminal equipment corresponding to the target application, and one terminal equipment corresponds to one number of installation times sample and one number of types sample. The terminal devices corresponding to the installation times samples and the model number samples can be selected at will from all terminal devices for installing the target application, and can also be selected according to different areas, which is not particularly limited in the disclosure.
And, the number of the installation number of samples and the number of the model number of samples may be set according to the actual situation, may be determined according to the total number of the terminal devices for installing the target application, and may also be set according to the pushing time of the target application, for example, the number of the installation number of samples and the number of the model number of samples may be set to 50% -100% of the total number of the terminal devices, and the number of the installation number of samples and the number of the model number of samples is not particularly limited in the disclosure.
In step S440, when the installation frequency is greater than the installation frequency threshold value, it is determined that the terminal device is an abnormal terminal device.
In an exemplary embodiment of the present disclosure, an abnormal terminal device is marked according to a unique identifier of the abnormal terminal device, and specifically, a unique identifier corresponding to the terminal device may be stored in an abnormal terminal device directory, so that a server identifies the abnormal terminal device according to the unique identifier of the abnormal terminal device. In addition, the abnormal account is marked according to account information corresponding to the abnormal terminal equipment and related to the target application. After the abnormal terminal equipment is identified by the method for identifying the abnormal terminal equipment, marking the abnormal terminal equipment according to the unique identification corresponding to the abnormal terminal equipment, and marking all accounts which are registered on the abnormal terminal equipment and related to the target application as abnormal accounts. Further, the unique identifier corresponding to the terminal device may be shared to the server corresponding to other application software, so that the other application software server may identify the abnormal account corresponding to other application software according to the abnormal terminal device.
In an exemplary embodiment of the present disclosure, determining whether a terminal device is an abnormal terminal device according to an installation record file includes: and determining the frequency and/or the frequency of the installation of the target application by the terminal equipment according to the installation record file, and judging whether the terminal equipment is abnormal terminal equipment according to the frequency and/or the frequency. For example, when the number of times is greater than the number of times threshold, judging that the terminal equipment is abnormal terminal equipment, otherwise, judging that the terminal equipment is normal terminal equipment; for another example, when the frequency (repeatedly installed in a period of time) is greater than the frequency threshold, judging that the terminal equipment is abnormal terminal equipment, otherwise, judging that the terminal equipment is normal terminal equipment; or judging whether the terminal equipment is abnormal or not according to the times and the frequency.
In the exemplary embodiment of the present disclosure, since the terminal device determines whether the terminal device is an abnormal terminal device according to the installation record file corresponding to the target application when the terminal device starts the target application for the first time, and marks the abnormal terminal device according to the unique identifier of the abnormal terminal device. Therefore, in order to save system loss and improve the efficiency of identifying the abnormal terminal device, when the terminal device is a target application for non-first start, the abnormal terminal device can be identified according to the unique identifier of the terminal device. Fig. 5 shows a schematic flow chart for identifying an abnormal terminal device according to a unique identifier of the terminal device, specifically including the following steps:
step S510, judging whether a first starting identifier corresponding to the target application exists in the private directory of the terminal equipment.
In an exemplary embodiment of the present disclosure, an association file corresponding to a target application is found in a private directory of a terminal device, and whether a first start identifier exists in the association file is determined.
Step S520, if there is a first start identifier corresponding to the target application in the private directory of the terminal device, judging whether the terminal device is an abnormal terminal device according to the unique identifier of the terminal device.
In an exemplary embodiment of the present disclosure, when a terminal device first starts a target application after installation, a first start identifier is recorded in an association file, and if the first start identifier exists in the association file, it indicates that the current start is not the first start.
In an exemplary embodiment of the present disclosure, the unique identification of the terminal device is compared with the unique identification of the abnormal terminal device in the abnormal terminal device directory; if the unique identifier of the terminal equipment exists in the abnormal terminal equipment catalog, judging that the terminal equipment is abnormal terminal equipment; if the unique identifier of the terminal equipment does not exist in the abnormal terminal equipment catalog, judging that the terminal equipment is normal terminal equipment.
Specifically, if the first starting identifier corresponding to the target application exists in the private directory, the fact that the target application is not installed and started for the first time is indicated, and when the target application is started for the first time by the terminal equipment, the abnormal terminal equipment is marked according to the unique identifier of the terminal equipment, at this time, only the unique identifier of the terminal equipment is required to be compared with the stored unique identifier of the abnormal terminal equipment, if the unique identifier of the terminal equipment is consistent with the unique identifier of the abnormal terminal equipment, the terminal equipment is judged to be the abnormal terminal equipment, and if the unique identifier of the terminal equipment is inconsistent with the unique identifier of the abnormal terminal equipment, the terminal equipment is judged to be the normal terminal equipment; if the first starting identification corresponding to the target application does not exist in the private directory, judging whether the terminal equipment is abnormal terminal equipment or not according to the installation record file.
Step S530, if the private directory of the terminal device does not have the first starting identifier corresponding to the target application, and judging whether the terminal device is an abnormal terminal device according to the installation record file.
In an exemplary embodiment of the present disclosure, when there is no first start identifier in an association file corresponding to a target application, the first start identifier is recorded in the association file, and whether the terminal device is an abnormal terminal device is determined according to the above method for identifying an abnormal terminal device.
Fig. 6 is a schematic flow chart for identifying an abnormal terminal device according to a specific embodiment of the present disclosure, which is an illustration of the above steps in the present exemplary embodiment, as shown in fig. 6, and the specific steps are as follows:
in step S610, in response to the start trigger operation for the target application, the target application is started according to the start trigger operation.
In an exemplary embodiment of the present disclosure, the launching triggering operation includes clicking on a target application on the terminal device, and may further include selecting an icon of the target application to be clicked on among other application software to install and launch the target application. The server receives a starting request corresponding to a starting triggering operation, wherein the starting request comprises a target application identifier corresponding to a target application, the starting request also comprises starting time for starting the target application, and the starting request can also comprise the terminal equipment model, the terminal equipment ID and the like.
In step S620, it is determined whether the current start-up is the first start-up after installation.
In an exemplary embodiment of the present disclosure, a server receives the start request, searches a first start identifier corresponding to a target application in a private directory of a terminal device according to the target application identifier in the start request, and determines whether the current start is the first start after installation according to whether the first start identifier exists in the private directory.
In step S630, if the current startup is not the first startup after installation, the unique identifier of the terminal device is obtained, and the abnormal terminal device is identified according to the unique identifier.
In an exemplary embodiment of the present disclosure, if a first start identifier corresponding to a target application does not exist in a private directory of a terminal device, it is determined that the currently started target application is not first started after installation.
In the exemplary embodiment of the present disclosure, since the server determines that the terminal device uses the method of identifying the abnormal terminal device in the above-described exemplary embodiment when the target application is started for the first time.
If the terminal device is an abnormal terminal device, the unique identifier corresponding to the abnormal terminal device is used for marking, and the method for marking the abnormal terminal device can be that the unique identifier of the abnormal terminal device is stored in an abnormal terminal device catalog, or other marking methods can be used, and the method for marking the abnormal terminal device is not particularly limited in the disclosure.
Therefore, if the current starting is not the first starting after installation, comparing the unique identifier of the terminal equipment with the unique identifier of the abnormal terminal equipment in the abnormal terminal equipment catalog, and if the unique identifier of the terminal equipment exists in the abnormal terminal equipment catalog, judging that the terminal equipment is the abnormal terminal equipment; if the unique identifier of the terminal equipment does not exist in the abnormal terminal equipment catalog, judging that the terminal equipment is normal terminal equipment. According to the method for identifying the abnormal terminal equipment, the abnormal terminal equipment is identified by using the installation record file only when the target application is started for the first time, and the abnormal terminal equipment can be identified by using the unique identification of the terminal equipment only when the target application is not started for the first time, so that the situation that the installation record file is acquired once and the abnormal terminal equipment is judged every time when the target application is started is avoided, and the system loss is saved.
In step S640, if the current start is the first start after installation, it is determined in the public directory of the terminal device whether or not there is an installation record file corresponding to the target application.
In the exemplary embodiment of the present disclosure, although the target application is started for the first time after installation, there are cases where the target application is uninstalled and reinstalled multiple times, and thus it is determined whether or not there is an installation record file corresponding to the target application in the public directory of the terminal device after the first time of starting the target application, the installation record file is not deleted along with the uninstallation of the target application.
In step S650, if an installation record file corresponding to the target application exists in the public directory of the terminal device, the current installation time and the current terminal device model are recorded in the installation record file.
In an exemplary embodiment of the present disclosure, if there is an installation record file corresponding to a target application in a public directory of a terminal device, it indicates that the target application is installed more than once on the terminal device.
In an exemplary embodiment of the present disclosure, the current installation time is a start time at which the corresponding start-up time is started for the first time after the target application is installed on the terminal device.
In step S660, if the installation record file corresponding to the target application does not exist in the public directory of the terminal device, the installation record file corresponding to the target application is created, and the current installation time and the current terminal device model are recorded in the installation record file.
In an exemplary embodiment of the present disclosure, if there is no installation record file corresponding to the target application in the public directory of the terminal device, it indicates that the terminal device installs the target application for the first time. When the terminal equipment installs the target application for the first time, the situation that the account number is installed and uninstalled for multiple times is avoided, and the terminal equipment can be judged to be normal. Of course, in order to save code space, the determination may be made by using the above-described method of identifying an abnormal terminal device also in the case of first installation of the target application, which is not particularly limited in the present disclosure.
In step S670, the installation time and/or the terminal device model recorded in the installation record file are acquired, and whether the terminal device is an abnormal terminal device is determined according to the installation time and/or the terminal device model.
In an exemplary embodiment of the present disclosure, all installation times corresponding to a target application recorded in an installation record file are obtained, the number of installation times for installing the target application on a terminal device within a preset time is calculated according to the installation times, the number of installation times is compared with an installation time threshold, and if the number of installation times is greater than the installation time threshold, the terminal device is determined to be an abnormal terminal device.
In an exemplary embodiment of the present disclosure, all terminal device models corresponding to a target application recorded in an installation record file are obtained, the number of models is calculated according to the terminal device models, the number of models is compared with a threshold value of the number of models, and if the number of models is greater than the threshold value of the number of models, the terminal device is determined to be an abnormal terminal device.
In an exemplary embodiment of the present disclosure, all installation times and terminal device models corresponding to a target application recorded in an installation record file are acquired, an installation frequency of installing the target application on a terminal device is calculated by weighting according to the installation times and the terminal device models, the installation frequency is compared with an installation frequency threshold, and if the installation frequency is greater than the installation frequency threshold, the terminal device is determined to be an abnormal terminal device.
In an exemplary embodiment of the present disclosure, the installation number threshold, the model number threshold, and the installation frequency threshold are obtained by the server obtaining the number of installation numbers and model numbers corresponding to the target application on the plurality of terminal devices, and calculating according to the plurality of installation numbers and model numbers. The plurality of terminal devices may be terminal devices installed with the target application, and 50-100% of the terminal devices installed with the target application may be arbitrarily selected as samples to perform calculation, where the number of samples for calculating the threshold is not specifically limited in the disclosure.
It should be noted that the installation number threshold, the model number threshold, and the installation frequency threshold may be updated within a preset time range, where the preset time range may be set according to an actual situation, for example, the installation number threshold, the model number threshold, and the installation frequency threshold may be updated once a week, or may be updated once a month, which is not limited in this disclosure. The number of installations threshold, the number of models threshold, and the frequency of installation threshold of the target application are related to the time of use of the target application, and are also related to the function of the target application, and variations of the number of installations threshold, the number of models threshold, and the frequency of installation threshold are within the scope of the disclosure.
The following describes an embodiment of an apparatus of the present disclosure, which may be used to perform the above-described method for identifying an abnormal terminal device of the present disclosure. For details not disclosed in the embodiments of the apparatus of the present disclosure, please refer to the embodiment of the method for identifying an abnormal terminal device described in the present disclosure.
Fig. 7 schematically illustrates a block diagram of an apparatus for identifying an abnormal terminal device according to one embodiment of the present disclosure.
Referring to fig. 7, an apparatus 700 for identifying an abnormal terminal device according to an embodiment of the present disclosure, the apparatus 700 for identifying an abnormal terminal device includes: a response module 701 and a judgment module 702.
Specifically:
a response module 701, configured to obtain an installation record file corresponding to a target application from a public directory of a terminal device;
and the judging module 702 is configured to judge whether the terminal device is an abnormal terminal device according to the installation record file.
The specific details of the above-mentioned devices for identifying the abnormal terminal equipment have been described in detail in the corresponding methods for identifying the abnormal terminal equipment, and thus will not be described herein.
It should be noted that although in the above detailed description several modules or units of a device for performing are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the invention may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 800 according to such an embodiment of the invention is described below with reference to fig. 8. The electronic device 800 shown in fig. 8 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 8, the electronic device 800 is embodied in the form of a general purpose computing device. Components of electronic device 800 may include, but are not limited to: the at least one processing unit 810, the at least one storage unit 820, a bus 830 connecting the different system components (including the storage unit 820 and the processing unit 810), and a display unit 840.
Wherein the storage unit stores program code that is executable by the processing unit 810 such that the processing unit 810 performs steps according to various exemplary embodiments of the present invention described in the above section of the "exemplary method" of the present specification. For example, the processing unit 810 may perform step S110 shown in fig. 1, and acquire an installation record file corresponding to the target application in the public directory of the terminal device; step S120, judging whether the terminal equipment is abnormal terminal equipment according to the installation record file.
The storage unit 820 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 8201 and/or cache memory 8202, and may further include Read Only Memory (ROM) 8203.
Storage unit 820 may also include a program/utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 830 may be one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 800 may also communicate with one or more external devices 1000 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a viewer to interact with the electronic device 800, and/or any device (e.g., router, modem, etc.) that enables the electronic device 800 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 850. Also, electronic device 800 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 860. As shown, network adapter 860 communicates with other modules of electronic device 800 over bus 830. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 800, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.
Referring to fig. 9, a program product 900 for implementing the above-described method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Furthermore, the above-described drawings are only schematic illustrations of processes included in the method according to the exemplary embodiment of the present invention, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (14)
1. A method of identifying an anomalous terminal device, comprising:
Acquiring an installation record file corresponding to a target application from a public directory of the terminal equipment; the installation record file comprises installation time and/or terminal equipment model;
Judging whether the terminal equipment is abnormal terminal equipment or not according to the installation record file;
the judging whether the terminal equipment is abnormal terminal equipment according to the installation record file comprises the following steps:
Acquiring one or more installation times in the installation record file, and determining the installation times in a preset time according to the installation times;
Acquiring one or more terminal equipment models in the installation record file, and determining the number of the models recorded on the terminal equipment according to the terminal equipment models;
calculating the installation frequency in a weighting manner according to the installation times and the model number, and judging whether the installation frequency is larger than an installation frequency threshold value or not;
And when the installation frequency is larger than the installation frequency threshold value, judging that the terminal equipment is the abnormal terminal equipment.
2. The method of identifying an anomalous terminal device according to claim 1, further comprising:
And responding to an uninstalling instruction aiming at the target application, deleting an associated file corresponding to the target application in a private directory of the terminal equipment according to the uninstalling instruction, and reserving an installation record file corresponding to the target application in a public directory of the terminal equipment.
3. The method of identifying an abnormal terminal device according to claim 1, wherein the installation record file includes one or more installation times;
judging whether the terminal equipment is abnormal terminal equipment according to the installation record file, comprising:
Acquiring one or more installation times in the installation record file, and determining the installation times in a preset time according to the installation times;
judging whether the installation times are larger than an installation times threshold value or not;
And when the installation times are larger than the installation times threshold, judging that the terminal equipment is the abnormal terminal equipment.
4. The method of identifying an abnormal terminal device according to claim 1, wherein the installation record file includes one or more terminal device models;
judging whether the terminal equipment is abnormal terminal equipment according to the installation record file, comprising:
Acquiring one or more terminal equipment models in the installation record file, and determining the number of the models recorded on the terminal equipment according to the terminal equipment models;
judging whether the model number is larger than a model number threshold;
And when the model number is larger than the model number threshold, judging that the terminal equipment is the abnormal terminal equipment.
5. The method of identifying an anomalous terminal device according to claim 1, further comprising:
Judging whether an installation record file corresponding to the target application exists in the public directory;
if the current installation time and the current terminal equipment model number are recorded in the installation record file, the installation record file corresponding to the target application is created in the public directory through the target application.
6. The method of identifying an anomalous terminal device according to claim 1, further comprising:
Marking the abnormal terminal equipment according to the unique identification of the abnormal terminal equipment, and marking an abnormal account according to account information corresponding to the abnormal terminal equipment and related to the target application.
7. The method of identifying an anomalous terminal device according to claim 6, further comprising:
judging whether the private directory of the terminal equipment contains a first starting identifier corresponding to the target application or not;
if yes, judging whether the terminal equipment is the abnormal terminal equipment according to the unique identifier of the terminal equipment;
If not, the first starting identification is recorded in the private directory, and whether the terminal equipment is the abnormal terminal equipment is judged according to the installation record file.
8. The method of identifying an abnormal terminal device according to claim 7, wherein determining whether the terminal device is the abnormal terminal device based on the unique identification of the terminal device comprises:
Comparing the unique identifier of the terminal equipment with the unique identifier of the abnormal terminal equipment;
And when the unique identifier of the terminal equipment is consistent with the unique identifier of the abnormal terminal equipment, judging that the terminal equipment is the abnormal terminal equipment.
9. A method of identifying an anomalous terminal device according to claim 3, further comprising:
Obtaining a frequency sample of installation of other terminal equipment corresponding to the target application, and determining the frequency threshold according to the frequency sample of installation through a first preset rule.
10. The method of identifying an anomalous terminal device according to claim 4, further comprising:
and obtaining model number samples of other terminal equipment corresponding to the target application, and determining the model number threshold value according to the model number samples through a second preset rule.
11. The method of identifying an anomalous terminal device according to claim 1, further comprising:
obtaining a number of installation times sample and a model number sample of other terminal equipment corresponding to the target application, calculating an installation frequency sample according to the number of installation times sample and the model number sample in a weighting mode, and determining the installation frequency threshold according to the installation frequency sample through a third preset rule.
12. An apparatus for identifying an abnormal terminal device, comprising:
The response module is used for acquiring an installation record file corresponding to the target application from the public directory of the terminal equipment; the installation record file comprises installation time and/or terminal equipment model;
The judging module is used for judging whether the terminal equipment is abnormal terminal equipment or not according to the installation record file; the judging whether the terminal equipment is abnormal terminal equipment according to the installation record file comprises the following steps: acquiring one or more installation times in the installation record file, and determining the installation times in a preset time according to the installation times; acquiring one or more terminal equipment models in the installation record file, and determining the number of the models recorded on the terminal equipment according to the terminal equipment models; calculating the installation frequency in a weighting manner according to the installation times and the model number, and judging whether the installation frequency is larger than an installation frequency threshold value or not; and when the installation frequency is larger than the installation frequency threshold value, judging that the terminal equipment is the abnormal terminal equipment.
13. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when executed by a processor, implements the method of identifying an abnormal terminal device according to any one of claims 1 to 11.
14. An electronic device, comprising:
One or more processors;
Storage means for storing one or more programs which when executed by the one or more processors cause the one or more processors to implement the method of identifying an anomalous terminal device according to any of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010329084.9A CN111475819B (en) | 2020-04-23 | 2020-04-23 | Method and device for identifying abnormal terminal equipment, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010329084.9A CN111475819B (en) | 2020-04-23 | 2020-04-23 | Method and device for identifying abnormal terminal equipment, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111475819A CN111475819A (en) | 2020-07-31 |
| CN111475819B true CN111475819B (en) | 2024-04-26 |
Family
ID=71763548
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010329084.9A Active CN111475819B (en) | 2020-04-23 | 2020-04-23 | Method and device for identifying abnormal terminal equipment, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111475819B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112511535A (en) * | 2020-11-27 | 2021-03-16 | 北京明略昭辉科技有限公司 | Equipment detection method, device, equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109766104A (en) * | 2018-12-07 | 2019-05-17 | 北京数字联盟网络科技有限公司 | Download system of application program, installation type determining method and storage medium |
-
2020
- 2020-04-23 CN CN202010329084.9A patent/CN111475819B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109766104A (en) * | 2018-12-07 | 2019-05-17 | 北京数字联盟网络科技有限公司 | Download system of application program, installation type determining method and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111475819A (en) | 2020-07-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8689203B2 (en) | Software update techniques based on ascertained identities | |
| US9183072B1 (en) | Error troubleshooting using a correlated knowledge base | |
| US8990772B2 (en) | Dynamically recommending changes to an association between an operating system image and an update group | |
| CN103518191A (en) | Upgrade method, intelligent terminal and upgrade system | |
| US8918776B2 (en) | Self-adapting software system | |
| CN109783345B (en) | Method and system for testing small program performance | |
| CN111741046B (en) | Data reporting method, data acquisition method, device, equipment and medium | |
| CN112307466A (en) | Application program detection method and device, electronic equipment and storage medium | |
| CN106155746B (en) | A kind of installation file processing method and processing device, server | |
| CN113760306B (en) | Method, device, electronic device and storage medium for installing software | |
| CN111475819B (en) | Method and device for identifying abnormal terminal equipment, storage medium and electronic equipment | |
| CN109117153A (en) | Processing method, device, terminal and the storage medium of application program | |
| CN112256295A (en) | Application program updating method, device, equipment and storage medium | |
| CN113760631B (en) | Method, device, equipment and storage medium for determining page loading time | |
| US20070074172A1 (en) | Software problem administration | |
| US20220334744A1 (en) | Method, electronic device, and computer program product for processing data | |
| CN112988192A (en) | Version updating method and device, electronic equipment and storage medium | |
| CN112486517A (en) | Application program installation method and system, electronic equipment and storage medium | |
| CN111124795B (en) | Application starting monitoring method, device and equipment | |
| CN106371873A (en) | Application starting request processing method and system and server | |
| CN111367537B (en) | Installation method and device of device driver, computer device and storage medium | |
| CN110333969A (en) | Application startup exception handling method and device, medium and device after system upgrade | |
| CN110647331A (en) | Method and device for acquiring development tool, storage medium, and electronic device | |
| CN116931995A (en) | System upgrading method and device, electronic equipment and storage medium | |
| CN111124627A (en) | Method, device, terminal and storage medium for determining application program caller |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |