CN113452719A - Application login method and device, terminal equipment and storage medium - Google Patents

Application login method and device, terminal equipment and storage medium Download PDF

Info

Publication number
CN113452719A
CN113452719A CN202110792035.3A CN202110792035A CN113452719A CN 113452719 A CN113452719 A CN 113452719A CN 202110792035 A CN202110792035 A CN 202110792035A CN 113452719 A CN113452719 A CN 113452719A
Authority
CN
China
Prior art keywords
login
information
verification
party
equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110792035.3A
Other languages
Chinese (zh)
Other versions
CN113452719B (en
Inventor
叶力
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Priority to CN202110792035.3A priority Critical patent/CN113452719B/en
Publication of CN113452719A publication Critical patent/CN113452719A/en
Application granted granted Critical
Publication of CN113452719B publication Critical patent/CN113452719B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN

Abstract

The invention discloses an application login method, an application login device, terminal equipment and a storage medium, wherein the application login method comprises the following steps executed by a server side: receiving login verification information sent by a client; if the login verification information is account number encryption character string information, performing account login verification on the account number encryption character string; if the login verification information is equipment information, performing equipment login verification on the equipment information, wherein the equipment information comprises equipment identification information and equipment login environment information; if the login verification information is third-party login information, the third-party login information is sent to a third-party server, and third-party login verification between the third-party server and the third-party server is completed; and if the account login verification passes or the equipment login verification passes or the third party login verification is confirmed to be successful, sending a jump instruction of successful login verification to the client. The technical scheme of the invention improves the efficiency, the intelligent level and the flexibility of application login.

Description

Application login method and device, terminal equipment and storage medium
Technical Field
The invention relates to the technical field of finance, in particular to an application login method, an application login device, terminal equipment and a storage medium.
Background
In the financial insurance industry, when different business systems need to be accessed, all the business systems can be logged in by using one universal account, and a single account corresponding to each different business system can also be used for logging in.
Disclosure of Invention
The embodiment of the invention provides a login method, a login device, terminal equipment and a storage medium, and aims to solve the problems of low flexibility and low login efficiency of a login mode.
In a first aspect, an embodiment of the present invention provides an application login method, including the following steps executed by a server:
if the starting operation of the user on the target application is detected, judging whether a login data record table corresponding to the target application is empty;
if the login data record table is empty, jumping to a login interface of the target application, and starting a first login process;
if the login data record table is not empty, analyzing the historical login mode of the user according to the historical login information stored in the login data record table, and determining the preferred login mode;
according to the preferred login mode, login authentication information is sent to the server side, so that the server side can perform login authentication according to the login authentication information;
and if a jump instruction which is sent by the server and successfully verified in login is received, jumping to an application interface of the target application.
In a second aspect, an embodiment of the present invention provides an application login method, including the following steps performed by a client:
receiving login verification information sent by a client, wherein the login verification information comprises one of account number encryption character string information, equipment information and third party login information;
if the login verification information is account number encryption character string information, performing account login verification on the account number encryption character string;
if the login authentication information is equipment information, performing equipment login authentication on the equipment information;
if the login verification information is third-party login information, the third-party login information is sent to a third-party server, and third-party login verification between the third-party server and the third-party server is completed;
and if the account login verification passes or the equipment login verification passes or the third party login verification between the third party server and the client is confirmed to be completed, sending a jump instruction of successful login verification to the client.
In a third aspect, an embodiment of the present invention provides an application login apparatus, including a client, where the client includes:
the judging module is used for judging whether a login data record table corresponding to the target application is empty or not if the starting operation of the user on the target application is detected;
the starting module is used for jumping to a login interface of the target application and starting a first login process if the login data record table is empty;
the analysis module is used for analyzing the historical login mode of the user according to the historical login information stored in the login data record table if the login data record table is not empty, and determining the preferred login mode;
the first sending module is used for sending login verification information to the server according to the preferred login mode so that the server performs login verification according to the login verification information;
and the skipping module is used for skipping to the application interface of the target application if a skipping instruction which is sent by the server and succeeds in login verification is received.
In a fourth aspect, an embodiment of the present invention provides an application login apparatus, including a server, where the server includes:
the system comprises an accepting module, a judging module and a judging module, wherein the accepting module is used for receiving login verification information sent by a client, and the login verification information comprises one of account number encryption character string information, equipment information and third party login information;
the first verification module is used for performing account login verification on the account number encryption character string if the login verification information is the account number encryption character string information;
the second verification module is used for performing equipment login verification on the equipment information if the login verification information is the equipment information;
the third verification module is used for sending the third party login information to a third party server to complete third party login verification between the third party server and the third party server if the login verification information is the third party login information;
and the second sending module is used for sending a jump instruction of successful login verification to the client if the account login verification passes or the equipment login verification passes or the third party login verification is confirmed to be successful.
In a fifth aspect, an embodiment of the present invention provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the application login method when executing the computer program.
In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps of the application login method are implemented.
According to the login method, the login device, the terminal device and the storage medium provided by the embodiment of the invention, on one hand, if the client detects the starting operation of the user on the target application, whether the login data record table corresponding to the target application is empty is judged, if the login data record table is empty, the login interface of the target application is jumped to, the first login process is started, if the login data record table is not empty, the historical login mode of the user is analyzed according to the historical login information stored in the login data record table to determine the preferred login mode, and then the login verification information is sent to the server according to the preferred login mode, so that the server performs login verification according to the login verification information. When a single legal user switches between a plurality of different applications, the switched applications can be automatically logged in according to the preferred login mode of the legal user, so that the complicated switching login process of the user is avoided, and the login efficiency and the intelligent level are effectively improved; on the other hand, the server receives login verification information sent by the client, if the login verification information is account number encryption character string information, account login verification is conducted on the account number encryption character string, if the login verification information is equipment information, equipment login verification is conducted on the equipment information, if the login verification information is third party login information, the third party login information is sent to a third party server, third party login verification between the third party server and the third party server is completed, finally, if the account login verification is passed or the equipment login verification is passed, or third party login verification between the third party server and the third party server is confirmed to be completed, a jump instruction with successful login verification is sent to the client, and if the client receives the jump instruction with successful login verification sent by the server, the jump is carried out to an application interface of a target application. The server side adopts different login verification processes for different login modes, login safety is effectively guaranteed, meanwhile, when the client side logs in an account password mode, information is interacted between the client side and the server side in an account encryption character string mode, and application login safety is further effectively improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
Fig. 1 is a schematic network structure diagram of an application login system in an application login method provided in embodiment 1 of the present invention;
fig. 2 is a flowchart of an implementation of an application login method provided in embodiment 1 of the present invention;
fig. 3 is a flowchart illustrating an implementation of a first login process initiated by a client in the application login method according to embodiment 1 of the present invention;
fig. 4 is a flowchart illustrating an implementation of determining, by a client, a preferred login manner in the application login method provided in embodiment 1 of the present invention;
fig. 5 is a flowchart illustrating an implementation of receiving and verifying first login request information by a server in the application login method according to embodiment 1 of the present invention;
fig. 6 is a flowchart illustrating an implementation of device login verification performed by a server in the application login method according to embodiment 1 of the present invention;
fig. 7 is a schematic diagram of an application login apparatus provided in embodiment 2 of the present invention;
fig. 8 is a schematic diagram of a terminal device provided in embodiment 4 of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
The application login method provided by the embodiment of the invention is applied to the financial industry. As shown in fig. 1, fig. 1 is a schematic diagram of a network structure of an application login system, where the application login system includes a client, a server, and a third-party server. The client refers to an intelligent device terminal, the intelligent device terminal can be a smart phone or an intelligent tablet computer, the server can be a cloud computing service center or a server cluster, and specific contents of the intelligent device terminal and the server can be set according to requirements of actual application, which is not limited here.
It should be noted that a plurality of clients may exist simultaneously, and the clients and the server, as well as the server and the third-party server, are connected through a network propagation medium, which may be a wired cable or a wireless electromagnetic wave.
The application login method in the embodiment of the invention specifically comprises the following steps executed by the client:
if the starting operation of the user on the target application is detected, judging whether a login data record table corresponding to the target application is empty;
if the login data record table is empty, jumping to a login interface of the target application, and starting a first login process;
if the login data record table is not empty, analyzing the historical login mode of the user according to the historical login information stored in the login data record table, and determining the preferred login mode;
according to the preferred login mode, login authentication information is sent to the server side, so that the server side can perform login authentication according to the login authentication information;
and if a jump instruction which is sent by the server and successfully verified in login is received, jumping to an application interface of the target application.
The application login method in the embodiment of the invention specifically comprises the following steps executed by the client:
receiving login verification information sent by a client, wherein the login verification information comprises one of account number encryption character string information, equipment information and third party login information;
if the login verification information is account number encryption character string information, performing account login verification on the account number encryption character string;
if the login authentication information is equipment information, performing equipment login authentication on the equipment information;
if the login verification information is third-party login information, the third-party login information is sent to a third-party server, and third-party login verification between the third-party server and the third-party server is completed;
and if the account login verification is passed or the equipment login verification is passed or the third party login verification between the client and the third party server is confirmed to be completed, sending a jump instruction of successful login verification to the client.
Referring to fig. 2, fig. 2 shows an implementation flow of the application login method provided in this embodiment. The details are as follows:
s1: and if the client detects the starting operation of the user on the target application, judging whether a login data record table corresponding to the target application is empty.
In the embodiment of the present invention, the target Application refers to an Application (APP), a business system, or the like, and may specifically exist in an Application platform of a terminal device such as an intelligent terminal or a computer. The starting operation of the user on the target application may specifically be a click operation of the user on the APP or the service system directly, an access operation of the user on the APP or the service system through a link or a website, and the like, and may also be other operations for starting the target application, which is not limited specifically.
The log data record table is used for recording historical log information, and the log data record table is stored in the record table database.
Specifically, if the client detects that the user starts the selected target application program, the client extracts the login data record table from the record table database, then checks whether the login data record table corresponding to the target application program has historical login information, and if not, the login data record table is considered to be empty; if so, the log data record is considered to be non-empty.
It should be noted that there are one or more application programs, one or more login data record tables, and the application programs and the login data record tables correspond to each other one to one.
S2: and if the login data record table is empty, the client jumps to a login interface of the target application, and starts a first login process.
In the embodiment of the invention, the login interface is an interactive interface for filling in login information by a user.
Specifically, if the login data record table corresponding to the target application program is empty, the client directly jumps to the interactive interface where the user corresponding to the target application program fills in the login information, and simultaneously starts the first login process.
S3: and if the login data record table is not empty, the client analyzes the historical login mode of the user according to the historical login information stored in the login data record table to determine the preferred login mode.
In the embodiment of the present invention, the historical login information refers to the historical login information that has been successfully logged in, and the historical login information includes historical login manner and historical login data, where the historical login data includes historical login time, historical login times, and the like, the historical login manner refers to the historical login manner that has been successfully logged in, the historical login time refers to the historical login time that has been successfully logged in, and the historical login times refers to the historical login times that have been successfully logged in.
The account login refers to login by using an account and a password, the account login may specifically be full-function account login, such as one-account login, and the third-party login refers to authorized login by using a third-party application program, the third-party login may be WeChat or microblog login, and specific contents of the account login and the third-party login may be set according to requirements of actual applications, which is not limited herein. Device login refers to login based on mobile device information. The preferred login means is a preferred login means of the user.
The log data record table corresponding to each application includes historical log information of a legitimate user who has successfully logged in the application, the historical log information records a historical log manner, a historical log time, and a historical log frequency, and corresponding historical log data is stored for each historical log manner.
Specifically, if the log-in data record table in the record table database is not empty, the client performs intelligent analysis on the historical log-in mode of the user according to the historical log-in information in the log-in data record table, and determines the preferred log-in mode of the user.
In the embodiment of the invention, when the client intelligently analyzes the historical login mode of the user according to the historical login information in the login data record table, the client defaults to acquire the historical login information of the legal user which successfully logs in the last time from the login data record table, defaults the historical login information of the legal user as the historical login information of the current user, and determines the preferred login mode of the current user by analyzing the historical login mode of the legal user recorded in the historical login information.
It should be noted that the technical solution of the present invention is directed to an application login scenario of a single legal user, that is, a login of a same legal user to a plurality of different applications. For example, a financial insurance system usually includes a plurality of different business application subsystems, a user can apply for an independent single account to log in at each business application subsystem, and simultaneously the user can also apply for a full-function account of the financial insurance system to log in all the business application subsystems, assuming that a legal insurance user is used to log in by using a full-function account, when the legal insurance user logs in to one application subsystem by using the single account at a certain time and needs to switch to another application subsystem, a client analyzes a historical login mode of the legal insurance user, judges that a preferred login mode of the legal insurance user is the full-function account login, and directly logs in to another application subsystem by using the full-function account, so that the legal insurance user does not need to switch to a full-function account login interface first and then uses the account to log in a complicated process, therefore, the login efficiency and the intelligent level can be effectively improved.
S4: and the client sends login authentication information to the server according to the preferred login mode so that the server performs login authentication according to the login authentication information.
Specifically, the client sends login authentication information corresponding to the preferred login mode of the user to the server according to the preferred login mode of the user, so that the server performs login authentication according to the login authentication information.
S5: the server receives login authentication information sent by the client, wherein the login authentication information comprises one of account number encryption character string information, equipment information and third party login information.
In the embodiment of the present invention, the account encryption string information refers to the encrypted string information of the account information. The device information includes device identification information and device login environment information. The device identification information may be a mobile phone number and a mobile phone serial number, and specific content of the device identification information may be set according to requirements of practical application, which is not limited herein. The device login environment information refers to a network environment in which the device is located in a login process, and includes a login network protocol, login time, a login place, an operating system of the login device, and the like. The third party login information refers to login information of a third party application program, and the third party login information comprises third party user identity identification information and third party application program identity identification information. The third party user identification information uniquely identifies the third party user, and the third party application program identification information uniquely identifies the third party application program.
Specifically, the server receives login authentication information corresponding to a preferred login mode of a user, which is sent by the client in real time, wherein the login authentication information includes one of account encryption string information, equipment identification information and equipment login environment information after account information is encrypted, or a combination of third-party user identification information and third-party application program identification information. If the login verification information is the encrypted character string information of the account after the account information is encrypted, the server confirms that account login verification needs to be executed, and the process goes to step S6 to continue execution; if the login verification information is the combination of the equipment identification information and the equipment login environment information, the server side confirms that equipment login verification needs to be executed, and the process goes to step S7 to continue execution; if the login verification information is the combination of the third-party user identity identification information and the third-party application identity identification information, the server side confirms that third-party login verification needs to be executed, and the process goes to step S8 to continue execution.
S6: and if the login verification information is account number encryption character string information, the server performs account login verification on the account number encryption character string.
Specifically, if the login verification information is account number encryption character string information, the server decrypts the account number encryption character string information according to a preset decryption mode to obtain an account password, then queries whether the decrypted account password exists in a registration database, and if so, the account login verification is passed; if not, the account login verification is not passed.
S7: and if the login authentication information is the equipment information, the server performs equipment login authentication on the equipment information.
Specifically, if the login authentication information is the device identification information and the device login environment information, the server performs device login authentication on the device identification information and the device login environment information.
The device login verification is used for verifying whether the device which is logging in is the same as the device which has logged in successfully last time.
S8: and if the login verification information is third-party login information, the server side sends the third-party login information to the third-party server to complete third-party login verification between the server side and the third-party server.
In the embodiment of the present invention, the third-party server refers to a server of a third-party application. Specifically, if the login verification information is third-party user identity identification information and third-party application identity identification information, the server side stores the third-party user identity identification information and the third-party application identity identification information into a third-party login database.
Sending the third-party user identity identification information to a server of a third-party application program for verification, after the third-party user identity identification information passes the verification of the server of the third-party application program, inquiring whether the target third-party application program identity identification information sent by the server of the third-party application program exists in a third-party login database, and if so, determining that the third-party login verification between the third-party application program and a third-party server is finished; if the third-party login authentication does not exist, the authentication of the third-party login between the third-party server and the user is considered to be incomplete, and the user needs to log in by using an account or equipment.
It should be noted that the third-party user identification information may be a third-party user OpenID, the third-party application program identification information may be a Process ID (PID), and specific contents of the third-party user identification information and the third-party application program identification information may be set according to requirements of actual applications, which is not limited herein.
The OpenID is a digital identity recognition framework with a user as a center, and is used as an identity authentication identifier of the user. The PID is an identification information that uniquely identifies the process.
S9: and if the account login verification passes or the equipment login verification passes or the third-party login verification between the server and the third-party server is confirmed to be completed, the server sends a jump instruction of successful login verification to the client.
Specifically, if the server confirms that the account login verification passes or the device login verification passes according to step S8, or confirms that the third party login verification with the third party server is completed, the server sends a jump instruction that the login verification is successful to the client.
S10: and if the client receives a jump instruction which is sent by the server and successfully verified in login, jumping to an application interface of the target application.
In the embodiment of the invention, the application interface refers to an interactive interface between a user and an application program when the user successfully logs in the application program.
Specifically, if the client receives a jump instruction which is sent by the server and is successfully logged in, the client jumps to an application interface of a target application which is successfully logged in by the user.
In the embodiment corresponding to fig. 2, on one hand, if the client detects a start operation of the user on the target application, the client determines whether the login data record table corresponding to the target application is empty, if the login data record table is empty, the client jumps to the login interface of the target application to start a first login process, and if the login data record table is not empty, the client analyzes the historical login manner of the user according to the historical login information stored in the login data record table to determine a preferred login manner, and then sends login authentication information to the server according to the preferred login manner, so that the server performs login authentication according to the login authentication information. When a single legal user switches between a plurality of different applications, the switched applications can be automatically logged in according to the preferred login mode of the legal user, so that the complicated switching login process of the user is avoided, and the login efficiency and the intelligent level are effectively improved; on the other hand, the server receives login verification information sent by the client, if the login verification information is account number encryption character string information, account login verification is conducted on the account number encryption character string, if the login verification information is equipment information, equipment login verification is conducted on the equipment information, if the login verification information is third party login information, the third party login information is sent to a third party server, third party login verification between the third party server and the third party server is completed, finally, if the account login verification is passed or the equipment login verification is passed, or third party login verification between the third party server and the third party server is confirmed to be completed, a jump instruction with successful login verification is sent to the client, and if the client receives the jump instruction with successful login verification sent by the server, the jump is carried out to an application interface of a target application. The server side adopts different login verification processes for different login modes, login safety is effectively guaranteed, meanwhile, when the client side logs in an account password mode, information is interacted between the client side and the server side in an account encryption character string mode, and application login safety is further effectively improved.
Next, based on the embodiment corresponding to fig. 2, a specific implementation method for starting the first login process mentioned in step S2 is described in detail below by using a specific embodiment.
Referring to fig. 3, fig. 3 shows a specific implementation process of the client initiating the first login process, which is detailed as follows:
s21: the client detects login operation of a user, if the login operation is login account input operation, account information input by the user is acquired, and if the login operation is third-party login starting operation, third-party login information is acquired.
In the embodiment of the invention, the access token of the third-party application refers to a privilege list of a security group assigned to a login user, and is a control command for executing relevant system operation on the user. The access token of the third party application includes third party user identification information and third party application identification information.
Specifically, the client detects the login operation of a user on a target application program in real time, and if the login operation of the user on the target application program is a login account input operation, an account and a password input by the user are acquired from a filling interface of login information of the user and the target application program; and if the login operation of the user on the target application program is the starting operation of third party login, acquiring the identity identification information of the third party user and the identity identification information of the third party application program from the access token of the third party application program.
S22: the client acquires device information.
Specifically, the client acquires device identification information and device login environment information.
S23: the client sends first login request information to the server, wherein the first login request information comprises a combination of third party login information and equipment information or a combination of account information and equipment information.
Specifically, when a user logs in a target application by using a third-party account, a client sends a combination of third-party user identity identification information, third-party application program identity identification information, equipment identification information and equipment login environment information to a server; when a user logs in to a target application by using an account, the client sends a combination of an account password, equipment identification information and equipment login environment information to the server.
The client sends the device information to the server through the first login request information, so that the server can use the device information to perform device login authentication in the case of non-first login.
S24: and if the client receives the account number encryption character string information sent by the server, the account number encryption character string information is saved.
In the embodiment of the invention, if the user successfully logs in by using the account, the client receives the account encryption character string information sent by the server.
Specifically, if the client receives account encryption string information sent by the server, the account encryption string information is stored in a string database.
S25: and if the client receives a jump instruction which is sent by the server and successfully logs in, jumping to an application interface of the target application.
In the embodiment of the invention, if the user successfully logs in by using the account or the third party, the client receives a jump instruction which is sent by the server and has successful login.
Specifically, if the client receives a jump instruction which is sent by the server and has successfully logged in, the client jumps to an application interface of a target application which the user has successfully logged in.
In the embodiment corresponding to fig. 3, the client detects a login operation of a user in real time, acquires account information input by the user if the login operation is a login account input operation, acquires third party login information if the login operation is a third party login start operation, then acquires device information, sends first login request information to the server, saves the account encryption string information if the account encryption string information sent by the server is received, and jumps to an application interface of a target application if a jump instruction for successful login sent by the server is received. The account login information, the third party login information and the equipment information which are logged in for the first time are sent to the server side through the client side, after verification is successfully stored, selection of an optimal login mode can be carried out according to the stored information in the following process, and login efficiency and intelligent level of application are improved.
Based on the embodiment corresponding to fig. 2 or fig. 3, a specific implementation method for analyzing the historical login manner of the user and determining the preferred login manner according to the historical login information stored in the login data record table mentioned in step S4 and according to a specific embodiment will be described in detail below.
Referring to fig. 4, fig. 4 shows a specific implementation flow of analyzing the historical login manner of the user and determining the preferred login manner according to the historical login information stored in the login data record table by the client, which is detailed as follows:
s31: the client acquires a preset default login mode.
In the embodiment of the present invention, the preset default login manner refers to a default login manner preset by a user, and the preset default login manner may be an account login manner, an equipment login manner, or a third party login manner, and may also be another preset login manner, which is not limited herein.
It should be noted that the preset default login manner is stored in the query default login manner table.
Specifically, the client extracts a preset default login mode from the default login mode table.
S32: and if the preset default login mode is not null, the client takes the preset default login mode as the preferred login mode.
Specifically, if the default login manner extracted from the default login manner table by the client is not null, the default login manner is used as the preferred login manner.
S33: if the preset default login mode is empty, the client determines m historical login modes of the user and historical login data under each historical login mode according to the historical login information, wherein m is a positive integer.
Specifically, if the preset default login manner extracted from the default login manner table by the client according to step S31 is empty, the client determines m types of historical login manners of the user, and the historical login time and the historical login frequency in the historical login data corresponding to each historical login manner according to the historical login information in the login database. The historical login data includes historical login time, historical login times and the like.
S34: the client calculates the preferred coefficient value for each historical login style using equation (1):
Figure BDA0003161340250000111
wherein Q isaPreferred coefficient value, k, for the a-th history entry modeaA preset weight for the a-th history login mode, N is the number of preset time periods, TahA preset weight value Fa for the h time period of the a-th historical login modehThe login times of the a-th historical login mode in the h-th time stage are obtained according to the login data, MhThe sum of the registration times of the m historical registration modes in the h time stage is as follows, a belongs to [1, m]。
Specifically, the client calculates the preferred coefficient value for each historical login style using equation (1).
It should be noted that the time phases may be divided in an overlapping manner or a non-overlapping manner, the time phases divided in the overlapping manner may be a week, a month, a year, etc., the time phases divided in the non-overlapping manner may be numbers 1 to 10 or numbers 11 to 30, etc., and the dividing manner of the time phases may be set according to the actual application requirements, which is not limited herein.
For a better understanding of this step, the following is illustrated by way of an example, specifically expressed as follows:
for example, assume that m is 3, the historical login manner includes account login, device login, and third party login, N is 3, the time period includes within a week, within a month, and outside a month, Qa、QbAnd QcPreferred coefficient values, k, for account login, device login, and third party login, respectivelya、kbAnd kcPreset weights, Ta, for account login, device login, and third party login, respectivelyh、TbhAnd TchAccount login, equipment login and third party login are respectively performed in one weekInner predetermined weight value, Tbi、TbiAnd TciPreset weighting values, Ta, for account login, device login and third party login within one month respectivelyj、TbjAnd TcjPreset weighting values Fa for account login, device login and third party login, respectively, which are one month awayh、FbhAnd FchThe login times of the account login, the equipment login and the third party login within one week, Fa, respectively, are obtained according to the login datai、FbiAnd FciThe login times of the account login, the equipment login and the third party login in one month, Fa, respectively, are obtained according to the login dataj、FbjAnd FcjRespectively the login times of the account login, the equipment login and the third party login which are acquired according to the login data and are out of one month, Mh、MiAnd MjK is the sum of the registration times of three historical registration modes within one week, one month and one montha＝0.9，kb＝0.85，kc＝0.5，Tah＝Tbh＝Tch＝0.9，Tbi＝Tbi＝Tci＝0.8，Taj＝Tbj＝Tcj＝0.5，Fah＝3，Fbh＝5，Fch＝1，Fai＝8，Fbi＝7，Fci＝1，Faj＝2，Fbj＝1，Fcj＝3，Mh＝Fah+Fbh+Fch＝9，Mi＝Fai+Fbi+Fci＝16，Mj＝Faj+Fbj+FcjWhen the value is 6, Q is calculated by using the formula (1)a＝0.69，Qb＝0.78，Qc＝0.46。
S35: and the client selects a history login mode corresponding to the maximum value of the m preferred coefficient values as a preferred login mode.
Specifically, the client selects the history login manner corresponding to the maximum value from the m preferred coefficient values obtained in step S34 as the preferred login manner.
For a better understanding of this step, the following is illustrated by way of an example, specifically expressed as follows:
for example, continuing with the example in step S35, the preferred coefficient value Q for the three history registration methods obtained in step S34a＝0.69，Qb＝0.78，Qc0.46, obviously, 0.78>0.69>0.46, the client selects the device login corresponding to 0.78 as the preferred login mode.
In the embodiment corresponding to fig. 4, by obtaining a preset default login manner, if the preset default login manner is not null, the preset default login manner is used as the preferred login manner, and if the preset default login manner is null, m kinds of historical login manners of the user and login data in each historical login manner are determined according to historical login information, wherein m is a positive integer, and then, a formula is used
Figure BDA0003161340250000121
And calculating the optimal coefficient value of each historical login mode, and selecting the historical login mode corresponding to the maximum value of the m optimal coefficient values as the optimal login mode. The preferred coefficient value of each historical login mode can be calculated to accurately judge the preferred login mode of the user, so that the intellectualization level of application login is effectively improved by using the preferred login mode for login.
On the basis of the corresponding embodiment in fig. 2, before receiving the login authentication information sent by the client in step S5, the server further includes a processing procedure of receiving and verifying the first login request information.
Referring to fig. 5, fig. 5 shows a specific implementation flow of a processing procedure for receiving and verifying first login request information by a server, which is detailed as follows:
s101: the server receives first login request information sent by the client, wherein the first login request information comprises a combination of third party login information and equipment information or a combination of account information and equipment information.
Specifically, the server receives first login request information sent by the client, wherein the first login request information includes third-party user identity identification information, third-party application identity identification information, a combination of device identification information and device login environment information, or a combination of an account password, device identification information and device login environment information.
S102: if the first login request information comprises third-party login information and equipment information, the server side starts third-party verification with the third-party server according to the third-party login information, saves the equipment information when the third-party verification is confirmed to be passed, and simultaneously sends a jump instruction of successful login to the client side.
Specifically, the server analyzes the first-time login request information, and if the first-time login request information comprises a combination of third-party user identity identification information, third-party application identity identification information, equipment identity information and equipment login environment information, the current login mode is confirmed to be third-party login.
The server side stores third-party user identity identification information and third-party application identity identification information into a third-party login database, and sends the third-party user identity identification information to the server side of the third-party application program for verification, after the third-party user identity identification information passes the verification of the server side of the third-party application program, whether target third-party application program identity identification information sent by the server side of the third-party application program exists or not is inquired in the third-party login database, if the target third-party application program identity identification information exists, the third-party application program identity identification information passes the verification, meanwhile, the standby identification information and equipment login environment information are stored in the login database, and a jump instruction of successful login is sent to the client side; and if the third party information does not exist, confirming that the third party verification is not passed, and requiring the user to log in by using the account information.
S103: and if the first login request information comprises account information and equipment information, the server side verifies the account information according to the registration information in the registration database.
In the embodiment of the invention, the registration database is used for storing registration information, and the registration information comprises an account number and a password.
It should be noted that before logging in the target application program, the user needs to fill in an account and a password for registration, and then can log in by using the account and the password.
Specifically, the server analyzes the first login request information, and if the first login request information includes an account password, device identification information and device login environment information, it is determined that the current login mode is account login.
The server side inquires whether account information exists from the registration information of the registration database, and if the account information exists, the account information is considered to pass the verification; if not, the check is considered to have failed.
S104: and if the verification is passed, the server stores the account information and the equipment information in a correlation manner.
Specifically, if the verification result in step S103 is that the verification is passed, the server associates the account password, the device identification information, and the device login environment information, and stores the account password, the device identification information, and the device login environment information in the login database.
S105: and the server side combines and encrypts the account information and the random number generated at random to generate account encryption character string information.
Specifically, the server combines the account password and the random number generated randomly and encrypts the account password and the random number through an encryption method to generate corresponding account encryption character string information and store the account encryption character string information in an encryption database.
It should be noted that the random number may be a letter or a number, the encryption method may be a symmetric encryption method or an asymmetric encryption method, the symmetric encryption method may be DES or 3DES, the asymmetric encryption method may be RSA or Elgamal, and specific contents of the random number and the encryption method may be set according to practical applications, which is not limited herein.
The symmetric encryption method is an encryption method in which both the sender and the receiver use the same key to encrypt and decrypt data. The asymmetric encryption method is that both the sender and the receiver use two keys to encrypt and decrypt data, and if the public key is used to encrypt the data, the corresponding private key is used to decrypt the data; an encryption method in which data can be decrypted using a corresponding public key if the data is encrypted using a private key.
S106: and the server side sends the account number encryption character string information to the client side.
Specifically, the server extracts account encryption character string information from the encryption database and sends the account encryption character string information to the client.
S107: and the server side sends a jump instruction of successful login to the client side.
Specifically, the server sends a jump instruction with successful login to the client, so that the client jumps to the corresponding application interface when receiving the jump instruction.
In the embodiment corresponding to fig. 5, by receiving the first-time login request information sent by the client, if the first-time login request information includes the third-party login information and the device information, then, according to the third party login information, starting the third party verification with the third party server, and saving the equipment information when the third party verification is confirmed to pass, meanwhile, a jump instruction of successful login is sent to the client, if the first login request information comprises account information and equipment information, checking the account information according to the registration information in the registration database, if the check is passed, storing the account information and the equipment information in a correlation way, and then, combining and encrypting the account information and a random number generated randomly to generate account encryption character string information, sending the account encryption character string information to the client, and sending a jump instruction of successful login to the client. The account information and the equipment information are correlated to provide basic data for equipment login when subsequent preferred login mode analysis is carried out, so that the diversity of application login modes is effectively improved, and meanwhile, when the account password mode is used for login, information is interacted between the client and the server in an account encryption character string mode, so that the application login safety is further effectively improved.
Based on the embodiment corresponding to fig. 2 or fig. 5, the device information includes the device identification information and the device login environment information, and a specific implementation method for performing device login authentication on the device information if the login authentication information is the device information, which is mentioned in step S7, is described in detail below by using a specific embodiment.
Referring to fig. 6, fig. 6 shows a specific implementation flow of performing device login authentication on device information by a server if the login authentication information is the device information, which is detailed as follows:
s71: and if the login verification information is equipment identification information and equipment login environment information, the server side inquires whether the equipment identification information exists in a login database.
Specifically, if the login verification information is the device identification information and the device login environment information, the server side inquires whether the device identification information exists in the login database, if each piece of data in the device identification information is consistent with the historical device identification information of the latest successful login stored in the login database, the server side confirms that the device identification information exists, otherwise, if one piece of data in the device identification information is inconsistent with the historical device identification information of the latest successful login stored in the login database, the server side confirms that the device identification information does not exist.
For a better understanding of this step, the following is illustrated by way of an example, specifically expressed as follows:
for example, assuming that the first device identification information includes a mobile phone number and a device number, the mobile phone number is 130xxxxx525, the device number is ABC20171010, the second device identification information includes a mobile phone number and a device number, the mobile phone number is 189xxxxx020, the device number is ABC20171010, the third device identification information includes a mobile phone number and a device number, the mobile phone number is 130xxxxx525, the device number is EFG20180808, the historical device identification information of the last successful login includes a historical mobile phone number and a historical device number, the historical mobile phone number is 130xxxxx525, the historical device number is ABC20171010, the login database is Z database, the server considers that if the login verification information is 130xxxxx525 and ABC 2017180010 and the device login environment information, the 130xxxxx525 and the ABC20171010 are consistent with the 130xxxxx525 and the ABC 71010 in the Z database, otherwise, the xxx020 is inconsistent with the xxx 71010 in the Z database 130xxx, the ABC 71010 or the xxx database 130xxx, the ABC 71525 and the ABC 71010 are inconsistent with the Z database 130xxx 525 or the ABC 71010, if EFG20180808 is inconsistent with ABC20171010 in the Z database, 189xxxxx020 and ABC20171010, or 130xxxxx525 and EFG20180808 are considered to be absent.
S72: and if so, the server side confirms that the equipment identification information passes the verification.
Specifically, if the server determines that the device identification information exists in the login database according to step S71, the server confirms that the device identification information passes the verification.
If the equipment identification information does not exist in the login database, the server side confirms that the equipment identification information is not verified, and the account number login or third party login is needed.
S73: if the equipment identification information passes the verification, the server side calculates the similarity coefficient of the login environment by using a formula (2):
Figure BDA0003161340250000161
wherein, a is historical device login environment information which is saved in a login database and successfully logged in last time, B is device login environment information, f (x) is a preset weight corresponding to the device login environment x, and J (a, B) is a similarity coefficient between the historical device login environment information and the device login environment information.
In the embodiment of the invention, the historical equipment login environment information comprises a historical login network protocol, historical login time, a historical login place and an operating system of the historical login equipment.
Specifically, if the server determines that the device identification information passes the verification according to step S72, a corresponding weight is set for the device login environment information, and a similarity coefficient of the login environment is calculated using formula (2).
It should be noted that a ≡ B is a portion where the historical device login environment information of the latest successful login stored in the login database is the same as the device login environment information, and a ≡ B is the sum of the historical device login environment information of the latest successful login stored in the login database and the device login environment information. The size of the weight value represents the importance degree of the equipment login environment information, and the larger the weight value is, the more important the equipment login environment information is.
For a better understanding of this step, the following is illustrated by way of an example, specifically expressed as follows:
for example, it is assumed that the historical device login environment information of the latest successful login, which is stored in the login database, includes a historical login network protocol, historical login time, a historical login location, and an operating system of the historical login device, where the historical login network protocol is 119.136.153.184, the historical login time is 2017.10.12, the historical login location is shenzhen, and the operating system of the historical login device is android 4.0; the device login environment information comprises a login network protocol, login time, a login place and an operating system of the login device, wherein the login network protocol is 119.136.153.184, the login time is 2017.11.10, the login place is Shenzhen, and the operating system of the login device is android 4.5. If the absolute value of the difference between the historical login time and the login time is less than 30 days, the login time is considered to belong to the same login time, and if the corresponding weights preset for the login network protocol, the login time, the login place and the operating system of the login equipment are respectively 1, 1.5, 0.5 and 0.65, the similarity coefficient is calculated to be
Figure BDA0003161340250000162
S74: and if the similarity coefficient is larger than or equal to a preset similarity threshold, the server side confirms that the equipment login verification is passed.
Specifically, if the similarity coefficient obtained in step S73 is greater than or equal to the preset similarity threshold, the server confirms that the device login verification is passed.
It should be noted that the larger the similarity coefficient is, the more similar the login environment is, and when the similarity coefficient is larger than a preset similarity threshold, the current login device and the last successful login historical login device are considered to be the same device.
For a better understanding of this step, the following is illustrated by way of an example, specifically expressed as follows:
for example, continuing with the example in step S73, assuming that the preset threshold of the degree of identity is 0.7, and obviously 0.72 is greater than 0.7, the server confirms that the device login authentication is passed.
In the embodiment corresponding to fig. 6, if the login authentication information is the device identification information and the device login environment information, the server queries whether the device identification information exists in the login database, if so, it is determined that the device identification information passes the verification, if so, the similarity coefficient of the login environment is calculated by using the formula (2), and if the similarity coefficient is greater than or equal to the preset similarity threshold, it is determined that the device login authentication passes. By using the calculation method of the similarity coefficient, whether the current login equipment and the historical login equipment are the same login equipment can be accurately judged, so that the login safety of the equipment login mode is effectively improved.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Example 2
Fig. 7 shows application login apparatuses corresponding to the application login methods provided in embodiment 1 one to one, corresponding to the application login methods in embodiment 1. For convenience of explanation, only portions related to the embodiments of the present invention are shown.
Referring to fig. 7, the client of the application registration apparatus includes: a decision module 711, a start module 712, an analysis module 713, a first sending module 714, and a skip module 715. The functional modules are explained in detail as follows:
the determining module 711 is configured to determine whether a login data record table corresponding to the target application is empty if a starting operation of the user on the target application is detected;
a starting module 712, configured to jump to a login interface of the target application if the login data record table is empty, and start a first login process;
an analysis module 713, configured to, if the login data record table is not empty, analyze a historical login manner of the user according to historical login information stored in the login data record table, and determine a preferred login manner;
a first sending module 714, configured to send login authentication information to the server according to a preferred login manner, so that the server performs login authentication according to the login authentication information;
and the jump module 715 is configured to jump to an application interface of the target application if a jump instruction that the login verification is successful is received, where the jump instruction is sent by the server.
Further, the starting module 712 includes:
the detection submodule 7121 is configured to detect a login operation of a user, acquire account information input by the user if the login operation is a login account input operation, and acquire third party login information if the login operation is a third party login start operation;
a first obtaining sub-module 7122, configured to obtain device information;
the delivery submodule 7123 is configured to send first login request information to the server, where the first login request information includes a combination of third party login information and device information, or a combination of account information and device information;
the saving submodule 7124 is configured to, if account encryption string information sent by the server is received, save the account encryption string information;
and the transformation submodule 7125 is used for jumping to an application interface of the target application if a jump instruction which is sent by the server and used for successfully logging in is received.
Further, the analysis module 713 includes:
a second obtaining submodule 7131, configured to obtain a preset default login manner;
a first determining submodule 7132, configured to, if the preset default login manner is non-empty, use the preset default login manner as the preferred login manner;
a second determining submodule 7133, configured to determine, according to the historical login information, m historical login manners of the user and historical login data in each historical login manner if the preset default login manner is null, where m is a positive integer;
a first calculation sub-module 7134 for calculating a preferred coefficient value for each of said historical login manners using the following formula:
Figure BDA0003161340250000181
wherein Q isaPreferred coefficient value, k, for the a-th history entry modeaA preset weight of the a-th history login mode, N is the number of preset time stages, and TahA preset weighted value Fa of the a-th historical login mode in the h-th time stagehThe login times of the a-th historical login mode in the h-th time stage, M, are acquired according to the login datahThe sum of the registration times of m historical registration modes in the h time stage is as follows, a belongs to [1, m]；
And the third determining submodule 7135 is used for selecting a history login mode corresponding to the maximum value of the m preferred coefficient values as a preferred login mode.
Referring to fig. 7, the server of the application login device includes: a first accepting module 721, a first verifying module 722, a second verifying module 723, a third verifying module 724, and a third sending module 725. The functional modules are explained in detail as follows:
a first receiving module 721, configured to receive login authentication information sent by a client, where the login authentication information includes one of account encryption string information, device information, and third party login information;
the first verification module 722 is configured to perform account login verification on the account encryption string if the login verification information is the account encryption string information;
a second verification module 723, configured to perform device login verification on the device information if the login verification information is the device information;
a third verification module 724, configured to send the third party login information to a third party server if the login verification information is the third party login information, so as to complete third party login verification with the third party server;
a second sending module 725, configured to send a jump instruction that the login verification is successful to the client if the account login verification passes or the device login verification passes, or it is determined that the third party login verification with the third party server is completed.
Further, the server of the application login device further includes:
a second receiving module 101, configured to receive first login request information sent by a client, where the first login request information includes a combination of third party login information and device information, or a combination of account information and device information;
the first verification module 102 is configured to, if the first login request information includes third-party login information and device information, start third-party verification with the third-party server according to the third-party login information, store the device information when the third-party verification is confirmed to be passed, and send a jump instruction that the login is successful to the client;
the second checking module 103 is configured to check the account information according to the registration information in the registration database if the first login request information includes the account information and the device information;
the association module 104 is configured to, if the verification passes, associate and store the account information and the device information;
the generation module 105 is used for carrying out combination encryption on the account information and the random number generated randomly to generate account encryption character string information;
the third sending module 106 is configured to send the account encryption string information to the client;
a fourth sending module 107, configured to send a jump instruction with successful login to the client.
Further, the device information includes device identification information and device login environment information, and the second authentication module 723 includes:
the query submodule 7231 is configured to query whether the device identification information exists in the login database if the login verification information is the device identification information and the device login environment information;
a fourth determination submodule 7232, configured to determine that the device identification information is verified if the device identification information exists;
the second calculating sub-module 7233 is configured to, if the device identification information passes verification, calculate a similarity coefficient of the login environment using the following formula:
Figure BDA0003161340250000191
wherein, a is historical device login environment information which is saved in a login database and successfully logged in last time, B is device login environment information, f (x) is a preset weight corresponding to the device login environment x, and J (a, B) is a similarity coefficient between the historical device login environment information and the device login environment information;
the fifth determining sub-module 7234 is configured to determine that the device login verification is passed if the similarity coefficient is greater than or equal to the preset similarity threshold.
The process of implementing each function by each module in the application login apparatus provided in this embodiment may specifically refer to the description in embodiment 1, and is not described herein again.
Example 3
This embodiment provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the application login method in embodiment 1 is implemented, and details are not described here for avoiding repetition. Or, the computer program is executed by a processor to realize the functions of each module/unit in the application login apparatus in embodiment 2,
to avoid repetition, further description is omitted here.
It is to be understood that the computer-readable storage medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, and the like.
Example 4
Fig. 8 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 8, the terminal device 80 of this embodiment includes: a processor 81, a memory 82, and a computer program 83 stored in the memory 82 and operable on the processor 81. The processor 81 implements the steps of the application login method in embodiment 1 described above, such as steps S1 to S10 shown in fig. 2, when executing the computer program 83. Alternatively, the processor 81 executes the computer program 83 to realize the functions of the modules/units in the above-described device embodiments, such as the functions of the modules 711 to 715 of the client side and the functions of the modules 721 to 725 of the server side shown in fig. 7.
Illustratively, the computer program 83 may be divided into one or more modules/units, which are stored in the memory 82 and executed by the processor 81 to carry out the invention. One or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 83 in the terminal device 80. For example, the computer program 83 may be divided into a determining module, a starting module, an analyzing module, a first sending module, and a skipping module, and specific functions of the modules are as shown in embodiment 2, which are not repeated herein. The computer program 83 may also be divided into a receiving module, a first verifying module, a second verifying module, a third verifying module, and a second sending module, and specific functions of the modules are as shown in embodiment 2, which is not repeated herein.
The terminal device 80 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 81, a memory 82. Those skilled in the art will appreciate that fig. 8 is only an example of a terminal device 80 and does not constitute a limitation of terminal device 80 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the terminal device may also include input output devices, network access devices, buses, etc.
The Processor 81 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 82 may be an internal storage unit of the terminal device 80, such as a hard disk or a memory of the terminal device 80. The memory 82 may also be an external storage device of the terminal device 80, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the terminal device 80. Further, the memory 82 may also include both an internal storage unit of the terminal device 80 and an external storage device. The memory 82 is used for storing computer programs and other programs and data required by the terminal device. The memory 82 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.

Claims (10)

1. An application login method is characterized by comprising the following steps executed by a server side:
receiving login verification information sent by a client, wherein the login verification information comprises one of account number encryption character string information, equipment information and third party login information;
if the login verification information is the account number encryption character string information, performing account login verification on the account number encryption character string;
if the login verification information is the equipment information, performing equipment login verification on the equipment information, wherein the equipment information comprises equipment identification information and equipment login environment information;
if the login verification information is the third-party login information, the third-party login information is sent to a third-party server, and third-party login verification between the third-party server and the third-party server is completed;
and if the account login verification passes or the equipment login verification passes or the third party login verification is confirmed to be successful, sending a jump instruction of successful login verification to the client.
2. The application login method of claim 1, wherein performing device login authentication on the device information if the login authentication information is the device information comprises:
if the login verification information is the equipment identification information and the equipment login environment information, inquiring whether the equipment identification information exists in a login database;
if yes, confirming that the equipment identification information passes verification;
if the device identification information passes verification, calculating a similarity coefficient of the login environment by using the following formula:
Figure FDA0003161340240000011
wherein, a is historical device login environment information of the latest successful login stored in the login database, B is the device login environment information, f (x) is a preset weight corresponding to the device login environment information x, J (a, B) is a similarity coefficient between the historical device login environment information and the device login environment information, a ≡ B is a part of the historical device login environment information of the latest successful login stored in the login database, which is the same as the device login environment information, and a ≡ B is a sum of the historical device login environment information of the latest successful login stored in the login database and the device login environment information;
and if the similarity coefficient is larger than or equal to a preset similarity threshold, confirming that the equipment login verification is passed.
3. The application login method of claim 1, wherein before the receiving the login authentication information sent by the client, the application login method further comprises the following steps executed by the server:
receiving first login request information sent by the client, wherein the first login request information comprises a combination of the third party login information and the equipment information;
and starting third party verification with the third party server according to the third party login information, saving the equipment information when the third party verification is confirmed to be passed, and simultaneously sending a jump instruction for successful login to the client.
4. The application login method of claim 1, wherein before the receiving the login authentication information sent by the client, the application login method further comprises the following steps executed by the server:
receiving first login request information sent by the client, wherein the first login request information comprises a combination of account information and the equipment information;
checking the account information according to the registration information in the registration database;
if the verification is passed, the account information and the equipment information are stored in a correlated manner;
combining and encrypting the account information and a random number generated randomly to generate account encryption character string information;
sending the account encryption character string information to the client;
and sending a jump instruction with successful login to the client.
5. The application login method of claim 1, wherein the receiving login authentication information sent by the client comprises:
receiving login verification information which is sent by a client and determined based on a preferred login mode; the preferred login mode is a default login mode or a historical login mode corresponding to the maximum value in the m preferred coefficient values;
wherein the calculation formula of the preferred coefficient value is
Figure FDA0003161340240000021
QaPreferred coefficient value, k, for the a-th history entry modeaA preset weight for the a-th history login mode, N is the number of preset time periods, TahA preset weight value Fa for the h time period of the a-th historical login modehThe login times of the a-th historical login mode in the h-th time stage are obtained according to the login data, MhThe sum of the registration times of the m historical registration modes in the h time stage is as follows, a belongs to [1, m]。
6. An application login device is characterized in that the application login device comprises the following steps executed by a server side:
the system comprises an accepting module, a judging module and a judging module, wherein the accepting module is used for receiving login verification information sent by a client, and the login verification information comprises one of account number encryption character string information, equipment information and third party login information;
the first verification module is used for performing account login verification on the account number encryption character string if the login verification information is the account number encryption character string information;
the second verification module is used for performing equipment login verification on the equipment information if the login verification information is the equipment information, wherein the equipment information comprises equipment identification information and equipment login environment information;
the third verification module is used for sending the third party login information to a third party server to complete third party login verification between the third party server and the third party server if the login verification information is the third party login information;
and the second sending module is used for sending a jump instruction of successful login verification to the client if the account login verification passes or the equipment login verification passes or the third party login verification is confirmed to be successful.
7. The application login apparatus of claim 6, wherein the second authentication module comprises:
the query submodule is used for querying whether the equipment identification information exists in a login database if the login verification information is the equipment identification information and the equipment login environment information;
a fourth determining submodule, configured to determine that the device identification information passes verification if the device identification information exists;
a second calculating submodule, configured to calculate, if the device identification information passes verification, a similarity coefficient of the login environment using the following formula:
Figure FDA0003161340240000031
wherein, a is historical device login environment information of the latest successful login stored in the login database, B is the device login environment information, f (x) is a preset weight corresponding to the device login environment information x, J (a, B) is a similarity coefficient between the historical device login environment information and the device login environment information, a ≡ B is a part of the historical device login environment information of the latest successful login stored in the login database, which is the same as the device login environment information, and a ≡ B is a sum of the historical device login environment information of the latest successful login stored in the login database and the device login environment information;
and the fifth determining submodule is used for determining that the equipment login verification is passed if the similarity coefficient is greater than or equal to a preset similarity threshold.
8. The application login apparatus of claim 6, wherein the accepting module is configured to receive login authentication information sent by the client and determined based on the preferred login manner; the preferred login mode is a default login mode or a historical login mode corresponding to the maximum value in the m preferred coefficient values;
wherein the calculation formula of the preferred coefficient value is
Figure FDA0003161340240000032
QaPreferred coefficient value, k, for the a-th history entry modeaA preset weight for the a-th history login mode, N is the number of preset time periods, TahA preset weight value Fa for the h time period of the a-th historical login modehThe login times of the a-th historical login mode in the h-th time stage are obtained according to the login data, MhThe sum of the registration times of the m historical registration modes in the h time stage is as follows, a belongs to [1, m]。
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the steps of the application login method according to any of claims 1 to 5 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the application login method according to any one of claims 1 to 5.
CN202110792035.3A 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium Active CN113452719B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110792035.3A CN113452719B (en) 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810276499.7A CN108551443B (en) 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium
CN202110792035.3A CN113452719B (en) 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201810276499.7A Division CN108551443B (en) 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113452719A true CN113452719A (en) 2021-09-28
CN113452719B CN113452719B (en) 2022-12-30

Family

ID=63517453

Family Applications (2)

Application Number Title Priority Date Filing Date
CN201810276499.7A Active CN108551443B (en) 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium
CN202110792035.3A Active CN113452719B (en) 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN201810276499.7A Active CN108551443B (en) 2018-03-30 2018-03-30 Application login method and device, terminal equipment and storage medium

Country Status (2)

Country Link
CN (2) CN108551443B (en)
WO (1) WO2019184135A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006738A (en) * 2021-10-25 2022-02-01 上海交通大学 APP instance fingerprint and device fingerprint based hand-trip login verification method and system
CN114297621A (en) * 2022-03-08 2022-04-08 浙江毫微米科技有限公司 Login method and device based on spatial anchor point and electronic equipment

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109462602B (en) * 2018-12-13 2022-11-01 平安普惠企业管理有限公司 Login information storage method, login verification method, device, equipment and medium
CN109766676A (en) * 2018-12-13 2019-05-17 深圳豪客互联网有限公司 A kind of cross-platform login method and device
CN111339505A (en) * 2018-12-18 2020-06-26 北京奇虎科技有限公司 Method and device for realizing user login
CN110166438B (en) * 2019-04-19 2022-03-18 平安科技（深圳）有限公司 Account information login method and device, computer equipment and computer storage medium
CN110231965B (en) * 2019-06-19 2022-05-10 京东方科技集团股份有限公司 Cloud device, application processing method and electronic device
CN110750511A (en) * 2019-09-06 2020-02-04 平安普惠企业管理有限公司 Operation history restoration method and device, computer equipment and storage medium
CN110505245B (en) * 2019-09-24 2022-06-03 北京百度网讯科技有限公司 Application login method, device and equipment
CN112714093B (en) * 2019-10-25 2023-05-12 深信服科技股份有限公司 Account abnormity detection method, device, system and storage medium
CN110889094A (en) * 2019-11-18 2020-03-17 中国银行股份有限公司 Login authentication method and device
CN111414526B (en) * 2020-03-02 2023-04-21 浙江同洲项目管理有限公司 Elevator additionally-installed supervision method and computer-readable storage medium
CN113395240B (en) * 2020-03-12 2023-09-05 阿里巴巴集团控股有限公司 Data acquisition method, device, equipment and medium
CN111552932A (en) * 2020-03-27 2020-08-18 北京奇艺世纪科技有限公司 Identity authentication method and device, electronic equipment and readable storage medium
CN111352552B (en) * 2020-03-30 2021-09-10 北京达佳互联信息技术有限公司 Application login method and device, electronic equipment and storage medium
CN111563005B (en) * 2020-04-02 2023-05-19 苏宁云计算有限公司 Cookie data processing method and device, computer equipment and storage medium
CN111741115B (en) * 2020-06-24 2022-12-16 支付宝(杭州)信息技术有限公司 Service processing method, device and system and electronic equipment
CN111797038B (en) * 2020-07-03 2021-12-10 深圳市慧为智能科技股份有限公司 Burning control method, system, device, equipment and computer readable storage medium
CN111859378B (en) * 2020-07-31 2022-11-18 中国工商银行股份有限公司 Processing method and device for protecting data model
CN112435063A (en) * 2020-11-27 2021-03-02 北京达佳互联信息技术有限公司 Resource processing method and device, electronic equipment and storage medium
CN112738021B (en) * 2020-12-02 2023-10-24 海能达通信股份有限公司 Single sign-on method, terminal, application server, authentication server and medium
CN112631700A (en) * 2020-12-22 2021-04-09 平安普惠企业管理有限公司 Login interface display method and device, computer equipment and storage medium
CN112953905A (en) * 2021-01-27 2021-06-11 湖南快乐阳光互动娱乐传媒有限公司 Data transmission method, system and server equipment
CN112784256A (en) * 2021-01-28 2021-05-11 北京明略昭辉科技有限公司 Account password management method and system
CN112948803B (en) * 2021-02-27 2023-10-27 平安科技（深圳）有限公司 Login method, system, equipment and storage medium of application program
CN113111340A (en) * 2021-04-10 2021-07-13 支付宝(杭州)信息技术有限公司 Method, device, equipment and readable medium for displaying login mode options
CN113435910A (en) * 2021-06-28 2021-09-24 平安信托有限责任公司 Sales-under-sale signing method and device, electronic equipment and storage medium
CN113472774B (en) * 2021-06-29 2022-10-25 平安普惠企业管理有限公司 Account login-free method, system, device and computer readable storage medium
CN117972672A (en) * 2021-07-28 2024-05-03 支付宝(杭州)信息技术有限公司 Login mode recommending method, device and equipment after unloading and reloading of application program
CN113722687A (en) * 2021-08-30 2021-11-30 康键信息技术（深圳）有限公司 Application software login method, device, medium and equipment
CN114095230B (en) * 2021-11-15 2023-09-26 腾讯科技（上海）有限公司 Data processing method, device, computer equipment and storage medium
CN114611079A (en) * 2022-02-18 2022-06-10 广州市玄武无线科技股份有限公司 Mobile terminal login method, device, equipment and storage medium
CN114584478B (en) * 2022-02-18 2024-02-27 北京圣博润高新技术股份有限公司 Method, device, equipment and storage medium for auditing application operation process
CN114363307B (en) * 2022-03-18 2022-08-26 浙江网商银行股份有限公司 Information processing method and system
CN114884646B (en) * 2022-03-24 2022-12-02 慧之安信息技术股份有限公司 System password storage method based on improved MD5 encryption processing
CN114816587B (en) * 2022-07-01 2022-11-25 五矿财富投资管理有限公司 Pull-up processing method and system based on native general application
CN115688069B (en) * 2022-11-04 2023-06-30 江西五十铃汽车有限公司 System login request response method, device and equipment
CN115941316B (en) * 2022-12-05 2023-08-08 广州力麒智能科技有限公司 Intelligent self-service terminal middleware calling method and device
CN116436633B (en) * 2023-02-08 2023-12-05 广州希倍思智能科技有限公司 Platform login method and system for receiving and transmitting verification code based on instant messaging
CN117077097B (en) * 2023-08-31 2024-03-19 深圳市易连汇通科技有限公司 Tablet personal computer login verification method based on data analysis
CN117459326B (en) * 2023-12-25 2024-03-08 吉林信息安全测评中心 Network safety protection system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103685169A (en) * 2012-09-06 2014-03-26 盛趣信息技术（上海）有限公司 Logging in method and system
CN105187431A (en) * 2015-09-17 2015-12-23 网易（杭州）网络有限公司 Log-in method, server, client and communication system for third party application
CN105553972A (en) * 2015-12-14 2016-05-04 苏州天平先进数字科技有限公司 Method of using third-party account to log in to screen locking APP community
CN107026832A (en) * 2016-10-10 2017-08-08 阿里巴巴集团控股有限公司 Account logon method, equipment and server

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007334490A (en) * 2006-06-13 2007-12-27 Yokogawa Electric Corp User authentication method and user authentication device
CN104518876B (en) * 2013-09-29 2019-01-04 腾讯科技（深圳）有限公司 Service login method and device
CN105828322B (en) * 2015-01-04 2019-09-17 中国移动通信集团辽宁有限公司 A kind of method, mobile terminal and security centre that user logs in
CN104539741B (en) * 2015-01-26 2019-10-15 北京奇艺世纪科技有限公司 A kind of reminding method and device of Account Logon
CN107248995B (en) * 2017-06-28 2021-06-01 北京五八信息技术有限公司 Account verification method and device
CN107995161A (en) * 2017-10-26 2018-05-04 深圳市华阅文化传媒有限公司 Read the processing method and processing device of APP login modes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103685169A (en) * 2012-09-06 2014-03-26 盛趣信息技术（上海）有限公司 Logging in method and system
CN105187431A (en) * 2015-09-17 2015-12-23 网易（杭州）网络有限公司 Log-in method, server, client and communication system for third party application
CN105553972A (en) * 2015-12-14 2016-05-04 苏州天平先进数字科技有限公司 Method of using third-party account to log in to screen locking APP community
CN107026832A (en) * 2016-10-10 2017-08-08 阿里巴巴集团控股有限公司 Account logon method, equipment and server

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006738A (en) * 2021-10-25 2022-02-01 上海交通大学 APP instance fingerprint and device fingerprint based hand-trip login verification method and system
CN114297621A (en) * 2022-03-08 2022-04-08 浙江毫微米科技有限公司 Login method and device based on spatial anchor point and electronic equipment

Also Published As

Publication number Publication date
CN108551443B (en) 2021-07-23
CN108551443A (en) 2018-09-18
CN113452719B (en) 2022-12-30
WO2019184135A1 (en) 2019-10-03

Similar Documents

Publication Publication Date Title
CN108551443B (en) Application login method and device, terminal equipment and storage medium
CN108768970B (en) Binding method of intelligent equipment, identity authentication platform and storage medium
CN103873454B (en) Authentication method and equipment
US9787672B1 (en) Method and system for smartcard emulation
US20210120392A1 (en) Virtual key binding method and system
CN110299996B (en) Authentication method, equipment and system
US20200280550A1 (en) System and method for endorsing a new authenticator
WO2020041747A1 (en) Methods, apparatuses, and computer program products for frictionless electronic signature management
KR20180026508A (en) A security verification method based on biometric characteristics, a client terminal, and a server
TW201903637A (en) Query system, method and non-transitory machine-readable medium to determine authentication capabilities
US9124571B1 (en) Network authentication method for secure user identity verification
CN112632521B (en) Request response method and device, electronic equipment and storage medium
US11044085B2 (en) Method employed in user authentication system and information processing apparatus included in user authentication system
CN109145628B (en) Data acquisition method and system based on trusted execution environment
CN108959990B (en) Two-dimensional code verification method and device
CN103488922A (en) Method and equipment for providing verification code
WO2017206524A1 (en) Electronic device control method, terminal and control system
CN105656627A (en) Identity verification method, device and system
CN105577619B (en) Client login method, client and system
CN104935435A (en) Login methods, terminal and application server
WO2020025056A1 (en) Method, device, system, and mobile terminal for security authorization
CN112217873B (en) Device sharing method, related device and storage medium
CN106537962B (en) Wireless network configuration, access and access method, device and equipment
CN114448722B (en) Cross-browser login method and device, computer equipment and storage medium
EP2916509B1 (en) Network authentication method for secure user identity verification

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant