Account login method and device

Abstract

The invention provides an account login method and device, and relates to the technical field of data processing. A login request instruction sent by a third-party system is received, the login request instruction is analyzed to obtain a user token, and the user token at least comprises user communication elements of a target user to be logged in; a member main table and a member detailed table are obtained, the member main table is used for recording the mapping relation among the communication elements, the identity elements and the accounts of the members, and the member detailed table is used for recording the historical login information of the members; determining a target account corresponding to the target user according to at least one of the user token, the member main table and the member detailed table; determining a remaining account related to the identity element corresponding to the target account from the member detail list, and generating a target account parameter according to account parameters corresponding to the target account and the remaining account; and rendering an account interface according to the target account parameter, and returning the account interface to the third-party system for display.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to an account login method and device thereof. Background Art

[0002] With the rapid development of Internet technology, users need to frequently log in to various online services in their daily lives, such as social media, e-commerce websites, banking services, etc. Traditional login methods usually require users to manually enter their account and password, which is not only cumbersome but also prone to password leakage and other problems. Therefore, exploring more convenient and secure login methods has become an urgent need for industry development. Summary of the invention

[0003] The present disclosure provides an account login method and device thereof, so as to at least solve the problem that the traditional login method in the related art usually requires the user to manually input the account number and password, which is not only cumbersome but also easily leads to problems such as password leakage.

[0004] The first aspect of the present application proposes an account login method, including: receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token includes at least a user communication element of a target user to be logged in; obtaining a member main table and a member detail table, wherein the member main table is used to record the mapping relationship between the member's communication element, identity element and account, and the member detail table is used to record the member's historical login information; determining a target account corresponding to the target user according to at least one of the user token, the member main table and the member detail table; determining the remaining accounts related to the identity element corresponding to the target account from the member detail table, and generating target account parameters according to the account parameters corresponding to the target account and the remaining accounts; rendering an account interface according to the target account parameters, and returning the account interface to the third-party system for display.

[0005] According to one embodiment of the present application, a target account corresponding to a target user is determined based on at least one of a user token, a member master table, and a member detail table, including: in response to the existence of a user communication element in the member master table, obtaining an account bound to the user communication element from the member master table as the target account corresponding to the target user.

[0006] According to one embodiment of the present application, the account login method also includes: in response to the absence of a user communication element in the member main table, querying whether there is a target identity element bound to the user communication element in the member details table; in response to the presence of a target identity element bound to the user communication element in the member details table, determining the account bound to the target identity element from the member details table as the target account of the target user.

[0007] According to one embodiment of the present application, the account login method also includes: in response to the absence of a user communication element in the member main table and the absence of a target identity element bound to the user communication element in the member details table, registering a new account as the target account based on the user communication element.

[0008] According to an embodiment of the present application, after determining the account bound to the target identity element from the member details table as the target account of the target user, it also includes: updating the member main table based on the user communication element, the target identity element and the target account.

[0009] According to one embodiment of the present application, in response to the user token also including a user identity element, a target account corresponding to the target user is determined based on the user token, at least one of the member master table and the member detail table, including: in response to the existence of a user communication element in the member master table, determining the master table information corresponding to the user communication element in the member master table; querying whether the master table information includes the user identity element; in response to the master table information including the user identity element, obtaining the account included in the master table information as the target account.

[0010] According to one embodiment of the present application, the account login method also includes: in response to the absence of user communication elements in the member main table, or the main table information does not include user identity elements, querying whether there are user identity elements in the member details table; in response to the existence of user identity elements in the member details table, determining the account bound to the user identity element from the member details table as the target account of the target user.

[0011] According to one embodiment of the present application, the account login method also includes: in response to the absence of user communication elements in the member main table and the absence of user identity elements in the member details table, registering a new account as the target account based on the user communication elements and the user identity elements; and, in response to the main table information not including the user identity elements and the absence of the user identity elements in the member details table, registering a new account as the target account based on the user communication elements and the user identity elements.

[0012] According to one embodiment of the present application, after registering a new account as a target account based on user communication elements and user identity elements, it also includes: obtaining the real-name level of the third-party system; in response to the real-name level being greater than the level threshold, updating the member master table based on the user communication elements, user identity elements and the new account.

[0013] According to one embodiment of the present application, the process of determining the target account includes: for any identity element among the target identity element and the user identity element, obtaining the candidate account bound to any identity element in the member details table; obtaining login-related parameters of the candidate account; and determining the target account from the candidate accounts based on the login-related parameters.

[0014] According to one embodiment of the present application, the login-related parameter is the login time of the last login of the candidate account, and the target account is determined from the candidate accounts based on the login-related parameter, including: selecting the candidate account whose last login time is closest to the current time as the target account.

[0015] According to one embodiment of the present application, a target account is determined from candidate accounts based on login-related parameters, including: obtaining the login frequency and valid indicator bit of the candidate account; determining a valid first candidate account from the candidate accounts based on the valid indicator bit; and selecting the first candidate account with the highest login frequency as the target account.

