Compliant Android app installation detection method and system

Abstract

The invention provides a compliant Android app installation detection method and system, the method is applied to a server, and the method comprises the following steps: obtaining a local detection list of a client and a server version list for consistency detection, if the detection results are consistent, feeding back a client target instruction, and if the detection results are inconsistent, feeding back the client target instruction; if so, feeding back to the client for app detection based on increment updating operation; obtaining an app detection result of the client, and carrying out data decryption and restoration to obtain a risk app; and generating a risk tag based on the quantity value of the risk app, and adding the risk tag to the user attribute of the client. The invention provides a complete detection scheme of a specified app meeting supervision requirements and service requirements, and dynamic increment updating for saving data traffic based on an app list, and the transmitted data volume and the number of apps detected by a client each time can be reduced through dynamic increment updating and a data encryption mode.

Description

Technical Field

[0001] The present invention relates to the technical fields of data processing and mobile app, and particularly to a compliant Android app installation detection method and system. Background Art

[0002] When a user uses an app, the installed apps on the client can be detected to obtain a list of all apps installed on the mobile phone for analysis, which is mainly used in business scenarios such as recommendation and risk control to improve business quality, so as to profile the user.

[0003] Currently, when conducting app detection, due to regulatory requirements, it is no longer allowed for the business to directly obtain the app installation list. Instead, it is necessary to change to user authorization or detect whether a specified app is installed. Most solutions will pop up a window to prompt the user for authorization in order to obtain the app list with the user's permission. At the same time, as the number of installed apps continues to increase, it also brings a large amount of data for detection. Summary of the Invention

[0004] The purpose of the present invention is to provide a compliant Android app installation detection method and system for solving the problem of compliant Android app installation detection.

[0005] In a first aspect, the present application provides a compliant Android app installation detection method, which is applied to a server, and the method includes:

[0006] Obtain the local detection list of the client and perform consistency detection with the server version list, where

[0007] If the detection result is consistent, feedback the target instruction to the client. If the detection result is inconsistent, perform incremental update operation and then feedback to the client for app detection;

[0008] Obtain the app detection result of the client and decrypt and restore the data to obtain the risk app;

[0009] Generate a risk label based on the quantity value of the risk app, and add the risk label to the user attributes of the client.

[0010] In a possible implementation manner of the present application, the obtaining the local detection list of the client and performing consistency detection with the server version list specifically includes:

[0011] Obtain the local detection list based on the local detection version reported by the client;

[0012] Perform consistency detection based on the local detection list and the server version list, where

[0013] If the app versions in the local detection list are the same as those in the server version list, it indicates that the detection results are consistent;

[0014] If the app versions in the local detection list are different from those in the server version list, it indicates that the detection results are inconsistent.

[0015] In a possible implementation manner of the present application, the method further includes dynamically updating the server version list.

[0016] In a possible implementation manner of the present application, the incremental update job specifically includes:

[0017] When the current local client version number is lower than the server version number based on the version number, an incremental update job is performed;

[0018] The version increments in the local detection list and the server version list are packaged, encrypted, compressed, and fed back to the client, where the encryption method includes shift encryption.

[0019] In a possible implementation manner of the present application, the obtaining the app detection result of the client and decrypting and restoring the data to obtain the risky app specifically includes:

[0020] Obtain the app detection result of the client to identify the binary sequence;

[0021] Based on the binary sequence, data matching is performed in combination with the server version list, where the corresponding app in the server version list is extracted based on the target number in the binary sequence as the risky app.

[0022] In a possible implementation manner of the present application, the generating a risk label based on the quantity value of the risky app and adding the risk label to the user attributes of the client specifically includes:

[0023] Count the quantity value of the risky app to obtain the target value;

[0024] Based on the comparison between the target value and the preset value, it is determined whether to generate the risk label, where,

[0025] If the target value is greater than or equal to the preset value, the risk label is generated and synchronously added to the user attributes of the client;

[0026] If the target value is less than the preset value, the risk label is not generated.

[0027] In a second aspect, the present application provides a compliant Android app installation detection system, which is applied to the server, and the system includes:

