CN114201776A - Method and device for hiding user identity aiming at target applet - Google Patents

Abstract

The embodiment of the specification provides a method and a device for hiding user identity for a target applet. The target small program is configured with an identity hiding type, and a host application where the target small program is located corresponds to a first service end, wherein the method comprises the following steps: the host application responds to the privacy authorization agreement operation executed by the user aiming at the target applet and sends a first acquisition request aiming at an authorization code to the first server; the first server side generates and returns an authorization code according to the first acquisition request; the host application sends the authorization code to a second server corresponding to the target applet through the target applet; the first service end receives a second acquisition request aiming at the private data of the user from a second service end, wherein the second acquisition request comprises an authorization code; according to the second acquisition request, private data and a virtual user identifier of the user are respectively acquired, and the virtual user identifier is determined according to a virtual user identifier determination mode indicated by the identity hiding type; and returning the privacy data and the virtual user identification of the user to the second server.

Description

Method and device for hiding user identity aiming at target applet

The application is a divisional application of an invention patent application with the application number of 202110863291.7, entitled "method and device for hiding user identity aiming at target applet", which is filed on 29/07/2021.

Technical Field

The embodiment of the specification relates to the technical field of computers, in particular to a method and a device for user identity hiding setting aiming at a target applet and a method and a device for user identity hiding aiming at the target applet.

Background

An applet is an application that can be used without download installation, and that can run in a client application, which can be referred to as the applet's host application. In practice, a host application may carry multiple applets that may provide various business services to a user.

Currently, business services and user privacy have been conflicting. From the perspective of an enterprise, by collecting user information and depicting a user portrait, more customized services can be provided for the user. From the user's perspective, sometimes such customized services will give the user the feeling of monitoring and make no sense of privacy in the network.

Therefore, a reasonable and reliable scheme is urgently needed, which can help users to protect personal privacy, prevent tracking and the like while enjoying normal business services of applets.

Disclosure of Invention

The embodiment of the specification provides a method and a device for user identity hiding setting aiming at a target applet, and a method and a device for user identity hiding aiming at the target applet, which can help a user to protect personal privacy and prevent tracking and the like when the user enjoys normal business service of the applet.

In a first aspect, an embodiment of the present specification provides a method for performing user identity hiding setting for a target applet, which is applied to a host application in which the target applet is located, and includes: acquiring an identity hiding type configured by a user for the target applet, wherein the identity hiding type is used for indicating a virtual user identifier determining mode, so that the target applet acquires a virtual user identifier determined according to the virtual user identifier determining mode when applying privacy authorization; sending an identity hiding setting request to a first server corresponding to the host application, wherein the identity hiding setting request comprises a program identifier of the target applet, a real user identifier of the user and the identity hiding category; and correspondingly storing the program identifier, the real user identifier and the identity hiding category by the first service end.

In some embodiments, the method further comprises: responding to the triggering operation of the user on an identity hiding setting inlet displayed on a first page of the target applet, and displaying an identity hiding setting window to the user; and the acquiring the identity hiding category configured by the user for the target applet comprises: and acquiring the identity hiding type configured by the user through the identity hiding setting window.

In some embodiments, the virtual user identity determination comprises determining different virtual user identities for the user for different applets.

In some embodiments, the identity hiding category is a first hiding category, and the virtual user identifier determining means further includes determining, for a same applet, a same virtual user identifier of the user; or the identity hiding type is a second hiding type, and the virtual user identifier determining mode further comprises the step of determining different virtual user identifiers of the user aiming at the same applet.

In some embodiments, the identity hiding category is one of a plurality of hiding categories, and the identity hiding setting window displays a plurality of options corresponding to the plurality of hiding categories; and the acquiring the identity hiding type configured by the user through the identity hiding setting window comprises: and in response to a category selection operation executed by the user through any one of the plurality of options, acquiring a hidden category pointed by the category selection operation as the identity hidden category.

In a second aspect, an embodiment of the present disclosure provides a method for hiding a user identity for a target applet, which is applied to a first service end corresponding to a host application where the target applet is located, and includes: receiving an identity hiding setting request from the host application, wherein the identity hiding setting request comprises a program identifier of the target applet, a real user identifier of a user and an identity hiding category configured by the user for the target applet, and the identity hiding category is used for indicating a virtual user identifier determining mode, so that the target applet obtains the virtual user identifier determined according to the virtual user identifier determining mode when applying privacy authorization; and correspondingly storing the program identifier, the real user identifier and the identity hiding type.

In a third aspect, an embodiment of the present disclosure provides a method for hiding a user identity for a target applet, where the target applet is configured with an identity hiding type, and the identity hiding type is used to indicate a virtual user identifier determining manner, where the method is applied to a first service end corresponding to a host application where the target applet is located, and includes: receiving a first acquisition request for an authorization code from the host application, the first acquisition request being sent by the host application in response to a user performing an operation of granting privacy authorization for the target applet, the first acquisition request including at least a program identification of the target applet and a real user identification of the user; generating and returning an authorization code according to the first acquisition request; receiving a second obtaining request aiming at the privacy data of the user from a second server corresponding to the target applet, wherein the second obtaining request comprises the authorization code; according to the second acquisition request, acquiring privacy data of the user and acquiring a virtual user identifier of the user, wherein the virtual user identifier is determined according to the virtual user identifier determination mode; and returning the acquired private data of the user and the virtual user identifier to the second server.

