Account binding method, device, server and system

Abstract

Embodiments of the present application provide a kind of account binding method, equipment, server and system, it is related to electronic technical field.The method is: the first application can obtain the OpenID corresponding to the user account of the first application, the second server of the second application can allocate access credential for OpenID, to realize the two-way binding of the user account of the second application and the user account of the first application by OpenID.Make that, the second server can use the OpenID provided by the first server to push the user association event to the user account of the first application, and the first server can use the access credential allocated by the second server to access the second server.

Description

Technical Field

[0001] This application relates to the field of electronic technology, and in particular to an account binding method, device, server, and system. Background Technology

[0002] On electronic devices such as mobile phones, tablets, or in-vehicle systems, the Connect app can collaborate with third-party applications. Generally, after a user account of a third-party application is linked to a user account of the Connect app, the Connect app can display user-related events recommended by the third-party application.

[0003] In existing technology, the Changlian application calls its own software development kit (SDK) to obtain the authorization code corresponding to the user account, and then obtains the user's open unique identifier (OpenID). The Changlian application's server sends the user's OpenID to a third-party server. The third-party server uses the OpenID to bind the third-party application's user account with the Changlian application's user account. Afterwards, the third-party application can push user-related events to the Changlian application, which can then display these events to the user.

[0004] However, in the existing account binding scheme, the Changlian app can only receive user association events pushed by third-party servers, and cannot access third-party servers to obtain the detailed content of user association events. Summary of the Invention

[0005] This application provides an account binding method, device, server, and system that enables two-way binding of user accounts between two applications.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] In a first aspect, embodiments of this application provide an account binding method. The executing entity of this method can be an electronic device or a component located within the electronic device (e.g., a chip, chip system, or processor). The following description uses an electronic device as the executing entity. The method includes: the electronic device logging into a user account of a first application; the electronic device receiving a first operation from the user, the first operation indicating that a second application be associated with the first application; the electronic device responding to the first operation sending an account binding request to a first server of the first application, the account binding request carrying the user account of the first application, the OpenUnique Identifier (OpenID) corresponding to the user account of the first application, and the identity information of the second application, for the first server to send the OpenID to a second server of the second application; the electronic device receiving login page information of the second application returned by the first server, the login page information including a first access credential, the first access credential being assigned to the OpenID by the second server of the second application; the electronic device displaying the login page of the second application according to the login page information of the second application; and the electronic device receiving the user account of the second application entered by the user on the login page of the second application. The electronic device submits the user account of the second application and the first access credential to the second server. The second server verifies the user account of the second application. After successful verification, it finds the OpenID corresponding to the user account of the first application based on the first access credential, assigns a second access credential to the OpenID, and establishes a binding relationship between the OpenID of the first application and the user account of the second application. The electronic device receives a successful account binding message from the first server, which is generated by the second server.

[0008] In this way, the first application can obtain the OpenID corresponding to the user account of the first application, and the second server of the second application can assign a second access credential to the OpenID, so as to achieve two-way binding between the user account of the second application and the user account of the first application through the OpenID. This allows the second server to use the OpenID provided by the first server to push user-related events to the user account of the first application, and the first server to use the second access credential assigned by the second server to access the second server.

[0009] Furthermore, when the first server calls the second server, it uses a second access credential assigned by the second server instead of an OpenID, effectively reducing the risk of OpenID leakage. Moreover, when the first server accesses the second server, the second server does not need to identify the user of the first application on the first server; it only needs to authenticate the access credential required when the user initiates a request to access the second server from the first application. Additionally, during the process of establishing account binding between the first and second servers, only one login with the third-party account is required to establish the binding relationship.

[0010] In some implementations, after the electronic device receives the account binding success information from the first server, the process further includes: the electronic device receiving first content corresponding to a user association event from the first server. The electronic device receives a second operation from the user on the first content, the second operation instructing the first server to access the second server to obtain second content corresponding to the user association event, which is a detail of the first content. In response to the second operation, the electronic device requests the first server to send a first access request to the second server, the first access request carrying a second access credential for requesting the second content corresponding to the user association event. The electronic device then receives the second content from the first server. The second content is provided by the second server based on the first access request.

[0011] In some implementations, after the electronic device receives the account binding success information from the first server, the process further includes: the electronic device receiving a third operation from the user on a target interface element in the first interface of the first application, where the target interface element is provided by the second application. In response to the third operation, the electronic device requests the first server to send a second access request to the second server. The second access request carries a second access credential, used to request the retrieval of the content corresponding to the target interface element.

[0012] In some implementations, before the electronic device sends an account binding request to the first server of the first application, the method further includes: the electronic device calling the account management SDK of the first application through the first application to obtain the OpenID corresponding to the user account of the first application from the account management server.

[0013] In one possible implementation, the first application is either the negative one screen or a seamless application.

[0014] Secondly, embodiments of this application provide an account binding method. The execution subject of this method can be a first server or a component located in the first server (e.g., a chip, chip system, or processor). The following description uses the first server as the execution subject. The method includes: the first server receiving an account binding request sent by an electronic device. The account binding request carries a user account of a first application, an Open Unique Identifier (OpenID) corresponding to the user account of the first application, and the identity information of the second application. The first server sends the OpenID to a second server of the second application based on the identity information of the second application. The first server receives login page information of the second application returned by the second server. The login page information includes a first access credential, which is assigned by the second server to the OpenID. The first server sends the login page information to the electronic device for the electronic device to display the login page of the second application. The second server verifies the user account of the second application, and after successful verification, finds the OpenID corresponding to the user account of the first application based on the first access credential, assigns a second access credential to the OpenID, and establishes a binding relationship between the OpenID corresponding to the user account of the first application and the user account of the second application. The first server receives account binding success information sent by the second server. The account binding success information carries the second access credential and is generated by the second server.

[0015] In this way, the first application can obtain the OpenID corresponding to the user account of the first application, and the second server of the second application can assign a second access credential to the OpenID, so as to achieve two-way binding between the user account of the second application and the user account of the first application through the OpenID. This allows the second server to use the OpenID provided by the first server to push user-related events to the user account of the first application, and the first server to use the second access credential assigned by the second server to access the second server.

[0016] In some implementations, after the first server receives the account binding success information sent by the second server, the process further includes: the first server receiving first content corresponding to the user association event sent by the second server. The first server sends the first content to an electronic device, which displays the first content. In response to the user's operation on the first content, the first server sends a first access request to the second server. The first access request is used to access second content corresponding to the user association event, which is a detail of the first content. The first server receives the second content corresponding to the user association event sent by the second server. The first server sends the second content to the electronic device, which displays the second content corresponding to the user association event.

[0017] In some implementations, after the first server receives the account binding success information sent by the second server, the process further includes: the first server responding to a second operation by the user on a target interface element in the first interface of the first application, where the target interface element is provided by the second application. The first server sends a second access request to the second server, the second access request carrying a second access credential, used to request the second server to obtain the content corresponding to the target interface element.

[0018] In some implementations, the first application is either the negative one screen or the seamless application.

[0019] Thirdly, embodiments of this application provide an account binding method. The execution subject of this method can be a second server or a component located within the second server (e.g., a chip, chip system, or processor). The following description uses the second server as the execution subject. The method includes: the second server receiving an account binding request sent by the first server of a first application, the account binding request carrying an Open Unique Identifier (OpenID) corresponding to the user account of the first application. The second server assigns a first access credential to the OpenID. The second server returns login page information of the second application to the first server, the login page information including the first access credential. The second server receives the user account and the first access credential of the second application sent by the electronic device. The second server verifies the application account of the second application. After successful verification, the second server finds the OpenID corresponding to the user account of the first application based on the first access credential, assigns a second access credential to the OpenID, and establishes a binding relationship between the OpenID corresponding to the user account of the first application and the user account of the second application. The second server generates account binding success information, the account binding success information carrying the second access credential. The second server sends the account binding success information.

[0020] In this way, the first application can obtain the OpenID corresponding to the user account of the first application, and the second server of the second application can assign a second access credential to the OpenID, so as to achieve two-way binding between the user account of the second application and the user account of the first application through the OpenID. This allows the second server to use the OpenID provided by the first server to push user-related events to the user account of the first application, and the first server to use the second access credential assigned by the second server to access the second server.

[0021] In some implementations, after the second server sends the account binding success information, the method further includes: the second server sending first content corresponding to the user association event to the first server. The second server receives a first access request sent by the first server, the first access request being used to access second content corresponding to the user association event, the second content being details of the first content. Based on the first access request, the second server sends the second content corresponding to the user association event to the first server.

[0022] In some implementations, after the second server sends the account binding success information, the method further includes: the second server receiving a second access request sent by the first server, the second access request carrying a second access credential used to obtain the content corresponding to the target interface element. The second server then sends the content corresponding to the target interface element to the first server.

