A cross-platform fast account verification method and device

By establishing an account verification relationship between the proxy server and the logged-in platform in the platform pool, setting a quick or verification code login method based on the device identifier and account association number of the user terminal, it solves the problem that users frequently enter account information on multiple platforms. The problem of this problem has achieved rapid cross-platform account verification, reducing resource consumption and tariffs, and improving efficiency.

CN117857164BActive Publication Date: 2024-11-12HUBEI DIGITAL IND DEV GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311846446.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-12-29
Publication Date
2024-11-12
Estimated Expiration
2043-12-29

AI Technical Summary

Technical Problem

In the prior art, users need to frequently enter user names and passwords or mobile phone numbers and verification codes on multiple Internet third-party platforms, resulting in cumbersome login process, increasing user burden and platform resource occupation, and the SMS verification code fee is relatively high.

Method used

By establishing an account verification relationship between the platform pool and the proxy server, setting up a quick login or verification code login method based on the device identifier and account association number of the user terminal, realizing fast cross-platform account verification, and centrally processing accounts of multiple platforms Verify the request and reduce the number of times the SMS verification code is sent.

Benefits of technology

It simplifies user operations, reduces platform resource consumption and tariff costs, improves the work efficiency of users and platforms, and realizes the convenience of multi-platform account verification.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117857164B_ABST
    Figure CN117857164B_ABST
Patent Text Reader

Abstract

The present invention relates to the field of Internet technology, and provides a cross-platform fast account verification method and device. The present invention establishes an account verification relationship between a proxy server corresponding to a platform pool and each log-in platform in the platform pool. After the log-in platform receives an account verification request, the proxy server to which it belongs is determined according to the account verification relationship, and the account verification request is transmitted to the proxy server; the account verification request is compared with a user terminal that has been used for account verification by the same user account, and an account verification method for processing the account verification request is determined to complete the account verification; the present invention centrally processes the account verification operations of multiple third-party platforms through a proxy server, greatly reducing the tediousness of account verification, reducing the computing resources and tariff costs of account verification for third-party platform enterprises, and improving overall work efficiency; work efficiency is improved on both the user side and the server side.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a cross-platform rapid account verification method and device. Background Art

[0002] As information systems continue to grow and become more complex, the need for effective management and control of user accounts is also increasing. In many scenarios, users need to use multiple systems and applications to complete their work, and each system may require a separate account verification operation. This not only causes trouble for users, but also increases the complexity of management.

[0003] With the development of Internet technology, a single user needs to log in to a large number of Internet third-party platforms every day (for the sake of convenience, hereinafter referred to as "third-party platforms"). In this scenario, the user name and password account verification method of the existing technology is not fast enough, and the user needs to enter the user name and password at least once on the login page of each third-party platform. When logging in to a large number of third-party platforms every day, memorizing a large number of user names and passwords and entering them multiple times creates a heavy burden on users, reducing their work efficiency.

[0004] The existing mobile phone SMS verification code login method has gradually replaced the traditional user name and password account verification method. The third-party platform sends a text message verification code to the mobile phone number entered by the user through the operator. The user enters the text message verification code into the third-party platform, and the third-party platform verifies the account according to the text message verification code entered by the user. This method solves the burden of memorizing a large number of user names and passwords to a certain extent, but for a large number of third-party platforms that need to be logged in, the user needs to enter the mobile phone number and fill in the verification code for each third-party platform, which is less convenient, resulting in the user's login to all third-party platforms being too cumbersome.

[0005] For third-party platforms, although they can reduce the SMS charges for sending SMS verification codes by signing an annual service contract with the operator, the annual charges are still high because the base number of SMS verification codes sent is large and the resources occupied by the operator cannot be reduced.

[0006] Moreover, since account verification on third-party platforms requires multiple steps such as obtaining a mobile phone number, generating and sending a verification code, and matching verification codes, the account verification scenario alone takes up a large amount of resources, reducing the overall performance of the corresponding third-party platform.

[0007] In view of this, overcoming the defects of the prior art is an urgent problem to be solved in the field of this technology. Summary of the invention

[0008] The technical problem to be solved by the present invention is to provide a cross-platform fast account verification method and device, the purpose of which is to save the SMS charges of the corresponding platforms, simplify the tediousness of user operations, and improve the overall work efficiency by realizing quick account verification associated with multiple platforms, thereby solving the problems in the prior art that the SMS verification code charges generated by the platform are high, and the account verification operation is too cumbersome due to the need to enter the mobile phone number and fill in the verification code for each platform.

[0009] The present invention adopts the following technical solution:

[0010] In a first aspect, the present invention provides a cross-platform fast account verification method, which determines a third-party platform to join a corresponding platform pool by signing a contract, and uses the third-party platform that has joined the platform pool as a log-in platform in the platform pool, wherein a platform pool includes at least one log-in platform, and a platform pool corresponds to a proxy server; the cross-platform fast account verification method includes:

[0011] Establishing an account verification relationship between the proxy server corresponding to the platform pool and each log-in platform in the platform pool;

[0012] After the login platform receives the account verification request, the login platform determines the corresponding proxy server according to the account verification relationship, and transmits the account verification request to the proxy server;

[0013] According to the account verification request and the user terminal that has been used for account verification with the same user account, an account verification method for processing the account verification request is determined; and according to the corresponding account verification method, the account verification of the user account is completed.