In some embodiments, the first get request further includes a virtual user identification of the user determined by the host application; and acquiring the virtual user identifier of the user, including: and acquiring the virtual user identification of the user from the first acquisition request.

In some embodiments, obtaining the virtual user identification of the user comprises: and acquiring the virtual user identifier of the user according to the stored virtual user identifier determining mode indicated by the identity hiding type.

In some embodiments, the identity hiding category is a first hiding category; and the obtaining the virtual user identifier of the user according to the stored virtual user identifier determining mode indicated by the identity hiding type comprises the following steps: determining whether the program identification has been associated with a virtual user identification of the user under the first hidden category; if the program identifier is determined to be the virtual user identifier of the user associated with the program identifier under the first hidden category, acquiring the virtual user identifier of the user associated with the program identifier under the first hidden category; and if the determination result is negative, randomly generating the virtual user identifier of the user aiming at the target small program.

In some embodiments, after said randomly generating a virtual user identity for said user for said target applet, further comprises: setting the virtual user identifier as the virtual user identifier of the user associated with the program identifier under the first hidden category.

In some embodiments, the identity hiding category is a second hiding category; and the obtaining the virtual user identifier of the user according to the stored virtual user identifier determining mode indicated by the identity hiding type comprises the following steps: and randomly generating a virtual user identifier of the user aiming at the request of the target applet.

In some embodiments, the first acquisition request further includes a user authorization scope; and obtaining the private data of the user, including: and obtaining the privacy data of the user within the user authorization range.

In a fourth aspect, an embodiment of the present specification provides a method for hiding a user identity for a target applet, where the target applet is configured with an identity hiding class, the identity hiding class is used to indicate a virtual user identifier determining method, and a host application where the target applet is located corresponds to a first service end, where the method includes: the host application responds to an agreement privacy authorization operation executed by a user for the target applet, and sends a first acquisition request for an authorization code to the first server, wherein the first acquisition request at least comprises a program identifier of the target applet and a real user identifier of the user; the first server side generates and returns an authorization code according to the first acquisition request; the host application sends the authorization code to a second server corresponding to the target applet through the target applet; the first service end receives a second obtaining request aiming at the privacy data of the user from the second service end, wherein the second obtaining request comprises the authorization code; according to the second acquisition request, acquiring privacy data of the user and acquiring a virtual user identifier of the user, wherein the virtual user identifier is determined according to the virtual user identifier determination mode; and returning the acquired private data of the user and the virtual user identifier to the second server.

In some embodiments, before the sending the first acquisition request for the authorization code to the first server, the method further includes: the host application acquires the virtual user identifier of the user according to the stored virtual user identifier determining mode indicated by the identity hiding type; the first acquisition request also comprises a virtual user identifier of the user; the first server side obtains the virtual user identification of the user through the following obtaining modes: and acquiring the virtual user identification of the user from the first acquisition request.

In some embodiments, the host application includes an authorization interface, the method further comprising: the host application receives a privacy authorization request of the target applet through the authorization interface, and presents prompt information for inquiring whether privacy authorization is agreed to the user, wherein the prompt information comprises an agreement option for triggering agreement on the privacy authorization; and the consent privacy authorization operation comprises a trigger operation on the consent option.

In a fifth aspect, an embodiment of the present specification provides an apparatus for performing user identity hiding setting for a target applet, which is applied to a host application where the target applet is located, and includes: the acquiring unit is configured to acquire an identity hiding type configured by a user for the target applet, wherein the identity hiding type is used for indicating a virtual user identifier determining mode, so that the target applet acquires a virtual user identifier determined according to the virtual user identifier determining mode when applying privacy authorization; a sending unit, configured to send an identity hiding setting request to a first server corresponding to the host application, where the identity hiding setting request includes a program identifier of the target applet, a real user identifier of the user, and the identity hiding category; and correspondingly storing the program identifier, the real user identifier and the identity hiding category by the first service end.

In a sixth aspect, an embodiment of the present disclosure provides an apparatus for performing user identity hiding setting for a target applet, where the apparatus is applied to a first service end corresponding to a host application where the target applet is located, and the apparatus includes: a receiving unit, configured to receive an identity hiding setting request from the host application, where the identity hiding setting request includes a program identifier of the target applet, a real user identifier of a user, and an identity hiding category configured by the user for the target applet, and the identity hiding category is used for indicating a virtual user identifier determination manner, so that the target applet, when applying privacy authorization, obtains a virtual user identifier determined according to the virtual user identifier determination manner; a storage unit configured to correspondingly store the program identifier, the real user identifier, and the identity hiding category.

A seventh aspect of the present disclosure provides an apparatus for hiding a user identity for a target applet, where the target applet is configured with an identity hiding class, and the identity hiding class is used to indicate a virtual user identifier determining manner, and the apparatus is applied to a first service end corresponding to a host application where the target applet is located, and includes: a first receiving unit configured to receive, from the host application, a first acquisition request for an authorization code, the first acquisition request being sent by the host application in response to a consent privacy authorization operation performed by a user for the target applet, the first acquisition request including at least a program identification of the target applet and a real user identification of the user; a generating unit configured to generate and return an authorization code according to the first acquisition request; a second receiving unit, configured to receive, from a second server corresponding to the target applet, a second acquisition request for the private data of the user, where the second acquisition request includes the authorization code; an obtaining unit configured to obtain the privacy data of the user and obtain a virtual user identifier of the user according to the second obtaining request, wherein the virtual user identifier is determined according to the virtual user identifier determining manner; a sending unit configured to return the acquired privacy data of the user and the virtual user identifier to the second server.

