Account Management Method, Device, Equipment and Medium Based on Multi-Application System

Abstract

The present application discloses an account management method, device, equipment and medium based on a multi-application system. The multi-application system includes a first application and a second application. The method includes: obtaining the login status of the first application and the login serial number corresponding to the first application, and when the first application is in the login status, obtaining the first account corresponding to the first application and the first binding relationship corresponding to the first account; obtaining the login status of the second application, and when the second application is in the login status, obtaining the second account corresponding to the second application and the second binding relationship corresponding to the second account; determining an account control policy for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship and the login serial number, effectively reducing the risk of terminal user privacy leakage.

Description

Technical Field

[0001] The present disclosure generally relates to the field of computer technology, specifically to the field of account management technology, and particularly to an account management method, device, equipment, and medium based on a multi-application system. Background Art

[0002] With the gradual improvement of the intelligence of in-vehicle terminals, in-vehicle terminals have been upgraded from simple menu functions to being able to install a variety of intelligent application programs. In related technologies, a terminal account is usually used to bind or log in to a third-party application installed on the in-vehicle terminal, and the terminal account is usually registered with privacy data such as the user's mobile phone number, which makes it easy to cause the risk of user privacy leakage when using the terminal account to log in to the third-party application, and improvement is needed. Summary of the Invention

[0003] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide an account management method, device, equipment, and medium based on a multi-application system to reduce the risk of terminal user privacy leakage.

[0004] In a first aspect, an embodiment of the present application provides an account management method based on a multi-application system, where the multi-application system includes a first application and a second application, the first application is an application program associated with the multi-application system, and the second application is an application program provided by a third-party server. The method includes:

[0005] Obtain the login status of the first application and the login serial number corresponding to the first application, and when the first application is in the logged-in state, obtain the first account corresponding to the first application and the first binding relationship corresponding to the first account;

[0006] Obtain the login status of the second application, and when the second application is in the logged-in state, obtain the second account corresponding to the second application and the second binding relationship corresponding to the second account;

[0007] Determine an account control strategy for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number;

[0008] wherein the login serial number is used to represent the change situation of the login status of the first application;

[0009] The first binding relationship includes two states: empty and non-empty. When the first binding relationship is empty, the first account is not bound to the account of the second application; when the first binding relationship is non-empty, the first account is in a binding relationship with the second binding account of the second application;

[0010] The second binding relationship includes two states: empty and non-empty. When the second binding relationship is empty, the second account is not bound to any account of the first application; when the second binding relationship is non-empty, the second account is in a binding relationship with at least one first binding account of the first application.

[0011] In a second aspect, an embodiment of the present application provides an account management device based on a multi-application system. The multi-application system includes a first application and a second application. The first application is an application program associated with the multi-application system, and the second application is an application program provided by a third-party server. The device includes:

[0012] A first acquisition module, configured to acquire the login state of the first application and the login serial number corresponding to the first application, and when the first application is in a logged-in state, acquire the first account corresponding to the first application and the first binding relationship corresponding to the first account;

[0013] A second acquisition module, configured to acquire the login state of the second application, and when the second application is in a logged-in state, acquire the second account corresponding to the second application and the second binding relationship corresponding to the second account;

[0014] A control module, configured to determine an account control strategy for the first application and the second application according to the login state of the first application, the login state of the second application, the first binding relationship, the second binding relationship, and the login serial number;

[0015] Wherein, the login serial number is used to represent the change situation of the login state of the first application;

[0016] The first binding relationship includes two states: empty and non-empty. When the first binding relationship is empty, the first account is not bound to the account of the second application; when the first binding relationship is non-empty, the first account is in a binding relationship with the second binding account of the second application;

[0017] The second binding relationship includes two states: empty and non-empty. When the second binding relationship is empty, the second account is not bound to any account of the first application; when the second binding relationship is non-empty, the second account is in a binding relationship with at least one first binding account of the first application.

[0018] In a third aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the method described in the embodiment of the present application is implemented.

[0019] Fourthly, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the method described in the embodiment of the present application is implemented.

[0020] The account management method based on a multi-application system proposed in the embodiment of the present application effectively realizes the account control of the first application and the second application by monitoring the login states of the first application and the second application, and according to the binding relationship corresponding to the logged-in account when the first application and / or the second application is in the logged-in state. It effectively avoids the interaction of user account information between the first application and the second application, and reduces the risk of privacy leakage from the first application to the second application.

[0021] Additional aspects and advantages of the present invention will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] By reading the detailed description of the non-limiting embodiments with reference to the following drawings, other features, objects, and advantages of the present application will become more apparent:

[0023] Figure 1 It is a flowchart of an account management method based on a multi-application system proposed in the embodiment of the present application;

[0024] Figure 2 It is a flowchart of another account management method based on a multi-application system proposed in the embodiment of the present application;

[0025] Figure 3 It is a flowchart of yet another account management method based on a multi-application system proposed in the embodiment of the present application;

[0026] Figure 4 It is a flowchart of still another account management method based on a multi-application system proposed in the embodiment of the present application;

[0027] Figure 5 It is a flowchart of still another account management method based on a multi-application system proposed in the embodiment of the present application;

[0028] Figure 6 It is a block diagram of an account management device based on a multi-application system proposed in the embodiment of the present application;

[0029] Figure 7 It shows a schematic structural diagram of a computer system of an electronic device or a server suitable for implementing the embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0030] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the invention are shown in the accompanying drawings.

[0031] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0032] Figure 1 This is a flowchart of an account management method based on a multi-application system proposed in an embodiment of the present application.

[0033] Among them, it should be noted that the executor of the account management method based on a multi-application system in this embodiment is an account management device based on a multi-application system. The account management device based on a multi-application system can be implemented by software and / or hardware. The account management device based on a multi-application system in this embodiment can be configured in an electronic device, or in a server for controlling the electronic device. The server communicates with the electronic device and then controls it.