[0028] An acquisition module, configured to acquire a local detection list of a client and perform consistency detection with a server version list. If the detection results are consistent, a target instruction is fed back to the client. If the detection results are inconsistent, after an incremental update job is performed, it is fed back to the client for app detection.

[0029] An identification module, configured to acquire an app detection result of the client, perform data decryption and restoration, and identify a risky app by matching the server version list.

[0030] A generation module, configured to generate a risk label based on the quantity value of the risky app, and add the risk label to the user attributes of the client.

[0031] In a third aspect, the present application provides a method for detecting the installation of a compliant Android app, which is applied to a client. The method includes:

[0032] Uploading a local detection version to the server, and acquiring a server version list fed back by the server;

[0033] Detecting local apps based on the server version list;

[0034] Encrypting the app detection result based on the server version list, where the encryption method includes list binary encoding;

[0035] Feeding back the encrypted app detection result to the server.

[0036] In a possible implementation manner of the present application, the method further includes identifying a trigger detection condition to perform app detection, where the trigger detection condition includes: triggering detection when the target app is opened for the first time, and / or triggering detection when the user operates the target app to generate a target interface.

[0037] In a fourth aspect, the present application provides a system for detecting the installation of a compliant Android app, which is applied to a client. The system includes:

[0038] An upload module, configured to upload a local detection version to the server, and acquire a server version list fed back by the server;

[0039] A detection module, configured to detect local apps based on the server version list;

[0040] An encryption module, configured to encrypt the app detection result based on the server version list, where the encryption method includes list binary encoding;

[0041] A feedback module, configured to feed back the encrypted app detection result to the server.

[0042] As described above, the compliant Android app installation detection method and system of the present invention provide a complete detection solution for specified apps that meets regulatory requirements and business requirements, as well as dynamic incremental updates that save data traffic based on the app list. By means of dynamic incremental updates and data encryption, the amount of data transmitted can be reduced and the number of apps detected by the client each time can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 It shows a scenario application diagram of the compliant Android app installation detection method of the present invention in an embodiment;

[0044] Figure 2 It shows a schematic diagram of the method steps of the compliant Android app installation detection method of the present invention in an embodiment;

[0045] Figure 3 It shows a schematic diagram of the method steps of the compliant Android app installation detection method of the present invention in an embodiment;

[0046] Figure 4 It shows a schematic diagram of the method steps of the compliant Android app installation detection method of the present invention in an embodiment;

[0047] Figure 5 It shows a schematic diagram of the method steps of the compliant Android app installation detection method of the present invention in an embodiment;

[0048] Figure 6 It shows a schematic diagram of the method steps of the compliant Android app installation detection method of the present invention in an embodiment;

[0049] Figure 7 It shows a schematic structural diagram of the compliant Android app installation detection system of the present invention in an embodiment;

[0050] Figure 8 It shows a schematic diagram of the method steps of the compliant Android app installation detection method of the present invention in an embodiment;

[0051] Figure 9 It shows a schematic structural diagram of the compliant Android app installation detection system of the present invention in an embodiment.

[0052] DESCRIPTION OF REFERENCE NUMERALS

[0053] Steps S202 - S208

[0054] Steps S302 - S306

[0055] Steps S402 - S404

[0056] Steps S502 - S504

[0057] Steps S602 - S606

[0058] 70 - compliant Android app installation detection system

[0059] 71 Acquisition module

[0060] 72 Identification module

[0061] 73 Generation module

[0062] 90 - compliant Android app installation detection system

[0063] 91 Upload module

[0064] 92 Detection module

[0065] 93 Encryption module

[0066] 94 Feedback module Detailed implementation manners

[0067] The following uses specific specific examples to illustrate the implementation manners of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific implementation manners. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, without conflict, the following embodiments and the features in the embodiments can be combined with each other.

[0068] It should be noted that the diagrams provided in the following embodiments only illustrate the basic concept of the present invention in a schematic manner. Therefore, only the components related to the present invention are shown in the diagrams, rather than being drawn according to the number, shape, and size of the components in actual implementation. The type, quantity, and proportion of each component in its actual implementation can be an arbitrary change, and the component layout type may also be more complex.

