Applet login method, device and related equipment

Abstract

The present disclosure provides a kind of applet login method, device, electronic equipment and computer readable storage medium, the applet login method can include: in the first application program of target account login, the login page of first applet is displayed, login page includes request login control;In response to the trigger operation for request login control, jump to second applet;At least one associated account associated with target account is shown by second applet, and at least one associated account includes target associated account;In response to the trigger operation for target associated account, back to first applet, to log in first applet by target associated account.The present disclosure embodiment can use the associated account of the login account of first application program to log in the first applet in the first application program, so as to view the relevant information corresponding to the associated account in the first applet.

Description

Technical Field

[0001] This disclosure relates to the field of computer and internet technology, and in particular to a method, apparatus, electronic device, computer-readable storage medium, and computer program product for logging in to a mini-program. Background Technology

[0002] A mini program is an application that can be used without downloading or installing it. It realizes the dream of "applications at your fingertips". Users can find and open mini programs by scanning a QR code or searching. It also embodies the concept of "use and go", so users don't have to worry about installing too many applications.

[0003] In related technologies, users can use a mini-program simply by searching for or clicking on the mini-program they need in the "Mini-program" entry of an application (APP), or by scanning the mini-program code through an application (APP).

[0004] However, when opening a mini-program through an application, the system typically obtains the login account of that application and then uses that account to complete the login or registration process for the mini-program. For example, if logging into or registering for a mini-program within a chat application, the relevant technology directly obtains the chat application's login account and then uses that account to complete the login or registration for the mini-program.

[0005] The above login or registration methods are too simplistic and cannot meet the diverse needs of users. Summary of the Invention

[0006] The purpose of this disclosure is to provide a method, device, electronic device, computer-readable storage medium, and computer program product for logging into a mini-program, which can use an account associated with the login account of a first application to complete the login of a first mini-program, thus enriching the login methods of mini-programs and better meeting the diverse needs of users.

[0007] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0008] This disclosure provides a method for logging into a mini-program, comprising: displaying a login page of a first mini-program in a first application for logging into a target account, the login page including a login request control; redirecting to a second mini-program in response to a triggering operation of the login request control; displaying at least one associated account associated with the target account through the second mini-program, the at least one associated account including a target associated account; and redirecting back to the first mini-program in response to a triggering operation of the target associated account, so as to log into the first mini-program through the target associated account.

[0009] This disclosure provides a mini-program login device, including: a login page display module, a second mini-program redirection module, an associated account display module, and a bounce module.

[0010] The login page display module is used to display the login page of the first mini-program in the first application where the target account is logged in. The login page includes a login request control. The second mini-program redirection module is used to redirect to the second mini-program in response to a trigger operation on the login request control. The associated account display module is used to display at least one associated account associated with the target account through the second mini-program. The at least one associated account includes the target associated account. The jumpback module is used to log in to the first mini-program with the target associated account in response to a trigger operation on the target associated account.

[0011] In some embodiments, the second mini-program jump module includes: a second mini-program opening sub-module, a second mini-program login sub-module, and an associated account display sub-module.

[0012] The second mini-program opening sub-module is used to open the second mini-program in the first application in response to the triggered operation of the login request control; the second mini-program login sub-module is used to log in to the second mini-program through the target account; the associated account display sub-module is used to determine the at least one associated account associated with the target account through the second mini-program, so as to display the at least one associated account.

[0013] In some embodiments, the target account is an account registered by the target object in the first application, and the second applet is used to display the registered account in the second application; wherein, the associated account display submodule includes: a registered account determination unit and an associated account determination unit.

[0014] The registered account determination unit is used to determine at least one account registered by the target object in the second application through the second mini-program; the associated account determination unit is used to identify at least one account registered by the target object in the second application as at least one associated account associated with the target account.

[0015] In some embodiments, the second application is a team communication application that provides communication services to different communication teams; wherein, the registration account determination unit includes: a communication team determination subunit, a communication account determination subunit, and a registration account determination subunit.

[0016] The communication team determination subunit is used to determine, through the second applet, at least one communication team to which the target object belongs in the team communication application; the communication account determination subunit is used to determine the communication account of the target object in each communication team; and the registration account determination subunit is used to use the communication account of the target object in each communication team as at least one account registered by the target object in the second application.

[0017] In some embodiments, the bounce module includes: an authorization confirmation page display submodule and an authorization submodule.

[0018] The authorization confirmation page display submodule is used to respond to a triggered operation for the target associated account and display an authorization confirmation page in the second mini-program. The authorization confirmation page is used to confirm the authorization for logging into the first mini-program using the target associated account. The authorization submodule is used to jump back to the first mini-program after obtaining authorization confirmation through the authorization confirmation page and log into the first mini-program with the target associated account.

[0019] In some embodiments, the bounce module includes: an authorization code acquisition submodule, an authorization code sending submodule, and an account information acquisition submodule.

[0020] The authorization code acquisition submodule is used to obtain the authorization code of the target associated account for the first mini-program in response to a trigger operation for the target associated account; the authorization code sending submodule is used to send the authorization code to the first mini-program during the process of jumping back to the first mini-program; the account information acquisition submodule is used for the first mini-program to obtain the account information of the target associated account based on the authorization code, so as to log in to the first mini-program through the account information of the target associated account.

[0021] In some embodiments, the first mini-program is used to display data in a target functional module of the second application, and the authorization code is an authorization code jointly issued by the target associated account and the target functional module to the first mini-program; wherein, the second mini-program jump module includes: a jump sub-module and a functional module identifier sending sub-module; the authorization code acquisition sub-module includes: an authorization code acquisition unit; the account information acquisition sub-module includes: an account information acquisition unit, and the mini-program login device further includes a functional module data acquisition module.

[0022] The jump module is used to jump to the second mini-program in response to a trigger operation of the login request control; the function module identifier sending sub-module is used to send the function module identifier of the target function module to the second mini-program during the jump to the second mini-program; the authorization code acquisition unit is used to obtain the authorization code jointly issued by the target associated account and the target function module to the first mini-program based on the function module identifier by the second mini-program; the account information acquisition unit is used to obtain the account information of the target associated account based on the authorization code, so as to log in to the first mini-program through the account information of the target associated account; the function module data acquisition module is used by the first mini-program to obtain the data corresponding to the target associated account in the target function module through the authorization code.

