Privacy data processing method and device, electronic device, and readable storage medium

Abstract

The disclosure provides a privacy data processing method and device, electronic equipment and readable storage medium, relates to the technical field of computers, in particular to the technical field of mobile platform technology, application development and the like. The specific implementation scheme is as follows: a plurality of privacy application programming interfaces are configured according to a preset privacy rule; each privacy application programming interface corresponds to at least one function function, and the function function of the function function is to process privacy data; the plurality of configured privacy application programming interfaces are encapsulated to generate a calling application programming interface for calling by an application function module.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to the fields of mobile platform technology and application development. Specifically, this disclosure relates to privacy data processing methods and apparatus, electronic devices, computer-readable storage media, and computer program products. Background Technology

[0002] With technological and social development, the protection of personal privacy data has become a major focus of attention across all sectors of society. As the protection of personal privacy data becomes increasingly important, the need to build a robust privacy protection system that complies with regulations is becoming more and more urgent. Summary of the Invention

[0003] This disclosure provides a method and apparatus for processing privacy data, an electronic device, a computer-readable storage medium, and a computer program product.

[0004] According to a first aspect of this disclosure, a privacy data processing method is provided, the method comprising:

[0005] Multiple privacy application programming interfaces are configured according to preset privacy rules; each privacy application programming interface corresponds to at least one function, and the function of the function is to process privacy data;

[0006] The configured privacy application programming interfaces are encapsulated to generate application programming interfaces that can be called by application function modules.

[0007] According to a second aspect of this disclosure, a privacy data processing apparatus is provided, the apparatus comprising:

[0008] A configuration module is used to configure multiple privacy application programming interfaces according to preset privacy rules; each privacy application programming interface corresponds to at least one function, and the function of the function is to process privacy data;

[0009] The encapsulation module is used to encapsulate multiple configured privacy application programming interfaces (APIs) and generate APIs for application function modules to call.

[0010] According to a third aspect of this disclosure, an electronic device is provided, the electronic device comprising:

[0011] At least one processor; and

[0012] A memory communicatively connected to at least one of the aforementioned processors; wherein,

[0013] The memory stores instructions that can be executed by at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the privacy data processing method.

[0014] According to a fourth aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause a computer to perform the above-described privacy data processing method.

[0015] According to a fifth aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the above-described privacy data processing method.

[0016] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0018] Figure 1 This is a schematic flowchart of a privacy data processing method provided in an embodiment of this disclosure;

[0019] Figure 2 This is a flowchart illustrating some steps of another privacy data processing method provided in this embodiment of the disclosure;

[0020] Figure 3 This is a flowchart illustrating some steps of another privacy data processing method provided in this embodiment of the disclosure;

[0021] Figure 4 This is a flowchart illustrating some steps of another privacy data processing method provided in this embodiment of the disclosure;

[0022] Figure 5 This is a flowchart illustrating some steps of another privacy data processing method provided in this embodiment of the disclosure;

[0023] Figure 6 This is a flowchart illustrating some steps of another privacy data processing method provided in this embodiment of the disclosure;

[0024] Figure 7 This is a flowchart illustrating some steps of another privacy data processing method provided in this embodiment of the disclosure;

[0025] Figure 8 This is a schematic diagram of the structure of a privacy data processing device provided in an embodiment of this disclosure;

[0026] Figure 9 This is a block diagram of an electronic device used to implement the privacy data processing method of the embodiments of this disclosure. Detailed Implementation

[0027] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0028] Because the software development kit for mobile devices (such as mobile phones) contains many business modules, any changes to the privacy policy will require these business modules to be modified to comply with privacy regulations, even if these functional modules already meet the privacy policy requirements.

[0029] In some related technologies, each functional module can be adapted to comply with the privacy policy to ensure that it meets the requirements. However, this method relies on the responsiveness of each functional module, which leads to long development cycles and high manpower costs. Furthermore, developers of different functional modules may have inconsistent interpretations of the privacy policy, which can easily introduce new problems and cannot efficiently cope with ever-changing privacy policies.

[0030] In some related technologies, mobile platforms can be used to scan applications to obtain API (Application Programming Interface) call information related to privacy policies, and then notify the corresponding functional modules to make corrections.

[0031] However, this method relies on the scanning results of the mobile platform, which is difficult to cover all user scenarios. There may be cases where privacy APIs are missed in individual scenarios. Furthermore, the scanned functional modules already require individual modification. Therefore, it still suffers from long development cycles, high manpower costs, and the potential to introduce new problems, making it difficult to efficiently cope with ever-changing privacy policies.

[0032] The privacy data processing methods and apparatuses, electronic devices, computer-readable storage media, and computer program products provided in this disclosure are intended to solve at least one of the above-mentioned technical problems of the prior art.

[0033] The privacy data processing method provided in this disclosure can be executed by an electronic device such as a terminal device or a server. The terminal device can be an in-vehicle device, user equipment (UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. The method can be implemented by a processor calling computer-readable program instructions stored in memory. Alternatively, the method can be executed by a server.

[0034] Figure 1 A flowchart illustrating the privacy data method provided in an embodiment of this disclosure is shown. Figure 1 As shown in the embodiments of this disclosure, the privacy data method may include steps S110 and S120.

[0035] In step S110, multiple privacy application programming interfaces are configured according to preset privacy rules;

[0036] In step S120, the configured multiple privacy application programming interfaces are encapsulated to generate a calling application programming interface for application function modules to call.

[0037] For example, the privacy data processing method provided in this disclosure can be used for application development on mobile development platforms (such as Android, HarmonyOS, iOS, etc.).

[0038] In some possible implementations, in step S110, the multiple privacy application programming interfaces (i.e., privacy APIs) can be privacy data-related APIs in a mobile development platform.

[0039] An API is a predefined set of functions that perform specific functionalities. Its purpose is to provide developers with the ability to access a set of routines based on certain software or hardware, without needing access to the source code or understanding the details of the internal workings. Similarly, each privacy API includes one or more functions, at least one of which can perform the function of processing privacy-preserving data.

[0040] In other words, the APIs related to privacy data, i.e., the corresponding function functions, are APIs that process privacy data.

[0041] Processing privacy data can include collecting privacy data, storing privacy data, modifying privacy data, and deleting privacy data.

[0042] Taking the HarmonyOS NEXT platform as an example, Accessibility Kit, TelephonyKit, NetworkKit, LocationKit, AbilityKit, InputKit, SensorServiceKit, etc. all include APIs related to privacy data.

[0043] In some possible implementations, the preset privacy rules can be generated based on the privacy policy. These rules can include the types of privacy data that can be collected, the corresponding collection frequency and collection scenarios, the storage method of privacy data, and any rules for processing privacy data, such as the permission to modify privacy data.

[0044] In some possible implementations, preset privacy rules can be obtained through manual interpretation of the privacy policy, or through interpretation of the privacy policy using a large language model, etc. This disclosure does not limit the method for obtaining privacy rules.

[0045] In some possible implementations, configuring multiple privacy APIs according to preset privacy rules can be achieved by restricting the usage conditions of the privacy APIs to ensure that their processing of privacy data complies with the preset privacy rules. Since the privacy rules are derived from the interpretation of the privacy policy, the fact that the privacy APIs' processing of privacy data complies with the preset privacy rules is equivalent to the privacy APIs' processing of privacy data complying with the privacy policy.

[0046] In some possible implementations, in step S120, the configured multiple privacy APIs are encapsulated into a new calling API for application function modules to call.

[0047] In some possible implementations, encapsulating multiple configured privacy APIs may include setting up API calling functions, standards, access protocols, authentication methods, etc., based on the configured privacy APIs, so that the API calling can be integrated into the software development environment for application function modules to call.

[0048] Of course, any other method that can encapsulate an API for use by application function modules is also within the scope of protection of this disclosure.

[0049] In some possible implementations, the application functional modules can be the software development kit of a mobile development platform.

[0050] Taking the HarmonyOS NEXT platform as an example, the application's functional module can be a HAP; taking the Android platform as an example, the application's functional module can be an SDK (Software Development Kit).

[0051] Once the privacy API is configured, if the processing of privacy data by the privacy API complies with the privacy policy, then the encapsulated API for calling privacy data will also comply with the privacy policy. By calling the API and using the corresponding function to process privacy data, the application's functional modules can ensure that their processing of privacy data complies with the privacy policy.

[0052] In the privacy data processing method provided in this disclosure embodiment, the privacy API is configured and encapsulated according to privacy rules so that the processing of privacy data by the privacy API complies with the privacy policy, thereby ensuring that the processing of privacy data by application functional modules through the privacy API also complies with the privacy policy.

[0053] The privacy data processing method provided in the embodiments of this disclosure will be described in detail below.

[0054] As mentioned above, in some possible implementations, configuring multiple privacy APIs according to preset privacy rules can be achieved by restricting the usage conditions of the privacy APIs to ensure that the processing of privacy data by the privacy APIs complies with the preset privacy rules.

[0055] Figure 2 This diagram illustrates a specific implementation method for ensuring that the processing of private data by the privacy API complies with preset privacy rules by restricting the conditions under which the privacy API is used.

[0056] like Figure 2 As shown, restricting the use of the privacy API to ensure that its processing of privacy data complies with preset privacy rules may include steps S210 and S220.

[0057] In step S210, the usage conditions of the functions corresponding to multiple privacy application programming interfaces are determined according to preset privacy rules;

[0058] In step S220, multiple privacy application programming interfaces are configured according to the usage conditions.

[0059] In some possible implementations, in step S210, the usage restrictions of privacy data can be determined according to preset privacy rules, and the usage conditions of the function functions used to process privacy data can be determined according to the usage restrictions of privacy data, thereby determining the usage conditions of the function functions corresponding to each privacy API.

[0060] In some possible implementations, in step S220, the usage conditions of the function corresponding to the privacy API are determined, and the privacy API is configured so that the use of the function corresponding to the privacy API satisfies the usage conditions of the function corresponding to the privacy API.

[0061] Since APIs consist of predefined functions, configuring privacy APIs by restricting the usage conditions of the corresponding functions can avoid modifying the predefined functions in the API. This reduces the workload of configuring privacy APIs, and if privacy rules change, only the usage conditions of the corresponding functions need to be changed.

[0062] As mentioned above, in some specific implementations, privacy rules can include the types of privacy data that can be collected. Figure 3 This diagram illustrates a specific implementation method for ensuring that the processing of privacy data by the privacy API complies with preset privacy rules when the privacy rules include the types of privacy data that can be collected.

[0063] like Figure 3 As shown, restricting the use of the privacy API to ensure that its processing of privacy data complies with preset privacy rules may include steps S310, S320, and S330.

[0064] In step S310, based on preset privacy rules, the privacy data that can be collected and the privacy data that cannot be collected are determined.

[0065] In step S320, the privacy application programming interface for collecting collectable privacy data is configured to be called by application function modules;

[0066] In step S330, the privacy application programming interface for collecting non-collectible privacy data is configured to be uncallable.

[0067] In some possible implementations, in step S310, collectable privacy data and non-collectable privacy data can be determined based on the type of collectable privacy data.

[0068] In some possible implementations, in steps S320 and S330, a switch can be set for each privacy API. The privacy API switch that enables the corresponding function to collect collectable privacy data can be turned on for use by application function modules, while the privacy API switch that enables the corresponding function to collect non-collectable privacy data can be turned off to prevent it from being called.

[0069] By making certain privacy APIs uncallable, it is easy and direct to prevent the collection of specific types of privacy data. For example, user identity information can be prevented from being collected by setting the privacy API that collects user identity information to be uncallable.

[0070] In some specific implementations, privacy rules may also include the scenarios in which privacy data is collected. Figure 4 This diagram illustrates a specific implementation method for ensuring that the processing of privacy data by the privacy API complies with preset privacy rules when privacy rules include scenarios involving the collection of privacy data.

[0071] like Figure 4 As shown, restricting the use of the privacy API to ensure that its processing of privacy data complies with preset privacy rules may include steps S410 and S420.

[0072] In step S410, the data collection scenario for privacy data is determined according to preset privacy rules;

[0073] In step S420, the first privacy application programming interface is configured to be called by the application function module when the use scenario of the application function module meets the data collection scenario.

[0074] In some possible implementations, in step S410, the collection scenario for collecting privacy data in the privacy rules is the data collection scenario for privacy data.

[0075] In some specific implementations, data collection scenarios can include foreground scenarios, background scenarios, screen-on scenarios, and screen-off scenarios.

[0076] In some possible implementations, in step S420, the first privacy application programming interface (first privacy API) corresponds to at least one function, and the function of the function is to collect privacy data. That is to say, the first privacy API is also a privacy API, which is a privacy API used to collect privacy data.

[0077] In some possible implementations, scene information representing the current scene of the application's functional modules can be received. By comparing the scene information with the data collection scene, if the comparison is consistent, the corresponding privacy API (i.e., the first privacy API) can be called by the application's functional modules.

[0078] The above settings can protect privacy data in certain scenarios. For example, setting the privacy API to not be called in the background can prevent application modules from collecting privacy data in the background.

[0079] In some specific implementations, privacy rules may also include the frequency of collecting privacy data. Figure 5 This diagram illustrates a specific implementation method for ensuring that the processing of privacy data by the privacy API complies with preset privacy rules when the privacy rules include the frequency of collection of privacy data.

[0080] like Figure 5 As shown, restricting the use of the privacy API to ensure that its processing of privacy data complies with preset privacy rules may include steps S510 and S520.

[0081] In step S510, the data collection frequency of privacy data is determined according to preset privacy rules;

[0082] In step S520, the second privacy application programming interface is configured to be available for use by the application function module when the frequency of calling privacy data is no greater than the data collection frequency.

[0083] In some possible implementations, in step S510, the collection frequency of privacy data in the privacy rules is the data collection frequency of privacy data.

[0084] In some specific implementations, the data acquisition frequency can be based on natural days, or the acquisition frequency can be set freely.

[0085] In some possible implementations, in step S520, the second privacy application programming interface (second privacy API) corresponds to at least one function, and the function of the function is to collect privacy data. That is to say, the second privacy API is also a privacy API, which is a privacy API used to collect privacy data.

[0086] In some possible implementations, frequency information representing the frequency at which application function modules collect privacy information can be received. By comparing the frequency information with the data collection frequency, the corresponding privacy API (i.e., the second privacy API) can be called by the application function modules only if the frequency information is not greater than the data collection frequency.

[0087] The above settings can be used to limit the frequency of privacy data collection, such as setting it to only collect privacy data on a daily basis.

[0088] In some specific implementations, privacy rules may also include how privacy data is stored. Figure 6This diagram illustrates a specific implementation method for ensuring that the processing of privacy data by the privacy API complies with preset privacy rules, where privacy rules include the method of storing privacy data.

[0089] like Figure 6 As shown, restricting the use of the privacy API to ensure that its processing of privacy data complies with preset privacy rules may include steps S610 and S620.

[0090] In step S610, the data caching method for privacy data is determined according to preset privacy rules;

[0091] In step S620, the third privacy application programming interface is configured to write privacy data to the storage device using a data caching method.

[0092] In some possible implementations, in step S610, the storage method of privacy data in the privacy rules is the data caching method of privacy data.

[0093] In some specific implementations, privacy data caching methods can include memory caching (i.e., temporary storage) and file caching (i.e., persistent storage).

[0094] In some possible implementations, in step S620, the third privacy application programming interface (third privacy API) corresponds to at least one function, and the function of the function is to write privacy data to a storage device. That is to say, the third privacy API is also a privacy API, which is a privacy API used to store privacy data.

[0095] In some possible implementations, when the privacy data is cached temporarily, the privacy APIs for functions that are cached in memory can be made callable, while those for functions that are cached in files can be made uncallable. Conversely, privacy APIs for functions that are cached in memory can be made uncallable, while those for functions that are cached in files can be made callable.

[0096] The above settings allow you to restrict how private data is stored, such as setting it to only allow temporary private data.

[0097] Among some possible implementations, the above settings for the privacy API can be achieved by configuring functional modules.

[0098] Figure 7 The diagram illustrates a specific implementation method for configuring a privacy API by setting functional modules, such as... Figure 7 As shown, setting up the privacy API by configuring the functional module can include steps S710, S720, and S730.

[0099] In step S710, a functional module is set up to call the privacy application programming interface function according to preset conditions;

[0100] In step S720, the calling conditions for multiple privacy application programming interfaces are determined according to preset privacy rules;

[0101] In step S730, based on the calling conditions, multiple privacy application programming interfaces are configured by combining the set functional modules.

[0102] In some specific implementations, in step S710, the functional module can be a cloud-controlled switch.

[0103] In some specific implementations, each privacy API can be set with a separate cloud control switch. When the cloud control switch is on, the privacy API can be called; when the cloud control switch is off, the privacy API cannot be called.

[0104] In some specific implementations, separate cloud control switches can be set for foreground, background, screen-on, and screen-off scenarios. When the corresponding cloud control switch for the foreground scenario is turned on, the privacy API can be called in the foreground scenario; when the corresponding cloud control switch for the foreground scenario is turned off, the privacy API cannot be called in the foreground scenario.

[0105] Similarly, in background scenarios, the privacy API is accessible when the corresponding cloud control switch is on, and inaccessible when it is off. In screen-on scenarios, the privacy API is accessible when the corresponding cloud control switch is on, and inaccessible when it is off. Similarly, in screen-off scenarios, the privacy API is accessible when the corresponding cloud control switch is on, and inaccessible when it is off.

[0106] In some specific implementations, a cloud control switch can be set for a daily data collection frequency, and another can be freely configured. When the cloud control switch for the daily collection frequency is on, the privacy API can be called daily. When the cloud control switch for the freely configured frequency is on, the frequency of calling the privacy API can be freely set.

[0107] In some specific implementations, a cloud control switch corresponding to temporary storage can be set. When the cloud control switch for temporary storage is on, the corresponding function enables the privacy API settings for the memory cache to be called; when the cloud control switch for temporary storage is off, the corresponding function disables the privacy API settings for the memory cache.

[0108] In some specific implementations, a cloud control switch corresponding to permanent storage can be set. When the cloud control switch for permanent storage is turned on, the corresponding function enables the calling of the privacy API for memory caching; when the cloud control switch for permanent storage is turned off, the corresponding function disables the calling of the privacy API for memory caching.

[0109] Both storage methods can be turned on or off individually, or simultaneously, and each storage interval can be configured separately.

[0110] In some specific implementations, in steps S720 and S730, the privacy API is configured by combining cloud control switches according to the calling conditions.

[0111] By setting up cloud control switches, developers can configure privacy APIs through combinations of switches, further reducing their workload and improving the efficiency of API configuration.

[0112] In some possible implementations, when the privacy policy changes, new privacy rules are generated. If the privacy rules are updated, the above methods are used to reconfigure and encapsulate multiple privacy application programming interfaces according to the updated privacy rules.

[0113] The privacy API is configured and encapsulated according to the updated privacy rules to ensure that its processing of privacy data complies with the updated privacy policy. This guarantees that the processing of privacy data by application modules through the privacy API also complies with the updated privacy policy, eliminating the need for each application module to be individually modified according to the updated privacy policy. This solves the problems of long development cycles, high manpower costs, easy introduction of new issues, and inefficiency in dealing with ever-changing privacy policies.

[0114] To better support API calls by application modules, facilitate business access, and enhance privacy compliance, this disclosure also includes quality control over privacy data processing during the development, compilation, testing, and online phases.

[0115] In some possible implementations, during the development phase, a software development kit (SDK) is generated based on calls to the application programming interface (API), and the generated SSD is used by application functional modules for invocation.

[0116] During the development phase, software development kits (SDKs) can be generated based on API calls through integration. Specifically, API calls support two integration methods: HAR (Hypertext Repository) and OHPM (OpenHarmony Package Manager, provided by the OpenHarmony third-party repository website and command-line tools). After integration, developers using HAR or OHPM do not need to record or consult privacy APIs during development. When writing code involving privacy APIs, the system will automatically prompt for replacement with API calls.

[0117] In some possible implementations, during the compilation phase, the submitted code is inspected to obtain the privacy interface code within the submitted code; the privacy interface code is then replaced with the interface call code.

[0118] Among them, the privacy interface code is the code used to call the privacy application programming interface; the interface call code is the code used to call the encapsulated application programming interface.

[0119] During the compilation phase, when code is committed to the repository, the submitted code is automatically scanned and detected. If any privacy APIs are not replaced with API calls, a warning is issued, requiring modification before submission. During compilation, all code in the repository is checked, and if any updates to privacy data processing methods are made, a prompt will be issued to change to API calls.

[0120] In some possible implementations, during the testing phase, test results from the application functional module testing phase are received, and multiple privacy application programming interfaces are configured based on the test results.

[0121] During the testing phase, static and dynamic testing are conducted. Static testing includes decompiling and scanning for privacy data to ensure compliance with the privacy policy. Dynamic testing monitors privacy API calls, scenarios, and cached log readings to dynamically check whether the handling of privacy data complies with the privacy policy.

[0122] If static and dynamic tests reveal that the processing of privacy data does not comply with the privacy policy, the privacy API will be configured to comply with the privacy policy based on the test results.

[0123] In some possible implementations, during the online phase, monitoring results are received after the application functional modules are launched, and multiple privacy application programming interfaces are configured based on the monitoring results.

[0124] During the online phase, after the application's functional modules are launched, data reports based on data collection metrics are used to monitor and issue early warnings regarding online privacy data compliance. Based on the monitoring results after launch, the privacy API is configured to ensure that its processing of privacy data complies with the privacy policy.

[0125] Based on and Figure 1 The method shown follows the same principle. Figure 8 A schematic diagram of the structure of a privacy data processing apparatus provided in an embodiment of this disclosure is shown, such as... Figure 8 As shown, the privacy data processing device 80 may include:

[0126] The configuration module 810 is used to configure multiple privacy application programming interfaces according to preset privacy rules; each privacy application programming interface corresponds to at least one function, and the function of the function is to process privacy data;

[0127] The encapsulation module 820 is used to encapsulate multiple configured privacy application programming interfaces (APIs) to generate APIs for application function modules to call.

[0128] In the privacy data processing apparatus provided in this disclosure embodiment, the privacy API is configured and encapsulated according to privacy rules so that the processing of privacy data by the privacy API complies with the privacy policy, thereby ensuring that the processing of privacy data by application function modules through the privacy API also complies with the privacy policy.

[0129] In some possible implementations, the configuration module includes: a condition determination unit, used to determine the usage conditions of the functions corresponding to multiple privacy application programming interfaces according to preset privacy rules; and an interface configuration unit, used to configure multiple privacy application programming interfaces according to the usage conditions.

[0130] In some possible implementations, the condition determination unit is used to: determine the collectable privacy data and the non-collectable privacy data according to preset privacy rules; the interface configuration unit is used to: configure the privacy application programming interface whose function is to collect collectable privacy data for use by application function modules; and configure the privacy application programming interface whose function is to collect non-collectable privacy data as non-callable.

[0131] In some possible implementations, the condition determination unit is used to: determine the data collection scenario of privacy data according to preset privacy rules; the interface configuration unit is used to: configure the first privacy application programming interface to be called by the application functional module when the usage scenario of the application functional module meets the data collection scenario; the first privacy application programming interface corresponds to at least one function, and the function of the function is to collect privacy data.

[0132] In some possible implementations, the condition determination unit is used to: determine the data collection frequency of privacy data according to preset privacy rules; the interface configuration unit is used to: configure the second privacy application programming interface to be called by the application function module when the frequency of calling privacy data is not greater than the data collection frequency; the second privacy application programming interface corresponds to at least one function, and the function of the function is to collect privacy data.

[0133] In some possible implementations, the condition determination unit is used to: determine the data caching method of privacy data according to preset privacy rules; the interface configuration unit is used to: configure the third privacy application programming interface to write privacy data to the storage device using the data caching method; the third privacy application programming interface corresponds to at least one function, and the function of the function is to write privacy data to the storage device.

[0134] In some possible implementations, the privacy data processing device further includes: a functional module for setting up a functional module that calls privacy application programming interface functions according to preset conditions; and a configuration module for: determining the calling conditions of multiple privacy application programming interfaces according to preset privacy rules; and configuring multiple privacy application programming interfaces by combining the set functional modules according to the calling conditions.

[0135] In some possible implementations, the privacy data processing apparatus further includes an update module for reconfiguring multiple privacy application programming interfaces according to the updated privacy rules when the privacy rules are updated.

[0136] In some possible implementations, the privacy data processing device further includes: a development module for generating a software development kit based on calls to an application programming interface, the software development kit being used by application function modules for invocation.

[0137] In some possible implementations, the privacy data processing device further includes: a compilation module for detecting submitted code and obtaining privacy interface code in the submitted code; the privacy interface code for calling a privacy application programming interface; replacing the privacy interface code with interface call code; and the interface call code for calling the encapsulated application programming interface.

[0138] In some possible implementations, the privacy data processing device further includes a testing module for receiving test results from the application functional module testing phase and configuring multiple privacy application programming interfaces based on the test results.

[0139] In some possible implementations, the privacy data processing device also includes an online module for receiving monitoring results after the application function modules are online, and configuring multiple privacy application programming interfaces based on the monitoring results.

[0140] It is understood that the above-described modules of the privacy data processing apparatus in the embodiments of this disclosure have the ability to implement... Figure 1 The embodiments shown illustrate the functionality of corresponding steps in the privacy data processing method. This functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. These modules can be software and / or hardware, and each module can be implemented individually or multiple modules can be integrated. For a detailed description of the functions of each module in the aforementioned privacy data processing device, please refer to [link to relevant documentation]. Figure 1 The corresponding descriptions of the privacy data processing methods in the embodiments shown are not repeated here.

[0141] The acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0142] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0143] The electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the privacy data processing method provided in the embodiments of this disclosure.

[0144] Compared with existing technologies, this electronic device configures and encapsulates the privacy API according to privacy rules, so that the processing of privacy data by the privacy API complies with the privacy policy, thereby ensuring that the processing of privacy data by application functional modules through the privacy API also complies with the privacy policy.

[0145] The readable storage medium is a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the privacy data processing method provided in the embodiments of this disclosure.

[0146] Compared with existing technologies, this readable storage medium configures and encapsulates the privacy API according to privacy rules, so that the processing of privacy data by the privacy API complies with the privacy policy, thereby ensuring that the processing of privacy data by application functional modules through the privacy API also complies with the privacy policy.

[0147] The computer program product includes a computer program that, when executed by a processor, implements the privacy data processing method provided in the embodiments of this disclosure.

[0148] Compared with existing technologies, this computer program product configures and encapsulates the privacy API according to privacy rules, so that the processing of privacy data by the privacy API complies with the privacy policy, thereby ensuring that the processing of privacy data by application functional modules through the privacy API also complies with the privacy policy.

[0149] Figure 9 A schematic block diagram of an example electronic device 900 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0150] like Figure 9 As shown, device 900 includes a computing unit 901, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 902 or a computer program loaded from storage unit 908 into random access memory (RAM) 903. RAM 903 may also store various programs and data required for the operation of device 900. The computing unit 901, ROM 902, and RAM 903 are interconnected via bus 904. Input / output (I / O) interface 905 is also connected to bus 904.

[0151] Multiple components in device 900 are connected to I / O interface 905, including: input unit 906, such as keyboard, mouse, etc.; output unit 907, such as various types of monitors, speakers, etc.; storage unit 908, such as disk, optical disk, etc.; and communication unit 909, such as network card, modem, wireless transceiver, etc. Communication unit 909 allows device 900 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0152] The computing unit 901 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 901 performs the various methods and processes described above, such as privacy data processing methods. For example, in some embodiments, the privacy data processing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program may be loaded and / or installed on device 900 via ROM 902 and / or communication unit 909. When the computer program is loaded into RAM 903 and executed by the computing unit 901, one or more steps of the privacy data processing method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform privacy data processing methods by any other suitable means (e.g., by means of firmware).

[0153] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0154] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0155] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0156] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0157] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0158] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0159] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0160] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for processing privacy data, comprising: The calling conditions of multiple privacy application programming interfaces are determined according to preset privacy rules; each privacy application programming interface corresponds to at least one function, and the function of the function is to process privacy data; Based on the calling conditions, multiple privacy application programming interfaces are configured by combining preset functional modules; the functional modules are cloud-controlled switches that can independently control the privacy application programming interfaces. The configured privacy application programming interfaces are encapsulated to generate application programming interfaces that can be called by application function modules; The application programming interface (API) is invoked by one or more application function modules to access the configured functions of the multiple privacy APIs to process privacy data, thereby ensuring that the processing of privacy data by the application function modules conforms to the preset privacy rules.

