Data compliance collection method and related device

Abstract

Embodiments of this application disclose a method and related devices for compliant data collection. The method includes: in response to a current data collection request of an application program, determining a target data code value corresponding to the current data collection request; if the target data code value indicates that the collection status of the current target data is non-collectible, returning a null value to the application program; if the target data code value indicates that the collection status of the current target data is collectible, determining whether the application program meets the compliant collection conditions for the current target data; if the application program meets the compliant collection conditions for the current target data, returning cached data to the application program when the cached data is valid. Using the embodiments of this application helps to ensure that data collection complies with the regulatory requirements of relevant departments and also helps to improve the efficiency of data collection.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular, to a method for collecting data in compliance and related devices. Background Art

[0002] With the increasing intensity of personal information protection, in the aspect of application programs collecting users' personal information, the regulatory intensity faced by major application program manufacturers is also gradually increasing. For different user information, such as users' personal credit information and the IMEI of users' devices, their regulatory intensity and access permissions are different. Therefore, it is difficult to ensure the compliance of information collection when application programs collect users' information. Summary of the Invention

[0003] Embodiments of this application provide a method for collecting data in compliance and related devices, which helps to ensure that information collection meets the regulatory requirements of relevant departments and also helps to improve the efficiency of information collection.

[0004] In a first aspect, embodiments of this application provide a method for collecting data in compliance, and the method includes:

[0005] In response to a current data collection request of an application program, determine a target data code value corresponding to the current data collection request, where the data collection request corresponds to the target data one by one, the current target data is the data collected corresponding to the current data collection request, and the target data code value is used to represent the collection status of the current target data, and the collection status includes collectable and non - collectable;

[0006] If the target data code value indicates that the collection status of the current target data is non - collectable, return a null value to the application program;

[0007] If the target data code value indicates that the collection status of the current target data is collectable, determine whether the application program meets the compliance collection conditions of the current target data, and the compliance collection conditions correspond to the target data one by one;

[0008] If the application program meets the compliance collection conditions of the current target data, obtain the cached data corresponding to the current target data and the update time of the cached data;

[0009] According to the current time of the user - end device and the update time of the cached data, determine the cache duration of the cached data;

[0010] According to the cache duration and a preset cache duration threshold, determine whether the cached data is valid;

[0011] If the cached data is valid, return the cached data to the application program.

[0012] In a second aspect, an embodiment of the present application provides a data compliance acquisition device, which includes a response unit, a determination unit, an acquisition unit, and a return unit. Among them,

[0013] The response unit is configured to, in response to a current data acquisition request of an application program, determine a target data code value corresponding to the current data acquisition request. Among them, the data acquisition request corresponds to the target data one by one. The current target data is the data collected corresponding to the current data acquisition request. The target data code value is used to represent the acquisition status of the current target data, and the acquisition status includes collectable and uncollectable;

[0014] The return unit is configured to, in the case where the target data code value indicates that the acquisition status of the current target data is uncollectable, return a null value to the application program;

[0015] The determination unit is configured to, in the case where the target data code value indicates that the acquisition status of the current target data is collectable, determine whether the application program meets the compliance acquisition conditions of the current target data. The compliance acquisition conditions correspond to the target data one by one;

[0016] The acquisition unit is configured to, under the condition that the application program meets the compliance acquisition conditions of the current target data, acquire the cache data corresponding to the current target data and the update time of the cache data;

[0017] The determination unit is further configured to determine the cache duration of the cache data according to the current time of the user terminal device and the update time of the cache data;

[0018] The determination unit is further configured to determine whether the cache data is valid according to the cache duration and a preset cache duration threshold;

[0019] The return unit is further configured to, if the cache data is valid, return the cache data to the application program.

[0020] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a computer program or instruction stored on the memory. The processor executes the computer program or instruction to implement the steps in the first aspect of the embodiments of the present application.

[0021] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. Among them, the above computer-readable storage medium stores a computer program for electronic data exchange. Among them, the above computer program enables a computer to execute instructions for performing some or all of the steps described in the first aspect of the embodiments of the present application.

[0022] Fifth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a computer program, and the computer program is operable to cause a computer to execute some or all of the steps described in the first aspect of the embodiment of the present application.

[0023] Implementing the embodiments of the present application has the following beneficial effects:

[0024] It can be seen that in the data compliance collection method and related device described in the embodiment of the present application, in response to the current data collection request of the application program, the target data code value corresponding to the current data collection request is determined. If the target data code value indicates that the collection status of the current target data is non-collectable, a null value is returned to the application program. If the target data code value indicates that the collection status of the current target data is collectable, it is determined whether the application program meets the compliance collection conditions of the current target data. If the application program meets the compliance collection conditions of the current target data, the cached data corresponding to the current target data and the update time of the cached data are obtained. According to the current time of the user terminal device and the update time of the cached data, the cache duration of the cached data is determined. According to the cache duration and the preset cache duration threshold, it is determined whether the cached data is valid. If the cached data is valid, the cached data is returned to the application program; thus, before collecting the target data, it is first determined whether the target data is in a collectable state through the data code value, and during the process of collecting the target data, the collection of the target data is restricted by the compliance collection conditions, which helps to ensure that the data collection complies with the supervision requirements of relevant departments and also helps to improve the efficiency of data collection. Description of the Drawings

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0026] Figure 1 is a schematic diagram of the system architecture of a data compliance collection method provided by an embodiment of the present application;

[0027] Figure 2A is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application;

[0028] Figure 2B is a schematic diagram of the flow of a data compliance collection method provided by an embodiment of the present application;

[0029] Figure 2C is a schematic diagram of the flow of another data compliance collection method provided by an embodiment of the present application;

[0030] Figure 2D It is a schematic flowchart of another data compliance collection method provided by an embodiment of the present application;

[0031] Figure 3 It is a schematic structural diagram of another electronic device provided by an embodiment of the present application;

[0032] Figure 4 It is a block diagram of the functional units of a data compliance collection device provided by an embodiment of the present application. Detailed implementation manners

[0033] Terms such as "first" and "second" in the specification, claims and above-mentioned drawings of the present application are used to distinguish different objects, rather than to describe a specific order. These terms are only used to distinguish two objects. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products or devices. The term "plurality" may refer to two or more, which will not be elaborated hereinafter.

[0034] Referring to "embodiment" herein means that a specific feature, structure or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The phrase appears in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0035] In order to enable those skilled in the art to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0036] The key concepts and terms involved in the present application include but are not limited to the following:

