Small program authorization processing method, device and equipment

By uniformly initiating pre-authorization on the centralized scene page of the parent application, the problem of frequent interruption of mini-program authorization requests is solved, the user experience and security are improved, and the convenient authorization processing of mini-programs is realized.

CN119066677AActive Publication Date: 2024-12-03ALIPAY (HANGZHOU) INFORMATION TECH CO LTD

Patent Information

Application Number
CN202411111916.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-13
Publication Date
2024-12-03
Estimated Expiration
2044-08-13

AI Technical Summary

Technical Problem

In the scenario where the parent application is connected to multiple mini programs, the user experience is frequently disturbed by authorization requests, which affects the mini program's traffic acquisition and user conversion.

Method used

By entering the centralized scenario page, a unified pre-authorization request is initiated to the user, authorization data is generated, and the data is directly used when the user enters the specific applet to avoid requesting authorization in the applet.

Benefits of technology

It reduces the disturbance of authorization pop-ups to users, improves the user experience, and manages authorization through the parent application, enhances security and prevents mini-programs from abuse of permissions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119066677A_ABST
    Figure CN119066677A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses an applet authorization processing method, device and equipment. According to the scheme, the method comprises the steps of entering a centralized scene page of a specified application, wherein the centralized scene page is provided with entrances of a plurality of applets accessed by the specified application; in the centralized scene page, initiating a unified authorization request corresponding to the plurality of applets to a current user; if the current user agrees to perform pre-authorization in response to the unified authorization request, triggering corresponding authorization data generation; and after the pre-authorization, if the current user enters the corresponding applet in the plurality of applets from the entry in the centralized scene page, directly obtaining the specified information of the current user in the corresponding applet according to the authorization data, and if the current user enters the corresponding applet from the entry in the centralized scene page, directly obtaining the specified information of the current user in the corresponding applet. And the service module is used for carrying out the service of the corresponding applet for the current user without requesting authorization from the current user in the corresponding applet.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This specification relates to the field of mini-program technology, and in particular to a mini-program authorization processing method, device and equipment. Background Art

[0002] With the development of Internet technology and the popularization of smart phones, more and more businesses are conducted through various applications, which has also led to the emergence of some large and medium-sized comprehensive platform applications.

[0003] Some sub-applications of the service provider to which the comprehensive platform application belongs, or applications of other small and medium-sized service providers, will embed the services they can provide into the comprehensive platform application in the form of mini-programs. The comprehensive platform application will be regarded as the parent application, and the mini-programs can be run based on the parent application, so that services can be provided to users in a lighter manner. Users do not need to download and install these small-scale corresponding application clients separately, which improves the user experience and helps to obtain more traffic through the parent application.

[0004] In this context, the parent application often connects to many mini-programs, and some users can frequently access different mini-programs in the parent application. Current mini-programs usually require users to provide authorization for information such as geographic location, avatar nickname, mobile phone number, discounts, messages, etc. when using them. The mini-program will request user authorization through pop-up windows. In this case, for users who access different mini-programs in a short period of time, they will be frequently disturbed by authorization request pop-ups from different mini-programs, which will affect the user experience, and in turn affect the effectiveness of the mini-program in acquiring and converting traffic, and may even cause the parent application itself to lose users.

[0005] Based on this, in the scenario where the parent application is connected to multiple mini-programs, a mini-program authorization solution with better user experience is needed. Summary of the invention

[0006] One or more embodiments of the present specification provide a method, apparatus, device, and storage medium for processing mini-program authorization to solve the following technical problem: In a scenario where a parent application is connected to multiple mini-programs, a mini-program authorization solution with better user experience is needed.

[0007] To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

[0008] One or more embodiments of this specification provide a method for processing mini-program authorization, including:

[0009] Enter the centralized scene page of the specified application, which has entrances to multiple mini-programs connected to the specified application;

[0010] Initiate a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page;

[0011] If the current user agrees to perform pre-authorization in response to the unified authorization request, the generation of corresponding authorization data is triggered;

[0012] After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the corresponding mini-program directly obtains the specified information of the current user according to the authorization data, and uses it to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0013] One or more embodiments of this specification provide a small program authorization processing device, including:

[0014] A centralized scene entry module is used to enter the centralized scene page of a specified application. The centralized scene page has respective entrances to multiple mini-programs connected to the specified application.

[0015] A unified authorization request module, in the centralized scenario page, initiates a unified authorization request corresponding to the multiple mini-programs to the current user;

[0016] An authorization data triggering module triggers the generation of corresponding authorization data if the current user agrees to perform pre-authorization in response to the unified authorization request;

[0017] The mini-program quick processing module, after the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, then in the corresponding mini-program, the specified information of the current user is directly obtained according to the authorization data, so as to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0018] One or more embodiments of this specification provide a small program authorization processing device, including:

[0019] at least one processor; and,

[0020] a memory communicatively connected to the at least one processor; wherein,

[0021] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0022] Enter the centralized scene page of the specified application, which has entrances to multiple mini-programs connected to the specified application;

[0023] Initiate a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page;

[0024] If the current user agrees to perform pre-authorization in response to the unified authorization request, the generation of corresponding authorization data is triggered;

[0025] After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the corresponding mini-program directly obtains the specified information of the current user according to the authorization data, and uses it to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0026] One or more embodiments of this specification provide a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured to:

[0027] Enter the centralized scene page of the specified application, which has entrances to multiple mini-programs connected to the specified application;