[0034] Among them, the electronic equipment in this embodiment may include but is not limited to personal computers, platform computers, smart phones, vehicle-mounted terminals and other devices. This embodiment does not specifically limit the electronic equipment.

[0035] The multi-application system includes a first application and a second application, the first application is an application associated with the multi-application system, and the second application is an application provided by a third-party server.

[0036] That is to say, the first application is an application that comes with the multi-application system, or an application provided by the multi-application system server. For example, when the multi-application system is a vehicle-mounted terminal system, the first application is an application built into the vehicle-mounted terminal, which is used to provide functions preset by the vehicle manufacturer. The second application is an application provided by a third-party server, which can be installed in the multi-application system according to the installation package downloaded by the user on the Internet, or the installation package can be preset in the system installation package according to the agreement between the third-party manufacturer and the vehicle manufacturer, and installed together when the system is installed on the vehicle terminal.

[0037] Step 101, obtaining a login status of a first application and a login serial number corresponding to the first application, and when the first application is in a logged-in state, obtaining a first account corresponding to the first application and a first binding relationship corresponding to the first account.

[0038] The login sequence number is used to indicate changes in the login status of the first application.

[0039] It should be noted that the login serial number is a serial number that changes continuously according to the login situation of the first account in the first application, and is used to identify the change of the login state of the first application and whether the two consecutive login operations are of the same account.

[0040] In one or more embodiments, monitor the change of the login state of the first application, and record the prior first account information and the subsequent first account information in two consecutive logged-in states of the first application; when the login state of the first application does not change, control the login serial number to remain unchanged; when the login state of the first application changes from the logged-in state to the non-logged-in state, control the value of the login serial number to perform a first operation, and assign the result of the operation to the login serial number; when the login state of the first application changes from the non-logged-in state to the logged-in state, identify whether the prior first account is the same as the subsequent first account; if the prior first account is the same as the subsequent first account, control the login serial number to perform a second operation, and assign the result of the operation to the login serial number; wherein, the second operation is the inverse function of the first operation; if the prior first account is not the same as the subsequent first account, control the login serial number to perform a first operation, and assign the result of the operation to the login serial number.

[0041] Wherein, the second operation is the inverse function of the first operation, that is, the numerical value a or the matrix A can obtain the numerical value b or the matrix B through the first operation, and the numerical value b or the matrix B can obtain the numerical value a or the matrix A through the second operation.

[0042] Optionally, the operation on the login serial number is usually an addition or subtraction operation, so that the serial number value gradually increases or decreases to form a natural number sequence. Preferably, the first operation is an addition operation to promote the serial number to increase gradually, and the second operation is a subtraction operation to ensure that the login serial number remains unchanged when the prior first account is the same as the subsequent first account, that is, the login serial number does not change during consecutive logins of the same account, so as to reduce the frequent response of the second application or the second account.

[0043] As a specific embodiment, as Figure 2 shown, the following steps are included:

[0044] Step 201, monitor the change of the login state of the first application, and record the prior first account information and the subsequent first account information before and after the login change of the first application.

[0045] It should be noted that the prior first account information and the subsequent first account information are respectively the account information of two consecutive logins of the first application, and the prior first account information and the subsequent first account information may be the same or different.

[0046] Step 202, identify whether the state of the first application has changed.

[0047] If so, execute step 203; if not, control the login serial number to remain unchanged.

[0048] That is to say, the change of the login serial number occurs based on the change of the login status of the first application. That is, when the login status of the first application does not change, including the continuous non-login status or the continuous logged-in status, it is determined that the login serial number has not changed. When the login status of the first application changes, for example, when the first application changes from the non-login status to the logged-in status, it is determined that the value of the login serial number changes, or when the first application changes from the logged-in status to the non-login status, it is determined that the login serial number changes.

[0049] Step 203: Determine whether the login status of the first application is logged out.

[0050] If so, control the value of the login serial number to be incremented by 1; if not, execute step 204.

[0051] Here, "logged out" means changing from the logged-in status to the non-login status.

[0052] It should be noted that it can be understood that the login serial number can be a counting parameter for the login and logout actions of the first application. Therefore, when the first application is logged out, the counter is incremented by 1 to record the situation of the login change of the first application.

[0053] Step 204: Determine whether the previous first account is the same as the subsequent first account.

[0054] If the previous first account is the same as the subsequent first account, control the value of the login serial number to be decremented by 1; if the previous first account is not the same as the subsequent first account, control the value of the login serial number to be incremented by 1.

[0055] It should be noted that when the previous first account is the same as the subsequent first account, it means that the two login actions belong to the same account. Therefore, in order to reduce the control frequency of the second application, it can be controlled that when the subsequent first account logs in, the value of the login serial number is incremented by 1, so that the login serial number after the subsequent first account logs in is the same as the login serial number before the previous first account logs out. Furthermore, it can be determined that the first application has not changed its state based on the change of the login serial number, thus avoiding the second application from logging out and / or logging in repeatedly, and reducing the data processing volume of the multi-application system.

[0056] In one or more embodiments, the first binding relationship includes two states: empty and non-empty. When the first binding relationship is empty, the first account is not bound to the account of the second application; when the first binding relationship is non-empty, the first account and the second binding account of the second application are in a binding relationship. Among them, each first account can bind one second account. Optionally, when there are multiple second applications, each first account can bind one second account for each second application.

[0057] Step 102: Obtain the login status of the second application. When the second application is in the logged-in state, obtain the second account corresponding to the second application and the second binding relationship corresponding to the second account.

[0058] The second binding relationship includes two states: empty and non-empty. When the second binding relationship is empty, the second account is not bound to any account of the first application; when the second binding relationship is non-empty, the second account is bound to at least one first binding account of the first application.