[0023] In some embodiments, the functional module data acquisition unit includes: a data request subunit, a data existence judgment subunit, and a data non-existence judgment subunit.

[0024] The data request subunit is configured to have the first mini-program request data from the background device corresponding to the second application based on the authorization code, wherein the background device provides storage services for the second application; the data existence determination subunit is configured to have the first mini-program receive the data of the target associated account in the target functional module from the background device if the target associated account has data in the target functional module; and the data non-existence determination subunit is configured to have the first mini-program not receive the data of the target associated account in the target functional module from the background device if the target associated account does not have data in the target functional module.

[0025] In some embodiments, the second application is a team communication application that provides communication services to different communication teams. The first mini-program is used to display the data of the target communication team in the target functional module in the second application. The functional module data acquisition unit includes: a background request sub-unit, a communication account judgment first sub-unit, and a communication account judgment second sub-unit.

[0026] The background request subunit is configured to have the first mini-program request data of the target associated account in the target functional module from the background device corresponding to the team communication application based on the authorization code, wherein the background device provides storage services for the team communication application; the communication account determination first subunit is configured to have the first mini-program receive data of the target associated account in the target functional module from the background device if the target associated account is a communication account in the target communication team; the communication account determination second subunit is configured to have the first mini-program not receive data of the target associated account in the target functional module from the background device if the target associated account is not a communication account in the target communication team.

[0027] In some embodiments, the first applet is used to display data corresponding to the target communication team in the team communication application; wherein, the account information acquisition submodule includes: a temporary call credential acquisition unit and a joint request unit.

[0028] The temporary call credential acquisition unit is used by the first mini-program to request a temporary call credential from the backend device corresponding to the second mini-program based on the team identifier of the target communication team, so as to determine that the target communication team has the right to request data from the backend device; the joint request unit is used by the first mini-program to request the account information of the target associated account from the backend device based on the temporary call credential and the authorization code.

[0029] In some embodiments, the account information of the target associated account includes sensitive account information and non-sensitive account information. The first applet includes a sensitive information security display interface provided by a second application. The sensitive information security display interface is used to protect the sensitive information in the target associated account. The account information acquisition submodule includes a non-sensitive information acquisition unit and a sensitive information acquisition unit.

[0030] The non-sensitive information acquisition unit is used by the first mini-program to request non-sensitive information of the target associated account from the backend device corresponding to the second mini-program based on the authorization code; the sensitive information acquisition unit is used by the first mini-program to send the authorization code to the sensitive information security display interface so that the sensitive information security display interface can securely display the sensitive information of the target associated account, thereby preventing the first mini-program from acquiring the sensitive information of the target associated account.

[0031] This disclosure provides an electronic device comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the mini-program login method described above.

[0032] This disclosure provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the mini-program login method as described in any of the preceding embodiments.

[0033] This disclosure provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned applet login method.

[0034] The mini-program login method, device, electronic device, and computer-readable storage medium provided in this disclosure can log in to the first mini-program in the first application through the associated account (i.e., the target associated account) of the login account (i.e., the target account) of the first application. This allows users to view the information corresponding to the target associated account in the first mini-program of the first application, realizing information exchange between different accounts, enriching the login methods of mini-programs, and better meeting the diverse needs of users.

[0035] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this disclosure. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0037] Figure 1 A schematic diagram of an exemplary system architecture that can be applied to the mini-program login method or mini-program login device in the embodiments of this disclosure is shown.

[0038] Figure 2 This is a flowchart illustrating a method for logging into a mini-program according to an exemplary embodiment.

[0039] Figure 3 This is a product illustration corresponding to a mini-program login method according to an exemplary embodiment.

[0040] Figure 4 This is a product illustration corresponding to a mini-program login method according to an exemplary embodiment.

[0041] Figure 5 This is a flowchart illustrating a method for logging into a mini-program according to an exemplary embodiment.

[0042] Figure 6 This is a flowchart illustrating a method for logging into a first mini-program through a target associated account, according to an exemplary embodiment.

[0043] Figure 7 This is a timing diagram illustrating a WeChat Mini Program login method according to an exemplary embodiment.

[0044] Figure 8 This is a timing diagram illustrating a data request method according to an exemplary embodiment.

[0045] Figure 9 This is a product illustration corresponding to a mini-program login method according to an exemplary embodiment.

[0046] Figure 10 This is a block diagram illustrating a mini-program login device according to an exemplary embodiment.

[0047] Figure 11 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. Detailed Implementation

[0048] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0049] The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more specific details omitted, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0050] The accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus omitting repeated descriptions of them. Some block diagrams shown in the drawings do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0051] The flowchart shown in the accompanying drawings is merely illustrative and does not necessarily include all content and steps, nor does it require execution in the described order. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0052] In this specification, the terms “a,” “an,” “the,” “the,” and “at least one” are used to indicate the presence of one or more elements / components / etc.; the terms “comprising,” “including,” and “having” are used to indicate an open-ended inclusion and to mean that there may be other elements / components / etc. in addition to the listed elements / components / etc.; the terms “first,” “second,” and “third,” etc., are used only as markings and are not a limitation on the number of objects.

[0053] To better understand the above-mentioned objectives, features and advantages of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0054] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0055] Figure 1 A schematic diagram of an exemplary system architecture that can be applied to the mini-program login method or mini-program login device in the embodiments of this disclosure is shown.

[0056] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0057] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, desktop computers, wearable devices, virtual reality devices, smart home devices, etc.

[0058] Terminal devices 101, 102, and 103 may, for example, display the login page of a first mini-program in a first application for login to the target account, the login page including a login request control; terminal devices 101, 102, and 103 may, for example, jump to a second mini-program in response to a triggering operation on the login request control; terminal devices 101, 102, and 103 may, for example, display at least one associated account associated with the target account through the second mini-program, the at least one associated account including the target associated account; terminal devices 101, 102, and 103 may, for example, log in to the first mini-program with the target associated account in response to a triggering operation on the target associated account.