[0016] The second aspect of the present application proposes an account login device, including: a receiving module, used to receive a login request instruction sent by a third-party system, and parse the login request instruction to obtain a user token, wherein the user token at least includes a user communication element of a target user to be logged in; an acquisition module, used to obtain a member main table and a member detail table, wherein the member main table is used to record the mapping relationship between the member's communication element, identity element and account, and the member detail table is used to record the member's historical login information; a determination module, used to determine a target account corresponding to the target user based on at least one of the user token, the member main table and the member detail table; a generation module, used to determine the remaining accounts related to the identity element corresponding to the target account from the member detail table, and generate target account parameters based on the account parameters corresponding to the target account and the remaining accounts; a return module, used to render an account interface based on the target account parameters, and return the account interface to the third-party system for display.

[0017] According to one embodiment of the present application, the determination module is further used to: in response to the existence of a user communication element in the member master table, obtain an account bound to the user communication element from the member master table as a target account corresponding to the target user.

[0018] According to one embodiment of the present application, the determination module is also used to: in response to the absence of a user communication element in the member main table, query whether there is a target identity element bound to the user communication element in the member details table; in response to the presence of a target identity element bound to the user communication element in the member details table, determine the account bound to the target identity element from the member details table as the target account of the target user.

[0019] According to one embodiment of the present application, the determination module is also used to: in response to the absence of a user communication element in the member main table and the absence of a target identity element bound to the user communication element in the member details table, register a new account as a target account based on the user communication element.

[0020] According to an embodiment of the present application, the determination module is further used to: update the member master table based on the user communication element, the target identity element and the target account number.

[0021] According to one embodiment of the present application, in response to the user token also including a user identity element, the determination module is also used to: in response to the existence of the user communication element in the member master table, determine the master table information corresponding to the user communication element in the member master table; query whether the master table information includes the user identity element; in response to the master table information including the user identity element, obtain the account included in the master table information as the target account.

[0022] According to one embodiment of the present application, the determination module is also used to: in response to the absence of user communication elements in the member main table, or the main table information does not include user identity elements, query whether there are user identity elements in the member details table; in response to the existence of user identity elements in the member details table, determine the account bound to the user identity element from the member details table as the target account of the target user.

[0023] According to one embodiment of the present application, the determination module is also used to: in response to the absence of user communication elements in the member main table and the absence of user identity elements in the member details table, register a new account as a target account based on the user communication elements and the user identity elements; and, in response to the main table information not including the user identity elements and the absence of the user identity elements in the member details table, register a new account as a target account based on the user communication elements and the user identity elements.

[0024] According to one embodiment of the present application, the determination module is also used to: obtain the real-name level of the third-party system; in response to the real-name level being greater than the level threshold, update the member master table based on user communication elements, user identity elements and the new account.

[0025] According to one embodiment of the present application, the determination module is also used to: for any identity element among the target identity element and the user identity element, obtain the candidate account bound to any identity element in the member details table; obtain login-related parameters of the candidate account; and determine the target account from the candidate accounts based on the login-related parameters.

[0026] According to one embodiment of the present application, the login-related parameter is the login time of the last login of the candidate account, and the determination module is also used to: select the candidate account whose last login time is closest to the current time as the target account.

[0027] According to one embodiment of the present application, the determination module is also used to: obtain the login frequency and valid indicator bit of the candidate account; determine the valid first candidate account from the candidate accounts based on the valid indicator bit; and select the first candidate account with the highest login frequency as the target account.

[0028] The third aspect embodiment of the present application proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to implement the account login method as described in the first aspect embodiment of the present application.

[0029] The fourth aspect embodiment of the present application proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to implement the account login method as described in the first aspect embodiment of the present application.

[0030] The fifth aspect embodiment of the present application proposes a computer program product, including a computer program, which, when executed by a processor, implements the account login method as described in the first aspect embodiment of the present application.

[0031] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects: the present application realizes a password-free login method based on a third-party login platform, and users do not need to manually enter their account number and password, but can log in through a token provided by a third-party system, thereby reducing the risk of password leakage; by combining the information of the member main table and the member detailed table, user tokens can be flexibly matched to ensure the accuracy of login; through the target account parameters, a more personalized service experience is provided; users can view complete account-related information in the third-party system without having to jump to other pages.

[0032] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0034] Figure 1 It is a schematic diagram of an exemplary implementation of an account login method shown in an embodiment of the present application.

[0035] Figure 2 It is a schematic diagram of an exemplary implementation of an account login method shown in an embodiment of the present application.

[0036] Figure 3 It is a schematic diagram of an exemplary implementation of an account login method shown in an embodiment of the present application.

[0037] Figure 4 It is an overall flow chart of an exemplary implementation of an account login method shown in an embodiment of the present application.

[0038] Figure 5 It is a schematic diagram of an account login device shown in an embodiment of the present application.

[0039] Figure 6 It is a schematic diagram of an electronic device shown in one embodiment of the present application. DETAILED DESCRIPTION