[0037] (1) Data code values can be used to identify the acquisition instructions pre-written by R & D personnel for each type of target data. If the data code value carried in the data acquisition request exists in the database, it indicates that the acquisition instruction for the target data corresponding to this data code value exists, that is to say, the target data is in a collectible state. On the contrary, if the data code value carried in the data acquisition request does not exist in the database, it means that the acquisition instruction for the target data corresponding to this data code value does not exist, that is to say, the R & D personnel have not studied and developed the acquisition of this target data, and the target data is in a non-collectible state.

[0038] (2) The electronic device can be a portable electronic device, such as a mobile phone, a tablet computer, a wearable electronic device with wireless communication function (such as a smart watch), etc. Exemplary embodiments of the portable electronic device include, but are not limited to, portable electronic devices equipped with IOS system, Android system, Microsoft system or other operating systems. The above portable electronic devices can also be other portable electronic devices, such as a laptop computer. It should also be understood that in some other embodiments, the above electronic device may not be a portable electronic device, but a desktop computer. The electronic device can also be a server, etc., which is not limited here.

[0039] As the intensity of personal information protection gradually increases, in terms of application programs collecting user personal information, the regulatory intensity faced by major application program manufacturers is also gradually increasing. For different user information, such as the user's personal credit information and the International Mobile Equipment Identity (IMEI) of the user's device, their regulatory intensity and acquisition permissions are different. Specifically, since personal credit information includes the user's identity information, borrowing information, asset information, etc., which involves more sensitive information, the regulatory intensity for the user's personal credit information may be greater than that for the IMEI of the user's device. Due to the different regulatory intensities of different user information, when an application program collects user information, if the same permission is set to obtain different user information, it is difficult to ensure the compliance of information collection and it is easy to violate regulatory rules.

[0040] Based on the above problems, this application provides a data compliance acquisition method and related device, which will be described in detail below with reference to the accompanying drawings.

[0041] The data compliance acquisition method provided in the embodiments of this application can be applied to, for example Figure 1In the system architecture shown, the system architecture includes a client device 102 and a server 104. Among them, the client device 102 can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, and portable wearable devices, and the server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0042] Among them, the data compliance collection method provided in the embodiments of the present application can be executed by the client device 102 or by the server 104, which is not limited herein.

[0043] When the execution entity is the server 104, the server 104 responds to the current data collection request of the application program of the client device 102, determines the target data code value corresponding to the current data collection request; if the target data code value indicates that the collection status of the current target data is non - collectable, returns a null value to the application program of the client device 102; if the target data code value indicates that the collection status of the current target data is collectable, determines whether the application program meets the compliance collection conditions of the current target data. If the application program of the client device 102 meets the compliance collection conditions of the current target data, obtains the cached data corresponding to the current target data and the update time of the cached data, determines the cache duration of the cached data according to the current time of the client device and the update time of the cached data, determines whether the cached data is valid according to the cache duration and a preset cache duration threshold. If the cached data is valid, returns the cached data to the application program of the client device 102.

[0044] When the execution entity is the client device 102, the processor of the client device 102 responds to the current data collection request of the application program, determines the target data code value corresponding to the current data collection request. If the target data code value indicates that the collection status of the current target data is non - collectable, returns a null value to the application program; if the target data code value indicates that the collection status of the current target data is collectable, determines whether the application program meets the compliance collection conditions of the current target data. If the application program meets the compliance collection conditions of the current target data, obtains the cached data corresponding to the current target data and the update time of the cached data, determines the cache duration of the cached data according to the current time of the client device and the update time of the cached data, determines whether the cached data is valid according to the cache duration and a preset cache duration threshold. If the cached data is valid, returns the cached data to the application program.

[0045] Please refer to Figure 2A , Figure 2AIt is a schematic structural diagram of an electronic device provided by an embodiment of the present application. The electronic device can be a client device or a server. The electronic device includes a processor, a memory, and so on. Among them, the memory is connected to the processor. The processor is the control center of the electronic device, connecting various parts of the entire electronic device through various interfaces and lines, and by running or executing software programs and / or modules stored in the memory, as well as calling data stored in the memory, it executes various functions of the electronic device and processes data, thereby monitoring the electronic device as a whole. The processor can be a Central Processing Unit / Processor (CPU), a Graphics Processing Unit (GPU), or a Neural-network Processing Unit (NPU).

[0046] Further, the processor may integrate an application processor and a modem processor. Among them, the application processor mainly processes the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor may not be integrated into the processor.

[0047] Among them, the memory is used to store software programs and / or modules. The processor executes various functional applications of the electronic device by running the software programs and / or modules stored in the memory. The memory may mainly include a program storage area and a data storage area. Among them, the program storage area may store the operating system, software programs required for at least one function, etc.; the data storage area may store data created according to the use of the electronic device. In addition, the memory may include high-speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0048] Please refer to Figure 2B , Figure 2B It is a schematic flowchart of a data compliance collection method provided by an embodiment of the present application. As shown in the figure, it is applied to the electronic device as shown in Figure 2A The present data compliance collection method includes:

[0049] Step 101: In response to the current data collection request of the application program, determine the target data code value corresponding to the current data collection request.

[0050] Among them, the data collection requests correspond to the target data one by one, and the current target data is the data collected corresponding to the current data collection request. As mentioned above, due to the different collection situations of different target data (such as whether the target data is sensitive data, the supervision intensity of the target data, the time of collecting the target data, etc.), the R & D personnel pre-write the collection instructions for each type of target data, and different collection instructions are used to collect different target data.

[0051] Among them, the above target data code value is used to represent the collection status of the current target data, and the above collection status includes collectable and non-collectable. Each collection instruction for a target data includes a data code value, and the data code value is used to identify the collection instruction, so the data code value is unique. It can be understood that if the data code value carried in the data collection request exists in the database, it means that the collection instruction for the target data corresponding to the data code value exists, that is to say, the target data is in a collectable state. On the contrary, if the data code value carried in the data collection request does not exist in the database, it means that the collection instruction for the target data corresponding to the data code value does not exist, that is to say, the R & D personnel have not studied and developed the collection of the target data, and the target data is in a non-collectable state.

[0052] Step 102: If the target data code value indicates that the collection status of the current target data is non-collectable, return a null value to the application program.

[0053] That is to say, the target data code value corresponding to the current data collection request initiated by the application program does not exist in the database, and the R & D personnel have not studied and developed the collection of the target data, and the target data is in a non-collectable state. Therefore, at this time, a null value is directly returned to the application program of the user terminal device, avoiding subsequent searching for the target data in the massive data of the database, which helps to improve the efficiency of data collection.