[0059] It should be noted that similar to the first application, the second application also has a logged-in state and a non-logged-in state. Each second account can be bound to a preset number of first binding accounts, that is, the second binding relationship of each second account can include less than the preset number of first binding accounts. Optionally, the preset number can be 5.

[0060] Step 103: Determine the account control policies for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number.

[0061] Therefore, the account management method based on a multi-application system proposed in the embodiments of the present application effectively realizes the account control of the first application and the second application by monitoring the login statuses of the first application and the second application and according to the binding relationships corresponding to the logged-in accounts when the first application and / or the second application is in the logged-in state, effectively avoiding the interaction of user account information between the first application and the second application and reducing the risk of privacy leakage from the first application to the second application.

[0062] In one or more embodiments, determining the account control policies for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number includes: when the first application is in the logged-in state, the first binding relationship is non-empty, and the second application is in the non-logged-in state, controlling the second application to log in to the second binding account; when the first application is in the logged-in state, the first binding relationship is non-empty, and when the second application is in the logged-in state and the second account is the same as the bound second account, controlling the second application to maintain the current state; when the first application is in the logged-in state, the first binding relationship is non-empty, and when the second application is in the logged-in state and the second account is different from the candidate second account, controlling the second application to log out of the second account and controlling the second application to log in to the bound second account.

[0063] In one or more embodiments, an account control policy for a first application and a second application is determined based on the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number, including: when the first application is in a logged-in state, the first binding relationship is empty, the second application is in a logged-in state, the login serial number has changed, and the second binding relationship is non-empty, controlling the second application to log out of the second account; when the first application is in a logged-in state, the first binding relationship is empty, the second application is in a logged-in state, the login serial number has changed, and the second binding relationship is empty, controlling to issue a reminder to establish a binding relationship between the first account and the second account.

[0064] In one or more embodiments, an account control policy for a first application and a second application is determined based on the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number, including: when the first application is in a non-logged-in state, the second application is in a logged-in state, the second binding relationship is non-empty, and the login serial number has changed, controlling the second application program to log out of the second account.

[0065] In one or more embodiments, an account control policy for a first application and a second application is determined based on the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number, including: when the first application is in a non-logged-in state, if the second application is in a non-logged-in state, or the second binding relationship is empty, or the login serial number has not changed, controlling the second application to maintain the login status of the current state; when the first application is in a logged-in state and the first binding relationship is empty, if the second application is in a non-logged-in state, or the login serial number has not changed, controlling the second application to maintain the login status of the current state.

[0066] In one or more embodiments, as Figure 3 shown, the account management method based on a multi-application system proposed by the embodiments of the present application includes the following steps:

[0067] Step 301, determine whether the first application is in a logged-in state.

[0068] If the first application is in a logged-in state, then execute step 302; if the first application is not in a logged-in state, then execute step 308.

[0069] Step 302, determine whether the second bound account is included in the first binding relationship corresponding to the first account.

[0070] If so, then execute step 303; if not, then execute step 305.

[0071] Step 303: Determine whether the second application is in a logged-in state.

[0072] If the second application is in a logged-in state, execute Step 304; if the second application is not in a logged-in state, control the second application to log in to the second bound account.

[0073] That is to say, when the first application is in a logged-in state, the second application is not in a logged-in state, and the first account logged in by the first application has a bound second bound account, the login state of the first application can be used to control the second application to log in to the second bound account bound to the first account, effectively realizing the account linkage between the first application and the second application, providing a seamless login for the second application, effectively improving the intelligence level of the multi-application system, enhancing the user experience, meeting the need for account login without manual login, and reducing the number of terminal operations of the user.

[0074] Step 304: Determine whether the second account is the same as the second bound account.

[0075] If they are the same, maintain the current state; if they are not the same, control the second application to log out of the currently logged-in second account and control the second application to log in to the second bound account.

[0076] That is to say, when both the first application and the second application are in a logged-in state, if the second account currently logged in by the second application is the same as the second bound account bound to the first account logged in by the first application, it means that the currently logged-in accounts of the first application and the second application are associated accounts, and control the first application and the second application to maintain the current logged-in state to meet the operation requirements of the user for the first application and the second application. If the second account currently logged in by the second application is not the same as the second bound account bound to the first account logged in by the first application, it means that the currently logged-in accounts of the first application and the second application are not associated accounts. At this time, control the second application to log out of the currently logged-in second account to prevent the account information of the first account from being leaked to the second application, and at the same time control the second application to log in to the second bound account to provide seamless switching of the second application account to meet the user's usage requirements for the second application.

[0077] Step 305: Determine whether the second application is in a logged-in state.

[0078] If the second application is in a logged-in state, execute Step 306; if the second application is not in a logged-in state, control the first application and the second application to maintain the current state.

[0079] That is to say, when the first application is in the logged-in state, the second application is in the non-logged-in state, and the first account logged in by the first application does not have a bound second binding account, at this time, if the second account that can be logged in cannot be determined based on the first account, then the logged-in state of the first application and the non-logged-in state of the second application are continued to be maintained.

[0080] Step 306: Determine whether the login serial number corresponding to the first application has changed.

[0081] Among them, it is necessary to compare the current login serial number of the first application with the login serial number when the first application was last in the logged-in state. To prevent an incorrect judgment result of the serial number change and thus avoid the problem of privacy information leakage caused by inconsistent accounts logged in before and after.

[0082] If it has changed, then execute Step 307; if not, then control the first application and the second application to maintain the current state.

