Method and device for hiding user identity for target applet

Abstract

The embodiment of the present specification provides a method and device for user identity hiding for a target miniprogram. The target miniprogram is configured with an identity hiding category, and a host application where the target miniprogram is located corresponds to a first server. The method comprises: the host application sends a first acquisition request for an authorization code to the first server in response to a user performing a consent privacy authorization operation on the target miniprogram; the first server generates and returns the authorization code according to the first acquisition request; the host application sends the authorization code to a second server corresponding to the target miniprogram via the target miniprogram; the first server receives a second acquisition request for privacy data of the user from the second server, which includes the authorization code; according to the second acquisition request, the privacy data of the user and a virtual user identifier are acquired respectively, and the virtual user identifier is determined according to a virtual user identifier determination manner indicated by the identity hiding category; and the privacy data of the user and the virtual user identifier are returned to the second server.

Description

[0001] This application is a divisional application of the invention patent application with application number 202110863291.7, filed on July 29, 2021, and named "Method and device for hiding user identity for target applet". TECHNICAL FIELD

[0002] The embodiments of the present specification relate to the technical field of computer technology, in particular, to a method and device for setting user identity hiding for a target applet, and a method and device for hiding user identity for a target applet. BACKGROUND

[0003] An applet is an application that can be used without downloading and installing, which can run in a client application, which can be referred to as a host application of the applet. In practice, the host application can carry multiple applets, which can provide multiple business services to users.

[0004] Currently, business services and user privacy have always been in conflict. From the perspective of enterprises, by collecting user information and profiling users, more customized services can be provided to users. From the perspective of users, sometimes such customized services make them feel monitored and have no secrets in the network.

[0005] Therefore, there is an urgent need for a reasonable and reliable solution to help users protect their personal privacy while enjoying normal business services of applets and prevent being tracked, etc. SUMMARY

[0006] The embodiments of the present specification provide a method and device for setting user identity hiding for a target applet, and a method and device for hiding user identity for a target applet, which can help users protect their personal privacy while enjoying normal business services of applets and prevent being tracked, etc.

[0007] In a first aspect, the embodiments of the present specification provide a method for setting user identity hiding for a target applet, applied to a host application where the target applet is located, comprising: obtaining an identity hiding category configured by a user for the target applet, the identity hiding category being used to indicate 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 for privacy authorization; sending an identity hiding setting request to a first server corresponding to the host application, which includes a program identifier of the target applet, a real user identifier of the user and the identity hiding category; so that the first server stores the program identifier, the real user identifier and the identity hiding category correspondingly.

[0008] In some embodiments, the method further includes: in response to a triggering operation of the user on an identity hiding setting entry displayed on a first page of the target applet, displaying an identity hiding setting window to the user; and the obtaining of the identity hiding category configured by the user for the target applet includes: obtaining the identity hiding category configured by the user through the identity hiding setting window.

[0009] In some embodiments, the virtual user identifier determination manner includes determining different virtual user identifiers of the user for different applets.

[0010] In some embodiments, the identity hiding category is a first hiding category, and the virtual user identifier determination manner further includes determining a same virtual user identifier of the user for a same applet; or the identity hiding category is a second hiding category, and the virtual user identifier determination manner further includes determining different virtual user identifiers of the user for a same applet.

[0011] 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 obtaining of the identity hiding category configured by the user through the identity hiding setting window includes: in response to a category selection operation performed by the user through any one of the plurality of options, obtaining a hiding category pointed by the category selection operation as the identity hiding category.

[0012] In a second aspect, the embodiments of the present specification provide a method for setting user identity hiding for a target applet, applied to a first server corresponding to a host application where the target applet is located, including: receiving an identity hiding setting request from the host application, wherein 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, the identity hiding category being used to indicate 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 for a privacy authorization; and storing the program identifier, the real user identifier, and the identity hiding category correspondingly.

[0013] In a third aspect, an embodiment of the present specification provides a method for hiding the identity of a user for a target mini-program, wherein the target mini-program is configured with an identity hiding category, and the identity hiding category is used to indicate a virtual user identifier determination manner. The method is applied to a first server corresponding to a host application in which the target mini-program is located, and includes: receiving a first acquisition request for an authorization code from the host application, wherein the first acquisition request is sent by the host application in response to a user performing a privacy authorization operation for the target mini-program, and the first acquisition request at least includes a program identifier of the target mini-program and a real user identifier of the user; generating and returning an authorization code according to the first acquisition request; receiving a second acquisition request for privacy data of the user from a second server corresponding to the target mini-program, wherein the second acquisition request includes the authorization code; obtaining the privacy data of the user and a virtual user identifier of the user according to the second acquisition request, wherein the virtual user identifier is determined according to the virtual user identifier determination manner; and returning the obtained privacy data of the user and the virtual user identifier to the second server.

[0014] In some embodiments, the first acquisition request further includes a virtual user identifier of the user determined by the host application; and obtaining the virtual user identifier of the user includes: obtaining the virtual user identifier of the user from the first acquisition request.

[0015] In some embodiments, obtaining the virtual user identifier of the user includes: obtaining the virtual user identifier of the user according to a virtual user identifier determination manner indicated by the stored identity hiding category.