[0054] Step 103: If the target data code value indicates that the collection status of the current target data is collectable, determine whether the application program meets the compliance collection conditions of the current target data.

[0055] Among them, the compliance collection conditions correspond to the target data one by one. As mentioned above, due to the different collection situations of different target data (such as whether the target data is sensitive data, the supervision intensity of the target data, the time of collecting the target data, etc.), the compliance collection conditions corresponding to the target data are also different. In order to make the data collection meet the supervision requirements of relevant departments, different compliance collection conditions are set for different target data in this application.

[0056] Step 104: If the application program meets the compliance collection conditions of the current target data, obtain the cached data corresponding to the current target data and the update time of the cached data.

[0057] Step 105: Determine the caching duration of the cached data based on the current time of the client device and the update time of the cached data.

[0058] Step 106: Determine whether the cached data is valid based on the caching duration and a preset caching duration threshold.

[0059] Step 107: If the cached data is valid, return the cached data to the application.

[0060] Among them, the above-mentioned preset caching duration threshold can be a fixed value preset by R & D personnel, or can vary flexibly according to factors such as the type of target data, the running status of the application, and / or the processor performance of the electronic device, which is not limited here. For example, the preset caching duration threshold can be 30 minutes, 25 minutes, 20 minutes, 18 minutes, 10 minutes, 7 minutes, 5 minutes, 3 minutes, 2 minutes, 1 minute, 45 seconds, 30 seconds, 20 seconds, 15 seconds, 10 seconds, 6 seconds, 2 seconds, etc.

[0061] It can be understood that when the application meets the compliance collection conditions of the current target data, if there is valid cached data stored in the electronic device, the cached data can be directly returned to the application. In this way, it helps to improve the utilization rate of database resources, and also helps to improve the response rate of the application and optimize the user experience.

[0062] In specific implementation, the electronic device responds to the current data collection request of the application, determines the corresponding target data code value. When the target data code value indicates that the collection status of the current target data is collectable, it determines whether the application meets the compliance collection conditions of the current target data. If it meets, it determines whether the cached data corresponding to the current target data is valid according to the current time of the client device, the update time of the cached data, and the preset caching duration threshold. If the cached data is valid, the cached data can be directly returned to the application.

[0063] In this way, before collecting the target data, first judge whether the target data is in a collectable state through the data code value, and during the process of collecting the target data, the collection of the target data is restricted by the compliance collection conditions, which helps to ensure that the data collection meets the regulatory requirements of relevant departments and also helps to improve the efficiency of data collection.

[0064] In a possible example, the above step 103, determining whether the application meets the compliance collection conditions of the current target data, may include the following steps:

[0065] Step 1031: Determine whether obtaining user authorization is required to collect the current target data;

[0066] Step 1032: If obtaining user authorization is required, generate an authorization request page in the application;

[0067] Step 1033: Determine whether the user enters authorization confirmation information on the authorization request page;

[0068] Step 1034: If the user enters authorization confirmation information, determine whether the application meets the collection permission for the current target data;

[0069] Step 1035: If the application meets the collection permission for the current target data, determine that the application meets the compliance collection conditions for the current target data;

[0070] Step 1036: If the user does not enter authorization confirmation information, or the application does not meet the collection permission for the current target data, determine that the application does not meet the compliance collection conditions for the current target data.

[0071] Among them, the input method of the above authorization confirmation information can be that the user clicks the "Agree" control on the authorization request page to input, or the user signs in the corresponding area of the authorization request page, which is not limited here. In addition, the user authorization can also be confirmed according to the authorization confirmation information of the user within the preset period. For example, if the same user has entered authorization confirmation information within 24 hours, then when the user authorization is required again within 24 hours, there is no need to request the user to enter authorization confirmation information again.

[0072] Among them, the collection permission for the above current target data can include the permissions set by the user device for the application, or the permissions set by the application for specific data acquisition scenarios. For example, when obtaining location data, it is necessary for the application to initiate a request to obtain location data to the user device, and it is also necessary for the user device to enable the location function.

[0073] In specific implementation, the compliance collection conditions for the current target data can include the part of user authorization and the part of application collection permission, and the part of user authorization takes precedence over the part of application collection permission. In this way, in the case of user refusal of authorization, it can be directly considered that the application does not meet the compliance collection conditions for the current target data, and the corresponding result is returned to the application, which helps to improve the response efficiency of the application and optimize the user experience.

[0074] For the part of user authorization, first determine whether user authorization is required to collect the current target data. If authorization is required, an authorization request page is generated in the application, and it is detected whether the user enters authorization confirmation information. After the user enters the authorization confirmation information, then judge the part of the application collection permission.

[0075] When the user confirms authorization and the application meets the collection permission for the current target data, it is determined that the application meets the compliance collection conditions for the current target data, and the valid cached data corresponding to the current target data is obtained, and the cached data is returned to the application.

[0076] When the user does not enter the authorization confirmation information, or the application does not meet the collection permission for the current target data, it is determined that the application does not meet the compliance collection conditions for the current target data.

[0077] It can be seen that in the embodiments of the present application, the electronic device can determine whether user authorization is required to collect the current target data. When user authorization is required, an authorization request page is generated in the application, and it is determined whether the user enters the authorization confirmation information on the authorization request page. When the user enters the authorization confirmation information, it is determined whether the application meets the collection permission for the current target data. When the application meets the collection permission for the current target data, it is determined that the application meets the compliance collection conditions for the current target data. When the user does not enter the authorization confirmation information, or the application does not meet the collection permission for the current target data, it is determined that the application does not meet the compliance collection conditions for the current target data; in this way, the compliance collection conditions are divided into the part of user authorization and the part of the application collection permission, and the sequence of the above two parts is limited, with the user's will as the priority. When the user refuses authorization, it can be directly considered that the application does not meet the compliance collection conditions for the current target data, and the corresponding result is returned to the application, which helps to improve the response efficiency of the application and optimize the user experience.

[0078] In a possible example, the above method is applied to the server, and the server is communicatively connected to at least one client device; if the current target data is personal credit data, step 1034 above, determining whether the application meets the collection permission for the current target data, may include the following steps:

[0079] Step 10341: Obtain the unique identification code of each client device, and a unique identification code is used to identify a client device;

[0080] Step 10342: According to the unique identification code, determine the login account that logs in to the application in the same client device, and the login account includes the current login account and the historical login account;