[0023] In one implementation, the second server verifies the second access credential by determining that the second access credential is invalid. The second server then assigns a third access credential using OpenID, which is different from the second access credential. The second server sends this third access credential along with account binding success information to the first server.

[0024] In one implementation, the first application is either the negative one screen or the MeeTime application.

[0025] Fourthly, embodiments of this application provide an account management system, which may include: an electronic device, a first server of a first application, an account management server of the first application, and a second server of a second application; wherein the electronic device logs into the user account of the first application. The electronic device receives a first operation from the user, the first operation being used to instruct the second application to be associated with the first application. In response to the first operation, the electronic device sends an account binding request to the first server, the account binding request carrying the user account of the first application, the OpenUnique Identifier (OpenID) corresponding to the user account of the first application, and the identity information of the second application. The first server receives the account binding request sent by the electronic device. The first server locates the second server of the second application based on the identity information of the second application. The first server sends the OpenID to the second server. The second server assigns a first access credential to the OpenID. The second server returns the login page information of the second application to the first server, the login page information including the first access credential. The first server receives the login page information of the second application returned by the second server, the login page information including the first access credential, the first access credential being assigned by the second server to the OpenID. The first server sends the login page information of the second application to the electronic device. The electronic device displays the login page of the second application based on the login page information of the second application;

[0026] In response to the user entering their second application's user account on the second application's login page, the electronic device sends the second application's user account and a first access credential to a second server. The second server verifies the second application's user account, and upon successful verification, finds the OpenID corresponding to the first application's user account based on the first access credential, assigns a second access credential to the OpenID, and establishes a binding relationship between the OpenID corresponding to the first application's user account and the second application's user account. The second server generates an account binding success message, which carries the second access credential. The first server receives the account binding success message sent by the second server.

[0027] In this way, the first application can obtain the OpenID corresponding to the user account of the first application, and the second server of the second application can assign a second access credential to the OpenID, so as to achieve two-way binding between the user account of the second application and the user account of the first application through the OpenID. This allows the second server to use the OpenID provided by the first server to push user-related events to the user account of the first application, and the first server to use the second access credential assigned by the second server to access the second server.

[0028] In some implementations, the system further includes: a second server sending first content corresponding to a user-associated event to a first server. The first server receiving the first content sent by the second server. The first content being sent to an electronic device, which displays the first content corresponding to the user-associated event; the electronic device receiving a third operation from the user on the first content. In response to the third operation, the electronic device sending an access request to the first server, the access request being used to access second content corresponding to the user-associated event on the second server, the second content being details of the first content. The first server sending the access request to the second server. Based on the access request, the second server accesses the second content corresponding to the user-associated event and sends the second content corresponding to the user-associated event to the first server. The first server receiving the second content corresponding to the user-associated event sent by the second server. The first server sending the second content corresponding to the user-associated event to the electronic device, which displays the second content corresponding to the user-associated event.

[0029] Fifthly, embodiments of this application provide an electronic device, which includes: one or more processors; and a memory storing code; when the code is executed by the electronic device, the electronic device performs the account binding method as described in the first aspect.

[0030] In a sixth aspect, embodiments of this application provide a server comprising: one or more processors; and a memory storing code; when the code is executed by the server, the server performs the account binding method as described in the second aspect, or the server performs the account binding method as described in the third aspect.

[0031] Seventhly, embodiments of this application provide an account binding device included in an electronic device. This device has the function of implementing the behavior of the electronic device in any of the above aspects and possible designs. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above function. For example, a display module / unit, a processing module / unit, a communication module / unit, a storage module / unit, etc.

[0032] Eighthly, embodiments of this application provide a computer storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the account binding method in any of the possible designs described above.

[0033] Ninthly, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to execute the account binding method performed by the electronic device in any of the possible designs described above.

[0034] In a tenth aspect, embodiments of this application provide a chip system applied to an electronic device. The chip system includes one or more interface circuits and one or more processors; the interface circuits and processors are interconnected via lines; the interface circuits are used to receive signals from the electronic device's memory and send signals to the processors, the signals including computer instructions stored in the memory; when the processor executes the computer instructions, it causes the electronic device to perform the account binding method in any of the possible designs described above.

[0035] For the other beneficial effects mentioned above, please refer to the description of the beneficial effects of the method, which will not be repeated here. Attached Figure Description

[0036] Figure 1 An architecture diagram of an account management system provided in an embodiment of this application;

[0037] Figure 2 A flowchart for obtaining an OpenID is provided as an embodiment of this application;

[0038] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0039] Figure 4 A flowchart illustrating an account binding method provided in this application embodiment;

[0040] Figure 5 Image (a) is a schematic diagram of an interface provided in an embodiment of this application;

[0041] Figure 5 Image (b) is a schematic diagram of an interface provided in an embodiment of this application;

[0042] Figure 5 Image (c) is a schematic diagram of an interface provided in an embodiment of this application;

[0043] Figure 5 Image (d) is a schematic diagram of an interface provided in an embodiment of this application;

[0044] Figure 5 Image (e) is a schematic diagram of an interface provided in an embodiment of this application;

[0045] Figure 5 Image (f) is a schematic diagram of an interface provided in an embodiment of this application;

[0046] Figure 5 Image (g) is a schematic diagram of an interface provided in an embodiment of this application;

[0047] Figure 5 Image (h) is a schematic diagram of an interface provided in an embodiment of this application;

[0048] Figure 5 Image (i) is a schematic diagram of an interface provided in an embodiment of this application;

[0049] Figure 6 A flowchart illustrating an application scenario of an account binding method provided in this application embodiment;

[0050] Figure 7 A flowchart illustrating another application scenario of an account binding method provided in this application embodiment;

[0051] Figure 8 This is another structural schematic diagram provided for an embodiment of this application. Detailed Implementation

[0052] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0053] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0054] Currently, the Changlian application calls its own account SDK to obtain the authorization code corresponding to the user's account, and then obtains the user's OpenID, etc. The Changlian application's server sends the user's OpenID to a third-party server. The third-party server uses the OpenID to bind the third-party application's user account to the Changlian application's user account. Afterwards, the third-party application can push user-related events to the Changlian application, which will then display these events to the user. However, currently only the third-party server can bind the user account between the third-party application and the Changlian application; the Changlian application's server cannot bind the user account between the two applications. In other words, two-way binding of user accounts between the two applications is not possible.

[0055] To address the aforementioned technical issues, in this embodiment, the OpenID corresponding to the user account of the first application is obtained through the first application. The first server sends the OpenID to the second server, which then assigns a first access credential to the OpenID and sends the first access credential to the first server. In this way, the second server can use the OpenID provided by the first server to push user-related events to the user account of the first application, and the first server can use the first access credential assigned by the second server to access the second server. This achieves two-way account binding, facilitating cooperation between the second application and the first application and expanding the functionality of the first application's collaborative group.

[0056] In some embodiments, the electronic device logs into the user account of a first application. The electronic device receives a first operation from the user, which instructs the association of a second application with the first application. In response to the first operation, the electronic device sends an account binding request to the first server of the first application, the account binding request carrying the user account of the first application, the OpenID corresponding to the user account of the first application, and the identity information of the second application. The first server locates the second server of the second application based on the identity information of the second application and sends the OpenID to the second server. The second server assigns a first access credential to the OpenID and returns the first access credential as a parameter of the login page of the second application to the first application via the first server. The first application launches the login page of the second application with the first access credential parameter. At this time, the electronic device displays a first interface, which includes the login page information of the second application, including the first access credential. When the electronic device detects the user's input of the user account of the second application, the electronic device submits the user account of the second application and the first access credential to the second server. The second server verifies the user account of the second application. After successful verification on the second server, the second server locates the OpenID corresponding to the user account of the first application based on the first access credential, assigns a second access credential to the OpenID, and establishes a binding relationship between the user account of the second application and the OpenID, i.e., a binding relationship between the user account of the second application and the user account of the first application. The second server pushes a successful account binding message to the first server. This successful account binding message carries the second access credential. The electronic device retrieves the successful account binding message from the first server.

[0057] In some embodiments, after the second server establishes a binding relationship between the user account of the second application and the user account of the first application, the second server pushes the first content corresponding to the user-associated event to the first application through the first server. The electronic device detects a second operation by the user on the first content, which instructs the first server to access the second server to obtain the second content corresponding to the user-associated event. This second content is the detailed content (or details) of the first content. In response to the second operation, the electronic device requests the first server to send a first access request to the second server, which carries a second access credential. The second server receives the first access request sent by the first server and verifies the second access credential. After successful verification of the second access credential, the second server obtains the second content corresponding to the user-associated event and feeds it back to the first application through the first server. The electronic device then obtains the second content corresponding to the user-associated event from the first server.