[0040] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0041] It should be noted that the acquisition, transmission, storage, use, and processing of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations.

[0042] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0043] Figure 1 is a schematic diagram of an exemplary implementation of an account login method shown in the present application, such as Figure 1 As shown, the account login method includes the following steps:

[0044] S101, receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token at least includes a user communication element of a target user to be logged in.

[0045] Receive a login request instruction sent by a third-party system, which contains the necessary information for the user to log in, such as a user token.

[0046] Among them, the user token includes at least the user's user communication element (such as mobile phone number or email address). In this way, the user does not need to manually enter the account number and password, and can log in through the token provided by the third-party system.

[0047] S102, obtaining a member master table and a member detail table, wherein the member master table is used to record the mapping relationship between the member's communication elements, identity elements and account number, and the member detail table is used to record the member's historical login information.

[0048] The member master table records the information of members who have been authenticated by real name, including the mapping relationship between communication elements (such as mobile phone number), identity elements (such as name, ID type, ID number) and account number. The record format is: mobile phone number + identity elements (name, ID type, ID number) + account number.

[0049] Among them, the member details table records all login behaviors of users and contains more information than the member master table, but not all of it is real-name authenticated. Some elements may be missing in the member details table, such as only communication elements (such as mobile phone numbers) but no identity elements. The member details table can supplement the missing information in the member master table to ensure the integrity and accuracy of the data.

[0050] S103, determining a target account corresponding to the target user according to at least one of the user token, the member master table and the member detail table.

[0051] Use the user's communication elements (such as mobile phone number) in the user token to find matching records in the member master table.

[0052] If there is a matching record in the main table, the target account is directly determined; if there is no matching record in the main table, it is searched in the member details table; if a matching record is found in the member details table, the account recorded in the member details table is used as the target account.

[0053] S104, determining the remaining accounts related to the identity elements corresponding to the target account from the member details table, and generating target account parameters according to the account parameters corresponding to the target account and the remaining accounts.

[0054] After the target account is determined, the remaining accounts (other accounts logged in using the same identity element) associated with the identity element corresponding to the target account are determined from the member list.

[0055] If there are remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are generated according to the account parameters (such as order parameters, etc.) corresponding to the target account and the remaining accounts.

[0056] If there are no remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are directly generated based on the account parameters corresponding to the target account.

[0057] S105, rendering the account interface according to the target account parameters, and returning the account interface to the third-party system for display.

[0058] According to the generated target account parameters, an account interface suitable for the user is rendered; the rendered account interface is returned to the third-party system, which is displayed to the user.

[0059] As an implementable manner, the display content on the account interface may include account boxes of remaining accounts associated with the target account, and the account boxes may be clicked to switch between accounts.

[0060] As another achievable manner, the display content on the account interface may include the total order details of multiple accounts, that is, the user's order history information on all accounts can be obtained by simply browsing the target account.

[0061] The embodiment of the present application proposes an account login method, including: receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token includes at least the user communication element of the target user to be logged in; obtaining a member master table and a member detail table, wherein the member master table is used to record the mapping relationship between the member's communication element, identity element and account, and the member detail table is used to record the member's historical login information; determining the target account corresponding to the target user according to at least one of the user token, the member master table and the member detail table; determining the remaining accounts related to the identity element corresponding to the target account from the member detail table, and generating target account parameters according to the account parameters corresponding to the target account and the remaining accounts; rendering the account interface according to the target account parameters, and returning the account interface to the third-party system for display. The present application implements a password-free login method based on a third-party login platform, where users do not need to manually enter their account and password, and can log in through the token provided by the third-party system, reducing the risk of password leakage; by combining the information of the member master table and the member detail table, flexibly matching the user token to ensure the accuracy of the login; providing a more personalized service experience through the target account parameters; users can view complete account-related information in the third-party system without jumping to other pages.

[0062] Figure 2 is a schematic diagram of an exemplary implementation of an account login method shown in the present application, such as Figure 2 As shown, the account login method includes the following steps:

[0063] S201, receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token at least includes a user communication element of a target user to be logged in.

[0064] S202, obtaining a member master table and a member detail table, wherein the member master table is used to record the mapping relationship between the member's communication elements, identity elements and account number, and the member detail table is used to record the member's historical login information.

[0065] Regarding the specific implementation of steps S201 to S202, reference may be made to the specific introduction of the relevant parts in the above embodiments, which will not be elaborated here.

[0066] S203, in response to the existence of the user communication element in the member master table, obtaining the account bound to the user communication element from the member master table as the target account corresponding to the target user.

[0067] Check whether there is a user communication element (such as user mobile phone number) of the target user to be logged in in the member main table. If the user communication element exists in the member main table, obtain the account bound to the user communication element from the member main table as the target account corresponding to the target user.