[0059] Server 105 can be a server that provides various services, such as a backend management server that supports the devices operated by users using terminal devices 101, 102, and 103. The backend management server can analyze and process received requests and other data, and feed the processing results back to the terminal devices.

[0060] A server can be a standalone physical server, a server cluster or a distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. This disclosure does not impose any restrictions on this.

[0061] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Server 105 can be a single physical server or a combination of multiple servers. Depending on actual needs, it can have any number of terminal devices, networks, and servers.

[0062] Before explaining this application, it is necessary to explain some of the terms used in this application.

[0063] Applications: Applications are a collective term for programs that users choose to install. They typically include driver processes, image viewer processes, decompression software processes, and other general-purpose software. Alternatively, as the name suggests, applications are software programs developed to facilitate communication between users and computing devices.

[0064] Mini programs are applications that can be used without downloading or installing them. They realize the dream of "applications at your fingertips," allowing users to open the application simply by scanning a QR code or searching for it.

[0065] Figure 2 This is a flowchart illustrating a WeChat Mini Program login method according to an exemplary embodiment. The method provided in this disclosure can be executed by any electronic device with computing power; for example, the method can be executed by the aforementioned... Figure 1 The terminal device in the embodiments can be used to execute the commands, or the server and the terminal device can be used together. In the following embodiments, the terminal device is used as the execution subject for illustration, but this disclosure is not limited to this.

[0066] Reference Figure 2 The mini-program login method provided in this embodiment may include the following steps.

[0067] Step S202: Display the login page of the first mini-program in the first application where the target account is logged in. The login page includes a login request control.

[0068] The first application can be any kind of application, such as a chat application APP, a shopping application APP, a news application APP, a business application APP, a browser application APP, or a payment application APP, and this disclosure does not impose any restrictions on it.

[0069] The target account can be the login account in the first application.

[0070] The first mini-program can be a mini-program opened in the first application, and this application does not restrict the function of the first mini-program.

[0071] In some embodiments, the login page of the first mini-program can be either a login page or a registration page before login; this disclosure does not impose any restrictions on this.

[0072] The login request control (which can also be a registration request control) facilitates the target user's decision to log in to the first mini-program using an account in the second application. In some embodiments, the login request control may refer to, for example... Figure 3The jump button corresponding to "Second Application Login" on the login page 301 shown can also refer to a voice control that receives voice commands (not shown in the figure). This disclosure does not limit the form of the login request control.

[0073] Step S204: In response to the triggered operation of the login request control, jump to the second mini-program.

[0074] The second mini-program can refer to a mini-program used to display the associated accounts of the target account.

[0075] In some embodiments, when a login request control is triggered in the first mini-program (e.g., by clicking), Figure 3 After clicking the button corresponding to "Second Application Login" on the login page 301 shown, you can directly jump from the first mini-program to the second mini-program (for example, jump to the account list display page 302 of the second mini-program).

[0076] Step S206: Display at least one associated account linked to the target account through the second mini-program, wherein the at least one associated account includes the target associated account.

[0077] The target account and the at least one associated account mentioned above can be login accounts of the target object in different applications. The target account and the at least one associated account mentioned above can also be login accounts of the target object in different teams in the same application. This disclosure does not limit the relationship between the target account and the at least one associated account.

[0078] The aforementioned at least one associated account can be an account registered in the same application or an account registered in different applications; this disclosure does not impose any restrictions on this. For example, the aforementioned at least one associated account can include an account associated with the target account in a second application, or an account associated with the target account in a third application; this disclosure does not impose any restrictions on this. Specifically, the aforementioned at least one associated account can include a first associated account and a second associated account, wherein the first associated account can be a login account in the second application, and the second associated account can be a login account in the third application; of course, both the first associated account and the second associated account can be login accounts in the second application.

[0079] The target account can be a login account registered using target registration information, which may include information such as mobile phone number, ID card number, name, address, and organization. At least one associated account linked to the target account can be an account in a second application (or a third application) that shares some (or all) of the target account's registration information. For example, it could be an account whose registered mobile phone number is the same as the target account's registered mobile phone number, or an account whose registered ID card number is the same as the target account's registered ID card number, and so on. This disclosure does not impose any restrictions in this regard.

[0080] In some embodiments, when navigating from the first mini-program to the second mini-program, the second mini-program can... Figure 3 The account list display page 302 shows at least one associated account (such as account 1, account 2, and account 3) in the second application (and / or the third application) that is associated with the target account. The at least one associated account may include the target associated account (e.g., account 2).

[0081] Step S208: In response to the triggered operation for the target associated account, log in to the first mini program with the target associated account.

[0082] In some embodiments, when a second applet receives a request for a target associated account (such as...) Figure 3 After the trigger action of account 2), it can automatically jump from the second mini-program to the first mini-program (for example, from...). Figure 3 The second mini-program's account list display page 302 redirects to the first mini-program's login completion page 303, and the user logs into the first mini-program using the target associated account, thus completing the login process for the first mini-program.

[0083] In some other embodiments, after responding to a triggering operation for the target associated account, an authorization confirmation page is displayed in the second mini-program, which is used to confirm the authorization for logging into the first mini-program using the target associated account; after obtaining authorization confirmation through the authorization confirmation page, the user is redirected back to the first mini-program.

[0084] For example, such as Figure 4As shown, after the login page 401 is displayed in the first mini-program of the first application, a login request control (such as the "Second Application Login" button) in the login page 401 can be triggered. In response to the triggering operation of the login request control, the user can jump from the login page 401 of the first mini-program to the account list display page 402 of the second mini-program to display at least one associated account of the target account. After the target associated account in at least one associated account is triggered, the second mini-program will jump from the account list display page 402 to the authorization confirmation page 403 in the second mini-program to obtain authorization confirmation for logging into the first mini-program using the target associated account. After obtaining authorization confirmation through the authorization confirmation page 403, the user can jump directly from the authorization confirmation page 403 of the second mini-program to the login completion page 404 of the first mini-program.