[0028] Initiate a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page;

[0029] If the current user agrees to perform pre-authorization in response to the unified authorization request, the generation of corresponding authorization data is triggered;

[0030] After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the corresponding mini-program directly obtains the specified information of the current user according to the authorization data, and uses it to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0031] At least one of the above-mentioned technical solutions adopted in one or more embodiments of the present specification can achieve the following beneficial effects: considering that if the current user enters the centralized scenario page of the specified application (as the parent application), there is a great probability that the user will enter the mini-program through different mini-program entrances provided by the page, and may also exit the mini-program and return to the page, and then enter other mini-programs, thereby using multiple different mini-programs in a short period of time, therefore, when the user initially arrives at the centralized scenario page, it can represent multiple mini-programs and uniformly request pre-authorization from the user, instead of requesting authorization from the user separately in the mini-programs that the user may further enter from here later, thereby greatly reducing the disturbance of the authorization pop-up window to the user; not only that, when using If the user agrees to the pre-authorization, such authorization can be conveniently controlled by the parent application to prevent the abuse of the mini-program. Only when the user actually enters a mini-program from the centralized scene page can the mini-program actually use the authorized limitations. If the user has not yet entered the mini-program, then even if the user has performed the pre-authorization, the mini-program may still not be allowed to use the authorized limitations. Moreover, the validity of the pre-authorization can also be converged to the jurisdiction of the centralized scene page, so that if the user enters the mini-program from channels other than the centralized scene page, the mini-program may still not be allowed to use the authorized limitations; thereby improving security. Therefore, the above solution can effectively improve user experience and take into account security. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0033] Figure 1 A flowchart of a method for processing mini-program authorization provided for one or more embodiments of this specification;

[0034] Figure 2 A flowchart of a solution for obtaining user specified information in a mini program provided in one or more embodiments of this specification;

[0035] Figure 3 A flowchart of a small program quick authorization processing solution in an application scenario provided by one or more embodiments of this specification;

[0036] Figure 4 One or more embodiments of this specification provide Figure 3 Schematic diagram of some page effects of the middle solution;

[0037] Figure 5 A flowchart of a risk defense solution for cooperating with pre-authorization provided in one or more embodiments of this specification;

[0038] Figure 6 A flowchart of a user protection solution for a mini-program provided by a parent application in one or more embodiments of this specification;

[0039] Figure 7 A schematic diagram of the structure of a small program authorization processing device provided for one or more embodiments of this specification;

[0040] Figure 8 A schematic diagram of the structure of a mini-program authorization processing device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

[0041] The embodiments of this specification provide a method, apparatus, device and storage medium for processing mini-program authorization.

[0042] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0043] As mentioned in the background technology, at present, for some large and medium-sized comprehensive platform applications, when users enter the mini program in a centralized scenario, there may be frequent pop-ups, lengthy and confusing processes, and other experience problems. This also brings more negative effects, including: large process consumption of platforms and merchants, and waste of operating costs. For example, for mini programs entered in a centralized scenario, when the mini program is a non-well-known merchant, because users do not understand the scenario and there is no brand endorsement, the authorization approval rate is low when the experience is poor; low platform satisfaction affects user revisits and retention. For example, for well-known mini programs that users enter in a centralized scenario, although the authorization approval rate may not be affected due to targeted consumption and brand endorsement, it may affect users' overall satisfaction with the platform compared to other platforms that may do better, thereby affecting the competitiveness of the platform.

[0044] In order to solve these problems, this application can quickly request pre-authorization from users in the scenario of platform-centralized traffic distribution, and try to avoid requesting authorization separately in each mini-program, thereby reducing multiple pop-up window interruptions and eliminating the need for troublesome mini-program adaptation and transformation, which helps to improve user experience, platform satisfaction and traffic conversion rate. Based on this overall idea, the solution of this application is further explained below.

[0045] Regarding authorization, based on the legal and justifiable principle of minimum necessity for personal information protection, the user's right to know and autonomy is protected. When a third party or other non-information holder needs to obtain the user's information left on the current platform to complete the service, the user's full consent is required. For example, assuming that the user wants to use the taxi service provided by other platforms on the current platform, currently, users generally have two choices, one is to choose to enter a new mobile phone number to register a new account; the other is to choose to use the current platform account to quickly log in. In this case, the user agrees to authorize the other platform to use his account information on the current platform.

[0046] Figure 1 A flowchart of a method for processing mini-program authorization provided for one or more embodiments of this specification. The execution subject of the process may include a client of a specified application (the mini-program connected to the client can also be regarded as a whole with the client here), and may also include a corresponding server. For the client, the hardware execution subject also includes the device where the client is located, such as the user's smartphone, tablet computer, etc.

[0047] Figure 1 The process in includes the following steps:

[0048] S102: Enter the centralized scene page of the specified application, and the centralized scene page has respective entrances to multiple mini-programs connected to the specified application.

[0049] In one or more embodiments of the present specification, the designated application may be the parent application mentioned in the background technology, and in particular may be a large or medium-sized platform application with large traffic, which, through one or more centralized scenario pages, directs traffic to multiple cooperatively connected mini-programs to increase users' visits to these mini-programs.

[0050] The centralized scenario mentioned here is essentially a centralized traffic distribution scenario, which is a centralized traffic entrance provided by the platform for other partners. The centralized scenario page can especially be the homepage of the scenario. For example, the main page of business scenarios such as the consumer circle, citizen center, game center, and medical center provided by a payment platform is similar to the public area after entering the gate of an offline commercial complex, where users can freely choose to go to the store they are interested in (similar to a mini program).