[0083] Among them, when the login serial number corresponding to the first application has not changed, it means that the first application remains in the logged-in state continuously and does not change from the non-logged-in state to the logged-in state. At this time, although the second application is also in the logged-in state, there is no binding relationship between the two. That is, the first application and the second application have reached a balanced state under the control of other processes, and there is no need to change the account states of the two, and the first application and the second application can continue to be controlled to maintain the current state.

[0084] Step 307: Determine whether the second binding relationship corresponding to the second account logged in by the second application contains at least one first binding account.

[0085] If it does, then control the second application to log out of the currently logged-in second account or control to send a prompt message for establishing a binding relationship; if not, then control to send a prompt message for establishing a binding relationship.

[0086] That is to say, when both the first application and the second application are in the logged-in state, the second application has already bound the corresponding first binding account, while the first account has not bound the second binding account, and the login serial number

[0087] If the value changes, it indicates that the first application has logged in and the logged-in first account is a new subsequent first account, and this new subsequent first account is not bound to the second bound account. Therefore, the second account logged in by the current second application is an incorrect account, that is, it does not match the first account. At this time, a prompt message for establishing a binding relationship can be controlled to be sent, reminding the user to bind the unbound first account to the currently logged-in second account, so that the unbound first account has a bound second bound account. When the user chooses not to create, the login state of the current second application can be exited according to the user's choice, or when it is determined that the second account logged in by the current second application is an incorrect account, the second application can be directly controlled to exit the login state of the current second account.

[0088] When both the first application and the second application are in the logged-in state, and no binding relationship has been established between the first account and the second account, that is, the first account is not bound to the second bound account and the second account is not bound to the first bound account either, then a prompt message for establishing a binding relationship is controlled to be sent, reminding the user to bind the unbound first account to the currently logged-in second account.

[0089] It should be noted that in the embodiments of the present application, the prompt message for establishing a binding relationship can be sent by the first application, or by the second application, or by both applications simultaneously. Optionally, the application that logged in first can be controlled to send a reminder for establishing a binding relationship, or the application that logged in later can be controlled to send a reminder for establishing a binding relationship, or a fixed application can be controlled to send a reminder for establishing a binding relationship. Specifically, it can be implemented according to the settings in the multi-application system.

[0090] Step 308, determine whether the second application is in the logged-in state.

[0091] If the second application is in the logged-in state, execute step 309. If the second application is in the non-logged-in state, control the first application and the second application to maintain the current state.

[0092] That is to say, in the current state, no application is in the logged-in state. At this time, the multi-application system waits for the user's login behavior.

[0093] Step 309, determine whether the second binding relationship corresponding to the second account logged in by the second application contains at least one first binding account.

[0094] If so, execute step 310. If not, control the first application and the second application to maintain the current state.

[0095] That is to say, at this time, only the second application is in the logged-in state, and the second application does not have a bound first binding account. Therefore, the first application cannot be controlled to log in based on the already logged-in second account. Thus, control the first application and the second application to maintain the current state.

[0096] Step 310, determine whether the login serial number corresponding to the first application has changed.

[0097] If so, log out of the current second account; if not, control the first application and the second application to maintain the current state.

[0098] It should be noted that when the login serial number changes, it means that the first application changes from the logged-in state to the logged-out state. At this time, the second account of the second application in the logged-in state is logged out synchronously, realizing the seamless logout of the second application and preventing users from leaking privacy due to forgetting to log out the second application.

[0099] When the login serial number does not change, it means that the first application continues to maintain the logged-out state. At this time, the login state of the second application can be continued to meet the user's login needs.

[0100] For example, the first application is the BYD system, the first account is the user account registered by the user in the BYD system, the second application is the information interaction platform installed in the BYD system, such as WeChat, Weibo, navigation, etc., and the second account is the account registered by the user in the information interaction platform. Therefore, when the user establishes a binding relationship between the BYD account and an account such as WeChat, Weibo, or navigation, the BYD system can control the accounts of the WeChat, Weibo, or navigation application to log in or log out simultaneously according to the user's login or logout operation of the BYD account, thus realizing seamless login and logout operations, reducing the user's repeated login operations, and improving the user experience.

[0101] When the BYD system account and the accounts logged in to WeChat, Weibo, or navigation each have a binding account, the currently logged-in account of WeChat, Weibo, or navigation is controlled to log out according to the binding situation of the BYD account, thus preventing the leakage of private data in the BYD account to the WeChat, Weibo, or navigation application.

[0102] When the BYD system account and the accounts logged in to WeChat, Weibo, or navigation do not bind each other's accounts, it means that the user is performing the initial login. Then, a prompt message for establishing a binding relationship is sent according to the preset prompt method rule to remind the user to establish the corresponding binding relationship, so that the login or logout of WeChat, Weibo, or navigation can be controlled according to the login or logout of the BYD account when used later.

[0103] In one or more embodiments, the method further includes: receiving a request from a second application to establish a second binding relationship; when the first application is in a logged-in state, the first binding relationship corresponding to the first account is empty, and the number of first binding accounts in the second binding relationship corresponding to the second account is less than a first preset number, setting the second binding relationship to add the first account as a first binding account, and setting the second account as a second binding account in the first binding relationship; or when the first application is in a logged-in state, the first binding relationship is empty, and the number of first binding accounts in the second binding relationship is equal to the first preset number, obtaining the last login time corresponding to each first binding account; setting the second binding relationship to delete the first binding account with the earliest last login time, setting the second binding relationship to add the first account as a first binding account, and setting the second account as a second binding account in the first binding relationship.

[0104] Optionally, as Figure 4 shown, the method includes the following steps:

[0105] Step 401, receiving a request from a second application to establish a second binding relationship.

[0106] It should be noted that when the user only logs in to the second application, according to the selection instruction of the user on the second application, it can be analyzed and determined that the received selection instruction is a request to establish a second binding relationship. Also, when both the first application and the second application are logged in, after sending a prompt message for establishing a binding relationship based on the binding relationship between the first account and the second account, the received request to establish a second binding relationship can be determined according to the user's selection instruction.