[0058] In some embodiments, after the second server establishes a binding relationship between the user account of the second application and the user account of the first application, the electronic device receives a third operation from the user on a target interface element in the first interface of the first application, where the target interface element is provided by the second application. In response to the third operation, the electronic device requests the first server to send a second access request to the second server, the second access request carrying a second access credential. The second server retrieves the content corresponding to the target interface element based on the second access request and returns the content to the first server. The first server receives the content corresponding to the target interface element and sends it to the electronic device for display.

[0059] In some embodiments, the second access credential has a validity period, which may refer to a valid start time, valid end time, valid time period, etc. For example, the validity period of the second access credential may be 1 hour, or 30 minutes, or 2 hours. The valid start time of the second access credential is January 1, 2021, and the valid end time is August 1, 2021. Alternatively, the valid start time of the second access credential is 11:00 AM on January 1, 2021, and the valid end time is 1:00 PM on January 1, 2021. The second access credential is considered valid if it is within its validity period; the second access credential is considered invalid if it is outside its validity period.

[0060] In one possible implementation, the second server verifies the second access credential by verifying its validity. In some embodiments, if the second server determines that the second access credential is invalid, the second server assigns a third access credential to the OpenID. The third access credential is different from the second access credential.

[0061] In some embodiments, the first application may include the Connect app (hereinafter referred to as the Connect APP) or the negative one screen. The second application may include a third-party application.

[0062] The Changlian app is typically integrated into the phone application. After a user launches the phone application, the phone displays the phone interface, which shows the Changlian app icon. The user interacts with the Changlian app icon. Upon receiving the user's interaction, the phone displays the Changlian app's main page. The Changlian app can provide users with notifications or quick access to services such as express delivery, food delivery, news, sports and health, lifestyle services, and app recommendations. Additionally, the Changlian app can provide users with interfaces to access other third-party applications. After a third-party application's user account is linked to the Changlian app's user account, the third-party application can recommend content related to a user-related event to the Changlian app based on this linking relationship. The Changlian app can also access third-party applications in response to user actions based on this linking relationship.

[0063] The negative one screen is typically the leftmost screen on the desktop (or widget interface). It provides users with notifications or quick access to services such as search, news, health and fitness, lifestyle services, past apps, and app recommendations. Only after a third-party app's user account is linked to the negative one screen's user account can the app recommend content related to events that the user is interested in, based on this linking relationship.

[0064] User-related events are those generated by third-party applications that are relevant to the user and that the user cares about or is interested in. For example, if the third-party application is a food delivery app, the user-related event is the delivery of the user's order. Another example is an entertainment app, where user-related events are events that allow the user to generate energy. Yet another example is a stock market app, where user-related events are events related to stocks that the user is interested in.

[0065] In some embodiments, for security reasons, the electronic device may pre-configure an interface for calling the authorization code of a user account (e.g., a Huawei user account) for the first application. This interface allows the first application to obtain the authorization code of the user account and then retrieve the OpenID corresponding to the user account based on the authorization code. Alternatively, for security reasons, the application may need to integrate a user account management SDK before it can call the SDK to obtain the authorization code of the user account and then retrieve the OpenID corresponding to the user account based on the authorization code.

[0066] In one specific implementation, this application provides an account binding method that can be applied to, for example... Figure 1The account management system 01 shown is an electronic device 10, which includes a first application and a second application. The second application is a third-party application, distinct from the first application. The account management system 01 also includes a server 20 for the first application, a third-party server 30, and an account management server 40. The account management server 40 manages the user accounts for the first application. The third-party application does not use the same user accounts as the first application. The user accounts for the third-party application and the first application correspond to different account management systems. The third-party server is the server for the third-party application, i.e., the server for the aforementioned second application. After the user accounts for the third-party application are bound to the user accounts for the first application, the first application can display content related to user-related events recommended by the third-party application.

[0067] During the process of binding user accounts between third-party applications and the primary application, see [link to relevant documentation]. Figure 2 ① The first application on electronic device 10 can call its account management SDK to obtain the OpenID corresponding to the user account of the first application from the account management server 40. ② The first application on electronic device 10 sends the OpenID to its server 20. ③ The server 20 sends the OpenID to the third-party server 30. ④ The third-party server 30 assigns a first access credential to the OpenID. The third-party server 30 returns the first access credential as a parameter to the login page of the third-party application to the server 20. ⑤ The server 20 returns the first access credential as a parameter to the login page of the third-party application to the first application. The first application launches the login page of the third-party application with the first access credential parameter. ⑥ After the first application detects the user account of the third-party application entered by the user on the login page of the third-party application, the first application submits the user account and the first access credential to the third-party server 30. The third-party server 30 verifies the user account of the second application. After successful verification by the third-party server 30, the third-party server 30 can establish a binding relationship between the user account of the third-party application and the OpenID, that is, establish a binding relationship between the user account of the third-party application and the user account of the first application. The third-party server 30 also assigns a second access credential to the OpenID. The third-party server 30 generates an account binding success message, which carries the second access credential. The third-party server 30 sends the account binding success message to the server 20. The server 20 returns the account binding success message to the electronic device 10.

[0068] It should be noted that, in the embodiments of this application, the user account can also be simply referred to as an account. A user account may include a username, password, and verification code. For example, a username may be a mobile phone number, email address, a string, or a nickname.

[0069] In this embodiment, the OpenID corresponding to the user account of the first application is obtained through the first application. The first server sends the OpenID to the second server, which then assigns a second access credential to the OpenID and sends the second access credential to the first server. In this way, the second server can use the OpenID provided by the first server to push user-related events or content corresponding to user-related events to the user account of the first application. The first server can use the second access credential assigned by the second server to access the second server, achieving two-way account binding. This facilitates cooperation between the second application and the first application, expanding the functionality of the first application's collaborative group.

[0070] Furthermore, when the first server calls the second server, it uses a second access credential assigned by the second server instead of an OpenID, effectively reducing the risk of OpenID leakage. Moreover, when the first server accesses the second server, the second server does not need to identify the user of the first application on the first server; it only needs to authenticate the access credential required when the user initiates a request to access the second server from the first application. Additionally, during the process of establishing account binding between the first and second servers, only one login with the third-party account is required to establish the binding relationship.

[0071] For example, the electronic device may specifically be a mobile phone, tablet computer, in-vehicle device, laptop computer, smart screen, wearable device, augmented reality (AR) / virtual reality (VR) device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. This application embodiment does not impose any restrictions on the type of electronic device.

[0072] For example, Figure 3 A schematic diagram of the electronic device 100 is shown. 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, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, a camera 193, and a display screen 194, etc. The sensor module 180 may include a touch sensor, a pressure sensor, a gyroscope sensor, or an accelerometer sensor, etc.

[0073] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0074] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0075] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0076] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0077] The external storage interface 120 can 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 storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0078] Internal memory 121 can be used to store computer executable program code, including instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as OpenID, audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0079] The internal memory 121 can store the account management SDK of the first application. The processor 110 can call the account management SDK of the first application to obtain the authorization code and OpenID of the first application.

[0080] Internal memory 121 may store the code of the first application. Processor 110 executes 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 binding relationship between the user account of the third-party application and the user account of the first application.

[0081] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0082] 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.

[0083] 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 charging management module 140 to power 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 count, and battery health status (leakage current, impedance).

[0084] The mobile communication module 150, wireless communication module 160, or USB interface 130 and other communication interfaces can be used for electronic device 100 to communicate with the server of the first application, the third-party application server, or the account management server, thereby exchanging information such as OpenID, login card object of the third-party application, or login page address.

[0085] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0086] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0087] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0088] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, 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 via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0089] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0090] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. Wireless communication technology may include 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, and / or IR technologies, etc. GNSS can include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0091] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0092] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0093] In the embodiments of this application, the display screen 194 can display the main page of the negative one screen, the login page of a third-party application, or the page in the account binding process, etc.

[0094] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. For example, the audio module 170 can detect a user's voice signal to control the electronic device 100 to perform operations such as account binding or login as voice commands.

[0095] The touch sensor in sensor module 180 is also called a "touch panel". The touch sensor can be located on display screen 194, and the touch sensor and display screen 194 together form a touchscreen, also called a "touch screen". The touch sensor is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, the touch sensor may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0096] In the embodiments of this application, the display screen 194 can display interfaces such as the main page of the negative one screen, the login page of a third-party application, or pages in the account binding process. The internal memory 121 can 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 that the second server can allocate a second access credential for the OpenID. This facilitates the second server to establish a binding relationship between the user account of the third-party application and the OpenID, that is, to establish a binding relationship between the user account of the third-party application and the user account of the first application. In this way, two-way account binding is realized. That is, the second server can use the OpenID provided by the first server to push user-related events to the user account of the first application, and the first server can use the second access credential allocated by the second server to access the second server. This facilitates cooperation between the third-party application and the first application, expanding the functionality of the first application's cooperative group. Furthermore, the account management SDK of the first application does not need to be integrated into the third-party application.