[0051] The entrances to the mini-programs are usually presented in the form of corresponding icons, cards, text or other links in the centralized scene page, and users can jump to the corresponding mini-programs by clicking. It should be noted that after jumping into the mini-program, the user is generally still in the designated application. However, depending on the cooperation mode and technical implementation mode, the user can also leave the designated application. In this case, the solution of this application can be continued to be implemented based on cooperation between applications or assistance at the operating system level, and the execution subject of the solution can be increased accordingly.

[0052] S104: In the centralized scenario page, a unified authorization request corresponding to the multiple mini-programs is initiated to the current user.

[0053] In one or more embodiments of this specification, in a centralized scenario page, a pop-up window is displayed to the current user, and a unified authorization request corresponding to multiple applets is initiated through the pop-up window, so that the current user can authorize by interacting with the pop-up window. In addition to the pop-up window method, other methods can also be used, such as banners, tags, additional small screen notifications, etc. Of course, these methods may actually cause some disturbance to the user, but this application is to use this possible disturbance in exchange for no need to disturb the user multiple times in different applets in the future, so it is very cost-effective overall.

[0054] In one or more embodiments of this specification, the authorization requested by the unified authorization request is called pre-authorization, that is, the authorization performed in advance before the current user enters each mini-program. However, it should be noted that although the authorization limit here is unified for these multiple mini-programs, it is also controlled by the specified application. In other words, the user is essentially authorizing the specified application, and the specified application can control when the permission takes effect and for which mini-program according to needs, so as to avoid authorization generalization and abuse of permissions by multiple mini-programs. In addition, even if it is the specified application itself, it can also limit the specific conditions under which the specified application can use the permission based on the pre-negotiation with the user or the security policy of the platform itself.

[0055] S106: If the current user agrees to perform pre-authorization in response to the unified authorization request, generation of corresponding authorization data is triggered.

[0056] Taking the unified authorization request in a pop-up window as an example, the current user can click the corresponding button in the pop-up window to give instructions to agree to the pre-authorization or reject the pre-authorization. If the user agrees, authorization data will be generated accordingly to describe the current authorization consent or as authorization credentials for subsequent verification of permissions. The authorization data can be generated on the current user terminal or on the corresponding server, depending on whether the subsequent verification is to be conducted locally or remotely. The authorization data can indicate the authorized status, and can also indicate which centralized scenario or which centralized scenario page the authorization is for. More instructions can be given as needed, such as indicating the authorization validity period, the authorized business scope, etc.

[0057] S108: After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the specified information of the current user is directly obtained in the corresponding mini-program according to the authorization data, so as to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0058] The designated information is information that requires the authorization of the current user to obtain, and it is usually information involving user privacy, such as the user's geographic location, avatar nickname, mobile phone number, discounts, etc. In the absence of prior authorization, if the current user enters the corresponding mini-program among multiple mini-programs from the entrance in the centralized scene page, if the mini-program wants to obtain the designated information of the current user, then the mini-program needs to initiate an authorization request to the user in the mini-program (usually in the form of a pop-up window), as described in the background technology. Only after the user agrees to the authorization can the designated information of the current user be obtained. In step S108, the so-called "direct acquisition" means that the designated information of the current user can be obtained without disturbing the user in the corresponding mini-program (for example, a pop-up window) to request authorization, and based on the verification of the authorization data, it can be obtained if the verification passes.

[0059] Furthermore, the designated information may be information that is updated dynamically in a timely manner, such as real-time geographic location, real-time order information, real-time user behavior operations, etc., so that the mini program can provide instant services in a more targeted manner to cater to user situations.

[0060] In one or more embodiments of this specification, it is mentioned above that the designated application can control the authorized permissions. For example, after the pre-authorization, before the current user enters the corresponding mini program from the entrance in the centralized scene page, the corresponding mini program is not allowed to directly obtain the current user's specified information. It can only be obtained after entering. In addition, if the current user enters the corresponding mini program from other channels other than the centralized scene page, the authorized permissions may not be allowed. In this case, the pre-authorization performed by the user is actually strictly for the centralized scene page, which helps to protect the user's information security.

[0061] pass Figure 1 The method takes into account that if the current user enters the centralized scenario page of the specified application (as the parent application), there is a great probability that the user will enter the mini-program through different mini-program entrances provided by the page, and may also exit the mini-program and return to the page, and then enter other mini-programs, thereby using multiple different mini-programs in a short period of time. Therefore, when the user initially arrives at the centralized scenario page, it can represent multiple mini-programs and uniformly request pre-authorization from the user, instead of requesting authorization from the user separately in the mini-programs that the user may further enter from here, thereby greatly reducing the disturbance of the authorization pop-up window to the user; not only that, if the user agrees to the pre-authorization, such authorization The authority can be conveniently controlled by the parent application to prevent the abuse of mini-programs. Only when the user actually enters a mini-program from the centralized scene page can the mini-program actually use the authorized permissions. If the user has not yet entered the mini-program, even if the user has performed pre-authorization, the mini-program may still not be allowed to use the authorized permissions. Moreover, the validity of the pre-authorization can also be converged to the jurisdiction of the centralized scene page, so that if the user enters the mini-program from channels other than the centralized scene page, the mini-program may still not be allowed to use the authorized permissions; thereby improving security. Therefore, the above solution can effectively improve user experience and take into account security.