[0069] Such as Figure 1As shown, it is a scenario application diagram of the compliant Android app installation detection method described in this application. Among them, the compliant Android app installation detection method described in this application includes a server and a client. Among them, the client needs to upload the detection list of local applications, and obtain the server version list issued by the server for app detection, so as to encrypt the detection results into binary code and upload them to the server. At the same time, the server needs to dynamically update the application list to be detected, and compare it with the uploaded local application detection list to issue the corresponding server version list. Among them, when comparing the lists, incremental updates can be used to shorten the data processing process, and the lists are encrypted and compressed to ensure the privacy of data transmission. At the same time, when decrypting and restoring the detection results, the target apps existing in the current client can be parsed according to the server list combined with the corresponding binary code results. For example, in the risk control detection scenario, financial apps need to be detected. The detection list includes four apps, such as Alipay, JD Finance, Du Xiaoman, and Fenqile. Thus, it can be parsed according to the binary code results whether the corresponding applications exist in the current client to add tags to the user attributes of the client for subsequent risk judgment.

[0070] Please refer to Figure 2 , in an embodiment of the invention, the compliant Android app installation detection method of the invention is applied to the server, and the method includes the following steps:

[0071] Step S202, obtain the local detection list of the client and the server version list for consistency detection;

[0072] Step S204, if the detection results are consistent, feedback the target instruction to the client; if the detection results are inconsistent, then perform incremental update operations and then feedback to the client for its app detection;

[0073] Step S206, obtain the app detection results of the client, decrypt and restore the data to obtain the risk apps;

[0074] Step S208, generate risk labels based on the quantity values of the risk apps, and add the risk labels to the user attributes of the client.

[0075] It should be noted that the obtaining of the local detection list of the client and the server version list for consistency detection, as Figure 3 shown, specifically includes the following steps:

[0076] Step S302, obtain the local detection list based on the local detection version reported by the client;

[0077] Step S304, perform consistency detection based on the local detection list and the server version list;

[0078] Step S306. If the app versions in the local detection list are the same as those in the server version list, it indicates that the detection results are consistent; if the app versions in the local detection list are different from those in the server version list, it indicates that the detection results are inconsistent.

[0079] Specifically, the local detection versions uploaded by the client are the lists corresponding to the detections in historical data. Then, when the server issues a new server version list, there may be a scenario where the versions are inconsistent. Therefore, it is necessary to perform a consistency check based on the local detection list and the server version list. Specifically, it is to compare whether the app versions in the two lists are the same. Among them, the same app version corresponds to the same app to be detected. For example, if the local detection list is for three apps "A, B, and C", and the corresponding server version list on the server is also for three apps "A, B, and C", then it indicates that the detection is consistent. At this time, the server feeds back a target instruction to the client. Among them, the target instruction can correspond to the instruction with the server version list being "0", that is, the client can directly perform app detection based on the local detection version, and replacing the server version list with the target instruction can further reduce the amount of transmitted data.

[0080] In one embodiment of the invention, the method further includes dynamically updating the server version list.

[0081] Furthermore, it should be noted that in actual applications, the behaviors of black and gray production are constantly changing, so it is also required that the key points for detecting apps need to change synchronously. Therefore, when the server generates the server version list, it will dynamically adjust the apps in the list in real time. Specifically, it will update the detection list according to industry intelligence, which can be updated manually by humans or automatically according to the results of big data screening.

[0082] Furthermore, in one embodiment of the invention, as Figure 4 shown, based on the incremental update job, it specifically includes the following steps:

[0083] Step S402. When it is identified based on the version number that the current local client version number is lower than the server version number, perform an incremental update job;

[0084] Step S404. Package and encrypt and compress the version increments in the local detection list and the server version list and feedback them to the client, where the encryption method includes shift encryption.

