WO2021073428A1 - 一种账号绑定方法、设备及系统 - Google Patents

一种账号绑定方法、设备及系统 Download PDF

Info

Publication number
WO2021073428A1
WO2021073428A1 PCT/CN2020/119018 CN2020119018W WO2021073428A1 WO 2021073428 A1 WO2021073428 A1 WO 2021073428A1 CN 2020119018 W CN2020119018 W CN 2020119018W WO 2021073428 A1 WO2021073428 A1 WO 2021073428A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
server
electronic device
login page
openid
Prior art date
Application number
PCT/CN2020/119018
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 华为技术有限公司
Priority to EP20877057.8A priority Critical patent/EP4033724A4/en
Priority to US17/768,561 priority patent/US20230122238A1/en
Publication of WO2021073428A1 publication Critical patent/WO2021073428A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/084—Access security using delegated authorisation, e.g. open authorisation [OAuth] protocol
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/35—Protecting application or service provisioning, e.g. securing SIM application provisioning

Definitions

  • the embodiments of the present application relate to the field of electronic technology, and in particular to an account binding method, device, and system.
  • the negative one screen can cooperate with third-party applications to show users the events recommended by the third-party applications.
  • the negative one screen can display user-related events recommended by the three-party application.
  • the tripartite application side needs to develop tripartite quick apps, develop login pages based on tripartite quick apps, and need to call a negative one-screen account management software development kit (SDK) in the tripartite quick apps.
  • SDK negative one-screen account management software development kit
  • OpenID open unique identity document
  • the developers of the third-party application may not be familiar with the development process of the fast application, so the development work is more difficult, and the development workload on the third-party application side is large, the binding process is complicated, and the binding cost High, which is not conducive to the introduction of negative one screen to the third party application.
  • the embodiment of the application provides an account binding method, device and system.
  • One screen can replace the three-party quick application to obtain the OpenID corresponding to the user account of the one-screen negative, so as to realize the user account of the three-party application and the user of the one-screen negative through OpenID.
  • the binding of accounts reduces the development workload of three-party applications, simplifies the process of binding three-party applications and one-screen accounts, and improves the efficiency and flexibility of account binding.
  • an embodiment of the present application provides an account binding method.
  • the method includes: an electronic device logs in to a user account of a first application.
  • the electronic device detects a first preset operation of the user, and the first preset operation is used to instruct to associate the second application with the first application.
  • the electronic device obtains the open unique identifier OpenID corresponding to the user account of the first application through the first application.
  • the electronic device sends the OpenID and the identity information of the second application to the server of the first application.
  • the electronic device obtains account binding success information from the server of the first application, and the account binding success information is used to indicate that the user account of the first application and the user account of the second application have been bound.
  • the first application can replace the third-party application to apply and obtain the OpenID corresponding to the user account of the first application, so as to establish the binding relationship between the user account of the third-party application and the OpenID, that is, to establish the third-party application The binding relationship between the user account of and the user account of the first application.
  • the three-party application does not need to develop the three-party express application in order to achieve the binding, nor does it need to specifically develop a login page based on the three-party express application in order to realize the binding, and does not need to call the account management SDK of the first application in the three-party express application ,
  • To obtain the OpenID and other complex development work corresponding to the user account of the first application thereby simplifying the development process of the third party application, reducing the development workload of the third party application, simplifying the account binding process of the third party application and the first application, and reducing the target
  • the cost of account binding for third-party applications improves the efficiency and flexibility of account binding.
  • the account binding success information is generated by the server of the first application after the server of the second application binds the OpenID with the user account of the second application and notifies the server of the first application.
  • the server of the second application binds the user account of the second application with the OpenID, and notifies the server of the first application after the account is successfully bound. Therefore, the electronic device can obtain the account binding success information from the server of the first application.
  • the method further includes: the electronic device obtains the login page information of the second application from the server of the first application, and the login page information includes OpenID.
  • the electronic device displays the login page of the second application according to the login page information.
  • the electronic device obtains the user account of the second application entered by the user on the login page.
  • the electronic device sends the user account and OpenID of the second application input by the user to the server of the second application.
  • the electronic device may obtain the login page information of the second application from the server of the first application, and display the user login page of the second application according to the information, so that the user can input the user account of the second application. Then, the electronic device can send the user account and OpenID of the second application to the server of the second application, so that the service of the second application binds the user account and OpenID of the second application after the user account of the second application is verified. That is, the user account of the second application is bound to the user account of the first application.
  • the login page information is a login card object corresponding to the second application
  • the parameters of the login card object include OpenID.
  • the electronic device displaying the login page of the second application according to the login page information includes: the electronic device displays the login card of the second application according to the login card object.
  • the electronic device can display the login page of the second application in the form of a login card.
  • the login page information is the address of the 5th generation hypertext markup language H5 login page of the second application, and the address of the H5 login page includes OpenID.
  • the electronic device displaying the login page of the second application according to the login page information includes: the electronic device displays the H5 login page of the second application according to the address of the H5 login page.
  • the electronic device can display the H5 login page of the second application.
  • the address of the H5 login page obtained by the electronic device from the first application server is spliced with the OpenID.
  • the login page information is the address of the native application login page of the second application, and the address of the native application login page includes OpenID.
  • the electronic device displaying the login page of the second application according to the login page information includes: the electronic device displays the native application login page of the second application according to the address of the native application login page.
  • the login page information is the deep link DeepLink address of the native application login page of the second application.
  • the electronic device can display the native application login page of the second application.
  • the address of the native application login page obtained by the electronic device from the first application server is spliced with the OpenID.
  • the login page information is the address of the quick app login page of the second application, and the address of the quick app login page includes OpenID.
  • the electronic device displaying the login page of the second application according to the login page information includes: the electronic device displays the quick application login page of the second application according to the address of the quick application login page.
  • the login page information is the deep link DeepLink address of the quick application login page of the second application.
  • the electronic device can display the quick application login page of the second application.
  • the address of the quick application login page obtained by the electronic device from the first application server is spliced with the OpenID.
  • the electronic device sends the user account and OpenID of the second application input by the user to the server of the second application, including: after the electronic device detects the second preset operation of the user, the user The input user account and OpenID of the second application are sent to the server of the second application, and the second preset operation is used to instruct to bind the user account of the first application with the user account of the second application.
  • the electronic device sends the user account and OpenID of the second application to the server of the second application only after the user instructs to bind, so that the server of the second application can bind.
  • that the electronic device obtains the OpenID through the first application includes: the electronic device obtains the identity information of the second application. The electronic device sends the identity information of the second application to the account management server of the first application through the first application. The electronic device obtains the OpenID from the account management server of the first application.
  • the electronic device may send the identity information of the second application to the account management server of the first application, so that the electronic device generates the OpenID corresponding to the user account of the first application according to the identity information of the second application.
  • the method further includes: the electronic device obtains the user-related event pushed by the server of the second application.
  • the electronic device prompts the user to associate the event to the user through the first application.
  • the server of the second application may, according to the binding relationship, Push the generated user-related events to the first application and electronic device corresponding to OpenID, so that the electronic device can display the user-related events to the user through the first application.
  • the first application is a negative one screen.
  • the user account of the second application can be bound to the user account of the negative one screen, and the electronic device can display the user-related events pushed by the server of the second application through the negative one screen.
  • an embodiment of the present application provides an account management system, including: an electronic device, a server of a first application, an account management server of the first application, and a server of the second application.
  • the electronic device is used to: log in to the user account of the first application; detect a first preset operation of the user, and the first preset operation is used to instruct to associate the second application with the first application;
  • the account management server of the first application obtains the open unique identifier OpenID corresponding to the user account of the first application; sends the OpenID and the identity information of the second application to the server of the first application; obtains the account binding from the server of the first application Success information, the account binding success information is used to indicate that the user account of the first application and the user account of the second application have been bound.
  • the server of the first application is further configured to obtain login page information of the second application according to the identity information of the second application obtained from the electronic device, where the login page information includes OpenID.
  • the server of the first application is also used to send the login page information to the electronic device.
  • the electronic device is also configured to display the login page of the second application according to the login page information obtained from the server of the first application.
  • the electronic device is also used to obtain the user account of the second application entered by the user on the login page.
  • the electronic device is also used to send the user account and OpenID of the second application input by the user to the server of the second application.
  • the server of the second application is configured to bind the OpenID with the user account of the second application after the user account of the second application input by the user is verified.
  • the server of the second application is further configured to notify the server of the first application that the user account of the first application and the user account of the second application have been bound.
  • the server of the first application is configured to obtain the login card object corresponding to the second application according to the identity information of the second application obtained from the electronic device, and the parameters of the login card object include OpenID.
  • the server of the first application is configured to send the OpenID to the server of the second application according to the identity information of the second application obtained from the electronic device.
  • the server of the second application is also used to send the address of the H5 login page of the fifth generation hypertext markup language of the second application to the server of the first application, and the address of the H5 login page includes OpenID.
  • the server of the first application is also used to send the address of the H5 login page to the electronic device.
  • the address of the H5 login page sent by the second application server to the first application server is spliced with the OpenID.
  • the server of the first application is configured to send the OpenID to the server of the second application according to the identity information of the second application obtained from the electronic device.
  • the server of the second application is further configured to send the address of the native application login page of the second application to the server of the first application, and the address of the native application login page includes OpenID.
  • the server of the first application is also used to send the address of the login page of the native application to the electronic device.
  • the OpenID is spliced with the address of the native application login page sent by the second application server to the first application server.
  • the server of the first application is configured to send the OpenID to the server of the second application according to the identity information of the second application obtained from the electronic device.
  • the server of the second application is also used to send the address of the quick application login page of the second application to the server of the first application, and the address of the quick application login page includes OpenID.
  • the server of the first application is also used to send the address of the quick application login page to the electronic device.
  • the address of the quick application login page sent by the second application server to the first application server is spliced with the OpenID.
  • the server of the second application is also used to, after binding OpenID with the user account of the second application, if a user-related event corresponding to OpenID is generated according to the determination, then the user-related event is pushed to Electronic equipment corresponding to OpenID.
  • the electronic device is also configured to, after acquiring the user-related event pushed by the server of the second application, prompt the user of the user-related event through the first application.
  • the first application is a negative screen.
  • an embodiment of the present application provides an account binding device, which is included in an electronic device.
  • the device has the function of realizing the behavior of the electronic device in any of the above aspects and possible design methods.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes at least one module or unit corresponding to the above-mentioned functions. For example, display module/unit, processing module/unit, communication module/unit, storage module/unit, etc.
  • an embodiment of the present application provides a computer storage medium, including computer instructions, which when the computer instructions run on an electronic device, cause the electronic device to execute the account binding method in any one of the possible designs in the foregoing aspects.
  • the embodiments of the present application provide a computer program product, which when the computer program product runs on a computer, causes the computer to execute the account binding method executed by the electronic device in any one of the possible designs in the foregoing aspects.
  • an embodiment of the present application provides a chip system, which is applied to an electronic device.
  • the chip system includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected by wires; the interface circuit is used to receive signals from the memory of the electronic device and send signals to the processor.
  • the signals include the memory Stored computer instructions; when the processor executes the computer instructions, it causes the electronic device to execute the account binding method in any one of the possible designs of the above aspects.
  • FIG. 1A is a flowchart of an account binding method provided in the prior art
  • FIG. 1B is a flow chart of obtaining OpenID provided by the prior art
  • FIG. 1C is a schematic diagram of an interface during a set of account binding process provided by the prior art
  • FIG. 2 is a structural diagram of an account management system provided by an embodiment of the application.
  • FIG. 3 is a flowchart of obtaining OpenID according to an embodiment of the application.
  • FIG. 4 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • FIG. 5 is a flowchart of an account binding method provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of a set of interfaces provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of an interface provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of another set of interfaces provided by an embodiment of the application.
  • FIG. 9 is a schematic diagram of another set of interfaces provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of another interface provided by an embodiment of the application.
  • FIG. 11 is a schematic diagram of another set of interfaces provided by an embodiment of the application.
  • FIG. 12 is a schematic diagram of another set of interfaces provided by an embodiment of the application.
  • FIG. 13 is a schematic diagram of another set of interfaces provided by an embodiment of the application.
  • FIG. 14 is a schematic diagram of another interface provided by an embodiment of the application.
  • FIG. 15 is a flowchart of displaying a login page of a three-party application according to an embodiment of the application
  • FIG. 16 is a schematic diagram of another set of interfaces provided by an embodiment of the application.
  • FIG. 17 is another flowchart for displaying a login page of a three-party application provided by an embodiment of the application.
  • FIG. 18 is another flowchart for displaying a login page of a three-party application provided by an embodiment of the application.
  • FIG. 19 is a schematic diagram of a group of account binding process provided by an embodiment of the application.
  • FIG. 20 is a schematic diagram of another interface provided by an embodiment of the application.
  • FIG. 21 is a schematic diagram of another structure provided by an embodiment of the application.
  • first and second are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with “first” and “second” may explicitly or implicitly include one or more of these features. In the description of the present embodiment, unless otherwise specified, "plurality" means two or more.
  • the main page of the negative one screen is usually the leftmost screen of the desktop, that is, the leftmost page of the desktop (or Widget interface).
  • Negative one screen can provide users with notifications or quick use of services such as search, news, sports health, life services, historical applications or application recommendations.
  • the three-party application can recommend the user related event to the negative one screen based on the binding relationship after the related event concerned by the user is generated. To show.
  • user-related events are events generated by three-party applications that are related to, and care about or concerned by, users.
  • a three-party application is a food delivery application
  • a user-related event is a delivery event of a user order.
  • the three-party application is Ant Forest
  • user-related events are events that generate green energy in the user's Ant Forest.
  • the three-party application is Oriental Fortune
  • user-related events are related events of stocks that users follow.
  • the mobile phone can preset the call interface of the authorization code of the mobile phone user account (such as Huawei user account) in the system for the quick app, and the quick app obtains the authorization code of the mobile user account through the interface, and then according to the authorization code Obtain the OpenID corresponding to the mobile phone user account.
  • the application needs to integrate the mobile user account management SDK before calling the SDK to obtain the authorization code of the mobile user account, and then obtain the OpenID corresponding to the mobile user account according to the authorization code.
  • the user account of the mobile phone is shared with one negative screen.
  • the authorization code and OpenID of the mobile phone user account need to be obtained through the SDK integrated in the quick app or the third-party app.
  • the authorization code and OpenID of the one-screen user account need to be obtained through the SDK integrated in the quick app or the third-party app.
  • a third-party application can develop an installation package of a native third-party application (for example, an Android package (APK)), and the third-party application and a negative one-screen user account can be connected in the installation package of the native third-party application.
  • Binding function This method requires the integration of a negative one-screen account management SDK in the installation package of the native third-party application.
  • the negative one-screen account management SDKs of different device manufacturers are different.
  • the installation package of the native third-party application needs to integrate multiple account management SDKs of different device manufacturers. This will make the installation package of the native third-party application larger, which will lead to the tripartite application.
  • the application occupies too much mobile phone memory, the user needs more traffic when downloading, the download process is slow, and the running process will take up more resources, and the user experience is poor. Therefore, this method is usually not adopted by third-party applications. .
  • the tripartite application side has developed a tripartite quick application.
  • fast apps can also be called JavaScript applets.
  • FIG. 1A and FIG. 1B the user has logged in the user account of the negative one screen, and the user account binding the negative one screen to the third-party application is triggered.
  • a negative screen pulls up the three-party app, and the three-party app provides a login page (or account binding page) for users to enter the account of the three-party app.
  • the Ssweeping Express application calls the Open Authorization (OAUTH) account management SDK to obtain the user's avatar, nickname, authorization code and other information.
  • OAUTH Open Authorization
  • the three-party app obtains the user account of the three-party application entered by the user, and submits the account binding information to the three-party server.
  • the account binding information carries the user's authorization code and the user account of the third-party application.
  • the three-party server calls the negative one-screen account management server interface to obtain the user's access token AccessToken through the authorization code, and obtain the user's OpenID through the AccessToken, that is, to obtain the negative one-screen user account Corresponding OpenID, thereby establishing the binding relationship between the user account of the three-party application and the OpenID, that is, establishing the binding relationship between the user account of the three-party application and the user account of the negative one screen.
  • the three-party application side needs to develop the three-party quick app, develop the three-party quick app’s login page based on the quick app, and call the negative one-screen account management SDK in the three-party quick app.
  • the authorization code corresponding to the user account of the negative one screen and then obtain the complicated development work such as OpenID, so as to realize the binding of the user account of the third party application and the user account of the negative one screen through OpenID.
  • OpenID complicated development work
  • the developers of the third-party application usually cannot grasp the development process of the fast application, and the call interface of the negative one-screen account management SDK corresponding to different device manufacturers It is different from the calling method, so the development work is more difficult; the cost of the three-party application and the negative one-screen account binding process is higher, and the binding process is more complicated, which is not conducive to the large-scale introduction of the negative one screen of the electronic device to the three-party application.
  • the embodiment of the present application provides an account binding method, which can be applied to the account management system 01 shown in FIG. 2.
  • the account management system 01 includes an electronic device 10, and the electronic device 10 includes a first application and a second application. Among them, the second application is a three-party application different from the first application.
  • the account management system 01 also includes a server 20 of the first application, a three-party server 30, and an account management server 40.
  • the account management server 40 is used to manage user accounts of the first application. Among them, the three-party application and the first application do not use the same user account.
  • the user account of the three-party application and the user account of the first application correspond to different account management systems.
  • the three-party server is the server of the three-party application, that is, the server of the aforementioned second application. After the user account of the third-party application is bound to the user account of the first application, the first application can display user-related events recommended by the third-party application.
  • the first application can call the account management SDK of the first application, obtain the OpenID corresponding to the user account of the first application from the account management server, and add OpenID is sent to the third party server.
  • the third-party server returns the OpenID as a parameter of the login page of the third-party application to the first application.
  • the first application pulls the login page of the third-party application with OpenID parameters.
  • the three-party server may establish a binding relationship between the user account of the three-party application and the OpenID, that is, the binding relationship between the user account of the three-party application and the user account of the first application.
  • the user account may also be referred to as an account for short.
  • the user account can include a user name and password.
  • the user name can be a mobile phone number, email address, character string or nickname, etc.
  • the first application can apply for and obtain the OpenID corresponding to the user account of the first application in place of the three-party application, so as to establish the binding relationship between the user account of the three-party application and the OpenID, that is, to establish the three-party application.
  • the binding relationship between the user account of the application and the user account of the first application can apply for and obtain the OpenID corresponding to the user account of the first application in place of the three-party application, so as to establish the binding relationship between the user account of the three-party application and the OpenID, that is, to establish the three-party application.
  • the three-party application does not need to develop the three-party express application in order to achieve the binding, nor does it need to specifically develop a login page based on the three-party express application in order to realize the binding, and does not need to call the account management SDK of the first application in the three-party express application .
  • To obtain the OpenID and other complex development work corresponding to the user account of the first application which can simplify the development process of the third party application, reduce the development workload of the third party application, simplify the account binding process of the third party application and the first application, and reduce the three-party application development process.
  • the application’s account binding cost improves the efficiency and flexibility of account binding; thereby facilitating the cooperation between the three-party application and the first application and expanding the cooperation group of the first application.
  • the third-party application does not need to integrate the account management SDK of the first application.
  • the first application is a negative screen, that is, a negative screen is an application.
  • One screen negative can obtain the OpenID corresponding to the user account of one negative screen, so as to establish the binding relationship between the user account of the third party application and the OpenID, that is, the binding relationship between the user account of the third party application and the user account of the negative one screen.
  • the negative one screen can replace the three-party application to apply for and obtain the OpenID corresponding to the user account of the negative one
  • the login page of the application does not need to call the negative one-screen account management SDK in the Ssweeping Express application to obtain the authorization code corresponding to the negative one-screen user account and then obtain the complicated development work such as OpenID, thus simplifying the development process of the three-party application , Reduce the workload of the development of three-party applications, simplify the process of binding three-party applications and negative one-screen accounts, reduce the cost of account binding for target three-party applications, and improve the efficiency and flexibility of account binding.
  • the electronic device may specifically be a mobile phone, a tablet computer, a vehicle-mounted device, a notebook computer, a smart screen, a wearable device, an augmented reality (AR)/virtual reality (VR) device, a super mobile personal computer (
  • AR augmented reality
  • VR virtual reality
  • UMPC ultra-mobile personal computer
  • PDA personal digital assistant
  • FIG. 4 shows a schematic structural diagram of the electronic device 100.
  • the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2.
  • the sensor module 180 may include a touch sensor, a pressure sensor, a gyroscope sensor or an acceleration sensor, etc.
  • the processor 110 may include one or more processing units.
  • the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) Wait.
  • AP application processor
  • modem processor modem processor
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • controller memory
  • video codec digital signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • the different processing units may be independent devices or integrated in one or more processors.
  • the controller may be the nerve center and command center of the electronic device 100.
  • the controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.
  • a memory may also be provided in the processor 110 to store instructions and data.
  • the memory in the processor 110 is a cache memory.
  • the memory can store instructions or data that the processor 110 has just used or used cyclically. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated accesses are avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.
  • the processor 110 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, and a universal asynchronous transmitter/receiver (universal asynchronous) interface.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transmitter/receiver
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB Universal Serial Bus
  • the external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example, save music, video and other files in an external memory card.
  • the internal memory 121 may be used to store computer executable program code, and the executable program code includes instructions.
  • the processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121.
  • the internal memory 121 may include a storage program area and a storage data area.
  • the storage program area can store an operating system, at least one application program (such as a sound playback function, an image playback function, etc.) required by at least one function.
  • the data storage area can store data (such as OpenID, audio data, phone book, etc.) created during the use of the electronic device 100.
  • the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), and the like.
  • UFS universal flash storage
  • the internal memory 121 may store the account management SDK of the first application.
  • the processor 110 may call the account management SDK of the first application to obtain the authorization code and OpenID of the first application.
  • the internal memory 121 may store the code of the first application.
  • the processor 110 runs the code of the first application, so that the first application obtains the OpenID corresponding to the user account of the first application in the account binding scenario, so as to establish the binding relationship between the user account of the third-party application and the OpenID, that is, to establish the third-party application The binding relationship between the user account of and the user account of the first application.
  • the USB interface 130 is an interface that complies with the USB standard specification, and specifically may be a Mini USB interface, a Micro USB interface, a USB Type C interface, and so on.
  • the USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect earphones and play audio through earphones. This interface can also be used to connect to other electronic devices, such as AR devices.
  • the charging management module 140 is used to receive charging input from the charger.
  • the charger can be a wireless charger or a wired charger.
  • the power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110.
  • the power management module 141 receives input from the battery 142 and/or the charge management module 140 and supplies power to other modules of the electronic device 100.
  • the power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, and battery health status (leakage, impedance).
  • the mobile communication module 150, the wireless communication module 160 or the USB interface 130 and other communication interfaces can be used for the electronic device 100 to communicate with the first application server or the third-party application server or the account management server to interact with OpenID and the login card object of the third-party application Or information such as the address of the login page.
  • the interface connection relationship between the modules illustrated in the embodiment of the present application is merely a schematic description, and does not constitute a structural limitation of the electronic device 100.
  • the electronic device 100 may also adopt different interface connection modes in the foregoing embodiments, or a combination of multiple interface connection modes.
  • the wireless communication function of the electronic device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.
  • the antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in the electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.
  • Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network.
  • the antenna can be used in combination with a tuning switch.
  • the mobile communication module 150 can provide a wireless communication solution including 2G/3G/4G/5G and the like applied to the electronic device 100.
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.
  • the mobile communication module 150 can receive electromagnetic waves by the antenna 1, and perform processing such as filtering, amplifying and transmitting the received electromagnetic waves to the modem processor for demodulation.
  • the mobile communication module 150 can also amplify the signal modulated by the modem processor, and convert it into electromagnetic wave radiation via the antenna 1.
  • at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110.
  • at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.
  • the wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), and global navigation satellites.
  • WLAN wireless local area networks
  • BT wireless fidelity
  • GNSS global navigation satellite system
  • FM frequency modulation
  • NFC near field communication technology
  • infrared technology infrared, IR
  • the wireless communication module 160 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110.
  • the wireless communication module 160 may also receive the signal to be sent from the processor 110, perform frequency modulation, amplify it, and convert it into electromagnetic waves to radiate through the antenna 2.
  • the antenna 1 of the electronic device 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology.
  • Wireless communication technologies can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), and broadband code division. Multiple access (wideband code division multiple access, WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM , And/or IR technology, etc.
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • CDMA code division multiple access
  • CDMA broadband code division. Multiple access (wideband code division multiple access, WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM , And/or IR technology, etc.
  • GNSS can include global positioning system (GP
  • the camera 193 is used to capture still images or videos.
  • the object generates an optical image through the lens and is projected to the photosensitive element.
  • the photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the optical signal into an electrical signal, and then transfers the electrical signal to the ISP to convert it into a digital image signal.
  • ISP outputs digital image signals to DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV and other formats of image signals.
  • the electronic device 100 may include one or N cameras 193, and N is a positive integer greater than one.
  • the display screen 194 is used to display images, videos, and the like.
  • the display screen 194 includes a display panel.
  • the display panel can use liquid crystal display (LCD), organic light-emitting diode (OLED), active matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode).
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • active-matrix organic light-emitting diode active-matrix organic light-emitting diode
  • AMOLED flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (QLED), etc.
  • the electronic device 100 may include one or N display screens 194, and N is a positive integer greater than one.
  • the display screen 194 may display interfaces such as a negative one-screen home page, a login page of a three-party application, or a page in the account binding process.
  • the audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a digital audio signal.
  • the audio module 170 can also be used to encode and decode audio signals.
  • the audio module 170 may detect the user's voice signal, and use it as a voice command to control the electronic device 100 to perform operations such as account binding or login.
  • the touch sensor in the sensor module 180 is also called a “touch panel”.
  • the touch sensor may be provided on the display screen 194, and the touch screen is composed of the touch sensor and the display screen 194, which is also called a “touch screen”.
  • the touch sensor is used to detect touch operations acting on or near it.
  • the touch sensor can pass the detected touch operation to the application processor to determine the type of touch event.
  • the visual output related to the touch operation can be provided through the display screen 194.
  • the touch sensor may also be disposed on the surface of the electronic device 100, which is different from the position of the display screen 194.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100.
  • the electronic device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components.
  • the illustrated components can be implemented in hardware, software, or a combination of software and hardware.
  • the display screen 194 may display interfaces such as a negative one-screen home page, a login page of a three-party application, or a page in the account binding process.
  • the internal memory 121 may store the code of the first application and the account management SDK of the first application.
  • the processor 110 runs the code of the first application, so that in the account binding scenario, the first application calls the account management SDK of the first application to obtain the OpenID corresponding to the user account of the first application, so as to establish the user account of the third-party application and
  • the binding relationship of OpenID is to establish the binding relationship between the user account of the third-party application and the user account of the first application.
  • the three-party application does not need to develop the three-party quick application, nor does it need to specifically develop a login page based on the three-party quick application, and does not need to call the account management SDK of the first application in the three-party quick application to obtain the corresponding user account of the first application
  • Complex development work such as OpenID can simplify the development process of third-party applications, reduce the development workload of third-party applications, simplify the account binding process of third-party applications and the first application, reduce the cost of account binding for third-party applications, and increase account binding Efficiency and flexibility.
  • the electronic device in the account management system shown in FIG. 2 is a mobile phone with the structure shown in FIG. 4, and the first application is a negative screen on the mobile phone as an example, to describe the account binding method provided in the embodiment of the present application.
  • the negative screen is an application on the mobile phone.
  • the operations, steps or functions performed by the negative screen are implemented by calling the functional modules or components in the mobile phone by the negative screen.
  • operations, steps, or functions performed by a negative screen can also be understood as operations, steps, or functions performed by a mobile phone.
  • the mobile phone can log in to a user account with a negative screen.
  • the negative one screen After detecting the operation of associating the target third-party application with the negative one screen by the user, the negative one screen can obtain the OpenID corresponding to the negative one screen user account, and send the OpenID to the negative one screen server.
  • the one-screen negative server can send the OpenID to the three-party server of the target three-party application, so that the three-party server binds the user account of the target three-party application with the OpenID, that is, binds the user account of the target three-party application with the user account of the negative one-screen.
  • the three-party server can notify the negative one-screen server.
  • the negative one screen can obtain the account binding success information from the negative one screen server.
  • the user account information of the target third-party application can also be obtained.
  • the negative one screen may obtain the login page information of the target third-party application from the negative one screen server, and the login page information includes OpenID.
  • Negative screen can display the login page of the target third-party application according to the login page information.
  • the negative one screen device can send the user account of the second application entered by the user to the third-party server together with the OpenID.
  • the three-party server can push the user-related event to the negative one screen after generating the user-related event related to the user account of the negative one screen corresponding to the OpenID.
  • the negative screen can prompt the user of the user-related event in the form of a card or the like.
  • the specific process of the account binding method provided in the embodiment of the present application may include:
  • the mobile phone displays a negative one-screen home page.
  • the mobile phone displays a negative one screen home page on the screen.
  • the screen can be a display screen or a touch screen composed of a display screen and a touch sensor.
  • the negative one-screen main page is usually the leftmost page of the desktop, which can provide users with notifications or quick use of services such as search, news, sports health, life services, historical applications, or application recommendations.
  • the user can swipe to the right on the mobile phone desktop; in response to the user's sliding to the right, the mobile phone can move the display desktop to the left until the leftmost The desktop, that is, the main page with one screen negative.
  • the user account of the negative one screen is usually consistent with the user account of the mobile phone. For example, if the device manufacturer of the mobile phone is Huawei, the user account with one screen negative is usually a Huawei account; if the device manufacturer of the mobile phone is Apple, the user account with one screen negative is usually an Apple account.
  • the mobile phone If the mobile phone has not logged in to the user account with one screen before, the user can click the avatar control in the upper left corner of the page shown in Figure 7 to log in to the user account with one screen. In some embodiments, if the mobile phone has logged in to the user account of the mobile phone before, the mobile phone automatically logs in to the user account of the negative one screen.
  • a negative screen detects a user's preset operation 1 for the target three-party application.
  • the target tripartite application is another application different from the negative one.
  • the target third-party application may specifically be an application (application, APP), an application applet, a quick application, or other forms of applications.
  • the target third-party application and the negative screen do not use the same user account, and correspond to different account management systems. For example, when a Huawei account is used for a negative screen, the target third-party application does not use the Huawei account.
  • the detection of the user's operation on the negative screen can be understood as the mobile phone detects the user's operation through detection components such as touch sensors, cameras, or microphones and notifies the negative screen.
  • the user may have multiple operation modes for the preset operation 1 of the target three-party application, such as touch operation mode, voice command mode, or air-space operation mode.
  • the target three-party application can be Ant Forest, Oriental Fortune, Microsoft Xiaoice or Smart Life, etc.
  • the negative one screen detects that the user clicks on the avatar control on the negative one screen homepage as shown in Figure 8 (a)
  • the negative one shown in Figure 8 (b) is displayed.
  • the function page of the screen After the negative screen detects that the user clicks on the "scene intelligence" control as shown in (b) in FIG. 8, the application list as shown in (c) in FIG. 8 is displayed.
  • the user's preset operation 1 for the target third-party application may include the operation of the user clicking the avatar control on the homepage of one screen, the user clicking the "contextual intelligence" control on the function page, and the user clicking the application list The operation of the ">" control corresponding to the target third-party application (for example, Eastern Fortune) in.
  • the user's preset operation 1 for the target third-party application may be the user clicking on the ">" control corresponding to the target third-party application (for example, Oriental Fortune) in the application list.
  • the negative screen can also detect the operation of the user clicking the avatar control on the homepage of the negative screen, or the user clicking the "scene intelligence" control on the function page and other operations.
  • the preset operation 1 may be an operation in which a user's voice instruction is detected in a negative screen to open the subscription page of the target three-party application.
  • the negative screen displays an associated page of the target third-party application, and the associated page indicates that the negative screen is not bound to the target third-party application.
  • the associated page corresponding to the target third-party application can be displayed.
  • the associated page may refer to (a) in FIG. 9 or (b) in FIG. 9.
  • the association page indicates that the user account of the current target third-party application is not bound to the user account of the negative one screen.
  • the negative screen is a platform application, which can load and display the interface of the third-party application, for example, display the associated page of the target third-party application.
  • the interface of the third party application displayed on the negative one screen can be understood as the interface of the third party application is loaded on the negative one screen and displayed on the mobile phone screen.
  • step 504 the method may further include step 505:
  • the negative screen detects the user's instruction to open the target third-party application, and displays the interface of the target third-party application.
  • the interface of the target third-party application can be displayed to enter the target third-party application.
  • the target third-party application can be opened and the target shown in Figure 10 is displayed. The interface of the third party application.
  • the method may further include the following steps:
  • the user's preset operation 2 is detected on a negative screen.
  • the preset operation 2 is used to instruct to associate the target three-party application with the negative one screen, and is used to trigger the binding of the user account of the target three-party application with the negative one screen user account. After the preset operation 2 is detected in the negative screen, the process of binding the target three-party application and the negative screen account is initiated.
  • the preset operation 2 may be an operation for the user to turn on the "subscribe" switch 901 on the associated page shown in (a) of FIG. 9 and click the ">” control 902 after "unbound".
  • the target third-party application can be subscribed, that is, the target third-party application can be enabled on the negative screen; the ">" control after the user is detected to click "unbound”
  • the account binding process is initiated.
  • the preset operation 2 may be an operation of the user clicking the "subscribe and bind" control 903 on the associated page shown in (b) in FIG. 9. After the negative screen detects the preset operation 2, the account binding process is initiated.
  • the mobile phone may not have logged in to the user account of the negative one screen, that is, the mobile phone may not perform step 502 before step 506. If the mobile phone determines after step 506 that the user account with a negative screen has not been logged in, it can log in first, and then perform step 507 and subsequent steps.
  • One screen negative obtains the OpenID corresponding to the user account of one screen negative from the account management server.
  • the account management server with one screen negative is the OAuth account management server.
  • One screen negative can call the SDK of the negative one screen OAuth account management, and obtain the OpenID corresponding to the negative one screen user account from the negative one screen OAuth account management server.
  • the negative screen and the mobile phone share the same user account, that is, the negative screen can obtain the OpenID corresponding to the mobile phone user account from the OAuth account management server of the mobile phone user account.
  • the negative screen can obtain the identity information of the target third-party application, such as the application identity document (AppId) of the target third-party application, or the application name of the target third-party application. Take the example that the identity information of the target third-party application is AppId.
  • One screen negative can call the SDK for OAuth account management in the mobile phone, pass the AppId of the target third-party application to the OAuth account management server, and apply to the OAuth account management server to obtain the OpenID corresponding to the user account of the negative one screen.
  • the OAuth account management server generates the OpenID corresponding to the one-screen user account according to the AppId of the target third-party application, and returns the OpenID to the one-screen negative.
  • the negative one screen can be obtained.
  • the negative one screen can be obtained.
  • the OpenID corresponding to the negative one screen user account can be obtained for subsequent account binding based on the OpenID; the target third-party application does not need to develop a three-party quick application, nor does it need to be used in a three-party quick application
  • Simplify the account binding process between the target third-party application and the negative one screen reduce the account binding cost of the target third-party application, and improve the efficiency and flexibility of account binding.
  • One screen negative sends account authorization information to the negative one screen server, where the account authorization information includes the OpenID and the identity information of the target third-party application.
  • the account authorization information is used to indicate that the user indicates to bind the user account of the target third-party application with the user account of one screen, that is, the user indicates to bind the user account of the target third-party application with the OpenID; or, it is used to indicate that the user uses the OpenID Authorized to the target third-party application; or, used to indicate that the user authorizes the one-screen server to provide the OpenID to the target third-party application; or, used to indicate that the user is authorized to bind the user account of the target third-party application with the OpenID.
  • One-screen negative obtains login page information of the target three-party application through the one-screen negative server, where the login page information includes OpenID.
  • the login page information of the target third-party application is used to obtain the login page of the target third-party application by one screen.
  • the login page may be as shown in (a) in FIG. 11 or (b) in FIG. 11.
  • Negative One Screen does not call the Negative One Screen Account Management SDK to obtain user information such as the user's avatar and nickname when displaying the login page of the target third-party application.
  • the login page of the target third-party application may not display user information such as user avatars or nicknames.
  • the negative screen displays the login page of the target three-party application according to the login page information.
  • the login page information of the target third-party application includes the OpenID corresponding to the user account of the negative one screen.
  • a negative screen detects the user account of the target three-party application input by the user.
  • the login page of the target third-party application is displayed on the negative screen, and the user can enter the user name and password of the target third-party application on the login page of the target third-party application displayed on the negative screen.
  • the user account and OpenID of the target third-party application are sent to the third-party server.
  • the account binding information can be sent to the third-party server.
  • the account binding information includes the user account and the user account of the target third-party application. OpenID.
  • the operation 3 may be an operation in which the user clicks the "verify and bind" control on (a) in FIG. 11 or (b) in FIG. 11.
  • the login page of the target third-party application includes a "login and bind” control
  • operation 3 may be an operation for the user to click the "login and bind” control.
  • the login page of the target third-party application includes an "OK” control
  • operation 3 may be an operation of the user clicking the "OK” control.
  • the three-party server binds the user account and OpenID of the target three-party application after the user account of the target three-party application sent by the negative one screen is verified.
  • the login page information obtained in step 509 for one screen includes OpenID, that is, the login page is bound with OpenID.
  • the negative screen displays the login page according to the login page information and obtains the account of the target third-party application entered by the user, the user account of the target third-party application and the OpenID corresponding to the user account of the negative one screen can be submitted to the third-party server. , So that the third-party server can bind.
  • the OpenID corresponding to the user account of the negative one screen can be obtained by the negative one screen, and the three-party server binds the user account of the target three-party application according to the OpenID.
  • the target third-party application does not need to develop the third-party quick application, nor does it need to call the negative one-screen account management SDK in the three-party quick application to obtain the authorization code corresponding to the negative one-screen user account to obtain complex development work such as OpenID.
  • step 514 the method may further include step 514:
  • a negative screen displays the login success page of the target third-party application.
  • the third-party server determines that the target third-party application is successfully logged in, and prompts the user to log in successfully through the login interface.
  • the interface displayed on the negative one screen prompts the user to log in successfully, that is, the negative one screen displays the login success page of the target third-party application.
  • the interface of successful login of the target third-party application can be seen in (a) or (b) in FIG. 12 above.
  • the method may further include:
  • the three-party server notifies the negative one-screen server that the account is bound successfully.
  • the three-party server may push the message that the account is successfully bound to the negative one-screen server, and the message of the successful binding may include the OpenID.
  • the message that the account is successfully bound may also include the user account of the target third-party application.
  • Negative screen obtains information about successful account binding from the negative one screen server.
  • the information that the account is successfully bound is used to indicate that the third-party server has successfully bound the user account of the negative one screen with the user account of the target third-party application.
  • the negative one screen can periodically query the negative one screen server for binding information, so as to know that the user account of the target three-party application is successfully bound with the negative one screen user account.
  • the negative one screen can receive the message pushed by the negative one screen server, thereby knowing that the user account of the target three-party application is successfully bound with the negative one screen user account.
  • the binding success page is displayed on a negative screen.
  • the binding success page indicates that the negative screen has been bound to the target third-party application. For example, after a negative screen detects that the user clicks on the "done" control shown in Figure 12 (a) or Figure 12 (b), it can display the one shown in Figure 12 (c), which means a negative screen
  • the binding success page that has been bound to the user account of the target third-party application.
  • the three-party server pushes user-related events to the negative one screen corresponding to OpenID according to the binding relationship.
  • the three-party server When the three-party server generates a user-related event, it pushes the user-related event to the negative one screen corresponding to the OpenID in the binding relationship, thereby recommending the user-related event to the user through the negative one screen.
  • a negative screen can receive user-related events pushed by three-party servers.
  • One screen negative displays user-related events recommended by the target three-party application on the home page of one negative screen.
  • the three-party server can push user-related events to the negative one screen corresponding to OpenID based on the binding relationship, that is, recommend events that the user cares about in the target three-party application to the negative one screen.
  • the negative one screen can show the user-related events to the user in the form of cards, etc., so that the user can timely understand the relevant information of the target third-party application that he is concerned about.
  • the user-related event may be a delivery event of the user's order. If the target third-party application is an ant forest, the user-related event may be an event that generates green energy in the user's ant forest. If the target three-party application is Oriental Fortune, the user-related event is an event related to the stock that the user pays attention to. Exemplarily, if the user-selected stocks that the user pays attention to in the target three-party application Oriental Fortune includes BOE A, the negative one-screen main page used to display user-related events can be seen in Figure 13 (a) or Figure 13 ( b).
  • the target third-party application can send OpenID
  • the corresponding negative one-screen recommendation general events are displayed on the negative one-screen main page.
  • the target tripartite application is Oriental Fortune
  • the general event is stock market information.
  • the three-party server may also recommend a general event to the negative one screen and display it on the negative one screen homepage.
  • the card used for displaying recommended general events on a negative screen may further include a control 1401 for account binding. After the negative screen detects that the user clicks on the control 1401, the above step 507 and the subsequent account binding process can be executed.
  • the login page of the target third-party application can have various forms, and steps 509 to 510 can also correspond to different implementations, which are described below by examples.
  • the login page of the target third-party application is the login card.
  • the login page of the target third-party application during binding can be preset to the card mode, and the login page information is the login card object.
  • the login card is preset on the negative one-screen server.
  • the foregoing step 509 may include:
  • the negative one screen server determines that the login page is in the card mode, and sends the login card object corresponding to the target three-party application to the negative one screen.
  • the parameters of the login card object include OpenID.
  • the negative one-screen server can determine the login card object corresponding to the target three-party application according to the identity information of the target three-party application.
  • the login card object includes parameters, which are used to describe the features or functions of the login card.
  • the negative one screen server can add OpenID to the parameters of the login card object, thereby sending the OpenID together with the login card object to the negative one screen.
  • the login card may be described by JavaScript code
  • the login card object may be the download address of the login card JavaScript code and the corresponding parameters.
  • One screen negative receives a login card object sent by a negative one screen server, and the parameters of the login card object include OpenID.
  • the foregoing step 510 may include:
  • the negative screen displays the login card according to the login card object.
  • the negative one screen may display the login card as shown in (a) in FIG. 16 or (b) in FIG. 16.
  • the login card is not developed based on the three-party quick application.
  • the login card is preset on a three-party server.
  • the negative one-screen server calls the three-party server interface in real time, and sends the OpenID to the three-party server.
  • the three-party server adds OpenID to the parameters of the login card, and sends the login card object after adding OpenID to the negative one screen server; the negative one screen server forwards the login card object after adding OpenID to the negative one screen.
  • the login card is preset on a three-party server.
  • the negative one-screen server calls the three-party server interface in real time to obtain the download path of the login card; the negative one-screen server adds OpenID to the download path of the login card, and adds the download path of the login card after adding OpenID. Forward to a negative screen.
  • the negative one-screen server may also be uncertain whether the login page of the target third-party application is the card mode or the page mode, and the login page mode of the target third-party application is determined by the third-party server.
  • the negative one-screen server can request the third-party server to obtain the login page information of the target third-party application.
  • the third-party server determines that the login page of the target third-party application is in card mode, it will add OpenID to the download path of the login card and return to the negative one server.
  • the negative one screen server returns the download path of the login card after adding OpenID to the negative one screen.
  • the login card is a static resource. Taking into account the instability and time delay of the network status, compared with presetting the login card on the three-party server, the login card is preset on the negative one-screen server.
  • the device manufacturer of the mobile phone Processing such as acceleration can be performed, so the performance and reliability are higher.
  • the parameters of the login card object returned by the negative one screen server to the negative one screen in step 1501a include OpenID, that is, the login page is bound with OpenID.
  • the negative one screen displays the login page according to the login card object and obtains the account of the target third-party application entered by the user, the user account and OpenID of the target third-party application can be submitted to the third-party server so that the third-party server can bind the account. .
  • the OpenID corresponding to the user account of the negative one screen can be obtained for the negative one screen, and the binding relationship between the user account of the target third party application and the OpenID is established based on the preset login card of the target third party application. That is, the binding relationship between the user account of the target third-party application and the user account of the negative one screen is established.
  • the login card is not developed based on the three-party quick application.
  • the target three-party application does not need to develop a three-party express application for account binding, nor does it need to specifically develop a login page based on the three-party express application for account binding, and does not need to be in the three-party express application.
  • Call the account management SDK of the negative one screen to obtain the authorization code corresponding to the user account of the negative one screen, and then obtain the complicated development work such as OpenID, which can simplify the development process of the target third-party application, reduce the development workload of the target third-party application, and simplify The process of binding the target third-party application to one-screen accounts reduces the cost of account binding of the target third-party application, and improves the efficiency and flexibility of account binding.
  • the login page of the target third-party application is the 5th generation hypertext markup language H5 login page.
  • the login page of the target third-party application during binding can be preset to page mode, and the login page information is the address of the spliced H5 login page.
  • the foregoing step 509 may include:
  • the negative one-screen server determines that the login page is in page mode, and sends account authorization information to the three-party server, where the account authorization information includes the OpenID.
  • the negative one-screen server may determine the three-party server according to the identity information of the target three-party application received from the negative one, so as to send the OpenID to the three-party server.
  • the account authorization information sent by the negative one-screen server to the third-party server includes OpenID; and may include the identity information of the target third-party application, or may not include the identity information of the target third-party application.
  • the three-party server determines that it supports the H5 login page of the target three-party application, it splices the address of the OpenID and the H5 login page, and returns the address of the spliced H5 login page to the negative one-screen server.
  • the H5 login page address may be the address of an existing login page of the target third-party application, for example, may be the HTTP address of the login page.
  • the binding process can reuse the existing H5 login page, without the need for the target third-party application to specifically design a login page for account binding.
  • OpenID can be spliced after, before, or within the address of the H5 login page.
  • the third-party server can splice OpenID into the address of the H5 login page. Subsequently, the third-party server can provide the H5 login page of the target third-party application according to the address of the spliced H5 login page.
  • Negative screen receives the address of the spliced H5 login page sent by the negative one screen server.
  • the foregoing step 510 may include:
  • One Negative Screen sends H5 login page request information to the three-party server, and the request information includes OpenID.
  • One screen calls the address of the spliced H5 login page to request the third-party server to obtain the H5 login page of the target third-party application.
  • the negative screen receives the content of the H5 login page sent by the three-party server, and displays the H5 login page.
  • the three-party server returns the content of the H5 login page to the negative screen, and loads the H5 login page with a web browser on the negative screen, and the user can see the H5 login page on the screen.
  • the H5 login page can display information such as the user name and password input box provided by the target third-party application to the user.
  • the H5 login page may refer to (a) in FIG. 11 or (b) in FIG. 11, and the H5 login page is not a page developed based on the three-party quick application.
  • the OpenID corresponding to the user account of the negative one screen can be obtained for the negative one screen, and the existing H5 login page of the target third-party application can be reused to establish the binding relationship between the user account of the target third-party application and OpenID , That is, the binding relationship between the user account of the target third-party application and the user account of the negative one screen is established.
  • the H5 login page is an existing page, not a page developed based on the three-party quick application.
  • the target three-party application does not need to develop a three-party express application for account binding, nor does it need to specifically develop a login page based on the three-party express application for account binding, and does not need to be in the three-party express application.
  • Call the account management SDK of the negative one screen to obtain the authorization code corresponding to the user account of the negative one screen, and then obtain the complicated development work such as OpenID, which can simplify the development process of the target third-party application, reduce the development workload of the target third-party application, and simplify The process of binding the target third-party application to one-screen accounts reduces the cost of account binding of the target third-party application, and improves the efficiency and flexibility of account binding.
  • the login page of the target third-party application is the native application login page, that is, the login page of the native target third-party application.
  • the login page information is the address of the spliced native application login page, such as the spliced native application login The DeepLink address of the page.
  • the foregoing step 509 may include:
  • the negative one-screen server determines that the login page is in page mode, and sends account authorization information to the three-party server, where the account authorization information includes the OpenID.
  • the negative one-screen server may determine the three-party server according to the identity information of the target three-party application received from the negative one, so as to send the OpenID to the three-party server.
  • the account authorization information sent by the negative one-screen server to the third-party server includes OpenID; and may include the identity information of the target third-party application, or may not include the identity information of the target third-party application.
  • the third-party server determines that it supports the native application login page of the target third-party application, it splices the OpenID and the DeepLink address of the native application login page, and returns the DeepLink address of the spliced native application login page to the negative one-screen server.
  • the third-party server can splice OpenID into the DeepLink address of the native application login page. Subsequently, the third-party server can provide the native application login page of the target third-party application according to the DeepLink address of the spliced native application login page.
  • Negative screen receives the DeepLink address of the spliced native application login page sent by the negative one screen server.
  • the foregoing step 510 may include:
  • Negative screen displays the native application login page according to the DeepLink address of the spliced native application login page.
  • a negative screen can pull up the native application login page according to the DeepLink address of the spliced native application login page.
  • the native application login page here refers to the login page of the native target third-party application.
  • the native application login page may refer to the page shown in Figure 11 (a) or Figure 11 (b), and the login page is not a page developed based on the three-party quick application.
  • one screen negative can obtain the OpenID corresponding to the user account of the negative one screen, and reuse the existing native application login page of the target third-party application to establish a binding between the user account of the target third-party application and OpenID
  • the relationship is to establish a binding relationship between the user account of the target third-party application and the user account of the negative one screen.
  • the native application login page is an existing page, not a page developed based on the Sggling Express application.
  • the target three-party application does not need to develop a three-party express application for account binding, nor does it need to specifically develop a login page based on the three-party express application for account binding, and does not need to be in the three-party express application.
  • Call the account management SDK of the negative one screen to obtain the authorization code corresponding to the user account of the negative one screen, and then obtain the complicated development work such as OpenID, which can simplify the development process of the target third-party application, reduce the development workload of the target third-party application, and simplify The process of binding the target third-party application to one-screen accounts reduces the cost of account binding of the target third-party application, and improves the efficiency and flexibility of account binding.
  • the login page of the target third-party application is the quick application login page of the target third-party application.
  • the corresponding processing flow in this case is similar to the above case (3), except that the address of the login page of the native application is replaced with the address of the quick application login page of the target third-party application.
  • the DeepLink address of the login page of the native application is replaced with the DeepLink address of the quick application login page.
  • the third-party server can splice OpenID to the DeepLink address of the quick app login page, and return the DeepLink address of the spliced quick app login page to the negative one screen, so that the negative one screen displays the quick app login page.
  • the quick application login page may refer to the page shown in FIG. 11(a) or FIG. 11(b).
  • the login page of the fast app is a login page developed based on the three party fast app, but the existing login page of the target three party app is not a login page specially designed for the account binding process, so it is not intended to be a negative screen. Binding and binding increase the additional development process and development workload of the target third-party application.
  • a negative screen can obtain the OpenID corresponding to the user account of the negative screen, and reuse the existing fast application login page of the target third-party application to establish the binding relationship between the user account of the target third-party application and the OpenID, that is, establish the target The binding relationship between the user account of the third-party application and the user account of the negative one screen.
  • the quick app login page is an existing page, not a page developed based on the three party quick app.
  • the target tripartite application does not need to develop a tripartite app for account binding, nor does it need to specifically develop a login page based on the tripartite app for account binding, and does not need to be called in the tripartite app.
  • the negative one-screen account management SDK can obtain the authorization code corresponding to the negative one-screen user account to obtain complex development work such as OpenID, which can simplify the development process of the target third-party application, reduce the development workload of the target third-party application, and simplify the target
  • the three-party application and negative one-screen account binding process reduces the account binding cost of the target three-party application and improves the efficiency and flexibility of account binding.
  • the address of the spliced login page returned by the third-party server to the negative one-screen server in step 1502b or step 1502c includes OpenID, that is, the login page is bound with OpenID.
  • the negative one screen subsequently obtains the account of the target third-party application entered by the user by displaying the login page, the user account and OpenID of the target third-party application can be submitted to the third-party server so that the third-party server can bind the account.
  • the account binding method provided by the embodiment of the present application can also refer to (a) in Figure 19; if the negative one-screen server determines that the login page is in page mode, then The process of the account binding method provided by the embodiment of the present application can also refer to (b) in FIG. 19.
  • the negative one-screen server may also be uncertain whether the login page of the target three-party application is in card mode or page mode, and the negative one-screen server may send account authorization information to the three-party server.
  • the pattern of the login page of the target third-party application is determined by the third-party server.
  • step 1502b or step 1502c if the three-party server determines that the login page of the target three-party application is in page mode, it will splice the OpenID into the address corresponding to the supported page type.
  • the supported page types include H5 login page, native application login page, or quick application login page, etc.
  • the third-party server may return the address corresponding to one or more of the page types to the negative one-screen server. For example, different page types have different priorities, and the three-party server may return the address corresponding to the page type with the highest priority to the negative one-screen server. For another example, a three-party server can randomly select an address corresponding to a page type and return it to the negative one-screen server.
  • the account binding method may include some of the steps in the above process. In some other embodiments, the account binding method may further include other steps besides the steps shown in the above process.
  • the login card may also include a jump control for jumping to the H5 login page, the native application login page, or the quick application login page for account login.
  • the jump button may be the control 2001 shown in FIG. 20.
  • the aforementioned account management server, negative one-screen server, or third-party server may be a cloud server or other servers.
  • the OpenID and H5 login page address, the DeepLink address of the native application login page, or the DeepLink address of the quick application login page can be spliced together. It is not performed on the third-party server, but on the negative one-screen server; or the spliced address can be preset on the negative one-screen server.
  • the address splicing method is more flexible, and the address splicing method of different target three-party applications may be different.
  • the third-party server may carry some time-varying parameters in the address to prevent the login page from being replayed and the splicing method is more complicated. Therefore, the method of address splicing by the three-party server is simpler and easier to adapt to the processing methods of three-party applications with different targets.
  • the negative one screen instead of the target third-party application to obtain the OpenID can also be replaced by the negative one-screen server instead of the target third-party application to obtain the OpenID.
  • the negative one-screen instead of the target third-party application to obtain OpenID can interact with the user through the negative one, and obtain OpenID after the user is authorized to bind, which is not easy to violate user privacy The problem.
  • the main page with one screen negative is currently the leftmost screen of the desktop.
  • the negative screen may also be the rightmost screen of the desktop or a page in another location, which is not limited in this embodiment of the application.
  • the first application is the negative screen sharing the same user account with the mobile phone.
  • the first application may also be other applications that share the same user account with the mobile phone, such as system applications. (For example, status bar, etc.), the embodiments of this application will not give examples one by one.
  • the first application may also be an application that does not share the same user account with the mobile phone.
  • the first application may be a platform application such as WeChat or Alipay that can display events recommended by the target third-party application.
  • WeChat can display user-related events recommended by other applications.
  • the OpenID corresponding to the first application is no longer the OpenID assigned by the account management server of the mobile phone, but the OpenID assigned by the account management server corresponding to the first application such as WeChat or Alipay.
  • the target tripartite application may be an application with specific qualifications (such as stocks, medical care, etc.).
  • the solution provided by the embodiments of this application can be applied to the following scenarios: Due to the constraints of qualifications and other factors, the event card displayed on the negative one screen cannot be developed by the mobile phone system and must be developed by the target third-party application. Therefore, the target third-party application needs to be compared with the negative one. The scene of account binding on the screen.
  • the first application may also display user-related events recommended by other applications that share the same user account as the first application, without the need to perform the above account binding process.
  • a negative screen shares a Huawei account with Huawei Video, without the above binding process, and a negative screen can display user-related events recommended by Huawei Video.
  • the first application may also display user-related events recommended by other applications (such as news, etc.) that do not require account binding with the first application.
  • the above description is made by taking the electronic device as a mobile phone as an example.
  • the account binding method provided in the embodiment of the present application can also be applied to other electronic devices such as a tablet or a car, and the embodiment of the present application will not be described in detail.
  • the electronic device includes hardware and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Those skilled in the art can use different methods for each specific application in combination with the embodiments to implement the described functions, but such implementation should not be considered as going beyond the scope of the present application.
  • the electronic device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the electronic device 2100 may include: a display module 2101, a processing module 2102, a communication module 2103, and a storage module 2104.
  • the display module 2101 can be used to support the electronic device 2100 to display a user interface.
  • the display module 2101 can be used to support the electronic device 2100 to perform step 501, step 504, step 505, step 510, step 514, step 517, step 519, etc. in the process shown in FIG. 5, and/or used in the description herein Other processes of the technology.
  • the processing module 2102 may be used to control and manage the actions of the electronic device 2100.
  • the processing module 2102 can be used to support the electronic device 2100 to perform step 502, step 503, step 505, step 506, step 511, step 512, etc. in the flow shown in FIG. Other processes.
  • the communication module 2103 may be used to support communication between the electronic device 2100 and other devices.
  • the communication module 2103 may be used to support the electronic device 2100 to perform step 507, step 508, step 509, step 512, or step 516 in the flow shown in FIG. 5, and/or other processes used in the technology described herein.
  • the storage module 2104 may be used to store instructions and data, for example, store the code of the first application, store the OpenID obtained by the electronic device 2100 through the communication module, and store information such as the user account entered by the user.
  • the display module 2101 may be a display, for example, it may be a display screen 194 in the hardware structure shown in FIG. 4.
  • the processing module 2102 may be a processor or a controller. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, and so on.
  • DSP digital signal processing
  • the processing module 2102 may specifically be the processor 110 in the hardware structure shown in FIG. 4.
  • the communication module 2103 may be a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, and other devices that interact with other electronic devices.
  • the communication module 2103 may include the mobile communication module 150, the wireless communication module 160, the antenna 1 or the antenna 2, etc. in the hardware structure shown in FIG. 4.
  • the storage module 2104 may be a memory, for example, it may be the internal memory 121 in the hardware structure shown in FIG. 4.
  • An embodiment of the present application also provides an electronic device including one or more processors and one or more memories.
  • the one or more memories are coupled with one or more processors, and the one or more memories are used to store computer program codes.
  • the computer program codes include computer instructions.
  • the electronic device executes The above related method steps implement the account binding method in the above embodiment.
  • the embodiments of the present application also provide a computer storage medium that stores computer instructions, and when the computer instructions run on an electronic device, the electronic device executes the above-mentioned related method steps to implement the account binding in the above-mentioned embodiment. Set method.
  • the embodiment of the present application also provides a computer program product, when the computer program product runs on a computer, the computer is caused to execute the above-mentioned related steps, so as to realize the account binding method executed by the electronic device in the above-mentioned embodiment.
  • the embodiments of the present application also provide a device.
  • the device may specifically be a chip, component or module.
  • the device may include a processor and a memory connected to each other.
  • the memory is used to store computer execution instructions.
  • the processor can execute the computer-executable instructions stored in the memory, so that the chip executes the account binding method executed by the electronic device in the foregoing method embodiments.
  • the embodiment of the present application also provides a chip system, the chip system is applied to an electronic device, and the chip system includes one or more interface circuits and one or more processors.
  • the interface circuit and the processor are interconnected by wires; the interface circuit is used to receive signals from the memory of the electronic device and send signals to the processor, and the signals include computer instructions stored in the memory.
  • the processor executes the computer instruction, the electronic device is caused to execute the account binding method provided by the foregoing method embodiments.
  • the electronic device, computer storage medium, computer program product, or chip provided in this embodiment are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the corresponding method provided above. The beneficial effects of the method will not be repeated here.
  • FIG. 2 For a schematic diagram of the architecture of the system, refer to FIG. 2. Each device in the system may be used to implement the account binding method in the foregoing method embodiments.
  • the disclosed device and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be divided. It can be combined or integrated into another device, or some features can be omitted or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate parts may or may not be physically separate.
  • the parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product, and the software product is stored in a storage medium. It includes several instructions to make a device (may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read only memory (read only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Stored Programmes (AREA)
  • Telephone Function (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请实施例提供一种账号绑定方法、设备及系统，涉及电子技术领域，负一屏能够代替三方快应用获取负一屏的用户账号对应的OpenID，以通过OpenID实现三方应用的用户账号与负一屏的用户账号的绑定，降低三方应用的开发工作量，简化三方应用与负一屏的账号绑定流程，提高账号绑定的效率及灵活性。具体方案为：电子设备登录第一应用的用户账号；在检测到用户的第一预设操作后，通过第一应用获取第一应用的用户账号对应的OpenID，第一预设操作用于指示将第二应用与第一应用相关联；将OpenID和第二应用的身份信息发送给第一应用的服务器；从第一应用的服务器获取账号绑定成功信息。本申请实施例用于账号绑定。

Description

一种账号绑定方法、设备及系统
本申请要求于2019年10月14日提交国家知识产权局、申请号为201910974891.3、申请名称为“一种账号绑定方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及电子技术领域，尤其涉及一种账号绑定方法、设备及系统。
背景技术
在手机、平板或车机等电子设备上，负一屏可以与三方应用合作，从而为用户展示三方应用推荐的事件。一般地，在三方应用的用户账号与负一屏的用户账号建立绑定关系后，负一屏可以展示三方应用推荐的用户关联事件。
现有技术中，三方应用侧需要开发三方快应用，开发基于三方快应用的登录页面，并需要在三方快应用内调用负一屏的账号管理软件开发工具包(software development kit，SDK)，以获取负一屏的用户账号对应的授权码进而获取用户的开放唯一身份标识符(open identity document，OpenID)等进行复杂的开发工作，从而通过OpenID实现三方应用的用户账号与负一屏的用户账号的绑定。
在现有账号绑定方案中，三方应用的开发人员可能并不熟悉快应用的开发流程，因而开发工作的难度较大，且三方应用侧的开发工作量大，绑定流程复杂，绑定成本高，不利于负一屏对三方应用的引入。
发明内容
本申请实施例提供一种账号绑定方法、设备及系统，负一屏能够代替三方快应用获取负一屏的用户账号对应的OpenID，以通过OpenID实现三方应用的用户账号与负一屏的用户账号的绑定，降低三方应用的开发工作量，简化三方应用与负一屏的账号绑定流程，提高账号绑定的效率及灵活性。
为达到上述目的，本申请实施例采用如下技术方案：
一方面，本申请实施例提供了一种账号绑定方法，该方法包括：电子设备登录第一应用的用户账号。电子设备检测到用户的第一预设操作，第一预设操作用于指示将第二应用与第一应用相关联。电子设备通过第一应用，获取第一应用的用户账号对应的开放唯一身份标识符OpenID。电子设备将OpenID和第二应用的身份信息发送给第一应用的服务器。电子设备从第一应用的服务器获取账号绑定成功信息，账号绑定成功信息用于表示第一应用的用户账号与第二应用的用户账号已绑定。
在该方案中，在账号绑定场景下，第一应用可以代替三方应用申请并获取第一应用的用户账号对应的OpenID，以便建立三方应用的用户账号与OpenID的绑定关系，即建立三方应用的用户账号与第一应用的用户账号的绑定关系。这样，三方应用不需要为了实现该绑定开发三方快应用，也不需要为了实现该绑定而专门开发基于三方快应用的登录页面，不需要在三方快应用内调用第一应用的账号管理SDK，以获取第一应用的用户账号对应的 OpenID等复杂的开发工作，从而可以简化三方应用的开发流程，降低三方应用的开发工作量，简化三方应用与第一应用的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
在一种可能的实现方式中，账号绑定成功信息在第二应用的服务器绑定OpenID与第二应用的用户账号并通知第一应用的服务器后，由第一应用的服务器产生。
也就是说，第二应用的服务器进行第二应用的用户账号和该OpenID的绑定，并在账号绑定成功后通知第一应用的服务器。从而，电子设备可以从第一应用的服务器获取到账号绑定成功信息。
在另一种可能的实现方式中，在电子设备将OpenID发送给第一应用的服务器之后，该方法还包括：电子设备从第一应用的服务器获取第二应用的登录页面信息，登录页面信息包括OpenID。电子设备根据登录页面信息显示第二应用的登录页面。电子设备获取登录页面上用户输入的第二应用的用户账号。电子设备将用户输入的第二应用的用户账号和OpenID，发送给第二应用的服务器。
在该方案中，电子设备可以从第一应用的服务器获取到第二应用的登录页面信息，从而根据该信息显示第二应用的用户登录页面，以便用户输入第二应用的用户账号。而后，电子设备可以将第二应用的用户账号和OpenID发送给第二应用的服务器，以便第二应用的服务在第二应用的用户账号验证通过后，绑定第二应用的用户账号和OpenID，也就是绑定第二应用的用户账号和第一应用的用户账号。
在另一种可能的实现方式中，登录页面信息为第二应用对应的登录卡片对象，登录卡片对象的参数包括OpenID。电子设备根据登录页面信息显示第二应用的登录页面，包括：电子设备根据登录卡片对象显示第二应用的登录卡片。
在该方案中，电子设备可以显示登录卡片形式的第二应用的登录页面。
在另一种可能的实现方式中，登录页面信息为第二应用的第5代超文本标记语言H5登录页面的地址，H5登录页面的地址包括OpenID。电子设备根据登录页面信息显示第二应用的登录页面，包括：电子设备根据H5登录页面的地址显示第二应用的H5登录页面。
在该方案中，电子设备可以显示第二应用的H5登录页面。
在另一种可能的实现方式中，电子设备从第一应用服务器获取的H5登录页面的地址拼接了该OpenID。
在另一种可能的实现方式中，登录页面信息为第二应用的原生应用登录页面的地址，原生应用登录页面的地址包括OpenID。电子设备根据登录页面信息显示第二应用的登录页面，包括：电子设备根据原生应用登录页面的地址，显示第二应用的原生应用登录页面。
例如，登录页面信息为第二应用的原生应用登录页面的深度链接DeepLink地址。在该方案中，电子设备可以显示第二应用的原生应用登录页面。
在另一种可能的实现方式中，电子设备从第一应用服务器获取的原生应用登录页面的地址拼接了该OpenID。
在另一种可能的实现方式中，登录页面信息为第二应用的快应用登录页面的地址，快应用登录页面的地址包括OpenID。电子设备根据登录页面信息显示第二应用的登录页面，包括：电子设备根据快应用登录页面的地址，显示第二应用的快应用登录页面。
例如，登录页面信息为第二应用的快应用登录页面的深度链接DeepLink地址。在该 方案中，电子设备可以显示第二应用的快应用登录页面。
在另一种可能的实现方式中，电子设备从第一应用服务器获取的快应用登录页面的地址拼接了该OpenID。
在另一种可能的实现方式中，电子设备将用户输入的第二应用的用户账号和OpenID发送给第二应用的服务器，包括：电子设备在检测到用户的第二预设操作后，将用户输入的第二应用的用户账号和OpenID发送给第二应用的服务器，第二预设操作用于指示绑定第一应用的用户账号与第二应用的用户账号。
也就是说，电子设备在用户指示绑定后，才将第二应用的用户账号和OpenID发送给第二应用的服务器，以便第二应用的服务器进行绑定。
在另一种可能的实现方式中，电子设备通过第一应用获取OpenID，包括：电子设备获取第二应用的身份信息。电子设备通过第一应用将第二应用的身份信息发送给第一应用的账号管理服务器。电子设备从第一应用的账号管理服务器获取OpenID。
在该方案中，电子设备可以将第二应用的身份信息发送给第一应用的账号管理服务器，以便电子设备根据第二应用的身份信息生成第一应用的用户账号对应的OpenID。
在另一种可能的实现方式中，在电子设备从第一应用的服务器获取账号绑定成功信息之后，该方法还包括：电子设备获取第二应用的服务器推送的用户关联事件。电子设备通过第一应用向用户提示用户关联事件。
也就是说，在第二应用的用户账号与OpenID绑定成功后，即在第二应用的用户账号与第一应用的用户账号绑定成功后，第二应用的服务器可以根据该绑定关系，将产生的用户关联事件推送给OpenID对应的第一应用和电子设备，以便电子设备通过第一应用为用户展示用户关联事件。
在另一种可能的实现方式中，该第一应用为负一屏。
这样，第二应用的用户账号可以与负一屏的用户账号相绑定，电子设备可以通过负一屏展示第二应用的服务器推送的用户关联事件。
另一方面，本申请实施例提供了一种账号管理系统，包括：电子设备，第一应用的服务器，第一应用的账号管理服务器，以及第二应用的服务器。其中，电子设备用于：登录第一应用的用户账号；检测到用户的第一预设操作，第一预设操作用于指示将第二应用与第一应用相关联；通过第一应用，从第一应用的账号管理服务器获取第一应用的用户账号对应的开放唯一身份标识符OpenID；将OpenID和第二应用的身份信息发送给第一应用的服务器；从第一应用的服务器获取账号绑定成功信息，账号绑定成功信息用于表示第一应用的用户账号与第二应用的用户账号已绑定。
在一种可能的实现方式中，第一应用的服务器还用于，根据从电子设备获取到的第二应用的身份信息获取第二应用的登录页面信息，登录页面信息包括OpenID。第一应用的服务器还用于，将登录页面信息发送给电子设备。电子设备还用于，根据从第一应用的服务器获取的登录页面信息显示第二应用的登录页面。电子设备还用于，获取登录页面上用户输入的第二应用的用户账号。电子设备还用于，将用户输入的第二应用的用户账号和OpenID发送给第二应用的服务器。第二应用的服务器用于，在用户输入的第二应用的用户账号验证通过后，绑定OpenID与第二应用的用户账号。第二应用的服务器还用于，通知第一应用的服务器第一应用的用户账号与第二应用的用户账号已绑定。
在另一种可能的实现方式中，第一应用的服务器用于：根据从电子设备获取到的第二应用的身份信息获取第二应用对应的登录卡片对象，登录卡片对象的参数包括OpenID。
在另一种可能的实现方式中，第一应用的服务器用于，根据从电子设备获取到的第二应用的身份信息，将OpenID发送给第二应用的服务器。第二应用的服务器还用于，将第二应用的第5代超文本标记语言H5登录页面的地址发送给第一应用的服务器，H5登录页面的地址包括OpenID。第一应用的服务器还用于，将H5登录页面的地址发送给电子设备。
在另一种可能的实现方式中，第二应用服务器发送给第一应用服务器的H5登录页面的地址拼接了该OpenID。
在另一种可能的实现方式中，第一应用的服务器用于，根据从电子设备获取到的第二应用的身份信息，将OpenID发送给第二应用的服务器。第二应用的服务器还用于，将第二应用的原生应用登录页面的地址发送给第一应用的服务器，原生应用登录页面的地址包括OpenID。第一应用的服务器还用于，将原生应用登录页面的地址发送给电子设备。
在另一种可能的实现方式中，第二应用服务器发送给第一应用服务器的原生应用登录页面的地址拼接了该OpenID。
在另一种可能的实现方式中，第一应用的服务器用于，根据从电子设备获取到的第二应用的身份信息，将OpenID发送给第二应用的服务器。第二应用的服务器还用于，将第二应用的快应用登录页面的地址发送给第一应用的服务器，快应用登录页面的地址包括OpenID。第一应用的服务器还用于，将快应用登录页面的地址发送给电子设备。
在另一种可能的实现方式中，第二应用服务器发送给第一应用服务器的快应用登录页面的地址拼接了该OpenID。
在另一种可能的实现方式中，第二应用的服务器还用于，在绑定OpenID与第二应用的用户账号之后，若根据确定产生OpenID对应的用户关联事件，则将用户关联事件推送给OpenID对应的电子设备。电子设备还用于，获取到第二应用的服务器推送的用户关联事件后，通过第一应用向用户提示用户关联事件。
在另一种可能的实现方式中，第一应用为负一屏。
又一方面，本申请实施例提供了一种账号绑定装置，该装置包含在电子设备中。该装置具有实现上述方面及可能的设计中任一方法中电子设备行为的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括至少一个与上述功能相对应的模块或单元。例如，显示模块/单元，处理模块/单元，通信模块/单元，存储模块/单元等。
另一方面，本申请实施例提供了一种计算机存储介质，包括计算机指令，当计算机指令在电子设备上运行时，使得电子设备执行上述方面任一项可能的设计中的账号绑定方法。
又一方面，本申请实施例提供了一种计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机执行上述方面任一项可能的设计中电子设备执行的账号绑定方法。
另一方面，本申请实施例提供了一种芯片系统，该芯片系统应用于电子设备。该芯片系统包括一个或多个接口电路和一个或多个处理器；接口电路和处理器通过线路互联；接口电路用于从电子设备的存储器接收信号，并向处理器发送信号，信号包括存储器中存储的计算机指令；当处理器执行计算机指令时，使得电子设备执行上述方面任一项可能的设计中的账号绑定方法。
上述其他方面对应的有益效果，可以参见关于方法方面的有益效果的描述，此处不予赘述。
附图说明
图1A为现有技术提供的一种账号绑定方法流程图；
图1B为现有技术提供的获取OpenID的流程图；
图1C为现有技术提供的一组账号绑定过程中的界面示意图；
图2为本申请实施例提供的一种账号管理系统的架构图；
图3为本申请实施例提供的一种获取OpenID的流程图；
图4为本申请实施例提供的一种电子设备的结构示意图；
图5为本申请实施例提供的一种账号绑定方法流程图；
图6为本申请实施例提供的一组界面示意图；
图7为本申请实施例提供的一种界面示意图；
图8为本申请实施例提供的另一组界面示意图；
图9为本申请实施例提供的另一组界面示意图；
图10为本申请实施例提供的另一种界面示意图；
图11为本申请实施例提供的另一组界面示意图；
图12为本申请实施例提供的另一组界面示意图；
图13为本申请实施例提供的另一组界面示意图；
图14为本申请实施例提供的另一种界面示意图；
图15为本申请实施例提供的一种显示三方应用登录页面的流程图；
图16为本申请实施例提供的另一组界面示意图；
图17为本申请实施例提供的另一种显示三方应用登录页面的流程图；
图18为本申请实施例提供的另一种显示三方应用登录页面的流程图；
图19为本申请实施例提供的一组账号绑定过程示意图；
图20为本申请实施例提供的另一种界面示意图；
图21为本申请实施例提供的另一种结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请实施例的描述中，“多个”是指两个或多于两个。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
负一屏的主页面通常为桌面的最左屏，即桌面最左侧的页面(或称Widget界面)。负一屏可以为用户提供搜索、新闻、运动健康、生活服务、历史应用或应用推荐等服务的通知或快捷使用。在三方应用(或称第三方应用)的用户账号绑定负一屏的用户账号之后， 三方应用才能在产生用户关注的关联事件后，基于该绑定关系将用户关联事件推荐到负一屏上进行展示。
其中，用户关联事件是三方应用产生的，与用户相关、用户关心或关注的事件。例如，三方应用为外卖应用，用户关联事件为用户订单的配送事件。再例如，三方应用为蚂蚁森林，用户关联事件为用户蚂蚁森林中产生绿色能量的事件。再例如，三方应用为东方财富，用户关联事件为用户关注的股票的相关事件。
基于安全性考虑，手机可以在系统中为快应用预置手机用户账号(例如华为用户账号)的授权码的调用接口，用于快应用通过该接口获取手机用户账号的授权码，进而根据授权码获取手机用户账号对应的OpenID。或者，基于安全性考虑，应用需要集成手机用户账号管理SDK后，才能调用该SDK获取手机用户账号的授权码，进而根据授权码获取手机用户账号对应的OpenID。
一般情况下，负一屏共用手机的用户账号。基于安全考虑，手机用户账号的授权码和OpenID需要通过快应用或三方应用内集成的SDK才能获取到。也就是说，负一屏用户账号的授权码和OpenID需要通过快应用或三方应用内集成的SDK才能获取到。
在一种现有技术中，三方应用可以开发原生三方应用的安装包(例如安卓安装包(android package，APK))，在原生三方应用的安装包里实现三方应用与负一屏的用户账号的绑定功能。该种方式需要在原生三方应用的安装包里集成负一屏的账号管理SDK。而不同设备厂商的负一屏的账号管理SDK不同，原生三方应用的安装包中需要集成多个不同设备厂商的多种账号管理SDK，这将使得原生三方应用的安装包较大，从而导致三方应用占用手机内存过大，用户下载时需要较多的流量，下载过程较慢，运行过程中也会占用较多的资源，用户体验较差等问题，因而该种方式通常不被三方应用所采用。
在另一种现有技术中，三方应用侧开发了三方快应用。其中，快应用也可以称为JavaScript小程序。参见图1A和图1B所示的流程图，用户已经登录了负一屏的用户账号，并触发绑定负一屏与三方应用的用户账号。负一屏拉起三方快应用，三方快应用提供登录页面(或称账号绑定页面)，以便用户输入三方应用的账号。三方快应用调用开放授权(open authorization，OAUTH)账号管理SDK获取用户的头像、昵称以及授权码等信息。三方快应用获取用户输入的三方应用的用户账号，并向三方服务器提交账号绑定信息，账号绑定信息携带有用户的授权码和三方应用的用户账号。三方服务器在三方应用的用户账号验证通过后，调用负一屏的账号管理服务器接口，从而通过授权码获取用户的访问令牌AccessToken，并通过AccessToken获取用户的OpenID，即获取负一屏的用户账号对应的OpenID，从而建立三方应用的用户账号与OpenID的绑定关系，即建立三方应用的用户账号与负一屏的用户账号的绑定关系。
示例性的，以三方应用为东方财富为例，在三方应用的用户账号与负一屏的用户账号的绑定过程中，电子设备的界面示意图可以参见图1C中的(a)-(f)。其中，图1C中的(c)和图1C中的(d)为三方应用基于快应用开发的登录页面。
在该现有技术提供的方案中，为了实现账号绑定，三方应用侧需要开发三方快应用，基于快应用开发三方快应用的登录页面，以及在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，从而通过OpenID实现三方应用的用户账号与负一屏的用户账号的绑定。该方案对三方应用的要求较 高，三方应用侧的开发工作量大，三方应用的开发人员通常并不能掌握快应用的开发流程，而且不同设备厂商对应的负一屏的账号管理SDK的调用接口和调用方式不同，因而开发工作的难度较大；三方应用与负一屏的账号绑定流程的成本较高，绑定流程较为复杂，不利于电子设备的负一屏对三方应用的大量引入。
本申请实施例提供了一种账号绑定方法，可以应用于如图2所示的账号管理系统01。该账号管理系统01包括电子设备10，该电子设备10包括第一应用和第二应用。其中，第二应用是不同于第一应用的三方应用。该账号管理系统01还包括第一应用的服务器20、三方服务器30和账号管理服务器40，该账号管理服务器40用于管理第一应用的用户账号。其中，三方应用与第一应用不使用同一用户账号。三方应用的用户账号与第一应用的用户账号对应的不同的账号管理体系。三方服务器是三方应用的服务器，即上述第二应用的服务器。三方应用的用户账号与第一应用的用户账号绑定后，第一应用可以展示三方应用推荐的用户关联事件。
在三方应用和第一应用的用户账号的绑定过程中，参见图3，第一应用可以调用第一应用的账号管理SDK，从账号管理服务器获取第一应用的用户账号对应的OpenID，并将OpenID发送给三方服务器。三方服务器将OpenID作为三方应用的登录页面的参数返回给第一应用。第一应用拉取带有OpenID参数的三方应用的登录页面。第一应用检测到用户在三方应用的登录页面输入的三方应用的用户账号后，将三方应用的用户账号和OpenID提交给三方服务器。而后，三方服务器可以建立三方应用的用户账号与OpenID的绑定关系，即建立三方应用的用户账号与第一应用的用户账号的绑定关系。
需要说明的是，在本申请的实施例中，用户账号也可以简称为账号。用户账号可以包括用户名和密码。例如，用户名可以是手机号、邮箱、字符串或昵称等。
在本申请实施例提供的账号绑定方法中，第一应用可以代替三方应用申请并获取第一应用的用户账号对应的OpenID，以便建立三方应用的用户账号与OpenID的绑定关系，即建立三方应用的用户账号与第一应用的用户账号的绑定关系。这样，三方应用不需要为了实现该绑定开发三方快应用，也不需要为了实现该绑定而专门开发基于三方快应用的登录页面，不需要在三方快应用内调用第一应用的账号管理SDK，以获取第一应用的用户账号对应的OpenID等复杂的开发工作，从而可以简化三方应用的开发流程，降低三方应用的开发工作量，简化三方应用与第一应用的账号绑定流程，降低三方应用的账号绑定成本，提高账号绑定的效率及灵活性；从而方便三方应用与第一应用进行合作，扩大第一应用的合作群体。并且，三方应用中不需要集成第一应用的账号管理SDK。
举例来说，第一应用为负一屏，即负一屏是一个应用。负一屏可以获取负一屏的用户账号对应的OpenID，以便建立三方应用的用户账号与OpenID的绑定关系，即建立三方应用的用户账号与负一屏的用户账号的绑定关系。这样，负一屏可以代替三方应用申请并获取负一屏的用户账号对应的OpenID，三方应用不需要为了实现该绑定开发三方快应用，也不需要为了实现该绑定而专门开发基于三方快应用的登录页面，不需要在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，因而可以简化三方应用的开发流程，降低三方应用的开发工作量，简化三方应用与负一屏的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
例如，该电子设备具体可以是手机、平板电脑、车载设备、笔记本电脑、智慧屏、可穿戴设备、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本或个人数字助理(personal digital assistant，PDA)等设备，本申请实施例对电子设备的设备类型不作任何限制。
示例性的，图4示出了电子设备100的结构示意图。电子设备100可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，传感器模块180，摄像头193，以及显示屏194等。其中传感器模块180可以包括触摸传感器，压力传感器，陀螺仪传感器或加速度传感器等。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是电子设备100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展电子设备100的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器121可以用于存储计算机可执行程序代码，可执行程序代码包括指令。处理器110通过运行存储在内部存储器121的指令，从而执行电子设备100的各种功能应用以及数据处理。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储电子设备100使用过程中所创建的数据(比如OpenID，音频数据，电话本等)等。此外，内部存储器121可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS) 等。
内部存储器121可以存储有第一应用的账号管理SDK。处理器110可以调用第一应用的账号管理SDK获取第一应用的授权码和OpenID。
内部存储器121可以存储有第一应用的代码。处理器110运行第一应用的代码，以使得第一应用在账号绑定场景下获取第一应用的用户账号对应的OpenID，以便建立三方应用的用户账号与OpenID的绑定关系，即建立三方应用的用户账号与第一应用的用户账号的绑定关系。
USB接口130是符合USB标准规范的接口，具体可以是Mini USB接口，Micro USB接口，USB Type C接口等。USB接口130可以用于连接充电器为电子设备100充电，也可以用于电子设备100与外围设备之间传输数据。也可以用于连接耳机，通过耳机播放音频。该接口还可以用于连接其他电子设备，例如AR设备等。
充电管理模块140用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。
电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为电子设备100的其他模块供电。电源管理模块141还可以用于监测电池容量，电池循环次数，电池健康状态(漏电，阻抗)等参数。
移动通信模块150，无线通信模块160或USB接口130等通信接口，可以用于电子设备100与第一应用的服务器或三方应用服务器或账号管理服务器进行通信，从而交互OpenID、三方应用的登录卡片对象或登录页面地址等信息。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对电子设备100的结构限定。在本申请另一些实施例中，电子设备100也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
电子设备100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。电子设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在电子设备100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
无线通信模块160可以提供应用在电子设备100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation， FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，电子设备100的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合，使得电子设备100可以通过无线通信技术与网络以及其他设备通信。无线通信技术可以包括全球移动通讯系统(global system for mobile communications，GSM)，通用分组无线服务(general packet radio service，GPRS)，码分多址接入(code division multiple access，CDMA)，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，长期演进(long term evolution，LTE)，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
摄像头193用于捕获静态图像或视频。物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工处理。DSP将数字图像信号转换成标准的RGB，YUV等格式的图像信号。在一些实施例中，电子设备100可以包括1个或N个摄像头193，N为大于1的正整数。
显示屏194用于显示图像，视频等。显示屏194包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，电子设备100可以包括1个或N个显示屏194，N为大于1的正整数。
在本申请的实施例中，显示屏194可以显示负一屏的主页面、三方应用的登录页面或账号绑定流程中的页面等界面。
音频模块170用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。音频模块170还可以用于对音频信号编码和解码。例如，音频模块170可以检测到用户的声音信号，以作为语音指令控制电子设备100执行账号绑定或登录等操作。
传感器模块180中的触摸传感器，也称“触控面板”。触摸传感器可以设置于显示屏194，由触摸传感器与显示屏194组成触摸屏，也称“触控屏”。触摸传感器用于检测作用于其上或附近的触摸操作。触摸传感器可以将检测到的触摸操作传递给应用处理器，以确定触摸事件类型。可以通过显示屏194提供与触摸操作相关的视觉输出。在另一些实施例中，触摸传感器也可以设置于电子设备100的表面，与显示屏194所处的位置不同。
可以理解的是，本申请实施例示意的结构并不构成对电子设备100的具体限定。在本申请另一些实施例中，电子设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
在本申请的实施例中，显示屏194可以显示负一屏的主页面、三方应用的登录页面或账号绑定流程中的页面等界面。内部存储器121可以存储有第一应用的代码，以及第一应用的账号管理SDK。处理器110运行第一应用的代码，以使得第一应用在账号绑定场景下，调用第一应用的账号管理SDK，获取第一应用的用户账号对应的OpenID，以便建立三方应用的用户账号与OpenID的绑定关系，即建立三方应用的用户账号与第一应用的用户账号的绑定关系。这样，三方应用不需要开发三方快应用，也不需要专门开发基于三方快应用的登录页面，不需要在三方快应用内调用第一应用的账号管理SDK，以获取第一应用的用户账号对应的OpenID等复杂的开发工作，从而可以简化三方应用的开发流程，降低三方应用的开发工作量，简化三方应用与第一应用的账号绑定流程，降低三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
以下将以图2所示账号管理系统中的电子设备为具有图4所示结构的手机，第一应用为手机上的负一屏为例，对本申请实施例提供的账号绑定方法进行阐述。
需要说明的是，负一屏是手机上的一个应用，在账号绑定流程中，负一屏执行的操作、步骤或功能，是负一屏调用手机中的功能模块或部件实现的。也就是说，负一屏执行的操作、步骤或功能，也可以理解为手机执行的操作、步骤或功能。
在本申请的实施例中，手机可以登录负一屏的用户账号。负一屏在检测到用户指示将目标三方应用与负一屏相关联的操作后，可以获取负一屏的用户账号对应的OpenID，并将该OpenID发送给负一屏服务器。负一屏服务器可以将该OpenID发送给目标三方应用的三方服务器，以便三方服务器绑定目标三方应用的用户账号与该OpenID，即绑定目标三方应用的用户账号与负一屏的用户账号。在账号绑定成功后，三方服务器可以通知负一屏服务器。负一屏可以从负一屏服务器获取账号绑定成功信息。
负一屏将OpenID发送给负一屏服务器后，还可以获取目标三方应用的用户账号信息。例如，负一屏可以从负一屏服务器获取目标三方应用的登录页面信息，该登录页面信息包括OpenID。负一屏可以根据登录页面信息显示目标三方应用的登录页面。负一屏备获取到登录页面上用户输入的目标三方应用的用户账号后，可以将用户输入的第二应用的用户账号和OpenID一起发送给三方服务器。
在账号绑定成功后，三方服务器在产生OpenID对应的负一屏的用户账号相关的用户关联事件后，可以将该用户关联事件推送给负一屏。负一屏获取到三方服务器推送的该用户关联事件后，可以通过卡片等形式向用户提示该用户关联事件。
参见图5，本申请实施例提供的账号绑定方法的具体流程可以包括：
501、手机显示负一屏的主页面。
手机在屏幕上显示负一屏的主页面。该屏幕可以是显示屏，也可以是显示屏与触摸传感器组合成的触摸屏。负一屏的主页面通常为桌面最左侧的页面，可以为用户提供搜索、新闻、运动健康、生活服务、历史应用或应用推荐等服务的通知或快捷使用。
示例性的，参见图6中的(a)-(b)，用户可以在手机桌面上向右滑动；响应于用户 向右滑动的操作，手机可以向左移动显示桌面，直至显示最左侧的桌面，即显示负一屏的主页面。
502、手机登录负一屏的用户账号。
其中，负一屏的用户账号通常与手机的用户账号相一致。例如，若手机的设备厂商为华为，则负一屏的用户账号通常为华为账号；若手机的设备厂商为苹果，则负一屏的用户账号通常为苹果账号。
若手机之前未登录负一屏的用户账号，则用户可以点击图7所示页面左上角的头像控件，以登录负一屏的用户账号。在一些实施例中，若手机之前已登录手机的用户账号，则手机自动登录负一屏的用户账号。
503、负一屏检测到用户针对目标三方应用的预设操作1。
其中，目标三方应用是不同于负一屏的另一应用。例如，目标三方应用具体可以是应用程序(application，APP)、应用小程序或、快应用或其他形式的应用。目标三方应用与负一屏不使用同一用户账号，对应不同的账号管理体系。例如，当负一屏使用华为账号时，目标三方应用不使用华为账号。
负一屏检测到用户的操作可以理解为，手机通过触摸传感器、摄像头或麦克风等检测部件检测到用户的操作并通知给负一屏。
用户针对目标三方应用的预设操作1的操作方式可以有多种，例如触摸操作方式、语音指令方式或隔空操作方式等。例如，目标三方应用可以是蚂蚁森林、东方财富、微软小冰或智慧生活等。
示例性的，负一屏检测到用户点击如图8中的(a)所示的负一屏的主页面上的头像控件的操作后，显示如图8中的(b)所示的负一屏的功能页面。负一屏检测到用户点击如图8中的(b)所示的“情景智能”控件的操作后，显示如图8中的(c)所示的应用列表。
在一些实施例中，用户针对目标三方应用的预设操作1可以包括用户点击负一屏的主页面上头像控件的操作，用户点击功能页面上“情景智能”控件的操作，以及用户点击应用列表中的目标三方应用(例如东方财富)对应的“>”控件的操作。
在另一些实施例中，用户针对目标三方应用的预设操作1可以为用户点击应用列表中的目标三方应用(例如东方财富)对应的“>”控件的操作，在用户针对目标三方应用的预设操作1的操作之前，负一屏还可以检测到用户点击负一屏的主页面上头像控件的操作，或用户点击功能页面上“情景智能”控件的操作等其他操作。
再示例性的，预设操作1可以为负一屏检测到用户语音指示打开目标三方应用的订阅页面的操作。
504、负一屏显示目标三方应用的关联页面，该关联页面表示负一屏与目标三方应用未绑定。
负一屏检测到用户针对目标三方应用的预设操作1后，可以显示该目标三方应用对应的关联页面。示例性的，该关联页面可以参见图9中的(a)或图9中的(b)。该关联页面表示当前目标三方应用的用户账号与负一屏的用户账号未绑定。
需要说明的是，负一屏是平台类应用，可以加载和显示三方应用的界面，例如显示目标三方应用的关联页面。负一屏显示三方应用的界面可以理解为，负一屏加载三方应用的界面并通过手机屏幕进行显示。
可选地，在步骤504之后，该方法还可包括步骤505：
505、负一屏检测到用户指示打开目标三方应用的操作，显示目标三方应用的界面。
负一屏检测到用户指示打开目标三方应用的操作后，可以显示目标三方应用的界面，进入目标三方应用。示例性的，负一屏检测到用户点击图9中的(a)或图9中的(b)所示的“进入服务”的控件后，可以打开目标三方应用，显示如图10所示目标三方应用的界面。
在步骤504之后，该方法还可以包括以下步骤：
506、负一屏检测到用户的预设操作2。
其中，预设操作2用于指示将目标三方应用与负一屏相关联，用于触发绑定目标三方应用的用户账号与负一屏的用户账号。负一屏检测到预设操作2后，发起目标三方应用与负一屏的账号绑定流程。
例如，该预设操作2可以为用户打开图9中的(a)所示的关联页面上“订阅”开关901，并点击“未绑定”之后的“>”控件902的操作。其中，负一屏检测到用户点击“订阅”开关901的操作后，可以订阅目标三方应用，即可以在负一屏启用目标三方应用；检测到用户点击“未绑定”之后的“>”控件902的操作后，发起账号绑定流程。
再例如，该预设操作2可以为用户点击图9中的(b)所示的关联页面上“订阅并绑定”控件903的操作。负一屏检测到该预设操作2后，发起账号绑定流程。
需要说明的是，在步骤506之后，手机也可能尚未登录负一屏的用户账号，即手机在步骤506之前可以不执行步骤502。若手机在步骤506之后确定尚未登录负一屏的用户账号，则可以先进行登录，而后再执行步骤507及后续步骤。
507、负一屏从账号管理服务器获取负一屏的用户账号对应的OpenID。
例如，负一屏的账号管理服务器为OAuth账号管理服务器。负一屏可以调用负一屏的OAuth账号管理的SDK，从负一屏的OAuth账号管理服务器获取负一屏的用户账号对应的OpenID。当负一屏与手机共用相同的用户账号时，也就是说，负一屏可以从手机用户账号的OAuth账号管理服务器获取手机用户账号对应的OpenID。
其中，负一屏可以获取目标三方应用的身份信息，例如目标三方应用的应用程序唯一身份标识(application identity document，AppId)，或目标三方应用的应用名称等。以目标三方应用的身份信息为AppId为例进行说明。负一屏可以调用手机中的OAuth账号管理的SDK，将目标三方应用的AppId传递给OAuth账号管理服务器，并向OAuth账号管理服务器申请获取负一屏的用户账号对应的OpenID。OAuth账号管理服务器根据目标三方应用的AppId生成负一屏的用户账号对应的OpenID，并将该OpenID返回给负一屏。
这样，负一屏可以获取到负一屏可以获取负一屏的用户账号对应的OpenID，以便后续根据该OpenID进行账号绑定；目标三方应用不需要开发三方快应用，也不需要在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，因而可以简化目标三方应用的开发流程，降低目标三方应用的开发工作量，简化目标三方应用与负一屏的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
508、负一屏向负一屏服务器发送账号授权信息，该账号授权信息包括该OpenID以及目标三方应用的身份信息。
其中，账号授权信息用于表示用户指示绑定目标三方应用的用户账号与负一屏的用户账号，即用户指示绑定目标三方应用的用户账号与该OpenID；或者，用于表示用户将该OpenID授权给目标三方应用；或者，用于表示用户授权负一屏服务器将该OpenID提供给目标三方应用；或者，用于表示用户授权绑定目标三方应用的用户账号与该OpenID。
509、负一屏通过负一屏服务器获取目标三方应用的登录页面信息，该登录页面信息包括OpenID。
目标三方应用的登录页面信息用于负一屏获取目标三方应用的登录页面。示例性的，该登录页面可以为图11中的(a)或图11中的(b)所示。
需要说明的是，在一些实施例中，负一屏在显示目标三方应用的登录页面时不会调用负一屏的账号管理SDK获取用户的头像和昵称等用户信息，该种情况下，如图11中的(b)所示，目标三方应用的登录页面上可以不显示用户头像或昵称等用户信息。
510、负一屏根据登录页面信息显示目标三方应用的登录页面。
其中，目标三方应用的登录页面信息包括负一屏的用户账号对应的OpenID。
511、负一屏检测到用户输入的目标三方应用的用户账号。
在负一屏显示目标三方应用的登录页面，用户可以在负一屏显示的目标三方应用的登录页面上，输入目标三方应用的用户名和密码。
512、负一屏检测到用户指示绑定的操作3后，将目标三方应用的用户账号和OpenID发送给三方服务器。
负一屏检测到用户指示绑定目标三方应用的用户账号和负一屏的用户账号的操作3后，可以向三方服务器发送账号绑定信息，该账号绑定信息包括目标三方应用的用户账号和OpenID。
例如，该操作3可以为用户在图11中的(a)或图11中(b)上点击“验证并绑定”控件的操作。再例如，目标三方应用的登录页面上包括“登录并绑定”控件，操作3可以为用户点击该“登录并绑定”控件的操作。再例如，目标三方应用的登录页面上包括“确定”控件，操作3可以为用户点击该“确定”控件的操作。
513、三方服务器在负一屏发送的目标三方应用的用户账号验证通过后，绑定目标三方应用的用户账号和OpenID。
需要说明的是，负一屏在步骤509中获取的登录页面信息包括OpenID，即登录页面与OpenID进行了绑定。这样，负一屏后续根据登录页面信息显示登录页面并获取到用户输入的目标三方应用的账号后，可以将目标三方应用的用户账号和负一屏的用户账号对应的OpenID一并提交给三方服务器，以便三方服务器进行绑定。
在步骤501-步骤513描述的方案中，负一屏可以获取到负一屏可以获取负一屏的用户账号对应的OpenID，三方服务器根据该OpenID绑定目标三方应用的用户账号。目标三方应用不需要开发三方快应用，也不需要在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，因而可以简化目标三方应用的开发流程，降低目标三方应用的开发工作量，简化目标三方应用与负一屏的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
在步骤513之后，该方法还可以包括步骤514：
514、负一屏显示目标三方应用的登录成功页面。
三方服务器在目标三方应用的用户账号验证通过后，确定目标三方应用登录成功，并通过登录界面上提示用户成功登录。此时，负一屏显示的界面上提示用户成功登录，即负一屏显示目标三方应用的登录成功页面。示例性的，目标三方应用登录成功的界面可以参见上述图12中的(a)或图12中的(b)。
在步骤513之后，该方法还可以包括：
515、三方服务器通知负一屏服务器账号绑定成功。
三方服务器可以将账号绑定成功的消息推送给负一屏服务器，该绑定成功的消息可以包括OpenID。该账号绑定成功的消息还可以包括目标三方应用的用户账号。
516、负一屏从负一屏服务器获取账号绑定成功的信息。
其中，账号绑定成功的信息用于表示三方服务器已成功绑定负一屏的用户账号与目标三方应用的用户账号。例如，负一屏可以周期性地向负一屏服务器查询绑定信息，从而获知目标三方应用的用户账号与负一屏的用户账号绑定成功。或者，负一屏可以接收负一屏服务器推送的消息，从而获知目标三方应用的用户账号与负一屏的用户账号绑定成功。
517、负一屏显示绑定成功页面。
该绑定成功页面表示负一屏与目标三方应用已绑定。例如，负一屏检测到用户点击图12中的(a)或图12中的(b)所示的“完成”控件后，可以显示图12中的(c)所示的，表示负一屏与目标三方应用的用户账号已绑定的绑定成功页面。
518、三方服务器根据绑定关系向OpenID对应的负一屏推送用户关联事件。
三方服务器在产生用户关联事件时，向绑定关系中的OpenID对应的负一屏推送用户关联事件，从而通过负一屏将用户关联事件推荐给用户。相应的，负一屏可以接收三方服务器推送的用户关联事件。
519、负一屏在负一屏的主页面上显示目标三方应用推荐的用户关联事件。
在账号绑定成功后，三方服务器可以基于绑定关系向OpenID对应的负一屏推送用户关联事件，即向负一屏推荐目标三方应用中发生的用户关心的事件。负一屏获取到三方服务器推送的用户关联事件后，可以通过卡片等形式向用户展示用户关联事件，以便用户及时了解自己所关注的目标三方应用的相关信息。
示例性的，若目标三方应用为外卖应用，则用户关联事件可以为用户订单的配送事件。若目标三方应用为蚂蚁森林，则用户关联事件可以为用户蚂蚁森林中产生绿色能量的事件。若目标三方应用为东方财富，则用户关联事件为用户关注的股票的相关事件。示例性的，若用户在目标三方应用东方财富中关注的自选股包括京东方A，则用于展示用户关联事件的负一屏的主页面可以参见图13中的(a)或图13中的(b)。
另外，在另一些实施例中，若用户指示订阅目标三方应用并绑定账号，但用户未在三方应用中设置用户个性化的关联事件，则在账号绑定成功后，目标三方应用可以向OpenID对应的负一屏推荐通用事件，并在负一屏的主页面上进行展示。例如，目标三方应用为东方财富，通用事件为股票大盘信息。
此外，在其他一些实施例中，若用户指示订阅目标三方应用但未指示绑定账号，则三方服务器也可以向负一屏推荐通用事件，并在负一屏的主页面上进行展示。在一些实施例中，参见图14，负一屏用于展示推荐的通用事件的卡片上还可以包括用于进行账号绑定的控件1401。负一屏检测到用户点击该控件1401的操作后，可以执行上述步骤507及后续 的账号绑定流程。
在本申请的实施例中，目标三方应用的登录页面可以有多种形式，步骤509-步骤510也可对应不同的实现方式，以下通过举例进行说明。
(1)、目标三方应用的登录页面为登录卡片。
目标三方应用在负一屏服务器上发布时，可以预先设置绑定时目标三方应用的登录页面为卡片模式，登录页面信息为登录卡片对象。
在一些实施例中，登录卡片预设在负一屏服务器上。参见图15，上述步骤509可以包括：
1501a、负一屏服务器确定登录页面为卡片模式，并将目标三方应用对应的登录卡片对象发送给负一屏，该登录卡片对象的参数包括OpenID。
负一屏服务器可以根据目标三方应用的身份信息确定目标三方应用对应的登录卡片对象。该登录卡片对象包括参数，该参数用于描述登录卡片的特征或功能。负一屏服务器可以将OpenID添加到登录卡片对象的参数中，从而将OpenID与登录卡片对象一起发送给负一屏。例如，登录卡片可以通过JavaScript代码描述，登录卡片对象可以是登录卡片JavaScript代码的下载地址及对应的参数。
1502a、负一屏接收负一屏服务器发送的登录卡片对象，该登录卡片对象的参数包括OpenID。
参见图15，上述步骤510可以包括：
1503a、负一屏根据登录卡片对象显示登录卡片。
示例性的，负一屏在检测到用户指示绑定的预设操作1之后，可以显示如图16中的(a)或如图16中的(b)所示的登录卡片。该登录卡片并不是基于三方快应用而开发的。
在另一些实施例中，登录卡片预设在三方服务器上。在上述步骤509中，负一屏服务器实时调用三方服务器接口，将OpenID发送给三方服务器。三方服务器将OpenID添加到登录卡片的参数中，并将添加OpenID后的登录卡片对象发送给负一屏服务器；负一屏服务器将添加OpenID后的登录卡片对象转发给负一屏。
在其他一些实施例中，登录卡片预设在三方服务器上。在上述步骤509中，负一屏服务器实时调用三方服务器接口获取登录卡片的下载路径；负一屏服务器将OpenID添加到登录卡片的下载路径中，并将添加OpenID后的登录卡片登录卡片的下载路径转发给负一屏。该种情况下，负一屏服务器也可以不确定目标三方应用的登录页面为卡片模式还是页面模式，目标三方应用的登录页面的模式由三方服务器来确定。负一屏服务器可以向三方服务器请求获取目标三方应用的登录页面信息，若三方服务器确定目标三方应用的登录页面为卡片模式，则将OpenID添加到登录卡片的下载路径中，并返回给负一屏服务器。负一屏服务器将添加OpenID后的登录卡片的下载路径返回给负一屏。
其中，登录卡片为静态资源，考虑到网络状态的不稳定和时延等情况，与将登录卡片预设在三方服务器上相比，将登录卡片预设在负一屏服务器上，手机的设备厂商可以进行加速等处理，因而性能和可靠性更高。
需要说明的是，负一屏服务器在步骤1501a中向负一屏返回的登录卡片对象的参数包括OpenID，即登录页面与OpenID进行了绑定。这样，负一屏后续根据登录卡片对象显示登录页面并获取到用户输入的目标三方应用的账号后，可以将目标三方应用的用户账号和 OpenID一并提交给三方服务器，以便三方服务器进行账号绑定。
在图15所示的方案中，负一屏可以获取负一屏的用户账号对应的OpenID，并基于预设的目标三方应用的登录卡片，建立目标三方应用的用户账号与OpenID的绑定关系，即建立目标三方应用的用户账号与负一屏的用户账号的绑定关系。该登录卡片并不是基于三方快应用而开发的。
因而，与现有技术相比，目标三方应用不需要为了实现账号绑定开发三方快应用，也不需要为了实现账号绑定而专门开发基于三方快应用的登录页面，不需要在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，因而可以简化目标三方应用的开发流程，降低目标三方应用的开发工作量，简化目标三方应用与负一屏的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
(2)、目标三方应用的登录页面为第5代超文本标记语言H5登录页面。
目标三方应用在负一屏服务器上发布时，可以预先设置绑定时目标三方应用的登录页面为页面模式，登录页面信息为拼接后的H5登录页面的地址。参见图17，上述步骤509可以包括：
1501b、负一屏服务器确定登录页面为页面模式，并向三方服务器发送账号授权信息，该账号授权信息包括该OpenID。
负一屏服务器可以根据从负一屏接收到的目标三方应用的身份信息确定三方服务器，从而向三方服务器发送该OpenID。其中，负一屏服务器向三方服务器发送的账号授权信息包括OpenID；且可以包括目标三方应用的身份信息，也可以不包括目标三方应用的身份信息。
1502b、若三方服务器确定支持目标三方应用的H5登录页面，则拼接OpenID与H5登录页面的地址，并将拼接后的H5登录页面的地址返回给负一屏服务器。
其中，H5登录页面地址可以为目标三方应用已有的登录页面的地址，例如可以为登录页面的HTTP地址。绑定过程可以复用已有的H5登录页面，而不需要目标三方应用为账号绑定专门设计一个登录页面。
OpenID与H5登录页面的地址的拼接方式比较灵活。例如，OpenID可以拼接到H5登录页面的地址之后、之前或之内。也就是说，三方服务器可以将OpenID拼接到H5登录页面的地址中。后续，三方服务器可以根据拼接后的H5登录页面的地址提供目标三方应用的H5登录页面。
1503b、负一屏接收负一屏服务器发送的拼接后的H5登录页面的地址。
上述步骤510可以包括：
1504b、负一屏向三方服务器发送H5登录页面请求信息，该请求信息包括OpenID。
负一屏调用拼接后的H5登录页面的地址，以向三方服务器请求获取目标三方应用的H5登录页面。
1505b、负一屏接收三方服务器发送的H5登录页面的内容，并显示H5登录页面。
三方服务器向负一屏返回H5登录页面的内容，负一屏使用web浏览器加载这个H5登录页面，用户就可以在屏幕上看到H5登录页面。H5登录页面可以将目标三方应用提供的用户名和密码输入框等信息等展示给用户。示例性的，H5登录页面可以参见图11中的 (a)或图11中的(b)，该H5登录页面并不是基于三方快应用开发的页面。
在图17所示的方案中，负一屏可以获取负一屏的用户账号对应的OpenID，并复用目标三方应用已有的H5登录页面，建立目标三方应用的用户账号与OpenID的绑定关系，即建立目标三方应用的用户账号与负一屏的用户账号的绑定关系。该H5登录页面为已有的页面，并不是基于三方快应用开发的页面。
因而，与现有技术相比，目标三方应用不需要为了实现账号绑定开发三方快应用，也不需要为了实现账号绑定而专门开发基于三方快应用的登录页面，不需要在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，因而可以简化目标三方应用的开发流程，降低目标三方应用的开发工作量，简化目标三方应用与负一屏的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
(3)、目标三方应用的登录页面为原生应用登录页面，即原生目标三方应用的登录页面。
目标三方应用在负一屏服务器上发布时，可以预先设置账号绑定时目标三方应用的登录页面为页面模式，登录页面信息为拼接后的原生应用登录页面的地址，例如拼接后的原生应用登录页面的深度链接DeepLink地址。参见图18，上述步骤509可以包括：
1501c、负一屏服务器负一屏服务器确定登录页面为页面模式，并向三方服务器发送账号授权信息，该账号授权信息包括该OpenID。
负一屏服务器可以根据从负一屏接收到的目标三方应用的身份信息确定三方服务器，从而向三方服务器发送该OpenID。其中，负一屏服务器向三方服务器发送的账号授权信息包括OpenID；且可以包括目标三方应用的身份信息，也可以不包括目标三方应用的身份信息。
1502c、若三方服务器确定支持目标三方应用的原生应用登录页面，则拼接OpenID与原生应用登录页面的DeepLink地址，并将拼接后的原生应用登录页面的DeepLink地址返回给负一屏服务器。
也就是说，三方服务器可以将OpenID拼接到原生应用登录页面的DeepLink地址中。后续，三方服务器可以根据拼接后的原生应用登录页面的DeepLink地址，提供目标三方应用的原生应用登录页面。
1503c、负一屏接收负一屏服务器发送的拼接后的原生应用登录页面的DeepLink地址。
上述步骤510可以包括：
1504c、负一屏根据拼接后的原生应用登录页面的DeepLink地址显示原生应用登录页面。
负一屏可以根据拼接后的原生应用登录页面的DeepLink地址拉起原生应用登录页面。其中，这里的原生应用登录页面是指即原生目标三方应用的登录页面。示例性的，原生应用登录页面可以参见图11中的(a)或图11中的(b)所示的页面，该登录页面并不是基于三方快应用开发的页面。
在图18所示的方案中，负一屏可以获取负一屏的用户账号对应的OpenID，并复用目标三方应用已有的原生应用登录页面，建立目标三方应用的用户账号与OpenID的绑定关系，即建立目标三方应用的用户账号与负一屏的用户账号的绑定关系。该原生应用登录页 面为已有的页面，并不是基于三方快应用开发的页面。
因而，与现有技术相比，目标三方应用不需要为了实现账号绑定开发三方快应用，也不需要为了实现账号绑定而专门开发基于三方快应用的登录页面，不需要在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，因而可以简化目标三方应用的开发流程，降低目标三方应用的开发工作量，简化目标三方应用与负一屏的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
(4)、目标三方应用的登录页面为目标三方应用的快应用登录页面。
参见图18，该种情况下对应的处理流程与上述情况(3)类似，不同之处在于上述原生应用登录页面的地址替换为目标三方应用的快应用登录页面的地址。例如，上述原生应用登录页面的DeepLink地址替换为快应用登录页面的DeepLink地址。也就是说，三方服务器可以将OpenID拼接到快应用登录页面的DeepLink地址中，并将拼接后的快应用登录页面的DeepLink地址返回给负一屏，以便负一屏显示快应用登录页面。示例性的，快应用登录页面可以参见图11中的(a)或图11中的(b)所示的页面。
值得注意的是，该快应用登录页面为基于三方快应用开发的登录页面，但是目标三方应用已有的登录页面而不是为了账号绑定流程专门设计的登录页面，因而并没有为了与负一屏绑定绑定而增加目标三方应用额外的开发流程和开发工作量。
也就是说，负一屏可以获取负一屏的用户账号对应的OpenID，并复用目标三方应用已有的快应用登录页面，建立目标三方应用的用户账号与OpenID的绑定关系，即建立目标三方应用的用户账号与负一屏的用户账号的绑定关系。该快应用登录页面为已有的页面，并不是基于三方快应用开发的页面。
因而，与现有技术相比，目标三方应用不需要为了实现账号绑定开发三方快应用，也不需要为了实现账号绑定专门开发基于三方快应用的登录页面，不需要在三方快应用内调用负一屏的账号管理SDK，以获取负一屏的用户账号对应的授权码进而获取OpenID等复杂的开发工作，因而可以简化目标三方应用的开发流程，降低目标三方应用的开发工作量，简化目标三方应用与负一屏的账号绑定流程，降低目标三方应用的账号绑定成本，提高账号绑定的效率及灵活性。
需要注意的是，三方服务器在步骤1502b或步骤1502c中向负一屏服务器返回的拼接后的登录页面的地址包括OpenID，即登录页面与OpenID进行了绑定。这样，负一屏后续通过显示登录页面获取到用户输入的目标三方应用的账号后，可以将目标三方应用的用户账号和OpenID一并提交给三方服务器，以便三方服务器进行账号绑定。
其中，若负一屏服务器确定登录页面为卡片模式，则本申请实施例提供的账号绑定方法流程还可以参见图19中的(a)；若负一屏服务器确定登录页面为页面模式，则本申请实施例提供的账号绑定方法流程还可以参见图19中的(b)。
以上图17或图18所示流程是以负一屏服务器确定登录页面为页面模式为例进行说明的。在其他一些实施例中，在步骤1501b或步骤1501c中，负一屏服务器也可以不确定目标三方应用的登录页面为卡片模式还是页面模式，负一屏服务器可以向三方服务器发送账号授权信息。目标三方应用的登录页面的模式由三方服务器来确定。在步骤1502b或步骤1502c中，若三方服务器确定目标三方应用的登录页面为页面模式，则将OpenID拼接到支 持的页面类型对应的地址中。其中，支持的页面类型包括H5登录页面、原生应用登录页面或快应用登录页面等。
其中，若三方服务器确定支持多种页面类型，则可以将其中的一种或多种页面类型对应的地址返回给负一屏服务器。例如，不同页面类型具有不同的优先级，三方服务器可以将优先级最高的页面类型对应的地址返回给负一屏服务器。再例如，三方服务器可以随机选择一种页面类型对应的地址，并返回给负一屏服务器。
需要说明的是，在其他一些实施例中，账号绑定方法可以包括以上流程中的部分步骤。在其他一些实施例中，账号绑定方法还可以包括以上流程所示步骤之外的其他步骤。
在其他一些实施例中，登录卡片上也可以包括跳转控件，用于跳转到H5登录页面、原生应用登录页面或快应用登录页面进行账号登录。示例性的，该跳转按钮可以为图20所示的控件2001。
在一些实施例中，上述账号管理服务器、负一屏服务器或三方服务器可以为云服务器或其他服务器。
在另一些实施例中，在账号绑定时目标三方应用的登录页面为页面模式的情况下，OpenID与H5登录页面地址、原生应用登录页面的DeepLink地址或快应用登录页面的DeepLink地址拼接，可以不在三方服务器上进行，而在负一屏服务器上进行；或者拼接后的地址可以预设在负一屏服务器上。其中，地址拼接方式较为灵活，不同目标三方应用的地址拼接方式可能不同。并且，为了保证安全，三方服务器可能在地址中携带一些时变参数，以防登录页面被重放攻击，拼接方式较为复杂。因而，三方服务器进行地址拼接的方式更为简单，也更容易适应不同目标三方应用的处理方式。
在其他一些实施例中，负一屏代替目标三方应用获取OpenID也可以替换为，负一屏服务器代替目标三方应用获取OpenID。与负一屏服务器代替目标三方应用获取OpenID相比，负一屏代替目标三方应用获取OpenID可以通过负一屏与用户进行交互，并在用户授权绑定后再获取OpenID，不容易出现违反用户隐私的问题。
可以理解的是，负一屏的主页面目前通常为桌面的最左屏。在其他一些实施例中，负一屏也可以为桌面的最右屏或其他位置的页面，本申请实施例不予限定。
以上主要是以第一应用为与手机共用同一用户账号的负一屏为例进行说明的，在其他一些实施例中，第一应用也可以为与手机共用同一用户账号的其他应用，例如系统应用(比如状态栏等)，本申请实施例不再一一举例。
在其他一些实施例中，第一应用也可以为不与手机共用同一用户账号的应用。例如，第一应用可以为微信或支付宝等可以展示目标三方应用推荐的事件的平台类应用。比如，微信中可以展示其他应用推荐的用户关联事件等。该种情况下，第一应用对应的OpenID不再是手机的账号管理服务器分配的OpenID，而是微信或支付宝等第一应用对应的账号管理服务器分配的OpenID。
尤其地，目标三方应用可以为有特定资质(如股票、医疗等)的应用。本申请实施例提供的方案可以应用于以下场景：受限于资质等因素的约束，负一屏展示的事件卡片无法由手机系统开发，须由目标三方应用开发，因而目标三方应用需与负一屏进行账号绑定的场景。
在其他一些实施例中，第一应用还可以展示与第一应用共用相同的用户账号的其他应 用推荐的用户关联事件，而无需进行上述账号绑定流程。例如，负一屏与华为视频共用华为账号，无需上述绑定流程，负一屏可以展示华为视频推荐的用户关联事件。
在其他一些实施例中，第一应用还可以展示不需要与第一应用进行账号绑定的其他应用(例如新闻等)推荐的用户关联事件。
以上是以电子设备为手机为例进行说明的，本申请实施例提供的账号绑定方法还可以应用于平板或车机等其他电子设备，本申请实施例不再细述。
可以理解的是，为了实现上述功能，电子设备包含了执行各个功能相应的硬件和/或软件模块。结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以结合实施例对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本实施例可以根据上述方法示例对电子设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块可以采用硬件的形式实现。需要说明的是，本实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
例如，在一种划分方式中，参见图21，该电子设备2100可以包括：显示模块2101，处理模块2102，通信模块2103和存储模块2104。
其中，显示模块2101可以用于支持电子设备2100显示用户界面。例如，显示模块2101可以用于支持电子设备2100执行图5所示流程中的步骤501、步骤504、步骤505、步骤510、步骤514、步骤517、步骤519等，和/或用于本文所描述的技术的其他过程。
处理模块2102可以用于对电子设备2100的动作进行控制管理。例如，处理模块2102可以用于支持电子设备2100执行图5所示流程中的步骤502、步骤503、步骤505、步骤506、步骤511、步骤512等，和/或用于本文所描述的技术的其他过程。
通信模块2103可以用于支持电子设备2100与其他设备的通信。例如，通信模块2103可以用于支持电子设备2100执行图5所示流程中的步骤507、步骤508、步骤509、步骤512或步骤516等，和/或用于本文所描述的技术的其他过程。
存储模块2104可以用于存储指令和数据，例如存储第一应用的代码，存储电子设备2100通过通信模块获取的OpenID，存储用户输入的用户账号等信息。
其中，显示模块2101可以显示器，例如具体可以是图4所示硬件结构中的显示屏194。处理模块2102可以是处理器或控制器。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理(digital signal processing，DSP)和微处理器的组合等等。例如，处理模块2102具体可以是图4所示硬件结构中的处理器110。通信模块2103可以为射频电路、蓝牙芯片、Wi-Fi芯片等与其他电子设备交互的设备。例如，通信模块2103可以包括图4所示硬件结构中的移动通信模块150、无线通信模块160、天线1或天线2等。存储模块2104可以是存储器，例如具体可以是图4所示硬件结构中的内部存储器121。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能 模块的功能描述，在此不再赘述。
本申请实施例还提供一种电子设备，包括一个或多个处理器以及一个或多个存储器。该一个或多个存储器与一个或多个处理器耦合，一个或多个存储器用于存储计算机程序代码，计算机程序代码包括计算机指令，当一个或多个处理器执行计算机指令时，使得电子设备执行上述相关方法步骤实现上述实施例中的账号绑定方法。
本申请的实施例还提供一种计算机存储介质，该计算机存储介质中存储有计算机指令，当该计算机指令在电子设备上运行时，使得电子设备执行上述相关方法步骤实现上述实施例中的账号绑定方法。
本申请的实施例还提供了一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述相关步骤，以实现上述实施例中电子设备执行的账号绑定方法。
另外，本申请的实施例还提供一种装置，这个装置具体可以是芯片，组件或模块，该装置可包括相连的处理器和存储器；其中，存储器用于存储计算机执行指令，当装置运行时，处理器可执行存储器存储的计算机执行指令，以使芯片执行上述各方法实施例中电子设备执行的账号绑定方法。
本申请的实施例还提供一种芯片系统，该芯片系统应用于电子设备，该芯片系统包括一个或多个接口电路和一个或多个处理器。其中，接口电路和处理器通过线路互联；接口电路用于从该电子设备的存储器接收信号，并向处理器发送信号，信号包括存储器中存储的计算机指令。当处理器执行计算机指令时，使得该电子设备执行上述各方法实施例提供的账号绑定方法。
其中，本实施例提供的电子设备、计算机存储介质、计算机程序产品或芯片均用于执行上文所提供的对应的方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
本申请另一实施例提供了一种系统，该系统可以的架构示意图可以参见图2，该系统中的各设备可以用于实现上述各方法实施例中的账号绑定方法。
通过以上实施方式的描述，所属领域的技术人员可以了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既 可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上内容，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种账号绑定方法，其特征在于，包括：
    电子设备登录第一应用的用户账号；
    所述电子设备检测到用户的第一预设操作，所述第一预设操作用于指示将第二应用与所述第一应用相关联；
    所述电子设备通过所述第一应用，获取所述第一应用的用户账号对应的开放唯一身份标识符OpenID；
    所述电子设备将所述OpenID和所述第二应用的身份信息发送给所述第一应用的服务器；
    所述电子设备从所述第一应用的服务器获取账号绑定成功信息，所述账号绑定成功信息用于表示所述第一应用的用户账号与所述第二应用的用户账号已绑定。
  2. 根据权利要求1所述的方法，其特征在于，所述账号绑定成功信息在所述第二应用的服务器绑定所述OpenID与所述第二应用的用户账号并通知所述第一应用的服务器后，由所述第一应用的服务器产生。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述电子设备将所述OpenID发送给所述第一应用的服务器之后，所述方法还包括：
    所述电子设备从所述第一应用的服务器获取所述第二应用的登录页面信息，所述登录页面信息包括所述OpenID；
    所述电子设备根据所述登录页面信息显示所述第二应用的登录页面；
    所述电子设备获取所述登录页面上所述用户输入的所述第二应用的用户账号；
    所述电子设备将所述用户输入的所述第二应用的用户账号和所述OpenID，发送给所述第二应用的服务器。
  4. 根据权利要求3所述的方法，其特征在于，所述登录页面信息为所述第二应用对应的登录卡片对象，所述登录卡片对象的参数包括所述OpenID；
    所述电子设备根据所述登录页面信息显示所述第二应用的登录页面，包括：
    所述电子设备根据所述登录卡片对象显示所述第二应用的登录卡片。
  5. 根据权利要求3所述的方法，其特征在于，所述登录页面信息为所述第二应用的第5代超文本标记语言H5登录页面的地址，所述H5登录页面的地址包括所述OpenID；
    所述电子设备根据所述登录页面信息显示所述第二应用的登录页面，包括：
    所述电子设备根据所述H5登录页面的地址显示所述第二应用的H5登录页面。
  6. 根据权利要求3所述的方法，其特征在于，所述登录页面信息为所述第二应用的原生应用登录页面的地址，所述原生应用登录页面的地址包括所述OpenID；
    所述电子设备根据所述登录页面信息显示所述第二应用的登录页面，包括：
    所述电子设备根据所述原生应用登录页面的地址，显示所述第二应用的原生应用登录页面。
  7. 根据权利要求3所述的方法，其特征在于，所述登录页面信息为所述第二应用的快应用登录页面的地址，所述快应用登录页面的地址包括所述OpenID；
    所述电子设备根据所述登录页面信息显示所述第二应用的登录页面，包括：
    所述电子设备根据所述快应用登录页面的地址，显示所述第二应用的快应用登录页面。
  8. 根据权利要求3-7任一项所述的方法，其特征在于，所述电子设备将所述用户输入的所述第二应用的用户账号和所述OpenID发送给所述第二应用的服务器，包括：
    所述电子设备在检测到所述用户的第二预设操作后，将所述用户输入的所述第二应用的用户账号和所述OpenID发送给所述第二应用的服务器，所述第二预设操作用于指示绑定所述第一应用的用户账号与所述第二应用的用户账号。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述电子设备通过所述第一应用获取所述OpenID，包括：
    所述电子设备获取所述第二应用的身份信息；
    所述电子设备通过所述第一应用将所述第二应用的身份信息发送给所述第一应用的账号管理服务器；
    所述电子设备从所述第一应用的账号管理服务器获取所述OpenID。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，在所述电子设备从所述第一应用的服务器获取账号绑定成功信息之后，所述方法还包括：
    所述电子设备获取所述第二应用的服务器推送的用户关联事件；
    所述电子设备通过所述第一应用向所述用户提示所述用户关联事件。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述第一应用为负一屏。
  12. 一种电子设备，其特征在于，包括：一个或多个处理器；以及存储器，所述存储器中存储有代码；
    当所述代码被所述电子设备执行时，使得所述电子设备执行如权利要求1-11任一项所述的账号绑定方法。
  13. 一种计算机存储介质，其特征在于，包括计算机指令，当所述计算机指令在电子设备上运行时，使得所述电子设备执行如权利要求1-11任一项所述的账号绑定方法。
  14. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1-11任一项所述的所述电子设备执行的账号绑定方法。
  15. 一种账号管理系统，其特征在于，包括：电子设备，第一应用的服务器，所述第一应用的账号管理服务器，以及第二应用的服务器；其中，所述电子设备用于：
    登录所述第一应用的用户账号；
    检测到用户的第一预设操作，所述第一预设操作用于指示将第二应用与所述第一应用相关联；
    通过所述第一应用，从所述第一应用的账号管理服务器获取所述第一应用的用户账号对应的开放唯一身份标识符OpenID；
    将所述OpenID和所述第二应用的身份信息发送给所述第一应用的服务器；
    从所述第一应用的服务器获取账号绑定成功信息，所述账号绑定成功信息用于表示所述第一应用的用户账号与所述第二应用的用户账号已绑定。
  16. 根据权利要求15所述的系统，其特征在于，
    所述第一应用的服务器还用于，根据从所述电子设备获取到的所述第二应用的身份信息获取所述第二应用的登录页面信息，所述登录页面信息包括所述OpenID；
    所述第一应用的服务器还用于，将所述登录页面信息发送给所述电子设备；
    所述电子设备还用于，根据从所述第一应用的服务器获取的所述登录页面信息显示所 述第二应用的登录页面；
    所述电子设备还用于，获取所述登录页面上所述用户输入的所述第二应用的用户账号；
    所述电子设备还用于，将所述用户输入的所述第二应用的用户账号和所述OpenID发送给所述第二应用的服务器；
    所述第二应用的服务器用于，在所述用户输入的所述第二应用的用户账号验证通过后，绑定所述OpenID与所述第二应用的用户账号；
    所述第二应用的服务器还用于，通知所述第一应用的服务器所述第一应用的用户账号与所述第二应用的用户账号已绑定。
  17. 根据权利要求16所述的系统，其特征在于，所述第一应用的服务器用于：
    根据从所述电子设备获取到的所述第二应用的身份信息获取所述第二应用对应的登录卡片对象，所述登录卡片对象的参数包括所述OpenID。
  18. 根据权利要求16所述的系统，其特征在于，
    所述第一应用的服务器用于，根据从所述电子设备获取到的所述第二应用的身份信息，将所述OpenID发送给所述第二应用的服务器；
    所述第二应用的服务器还用于，将所述第二应用的第5代超文本标记语言H5登录页面的地址发送给所述第一应用的服务器，所述H5登录页面的地址包括所述OpenID；
    所述第一应用的服务器还用于，将所述H5登录页面的地址发送给所述电子设备。
  19. 根据权利要求16所述的系统，其特征在于，
    所述第一应用的服务器用于，根据从所述电子设备获取到的所述第二应用的身份信息，将所述OpenID发送给所述第二应用的服务器；
    所述第二应用的服务器还用于，将所述第二应用的原生应用登录页面的地址发送给所述第一应用的服务器，所述原生应用登录页面的地址包括所述OpenID；
    所述第一应用的服务器还用于，将所述原生应用登录页面的地址发送给所述电子设备。
  20. 根据权利要求16所述的系统，其特征在于，
    所述第一应用的服务器用于，根据从所述电子设备获取到的所述第二应用的身份信息，将所述OpenID发送给所述第二应用的服务器；
    所述第二应用的服务器还用于，将所述第二应用的快应用登录页面的地址发送给所述第一应用的服务器，所述快应用登录页面的地址包括所述OpenID；
    所述第一应用的服务器还用于，将所述快应用登录页面的地址发送给所述电子设备。
  21. 根据权利要求15-20任一项所述的系统，其特征在于，
    所述第二应用的服务器还用于，在绑定所述OpenID与所述第二应用的用户账号之后，若根据确定产生所述OpenID对应的用户关联事件，则将所述用户关联事件推送给所述OpenID对应的电子设备；
    所述电子设备还用于，获取到所述第二应用的服务器推送的所述用户关联事件后，通过所述第一应用向所述用户提示所述用户关联事件。
  22. 根据权利要求15-21任一项所述的系统，其特征在于，所述第一应用为负一屏。
PCT/CN2020/119018 2019-10-14 2020-09-29 一种账号绑定方法、设备及系统 WO2021073428A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20877057.8A EP4033724A4 (en) 2019-10-14 2020-09-29 ACCOUNT NUMBER BINDING METHOD, DEVICE AND SYSTEM
US17/768,561 US20230122238A1 (en) 2019-10-14 2020-09-29 Account binding method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910974891.3A CN112738143B (zh) 2019-10-14 2019-10-14 一种账号绑定方法、设备及系统
CN201910974891.3 2019-10-14

Publications (1)

Publication Number Publication Date
WO2021073428A1 true WO2021073428A1 (zh) 2021-04-22

Family

ID=75538404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/119018 WO2021073428A1 (zh) 2019-10-14 2020-09-29 一种账号绑定方法、设备及系统

Country Status (4)

Country Link
US (1) US20230122238A1 (zh)
EP (1) EP4033724A4 (zh)
CN (1) CN112738143B (zh)
WO (1) WO2021073428A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115576460A (zh) * 2022-01-06 2023-01-06 荣耀终端有限公司 一种帐号绑定方法和电子设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113472774B (zh) * 2021-06-29 2022-10-25 平安普惠企业管理有限公司 账号免登录方法、系统、设备及计算机可读存储介质
CN115967507A (zh) * 2021-10-11 2023-04-14 华为技术有限公司 一种账号绑定方法、设备、服务器及系统
CN115086344B (zh) * 2021-10-14 2023-06-13 荣耀终端有限公司 一种卡片分享方法、系统及存储介质
US12021860B2 (en) * 2022-05-23 2024-06-25 Bank Of America Corporation Systems and methods for multi-stage, identity-based, digital authentication
CN117574348B (zh) * 2024-01-15 2024-05-10 浙江口碑网络技术有限公司 图形标识码的管理方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014176749A1 (en) * 2013-04-28 2014-11-06 Tencent Technology (Shenzhen) Company Limited Method, device, server, and system for making payment with a messaging application on a mobile device
CN104243433A (zh) * 2013-06-20 2014-12-24 腾讯科技（深圳）有限公司 基于浏览器客户端账号的登录方法、设备及系统
CN105262819A (zh) * 2015-10-29 2016-01-20 努比亚技术有限公司 一种移动终端及其实现推送的方法
CN106686025A (zh) * 2015-11-05 2017-05-17 腾讯科技（深圳）有限公司 收集数据的方法和装置
CN109525604A (zh) * 2018-12-29 2019-03-26 乐蜜有限公司 一种账号绑定的方法及相关设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954322B (zh) * 2014-03-25 2019-10-22 腾讯科技（深圳）有限公司 一种账号的绑定处理方法、装置及系统
CN105897668A (zh) * 2015-10-22 2016-08-24 乐视致新电子科技（天津）有限公司 一种第三方账号授权方法、设备、服务器及其系统
CN105306733B (zh) * 2015-11-13 2018-11-09 深圳正品创想科技有限公司 基于手机app的第三方登录绑定手机号方法
CN108476226B (zh) * 2016-12-22 2021-06-22 华为技术有限公司 应用程序授权方法、终端及服务器
CN108337227B (zh) * 2017-12-22 2019-01-29 北京深思数盾科技股份有限公司 基于OpenID账号登录应用程序的方法及中间件
CN108768803A (zh) * 2018-05-28 2018-11-06 北京小米移动软件有限公司 添加智能设备的方法、装置及存储介质
CN110225035B (zh) * 2019-06-11 2022-11-11 深圳市微付充科技有限公司 第三方账户绑定及登录方法、服务器、终端及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014176749A1 (en) * 2013-04-28 2014-11-06 Tencent Technology (Shenzhen) Company Limited Method, device, server, and system for making payment with a messaging application on a mobile device
CN104243433A (zh) * 2013-06-20 2014-12-24 腾讯科技（深圳）有限公司 基于浏览器客户端账号的登录方法、设备及系统
CN105262819A (zh) * 2015-10-29 2016-01-20 努比亚技术有限公司 一种移动终端及其实现推送的方法
CN106686025A (zh) * 2015-11-05 2017-05-17 腾讯科技（深圳）有限公司 收集数据的方法和装置
CN109525604A (zh) * 2018-12-29 2019-03-26 乐蜜有限公司 一种账号绑定的方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4033724A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115576460A (zh) * 2022-01-06 2023-01-06 荣耀终端有限公司 一种帐号绑定方法和电子设备

Also Published As

Publication number Publication date
CN112738143B (zh) 2022-05-10
CN112738143A (zh) 2021-04-30
EP4033724A1 (en) 2022-07-27
EP4033724A4 (en) 2022-11-16
US20230122238A1 (en) 2023-04-20

Similar Documents

Publication Publication Date Title
WO2021073428A1 (zh) 一种账号绑定方法、设备及系统
US11947974B2 (en) Application start method and electronic device
US20230422154A1 (en) Method for using cellular communication function, and related apparatus and system
KR102481065B1 (ko) 애플리케이션 기능 구현 방법 및 전자 디바이스
CN112351412A (zh) 一种内容接续方法、系统及电子设备
US20220083642A1 (en) Intelligent terminal login method and electronic device
WO2020224447A1 (zh) 一种在联系人中添加智能家居设备的方法及系统
WO2022089121A1 (zh) 处理推送消息的方法和装置
EP4246347A1 (en) Method for authorizing by using another device, electronic devices and system
WO2024037032A1 (zh) 账号登录的方法及电子设备
WO2021042991A1 (zh) 一种非侵入式交互方法及电子设备
US20210385187A1 (en) Method and device for performing domain name resolution by sending key value to grs server
WO2022199673A1 (zh) 一种登录认证的方法和电子设备
WO2022143155A1 (zh) 资源访问方法和终端设备
WO2022206770A1 (zh) 一种设备间应用协同工作的方法及设备
CN114928898B (zh) 建立基于WiFi直接连接的会话的方法和装置
US20240094972A1 (en) Page Display Method and Apparatus, Electronic Device, and Readable Storage Medium
WO2023061058A1 (zh) 一种账号绑定方法、设备、服务器及系统
CN115002939B (zh) 加入WiFi群组的方法和装置
CN114765605B (zh) 资源访问方法和终端设备
EP4366235A1 (en) Cross-device authentication method and apparatus
CN116560769A (zh) 应用组件分享方法及相关设备
CN116560535A (zh) 应用组件管理方法及相关设备
CN118101229A (zh) 资源共享方法、介质及电子设备
CN115510447A (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: 20877057

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020877057

Country of ref document: EP

Effective date: 20220421