[0062] based on Figure 1 This specification also provides some specific implementation plans and extension plans of the method, which will be described below.

[0063] One or more embodiments of this specification provide a flowchart of a solution for obtaining user specified information in a mini program, such as Figure 2 shown.

[0064] Figure 2 The process in includes the following steps:

[0065] S202: After the pre-authorization, determine the corresponding authorization data generated, the corresponding authorization data including the user identifier of the current user, the centralized scene identifier corresponding to the centralized scene page, and the correspondence between the authorized status information.

[0066] The corresponding mini-program identifier may also be added to the above correspondence, so that the above correspondence can be maintained for a particular mini-program.

[0067] By default, pre-authorization is for all mini-programs in the centralized scene corresponding to the centralized scene identifier. However, users may not trust all these mini-programs, and may even dislike a certain mini-program. Therefore, separate management methods can be provided to users. For example, after pre-authorization, the authorization setting options corresponding to multiple mini-programs can be displayed to the current user. If the current user cancels the authorization for any of the multiple mini-programs by operating the authorization setting options, it is determined that the pre-authorization is invalid for any of the mini-programs (for example, the identifier of any of the mini-programs can be removed from the above correspondence), so that no mini-program is allowed to directly obtain the current user's specified information based on the authorization data, while other mini-programs that have not been canceled in the multiple mini-programs are still allowed to directly obtain the current user's specified information based on the authorization data; similarly, users can also make the above settings in advance.

[0068] S204: When entering a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scene page, the centralized scene identifier corresponding to the centralized scene page is sent to the server for verification by the server.

[0069] The server can verify whether the corresponding centralized scene identifier received matches the generated authorization data, and determine whether to allow the corresponding mini program to directly obtain the user's information based on the matching result. For example, if it is determined through matching that the centralized scene identifier contained in a certain generated authorization data is the corresponding centralized scene identifier currently received by the server, and both parties also match in aspects such as user identification and authorization scope, then the corresponding mini program can be allowed to directly obtain the user's information, otherwise it can be rejected. The verification action can also be performed on the user terminal. In this case, the authorization data can be saved on the user terminal in advance, so that efficient verification can be achieved.

[0070] The verification here can also be simplified, for example, only verify whether the centralized scene corresponding to the received centralized scene identifier supports pre-authorization. If it does, the verification passes. This can more efficiently determine whether the current mini program entry channel is the channel targeted by this solution (i.e., entering from a specific centralized scene).

[0071] S206: When entering a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, an authorization request is initiated through the corresponding mini-program without a corresponding pop-up window.

[0072] In one or more embodiments of this specification, the authorization request initiated by the corresponding applet is for the specified application, which is imperceptible to the current user and does not disturb the user. When implementing this solution, you can first intercept the authorization request pop-up window of the corresponding applet, and then decide whether the intercepted pop-up window needs to be displayed to the user based on whether the pre-authorization has been performed. In this way, when implementing this solution, you can try to avoid the corresponding applet from cooperating with the improvement, and only need to specify the application itself for improvement, which is more friendly to the service providers of multiple applet.

[0073] S208: In response to the authorization request, locally or at the server end, based on the user identification and authorization status information included in the generated authorization data, verify whether the user corresponding to the authorization request has been authorized, and whether the authorization scope of the requested authorization is reasonable.

[0074] The verification in steps S204 and S208 may be performed together or at different times.

[0075] S210: If yes, the user's information is sent to the corresponding applet.

[0076] If the verification fails, the corresponding mini program pop-up window can be allowed to request authorization from the current user.

[0077] pass Figure 2 The solution can maintain the corresponding relationship reflecting the pre-authorization status and perform corresponding verification when the user actually enters the mini program, so as to precisely and reliably control whether the user may be disturbed by authorization requests in the mini program in the future. At the same time, if necessary, the user can also take the initiative to control it in advance to improve his or her own experience.

[0078] According to the above description, one or more embodiments of this specification also provide a flowchart of a small program quick authorization processing solution in an application scenario, as well as some page effect diagrams of the solution, see respectively Figure 3 , Figure 4 .

[0079] In this solution, one or more centralized scenarios can be determined in advance in the app (i.e., the designated application mentioned above), such as "xx store", "consumption circle", etc., which are connected to multiple merchant mini-programs. A corresponding distinguishing identifier can be set for each centralized scenario, for example, it is called a centralized scenario channel identifier, such as A, B, C, etc. When the user jumps from the centralized scenario home page to the mini-program in it, the current client can carry the corresponding scenario channel identifier to the server.

[0080] Initially, assuming that the user has not authorized yet, when entering the centralized scene, the app can call up a quick authorization management pop-up window to request the user to perform unified pre-authorization in this scene. If the user agrees to authorize, a quick authorization relationship can be created for the user as the above authorization data, which is saved locally or on the server. An exemplary quick authorization relationship includes: scene channel identifier (A / B / C) + user identifier + activation status + pop-up-free authorization scope. If the user refuses to authorize, the pop-up window is closed.

[0081] After the user agrees to the authorization, if the user has not yet jumped from the centralized scene to a merchant mini program, the merchant mini program still cannot obtain the user data corresponding to the corresponding permission (i.e. the specified information mentioned above). In other words, for the merchant mini program, the permission has not actually taken effect, which helps reduce the risk of merchants abusing user data.