[0085] It should be noted that in this embodiment, each time the user opens the app, the latest detection list will be obtained. However, in most cases, the obtained list is the same as the previous one. Therefore, in order to reduce data transmission and save traffic for users, an incremental update job can be adopted to update the list. At the same time, the concept of the list version number is also explained. Specifically, for example, when the server first configures the apps to be detected as "A, B, and C", the corresponding version number is "Version 1, detect A, B, C". The second time it receives intelligence, it needs to add "D, E" two apps, and at the same time, the effect of "B" is not good and needs to be deleted. The corresponding version number is "Version 2, detect D, E, -B". The third time it adds the detection of "F, G" two apps, and the corresponding version number is "Version 3, detect F, G". So the final complete server version list is "A, C, D, E, F, G". Among them, when a user opens the app, the local client version number corresponding to the local detection list is "Version 1", and at this time, the maximum version number corresponding to the server version list is already "Version 3". So the incremental package between "Version 1" and "Version 3", that is, the data [D, E, -B, F, G] is sent to the app for it to update. Then, when this user opens the corresponding app again, the version number corresponding to the local detection list is then "Version 3", and at this time, the maximum version number corresponding to the server version list is also 3, so there is no need to return the list data to the client. Among them, through incremental update, the transmission of duplicate data can be reduced, thus reducing the transmission volume of duplicate data.

[0086] Further, when performing incremental packaging, encryption and compression are required. In this embodiment, the shift encryption method is used for compression. Specifically, taking four apps, namely Alipay, JD Finance, Du Xiaoman Finance, and Fenqile, as an example, the generated detection list is "com.eg.android.AlipayGphone,com.jd.jrapp,com.duxiaoman.wallet,com.fenqile.fenqile". This character string will first be compressed into a byte stream using zlib. After verification, the character length will be reduced by more than "80%" after zlib compression. Then, shift encryption is used for character shift transformation. For the shift transformation, there will be a shift table. For example, in the first round, all characters after the first character are cyclically shifted left by "1" bit; in the second round, all characters after the fifth character are cyclically shifted right by "2" bits. Specifically, assuming the character to be encrypted is "abcdefgh", the server uses the shift table for encryption: In the first round: The characters after the first character 'a' are shifted left to become "acdefghb"; in the second round: The characters after the fifth character 'f' are shifted right to become "acdefhbg"; finally, "abcdefgh" becomes "acdefhbg", achieving the encryption effect. For the encryption scenario in this embodiment, the encryption does not affect the data length and can achieve the purpose of obfuscating the data, so as to provide the client for app detection.

[0087] Further, in an embodiment of the invention, as Figure 5 shown, the steps of obtaining the app detection result of the client and decrypting and restoring the data to obtain the risk app specifically include the following steps:

[0088] Step S502, obtaining the app detection result of the client to identify the binary sequence;

[0089] Step S504, based on the binary sequence, combining with the server version list for data matching, wherein, based on the target number in the binary sequence, the corresponding app in the server version list is extracted as the risk app.

[0090] It should be noted that after the client detects the app, it will perform binary encoding on the app detection results. Taking the four apps of Alipay, JD Finance, Du Xiaoman Finance, and Fenqile as examples, since the generated server version list is "com.eg.android.AlipayGphone,com.jd.jrapp,com.duxiaoman.wallet,com.fenqile.fenqile", when the client detects, it actually detects two apps, namely "com.jd.jrapp" and "com.fenqile.fenqile". Then, when the client performs binary encoding, it will convert the detected apps into the format of "0,1" according to the server version list order, specifically

[0101] . Therefore, on the server side, after receiving

[0101] , it will compare it with the original list "com.eg.android.AlipayGphone,com.jd.jrapp,com.duxiaoman.wallet,com.fenqile.fenqile", and extract the items corresponding to the target numbers (corresponding to the value "1") in the binary sequence: [com.jd.jrapp, com.fenqile.fenqile], so as to finally know that the user's mobile phone has installed two applications, JD Finance and Fenqile.

[0091] Further, in an embodiment of the invention, as Figure 6 shown, generating a risk label based on the quantity value of the risk app and adding the risk label to the user attributes of the client specifically includes the following steps:

[0092] Step S602, counting the quantity value of the risk app to obtain a target value;

[0093] Step S604, judging whether to generate the risk label based on the comparison between the target value and a preset value;

[0094] Step S606, if the target value is greater than or equal to the preset value, generate the risk label and synchronously add the risk label to the user attributes of the client; if the target value is less than the preset value, do not generate the risk label.