[0081] Step 10343: Count the number of login accounts;

[0082] Step 10344: When the number of login accounts is greater than the preset number threshold, determine that the risk level of the current login account is high risk;

[0083] Step 10345: When the number of logged-in accounts is less than or equal to a preset quantity threshold, determine that the risk level of the current logged-in account is low risk;

[0084] Step 10346: According to the risk level of the current logged-in account, determine whether the application meets the collection permission for personal credit data.

[0085] Among them, there is at least one of the above-mentioned unique identification codes. That is to say, one user terminal device corresponds to one unique identification code. Then, when there is one user terminal device, the obtained unique identification code is also one; when there are multiple user terminal devices, the obtained unique identification codes are also multiple. The unique identification code can be the IMEI code of the user terminal device, or other characters that can uniquely identify the user terminal device, which is not limited here.

[0086] Among them, the above-mentioned preset quantity threshold can be a fixed value preset by R & D personnel, or can vary flexibly according to factors such as the type of target data, the running status of the application, and / or the processor performance of the electronic device, which is not limited here. For example, the preset quantity threshold can be 15, 12, 10, 7, 5, 3, 2, etc.

[0087] In specific implementation, if the current target data is personal credit data, since personal credit information includes the user's identity information, borrowing information, asset information, etc., which involves a lot of sensitive information, the relevant departments have strong supervision over personal credit data. Therefore, when obtaining personal credit data, it is necessary to carefully judge the collection permission of the application.

[0088] For example, the server is communicatively connected to client devices A, B, and C. The server obtains the unique identification code 1234 of client device A, the unique identification code 3456 of client device B, and the unique identification code 5678 of client device C. According to the unique identification code 1234 of device A, it is determined that the number of logged-in accounts on device A is 3. According to the unique identification code 3456 of device B, it is determined that the number of logged-in accounts on device B is 9. According to the unique identification code 5678 of device C, it is determined that the number of logged-in accounts on device C is 1. Assuming that the preset quantity threshold is 6, for device A, the risk level of the currently logged-in account of the application on device A is low risk. Similarly, the risk level of the currently logged-in account of the application on device C is also low risk. Since the number of logged-in accounts on device B is greater than the preset quantity threshold, the currently logged-in account of the application on device B is high risk. According to the risk level of the currently logged-in account, it is determined that the application on device B does not meet the collection permission for personal credit data, and the applications on device A and device C meet the collection permission for personal credit data. That is to say, if the risk level of the currently logged-in account is high risk, the corresponding client device does not meet the collection permission for personal credit data; if the risk level of the currently logged-in account is low risk, the corresponding client device meets the collection permission for personal credit data.

[0089] It can be understood that, generally, the number of logged-in accounts on the same client device usually does not exceed 5. If there are too many logged-in accounts on the same client device, a more likely event is that the user holding the client device is conducting account testing. And except for application developers, those who are likely to conduct account testing are users who are preparing or are in the process of conducting illegal activities. Therefore, the risk of the currently logged-in account can be evaluated by counting the number of logged-in accounts, so as to determine whether the application meets the collection permission for personal credit data. If the user logging in to the application on the client device is malicious, by specifically closing the data collection permission of the application, the personal credit data of the malicious user can be prevented from being collected, and the data collection behavior can be stopped, thereby ensuring to a certain extent that the data collection complies with the regulatory requirements of relevant departments.

[0090] In a possible example, the above method is applied to the server, and the server is communicatively connected to multiple client devices; the above step 1034, determining whether the application meets the collection permission for the current target data, may include the following steps:

[0091] Step 10347: Obtain the location information of each client device;

[0092] The following steps 10348 - 103412 are executed for each client device:

[0093] Step 10348: Determine the reference device of the currently processed client device according to the positioning information. The positioning of the reference device and the positioning of the currently processed client device are both within a preset range. The number of reference devices is the first number, and the first number is a positive integer greater than 2.

[0094] Step 10349: Count the number of reference devices that meet the acquisition permission of the current target data. The number of reference devices that meet the acquisition permission of the current target data is the second number.

[0095] Step 103410: Determine the ratio of the second number to the first number.

[0096] Step 103411: When the ratio is greater than the preset reference threshold, determine that the application meets the acquisition permission of the current target data.

[0097] Step 103412: When the ratio is less than or equal to the preset reference threshold, determine that the application does not meet the acquisition permission of the current target data.

[0098] Among them, the above preset range can be a fixed value preset by R & D personnel, or can vary flexibly according to factors such as the type of target data, the running situation of the application, and / or the processor performance of the electronic device, etc., which is not limited here. For example, the preset range can be 10 kilometers, 8 kilometers, 5 kilometers, 3 kilometers, 2 kilometers, 1 kilometer, 800 meters, 500 meters, 300 meters, 100 meters, 50 meters, etc.

[0099] Among them, the above preset reference threshold can be a fixed value preset by R & D personnel, or can vary flexibly according to factors such as the type of target data, the running situation of the application, and / or the processor performance of the electronic device, etc., which is not limited here. For example, the preset reference threshold can be 45%, 50%, 60%, 66%, 70%, 86%, 90%, etc.

[0100] Among them, the above reference device is other client devices within the preset range except the currently processed client device. The number of reference devices is greater than 2, that is to say, in the embodiments of the present application, the number of client devices communicatively connected to the server is greater than 3.

[0101] In specific implementation, considering that multiple malicious users may gather in one area to commit crimes, therefore, when multiple client devices use the application in the same area, the acquisition permission of the application of the currently processed client device can be determined according to the acquisition permission situation of the application obtained by the reference device.

[0102] For example, set the preset range to 5 kilometers and the preset reference threshold to 50%. The server is communicatively connected to client devices A, B, C, and D. If the positions indicated by the positioning information of A, B, C, and D are within 5 kilometers of each other (which can be understood as the positions of A, B, C, and D can be encompassed within a circle with a diameter of 5 kilometers), then for device A, devices B, C, and D are reference devices. For the current target data (such as microphone input data or camera data, etc.), if among devices B, C, and D, device B does not meet the acquisition permission for the current target data, and devices C and D meet the acquisition permission for the current target data, then the ratio of the second quantity to the first quantity is 66.7%. Since this ratio of 66.7% is greater than the preset reference threshold of 50%, it is determined that device A also meets the acquisition permission for the current target data, that is to say, the application in device A meets the acquisition permission for the current target data.