[0107] Step 402, determining whether the first application is in a logged-in state.

[0108] If so, execute step 403; if not, control to send a login prompt message for entering the first account.

[0109] Step 403, obtaining the number of first binding accounts included in the second binding relationship corresponding to the second account.

[0110] Step 404, determining whether the number of first binding accounts is less than a first preset number.

[0111] If so, establish a second binding relationship based on the first account and the second account; if not, execute step 405.

[0112] Step 405, obtaining the last login time corresponding to each first binding account.

[0113] Step 406, using the first account to replace the first binding account with the earliest last login time.

[0114] It should be noted that when the first application is in the unlogged state, a prompt message for entering the first account is controlled to be sent. The prompt message can be the login interface of the first account or an independent account input interface.

[0115] That is to say, the second application can initiate a request to establish a binding relationship. When there is no logged-in first account, a reminder message is sent to prompt the user to enter the corresponding account to achieve account binding. When the first account is logged in the first application, it is further determined the number of first accounts currently bound to the second account. When the number of first accounts bound to the second account is less than the first preset number, the current binding policy is determined to be setting the second binding relationship to add the first account as a first binding account, and then the binding operation is directly executed. When the number of first accounts bound to the second account is greater than or equal to the first preset number, the current binding policy is determined to be setting the first account to replace the first binding account that has not been logged in for a long time, then the first account that has not been logged in for the longest time is unbound, and then the currently logged-in first account is bound to the second account.

[0116] It should be understood that before sending the prompt message for entering the first account, it is also possible to judge the data of the first binding accounts bound to the second account, and send the prompt message for entering the first account when the amount of data of the first binding accounts bound is less than the first preset number, and when the number of first binding accounts bound is greater than or equal to the first preset number, first unbind the first binding account that has not been logged in for the longest time, and then send the prompt message for entering the first account.

[0117] In one or more embodiments, the method further includes: receiving a request from the first application to establish a first binding relationship; when the second application is in the logged-in state and the number of first binding accounts in the second binding relationship corresponding to the second account is less than the second preset number, setting the second account as the second binding account in the first binding relationship corresponding to the first account, and setting the second binding relationship to add the first account as a first binding account; or when the second application is in the logged-in state and the number of first binding accounts in the second binding relationship corresponding to the second account is equal to the second preset number, obtaining the last login time corresponding to each first binding account; setting the second account as the second binding account in the first binding relationship corresponding to the first account, and setting the second binding relationship to delete the first binding account with the earliest last login time, and setting the second binding relationship to add the first account as a first binding account.

[0118] Wherein, the second preset number may be equal to the first preset number or may not be equal to the first preset number.

[0119] Optionally, as Figure 5 shown, the following steps are included:

[0120] Step 501: Receive a request from the first application to establish a first binding relationship.

[0121] Step 502: Determine whether the second application is in a logged-in state.

[0122] If so, execute Step 503; if not, control to issue a login prompt message for the second account.

[0123] Step 503: Obtain the number of first binding accounts included in the second binding relationship corresponding to the second account.

[0124] Step 504: Determine whether the number of first binding accounts is less than a second preset number.

[0125] If so, establish a second binding relationship based on the first account and the second account; if not, execute Step 505.

[0126] Step 505: Obtain the last login time corresponding to each first binding account.

[0127] Step 506: Use the first account to replace the first binding account with the earliest last login time.

[0128] It should be noted that when the second application is in an unlogged state, control to issue a prompt message for the second account. The prompt message can be the login interface of the second account or an independent account input interface.

[0129] That is to say, the first application can initiate a request to establish a binding relationship. When there is no logged-in second account, the account binding can be achieved by issuing a reminder message to prompt the user to input the corresponding account. When the second application has a logged-in second account, further determine the number of first binding accounts currently bound to the second account. When the number of first binding accounts bound to the second account is less than the second preset number, directly perform the binding operation. When the number of first binding accounts bound to the second account is greater than or equal to the second preset number, unbind the first account that has not been logged in for the longest time, and then bind the currently logged-in first account to the second account.

[0130] It should be understood that after issuing the prompt message for the second account and receiving the second account input by the user, it is also possible to judge the data of the first binding accounts bound to the second account. When the data volume of the first binding accounts bound is less than the second preset number, issue a prompt message for the first account. When the number of first binding accounts bound is greater than or equal to the second preset number, first unbind the first account that has not been logged in for the longest time, and then issue a prompt message for the first account.

[0131] In one or more embodiments, a request to set a second account as a second binding account in a first binding relationship is received; a login identifier corresponding to the second account is obtained; the second account is set as the second binding account in the first binding relationship, and the login identifier is recorded as the login identifier of the second binding account; wherein, when the first application is in a logged-in state, the first account can control the second application to log in to the second binding account through the login identifier.

[0132] Among them, the login ID is non-personal privacy information, and personal privacy information may include telephone number, email address, ID number, birthday, etc.

[0133] That is to say, by encrypting the second account, the encrypted information is used when performing synchronous login or logout operations, that is, the second application logs in or logs out according to the login identifier, thereby effectively avoiding leakage of user account information between the first application and the second application, that is, binding is performed using the login identifier corresponding to the second account, effectively avoiding the first application from obtaining the second account of the second application, and then avoiding leakage of the second account to the first application, further improving confidentiality.

[0134] Among them, the login identifier can be the encrypted information of the second account registration information, or it can be the login key issued by a third-party application to the second account. This application does not specifically limit the method for obtaining the login identifier.