[0082] When a user jumps from a centralized scenario to a merchant mini program, the merchant mini program initiates an authorization request. The system verifies whether the user has enabled quick authorization and whether the authorization scope includes the merchant's request scope. If the verification is successful, the user data corresponding to the permission is directly returned. Otherwise, the authorization request pop-up window can be evoked for the user to confirm the authorization.

[0083] exist Figure 4In the effect diagram, some information is blocked without affecting understanding. From left to right, you can see 4 sub-pictures. In the first picture, the user is on the main page of a centralized scene called "xx Store". The quick authorization management pop-up window has been evoked on this page. From the pop-up window, it can be seen that the required scope of authority includes the user's geographic location and preferential information in the app (the intended use of this information is also prompted). The user can click the "Allow" button to agree to the authorization. If the user agrees to the authorization, the page in the second picture will be displayed. On this page, the user is also prompted to perform quick authorization management as needed, for example, cancel the quick authorization at any time through the quick authorization switch. The third picture shows by way of example what access path can reach the quick authorization management page, and the fourth picture shows the quick authorization switch in the quick authorization management page. Of course, according to the previous description, if necessary, you can also add quick authorization switches for each mini program in a more fine-grained manner in the quick authorization management page.

[0084] pass Figure 3 The solution, since the number of centralized scenarios is limited and controllable, can avoid the problem of excessively high technical costs of data expansion, and the solution is more practical.

[0085] In one or more embodiments of this specification, in the case of pre-authorization, the user actually hands over more security responsibility to the designated application. In order to enable the user to more clearly perceive and deal with risks, one or more embodiments of this specification also provide a flow chart of a risk defense solution that cooperates with pre-authorization, see Figure 5 .

[0086] Figure 5 The process in includes the following steps:

[0087] S502: After directly acquiring the specified information of the current user according to the authorization data in the corresponding mini-program, a business opportunity node involving the specified information of the current user in the corresponding mini-program is detected.

[0088] After the corresponding mini program obtains the specified information of the current user, it will execute one or more time-sequenced business processes based on the user's immediate operations and the mini program's own business logic. The business process currently being executed can be divided into multiple business timing nodes according to the set method (for example, according to the different business data used, according to the different functions called, according to the different business types of returned data, according to the interactive user interface elements, etc.).

[0089] This solution mainly focuses on the business opportunity nodes related to the specified information. For example, the business opportunity nodes that directly or indirectly use the specified information can be detected and filtered out as relevant business opportunity nodes.

[0090] S504: Generate a user information risk link according to the time sequence relationship of each of the business opportunity nodes.

[0091] In one or more embodiments of the present specification, each business opportunity node is arranged and linked according to a time sequence relationship (wherein a link branch may appear so as to cover business behaviors within a longer time range in the corresponding mini program), and a visual and as concise as possible user information risk link is generated. The business behaviors for the specified information reflected in the user information risk link may contain potential risks, so it can be given to the user as a reference so that the user can more clearly understand where the specified information is used.

[0092] Considering that in actual applications, the professional level of the user information risk link may vary, so it may not be fully understood by all users. Therefore, intelligent analysis can be used to help generate a user information risk link that is more user-friendly. For example, assuming that the above unified authorization request carries the expected use of the current user's specified information (such as Figure 4 The first subgraph in the figure belongs to this case), then each detected business opportunity node can be matched and analyzed with the expected purpose to obtain the purpose deviation result. According to the purpose deviation result and the temporal relationship of each business opportunity node, a user information risk link is generated.

[0093] S506: In response to a request from the current user, display the information risk link to the current user.

[0094] The information risk link may not be displayed by default, and the user may actively call out the information risk link if he / she wants to view it. Alternatively, the information risk link may be actively displayed to the user when a risk is automatically detected.

[0095] S508: Receive the risk blocking point indicated by the current user in the information risk link.

[0096] It not only provides users with a means to discover risks, but also provides flexible and timely solutions to deal with risks. Users can select business opportunity nodes in the information risk chain that they think are at risk, or that the system indicates are at risk, as risk blocking points.

[0097] S510: Block the path after the risk blocking point in the information risk link, and roll back the business involved in the information risk link to the risk blocking point or before it in the corresponding mini-program.

[0098] In order to more reliably protect user privacy and implement business rollback with less impact, one or more embodiments of this specification also provide a flow chart of a user protection solution for a mini-program by a parent application, see Figure 6 .

[0099] Figure 6 The process in includes the following steps:

[0100] S602: Before directly obtaining the specified information of the current user in the corresponding mini-program according to the authorization data, a corresponding disguised user is generated for the current user through the designated application according to the business characteristics of the corresponding mini-program and the specified original information of the current user, and disguised feature information of the disguised user is generated.

[0101] In one or more embodiments of the present specification, the designated application will remap the real account of the current user and generate a new account to represent the current user, which becomes a disguised user. In addition, according to the business characteristics of the corresponding applet, and under the condition that the corresponding applet is basically sufficient to conduct business normally, the designated original information of the current user is disguised as much as possible to obtain the disguised characteristic information of the disguised user. For example, for a food delivery applet, which requires the user's delivery address at a minimum, other information can be blurred as much as possible or confused with other users, and the delivery address can also be slightly blurred (for example, blurred to the floor instead of the specific house number; for another example, blurred to a dynamic address pre-accepted by a user tens of meters or even more than ten meters away from the actual delivery address; etc.), thereby achieving disguise.

[0102] S604: When directly obtaining the specified information of the current user in the corresponding mini program according to the authorization data, specifically, directly obtaining the disguised feature information of the disguised user in the corresponding mini program according to the authorization data, for performing the business of the corresponding mini program for the current user.