In an eighth aspect, the present specification provides a computer-readable storage medium, on which a computer program is stored, wherein when the computer program is executed in a computer, the computer is caused to execute the method described in any implementation manner of the first aspect to the third aspect.

In a ninth aspect, the present specification provides a computing device, including a memory and a processor, where the memory stores executable code, and the processor executes the executable code to implement the method described in any one of the implementation manners of the first aspect to the third aspect.

In a tenth aspect, the present specification provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the method described in any implementation manner of the first to third aspects.

In the method and the apparatus provided in the foregoing embodiment of the present specification, the host application obtains the identity hiding type configured by the user for the target applet, and sends the identity hiding setting request to the first server corresponding to the host application, so that the first server stores identity hiding setting information (for example, a program identifier of the target applet, a real user identifier of the user, and the identity hiding type) for the target applet, and thus, the user can select identity hiding in a customized manner. And then, when the target applet applies for privacy authorization, the first server side acquires the virtual user identifier of the user determined according to the virtual user identifier determination mode indicated by the identity hiding type, and returns the virtual user identifier of the user and the privacy data applied by the target applet to the second server side corresponding to the target applet, so that the real identity of the user can be hidden, the user can be helped to protect personal privacy and prevent tracking and the like when enjoying normal service of the target applet.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments disclosed in the present specification, the drawings needed to be used in the description of the embodiments will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments disclosed in the present specification, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.

FIG. 1 is an exemplary system architecture diagram to which some embodiments of the present description may be applied;

FIG. 2 is a schematic diagram of one embodiment of a method for user identity hiding settings for a target applet;

FIG. 3 is a schematic diagram of a configuration process for the identity hiding class;

FIG. 4 is a schematic diagram of one embodiment of a method for user identity hiding for a target applet;

FIG. 5 is a schematic illustration of a prompt for asking whether privacy authorization is granted;

FIG. 6 is a schematic diagram of an apparatus for user identity hiding for a target applet;

FIG. 7 is a schematic diagram of an apparatus for user identity hiding settings for a target applet;

fig. 8 is a schematic structural diagram of an apparatus for user identity hiding for a target applet.

Detailed Description

The present specification will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. The described embodiments are only a subset of the embodiments described herein and not all embodiments described herein. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step are within the scope of the present application.

It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings. The embodiments and features of the embodiments in the present description may be combined with each other without conflict. In addition, the terms "first", "second", and the like in the present specification are used only for information distinction and do not play any limiting role.

As previously mentioned, business services and user privacy have been conflicting. From the perspective of an enterprise, by collecting user information and depicting a user portrait, more customized services can be provided for the user. From the user's perspective, sometimes such customized services will give the user the feeling of monitoring and make no sense of privacy in the network.

Based on this, some embodiments of the present description provide a method for user identity hiding setting for a target applet, and a method for user identity hiding for a target applet. By the method, the user can be helped to protect personal privacy, prevent tracking and the like when enjoying normal business service of the applet. In particular, FIG. 1 illustrates an exemplary system architecture diagram suitable for use with these embodiments.

As shown in fig. 1, the system architecture may include a host application, an arbitrary applet (e.g., applet a shown in fig. 1) carried by the host application, a first service end corresponding to the host application, and a second service end corresponding to the applet. The first server is a background server of the host application, and the background server may be implemented as a service platform, a physical server, or a cloud server, and is not limited specifically herein. The second server is a background server of the corresponding applet.

The host application may be any kind of client application, for example, a payment-type client application, a social-type client application, or a financial-type client application, and the like, and is not limited in particular. In addition, the host application may be installed in various terminal devices, which may include smart phones, tablet computers, notebook computers, desktop computers, and the like.

In practice, the host application may carry a plurality of applets, and for any one of the plurality of applets, for example, applet a, the host application may support the user to configure an identity hiding category for applet a. The identity hiding type can be used for indicating a virtual user identifier determining mode, so that the applet obtains the virtual user identifier determined according to the virtual user identifier determining mode when applying privacy authorization.

In particular, referring to fig. 1, a user may first configure an identity hiding category for applet a, as indicated at reference numeral 102. Thereafter, the host application may request, as indicated by reference numeral 104, the first server to set identity hiding for the applet a, so that the first server stores corresponding identity hiding setting information for the applet a, where the identity hiding setting information may be used to indicate that the applet a has activated an identity hiding function. The identity hiding setting information may include, for example, a program identifier of the applet a, an actual user identifier of the user, and the identity hiding category.

For any applet borne by the host application, when the applet applies for privacy authorization, the first server side can obtain the virtual user identifier of the user determined according to the virtual user identifier determining mode, and returns the virtual user identifier and the privacy data of the user applied by the applet to the second server side corresponding to the applet, so that the second server side provides service response for the user according to the privacy data of the user and the virtual user identifier.

