Privacy protection method, apparatus, device, medium, and product

Abstract

The application discloses a privacy protection method and device, equipment, medium and product. The method comprises the following steps: obtaining configuration content input by a user in a visual interface, wherein the configuration content comprises calling detail information corresponding to M privacy application programming interfaces (APIs), and M is a positive integer; translating the calling detail information of the M privacy APIs into a plurality of JS script files through a function service; and delivering the plurality of JS script files to a terminal device, so that the terminal device defines a calling rule of the privacy APIs according to the JS script files, and calls the privacy APIs according to the calling rule. According to the embodiment of the application, the occurrence of abnormal calling behaviors of the privacy APIs can be effectively avoided, the privacy protection strength is improved, and the security of personal information of the user is ensured.

Description

Technical Field

[0001] This application belongs to the field of computer technology, and in particular relates to a privacy protection method, device, equipment, medium and product. Background Technology

[0002] As regulatory authorities tighten their control over the collection of privacy information, they have launched several campaigns to crack down on illegal and irregular collection and use of personal information by mobile applications (APPs).

[0003] In related technologies, in order to enhance privacy protection and safeguard personal information, the privacy-preserving method call behavior of Application Programming Interfaces (APIs) can be detected. However, the detection results are usually delayed in the transmission of sensitive data. Therefore, the privacy protection solutions in related technologies cannot provide real-time protection, have insufficient privacy protection, and cannot guarantee the security of users' personal information. Summary of the Invention

[0004] This application provides a privacy protection method, apparatus, device, medium, and product that can effectively prevent abnormal calls to privacy APIs, enhance privacy protection, and ensure the security of users' personal information.

[0005] In a first aspect, embodiments of this application provide a privacy protection method, the method comprising:

[0006] Obtain the configuration content input by the user in the visual interface, where the configuration content includes call details information corresponding to M privacy application programming interface APIs, where M is a positive integer;

[0007] The function service translates the call details of M privacy APIs into multiple JS script files;

[0008] Multiple JS script files are distributed to the terminal device so that the terminal device can define the calling rules of the privacy API according to the JS script files and call the privacy API according to the calling rules.

[0009] Secondly, embodiments of this application provide a privacy protection device, the device comprising:

[0010] The acquisition module is used to acquire the configuration content entered by the user in the visual interface. The configuration content includes call details information corresponding to M privacy application programming interface APIs, where M is a positive integer.

[0011] The translation module is used to translate the call details of M privacy APIs into multiple JS script files via a function service;

[0012] The distribution module is used to distribute multiple JS script files to the terminal device, so that the terminal device can define the calling rules of the privacy API according to the JS script files and call the privacy API according to the calling rules.

[0013] Thirdly, embodiments of this application provide an electronic device, including: a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the privacy protection method shown in the first aspect.

[0014] Fourthly, embodiments of this application provide a computer-readable storage medium on which a program or instructions are stored, and when the program or instructions are executed by a processor, the steps of the privacy protection method as described in the first aspect are implemented.

[0015] Fifthly, embodiments of this application provide a computer program product stored in a non-volatile storage medium, which, when executed by at least one processor, implements the steps of the privacy protection method as described in the first aspect.

[0016] In a sixth aspect, embodiments of this application provide a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the steps of the privacy protection method as described in the first aspect.

[0017] This application provides a privacy protection method, apparatus, device, medium, and product. It offers a visual interface for flexibly configuring privacy API call details. Subsequently, a function service can translate the call details of M privacy APIs into multiple JS script files. Based on this, multiple JS script files can be promptly distributed to the terminal device, enabling the terminal device to define privacy API call rules according to the JS script files. This allows for highly flexible configuration of privacy API call rules, meeting the needs of privacy method calls in various business scenarios. Furthermore, by promptly distributing JS script files to define privacy API call rules, the privacy API call methods on the terminal device become effective immediately. Subsequent calls to the privacy API follow the defined call rules, effectively preventing abnormal privacy API call behavior. This achieves real-time dynamic protection of privacy method calls on the terminal device, enhancing privacy protection and ensuring the security of user personal information. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1A flowchart of an embodiment of the privacy protection method provided in the first aspect of this application;

[0020] Figure 2 An exemplary schematic diagram of the visual interface provided for the first aspect of this application;

[0021] Figure 3 A flowchart of another embodiment of the privacy protection method provided in the first aspect of this application;

