Account login method and device, equipment and storage medium

Abstract

The invention discloses an account login method and device, equipment and a storage medium. Specifically, the method comprises the steps of calling an account generation service to execute an account generation task in response to an account acquisition request triggered based on an application login request of a target object under the condition that the target object logs in a target application for the first time; determining a target application account from a plurality of to-be-distributed application accounts in an account pre-storage area under the condition that calling of the account generation service fails, the plurality of to-be-distributed application accounts being a preset number of application accounts pre-generated through the account generation service under a real-time account number detection mechanism; and performing login verification processing based on the target application account to generate a first account login result. By means of the technical scheme, it can be guaranteed that the preset number of to-be-distributed application accounts are pre-stored in the account pre-storage area all the time, even if real-time calling of the account generation service fails, the accounts can be distributed to the new user for login, and therefore the login success rate of the new user is increased.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to an account login method, device, equipment and storage medium. Background Art

[0002] Currently, many applications on the application market are logged in through third-party accounts, such as QQ accounts, WeChat accounts, email accounts, etc. The application does not have its own account system. When the user logs in, the open interface of QQ and WeChat is directly called to query user information, login tickets and other information.

[0003] This method is "strongly dependent" on the third-party account system. When the third-party account system has problems, users will not be able to log in and use the application, especially new users who use the application for the first time. Login failure may cause the loss of new users and affect the operation and promotion of the application product. Summary of the invention

[0004] The present application provides an account login method, apparatus, device and storage medium. After receiving an application login request from a new user, even if the real-time call of the account generation service fails, a target application account can be allocated to the new user from a plurality of application accounts to be allocated pre-stored in the account pre-storage area for login, thereby improving the login (registration) success rate of the new user, thereby improving the user experience and the application attracting effect. The technical solution of the present application is as follows:

[0005] On the one hand, a method for logging in to an account is provided, the method comprising:

[0006] In the case where the target object logs in to the target application for the first time, in response to an account acquisition request triggered by the application login request of the target object, calling an account generation service to perform an account generation task;

[0007] In the case of failure in calling the account generation service, determining a target application account from a plurality of application accounts to be allocated in the account pre-stored area, wherein the plurality of application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service under a real-time account number detection mechanism;

[0008] A login verification process is performed based on the target application account to generate a first account login result.

[0009] On the other hand, an account login device is provided, the device comprising:

[0010] A first account generation service calling module is used to call the account generation service to perform an account generation task in response to an account acquisition request triggered by an application login request of the target object when the target object logs in to the target application for the first time;

[0011] a target application account determination module, configured to determine a target application account from a plurality of application accounts to be allocated in an account pre-stored area when the call to the account generation service fails, wherein the plurality of application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service under a real-time account number detection mechanism;

[0012] The first account login result generating module is used to perform login verification processing based on the target application account to generate a first account login result.

[0013] On the other hand, an account login device is provided, the device comprising a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the account login method as described in the first aspect.

[0014] On the other hand, a computer-readable storage medium is provided, in which at least one instruction or at least one program is stored, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the account login method as described in the first aspect.

[0015] On the other hand, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the account login method as described in the first aspect.

[0016] The present application provides an account login method, device, equipment and storage medium, which have the following technical effects:

[0017] In the application scenario of new user registration (first login), this application monitors the number of accounts in the account pre-storage area to ensure that the account pre-storage area always has a preset number of unallocated application accounts pre-stored. After receiving the application login request from the new user, even if the real-time call of the account generation service fails, the target application account can be allocated to the new user from the multiple unallocated application accounts pre-stored in the account pre-storage area for login, thereby improving the login (registration) success rate of new users and the reliability of the account login system, thereby improving the user experience and the application acquisition effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions and advantages in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 is a schematic diagram of an application environment provided by an embodiment of the present application;

[0020] Figure 2 It is a flowchart of an account login method provided in an embodiment of the present application;

[0021] Figure 3 This is a schematic diagram of a process of node election by an account server provided in an embodiment of the present application;

[0022] Figure 4 It is a flowchart of a method for an application login service to respond to an account acquisition request and call an account generation service to perform an account generation task provided by an embodiment of the present application;

[0023] Figure 5 is a schematic diagram of an account generation strategy provided in an embodiment of the present application;

[0024] Figure 6 A flowchart of another account login method provided in an embodiment of the present application;

[0025] Figure 7 This is a schematic diagram of the architecture of an account login system provided in an embodiment of the present application;

[0026] Figure 8 It is a schematic diagram of an account login process provided by an embodiment of the present application;

[0027] Fig. 9 It is a block diagram of a composition of an account login device provided in an embodiment of the present application;

[0028] Fig.10 It is a structural diagram of an account login device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0030] It should be noted that the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] It is understandable that in the specific implementation of this application, related data such as user information is involved. When the following embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0032] See also Figure 1 , Figure 1 1 is a schematic diagram of an application environment provided by an embodiment of the present application. The application environment may include a client 10, an application login service 20, and an account generation service 30. The client 10, the application login service 20, and the account generation service 30 may be indirectly connected via wireless communication. The application login service 20 includes at least one login server 21, and the account generation service 30 includes multiple account servers 31. When the target object logs in to the target application for the first time, the client 10 of the target object sends an application login request to the application login service 20. The application login service 20 triggers an account acquisition request in response to the application login request, and calls the account generation service 30 in response to the account acquisition request so that the account generation service 30 performs the account generation task. Then, when the call to the account generation service 30 fails, the target application account is determined from multiple application accounts to be allocated in the account pre-stored area. The multiple application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service 30 under the real-time account quantity detection mechanism. Then, a login verification process is performed based on the target application account to generate a first account login result, and the first account login result is returned to the client 10. It should be noted that Figure 1 Just an example.