[0135] In one or more embodiments, the first application and the second application may also initiate an unbinding request, that is, initiate a request to unbind the binding relationship, and control the unbinding relationship when the first application is in a logged-in state, wherein the first application may be controlled to log in or issue a reminder message that the first application needs to be logged in when the first application is not logged in. The unbinding request is used to unbind the binding relationship, for example, unbinding the first account is to delete the second bound account from the first binding relationship, and unbinding the second account is to delete the first bound account from the second binding relationship.

[0136] To summarize, the account management method based on a multi-application system proposed in the embodiment of the present application effectively implements account control of the first application and the second application by monitoring the login status of the first application and the second application, and based on the binding relationship corresponding to the login account when the first application and / or the second application is in the login state, effectively avoids the interaction of user account information between the first application and the second application, and reduces the risk of privacy leakage from the first application to the second application.

[0137] It should be noted that although the operations of the method of the present invention are described in a particular order in the drawings, this does not require or imply that the operations must be performed in this particular order or that all illustrated operations must be performed to achieve desired results.

[0138] Figure 6 This is a block diagram of an account management device based on multiple application systems proposed in an embodiment of the present application. Among them, the multiple application systems include a first application and a second application. The first application is an application program associated with the multiple application systems, and the second application is an application program provided by a third-party server.

[0139] As Figure 6 shown, the account management device 10 based on multiple application systems includes:

[0140] A first acquisition module 11, configured to acquire the login status of the first application and the login serial number corresponding to the first application, and when the first application is in the logged-in state, acquire the first account corresponding to the first application and the first binding relationship corresponding to the first account;

[0141] A second acquisition module 12, configured to acquire the login status of the second application, and when the second application is in the logged-in state, acquire the second account corresponding to the second application and the second binding relationship corresponding to the second account;

[0142] A control module 13, configured to determine an account control policy for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number;

[0143] Among them, the login serial number is used to represent the change situation of the login status of the first application;

[0144] The first binding relationship includes two states: empty and non-empty. When the first binding relationship is empty, the first account is not bound to the account of the second application; when the first binding relationship is non-empty, the first account and the second binding account of the second application are in a binding relationship;

[0145] The second binding relationship includes two states: empty and non-empty. When the second binding relationship is empty, the second account is not bound to any account of the first application; when the second binding relationship is non-empty, the second account and at least one first binding account of the first application are in a binding relationship.

[0146] In some embodiments, the control module 13 is further configured to:

[0147] When the first application is in the logged-in state, the first binding relationship is non-empty, and the second application is in the unlogged state, control the second application to log in to the second binding account; when the first application is in the logged-in state, the first binding relationship is non-empty, and when the second application is in the logged-in state and the second account is the same as the bound second account, control the second application to maintain the current state;

[0148] When the first application is in the logged-in state, and the first binding relationship is non-empty, and the second application is in the logged-in state, and the second account is different from the candidate second account, control the second application to log out of the second account, and control the second application to log in and bind to the second account.

[0149] In some embodiments, the control module 13 is further configured to:

[0150] When the first application is in the logged-in state, and the first binding relationship is empty, and the second application is in the logged-in state, and the login serial number changes, and the second binding relationship is non-empty, control the second application to log out of the second account.

[0151] When the first application is in the logged-in state, and the first binding relationship is empty, and the second application is in the logged-in state, and the login serial number changes, and the second binding relationship is empty, control to issue a reminder to establish a binding relationship between the first account and the second account.

[0152] In some embodiments, the control module 13 is further configured to:

[0153] When the first application is in the non-logged-in state, and the second application is in the logged-in state, and the second binding relationship is non-empty, and the login serial number changes, control the second application to log out of the second account.

[0154] In some embodiments, the control module 13 is further configured to:

[0155] When the first application is in the non-logged-in state, if the second application is in the non-logged-in state, or the second binding relationship is empty, or the login serial number does not change, control the second application to maintain the login state of the current state.

[0156] When the first application is in the logged-in state, and the first binding relationship is empty, if the second application is in the non-logged-in state, or the login serial number does not change, control the second application to maintain the login state of the current state.

[0157] In some embodiments, the control module 13 is further configured to:

[0158] Monitor the change of the login state of the first application, and record the prior first account information and the subsequent first account information in two adjacent logged-in states of the first application;

[0159] When the login state of the first application does not change, control the login serial number to remain unchanged;

[0160] When the login state of the first application changes from the logged-in state to the non-logged-in state, control the value of the login serial number to perform a first operation, and assign the result of the operation to the login serial number;

[0161] When the login status of the first application changes from the never - logged - in status to the logged - in status, identify whether the prior first account is the same as the subsequent first account;

[0162] If the prior first account is the same as the subsequent first account, control the login serial number to perform a second operation, and assign the result of the operation to the login serial number; wherein, the second operation is the inverse function of the first operation;

[0163] If the prior first account is not the same as the subsequent first account, control the login serial number to perform the first operation, and assign the result of the operation to the login serial number

[0164] In some embodiments, the control module 13 is further configured to:

[0165] Receive a request from the second application to establish a second binding relationship;

[0166] When the first application is in the logged - in state, and the first binding relationship corresponding to the first account is empty, and the number of the first binding accounts in the second binding relationship corresponding to the second account is less than the first preset number, set the second binding relationship to add the first account as a first binding account, and set the second account as the second binding account in the first binding relationship;

[0167] Or

[0168] When the first application is in the logged - in state, and the first binding relationship is empty, and the number of the first binding accounts in the second binding relationship is equal to the first preset number, obtain the last login time corresponding to each first binding account;

[0169] Set the second binding relationship to delete the first binding account with the earliest last login time, set the second binding relationship to add the first account as a first binding account, and set the second account as the second binding account in the first binding relationship.

[0170] In some embodiments, the control module 13 is further configured to:

[0171] Receive a request from the first application to establish a first binding relationship;