[0022] Figure 4 A flowchart of yet another embodiment of the privacy protection method provided in the first aspect of this application;

[0023] Figure 5 A schematic diagram of the structure of an embodiment of the privacy protection device provided in the second aspect of this application;

[0024] Figure 6 A schematic diagram of the structure of an embodiment of the electronic device provided in the third aspect of this application. Detailed Implementation

[0025] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0026] In related technologies, to enhance privacy protection and safeguard personal information, the privacy-preserving call behavior of Application Programming Interfaces (APIs) can be detected to identify normal or abnormal call behavior. However, when abnormal call behavior is identified, it means that the abnormal call behavior has already occurred, and the detection results usually lag behind the transmission of sensitive data. Therefore, the privacy protection solutions in related technologies cannot achieve real-time protection, have insufficient privacy protection capabilities, and cannot guarantee the security of users' personal information.

[0027] To address the aforementioned issues, this application provides a privacy protection method, apparatus, device, medium, and product. It offers a visual interface for flexibly configuring privacy API call details. Subsequently, a function service can translate the call details of M privacy APIs into multiple JS script files. Based on this, multiple JS script files can be promptly distributed to the terminal device, enabling it to define privacy API call rules according to these files. This allows for highly flexible configuration of privacy API call rules, meeting the needs of various business scenarios. Furthermore, by promptly distributing JS script files to define privacy API call rules, the privacy API call methods on the terminal device become effective immediately. Subsequent calls to the privacy API follow the defined rules, effectively preventing abnormal privacy API calls and achieving real-time dynamic protection of privacy method calls on the terminal device. This enhances privacy protection and ensures the security of user personal information.

[0028] The privacy protection method in this application embodiment can be applied to API call scenarios of terminal devices. The privacy protection method provided in this application embodiment will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0029] The first aspect of this application provides a privacy protection method that can be applied to a privacy protection platform, meaning that the privacy protection method can be executed by the privacy protection platform. It should be noted that the aforementioned executing entity does not constitute a limitation on this application.

[0030] Figure 1 A flowchart illustrating an embodiment of the privacy protection method provided in the first aspect of this application. Figure 1 As shown, the privacy protection method may include steps 110-130.

[0031] Step 110: Obtain the configuration content entered by the user in the visual interface. The configuration content includes call details information corresponding to M privacy application programming interface APIs.

[0032] Step 120: Translate the call details of the M privacy APIs into multiple JS script files using a function service;

[0033] Step 130: Distribute multiple JS script files to the terminal device so that the terminal device can define the calling rules of the privacy API according to the JS script files and call the privacy API according to the calling rules.

[0034] The privacy protection method provided in this application embodiment offers a visual interface for flexibly configuring the call details of privacy APIs. Subsequently, a function service can translate the call details of M privacy APIs into multiple JS script files. Based on this, multiple JS script files can be promptly distributed to the terminal device, enabling the terminal device to define the calling rules of the privacy APIs according to the JS script files. This allows for customized configuration of the privacy API calling rules, offering high flexibility and meeting the needs of privacy method calls in various business scenarios. Furthermore, by promptly distributing JS script files to define the calling rules of the privacy APIs, the calling methods of the privacy APIs on the terminal device become effective immediately. Subsequent calls to the privacy APIs will be executed according to the defined calling rules, effectively preventing abnormal privacy API call behavior. This achieves real-time dynamic protection of privacy method calls on the terminal device, enhancing privacy protection and ensuring the security of users' personal information.

[0035] The specific implementation of the above steps will be described in detail below with reference to the embodiments.

[0036] Step 110 involves obtaining the configuration content input by the user in the visual interface. The configuration content includes call details information corresponding to M privacy application programming interface APIs.

[0037] In step 110, M is a positive integer, and the privacy API can be an API that involves calling privacy device permissions, such as camera permissions, album permissions, contact permissions, microphone permissions, location permissions, etc. This application does not make specific limitations on this.

[0038] The visual interface is the front-end interface of the privacy protection platform, specifically the rule configuration interface for privacy APIs. In this visual interface, users can configure the calling rules for each privacy API and obtain the calling details information for each privacy API. Therefore, the calling details information contains the calling rules corresponding to the privacy API, which are the business calling logic or calling restriction scope of the privacy API.

[0039] In some embodiments of this application, the calling rule may include a calling time period, a calling frequency threshold, and a calling count threshold within the calling time period.

[0040] Specifically, the call time period, call frequency threshold, and call count threshold can be flexibly configured in the visual interface, with the call time period being the effective period of the call rule. Different call time periods, call frequency thresholds, and call count thresholds can be configured for different privacy APIs, or the same call time period, call frequency threshold, and call count threshold can be configured. That is, the call rules for different privacy APIs can be the same or different.

[0041] For example, for a privacy API that queries camera access status, the call time period can be set to 12 months after the current time, and the call frequency threshold within the call time period can be limited to 10 times / day, and the call count threshold can be 10,000 times.

[0042] In this application embodiment, for different privacy APIs, the call time period, call frequency threshold, and call count threshold within the call time period can be flexibly configured, providing a high degree of configuration freedom and meeting different business scenarios.

[0043] In some embodiments, the invocation rule may further include triggering conditions, input parameters, return values, and authorized access personnel identifiers.

[0044] In related technologies, the restriction on privacy method calls is a one-size-fits-all principle: privacy methods are either called or not called, with only YES or NO options, and no other flexible rules are available.

[0045] In some embodiments of this application, to improve the flexibility of privacy method invocation, step 110 above, which obtains the configuration content input by the user in the visual interface, may specifically include:

[0046] Obtain at least one call detail information configured by the user for each privacy API in the visualization interface, and obtain multiple call detail information for M privacy APIs.

[0047] The call details may include the target terminal range and target application range selected by the user, as well as the call rules configured for the privacy API under the target terminal range and target application range. At least one call details information contains different call rules for the same privacy API under different target terminal ranges and / or different target application ranges.

[0048] Specifically, after receiving initial user input (selecting the target terminal range and target application range) through a visual interface, the privacy protection platform can then receive a second user input (configuring the calling rules for the privacy API) and associate the combination of the target terminal range and target application range with the calling rules for that privacy API. For the same privacy API, different calling rules can be configured for different terminal ranges and / or different target application ranges.

[0049] In this embodiment, the target terminal range refers to the range of terminals to which the calling rules corresponding to the privacy API apply, and the target application range refers to the range of applications to which the calling rules corresponding to the privacy API apply. Combining the target terminal range and the target application range constitutes the calling scenario. For the same privacy API, by configuring different calling rules under different terminal ranges and / or different target application ranges, the calling control of the same privacy API under different calling scenarios can be realized, improving the flexibility of privacy method calling. The privacy API can be called in specific scenarios, providing personalized protection for each privacy API, and achieving strong data protection and privacy management for the client.

[0050] In some embodiments of this application, the privacy protection platform can provide a rule orchestration service based on metadata. The visual interface can be a rule orchestration interface, which can include a first input area, a second input area, and a third input area. The first input area can be used to obtain privacy API call rules, the second input area can be used to obtain the target terminal range corresponding to the privacy API call rules, and the third input area can be used to obtain the target application range corresponding to the privacy API call rules.

[0051] For example, such as Figure 2 As shown, the visualization interface 201 includes a first input area 202, a second input area 203, and a third input area 204. The specific calling rules of the privacy API can be configured in the first input area 202. The applicable terminal range of the specific calling rules in 202, i.e., the target terminal range, can be configured in the second input area 203. The applicable application range of the specific calling rules in 202, i.e., the target application range, can be configured in the third input area 204.

[0052] In some embodiments of this application, obtaining at least one call detail information configured by the user for each privacy API in the visual interface may specifically include:

[0053] Obtain device and application information input by the user;

[0054] Determine the range of target terminals selected by the user based on device information;

[0055] The scope of the target application selected by the user is determined based on the application information.

[0056] The device information includes at least one of the following: runtime environment information, operating system version information, device model information, and device location information. The application information includes at least one of the following: application industry information, application field information, application type, and application identifier.

[0057] For example, such as Figure 2As shown, users can input the call time period, call frequency threshold, and call count threshold through the input boxes in the visual interface to configure the calling rules of the privacy API. By limiting the Runtime environment and operating system version, the target terminal range to which the calling rules of the privacy API apply can be determined. By limiting the APP industry and APP field, the target application range to which the calling rules of the privacy API apply can be determined.

