WO2021208743A1 - 应用程序的账户绑定 - Google Patents

应用程序的账户绑定 Download PDF

Info

Publication number
WO2021208743A1
WO2021208743A1 PCT/CN2021/084618 CN2021084618W WO2021208743A1 WO 2021208743 A1 WO2021208743 A1 WO 2021208743A1 CN 2021084618 W CN2021084618 W CN 2021084618W WO 2021208743 A1 WO2021208743 A1 WO 2021208743A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
binding
service
account
token
Prior art date
Application number
PCT/CN2021/084618
Other languages
English (en)
French (fr)
Inventor
王坤
Original Assignee
支付宝(杭州)信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝(杭州)信息技术有限公司 filed Critical 支付宝(杭州)信息技术有限公司
Publication of WO2021208743A1 publication Critical patent/WO2021208743A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/101—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities
    • G06F21/1014—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities to tokens

Definitions

  • This document relates to the field of Internet technology, and in particular to an account binding method, device and system for application programs.
  • the change information of the business service is uploaded to the smart scene module under the operating system of the client, so that the change information of the business service is displayed in the corresponding smart scene card in the negative screen of the terminal, and when the user When the smart scene card is clicked, it can automatically jump to the corresponding interactive interface.
  • the account binding of the application program is mainly completed by the system server corresponding to the client, requiring the user to enter the account and password of the service providing application, or relying on the digital identity proxy acquisition capability provided by the manufacturer’s operating system. , In order to realize the account binding of the application.
  • the account binding method of the application program includes: obtaining a digital identity issued by the system server corresponding to the client for the target service fast application, the target service fast application includes the running of the fast application provided by the operating system of the client At least one business service quick application developed in the environment, the business service quick application corresponding to a preset business service in the service providing application; based on the digital identity, a binding is sent to the business server corresponding to the service providing application Relation query request; receiving the account binding token returned by the business server, where the account binding token is generated when the business server determines that the account binding is not performed for the digital identity
  • the service-providing application sends a one-key binding request carrying the account binding token to the business server, so that the business server is based on all
  • the account binding token binds the digital identity and the account of the service providing application.
  • One or more embodiments of this specification provide an account binding method for an application program.
  • the account binding method of the application program includes: receiving a binding relationship query request for a target service application, and the target service application includes at least one business service application developed in the operating environment of the application provided by the operating system of the client.
  • the business service application corresponds to a preset business service in the service provision application, and the binding relationship query request is based on the digital identity issued by the system server corresponding to the client for the target service application
  • the binding relationship query request if it is determined that account binding has not been performed for the digital identity, then the account binding token is returned to the target service application; the target service is received
  • the token binds the digital identity and the account of the service providing application.
  • the account binding device of the application includes: an identity acquisition module, which acquires the digital identity issued by the system server corresponding to the client for the target service application, the target service application includes the operating system of the client At least one business service quick application developed in the provided quick application operating environment, the business service quick application corresponding to a preset business service in the service providing application; a binding relationship query module, which is based on the digital identity
  • the business server corresponding to the service providing application sends a binding relationship query request; a binding token receiving module that receives the account binding token returned by the business server, where the account binding token is
  • the business server is generated when it is determined that account binding is not performed for the digital identity; the account binding trigger module detects the user’s one-key binding trigger operation, and then sends the service to all users through the service providing application.
  • the business server sends a one-click binding request carrying an account binding token, so that the business server binds the digital identity to the account of the service providing application based on the account binding token
  • the account binding device of the application program includes: a query request receiving module, which receives a binding relationship query request for a target service application, the target service application includes being developed in the operating environment of the application provided by the operating system of the client At least one business service application of the client, the business service application corresponds to a preset business service in the service provision application, and the binding relationship query request is based on the system server corresponding to the client for the target service Generated by the digital identity issued by the application; the binding token sending module, which responds to the binding relationship query request, and if it is determined that the account binding has not been performed for the digital identity, then it will send the service to the target The application returns the account binding token; the binding request receiving module receives the one-key binding request sent by the target service application through the service providing application, wherein the one-key binding request carries the account Binding token; an application account binding module, which, in response to the one-key binding request, binds the digital identity and the account of the
  • the account binding system of the application includes a client and a background server.
  • a service providing application is installed on the client, and the target service fast application is run in the fast application running environment provided by the operating system of the client.
  • the background server includes a business server corresponding to the service providing application, the target service express application includes at least one business service express application, and the business service express application corresponds to a preset business service in the service provision application .
  • the target service application obtains the digital identity issued by the system server corresponding to the client for the target service application; and, based on the digital identity, sends a binding to the business server corresponding to the service providing application Relation query request; and receiving the account binding token returned by the business server; and sending a one-key binding request carrying the account binding token to the business server through the service providing application.
  • the business server in response to the binding relationship query request, returns an account binding token to the target service application when it is determined that the account binding has not been performed for the digital identity; and, in response to all In the one-key binding request, the digital identity is bound to the account of the service providing application based on the account binding token.
  • One or more embodiments of this specification provide an account binding device for an application program, including a processor and a memory arranged to store computer-executable instructions.
  • the processor obtains the digital identity issued by the system server corresponding to the client for the target service application, the target service application includes the operating system of the client At least one business service quick application developed under the provided quick application operating environment, the business service quick application corresponding to a preset business service in the service providing application; based on the digital identity, the service corresponding to the application is provided
  • the business server sends a binding relationship query request; receives the account binding token returned by the business server, where the account binding token is the account that the business server determines that the digital identity has not executed the account Generated during binding; after detecting the user's one-key binding trigger operation, send a one-key binding request carrying an account binding token to the business server through the service providing application, so that all
  • the business server binds the digital identity and the account of the service providing application based on the account binding token.
  • One or more embodiments of this specification provide an account binding device for an application program, including a processor and a memory arranged to store computer-executable instructions.
  • the computer-executable instructions when executed, cause the processor to: receive a binding relationship query request for a target service application, the target service application includes being developed under the operating environment of the application provided by the operating system of the client At least one business service application of the client, the business service application corresponds to a preset business service in the service provision application, and the binding relationship query request is based on the system server corresponding to the client for the target service Generated by the digital identity issued by the application; in response to the binding relationship query request, if it is determined that the account binding has not been performed for the digital identity, then the account binding token is returned to the target service application; Receiving a one-key binding request sent by the target service fast application through the service providing application, the one-key binding request carrying the account binding token; in response to the one-key binding request, based on all The account binding token binds the digital identity and the account of
  • One or more embodiments of this specification provide a storage medium for storing computer-executable instructions.
  • the executable instruction When executed by the processor, it obtains the digital identity issued by the system server corresponding to the client for the target service fast application, and the target service fast application includes the fast service provided by the operating system of the client.
  • At least one business service quick application developed in the application operating environment, the business service quick application corresponding to a preset business service in the service providing application; based on the digital identity, sending to the business server corresponding to the service providing application Binding relationship query request; receiving the account binding token returned by the business server, where the account binding token is the account binding token used by the business server when determining that the account binding is not performed for the digital identity Generated; after detecting the user's one-key binding trigger operation, send a one-key binding request carrying an account binding token to the business server through the service providing application, so that the business server Bind the digital identity and the account of the service providing application based on the account binding token.
  • One or more embodiments of this specification provide a storage medium for storing computer-executable instructions.
  • the executable instruction is executed by the processor, a binding relationship query request for a target service application is received, and the target service application includes at least one service developed under the application running environment provided by the operating system of the client Service fast application, the business service fast application corresponds to a preset business service in the service provision application, and the binding relationship query request is issued based on the target service fast application by the system server corresponding to the client Generated by a digital identity; in response to the binding relationship query request, if it is determined that account binding has not been performed for the digital identity, return an account binding token to the target service application; receive the target The one-key binding request sent by the service fast application through the service providing application, wherein the one-key binding request carries the account binding token; in response to the one-key binding request, based on the account The binding token binds the digital identity and the account of the service providing application.
  • FIG. 1 is a schematic diagram of an application scenario of an application account binding system provided by one or more embodiments of this specification;
  • FIG. 2 is a schematic diagram of the first flow of an application account binding method provided in one or more embodiments of this specification;
  • FIG. 3 is a schematic diagram of the second flow of an application account binding method provided in one or more embodiments of this specification;
  • FIG. 4 is a schematic diagram of a third process of the method for binding an account of an application provided by one or more embodiments of this specification;
  • FIG. 5 is a schematic diagram of a multi-terminal interaction process involved in an application account binding method provided in one or more embodiments of this specification;
  • FIG. 6 is a schematic flowchart of an account binding method applied to an application on a business server provided by one or more embodiments of this specification;
  • FIG. 7 is a schematic diagram of the composition of the first module of the device for binding an account of an application provided by one or more embodiments of this specification;
  • FIG. 8 is a schematic diagram of the composition of the second module of the device for binding an account of an application provided in one or more embodiments of this specification;
  • Figure 9 is a schematic structural diagram of an account binding device for an application provided by one or more embodiments of this specification.
  • One or more embodiments of this specification provide a method, device, and system for binding an application program account.
  • a target service fast application For a target service fast application, a digital identity issued by the system server corresponding to the client is obtained, and based on the digital identity
  • the identifier sends a binding relationship query request to the business server, and receives the account binding token returned by the business server, and sends a one-key binding request to the business server through the service providing application based on the account binding token to trigger
  • the service providing application requests the business server to complete the one-click binding between the digital identity issued by the system server for the target service fast application and the account of the service providing application, so that the one-click is completed directly by the service providing application and the business server
  • Account binding can use the service to provide the login status of the application itself and the password-free login method, which simplifies the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the account of the application Universality
  • Fig. 1 is a schematic diagram of an application scenario of an application account binding system provided by one or more embodiments of this specification.
  • the system includes a back-end server and a client.
  • a service providing application is installed on the client, and the target service fast application is run in the fast application running environment provided by the operating system of the client, and the target service fast application corresponds to at least one preset business service in the service providing application;
  • the client can be a mobile terminal such as a smart phone or a tablet computer, and the client can also be a terminal device such as a personal computer.
  • the background server includes a business server corresponding to a service providing application and a system server corresponding to an operating system application.
  • the background server can be an independent server or a server cluster composed of multiple servers. Among them, the specific process of the account binding of the above application is:
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client for the target service fast application.
  • the target service fast application includes at least one developed in the fast application running environment provided by the client's operating system Business service quick application, which corresponds to the preset business service in the service provision application;
  • the target service fast application sends a binding relationship query request to the business server corresponding to the service providing application based on the acquired digital identity, and the binding relationship query request carries the digital identity;
  • the business server In response to the received binding relationship query request, the business server returns an account binding token to the target service application when it is determined that the account binding has not been performed for the above-mentioned digital identity.
  • the above-mentioned account binding token is used
  • the target service fast application requests the business server to perform account binding through the service providing application;
  • the target service express application After receiving the account binding token returned by the business server, the target service express application displays the one-key binding trigger control;
  • the target service fast application After the target service fast application detects the user's touch operation for the one-key binding trigger control, it sends the account binding token to the service providing application and triggers the service providing application to display the account binding page;
  • the service providing application After the service providing application detects the user's confirmation information for the account binding page, it sends a one-key binding request carrying the account binding token to the business server;
  • the business server In response to the received one-key binding request, the business server binds the digital identity of the target service fast application with the account of the service providing application based on the above account binding token;
  • the business server synchronizes the account binding relationship between the target service fast application and the service providing application to the system server, where the system server is the vendor server of the client.
  • the business server detects the business change information of at least one business service corresponding to the target service fast application in the service providing application, and uploads the business change information to the system server so that The system server triggers the client to display the business change information in the smart context interactive interface, that is, displays the business change information in the smart context card corresponding to the target service application under the client’s operating system, where the smart context card is located In the interactive interface of one screen on the terminal.
  • the target service fast application obtains the digital identity issued for it by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity. And receiving the account binding token returned by the business server, and based on the account binding token, send a one-click binding request to the business server through the service providing application to trigger the service provision application request.
  • the business server completes the system server as One-click binding between the digital identity issued by the target service fast application and the account of the service providing application, so that by directly completing the one-click account binding by the service providing application and the business server, the login of the application itself can be provided by the service
  • the login mode and password-free login method simplify the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer’s operating system, which improves the universality of application account binding.
  • Figure 2 is a schematic diagram of the first flow chart of the application account binding method provided by one or more embodiments of this specification.
  • the method in Figure 2 can be executed by the target service fast application in the client shown in Figure 1, such as As shown in Figure 2, the method includes at least the following steps:
  • the target service application includes at least one business service application, and the business service application corresponds to a preset service in the service provision application. service.
  • the above-mentioned target service fast application is a vendor fast application corresponding to at least one business service developed by the service provider corresponding to the service providing application in advance in the fast application operating environment provided by the client's operating system
  • the above service providing application is Refers to an application that provides users with at least one business service.
  • at least one business service in the application is provided in advance for the service, and the corresponding business service quick application is created in the quick application operating environment provided by the client's operating system
  • the business service quick application in the quick application running environment provided by the operating system of the client corresponding to at least one business service that needs to display business service change information on one screen of the terminal is determined as the target service quick application, the above-mentioned digital identity identifier It is OpenID.
  • the account binding activation control After detecting the trigger operation of the user's account binding activation control for the business service fast application that is not bound in the smart scenario alternative binding list in the client's operating system, it sends a digital identity acquisition request to the system server , Wherein the account binding activation control is used to trigger the process link of connecting the change information of at least one business service in the service providing application corresponding to the target service fast application to the smart context card under the operating system of the client.
  • the digital identity issued by the system server corresponding to the client for the target service application can also be directly obtained through the preset interface.
  • the business server After the business server receives the binding relationship query request, it queries whether the account binding has been performed for the digital identity, that is, the query between the digital identity OpenID issued by the system server for the target service fast application and the account of the service providing application Whether there is a binding relationship.
  • S206 Receive an account binding token returned by the business server, where the account binding token is generated by the business server when it determines that the digital identity corresponding to the target service fast application has not performed account binding.
  • the business server determines that the digital identity OpenID issued by the system server for the target service fast application does not have a binding relationship with the account of the service providing application, it generates an account binding token and binds the account to the token Send to the target service fast application.
  • the one-key binding trigger control After receiving the account binding token returned by the business server, the one-key binding trigger control is displayed; if the user's touch operation on the one-key binding trigger control is detected, the account binding token is sent to the service providing application , And trigger the service providing application to display the account binding page; after detecting the user's confirmation information for the account binding page, send a one-click binding request carrying the account binding token to the business server.
  • the target fast application can invoke the service provision application based on the scheme protocol to execute the one-click binding of the digital identity OpenID issued by the system server for the target service fast application and the account of the service provision application.
  • the business server detects the service change information of the business service corresponding to the started and bound business service fast application in the service; and synchronizes the change information to the intelligent scene interaction interface under the client's operating system (that is, the terminal is negative one screen) In the smart situation card corresponding to the business service quick application.
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login method simplifies the user’s operation steps and improves the user experience; and, it reduces the complexity of the account binding link, and improves the success rate of account binding; and, it eliminates the need to return to the vendor’s quick application.
  • the parameter transmission link avoids the security risks in the parameter return process; at the same time, it
  • the process of the business server returning the scheme protocol link containing the account binding token to the target service fast application may be intercepted, in order to improve the security of the account binding link of the application, first The business server encrypts the digital identity, and then transmits the account binding token in ciphertext to prevent the transmission of information from being hijacked.
  • receiving the account binding token returned by the business server specifically includes S2061, receiving the scheme protocol link containing the account binding token returned by the business server.
  • the account binding token is obtained by the business server after determining that the digital identity corresponding to the target service fast application has not performed account binding and encrypting the digital identity and the preset encryption factor.
  • the aforementioned preset encryption factor may include at least one of time stamp information and random character string.
  • the above S208 through the service providing application, sends a one-key binding request carrying the account binding token to the business server, so that the business
  • the server binds the digital identity of the target service fast application with the account of the service providing application based on the account binding token, which specifically includes: sending a key carrying the account binding token to the business server through the service providing application Binding request, so that the business server can verify the validity of the preset encryption factor in the acquired account binding token, and after the validity verification of the preset encryption factor is passed, the digital identity of the target service is quickly applied. Bind with the login account of the service provider application.
  • the business server When the business server is triggered by the service provision application to perform account one-click binding, the business server first verifies whether the preset encryption factor in the account binding token is valid, only when it is determined that the account binding token is credible , The account binding is performed, which can further confirm the security of the account one-key binding.
  • the above S208 after detecting the user's one-click binding trigger operation, sends the account binding token carrying the account binding token to the business server through the service providing application.
  • the one-click binding request specifically includes: after detecting the user's one-click binding trigger operation, triggering the service provider application to display the application account binding page; if the business server returns to the target service fast application containing the account binding token If the target service application detects the user’s touch operation for the one-key binding trigger control, it triggers the service provider application to open the account binding page based on the scheme protocol link containing the account binding token; After the user confirms the binding request for the application account binding page, the preset bind interface is called through the service providing application, and the one-key binding request carrying the account binding token is sent to the business server.
  • the account binding relationship for the target service fast application is synchronized to the system server.
  • the above-mentioned service-providing application calls the preset bind interface and sends the account binding token to the business server.
  • the one-click binding request specifically includes: calling the preset bind interface through the service providing application, and sending the one-click binding request carrying the account binding token to the business server, so that the business server can complete the account binding after the account binding is completed. Synchronize the account binding relationship for the target service fast application to the system server.
  • the account binding correspondence is uploaded to the system server corresponding to the client (ie, the vendor server).
  • the service provider application in order to simplify the user’s application login steps, the service provider application’s password-free login method can be used to quickly log in to the service provider application.
  • the bind interface which sends a one-key binding request carrying an account binding token to the business server, specifically including: if the service providing application is detected to be in an unlogged state, then the password-free login method based on the service providing application selected by the user ,
  • the login service provides an application.
  • the password-free login method can include any one of face-swiping login, fingerprint login, and open authorization login.
  • the preset bind interface is called through the service providing application, and the account binding token is sent to the business server. One-click binding request.
  • the account binding after the account binding is completed, in order to further improve the user experience, it can also automatically jump to the smart context information display page, as shown in Figure 4, in the above S208, after the user’s one-key binding trigger operation is detected .
  • the service providing application After sending the one-key binding request carrying the account binding token to the business server through the service providing application, it also includes:
  • the target service app executes the background operation, and the system process automatically switches to the manufacturer's negative screen, where the manufacturer's negative screen contains the service changes used to display the target service's quick application Informational smart situational cards.
  • FIG. 5 a schematic diagram of the multi-terminal interaction process in the account binding method of the application program is given, which specifically includes:
  • the target service fast application obtains a digital identity issued by the system server corresponding to the client for the target service fast application, and the target service fast application includes at least one business developed in the fast application running environment provided by the operating system of the client Quick service application, which corresponds to the preset business service in the service provision application;
  • the target service fast application sends a binding relationship query request to the business server corresponding to the service providing application based on the acquired digital identity, and the binding relationship query request carries the digital identity;
  • the business server determines whether there is a binding relationship between the digital identity issued by the system server for the target service application and the account of the service providing application;
  • the target service fast application After the target service fast application detects the user's touch operation on the one-key binding trigger control, it triggers the service providing application to open the account binding page based on the scheme protocol link containing the account binding token;
  • S511 The business server synchronizes the account binding relationship for the target service fast application to the system server;
  • S512 The business server sends the successful account binding result for the target service fast application to the service providing application;
  • S513 The service providing application sends the account binding successful result to the target service app, so that after the target service app receives the account binding successful result, the background operation is performed, and the system process is automatically switched to the manufacturer's negative one screen.
  • the application account binding method in one or more embodiments of this specification obtains the digital identity issued by the system server corresponding to the client for the target service fast application, and sends it to the business server based on the digital identity Binding relationship query request, and receiving the account binding token returned by the business server, and based on the account binding token, send a one-key binding request to the business server through the service provider application to trigger the service provision application request business service
  • the terminal completes the one-click binding between the digital identity issued by the system server for the target service fast application and the account of the service providing application, so that by directly completing the one-click account binding by the service providing application and the business server, you can use
  • the service provides the login status of the application itself and the password-free login method, which simplifies the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the universality of the account binding of the application .
  • FIG. 6 is an example of this specification.
  • S602. Receive a binding relationship query request for a target service fast application, where the target service fast application includes at least one business service fast application developed in the fast application running environment provided by the operating system of the client, and the business service fast application corresponds to The service provides the preset business service in the application, and the binding relationship query request is generated based on the digital identity issued by the system server corresponding to the client for the target service fast application;
  • S604 In response to the received binding relationship query request, if it is determined that account binding has not been performed for the digital identity of the target service application, return an account binding token to the target service application;
  • S606 Receive a one-key binding request sent by the target service express application through the service providing application, where the one-key binding request carries the account binding token;
  • S608 In response to the received one-key binding request, bind the digital identity of the target service application and the account of the service providing application based on the above-mentioned account binding token.
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login mode simplifies the user's operation steps; at the same time, it does not rely on the ability of the manufacturer's operating system to provide the digital identity proxy acquisition, which improves the universality of application account binding.
  • the above S604, returning the account binding token to the target service fast application specifically includes: performing encryption processing on the digital identity of the service providing application and the preset encryption factor to obtain the account binding token; the encrypted account will be included
  • the scheme protocol link of the binding token is sent to the target service fast application.
  • the above S608 in response to the received one-key binding request, binds the digital identity of the target service fast application and the account of the service providing application based on the above account binding token, which specifically includes: responding to the received one One-click binding request to verify the validity of the preset encryption factor in the above account binding token; if it is determined that the validity verification of the preset encryption factor is passed, the digital identity and service provision application of the target service will be applied To bind your account.
  • receiving the one-key binding request sent by the target service application through the service providing application specifically includes: receiving the one-key binding request sent by the target service application through the service providing application invoking the preset bind interface.
  • the aforementioned one-key binding request is generated based on the account binding token after the service providing application detects the user's confirmation binding request for the application account binding page.
  • FIG. 7 is an example of this specification.
  • a schematic diagram of the module composition of an application account binding device provided by multiple embodiments. The device is set on the client side and used to execute the application account binding method described in FIGS. 2 to 5, as shown in FIG. 7, The device includes:
  • the target service fast application includes the development of the fast application running environment provided by the operating system of the client At least one business service quick application in the application, where the business service quick application corresponds to a preset business service in the service providing application;
  • a binding relationship query module 702 which sends a binding relationship query request to the business server corresponding to the service providing application based on the digital identity;
  • Binding token receiving module 703 which receives the account binding token returned by the business server, where the account binding token is the account binding token that the business server has determined not to perform account binding for the digital identity. Generated regularly; account binding trigger module 704, which, after detecting the user's one-key binding trigger operation, sends a one-key carrying account binding token to the business server through the service providing application Binding request, so that the business server binds the digital identity and the account of the service providing application based on the account binding token.
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login mode simplifies the user's operation steps; at the same time, it does not rely on the ability of the manufacturer's operating system to provide the digital identity proxy acquisition, which improves the universality of application account binding.
  • the binding token receiving module 703 receives the scheme protocol link containing the account binding token returned by the business server.
  • the account binding token is obtained by encrypting the digital identity and a preset encryption factor.
  • the account binding triggering module 704 sends a one-click binding request carrying an account binding token to the service server through the service providing application, so that the service server responds to the The preset encryption factor in the account binding token is validated, and the digital identity is bound to the account of the service providing application after the validity verification of the preset encryption factor is passed.
  • the account binding trigger module 704 after detecting the user's one-key binding trigger operation, trigger the service providing application to display the application account binding page; upon detecting that the user is targeting the application account After the binding request is confirmed on the binding page, the preset bind interface is invoked through the service providing application, and a one-key binding request carrying the account binding token is sent to the service server.
  • the account binding trigger module 704 invokes a preset bind interface through the service providing application, and sends a one-click binding request carrying an account binding token to the service server, so that the After the account binding is completed, the business server synchronizes the account binding relationship for the target service application to the system server.
  • the account binding trigger module 704 if it is detected that the service providing application is not logged in, log in to the service providing application based on the secret-free login mode of the service providing application selected by the user Application; Call the preset bind interface through the service providing application, and send a one-key binding request carrying an account binding token to the service server.
  • the above-mentioned device further includes a binding result display module, which: receives and displays the account binding successful result sent by the service providing application; and switches the current interactive interface to the smart scenario under the operating system of the client An interactive interface, where the intelligent contextual interaction interface includes a smart context card for displaying service change information.
  • a binding result display module which: receives and displays the account binding successful result sent by the service providing application; and switches the current interactive interface to the smart scenario under the operating system of the client An interactive interface, where the intelligent contextual interaction interface includes a smart context card for displaying service change information.
  • the account binding device of the application in one or more embodiments of this specification obtains the digital identity issued by the system server corresponding to the client for the target service fast application, and sends the digital identity to the business server based on the digital identity Binding relationship query request, and receiving the account binding token returned by the business server, and based on the account binding token, send a one-key binding request to the business server through the service provider application to trigger the service provision application request business service
  • the terminal completes the one-click binding between the digital identity issued by the system server for the target service fast application and the account of the service providing application, so that by directly completing the one-click account binding by the service providing application and the business server, you can use
  • the service provides the login status of the application itself and the password-free login method, which simplifies the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the universality of the account binding of the application .
  • FIG. 8 is one or more The embodiment provides a schematic diagram of the module composition of the application account binding device, which is set on the business server corresponding to the service providing application and is used to execute the application account binding method described in FIG. 6, as shown in FIG. 8,
  • the device includes:
  • Query request receiving module 801 which receives a binding relationship query request for a target service fast application, the target service fast application including at least one business service fast application developed in the fast application running environment provided by the operating system of the client, so The business service application corresponds to a preset business service in the service provision application, and the binding relationship query request is generated based on the digital identity issued by the system server corresponding to the client for the target service application. of;
  • the binding token sending module 802 in response to the binding relationship query request, if it is determined that account binding has not been performed for the digital identity, it returns an account binding token to the target service application;
  • the application account binding module 804 in response to the one-key binding request, binds the digital identity to the account of the service providing application based on the account binding token.
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login mode simplifies the user's operation steps; at the same time, it does not rely on the ability of the manufacturer's operating system to provide the digital identity proxy acquisition, which improves the universality of application account binding.
  • the binding token sending module 802 which: encrypts the digital identity and a preset encryption factor to obtain an account binding token; and includes the scheme protocol of the account binding token The link is sent to the target service fast application.
  • the application account binding module 804 is configured to: in response to the one-key binding request, verify the validity of the preset encryption factor in the account binding token; Assuming that the validity verification of the encryption factor is passed, the digital identity is bound to the account of the service providing application.
  • the binding request receiving module 803 receives the one-key binding request sent by the target service application through the service providing application calling a preset bind interface.
  • the one-key binding request is generated based on the account binding token after the service providing application detects the user's confirmation binding request for the application account binding page.
  • the above device further includes a binding relationship synchronization module, which synchronizes the account binding relationship for the target service application to the system server after the account binding is completed.
  • the account binding device of the application in one or more embodiments of this specification obtains the digital identity issued by the system server corresponding to the client for the target service fast application, and sends the digital identity to the business server based on the digital identity Binding relationship query request, and receiving the account binding token returned by the business server, and based on the account binding token, send a one-key binding request to the business server through the service provider application to trigger the service provision application request business service
  • the terminal completes the one-click binding between the digital identity issued by the system server for the target service fast application and the account of the service providing application, so that by directly completing the one-click account binding by the service providing application and the business server, you can use
  • the service provides the login status of the application itself and the password-free login method, which simplifies the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the universality of the account binding of the application .
  • one or more embodiments of this specification also provide an application account binding system, which is used to execute the diagram 2 to 6 describe the application account binding method.
  • the system includes a client and a background server.
  • a service providing application is installed on the client, and the target service fast application is run in the fast application running environment provided by the operating system of the client;
  • the background server includes a business server corresponding to the service providing application ,
  • the target service quick application includes at least one business service quick application, and the business service quick application corresponds to a preset business service in the service providing application.
  • the target service application obtains the digital identity issued by the system server corresponding to the client for the target service application; and, based on the digital identity, sends a binding to the business server corresponding to the service providing application Relation query request; and receiving the account binding token returned by the business server; and sending a one-key binding request carrying the account binding token to the business server through the service providing application.
  • the business server in response to the binding relationship query request, returns an account binding token to the target service application when it is determined that the account binding has not been performed for the digital identity; and, in response to all In the one-key binding request, the digital identity is bound to the account of the service providing application based on the account binding token.
  • the account binding system of the application in one or more embodiments of this specification obtains the digital identity issued by the system server corresponding to the client for the target service fast application, and sends the digital identity to the business server based on the digital identity Binding relationship query request, and receiving the account binding token returned by the business server, and based on the account binding token, send a one-key binding request to the business server through the service provider application to trigger the service provision application request business service
  • the terminal completes the one-click binding between the digital identity issued by the system server for the target service fast application and the account of the service providing application, so that by directly completing the one-click account binding by the service providing application and the business server, you can use
  • the service provides the login status of the application itself and the password-free login method, which simplifies the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the universality of the account binding of the application .
  • one or more embodiments of this specification also provide an application account binding device, which is used to execute the above application
  • the account binding method of the program is shown in Figure 9.
  • the account binding device of the application program may have relatively large differences due to different configurations or performances, and may include one or more processors 901 and a memory 902, and the memory 902 may store one or more storage applications or data. Among them, the memory 902 may be short-term storage or persistent storage.
  • the application program stored in the memory 902 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the device that binds the account of the application program.
  • the processor 901 may be configured to communicate with the memory 902, and execute a series of computer-executable instructions in the memory 902 on the account binding device of the application program.
  • the account binding device of the application program may also include one or more power sources 903, one or more wired or wireless network interfaces 904, one or more input and output interfaces 905, one or more keyboards 906, and so on.
  • the account binding device of the application program includes a memory and one or more programs.
  • One or more programs are stored in the memory, and the one or more programs may include one or more programs.
  • Modules, and each module may include a series of computer-executable instructions in the device that binds the account to the application, and is configured to be executed by one or more processors.
  • the one or more programs include the following computer executable instructions Execution instruction: Obtain the digital identity issued by the system server corresponding to the client for the target service fast application, the target service fast application including at least one service developed in the fast application running environment provided by the operating system of the client Fast service application, where the fast service application corresponds to a preset service service in a service providing application; based on the digital identity, sending a binding relationship query request to the service end corresponding to the service providing application; receiving the The account binding token returned by the business server, where the account binding token is generated by the business server when it determines that the account binding is not performed for the digital identity; when a user’s one is detected After the key binding triggers the operation, the service providing application sends a one-key binding request carrying the account binding token to the service server, so that the service server will transfer the account binding token based on the account binding token.
  • Execution instruction Obtain the digital identity issued by the system server corresponding to the client for the target service fast application, the target service fast application including at least one service developed in
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login mode simplifies the user's operation steps; at the same time, it does not rely on the ability of the manufacturer's operating system to provide the digital identity proxy acquisition, which improves the universality of application account binding.
  • the receiving the account binding token returned by the business server includes: receiving the scheme protocol link containing the account binding token returned by the business server; Wherein, the account binding token is obtained by encrypting the digital identity and a preset encryption factor.
  • the service providing application sends a one-key binding request carrying an account binding token to the business server, so that the business server is based on The account binding token binding the digital identity and the account of the service providing application includes: sending a key carrying the account binding token to the business server through the service providing application Binding request, so that the business server verifies the validity of the preset encryption factor in the account binding token, and after the validity verification of the preset encryption factor is passed, the digital identity is identified Bind with the account of the service providing application.
  • the one-key binding trigger operation of the user is detected, and then the service providing application sends the one carrying the account binding token to the business server through the service providing application.
  • the key binding request includes: after detecting a user's one-key binding trigger operation, triggering the service providing application to display an application account binding page; upon detecting that the user confirms the binding of the application account binding page
  • the preset bind interface is invoked through the service providing application, and a one-key binding request carrying the account binding token is sent to the service server.
  • the calling a preset bind interface through the service providing application and sending a one-key binding request carrying an account binding token to the business server includes: Call the preset bind interface through the service providing application, and send a one-click binding request carrying the account binding token to the service server, so that the service server will target the service after the account binding is completed.
  • the account binding relationship of the target service application is synchronized to the system server.
  • the calling a preset bind interface through the service providing application and sending a one-key binding request carrying an account binding token to the business server includes: If it is detected that the service providing application is not logged in, log in to the service providing application based on the password-free login mode of the service providing application selected by the user; call the preset bind interface through the service providing application , Sending a one-key binding request carrying the account binding token to the business server.
  • the computer-executable instruction when executed, after sending the one-key binding request carrying the account binding token to the business server through the service providing application, it further includes: receiving and displaying the The result of successful account binding sent by the service providing application; and, switching the current interactive interface to the smart scenario interactive interface under the operating system of the client, wherein the smart scenario interactive interface includes a smart scenario for displaying service change information card.
  • the account binding device of the application in one or more embodiments of this specification obtains the digital identity issued by the system server corresponding to the client for the target service fast application, and sends it to the business server based on the digital identity Binding relationship query request, and receiving the account binding token returned by the business server, and based on the account binding token, send a one-key binding request to the business server through the service provider application to trigger the service provision application request business service
  • the terminal completes the one-click binding between the digital identity issued by the system server for the target service fast application and the account of the service providing application, so that by directly completing the one-click account binding by the service providing application and the business server, you can use
  • the service provides the login status of the application itself and the password-free login method, which simplifies the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the universality of the account binding of the application .
  • the account binding device of the application program includes a memory and one or more programs, wherein one or more programs are stored in the memory, and the one or more programs may include one or more programs.
  • the above modules, and each module may include a series of computer-executable instructions in the device that binds the account of the application program, and is configured to be executed by one or more processors.
  • the one or more programs include a computer for performing the following Executable instruction: receiving a binding relationship query request for a target service fast application, the target service fast application including at least one business service fast application developed under the fast application running environment provided by the operating system of the client, the business service The fast application corresponds to a preset business service in the service providing application, and the binding relationship query request is generated based on the digital identity issued by the system server corresponding to the client for the target service fast application; and a response;
  • the binding relationship query request if it is determined that the account binding has not been performed for the digital identity, the account binding token is returned to the target service application; the target service application is received through the service A one-key binding request sent by an application, wherein the one-key binding request carries the account binding token; in response to the one-key binding request, the number is transferred based on the account binding token
  • the identity identifier is bound to the account of the service providing application.
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login mode simplifies the user's operation steps; at the same time, it does not rely on the ability of the manufacturer's operating system to provide the digital identity proxy acquisition, which improves the universality of application account binding.
  • the returning the account binding token to the target service application includes: encrypting the digital identity and the preset encryption factor to obtain the account binding Token; sending the scheme protocol link containing the account binding token to the target service fast application.
  • the computer executable instruction in response to the one-key binding request, bind the digital identity with the account of the service providing application based on the account binding token , Including: in response to the one-key binding request, verifying the validity of the preset encryption factor in the account binding token; The digital identity is bound to the account of the service providing application.
  • the receiving the one-key binding request sent by the target service application through the service providing application includes: receiving the target service application through the service providing The application calls the one-key binding request sent by the preset bind interface.
  • the one-key binding request is generated based on the account binding token after the service providing application detects the user's confirmation binding request for the application account binding page.
  • the computer-executable instructions when executed, after binding the digital identity and the account of the service providing application based on the account binding token, it further includes: after the account binding is completed Sync the account binding relationship for the target service fast application to the system server.
  • the account binding device of the application in one or more embodiments of this specification obtains the digital identity issued by the system server corresponding to the client for the target service fast application, and sends it to the business server based on the digital identity Binding relationship query request, and receiving the account binding token returned by the business server, and based on the account binding token, send a one-key binding request to the business server through the service provider application to trigger the service provision application request business service
  • the terminal completes the one-click binding between the digital identity issued by the system server for the target service fast application and the account of the service providing application, so that by directly completing the one-click account binding by the service providing application and the business server, you can use
  • the service provides the login status of the application itself and the password-free login method, which simplifies the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the universality of the account binding of the application .
  • one or more embodiments of this specification also provide a storage medium for storing computer-executable instructions, a specific implementation
  • the storage medium can be a U disk, an optical disk, a hard disk, etc.
  • the computer executable instructions stored in the storage medium can realize the following process when executed by the processor:
  • Obtain the system server corresponding to the client for the target service fast application The issued digital identity
  • the target service fast application includes at least one business service fast application developed in the fast application running environment provided by the operating system of the client, and the business service fast application corresponds to the service providing application
  • send a binding relationship query request to the business server corresponding to the service providing application receive the account binding token returned by the business server, where the account The binding token is generated when the business server determines that the account binding is not performed for the digital identity; after detecting the user's one-key binding trigger operation, the service providing application sends the The business server sends a one-key
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login mode simplifies the user's operation steps; at the same time, it does not rely on the ability of the manufacturer's operating system to provide the digital identity proxy acquisition, which improves the universality of application account binding.
  • the receiving the account binding token returned by the business server includes: receiving the account binding token returned by the business server.
  • the account binding token is obtained by encrypting the digital identity and a preset encryption factor.
  • the service providing application sends a one-key binding request carrying an account binding token to the business server, so as to Enabling the business server to bind the digital identity and the account of the service providing application based on the account binding token includes: sending, through the service providing application, to the business server carrying the account The one-key binding request of the binding token, so that the business server verifies the validity of the preset encryption factor in the account binding token, and when the validity verification of the preset encryption factor passes Then, the digital identity is bound to the account of the service providing application.
  • the one-key binding trigger operation of the user is detected, and the service-providing application sends the data carrying
  • the one-key binding request of the account binding token includes: after detecting the user's one-key binding trigger operation, triggering the service providing application to display the application account binding page; After confirming the binding request on the account binding page, the preset bind interface is invoked through the service providing application, and the one-key binding request carrying the account binding token is sent to the service server.
  • the preset bind interface is invoked through the service providing application, and the one carrying the account binding token is sent to the service server.
  • the key binding request includes: invoking a preset bind interface through the service providing application, and sending a one-key binding request carrying an account binding token to the business server, so that the business server can bind the account to the account.
  • the account binding relationship for the target service fast application is synchronized to the system server.
  • the preset bind interface is invoked through the service providing application, and the one carrying the account binding token is sent to the service server.
  • the key binding request includes: if it is detected that the service providing application is in an unlogged state, logging in to the service providing application based on the secret-free login mode of the service providing application selected by the user; An application is provided to call a preset bind interface, and send a one-key binding request carrying an account binding token to the business server.
  • the processor when the computer-executable instructions stored in the storage medium are executed by the processor, after the one-key binding request carrying the account binding token is sent to the business server through the service providing application, further Including: receiving and displaying the account binding successful result sent by the service providing application; and switching the current interaction interface to the intelligent context interaction interface under the operating system of the client, wherein the intelligent context interaction interface includes Smart scene card that displays service change information.
  • the computer-executable instructions stored in the storage medium in one or more embodiments of this specification When executed by the processor, they obtain the digital identity issued by the system server corresponding to the client for the target service fast application, and based on the number
  • the identity identifier sends a binding relationship query request to the business server, and receives the account binding token returned by the business server, and sends a one-key binding request to the business server through the service providing application based on the account binding token.
  • the key account binding can use the service to provide the login status of the application itself and the password-free login method, simplifying the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the application
  • the universality of account binding can use the service to provide the login status of the application itself and the password-free login method, simplifying the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the application The universality of account binding.
  • the storage medium may be a U disk, an optical disk, a hard disk, etc.
  • the target service fast application includes at least one business service fast application developed in the fast application running environment provided by the operating system of the client, and the business service fast application corresponds to a preset in the service providing application
  • the binding relationship query request is generated based on the digital identity issued by the system server corresponding to the client for the target service fast application; in response to the binding relationship query request, if it is determined If account binding is not performed for the digital identity, then the account binding token is returned to the target service application; the one-key binding request sent by the target service application through the service providing application is received, where: The one-key binding request carries the account binding token; in response to the one-key binding request, the digital identity and the account of the service providing application are performed based on the account binding token. Binding.
  • the target service fast application obtains the digital identity issued by the system server corresponding to the client, and sends a binding relationship query request to the business server based on the digital identity, and receives The account binding token returned by the business server, and based on the account binding token, a one-key binding request is sent to the business server through the service providing application to trigger the service provision application request
  • the business server completes the system server as the target service
  • the one-click binding between the digital identity issued by the fast app and the account of the service-providing application so that by directly completing the one-click account binding by the service-providing application and the business server, the service can provide the login status of the application itself and
  • the password-free login mode simplifies the user's operation steps; at the same time, it does not rely on the ability of the manufacturer's operating system to provide the digital identity proxy acquisition, which improves the universality of application account binding.
  • the returning the account binding token to the target service application includes: performing the digital identification and the preset encryption factor Encryption processing to obtain the account binding token; sending the scheme protocol link containing the account binding token to the target service fast application.
  • the digital identity is combined with the service based on the account binding token.
  • the binding of the account that provides the application includes: in response to the one-key binding request, verifying the validity of the preset encryption factor in the account binding token; if the preset encryption factor is valid If the sexual verification is passed, the digital identity is bound to the account of the service providing application.
  • the receiving the one-key binding request sent by the target service application through the service providing application includes: receiving the target service
  • the fast application calls the one-key binding request sent by the preset bind interface through the service providing application.
  • the one-key binding request is generated based on the account binding token after the service providing application detects the user's confirmation binding request for the application account binding page.
  • the computer-executable instructions stored in the storage medium when executed by the processor, after binding the digital identity and the account of the service providing application based on the account binding token, it further includes : After the account binding is completed, the account binding relationship for the target service application is synchronized to the system server.
  • the computer-executable instructions stored in the storage medium in one or more embodiments of this specification When executed by the processor, they obtain the digital identity issued by the system server corresponding to the client for the target service fast application, and based on the number
  • the identity identifier sends a binding relationship query request to the business server, and receives the account binding token returned by the business server, and sends a one-key binding request to the business server through the service providing application based on the account binding token.
  • the key account binding can use the service to provide the login status of the application itself and the password-free login method, simplifying the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the application
  • the universality of account binding can use the service to provide the login status of the application itself and the password-free login method, simplifying the user's operation steps; at the same time, it does not rely on the digital identity proxy acquisition capability provided by the manufacturer's operating system, which improves the application The universality of account binding.
  • the improvement of a technology can be clearly distinguished between hardware improvements (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method flow).
  • hardware improvements for example, improvements in circuit structures such as diodes, transistors, switches, etc.
  • software improvements improvements in method flow.
  • the improvement of many methods and processes of today can be regarded as a direct improvement of the hardware circuit structure.
  • Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by the hardware entity module.
  • a programmable logic device Programmable Logic Device, PLD
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • ABEL Advanced Boolean Expression Language
  • AHDL Altera Hardware Description Language
  • HD Cal JHDL
  • Java Hardware Description Language Lava, Lola, My HDL, PALASM, RHDL (Ruby Hardware Description), etc.
  • VHDL Very-High-Speed Integrated Circuit Hardware Description Language
  • Verilog Verilog
  • the controller can be implemented in any suitable manner.
  • the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program codes (such as software or firmware) executable by the (micro)processor. , Logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicon Labs C8051F320, the memory controller can also be implemented as part of the memory control logic.
  • controllers in addition to implementing the controller in a purely computer-readable program code manner, it is entirely possible to program the method steps to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded logic.
  • the same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as a structure within the hardware component. Or even, the device for realizing various functions can be regarded as both a software module for realizing the method and a structure within a hardware component.
  • a typical implementation device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cell 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 Any combination of these devices.
  • one or more of the embodiments in this specification can be provided as a method, a system, or a computer program product. Therefore, one or more of this specification may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more of this specification can adopt computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. form.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are used to generate It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory in computer readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the 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, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • one or more of the embodiments in this specification can be provided as a method, a system, or a computer program product. Therefore, one or more of this specification may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more of this specification can adopt computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. form.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • program modules can also be practiced in a distributed computing environment. In these distributed computing environments, tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种应用程序的账户绑定方法、装置及系统，该方法包括：获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识（S202）；基于获取到的数字身份标识，向服务提供应用对应的业务服务端发送绑定关系查询请求（S204）；接收业务服务端返回的账户绑定令牌，其中，该账户绑定令牌是业务服务端在确定针对数字身份标识未执行账户绑定时所生成的；在检测到用户的一键绑定触发操作后，通过服务提供应用向业务服务端发送携带有账户绑定令牌的一键绑定请求，以使业务服务端基于该账户绑定令牌将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定（S208）。