[0068] For example, if the user communication element of the target user to be logged in is the mobile phone number: 12345678910, then check whether 12345678910 exists in the column where the user communication element of the member main table is located. If 12345678910 exists in the member main table, and it is determined from the member main table that the account bound to 12345678910 is account A, then account A is used as the target account corresponding to the target user.

[0069] S204: In response to the user communication element not existing in the member master table, query the member detail table to see whether there is a target identity element bound to the user communication element.

[0070] If the user communication elements of the target user to be logged in do not exist in the member master table, the member details table is queried based on the user communication elements (if the member master table is not updated in a timely manner based on the member details table, it is possible that relevant complete real-name account information is saved in the member details table but not stored in the member master table. Therefore, in this step, after the user communication elements of the target user do not exist in the member master table, the member details table needs to be queried). If the user communication elements of the target user exist in the member details table, the identity elements queried from the member details table based on the user communication elements will be used as the target identity elements.

[0071] As an extension, as another achievable method, the API interface associated with the current system is queried based on the user communication element to obtain the target identity element.

[0072] S205 , in response to the existence of a target identity element bound to the user communication element in the member list, determining an account bound to the target identity element from the member list as a target account of the target user.

[0073] If there is a target identity element bound to the user communication element in the member list, then the candidate account bound to the target identity element in the member list is obtained.

[0074] As a feasible approach, if there is only one candidate account, the candidate account is directly used as the target account of the target user.

[0075] As another achievable manner, if there are multiple candidate accounts, the login-related parameters of each candidate account are obtained, and the target account is determined from the candidate accounts according to the login-related parameters.

[0076] Optionally, if the login-related parameter is the login time of the last login of the candidate account, when determining the target account from the candidate accounts based on the login-related parameter, the candidate account whose last login time is closest to the current time is selected as the target account.

[0077] Optionally, when determining the target account from the candidate accounts based on login-related parameters, obtain the login frequency and valid indication bit (used to indicate whether the candidate account is in a valid state at the current moment) of the candidate account; determine the valid first candidate account from the candidate accounts based on the valid indication bit; and select the first candidate account with the highest login frequency as the target account.

[0078] Furthermore, in S205, after the account bound to the target identity element is determined from the member details table as the target account of the target user, the member master table is updated based on the user communication element, the target identity element and the target account.

[0079] As an extension, if the target identity element is queried by querying the API interface associated with the current system, a new account is registered as the target account based on the user communication element and the target identity element, and the member main table is updated based on the user communication element, the target identity element and the target account.

[0080] S206 , in response to the user communication element not existing in the member master table and the target identity element bound to the user communication element not existing in the member detail table, registering a new account as the target account based on the user communication element.

[0081] If the user communication element does not exist in the member main table, and the target identity element bound to the user communication element does not exist in the member details table, it is not difficult to understand that the target user is likely to be a new user in the current system. In this case, a new account is directly registered based on the user communication element as the target account, and the target account is used for login without real name.

[0082] As an extension, if the API interface associated with the current system does not find the target identity element, a new account is directly registered as the target account based on the user communication element, and the target account is used for logging in without real name.

[0083] S207, determining the remaining accounts related to the identity elements corresponding to the target account from the member details table, and generating target account parameters according to the account parameters corresponding to the target account and the remaining accounts.

[0084] After the target account is determined, the remaining accounts related to the identity elements corresponding to the target account are determined from the member list.

[0085] If there are remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are generated according to the account parameters corresponding to the target account and the remaining accounts.

[0086] If there are no remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are directly generated based on the account parameters corresponding to the target account.

[0087] S208, rendering the account interface according to the target account parameters, and returning the account interface to the third-party system for display.

[0088] Regarding the specific implementation of steps S207 to S208, reference may be made to the specific introduction of the relevant parts in the above embodiments, which will not be elaborated here.

[0089] The embodiment of the present application focuses on comparing the user communication elements contained in the user token with the member master table and the member detail table, and realizes a password-free login method based on a third-party login platform. The user does not need to manually enter the account number and password, and can log in through the token provided by the third-party system, thereby reducing the risk of password leakage; by combining the information of the member master table and the member detail table, the user token is flexibly matched to ensure the accuracy of the login; through the target account parameters, a more personalized service experience is provided; the user can view complete account-related information in the third-party system without jumping to other pages.

[0090] Figure 3 is a schematic diagram of an exemplary implementation of an account login method shown in the present application, such as Figure 3 As shown, the account login method includes the following steps:

[0091] S301, receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token includes a user communication element and a user identity element of a target user to be logged in.

[0092] Different from the above-mentioned second embodiment, in this embodiment, the user token includes not only the user communication elements of the target user to be logged in, but also the user identity elements of the target user (such as name, certificate type, and certificate number).

[0093] In this application, the identity element directly carried in the user token is referred to as the user identity element.

[0094] S302, obtaining a member master table and a member detail table, wherein the member master table is used to record the mapping relationship between the member's communication elements, identity elements and account number, and the member detail table is used to record the member's historical login information.