[0058] In this embodiment, by flexibly configuring runtime environment information, operating system version information, device model information, and device location information, the applicable terminal range of privacy API call rules can be precisely limited; by flexibly configuring application industry information, application field information, application type, and application identifier, the applicable application range of privacy API call rules can be precisely limited. Based on this, combined with user-input device information and application information, precise restrictions can be achieved on the applicable scenario range of privacy API call rules, meeting the different call requirements of the same privacy API in different business scenarios, making business more flexible, increasing the possibilities of more API call functions, and improving the flexibility of privacy API calls. In addition, considering security, the distribution of scripts needs to be cautious. It is possible that the distribution of problematic code due to negligence could cause a large number of apps to crash. Therefore, during the gray-scale phase, the target terminal range can be determined based on device information such as region / system / device model. The JS script is first distributed to a portion of terminal devices. After confirming that the privacy API calls are not problematic, it is gradually rolled over to all terminal devices. If there are problems with the privacy API calls, a rollback can be performed. The rollback is implemented by the privacy protection platform sending a rollback command to the terminal devices corresponding to the target terminal range, so that the apps on the terminal devices will not execute the previously distributed JS scripts when they are launched again.

[0059] In other embodiments of this application, the privacy protection platform may also provide a personalized definition service for privacy API call details. The visual interface is a personalized definition interface, which can receive at least one code snippet input by the user for each privacy API. Each code snippet is used to implement the calling rule configuration of the privacy API under the corresponding target terminal range and target application range.

[0060] In this embodiment of the application, developers can also customize the privacy API details pattern, combining the relevant business details of the privacy API to be called with the relevant class and method names and relevant parameters, and write small, specific code snippets for the APP to call.

[0061] Step 120 involves translating the call details of M privacy APIs into multiple JS script files via a function service.

[0062] In step 120, the function service is a crucial hub connecting the preceding and following processes. Through the function service, the configured call details information can be translated into relevant code and verified, such as checking syntax issues. Once the verification is successful, the expected JavaScript script is generated.

[0063] In some embodiments of this application, the function service can also be used to manage the lifecycle of function code, including the deployment, updating, monitoring, and maintenance of functions.

[0064] In some embodiments of this application, in order to improve the security of calling details information, after step 120 and before step 130, the method may further include: encrypting and compressing multiple JS script files; step 130 of sending multiple JS script files to the terminal device may specifically include: sending multiple encrypted and compressed JS script files to the terminal device through a content delivery network.

[0065] Specifically, JS scripts can be encrypted and compressed through function services, and then multiple encrypted and compressed JS scripts can be directly sent to the Content Delivery Network (CDN) through function services, so that the CDN can send JS scripts to the terminal devices nearby.

[0066] In this embodiment of the application, the security of the JS script transmission can be ensured by encrypting and compressing the JS script before it is distributed, thereby ensuring the security of the call details information. At the same time, the compression operation can shorten the transmission time and speed up the distribution efficiency of the JS script through the content delivery network.

[0067] Step 130 involves sending multiple JS script files to the terminal device so that the terminal device can define the calling rules of the privacy API according to the JS script files and call the privacy API according to the calling rules.

[0068] In step 130, the terminal device redefines the calling rules of the privacy API according to the JS script file. That is, the calling rules of the privacy API are updated using the JS script file, overriding the original calling rules, so that the privacy API can be called using the updated calling rules in the future.

[0069] In some embodiments of this application, the update of the calling rules for the privacy API can be triggered by events, such as when the terminal device receives an HTTP request, a warm start event, or a cold start event.

[0070] In some embodiments of this application, Figure 3 This is a flowchart of another embodiment of the privacy protection method provided in the first aspect of this application. Step 130 described above may include... Figure 3 Steps 310 and 320 are shown.

[0071] Step 310: For each call detail information, associate the target terminal range in the call detail information with the JS script corresponding to the call detail information;

[0072] Step 320: Send a JS script associated with the target terminal range to the terminal devices that match the target terminal range, so that the application corresponding to the target application range on the terminal device can call the privacy API by executing the JS script according to the calling rules in the calling details information.

[0073] For example, for the privacy API for querying camera access status, the target terminal range is selected as operating system version A.1, and the target application range is APP1, APP2, and APP3. The calling rule X1 for this target terminal range and target application range is configured: the calling time period is 12 months after the current time, the calling frequency threshold is limited to 10 times / day within the calling time period, and the calling count threshold is 10,000 times. In this way, "operating system version A.1" can be associated with the JS script corresponding to the calling details information. When this JS script is distributed, it is only distributed to terminal devices with "operating system version A.1," so that APP1, APP2, and APP3 on terminal devices with "operating system version A.1" can call the privacy API for querying camera access status according to calling rule X1.