[0016] In some embodiments, the identity hiding category is a first hiding category; and obtaining the virtual user identifier of the user according to the virtual user identifier determination manner indicated by the stored identity hiding category includes: determining whether the program identifier has associated the virtual user identifier of the user under the first hiding category; if the determination result is yes, obtaining the virtual user identifier of the user that the program identifier has associated under the first hiding category; and if the determination result is no, randomly generating the virtual user identifier of the user for the target mini-program.

[0017] In some embodiments, after the virtual user identifier of the user is randomly generated for the target mini-program, the method further includes: setting the virtual user identifier as the virtual user identifier of the user associated with the program identifier under the first hiding category.

[0018] 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 determination manner indicated by the identity hiding category comprises: randomly generating the virtual user identifier of the user for the current request of the target miniprogram.

[0019] In some embodiments, the first obtaining request further comprises a user authorization range; and the obtaining the privacy data of the user comprises: obtaining the privacy data of the user within the user authorization range.

[0020] In the fourth aspect, the embodiments of the present specification provide a method for user identity hiding for a target miniprogram, the target miniprogram is configured with an identity hiding category, the identity hiding category is used to indicate a virtual user identifier determination manner, a host application where the target miniprogram is located corresponds to a first server, and the method comprises: the host application sends a first obtaining request for an authorization code to the first server in response to a privacy authorization consent operation performed by a user for the target miniprogram, wherein the first obtaining request at least comprises a program identifier of the target miniprogram and a real user identifier of the user; the first server generates and returns an authorization code according to the first obtaining request; the host application sends the authorization code to a second server corresponding to the target miniprogram via the target miniprogram; the first server receives a second obtaining request for privacy data of the user from the second server, wherein the second obtaining request comprises the authorization code; obtains the privacy data of the user and 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 determination manner; and returns the obtained privacy data of the user and the virtual user identifier of the user to the second server.

[0021] In some embodiments, before the sending the first obtaining request for the authorization code to the first server, the method further comprises: the host application obtains the virtual user identifier of the user according to the stored virtual user identifier determination manner indicated by the identity hiding category; and the first obtaining request further comprises the virtual user identifier of the user; and the first server obtains the virtual user identifier of the user by the following obtaining manner: obtaining the virtual user identifier of the user from the first obtaining request.

[0022] In some embodiments, the host application comprises an authorization interface, and the method further comprises: the host application receives a privacy authorization request of the target miniprogram through the authorization interface, displays prompt information for inquiring whether to consent to the privacy authorization to the user, and the prompt information comprises a consent option for triggering the consent to the privacy authorization; and the privacy authorization consent operation comprises a triggering operation on the consent option.

[0023] In a fifth aspect, an apparatus for setting a user identity hiding for a target mini-program is provided, and is applied to a host application in which the target mini-program is located, and includes: an obtaining unit configured to obtain an identity hiding category configured by a user for the target mini-program, the identity hiding category being used to indicate a virtual user identifier determination manner, so that the target mini-program obtains a virtual user identifier determined according to the virtual user identifier determination manner when applying for a privacy authorization; and a sending unit configured to send, to a first server corresponding to the host application, an identity hiding setting request including a program identifier of the target mini-program, a real user identifier of the user, and the identity hiding category, so that the first server stores the program identifier, the real user identifier, and the identity hiding category correspondingly.

[0024] In a sixth aspect, an apparatus for setting a user identity hiding for a target mini-program is provided, and is applied to a first server corresponding to a host application in which the target mini-program is located, and includes: a receiving unit configured to receive, from the host application, an identity hiding setting request including a program identifier of the target mini-program, a real user identifier of a user, and an identity hiding category configured by the user for the target mini-program, the identity hiding category being used to indicate a virtual user identifier determination manner, so that the target mini-program obtains a virtual user identifier determined according to the virtual user identifier determination manner when applying for a privacy authorization; and a storage unit configured to store the program identifier, the real user identifier, and the identity hiding category correspondingly.

[0025] In a seventh aspect, an apparatus for hiding a user identity for a target mini-program is provided. The target mini-program is configured with an identity hiding category, which is used to indicate a virtual user identifier determination manner. The apparatus is applied to a first server corresponding to a host application in which the target mini-program is located, and includes a first receiving unit configured to receive a first acquisition request for an authorization code from the host application. The first acquisition request is sent by the host application in response to a user performing a privacy authorization operation for the target mini-program. The first acquisition request includes at least a program identifier of the target mini-program and a real user identifier of the user. A generating unit is configured to generate and return an authorization code according to the first acquisition request. A second receiving unit is configured to receive a second acquisition request for privacy data of the user from a second server corresponding to the target mini-program, which includes the authorization code. An obtaining unit is configured to obtain the privacy data of the user and a virtual user identifier of the user according to the second acquisition request. The virtual user identifier is determined according to the virtual user identifier determination manner. A sending unit is configured to return the obtained privacy data and virtual user identifier of the user to the second server.

[0026] In an eighth aspect, a computer readable storage medium is provided. The computer readable storage medium stores a computer program. When the computer program is executed in a computer, the computer performs the method described in any implementation manner of the first aspect to the third aspect.

[0027] In a ninth aspect, a computing device is provided. The computing device includes a memory and a processor. The memory stores executable code. When the processor executes the executable code, the method described in any implementation manner of the first aspect to the third aspect is implemented.

[0028] In a tenth aspect, a computer program is provided. When the computer program is executed in a computer, the computer performs the method described in any implementation manner of the first aspect to the third aspect.