[0095] S303, in response to the existence of the user communication element in the member master table, determining the master table information corresponding to the user communication element in the member master table, and querying whether the master table information includes the user identity element.

[0096] Check whether the user communication elements (such as user mobile phone number) of the target user to be logged in exist in the member master table. If the user communication elements exist in the member master table, determine the master table information corresponding to the user communication elements in the member master table, and check whether the master table information includes user identity elements (such as name, ID type, and ID number).

[0097] S304: In response to the main table information including the user identity element, the account number included in the main table information is obtained as the target account number.

[0098] S305: In response to the fact that the user communication element does not exist in the member master table, or the user identity element is not included in the master table information, query whether the user identity element exists in the member detail table.

[0099] S306, in response to the user identity element existing in the member details table, determining the account bound to the user identity element from the member details table as the target account of the target user.

[0100] If the user identity element exists in the member list, the candidate account bound to the user identity element in the member list is obtained.

[0101] As a feasible approach, if there is only one candidate account, the candidate account is directly used as the target account of the target user.

[0102] As another achievable manner, if there are multiple candidate accounts, the login-related parameters of each candidate account are obtained, and the target account is determined from the candidate accounts according to the login-related parameters.

[0103] Optionally, if the login-related parameter is the login time of the last login of the candidate account, when determining the target account from the candidate accounts based on the login-related parameter, the candidate account whose last login time is closest to the current time is selected as the target account.

[0104] Optionally, when determining the target account from the candidate accounts based on login-related parameters, obtain the login frequency and valid indication bit (used to indicate whether the candidate account is in a valid state at the current moment) of the candidate account; determine the valid first candidate account from the candidate accounts based on the valid indication bit; and select the first candidate account with the highest login frequency as the target account.

[0105] Furthermore, in S306, after the account bound to the user identity element is determined from the member details table as the target account of the target user, the member master table is updated based on the user communication element, the user identity element and the target account.

[0106] S307, in response to the absence of user communication elements in the member main table and the absence of user identity elements in the member details table, registering a new account as the target account based on the user communication elements and the user identity elements; and, in response to the main table information not including the user identity elements and the absence of user identity elements in the member details table, registering a new account as the target account based on the user communication elements and the user identity elements.

[0107] Furthermore, after registering a new account in the above S307, the real-name level of the third-party system is obtained. If the real-name level is greater than the level threshold, it means that the user identity elements uploaded by the third-party system are highly trustworthy. Therefore, the member master table is updated based on the user communication elements, user identity elements and the new account, thereby ensuring the real-name accuracy of the member account information stored in the member master table.

[0108] S308, determining the remaining accounts related to the identity elements corresponding to the target account from the member details table, and generating target account parameters according to the account parameters corresponding to the target account and the remaining accounts.

[0109] After the target account is determined, the remaining accounts related to the identity elements corresponding to the target account are determined from the member list.

[0110] If there are remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are generated according to the account parameters corresponding to the target account and the remaining accounts.

[0111] If there are no remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are directly generated based on the account parameters corresponding to the target account.

[0112] S309, rendering the account interface according to the target account parameters, and returning the account interface to the third-party system for display.

[0113] The embodiment of the present application focuses on comparing the user communication elements and user identity elements contained in the user token with the member master table and the member detail table, and realizes a password-free login method based on a third-party login platform. The user does not need to manually enter the account number and password, and can log in through the token provided by the third-party system, thereby reducing the risk of password leakage; by combining the information of the member master table and the member detail table, the user token is flexibly matched to ensure the accuracy of the login; through the target account parameters, a more personalized service experience is provided; the user can view complete account-related information in the third-party system without jumping to other pages.

[0114] Figure 4 is a general flow chart of an exemplary implementation of an account login method shown in the present application, such as Figure 4 As shown, the account login method includes the following steps:

[0115] S401, receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token at least includes a user communication element of a target user to be logged in.

[0116] S402, obtaining a member master table and a member detail table, wherein the member master table is used to record the mapping relationship between the member's communication elements, identity elements and account number, and the member detail table is used to record the member's historical login information.

[0117] Regarding the specific implementation of steps S401 to S402, reference may be made to the specific introduction of the relevant parts in the above embodiments, which will not be elaborated here.

[0118] S403, in response to the existence of the user communication element in the member master table, obtaining the account bound to the user communication element from the member master table as the target account corresponding to the target user.

[0119] S404: In response to the user communication element not existing in the member master table, query the member detail table to see whether there is a target identity element bound to the user communication element.

[0120] S405, in response to the existence of a target identity element bound to a user communication element in the member details table, determining the account bound to the target identity element from the member details table as the target account of the target user, and updating the member master table based on the user communication element, the target identity element and the target account.

[0121] S406, in response to the fact that the user communication element does not exist in the member master table and the target identity element bound to the user communication element does not exist in the member detail table, a new account is registered as the target account based on the user communication element. Since the target identity element is missing at this time, the member master table is not updated at this time, and the target account is logged in in an unrealized state.