2. The method according to claim 1, further comprising: Based on preset privacy rules, determine the usage conditions of the functions corresponding to the multiple privacy application programming interfaces; Configure multiple privacy application programming interfaces according to the stated usage conditions.

3. The method according to claim 2, wherein, The step of determining the usage conditions of the functions corresponding to multiple privacy application programming interfaces according to preset privacy rules includes: Based on preset privacy rules, determine which privacy data can be collected and which cannot. The configuration of multiple privacy application programming interfaces according to the usage conditions includes: Configure the privacy application programming interface (API) for collecting the collectable privacy data to be called by application function modules; Configure the privacy application programming interface (API) that collects the non-collectible privacy data as uncallable.

4. The method according to claim 2, wherein, The step of determining the usage conditions of the functions corresponding to multiple privacy application programming interfaces according to preset privacy rules includes: Determine the data collection scenarios for privacy data based on preset privacy rules; The configuration of multiple privacy application programming interfaces according to the usage conditions includes: The first privacy application programming interface is configured to be called by the application functional module when the usage scenario of the application functional module meets the data collection scenario; the first privacy application programming interface corresponds to at least one function, and the function of the function is to collect the privacy data.

5. The method according to claim 2, wherein, The step of determining the usage conditions of the functions corresponding to multiple privacy application programming interfaces according to preset privacy rules includes: The frequency of privacy data collection is determined based on preset privacy rules; The step of configuring the usage conditions of the functions corresponding to multiple privacy application programming interfaces according to preset privacy rules includes: The second privacy application programming interface is configured to be called by the application function module when the frequency of the application function module calling the privacy data is no greater than the data collection frequency; the second privacy application programming interface corresponds to at least one function, and the function of the function is to collect the privacy data.