[0029] The method and device provided by the above embodiments of the present specification can obtain the identity hiding category configured by the user for the target miniprogram through the host application, and send an identity hiding setting request to the first server corresponding to the host application, so that the first server stores the identity hiding setting information (for example, the program identifier of the target miniprogram, the real user identifier of the user, and the identity hiding category) for the target miniprogram, so as to realize the user's customized selection of identity hiding. Then, when the target miniprogram applies for privacy authorization, the virtual user identifier of the user determined according to the virtual user identifier determination mode indicated by the identity hiding category is obtained through the first server, and the virtual user identifier of the user and the privacy data applied for by the target miniprogram are returned to the second server corresponding to the target miniprogram, so as to realize the hiding of the user's real identity, help the user to protect personal privacy when enjoying normal services of the target miniprogram, and prevent being tracked. BRIEF DESCRIPTION OF DRAWINGS

[0030] In order to more clearly illustrate the technical solutions of the multiple embodiments disclosed in the present specification, the drawings required in the embodiment description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the present specification, and other drawings can also be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0031] Figure 1 is an exemplary system architecture diagram to which some embodiments of the present specification can be applied;

[0032] Figure 2 is a schematic diagram of an embodiment of a method for setting user identity hiding for a target miniprogram;

[0033] Figure 3 is a schematic diagram of a configuration process of an identity hiding category;

[0034] Figure 4 is a schematic diagram of an embodiment of a method for hiding user identity for a target miniprogram;

[0035] Figure 5 is a schematic diagram of prompt information for inquiring whether to agree to privacy authorization;

[0036] Figure 6 is a structural schematic diagram of an apparatus for setting user identity hiding for a target miniprogram;

[0037] Figure 7 is a structural schematic diagram of an apparatus for setting user identity hiding for a target miniprogram;

[0038] Figure 8is a structural schematic diagram of an apparatus for user identity hiding for a target applet. DETAILED DESCRIPTION

[0039] The present specification will be further described in conjunction with the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the related application, and not to limit the application. The described embodiments are only part of the embodiments of the present specification, not all. Based on the embodiments in the present specification, all other embodiments obtained by those skilled in the art without creative labor are within the scope of the present application.

[0040] It should be noted that, for the convenience of description, only the part related to the application is shown in the drawings. The embodiments in the present specification and the features in the embodiments can be combined with each other without conflict. In addition, the words "first", "second" and the like in the present specification are only used for information distinction, and do not have any limiting effect.

[0041] As mentioned before, business services and user privacy have always been in conflict. From the perspective of enterprises, by collecting user information and profiling users, more customized services can be provided for users. From the perspective of users, sometimes such customized services make them feel monitored and have no secrets in the network.

[0042] Based on this, some embodiments of the present specification provide a method for setting user identity hiding for a target applet and a method for user identity hiding for a target applet. Through the method, the user can protect personal privacy and prevent being tracked while enjoying normal business services of the applet. Specifically, Figure 1 An exemplary system architecture diagram applicable to these embodiments is shown.

[0043] As Figure 1 shown, the system architecture can include a host application, any applet (such as applet A shown in Figure 1 ) carried by the host application, a first server corresponding to the host application, and a second server corresponding to the applet. The first server is the background server of the host application, which can be implemented as a service platform, a physical server or a cloud server, etc., which is not specifically limited here. The second server is the background server of the corresponding applet.

[0044] The host application can be any type of client application, such as a payment client application, a social client application, or a financial client application, etc., which is not specifically limited here. In addition, the host application can be installed in various terminal devices, which can include smartphones, tablet computers, notebook computers, desktop computers, etc.

[0045] In practice, the host application can carry multiple applets, for any one of the multiple applets, e.g., applet A, the host application can support the user to configure an identity hiding category for the applet A. The identity hiding category can be used to indicate a virtual user identifier determination manner, so that the applet obtains a virtual user identifier determined according to the virtual user identifier determination manner when applying for privacy authorization.

[0046] Specifically, referring to Figure 1 , the user can first configure the identity hiding category for the applet A as shown by reference numeral 102. Then, the host application can request the first server to set identity hiding for the applet A as shown by reference numeral 104, so that the first server stores corresponding identity hiding setting information for the applet A, which can be used to indicate that the applet A has opened the identity hiding function. The identity hiding setting information may, for example, include the program identifier of the applet A, the real user identifier of the user, and the identity hiding category.

[0047] For any one of the applets carried by the host application, when the applet applies for privacy authorization, the first server can obtain a virtual user identifier of the user determined according to the virtual user identifier determination manner, and return the virtual user identifier and the privacy data of the user applied by the applet to the second server corresponding to the applet, so that the second server provides a service response for the user according to the privacy data of the user and the virtual user identifier.

[0048] Continuing to take the applet A as an example, after completing the identity hiding setting for the applet A, when the applet A applies for privacy authorization as shown by reference numeral 106, the host application can request the first server for an authorization code after the user agrees to the privacy authorization as shown by reference numeral 108. Then, the first server can return the authorization code to the host application as shown by reference numeral 110. Thereafter, the host application can return the authorization code to the applet A as shown by reference numeral 112. Next, the applet A can send the authorization code to the corresponding second server as shown by reference numeral 114. Then, the second server can request the first server for the privacy data of the user using the authorization code as shown by reference numeral 116. Then, the first server can return the privacy data of the user and a virtual user identifier to the second server as shown by reference numeral 118. The virtual user identifier is determined according to the virtual user identifier determination manner. Thereafter, the second server can provide a service response for the user according to the received privacy data of the user and the virtual user identifier as shown by reference numeral 120.