[0095] It should be noted that the app installation data collection mainly uses the risk control scenario. Risk control will assign tags based on data characteristics. For example, after the app detection data is reported to the server and the server restores the data, it is known that the user has installed "10" loan apps. From a risk perspective, generally, a normal user will not install so many loan apps. Therefore, the risk control system will assign a risk tag to this user, indicating that this user has a risk of owing money, and synchronize the risk tag to the user attributes on the client side. Subsequently, the app business will process differently according to this tag, and the preset value can be adjusted as needed. In this embodiment, the preset value adopted is "10".

[0096] The embodiment of the present application also provides a compliant Android app installation detection system, which is applied to the server side. The compliant Android app installation detection system can implement the compliant Android app installation detection method described in the present application. However, the implementation device of the compliant Android app installation detection method described in the present application includes but is not limited to the structure of the compliant Android app installation detection system listed in this embodiment. Any structural deformation and replacement of the prior art made according to the principle of the present application are included in the protection scope of the present application.

[0097] Please refer to Figure 7 , in an embodiment, a compliant Android app installation detection system 70 provided in this embodiment is applied to the server side. The system includes:

[0098] An acquisition module 71, configured to perform consistency detection on the local detection list of the client and the server version list. Among them, if the detection result is consistent, a target instruction for the client is fed back. If the detection result is inconsistent, it is fed back to the client for app detection after an incremental update job is performed;

[0099] An identification module 72, configured to decrypt and restore the data of the app detection result of the client and match the server version list to identify a risky app;

[0100] A generation module 73, configured to generate a risk tag based on the quantity value of the risky app and add the risk tag to the user attributes of the client.

[0101] Since the specific implementation manner of this embodiment corresponds to the foregoing method embodiment, the same details will not be repeated here. Those skilled in the art should also understand that Figure 7The division of each module in the embodiments is only a division of logical functions. In actual implementation, all or part of them can be integrated into one or more physical entities. These modules can all be implemented in the form of software called by processing elements, or all be implemented in the form of hardware, or some modules be implemented in the form of software called by processing elements and some modules be implemented in the form of hardware.

[0102] The above embodiments illustrate the application scenario of the disclosed compliant Android app installation detection method on the server side. Further, the disclosed compliant Android app installation detection method is also applied to the client side. Among them, referring to Figure 8 , in an embodiment of the invention, the compliant Android app installation detection method of the invention is applied to the client side, and the method includes the following steps:

[0103] Step S802, upload the local detection version to the server and obtain the server version list fed back by the server;

[0104] Step S804, detect the local app based on the server version list;

[0105] Step S806, encrypt the app detection result based on the server version list, where the encryption method includes list binary encoding;

[0106] Step S808, feed back the encrypted app detection result to the server.

[0107] It should be noted that the method further includes identifying a trigger detection condition to perform app detection, where the trigger detection condition includes: triggering detection when the target app is opened for the first time, and / or triggering detection when the user operates the target app to generate a target interface.

[0108] Specifically, certain trigger conditions are required when performing app detection to identify whether a specified app (corresponding to the target app) is installed on the current client. In this embodiment, two trigger conditions are illustrated. The first one is: perform detection when the target app is opened for the first time; the second one: trigger detection at a certain time. For example, when triggering a loan business, in order to judge the user risk, detection will be performed when the user opens the borrowing page to detect those lending and other fraud apps to reduce transaction risks. Correspondingly, the second trigger scenario can also be extended. For example, detection is triggered on the user order page to check whether a screen monitoring app is installed to inform the user of the risk of bank information leakage.

[0109] Furthermore, in the above embodiments, it is illustrated that the server encrypts and transmits the incrementally updated content. In this embodiment, when the client receives the corresponding encrypted data, it can use the shift table for reverse decryption. Specifically: In the first round: The characters after the fifth character 'f' are shifted left to become "acdefghb"; in the second round: The characters after the first character 'a' are shifted right to become "abcdefgh" to restore the characters. After the characters are restored on the client side, zlib decompression is performed to obtain the server version list "com.eg.android.AlipayGphone,com.jd.jrapp,com.duxiaoman.wallet,com.fenqile.fenqile" sent by the server, and then this part of the list is stored locally on the mobile phone for app detection. Among them, if the detection results are consistent, the server version list fed back by the server will correspond to the target instruction with the server version list being "0". At this time, the client can directly perform app detection based on the locally detected version, thereby reducing a large amount of repeated data transmission.