[0097] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0098] In this embodiment, the first application can be a Connect app (referred to as Connect APP) or a negative one screen; the second application can be a third-party application; and correspondingly, the second server can be a third-party server. In this embodiment, the following will refer to... Figure 1 The electronic devices in the account management system shown are those with Figure 3 Taking the mobile phone with the structure shown as an example, where the first application is the Changlian APP on the mobile phone and the first server is the server of the Changlian APP, the account binding method provided in this application embodiment will be described.

[0099] It should be noted that the Changlian APP is an application integrated into the phone's calling application. During the account binding process, the operations, steps, or functions performed by the Changlian APP are implemented by the Changlian APP calling functional modules or components on the phone. In other words, the operations, steps, or functions performed by the Changlian APP can also be understood as the operations, steps, or functions performed by the phone.

[0100] See Figure 4 The specific process of the account binding method provided in this application embodiment may include:

[0101] S401, User account for logging into the Changlian APP on mobile phone.

[0102] The user account in the Connect app is usually the same as the user account on the mobile phone. For example, if the mobile phone manufacturer is Huawei, the user account in the Connect app is usually a Huawei account; if the mobile phone manufacturer is... The user account of the Changlian APP is usually account.

[0103] If the user has not previously logged into a Changlian APP account on their phone, they can click... Figure 5 The avatar control in the upper left corner of the page shown in (a) is used to log in to the user account of the Changlian APP. In some embodiments, if the mobile phone has already been logged into a user account, the mobile phone will automatically log in to the user account of the Changlian APP.

[0104] S402. The Changlian APP displays the association page of the target third-party application, which indicates that the Changlian APP and the target third-party application are not bound.

[0105] After receiving a user's first action targeting a third-party application, the Changlian APP can display the associated page for that application. For example, this associated page can be found here: Figure 5 As shown in (f) in the diagram. This associated page indicates that the user account of the current target third-party application is not bound to the user account of the Changlian APP.

[0106] It's important to note that the Changlian app is a platform application that can load and display the interfaces of third-party applications, such as displaying the associated pages of a target third-party application. Displaying the interface of a third-party application on the Changlian app can be understood as the Changlian app loading the interface of the third-party application and displaying it on the phone screen.

[0107] In some embodiments, when a user selects a desired Connect service in the Connect app's interface, the mobile phone sends a service subscription request to the Connect app's server, such as a first server. The first server saves the user's subscription service based on the service subscription request. In some embodiments, the Connect app can also be used to load and display the subscription service interface. For example, when a user operates on a subscription service within the Connect app's interface, the Connect app sends a service subscription request to the first server. The first server then saves the user's subscription service based on the service subscription request.

[0108] Optionally, after step 402, the method may further include step 403:

[0109] S403. The Changlian APP receives a user instruction to open the target third-party application and, in response, displays the interface of the target third-party application.

[0110] After receiving a user's instruction to open a target third-party application, the Changlian APP can display the target third-party application's interface and enter the application. For example, the Changlian APP receives a user's click... Figure 5 After the "Connect Service" control shown in (a) above, you can display... Figure 5 The interface shown in (b) can include multiple controls, such as a control for "Connect Service Name". The Connect APP receives a user click... Figure 5 After clicking the "Connect Service Name" control shown in (b) above, the target third-party application can be opened and displayed as shown below. Figure 5 (c) or Figure 5 (d) or Figure 5 The target third-party application interface is shown in (e). Users can navigate through menu options (such as...) on the target third-party application interface. Figure 5 As shown in (c), users can request access to the server of the target third-party application. Alternatively, users can also enter text on the interface of the target third-party application (such as...). Figure 5 As shown in (d), users can request access to the server of the target third-party application. Alternatively, users can input voice commands on the interface of the target third-party application (such as...). Figure 5 As shown in (e), it requests access to the server of the target third-party application.

[0111] S404, The mobile phone receives the user's first operation, which is used to instruct the target third-party application to be associated with the Changlian APP.

[0112] The target third-party application is a separate application from the Connect app. Specifically, it can be an application (APP), a mini-program, a quick app, or other forms of application. The target third-party application and the Connect app do not use the same user account and have different account management systems. For example, while the Connect app uses a Huawei account, the target third-party application does not.

[0113] The "Changlian APP receiving the user's first action" can be understood as the phone receiving the user's first action through detection components such as touch sensors, cameras, or microphones and notifying the Changlian APP of it.

[0114] Users can perform various actions on a target third-party application, such as touch operation, voice command, or air gesture. For example, the target third-party application could be a stock trading app, an entertainment app, a food delivery app, or a ride-hailing app.

[0115] For example, when the Changlian APP receives a user's click, such as Figure 5After the user interacts with the avatar control on the main page of the Changlian APP as shown in (a), they log in to their Changlian APP account. The Changlian APP receives the user's click as shown... Figure 5 After operating the "Connect Service" control shown in (a) above, the following will be displayed: Figure 5 (b) shows the Connect service followed by the Connect app.

[0116] In some embodiments, the first operation may include the user clicking the avatar control on the main page of the Changlian APP, the user clicking the "Changlian Service" control on the function page, the user clicking the control corresponding to the target third-party application (e.g., Travel Assistant) in the Changlian Service Follow list, and the user clicking the control in the interface of the target third-party application.

[0117] In other embodiments, the first operation may be a user click. Figure 5 The operation of the "unbound" control shown in (f).

[0118] In other embodiments, the first operation may be to open for the user. Figure 5 The operation of clicking the "Follow Service" control on the associated page shown in (f) and clicking the "Unbound" control.

[0119] In other embodiments, the first operation may be the operation of the Changlian APP detecting a user's voice instruction to open the subscription page of the target third-party application.

[0120] S405. In response to the first operation, the mobile phone sends an account binding request to the first server of the Changlian APP. The account binding request carries the user account of the Changlian APP, the OpenUnique Identifier OpenID corresponding to the user account of the Changlian APP, and the identity information of the target third-party application.

[0121] For example, this first operation can open for the user Figure 5 Taking the "Follow Service" control on the associated page shown in (f) as an example, and clicking the "Unbound" control, after the Changlian APP detects the user's click on the "Follow Service" control, it can follow the target third-party application, that is, enable the target third-party application in the Changlian APP; after detecting the user's click on the "Unbound" control, it initiates the account binding process, that is, sends an account binding request to the first server.

[0122] In some embodiments, the Changlian App obtains the OpenID corresponding to the Changlian App's user account from the account management server. For example, the Changlian App's account management server is an OAuth account management server. The Changlian App can call its OAuth account management SDK to obtain the OpenID corresponding to the Changlian App's user account from the OAuth account management server. When the Changlian App and the mobile phone share the same user account, that is, the Changlian App can obtain the OpenID corresponding to the mobile phone's user account from the mobile phone's OAuth account management server.

[0123] Among them, the Changlian APP can obtain the identity information of the target third-party application, such as the application identity (AppId) of the target third-party application, or the application name of the target third-party application.

[0124] In other embodiments, the Changlian APP can obtain the OpenID corresponding to the user account of the Changlian APP based on the identity information of the target third-party application. For example, the AppId of the target third-party application can be used as an example. The Changlian APP can call the OAuth account management SDK on the phone, pass the AppId of the target third-party application to the OAuth account management server, and request the OpenID corresponding to the user account of the Changlian APP from the OAuth account management server. The OAuth account management server generates the OpenID corresponding to the user account of the Changlian APP based on the AppId of the target third-party application and returns the OpenID to the Changlian APP.

[0125] Specifically, the Changlian APP determines whether there is a history of authorized login. After the user account in the Changlian APP is authorized, the Changlian APP can call the OAuth account management SDK on the phone to obtain a unique authorization code. The Changlian APP passes the authorization code to the first server. The first server uses the authorization code to call the account management server's interface to obtain the user's Access token. The account management server returns the user's Access token and Refresh token. The first server uses the user's Access token to call the account management server's interface to obtain the user's OpenID, avatar, nickname, mobile phone number (if needed), and email address (if needed). The account management server returns the user's OpenID, avatar, nickname, mobile phone number (if needed), and email address (if needed) to the first server.

[0126] When the account management server returns a user's OpenID and mobile phone number to the first server, the first server compares the mobile phone number with the mobile phone numbers of existing users in the system (such as Huawei users). If a matching mobile phone number is found, it is considered to be the same user, and an association is established between the first server's user and the existing user's OpenID. Alternatively, a new user can be created in the system based on an existing user's mobile phone number, establishing an association between the first server's user and the existing user's OpenID. The first server simultaneously assigns access credentials (such as AT) to the existing user.

[0127] When the account management server returns the user's OpenID to the first server, and the account management server does not return the mobile phone number to the first server, the first server executes the subsequent account binding process.