[0049] Thus, the user can customize the identity hiding for the applet A, and the applet A can obtain the virtual user identifier of the user and cannot obtain the real user identifier, so that the real identity of the user can be well hidden. Thus, the user can enjoy the normal service of the applet A while protecting the personal privacy and preventing being tracked.

[0050] Next, specific implementation steps of the above method are described in combination with specific embodiments. It should be noted that, in the following, any one applet carried by the host application is referred to as a target applet for the convenience of description.

[0051] Referring to Figure 2 which is a schematic diagram of one embodiment of the method for setting the user identity hiding for the target applet. The method includes the following steps:

[0052] In step 202, the host application obtains the identity hiding category configured by the user for the target applet.

[0053] In step 204, the host application sends an identity hiding setting request to the first server.

[0054] In step 206, the first server stores the program identifier, the real user identifier, and the identity hiding category correspondingly.

[0055] Next, each of the above steps is further described.

[0056] In step 202, the host application can obtain the identity hiding category configured by the user for the target applet in real time. The identity hiding category is used to indicate the virtual user identifier determination manner, so that the target applet obtains the virtual user identifier determined according to the virtual user identifier determination manner when applying for the privacy authorization.

[0057] For example, the virtual user identifier determination manner can include determining different virtual user identifiers of the user for different applets. Based on this, for each applet configured with the identity hiding category, different virtual user identifiers of the user can be determined for the applet when the applet applies for the privacy authorization. In this case, for multiple applets belonging to the same enterprise in the applets, since the multiple applets obtain different virtual user identifiers of the user, the enterprise cannot associate the user behavior information generated by the user in the multiple applets based on the same user identifier, so as to describe the user portrait of the user, thereby the personal privacy of the user can be well protected and the user can be prevented from being tracked.

[0058] In some embodiments, the host application can be preconfigured with multiple hiding categories. For example, the multiple hiding categories can include a first hiding category and a second hiding category, etc.

[0059] The first hidden category indicated virtual user identity determination manner specifically includes that different virtual user identities of a user are determined for different applets, and the same virtual user identity of the user is determined for the same applet. The first hidden category can be regarded as a hidden category in the APPID (program identifier) dimension. It can be understood that, in a case where the identity hiding category configured for the target applet is the first hidden category, the same virtual user identity of the user can be determined for the target applet each time the target applet applies for privacy authorization, and the virtual user identity is different from the virtual user identity that has been determined for other applets.

[0060] The second hidden category indicated virtual user identity determination manner specifically includes that different virtual user identities of a user are determined for different applets, and different virtual user identities of the user are determined for the same applet. It can be understood that, in a case where the identity hiding category configured for the target applet is the second hidden category, different virtual user identities of the user can be determined for the target applet each time the target applet applies for privacy authorization, and the virtual user identities are different from the virtual user identities that have been determined for other applets.

[0061] Generally, 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 category can be regarded as a hidden category in the interface dimension. It can be understood that, in a case where the hidden category in the interface dimension is configured for the target applet, different virtual user identities of a user are returned for each call of the authorization interface by the target applet.

[0062] In practice, when the user wants to enjoy the recommendation service of the target applet, the first hidden category can be configured for the target applet to allow the target applet to use the same virtual user identity of the user globally. When the user does not need to use the recommendation service of the target applet, or when the target applet is an applet that provides temporary service, the second hidden category can be configured for the target applet to make the target applet obtain different virtual user identities of the user each time. In this way, the real identity of the user can be hidden without affecting the business function of the target applet.

[0063] In other embodiments, the identity hiding category and the corresponding virtual user identifier determination manner can also have other setting manners. For example, in one example, a more coarse-grained manner is adopted, and the small programs are divided into several categories according to certain rules, and different virtual user identifiers are determined for the small programs of different categories. In another example, on the basis of the first and second hiding categories described above, a third hiding category can also be set, wherein for the same user of the same small program, the virtual user identifier is replaced once every certain time interval, for example, one day, one week; and within the time interval, the same virtual user identifier is used for the user, thereby allowing the small program to have user context data within a certain time range. With regard to the identity hiding category and the corresponding virtual user identifier determination manner, those skilled in the art can make more designs on the basis of reading the present specification, and they are not enumerated here.

[0064] In some embodiments, before step 202, a step of displaying an identity hiding setting window to the user in response to a triggering operation of the user on an identity hiding setting entry displayed on a first page of the target small program can also be included. The first page can be any one page of the target small program. Further, the first page can be the home page of the target small program. The identity hiding setting entry can be presented by the host application on the first page. In addition, the identity hiding setting entry can be an entry in the form of a button or a hyperlink, which is not specifically limited here. Based on this, step 202 can further include obtaining the identity hiding category configured by the user through the identity hiding setting window.

[0065] In some embodiments, the identity hiding category is one of the above-mentioned multiple hiding categories, and the identity hiding setting window can display multiple options corresponding to the above-mentioned multiple hiding categories. The above-mentioned multiple hiding categories and the multiple options have a one-to-one correspondence. The multiple options can be options in the form of radio buttons or switch controls, which are not specifically limited here. Based on this, in step 202, the host application can obtain the hiding category pointed by the category selection operation as the identity hiding category in response to the category selection operation performed by the user through any one of the multiple options.