[0122] Regarding the specific implementation of steps S403 to S406, reference may be made to the specific introduction of the relevant parts in the above embodiments, which will not be elaborated here.

[0123] Furthermore, the user token may include user identity elements in addition to user communication elements. The following S407 to S412 mainly introduce the case where the user token includes both user communication elements and user identity elements.

[0124] S407, when the user token includes both user communication elements and user identity elements, if the user communication elements exist in the member master table, determine the master table information corresponding to the user communication elements in the member master table, and query whether the master table information includes the user identity elements.

[0125] S408, in response to the main table information including the user identity element, obtaining the account included in the main table information as the target account.

[0126] S409, in response to the fact that the user communication element does not exist in the member master table, or the master table information does not include the user identity element, query whether the user identity element exists in the member detail table.

[0127] S410, in response to the existence of the user identity element in the member details table, determine the account bound to the user identity element from the member details table as the target account of the target user, and update the member master table based on the user communication element, the user identity element and the target account.

[0128] S411, in response to the absence of user communication elements in the member main table and the absence of user identity elements in the member details table, registering a new account as a target account based on the user communication elements and the user identity elements; and, in response to the main table information not including the user identity elements and the absence of user identity elements in the member details table, registering a new account as a target account based on the user communication elements and the user identity elements.

[0129] S412, after registering a new account in step S411, obtain the real-name level of the third-party system. In response to the real-name level being greater than the level threshold (the third-party system is considered to be a strong real-name authentication channel at this time), the member master table is updated based on the user communication elements, user identity elements and the new account.

[0130] Regarding the specific implementation of steps S407 to S412, reference may be made to the specific introduction of the relevant parts in the above embodiments, which will not be elaborated here.

[0131] S413, after the target account is determined, the remaining accounts related to the identity elements corresponding to the target account are determined from the member list, and the target account parameters are generated according to the account parameters corresponding to the target account and the remaining accounts.

[0132] After the target account is determined, the remaining accounts related to the identity elements corresponding to the target account are determined from the member list.

[0133] If there are remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are generated according to the account parameters corresponding to the target account and the remaining accounts.

[0134] If there are no remaining accounts related to the identity elements corresponding to the target account in the member details table, the target account parameters are directly generated based on the account parameters corresponding to the target account.

[0135] S414, rendering the account interface according to the target account parameters, and returning the account interface to the third-party system for display.

[0136] The embodiments of the present application introduce the account login process in two cases: one in which the user token only includes user communication elements, and the other in which it includes both user communication elements and user identity elements. The method realizes a password-free login method based on a third-party login platform. Users do not need to manually enter their account number and password, but can log in through a token provided by a third-party system, thereby reducing the risk of password leakage. By combining the information of the member main table and the member detailed table, user tokens can be flexibly matched to ensure the accuracy of login. Through the target account parameters, a more personalized service experience is provided. Users can view complete account-related information in the third-party system without having to jump to other pages.

[0137] It is not difficult to understand that in this application, after the login operation is performed based on the target account, the member details table needs to be recorded and updated.

[0138] Figure 5 is a schematic diagram of an account login device shown in this application, such as Figure 5 As shown, the account login device 500 includes a receiving module 501, an acquisition module 502, a determination module 503, a generation module 504 and a return module 505, wherein:

[0139] The receiving module 501 is used to receive a login request instruction sent by a third-party system, and parse the login request instruction to obtain a user token, wherein the user token at least includes a user communication element of a target user to be logged in.

[0140] The acquisition module 502 is used to acquire the member master table and the member detail table, wherein the member master table is used to record the mapping relationship between the member's communication elements, identity elements and account number, and the member detail table is used to record the member's historical login information.

[0141] The determination module 503 is used to determine the target account corresponding to the target user according to at least one of the user token, the member master table and the member detail table.

[0142] The generating module 504 is used to determine the remaining accounts related to the identity elements corresponding to the target account from the member details table, and generate the target account parameters according to the account parameters corresponding to the target account and the remaining accounts.

[0143] The return module 505 is used to render the account interface according to the target account parameters and return the account interface to the third-party system for display.

[0144] This device implements a password-free login method based on a third-party login platform. Users do not need to manually enter their account number and password, but can log in through the token provided by the third-party system, reducing the risk of password leakage. By combining the information of the member main table and the member detailed table, user tokens can be flexibly matched to ensure the accuracy of login. Through the target account parameters, a more personalized service experience is provided. Users can view complete account-related information in the third-party system without jumping to other pages.

[0145] Furthermore, the determination module 503 is further configured to: in response to the existence of the user communication element in the member master table, obtain the account bound to the user communication element from the member master table as the target account corresponding to the target user.

[0146] Furthermore, the determination module 503 is also used to: in response to the absence of a user communication element in the member main table, query whether there is a target identity element bound to the user communication element in the member details table; in response to the presence of a target identity element bound to the user communication element in the member details table, determine the account bound to the target identity element from the member details table as the target account of the target user.