[0128] S406. The first server determines the third-party server of the target third-party application based on the identity information of the target third-party application, and sends the OpenID to the third-party server.

[0129] S407. The third-party server assigns a first access credential to the OpenID and returns this first access credential to the Changlian APP via the first server as a parameter of the login page of the target third-party application.

[0130] The first access credential is, for example, the sessionID. This first access credential is a one-time access credential.

[0131] S408, the Changlian APP launches the login page of the target third-party application with the first access credential parameter. At this time, the phone displays a first interface based on the launch result. The first interface includes the login page information of the target third-party application, and the login page information includes the first access credential.

[0132] In the embodiments of this application, the login page of the target third-party application can take various forms, which are illustrated below with examples:

[0133] (1) The login page of the target third-party application is a login card.

[0134] When the target third-party application is published on the first server, the login page of the target third-party application can be pre-configured to card mode, and the login page information is a login card object.

[0135] In some embodiments, a login card is preset on a first server. The first server determines that the login page is in card mode and sends the login card object corresponding to the target third-party application to the Changlian APP. The parameters of the login card object include a first access credential. The Changlian APP receives the login card object sent by the first server, and the parameters of the login card object include the first access credential.

[0136] The first server can determine the login card object corresponding to the target third-party application based on the application's identity information. This login card object includes parameters that describe the characteristics or functions of the login card. The first server can add a first access credential to the parameters of the login card object, thereby sending the first access credential along with the login card object to the Changlian APP. For example, the login card can be described by JavaScript code, and the login card object can be the download address of the JavaScript code and its corresponding parameters.

[0137] In other embodiments, the login card is pre-installed on a third-party server. In S408 above, the first server calls the third-party server interface in real time to send the OpenID to the third-party server. The third-party server assigns a first access credential to the OpenID, adds the first access credential to the parameters of the login card, and sends the login card object with the added first access credential to the first server; the first server forwards the login card object with the added first access credential to the Changlian APP.

[0138] Accordingly, the above S408 can specifically be: The Changlian APP displays the login card based on the login card object.

[0139] Among them, the login card is a static resource. Considering the instability and latency of the network, compared with pre-setting the login card on a third-party server, pre-setting the login card on the first server allows the mobile device manufacturer to perform acceleration and other processing, thus resulting in higher performance and reliability.

[0140] (2) The login page of the target third-party application is the 5th generation Hypertext Markup Language H5 login page.

[0141] When the target third-party application is published on the first server, its login page can be pre-configured to a page-based mode, with the login page information being the concatenated address of the H5 login page. The first server confirms the login page is in page mode and sends account authorization information, including the OpenID, to the third-party server. The third-party server assigns a first access credential to the OpenID. If the third-party server determines it supports the target third-party application's H5 login page, it concatenates the first access credential with the H5 login page address and returns the concatenated H5 login page address to the first server. The Changlian APP receives the concatenated H5 login page address sent by the first server.

[0142] The first server can determine the third-party server based on the identity information of the target third-party application received from the Changlian APP, and then send the first access credential to the third-party server. The account authorization information sent by the first server to the third-party server includes the first access credential; it may or may not include the identity information of the target third-party application.

[0143] The H5 login page address can be the address of an existing login page in the target third-party application, such as the HTTP address of the login page. The binding process can reuse the existing H5 login page, without requiring the target third-party application to design a separate login page for account binding.

[0144] The way the initial access credential is concatenated with the H5 login page address is quite flexible. For example, the initial access credential can be appended to, before, or within, the H5 login page address. In other words, the third-party server can append the initial access credential to the H5 login page address. Subsequently, the third-party server can provide the target third-party application's H5 login page based on the concatenated H5 login page address.

[0145] Accordingly, S408 can specifically be: The Changlian APP sends an H5 login page request to the third-party server, the request including the first access credential. The Changlian APP receives the content of the H5 login page sent by the third-party server and displays the H5 login page.

[0146] The Changlian APP calls the concatenated address of the H5 login page to request the target third-party application's H5 login page from the third-party server.

[0147] The third-party server returns the content of the H5 login page to the Changlian APP. The Changlian APP uses a web browser to load this H5 login page, which the user can then see on their screen. The H5 login page can display information such as username and password input fields provided by the target third-party application to the user.

[0148] (3) The login page of the target third-party application is the login page of the native application, that is, the login page of the native target third-party application.

[0149] When the target third-party application is published on the first server, its login page can be pre-configured to a page mode for account binding. The login page information is a concatenated address of the native application's login page, such as a DeepLink address of the concatenated native application's login page. The first server determines that the login page is in page mode and sends account authorization information, including the OpenID, to the third-party server. The third-party server assigns a first access credential to the OpenID. If the third-party server determines that it supports the target third-party application's native application login page, it concatenates the first access credential with the DeepLink address of the native application's login page and returns the concatenated DeepLink address of the native application's login page to the first server. The Changlian APP receives the concatenated DeepLink address of the native application's login page sent by the first server.

[0150] The first server can determine the third-party server based on the identity information of the target third-party application received from the Changlian APP, and then send the first access credential to the third-party server. The account authorization information sent by the first server to the third-party server includes the first access credential; it may or may not include the identity information of the target third-party application.

[0151] In other words, the third-party server can append the initial access credentials to the DeepLink address of the native application's login page. Subsequently, the third-party server can use the appended DeepLink address of the native application's login page to provide the target third-party application's native application login page.

[0152] Accordingly, the above S408 can specifically be: The Changlian APP displays the native application login page based on the DeepLink address of the concatenated native application login page.

[0153] The Changlian app can launch the native app login page based on the DeepLink address of the concatenated native app login page. Here, the native app login page refers to the login page of the target third-party app.

[0154] (4) The login page of the target third-party application is the quick app login page of the target third-party application.

[0155] The corresponding processing flow in this case is similar to that in case (3) above, except that the address of the original application login page is replaced with the address of the quick app login page of the target third-party application. For example, the DeepLink address of the original application login page is replaced with the DeepLink address of the quick app login page. That is to say, the third-party server can append the OpenID to the DeepLink address of the quick app login page and return the appended DeepLink address of the quick app login page to the Changlian APP so that the Changlian APP can display the quick app login page.

[0156] It is worth noting that the login page of this quick app is a login page developed based on a third-party quick app. However, it is not a login page that the target third-party app already has, but rather a login page that is not specifically designed for the account binding process. Therefore, it does not add any extra development process or workload to the target third-party app in order to bind it with the Changlian APP.

[0157] It's important to note that the third-party server includes the first access credential in the concatenated login page address returned to the first server, meaning the login page and the first access credential are bound together. This allows the Changlian app to subsequently obtain the user's entered account for the target third-party application by displaying the login page, and then submit both the user account and the first access credential to the third-party server for account binding.

[0158] If the third-party server determines that it supports multiple page types, it can return the addresses corresponding to one or more of these page types to the first server. For example, different page types have different priorities, and the third-party server can return the address corresponding to the page type with the highest priority to the first server. Alternatively, the third-party server can randomly select the address corresponding to a page type and return it to the first server.

[0159] For example, as described above, when a user clicks... Figure 5 After the "Unbound" control shown in (f), the electronic device displays as follows: Figure 5 The interface shown in (g) displays the login page of the target third-party application (such as the login page of a travel assistant).

[0160] S409. When the mobile phone detects the user account of the target third-party application entered by the user, the mobile phone submits the user account of the target third-party application and the first access credential to the third-party server.

[0161] The Changlian APP displays the login page of the target third-party application. Users can enter the target third-party application's username and password on this page. After detecting a user's instruction to bind the target third-party application's user account and the Changlian APP's user account, the Changlian APP can send account binding information to the third-party server. This account binding information includes the target third-party application's user account and OpenID. For example, when a user... Figure 5 After entering the user account of the travel assistant in the interface shown in (g), the user clicks the "Verify and Bind" control, and the mobile phone submits the user account of the target third-party application and the first access credential to the third-party server.

[0162] S410, Third-party server verifies the user account of the target third-party application.

[0163] S411. After the third-party server verifies the application, the third-party server can establish a binding relationship between the user account of the target third-party application and the OpenID, that is, establish a binding relationship between the user account of the target third-party application and the user account of the Changlian APP.

[0164] Simultaneously, the third-party server assigns a second access credential to the OpenID. Furthermore, the third-party server generates an account binding success message, which includes the second access credential.

[0165] For example, after the user account verification for the target third-party application is successful, the third-party server confirms successful login and notifies the user of this success on the login interface. At this time, the Changlian APP displays a similar success message, showing the login success page for the target third-party application. For example, when the user clicks... Figure 5 The "Verify and Bind" control shown in (g) verifies the first access credential through a third-party server. After the third-party server successfully verifies the first access credential, it sends the verification result to the mobile phone via the first server. At this point, the mobile phone's display interface changes from... Figure 5 The interface shown in (g) will redirect to... Figure 5 The interface shown in (h) is shown in the middle.