[0103] In this way, for the designated application, the corresponding applet can complete the business normally, and avoid making it accurately grasp the user information. In addition, assuming that the above-mentioned risk blocking and rollback operation is supported, the designated application can generate more than two disguised users for the same applet of the same user, and generate disguised feature information for them separately and separately. At the beginning, only one of the disguised users is provided to the applet. If the disguised user has a risk blocking rollback, the remaining business logic after the rollback is copied or replaced to the remaining disguised user, so that the applet can continue to complete the business for the remaining disguised user. Of course, in this scheme, the remaining disguised user can also be similarly replaced with a real user. For example, after determining that there is a high probability of no risk, the real user can be enabled for the applet. In this way, the disguised user can help the real user to test the risk and more reliably establish a business path with a high probability of no risk, so that the applet can conduct business, thereby more effectively protecting user privacy and security.

[0104] Based on the same idea, one or more embodiments of this specification also provide devices and apparatuses corresponding to the above methods, such as Figure 7 , Figure 8 The apparatus and device can accordingly execute the above method and related optional solutions.

[0105] Figure 7 A schematic diagram of a structure of a mini-program authorization processing device provided for one or more embodiments of this specification, the device comprising:

[0106] Centralized scene entry module 702, enters the centralized scene page of the specified application, and the centralized scene page has respective entrances to multiple mini-programs connected to the specified application;

[0107] A unified authorization request module 704 initiates a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page;

[0108] The authorization data triggering module 706 triggers the generation of corresponding authorization data if the current user agrees to perform pre-authorization in response to the unified authorization request;

[0109] The mini-program quick processing module 708, after the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, then in the corresponding mini-program, the specified information of the current user is directly obtained according to the authorization data, so as to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0110] Optionally, the authorization data trigger module 706, after the pre-authorization, does not allow the corresponding mini-program to directly obtain the specified information of the current user before the current user enters the corresponding mini-program from the entrance in the centralized scene page.

[0111] Optionally, the unified authorization request module 704 pops up a window to the current user in the centralized scenario page, and initiates a unified authorization request corresponding to the multiple mini-programs through the pop-up window, so that the current user performs authorization by interacting with the pop-up window;

[0112] The mini-program shortcut processing module 708 directly obtains the user's information according to the authorization data in the corresponding mini-program, without popping up a window in the corresponding mini-program to request authorization from the current user to obtain the specified information of the current user.

[0113] Optionally, when the mini-program shortcut processing module 708 enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scene page, the mini-program shortcut processing module 708 sends the centralized scene identifier corresponding to the centralized scene page to the server, so that the server can verify whether the corresponding centralized scene identifier received matches the generated authorization data, and determine whether to allow the corresponding mini-program to directly obtain the user's information based on the matching result.

[0114] Optionally, the corresponding authorization data includes a user identifier of the current user, a centralized scene identifier corresponding to the centralized scene page, and a correspondence between the authorized state information;

[0115] The mini-program shortcut processing module 708, when entering a corresponding mini-program among the plurality of mini-programs from the entrance in the centralized scenario page, initiates an authorization request through the corresponding mini-program without responding to a pop-up window;

[0116] In response to the authorization request, locally or at the server end, verify whether the user corresponding to the authorization request has been authorized and whether the authorization scope of the requested authorization is reasonable according to the user identification and authorization status information included in the generated authorization data;

[0117] If so, the user's information is sent to the corresponding applet.

[0118] Optionally, the authorization data triggering module 706 displays authorization setting options corresponding to the multiple mini-programs to the current user after the pre-authorization;

[0119] If the current user cancels authorization for any of the multiple mini-programs by operating the authorization setting option, it is determined that the pre-authorization is invalid for any of the mini-programs, so that any of the mini-programs is not allowed to directly obtain the specified information of the current user based on the authorization data, while other mini-programs among the multiple mini-programs that have not been canceled are still allowed to directly obtain the specified information of the current user based on the authorization data.

[0120] Optionally, the mini-program shortcut processing module 708, after directly acquiring the specified information of the current user according to the authorization data in the corresponding mini-program, detects a service opportunity node related to the specified information of the current user in the corresponding mini-program;

[0121] Generating a user information risk link according to the time sequence relationship of each of the business opportunity nodes;

[0122] In response to a request from the current user, the information risk link is displayed to the current user.

[0123] Optionally, the unified authorization request carries the expected use of the designated information of the current user;

[0124] The mini-program quick processing module 708 matches and analyzes each of the business opportunity nodes with the expected purpose to obtain a purpose deviation result;

[0125] A user information risk link is generated according to the usage deviation result and the timing relationship between the business opportunity nodes.

[0126] Optionally, the mini-program shortcut processing module 708 receives a risk blocking point indicated by the current user in the information risk link after presenting the information risk link to the current user;

[0127] The path in the information risk link that is after the risk blocking point is blocked, and the business involved in the information risk link is rolled back to the risk blocking point or before it in the corresponding mini-program.

[0128] Optionally, the mini-program shortcut processing module 708 generates a corresponding disguised user for the current user and disguised feature information of the disguised user through the designated application according to the service characteristics of the corresponding mini-program and the designated original information of the current user before directly acquiring the designated information of the current user in the corresponding mini-program according to the authorization data;

[0129] The directly acquiring the specified information of the current user according to the authorization data in the corresponding applet specifically includes:

[0130] In the corresponding mini-program, the disguised feature information of the disguised user is directly obtained according to the authorization data, so as to perform the service of the corresponding mini-program for the current user.

[0131] Figure 8 A schematic diagram of a small program authorization processing device provided for one or more embodiments of this specification, the device comprising:

[0132] at least one processor; and,

[0133] a memory communicatively connected to the at least one processor; wherein,

[0134] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0135] Enter the centralized scene page of the specified application, which has entrances to multiple mini-programs connected to the specified application;

[0136] Initiate a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page;

[0137] If the current user agrees to perform pre-authorization in response to the unified authorization request, the generation of corresponding authorization data is triggered;

[0138] After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the corresponding mini-program directly obtains the specified information of the current user according to the authorization data, and uses it to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0139] Based on the same idea, one or more embodiments of this specification further provide a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as follows:

[0140] Enter the centralized scene page of the specified application, which has entrances to multiple mini-programs connected to the specified application;

[0141] Initiate a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page;

[0142] If the current user agrees to perform pre-authorization in response to the unified authorization request, the generation of corresponding authorization data is triggered;

[0143] After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the corresponding mini-program directly obtains the specified information of the current user according to the authorization data, and uses it to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

[0144] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0145] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0146] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0147] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0148] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may be in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0149] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0150] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0151] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0152] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0153] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0154] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0155] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0156] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media including storage devices.

[0157] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0158] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0159] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A method for processing mini program authorization, comprising: Enter the centralized scene page of the specified application, which has entrances to multiple mini-programs connected to the specified application; Initiate a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page; If the current user agrees to perform pre-authorization in response to the unified authorization request, the generation of corresponding authorization data is triggered; After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the corresponding mini-program directly obtains the specified information of the current user according to the authorization data, and uses it to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

2. The method according to claim 1, after the pre-authorization, the method further comprises: Before the current user enters the corresponding mini-program from the entrance in the centralized scenario page, the corresponding mini-program is not allowed to directly obtain the specified information of the current user.

3. The method according to claim 1, wherein in the centralized scenario page, initiating a unified authorization request corresponding to the multiple mini-programs to the current user specifically comprises: In the centralized scenario page, a pop-up window is displayed to the current user, and a unified authorization request corresponding to the multiple mini-programs is initiated through the pop-up window, so that the current user performs authorization by interacting with the pop-up window; The directly acquiring the specified information of the current user according to the authorization data in the corresponding applet specifically includes: In the corresponding mini-program, the user's information is directly obtained according to the authorization data, without popping up a window in the corresponding mini-program to request authorization from the current user to obtain the specified information of the current user.

4. The method according to claim 1, wherein entering a corresponding mini-program among the plurality of mini-programs from the entrance in the centralized scenario page specifically comprises: When entering a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scene page, the centralized scene identifier corresponding to the centralized scene page is sent to the server, so that the server can verify whether the corresponding centralized scene identifier received matches the generated authorization data, and determine whether to allow the corresponding mini-program to directly obtain the user's information based on the matching result.

5. The method according to claim 4, wherein the corresponding authorization data includes a user ID of the current user, a centralized scene ID corresponding to the centralized scene page, and a correspondence between the authorized state information; The obtaining, in the corresponding applet according to the authorization data, the specified information of the current user specifically includes: When entering a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, initiating an authorization request through the corresponding mini-program without responding to a pop-up window; In response to the authorization request, locally or at the server end, verify whether the user corresponding to the authorization request has been authorized and whether the authorization scope of the requested authorization is reasonable according to the user identification and authorization status information included in the generated authorization data; If so, the user's information is sent to the corresponding applet.

6. The method according to claim 1, after the pre-authorization, the method further comprises: Displaying authorization setting options corresponding to the multiple mini-programs to the current user; If the current user cancels authorization for any of the multiple mini-programs by operating the authorization setting option, it is determined that the pre-authorization is invalid for any of the mini-programs, so that any of the mini-programs is not allowed to directly obtain the specified information of the current user based on the authorization data, while other mini-programs among the multiple mini-programs that have not been canceled are still allowed to directly obtain the specified information of the current user based on the authorization data.

7. The method according to claim 1, after directly acquiring the specified information of the current user according to the authorization data in the corresponding applet, the method further comprises: Detecting a business opportunity node involving the specified information of the current user in the corresponding mini-program; Generating a user information risk link according to the time sequence relationship of each of the business opportunity nodes; In response to a request from the current user, the information risk link is displayed to the current user.

8. The method according to claim 7, wherein the unified authorization request carries the expected use of the specified information of the current user; Generating a user information risk link according to the timing relationship of each of the business opportunity nodes specifically includes: Matching and analyzing each of the business opportunity nodes with the expected use to obtain a use deviation result; A user information risk link is generated according to the usage deviation result and the timing relationship between the business opportunity nodes.

9. The method according to claim 7, after presenting the information risk link to the current user, the method further comprises: Receiving a risk blocking point indicated by the current user in the information risk link; The path in the information risk link that is after the risk blocking point is blocked, and the business involved in the information risk link is rolled back to the risk blocking point or before it in the corresponding mini-program.

10. The method according to claim 1 or 7, before directly acquiring the specified information of the current user in the corresponding applet according to the authorization data, the method further comprises: Generate a corresponding disguised user for the current user and generate disguised feature information of the disguised user through the designated application according to the service characteristics of the corresponding applet and the designated original information of the current user; The directly acquiring the specified information of the current user according to the authorization data in the corresponding applet specifically includes: In the corresponding mini-program, the disguised feature information of the disguised user is directly obtained according to the authorization data, so as to perform the service of the corresponding mini-program for the current user.