[0033] The client can be a physical device such as a smart phone, a computer (such as a desktop computer, a tablet computer, a laptop computer), a digital assistant, an intelligent voice interaction device (such as an intelligent speaker), an intelligent wearable device, a vehicle-mounted terminal, etc., or it can be software running in a physical device, such as a computer program. The operating system corresponding to the first client can be an Android system (Android system), an iOS system (a mobile operating system developed by Apple), a Linux system (an operating system), a Microsoft Windows system (Microsoft Windows operating system), etc.

[0034] The server side can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The server can include a network communication unit, a processor, and a memory, etc. The server side can provide background services for the corresponding client.

[0035] The above-mentioned client 10, application login service 20 and account generation service 30 can be used to build a system for account login, which can be a distributed system. Taking the distributed system as a blockchain system as an example, it is formed by multiple nodes (any form of computing devices in the access network, such as servers, user terminals) and clients, and a peer-to-peer (P2P) network is formed between the nodes. The P2P protocol is an application layer protocol running on the Transmission Control Protocol (TCP) protocol. In a distributed system, any machine such as a server or a terminal can join and become a node, and the node includes a hardware layer, an intermediate layer, an operating system layer, and an application layer.

[0036] The functions of each node in the above blockchain system include:

[0037] 1) Routing: a basic function of a node, used to support communication between nodes.

[0038] In addition to the routing function, the node can also have the following functions:

[0039] 2) Applications are deployed in the blockchain to implement specific businesses based on actual business needs, record data related to the implementation of functions to form record data, carry digital signatures in the record data to indicate the source of the task data, and send the record data to other nodes in the blockchain system for other nodes to add the record data to a temporary block when they successfully verify the source and integrity of the record data.

[0040] 3) Blockchain, including a series of blocks that are connected to each other in the order of their generation. Once a new block is added to the blockchain, it will not be removed. The block records the record data submitted by the nodes in the blockchain system.

[0041] The following describes a specific embodiment of an account login method provided by this application. Figure 2It is a flowchart of an account login method provided by an embodiment of the present application. The present application provides method operation steps as described in the embodiment or flowchart, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only order of execution. When the actual system or product is executed, it can be executed in sequence or in parallel according to the method shown in the embodiment or the accompanying drawings (for example, in a parallel processor or multi-threaded processing environment). Specifically, as Figure 2 As shown, the method may include:

[0042] S201, the client sends an application login request of a target object to an application login service.

[0043] S202: When the target object logs in to the target application for the first time, the application login service triggers an account acquisition request based on the application login request.

[0044] In the embodiment of the present specification, the target object may be an object logging into the target application for the first time. Specifically, the target object may be a new user of the target application.

[0045] In a specific embodiment, the application login service may include at least one login server, and the client may send an application login request of the target object to any one of the at least one login server, so that the login server triggers an account acquisition request based on the application login request.

[0046] S203: The application login service responds to the account acquisition request and calls the account generation service to execute the account generation task.

[0047] In a specific embodiment, the above-mentioned account generation service may include multiple account servers, and the multiple account servers may include: multiple master account servers and multiple slave account servers. Specifically, each of the multiple master account servers can assign account generation tasks to multiple slave account servers, and each slave account server can execute the account generation task assigned to itself.

[0048] In a specific embodiment, the master account server and the slave account server among the multiple account servers can be determined by node election. Figure 3 , Figure 3It is a flow diagram of a node election performed by an account server provided in an embodiment of the present application. Specifically, the election server can be pre-set with multiple master nodes. Each account server in the multiple account servers of the account generation service can request the election server to seize each master node in turn. If account server A in the multiple account servers successfully seizes the master node x, account server A becomes the master node x and executes the task allocation process corresponding to the master node x; if account server B in the multiple account servers fails to seize all the master nodes, it becomes a slave node (slave account server) and detects change messages for multiple master nodes in real time; in the case that the account server corresponding to the master node y fails, the election server will delete the account server corresponding to the master node y, and send a change message for the master node y to the account server that has not been elected. The account server B that receives the change message can continue to run for the master node y. The account server B that succeeds in the election will be upgraded to become the master node and execute the task allocation process corresponding to the master node y.

[0049] In a specific embodiment, the above-mentioned change message for the master node may include: server deletion information for the master node.

[0050] In a specific embodiment, the above-mentioned account acquisition request may carry request association information. Specifically, the request association information may be any associated sequence of the account acquisition request, for example, it may include but is not limited to the request time corresponding to the account acquisition request, the request identification information corresponding to the account acquisition request, etc.

[0051] In a specific embodiment, Figure 4 As shown, the above application login service responds to the account acquisition request and calls the account generation service to perform the account generation task, which may include:

[0052] S401, the application login service calls the account generation service in response to the account acquisition request.

[0053] S402: The account generation service performs hash processing on the request association information based on the number of the multiple primary account servers to obtain first server index information.

[0054] In a specific embodiment, the account generation service performs hash processing on the request association information based on the number of multiple primary account servers to obtain the first server index information, which may include: the account generation service performs modulo processing on the request association information based on the number of multiple primary account servers to obtain the first server index information.

[0055] In some embodiments, the account generation service may perform a modulo process on the request time based on the number of multiple master account servers to obtain the first server index information; in other embodiments, the account generation service may also perform a modulo process on the request identification information based on the number of multiple master account servers to obtain the first server index information.

[0056] Illustratively, the number of the multiple master account servers is W, the request time is 16:32:22, and the result of 22%W is used as the first server index information.

[0057] S403: The account generation service sends an account generation task to a target master account server corresponding to the first server index information among the multiple master account servers.

[0058] In a specific embodiment, the account generation service can also pre-set the number of segments and the number segment ranges corresponding to each of the multiple master account servers, perform modulo processing on the request association information based on the preset number of segments, obtain the number segment index information, and use the master account server whose corresponding number segment range matches the number segment index information as the target master account server. Schematically, the preset number of segments is M, the number segment range corresponding to the master account server C is [m,n], and the request association information K corresponding to the account generation task sent by the account generation service to the master account server C needs to satisfy K%M≥m and K%M≤n. Specifically, the preset number of segments can be set in combination with the account generation demand in the actual application, and the number segment range corresponding to each master account server can be set in combination with the load balancing diversion demand in the actual application.

[0059] S404, the target master account server distributes the account generation task to a target slave account server among the multiple slave account servers.

[0060] In an optional embodiment, the target slave account server among multiple slave account servers can be determined in the following manner: the target master account server hashes the request association information based on the number of multiple slave account servers to obtain the second server index information, and uses the slave account server among the multiple slave account servers corresponding to the second server index information as the target slave account server.

[0061] In another optional embodiment, the target slave account server among the multiple slave account servers can be determined in the following manner: the target master account server detects the communication link between itself and the multiple slave account servers in real time, obtains the link quality information corresponding to each slave account server, and determines the target slave account server among the multiple slave account servers based on the link quality information. Specifically, the link quality information may include but is not limited to: request volume, request success rate, request timeout, etc.

[0062] S405 , the target master account server receives the target application account of the target slave account server based on the account generation task feedback.

[0063] It can be seen from the above embodiments that the account generation service performs hash processing on the request association information based on the number of multiple master account servers to obtain the first server index information, and sends the account generation task to the target master account server corresponding to the first server index information among the multiple master account servers, so that the target master account server distributes the account generation task to the target slave account server among the multiple slave account servers, realizes load balancing, prevents requests from being concentrated on the same machine, and thereby improves the efficiency and success rate of account generation.

[0064] In a specific embodiment, after the target master account server receives the target application account of the target slave account server based on the account generation task feedback, the method may further include:

[0065] The application login service receives the target application account fed back by the target master account server. The target master account server is the account server that campaigns for the target master node and is elected as the target master node when the change information for the target master node is detected in real time. The target master node is any master node among multiple master nodes, and the multiple master nodes are server nodes corresponding to multiple master account servers.

[0066] It can be seen from the above embodiments that the normal operation of the account generation service is guaranteed through node election and master node status detection, thereby improving the success rate of account generation.

[0067] S204, when the application login service fails to call the account generation service, the application login service determines the target application account from the multiple application accounts to be allocated in the account pre-stored area, and the multiple application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service under the real-time account quantity detection mechanism.

[0068] In the embodiment of this specification, the account pre-storage area can be used to store pre-generated application accounts to be allocated. Specifically, the account pre-storage area can include: a message queue, a memory, and the like.

[0069] In a specific embodiment, before the client sends the application login request of the target object to the application login service, the method may further include:

[0070] 1) The application login service performs real-time detection of the number of pre-stored application accounts to be allocated in the account pre-store area;

[0071] 2) When it is detected that the pre-stored amount is less than the preset amount, the application login service calls the account generation service to perform the account pre-generation task;

[0072] 3) The application login service receives the application account fed back by the account generation service based on the account pre-generation task;

[0073] 4) The application login service stores the application account in the account pre-storage area until the current pre-storage quantity reaches the preset quantity.

[0074] Specifically, the preset quantity here can be preset in combination with the account acquisition demand in actual application.

[0075] See also Figure 5 , Figure 5 It is a schematic diagram of an account generation strategy provided by an embodiment of the present application. Specifically, the account generation strategy includes: an account pre-generation process and an account real-time generation process. The account real-time generation process can execute the account generation task in real time by calling the account generation service, and the account pre-generation process can store the pre-generated account through the queue, and detect the account balance in the pre-generated account queue through the scheduled task. When the account balance is less than the configured threshold, the generation of a new account is triggered, and the newly generated account is written into the pre-generated account queue. When a new user registers (logins for the first time), the account real-time generation process is used first to assign an account to the new user. If the account real-time generation process fails to be called, the account is assigned to the new user from the pre-generated account queue, thereby ensuring that the new user can obtain a usable account when registering.

[0076] In a specific embodiment, the account pre-storage area may include: an account pre-storage memory and an account pre-storage queue, and the determining the target application account from the multiple application accounts to be allocated in the account pre-storage area may include: determining the target application account from the multiple application accounts to be allocated in the account pre-storage memory;

[0077] Accordingly, the above method may further include:

[0078] 1) The application login service performs real-time detection on the first pre-stored number of application accounts to be allocated in the account pre-stored memory, and when it is detected that the first pre-stored number is less than the first preset number, reads the application account from the account pre-stored queue and stores the application account in the account pre-stored memory until the current first pre-stored number reaches the preset number;

[0079] 2) During the process of the application login service reading the application account from the account pre-storage queue, a second pre-storage quantity of the application account to be allocated in the account pre-storage queue is detected in real time. When it is detected that the second pre-storage quantity is less than the second preset quantity, the account generation service is called to execute the account pre-generation task, the application account is received from the account generation service based on the account pre-generation task feedback, and the application account is stored in the account pre-storage queue until the current second pre-storage quantity reaches the second preset quantity.

[0080] Specifically, the first preset number and the second preset number here can be preset in combination with the account acquisition demand in actual application, wherein the first preset number is smaller than the second preset number.

[0081] It can be seen from the above embodiments that the real-time account number detection mechanism ensures that the account pre-storage area always stores a preset number of application accounts, avoiding the situation where no accounts can be allocated, thereby improving the login success rate of new users.

[0082] S205, the application login service performs a login verification process based on the target application account and generates a first account login result.

[0083] In a specific embodiment, the application login service performs login verification processing based on the target application account, and generating the first account login result may include:

[0084] 1) The application login service calls the ticket service to obtain the first account ticket corresponding to the target application account;

[0085] 2) The application login service performs login verification based on the target application account and the first account ticket to obtain the first account login result.

[0086] Specifically, the ticket service is used to generate account tickets for application accounts. Account tickets can be used to verify the legitimacy of the identity of the corresponding application account. Account tickets usually record account-related information such as the application account, account password, and ticket validity period. Among them, the ticket validity period can be configured based on the login security requirements in the actual application.

[0087] In a specific embodiment, the above-mentioned application login service performs login verification processing based on the target application account and the first account ticket, and the first account login result obtained may include: the application login service calls the ticket service to perform ticket validity verification on the first account ticket; if the ticket validity verification of the first account ticket passes, the first account login result generated by the application login service is a successful login; or if the ticket validity verification of the first account ticket fails, the first account login result generated by the application login service is a failed login.

[0088] In actual applications, when the login is successful, the application login service can return the first account login result and the target application account to the client to display the first account login result and the target application account to the target object.

[0089] It can be seen from the above embodiments that the application login service performs login verification processing based on the target application account and the first account ticket, and obtains the first account login result, which can improve the security of account login.

[0090] In an optional embodiment, the application login request carries the object identification information of the target object, and the application login service performs login verification processing based on the target application account, and generating the first account login result may include:

[0091] 1) The application login service encrypts the target application account based on the object identification information to obtain the encrypted account information;

[0092] 2) The application login service performs login verification based on the encrypted account information and generates a first account login result.

[0093] In a specific embodiment, encrypting the target application account based on the object identification information to obtain the encrypted account information may include: encrypting the target application account based on the object identification information and a symmetric encryption algorithm to obtain the encrypted account information.

[0094] In a specific embodiment, the application login request includes a first login request triggered by a third-party account of the target object, and the method may further include:

[0095] 1) In response to the first login request, the application login service sends a first account query request for the third-party account to a third-party server corresponding to the third-party account through the proxy server;

[0096] 2) When the application login service fails to obtain the first request response information for the first account query request, the account acquisition request is triggered.

[0097] Specifically, the third-party account may be an application account provided by a third-party application other than the target application.

[0098] Specifically, the application login service can interact with the third-party server through the proxy server, and configure the access of the third-party account through the proxy server, saving development manpower.

[0099] It can be seen from the above embodiments that in the scenario where the user logs in for the first time and fails to log in through a third-party account, even if the real-time call to the account generation service fails, the target application account can be allocated to the new user for login from multiple application accounts to be allocated pre-stored in the account pre-storage area, thereby improving the login (registration) success rate of new users and further improving the user experience and the effect of attracting new users to the application.

[0100] In a specific embodiment, after the application login service performs login verification processing based on the target application account and generates a first account login result, the method may further include:

[0101] 1) In response to a second login request triggered by a third-party account, the application login service sends a second account query request for the third-party account to the third-party server through the proxy server;

[0102] 2) The application login service receives a second request response message for the second account query request, the second request response message including: a second account ticket corresponding to the third-party account;

[0103] 3) The application login service calls the ticket service to verify the validity of the second account ticket;

[0104] 4) When the ticket validity check of the second account ticket passes, the application login service binds the third-party account to the target application account.

[0105] Specifically, the second login request may be an application login request triggered after the first login request.

[0106] In a specific embodiment, the second login request may carry a third-party account and a target application account input by the target object. When the validity of the respective tickets of the third-party account and the target application account are verified, the application login service binds the third-party account and the target application account, so that the target object can subsequently log in to the target application through the third-party account or the target application account, thereby improving the login success rate and user experience of existing users.