[0085] The mini-program login method provided in this embodiment allows users to log in to the first mini-program in the first application through the associated account (i.e., the target associated account) of the login account (i.e., the login account of the first application). This enables users to view the information corresponding to the associated account in the first mini-program of the first application, thus realizing information exchange between different accounts.

[0086] Furthermore, with the technical solution provided in this embodiment, the business side does not need to upgrade the version number, and can achieve unified management of login compatibility between the old and new versions of the second application and new functions of the first application. In addition, the mini-program login method of this application is not limited by plugin API calls or plugin component usage. Different first mini-programs and different users can all jump to the unified login confirmation page of the second mini-program, which is simple to interact with. In addition, the user interface (UI) can be uniformly customized through the second mini-program.

[0087] Figure 5 This is a flowchart illustrating a WeChat Mini Program login method according to an exemplary embodiment. (Refer to...) Figure 5 The mini-program login method provided in this embodiment may include the following steps.

[0088] Step S502: Display the login page of the first mini-program in the first application where the target account is logged in. The login page includes a login request control.

[0089] In some embodiments, the target account may be an account registered by the target object in the first application. The target object may register the target account in the first application using unique identification information such as a mobile phone number or ID card.

[0090] Step S504: In response to the triggered operation of the login request control, open the second applet in the first application.

[0091] In some embodiments, the first mini-program can be used to display application data in the second application (i.e., the first mini-program can be a business-type mini-program developed by the developer), and the second mini-program can be used to display the account in the second application. The second application and the first application can be different applications.

[0092] Assuming the first application is an application that enables communication between objects, and the second application is a team communication application (e.g., an application for internal enterprise communication), then the first applet can be an applet that can display and manipulate functional data (e.g., business data) of a team (e.g., an enterprise) in the second application, and the second applet can be an applet that can display login accounts in the second application for selection. This disclosure limits these steps.

[0093] Step S506: Log in to the second mini-program using the target account.

[0094] In some embodiments, upon triggering an operation on the login request control, the user can be directly redirected to the second mini-program and log in to the second mini-program using the login account of the first application (i.e., the target account).

[0095] Step S508: Determine at least one account registered by the target object in the second application through the second applet.

[0096] In some embodiments, the second applet can determine at least one account registered by the target object in the second application. For example, the second applet can request at least one account registered by the target object in the second application from the background device corresponding to the second application, wherein the background device corresponding to the second application can be used to provide storage and computing services to the second application, for example, the background device can be used to store registered account information in the second application.

[0097] In some embodiments, the second mini-program may, for example, determine at least one associated account registered by the target object in the second application through the registered mobile phone number corresponding to the target account. The second mini-program may also, for example, determine at least one account registered by the target object in the second application through the registered ID number corresponding to the target account. This disclosure does not limit this.

[0098] It should be understood that when a second mini-program uses an ID card number or mobile phone number to identify at least one account registered by a target object in the second application, prior authorization is required. For example, the target object's permission can be obtained when registering the target account, or when logging into the first mini-program. This disclosure does not impose any restrictions on this.

[0099] In some embodiments, the second application may be a team communication application that can provide communication services to different communication teams (e.g., different enterprises). Therefore, determining at least one account registered by the target object in the second application via the second applet may include the following steps: determining, via the second applet, that the target object belongs to at least one communication team in the team communication application (e.g., in the second application, the target object may belong to either the first or the second communication team; this disclosure does not impose any restrictions); determining the target object's communication accounts in each communication team; and using the target object's communication accounts in each communication team as at least one account registered by the target object in the second application.

[0100] Step S510: At least one account registered by the target object in the second application is designated as at least one associated account associated with the target account.

[0101] Step S512: In response to the triggered operation for the target associated account, jump back to the first mini-program to log in to the first mini-program through the target associated account.

[0102] The mini-program login method provided in this embodiment allows users to log in to the first mini-program in the first application through the associated account (i.e., the target associated account) associated with the login account (i.e., the target account) of the first application. This enables users to view the information corresponding to the associated account in the first mini-program within the first application, thus achieving information exchange between different accounts.

[0103] Figure 6 This is a flowchart illustrating a method for logging into a first mini-program via a target associated account, according to an exemplary embodiment. (Refer to...) Figure 6 The method for logging into a first mini-program through a target associated account provided in this embodiment may include the following steps.

[0104] In some embodiments, the first mini-program can be used to display application data in the second application.

[0105] In some embodiments, upon triggering an operation on the login request control, a direct jump can be made from the first mini-program to the second mini-program. The first mini-program sends request parameters to the second mini-program so that the second mini-program can determine an authorization code for the first mini-program based on the request parameters. The request parameters may include the identifier of the first mini-program, etc., and those skilled in the art can set the request parameters according to actual needs.

[0106] For example, suppose the first mini-program is a business mini-program in the first application, and the second mini-program is a mini-program developed to display the account of the second application (which could be a team communication application); when the target object triggers the login request control in the business mini-program, the first mini-program will jump to the second mini-program through a jump function and send request parameters for the target account to the second mini-program.

[0107] In step S602, in response to the triggered operation for the target associated account, the second mini-program obtains the authorization code of the target associated account for the first mini-program.

[0108] In some embodiments, after a user jumps from the first mini-program to the second mini-program, the second mini-program obtains the identity information of the target object corresponding to the target account and displays at least one associated account associated with the target account, which may include the target associated account.

[0109] In some embodiments, when the target associated account is triggered (e.g., selected), the second mini-program will obtain the authorization code of the target associated account for the first mini-program based on the request parameters sent by the first mini-program.

[0110] In step S604, during the process of jumping back to the first mini-program, the second mini-program sends the authorization code to the first mini-program.

[0111] In some embodiments, during the process of jumping back to the first mini-program, the second mini-program sends an authorization code to the first mini-program. For example, the second mini-program returns to the first mini-program via a jump function, carrying the aforementioned authorization code.

[0112] In step S606, the first mini-program obtains the account information of the target associated account based on the authorization code, so as to log in to the first mini-program using the account information of the target associated account.

[0113] In some embodiments, the first mini-program may request account information of the target associated account, such as avatar information and name information, from the background device of the second application based on the authorization code mentioned above.