Description

应用程序的账户绑定 技术领域
本文件涉及互联网技术领域，尤其涉及一种应用程序的账户绑定方法、装置及系统。
背景技术
目前，随着互联网时代的到来，互联网在人们日常的学习、工作和生活中得到广泛的应用。人们日常的各种事务都可以通过互联网来处理和呈现。同时，随着移动互联网的快速发展，各互联网服务提供方通过开发各自的应用程序为用户提供相应的业务服务，用户可以根据各自的实际需求在智能手机中安装相应的应用程序，例如，视频应用、聊天应用、购物应用、支付应用等等。
其中，为了能够便于用户快速查看某一业务服务的变化信息，因此，通过将目标服务提供应用的账户与厂商快应用的账户进行绑定，这样在检测到该目标服务提供应用中的至少一个业务服务的变化信息时，将该业务服务的变化信息上传至客户端的操作系统下的智能情景模块，以便在终端负一屏中相应的智能场景卡片中显示该业务服务的变化信息，并且，当用户点击该智能场景卡片时能够自动跳转至相应的交互界面。然而，现有技术中主要是由客户端对应的系统服务端完成应用程序的账户绑定，需要用户输入服务提供应用的账号和密码，或者需要依赖于厂商操作系统提供的数字身份标识代理获取能力，才能实现应用程序的账户绑定。
由此可知，需要提供一种操作简单、普适性高的应用程序的账户绑定的技术方案。
发明内容
本说明书一个或多个实施例提供一种应用程序的账户绑定方法。该应用程序的账户绑定方法包括：获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的 一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种应用程序的账户绑定方法。该应用程序的账户绑定方法包括：接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种应用程序的账户绑定装置。该应用程序的账户绑定装置包括：身份标识获取模块，其获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；绑定关系查询模块，其基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；绑定令牌接收模块，其接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；账户绑定触发模块，其在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种应用程序的账户绑定装置。该应用程序的账户绑定装置包括：查询请求接收模块，其接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；绑定令牌发送模块，其响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定 令牌；绑定请求接收模块，其接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；应用账户绑定模块，其响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种应用程序的账户绑定系统。该应用程序的账户绑定系统包括客户端和后台服务端。其中，所述客户端上安装有服务提供应用，在所述客户端的操作系统所提供的快应用运行环境下运行目标服务快应用。所述后台服务端包括所述服务提供应用对应的业务服务端，所述目标服务快应用包括至少一个业务服务快应用，所述业务服务快应用对应于所述服务提供应用中的预设业务服务。所述目标服务快应用，获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识；以及，基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；以及，接收所述业务服务端返回的账户绑定令牌；以及，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。所述业务服务端，响应于所述绑定关系查询请求，在确定针对所述数字身份标识未执行账户绑定时，向所述目标服务快应用返回账户绑定令牌；以及，响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种应用程序的账户绑定设备，包括处理器以及被安排成存储计算机可执行指令的存储器。所述计算机可执行指令在被执行时使所述处理器：获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种应用程序的账户绑定设备，包括处理器以及被安排成存储计算机可执行指令的存储器。所述计算机可执行指令在被执行时使所述处理器：接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端 的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，所述一键绑定请求携带有所述账户绑定令牌；响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种存储介质，用于存储计算机可执行指令。所述可执行指令在被处理器执行时：获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例提供一种存储介质，用于存储计算机可执行指令。所述可执行指令在被处理器执行时：接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
附图说明
为了更清楚地说明本说明书一个或多个实施例或现有技术中的技术方案，下面将对 实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书一个或多个实施例提供的应用程序的账户绑定系统的应用场景示意图；
图2为本说明书一个或多个实施例提供的应用程序的账户绑定方法的第一种流程示意图；
图3为本说明书一个或多个实施例提供的应用程序的账户绑定方法的第二种流程示意图；
图4为本说明书一个或多个实施例提供的应用程序的账户绑定方法的第三种流程示意图；
图5为本说明书一个或多个实施例提供的应用程序的账户绑定方法中涉及的多端交互过程示意图；
图6为本说明书一个或多个实施例提供的应用于业务服务端的应用程序的账户绑定方法的流程示意图；
图7为本说明书一个或多个实施例提供的应用程序的账户绑定装置的第一种模块组成示意图；
图8为本说明书一个或多个实施例提供的应用程序的账户绑定装置的第二种模块组成示意图；
图9为本说明书一个或多个实施例提供的应用程序的账户绑定设备的结构示意图。
具体实施方式
为了使本技术领域人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合附图对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述。所描述的实施例仅仅是本说明书一个或多个一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都应当属于本本文件的保护范围。
需要说明的是，在不冲突的情况下，本说明书中的一个或多个实施例以及实施例中 的特征可以相互组合。下面将参考附图并结合实施例来详细说明本说明书一个或多个实施例。
本说明书一个或多个实施例提供了一种应用程序的账户绑定方法、装置及系统，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
图1为本说明书一个或多个实施例提供的应用程序的账户绑定系统的应用场景示意图，如图1所示，该系统包括后台服务端和客户端。其中，该客户端上安装有服务提供应用，在客户端的操作系统所提供的快应用运行环境下运行目标服务快应用，该目标服务快应用对应于服务提供应用中的至少一个预设业务服务；该客户端可以是智能手机、平板电脑等移动终端，该客户端还可以是个人计算机等终端设备，该后台服务端包括服务提供应用对应的业务服务端、以及操作系统应用对应的系统服务端，该后台服务端可以是独立的服务器，也可以是由多个服务器组成的服务器集群。其中，上述应用程序的账户绑定的具体过程为：
(1)目标服务快应用获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，该目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，该业务服务快应用对应于服务提供应用中的预设业务服务；
(2)目标服务快应用基于获取到的数字身份标识，向服务提供应用对应的业务服务端发送绑定关系查询请求，该绑定关系查询请求携带有数字身份标识；
(3)业务服务端响应于接收到的绑定关系查询请求，在确定针对上述数字身份标识未执行账户绑定时，向目标服务快应用返回账户绑定令牌，上述账户绑定令牌用于目标服务快应用通过服务提供应用请求业务服务端进行账户绑定；
(4)目标服务快应用在接收到业务服务端返回的账户绑定令牌后，展示一键绑定触发控件；
(5)目标服务快应用在检测到用户针对一键绑定触发控件的触控操作后，向服务提供应用发送账户绑定令牌，并触发服务提供应用展示账户绑定页面；
(6)服务提供应用在检测到用户针对账户绑定页面的确认信息后，向业务服务端发送携带有账户绑定令牌的一键绑定请求；
(7)业务服务端响应于接收到的一键绑定请求，基于上述账户绑定令牌将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定；
(8)业务服务端将针对目标服务快应用和服务提供应用的账户绑定关系同步至系统服务端，其中，该系统服务端即为客户端的厂商服务端。
具体的，在账户绑定完成后，业务服务端在检测到服务提供应用中与目标服务快应用对应的至少一个业务服务的业务变化信息后，将该业务变化信息上传至系统服务端，以使系统服务端触发客户端在智能情景交互界面中显示该业务变化信息，即在客户端的操作系统下与该目标服务快应用对应的智能情景卡片中显示该业务变化信息，其中，该智能情景卡片位于终端负一屏的交互界面中。
在上述应用程序的账户绑定的过程中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
图2为本说明书一个或多个实施例提供的应用程序的账户绑定方法的第一种流程示意图，图2中的方法能够由图1所示的客户端中的目标服务快应用执行，如图2所示，该方法至少包括以下步骤：
S202，获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，该目标服务快应用包括至少一个业务服务快应用，该业务服务快应用对应于服务提供应用中的预设业务服务。
其中，上述目标服务快应用即为服务提供应用对应的服务提供方预先在客户端的操作系统所提供的快应用运行环境下开发的与至少一项业务服务对应的厂商快应用，上述 服务提供应用是指为用户提供至少一项业务服务的应用程序，具体的，预先针对服务提供应用中的至少一项业务服务，在客户端的操作系统所提供的快应用运行环境下创建对应的业务服务快应用，将需要在终端负一屏显示业务服务变化信息的至少一项业务服务对应的运行于客户端的操作系统所提供的快应用运行环境中的业务服务快应用确定为目标服务快应用，上述数字身份标识即为OpenID。
在检测到用户针对客户端的操作系统中的智能情景备选绑定列表中的未启用绑定的业务服务快应用的账户绑定启用控件的触发操作后，向系统服务端发送数字身份标识获取请求，其中，该账户绑定启用控件用于触发将目标服务快应用对应的服务提供应用中的至少一项业务服务的变化信息接入客户端的操作系统下的智能情景卡片的处理链路。
针对目标服务快应用与服务提供应用之间已创建预设接口的情况，还可以直接通过预设接口获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识。
S204，基于获取到的数字身份标识，向服务提供应用对应的业务服务端发送绑定关系查询请求。
业务服务端在接收到绑定关系查询请求后，查询是否已针对数字身份标识执行账户绑定，即查询系统服务端为目标服务快应用所颁发的数字身份标识OpenID与服务提供应用的账户之间是否具有绑定关系。
S206，接收业务服务端返回的账户绑定令牌，其中，该账户绑定令牌是业务服务端在确定针对目标服务快应用对应的数字身份标识未执行账户绑定时所生成的。
业务服务端在确定系统服务端为目标服务快应用所颁发的数字身份标识OpenID与服务提供应用的账户之间不具有绑定关系时，生成账户绑定令牌，并将该账户绑定令牌发送至目标服务快应用。
S208，在检测到用户的一键绑定触发操作后，通过服务提供应用向业务服务端发送携带有账户绑定令牌的一键绑定请求，以使业务服务端基于该账户绑定令牌将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定。
在接收到业务服务端返回的账户绑定令牌后，展示一键绑定触发控件；若检测到用户针对一键绑定触发控件的触控操作后，向服务提供应用发送账户绑定令牌，并触发服务提供应用展示账户绑定页面；在检测到用户针对账户绑定页面的确认信息后，向业务服务端发送携带有账户绑定令牌的一键绑定请求。
目标快应用可以基于scheme协议唤起服务提供应用执行针对系统服务端为目标服 务快应用所颁发的数字身份标识OpenID与服务提供应用的账户一键绑定。
业务服务端检测服务提供应用中与已启动绑定的业务服务快应用对应的业务服务的变化信息；并将该变化信息同步到客户端的操作系统下的智能情景交互界面(即终端负一屏)中与该业务服务快应用对应的智能情景卡片中。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤，提升用户使用体验；以及，降级了账户绑定链路的复杂度，提高了账户绑定成功率；以及，省去了向厂商快应用进行回传参数的链路，避免了参数回传过程中的安全风险；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
其中，考虑到业务服务端向目标服务快应用返回包含账户绑定令牌的scheme协议链接的过程中，可能存在被截获的情况，为了提高应用程序的账户绑定链路的安全性，先在业务服务端对数字身份标识进行加密，再通过密文传输账户绑定令牌，以防止传输信息被劫持。基于此，如图3所示，上述S206，接收业务服务端返回的账户绑定令牌，具体包括S2061，接收业务服务端返回的包含账户绑定令牌的scheme协议链接。其中，该账户绑定令牌是业务服务端在确定针对目标服务快应用对应的数字身份标识未执行账户绑定且对该数字身份标识和预设加密因子进行加密得到的。
其中，上述预设加密因子可以包括时间戳信息、随机字符串中至少一项。业务服务端在确定目标服务快应用与服务提供应用之间不存账户绑定关系后，对服务提供应用的数字身份标识和预设加密因子进行加密处理，得到相应的账户绑定令牌，并将包含账户绑定令牌的scheme协议链接发送至目标服务快应用。
对应的，针对业务服务端返回的账户绑定令牌为密文数据的情况，上述S208，通过服务提供应用向业务服务端发送携带有账户绑定令牌的一键绑定请求，以使业务服务端基于该账户绑定令牌将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定，具体包括：通过服务提供应用向业务服务端发送携带有账户绑定令牌的一键绑定请求，以使业务服务端对获取到的账户绑定令牌中的预设加密因子进行有效性验证，并在 预设加密因子的有效性验证通过后针对目标服务快应用的数字身份标识和服务提供应用的登录账户进行绑定。
在通过服务提供应用触发业务服务端进行账户一键绑定时，由业务服务端先校验账户绑定令牌中的预设加密因子是否有效，只有确定账户绑定令牌具有可信性时，才执行账号绑定，这样能够进一步确定账户一键绑定的安全性。
针对目标服务快应用唤起服务提供应用进行一键账户绑定的过程，上述S208，在检测到用户的一键绑定触发操作后，通过服务提供应用向业务服务端发送携带有账户绑定令牌的一键绑定请求，具体包括：在检测到用户的一键绑定触发操作后，触发服务提供应用显示应用账户绑定页面；若业务服务端向目标服务快应用返回包含账户绑定令牌的scheme协议链接，则目标服务快应用在检测到用户针对一键绑定触发控件的触控操作后，触发服务提供应用基于包含账户绑定令牌的scheme协议链接打开账户绑定页面；在检测到用户针对应用账户绑定页面的确认绑定请求后，通过服务提供应用调用预设bind接口，向业务服务端发送携带有账户绑定令牌的一键绑定请求。
在完成账户绑定后，将针对目标服务快应用的账户绑定关系同步至系统服务端，基于此，上述通过服务提供应用调用预设bind接口，向业务服务端发送携带有账户绑定令牌的一键绑定请求，具体包括：通过服务提供应用调用预设bind接口，向业务服务端发送携带有账户绑定令牌的一键绑定请求，以使业务服务端在账户绑定完成后将针对目标服务快应用的账户绑定关系同步至系统服务端。
在业务服务端针对目标服务快应用和服务提供应用完成账户绑定成功后，将账户绑定对应关系上传至客户端对应的系统服务端(即厂商服务端)。
考虑到可能存在服务提供应用处于未登录状态的情况，为了简化用户的应用登录步骤，可以借助服务提供应用的免密登录方式，快速登录服务提供应用，基于此，上述通过服务提供应用调用预设bind接口，向业务服务端发送携带有账户绑定令牌的一键绑定请求，具体包括：若检测到服务提供应用处于未登录状态，则基于用户所选择的服务提供应用的免密登录方式，登录服务提供应用，该免密登录方式可以包括刷脸登录、指纹登录、开放授权登录中任一项，通过服务提供应用调用预设bind接口，向业务服务端发送携带有账户绑定令牌的一键绑定请求。
其中，在账户绑定完成之后，为了进一步提升用户使用体验，还可以自动跳转至智能情景信息展示页面，如图4所示，在上述S208，在检测到用户的一键绑定触发操作 后，通过服务提供应用向业务服务端发送携带有账户绑定令牌的一键绑定请求之后，还包括：
S210，接收并展示服务提供应用发送的账户绑定成功结果；以及，
S212，将当前交互界面切换至客户端的操作系统下的智能情景交互界面，其中，该智能情景交互界面包含用于显示服务变化信息的智能情景卡片。
具体的，目标服务快应用接收到账户绑定成功结果后，执行压后台操作，系统进程自动切换至厂商负一屏，其中，该厂商负一屏中包含用于显示目标服务快应用的服务变化信息的智能情景卡片。
在一个具体实施例中，如图5所示，给出了应用程序的账户绑定方法中的多端交互过程的示意图，具体包括：
S501，目标服务快应用获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，该目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，该业务服务快应用对应于服务提供应用中的预设业务服务；
S502，目标服务快应用基于获取到的数字身份标识，向服务提供应用对应的业务服务端发送绑定关系查询请求，该绑定关系查询请求携带有数字身份标识；
S503，业务服务端响应于接收到的绑定关系查询请求，确定系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间是否具有绑定关系；
S504，业务服务端在确定针对上述数字身份标识未执行账户绑定时，对上述数字身份标识和预设加密因子进行加密处理，得到相应的账户绑定令牌；
S505，业务服务端向目标服务快应用返回包含账户绑定令牌的scheme协议链接；
S506，目标服务快应用在接收到业务服务端返回的账户绑定令牌后，展示一键绑定触发控件；
S507，目标服务快应用在检测到用户针对一键绑定触发控件的触控操作后，触发服务提供应用基于包含账户绑定令牌的scheme协议链接打开账户绑定页面；
S508，服务提供应用在检测到用户针对账户绑定页面的确认信息后，通过调用预设bind接口向业务服务端发送携带有账户绑定令牌的一键绑定请求；
S509，业务服务端响应于接收到的一键绑定请求，对账户绑定令牌中的预设加密因子进行有效性验证；
S510，业务服务端在确定预设加密因子的有效性验证通过后，执行目标服务快应用的账户与服务提供应用的登录账户的绑定操作；
S511，业务服务端将针对目标服务快应用的账户绑定关系同步至系统服务端；
S512，业务服务端将针对目标服务快应用的账户绑定成功结果发送至服务提供应用；
S513，服务提供应用将账户绑定成功结果发送至目标服务快应用，以使目标服务快应用接收到账户绑定成功结果后，执行压后台操作，系统进程自动切换至厂商负一屏。
本说明书一个或多个实施例中的应用程序的账户绑定方法，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
对应上述图2至图5描述的应用程序的账户绑定方法，基于相同的技术构思，本说明书一个或多个实施例还提供了一种应用程序的账户绑定方法，图6为本说明书一个或多个实施例提供的应用程序的账户绑定方法的流程示意图，图6中的方法能够由图1中的服务提供应用对应的业务服务端执行，如图6所示，该方法至少包括以下步骤：
S602，接收针对目标服务快应用的绑定关系查询请求，该目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，该业务服务快应用对应于服务提供应用中的预设业务服务，该绑定关系查询请求是基于客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识所生成的；
S604，响应于接收到的绑定关系查询请求，若确定针对目标服务快应用的数字身份标识未执行账户绑定，则向目标服务快应用返回账户绑定令牌；
S606，接收目标服务快应用通过服务提供应用发送的一键绑定请求，其中，该一键绑定请求携带有所述账户绑定令牌；
S608，响应于接收到的一键绑定请求，基于上述账户绑定令牌将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
其中，上述S604，向目标服务快应用返回账户绑定令牌，具体包括：对服务提供应用的数字身份标识和预设加密因子进行加密处理，得到账户绑定令牌；将包含加密得到的账户绑定令牌的scheme协议链接发送至目标服务快应用。
其中，上述S608，响应于接收到的一键绑定请求，基于上述账户绑定令牌将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定，具体包括：响应于接收到的一键绑定请求，对上述账户绑定令牌中的预设加密因子进行有效性验证；若确定预设加密因子的有效性验证通过，则将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定。
其中，上述S606，接收目标服务快应用通过服务提供应用发送的一键绑定请求，具体包括：接收目标服务快应用通过服务提供应用调用预设bind接口发送的一键绑定请求。其中，上述一键绑定请求是服务提供应用在检测到用户针对应用账户绑定页面的确认绑定请求后基于账户绑定令牌所生成的。
其中，在S608，基于上述账户绑定令牌将目标服务快应用的数字身份标识和服务提供应用的账户进行绑定之后，还包括：在账户绑定完成后，将针对目标服务快应用的账户绑定关系同步至系统服务端。
本说明书一个或多个实施例中的应用程序的账户绑定方法，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同 时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
本说明书中该实施例与本说明书中上一实施例基于同一发明构思，因此该实施例的具体实施可以参见前述应用程序的账户绑定方法的实施，重复之处不再赘述。
对应上述图2至图5描述的应用程序的账户绑定方法，基于相同的技术构思，本说明书一个或多个实施例还提供了一种应用程序的账户绑定装置，图7为本说明书一个或多个实施例提供的应用程序的账户绑定装置的模块组成示意图，该装置设置于客户端，用于执行图2至图5描述的应用程序的账户绑定方法，如图7所示，该装置包括：
身份标识获取模块701，其获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；
绑定关系查询模块702，其基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；
绑定令牌接收模块703，其接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；账户绑定触发模块704，其在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
可选地，所述绑定令牌接收模块703接收所述业务服务端返回的包含账户绑定令牌的scheme协议链接。其中，所述账户绑定令牌是对所述数字身份标识和预设加密因子 进行加密得到的。
可选地，所述账户绑定触发模块704，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端对所述账户绑定令牌中的预设加密因子进行有效性验证，并在所述预设加密因子的有效性验证通过后将所述数字身份标识和所述服务提供应用的账户进行绑定。
可选地，所述账户绑定触发模块704：在检测到用户的一键绑定触发操作后，触发所述服务提供应用显示应用账户绑定页面；在检测到所述用户针对所述应用账户绑定页面的确认绑定请求后，通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
可选地，所述账户绑定触发模块704，通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端在账户绑定完成后将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
可选地，所述账户绑定触发模块704：若检测到所述服务提供应用处于未登录状态，则基于所述用户所选择的所述服务提供应用的免密登录方式，登录所述服务提供应用；通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
可选地，上述装置还包括绑定结果展示模块，其：接收并展示所述服务提供应用发送的账户绑定成功结果；以及，将当前交互界面切换至所述客户端的操作系统下的智能情景交互界面，所述智能情景交互界面包含用于显示服务变化信息的智能情景卡片。
本说明书一个或多个实施例中的应用程序的账户绑定装置，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
需要说明的是，本说明书中关于应用程序的账户绑定装置的实施例与本说明书中关 于应用程序的账户绑定方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应的应用程序的账户绑定方法的实施，重复之处不再赘述。
对应上述图6描述的应用程序的账户绑定方法，基于相同的技术构思，本说明书一个或多个实施例还提供了一种应用程序的账户绑定装置，图8为本说明书一个或多个实施例提供的应用程序的账户绑定装置的模块组成示意图，该装置设置于服务提供应用对应的业务服务端，用于执行图6描述的应用程序的账户绑定方法，如图8所示，该装置包括：
查询请求接收模块801，其接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；
绑定令牌发送模块802，其响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；
绑定请求接收模块803，其接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；
应用账户绑定模块804，其响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
可选地，所述绑定令牌发送模块802，其：对所述数字身份标识和预设加密因子进行加密处理，得到账户绑定令牌；将包含所述账户绑定令牌的scheme协议链接发送至所述目标服务快应用。
可选地，所述应用账户绑定模块804，其：响应于所述一键绑定请求，对所述账户绑定令牌中的所述预设加密因子进行有效性验证；若所述预设加密因子的有效性验证通过，则将所述数字身份标识和所述服务提供应用的账户进行绑定。
可选地，所述绑定请求接收模块803，其接收所述目标服务快应用通过所述服务提供应用调用预设bind接口发送的一键绑定请求。所述一键绑定请求是所述服务提供应用在检测到用户针对应用账户绑定页面的确认绑定请求后基于账户绑定令牌所生成的。
可选地，上述装置还包括绑定关系同步模块，其在账户绑定完成后，将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
本说明书一个或多个实施例中的应用程序的账户绑定装置，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
需要说明的是，本说明书中关于应用程序的账户绑定装置的实施例与本说明书中关于应用程序的账户绑定方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应的应用程序的账户绑定方法的实施，重复之处不再赘述。
对应上述图2至图6描述的应用程序的账户绑定方法，基于相同的技术构思，本说明书一个或多个实施例还提供了一种应用程序的账户绑定系统，该系统用于执行图2至图6描述的应用程序的账户绑定方法，该系统包括客户端和后台服务端。其中，所述客户端上安装有服务提供应用，在所述客户端的操作系统所提供的快应用运行环境下运行目标服务快应用；所述后台服务端包括所述服务提供应用对应的业务服务端，所述目标服务快应用包括至少一个业务服务快应用，所述业务服务快应用对应于所述服务提供应用中的预设业务服务。所述目标服务快应用，获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识；以及，基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；以及，接收所述业务服务端返回的账户绑定令牌；以及，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键 绑定请求。所述业务服务端，响应于所述绑定关系查询请求，在确定针对所述数字身份标识未执行账户绑定时，向所述目标服务快应用返回账户绑定令牌；以及，响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例中的应用程序的账户绑定系统，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
需要说明的是，本说明书中关于应用程序的账户绑定系统的实施例与本说明书中关于应用程序的账户绑定方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应的应用程序的账户绑定方法的实施，重复之处不再赘述。
进一步地，对应上述图2至图5所示的方法，基于相同的技术构思，本说明书一个或多个实施例还提供了一种应用程序的账户绑定设备，该设备用于执行上述的应用程序的账户绑定方法，如图9所示。
应用程序的账户绑定设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器901和存储器902，存储器902中可以存储有一个或一个以上存储应用程序或数据。其中，存储器902可以是短暂存储或持久存储。存储在存储器902的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括对应用程序的账户绑定设备中的一系列计算机可执行指令。更进一步地，处理器901可以设置为与存储器902通信，在应用程序的账户绑定设备上执行存储器902中的一系列计算机可执行指令。应用程序的账户绑定设备还可以包括一个或一个以上电源903，一个或一个以上有线或无线网络接口904，一个或一个以上输入输出接口905，一个或一个以上键盘906等。
在一个具体的实施例中，应用程序的账户绑定设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可 以包括一个或一个以上模块，且每个模块可以包括对应用程序的账户绑定设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
可选地，计算机可执行指令在被执行时，所述接收所述业务服务端返回的账户绑定令牌，包括：接收所述业务服务端返回的包含账户绑定令牌的scheme协议链接，其中，所述账户绑定令牌是对所述数字身份标识和预设加密因子进行加密得到的。
可选地，计算机可执行指令在被执行时，所述通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定，包括：通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端对所述账户绑定令牌中的预设加密因子进行有效性验证，并在所述预设加密因子的有效性验证通过后将所述数字身份标识和所述服务提供应用的账户进行绑定。
可选地，计算机可执行指令在被执行时，所述在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包 括：在检测到用户的一键绑定触发操作后，触发所述服务提供应用显示应用账户绑定页面；在检测到所述用户针对所述应用账户绑定页面的确认绑定请求后，通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
可选地，计算机可执行指令在被执行时，所述通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端在账户绑定完成后将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
可选地，计算机可执行指令在被执行时，所述通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：若检测到所述服务提供应用处于未登录状态，则基于所述用户所选择的所述服务提供应用的免密登录方式，登录所述服务提供应用；通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
可选地，计算机可执行指令在被执行时，在通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求之后，还包括：接收并展示所述服务提供应用发送的账户绑定成功结果；以及，将当前交互界面切换至所述客户端的操作系统下的智能情景交互界面，其中，所述智能情景交互界面包含用于显示服务变化信息的智能情景卡片。
本说明书一个或多个实施例中的应用程序的账户绑定设备，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
在另一个具体的实施例中，应用程序的账户绑定设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对应用程序的账户绑定设备中的一 系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
可选地，计算机可执行指令在被执行时，所述向所述目标服务快应用返回账户绑定令牌，包括：对所述数字身份标识和预设加密因子进行加密处理，得到账户绑定令牌；将包含所述账户绑定令牌的scheme协议链接发送至所述目标服务快应用。
可选地，计算机可执行指令在被执行时，所述响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定，包括：响应于所述一键绑定请求，对所述账户绑定令牌中的所述预设加密因子进行有效性验证；若所述预设加密因子的有效性验证通过，则将所述数字身份标识和所述服务提供应用的账户进行绑定。
可选地，计算机可执行指令在被执行时，所述接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，包括：接收所述目标服务快应用通过所述服务提供应用调用预设bind接口发送的一键绑定请求。所述一键绑定请求是所述服务提供应用在检测到用户针对应用账户绑定页面的确认绑定请求后基于账户绑定令牌所生成的。
可选地，计算机可执行指令在被执行时，在基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定之后，还包括：在账户绑定完成后，将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
本说明书一个或多个实施例中的应用程序的账户绑定设备，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
需要说明的是，本说明书中关于应用程序的账户绑定设备的实施例与本说明书中关于应用程序的账户绑定方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应的应用程序的账户绑定方法的实施，重复之处不再赘述。
进一步地，对应上述图2至图5所示的方法，基于相同的技术构思，本说明书一个或多个实施例还提供了一种存储介质，用于存储计算机可执行指令，一种具体的实施例中，该存储介质可以为U盘、光盘、硬盘等，该存储介质存储的计算机可执行指令在被处理器执行时，能实现以下流程：获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供 应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述接收所述业务服务端返回的账户绑定令牌，包括：接收所述业务服务端返回的包含账户绑定令牌的scheme协议链接。其中，所述账户绑定令牌是对所述数字身份标识和预设加密因子进行加密得到的。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定，包括：通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端对所述账户绑定令牌中的预设加密因子进行有效性验证，并在所述预设加密因子的有效性验证通过后将所述数字身份标识和所述服务提供应用的账户进行绑定。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：在检测到用户的一键绑定触发操作后，触发所述服务提供应用显示应用账户绑定页面；在检测到所述用户针对所述应用账户绑定页面的确认绑定请求后，通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端在账户绑定完成后将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：若检测到所述服务提供应用处于未登录状态，则基于所述用户所选择 的所述服务提供应用的免密登录方式，登录所述服务提供应用；通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，在通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求之后，还包括：接收并展示所述服务提供应用发送的账户绑定成功结果；以及，将当前交互界面切换至所述客户端的操作系统下的智能情景交互界面，其中，所述智能情景交互界面包含用于显示服务变化信息的智能情景卡片。
本说明书一个或多个实施例中的存储介质存储的计算机可执行指令在被处理器执行时，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
在另一个具体的实施例中，该存储介质可以为U盘、光盘、硬盘等，该存储介质存储的计算机可执行指令在被处理器执行时，能实现以下流程：接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
本说明书一个或多个实施例中，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服 务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述向所述目标服务快应用返回账户绑定令牌，包括：对所述数字身份标识和预设加密因子进行加密处理，得到账户绑定令牌；将包含所述账户绑定令牌的scheme协议链接发送至所述目标服务快应用。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定，包括：响应于所述一键绑定请求，对所述账户绑定令牌中的所述预设加密因子进行有效性验证；若所述预设加密因子的有效性验证通过，则将所述数字身份标识和所述服务提供应用的账户进行绑定。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，所述接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，包括：接收所述目标服务快应用通过所述服务提供应用调用预设bind接口发送的一键绑定请求。所述一键绑定请求是所述服务提供应用在检测到用户针对应用账户绑定页面的确认绑定请求后基于账户绑定令牌所生成的。
可选地，该存储介质存储的计算机可执行指令在被处理器执行时，在基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定之后，还包括：在账户绑定完成后，将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
本说明书一个或多个实施例中的存储介质存储的计算机可执行指令在被处理器执行时，针对目标服务快应用获取客户端对应的系统服务端为其颁发的数字身份标识，并基于该数字身份标识向业务服务端发送绑定关系查询请求，以及接收业务服务端返回的账户绑定令牌，并基于该账户绑定令牌通过服务提供应用向业务服务端发送一键绑定请求，以触发服务提供应用请求业务服务端完成系统服务端为目标服务快应用所颁发的数字身份标识与服务提供应用的账户之间的一键绑定，这样通过直接由服务提供应用和业务服务端完成一键账户绑定，能够借助服务提供应用本身的登录态及免密登录方式，简化了用户的使用操作步骤；同时，不依赖于厂商操作系统提供的数字身份标识代理获取能力，提高了应用程序的账户绑定的普适性。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于应用程序的账户绑定方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应的应用程序的账户绑定方法的实施，重复之处不再赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HD Cal、JHDL(Java Hardware Description Language)、Lava、Lola、My HDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit， ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书一个或多个时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书一个或多个的实施例可提供为方法、系统、或计算机程序产品。因此，本说明书一个或多个可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本说明书一个或多个可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书一个或多个是参照根据本说明书一个或多个实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括 指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本说明书一个或多个的实施例可提供为方法、系统或计算机程序产品。因此，本说明书一个或多个可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本说明书一个或多个可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、 CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书一个或多个可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书一个或多个，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本说明书一个或多个的实施例而已，并不用于限制本说明书一个或多个。对于本领域技术人员来说，本说明书一个或多个可以有各种更改和变化。凡在本说明书一个或多个的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本说明书一个或多个的权利要求范围之内。