[0107] It can be seen from the above embodiments that the application login service calls the ticket service to verify the validity of the second account ticket. When the ticket validity verification of the second account ticket passes, the application login service binds the third-party account with the target application account, which can improve the security of the application account. In addition, the user can subsequently log in to the target application through the third-party account or the target application account, which improves the login success rate and user experience of existing users.

[0108] In an optional embodiment, after the application login service binds the third-party account to the target application account, the method may further include:

[0109] In response to the third login request triggered by the third-party account, the application login service performs a login verification process based on the first account ticket corresponding to the third-party account and the target application account, and generates a second account login result.

[0110] In an optional embodiment, after the application login service binds the third-party account to the target application account, the method may further include:

[0111] In response to the third login request triggered based on the target application account, the application login service performs a login verification process based on the second account ticket corresponding to the target application account and the third-party account, and generates a second account login result.

[0112] Specifically, the third login request may be an application login request triggered after the second login request. Due to the binding of the third-party account and the target application account, when the target object subsequently logs in to the application, the application login service may perform login verification processing on the second account ticket corresponding to the target application account and the third-party account, or perform login verification processing on the first account ticket corresponding to the third-party account and the target application account based on the preset login verification protocol between the client, so as to improve the success rate of login verification, thereby improving the login success rate of existing users.

[0113] It can be seen from the above embodiments that the success rate of login verification can be improved, thereby improving the login success rate of existing users.

[0114] In a specific embodiment, the target application account can also be bound to multiple third-party accounts, and the multiple third-party accounts can communicate with each other to improve the operation and promotion effects of the application product.

[0115] It can be seen from the technical solutions provided by the above embodiments of the present application that the normal operation of the account generation service is guaranteed and the success rate of account generation is improved through node election and master node status detection. In the scenario of new user registration (first login), the application login service monitors the number of accounts in the account pre-storage area to ensure that there are always a preset number of application accounts to be allocated in the account pre-storage area. After receiving the application login request of the new user, even if the real-time call of the account generation service fails, the target application account can be allocated to the new user from the multiple application accounts to be allocated pre-stored in the account pre-storage area for login, thereby improving the login (registration) success rate of the new user and the reliability of the account login system, thereby improving the application acquisition effect; and when the new user subsequently logs in based on a third-party account, the application login service calls the ticket service to perform a ticket validity check on the second account ticket corresponding to the third-party account. When the ticket validity check of the second account ticket passes, the third-party account is bound to the target application account, which can improve the security of the application account. In addition, the user can subsequently log in to the target application through the third-party account or the target application account, thereby improving the login success rate and user experience of existing users.

[0116] The following introduces another account login method provided by the embodiment of the present application using the application login service as the execution subject. Figure 6A flowchart of another account login method provided for an embodiment of the present application. It should be noted that this specification provides method operation steps as described in the embodiment or flowchart, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only order of execution. When the system or product is executed in practice, it can be executed in sequence or in parallel (for example, in a parallel processor or multi-threaded processing environment) according to the method shown in the embodiment or the accompanying drawings. Specifically, Figure 6 As shown, the above method may include:

[0117] S601, when the target object logs in to the target application for the first time, in response to an account acquisition request triggered by the application login request of the target object, calling an account generation service to perform an account generation task;

[0118] S602, in the case where the call to the account generation service fails, determining a target application account from a plurality of application accounts to be allocated in the account pre-stored area, where the plurality of application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service under a real-time account number detection mechanism;

[0119] S603: Perform login verification processing based on the target application account to generate a first account login result.

[0120] In a specific embodiment, before the above-mentioned response to the account acquisition request triggered by the application login request based on the target object, the above-mentioned method may further include:

[0121] 1) Real-time detection of the pre-stored number of application accounts to be allocated in the account pre-stored area;

[0122] 2) When it is detected that the pre-stored amount is less than the preset amount, the account generation service is called to perform the account pre-generation task;

[0123] 3) receiving the application account from the account generation service based on the account pre-generation task feedback;

[0124] 4) The application account is stored in the account pre-storage area until the current pre-storage quantity reaches the preset quantity.

[0125] In a specific embodiment, the account acquisition request carries request association information, the account generation service may include: multiple master account servers and multiple slave account servers, and the calling of the account generation service to perform the account generation task may include:

[0126] 1) Calling the account generation service based on the number of primary account servers, performing hash processing on the request association information, and obtaining the first server index information;

[0127] 2) Calling the account generation service to send an account generation task to a target master account server corresponding to the first server index information among multiple master account servers, so that the target master account server distributes the account generation task to a target slave account server among multiple slave account servers, and receives a target application account fed back by the target slave account server based on the account generation task.

[0128] In a specific embodiment, the above method may also include: receiving a target application account fed back by a target master account server, the target master account server being an account server that campaigns for a target master node and is elected as the target master node when change information for a target master node is detected in real time, the target master node being any one of a plurality of master nodes, and the plurality of master nodes being server nodes corresponding to each of the plurality of master account servers.

[0129] In a specific embodiment, the above-mentioned performing login verification processing based on the target application account to generate the first account login result may include:

[0130] 1) Call the ticket service to obtain the first account ticket corresponding to the target application account;

[0131] 2) Perform login verification based on the target application account and the first account ticket to obtain the first account login result.

[0132] In a specific embodiment, the application login request may include a first login request triggered based on a third-party account of the target object, and the method may further include:

[0133] 1) In response to the first login request, sending a first account query request for the third-party account to a third-party server corresponding to the third-party account through the proxy server;

[0134] 2) When the first request response information for the first account query request fails to be obtained, an account acquisition request is triggered.

[0135] In a specific embodiment, after performing the login verification process based on the target application account and generating the first account login result, the method may further include:

[0136] 1) in response to a second login request triggered by a third-party account, sending a second account query request for the third-party account to the third-party server through the proxy server;

[0137] 2) receiving a second request response message for the second account query request, the second request response message including: a second account ticket corresponding to the third-party account;

[0138] 3) Calling the ticket service to verify the validity of the second account ticket;

[0139] 4) When the ticket validity check of the second account ticket passes, the third-party account is bound to the target application account.

[0140] In a specific embodiment, after the third-party account is bound to the target application account, the method may further include: responding to a third login request triggered by the third-party account, performing login verification processing based on the first account ticket corresponding to the third-party account and the target application account, and generating a second account login result.

[0141] The specific detailed steps of the embodiment of the account login method written from the application login service side can be referred to the embodiment of the interactive side account login method, which will not be repeated here.

[0142] It can be seen from the technical solutions provided by the above embodiments of the present application that the normal operation of the account generation service is guaranteed and the success rate of account generation is improved through node election and master node status detection. In the scenario of new user registration (first login), the application login service monitors the number of accounts in the account pre-storage area to ensure that there are always a preset number of application accounts to be allocated in the account pre-storage area. After receiving the application login request of the new user, even if the real-time call of the account generation service fails, the target application account can be allocated to the new user from the multiple application accounts to be allocated pre-stored in the account pre-storage area for login, thereby improving the login (registration) success rate of the new user and the reliability of the account login system, thereby improving the application acquisition effect; and when the new user subsequently logs in based on a third-party account, the application login service calls the ticket service to perform a ticket validity check on the second account ticket corresponding to the third-party account. When the ticket validity check of the second account ticket passes, the third-party account is bound to the target application account, which can improve the security of the application account. In addition, the user can subsequently log in to the target application through the third-party account or the target application account, thereby improving the login success rate and user experience of existing users.

[0143] See also Figure 7 , Figure 7 This is a schematic diagram of the architecture of an account login system provided by an embodiment of the present application. Specifically, the account login system may include: an application client, an application access layer, an account generation service, an application login service, and a proxy service. The account generation service may include account pre-generation and real-time generation to ensure the success rate of account allocation when a new user logs in. The ticket service is used to generate independent tickets, and the ticket validity period is configurable. The proxy service can be used to call third-party service calls.

[0144] The embodiments of this application are based on Figure 7The system architecture diagram shown in FIG. 1 provides a schematic diagram of the account login process. Specifically, Figure 8 As shown in the figure, in the application scenario of third-party service failure, the user can initiate a login request on the application client, such as QQ login. In response to the login request, the client calls the third-party open interface to query the third-party account and ticket. The third party returns a service exception; or a network failure, such as a 100% failure rate of different user requests within a specified time. Then the client calls the access layer to generate an independent account and ticket, and tells the login server that "no need" to do third-party account ID and ticket verification. The access layer forwards the request to the login server. The login server calls the account server to query the account. The account server queries or generates the account ID in real time. If the user is a new user, the account ID is generated in real time and the newly generated account ID is directly returned. Or, if the real-time generation fails, it is obtained from the pre-generated account ID list to ensure that the new user can be assigned an account ID when logging in for the first time. The account server returns the account ID to the login server. The login server calls the ticket server to query or obtain an independent ticket. In the case of the first login of a new user, a new ticket corresponding to the newly assigned account is generated. In the case of the login of an existing user, the ticket validity period is refreshed, and the validity period is configurable. The ticket server returns the ticket to the login server. The login server returns the login or registration processing result to the access layer. The access layer returns the login or registration processing result to the client. The client displays the login result and account information to the user.

[0145] In the application scenario where the third-party service is running normally, the user initiates a login request on the application client, such as QQ login. The client calls the third-party open interface to query the third-party account and ticket. The third party returns the third-party account and ticket. The client calls the access layer to generate an independent account and ticket. The access layer forwards the request to the login server. The login server calls the account server to query the account. The account server queries or generates the account ID in real time. If the user is a new user, the account ID is generated in real time and the newly generated account ID is directly returned. Or, if the real-time generation fails, it is obtained from the pre-generated account ID list to ensure that the new user can be assigned an account ID when logging in for the first time. The account server returns the account ID to the login server. The login server calls the ticket server to query or obtain an independent ticket. In the case of the first login of a new user, a new ticket corresponding to the newly assigned account is generated. In the case of the login of an existing user, the ticket validity period is refreshed, and the validity period is configurable. The ticket server returns the ticket to the login server. The login server calls the proxy server to verify whether the third-party account ID and ticket are correct. Here, the login verification protocol preset between the client and the login server is used to determine whether to call the third-party service to verify the account ID and ticket. The proxy server forwards the request to the third-party service. The proxy server returns the third-party service to the login service. The login service calls the account server to request account binding. The account server returns the account binding result to the login server. The login server returns the login or registration processing result to the access layer. The access layer returns the login or registration processing result to the client. The client displays the login result and account information to the user.