[0166] S412. The third-party server pushes a successful account binding message to the first server. This successful account binding message includes a second access credential.

[0167] For example, the third-party server can push a message indicating successful account binding to the first server. This message may include a second access credential. The message may also include the user account of the target third-party application.

[0168] S413, The mobile phone obtains the account binding success information from the first server.

[0169] The account binding success information obtained by the mobile phone from the first server may not include access credentials.

[0170] The "account binding successful" message indicates that the third-party server has successfully bound the user account of the Changlian APP to the user account of the target third-party application. For example, the Changlian APP can periodically query the first server for binding information to confirm that the user account of the target third-party application has been successfully bound to the user account of the Changlian APP. Alternatively, the Changlian APP can receive a push notification from the first server to confirm that the user account of the target third-party application has been successfully bound to the user account of the Changlian APP.

[0171] S414, the Changlian APP displays a page indicating successful binding.

[0172] This successful binding page indicates that the Changlian APP and the target third-party application have been bound. For example, the Changlian APP detects that the user clicked... Figure 5 After the "Complete" control shown in (h) is displayed, it can be shown Figure 5 The page shown in (i) indicates that the user account of the Changlian APP and the target third-party application has been successfully bound.

[0173] Following S414, the method further includes:

[0174] S415. The third-party server assigns a third access credential to OpenID at fixed time intervals.

[0175] This should be understood as the third-party server periodically assigning third access credentials to OpenID. Specifically, the third-party server periodically pushes account binding success information to the first server, which carries the third access credentials assigned to OpenID by the third-party server at fixed time intervals. When the second access credential is valid, the third access credential can be the second access credential; when the second access credential is invalid, the third access credential can be the third access credential.

[0176] After establishing a binding relationship between the target third-party application's user account and OpenID on the third-party server (i.e., establishing a binding relationship between the target third-party application's user account and the Changlian APP's user account), the first server can access the third-party server using the second access credential, and the third-party server can also access the first server using the OpenID. A specific implementation example is as follows:

[0177] Example 1:

[0178] S416. The third-party server pushes the first content corresponding to the user-related event to the Changlian APP corresponding to the OpenID according to the binding relationship.

[0179] When a user association event is generated by a third-party server, the server pushes the first piece of content corresponding to the user association event to the Changlian APP corresponding to the OpenID in the binding relationship, thereby recommending the first piece of content corresponding to the user association event to the user through the Changlian APP. Correspondingly, the Changlian APP can receive the first piece of content corresponding to the user association event pushed by the third-party server.

[0180] After successful account binding, the third-party server can push the first content corresponding to the user's associated events to the Changlian APP corresponding to the OpenID based on the binding relationship. That is, it recommends events of interest to the user that are occurring in the target third-party application to the Changlian APP. After the Changlian APP obtains the first content corresponding to the user's associated events pushed by the third-party server, it can display the user's associated events to the user in the form of cards or other means, so that the user can promptly understand the relevant information of the target third-party application they are interested in.

[0181] S417. The Changlian APP displays the first content corresponding to the user-related events recommended by the target third-party application on the main page of the Changlian APP.

[0182] S418. The mobile phone detects a second operation by the user on the first content. The second operation is used to instruct the first server to access a third-party server to obtain the second content corresponding to the user-associated event.

[0183] The second content can be understood as the detailed content of the first content, or the second content can be understood as further details of the first content.

[0184] For example, if the target third-party application is a food delivery application, the user-related event can be the delivery event of the user's order. When the user wants to learn more about the details of the delivery event of the user's order, the user interacts with the delivery event of the user's order to obtain more detailed information such as "delivery time" and "delivery distance".

[0185] S419. In response to the second operation, the mobile phone requests the first server to send an access request to the third-party server, the access request carrying the second access credential.

[0186] In response to a user action, the mobile phone requests the first server to send an access request, which includes a second access credential. Additionally, the access request may also include an event identifier and the access requirement. The third-party server then returns the content corresponding to the user-related event to the first server.

[0187] The second access credential has a validity period, which can refer to the start time, end time, or time period of validity. For example, the validity period of the second access credential may be 1 hour, 30 minutes, or 2 hours. The valid start time of the second access credential is January 1, 2021, and the valid end time is August 1, 2021. Alternatively, the valid start time of the second access credential is 11:00 AM on January 1, 2021, and the valid end time is 1:00 PM on January 1, 2021. A second access credential is considered valid if it is within its validity period; it is considered invalid if it is outside its validity period.

[0188] In one possible implementation, the third-party server verifies the second access credential by checking its validity. If the third-party server determines that the second access credential is invalid, it assigns a third access credential to the OpenID. This third access credential is different from the second access credential.

[0189] In this embodiment of the application, if the access credentials carried by the first server when calling the third-party server have expired, the third-party server will identify that the user is still a legitimate user before returning the AT expiration error code and will then reassign the access credentials to the first server. After receiving the AT expiration error code, the first server will re-query the access credentials of the third-party server.

[0190] The S420 and the Connect app display the content feedback page.

[0191] The mobile phone retrieves the second content corresponding to the user-related event from the first server based on the access request from the third-party server, and displays the second content corresponding to the user-related event. For example, the page displayed by the Changlian APP includes detailed information about the user's order delivery event, such as "delivery time" and "delivery distance".

[0192] In this embodiment, a third-party server can push events to users of the Changlian APP, and Changlian APP users can access controlled resources without a password using the third-party server's account. Specifically, after obtaining the access credentials (such as a unique identifier like OpenID) of the Changlian APP, the third-party server pushes a second access credential (such as AT) assigned by the third-party server to the first server corresponding to the OpenID of the Changlian APP user account. Subsequently, when the Changlian APP accesses the third-party server, it carries the access credential assigned by the third-party server as an authentication parameter. This two-way binding relationship allows the first server to carry the second access credential assigned by the third-party server when calling the third-party server, and also allows the third-party server to carry the second access credential assigned by the first server when calling the first server. Both parties can manage the validity period of the access credentials, and only one user authorization login is required to complete the process.

[0193] Example 2:

[0194] An electronic device receives a third operation from a user on a target interface element in a first application's first interface. This target interface element is provided by a second application. In response to the third operation, the electronic device requests a first server to send a second access request to a second server. This second access request carries a second access credential for requesting access to the content corresponding to the target interface element. The first server sends the second access request to the second server. The second server receives the second access request from the first server. The second server retrieves the content corresponding to the target interface element based on the second access request. The second server sends the content corresponding to the target interface element to the first server. The first server returns the content corresponding to the target interface element to the electronic device. The application interface of the first application on the electronic device displays the content corresponding to the target interface element.

[0195] For example, when the user operates Figure 5 (c)- Figure 5 The target interface element in the interface described in (e), such as the user clicks Figure 5 When the electronic device clicks the "Menu" control in "Connect Service Name 1" as shown in (c), it sends a request to the first server to access the second server. The second server then performs a menu content retrieval operation based on this request. For example, if the user clicks... Figure 5 When the "Press and hold to start speaking" control in "Connect Service Name 2" shown in (e), the electronic device sends a request to the first server to access the second server, which carries audio content. The second server returns a corresponding response based on the audio content.

[0196] It should be noted that in some other embodiments, the account binding method may include some steps in the above process. In some other embodiments, the account binding method may also include steps other than those shown in the above process.

[0197] In other embodiments, the login card may also include a redirection control for redirecting to an H5 login page, a native application login page, or a quick app login page for account login.

[0198] In some embodiments, the account management server, the negative one screen server, or the third-party server mentioned above can be a cloud server or other servers.

[0199] The above mainly uses the negative one screen, which shares the same user account as the mobile phone, as an example for explanation. In other embodiments, the first application may also be other applications that share the same user account as the mobile phone, such as system applications (such as the status bar). This application will not provide examples of each of these.

[0200] In some other embodiments, the first application may also be an application that does not share the same user account as the mobile phone. For example, the first application may be a platform application that can display events recommended by the target third-party application. For instance, the negative one screen may display user-related events recommended by other applications. In this case, the OpenID corresponding to the first application is no longer the OpenID assigned by the mobile phone's account management server, but rather the OpenID assigned by the account management server corresponding to the first application, such as the negative one screen.

[0201] In some examples, the target third-party application can be an application with specific qualifications (such as stocks, medical, etc.). The solution provided in this application embodiment can be applied to the following scenarios: where the event cards displayed on the negative one screen cannot be developed by the mobile system due to constraints such as qualifications, but must be developed by the target third-party application, and therefore the target third-party application needs to be account-bound to the negative one screen.