[0110] Furthermore, encrypt the app detection results based on the server version list. Among them, the encryption method includes list binary encoding. Specifically, after the client finishes detecting the app, it will perform binary encoding on the app detection results. Taking the four apps of Alipay, JD Finance, Du Xiaoman, and Fenqile as an example, since the generated server version list is "com.eg.android.AlipayGphone,com.jd.jrapp,com.duxiaoman.wallet,com.fenqile.fenqile", when the client detects, it actually detects two apps, "com.jd.jrapp" and "com.fenqile.fenqile". Then when the client performs binary encoding, it will convert the detected apps into the format of "0,1" according to the order of the server version list, specifically

[0101] . Correspondingly,

[0101] is used for data transmission. Compared with directly reporting [com.jd.jrapp, com.fenqile.fenqile], it not only reduces the data length but also desensitizes the data and hides the meaning of the data.

[0111] The embodiments of the present application also provide a compliant Android app installation detection system, which is applied to a client. The compliant Android app installation detection system can implement the compliant Android app installation detection method described in the present application. However, the implementation device of the compliant Android app installation detection method described in the present application includes, but is not limited to, the structure of the compliant Android app installation detection system listed in this embodiment. Any structural deformation and replacement of the prior art made according to the principle of the present application are included in the protection scope of the present application.

[0112] Please refer to Figure 9 , in an embodiment, a compliant Android app installation detection system 90 provided in this embodiment is applied to a client. The system includes:

[0113] An upload module 91, configured to upload a local detection version to a server and obtain a server version list fed back by the server;

[0114] A detection module 92, configured to detect a local app based on the server version list;

[0115] An encryption module 93, configured to encrypt the app detection result based on the server version list, where the encryption method includes list binary encoding;

[0116] A feedback module 94, configured to feedback the encrypted app detection result to the server.

[0117] Since the specific implementation manner of this embodiment corresponds to the foregoing method embodiment, the same details will not be repeated here. Those skilled in the art should also understand that Figure 9 The division of each module in the embodiment is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one or more physical entities, and these modules can all be implemented in the form of software called by a processing element, or all in the form of hardware, or some modules can be implemented in the form of software called by a processing element and some modules can be implemented in the form of hardware.

[0118] In addition, this embodiment can also provide an electronic device. Specifically, the electronic device at least includes: a memory and a processor connected by a bus. The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory to execute all or part of the steps in the foregoing method embodiment.

[0119] In summary, the present invention provides a complete detection solution for a specified app that meets regulatory requirements and business requirements, as well as a dynamic incremental update that saves data traffic based on the app list. Through dynamic incremental updates and data encryption methods, the amount of data transmitted can be reduced and the number of apps detected by the client each time can be decreased.

[0120] In several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, or method can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of modules / units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or units can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces, and the indirect coupling or communication connection of the apparatus or module or unit can be in an electrical, mechanical, or other form.

[0121] The modules / units described as separate components may or may not be physically separated. The components shown as modules / units may or may not be physical modules, that is, they can be located in one place or distributed to multiple network units. Some or all of the modules / units can be selected according to actual needs to achieve the purpose of the embodiments of the present application. For example, in each embodiment of the present application, the various functional modules / units can be integrated in a processing module, or each module / unit can exist physically alone, or two or more modules / units can be integrated in one module / unit.

[0122] Those of ordinary skill in the art should also further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0123] The embodiments of the present application also provide a computer-readable storage medium. Those of ordinary skill in the art can understand that all or part of the steps in the methods of the above embodiments can be completed by instructing a processor through a program. The program can be stored in a computer-readable storage medium, and the storage medium is a non-transitory medium, such as random access memory, read-only memory, flash memory, hard disk, solid state drive, magnetic tape, floppy disk, optical disc, and any combination thereof. The above storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid state disk (SSD)), etc.

[0124] The embodiments of the present application can also provide a computer program product, which includes one or more computer instructions. When the computer instructions are loaded and executed on a computing device, all or part of the processes or functions described in the embodiments of the present application are generated. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from a website, a computer, or a data center to another website, a computer, or a data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.).

[0125] When the computer program product is executed by a computer, the computer executes the method described in the foregoing method embodiments. The computer program product can be a software installation package. In the case where the foregoing method is required, the computer program product can be downloaded and executed on the computer.