[0146] The present application also provides an account login device, such as Fig. 9 As shown, the account login device may include:

[0147] A first account generation service calling module 910 is used to call an account generation service to perform an account generation task in response to an account acquisition request triggered by an application login request of the target object when the target object logs in to the target application for the first time;

[0148] The target application account determination module 920 is used to determine the target application account from the multiple application accounts to be allocated in the account pre-stored area when the call to the account generation service fails, where the multiple application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service under the real-time account number detection mechanism;

[0149] The first account login result generating module 930 is used to perform login verification processing based on the target application account and generate a first account login result.

[0150] In a specific embodiment, the above device may further include:

[0151] An account pre-deposit quantity monitoring module is used to perform real-time detection on the pre-deposit quantity of application accounts to be allocated in the account pre-deposit area;

[0152] The second account generation service calling module is used to call the account generation service to perform the account pre-generation task when it is detected that the pre-stored amount is less than the preset amount;

[0153] A pre-generated account receiving module, used to receive the application account fed back by the account generation service based on the account pre-generation task;

[0154] The pre-generated account storage module is used to store application accounts in the account pre-storage area until the current pre-stored number reaches a preset number.

[0155] In a specific embodiment, the account acquisition request carries request association information, the account generation service may include: multiple master account servers and multiple slave account servers, and the first account generation service calling module 910 may include:

[0156] A first hash processing unit, configured to call the account generation service based on the number of the plurality of primary account servers, perform hash processing on the request association information, and obtain first server index information;

[0157] An account generation task sending unit is used to call an account generation service to send an account generation task to a target master account server corresponding to the first server index information among multiple master account servers, so that the target master account server distributes the account generation task to a target slave account server among multiple slave account servers, and receives a target application account fed back by the target slave account server based on the account generation task.

[0158] In a specific embodiment, the above device may further include:

[0159] The target application account receiving unit is used to receive the target application account fed back by the target master account server. The target master account server is an account server that campaigns for the target master node and is elected as the target master node when the change information for the target master node is detected in real time. The target master node is any master node among multiple master nodes, and the multiple master nodes are server nodes corresponding to multiple master account servers respectively.

[0160] In a specific embodiment, the first account login result generating module 930 may include:

[0161] A first account ticket acquisition unit, configured to call a ticket service to acquire a first account ticket corresponding to a target application account;

[0162] The first login verification unit is used to perform login verification processing based on the target application account and the first account ticket to obtain a first account login result.

[0163] In a specific embodiment, the application login request may include a first login request triggered based on a third-party account of the target object, and the apparatus may further include:

[0164] A first account query request sending module, configured to respond to the first login request and send a first account query request for the third-party account to a third-party server corresponding to the third-party account through a proxy server;

[0165] The account acquisition request triggering unit is used to trigger the account acquisition request when the acquisition of the first request response information for the first account query request fails.

[0166] In a specific embodiment, the above device may further include:

[0167] A second account query request sending module, configured to respond to a second login request triggered based on a third-party account and send a second account query request for a third-party account to a third-party server through a proxy server;

[0168] A second request response information receiving module is used to receive second request response information for a second account query request, the second request response information including: a second account ticket corresponding to a third-party account;

[0169] A ticket validity verification module, used to call the ticket service to perform ticket validity verification on the second account ticket;

[0170] The account binding module is used to bind the third-party account to the target application account when the ticket validity check of the second account ticket passes.

[0171] In a specific embodiment, the above device may further include:

[0172] The second account login result generating module is used to respond to the third login request triggered by the third party account, perform login verification processing based on the first account ticket corresponding to the third party account and the target application account, and generate the second account login result.

[0173] It should be noted that the device in the device embodiment and the method embodiment are based on the same inventive concept.

[0174] An embodiment of the present application provides an account login device, which includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the account login method provided in the above method embodiment.

[0175] Further, Fig.10 A schematic diagram of the hardware structure of an account login device for implementing the account login method provided in the embodiment of the present application is shown. The account login device may participate in or include the account login apparatus provided in the embodiment of the present application. Fig.10 As shown, the account login device 100 may include one or more (1002a, 1002b, ..., 1002n are used to illustrate) processors 1002 (the processor 1002 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 1004 for storing data, and a transmission device 1006 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Fig.10 The structure shown is only for illustration and does not limit the structure of the above electronic device. Fig.10 More or fewer components as shown, or with Fig.10 Different configurations are shown.

[0176] It should be noted that the above-mentioned one or more processors 1002 and / or other data processing circuits may generally be referred to as "data processing circuits" in this article. The data processing circuit may be embodied in whole or in part as software, hardware, firmware, or any other combination. In addition, the data processing circuit may be a single independent processing module, or may be fully or partially integrated into any of the other components in the account login device 100 (or mobile device). As involved in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0177] The memory 1004 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the account login method described in the embodiment of the present application. The processor 1002 executes various functional applications and data processing by running the software programs and modules stored in the memory 1004, that is, to implement the above-mentioned account login method. The memory 1004 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1004 may further include a memory remotely arranged relative to the processor 1002, and these remote memories may be connected to the account login device 100 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0178] The transmission device 1006 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the account login device 100. In one example, the transmission device 1006 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one embodiment, the transmission device 1006 can be a radio frequency (Radio Frequency, RF) module, which is used to communicate with the Internet wirelessly.