Continuing with applet a as an example, after the identity hiding setting of applet a is completed, when the applet a applies for privacy authorization as indicated by reference numeral 106, the host application may request an authorization code from the first service end after the user agrees to the privacy authorization as indicated by reference numeral 108. The first server may then return an authorization code to the host application, as indicated by reference numeral 110. The host application may then return the authorization code to applet a as indicated by reference numeral 112. The applet a may then send the authorization code to the corresponding second server, as indicated by reference numeral 114. The second server may then request the user's private data from the first server using the authorization code, as shown at reference numeral 116. The first server may then return the user's private data and virtual user identification to the second server, as indicated by reference numeral 118. The virtual user identification is determined according to the virtual user identification determination mode. Thereafter, the second server may provide a service response for the user based on the received privacy data of the user and the virtual user identification, as indicated by reference numeral 120.

Therefore, the selected identity customized by the user for the small program A can be hidden, the small program A can acquire the virtual user identification of the user, the real user identification cannot be acquired, and the real identity of the user can be well hidden. Thus, it is possible to help the user to protect personal privacy, prevent tracking, and the like while enjoying the normal business service of the applet a.

The following describes specific implementation steps of the above method with reference to specific examples. It is noted that, for convenience of description, any one applet carried by the host application will be hereinafter referred to as a target applet.

Referring to fig. 2, a schematic diagram of one embodiment of a method for user identity hiding settings for a target applet is shown. The method comprises the following steps:

step 202, a host application acquires an identity hiding type configured by a user for a target applet;

step 204, the host application sends an identity hiding setting request to the first server;

and step 206, the first service end correspondingly stores the program identifier, the real user identifier and the identity hiding type.

The above steps are further explained below.

In step 202, the host application may obtain the identity hiding category configured by the user for the target applet in real time. The identity hiding type is used for indicating a virtual user identifier determining mode, so that the target applet obtains the virtual user identifier determined according to the virtual user identifier determining mode when applying privacy authorization.

The virtual user identifier determining method may include, for example, determining, for different applets, different virtual user identifiers of users. Based on this, for each applet configured with the identity hiding category, when the respective applet applies privacy authorization, a virtual user identifier different from the user may be determined for the respective applet. In this case, since the plurality of applets acquire virtual user identifiers different from one another for the user, the enterprise cannot associate user behavior information generated by the user in the plurality of applets based on the same user identifier, and cannot depict the user image of the user, thereby protecting the privacy of the user and preventing tracking.

In some embodiments, the host application may be preset with multiple hidden categories. The plurality of concealment categories may include, for example, a first concealment category and a second concealment category, and so on.

The determining method of the virtual user identifier indicated by the first hidden category specifically includes determining, for different applets, different virtual user identifiers of users, and determining, for the same applet, the same virtual user identifier of the user. Wherein the first hidden category can be considered as a hidden category of an APPID (program identification) dimension. It will be appreciated that where the identity hiding category configured for the target applet is the first hiding category, the same virtual user identity for the user may be determined for the target applet each time the target applet applies for privacy authorisation, and this virtual user identity is different from the virtual user identities already determined for the other applets.

The determining of the virtual user identifier indicated by the second hidden category specifically includes determining, for different applets, different virtual user identifiers for the users, and determining, for the same applet, different virtual user identifiers for the users. It will be appreciated that where the identity hiding category configured for the target applet is the second hiding category, a different virtual user identity for the target applet may be determined each time the target applet applies for privacy authorisation, and this virtual user identity is different from the virtual user identities already determined for the other applets.

In general, the host application includes an authorization interface, and each applet carried by the host application can apply for privacy authorization by calling the authorization interface. The second hidden class may be considered a hidden class of the interface dimension. It will be appreciated that where the hidden category of the interface dimension is configured for the target applet, a different virtual user identity is returned for the user for each invocation of the authorization interface by the target applet.

In practice, when a user wants to enjoy the recommended service of a target applet, a first hidden category may be configured for the target applet to allow the target applet to globally use the same virtual user identification of the user. When the user does not need to use the recommended service of the target applet, or when the target applet is an applet providing a temporary service, a second hidden category may be configured for the target applet so that the target applet acquires a different virtual user identifier for the user each time. Thus, the user can be helped to hide the real identity without influencing the business function of the target applet.

In other embodiments, the identity hiding category and the corresponding virtual user identifier determination mode may have other setting modes. For example, in one example, the respective applets are divided into several classes according to a certain rule in a coarser granularity manner, and different virtual user identifiers of users are determined for applets of different classes. In another example, on the basis of the first hidden category and the second hidden category, a third hidden category may be further set, where the virtual user identifier is replaced at regular time intervals, for example, one day and one week, for the same user of the same applet; and within that time interval the same virtual user identity is used for that user, allowing the applet to have a range of user context data. Regarding the identity hiding category and the corresponding virtual user identifier determining method, those skilled in the art may make more designs based on reading the present specification, which are not enumerated herein.

In some embodiments, before step 202, the method may further include: and responding to the triggering operation of the user on the identity hiding setting entry displayed on the first page of the target applet, and displaying an identity hiding setting window to the user. Wherein the first page may be any one of the pages of the target applet. Further, the first page may be a first page of the target applet. The identity hiding settings entry may be that the host application is presented on the first page. In addition, the identity hiding setting entry may be an entry in the form of a button or a hyperlink, and is not particularly limited herein. Based on this, step 202 may further include: and acquiring the identity hiding type configured by the user through the identity hiding setting window.