[0074] In this embodiment, the target terminal range corresponding to the same call details information and the JS script are associated. Based on this association, during the script distribution phase, the JS script can be selectively distributed to the appropriate terminal devices. Furthermore, different host apps have different API call service requirements. Therefore, by defining the target application range in the call details information, the JS script can be selectively distributed to specific target host apps, ensuring that the privacy API's JS script acts on the appropriate host app, effectively improving the security of the host app.

[0075] In some embodiments of this application, Figure 4 This is a flowchart of another embodiment of the privacy protection method provided in the first aspect of this application. Step 310 described above may include... Figure 4 Steps 410 and 420 are shown.

[0076] Step 410: Send a notification message to terminal devices that match the target terminal range;

[0077] Step 420: Upon receiving an update confirmation request from the terminal device, send the JS script file to the terminal device.

[0078] The notification message is used to instruct the updating of the calling rules for privacy APIs within the target application scope.

[0079] In this embodiment of the application, after the developer configures the calling rules of the privacy API and distributes the relevant JS scripts of the calling rules, an inquiry notification can be sent to the terminal devices within the target terminal range involved in the newly configured privacy API calling rules, so that users can be informed of the privacy API calling rule update message in a timely manner, and determine whether to update the privacy API calling method in the terminal device based on the user's decision, so as to better meet the user's needs.

[0080] In some embodiments of this application, step 130, which involves sending multiple JS script files to the terminal device, may specifically include:

[0081] Multiple JS script files are distributed to the third-party software development kit (SDK) of the terminal device, so that the third-party SDK can combine the Runtime mechanism and JSCore mechanism to modify the calling method of privacy API by loading the JS script files.

[0082] Specifically, the third-party SDK parses the distributed JS script and modifies the native privacy method function to point to a unified processing function for message forwarding. The context is passed to JSCore, which obtains the selector name and its parameters from the context, forwards the selector name and parameters to the JS privacy method, and executes the JS privacy method. During the execution of the JS privacy method, if a native method is called, the third-party SDK calls the native method via a bridge, obtains the return result, and continues executing the JS privacy method. After the JS privacy method completes execution, it returns the result to the native method, and the entire call process ends.

[0083] In this embodiment, the third-party SDK uses features such as JScore and runtime to dynamically update privacy method calls, directly applying the distributed JS script to the host App. This makes the dynamically distributed privacy API call logic take effect immediately, giving the host App flexible and effective real-time dynamic protection capabilities for privacy methods. This achieves strong data protection and privacy management for the client App, while also dynamically protecting the third-party SDK from calling privacy methods, ensuring that the application complies with privacy regulations and compliance requirements when calling privacy APIs to obtain user privacy information.

[0084] Based on the same inventive concept, the second aspect of this application provides a privacy protection device. Figure 5 A schematic diagram of the structure of an embodiment of the privacy protection device provided in the second aspect of this application.

[0085] like Figure 5 As shown, the privacy protection device 500 may specifically include: an acquisition module 510, a translation module 520, and a distribution module 530.

[0086] The acquisition module 510 is used to acquire the configuration content input by the user in the visual interface. The configuration content includes call details information corresponding to M privacy application programming interface APIs, where M is a positive integer.

[0087] Translate module 520 is used to translate the call details of M privacy APIs into multiple JS script files via function service;

[0088] The distribution module 530 is used to distribute multiple JS script files to the terminal device, so that the terminal device can define the calling rules of the privacy API according to the JS script files and call the privacy API according to the calling rules.

[0089] The privacy protection device provided in this application embodiment can offer a visual interface for flexibly configuring the call details of privacy APIs. Subsequently, a function service can translate the call details of M privacy APIs into multiple JS script files. Based on this, multiple JS script files can be promptly distributed to the terminal device, enabling the terminal device to define the calling rules of the privacy APIs according to the JS script files. This allows for customized configuration of the privacy API calling rules, offering high flexibility and meeting the needs of privacy method calls in various business scenarios. Furthermore, by promptly distributing JS script files to define the calling rules of the privacy APIs, the calling methods of the privacy APIs on the terminal device become effective immediately. Subsequent calls to the privacy APIs will be executed according to the defined calling rules, effectively preventing abnormal privacy API call behavior. This achieves real-time dynamic protection of privacy method calls on the terminal device, enhancing privacy protection and ensuring the security of users' personal information.