Claims (19)

  1. 一种应用程序的账户绑定方法，包括：
    获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；
    基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；
    接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；
    在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  2. 根据权利要求1所述的方法，其中，所述接收所述业务服务端返回的账户绑定令牌，包括：
    接收所述业务服务端返回的包含账户绑定令牌的scheme协议链接，其中，所述账户绑定令牌是对所述数字身份标识和预设加密因子进行加密得到的。
  3. 根据权利要求2所述的方法，其中，所述通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定，包括：
    通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端对所述账户绑定令牌中的预设加密因子进行有效性验证，并在所述预设加密因子的有效性验证通过后将所述数字身份标识和所述服务提供应用的账户进行绑定。
  4. 根据权利要求1所述的方法，其中，所述在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：
    在检测到用户的一键绑定触发操作后，触发所述服务提供应用显示应用账户绑定页面；
    在检测到所述用户针对所述应用账户绑定页面的确认绑定请求后，通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
  5. 根据权利要求4所述的方法，其中，所述通过所述服务提供应用调用预设bind 接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：
    通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端在账户绑定完成后将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
  6. 根据权利要求4所述的方法，其中，所述通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，包括：
    若检测到所述服务提供应用处于未登录状态，则基于所述用户所选择的所述服务提供应用的免密登录方式，登录所述服务提供应用；
    通过所述服务提供应用调用预设bind接口，向所述业务服务端发送携带有账户绑定令牌的一键绑定请求。
  7. 根据权利要求1所述的方法，其中，在通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求之后，还包括：
    接收并展示所述服务提供应用发送的账户绑定成功结果；以及，
    将当前交互界面切换至所述客户端的操作系统下的智能情景交互界面，其中，所述智能情景交互界面包含用于显示服务变化信息的智能情景卡片。
  8. 一种应用程序的账户绑定方法，包括：
    接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；
    响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；
    接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；
    响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  9. 根据权利要求8所述的方法，其中，所述向所述目标服务快应用返回账户绑定令牌，包括：
    对所述数字身份标识和预设加密因子进行加密处理，得到账户绑定令牌；
    将包含所述账户绑定令牌的scheme协议链接发送至所述目标服务快应用。
  10. 根据权利要求9所述的方法，其中，所述响应于所述一键绑定请求，基于所述 账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定，包括：
    响应于所述一键绑定请求，对所述账户绑定令牌中的所述预设加密因子进行有效性验证；
    若所述预设加密因子的有效性验证通过，则将所述数字身份标识和所述服务提供应用的账户进行绑定。
  11. 根据权利要求8所述的方法，其中，所述接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，包括：
    接收所述目标服务快应用通过所述服务提供应用调用预设bind接口发送的一键绑定请求；
    其中，所述一键绑定请求是所述服务提供应用在检测到用户针对应用账户绑定页面的确认绑定请求后基于账户绑定令牌所生成的。
  12. 根据权利要求11所述的方法，其中，在基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定之后，还包括：
    在账户绑定完成后，将针对所述目标服务快应用的账户绑定关系同步至所述系统服务端。
  13. 一种应用程序的账户绑定装置，包括：
    身份标识获取模块，其获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；
    绑定关系查询模块，其基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；
    绑定令牌接收模块，其接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；
    账户绑定触发模块，其在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  14. 一种应用程序的账户绑定装置，包括：
    查询请求接收模块，其接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系 查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；
    绑定令牌发送模块，其响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；
    绑定请求接收模块，其接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；
    应用账户绑定模块，其响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  15. 一种应用程序的账户绑定系统，包括客户端和后台服务端，所述客户端上安装有服务提供应用，在所述客户端的操作系统所提供的快应用运行环境下运行目标服务快应用；所述后台服务端包括所述服务提供应用对应的业务服务端，所述目标服务快应用包括至少一个业务服务快应用，所述业务服务快应用对应于所述服务提供应用中的预设业务服务；
    所述目标服务快应用，获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识；以及，基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；以及，接收所述业务服务端返回的账户绑定令牌；以及，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求；
    所述业务服务端，响应于所述绑定关系查询请求，在确定针对所述数字身份标识未执行账户绑定时，向所述目标服务快应用返回账户绑定令牌；以及，响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  16. 一种应用程序的账户绑定设备，包括：
    处理器；以及
    被安排成存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器：
    获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；
    基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；
    接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服 务端在确定针对所述数字身份标识未执行账户绑定时所生成的；
    在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  17. 一种应用程序的账户绑定设备，包括：
    处理器；以及
    被安排成存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器：
    接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；
    响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；
    接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；
    响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  18. 一种存储介质，用于存储计算机可执行指令，所述可执行指令在被处理器执行时实现以下方法：
    获取客户端对应的系统服务端针对目标服务快应用所颁发的数字身份标识，所述目标服务快应用包括在所述客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务；
    基于所述数字身份标识，向所述服务提供应用对应的业务服务端发送绑定关系查询请求；
    接收所述业务服务端返回的账户绑定令牌，其中，所述账户绑定令牌是所述业务服务端在确定针对所述数字身份标识未执行账户绑定时所生成的；
    在检测到用户的一键绑定触发操作后，通过所述服务提供应用向所述业务服务端发送携带有账户绑定令牌的一键绑定请求，以使所述业务服务端基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
  19. 一种存储介质，用于存储计算机可执行指令，所述可执行指令在被处理器执行 时实现以下方法：
    接收针对目标服务快应用的绑定关系查询请求，所述目标服务快应用包括在客户端的操作系统所提供的快应用运行环境下开发的至少一个业务服务快应用，所述业务服务快应用对应于服务提供应用中的预设业务服务，所述绑定关系查询请求是基于所述客户端对应的系统服务端针对所述目标服务快应用所颁发的数字身份标识所生成的；
    响应于所述绑定关系查询请求，若确定针对所述数字身份标识未执行账户绑定，则向所述目标服务快应用返回账户绑定令牌；
    接收所述目标服务快应用通过所述服务提供应用发送的一键绑定请求，其中，所述一键绑定请求携带有所述账户绑定令牌；
    响应于所述一键绑定请求，基于所述账户绑定令牌将所述数字身份标识和所述服务提供应用的账户进行绑定。