[0066] Taking the first page as the home page and the multiple hiding categories including the first hiding category (i.e., the APPID dimension hiding category) and the second hiding category (i.e., the interface dimension hiding category) as an example, the configuration process of the identity hiding category can be as shown in Figure 3 The left part of Figure 3 shows the home page of the target small program, and the identity hiding setting button is displayed in the upper right corner of the home page. When the user wants to perform identity hiding setting for the target small program, the identity hiding setting button can be clicked to enter Figure 3The identity hiding setting window is shown in the right part of FIG. 2. In the identity hiding setting window, switch controls corresponding to the hiding categories of the APPID dimension and the interface dimension are displayed, and the switch controls are in the off state by default. When the user wants to set the hiding category of the APPID dimension as the identity hiding category corresponding to the target mini-program, the user can click the switch control corresponding to the hiding category of the APPID dimension to turn on the switch control. The host application can obtain the hiding category of the APPID dimension as the identity hiding category configured by the user for the target mini-program in response to the click operation of the user on the switch control, that is, the category selection operation performed through the switch control.

[0067] In some embodiments, in order to facilitate the user to clearly understand the purpose of each hiding category, the description information of each hiding category can be presented in the identity hiding setting window. For example, Figure 3 The description information of the hiding category of the APPID dimension "after turning on, the same virtual user identifier of the user is used globally in the mini-program" and the description information of the hiding category of the interface dimension "after turning on, the virtual user identifier of the user is different each time the interface is called in the mini-program" are presented in FIG. 2. It should be understood that the specific content of the description information can be set according to actual needs, which is not limited here.

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

[0069] 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 mini-program according to the virtual user identifier determination manner can be specifically performed by the host application. Based on this, the identity hiding setting request in step 204 can not include the identity hiding category, and the first server can not store the identity hiding category in step 206. Further, the identity hiding category in step 206 can be replaced by an identity hiding flag, which can be used to indicate that the user has turned on the identity hiding function for the target mini-program.

[0070] Figure 2The corresponding embodiment provides a method for setting a user identity hiding mode for a target miniprogram. The host application acquires an identity hiding category configured by a user for a target miniprogram, and sends an identity hiding setting request to a 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 miniprogram, a real user identifier of the user, and the identity hiding category) for the target miniprogram, thereby realizing customized selection of the identity hiding mode by the user.

[0071] Next, an identity hiding method when a target miniprogram applies for privacy authorization is introduced.

[0072] Referring to Figure 4 which is a schematic diagram of one embodiment of a method for setting a user identity hiding mode for a target miniprogram. The method comprises the following steps:

[0073] In step 406, the host application sends a first acquisition request for an authorization code to the first server in response to a privacy authorization operation performed by the user for the target miniprogram, wherein the first acquisition request at least comprises a program identifier of the target miniprogram and a real user identifier of the user.

[0074] In step 408, the first server generates the authorization code according to the first acquisition request.

[0075] In step 410, the first server returns the authorization code to the host application.

[0076] In step 412, the host application sends the authorization code to a second server corresponding to the target miniprogram via the target miniprogram.

[0077] In step 414, the first server receives a second acquisition request for privacy data of the user from the second server, wherein the second acquisition request comprises the authorization code.

[0078] In step 416, the first server acquires the privacy data of the user and a virtual user identifier of the user according to the second acquisition request.

[0079] In step 418, the first server returns the acquired privacy data of the user and the virtual user identifier to the second server.

[0080] Next, each step shown in Figure 4 is further described.

[0081] In step 406, the host application sends a first acquisition request for an authorization code to the first server in response to a privacy authorization operation performed by the user for the target miniprogram, wherein the first acquisition request at least comprises a program identifier of the target miniprogram and a real user identifier of the user.

[0082] In practice, when the virtual user identifier of the user is determined by the first server, the first obtaining request can include the program identifier of the target miniprogram and the real user identifier of the user. When the virtual user identifier of the user is determined by the host application, the first obtaining request can include, in addition to the program identifier of the target miniprogram and the real user identifier of the user, the virtual user identifier of the user determined by the host application for the target miniprogram.

[0083] In some embodiments, before step 406, the method can further include: step 402, receiving, by the host application through the authorization interface thereof, a privacy authorization request of the target miniprogram; and step 404, presenting, by the host application, prompt information for inquiring whether to agree to the privacy authorization to the user, the prompt information including an agreement option for triggering agreement to the privacy authorization. Based on this, the above-mentioned operation of agreeing to the privacy authorization can include an operation of triggering the agreement option.

[0084] In practice, the above-mentioned prompt information can specifically include prompt content and an agreement option. The agreement option can be implemented as a button for indicating agreement, for example, a button with a name such as “Yes”, “Y”, “Yes”, or “Agree”. The prompt content may, for example, include the name of the target miniprogram and the data range of the privacy data applied for by the target miniprogram. From the perspective of the user, the data range can be referred to as a user authorization range. The user authorization range may, for example, include a geographic location, a picture library, a short message record, a call record, and / or a contact list, without being specifically limited here.

[0085] Optionally, the above-mentioned prompt information can further include a rejection option for triggering rejection of the privacy authorization by the user. The rejection option can be implemented as a button for indicating rejection, for example, a button with a name such as “No”, “N”, “No”, or “Reject”.