[0090] In some embodiments of this application, the acquisition module includes: an acquisition unit, configured to acquire at least one call detail information configured by the user for each privacy API in the visual interface, thereby obtaining multiple call detail information corresponding to M privacy APIs; wherein, the call detail information includes the target terminal range and target application range selected by the user, as well as the call rules configured for the privacy API under the target terminal range and target application range, and at least one call detail information includes different call rules for the same privacy API under different target terminal ranges and / or different target application ranges.

[0091] In some embodiments of this application, the delivery module includes: an association unit, used to associate the target terminal range in each call detail information with the corresponding JS script; and a delivery unit, used to deliver the JS script associated with the target terminal range to a terminal device that matches the target terminal range, so that the application corresponding to the target application range in the terminal device can call the privacy API by executing the JS script according to the calling rules in the call detail information.

[0092] In some embodiments of this application, the sending unit is specifically used to: send a notification message to a terminal device that matches the target terminal range, wherein the notification message is used to indicate the updating of the calling rules of the privacy API within the target application range; and, upon receiving an update confirmation request from the terminal device, send a JS script file to the terminal device.

[0093] In some embodiments of this application, the acquisition unit is specifically used to: acquire device information and application information input by the user; determine the target terminal range selected by the user based on the device information; and determine the target application range selected by the user based on the application information. The device information includes at least one of Runtime environment information, operating system version information, device model information, and device location information, and the application information includes at least one of application industry information, application field information, application type, and application identifier.

[0094] In some embodiments of this application, the calling rules include a calling time period, a calling frequency threshold, and a calling count threshold within the calling time period.

[0095] In some embodiments of this application, the distribution module is specifically used to: distribute multiple JS script files to a third-party software development kit (SDK) of the terminal device, so that the third-party SDK, in conjunction with the Runtime mechanism and the JSCore mechanism, can modify the calling method of the privacy API by loading the JS script files.

[0096] In some embodiments of this application, the apparatus further includes: an encryption module, used to encrypt and compress multiple JS script files before sending them to a terminal device; and a sending module specifically used to send the encrypted and compressed multiple JS script files to the terminal device via a content delivery network.

[0097] A third aspect of this application also provides an electronic device. Figure 6 A schematic diagram of the structure of an embodiment of the electronic device provided in the third aspect of this application. (See attached diagram.) Figure 6 As shown, the electronic device 600 includes a memory 601, a processor 602, and a computer program stored in the memory 601 and executable on the processor 602.

[0098] In one example, the processor 602 described above may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits that may be configured to implement the embodiments of this application.

[0099] Memory 601 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the privacy protection method in the embodiments according to the first aspect of this application.

[0100] The processor 602 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 601, in order to implement the privacy protection method in the embodiments of the first aspect described above.

[0101] In some examples, electronic device 600 may also include communication interface 603 and bus 604. For example, Figure 6 As shown, the memory 601, processor 602, and communication interface 603 are connected through bus 604 and complete communication with each other.

[0102] The communication interface 603 is mainly used to enable communication between various modules, devices, units, and / or equipment in the embodiments of this application. Input devices and / or output devices can also be connected through the communication interface 603.

[0103] Bus 604 includes hardware, software, or both, that couples components of electronic device 600 together. For example, and not limitingly, bus 604 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 604 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0104] A fourth aspect of this application provides a computer-readable storage medium storing a program or instructions. When executed by a processor, the program or instructions can implement the privacy protection method described in the first aspect and achieve the same technical effect. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.

[0105] The fifth aspect of this application provides a computer program product stored in a non-volatile storage medium. When executed by at least one processor, the computer program product implements the steps of the privacy protection method as shown in the first aspect. The specific content of the privacy protection method can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0106] The sixth aspect of this application provides a chip including a processor and a communication interface, the communication interface and the processor being coupled together. The processor is used to run programs or instructions to implement various processes of the privacy protection method embodiments shown in the first aspect, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0107] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0108] It should be clarified that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For the device embodiments, user terminal embodiments, equipment embodiments, system embodiments, and computer-readable storage medium embodiments, the relevant parts can be referred to the description section of the method embodiments. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application. Furthermore, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