[0014] Further, a set of terminal identifiers that have been used to log in to any one of the platforms that can be logged in in the platform pool is maintained in advance, and the account verification method for processing the account verification request is determined according to the account verification request and the user terminal that has been used for account verification with the same user account; and the account verification of the user account is completed according to the corresponding account verification method, specifically including:

[0015] Obtaining an account verification request sent by the user terminal at the first sending time, the account verification request including an account associated number and a device identifier of the user terminal, the account verification request being used to log into one of the logable platforms in the platform pool;

[0016] If the device identifier does not exist in the terminal identifier set, or the device identifier is not used for account verification of the user account corresponding to the account-associated number, storing the device identifier in the terminal identifier set, and setting the account verification mode of the user account to the verification code login mode;

[0017] If the device identifier exists in the terminal identifier set, when the difference between the first sending time and the second sending time of the historical verification request corresponding to the device identifier is less than or equal to a first preset time, setting the account verification mode to a quick login mode; wherein the historical verification request has been used to log in to one of the log-inable platforms in the platform pool;

[0018] When the account verification method is a quick login method, querying the user account corresponding to the account-associated number; obtaining login information according to the account verification request, and completing the account verification according to the login information;

[0019] When the account verification method is a verification code login method, a verification code is sent to the account associated number; and the account verification is completed according to the verification code input by the user.

[0020] Further, obtaining login information according to the account verification request and completing the account verification according to the login information specifically includes:

[0021] The proxy server obtains the login information of at least one loginable platform required for the user account to log in according to the account verification request;

[0022] Sending the login information to the corresponding login platform;

[0023] The log-inable platform receives the login information, completes internal login logic according to the login information, and returns a jump response to the proxy server to complete account verification according to the jump response.

[0024] Furthermore, the login platform receives the login information and completes internal login logic according to the login information, specifically including:

[0025] Use the user name and the corresponding password to complete the first security verification of the log-in platform; wherein the login information includes the user name, password and security authentication information of the user account in the corresponding log-in platform;

[0026] Using the security authentication information, completing the second security verification of the log-in platform;

[0027] When both the first security authentication and the second security authentication are completed, setting the user account to a logged-in state;

[0028] Generate a URL of a successful login page of the user account on the login-able platform according to the login status; and generate a jump response carrying the URL of the successful login page.

[0029] Further, returning a redirect response to the proxy server to complete the account verification according to the redirect response specifically includes:

[0030] Returning a redirect response to the proxy server, wherein the redirect response carries the URL of the login success page of the corresponding login platform;

[0031] The proxy server forwards the jump response to the user terminal;

[0032] The client that can log in to the platform jumps to the login success page corresponding to the user account according to the login success page URL to complete the account verification.

[0033] Further, when the account verification method is a verification code login method, sending a verification code to the account associated number; completing the account verification according to the verification code entered by the user, specifically includes:

[0034] The proxy server generates a verification code corresponding to the user account, and sends the verification code corresponding to the user account to the account-associated number through the operator;

[0035] The user terminal obtains a verification code input by a user; generates a verification code matching request according to the verification code input by the user and the account associated number; and sends the verification code matching request to the proxy server;

[0036] The proxy server obtains the verification code input by the user according to the verification code matching request; when the verification code input by the user matches the verification code corresponding to the user account, the proxy server obtains login information according to the account verification request, and completes the account verification according to the login information.

[0037] Furthermore, before obtaining the account verification request sent by the user terminal at the first sending time, the method specifically includes:

[0038] Go to the login page of the platform;

[0039] After receiving a click event corresponding to the send verification code button, obtain the account associated number entered by the user on the login page;

[0040] Obtaining the device identifier; generating an account verification request for the log-in platform according to the device identifier and the account associated number;

[0041] The account verification request is sent to the log-in platform; the log-in platform forwards the account verification request to a proxy server.

[0042] Further, after completing the account verification of the user account according to the corresponding account verification method, it also includes:

[0043] Starting from the completion of account verification on one of the log-in platforms, recording the non-communication time between the client of the log-in platform and the proxy server corresponding to the log-in platform; wherein the client is running on the user terminal;

[0044] When the difference between the non-communication time and the connection time threshold is less than a second preset time, and the user account is in a logged-in state, the client sends a heartbeat message to the proxy server, where the heartbeat message carries a corresponding device identifier;

[0045] According to the first preset time corresponding to the logon platform and the heartbeat message in the proxy server corresponding to the logon platform, the account verification method of the user account is set to complete the account verification according to the corresponding account verification method.

[0046] Further, the setting of the account verification mode of the user account according to the first preset time corresponding to the log-in platform and the heartbeat message in the proxy server corresponding to the log-in platform specifically includes:

[0047] When the difference between the first sending time and the second sending time is greater than a first preset time, determining whether there is a heartbeat message carrying the device identifier;

[0048] If there is a heartbeat message carrying the device identifier, setting the account verification mode to a quick login mode;

[0049] If there is no heartbeat message carrying the device identifier, the account verification mode is set to the verification code login mode.

[0050] In a second aspect, the present invention further provides a cross-platform fast account verification device, which is used to implement the cross-platform fast account verification method described in the first aspect, and the cross-platform fast account verification device includes:

[0051] 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 processor to execute the cross-platform fast account verification method described in the first aspect.