PCT/CN2021/084618 2020-04-15 2021-03-31 应用程序的账户绑定 WO2021208743A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010296957.0A CN111538980B (zh) 2020-04-15 2020-04-15 一种应用程序的账户绑定方法、装置及系统
CN202010296957.0 2020-04-15

Publications (1)

Publication Number Publication Date
WO2021208743A1 true WO2021208743A1 (zh) 2021-10-21

Family

ID=71978637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/084618 WO2021208743A1 (zh) 2020-04-15 2021-03-31 应用程序的账户绑定

Country Status (2)

Country Link
CN (2) CN111538980B (zh)
WO (1) WO2021208743A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113037741A (zh) * 2021-03-04 2021-06-25 腾讯科技（深圳）有限公司 一种鉴权方法和相关装置
CN114237938A (zh) * 2021-12-17 2022-03-25 支付宝(杭州)信息技术有限公司 车辆驾驶服务处理方法及装置
CN114500635A (zh) * 2022-01-07 2022-05-13 支付宝(杭州)信息技术有限公司 服务处理方法及装置
CN116132076A (zh) * 2021-11-15 2023-05-16 青岛海尔科技有限公司 终端绑定方法以及设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111538980B (zh) * 2020-04-15 2021-07-27 支付宝(杭州)信息技术有限公司 一种应用程序的账户绑定方法、装置及系统
CN113434849A (zh) * 2020-09-04 2021-09-24 支付宝(杭州)信息技术有限公司 一种基于可信硬件的数据管理方法、装置及设备
CN112565466B (zh) * 2021-02-20 2021-04-27 支付宝(杭州)信息技术有限公司 跨应用关联用户的方法及装置
CN116228442A (zh) * 2021-12-23 2023-06-06 浙江口碑网络技术有限公司 一种医疗服务订单的处理方法、装置及电子设备
CN114500025B (zh) * 2022-01-19 2023-10-27 北京达佳互联信息技术有限公司 一种账户标识获取方法、装置、服务器及存储介质

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468837A (zh) * 2014-12-29 2015-03-25 小米科技有限责任公司 智能设备的绑定方法和装置
CN105353625A (zh) * 2015-10-12 2016-02-24 珠海格力电器股份有限公司 绑定智能设备的方法、装置及系统
CN107369018A (zh) * 2017-06-26 2017-11-21 中国人民银行数字货币研究所 数字货币钱包的绑定方法和绑定系统
WO2018113130A1 (zh) * 2016-12-22 2018-06-28 华为技术有限公司 应用程序授权方法、终端及服务器
CN109274726A (zh) * 2018-08-31 2019-01-25 阿里巴巴集团控股有限公司 绑定、迁移方法和装置、计算设备及存储介质
CN109525604A (zh) * 2018-12-29 2019-03-26 乐蜜有限公司 一种账号绑定的方法及相关设备
CN109615366A (zh) * 2018-11-22 2019-04-12 阿里巴巴集团控股有限公司 设备支付方法及装置
CN110288332A (zh) * 2019-06-28 2019-09-27 北京三快在线科技有限公司 银行卡绑定的系统、方法、装置、设备及存储介质
CN111538980A (zh) * 2020-04-15 2020-08-14 支付宝(杭州)信息技术有限公司 一种应用程序的账户绑定方法、装置及系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8700729B2 (en) * 2005-01-21 2014-04-15 Robin Dua Method and apparatus for managing credentials through a wireless network
US10382500B2 (en) * 2013-02-27 2019-08-13 Microsoft Technology Licensing, Llc Systems and methods for binding online content accounts
CN104348613B (zh) * 2013-07-24 2017-05-17 深圳市腾讯计算机系统有限公司 用户校验方法、装置及系统
US9392104B2 (en) * 2014-04-15 2016-07-12 Google Inc. Limiting user interaction with a computing device based on proximity of a user
CN106131047A (zh) * 2016-08-12 2016-11-16 乐视控股（北京）有限公司 账号登录方法及相关设备、账号登录系统
SG10201706070TA (en) * 2017-07-25 2019-02-27 Mastercard International Inc Offline Payment Using Virtual Card Account Number
CN109768961A (zh) * 2018-12-12 2019-05-17 平安科技（深圳）有限公司 基于一账通的微信小程序登录方法、装置及存储介质
CN109842616B (zh) * 2018-12-29 2021-09-17 卓米私人有限公司 账号绑定方法、装置及服务器
CN110290055B (zh) * 2019-06-25 2021-09-10 携程计算机技术（上海）有限公司 微信小程序WebView与原生组件的通信方法及系统

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468837A (zh) * 2014-12-29 2015-03-25 小米科技有限责任公司 智能设备的绑定方法和装置
CN105353625A (zh) * 2015-10-12 2016-02-24 珠海格力电器股份有限公司 绑定智能设备的方法、装置及系统
WO2018113130A1 (zh) * 2016-12-22 2018-06-28 华为技术有限公司 应用程序授权方法、终端及服务器
CN107369018A (zh) * 2017-06-26 2017-11-21 中国人民银行数字货币研究所 数字货币钱包的绑定方法和绑定系统
CN109274726A (zh) * 2018-08-31 2019-01-25 阿里巴巴集团控股有限公司 绑定、迁移方法和装置、计算设备及存储介质
CN109615366A (zh) * 2018-11-22 2019-04-12 阿里巴巴集团控股有限公司 设备支付方法及装置
CN109525604A (zh) * 2018-12-29 2019-03-26 乐蜜有限公司 一种账号绑定的方法及相关设备
CN110288332A (zh) * 2019-06-28 2019-09-27 北京三快在线科技有限公司 银行卡绑定的系统、方法、装置、设备及存储介质
CN111538980A (zh) * 2020-04-15 2020-08-14 支付宝(杭州)信息技术有限公司 一种应用程序的账户绑定方法、装置及系统

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113037741A (zh) * 2021-03-04 2021-06-25 腾讯科技（深圳）有限公司 一种鉴权方法和相关装置
CN113037741B (zh) * 2021-03-04 2023-08-11 腾讯科技（深圳）有限公司 一种鉴权方法、鉴权装置、计算机设备及存储介质
CN116132076A (zh) * 2021-11-15 2023-05-16 青岛海尔科技有限公司 终端绑定方法以及设备
CN116132076B (zh) * 2021-11-15 2024-05-24 青岛海尔科技有限公司 终端绑定方法以及设备
CN114237938A (zh) * 2021-12-17 2022-03-25 支付宝(杭州)信息技术有限公司 车辆驾驶服务处理方法及装置
CN114237938B (zh) * 2021-12-17 2024-05-07 支付宝(杭州)信息技术有限公司 车辆驾驶服务处理方法及装置
CN114500635A (zh) * 2022-01-07 2022-05-13 支付宝(杭州)信息技术有限公司 服务处理方法及装置