11. A mini program authorization processing device, comprising: A centralized scene entry module is used to enter the centralized scene page of a specified application. The centralized scene page has respective entrances to multiple mini-programs connected to the specified application. A unified authorization request module, in the centralized scenario page, initiates a unified authorization request corresponding to the multiple mini-programs to the current user; An authorization data triggering module triggers the generation of corresponding authorization data if the current user agrees to perform pre-authorization in response to the unified authorization request; The mini-program quick processing module, after the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, then in the corresponding mini-program, the specified information of the current user is directly obtained according to the authorization data, so as to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

12. In the device as described in claim 11, the authorization data trigger module, after the pre-authorization, does not allow the corresponding mini-program to directly obtain the specified information of the current user before the current user enters the corresponding mini-program from the entrance in the centralized scene page.

13. The device according to claim 11, wherein the unified authorization request module pops up a window to the current user in the centralized scenario page, and initiates a unified authorization request corresponding to the multiple mini-programs through the pop-up window, so that the current user performs authorization by interacting with the pop-up window; The mini-program shortcut processing module directly obtains the user's information based on the authorization data in the corresponding mini-program, without popping up a window in the corresponding mini-program to request authorization from the current user to obtain the specified information of the current user.

14. In the device as described in claim 11, the mini-program shortcut processing module, when entering a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scene page, sends the centralized scene identifier corresponding to the centralized scene page to the server, so that the server can verify whether the corresponding centralized scene identifier received matches the generated authorization data, and determine whether to allow the corresponding mini-program to directly obtain the user's information based on the matching result.

15. The device according to claim 14, wherein the corresponding authorization data includes a user ID of the current user, a centralized scene ID corresponding to the centralized scene page, and a correspondence between the authorized state information; The mini-program quick processing module, when entering a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, initiates an authorization request through the corresponding mini-program without responding to a pop-up window; In response to the authorization request, locally or at the server end, verify whether the user corresponding to the authorization request has been authorized and whether the authorization scope of the requested authorization is reasonable according to the user identification and authorization status information included in the generated authorization data; If so, the user's information is sent to the corresponding applet.

16. The device according to claim 11, wherein the authorization data triggering module displays authorization setting options corresponding to the plurality of mini-programs to the current user after the pre-authorization; If the current user cancels authorization for any of the multiple mini-programs by operating the authorization setting option, it is determined that the pre-authorization is invalid for any of the mini-programs, so that any of the mini-programs is not allowed to directly obtain the specified information of the current user based on the authorization data, while other mini-programs among the multiple mini-programs that have not been canceled are still allowed to directly obtain the specified information of the current user based on the authorization data.

17. The device of claim 11, wherein the mini-program quick processing module detects a service opportunity node related to the specified information of the current user in the corresponding mini-program after directly acquiring the specified information of the current user according to the authorization data in the corresponding mini-program; Generating a user information risk link according to the time sequence relationship of each of the business opportunity nodes; In response to a request from the current user, the information risk link is displayed to the current user.

18. The apparatus of claim 17, wherein the unified authorization request carries an expected use of the specified information of the current user; The mini-program quick processing module matches and analyzes each of the business opportunity nodes with the expected use to obtain a use deviation result; A user information risk link is generated according to the usage deviation result and the timing relationship between the business opportunity nodes.

19. The device according to claim 17, wherein the mini-program quick processing module receives a risk blocking point indicated by the current user in the information risk link after the information risk link is displayed to the current user; The path in the information risk link that is after the risk blocking point is blocked, and the business involved in the information risk link is rolled back to the risk blocking point or before it in the corresponding mini-program.

20. The device according to claim 11 or 17, wherein the mini-program shortcut processing module generates a corresponding disguised user for the current user through the designated application according to the service characteristics of the corresponding mini-program and the designated original information of the current user, and generates disguised feature information of the disguised user before directly acquiring the designated information of the current user in the corresponding mini-program according to the authorization data; The directly acquiring the specified information of the current user according to the authorization data in the corresponding applet specifically includes: In the corresponding mini-program, the disguised feature information of the disguised user is directly obtained according to the authorization data, so as to perform the service of the corresponding mini-program for the current user.

21. A mini program authorization processing device, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: Enter the centralized scene page of the specified application, which has entrances to multiple mini-programs connected to the specified application; Initiate a unified authorization request corresponding to the multiple mini-programs to the current user in the centralized scenario page; If the current user agrees to perform pre-authorization in response to the unified authorization request, the generation of corresponding authorization data is triggered; After the pre-authorization, if the current user enters a corresponding mini-program among the multiple mini-programs from the entrance in the centralized scenario page, the corresponding mini-program directly obtains the specified information of the current user according to the authorization data, and uses it to perform the business of the corresponding mini-program for the current user, without requesting authorization from the current user in the corresponding mini-program.

Citation Information

Patent Citations

  • Small program login method, server and electronic equipment

    CN111245825A

  • Authorized login method and system for wechat applet to jump to H5 application

    CN116702106A

  • H5 page authorization method and H5 page authorization device

    CN117240677A

  • Business handling method, system and device based on mobile terminal information issuing

    CN117580002A

  • Systems and methods for controlling third-party access of a protected data resource

    US20210075782A1

Cited By

  • Mini‑program authorization processing

    WO2026037143A1