[0086] Referring to Figure 5 , which is a schematic diagram of prompt information for inquiring whether to agree to the privacy authorization. The prompt information includes prompt content “** Miniprogram applies for contact list authorization”, an agreement button for triggering agreement to the privacy authorization by the user, and a rejection button for triggering rejection of the privacy authorization by the user. Among them, “** Miniprogram” is the name of the target miniprogram, and “contact list” is the data range of the privacy data applied for by the target miniprogram.

[0087] After step 406 is performed, the first server can perform step 408 of generating an authorization code according to the first obtaining request. Then, the first server can perform step 410 of returning the authorization code to the host application.

[0088] In practice, the first server can generate the authorization code by using a preset authorization code generation rule. The generation process of the authorization code is not specifically limited here. It should be noted that after the authorization code is generated, the first server can correspondingly cache the first obtaining request and the authorization code.

[0089] Then, in step 412, the host application can send the authorization code to the target mini-program, so that the target mini-program sends the authorization code to the corresponding second server.

[0090] Then, in step 414, the first server can receive, from the second server, a second acquisition request for the privacy data of the user, which includes the authorization code.

[0091] Then, in step 416, the first server can acquire the privacy data of the user and the virtual user identifier of the user according to the second acquisition request.

[0092] In some embodiments, the second acquisition request can include a user authorization scope, and the first server can acquire the privacy data of the user within the user authorization scope.

[0093] In some embodiments, the first acquisition request in the foregoing can 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 then acquire the privacy data of the user within the user authorization scope according to the user authorization scope in the first acquisition request.

[0094] In some embodiments, the virtual user identifier is determined by the first server. In step 416, the first server can locate the first acquisition request according to the authorization code in the second acquisition request, and then acquire the identity hiding category corresponding to the program identifier and the real user identifier of the user which is stored locally according to the program identifier in the first acquisition request, and then determine the virtual user identifier of the user according to the virtual user identifier determination manner indicated by the identity hiding category.

[0095] As an example, when the identity hiding category is a first hiding category, the first server can determine whether the program identifier has associated the virtual user identifier of the user under the first hiding category. If the determination result is yes, the first server can acquire the virtual user identifier of the user associated with the program identifier under the first hiding category. If the determination result is no, the first server can randomly generate the virtual user identifier of the user for the target mini-program. It can be understood that the virtual user identifier generated this time is different from the virtual user identifier generated before.

[0096] It should be noted that in the case where the determination result is no, after randomly generating the virtual user identifier of the user for the target mini-program, the first server can set the virtual user identifier as the virtual user identifier of the user associated with the program identifier under the first hiding category. Specifically, the first server can store the randomly generated virtual user identifier in correspondence with the program identifier, the real user identifier of the user and the first hiding category.

[0097] As another example, when the identity hiding category is the second hiding category, the first server can randomly generate a virtual user identifier of the user for the current request of the target mini-program. This implementation manner can well hide the real identity of the user, and further prevent tracking, malicious recommendation, etc.

[0098] In some embodiments, the virtual user identifier is determined by the host application. Before step 406, the host application can obtain the virtual user identifier of the user according to the virtual user identifier determination manner indicated by the identity hiding category that has been stored for the target mini-program. Here, the virtual user identifier obtaining method adopted by the host application can refer to the related content described for the first server in the foregoing, which will not be described herein again.

[0099] Based on this, the first obtaining request in step 406 can further include the virtual user identifier of the user determined by the host application. In step 416, the first server can 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 pointed out that this implementation manner does not need the first server to generate the virtual user identifier, and can effectively improve the response performance of the first server.

[0100] Then, in step 418, the first server can return the obtained privacy data and virtual user identifier of the user to the second server. After that, the second server can provide a service response for the user according to the received privacy data and virtual user identifier of the user.

[0101] Figure 4 The method for hiding the user identity of the target mini-program provided by the corresponding embodiments can obtain the virtual user identifier of the user determined according to the virtual user identifier determination manner indicated by the identity hiding category through the first server when the target mini-program applies for privacy authorization, and return the virtual user identifier of the user and the privacy data applied for by the target mini-program to the second server corresponding to the target mini-program, which can realize the hiding of the real identity of the user, can help the user to protect the personal privacy when enjoying the normal service of the target mini-program, and prevent being tracked, etc. In addition, the target mini-program can apply for privacy authorization by calling the authorization interface, which can effectively solve the generation and maintenance of the virtual user identifier based on the unified authorization interface.

[0102] Further reference Figure 6 , the present specification provides an embodiment of an apparatus for setting a user identity hiding for a target mini-program, which can be applied to a host application (such as the host application shown in Figure 1 ) where the target mini-program is located.

[0103] As Figure 6As shown, the device 600 for setting user identity hiding for a target miniprogram in the embodiment includes an obtaining unit 601 and a sending unit 602. The obtaining unit 601 is configured to obtain an identity hiding category configured by a user for a target miniprogram, the identity hiding category being used to indicate a virtual user identifier determination manner, so that the target miniprogram obtains a virtual user identifier determined according to the virtual user identifier determination manner when applying for privacy authorization; and the sending unit 602 is configured to send an identity hiding setting request to a first server corresponding to a host application, the request including a program identifier of the target miniprogram, a real user identifier of the user, and the identity hiding category; so that the first server stores the program identifier, the real user identifier, and the identity hiding category correspondingly.