6. The method according to claim 2, wherein, The step of determining the usage conditions of the functions corresponding to multiple privacy application programming interfaces according to preset privacy rules includes: Determine the data caching method for privacy data based on preset privacy rules; The step of configuring the usage conditions of the functions corresponding to multiple privacy application programming interfaces according to preset privacy rules includes: The third privacy application programming interface is configured to write the privacy data to a storage device using the data caching method; the third privacy application programming interface corresponds to at least one function, and the function of the function is to write the privacy data to the storage device.

7. The method according to claim 1, further comprising: Set up a functional module that can invoke the privacy application programming interface function according to preset conditions.

8. The method according to claim 1, further comprising: If the privacy rules are updated, multiple privacy application programming interfaces are reconfigured according to the updated privacy rules.

9. The method according to claim 1, further comprising: A software development kit (SDK) is generated based on the application programming interface (API) call, and the SSD is used for application function modules to call.

10. The method according to claim 1, further comprising: The submitted code is inspected to extract the privacy interface code within it. The privacy interface code is used to call the privacy application programming interface; Replace the privacy interface code with the interface call code; The interface call code is used to invoke the application programming interface.

11. The method according to claim 1, further comprising: Receive the test results from the application functional module testing phase, and configure multiple privacy application programming interfaces based on the test results.