[0114] In some embodiments, the account information of the target associated account may include sensitive account information (such as name information, department information, etc., which can be set according to actual needs by those skilled in the art) and non-sensitive account information (such as profile picture information). The first mini-program may include a secure display interface for sensitive information, which can be used to protect the sensitive information in the target associated account. This secure display interface for sensitive information may be provided by a second application, through which sensitive information can be securely displayed in the first mini-program, preventing non-second applications such as the first mini-program from accessing the sensitive information.

[0115] Therefore, the process of the first mini-program obtaining the account information of the target associated account based on the authorization code may include the following steps: the first mini-program requests non-sensitive information of the target associated account from the backend device corresponding to the second mini-program based on the authorization code; the first mini-program sends the authorization code to the sensitive information security display interface so that the sensitive information security display interface can securely display the sensitive information of the target associated account, thereby preventing the first mini-program from obtaining the sensitive information of the target associated account.

[0116] In some embodiments, the first mini-program can be used to display data corresponding to a target communication team in a team communication application (a second application). Therefore, the first mini-program obtaining account information of the target associated account based on the authorization code may include: the first mini-program requesting a temporary access credential from the backend device corresponding to the second mini-program based on the team identifier of the target communication team, to determine that the target communication team has the right to request data from the backend device; and the first mini-program requesting account information of the target associated account from the backend device based on the temporary access credential and the authorization code.

[0117] In some embodiments, the first mini-program can be used to display data in a target functional module of the second application. Therefore, redirecting to the second mini-program in response to a trigger operation on a login request control can include: redirecting to the second mini-program in response to a trigger operation on a login request control; during the redirection to the second mini-program, the first mini-program sends the functional module identifier of the target functional module to the second mini-program. Furthermore, the first mini-program obtaining the account information of the target associated account based on the authorization code, so as to log in to the first mini-program using the account information of the target associated account, can include: obtaining the authorization code of the target associated account and the target functional module for the first mini-program based on the functional module identifier; obtaining the account information of the target associated account based on the authorization code, so as to log in to the first mini-program using the account information of the target associated account; and obtaining the data corresponding to the target associated account in the target functional module using the authorization code.

[0118] Therefore, obtaining the data corresponding to the target associated account in the target functional module through the authorization code can include: the first mini-program requests the data in the target functional module from the background device corresponding to the second application based on the authorization code, and the background device provides storage services for the second application; if the target associated account has data in the target functional module, the first mini-program receives the data of the target associated account in the target functional module from the background device; if the target associated account does not have data in the target functional module, the first mini-program will not receive the data of the target associated account in the target functional module from the background device, and a blank page may be displayed in the first mini-program when the first mini-program does not receive the data in the target functional module.

[0119] In some embodiments, the second application may be a team communication application that provides communication services to different communication teams. The first mini-program is used to display the data of the target communication team in the target functional module within the second application. Obtaining the data corresponding to the target associated account in the target functional module via the authorization code may include: the first mini-program requesting the data of the target associated account in the target functional module from the backend device corresponding to the team communication application based on the authorization code; the backend device provides storage services for the team communication application; if the target associated account is a communication account within the target communication team, the first mini-program receives the data of the target associated account in the target functional module from the backend device; if the target associated account is not a communication account within the target communication team, the first mini-program does not receive the data of the target associated account in the target functional module from the backend device.

[0120] Figure 7 This is a timing diagram illustrating a WeChat Mini Program login method according to an exemplary embodiment.

[0121] exist Figure 7 In the illustrated embodiment, the first mini-program can be a business mini-program 701 opened in the first application, the second mini-program 702 can be a mini-program developed to display accounts in the second application (in this embodiment, the second application is described as a team communication application), and the background device 703 can be a device (such as a server) that provides background services for the second mini-program 702 and the second application. The second application can be a team communication application.

[0122] The first mini-program can be used to display application data in the target functional module (such as the salary function module in a corporate team) of the target communication team in the second application, while the second mini-program can be used to display accounts in the second application.

[0123] refer to Figure 7 As shown in the timing diagram, the above-mentioned mini-program login method may include the following steps.

[0124] 1. Display the login page of the business mini-program in the first application where the target object logs in through the target account. The login page includes a login request control.

[0125] 2. After responding to the trigger operation of the login request control, you can jump directly from the business mini-program to the second mini-program, and the business mini-program will send request parameters to the second mini-program.

[0126] The aforementioned request parameters may include the identifier of the business mini-program, the identifier of the second mini-program to be opened, the identifier of the target functional module in the second application to be accessed, etc. Those skilled in the art can set the request parameters according to actual needs.

[0127] For example, suppose the business mini-program is a business mini-program within the first application, and the second mini-program is a mini-program developed to display the account of the second application; when the target object triggers a login request control in the business mini-program, such as Figure 7 The business mini-program shown will redirect to the second mini-program via a jump function (such as wx.navigateToMinProgram) and send request parameters for the target account to the second mini-program.

[0128] 3. The second mini-program obtains and displays the target object's accounts in different teams within the second application, or obtains the target object's accounts in different teams within the second application and displays the teams to which it belongs for selection.

[0129] 4. In response to a trigger operation by a specific account on the display page, the second mini-program obtains the authorization code jointly issued by the selected account and the target function module to the business mini-program.

[0130] 5. In response to a triggering action by a specific account on the display page, the second mini-program can send an authorization code to the business mini-program during the process of jumping back from the second mini-program to the business mini-program.

[0131] In some embodiments, during the jump back to the business mini-program, the second mini-program sends an authorization code to the business mini-program. For example, the second mini-program returns to the business mini-program via a jump function (e.g., wx.navigateBackMinProgram) carrying the aforementioned authorization code.

[0132] 6. The business mini-program receives data.

[0133] The business mini-program can receive the authorization code passed by the second application mini-program when it returns from the second application mini-program on page onShow (which is also a process of switching from the background to the foreground).

[0134] 7. The business mini-program requests the target associated account information from the backend device of the second application based on the authorization code.

[0135] In some embodiments, the business mini-program can request account information of the target associated account, such as profile picture information and name information, from the backend device of the second application based on the authorization code (or auth_code) mentioned above.