[0052] In a third aspect, the present invention further provides a non-volatile computer storage medium, wherein the computer storage medium stores computer executable instructions, which are executed by one or more processors to complete the cross-platform fast account verification method described in the first aspect.

[0053] The present invention establishes an account verification relationship between a proxy server corresponding to a platform pool and each log-in platform in the platform pool. After the log-in platform receives an account verification request, the log-in platform determines the proxy server to which it belongs according to the corresponding account verification relationship, and transmits the account verification request to the proxy server; the account verifications of multiple third-party platforms are associated by signing contracts, so as to facilitate cross-platform rapid account verification. The account verification request is compared with the user terminal that has been used for account verification of the same user account, and the account verification method for processing the account verification request is determined; according to the corresponding account verification method, the account verification of the user account is completed; the present invention provides a cross-platform rapid account verification architecture, which centrally processes the account verification operations of multiple third-party platforms through a proxy server, greatly reducing the tediousness of account verification on the user side and the platform (server) side, reducing the computing resources and fee costs of account verification for third-party platform enterprises, and improving the overall work efficiency; the work efficiency is improved on both the user side and the server side.

[0054] Furthermore, the account verification request sent by the user terminal at the first sending time is obtained through the proxy server. When the device identifier of the corresponding user terminal is not stored in the proxy server, the account verification mode of the user account corresponding to the account association number is set to the verification code login mode; when the device identifier is stored in the proxy server, and when the difference between the first sending time and the second sending time of the historical verification request corresponding to the device identifier is less than or equal to the first preset time, the account verification mode is set to the quick login mode; according to the corresponding account verification mode, the account verification of the user account is completed. By realizing the quick account verification of multi-platform association, the number of times the SMS verification code is sent is reduced as much as possible, the corresponding enterprise's tariff is saved, the tediousness of user operations is simplified, and the overall work efficiency is improved; it is realized that only one account verification operation is performed on one of the platforms in the platform pool in the form of SMS verification code, and the account verification of all platforms in the platform pool can be directly completed through the same user terminal, which simplifies the tediousness of user operations and improves work efficiency on both the user side and the server side. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0056] Figure 1 This is a schematic diagram of the overall process of a cross-platform rapid account verification method provided by an embodiment of the present invention;

[0057] Figure 2 It is a schematic diagram of the relationship between a third-party platform, a platform pool and a proxy server provided by an embodiment of the present invention;

[0058] Figure 3 This is a schematic diagram of the interaction of the first account verification provided by an embodiment of the present invention;

[0059] Figure 4 This is a schematic diagram of an interaction of an account verification in the prior art provided by an embodiment of the present invention;

[0060] Figure 5 This is another interactive diagram of account verification in the prior art provided by an embodiment of the present invention;

[0061] Figure 6 A schematic diagram of the relationship between another third-party platform, a platform pool and a proxy server provided by an embodiment of the present invention;

[0062] Figure 7 is a specific flow chart of step 30 of an embodiment of the present invention;

[0063] Figure 8 is a specific flow chart of step 301 of an embodiment of the present invention;

[0064] Fig. 9 is a user interface diagram of a login page provided by an embodiment of the present invention;

[0065] Fig.10 This is a schematic diagram of the interaction of the second account verification provided by an embodiment of the present invention;

[0066] Fig.11 is a specific flow chart of step 304 of an embodiment of the present invention;

[0067] Fig.12 This is a schematic diagram of the interaction of the third account verification provided by an embodiment of the present invention;

[0068] Fig.13 is a flowchart of step 3043 of an embodiment of the present invention;

[0069] Fig.14 is another flowchart diagram of step 3043 of an embodiment of the present invention;

[0070] Fig.15 is a specific flow chart of step 305 of an embodiment of the present invention;

[0071] Fig.16 It is a flowchart of a cross-platform rapid account verification method provided by an embodiment of the present invention;

[0072] Fig.17This is a specific flow chart of a cross-platform fast account verification method provided by an embodiment of the present invention;

[0073] Fig.18 It is a schematic diagram of the architecture of a cross-platform fast account verification device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0074] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0075] In the description of the present invention, the terms "inside", "outside", "longitudinal", "lateral", "upper", "lower", "top", "bottom" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and do not require that the present invention must be constructed and operated in a specific orientation. Therefore, they should not be understood as limitations on the present invention.

[0076] The terms "first", "second", etc. in the present invention 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", "second", etc. may explicitly or implicitly include one or more of the features. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0077] In the present application, unless otherwise clearly specified and limited, the term "connection" should be understood in a broad sense. For example, "connection" can be a fixed connection, a detachable connection, or an integral connection; it can be a direct connection or an indirect connection through an intermediate medium.

[0078] In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0079] Embodiment 1:

[0080] Embodiment 1 of the present invention provides a cross-platform fast account verification method, which determines the third-party platform that joins the corresponding platform pool by signing a contract, and uses the third-party platform that has joined the platform pool as the log-in platform in the platform pool. A platform pool includes at least one log-in platform, and a platform pool corresponds to a proxy server; Figure 1 As shown, the cross-platform fast account verification method includes:

[0081] Step 10: Establish an account verification relationship between the proxy server corresponding to the platform pool and each log-in platform in the platform pool.

[0082] The embodiment of the present invention allows a third-party platform to sign a contract with a platform pool that matches the demand through market promotion, so as to complete cross-platform rapid account verification through a corresponding proxy server.