In some embodiments, the identity hiding category is one of the multiple hiding categories, and the identity hiding setting window may display multiple options corresponding to the multiple hiding categories. Wherein, the hidden categories and the options have one-to-one correspondence. The plurality of options may be options in the form of radio buttons or switch controls, and the like, and are not particularly limited herein. Based on this, in step 202, the host application may, in response to a category selection operation performed by the user through any one of the plurality of options, acquire a hidden category pointed to by the category selection operation as the identity hidden category.

Taking the first page as the top page, and the plurality of hidden categories include a first hidden category (i.e., hidden category in APPID dimension) and a second hidden category (i.e., hidden category in interface dimension), the configuration process of the identity hidden category may be as shown in fig. 3. Wherein the left part of fig. 3 shows the home page of the target applet, the upper right corner of which is displayed with the identity hiding setting button. When the user wants to perform the identity hiding setting for the target applet, the user can enter the identity hiding setting window shown in the right part of fig. 3 by clicking the identity hiding setting button. The identity hiding setting window displays switch controls corresponding to the hiding types of the APPID dimension and the interface dimension respectively, and the switch controls are in an off state by default. When a user wants to set the hidden type of the APPID dimension as the identity hidden type corresponding to the target applet, the switch control corresponding to the hidden type of the APPID dimension can be clicked to open the switch control. The host application can respond to the click operation of the user on the switch control, namely the category selection operation executed by the switch control, and acquire the hidden category of the APPID dimension as the identity hidden category configured by the user for the target applet.

In some embodiments, to facilitate a user to clearly understand the purpose of each hidden category, in the identity hiding setup window, description information for each hidden category may be presented. For example, fig. 3 shows that the description information of the hidden category for the APPID dimension "after being turned on, the same virtual user id of the user is used globally by the applet", and the description information of the hidden category for the interface dimension "after being turned on, the virtual user ids of the applet are different each time the applet calls the interface". It should be understood that the specific content of the description information may be set according to actual requirements, and is not specifically limited herein.

Next, in step 204, the host application may send an identity hiding setting request to the first server, which may include the program identifier of the target applet, the real user identifier of the user, and the identity hiding category configured by the user for the target applet. Then, in step 206, the first server may correspondingly store the program identifier, the real user identifier, and the identity hiding category. It should be noted that, when the target applet applies for privacy authorization subsequently, the first server may determine the virtual user identifier of the user for the target applet according to the stored virtual user identifier determination manner indicated by the identity hiding category.

In some embodiments, in order to improve the response performance of the first server, the operation of determining the virtual user identifier of the user for the target applet may be specifically executed by the host application according to the virtual user identifier determination mode. Based on this, the identity hiding setting request in step 204 may not include the identity hiding class, and in step 206, the first server may not store the identity hiding class. Further, the identity hiding category in step 206 may be replaced with an identity hiding flag, which may be used to indicate that the user has turned on the identity hiding function for the target applet.

In the method for performing user identity hiding setting for a target applet, which is provided in the embodiment corresponding to fig. 2, the host application obtains the identity hiding type configured by the user for the target applet, and sends an identity hiding setting request to the first server corresponding to the host application, so that the first server stores identity hiding setting information (for example, a program identifier of the target applet, a real user identifier of the user, and the identity hiding type) for the target applet, and can implement customized selection of identity hiding by the user.

Next, an identity hiding method when the target applet applies for privacy authorization is described.

Referring to fig. 4, a schematic diagram of one embodiment of a method for user identity hiding for a target applet is shown. The method comprises the following steps:

step 406, in response to the privacy authorization agreement operation executed by the user for the target applet, the host application sends a first acquisition request for an authorization code to the first server, where the first acquisition request at least includes a program identifier of the target applet and a real user identifier of the user;

step 408, the first server generates an authorization code according to the first acquisition request;

step 410, the first server returns an authorization code to the host application;

step 412, the host application sends the authorization code to a second server corresponding to the target applet via the target applet;

step 414, the first service end receives a second obtaining request for the private data of the user from the second service end, wherein the second obtaining request includes an authorization code;

step 416, the first server obtains the private data of the user and obtains the virtual user identifier of the user according to the second obtaining request;

in step 418, the first server returns the obtained private data of the user and the virtual user identifier to the second server.

Next, each step shown in fig. 4 will be further explained.

In step 406, the host application sends a first obtaining request for an authorization code to the first server in response to the user performing the operation of agreeing to the privacy authorization on the target applet, where the first obtaining request at least includes the program identifier of the target applet and the real user identifier of the user.

In practice, when the virtual user identity of the user is determined by the first server, the first acquisition request may include a program identity of the target applet and a real user identity of the user. When the virtual user identity of the user is determined by the host application, the first acquisition request includes the virtual user identity of the user determined by the host application for the target applet in addition to the program identity of the target applet and the real user identity of the user.

In some embodiments, before step 406, the method may further include: step 402, the host application receives a privacy authorization request of a target applet through an authorization interface of the host application; in step 404, the host application presents prompt information for asking whether to approve the privacy authorization to the user, wherein the prompt information comprises an approval option for triggering the approval of the privacy authorization. Based on this, the consent privacy authorization operation may include a trigger operation for the consent option.

In practice, the prompt message may specifically include prompt content and an agreement option. The consent option may be implemented as a button for indicating consent, such as buttons named "Yes," "Y," "Yes," or "consent," etc. The hint content may include, for example, the name of the target applet, the data range of the private data that the target applet applies for. From the user's perspective, this data range may be referred to as a user authorization range. The user authorization scope may include, for example, a geographic location, a photo gallery, a short message record, a call record, and/or a contact list, and is not limited in this respect.