[0202] In other embodiments, the first application may also display user-related events recommended by other applications that share the same user account as the first application, without needing the account binding process described above. For example, if the negative one screen shares a Huawei account with Huawei Video, the binding process is unnecessary, and the negative one screen can display user-related events recommended by Huawei Video.

[0203] In some other embodiments, the first application may also display user-related events recommended by other applications (such as news apps) that do not require account binding with the first application.

[0204] It should be noted that in the above embodiments, the account binding process is initiated by the first application. In other embodiments, the two-way account binding process can also be completed by the second application. For example, the second application can be a native application (FA) of a third-party application or a mini-program of a third-party application, which is launched by the first application. The way the second application initiates the account binding process is the same as the way the first application initiates the account binding process, and will not be described again here.

[0205] The following example uses the account binding process initiated by the second application. For instance, the first application is an application already authorized to log in to a Huawei user account, such as the Changlian APP, and the first server of the first application can be a Huawei server. The second application can be the developer's FA (User Account Provider), and the second server of the second application can be the developer's server. The account server can be the Huawei account server. The account SDK can be the Huawei account SDK. The following explanations address different scenarios:

[0206] Scenario 1: Obtain the user's mobile phone number and OpenID.

[0207] like Figure 6 The diagram shown illustrates an application scenario of an account binding method provided in this application. The method may include:

[0208] S601. The electronic device determines whether the second application has used the user account login authorization of the first application.

[0209] S602. The electronic device obtains user authorization information by calling the user account SDK of the first application through the second application.

[0210] For example, if the device detects that the user has not logged into the first application's user account, it first displays the account login page, then the account authorization page. If the user has already logged into the first application's user account, the device directly displays the authorization page. After successful authorization, the device can use the second application to call the first application's user account SDK to obtain user authorization information, such as a unique authorization code.

[0211] S603. The electronic device reports user authorization information to the second server through the second application.

[0212] S604. The second server uses the user authorization information to call the account server of the first application in exchange for the first access token of the user account of the first application.

[0213] The first access credential is carried by the first server when accessing the second server. Once the second server verifies the access credential, it indicates that the user is a legitimate user.

[0214] S605. The account server returns the user account's access token and refresh token.

[0215] The refresh token is used to exchange for a new access token after the access token expires. The refresh token generally has a much longer validity period than the access token; an access token might only be valid for one hour, while a refresh token is usually valid for 30 days or more.

[0216] S606. The second server uses the user's access token to call the account server and obtain the OpenID, avatar, nickname, mobile phone number (on demand), and email address (on demand) of the user account of the first application.

[0217] S607. The account server returns the OpenID, avatar, nickname, mobile phone number (if needed), and email address (if needed) of the user account of the first application.

[0218] S608, the second server compares the user's mobile phone number with the mobile phone numbers of existing users in the system.

[0219] If the second server finds the same mobile phone number, it considers the user of the first application and the user of the second application to be the same user, and thus establishes an association between the OpenID of the second application user and the first application user account. Alternatively, it can create a new user in the system based on the first application user's mobile phone number and establish an association between the OpenID of the second application user and the first application user. The second server also assigns access credentials (such as AT) to the first application user.

[0220] S609. The second server pushes the account binding event to the first server, carrying the second access credential AT assigned to the second server and the OpenID of the first application user as parameters.

[0221] S610: Users can click to follow the connected services they are interested in on the first application.

[0222] S611, The first application reports the service ID and user ID that the user is interested in as parameters to the first server.

[0223] S612. The first server saves the services that the user is interested in to the database and returns a success message to the first application service.

[0224] S613. After receiving the service follow success message, the first application initiates the account binding process by calling the first-side server, carrying the first application user ID and the service ID being followed.

[0225] S614. The first server queries the database based on the user ID and service ID to obtain the account binding status.

[0226] S615, The first server returns the user's account binding status to the electronic device.

[0227] Scenario 2: Obtaining OpenID, but not the user's mobile phone number.

[0228] like Figure 7 The diagram shown illustrates another application scenario of an account binding method provided in this application. The method may include:

[0229] S701, The electronic device determines whether the second application has used the user account login authorization of the first application.

[0230] S702. The electronic device obtains user authorization information by calling the user account SDK of the first application through the second application.

[0231] For example, if the device detects that the user has not logged into the first application's user account, it first displays the account login page, then the account authorization page. If the user has already logged into the first application's user account, the device directly displays the authorization page. After successful authorization, the device receives a unique authorization code.

[0232] S703: The electronic device reports user authorization information to the second server through the second application.

[0233] S704. The second server uses the user authorization information to call the account server of the first application in exchange for the first access token of the user account of the first application.

[0234] S705, The account server returns the user account's access token and refresh token.

[0235] S706. The second server uses the user's access token to call the account server and obtain the OpenID, avatar, and nickname of the user account of the first application.

[0236] S707, The account server returns the OpenID, avatar, and nickname of the user account of the first application.

[0237] S708, the second server returns the account login page of the second application, carrying the session ID (sessionID) mapped to the OpenID of the first application user as a parameter.

[0238] The sessionID is a temporary credential assigned to the first application after verifying the user's legitimacy. The first application then carries this identifier in subsequent requests.

[0239] S709, The second application submits the user account of the second application entered by the user, and carries the first access credential as a parameter.

[0240] S710, The second server verifies the correctness of the user account submitted by the user for the second application.

[0241] S711. After the second server verifies the application, establish the association between the OpenID of the user in the second application and the user in the first application.

[0242] S712, the second server pushes the account binding event to the first server, carrying the second access credential AT assigned to the first application user and the first application user's OpenID as parameters.

[0243] S713: Users can click to follow the connected services they are interested in on the first application.

[0244] S714. The first application reports the service ID and user ID that the user is interested in as parameters to the first server.

[0245] S715. The first server saves the services that the user is interested in to the database and returns a success message to the first application service.

[0246] S716. After receiving the service follow success message, the first application initiates the account binding process by calling the first-side server, carrying the first application user ID and the service ID being followed.

[0247] S717. The first server queries the database based on the user ID and service ID to obtain the account binding status.

[0248] S718, The first server returns the user's account binding status to the electronic device.

[0249] The above description uses a mobile phone as an example of an electronic device. The account binding method provided in this application embodiment can also be applied to other electronic devices such as tablets or in-vehicle systems, which will not be described in detail in this application embodiment.

[0250] It is understood that, in order to achieve the above functions, the electronic device includes hardware and / or software modules that perform the respective functions. Based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0251] This embodiment can divide the electronic device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0252] For example, in one method of division, see [link to relevant documentation]. Figure 8 The electronic device 800 may include: a display module 801, a processing module 802, a communication module 803, and a storage module 804.

[0253] The display module 801 can be used to support the display of a user interface by the electronic device 800. For example, the display module 801 can be used to support the electronic device 800 in performing operations. Figure 4 S401, S402, S403, S408, S414, S417, S420, etc. in the process shown, and / or other processes used in the technology described herein.

[0254] The processing module 802 can be used to control and manage the actions of the electronic device 800. For example, the processing module 802 can be used to support the electronic device 800 in performing... Figure 4 S404, S408, S418, etc. in the process shown, and / or other processes used in the technology described herein.

[0255] The communication module 803 can be used to support communication between the electronic device 800 and other devices. For example, the communication module 803 can be used to support the electronic device 800 in performing... Figure 4 S405, S409, S413, S419, etc. in the process shown, and / or other processes used in the technology described herein.

[0256] The storage module 804 can be used to store instructions and data, such as storing the code of the first application, storing the OpenID obtained by the electronic device 800 through the communication module, and storing user account information entered by the user.

[0257] The display module 801 can be a display, for example, it can be a specific display. Figure 4 The hardware structure shown includes a display screen 194. The processing module 802 can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, digital signal processing (DSP), and microprocessors, etc. For example, the processing module 802 may specifically be... Figure 4 The processor 110 in the hardware structure shown. The communication module 803 can be a device that interacts with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, or a Wi-Fi chip. For example, the communication module 803 may include... Figure 4 The hardware structure shown includes a mobile communication module 150, a wireless communication module 160, and antenna 1 or antenna 2. The storage module 804 can be a memory, for example, specifically... Figure 4 The internal memory 18 in the hardware structure shown.

[0258] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0259] This application also provides an electronic device, including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, including computer instructions. When the one or more processors execute the computer instructions, the electronic device performs the aforementioned method steps to implement the account binding method in the above embodiments.

[0260] Embodiments of this application also provide a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the account binding method in the above embodiments.

[0261] Embodiments of this application also provide a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement the account binding method performed by the electronic device in the above embodiments.

[0262] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component or module. The apparatus may include a connected processor and a memory. The memory is used to store computer execution instructions. When the apparatus is running, the processor can execute the computer execution instructions stored in the memory to cause the chip to execute the account binding method executed by the electronic device in the above method embodiments.