[0172] When the second application is in the logged - in state, and the number of the first binding accounts in the second binding relationship corresponding to the second account is less than the second preset number, set the second account as the second binding account in the first binding relationship corresponding to the first account, and set the second binding relationship to add the first account as a first binding account;

[0173] Or

[0174] When the second application is in the logged-in state and the number of first bound accounts in the second binding relationship corresponding to the second account is equal to the second preset number, obtain the last login time corresponding to each first bound account;

[0175] Set the second account as the second bound account in the first binding relationship corresponding to the first account, set the second binding relationship to delete the first bound account with the earliest last login time, and set the second binding relationship to add the first account as a first bound account.

[0176] In some embodiments, the control module 13 is further configured to:

[0177] Receive a request to set the second account as the second bound account in the first binding relationship;

[0178] Obtain the login identifier corresponding to the second account;

[0179] Set the second account as the second bound account in the first binding relationship, and record the login identifier as the login identifier of the second bound account;

[0180] Wherein, when the first application is in the logged-in state, the first account can control the second application to log in to the second bound account through the login identifier.

[0181] In some embodiments, the login identifier is non-personal privacy information.

[0182] It should be understood that the various units or modules described in the account management device 10 based on the multi-application system correspond to the respective steps in the method described with reference to Figure 1 Therefore, the operations and features described above for the method also apply to the account management device 10 based on the multi-application system and the units included therein, and will not be repeated here. The account management device 10 based on the multi-application system can be pre-implemented in the browser or other security applications of the electronic device, or can be loaded into the browser or its security application of the electronic device by means of downloading, etc. The corresponding units in the account management device 10 based on the multi-application system can cooperate with the units in the electronic device to implement the solutions of the embodiments of the present application.

[0183] For the several modules or units mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0184] In summary, the account management device based on multiple application systems proposed in the embodiments of the present application effectively realizes account control for the first application and the second application by monitoring the login statuses of the first application and the second application, and according to the binding relationship corresponding to the logged-in account when the first application and / or the second application is in the logged-in state. It effectively avoids the interaction of user account information between the first application and the second application, and reduces the risk of privacy leakage from the first application to the second application.

[0185] It should be noted that for the details not disclosed in the account management device based on multiple application systems in the embodiments of the present application, please refer to the details disclosed in the above embodiments of the present application, and will not be elaborated here.

[0186] Next, referring to Figure 7 , Figure 7 FIG. shows a schematic structural diagram of a computer system of an electronic device or a server suitable for implementing the embodiments of the present application.

[0187] As Figure 7 shown, the computer system includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 702 or the program loaded from the storage section 708 into the random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation instructions of the system are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. The input / output (I / O) interface 705 is also connected to the bus 704.

[0188] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed so that the computer program read from it can be installed into the storage section 708 as needed.

[0189] Specifically, according to the embodiments of the present application, referring to the above flowchart Figure 2The described process can be implemented as a computer software program. For example, embodiments of the present application include a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes program code for performing the method shown in the flowchart. In such an embodiment, the computer program includes program code for performing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and / or installed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above functions defined in the system of the present application are performed.

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

[0191] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operation instructions of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the foregoing module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the accompanying drawings. For example, two connected blocks may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as the combination of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operation instructions, or may be implemented by a combination of dedicated hardware and computer instructions.

[0192] The units or modules involved in the embodiments described in the present application can be implemented in software or in hardware. The described units or modules can also be provided in a processor. For example, it can be described as: a processor includes a first acquisition module, a second acquisition module, and a control module. Among them, the names of these units or modules do not constitute a limitation on the units or modules themselves in some cases. For example, the first acquisition module can also be described as "acquiring the login status of the first application and the login serial number corresponding to the first application, and when the first application is in the login state, acquiring the first account corresponding to the first application, and the first mapping relationship corresponding to the first account, where the login serial number is used to represent the change in the login status of the first application".

[0193] On the other hand, the present application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments, or may exist separately without being assembled into the electronic device. The above computer-readable storage medium stores one or more programs, and when the above programs are executed by one or more processors, they are used to perform the account management method for a multi-application system described in the present application.

[0194] The above description is only the preferred embodiments of the present application and the description of the applied technical principles. Those skilled in the art should understand that the scope of disclosure involved in the present application is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the foregoing disclosure concept. For example, the technical solutions formed by mutually replacing the above features with the technical features (but not limited to) having similar functions disclosed in the present application.

Claims

1. An account management method based on a multi-application system, characterized in that, The multi-application system includes a first application and a second application. The first application is an application program associated with the multi-application system, and the second application is an application program provided by a third-party server. The method includes: Obtain the login status of the first application and the login serial number corresponding to the first application. When the first application is in the logged-in state, obtain the first account corresponding to the first application and the first binding relationship corresponding to the first account; Obtain the login status of the second application. When the second application is in the logged-in state, obtain the second account corresponding to the second application and the second binding relationship corresponding to the second account; Determine the account control policies for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number; Wherein, the login serial number is a sequence number that changes continuously according to the login situation of the first account in the first application, and is used to identify the change situation of the login status of the first application and whether the two consecutive login operations are for the same account; The first binding relationship includes two states: empty and non-empty. When the first binding relationship is empty, the first account is not bound to the account of the second application; when the first binding relationship is non-empty, the first account is in a binding relationship with the second binding account of the second application; The second binding relationship includes two states: empty and non-empty. When the second binding relationship is empty, the second account is not bound to any account of the first application; when the second binding relationship is non-empty, the second account is in a binding relationship with at least one first binding account of the first application.