[0126] The descriptions of the processes or structures corresponding to the above respective drawings each have their own emphases. For parts not detailed in a certain process or structure, reference can be made to the relevant descriptions of other processes or structures.

[0127] The above embodiments are only illustrative of the principles and effects of the present application and are not used to limit the present application. Any person familiar with this technology can modify or change the above embodiments without departing from the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by those of ordinary skill in the art in the technical field without departing from the spirit and technical ideas disclosed by the present application should still be covered by the claims of the present application.

Claims

1. A compliant Android app installation detection method, characterized in that, applied to the server side, the method includes: Obtain the local detection list of the client and perform consistency detection with the server version list. Among them, If the detection results are consistent, feedback the target instruction to the client. If the detection results are inconsistent, perform incremental update operations and then feedback to the client for app detection; Obtain the app detection results of the client, decrypt and restore the data to obtain risky apps; Generate risk labels based on the quantity values of the risky apps, and add the risk labels to the user attributes of the client.

2. The compliant Android app installation detection method according to claim 1, characterized in that, The obtaining the local detection list of the client and performing consistency detection with the server version list specifically includes: Obtain the local detection list based on the local detection version reported by the client; Perform consistency detection based on the local detection list and the server version list. Among them, If the app versions in the local detection list and the server version list are the same, it indicates that the detection results are consistent; If the app versions in the local detection list and the server version list are different, it indicates that the detection results are inconsistent.

3. The compliant Android app installation detection method according to claim 2, characterized in that, The method further includes dynamically updating the server version list.

4. The compliant Android app installation detection method according to claim 1, characterized in that, The incremental update operation specifically includes: Based on the version number, identify the current local client version number. If it is lower than the server version number, perform incremental update operations; Package and encrypt the version increments in the local detection list and the server version list and feedback them to the client. Among them, the encryption method includes shift encryption.

5. The compliant Android app installation detection method according to claim 4, characterized in that, The obtaining the app detection results of the client, decrypting and restoring the data to obtain risky apps specifically includes: Obtain the app detection results of the client to identify the binary sequence; Perform data matching based on the binary sequence and the server version list. Among them, extract the corresponding app in the server version list based on the target number in the binary sequence as the risky app.

6. The compliant Android app installation detection method according to claim 5, characterized in that, The generating risk labels based on the quantity values of the risky apps and adding the risk labels to the user attributes of the client specifically includes: Count the quantity values of the risky apps to obtain the target value; Judge whether to generate the risk labels based on the comparison between the target value and the preset value. Among them, If the target value is greater than or equal to the preset value, generate the risk labels and synchronously add the risk labels to the user attributes of the client; If the target value is less than the preset value, do not generate the risk labels.

7. A compliant Android app installation detection system, characterized in that, applied to the server side, the system includes: An acquisition module, configured to perform consistency detection on the local detection list of the client and the server version list. Among them, if the detection results are consistent, the target instruction of the client is fed back; if the detection results are inconsistent, it is fed back to the client for app detection after an incremental update job; An identification module, configured to decrypt and restore the app detection results of the client and match the server version list to identify risky apps; A generation module, configured to generate a risk label based on the numerical value of the risky apps and add the risk label to the user attributes of the client.

8. A compliant Android app installation detection method, characterized in that, applied to the client side, the method includes: Uploading the local detection version to the server and obtaining the server version list fed back by the server; Detecting the local apps based on the server version list; Encrypting the app detection results based on the server version list, where the encryption method includes list binary encoding; Feeding back the encrypted app detection results to the server.

9. The compliant Android app installation detection method according to claim 8, characterized in that, the method further includes identifying a trigger detection condition to perform app detection, where the trigger detection conditions include: triggering detection when the target app is first opened, and / or triggering detection when the user operates the target app to generate a target interface.

10. A compliant Android app installation detection system, characterized in that, applied to the client side, the system includes: An upload module, configured to upload the local detection version to the server and obtain the server version list fed back by the server; A detection module, configured to detect the local apps based on the server version list; An encryption module, configured to encrypt the app detection results based on the server version list, where the encryption method includes list binary encoding; A feedback module, configured to feed back the encrypted app detection results to the server.

Images