12. The method according to claim 1, further comprising: Receive monitoring results after the application function modules are launched, and configure multiple privacy application programming interfaces based on the monitoring results.

13. A privacy data processing apparatus, comprising: A configuration module is used to determine the calling conditions of multiple privacy application programming interfaces (APIs) according to preset privacy rules; each API corresponds to at least one function, and the function of the function is to process privacy data; according to the calling conditions, multiple APIs are configured by combining preset function modules; the function modules are cloud-controlled switches that can independently control the APIs. The encapsulation module is used to encapsulate multiple configured privacy application programming interfaces (APIs) and generate APIs for application function modules to call. The application programming interface (API) is invoked by one or more application function modules to access the configured functions of the multiple privacy APIs to process privacy data, thereby ensuring that the processing of privacy data by the application function modules conforms to the preset privacy rules.

14. The apparatus according to claim 13, wherein, The configuration module includes: The condition determination unit is used to determine the usage conditions of the functions corresponding to the multiple privacy application programming interfaces according to preset privacy rules. An interface configuration unit is used to configure multiple privacy application programming interfaces according to the usage conditions.

15. The apparatus according to claim 14, wherein, The condition determination unit is used to: determine the collectable privacy data and the non-collectable privacy data according to preset privacy rules; The interface configuration unit is used to: configure the privacy application programming interface whose function is to collect the collectable privacy data as callable by the application function module; and configure the privacy application programming interface whose function is to collect the non-collectable privacy data as uncallable.