2. The method according to claim 1, wherein The determining the account control policies for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number includes: When the first application is in the logged-in state, the first binding relationship is non-empty, and the second application is in the non-logged-in state, control the second application to log in to the second binding account; when the first application is in the logged-in state, the first binding relationship is non-empty, and when the second application is in the logged-in state and the second account is the same as the second binding account, control the second application program to maintain the current state; When the first application is in the logged-in state, the first binding relationship is non-empty, and when the second application is in the logged-in state and the second account is different from the candidate second account, control the second application to log out of the login state of the second account and control the second application to log in to the bound second account.

3. The method according to claim 1, wherein The determining the account control policies for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number includes: When the first application is in a logged-in state, the first binding relationship is empty, the second application is in a logged-in state, the login serial number changes, and the second binding relationship is non-empty, control the second application to exit the logged-in state of the second account; When the first application is in a logged-in state, the first binding relationship is empty, the second application is in a logged-in state, the login serial number changes, and the second binding relationship is empty, control to issue a reminder to establish a binding relationship between the first account and the second account.

4. The method according to claim 1, wherein Determining an account control policy for the first application and the second application according to the login state of the first application, the login state of the second application, the first binding relationship, the second binding relationship, and the login serial number includes: When the first application is in an unlogged state, the second application is in a logged-in state, the second binding relationship is non-empty, and the login serial number changes, control the second application program to exit the logged-in state of the second account.

5. The method according to claim 1, characterized in that Determining an account control policy for the first application and the second application according to the login state of the first application, the login state of the second application, the first binding relationship, the second binding relationship, and the login serial number includes: When the first application is in an unlogged state, if the second application is in an unlogged state, or the second binding relationship is empty, or the login serial number does not change, control the second application to maintain the logged-in state of the current state; When the first application is in a logged-in state and the first binding relationship is empty, if the second application is in an unlogged state, or the login serial number does not change, control the second application to maintain the logged-in state of the current state.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Monitor the change of the login state of the first application, and record the prior first account information and the subsequent first account information in two adjacent logged-in states of the first application; When the login state of the first application does not change, control the login serial number to remain unchanged; When the login state of the first application changes from a logged-in state to an unlogged state, control the login serial number to perform a first operation, and assign the result of the operation to the login serial number; When the login state of the first application changes from an unlogged state to a logged-in state, identify whether the prior first account is the same as the subsequent first account; If the prior first account is the same as the subsequent first account, control the login serial number to perform a second operation, and assign the result of the operation to the login serial number; wherein, the second operation is the inverse function of the first operation; If the prior first account is not the same as the subsequent first account, control the login serial number to perform a first operation, and assign the result of the operation to the login serial number.

7. The method according to claim 1, characterized in that, The method further includes: Receive a request from the second application to establish the second binding relationship; When the first application is in a logged-in state, the first binding relationship corresponding to the first account is empty, and the number of the first binding accounts in the second binding relationship corresponding to the second account is less than a first preset number, set the second binding relationship to add the first account as a first binding account, and set the second account as a second binding account in the first binding relationship; Or When the first application is in a logged-in state, the first binding relationship is empty, and the number of the first binding accounts in the second binding relationship is equal to the first preset number, obtain the last login time corresponding to each of the first binding accounts; Set the second binding relationship to delete the first binding account with the earliest last login time, set the second binding relationship to add the first account as a first binding account, and set the second account as a second binding account in the first binding relationship.

8. The method according to claim 1, characterized in that The method further includes: Receive a request from the first application to establish the first binding relationship; When the second application is in a logged-in state and the number of the first binding accounts in the second binding relationship corresponding to the second account is less than a second preset number, set the second account as a second binding account in the first binding relationship corresponding to the first account, and set the second binding relationship to add the first account as a first binding account; Or When the second application is in a logged-in state and the number of the first binding accounts in the second binding relationship corresponding to the second account is equal to the second preset number, obtain the last login time corresponding to each of the first binding accounts; Set the second account as a second binding account in the first binding relationship corresponding to the first account, set the second binding relationship to delete the first binding account with the earliest last login time, and set the second binding relationship to add the first account as a first binding account.

9. The method according to claim 1, wherein The method further includes: Receive a request to set the second account as a second binding account in the first binding relationship; Obtain the login identifier corresponding to the second account; Set the second account as a second binding account in the first binding relationship, and record the login identifier as the login identifier of the second binding account; Wherein, when the first application is in a logged-in state, the first account can control the second application to log in to the second binding account through the login identifier.

10. The method according to claim 9, wherein The login identifier is not personal privacy information.

11. An account management device based on a multi-application system, characterized in that, The multi-application system includes a first application and a second application. The first application is an application program associated with the multi-application system, and the second application is an application program provided by a third-party server. The device includes: A first acquisition module, configured to acquire the login state of the first application and the login serial number corresponding to the first application, and when the first application is in a logged-in state, acquire the first account corresponding to the first application and the first binding relationship corresponding to the first account; A second acquisition module, configured to acquire the login status of the second application, and when the second application is in the logged-in state, acquire the second account corresponding to the second application and the second binding relationship corresponding to the second account; A control module, configured to determine an account control policy for the first application and the second application according to the login status of the first application, the login status of the second application, the first binding relationship, the second binding relationship, and the login serial number; Wherein, the login serial number is a serial number that changes continuously according to the login situation of the first account in the first application, and is used to identify the change situation of the login status of the first application and whether the two consecutive login operations are the same account; The first binding relationship includes two states: empty and non-empty. When the first binding relationship is empty, the first account is not bound to the account of the second application; when the first binding relationship is non-empty, the first account and the second binding account of the second application are in a binding relationship; The second binding relationship includes two states: empty and non-empty. When the second binding relationship is empty, the second account is not bound to any account of the first application; when the second binding relationship is non-empty, the second account and at least one first binding account of the first application are in a binding relationship.

12. A terminal device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the account management method based on a multi-application system according to any one of claims 1-10.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the account management method based on a multi-application system according to any one of claims 1-10.

Images