Optionally, the prompt message may further include a rejection option for the user to trigger rejection of privacy authorization. The reject option may be implemented as a button for indicating rejection, such as buttons named "No", "N", "No", or "reject", etc.

Referring to fig. 5, a schematic diagram of a prompt for asking whether privacy authorization is granted is shown. The prompt message comprises prompt content, namely the small program applies for authorization of the contact list, an agreement button for the user to trigger agreement of privacy authorization, and a rejection button for the user to trigger rejection of privacy authorization. Wherein ". times. applet" is the name of the target applet. The "contact list" is a data range of private data that the target applet applies for.

After the step 406 is executed, the first server may execute step 408 to generate an authorization code according to the first obtaining request. The first server may then perform step 410 to return the authorization code to the host application.

In practice, the first server may generate the authorization code by using a preset authorization code generation rule. The generation process of the authorization code is not particularly limited. It should be noted that, after generating the authorization code, the first server may perform corresponding caching on the first acquisition request and the authorization code.

Next, in step 412, the host application may send the authorization code to the target applet, so that the target applet sends the authorization code to the corresponding second server.

Next, in step 414, the first server may receive a second obtaining request for the private data of the user from the second server, including the authorization code.

Next, in step 416, the first server may obtain the private data of the user and obtain the virtual user identifier of the user according to the second obtaining request.

In some embodiments, the second obtaining request may include a user authorization range, and the first server may obtain the private data of the user within the user authorization range.

In some embodiments, the first acquisition request in the foregoing may include a user authorization scope. The first server can locate the first acquisition request according to the authorization code in the second acquisition request, and further acquire the private data of the user within the user authorization range according to the user authorization range in the first acquisition request.

In some embodiments, the virtual user identity is determined by the first service. In step 416, the first server may locate the first acquisition request according to the authorization code in the second acquisition request, further obtain, according to the program identifier in the first acquisition request, the locally stored identity hiding category corresponding to the program identifier and the real user identifier of the user, and then obtain the virtual user identifier of the user according to the virtual user identifier determination manner indicated by the identity hiding category.

As an example, when the identity hiding category is a first hiding category, the first server may determine whether the program identifier is already associated with the virtual user identifier of the user under the first hiding category. If the determination result is yes, the first server may obtain the virtual user identifier of the user whose program identifier is already associated in the first hidden category. If the determination result is negative, the first server may randomly generate a virtual user identifier of the user for the target applet. It can be understood that the randomly generated virtual user id is different from the virtual user id that has been generated previously.

Note that, in a case where the determination result is negative, after randomly generating a virtual user identifier of the user for the target applet, the first server may set the virtual user identifier as a virtual user identifier of a user associated with the program identifier in the first hidden category. Specifically, the first server may store the randomly generated virtual user identifier in correspondence with the program identifier, the real user identifier of the user, and the first hidden category.

As another example, when the identity hiding category is the second hiding category, the first server may randomly generate the virtual user identifier of the user for the current request of the target applet. The realization mode can well hide the real identity of the user, and further prevent tracking, malicious recommendation and the like.

In some embodiments, the virtual user identification is determined by the host application. Prior to step 406, the host application may obtain the virtual user identification of the user based on the virtual user identification determination indicated by the identity hiding class that has been stored for the target applet. Here, for the virtual user identifier obtaining method adopted by the host application, reference may be made to the related content described in the foregoing for the first service end, and details are not described here again.

Based on this, the first get request in step 406 may also include the virtual user identification of the user as determined by the host application. In step 416, the first server may locate the first obtaining request according to the authorization code in the second obtaining request, and further obtain the virtual user identifier of the user from the first obtaining request. It should be noted that, in this implementation, the first server does not need to generate the virtual user identifier, and the response performance of the first server can be effectively improved.

Next, in step 418, the first server may return the obtained privacy data of the user and the virtual user identifier to the second server. And then, the second server side can provide service response for the user according to the received privacy data and the virtual user identification of the user.

In the method for hiding the user identity for the target applet provided in the embodiment corresponding to fig. 4, when the target applet applies for privacy authorization, the first server obtains the virtual user identifier of the user determined according to the virtual user identifier determining manner indicated by the identity hiding type, and returns the virtual user identifier of the user and the privacy data applied by the target applet to the second server corresponding to the target applet, so that the hiding of the real identity of the user can be realized, and the user can be helped to protect personal privacy and prevent tracking and the like when enjoying normal service of the target applet. In addition, the target applet can apply privacy authorization by calling the authorization interface, and the problems of generation and maintenance of the virtual user identifier can be effectively solved on the basis of the uniform authorization interface.

With further reference to fig. 6, the present specification provides one embodiment of an apparatus for user identity hiding settings for a target applet, which may be applied to a hosting application (such as the hosting application shown in fig. 1) where the target applet is located.

As shown in fig. 6, the apparatus 600 for user identity hiding setting for a target applet of this embodiment includes: an acquisition unit 601 and a transmission unit 602. The obtaining unit 601 is configured to obtain an identity hiding category configured by a user for the target applet, where the identity hiding category is used to indicate a virtual user identifier determining manner, so that the target applet obtains a virtual user identifier determined according to the virtual user identifier determining manner when applying privacy authorization; the sending unit 602 is configured to send an identity hiding setting request to a first server corresponding to the host application, where the identity hiding setting request includes a program identifier of the target applet, a real user identifier of the user, and an identity hiding category; and correspondingly storing the program identifier, the real user identifier and the identity hiding category by the first service end.