[0136] In some embodiments, the account information of the target associated account may include sensitive account information (such as name information, department information, etc., which can be set according to actual needs by those skilled in the art) and non-sensitive account information (such as profile picture information, team name information). The business mini-program may include a sensitive information secure display interface, which (e.g., the address book display control ww-open-data (a control) provided by the second application) is used to protect the sensitive information in the target associated account. The aforementioned address book display control ww-open-data may be provided by the second application. Through this sensitive information secure display interface, sensitive information from the second application can be displayed in the business mini-program to prevent such sensitive information from being obtained by programs outside the second application.

[0137] Therefore, after consuming the auth_code, the backend device of the second application returns ordinary information, such as the avatar (for sensitive information authorization) and team name. However, the name and department name are not given to the business mini-program in plaintext to prevent the business mini-program from collecting user information. Instead, it returns parameters such as corid (team identifier), openid (user identifier), and type to the business mini-program, which are then displayed through the address book display control ww-open-data.

[0138] Therefore, in some embodiments, the process of a business mini-program obtaining account information of a target associated account based on an authorization code may include the following steps: the business mini-program requests non-sensitive information of the target associated account from the backend device corresponding to the second mini-program based on the authorization code; the business mini-program sends the authorization code to the sensitive information security display interface so that the sensitive information security display interface can securely display the sensitive information of the target associated account, thereby preventing the business mini-program from obtaining the sensitive information of the target associated account.

[0139] In summary, after obtaining the login auth_code, the business mini-program can exchange it for user identity through the API provided by the second application backend.

[0140] Meanwhile, to ensure that the auth_code can only be consumed by the preset team, this embodiment provides the following example, taking a certain enterprise as the preset team. Figure 8 The data request method shown.

[0141] Suppose a business mini-program can be used to display data corresponding to a target company in a team communication application. Then, the process by which the business mini-program obtains the target associated account information based on the authorization code can include: the business mini-program requesting a temporary access token (provider_access_token) from the backend device corresponding to the second mini-program based on the target company's corporate identifier (corpid) to confirm that the target company has the right to request data from the backend device; and the business mini-program requesting the target associated account information from the backend device of the second application based on the temporary access token (provider_access_token) and the authorization code (auth_code).

[0142] The above method uses corid (enterprise identifier ID) and provider_secret (APPID) to ensure that auth_code can only be consumed by the current enterprise.

[0143] In this disclosure, a business mini-program is used to log in to a second application account based on a first application.

[0144] Provide a second mini-program. The business mini-program will redirect to the second mini-program, allowing the user to complete the team identity authorization. Then, the user will be redirected back to the business mini-program and successfully logged in, where information such as avatar, name, team name, and department name can be displayed.

[0145] This disclosure enables users to log in using the identity of the second application while on the first application, and to display user information.

[0146] Through the above Figure 7 and Figure 8 The product interface corresponding to the mini-program login method shown in the embodiment can be as follows: Figure 9As shown: When the login page 901 of the business mini-program is displayed in the first application where the target account is logged in, the login request control (e.g., the "Second Application Login" button) in the login page 901 can be triggered; in response to the triggering operation of the login request control, the user can jump from the business mini-program to the account list display page 902 of the second mini-program to display at least one associated account of the target account in the second application (the displayed account can be the associated account itself or the company to which the associated account belongs, such as XXX Co., Ltd., XXX Technology Co., Ltd., and XX Group); when the target associated account (e.g., XXXX Technology Co., Ltd.) in at least one associated account is triggered, the second mini-program will jump from the account list display page 902 to the authorization confirmation page 903 in the second mini-program to obtain authorization confirmation for logging into the business mini-program using the target associated account; after obtaining authorization confirmation through the authorization confirmation page 903, the user can jump directly from the authorization confirmation page of the second mini-program to the login completion page 904 of the business mini-program.

[0147] The above embodiments provide a second mini-program, allowing business mini-programs to be opened and used within the first application using the identity of the second application. For example, in a group chat between the second and first applications, mini-program cards shared by users in the second application can also be opened and used in the first application, without being restricted to the second application, resulting in a better and more convenient experience.

[0148] Figure 10 This is a block diagram illustrating a mini-program login device according to an exemplary embodiment. (Refer to...) Figure 10 The mini-program login device 1000 provided in this embodiment may include: a login page display module 1001, a second mini-program jump module 1002, an associated account display module 1003, and a jumpback module 1004.

[0149] The login page display module 1001 can be used to display the login page of the first mini-program in the first application for login of the target account. The login page includes a login request control. The second mini-program jump module 1002 can be used to jump to the second mini-program in response to a trigger operation on the login request control. The associated account display module 1003 can be used to display at least one associated account associated with the target account through the second mini-program. The at least one associated account includes the target associated account. The jumpback module 1004 can be used to log in to the first mini-program with the target associated account in response to a trigger operation on the target associated account.

[0150] In some embodiments, the second mini-program jump module 1002 may include: a second mini-program opening sub-module, a second mini-program login sub-module, and an associated account display sub-module.

[0151] The second mini-program opening sub-module can be used to open the second mini-program in the first application in response to the triggering operation of the login request control; the second mini-program login sub-module can be used to log in to the second mini-program through the target account; and the associated account display sub-module can be used to identify at least one associated account associated with the target account through the second mini-program so as to display at least one associated account.

[0152] In some embodiments, the target account is an account registered by the target object in the first application, and the second applet is used to display the registered account in the second application; wherein, the associated account display submodule includes: a registered account determination unit and an associated account determination unit.

[0153] The registered account determination unit can be used to determine at least one account registered by the target object in the second application through the second mini-program; the associated account determination unit can be used to identify at least one account registered by the target object in the second application as at least one associated account associated with the target account.

[0154] In some embodiments, the second application is a team communication application that provides communication services to different communication teams; wherein, the registration account determination unit may include: a communication team determination subunit, a communication account determination subunit, and a registration account determination subunit.