[0147] Furthermore, the determination module 503 is further configured to: in response to the absence of the user communication element in the member master table and the absence of the target identity element bound to the user communication element in the member detail table, register a new account as the target account based on the user communication element.

[0148] Furthermore, the determination module 503 is further used to update the member master table based on the user communication element, the target identity element and the target account number.

[0149] Furthermore, in response to the user token also including a user identity element, the determination module 503 is also used to: in response to the existence of the user communication element in the member master table, determine the master table information corresponding to the user communication element in the member master table; query whether the master table information includes the user identity element; in response to the master table information including the user identity element, obtain the account included in the master table information as the target account.

[0150] Furthermore, the determination module 503 is also used to: in response to the absence of user communication elements in the member main table, or the main table information does not include user identity elements, query whether there are user identity elements in the member details table; in response to the existence of user identity elements in the member details table, determine the account bound to the user identity element from the member details table as the target account of the target user.

[0151] Further, the determination module 503 is further used to: in response to the absence of the user communication element in the member main table and the absence of the user identity element in the member detail table, register a new account as the target account based on the user communication element and the user identity element; and in response to the absence of the user identity element in the main table information and the absence of the user identity element in the member detail table, register a new account as the target account based on the user communication element and the user identity element.

[0152] Furthermore, the determination module 503 is also used to: obtain the real-name level of the third-party system; in response to the real-name level being greater than the level threshold, update the member master table based on the user communication elements, user identity elements and the new account.

[0153] Furthermore, the determination module 503 is also used to: for any identity element among the target identity element and the user identity element, obtain a candidate account bound to any identity element in the member details table; obtain login-related parameters of the candidate account; and determine the target account from the candidate accounts based on the login-related parameters.

[0154] Furthermore, the login-related parameter is the login time of the last login of the candidate account, and the determination module 503 is further used to: select the candidate account whose last login time is closest to the current time as the target account.

[0155] Furthermore, the determination module 503 is also used to: obtain the login frequency and valid indicator of the candidate account; determine a valid first candidate account from the candidate accounts according to the valid indicator; and select the first candidate account with the highest login frequency as the target account.

[0156] In order to implement the above embodiment, the present application embodiment further proposes an electronic device 600, such as Figure 6 As shown, the electronic device 600 includes: a processor 601 and a memory 602 communicatively connected to the processor, the memory 602 stores instructions executable by at least one processor, and the instructions are executed by at least one processor 601 to implement the account login method shown in the above embodiment.

[0157] In order to implement the above embodiment, the embodiment of the present application also proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to implement the account login method shown in the above embodiment.

[0158] In order to implement the above embodiments, the embodiments of the present application also propose a computer program product, including a computer program, which implements the account login method shown in the above embodiments when executed by a processor.

[0159] In the description of the present application, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

[0160] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0161] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0162] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0163] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. An account login method, characterized in that: include: Receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token at least includes a user communication element of a target user to be logged in; Obtaining a member master table and a member detail table, wherein the member master table is used to record the mapping relationship between the member's communication elements, identity elements and account number, and the member detail table is used to record the member's historical login information; Determine a target account corresponding to the target user according to at least one of the user token, the member master table and the member detail table; Determine the remaining accounts related to the identity elements corresponding to the target account from the member details table, and generate target account parameters according to the account parameters corresponding to the target account and the remaining accounts; An account interface is rendered according to the target account parameters, and the account interface is returned to the third-party system for display.

2. The method according to claim 1, characterized in that The determining the target account corresponding to the target user according to at least one of the user token, the member master table and the member detail table includes: In response to the user communication element existing in the member master table, an account bound to the user communication element is obtained from the member master table as a target account corresponding to the target user.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: In response to the user communication element not existing in the member master table, querying the member detail table whether there is a target identity element bound to the user communication element; In response to the existence of a target identity element bound to the user communication element in the member list, an account bound to the target identity element is determined from the member list as a target account of the target user.

4. The method according to claim 1, characterized in that The method further comprises: In response to the user communication element not existing in the member master table and the target identity element bound to the user communication element not existing in the member detail table, a new account is registered as the target account based on the user communication element.

5. The method according to claim 3, characterized in that: After determining the account bound to the target identity element from the member list as the target account of the target user, the method further includes: The member master table is updated based on the user communication element, the target identity element and the target account number.

6. The method according to claim 1, characterized in that In response to the user token also including a user identity element, determining the target account corresponding to the target user according to the user token, at least one of the member master table and the member detail table, comprises: In response to the user communication element existing in the member master table, determining the master table information corresponding to the user communication element in the member master table; Query whether the main table information includes the user identity element; In response to the main table information including the user identity element, an account number included in the main table information is obtained as the target account number.

7. The method according to claim 6, characterized in that The method further comprises: In response to the user communication element not existing in the member master table, or the user identity element not being included in the master table information, querying whether the user identity element exists in the member detail table; In response to the user identity element existing in the member list, an account bound to the user identity element is determined from the member list as a target account of the target user.