[0103] In the above embodiments, the acquisition permission of the currently processed client device is mainly determined based on whether the reference devices meet the acquisition permission for the current target data. In another possible implementation, the acquisition permission of the current target data of the current client device can also be determined by the acquisition permission of the same type of target data in the same type of application programs of the reference devices. That is to say, the reference devices can be determined by the same type of target data of the same application program, or by the same type of template data of the same type of application programs.

[0104] Specifically, to determine whether an application meets the acquisition permission for the current target data, the following steps can be included: obtain the category of the application and the category of the current target data; obtain the positioning information of each client device; for each client device, perform the following steps: based on the positioning information, the category of the application, and the category of the current target data, determine the reference devices for the currently processed client device. The positions of the reference devices and the position of the currently processed client device are within the preset range. The number of reference devices is the third quantity, and the third quantity is a positive integer greater than 2. Also, the category of the application of the reference devices is the same as the category of the application in the currently processed client device, and the category of the current target data of the reference devices is the same as the category of the current target data in the currently processed client device. The category of the current target data is the first category; count the number of reference devices that meet the acquisition permission for the target data of the first category. The number of reference devices that meet the acquisition permission for the target data of the first category is the fourth quantity; determine the ratio of the fourth quantity to the third quantity; if the ratio of the fourth quantity to the third quantity is greater than the preset reference threshold, determine that the application meets the acquisition permission for the current target data; if the ratio of the fourth quantity to the third quantity is less than or equal to the preset reference threshold, determine that the application does not meet the acquisition permission for the current target data.

[0105] Among them, the categories of application programs may include financial management, gaming, social networking, etc., which are not limited herein. The categories of target data may include microphone data, camera data, location data, etc., which are not limited herein.

[0106] It can be seen that in the embodiments of the present application, the server is communicatively connected to multiple client devices. The server can obtain the location information of each client device and perform the following steps for each client device: According to the location information, determine the reference device of the currently processed client device. The location of the reference device and the location of the currently processed client device are within a preset range. The number of reference devices is the first number, and the first number is a positive integer greater than 2. Count the number of reference devices that meet the acquisition permission of the current target data. The number of reference devices that meet the acquisition permission of the current target data is the second number. Determine the ratio of the second number to the first number. When the ratio is greater than the preset reference threshold, determine that the application program meets the acquisition permission of the current target data. When the ratio is less than or equal to the preset reference threshold, determine that the application program does not meet the acquisition permission of the current target data. In this way, according to the situation of the application program's acquisition permission obtained from the reference device, determine the acquisition permission of the application program of the currently processed client device, and perform unified management on the client devices within the preset range, which helps to improve the management efficiency of multiple client devices during the process of compliant data acquisition.

[0107] In a possible example, the preset cache duration threshold includes a long cache threshold and a short cache threshold. The above step 106, determining whether the cache data is valid according to the cache duration and the preset cache duration threshold, may include the following steps:

[0108] Step 1061: Determine the data type of the current target data. The data type includes a long cache type and a short cache type;

[0109] Step 1062: If the data type of the current target data is the long cache type, determine whether the cache data is valid according to the cache duration and the long cache threshold;

[0110] Step 1063: If the data type of the current target data is the short cache type, determine whether the cache data is valid according to the cache duration and the short cache threshold.

[0111] Among them, the above long cache type may refer to a data type with a longer update cycle, such as the IMEI of the client device. The long cache type corresponds to the long cache threshold, and the long cache threshold may be a duration such as 30 days, 20 days, 15 days, 7 days, 3 days, 1 day, 8 hours, 3 hours, 1 hour, 30 minutes, 25 minutes, 20 minutes, 18 minutes, 10 minutes, etc., which is not limited herein.

[0112] For example, the long cache threshold is determined to be 30 minutes. If the current target data is the IMEI of the client device, when the cache duration of the IMEI is greater than 30 minutes, the cached data is considered invalid; when the cache duration of the IMEI is less than or equal to 30 minutes, the cached data is considered valid.

[0113] Among them, the above-mentioned short cache type may refer to a data type with a short update cycle, such as the location information of the client device. The short cache type corresponds to a short cache threshold, and the short cache threshold may be a duration such as 7 minutes, 5 minutes, 3 minutes, 2 minutes, 1 minute, 45 seconds, 30 seconds, 20 seconds, 15 seconds, 10 seconds, 6 seconds, 2 seconds, etc., which is not limited here. It should be noted that the long cache duration is greater than the short cache duration.

[0114] For example, the short cache threshold is determined to be 2 seconds. If the current target data is the location information of the client device, when the cache duration of the location information is greater than 2 seconds, the cached data is considered invalid; when the cache duration of the location information is less than or equal to 2 seconds, the cached data is considered valid.

[0115] It can be seen that in the embodiments of the present application, the preset cache duration thresholds include a long cache threshold and a short cache threshold. The electronic device determines the data type of the current target data. When the data type of the current target data is a long cache type, it determines whether the cached data is valid according to the cache duration and the long cache threshold. When the data type of the current target data is a short cache type, it determines whether the cached data is valid according to the cache duration and the short cache threshold. In this way, different cache duration thresholds are determined for different data types, which helps to improve the accuracy and effectiveness of the cached data, helps to ensure the accuracy of data collection, and optimizes the user experience.

[0116] Please refer to Figure 2C , in a possible example, the above method further includes the following steps:

[0117] Step 108: If the cached data is invalid, determine the target acquisition instruction corresponding to the current target data code value;

[0118] Step 109: Acquire the current target data through the target acquisition instruction;

[0119] Step 1010: Update the cached data according to the current target data;

[0120] Step 1011: Update the update time of the cached data according to the current time of the client device;

[0121] Step 1012: Return the current target data to the application program.

[0122] In a specific implementation, the electronic device determines the target data code value corresponding to the current data acquisition request of the application program in response to the current data acquisition request of the application program, and determines whether the current target data is in a collectible state according to the target data code value. If the current target data is in a collectible state and the application program meets the compliance acquisition conditions of the current target data, the valid cached data corresponding to the current target data is obtained and returned to the application program. Specifically, when the cached data expires, the latest current target data can be obtained through the target acquisition instruction corresponding to the current target data, and the cached data is updated. The updated cached data is the latest current target data.

[0123] It can be seen that in the embodiment of the present application, when the cached data expires, the current target data is collected through the target acquisition instruction, and the cached data and the update time of the cached data are updated, which helps to use the still valid cached data when the application program collects the current target data next time. In this way, it helps to improve the utilization rate of database resources, and helps to improve the response rate of the application program and optimize the user experience.