Also Published As

Publication number Publication date
CN111538980B (zh) 2021-07-27
CN113641983A (zh) 2021-11-12
CN111538980A (zh) 2020-08-14
CN113641983B (zh) 2024-06-07

Similar Documents

Publication Publication Date Title
WO2021208743A1 (zh) 应用程序的账户绑定
JP6859513B2 (ja) ２次元コード生成の方法およびデバイス、ならびに２次元コード認識の方法およびデバイス
WO2021208744A1 (zh) 应用程序的授权登录
EP3552132B1 (en) Login information processing method and device
US10957326B2 (en) Device identifier dependent operation processing of packet based data communication
CN110378091B (zh) 一种身份验证方法、装置及设备
JP6731202B2 (ja) アイデンティティ検証方法及びシステム並びにインテリジェントウェアラブルデバイス
KR102398502B1 (ko) 메시지를 처리하기 위한 전자 장치 및 그의 동작 방법
US10476870B2 (en) Local claim-based security service with cross-browser compatibility
CN113010870B (zh) 基于数字凭证的业务处理方法、装置及设备
US20200287891A1 (en) Electronic certificate transmission method, apparatus and device
JP2017085567A (ja) ユーザ端末、メッセージを送受信する方法及びコンピュータプログラム
US20210224784A1 (en) Fare payment
CN108564363B (zh) 一种交易处理方法、服务器、客户端及系统
JP6763088B2 (ja) リソース送信方法および装置
TW201909012A (zh) 資訊驗證處理方法、裝置、系統、客戶端及伺服器
US10831754B2 (en) Using metadata to take action on an SMS message on a proprietary system
CN112287376B (zh) 一种隐私数据的处理方法及装置
CN111368232A (zh) 口令分享回流方法、装置、电子设备及存储介质
TW202130160A (zh) 會話建立方法、跨境支付方法、裝置及系統
US10958726B2 (en) Method of synchronizing device list in a smart network system, apparatus, and computer storage medium thereof
CN112784243A (zh) 授权管理方法及装置、电子设备和存储介质
US10178087B2 (en) Trusted pin management
CN113572827B (zh) 注册处理方法及装置
CN103942313B (zh) 网站页面的展示方法、装置及终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21787719

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21787719

Country of ref document: EP

Kind code of ref document: A1