8. The method according to claim 7, characterized in that The method further comprises: In response to the user communication element not existing in the member master table and the user identity element not existing in the member detail table, registering a new account as a target account based on the user communication element and the user identity element; and, In response to the main table information not including the user identity element and the member list not containing the user identity element, a new account is registered as a target account based on the user communication element and the user identity element.

9. The method according to claim 8, characterized in that After registering a new account as a target account based on the user communication element and the user identity element, the method further includes: Obtaining the real-name level of the third-party system; In response to the real-name level being greater than a level threshold, the member master table is updated based on the user communication element, the user identity element and the new account.

10. The method according to claim 3 or 7, characterized in that: The process of determining the target account includes: For any identity element of the target identity element and the user identity element, obtaining a candidate account bound to the any identity element in the member list; Obtaining login-related parameters of the candidate account; A target account is determined from the candidate accounts according to the login-related parameters.

11. The method according to claim 10, characterized in that The login-related parameter is the login time of the last login of the candidate account, and determining the target account from the candidate accounts according to the login-related parameter includes: The candidate account whose last login time is closest to the current time is selected as the target account.

12. The method according to claim 10, characterized in that The determining a target account from the candidate accounts according to the login-related parameters includes: Obtaining the login frequency and valid indicator of the candidate account; Determining a valid first candidate account from the candidate accounts according to the valid indication bit; The first candidate account with the highest login frequency is selected as the target account.

13. An account login device, characterized in that: include: A receiving module, used for receiving a login request instruction sent by a third-party system, parsing the login request instruction to obtain a user token, wherein the user token at least includes a user communication element of a target user to be logged in; An acquisition module, used to acquire a member master table and a member detail table, wherein the member master table is used to record the mapping relationship between the member's communication elements, identity elements and account number, and the member detail table is used to record the member's historical login information; A determination module, configured to determine a target account corresponding to the target user according to at least one of the user token, the member master table and the member detail table; A generating module, configured to determine the remaining accounts related to the identity elements corresponding to the target account from the member list, and generate target account parameters according to the account parameters corresponding to the target account and the remaining accounts; The return module is used to render the account interface according to the target account parameters and return the account interface to the third-party system for display.

14. The device according to claim 13, characterized in that The determining module is further used for: In response to the user communication element existing in the member master table, an account bound to the user communication element is obtained from the member master table as a target account corresponding to the target user.

15. The device according to claim 13 or 14, characterized in that The determining module is further used for: In response to the user communication element not existing in the member master table, querying the member detail table whether there is a target identity element bound to the user communication element; In response to the existence of a target identity element bound to the user communication element in the member list, an account bound to the target identity element is determined from the member list as a target account of the target user.

16. The device according to claim 13, characterized in that The determining module is further used for: In response to the user communication element not existing in the member master table and the target identity element bound to the user communication element not existing in the member detail table, a new account is registered as the target account based on the user communication element.

17. The device according to claim 15, characterized in that The determining module is further used for: The member master table is updated based on the user communication element, the target identity element and the target account number.

18. The device according to claim 13, characterized in that In response to the user token further comprising a user identity element, the determining module is further configured to: In response to the user communication element existing in the member master table, determining the master table information corresponding to the user communication element in the member master table; Query whether the main table information includes the user identity element; In response to the main table information including the user identity element, an account number included in the main table information is obtained as the target account number.

19. The device according to claim 18, characterized in that The determining module is further used for: In response to the user communication element not existing in the member master table, or the user identity element not being included in the master table information, querying whether the user identity element exists in the member detail table; In response to the user identity element existing in the member list, an account bound to the user identity element is determined from the member list as a target account of the target user.

20. The device according to claim 19, characterized in that The determining module is further used for: In response to the user communication element not existing in the member master table and the user identity element not existing in the member detail table, registering a new account as a target account based on the user communication element and the user identity element; as well as, In response to the main table information not including the user identity element and the member list not containing the user identity element, a new account is registered as a target account based on the user communication element and the user identity element.

21. The device according to claim 20, characterized in that The determining module is further used for: Obtaining the real-name level of the third-party system; In response to the real-name level being greater than a level threshold, the member master table is updated based on the user communication element, the user identity element and the new account.

22. The device according to claim 15 or 19, characterized in that The determining module is further used for: For any identity element of the target identity element and the user identity element, obtaining a candidate account bound to the any identity element in the member list; Obtaining login-related parameters of the candidate account; A target account is determined from the candidate accounts according to the login-related parameters.

23. The device according to claim 22, characterized in that The login-related parameter is the last login time of the candidate account, and the determination module is further used to: The candidate account whose last login time is closest to the current time is selected as the target account.

24. The device according to claim 22, characterized in that The determining module is further used for: Obtaining the login frequency and valid indicator of the candidate account; Determining a valid first candidate account from the candidate accounts according to the valid indication bit; The first candidate account with the highest login frequency is selected as the target account.

25. An electronic device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 12.

26. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-12.

27. A computer program product comprising a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 12.

Images