[0124] Please refer to Figure 2D , in a possible example, the above method further includes the following steps:

[0125] Step 1013, if the application program does not meet the compliance acquisition conditions of the current target data, return a null value to the application program.

[0126] It can be understood that in the case where the application program does not meet the compliance acquisition conditions of the current target data, returning a null value to the application program helps to ensure that data acquisition complies with the regulatory requirements of relevant departments and helps to improve the standardization of data acquisition.

[0127] Consistent with the above embodiment, please refer to Figure 3 , Figure 3 is a schematic structural diagram of another electronic device provided by the embodiment of the present application. The electronic device can be a client device or a server. As shown in the figure, the electronic device includes a processor, a memory, and a computer program or instruction stored on the memory. Among them, the above computer program or instruction is stored in the above memory and is configured to be executed by the above processor. The electronic device may further include a communication interface. In the embodiment of the present application, the above program includes instructions for performing the following steps:

[0128] In response to the current data acquisition request of the application program, determine the target data code value corresponding to the current data acquisition request, where the data acquisition request corresponds to the target data one by one, the current target data is the data to be collected corresponding to the current data acquisition request, and the target data code value is used to represent the acquisition state of the current target data, and the acquisition state includes collectible and non - collectible;

[0129] If the target data code value indicates that the acquisition status of the current target data is non - acquirable, return a null value to the application program;

[0130] If the target data code value indicates that the acquisition status of the current target data is acquirable, determine whether the application program meets the compliance acquisition conditions for the current target data. The compliance acquisition conditions correspond to the target data one by one;

[0131] If the application program meets the compliance acquisition conditions for the current target data, obtain the cache data corresponding to the current target data and the update time of the cache data;

[0132] Determine the cache duration of the cache data according to the current time of the client device and the update time of the cache data;

[0133] Determine whether the cache data is valid according to the cache duration and the preset cache duration threshold;

[0134] If the cache data is valid, return the cache data to the application program.

[0135] It can be seen that the electronic device described in the embodiments of the present application can respond to the current data acquisition request of the application program, determine the target data code value corresponding to the current data acquisition request. If the target data code value indicates that the acquisition status of the current target data is non - acquirable, return a null value to the application program. If the target data code value indicates that the acquisition status of the current target data is acquirable, determine whether the application program meets the compliance acquisition conditions for the current target data. If the application program meets the compliance acquisition conditions for the current target data, obtain the cache data corresponding to the current target data and the update time of the cache data, determine the cache duration of the cache data according to the current time of the client device and the update time of the cache data, determine whether the cache data is valid according to the cache duration and the preset cache duration threshold, and if the cache data is valid, return the cache data to the application program. In this way, before collecting the target data, first judge whether the target data is in an acquirable state through the data code value, and during the process of collecting the target data, restrict the acquisition of the target data through the compliance acquisition conditions, which helps to ensure that the data acquisition meets the regulatory requirements of relevant departments and also helps to improve the efficiency of data acquisition.

[0136] In a possible example, in terms of determining whether the application program meets the compliance acquisition conditions for the current target data, the above - mentioned program includes instructions for performing the following steps:

[0137] Determine whether obtaining user authorization is required for collecting the current target data;

[0138] If user authorization is required, generate an authorization request page in the application program;

[0139] Determine whether the user enters authorization confirmation information on the authorization request page;

[0140] If the user enters authorization confirmation information, determine whether the application meets the collection permission for the current target data;

[0141] If the application meets the collection permission for the current target data, determine that the application meets the compliance collection conditions for the current target data;

[0142] If the user does not enter authorization confirmation information, or the application does not meet the collection permission for the current target data, determine that the application does not meet the compliance collection conditions for the current target data.

[0143] In a possible example, the electronic device is a server, and the server is communicatively connected to at least one client device; if the current target data is personal credit data, in determining whether the application meets the collection permission for the current target data, the above program includes instructions for performing the following steps:

[0144] Obtain the unique identification code of each client device, where one unique identification code is used to identify one client device, and there is at least one unique identification code;

[0145] According to the unique identification code, determine the login accounts that log in to the application in the same client device, where the login accounts include the current login account and historical login accounts;

[0146] Count the number of login accounts;

[0147] In the case where the number of login accounts is greater than the preset number threshold, determine that the risk level of the current login account is high risk;

[0148] In the case where the number of login accounts is less than or equal to the preset number threshold, determine that the risk level of the current login account is low risk;

[0149] According to the risk level of the current login account, determine whether the application meets the collection permission for personal credit data.

[0150] In a possible example, the electronic device is a server, and the server is communicatively connected to multiple client devices; in determining whether the application meets the collection permission for the current target data, the above program includes instructions for performing the following steps:

[0151] Obtain the location information of each client device;

[0152] For each client device, perform the following steps:

[0153] Based on the positioning information, determine the reference device of the currently processed client device. The positioning of the reference device and the positioning of the currently processed client device are both within a preset range, and the number of reference devices is the first number, where the first number is a positive integer greater than 2;

[0154] Count the number of reference devices that meet the acquisition permission for the current target data. The number of reference devices that meet the acquisition permission for the current target data is the second number;

[0155] Determine the ratio of the first number to the second number;

[0156] If the ratio is greater than a preset reference threshold, determine that the application meets the acquisition permission for the current target data;

[0157] If the ratio is less than or equal to the preset reference threshold, determine that the application does not meet the acquisition permission for the current target data.

[0158] In a possible example, the preset cache duration threshold includes a long cache threshold and a short cache threshold. In determining whether the cached data is valid based on the cache duration and the preset cache duration threshold, the above program includes instructions for performing the following steps:

[0159] Determine the data type of the current target data. The data type includes a long cache type and a short cache type;

[0160] If the data type of the current target data is the long cache type, determine whether the cached data is valid according to the cache duration and the long cache threshold;

[0161] If the data type of the current target data is the short cache type, determine whether the cached data is valid according to the cache duration and the short cache threshold.

[0162] In a possible example, the above program includes instructions for performing the following steps:

[0163] If the cached data is invalid, determine the current target acquisition instruction corresponding to the current target data code value;

[0164] Acquire the current target data through the current target acquisition instruction;

[0165] Update the cached data according to the current target data;

[0166] Update the update time of the cached data according to the current time of the client device;

[0167] Return the current target data to the application.

[0168] In a possible example, the above program includes instructions for performing the following steps:

[0169] If the application does not meet the compliance collection conditions for the current target data, a null value is returned to the application.