[0109] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0110] Those skilled in the art will understand that the above embodiments are exemplary and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, specification, and claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to identify names and not to indicate any particular order. No reference numerals in the claims should be construed as limiting the scope of protection. The functionality of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A privacy protection method, characterized in that, The method includes: The system obtains configuration content input by the user in a visual interface, wherein the configuration content includes at least one call detail information corresponding to M privacy application programming interface (API) entries, where M is a positive integer; the call detail information includes the target terminal range and target application range selected by the user, as well as the call rules configured for the privacy application programming interface API under the target terminal range and the target application range, and the at least one call detail information includes different call rules for the same privacy application programming interface API under different target terminal ranges and / or different target application ranges; The function service translates the call details of M privacy application programming interface APIs into multiple JS script files; The plurality of JS script files are distributed to the terminal device so that the terminal device defines the calling rules of the privacy application programming interface API according to the JS script files and calls the privacy application programming interface API according to the calling rules; The step of sending the multiple JS script files to the terminal device includes: for each call detail information, associating the target terminal range in the call detail information with the JS script corresponding to the call detail information; sending the JS script associated with the target terminal range to the terminal device that matches the target terminal range, so that the application corresponding to the target application range in the terminal device can call the privacy application programming interface API by executing the JS script according to the call rules in the call detail information.

2. The method according to claim 1, characterized in that, The process of obtaining the configuration content input by the user in the visual interface includes: Obtain at least one call detail information configured by the user for each privacy application programming interface (API) in the visual interface, and obtain multiple call detail information corresponding to the M privacy application programming interface (APIs).

3. The method according to claim 1, characterized in that, The step of sending a JS script associated with the target terminal range to terminal devices that match the target terminal range includes: Send a notification message to terminal devices that match the target terminal range, wherein the notification message is used to instruct the updating of the calling rules of the privacy application programming interface API within the target application range; Upon receiving an update confirmation request from the terminal device, the JS script file is sent to the terminal device.

4. The method according to claim 2, characterized in that, The acquisition of at least one call detail information from the user's configuration of each privacy application programming interface (API) in the visual interface includes: Obtain device and application information input by the user; The target terminal range selected by the user is determined based on the device information; The target application range selected by the user is determined based on the application information; The device information includes at least one of the following: runtime environment information, operating system version information, device model information, and device location information; the application information includes at least one of the following: application industry information, application field information, application type, and application identifier.

5. The method according to claim 1, characterized in that, The calling rules include a calling time period, a calling frequency threshold, and a calling count threshold within the calling time period.

6. The method according to claim 1, characterized in that, The step of sending the plurality of JS script files to the terminal device includes: The third-party software development kit (SDK) of the terminal device distributes the multiple JS script files, so that the third-party SDK, in conjunction with the Runtime mechanism and the JSCore mechanism, can modify the calling method of the privacy application programming interface (API) by loading the JS script files.

7. The method according to claim 1, characterized in that, Before sending the plurality of JS script files to the terminal device, the method further includes: The multiple JS script files are encrypted and compressed. The step of sending the plurality of JS script files to the terminal device includes: The encrypted and compressed JS script files are distributed to the terminal device via a content delivery network.

8. A privacy protection device, characterized in that, The device includes: The acquisition module is used to acquire configuration content input by the user in the visual interface, wherein the configuration content includes call details information corresponding to M privacy application programming interface (API) entries, where M is a positive integer; the call details information includes the target terminal range and target application range selected by the user, as well as the call rules configured for the privacy application programming interface (API) entries under the target terminal range and the target application range, and at least one of the call details information entries contains different call rules for the same privacy application programming interface (API) entries under different target terminal ranges and / or different target application ranges; The translation module is used to translate the call details of M privacy application programming interface APIs into multiple JS script files via function services; The distribution module is used to distribute the plurality of JS script files to the terminal device, so that the terminal device defines the calling rules of the privacy application programming interface API according to the JS script files, and calls the privacy application programming interface API according to the calling rules; The delivery module includes: an association unit, used to associate the target terminal range in each call detail information with the corresponding JS script; and a delivery unit, used to deliver the JS script associated with the target terminal range to the terminal device that matches the target terminal range, so that the application corresponding to the target application range in the terminal device can execute the JS script and call the privacy application programming interface API according to the calling rules in the call detail information.

9. An electronic device, characterized in that, The electronic device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the privacy protection method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program or instructions that, when executed by a processor, implement the privacy protection method as described in any one of claims 1 to 7.

11. A computer program product, characterized in that, The computer program product is stored in a non-volatile storage medium, and when executed by at least one processor, the computer program product implements the privacy protection method as described in any one of claims 1 to 7.

Images