[0155] The communication team determination subunit can be used to determine, through the second applet, at least one communication team to which the target object belongs in the team communication application; the communication account determination subunit can be used to determine the communication account of the target object in each communication team; and the registration account determination subunit can be used to use the communication account of the target object in each communication team as at least one account registered by the target object in the second application.

[0156] In some embodiments, the bounce module 1004 may include an authorization confirmation page display submodule and an authorization submodule.

[0157] The authorization confirmation page display submodule can be used to respond to a triggered operation for the target associated account and display an authorization confirmation page in the second mini-program. The authorization confirmation page is used to confirm the authorization for logging into the first mini-program using the target associated account. The authorization submodule can be used to jump back to the first mini-program after obtaining authorization confirmation through the authorization confirmation page and log into the first mini-program with the target associated account.

[0158] In some embodiments, the bounce module 1004 may include: an authorization code acquisition submodule, an authorization code sending submodule, and an account information acquisition submodule.

[0159] The authorization code acquisition submodule can be used to respond to a trigger operation for a target associated account, whereby the second mini-program obtains the authorization code of the target associated account for the first mini-program; the authorization code sending submodule can be used to send the authorization code to the first mini-program during the process of jumping back to the first mini-program; and the account information acquisition submodule can be used by the first mini-program to obtain the account information of the target associated account based on the authorization code, so as to log in to the first mini-program through the account information of the target associated account.

[0160] In some embodiments, the first mini-program is used to display data in a target functional module of the second application, and the authorization code is an authorization code jointly issued by the target associated account and the target functional module to the first mini-program; wherein, the second mini-program jump module includes: a jump sub-module and a functional module identifier sending sub-module; the authorization code acquisition sub-module includes: an authorization code acquisition unit; the account information acquisition sub-module includes: an account information acquisition unit, and the mini-program login device further includes a functional module data acquisition module.

[0161] The jump module is used to jump to the second mini-program in response to a trigger operation of the login request control; the function module identifier sending sub-module is used to send the function module identifier of the target function module to the second mini-program during the jump to the second mini-program; the authorization code acquisition unit is used to obtain the authorization code jointly issued by the target associated account and the target function module to the first mini-program based on the function module identifier by the second mini-program; the account information acquisition unit is used to obtain the account information of the target associated account based on the authorization code, so as to log in to the first mini-program through the account information of the target associated account; the function module data acquisition module is used by the first mini-program to obtain the data corresponding to the target associated account in the target function module through the authorization code.

[0162] In some embodiments, the functional module data acquisition unit may include: a data request subunit, a data existence judgment subunit, and a data non-existence judgment subunit.

[0163] The data request subunit can be used by the first mini-program to request data from the background device corresponding to the second application based on the authorization code, and the background device provides storage services for the second application; the data existence judgment subunit can be used to receive the data of the target associated account in the target functional module from the background device if the target associated account has data in the target functional module; the data non-existence judgment subunit can be used to receive the data of the target associated account in the target functional module from the background device if the target associated account does not have data in the target functional module.

[0164] In some embodiments, the second application is a team communication application that provides communication services to different communication teams. The first app is used to display the data of the target communication team in the target functional module in the second application. The functional module data acquisition unit may include: a background request subunit, a communication account judgment first subunit, and a communication account judgment second subunit.

[0165] The background request subunit is used by the first mini-program to request data of the target associated account in the target functional module from the background device corresponding to the team communication application based on the authorization code. The background device provides storage services for the team communication application. The communication account determination first subunit can be used to ensure that if the target associated account is a communication account in the target communication team, the first mini-program receives the data of the target associated account in the target functional module from the background device. The communication account determination second subunit can be used to ensure that if the target associated account is not a communication account in the target communication team, the first mini-program does not receive the data of the target associated account in the target functional module from the background device.

[0166] In some embodiments, the first applet is used to display data corresponding to the target communication team in the team communication application; wherein, the account information acquisition submodule may include: a temporary call credential acquisition unit and a joint request unit.

[0167] The temporary call credential acquisition unit can be used by the first mini-program to request a temporary call credential from the backend device corresponding to the second mini-program based on the team identifier of the target communication team, so as to determine that the target communication team has the right to request data from the backend device; the joint request unit can be used by the first mini-program to request the account information of the target associated account from the backend device based on the temporary call credential and the authorization code.

[0168] In some embodiments, the account information of the target associated account includes sensitive account information and non-sensitive account information. The first mini-program includes a sensitive information security display interface, which is used to protect the sensitive information in the target associated account. The account information acquisition sub-module may include a non-sensitive information acquisition unit and a sensitive information acquisition unit.

[0169] The non-sensitive information acquisition unit can be used by the first mini-program to request non-sensitive information of the target associated account from the backend device corresponding to the second mini-program based on the authorization code; the sensitive information acquisition unit can be used by the first mini-program to send the authorization code to the sensitive information security display interface so that the sensitive information security display interface can securely display the sensitive information of the target associated account, thereby preventing the first mini-program from acquiring the sensitive information of the target associated account.

[0170] Since the functions of the device 1000 have been described in detail in their corresponding method embodiments, they will not be repeated here.

[0171] The modules and / or sub-modules and / or units and / or sub-units described in the embodiments of this application can be implemented in software or hardware. The described modules and / or sub-modules and / or units and / or sub-units can also be located in a processor. The names of these modules and / or sub-modules and / or units and / or sub-units do not, in some cases, constitute a limitation on the module and / or sub-module and / or unit and / or sub-unit itself.

[0172] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0173] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this disclosure and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0174] Figure 11 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. It should be noted that... Figure 11 The illustrated electronic device 1100 is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0175] like Figure 11As shown, the electronic device 1100 includes a central processing unit (CPU) 1101, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1102 or a program loaded from a storage section 1108 into a random access memory (RAM) 1103. The RAM 1103 also stores various programs and data required for the operation of the electronic device 1100. The CPU 1101, ROM 1102, and RAM 1103 are interconnected via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0176] The following components are connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN card, modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to I / O interface 1105 as needed. Removable media 1111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1110 as needed so that computer programs read from them can be installed into storage section 1108 as needed.

[0177] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1109, and / or installed from removable medium 1111. When the computer program is executed by central processing unit (CPU) 1101, it performs the functions defined above in the system of this application.