In some embodiments, the apparatus 600 may further include: a presentation unit (not shown in the figure) configured to present an identity hiding setting window to a user in response to a user's trigger operation on an identity hiding setting entry displayed on a first page of a target applet; the obtaining unit 601 may be further configured to: and acquiring the identity hiding type configured by the user through the identity hiding setting window.

In some embodiments, the determining of the virtual user identifier includes determining, for different applets, different virtual user identifiers of users. Further, the identity hiding type is a first hiding type, and the virtual user identifier determining method further includes determining the same virtual user identifier of the user for the same applet; or the identity hiding type is a second hiding type, and the virtual user identifier determining mode further comprises the step of determining different virtual user identifiers of users aiming at the same applet.

In some embodiments, the identity hiding category is one of a plurality of hiding categories, and a plurality of options corresponding to the plurality of hiding categories are displayed in the identity hiding setting window; and the obtaining unit 601 may be further configured to: and in response to a category selection operation executed by a user through any one of the plurality of options, acquiring the hidden category pointed by the category selection operation as the identity hidden category.

With further reference to fig. 7, the present specification provides an embodiment of an apparatus for user identity hiding setting for a target applet, where the apparatus may be applied to a first service (e.g., the first service shown in fig. 1) corresponding to a host application where the target applet is located.

As shown in fig. 7, the apparatus 700 for user identity hiding setting for a target applet of this embodiment includes: a receiving unit 701 and a storage unit 702. The receiving unit 701 is configured to receive an identity hiding setting request from a host application, where the identity hiding setting request includes a program identifier of a target applet, a real user identifier of a user, and an identity hiding category configured by the user for the target applet, and the identity hiding category is used for indicating a virtual user identifier determination manner, so that the target applet obtains a virtual user identifier determined according to the virtual user identifier determination manner when applying privacy authorization; the storage unit 702 is configured to store the program identifier, the real user identifier and the identity hiding class correspondingly.

With further reference to fig. 8, the present specification provides an embodiment of an apparatus for hiding a user identity for a target applet, where the target applet is configured with an identity hiding class, and the identity hiding class is used to indicate a virtual user identifier determination manner, and the apparatus may be applied to a first server (e.g., the first server shown in fig. 1) corresponding to a host application where the target applet is located.

As shown in fig. 8, the apparatus 800 for hiding the user identity with respect to the target applet in this embodiment includes: a first receiving unit 801, a generating unit 802, a second receiving unit 803, an acquiring unit 804, and a transmitting unit 805. Wherein the first receiving unit 801 is configured to receive, from the host application, a first acquisition request for the authorization code, the first acquisition request being sent by the host application in response to an operation of agreeing to the privacy authorization performed by the user for the target applet, the first acquisition request including at least a program identifier of the target applet and a real user identifier of the user; the generating unit 802 is configured to generate and return an authorization code according to the first acquisition request; the second receiving unit 803 is configured to receive a second obtaining request for the private data of the user from a second server corresponding to the target applet, where the second obtaining request includes the authorization code; the obtaining unit 804 is configured to obtain the privacy data of the user and obtain the virtual user identifier of the user according to the second obtaining request, where the virtual user identifier is determined according to the virtual user identifier determining manner; the sending unit 805 is configured to return the obtained privacy data of the user and the virtual user identifier to the second server.

In some embodiments, the first get request further includes, a virtual user identification of the user determined by the host application; and the obtaining unit 804 may comprise a first obtaining sub-unit (not shown in the figure) configured to obtain the virtual user identity of the user from the first obtaining request.

In some embodiments, the obtaining unit 804 may include a second obtaining subunit (not shown in the figure), configured to obtain the virtual user identifier of the user according to the stored virtual user identifier determination manner indicated by the identity hiding category.

In some embodiments, the identity hiding category is a first hiding category; and the second acquiring subunit may include: a first obtaining module (not shown in the figure) configured to determine whether the program identifier is associated with the virtual user identifier of the user in the first hidden category; if the program identifier is in the first hidden category, acquiring a virtual user identifier of a user associated with the program identifier in the first hidden category; and if the determination result is negative, randomly generating the virtual user identification of the user aiming at the target small program.

In some embodiments, the first acquisition module may be further configured to: after a virtual user identifier of a user is randomly generated for a target applet, the virtual user identifier is set as the virtual user identifier of the user associated with the program identifier in a first hidden category.

In some embodiments, the identity hiding category is a second hiding category; and the second acquiring subunit may include: and a second obtaining module (not shown in the figure) configured to randomly generate a virtual user identifier of the user for the current request of the target applet.

In some embodiments, the first acquisition request further includes a user authorization scope; and the obtaining unit 804 may include a third obtaining subunit (not shown in the figure) configured to obtain the private data of the user within the user authorization range.

In the embodiment of the apparatus corresponding to fig. 6, fig. 7, and fig. 8, the detailed processing of each unit and the technical effect thereof can refer to the related description of the method embodiment in the foregoing, and are not repeated herein.

The present specification also provides a computer readable storage medium, on which a computer program is stored, wherein when the computer program is executed in a computer, the computer program causes the computer to execute the methods respectively described in the above method embodiments.