[0083] The embodiment of the present invention provides a cross-platform fast account verification architecture, which centrally processes the account verification operations of multiple third-party platforms through a proxy server, greatly reducing the tediousness of account verification on the user side and the platform (server) side, improving the account verification efficiency, and saving computing resource overhead and fee costs for the third-party platform.

[0084] like Figure 2 As shown, for example, the first platform, the second platform and the third platform sign a contract and join the first platform pool, and the fourth platform and the fifth platform sign a contract and join the second platform pool; a first account verification relationship is established between the first platform, the second platform and the third platform and the proxy server corresponding to the first platform pool, and the fourth platform and the fifth platform and the second platform pool establish a second account verification relationship between the proxy server corresponding to the second platform pool; wherein the first verification relationship refers to the mapping relationship between the proxy server of the first platform pool and the third-party platform joining the first platform pool, and the second verification relationship refers to the mapping relationship between the proxy server of the second platform pool and the third-party platform joining the second platform pool.

[0085] It should be noted that a proxy server corresponding to a platform pool in the embodiment of the present invention is not limited to a proxy server device in an actual physical device; in an optional embodiment, a proxy server cluster with data interoperability can be used to improve account verification performance, and the data that each proxy server in the proxy server cluster needs to process is implemented by technical personnel in this field with reference to the prior art and is not limited here.

[0086] Step 20: After the login platform receives the account verification request, the login platform determines the corresponding proxy server according to the account verification relationship, and transmits the account verification request to the proxy server.

[0087] like Figure 3 As shown, each time the login platform receives a verification request (eg, an account verification request), the received verification request is forwarded to the proxy server, which performs the account verification.

[0088] Step 30: Determine an account verification method for processing the account verification request based on the account verification request and the user terminal that has used the same user account for account verification; and complete the account verification of the user account based on the corresponding account verification method.

[0089] Among them, the embodiment of the present invention has two account verification methods, namely, the quick login method and the verification code login method. Figure 4 and Figure 5 As shown, the account verification method in the prior art needs to send a verification code, obtain the verification code input by the user, and match the verification code when performing an account verification on each platform that can be logged in. However, the cross-platform fast account verification method of the embodiment of the present invention only needs to use the verification code to verify the account at the first login for the same user terminal of the same user account (that is, use the verification code login method). When the corresponding verification request is received later, there is no need to send the verification code and match the verification code. The user does not need to enter the received verification code into the corresponding login page of the platform that can be logged in, but directly changes the login status of the user account on the platform that can be logged in to logged in (that is, use the quick login method); the fast verification method of the embodiment of the present invention greatly improves the work efficiency of the server side and the user side.

[0090] The more third-party platforms that join a platform pool at the same time, the more convenient the cross-platform fast account verification method of the embodiment of the present invention is. In an optional embodiment, all third-party platforms are signed to the same platform pool, and the proxy server corresponding to the platform pool is used to complete the account verification of all log-in platforms.

[0091] Specifically, for example, there are five third-party platforms: a first platform, a second platform, a third platform, a fourth platform, and a fifth platform.

[0092] like Figure 2 As shown, when the first account verification relationship is established between the first platform, the second platform and the third platform and the proxy server corresponding to the first platform pool, and the second account verification relationship is established between the fourth platform and the fifth platform and the proxy server corresponding to the second platform pool, for the same user account, after the account verification on the first platform and the second platform has been completed through the same user terminal within a certain period of time, when the proxy server of the first platform pool receives the account verification request of the third platform sent by the user terminal again, it can directly change the login status of the user account on the third platform to logged in, and complete the account verification on the third platform.

[0093] like Figure 6As shown, when the first platform, the second platform, the third platform, the fourth platform and the fifth platform have all established a first account verification relationship with the first platform pool, for the same user account, after the account verification on the first platform and the second platform has been completed through the same user terminal within a certain period of time, when the proxy server of the first platform pool receives the account verification request of the third platform, the fourth platform and the fifth platform sent by the user terminal again, the login status of the user account on the third platform, the fourth platform and the fifth platform can be directly changed to logged in, and the account verification on the third platform, the fourth platform and the fifth platform is completed. Among them, the proxy server performs account verification on the third platform, the fourth platform and the fifth platform separately.

[0094] Embodiment 2:

[0095] Based on Example 1, this embodiment of the present invention provides a preferred solution for a cross-platform fast account verification method. Specifically, Figure 7 As shown, a terminal identifier set that has been used to log in to any one of the platforms in the platform pool is maintained in advance, and the step 30 specifically includes:

[0096] Step 301: Obtain an account verification request sent by a user terminal at a first sending time, wherein the account verification request includes an account associated number and a device identifier of the user terminal, and the account verification request is used to log in to one of the logable platforms in a platform pool.

[0097] The proxy server maintains the specific time when the user terminal sends the account verification request on its own device or cloud device, so as to set the login method for the corresponding user account according to the time later; for example, the first sending time.

[0098] Step 302: If the device identifier does not exist in the terminal identifier set, or the device identifier is not used for account verification of the user account corresponding to the account association number, the device identifier is stored in the terminal identifier set, and the account verification method of the user account is set to the verification code login method.

[0099] The method for maintaining the terminal identifier set is selected by those skilled in the art according to a specific usage scenario and is not limited here.