[0179] The display may be, for example, a touch screen liquid crystal display (LCD), which may enable a user to interact with a user interface of the account login device 100 (or mobile device).

[0180] An embodiment of the present application also provides a computer-readable storage medium, which can be set in an account login device to store at least one instruction or at least one program related to the account login method in the method embodiment. The at least one instruction or the at least one program is loaded and executed by the processor to implement the account login method provided by the above method embodiment.

[0181] Optionally, in this embodiment, the storage medium may be located in at least one of the multiple network servers of the computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0182] The embodiment of the present application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the account login method provided in the method embodiment.

[0183] It should be noted that the above-mentioned sequence of the embodiments of the present application is only for description and does not represent the advantages and disadvantages of the embodiments. And the above-mentioned specific embodiments of the present application are described. Other embodiments are within the scope of the attached claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0184] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and equipment embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0185] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0186] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. An account login method, characterized in that: The method comprises: In the case where the target object logs in to the target application for the first time, in response to an account acquisition request triggered by the application login request of the target object, calling an account generation service to perform an account generation task; In the case of failure in calling the account generation service, determining a target application account from a plurality of application accounts to be allocated in the account pre-stored area, wherein the plurality of application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service under a real-time account number detection mechanism; A login verification process is performed based on the target application account to generate a first account login result.

2. The method according to claim 1, characterized in that: Before the account acquisition request triggered by the application login request based on the target object is responded to, the method further includes: Performing real-time detection on the pre-stored number of application accounts to be allocated in the account pre-stored area; In the case where it is detected that the pre-stored amount is less than the preset amount, calling the account generation service to perform the account pre-generation task; Receiving the application account fed back by the account generation service based on the account pre-generation task; The application account is stored in the account pre-storage area until the current pre-storage quantity reaches the preset quantity.

3. The method according to claim 1, characterized in that The account acquisition request carries request association information, the account generation service includes: a plurality of master account servers and a plurality of slave account servers, and the calling of the account generation service to perform the account generation task includes: Calling the account generation service to perform hash processing on the request association information based on the number of the multiple primary account servers to obtain first server index information; The account generation service is called to send the account generation task to a target master account server among the multiple master account servers corresponding to the first server index information, so that the target master account server distributes the account generation task to a target slave account server among the multiple slave account servers, and receives the target application account fed back by the target slave account server based on the account generation task.

4. The method according to claim 3, characterized in that The method further comprises: The target application account fed back by the target master account server is received, wherein the target master account server is an account server that campaigns for the target master node and is elected as the target master node when change information for the target master node is detected in real time, and the target master node is any master node among multiple master nodes, and the multiple master nodes are server nodes corresponding to each of the multiple master account servers.

5. The method according to claim 1, characterized in that The performing login verification processing based on the target application account to generate a first account login result includes: Calling a ticket service to obtain a first account ticket corresponding to the target application account; A login verification process is performed based on the target application account and the first account ticket to obtain a login result of the first account.

6. The method according to claim 1, characterized in that The application login request includes a first login request triggered based on a third-party account of the target object, and the method further includes: In response to the first login request, sending a first account query request for the third-party account to a third-party server corresponding to the third-party account through a proxy server; In the case where the first request response information for the first account query request fails to be obtained, the account acquisition request is triggered.

7. The method according to claim 6, characterized in that After performing the login verification process based on the target application account and generating a first account login result, the method further includes: In response to a second login request triggered based on the third-party account, sending a second account query request for the third-party account to the third-party server through the proxy server; receiving a second request response message for the second account query request, wherein the second request response message includes: a second account ticket corresponding to the third-party account; Calling the ticket service to perform ticket validity verification on the second account ticket; When the ticket validity check of the second account ticket passes, the third-party account is bound to the target application account.

8. The method according to claim 7, characterized in that After binding the third-party account with the target application account, the method further includes: In response to a third login request triggered based on the third-party account, a login verification process is performed based on the first account ticket corresponding to the third-party account and the target application account to generate a second account login result.

9. An account login device, characterized in that: The device comprises: A first account generation service calling module is used to call the account generation service to perform an account generation task in response to an account acquisition request triggered by an application login request of the target object when the target object logs in to the target application for the first time; a target application account determination module, configured to determine a target application account from a plurality of application accounts to be allocated in an account pre-stored area when the call to the account generation service fails, wherein the plurality of application accounts to be allocated are a preset number of application accounts pre-generated by the account generation service under a real-time account number detection mechanism; The first account login result generating module is used to perform login verification processing based on the target application account to generate a first account login result.

10. An account login device, characterized in that: The device includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the account login method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The storage medium stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the account login method as described in any one of claims 1 to 8.

12. A computer program product, characterized in that The computer program product includes at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the account login method as described in any one of claims 1 to 8.

Images