[0170] The above mainly introduces the solution of the embodiment of the present application from the perspective of the execution process on the method side. It can be understood that in order to implement the above functions, it includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combined with the units and algorithm steps of each example described in the embodiments provided in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware 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.

[0171] The embodiments of the present application can divide functional units according to the above method examples. For example, each functional unit can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation.

[0172] Please refer to Figure 4 , Figure 4 which is a block diagram of the functional unit composition of a data compliance collection device provided by an embodiment of the present application. The device 400 includes: a response unit 401, a determination unit 402, an acquisition unit 403, and a return unit 404, where

[0173] The response unit 401 is configured to, in response to a current data collection request of an application, determine a target data code value corresponding to the current data collection request, where the data collection request corresponds to the target data one by one, the current target data is the data to be collected corresponding to the current data collection request, and the target data code value is used to represent the collection status of the current target data, and the collection status includes collectable and non - collectable;

[0174] The return unit 404 is configured to, when the target data code value indicates that the collection status of the current target data is non - collectable, return a null value to the application;

[0175] The determination unit 402 is configured to, when the target data code value indicates that the collection status of the current target data is collectable, determine whether the application meets the compliance collection conditions for the current target data, and the compliance collection conditions correspond to the target data one by one;

[0176] An acquisition unit 403, configured to acquire cache data corresponding to the current target data and the update time of the cache data when the application meets the compliance acquisition condition of the current target data;

[0177] A determination unit 402, further configured to determine the cache duration of the cache data according to the current time of the client device and the update time of the cache data;

[0178] The determination unit 402 is further configured to determine whether the cache data is valid according to the cache duration and a preset cache duration threshold;

[0179] A return unit 404, further configured to return the cache data to the application if the cache data is valid.

[0180] It can be seen that the data compliance acquisition device described in the embodiments of the present application can, in response to the current data acquisition request of the application, determine the target data code value corresponding to the current data acquisition request. If the target data code value indicates that the acquisition status of the current target data is non-acquirable, an empty value is returned to the application. If the target data code value indicates that the acquisition status of the current target data is acquirable, it is determined whether the application meets the compliance acquisition condition of the current target data. If the application meets the compliance acquisition condition of the current target data, the cache data corresponding to the current target data and the update time of the cache data are acquired, the cache duration of the cache data is determined according to the current time of the client device and the update time of the cache data, and it is determined whether the cache data is valid according to the cache duration and a preset cache duration threshold. If the cache data is valid, the cache data is returned to the application. In this way, before collecting the target data, it is first determined whether the target data is in an acquirable state through the data code value, and during the process of collecting the target data, the acquisition of the target data is restricted by the compliance acquisition condition, which helps to ensure that the data acquisition complies with the regulatory requirements of relevant departments and also helps to improve the efficiency of data acquisition.

[0181] In a possible example, in terms of determining whether the application meets the compliance acquisition condition of the current target data, the determination unit 402 is specifically configured to:

[0182] Determine whether obtaining user authorization is required to collect the current target data;

[0183] If user authorization is required, an authorization request page is generated in the application;

[0184] Determine whether the user enters authorization confirmation information on the authorization request page;

[0185] If the user enters authorization confirmation information, determine whether the application meets the acquisition permission of the current target data;

[0186] If the application meets the acquisition permission for the current target data, it is determined that the application meets the compliance acquisition conditions for the current target data;

[0187] If the user does not enter the authorization confirmation information, or the application does not meet the acquisition permission for the current target data, it is determined that the application does not meet the compliance acquisition conditions for the current target data.

[0188] In a possible example, the data compliance acquisition device is a server, and the server is communicatively connected to at least one client device; if the current target data is personal credit data, in determining whether the application meets the acquisition permission for the current target data, the determining unit 402 is specifically configured to:

[0189] Obtain the unique identification code of each client device, where one unique identification code is used to identify one client device, and the number of unique identification codes is at least one;

[0190] According to the unique identification code, determine the login accounts that log in to the application on the same client device, where the login accounts include the current login account and historical login accounts;

[0191] Count the number of login accounts;

[0192] In the case where the number of login accounts is greater than the preset number threshold, determine that the risk level of the current login account is high risk;

[0193] In the case where the number of login accounts is less than or equal to the preset number threshold, determine that the risk level of the current login account is low risk;

[0194] According to the risk level of the current login account, determine whether the application meets the acquisition permission for personal credit data.

[0195] In a possible example, the data compliance acquisition device is a server, and the server is communicatively connected to multiple client devices; in determining whether the application meets the acquisition permission for the current target data, the determining unit 402 is specifically configured to:

[0196] Obtain the location information of each client device;

[0197] For each client device, perform the following steps:

[0198] According to the location information, determine the reference device of the currently processed client device, where the location of the reference device and the location of the currently processed client device are within the preset range, and the number of reference devices is the first number, and the first number is a positive integer greater than 2;

[0199] Count the number of reference devices that meet the acquisition permission for the current target data, and the number of reference devices that meet the acquisition permission for the current target data is the second number;

[0200] Determine the ratio of the first quantity to the second quantity;

[0201] When the ratio is greater than a preset reference threshold, determine that the application meets the acquisition permission for the current target data;

[0202] When the ratio is less than or equal to the preset reference threshold, determine that the application does not meet the acquisition permission for the current target data.

[0203] In a possible example, the preset cache duration threshold includes a long cache threshold and a short cache threshold. In determining whether the cached data is valid according to the cache duration and the preset cache duration threshold, the determination unit 402 is specifically configured to:

[0204] Determine the data type of the current target data, where the data type includes a long cache type and a short cache type;

[0205] If the data type of the current target data is the long cache type, determine whether the cached data is valid according to the cache duration and the long cache threshold;

[0206] If the data type of the current target data is the short cache type, determine whether the cached data is valid according to the cache duration and the short cache threshold.

[0207] In a possible example, the determination unit 402 is specifically further configured to:

[0208] If the cached data is invalid, determine the current target acquisition instruction corresponding to the current target data code value;

[0209] Acquire the current target data through the current target acquisition instruction;

[0210] Update the cached data according to the current target data;

[0211] Update the update time of the cached data according to the current time of the client device;

[0212] Return the current target data to the application.

[0213] In a possible example, the determination unit 402 is specifically further configured to:

[0214] If the application does not meet the compliance acquisition conditions for the current target data, return a null value to the application.

[0215] It can be understood that the functions of the various program modules of the data compliance acquisition device in this embodiment can be specifically implemented according to the methods in the above method embodiments, and the specific implementation process can refer to the relevant descriptions of the above method embodiments, which will not be elaborated here.