[0100] A cleaning time interval may be set, and device identifiers that have not been used for login within a certain period of time may be regularly cleaned up at each cleaning time interval. A first mapping relationship between an account-associated number and a user account may be maintained in advance in the proxy server, and the user account may be determined based on the corresponding first mapping relationship and the account-associated number; a second mapping relationship between a device identifier of a user terminal used to send an account verification request and a user account corresponding to the account verification request may be maintained in advance, and whether the device identifier has been used for account verification of the corresponding user account may be determined based on the corresponding second mapping relationship.

[0101] Step 303: If the device identifier exists in the terminal identifier set, when the difference between the first sending time and the second sending time of the historical verification request corresponding to the device identifier is less than or equal to a first preset time, the account verification method is set to a quick login method; wherein the historical verification request has been used to log in to one of the logable platforms in the platform pool.

[0102] Among them, the account verification request is the verification request for the current request for account verification; the historical verification request is the verification request sent by the same user terminal corresponding to the corresponding account verification request and corresponding to the same user account as the corresponding account verification request, and the historical verification request has been used to complete the account verification of one of the platforms that can log in to the platform; the historical verification request and the account verification request both carry the account association number and the device identifier of the user terminal used for sending. The first preset time is selected by those skilled in the art according to the specific usage scenario and is not limited here; in an optional embodiment, the first preset time can be 12 hours.

[0103] In the quick login method of the embodiment of the present invention, the proxy server does not need to send a verification code to the account-associated number through the operator, but directly completes the account verification and jumps the corresponding login platform page on the user terminal to the login success page.

[0104] Step 304: When the account verification method is a quick login method, query the user account corresponding to the account-associated number; obtain login information according to the account verification request, and complete the account verification according to the login information.

[0105] Step 305: When the account verification method is a verification code login method, a verification code is sent to the account associated number; and the account verification is completed according to the verification code input by the user.

[0106] One usage scenario of an embodiment of the present invention is as follows: as soon as the user turns on the computer, the account verification of multiple login-able platforms required for login is immediately completed. For this scenario, using the cross-platform fast account verification method of the embodiment of the present invention, for each login-able platform, the user only needs to enter the account-associated number and click the Send Verification Code button. Specifically, only when performing account verification on the first login-able platform, it is necessary to receive and enter the SMS verification code once, and click the Login button; for subsequent account verifications on the login-able platform, it is only necessary to enter the account-associated number and click the Send Verification Code button, and then the proxy server can be used to jump to the account verification success page on all subsequent login-able platforms.

[0107] The present invention obtains the account verification request sent by the user terminal at the first sending time through the proxy server. When the device identifier of the corresponding user terminal is not stored in the proxy server, the account verification mode of the user account corresponding to the account association number is set to the verification code login mode; when the device identifier is stored in the proxy server, and when the difference between the first sending time and the second sending time of the historical verification request corresponding to the device identifier is less than or equal to the first preset time, the account verification mode is set to the quick login mode; according to the corresponding account verification mode, the account verification of the user account is completed. The present invention solves the problems of high platform charges and overly complicated account verification operations on the user side and the server side by realizing quick account verification of multi-platform association; it realizes that only one account verification operation needs to be performed on one of the platforms in the platform pool in the form of a text message verification code, and the account verification of all platforms in the platform pool can be directly completed through the same user terminal.

[0108] To further illustrate the use scenario of the embodiment of the present invention, Figure 8 As shown, before step 301, the following steps are specifically included:

[0109] Step 3011: Enter the login page of the login platform.

[0110] Step 3012: After receiving a click event corresponding to the send verification code button, obtain the account associated number entered by the user in the login page.

[0111] The login page includes Fig. 9 In the user interface shown, the user enters the account-associated number into the control marked "Please enter your mobile phone number" and clicks the "Send verification code" button. After the front end of the login platform receives the click event corresponding to the send verification code button, it obtains the account-associated number entered by the user.

[0112] Step 3013: Obtain the device identifier; generate an account verification request for the login platform based on the device identifier and the account associated number.

[0113] When generating an account verification request, the device identifier is obtained based on the network information. In an optional embodiment, the device identifier may be a Media Access Control Address (MAC address).

[0114] Step 3014: Send the account verification request to the log-in platform; the log-in platform forwards the account verification request to the proxy server.

[0115] like Fig.10 As shown, in an optional embodiment, the user terminal includes a smart phone, a personal computer (PC) and a laptop computer; the quick login method includes the following three main steps: (1) the user fills in the account association number on the login page of the login platform; (2) the user terminal (for example, Fig.10 The PC and laptop shown in FIG. 1 ) generates a verification request corresponding to the log-in platform according to the account associated number and the login page (for example, Fig.10 ), and sends it to the proxy server; (3) the proxy server directly completes the account verification based on the received verification request, and returns the user account login success page on the login platform to the corresponding user terminal.