The present specification further provides a computing device, including a memory and a processor, where the memory stores executable codes, and the processor executes the executable codes to implement the methods respectively described in the above method embodiments.

The embodiments of the present specification also provide a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the methods respectively described in the above method embodiments.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments disclosed herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.

In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The above-mentioned embodiments, objects, technical solutions and advantages of the embodiments disclosed in the present specification are further described in detail, it should be understood that the above-mentioned embodiments are only specific embodiments of the embodiments disclosed in the present specification, and are not intended to limit the scope of the embodiments disclosed in the present specification, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the embodiments disclosed in the present specification should be included in the scope of the embodiments disclosed in the present specification.

Claims (14)

1. A method for hiding user identity for a target applet, wherein the target applet is configured with an identity hiding type, the identity hiding type is used for indicating a virtual user identifier determining mode, the method is applied to a first service end corresponding to a host application where the target applet is located, and the method comprises the following steps:

when the target applet applies for privacy authorization, obtaining privacy data of a user applied by the target applet and obtaining a virtual user identifier of the user, wherein the virtual user identifier is determined according to a virtual user identifier determination mode;

and returning the acquired private data and the virtual user identifier of the user to a second server corresponding to the target applet.

2. The method of claim 1, wherein the obtaining the virtual user identity of the user comprises:

and acquiring the virtual user identifier of the user according to the stored virtual user identifier determining mode indicated by the identity hiding type.

3. The method of claim 2, wherein the identity hiding category is a first hiding category; and

the acquiring the virtual user identifier of the user according to the stored virtual user identifier determining mode indicated by the identity hiding category includes:

determining whether a program identification of the target applet has been associated with a virtual user identification of the user in the first hidden category;

if the program identifier is determined to be the virtual user identifier of the user associated with the program identifier under the first hidden category, acquiring the virtual user identifier of the user associated with the program identifier under the first hidden category;

and if the determination result is negative, randomly generating the virtual user identifier of the user aiming at the target small program.

4. The method of claim 3, wherein after the randomly generating the virtual user identity for the user for the target applet, further comprising:

setting the virtual user identifier as the virtual user identifier of the user associated with the program identifier under the first hidden category.

5. The method of claim 2, wherein the identity hiding category is a second hiding category; and

the acquiring the virtual user identifier of the user according to the stored virtual user identifier determining mode indicated by the identity hiding category includes:

and randomly generating a virtual user identifier of the user aiming at the request of the target applet.

6. A method for user identity hiding setting aiming at a target applet, wherein the target applet is positioned in a host application, and the host application corresponds to a first service end, and the method comprises the following steps:

the host application sends an identity hiding setting request to the first server, wherein the identity hiding setting request is generated in response to the fact that an identity hiding category configured by a user for the target applet is obtained, the identity hiding category is used for indicating a virtual user identifier determining mode, so that the target applet obtains a virtual user identifier determined according to the virtual user identifier determining mode when applying privacy authorization, and the identity hiding setting request at least comprises a program identifier of the target applet and a real user identifier of the user;

the first server stores corresponding identity hiding setting information aiming at the target applet, wherein the identity hiding setting information is used for indicating that the identity hiding function of the target applet is opened and at least comprises the program identification and the real user identification.

7. The method of claim 6, wherein the identity hiding setup information further comprises an identity hiding flag for indicating that the user has turned on an identity hiding function for the target applet.

8. The method of claim 6, wherein before the host application sends an identity hiding setup request to the first server, further comprising:

the host application responds to the triggering operation of the user on an identity hiding setting inlet displayed on a first page of the target applet and displays an identity hiding setting window to the user;

and the host application acquires the identity hiding type configured by the user through the identity hiding setting window.

9. The method according to one of claims 6 to 8, wherein the virtual user identity determination comprises determining different virtual user identities of the user for different applets.

10. The method of claim 9, wherein,

the identity hiding type is a first hiding type, and the virtual user identification determining mode further comprises the step of determining the same virtual user identification of the user aiming at the same applet; or,

the identity hiding type is a second hiding type, and the virtual user identifier determining mode further comprises the step of determining different virtual user identifiers of the users aiming at the same applet.

11. The method of claim 8, wherein the identity hiding category is one of a plurality of hiding categories, and the identity hiding setting window displays a plurality of options corresponding to the plurality of hiding categories; and

the obtaining the identity hiding category configured by the user through the identity hiding setting window includes:

and in response to a category selection operation executed by the user through any one of the plurality of options, acquiring a hidden category pointed by the category selection operation as the identity hidden category.

12. An apparatus for hiding a user identity for a target applet, the target applet being configured with an identity hiding type, the identity hiding type being used to indicate a virtual user identifier determining manner, the apparatus being applied to a first service end corresponding to a host application where the target applet is located, comprising:

an obtaining unit configured to obtain, when the target applet applies for privacy authorization, privacy data of a user for which the target applet applies, and obtain a virtual user identifier of the user, the virtual user identifier being determined according to the virtual user identifier determination manner;

and the sending unit is configured to return the acquired privacy data and the acquired virtual user identifier of the user to a second server corresponding to the target applet.

13. A computer-readable storage medium, on which a computer program is stored, wherein the computer program causes a computer to carry out the method of any one of claims 1-11, when the computer program is carried out in the computer.

14. A computing device comprising a memory and a processor, wherein the memory has stored therein executable code that when executed by the processor implements the method of any of claims 1-11.

Images