Account binding method and device, electronic equipment and storage medium
After the account addition control triggers on the account addition page, the account binding prompt page of the communication application is displayed and the account binding is realized, the problem of the cumbersome account binding process in the existing technology is solved and the binding efficiency is improved.
Patent Information
- Application Number
- CN202311156842.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-06
- Publication Date
- 2025-03-07
Smart Images

Figure CN119583501A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computers, and in particular to an account binding method, device, electronic device and storage medium. Background Art
[0002] In the prior art, when a user needs to add a new email account in a mailbox application, he usually needs to submit server information related to the email account, including server type, receiving / sending server address, port number, user name, password, etc. The server verifies the above server information, and only after the verification is passed can the new email account be added to the mailbox application.
[0003] However, the above process is rather cumbersome, resulting in low binding efficiency when users add new email accounts. Summary of the invention
[0004] The embodiments of the present application provide an account binding method, device, electronic device and storage medium, which can improve the problem of low account binding efficiency in the prior art.
[0005] The present application embodiment provides an account binding method, which is applied to a terminal device, and the method includes:
[0006] Displaying an account adding page, wherein the account adding page includes an account adding control, wherein the account adding control is used to implement binding of the first account and the second account;
[0007] In response to a triggering operation for adding a control to the account, displaying an account binding prompt page of the communication application, wherein the account binding prompt page includes account binding prompt information;
[0008] In response to a confirmation operation on the account binding prompt information, the first account is bound to the second account.
[0009] The present application embodiment provides an account binding device, which is applied to a terminal device, and the device includes:
[0010] A page display unit, used to display an account adding page, wherein the account adding page includes an account adding control, wherein the account adding control is used to implement binding of the first account and the second account;
[0011] a trigger response unit, configured to display an account binding prompt page of the communication application in response to a trigger operation for adding a control to the account, wherein the account binding prompt page includes account binding prompt information;
[0012] A confirmation response unit is used to bind the first account with the second account in response to a confirmation operation on the account binding prompt information.
[0013] In one embodiment, the trigger response unit includes:
[0014] A protocol generation subunit, configured to generate a target protocol in response to a triggering operation of adding a control to the account;
[0015] The program jump subunit is used to jump to the communication application when the communication application responds to the target protocol, and display the account binding prompt page of the communication application.
[0016] In one embodiment, the protocol generation subunit includes:
[0017] A trigger response sub-subunit, for jumping to an information browsing application in response to a trigger operation for adding a control to an account;
[0018] The information combination sub-unit is used to obtain a preset protocol format and combine the preset protocol format with the first account information into a target protocol, wherein the predicted protocol format is generated by the communication application.
[0019] In one embodiment, the communication application includes a communication sub-plug-in; the device also includes:
[0020] An information display unit is used to display the communication information related to the first account in the communication sub-plug-in.
[0021] In one embodiment, the terminal device is a terminal device running a desktop operating system; the apparatus further comprises:
[0022] an information code acquisition unit, configured to send an information code acquisition request to a server when the communication application does not respond to the target protocol;
[0023] An information code receiving unit, configured to receive an information code returned by the server, wherein the information code carries the first account information and encryption information, wherein the encryption information includes the first account information and information of the time when the information code is generated by the first account information;
[0024] An information code display unit is used to display the information code on a display interface so that a mobile terminal can scan the information code and send the first account information and the encrypted information to a server, and after the server verifies the first account information and the encrypted information, the communication application is run on the mobile terminal, and based on the first account information, the binding of the first account and the second account is achieved.
[0025] In one implementation, the terminal device is a terminal device running a mobile operating system; the apparatus further includes:
[0026] A download prompt display unit, used to display download prompt information on a display interface when the communication application does not respond to the target protocol;
[0027] A program downloading unit is used to download the communication application program on the terminal device in response to a confirmation operation on the download prompt information.
[0028] In one embodiment, the device further comprises:
[0029] An information receiving unit is used to receive preset communication information in an application logged in with the first account, wherein the preset communication information includes the account adding control.
[0030] In one embodiment, the communication application includes a communication sub-plug-in; the device also includes:
[0031] An account information receiving unit, configured to receive a first account and account verification information in the communication sub-plug-in, and send the first account and account verification information to a server for verification;
[0032] An inquiry information sending unit, configured to display an information sending inquiry information on a display interface when the server returns a verification failure prompt message, wherein the information sending inquiry information is used to inquire whether to send the preset communication information to the first account;
[0033] A determination response unit is used to return a determination sending message to the server in response to a determination operation on the information sending inquiry information, so that the server sends the preset communication information to the first account based on the determination sending message.
[0034] In one embodiment, the confirmation response unit includes:
[0035] a target type determination subunit, configured to determine whether the first account is a target type account in response to a confirmation operation on the account binding prompt information;
[0036] a preset requirement determination subunit, configured to determine, when the first account is a target type account, that the account adding setting information of the communication application satisfies the preset requirement;
[0037] The account binding subunit is used to bind the first account and the second account and return binding success indication data.
[0038] In one embodiment, the first account information includes the first account and the time when the first account information is generated;
[0039] Account binding subunit, including:
[0040] An account information parsing sub-unit, configured to parse the first account information to obtain a generation time of the first account information;
[0041] A time comparison sub-unit, used to compare the generation time of the first account information with the current time;
[0042] A requirement determination sub-subunit, used for determining whether the account adding setting information of the communication application meets the preset requirement when the time span between the generation time of the first account information and the current time does not exceed the preset time length;
[0043] A lock generation sub-subunit, configured to generate a lock program for the first account and the second account when the account adding setting information of the communication application meets a preset requirement, wherein the duration of the lock program is a first time length;
[0044] The account binding sub-subunit is used to bind the first account to at least one binding identifier of the communication application program where the second account is located during the duration of the locking program.
[0045] In the account binding method provided in the embodiment of the present application, an account adding page including an account adding control may be displayed; in response to a user's triggering operation on the account adding control, an account binding prompt page of the communication application is displayed, and the account binding prompt page includes account binding prompt information. The account binding prompt page is displayed by the communication application in response to a target protocol, and the target protocol is generated by responding to a triggering operation on the account adding control. In response to a user's confirmation operation on the account binding prompt information, the first account is bound to the second account.
[0046] In the embodiment of the present application, when the account adding control on the account adding page is triggered and the communication application responds to the target protocol and displays the account binding prompt page, the user's confirmation operation for the account binding prompt information is responded to once again, and the binding process of the first account and the second account can be realized. Compared with the prior art, the tedious type setting or the trouble of entering a password is omitted, and the binding efficiency is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0048] Figure 1a This is a schematic diagram of an application scenario of the account binding method provided by this application;
[0049] Figure 1b It is a flowchart of the account binding method provided in the embodiment of the present application;
[0050] Figure 1c It is a schematic diagram of an implementation of an account adding page and an account adding control;
[0051] Figure 1d It is a schematic diagram of an implementation method of an account binding prompt page and account binding prompt information;
[0052] Figure 1e An interface diagram showing download prompt information;
[0053] Figure 1f An interface diagram showing the prompt information before the prompt email is sent
[0054] Figure 1g A schematic diagram showing an implementation of information sending inquiry information;
[0055] Figure 1h A schematic diagram showing an implementation of notifying information;
[0056] Figure 1i An interface diagram showing the communication sub-plugin displaying communication information related to the first account;
[0057] Figure 1j A schematic diagram showing an enterprise selection interface;
[0058] Figure 2 is a flowchart of an account binding method provided by another embodiment of the present application;
[0059] Figure 3 This is a structural diagram of an account binding device provided by an embodiment of the present application;
[0060] Figure 4 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0061] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0062] Embodiments of the present application provide an account binding method, device, electronic device, and storage medium.
[0063] The account binding device may be integrated into an electronic device, which may be a terminal, a server, or other device. The terminal may be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop, or a personal computer (PC). The server may be a single server or a server cluster consisting of multiple servers.
[0064] In some embodiments, the account binding device may also be integrated into multiple electronic devices. For example, the account binding device may be integrated into multiple servers, and the account binding method of the present application may be implemented by multiple servers.
[0065] In some embodiments, the server may also be implemented in the form of a terminal.
[0066] For more information, please see Figure 1a The method provided in an embodiment of the present application can display an account adding page, the account adding page includes an account adding control, wherein the account adding control is used to implement binding of a first account and a second account; in response to a triggering operation on the account adding control, an account binding prompt page of a communication application is displayed, the account binding prompt page includes account binding prompt information, wherein the account binding prompt page is displayed by the communication application in response to a target protocol, the target protocol is generated in response to a triggering operation on the account adding control, and the target protocol carries information of the communication application where the second account is located; in response to a confirmation operation on the account binding prompt information, the first account is bound to the second account.
[0067] The above method can realize the binding process of the first account and the second account by responding to the user's confirmation operation for the account binding prompt information once again when the account adding control on the account adding page is triggered and the communication application responds to the target protocol and displays the account binding prompt page. The above method saves the trouble of setting the account type or entering the password, and improves the binding efficiency.
[0068] It is understandable that in the embodiments of the present application, related data such as user information is involved. When the embodiments of the present application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
[0069] It should be noted that the serial numbers of the following embodiments are not intended to limit the preferred order of the embodiments.
[0070] In this embodiment, an account binding method is provided, such as Figure 1bAs shown, the account binding method is applied to an electronic device. The specific process of the method may include the following steps 110 to 130:
[0071] 110. Display an account adding page, wherein the account adding page includes an account adding control.
[0072] The account adding control carries the first account information, and the account adding control is used to implement binding between the first account and the second account.
[0073] The account adding page is a page for adding a new account. The account adding control is a control set on the account adding page for users to trigger. The first account information is information including the account content of the first account. The first account information can be recorded as a ticket parameter. The ticket parameter includes: the first account (recorded as alias), timestamp (recorded as time), binding type (recorded as bind_type), four-digit random string of base64 (recorded as rand), and binding reason (recorded as source). The timestamp is the moment when the first account information is generated; the binding type includes the following two types: binding through preset communication information, and binding by scanning an information code; the binding reason includes the following two types: account verification information verification failure, and receiving preset communication information sent by an administrator user. Specifically, the ticket parameter can be obtained by splicing the above data to obtain a splicing result, and the above splicing result is encrypted using the AES algorithm and the base64 algorithm.
[0074] The first account is an account for information communication between users. The first account can be an account of an instant messaging tool, including chat software, video conferencing software, etc.; it can also be an account of a non-instant messaging tool, including an e-mail, forum, blog, etc. The second account is an account different from the first account, for information communication between users. The second account can be an account of an instant messaging tool or an account of a non-instant messaging tool.
[0075] For ease of description, let's assume that the first account is not an instant messaging tool account, and the second account is an instant messaging tool account. Figure 1c In a specific implementation, the account adding page may be a receiving page of an e-mail box. The account adding control may be the receiving information displayed on the receiving page, specifically, it may be Figure 1c An "Add Now" virtual button is shown.
[0076] It should be understood that Figure 1cOnly one specific implementation of the account adding page and the account adding control is described. The account adding page can also be other pages, such as a posting interface of a forum, a chat interface of a chat software, etc.; the account adding control can also be in other forms, such as a virtual sliding module located on a virtual slide rail, etc. The specific forms of the account adding page and the account adding control should not be understood as limiting the present application.
[0077] 120. In response to a triggering operation for adding a control to the account, an account binding prompt page of the communication application is displayed, wherein the account binding prompt page includes account binding prompt information.
[0078] Among them, the account binding prompt page is displayed by the communication application in response to the target protocol, and the target protocol is generated in response to the trigger operation of adding a control to the account, and the target protocol carries information of the communication application where the second account is located.
[0079] The trigger operation is an operation for triggering the account adding control. The specific form of the trigger operation corresponds to the specific form of the account adding control. For example, if the account adding control is a virtual button, the trigger operation can be a tap operation; if the account adding control is a virtual sliding module located on a virtual slide rail, the trigger operation can be a sliding operation. It should be understood that the specific operation type of the trigger operation should not be understood as a limitation of the present application.
[0080] The communication application is a communication application running with the second account. In one embodiment, the communication application can be Figure 1c The B application is shown. The account binding prompt page is a page that prompts the user's account binding operation, and the account binding prompt information is text information located on the account binding prompt page that serves as a specific prompt. For details, please refer to Figure 1d The account binding prompt page can be the running interface of application B, and the account binding prompt information is a dialog box that pops up in application B.
[0081] The target protocol is information that carries the communication application where the second account is located. The specific generation process of the target protocol will be described in detail below.
[0082] In the above embodiment, the present application can generate a target protocol after responding to a trigger operation. If the target protocol receives a further response from the communication application, an account binding prompt page including account binding prompt information can be displayed.
[0083] Optionally, in a specific implementation, step 120 may specifically include the following steps 121 to 122:
[0084] 121. In response to a triggering operation of adding a control to the account, generate a target protocol.
[0085] The target protocol may be generated by a user performing a trigger operation on an account adding control. Optionally, in a specific implementation, the account adding control carries the first account information. Accordingly, step 121 may specifically include the following steps 1211 to 1213:
[0086] 1211. In response to a trigger operation for adding a control to an account, jump to an information browsing application.
[0087] The information browsing application is an application provided to the user so that the user can browse information. The information browsing application can specifically be a browser. After the electronic device receives the user's trigger operation to add a control to the account, it can jump to the information browsing application to perform subsequent steps.
[0088] 1212. Obtain a preset protocol format, and combine the preset protocol format with the first account information into a target protocol, wherein the predicted protocol format is generated by the communication application.
[0089] 1213. Run the target protocol through the information browsing application.
[0090] The preset protocol format is a pre-set protocol format, and the preset protocol format can be recorded as schema. Optionally, the preset protocol format can be the protocol format registered by the communication application in the operating system when the communication application is installed in the operating system of the electronic device. The operating system can control the communication application according to the preset protocol format. Optionally, the specific format of the preset protocol format can be: wxwork: / /
[0091] The target protocol is composed of a preset protocol format and the first account information, and the preset protocol format is registered in the operating system for the communication application running the second account. Therefore, the target protocol contains both the relevant information of the first account and the relevant information of the second account. Optionally, the target protocol can be specifically: wxwork: / / abcd; wherein wxwork: / / represents the preset protocol format, and abcd represents the first account information.
[0092] The information browsing application can attempt to wake up the communication application by running the target protocol. Whether the communication application responds to the target protocol, and the specific process corresponding to responding to the target protocol or not responding to the target protocol will be described in detail below.
[0093] In the above implementation, after receiving the user's trigger operation for adding controls to the account, the electronic device can jump to the information browsing application to prepare for the subsequent operation of the combined target protocol. The electronic device can also obtain a preset protocol format and combine the preset protocol format with the first account information to obtain the target protocol. The information browsing application can attempt to wake up the communication application by running the target protocol. The above implementation associates the first account and the second account through the target protocol to prepare for the subsequent binding of the first account and the second account.
[0094] Optionally, in a specific implementation, the communication application includes a communication sub-plug-in. Accordingly, before step 1211, the embodiment of the present application may also include the following steps S1 to S4:
[0095] S1. Receive a first account and account verification information in the communication sub-plug-in, and send the first account and account verification information to a server for verification.
[0096] The communication sub-plugin is a plug-in in the communication application for running the related functions of the first account. The account verification information is information for authenticating the user of the first account. The account verification information can be text information, such as an account password set by the user, or biometric information, such as fingerprint information, face information, iris information, etc. set by the user. It should be understood that the specific form of the account verification information should not be understood as a limitation on this application.
[0097] After receiving the first account and the account verification information, the electronic device may send the first account and the account verification information to the server so that the server can verify the above information. If the account verification information is successfully verified, the relevant functions of the first account can be directly run in the communication sub-plug-in. If the verification information fails to be verified, step S2 can be continued.
[0098] S2. If the server returns a verification failure prompt message, the message is displayed on the display interface and a query message is sent.
[0099] The information sending inquiry message is used to inquire whether to send the preset communication information to the first account. For details, please refer to Figure 1g The verification failure prompt information is a prompt information returned to the electronic device after the server verifies the first account and the account verification information and the verification fails.
[0100] After the preset communication information is received by the electronic device corresponding to the user and opened by the user, an account adding page including an account adding control may be displayed to the user.
[0101] In one implementation, the user may not be asked, but the preset communication information may be sent directly to the first account. After sending the preset communication information to the first account, the server returns a notification message to the electronic device. For details, see Figure 1h .
[0102] S3. In response to a determination operation on the information sending inquiry information, returning a determination sending message to the server, so that the server sends the preset communication information to the first account based on the determination sending message.
[0103] The confirmation sending message is used to indicate that the user corresponding to the electronic device has performed a confirmation operation on the information sending inquiry information.
[0104] After receiving the confirmation operation triggered by the user for the information sending inquiry information, the electronic device can return a confirmation sending message to the server. After receiving the confirmation sending message, the server can send the preset communication information to the first account.
[0105] S4. Receive preset communication information in the application logged in with the first account, wherein the preset communication information includes the account adding control.
[0106] The specific type of the application logged into the first account is related to the type of the first account. For example, if the first account is an instant messaging account, such as a chat software account, the application is the above chat software; if the first account is a non-instant messaging account, such as an email account, the application is an email application that can run an email account. It should be understood that the specific type of the application should not be understood as a limitation of the present application.
[0107] If the user receives and opens the preset communication information using the above-mentioned application logged in with the first account, the user can view the account adding page including the account adding control.
[0108] In the above implementation, the user can first choose to enter the first account and account verification information in the communication application to try to bind the first account with the second account. If the account verification information entered by the user is incorrect, the information sending inquiry information is displayed on the display interface of the communication application. After obtaining the user's confirmation operation on the information sending inquiry information, the server sends the preset communication information to the first account. The user can view the account adding page described in step 110 and the account adding control located on the account adding page by receiving and opening the preset communication information in the application logged in with the first account, so that the user can still implement the binding process of the first account and the second account in the case of forgetting the password, and increase the use scenario of the account binding operation.
[0109] Optionally, in addition to being triggered by the above steps S1 to S4, the preset communication message can also be triggered by the user setting of the administrator identity of application B. Let's take the first account as an email account and the second account as an instant messaging tool account as an example, the setting method of the administrator identity user is specifically described as follows:
[0110] If the user with administrator status is also the administrator of the corporate mailbox corresponding to the email account to be added, and the domain name corresponding to the email account to be added is in the whitelist, then after the user has added his own email account to application B, he can use the administrator status of the corporate mailbox to send reminder emails to the work emails of all members of the organization served by application B through the email account, and can also send reminder emails to all work emails in the domain name corresponding to the email account to be added through the email account.
[0111] The above reminder email is a preset communication message. The whitelist is a pre-set enterprise list database, which is set by an administrator or a person in charge of the enterprise. The organization can be a group organization such as an enterprise, a society, or a class.
[0112] If the user with administrator identity is not the administrator of the corporate mailbox corresponding to the mailbox account to be added, but the domain name corresponding to the mailbox account to be added is in the whitelist, then further judgment is made: among the work mailboxes used by members who use application B, whether the number of work mailboxes with the same domain name as the mailbox account to be added is not less than the set number.
[0113] If yes, after the user has added his / her email account in application B, the electronic device may pop up a pop-up message such as Figure 1f The prompt diagram shown prompts the user to send reminder emails to the work emails of all members of the organization served by application B through the email account. The user can also send reminder emails to all work emails in the domain name corresponding to the email account to be added through the email account.
[0114] If not, after the user has added his / her own email account in application B, the electronic device may pop up a message such as Figure 1f The prompt diagram shown prompts the user to send a prompt email to the work emails of all members of the organization served by application B through the email account.
[0115] If the domain name corresponding to the email account to be added is not in the whitelist, regardless of whether the administrator is the administrator of the corporate email corresponding to the email account to be added, after the user adds his own email account to application B, the user will send reminder emails to the work emails of all members of the organization served by application B through the email account.
[0116] The prompt email carries a ticket parameter, which is obtained by concatenating the first account (denoted as alias), timestamp (denoted as time), binding type (denoted as bind_type), a four-digit random string of base64 (denoted as rand), and binding reason (denoted as source), and the concatenated result is encrypted using the AES algorithm and the base64 algorithm.
[0117] In the above implementation, the scope of the work mailboxes that receive reminder emails can be determined based on the identity of the administrator user himself, and the relationship between the domain name corresponding to the email account to be added and the whitelist, so that the administrator user can send reminder emails in batches with one click, realize the reminder function for enterprise members, and thus help improve the work efficiency of enterprise members.
[0118] Optionally, in a specific implementation, the terminal device is a terminal device running a desktop operating system. Accordingly, after step 121, the embodiment of the present application may further include the following steps A1 to A3:
[0119] A1. If the communication application does not respond to the target protocol, send an information code acquisition request to the server.
[0120] Desktop operating system is a software system that runs on desktop terminal devices, such as personal computers (PCs), workstations, etc. Desktop operating systems include Windows, macOS, or Linux, etc.
[0121] The information code acquisition request is a message requesting to acquire the information code. The information code is a code system carrying information, and the information code can be a barcode, a QR code, etc. It should be understood that the specific type of the information code should not be understood as a limitation to the present application.
[0122] There may be the following situations where the communication application does not respond to the target protocol: the electronic device currently has no communication application installed; the electronic device has the above communication application installed, but the communication application is not in operation.
[0123] A2. Receive the information code returned by the server.
[0124] The information code carries the first account information and encryption information, and the encryption information includes the first account information and the time information when the first account information generates the information code; optionally, the encryption information can be recorded as an skey parameter.
[0125] The server receives an information code acquisition request sent by the electronic device, generates an information code based on the information code acquisition request, and returns the information code to the electronic device.
[0126] A3. Display the information code on the display interface so that a mobile terminal scans the information code and sends the first account information and the encrypted information to the server. After the server verifies the first account information and the encrypted information, the communication application is run on the mobile terminal, and based on the first account information, the first account and the second account are bound.
[0127] After the electronic device receives the information code returned by the server, it can display the information code on the display interface so that the user can scan the information code through a mobile terminal held by the user to obtain the first account information and encrypted information included in the information code. After obtaining the first account information and encrypted information, the mobile terminal can send the first account information and encrypted information to the server so that the server can verify the first account information and encrypted information.
[0128] The specific process of the server verifying the first account information and the encrypted information may be:
[0129] The server parses the encrypted information and obtains the parsed account information and time information. The server may first compare the parsed account information with the first account information carried by the information code. If the two are the same, the server calculates the difference between the current time and the above time information. If the difference between the two is less than the time length threshold, the server determines that the first account information and the encrypted information are verified, and the server may return the first account information to the above mobile terminal.
[0130] The mobile terminal can invoke the communication application installed on itself, and transmit the received first account information to the communication sub-plug-in of the communication application, thereby performing a binding process between the first account and the second account running on the communication application.
[0131] If the number of companies to which the second account corresponding to the communication application belongs is more than one, a multiple-option interface may pop up so that the user can select the company to be bound to the first account. For details, see Figure 1j ,exist Figure 1j In the application scenario shown, the second account can be a user's personal instant messaging account. Specifically, when the communication application scans the above information code, multiple companies corresponding to the second account can be determined according to a pre-set mapping list, and Figure 1j The above-mentioned multiple enterprises are displayed in the illustrated scene to facilitate the user to make a selection.
[0132] In a specific implementation, the above process can be implemented by the node layer of the electronic device calling the PortalCGI::QYGetCorpListByWxOpenID() program module.
[0133] The PortalCGI::QYGetCorpListByWxOpenID() program module can specifically perform the following process:
[0134] The ticket parameter is parsed based on the information code or preset communication information, and then the ticket parameter is judged whether it has expired based on the timestamp carried by the ticket parameter. If the time span between the timestamp and the current time does not exceed 7 days, it can be judged that the ticket parameter has not expired.
[0135] If the ticket parameter has not expired and the second account is the user's personal instant messaging account, it is further determined whether the number of first accounts bound by the scan code corresponding to the identity identifier of the second account does not exceed a set number threshold (such as 10).
[0136] If the number of first accounts bound by scanning the QR code exceeds the set threshold, a prompt message indicating that the addition failed will be returned.
[0137] If the number of first accounts bound by scanning the code does not exceed the set number threshold, all enterprises corresponding to the second account that are not bound to the first account can be obtained based on the identity identifier of the second account and displayed, such as Figure 1j shown.
[0138] After receiving the enterprise selected by the user, the program may jump to the PortalCGI::QYCheckBindVid() program module. The processing procedure of the PortalCGI::QYCheckBindVid() program module will be described below.
[0139] The duration of the time length threshold may be three minutes, or other time lengths, such as five minutes. It should be understood that the specific time length of the above-mentioned time length threshold should not be understood as a limitation to the present application.
[0140] If the mobile terminal fails to successfully invoke the communication application, it means that the communication application is not currently installed on the mobile terminal. A pop-up download prompt is used so that the user can go to the application store to download the communication application based on the download prompt. For details, please refer to Figure 1e , Figure 1e An interface diagram showing download prompt information.
[0141] In the above-mentioned implementation, if the terminal device is a desktop terminal device running a desktop operating system and the communication application does not respond to the target protocol, the terminal device can obtain an information code from the server and display the information code so that the user can scan the code through the mobile terminal held to realize the binding process of the first account and the second account, further expanding the application scenarios of the account binding process.
[0142] Optionally, in a specific implementation, the terminal device is a terminal device running a mobile operating system. Accordingly, after step 121, the embodiment of the present application may further include the following steps B1 to B2:
[0143] B1. If the communication application does not respond to the target protocol, a download prompt message is displayed on the display interface.
[0144] Mobile operating system is an operating system for mobile devices. Mobile devices include smartphones, tablets, and wearable devices. Download prompt information such as Figure 1e shown.
[0145] B2. In response to a confirmation operation on the download prompt information, download the communication application on the terminal device.
[0146] For more information, please see Figure 1e , the confirmation operation of the download prompt information can be performed by the user clicking Figure 1e The virtual button shown is: "Application B is not installed, go to download" is implemented. When the user triggers the confirmation operation for the download prompt information, the communication application can be downloaded on the terminal device.
[0147] In the above implementation, for a terminal device running a mobile operating system, if the communication application does not respond to the target protocol, it means that the terminal device currently does not have the communication application installed. Therefore, a download prompt message can be displayed to guide the user to download the communication application. After the user completes the download, if the user executes step 110 again, the communication application can usually respond to the target protocol. The above implementation reduces the occurrence of the communication application not responding to the target protocol by guiding the user to download the communication application on the mobile monopoly, and further expands the application scenarios of account binding.
[0148] 122. If the communication application responds to the target protocol, jump to the communication application and display an account binding prompt page of the communication application.
[0149] If the communication application responds to the target protocol, the display interface of the electronic device will jump to the UI interface of the communication application, and the account binding prompt page will be displayed in the UI interface. For details, please refer to Figure 1d .
[0150] In the above implementation, the account binding prompt page can be entered through a limited number of trigger operations by the user. Compared with the prior art, the complexity of the account binding process is greatly reduced and the efficiency of account binding is improved.
[0151] Optionally, in a specific implementation, the information browsing application attempts to wake up the communication application by running the target protocol, which may specifically include the following process: using the node layer of the electronic device to call the background interface of the qywebmngsvr module to verify the ticket parameters.
[0152] If the information browsing application wakes up the communication application by running the target protocol, the node layer of the electronic device can call the PortalCGI::QYCheckBindVid() program module in the qywebmngsvr module, which specifically performs the following process:
[0153] The ticket parameter is parsed based on the information code or preset communication information, and then the ticket parameter is judged whether it has expired based on the timestamp carried by the ticket parameter. If the time span between the timestamp and the current time does not exceed 7 days, it can be judged that the ticket parameter has not expired.
[0154] If the ticket parameter has not expired, the legitimacy of the second account running in the communication application is verified. Specifically, the following contents can be verified: whether the type of the first account is the preset mailbox type, whether the identity identifier of the second account does not have a closed mailbox label, whether the second account has not disabled the mailbox, whether the second account has not been bound to the first account, and whether the company to which the second account belongs does not have an exclusive domain name. If the above judgment results are all "yes", that is, the type of the first account is the preset mailbox type, the identity identifier of the second account does not have a closed mailbox label, the second account has not disabled the mailbox, the second account has not been bound to the first account, and the company to which the second account belongs does not have an exclusive domain name, the legitimacy verification of the second account is determined to be passed. If any of the above judgment results is "no", a message can be returned to the front end: page abnormality.
[0155] After executing the above process of the PortalCGI::QYCheckBindVid() program module, you can jump to the PortalCGI::QYBindExternalMail() program module in the qywebmngsvr module. The execution process of the PortalCGI::QYBindExternalMail() program module will be described below.
[0156] 130. In response to a confirmation operation on the account binding prompt information, bind the first account with the second account.
[0157] Optionally, in a specific implementation, the above step 130 may specifically include the following steps 131 to 133:
[0158] 131. In response to a confirmation operation on the account binding prompt information, determine whether the first account is a target type account. If so, execute step 132.
[0159] The target type account is an account that meets the set requirement type. For example, the target type can be one that meets the first type but not the second type. The first type can specifically be a work mailbox for a set enterprise, and the second type can specifically be a trial version mailbox for a set enterprise. It should be understood that the type of the specific account of the target type account should not be understood as a limitation on this application.
[0160] 132. Determine whether the account adding setting information of the communication application meets the preset requirements.
[0161] Optionally, the account adding setting information meets the preset requirements, which may specifically be: the account adding setting information meets a series of pre-set restrictions. The above series of restrictions may include: the application where the second account is located has not closed the tag of the type to which the first account belongs, the application where the second account is located has not disabled the type to which the first account belongs, and the application where the second account is located has not been bound to the first account, etc. It should be understood that the preset requirements may also include more restrictions, and the content of the specific restrictions of the preset requirements should not be understood as a limitation on this application.
[0162] 133. Bind the first account and the second account, and return binding success indication data.
[0163] Under the conditions that both the above steps 131 and 132 are satisfied, the binding process of the first account and the second account can be performed, and after the two are successfully bound, binding success indication data is returned.
[0164] In the above implementation, it is possible to judge in turn whether the first account meets the target type account and whether the account addition setting information of the communication application meets the preset requirements, and when the first account and the communication application both meet their respective conditions, the binding process of the first account and the second account is performed, thereby increasing the stability of the binding process.
[0165] Optionally, in a specific implementation, the first account information includes the first account and the time when the first account information is generated. Accordingly, step 133 may specifically include the following steps 1331 to 1335:
[0166] 1331. Parse the first account information to obtain a generation time of the first account information.
[0167] 1332. Compare the time when the first account information is generated with the current time.
[0168] Optionally, the electronic device may parse the first account information to obtain the generation time of the first account information, and compare the obtained generation time with the current time to obtain the time span between the two.
[0169] 1333. If the time span between the generation time of the first account information and the current time does not exceed the preset time length, determine whether the account adding setting information of the communication application meets the preset requirements. If so, execute step 1334.
[0170] The preset time length is a preset time length value, which may be 7 days, or other time length values, such as 5 days. It should be understood that the specific time length value of the preset time length should not be understood as a limitation to the present application.
[0171] When the time span between the generation time of the first account information and the current time does not exceed the preset time length, it can be confirmed again whether the account adding setting information of the communication application meets the preset requirements. After the reconfirmation, step 1334 can be executed.
[0172] 1334. Generate a locking program for the first account and the second account, where the duration of the locking program is a first time length.
[0173] The locking program is used to lock the terminal device that performs the binding process.
[0174] After the locking program is generated, it is possible to prevent other terminal devices from executing the binding process for the first account and the second account during the duration of the locking program.
[0175] 1335. During the duration of the locking procedure, bind the first account to at least one binding identifier of the communication application program where the second account is located.
[0176] The binding identifier is an identifier set in the communication application and reflects the identity identifier of the first account. A communication application may include multiple binding identifiers. That is, in one embodiment, the communication application running the second account can be bound to multiple first accounts. Multiple first accounts can be distinguished from each other by the binding identifier.
[0177] In the above implementation, the time span and the account adding setting information can be verified in sequence. After the above verification processes are verified, a locking program can be generated to ensure that the terminal device that executes the binding process of the first account and the second account will not be repeated, thereby avoiding errors or failures caused by duplication of terminal devices.
[0178] The above steps 1331 to 1335 can be executed by the PortalCGI::QYBindExternalMail() program module, which specifically performs the following process:
[0179] Based on the timestamp carried by the ticket parameter, determine whether the ticket parameter has expired. If the time span between the timestamp and the current time does not exceed 7 days, it can be determined that the ticket parameter has not expired.
[0180] Verify the legitimacy of the second account again, specifically verifying the following: whether the type of the first account is the preset email type, whether the identity identifier of the second account does not have a closed email tag, whether the second account does not have a disabled email, whether the second account does not have a bound first account, and whether the company to which the second account belongs does not have an exclusive domain name. If the above judgment results are all "yes", that is, the type of the first account is the preset email type, the identity identifier of the second account does not have a closed email tag, the second account does not have a disabled email, the second account does not have a bound first account, and the company to which the second account belongs does not have an exclusive domain name, the legitimacy verification of the second account is determined to be passed. If any of the above judgment results is "no", a message can be returned to the front end: page abnormality.
[0181] After both of the above verifications are passed, a key distributed lock can be generated based on the identity identifier vid of the second account and the first account, and the duration is 10 seconds. During the operation of the locking program, only one electronic device is allowed to execute the binding process between the first account and the second account. Specifically, the first account can be bound to at least one binding identifier DefaultUin of the communication application where the second account is located.
[0182] The three program modules of the qywebmngsvr module, PortalCGI::QYGetCorpListByWxOpenID(), PortalCGI::QYCheckBindVid() and PortalCGI::QYBindExternalMail(), are all defined and developed by developers.
[0183] Optionally, in a specific implementation, the communication application includes a communication sub-plug-in; accordingly, after step 130, the embodiment of the present application may further include the following step 140:
[0184] 140. Display communication information related to the first account in the communication sub-plug-in.
[0185] Users can view the communication information related to the first account by triggering the communication sub-plugin when running the communication application of the second account. For details, see Figure 1i , so that the communication information of multiple accounts can be aggregated in one application, which improves the convenience of information viewing. The above processing can simplify the user's operation process, so that different types of accounts can be aggregated in one place, improving the user's work efficiency.
[0186] In the account binding method provided in the embodiment of the present application, an account adding page including an account adding control can be displayed; in response to a user's triggering operation on the account adding control, an account binding prompt page of the communication application is displayed, and the account binding prompt page includes account binding prompt information. The account binding prompt page is displayed by the communication application in response to the target protocol, and the target protocol is generated by responding to the triggering operation on the account adding control. In response to the user's confirmation operation on the account binding prompt information, the first account is bound to the second account. In the embodiment of the present application, when the account adding control of the account adding page is triggered, and the communication application responds to the target protocol and displays the account binding prompt page, the binding process of the first account and the second account can be realized by responding to the user's confirmation operation on the account binding prompt information once more. Compared with the prior art, it saves the tediousness of type setting or the trouble of entering a password.
[0187] The embodiments of the present application can improve binding efficiency.
[0188] In this embodiment, the method of the embodiment of the present application is described in detail by taking the first account being an email account and the second account being an instant messaging account as an example.
[0189] like Figure 2 As shown, the specific process of an account binding method is as follows:
[0190] 201. Receive a first account and account verification information in the communication sub-plug-in, and send the first account and account verification information to a server for verification.
[0191] 202. If the server returns a verification failure prompt message, an information sending inquiry message is displayed on the display interface, wherein the information sending inquiry message is used to inquire whether to send the preset communication information to the first account.
[0192] 203. In response to the determination operation for the information sending inquiry information, return a determination sending message to the server, so that the server sends the preset communication information to the first account based on the determination sending message.
[0193] 204. Receive preset communication information in the application logged in with the first account, wherein the preset communication information includes the account adding control.
[0194] 205. Display an account adding page, wherein the account adding page includes an account adding control, wherein the account adding control carries the first account information, and the account adding control is used to implement binding between the first account and the second account.
[0195] 206. In response to the triggering operation of adding a control to the account, jump to the information browsing application.
[0196] 207. Obtain a preset protocol format, and combine the preset protocol format with the first account information into a target protocol, wherein the predicted protocol format is generated by the communication application.
[0197] 208. Run the target protocol through the information browsing application.
[0198] 209. If the communication application responds to the target protocol, jump to the communication application and display an account binding prompt page of the communication application.
[0199] 210. In response to a confirmation operation on the account binding prompt information, determine whether the first account is a target type account.
[0200] 211. If the first account is a target type account, determine whether the account adding setting information of the communication application meets the preset requirements.
[0201] 212. Parse the first account information to obtain a generation time of the first account information.
[0202] 213. Compare the generation time of the first account information with the current time.
[0203] 214. If the time span between the generation time of the first account information and the current time does not exceed the preset time length, determine whether the account adding setting information of the communication application meets the preset requirements.
[0204] 215. If the conditions are met, a locking program is generated for the first account and the second account, and the duration of the locking program is a first time length.
[0205] 216. During the duration of the locking procedure, bind the first account to at least one binding identifier of the communication application program where the second account is located.
[0206] 217. Display communication information related to the first account in the communication sub-plug-in.
[0207] The specific execution process of step 201 to step 217 has been described in detail above and will not be repeated here.
[0208] In the account binding method provided in the embodiment of the present application, an account adding page including an account adding control can be displayed; in response to a user's triggering operation on the account adding control, an account binding prompt page of the communication application is displayed, and the account binding prompt page includes account binding prompt information. The account binding prompt page is displayed by the communication application in response to the target protocol, and the target protocol is generated by responding to the triggering operation on the account adding control. In response to the user's confirmation operation on the account binding prompt information, the first account is bound to the second account. In the embodiment of the present application, when the account adding control of the account adding page is triggered, and the communication application responds to the target protocol and displays the account binding prompt page, the binding process of the first account and the second account can be realized by responding to the user's confirmation operation on the account binding prompt information once more. Compared with the prior art, it saves the tediousness of type setting or the trouble of entering a password.
[0209] The embodiments of the present application can improve binding efficiency.
[0210] In order to better implement the above method, the embodiment of the present application also provides an account binding device, which can be integrated into an electronic device, and the electronic device can be a terminal, a server, and other devices. Among them, the terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop, or a personal computer (PC) and other devices; the server can be a single server or a server cluster composed of multiple servers. For example, in this embodiment, the device of the embodiment of the present application will be described in detail by taking the account binding device specifically integrated in the server as an example.
[0211] For example, Figure 3 As shown, the account binding device includes:
[0212] The page display unit 301 is used to display an account adding page, wherein the account adding page includes an account adding control, wherein the account adding control is used to implement binding of a first account and a second account;
[0213] A trigger response unit 302, configured to display an account binding prompt page of the communication application in response to a trigger operation for adding a control to the account, wherein the account binding prompt page includes account binding prompt information;
[0214] The confirmation response unit 303 is used to bind the first account with the second account in response to a confirmation operation on the account binding prompt information.
[0215] In one implementation, the trigger response unit 302 includes:
[0216] A protocol generation subunit, configured to generate a target protocol in response to a triggering operation of adding a control to the account;
[0217] The program jump subunit is used to jump to the communication application when the communication application responds to the target protocol, and display the account binding prompt page of the communication application.
[0218] In one embodiment, the protocol generation subunit includes:
[0219] A trigger response sub-subunit, for jumping to an information browsing application in response to a trigger operation for adding a control to an account;
[0220] The information combination sub-unit is used to obtain a preset protocol format and combine the preset protocol format with the first account information into a target protocol, wherein the predicted protocol format is generated by the communication application.
[0221] In one embodiment, the communication application includes a communication sub-plug-in; the device also includes:
[0222] An information display unit is used to display the communication information related to the first account in the communication sub-plug-in.
[0223] In one embodiment, the terminal device is a terminal device running a desktop operating system; the apparatus further comprises:
[0224] an information code acquisition unit, configured to send an information code acquisition request to a server when the communication application does not respond to the target protocol;
[0225] An information code receiving unit, configured to receive an information code returned by the server, wherein the information code carries the first account information and encryption information, wherein the encryption information includes the first account information and information of the time when the information code is generated by the first account information;
[0226] An information code display unit is used to display the information code on a display interface so that a mobile terminal can scan the information code and send the first account information and the encrypted information to a server, and after the server verifies the first account information and the encrypted information, the communication application is run on the mobile terminal, and based on the first account information, the binding of the first account and the second account is achieved.
[0227] In one implementation, the terminal device is a terminal device running a mobile operating system; the apparatus further includes:
[0228] A download prompt display unit, used to display download prompt information on a display interface when the communication application does not respond to the target protocol;
[0229] A program downloading unit is used to download the communication application program on the terminal device in response to a confirmation operation on the download prompt information.
[0230] In one embodiment, the device further comprises:
[0231] An information receiving unit is used to receive preset communication information in an application logged in with the first account, wherein the preset communication information includes the account adding control.
[0232] In one embodiment, the communication application includes a communication sub-plug-in; the device also includes:
[0233] An account information receiving unit, configured to receive a first account and account verification information in the communication sub-plug-in, and send the first account and account verification information to a server for verification;
[0234] An inquiry information sending unit, configured to display an information sending inquiry information on a display interface when the server returns a verification failure prompt message, wherein the information sending inquiry information is used to inquire whether to send the preset communication information to the first account;
[0235] A determination response unit is used to return a determination sending message to the server in response to a determination operation on the information sending inquiry information, so that the server sends the preset communication information to the first account based on the determination sending message.
[0236] In one implementation, the confirmation response unit 303 includes:
[0237] a target type determination subunit, configured to determine whether the first account is a target type account in response to a confirmation operation on the account binding prompt information;
[0238] a preset requirement determination subunit, configured to determine, when the first account is a target type account, that the account adding setting information of the communication application satisfies the preset requirement;
[0239] The account binding subunit is used to bind the first account and the second account and return binding success indication data.
[0240] In one embodiment, the first account information includes the first account and the time when the first account information is generated;
[0241] Account binding subunit, including:
[0242] An account information parsing sub-unit, configured to parse the first account information to obtain a generation time of the first account information;
[0243] A time comparison sub-unit, used to compare the generation time of the first account information with the current time;
[0244] A requirement determination sub-subunit, used for determining whether the account adding setting information of the communication application meets the preset requirement when the time span between the generation time of the first account information and the current time does not exceed the preset time length;
[0245] A lock generation sub-subunit, configured to generate a lock program for the first account and the second account when the account adding setting information of the communication application meets a preset requirement, wherein the duration of the lock program is a first time length;
[0246] The account binding sub-subunit is used to bind the first account to at least one binding identifier of the communication application program where the second account is located during the duration of the locking program.
[0247] In specific implementation, the above units can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units can refer to the previous method embodiments, which will not be repeated here.
[0248] In the account binding method provided in the embodiment of the present application, an account adding page including an account adding control can be displayed; in response to a user's triggering operation on the account adding control, an account binding prompt page of the communication application is displayed, and the account binding prompt page includes account binding prompt information. The account binding prompt page is displayed by the communication application in response to the target protocol, and the target protocol is generated by responding to the triggering operation on the account adding control. In response to the user's confirmation operation on the account binding prompt information, the first account is bound to the second account. In the embodiment of the present application, when the account adding control of the account adding page is triggered, and the communication application responds to the target protocol and displays the account binding prompt page, the binding process of the first account and the second account can be realized by responding to the user's confirmation operation on the account binding prompt information once more. Compared with the prior art, it saves the tediousness of type setting or the trouble of entering a password.
[0249] The embodiments of the present application can improve binding efficiency.
[0250] The embodiment of the present application also provides an electronic device, which can be a terminal, a server, etc. The terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop, a personal computer, etc. The server can be a single server or a server cluster composed of multiple servers, etc.
[0251] In some embodiments, the account binding device may also be integrated into multiple electronic devices. For example, the account binding device may be integrated into multiple servers, and the account binding method of the present application may be implemented by multiple servers.
[0252] In this embodiment, the electronic device of this embodiment is an electronic device as an example for detailed description, for example, Figure 4 As shown, it shows a schematic diagram of the structure of the electronic device involved in the embodiment of the present application, specifically:
[0253] The electronic device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, an input module 404, and a communication module 405. Those skilled in the art will appreciate that Figure 4 The electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0254] The processor 401 is the control center of the electronic device, and uses various interfaces and lines to connect various parts of the entire electronic device. It executes various functions of the electronic device and processes data by running or executing software programs and / or modules stored in the memory 402, and calling data stored in the memory 402. In some embodiments, the processor 401 may include one or more processing cores; in some embodiments, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 401.
[0255] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and account binding by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.
[0256] The electronic device also includes a power supply 403 for supplying power to various components. In some embodiments, the power supply 403 can be logically connected to the processor 401 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 403 can also include any components such as one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, and power status indicators.
[0257] The electronic device may further include an input module 404, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
[0258] The electronic device may further include a communication module 405. In some embodiments, the communication module 405 may include a wireless module. The electronic device may perform short-range wireless transmission through the wireless module of the communication module 405, thereby providing the user with wireless broadband Internet access. For example, the communication module 405 may be used to help the user send and receive emails, browse web pages, and access streaming media.
[0259] Although not shown, the electronic device may further include a display unit, etc., which will not be described in detail herein. Specifically in this embodiment, the processor 401 in the electronic device will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby realizing various functions, as follows:
[0260] An account adding page is displayed, wherein the account adding page includes an account adding control, wherein the account adding control is used to implement binding of a first account and a second account; in response to a triggering operation on the account adding control, an account binding prompt page of a communication application is displayed, wherein the account binding prompt page includes account binding prompt information; in response to a confirmation operation on the account binding prompt information, the first account and the second account are bound.
[0261] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0262] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0263] To this end, an embodiment of the present application provides a computer-readable storage medium, which stores multiple instructions, which can be loaded by a processor to execute the steps in any account binding method provided in the embodiment of the present application. For example, the instruction can execute the following steps:
[0264] An account adding page is displayed, wherein the account adding page includes an account adding control, wherein the account adding control is used to implement binding of a first account and a second account; in response to a triggering operation on the account adding control, an account binding prompt page of a communication application is displayed, wherein the account binding prompt page includes account binding prompt information; in response to a confirmation operation on the account binding prompt information, the first account and the second account are bound.
[0265] The storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0266] According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in the various optional implementations provided in the above embodiments.
[0267] Since the instructions stored in the storage medium can execute the steps in any one of the account binding methods provided in the embodiments of the present application, the beneficial effects that can be achieved by any one of the account binding methods provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.
[0268] The above is a detailed introduction to an account binding method, device, electronic device and computer-readable storage medium provided in the embodiments of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the ideas of the present application, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. An account binding method, characterized in that: Applied to a terminal device, the method comprises: Displaying an account adding page, wherein the account adding page includes an account adding control, wherein the account adding control is used to implement binding of the first account and the second account; In response to a triggering operation for adding a control to the account, displaying an account binding prompt page of the communication application, wherein the account binding prompt page includes account binding prompt information; In response to a confirmation operation on the account binding prompt information, the first account is bound to the second account.
2. The method according to claim 1, characterized in that The step of displaying an account binding prompt page of the communication application in response to the triggering operation of adding a control to the account includes: In response to a triggering operation of adding a control to the account, generating a target protocol; If the communication application responds to the target protocol, the process jumps to the communication application and displays an account binding prompt page for the communication application.
3. The method according to claim 2, characterized in that The account adding control carries the first account information; The generating a target protocol in response to a triggering operation of adding a control to the account includes: In response to a trigger operation for adding a control to an account, jumping to an information browsing application; Acquire a preset protocol format, and combine the preset protocol format with the first account information into a target protocol, wherein the predicted protocol format is generated by the communication application; The target protocol is run through the information browsing application.
4. The method according to claim 1, characterized in that The account binding prompt page is displayed by the communication application in response to a target protocol, wherein the target protocol is generated in response to a triggering operation of adding a control to the account, and the target protocol carries information of the communication application where the second account is located.
5. The method according to claim 1, characterized in that The communication application includes a communication sub-plugin; After binding the first account with the second account in response to a confirmation operation on the account binding prompt information, the method further includes: The communication sub-plugin displays communication information related to the first account.
6. The method according to claim 2, characterized in that The terminal device is a terminal device running a desktop operating system; After generating the target protocol in response to the triggering operation of adding a control to the account, the method further includes: If the communication application does not respond to the target protocol, sending an information code acquisition request to the server; receiving an information code returned by the server, wherein the information code carries the first account information and encryption information, wherein the encryption information includes the first account information and information of the time when the information code is generated by the first account information; The information code is displayed on a display interface so that a mobile terminal can scan the information code and send the first account information and the encrypted information to a server. After the server verifies the first account information and the encrypted information, the communication application is run on the mobile terminal, and based on the first account information, the first account and the second account are bound.
7. The method according to claim 2, characterized in that The terminal device is a terminal device running a mobile operating system; After generating the target protocol in response to the triggering operation of adding a control to the account, the method further includes: If the communication application does not respond to the target protocol, displaying a download prompt message on the display interface; In response to a confirmation operation on the download prompt information, the communication application is downloaded to the terminal device.
8. The method according to claim 3, characterized in that Before jumping to the information browsing application in response to the triggering operation of adding a control to the account, the method further includes: The application program logged in with the first account receives preset communication information, wherein the preset communication information includes the account adding control.
9. The method according to claim 8, characterized in that The communication application includes a communication sub-plugin; Before the application logged in with the first account receives the preset communication information, the method further includes: receiving, at the communication sub-plugin, a first account and account verification information, and sending the first account and account verification information to a server for verification; If the server returns a verification failure prompt message, an information sending inquiry message is displayed on the display interface, wherein the information sending inquiry message is used to inquire whether to send the preset communication information to the first account; In response to a determination operation on the information sending inquiry information, a determination sending message is returned to the server, so that the server sends the preset communication information to the first account based on the determination sending message.
10. The method according to claim 1, characterized in that In response to the confirmation operation on the account binding prompt information, binding the first account with the second account includes: In response to a confirmation operation on the account binding prompt information, determining whether the first account is a target type account; If so, determining that the account adding setting information of the communication application meets the preset requirements; Bind the first account to the second account, and return binding success indication data.
11. The method according to claim 10, characterized in that The first account information includes the first account and the time when the first account information is generated; The binding the first account and the second account includes: Parsing the first account information to obtain the generation time of the first account information; Comparing the generation time of the first account information with the current time; If the time span between the generation time of the first account information and the current time does not exceed the preset time length, determining whether the account adding setting information of the communication application meets the preset requirements; If yes, a locking program is generated for the first account and the second account, and the duration of the locking program is a first time length; During the duration of the locking procedure, the first account is bound to at least one binding identifier of the communication application program where the second account is located.
12. An account binding device, characterized in that: Applied to a terminal device, the device comprises: A page display unit, used to display an account adding page, wherein the account adding page includes an account adding control, wherein the account adding control is used to implement binding of the first account and the second account; a trigger response unit, configured to display an account binding prompt page of the communication application in response to a trigger operation for adding a control to the account, wherein the account binding prompt page includes account binding prompt information; A confirmation response unit is used to bind the first account with the second account in response to a confirmation operation on the account binding prompt information.
13. An electronic device, characterized in that: It comprises a processor and a memory, wherein the memory stores a plurality of instructions; the processor loads instructions from the memory to execute the steps in the account binding method according to any one of claims 1 to 11.
14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the account binding method according to any one of claims 1 to 11.
15. A computer program product, characterized in that The method comprises a computer program / instruction, which, when executed by a processor, implements the steps in the account binding method according to any one of claims 1 to 11.