[0116] like Fig.10 As shown, in an optional embodiment, the verification code login method includes the following six main steps: (1) the user fills in the account associated number on the login page of the login platform; (2) the user terminal (for example, Fig.10 The smart phone shown in FIG. 1 generates a verification request (for example, Fig.10 ) and sends it to the proxy server; (3) the proxy server generates a verification code for the login platform based on the received verification request, and sends the verification code to the account-associated number through the operator; (4) the user receives a text message containing the verification code and enters the verification code into the login page; (5) the user terminal obtains the verification code from the login page and sends it to the proxy server; (6) the proxy server matches the received verification code with the verification code it generates. If the match is successful, the account verification is completed and the login success page of the user account on the login platform is returned to the corresponding user terminal.

[0117] In the embodiment of the present invention, since there is no need to send a verification code when using the quick login method, the fee for sending the verification code, the computing resources for generating the verification code and matching the verification code are saved. At the same time, on the user side, the user does not need to fill in the verification code multiple times; and when the user accidentally fills in the wrong verification code, the server side needs to increase the computing resource overhead of the verification code matching process at least once. This improves the work efficiency on both the server side and the user side.

[0118] Traditional account verification methods lack flexibility and are usually designed for a single platform, making it difficult to integrate account verification on multiple platforms. The embodiments of the present invention bind the login status of the user account according to the verification request, combine the quick login method and the verification code login method, apply for and allocate the account verification authority of the corresponding platform in the platform pool for the user account, and save time and operations on the user side and the server side, as well as the resources on the server side corresponding to the platform. To further illustrate the quick login method and the verification code login method of the embodiments of the present invention, specifically, Fig.11 As shown, in the step 304, the login information is obtained according to the account verification request, and the account verification is completed according to the login information, which specifically includes:

[0119] Step 3041: The proxy server obtains login information of at least one loginable platform required for the user account to log in according to the account verification request.

[0120] For example, Fig.10 As shown, the user fills in the account association number on the client of the platform that can be logged in on the smartphone, PC and laptop, and clicks the send verification code button. The smartphone, PC and laptop generate corresponding account verification requests respectively and send them to the proxy server. The proxy server receives the account verification requests from the smartphone, PC and laptop. Since the proxy server pre-maintains the user names and passwords corresponding to all user accounts that can log in to the platform in the platform pool, the login information corresponding to the smartphone, PC and laptop is directly obtained according to the corresponding account verification request. Among them, the login information includes the user name, password and security authentication information of the user account on the corresponding platform that can be logged in.

[0121] Step 3042: Send the login information to the corresponding login platform.

[0122] In the quick login method of the embodiment of the present invention, since the user terminal remains unchanged, the proxy server directly determines that the login is safe and generates corresponding security authentication information. Since the internal login logic record still needs to be added inside the login platform, the proxy server needs to send the login information to the corresponding server of the login platform to complete the account verification in the server of the login platform.

[0123] Step 3043: The login platform receives the login information, completes the internal login logic according to the login information, and returns a jump response to the proxy server to complete the account verification according to the jump response.

[0124] like Fig.12 As shown, among the N platforms in the platform pool, when the proxy server receives account verification requests for the first platform, the second platform to the Nth platform, the proxy server obtains corresponding login information and executes the internal login logic of the corresponding platform according to the login information request; the first platform server, the second platform server to the Nth platform server respectively execute their own internal login logic.

[0125] To further illustrate the internal login logic of the login platform, such as Fig.13 As shown, in step 3043, the log-in platform receives the login information and completes the internal login logic according to the login information, specifically including:

[0126] Step 30431a: Use the user name and the corresponding password to complete the first security verification of the log-in platform; wherein the login information includes the user name, password and security authentication information of the user account on the corresponding log-in platform.

[0127] Step 30432a: Use the security authentication information to complete the second security verification of the login platform.

[0128] Step 30433a: When the first security authentication and the second security authentication are completed, the user account is set to a logged-in state.

[0129] Step 30434a: Generate a URL for a successful login page of the user account on the login-able platform based on the login status; and generate a jump response carrying the URL for the successful login page.

[0130] like Fig.12 As shown, after the first platform server, the second platform server to the Nth platform server have respectively executed their own internal login logic, they return to the proxy server the Uniform Resource Locator (URL) of the login success page to which the corresponding platform will jump after the login is successful; the proxy server forwards the corresponding login success page URL to the smart phone.

[0131] like Fig.14 As shown, in step 3043, returning a jump response to the proxy server to complete the account verification according to the jump response specifically includes:

[0132] Step 30431b: Return a jump response to the proxy server, where the jump response carries the URL of the corresponding login success page of the login platform.

[0133] Step 30432b: The proxy server forwards the jump response to the user terminal.

[0134] Step 30433b: The client that can log into the platform jumps to the successful login page corresponding to the user account according to the successful login page URL to complete the account verification.

[0135] like Fig.12 As shown, the clients of the first platform, the second platform to the Nth platform running on the smart phone respectively jump to the login success page of the corresponding platform according to the login success page URL.

[0136] To illustrate the first time account verification, Fig.15 As shown, the step 305 specifically includes:

[0137] Step 3051: The proxy server generates a verification code corresponding to the user account, and sends the verification code corresponding to the user account to the account-associated number through the operator.

[0138] Step 3052: the user terminal obtains the verification code input by the user; generates a verification code matching request according to the verification code input by the user and the account associated number; and sends the verification code matching request to the proxy server.

[0139] Step 3053: The proxy server obtains the verification code input by the user according to the verification code matching request; when the verification code input by the user matches the verification code corresponding to the user account, the proxy server obtains login information according to the account verification request, and completes the account verification according to the login information.

[0140] Embodiment 3:

[0141] Based on Example 2, this embodiment of the present invention provides a preferred solution for a cross-platform fast account verification method. Specifically, Fig.16 As shown, after completing the account verification of the user account according to the corresponding account verification method in step 30, it also includes:

[0142] In step 401, starting from one of the log-in platforms after completing the account verification, the non-communication time between the client of the log-in platform and the proxy server corresponding to the log-in platform is recorded; wherein the client runs on the user terminal.

[0143] The non-communication time of a log-in platform is the time interval during which no communication is performed between the log-in platform and the proxy server.

[0144] In step 402, when the difference between the non-communication time and the connection time threshold is less than a second preset time, and the user account is in a logged-in state, the client sends a heartbeat message to the proxy server, and the heartbeat message carries a corresponding device identifier.

[0145] The second preset time and the connection time threshold are selected by those skilled in the art according to specific usage scenarios and are not limited here; in an optional embodiment, the connection time threshold may be two days, and the second preset time may be 0. Each heartbeat message carries a device identifier of the user terminal that sends the heartbeat message.

[0146] The heartbeat message is used to monitor the operating status of the machine network storage; the heartbeat request message is sent by the client to the server, and the heartbeat response message is the server's response to the client; the role of the heartbeat message is to maintain the connection between the client and the server.

[0147] Within the connection time threshold after establishing a connection with the server, the client needs to send data to the proxy server for communication, otherwise the proxy server will automatically disconnect. If the client does not send data within this connection time, but does not want to lose the connection with the proxy server, it must send a heartbeat request message.

[0148] In step 403, the account verification method of the user account is set according to the first preset time corresponding to the logon platform and the heartbeat message in the proxy server corresponding to the logon platform, so as to complete the account verification according to the corresponding account verification method.

[0149] A usage scenario of the embodiment of the present invention is as follows: when a user turns on a computer, only some of the required login accounts of multiple login platforms are verified. However, after a first preset time, the user needs to verify the accounts of other login platforms.

[0150] For this scenario, the cross-platform fast account verification method of this embodiment combines the heartbeat message to determine whether there is a platform that can be logged in and the user account is still logged in; if so, the user only needs to enter the account associated number and click the send verification code button to jump to the account verification success page on all subsequent platforms that can be logged in through the proxy server. Specifically, the step 403 specifically includes:

[0151] In step 4031, when the difference between the first sending time and the second sending time is greater than the first preset time, it is determined whether there is a heartbeat message carrying the device identifier.

[0152] Among them, the first platform has established a connection, and the corresponding proxy server will maintain this heartbeat message.

[0153] In step 4032, if there is a heartbeat message carrying the device identifier, the account verification method is set to a quick login method.

[0154] As long as it is determined that there is a heartbeat message for the user account for any of the platforms in the platform pool, that is, there is a user device that is logged in to any of the platforms, the same user device can be used to log in to other platforms in a quick login manner after the first preset time has expired.

[0155] In step 4033, if there is no heartbeat message carrying the device identifier, the account verification mode is set to the verification code login mode.

[0156] When the first preset time is exceeded and there is no corresponding heartbeat message, the login status of the user account in all the platforms that can be logged in in the platform pool is all logged in, and the first login cross-platform fast account verification method (verification code login method) is used to log in.

[0157] like Fig.17 As shown, the embodiment of the present invention designs a set of cross-platform fast account verification processes for multiple platforms; wherein, the execution subjects of the processes shown in the dotted box are all proxy servers. Users only need to perform account verification once by using the verification code login method, and then they can log in with one click through the quick login method, and seamlessly access multiple login platforms, avoiding the tedious process of repeatedly entering usernames and passwords, greatly improving the user experience, and simplifying the account verification process. And by reducing the number of account verifications by using the verification code login method, the SMS charges for sending SMS verification codes are greatly reduced.

[0158] Embodiment 4:

[0159] like Fig.18 , which is a schematic diagram of the architecture of a cross-platform fast account verification device according to an embodiment of the present invention. The cross-platform fast account verification device according to this embodiment includes one or more processors 21 and a memory 22. Fig.18 A processor 21 is taken as an example.

[0160] The processor 21 and the memory 22 may be connected via a bus or other means. Fig.18 The example of connecting through bus is taken in the following.

[0161] The memory 22 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs and non-volatile computer executable programs, such as the cross-platform fast account verification method in Example 1. The processor 21 executes the cross-platform fast account verification method by running the non-volatile software programs and instructions stored in the memory 22.

[0162] The memory 22 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some embodiments, the memory 22 may optionally include a memory remotely arranged relative to the processor 21, and these remote memories may be connected to the processor 21 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.

[0163] The program instructions / modules are stored in the memory 22, and when executed by the one or more processors 21, the cross-platform fast account verification method in the above embodiment 1 is executed, for example, the above described Figure 1 , Figure 7-Figure 8 , Fig.11 , Figure 13-Figure 16 The steps shown.

[0164] It is worth noting that the information interaction, execution process, etc. between the modules and units within the above-mentioned devices and systems are based on the same concept as the processing method embodiment of the present invention. The specific contents can be found in the description of the method embodiment of the present invention and will not be repeated here.

[0165] A person skilled in the art may understand that all or part of the steps in the various methods of the embodiments may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

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

Claims

1. A cross-platform rapid account verification method, characterized in that: The third-party platforms that join the corresponding platform pool are determined by signing contracts, and the third-party platforms that have joined the platform pool are used as log-in platforms in the platform pool. A platform pool includes at least one log-in platform, and a platform pool corresponds to a proxy server. The cross-platform fast account verification method includes: Establishing an account verification relationship between the proxy server corresponding to the platform pool and each log-in platform in the platform pool; After the login platform receives the account verification request, the login platform determines the corresponding proxy server according to the account verification relationship, and transmits the account verification request to the proxy server; Determine an account verification method for processing the account verification request based on the account verification request and a user terminal that has been used for account verification for the same user account; and complete the account verification of the user account based on the corresponding account verification method; Among them, pre-maintaining a set of terminal identifiers that have been used to log in to any one of the platforms that can be logged in in the platform pool, determining an account verification method for processing the account verification request based on the account verification request and the user terminal that has been used for account verification with the same user account; completing the account verification of the user account according to the corresponding account verification method, specifically includes: Obtaining an account verification request sent by the user terminal at the first sending time, the account verification request including an account associated number and a device identifier of the user terminal, the account verification request being used to log into one of the logable platforms in the platform pool; If the device identifier does not exist in the terminal identifier set, or the device identifier is not used for account verification of the user account corresponding to the account-associated number, storing the device identifier in the terminal identifier set, and setting the account verification mode of the user account to the verification code login mode; If the device identifier exists in the terminal identifier set, when the difference between the first sending time and the second sending time of the historical verification request corresponding to the device identifier is less than or equal to a first preset time, setting the account verification mode to a quick login mode; wherein the historical verification request has been used to log in to one of the log-inable platforms in the platform pool; When the account verification method is a quick login method, querying the user account corresponding to the account-associated number; obtaining login information according to the account verification request, and completing the account verification according to the login information; When the account verification method is a verification code login method, sending a verification code to the account associated number; completing the account verification according to the verification code entered by the user; After completing the account verification of the user account according to the corresponding account verification method, the method further includes: Starting from the completion of account verification on one of the log-in platforms, recording the non-communication time between the client of the log-in platform and the proxy server corresponding to the log-in platform; wherein the client is running on the user terminal; When the difference between the non-communication time and the connection time threshold is less than a second preset time, and the user account is in a logged-in state, the client sends a heartbeat message to the proxy server, where the heartbeat message carries a corresponding device identifier; When the difference between the first sending time and the second sending time is greater than a first preset time, determining whether there is a heartbeat message carrying the device identifier; If there is a heartbeat message carrying the device identifier, setting the account verification mode to a quick login mode; If there is no heartbeat message carrying the device identifier, the account verification mode is set to a verification code login mode, so as to complete the account verification according to the corresponding account verification mode.

2. The cross-platform rapid account verification method according to claim 1, characterized in that: The obtaining login information according to the account verification request and completing the account verification according to the login information specifically includes: The proxy server obtains the login information of at least one loginable platform required for the user account to log in according to the account verification request; Sending the login information to the corresponding login platform; The log-inable platform receives the login information, completes internal login logic according to the login information, and returns a jump response to the proxy server to complete account verification according to the jump response.

3. The cross-platform rapid account verification method according to claim 2, characterized in that: The login platform receives the login information and completes internal login logic according to the login information, specifically including: Use the user name and the corresponding password to complete the first security verification of the log-in platform; wherein the login information includes the user name, password and security authentication information of the user account in the corresponding log-in platform; Using the security authentication information, completing the second security verification of the log-in platform; When both the first security authentication and the second security authentication are completed, setting the user account to a logged-in state; Generate a URL of a successful login page of the user account on the login-able platform according to the login status; and generate a jump response carrying the URL of the successful login page.

4. The cross-platform rapid account verification method according to claim 2, characterized in that: The step of returning a redirect response to the proxy server to complete the account verification according to the redirect response specifically includes: Returning a redirect response to the proxy server, wherein the redirect response carries the URL of the login success page of the corresponding login platform; The proxy server forwards the jump response to the user terminal; The client that can log in to the platform jumps to the login success page corresponding to the user account according to the login success page URL to complete the account verification.

5. The cross-platform rapid account verification method according to claim 1, characterized in that: When the account verification method is a verification code login method, sending a verification code to the account associated number; completing the account verification according to the verification code input by the user, specifically includes: The proxy server generates a verification code corresponding to the user account, and sends the verification code corresponding to the user account to the account-associated number through the operator; The user terminal obtains a verification code input by a user; generates a verification code matching request according to the verification code input by the user and the account associated number; and sends the verification code matching request to the proxy server; The proxy server obtains the verification code input by the user according to the verification code matching request; when the verification code input by the user matches the verification code corresponding to the user account, the proxy server obtains login information according to the account verification request, and completes the account verification according to the login information.

6. The cross-platform rapid account verification method according to claim 1, characterized in that: Before obtaining the account verification request sent by the user terminal at the first sending time, the method specifically includes: Go to the login page of the platform; After receiving a click event corresponding to the send verification code button, obtain the account associated number entered by the user on the login page; Obtaining the device identifier; generating an account verification request for the log-in platform according to the device identifier and the account associated number; The account verification request is sent to the log-in platform; the log-in platform forwards the account verification request to a proxy server.

7. A cross-platform rapid account verification device, characterized in that: It includes at least one processor and a memory, the at least one processor and the memory are connected via a data bus, the memory stores instructions that can be executed by the at least one processor, and the instructions, after being executed by the processor, are used to implement the cross-platform fast account verification method described in any one of claims 1-6.