[0104] In some embodiments, the device 600 described above can further include a display unit (not shown in the figure) configured to display an identity hiding setting window to the user in response to a triggering operation of the user on an identity hiding setting entry displayed on a first page of the target miniprogram; and the obtaining unit 601 can be further configured to obtain the identity hiding category configured by the user through the identity hiding setting window.

[0105] In some embodiments, the virtual user identifier determination manner includes determining different virtual user identifiers of the user for different miniprograms. Further, the identity hiding category is a first hiding category, and the virtual user identifier determination manner further includes determining a same virtual user identifier of the user for a same miniprogram; or the identity hiding category is a second hiding category, and the virtual user identifier determination manner further includes determining different virtual user identifiers of the user for a same miniprogram.

[0106] 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 obtaining unit 601 can be further configured to obtain, as the identity hiding category, a hiding category pointed by a category selection operation of the user through any one of the plurality of options.

[0107] Further reference Figure 7 is made to an embodiment of a device for setting user identity hiding for a target miniprogram, which can be applied to a first server corresponding to a host application in which the target miniprogram is located (such as the first server shown in Figure 1 ).

[0108] As Figure 7As shown, the apparatus 700 for setting user identity concealment for a target mini-program in this embodiment includes a receiving unit 701 and a storage unit 702. The receiving unit 701 is configured to receive an identity concealment setting request from a host application, which includes the program identifier of the target mini-program, the user's real user identifier, and the identity concealment category configured by the user for the target mini-program. The identity concealment category indicates the method for determining the virtual user identifier, enabling the target mini-program to obtain the virtual user identifier determined according to the virtual user identifier determination method when requesting privacy authorization. The storage unit 702 is configured to store the program identifier, the real user identifier, and the identity concealment category accordingly.

[0109] Further reference Figure 8 This specification provides an embodiment of a device for hiding the user identity of a target mini-program. The target mini-program is configured with an identity hiding category, which is used to indicate the method of determining the virtual user identifier. This device can be applied to a first server corresponding to the host application where the target mini-program resides (e.g., ...). Figure 1 (The first server shown).

[0110] like Figure 8 As shown, the device 800 for hiding the user's identity in a target mini-program according to this embodiment includes: a first receiving unit 801, a generating unit 802, a second receiving unit 803, an acquiring unit 804, and a sending unit 805. The first receiving unit 801 is configured to receive a first acquiring request for an authorization code from a host application. The first acquiring request is sent by the host application in response to a user's consent to privacy authorization operations performed on the target mini-program. The first acquiring request includes at least the program identifier of the target mini-program and the user's real user identifier. The generating unit 802 is configured to generate and return an authorization code based on the first acquiring request. The second receiving unit 803 is configured to receive a second acquiring request for the user's privacy data, including the authorization code, from a second server corresponding to the target mini-program. The acquiring unit 804 is configured to acquire the user's privacy data and the user's virtual user identifier based on the second acquiring request. The virtual user identifier is determined according to the aforementioned virtual user identifier determination method. The sending unit 805 is configured to return the acquired user's privacy data and virtual user identifier to the second server.

[0111] In some embodiments, the first acquisition request further includes a virtual user identifier of the user determined by the host application; and the acquisition unit 804 may include a first acquisition subunit (not shown in the figure) configured to acquire the user's virtual user identifier from the first acquisition request.

[0112] In some embodiments, the obtaining unit 804 can 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 of the identity hiding category.

[0113] In some embodiments, the identity hiding category is a first hiding category; and the second obtaining subunit can include a first obtaining module (not shown in the figure) configured to determine whether the program identifier has been associated with the virtual user identifier of the user under the first hiding category, and if the determination result is yes, obtain the virtual user identifier of the user that the program identifier has been associated with under the first hiding category, and if the determination result is no, randomly generate the virtual user identifier of the user for the target mini-program.

[0114] In some embodiments, the first obtaining module can be further configured to, after randomly generating the virtual user identifier of the user for the target mini-program, set the virtual user identifier as the virtual user identifier of the user that the program identifier is associated with under the first hiding category.

[0115] In some embodiments, the identity hiding category is a second hiding category; and the second obtaining subunit can include a second obtaining module (not shown in the figure) configured to randomly generate the virtual user identifier of the user for the current request of the target mini-program.

[0116] In some embodiments, the first obtaining request further includes a user authorization range; and the obtaining unit 804 can include a third obtaining subunit (not shown in the figure) configured to obtain the privacy data of the user within the user authorization range.

[0117] In Figure 6 、 Figure 7 、 Figure 8 In the corresponding device embodiments, the specific processing of each unit and the technical effects brought by it can refer to the related description of the method embodiments in the foregoing description, and will not be described here.

[0118] The embodiments of the present specification also provide a computer readable storage medium having a computer program stored thereon, wherein when the computer program is executed in a computer, the computer is caused to execute the method described in each of the method embodiments.

[0119] The embodiments of the present specification also provide a computing device including a memory and a processor, wherein the memory has executable code stored therein, and the processor executes the executable code to implement the method described in each of the method embodiments.

[0120] 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 method described in each of the method embodiments.

[0121] Those skilled in the art can understand that, in one or more examples described above, the functions described in the embodiments disclosed in the specification can be implemented by hardware, software, firmware or any combination thereof. When implemented by software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or codes on a computer readable medium.