[0216] An embodiment of the present application further provides a computer storage medium. The computer storage medium stores a computer program for electronic data exchange, and the computer program causes a computer to execute some or all of the steps of any one of the methods described in the foregoing method embodiments.

[0217] An embodiment of the present application further provides a computer program product. The computer program product includes a computer program, and the computer program is operable to cause a computer to execute some or all of the steps of any one of the methods described in the foregoing method embodiments. A computer program product should be understood as a software product that mainly realizes its solution through a computer program.

[0218] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0219] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

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

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

[0222] In addition, the functional units in the various embodiments of the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0223] If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on such an understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned memory includes: USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical discs, etc., which are various media that can store program codes.

[0224] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing relevant hardware through a program. This program can be stored in a computer-readable memory, and the memory can include: flash drives, read-only memories (abbreviation: ROM), random access memories (abbreviation: RAM), magnetic disks, or optical discs, etc.

[0225] The above has introduced the embodiments of this application in detail. Specific examples are used in this article to elaborate on the principles and implementation manners of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation to this application.

Claims

1. A data compliance collection method, characterized in that, The method includes: In response to a current data collection request of an application, determining a target data code value corresponding to the current data collection request, where the data collection request corresponds to target data one by one, the current target data is the data to be collected corresponding to the current data collection request, and the target data code value is used to represent the collection status of the current target data, and the collection status includes collectable and non - collectable; If the target data code value indicates that the collection status of the current target data is non - collectable, then return a null value to the application; If the target data code value indicates that the collection status of the current target data is collectable, then determine whether the application meets the compliance collection conditions for the current target data, and the compliance collection conditions correspond to the target data one by one; If the application meets the compliance collection conditions for the current target data, then obtain the cached data corresponding to the current target data and the update time of the cached data; According to the current time of the client device and the update time of the cached data, determine the cache duration of the cached data; According to the cache duration and a preset cache duration threshold, determine whether the cached data is valid; If the cached data is valid, then return the cached data to the application.

2. The method according to claim 1, wherein The determining whether the application meets the compliance collection conditions for the current target data includes: Determining whether obtaining user authorization is required to collect the current target data; If user authorization is required, then generate an authorization request page in the application; Determine whether the user enters authorization confirmation information on the authorization request page; If the user enters the authorization confirmation information, then determine whether the application meets the collection permission for the current target data; If the application meets the collection permission for the current target data, then determine that the application meets the compliance collection conditions for the current target data; If the user does not enter the authorization confirmation information, or the application does not meet the collection permission for the current target data, then determine that the application does not meet the compliance collection conditions for the current target data.

3. The method according to claim 2, wherein The method is applied to a server, and the server is communicatively connected to at least one client device; if the current target data is personal credit data, the determining whether the application meets the collection permission for the current target data includes: Obtain the unique identification code of each client device, where one unique identification code is used to identify one client device, and there are at least one unique identification codes; According to the unique identification code, determine the login accounts that log in to the application on the same client device, and the login accounts include the current login account and historical login accounts; Count the number of the login accounts; In the case where the number of the login accounts is greater than a preset number threshold, determine that the risk level of the current login account is high - risk; In the case where the number of the login accounts is less than or equal to the preset number threshold, determine that the risk level of the current login account is low - risk; Determine whether the application program meets the collection permission of the personal credit data according to the risk level of the current logged-in account.

4. The method according to claim 2, wherein The method is applied to a server, and the server is communicatively connected to a plurality of client devices; determining whether the application program meets the collection permission of the current target data includes: Obtain the location information of each client device; Perform the following steps for each client device: According to the location information, determine a reference device of the currently processed client device, the location of the reference device and the location of the currently processed client device are within a preset range, the number of the reference devices is a first number, and the first number is a positive integer greater than 2; Count the number of reference devices that meet the collection permission of the current target data, and the number of reference devices that meet the collection permission of the current target data is a second number; Determine the ratio of the second number to the first number; If the ratio is greater than a preset reference threshold, determine that the application program meets the collection permission of the current target data; If the ratio is less than or equal to the preset reference threshold, determine that the application program does not meet the collection permission of the current target data.

5. The method according to claim 1, wherein The preset cache duration threshold includes a long cache threshold and a short cache threshold. Determining whether the cache data is valid according to the cache duration and the preset cache duration threshold includes: Determine the data type of the current target data, and the data type includes a long cache type and a short cache type; If the data type of the current target data is the long cache type, determine whether the cache data is valid according to the cache duration and the long cache threshold; If the data type of the current target data is the short cache type, determine whether the cache data is valid according to the cache duration and the short cache threshold.

6. The method according to claim 1, wherein The method further includes: If the cache data is invalid, determine the current target collection instruction corresponding to the current target data code value; Collect the current target data through the current target collection instruction; Update the cache data according to the current target data; Update the update time of the cache data according to the current time of the client device; Return the current target data to the application program.

7. The method according to claim 1, characterized in that, The method further includes: If the application program does not meet the compliance collection conditions of the current target data, return a null value to the application program.

8. A data compliance acquisition device, characterized in that, Includes: A response unit, a determination unit, an acquisition unit, and a return unit, wherein The response unit is configured to respond to a current data collection request of an application program, and determine a target data code value corresponding to the current data collection request, wherein the data collection request corresponds to the target data one by one, the current target data is the data collected corresponding to the current data collection request, and the target data code value is used to represent the collection status of the current target data, and the collection status includes collectable and non-collectable; The return unit is configured to return a null value to the application program when the target data code value indicates that the collection status of the current target data is non-collectable; The determining unit is configured to determine whether the application meets the compliance collection condition of the current target data when the target data code value indicates that the collection status of the current target data is collectable, and the compliance collection condition corresponds to the target data one by one; The obtaining unit is configured to obtain the cached data corresponding to the current target data and the update time of the cached data when the application meets the compliance collection condition of the current target data; The determining unit is further configured to determine the caching duration of the cached data according to the current time of the client device and the update time of the cached data; The determining unit is further configured to determine whether the cached data is valid according to the caching duration and a preset caching duration threshold; The returning unit is further configured to return the cached data to the application if the cached data is valid.

9. An electronic device, characterized in that, It includes a processor and a memory. The memory is used to store one or more programs and is configured to be executed by the processor. The programs include instructions for performing the steps in the method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, A computer program for electronic data exchange is stored, wherein the computer program causes a computer to execute the instructions for performing the steps in the method according to any one of claims 1-7.

Images