16. The apparatus according to claim 14, wherein, The condition determination unit is used to: determine the data collection scenario for privacy data according to preset privacy rules; The interface configuration unit is used to: configure the first privacy application programming interface to be called by the application function module when the usage scenario of the application function module meets the data collection scenario; the first privacy application programming interface corresponds to at least one function, and the function of the function is to collect the privacy data.

17. The apparatus according to claim 14, wherein, The condition determination unit is used to: determine the data collection frequency of privacy data according to preset privacy rules; The interface configuration unit is used to: configure the second privacy application programming interface to be called by the application function module when the frequency of the application function module calling the privacy data is not greater than the data collection frequency; the second privacy application programming interface corresponds to at least one function, and the function of the function is to collect the privacy data.

18. The apparatus according to claim 14, wherein, The condition determination unit is used to: determine the data caching method for privacy data according to preset privacy rules; The interface configuration unit is used to: configure the third privacy application programming interface to write the privacy data to the storage device using the data caching method; the third privacy application programming interface corresponds to at least one function, and the function of the function is to write the privacy data to the storage device.

19. The apparatus of claim 13, further comprising: A functional module is used to set up a functional module that can call the privacy application programming interface function according to preset conditions.

20. The apparatus of claim 13, further comprising: An update module is used to reconfigure multiple privacy application programming interfaces according to the updated privacy rules when the privacy rules are updated.

21. The apparatus of claim 13, further comprising: The development module is used to generate a software development kit based on the application programming interface, and the software development kit is used for application function modules to call.

22. The apparatus of claim 13, further comprising: The compilation module is used to inspect the submitted code and obtain the privacy interface code in the submitted code; The privacy interface code is used to call the privacy application programming interface; Replace the privacy interface code with the interface call code; The interface call code is used to invoke the application programming interface.

23. The apparatus of claim 13, further comprising: The testing module is used to receive the test results of the application functional module testing phase and configure multiple privacy application programming interfaces based on the test results.

24. The apparatus of claim 13, further comprising: The online module is used to receive monitoring results after the application function modules are launched, and to configure multiple privacy application programming interfaces based on the monitoring results.

25. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-12.

26. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-12.

27. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-12.

Images