[0122] In some cases, the actions or steps recited in the claims can be performed in a different order and still accomplish desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown or sequential order in order to achieve the desired results. In some implementations, multitasking and parallel processing can be advantageous.

[0123] The above detailed description merely describes specific implementations, not protecting the scope of the embodiments disclosed in the specification. Any modifications, equivalent replacements, improvements and the like made on the basis of the technical solutions of the embodiments disclosed in the specification shall be included in the protection scope of the embodiments disclosed in the specification.

Claims

1. A method for hiding the user identity of a target mini-program, wherein the target mini-program is configured with an identity hiding category, the identity hiding category being used to indicate the method for determining a virtual user identifier, the method being applied to a first server corresponding to the host application where the target mini-program resides, comprising: When the target mini-program applies for privacy authorization, the privacy data of the user applying for the authorization is obtained, as well as the virtual user identifier corresponding to the user's real user identifier. The virtual user identifier is determined according to the virtual user identifier determination method. Obtaining the virtual user identifier corresponding to the user's real user identifier includes: If the identity concealment category is the first concealment category, then determine whether the program identifier of the target mini-program has been associated with the user's virtual user identifier under the first concealment category; if the determination result is yes, then obtain the user's virtual user identifier that has been associated with the program identifier under the first concealment category; if the determination result is no, then randomly generate the user's virtual user identifier for the target mini-program. The obtained user privacy data and virtual user identifier are returned to the second server corresponding to the target mini-program.

2. The method according to claim 1, wherein, The step of obtaining the virtual user identifier corresponding to the real user identifier includes: The user's virtual user identifier is obtained according to the virtual user identifier determination method indicated by the stored identity concealment category.

3. The method according to claim 1, wherein, After randomly generating the virtual user identifier for the user in the target mini-program, the method further includes: Set the virtual user identifier as the virtual user identifier of the user associated with the program identifier under the first hidden category.

4. The method according to claim 1, wherein, The method further includes: If the identity concealment category is the second concealment category, then for this application of the target mini-program, a virtual user identifier for the user will be randomly generated.

5. A method for hiding the user identity of a target mini-program, wherein the target mini-program is located in a host application, and the host application corresponds to a first server, the method comprising: The host application sends an identity concealment setting request to the first server. The identity concealment setting request is generated in response to obtaining the identity concealment category configured by the user for the target mini-program. The identity concealment category is used to indicate the virtual user identifier determination method, so that when the target mini-program applies for privacy authorization, it obtains the virtual user identifier determined according to the virtual user identifier determination method. The identity concealment setting request includes at least the program identifier of the target mini-program and the real user identifier of the user. The first server stores corresponding identity hiding settings information for the target mini-program. The identity hiding settings information is used to indicate that the target mini-program has enabled the identity hiding function, and includes at least the program identifier and the real user identifier.

6. The method according to claim 5, wherein, The identity concealment settings information also include an identity concealment flag, which is used to indicate that the user has enabled the identity concealment function for the target mini-program.

7. The method according to claim 5, wherein, Before the host application sends the identity hiding setting request to the first server, the method further includes: The host application responds to the user's triggering operation on the identity hiding settings entry displayed on the first page of the target mini-program by showing the identity hiding settings window to the user; The host application obtains the identity concealment category configured by the user through the identity concealment settings window.

8. The method according to any one of claims 5-7, wherein, The method for determining the virtual user identifier includes determining different virtual user identifiers for different mini-programs.

9. The method according to claim 8, wherein, The identity concealment category is the first concealment category, and the method for determining the virtual user identifier further includes determining the same virtual user identifier for the same mini-program; or... The identity concealment category is the second concealment category, and the method for determining the virtual user identifier also includes determining different virtual user identifiers for the same mini-program.

10. The method according to claim 7, wherein, The identity concealment category is one of multiple concealment categories, and the identity concealment settings window displays multiple options corresponding to the multiple concealment categories; as well as The step of obtaining the identity concealment category configured by the user through the identity concealment settings window includes: In response to a user's category selection operation performed through any one of the multiple options, the hidden category pointed to by the category selection operation is obtained as the identity hiding category.

11. An apparatus for hiding the user identity of a target mini-program, the target mini-program being configured with an identity hiding category, the identity hiding category being used to indicate a method for determining a virtual user identifier, the apparatus being applied to a first server corresponding to a host application where the target mini-program resides, comprising: The acquisition unit is configured to acquire, when the target mini-program applies for privacy authorization, the privacy data of the user applying for privacy authorization by the target mini-program, and to acquire a virtual user identifier corresponding to the user's real user identifier, wherein the virtual user identifier is determined according to the virtual user identifier determination method; the acquisition of the virtual user identifier corresponding to the user's real user identifier includes: If the identity concealment category is the first concealment category, then determine whether the program identifier of the target mini-program has been associated with the user's virtual user identifier under the first concealment category; if the determination result is yes, then obtain the user's virtual user identifier that has been associated with the program identifier under the first concealment category; if the determination result is no, then randomly generate the user's virtual user identifier for the target mini-program. The sending unit is configured to return the acquired user's privacy data and virtual user identifier to the second server corresponding to the target mini-program.

12. A computer-readable storage medium having a computer program stored thereon, wherein, When the computer program is executed in the computer, it causes the computer to perform the method according to any one of claims 1-10.

13. A computing device comprising a memory and a processor, wherein, The memory stores executable code, and when the processor executes the executable code, it implements the method of any one of claims 1-10.

Images