[0263] Embodiments of this application also provide a chip system applied to an electronic device. The chip system includes one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines. The interface circuits are used to receive signals from the electronic device's memory and send signals to the processor, the signals including computer instructions stored in the memory. When the processor executes the computer instructions, it causes the electronic device to perform the account binding method provided in the above-described method embodiments.

[0264] In this embodiment, the electronic device, computer storage medium, computer program product or chip are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding method provided above, and will not be repeated here.

[0265] Another embodiment of this application provides a system, the architecture of which can be seen in the schematic diagram. Figure 2 Each device in this system can be used to implement the account binding method in the above method embodiments.

[0266] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0267] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0268] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0269] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0270] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0271] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An account binding method, characterized in that, The method comprises: logging in a user account of a first application; receiving a first operation of a user, the first operation being used to indicate associating a second application with the first application; in response to the first operation, sending an account binding request to a first server of the first application, the account binding request carrying a user account of the first application, an OpenID corresponding to the user account of the first application, and identity information of the second application, and being used for the first server to send the OpenID to a second server of the second application; receiving login page information of the second application returned by the first server, the login page information comprising a first access credential, the first access credential being assigned to the OpenID by the second server of the second application; displaying a login page of the second application according to the login page information of the second application; receiving a user account of the second application input by the user on the login page of the second application; submitting the user account of the second application and the first access credential to the second server, for the second server to verify the user account of the second application, and after verification, finding the OpenID corresponding to the user account of the first application according to the first access credential, assigning a second access credential to the OpenID, and establishing a binding relationship between the OpenID corresponding to the user account of the first application and the user account of the second application; wherein the second access credential is used for the first server to perform identity authentication on behalf of the user account of the first application when accessing the second server; receiving account binding success information from the first server, the account binding success information being generated by the second server.

2. The method of claim 1, wherein, After receiving the account binding success information from the first server, the method further comprises: receiving first content corresponding to a user association event from the first server; receiving a second operation of the user on the first content; in response to the second operation, requesting the first server to send a first access request to the second server, the first access request carrying the second access credential, and being used to request second content corresponding to the user association event, the second content being details of the first content; receiving the second content from the first server, the second content being fed back by the second server according to the first access request.

3. The method of claim 1, wherein, After receiving the account binding success information from the first server, the method further comprises: receiving a third operation of the user on a target interface element in a first interface of the first application, the target interface element being provided by the second application; in response to the third operation, requesting the first server to send a second access request to the second server, the second access request carrying the second access credential, and being used to request content corresponding to the target interface element.

4. The method according to any one of claims 1 to 3, characterized in that, Before sending the account binding request to the first server of the first application, the method further comprises: calling an account management SDK of the first application through the first application, and obtaining the OpenID corresponding to the user account of the first application from an account management server.

5. The method according to any one of claims 1 to 3, characterized in that, The first application is a home screen or a pass-through application.

6. An account binding method, characterized by, Comprising: receiving an account binding request sent by an electronic device, the account binding request carrying a user account of a first application, an OpenID corresponding to the user account of the first application, and identity information of a second application; sending the OpenID to a second server of the second application according to the identity information of the second application; receiving login page information of the second application returned by the second server, the login page information including a first access credential, the first access credential being assigned to the OpenID by the second server; sending the login page information to the electronic device for displaying a login page of the second application by the electronic device; receiving a user account of the second application and the first access credential input by a user on the login page; sending the user account of the second application and the first access credential to the second server, the second server being configured to verify the user account of the second application, find the OpenID corresponding to the user account of the first application according to the first access credential after verification, assign a second access credential to the OpenID, and establish a binding relationship between the OpenID corresponding to the user account of the first application and the user account of the second application; wherein the second access credential is used for identity authentication of the first server when accessing the second server on behalf of the user account of the first application; receiving account binding success information sent by the second server, the account binding success information carrying the second access credential, the account binding success information being generated by the second server.

7. The method of claim 6, wherein, After receiving the account binding success information sent by the second server, further comprising: receiving first content corresponding to a user association event sent by the second server; sending the first content to the electronic device for displaying the first content by the electronic device; in response to a first operation of a user on the first content, sending a first access request to the second server, the first access request carrying the second access credential, for accessing second content corresponding to the user association event, the second content being details of the first content; receiving the second content sent by the second server; sending the second content to the electronic device for displaying the second content by the electronic device.

8. The method of claim 6, wherein, After receiving the account binding success information sent by the second server, further comprising: in response to a second operation of a user on a target interface element in a first interface of the first application, the target interface element being provided by the second application; sending a second access request to the second server, the second access request carrying the second access credential, for requesting the second server to obtain content corresponding to the target interface element.

9. The method according to any one of claims 6-8, characterized in that, The first application is a home screen or a pass-through application.

10. An account binding method, characterized in that, Comprising: receiving, by a first server of a first application, an account binding request sent by the first server, the account binding request carrying an OpenID corresponding to a user account of the first application; allocating a first access credential for the OpenID; returning, to the first server, login page information of a second application, the login page information including the first access credential; receiving, by the electronic device, the user account of the second application and the first access credential sent by the electronic device; verifying the user account of the second application; after verification, finding the OpenID according to the first access credential, allocating a second access credential for the OpenID, and establishing a binding relationship between the OpenID corresponding to the user account of the first application and the user account of the second application; wherein the second access credential is used by the first server to perform identity authentication on behalf of the user account of the first application when accessing a second server; generating account binding success information, the account binding success information carrying the second access credential; sending the account binding success information.

11. The method of claim 10, wherein, After sending the account binding success information, further comprising: sending, to the first server, first content corresponding to a user association event; receiving, by the first server, a first access request sent by the first server, the first access request carrying the second access credential, and used to access second content corresponding to the user association event, the second content being details of the first content; sending, to the first server, the second content according to the first access request.

12. The method of claim 10, wherein, After sending the account binding success information, further comprising: receiving, by the first server, a second access request sent by the first server, the second access request carrying the second access credential, and used to obtain content corresponding to a target interface element; sending, to the first server, the content corresponding to the target interface element.

13. The method according to claim 11 or 12, characterized in that, After receiving the access request sent by the first server, further comprising: determining that the second access credential is invalid; allocating a third access credential for the OpenID, the third access credential being different from the second access credential; carrying the third access credential in the account binding success information and sending the account binding success information to the first server.

14. The method according to any one of claims 10-12, characterized in that, The first application is a negative one screen or a smooth connection application.

15. An account management system, comprising: Comprising: an electronic device, a first server of a first application, an account management server of the first application, and a second server of a second application; wherein the electronic device logs in a user account of the first application; the electronic device receives a first operation of a user, the first operation being used to indicate that the second application is associated with the first application; in response to the first operation, the electronic device sends an account binding request to the first server, the account binding request carrying the user account of the first application, an OpenID corresponding to the user account of the first application, and identity information of the second application; the first server receives the account binding request sent by the electronic device; the first server finds a second server of the second application according to the identity information of the second application; The first server sends the OpenID to the second server; The second server allocates a first access credential for the OpenID; The second server returns login page information of the second application to the first server, the login page information including the first access credential; The first server receives the login page information of the second application returned by the second server, the login page information including the first access credential, the first access credential being allocated by the second server for the OpenID; The first server sends the login page information of the second application to the electronic device; The electronic device displays a login page of the second application according to the login page information of the second application; In response to a user inputting a user account of the second application on the login page of the second application, the electronic device sends the user account of the second application and the first access credential to the second server; The second server verifies the user account of the second application, and after verification, finds the OpenID of the user of the first application according to the first access credential, allocates a second access credential for the user of the first application, and establishes a binding relationship between the OpenID corresponding to the user account of the first application and the user account of the second application; wherein the second access credential is used by the first server to perform identity authentication on behalf of the user account of the first application when accessing the second server; The second server generates account binding success information, and the account binding success information carries the second access credential; The first server receives the account binding success information sent by the second server.

16. An electronic device, comprising: comprise: one or more processors; and a memory, the memory having code stored therein; which when executed by the electronic device, causes the electronic device to perform the account binding method of any one of claims 1-5.

17. A server, comprising: comprise: one or more processors; and a memory, the memory having code stored therein; which when executed by the server, causes the server to perform the account binding method of any one of claims 6-9, or the server to perform the account binding method of any one of claims 10-14.

18. A computer storage medium, comprising, comprise computer instructions which, when executed on an electronic device and a server, cause the electronic device to perform the account binding method of any one of claims 1-5, or cause the server to perform the account binding method of any one of claims 6-9, or the server to perform the account binding method of any one of claims 10-14.

19. A computer program product, characterised in that, when the computer program product is executed on a computer, causes the computer to perform the account binding method of any one of claims 1-5, or the account binding method of any one of claims 6-9, or the account binding method of any one of claims 10-14.

Images