[0178] It should be noted that the computer-readable storage medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable storage medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable storage medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0179] In another aspect, this application also provides a computer-readable storage medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The aforementioned computer-readable storage medium carries one or more programs that, when executed by the device, enable the device to perform the following functions: displaying a login page of a first mini-program in a first application for login of the target account, the login page including a login request control; redirecting to a second mini-program in response to a triggering operation on the login request control; displaying at least one associated account associated with the target account through the second mini-program, the at least one associated account including the target associated account; and redirecting back to the first mini-program in response to a triggering operation on the target associated account to log in to the first mini-program through the target associated account.

[0180] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional implementations of the above embodiments.

[0181] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions of the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or smart device, etc.) to execute the method according to the embodiments of this disclosure, for example... Figure 2 , Figure 5 ,or Figure 6 One or more of the steps shown.

[0182] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0183] It should be understood that this disclosure is not limited to the detailed structures, drawing arrangements or implementations shown herein; rather, this disclosure is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A method for logging into a mini-program, characterized in that, include: The login page of the first mini-program is displayed in the first application where the target account is logged in, and the login page includes a login request control; In response to the triggering operation of the login control requested, the user is redirected to the second mini-program; The second mini-program displays at least one associated account linked to the target account, the at least one associated account including the target associated account; In response to a triggered operation targeting the target associated account, log in to the first mini-program with the target associated account.

2. The method according to claim 1, characterized in that, Responding to the login request control by redirecting to the second mini-program includes: In response to the triggered operation of the login request control, the second mini-program is opened in the first application; Log in to the second mini-program using the target account; The second mini-program is used to determine at least one associated account linked to the target account, so that the at least one associated account can be displayed.

3. The method according to claim 2, characterized in that, The target account is the account registered by the target object in the first application, and the second mini-program is used to display the registered accounts in the second application; wherein, determining the at least one associated account associated with the target account through the second mini-program includes: The second mini-program is used to determine at least one account registered by the target object in the second application; At least one account registered by the target object in the second application shall be used as at least one associated account associated with the target account.

4. The method according to claim 3, characterized in that, The second application is a team communication application that provides communication services for different communication teams; wherein, determining at least one account registered by the target object in the second application through the second app includes: The second mini-program is used to determine at least one communication team to which the target object belongs in the team communication application; Determine the target object's communication account in the at least one communication team; The target object's communication account in the at least one communication team is used as at least one account registered by the target object in the second application.

5. The method according to claim 1, characterized in that, In response to a triggered operation targeting the target associated account, logging into the first mini-program with the target associated account includes: In response to a triggered operation targeting the target associated account, an authorization confirmation page is displayed in the second mini-program. The authorization confirmation page is used to confirm authorization for logging into the first mini-program using the target associated account. After obtaining authorization confirmation through the authorization confirmation page, the user is redirected back to the first mini-program and logs in to the first mini-program with the target associated account.

6. The method according to claim 1, characterized in that, In response to a triggered operation targeting the target associated account, logging into the first mini-program with the target associated account includes: In response to a triggered operation targeting the target associated account, the second mini-program obtains the authorization code of the target associated account for the first mini-program; The second mini-program sends the authorization code to the first mini-program; The first mini-program obtains the account information of the target associated account based on the authorization code, so as to log in to the first mini-program using the account information of the target associated account.

7. The method according to claim 6, characterized in that, The first mini-program is used to display data from a target functional module in the second application. The authorization code is a joint authorization code issued by the target associated account and the target functional module to the first mini-program. The process of redirecting to the second mini-program in response to a trigger operation on the login request control includes: In response to the triggering operation of the login request control, the user is redirected to the second mini-program; During the process of jumping to the second mini-program, the first mini-program sends the functional module identifier of the target functional module to the second mini-program; The second mini-program obtains the authorization code of the target associated account for the first mini-program, including: The second mini-program obtains the authorization code jointly issued by the target associated account and the target functional module to the first mini-program based on the functional module identifier; The first mini-program obtains the account information of the target associated account based on the authorization code, so as to log in to the first mini-program using the account information of the target associated account, including: The first mini-program obtains the account information of the target associated account based on the authorization code, so as to log in to the first mini-program using the account information of the target associated account; The method further includes: The first mini-program obtains the data corresponding to the target associated account in the target functional module based on the authorization code.

8. The method according to claim 6, characterized in that, The first mini-program is used to display data corresponding to a target communication team in a team communication application; wherein, the first mini-program obtains account information of the target associated account based on the authorization code, including: The first mini-program requests a temporary calling credential from the backend device corresponding to the second mini-program based on the team identifier of the target communication team, in order to determine that the target communication team has the right to request data from the backend device; The first mini-program requests the account information of the target associated account from the backend device based on the temporary call credential and the authorization code.

9. The method according to claim 6, characterized in that, The account information of the target associated account includes sensitive account information, and the first mini-program includes a sensitive information security display interface provided by the second application; wherein, the first mini-program obtains the account information of the target associated account according to the authorization code, including: The first mini-program sends the authorization code to the sensitive information security display interface so that the sensitive information security display interface can securely display the sensitive information of the target associated account.

10. A mini-program login device, characterized in that, include: A login page display module is used to display the login page of the first mini-program in the first application where the target account is logged in. The login page includes a login request control. The second mini-program redirection module is used to redirect to the second mini-program in response to the trigger operation of the login request control; The associated account display module is used to display at least one associated account associated with the target account through the second mini-program, wherein the at least one associated account includes the target associated account; The bounce module is used to bounce back to the first mini-program in response to a triggered operation for the target associated account, so as to log in to the first mini-program through the target associated account.

11. An electronic device, characterized in that, include: Memory; as well as A processor coupled to the memory, the processor being used to execute the applet login method as described in any one of claims 1-9 based on instructions stored in the memory.

12. A computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the applet login method as described in any one of claims 1-9.

13. A computer program product comprising computer instructions stored in a computer-readable storage medium, characterized in that, When the computer instructions are executed by the processor, they implement the method of any one of claims 1-9.

Images