CN110011992B - System login method and electronic equipment - Google Patents
System login method and electronic equipment Download PDFInfo
- Publication number
- CN110011992B CN110011992B CN201910228238.2A CN201910228238A CN110011992B CN 110011992 B CN110011992 B CN 110011992B CN 201910228238 A CN201910228238 A CN 201910228238A CN 110011992 B CN110011992 B CN 110011992B
- Authority
- CN
- China
- Prior art keywords
- user
- login
- user side
- information
- connection
- 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.)
- Active
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
Abstract
The embodiment of the application discloses a system login method and electronic equipment. One embodiment of the method comprises: under the condition that the login information sent by the same user side for many times is detected to be verified incorrectly, judging whether the user side is a credible user or not; and if the user side is determined to be a trusted user and correct login information sent by the user side is received, establishing login connection. That is, even if the user inputs wrong login information a plurality of times, the connection waiting time period may not be set as long as it can be determined that the user is an authentic user. And the login connection can be directly established under the condition that the user inputs correct login information. Such an embodiment may help reduce the login duration while ensuring connection security.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a system login method and electronic equipment.
Background
With the popularization of computer technology, most users register accounts on various network applications (such as mailboxes, instant messaging tools and the like) and set login passwords. For security reasons, in order to prevent the login password from being violently cracked, the login system in the prior art usually sets a waiting time (e.g. 30 seconds) in case of multiple errors of the login password. The user is not permitted to log on the connection for this waiting period. That is, the user may only try logging in again by waiting for the wait period to expire, even if the correct login password has been entered during this period.
Disclosure of Invention
The embodiment of the application provides a system login method and electronic equipment.
In a first aspect, an embodiment of the present application provides a system login method, including: under the condition that the login information sent by the same user side for many times is detected to be verified incorrectly, judging whether the user side is a credible user or not; and if the user side is determined to be a trusted user and correct login information sent by the user side is received, establishing login connection.
In some embodiments, if the ue cannot be determined as a trusted ue, a connection waiting duration is set, wherein no login connection is established within the connection waiting duration.
In some embodiments, determining whether the user side is a trusted user comprises: matching the network address of the user side in a target address set, wherein the target address in the target address set is the network address which is successfully connected with the system in a login manner; and if the target address matched with the network address of the user side exists in the target address set, determining the user side as a trusted user.
In some embodiments, if there is a target address matching the network address of the user end in the target address set, determining that the user end is a trusted user includes: if the target address set has a target address matched with the network address of the user side, the number of times of successful connection of the matched target address is further obtained, and if the number of times is larger than a first preset value, the user side is determined to be a trusted user.
In some embodiments, determining whether the user side is a trusted user includes: matching the login information which is repeatedly sent and is verified to be wrong in a target information set, wherein the target information in the target information set is historical login information used for successfully establishing login connection with a system; and if the login information which is repeatedly sent and is verified to be wrong contains the target information in the target information set, determining that the user side is a trusted user.
In some embodiments, if the login information that is verified to be incorrect and sent multiple times includes target information in the target information set, determining that the user side is a trusted user includes: if the login information which is verified to be wrong and sent for multiple times contains the target information in the target information set, further judging whether the user side is a credible user or not according to the proportion of the contained target information in the login information which is verified to be wrong; and if the proportion of the contained target information in the log-in information which is verified to be wrong is larger than a second preset value, determining that the user side is a credible user.
In some embodiments, determining whether the user side is a trusted user includes: and if the different numbers of the login information which is subjected to the verification error and is sent for multiple times are not larger than a third preset value, determining that the user side is a trusted user.
In some embodiments, determining whether the user side is a trusted user comprises: and if the login information sent again by the user side is verified correctly, determining that the user side is a trusted user.
In a second aspect, an embodiment of the present application provides an electronic device, including: the processing module is configured to judge whether the user side is a trusted user or not under the condition that the login information sent by the same user side for multiple times is verified incorrectly; and the communication module is configured to establish login connection if the user side is determined to be a trusted user and correct login information sent by the user side is received.
In some embodiments, the electronic device further includes a timing module configured to set a connection waiting duration if the user side cannot be determined to be the trusted user, wherein the login connection is not established within the connection waiting duration.
The system login method and the electronic device provided by the embodiment of the application can judge the trusted user under the condition that the login information sent by the same user side for many times is detected to be verified incorrectly, namely, whether the user side is the trusted user is judged. If the user side is determined to be a trusted user and correct login information sent by the user side is received, login connection can be established. That is, even if the user inputs wrong login information many times, the connection waiting time period may not be set as long as it can be determined that the user is an authentic user. And the login connection can be directly established under the condition that the user inputs correct login information. Such an embodiment may help reduce the login duration while ensuring connection security.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:
FIG. 1 is a flow chart of one embodiment of a system login method provided herein;
FIG. 2 is a flow chart of another embodiment of a system login method provided by the present application;
fig. 3 is a schematic structural diagram of an embodiment of an electronic device provided in the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the present application is described in detail below with reference to the accompanying drawings and the detailed description.
Various aspects and features of the present application are described herein with reference to the accompanying drawings.
These and other characteristics of the present application will become apparent from the following description of preferred forms of embodiment, given as non-limiting examples, with reference to the attached drawings.
It should also be understood that, although the present application has been described with reference to some specific examples, a person of skill in the art shall certainly be able to achieve many other equivalent forms of application, having the characteristics as set forth in the claims and hence all coming within the field of protection defined thereby.
The above and other aspects, features and advantages of the present application will become more apparent in view of the following detailed description when taken in conjunction with the accompanying drawings.
Specific embodiments of the present application are described hereinafter with reference to the drawings; however, it is to be understood that the disclosed embodiments are merely exemplary of the application, which can be embodied in various forms. Well-known and/or repeated functions and constructions are not described in detail to avoid obscuring the application of unnecessary or unnecessary detail based on the historical actions of the user. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present application in virtually any appropriately detailed structure.
The specification may use the phrases "in one embodiment," "in another embodiment," "in yet another embodiment," or "in other embodiments," which may each refer to one or more of the same or different embodiments in accordance with the application.
Referring to fig. 1, a flow 100 of an embodiment of a system login method provided by the present application is shown. The system login method can be applied to various electronic devices. The electronic devices herein may include, but are not limited to, smart phones, tablet computers, desktop computers, servers, and the like. The system login method can comprise the following steps:
In general, in the conventional login connection method, if login information sent by the same user side for many times is wrong, the system usually extends a certain time before login is permitted. That is, for various users, the connection method generally adopts a uniform processing method. However, in the case of a malicious user (such as an illegal user or a stolen number user), such a connection mode may be beneficial to protect the security of the account. However, if the user is operating normally, the connection method often increases the login duration of the user, which causes inconvenience for the user to operate.
In this embodiment, if it is detected that the login information sent by the same ue for multiple times is verified incorrectly, it can be determined whether the ue is a trusted ue. That is, in this case, the determination of the trusted user may be performed first, and further processing may be performed according to the determination result. That is, different processing manners may be adopted for different users.
Here, various methods in the prior art may be adopted to determine whether the login information received multiple times is from the same user side. For example, it may be counted whether the account names transmitting the respective login information are the same. For another example, it may be counted whether the device identifiers (such as the mobile phone number and the device IP address) sending the respective login information are the same, and so on. The login information may be various information required for implementing account login, such as (but not limited to) an account name, a login password, and/or a check code. It is understood that the above-mentioned times can be set according to actual conditions. The plurality of times may be one time, for example, to secure the account. As another example, to improve the user experience, the plurality of times may be at least twice.
In this embodiment, the trusted user generally refers to a user without network security risk, and is generally a user who normally uses and operates. Whether the user side is a trusted user can be determined in various ways.
For example, the network address of the user terminal may be matched in the target address set. The target address in the target address set may be a network address that successfully establishes a login connection with the system. I.e. the destination address may be the network address of the user terminal that has previously successfully logged into the system. At this time, if there is a target address matching the network address of the ue in the target address set, it may indicate that the ue may be a ue that has successfully logged into the system before, so that the ue may be determined to be a trusted user.
It should be noted that the network Address may be a logical Address capable of uniquely determining the ue in a network (e.g., Internet, local area network, etc.), and may include (but is not limited to) an IP Address (Internet Protocol Address). Furthermore, the storage location of the target address set is not limited in this application.
Optionally, in order to improve the accuracy of the determination result, if a target address matching the network address of the user end exists in the target address set, the number of times of successful connection of the matching target address may be further obtained. If the number of successful connections of the matched target address is greater than the first preset value (e.g., 10), it can be said that the ue has successfully logged into the system many times, so that the ue can be determined to be a trusted ue. This is advantageous for improving the security of the login connection.
For another example, the log-in information that is verified to be incorrect and transmitted multiple times may be matched in the target information set. The target information in the target information set may be historical login information used for successfully establishing login connection with the system. That is, the target information may be the login information used for the previous correct connection to the system, that is, the login information that was used once. At this time, if the login information that is verified to be incorrect and transmitted multiple times includes the target information in the target information set, the user side can be determined as an authentic user.
In the case where the number of the login information with the verification error is not less than two, the login information with the verification error may be matched with each other in the target information set in order to improve the efficiency of the determination process. As long as there is matching target information, the matching process for other log-in information that is verified to be incorrect can be stopped. In order to improve the accuracy of the determination result, the user side may be determined to be a trusted user when all the login information sent multiple times and verified incorrectly is historical login information.
Optionally, in order to improve flexibility of the determination method, an application range of the method is expanded, and if the login information with the error verification sent multiple times includes the target information in the target information set, whether the user side is a trusted user may be further determined according to a ratio of the included target information in the login information with the error verification. That is, if only part of the registration information with the verification error transmitted a plurality of times is the history registration information, the ratio of the history registration information to the registration information with the verification error can be determined in order to improve the accuracy of the determination result. I.e. the probability of the occurrence of historical login information among multiple transmissions of login information with a verified error. At this time, if the ratio of the target information included in the log-in information with the verification error is greater than a second preset value (e.g., 80%), it may be determined that the user terminal is an authentic user.
For another example, it can also be determined whether the user side is a trusted user according to different conditions of login information that is sent by the user side every time and is verified incorrectly. In addition, when a login attempt is performed every time different login information is transmitted, it is generally considered as an abnormal operation, and an account may be attacked, which may cause a security risk. As an example, if the different numbers of login information with multiple verification errors are not greater than the third preset value (e.g., two types), the user terminal may be determined to be a trusted user. That is, if the login information that is verified to be incorrect is the same historical login information, it means that the user using the user terminal may forget to modify the login information and may attempt to login using the login information before modification.
It should be noted that, in order to further improve the accuracy of the determination result, if the different numbers of the login information with the verification error sent for multiple times are greater than the third preset value, at least one of the above manners (the target address set, the number of successful connections, the target information set, the ratio, and the like) may be adopted to further determine whether the user side is a trusted user. For example, although the different number of the wrong login information is greater than the third preset value, the network address of the user side is the target address, and/or the wrong login information is the historical login information, and the user side can also be determined as the trusted user.
It is understood that the above is to perform the determination of the trusted user according to the historical data of the user side. These approaches are more suitable for older users (registered or frequently logged-in users). For a new user, such as a newly registered user, or a user who has not logged in or logged in less times (e.g., not more than three times) after registration, the above method often cannot determine whether the user terminal is a trusted user. Optionally, if the login information sent again by the user side is verified correctly, the user side may be determined to be a trusted user. That is, for a new user, when receiving the correct login information sent by the new user, the new user can be determined as a trusted user, and the login connection is directly established.
In this embodiment, if the ue is determined to be a trusted ue and receives correct login information sent by the ue, the ue can directly establish login connection with the system. Instead, the conventional connection method, that is, the method of allowing connection after a certain period of time is not used, that is, the connection waiting period may not be set. Therefore, the login duration of the credible user is favorably shortened, and the login efficiency is improved.
In the prior art, if some management software does not change the password of the management terminal in time due to normal operation, the management software can continuously try to log in by using a wrong password. And finally, after the managed terminal refuses to log in, the managed terminal cannot normally connect for a long time even if the managed terminal is changed into a correct password.
In this embodiment, if the user terminal that has been connected before is found to be the wrong login password sent by the other party, the user terminal can be connected directly after receiving the correct password as long as the user terminal can be confirmed to be trusted before after the login connection is rejected due to the use of the old password for many times, and the connection method in the prior art is not used any longer.
The system login method provided by the embodiment of the application can judge the trusted user under the condition that the login information sent by the same user side for many times is detected to be verified incorrectly, namely, whether the user side is the trusted user is judged. If the user side is determined to be a trusted user and correct login information sent by the user side is received, login connection can be established. That is, even if the user inputs wrong login information a plurality of times, the connection waiting time period may not be set as long as it can be determined that the user is an authentic user. And the login connection can be directly established under the condition that the user inputs correct login information. Such an embodiment may help reduce the login duration while ensuring connection security.
With continued reference to fig. 2, a flow 200 of yet another embodiment of the system login method provided by the present application is shown. The system login method can comprise the following steps:
In step 203, if the user side cannot be determined as a trusted user, a connection waiting time length is set.
In this embodiment, if it cannot be determined that the ue is a trusted user, a login connection manner in the prior art may be adopted, that is, a connection waiting time (e.g., 30 seconds) is set. Wherein no login connection is established for the connection wait duration. Here, the implementation manner of not establishing the login connection is not limited. For example, the user terminal cannot input login information during the connection waiting time. Or the user side can input the login information within the connection waiting time, but the login information is not verified. Or, even if the login information is verified within the connection waiting time, the login connection is not permitted regardless of the verification result (correct or incorrect). That is, in a case where it is not possible to determine whether the user side is a trusted user, the connection waiting time period may be set in order to secure the account. Thus, the ue is not allowed to log on during the connection waiting time.
Further, if the login information sent again by the user side is verified incorrectly, the connection waiting time can be prolonged, so as to further improve the security of the account. For example, if the ue sends the wrong login information again within the connection waiting time, the connection waiting time currently being timed may be extended. For example, after the previous time of the connection waiting time period is timed, if the user terminal sends the wrong login information again, a connection waiting time period may be set again. Wherein the connection waiting time period set again may be longer than the previous connection waiting time period.
The system login method provided by the embodiment of the application further enriches and perfects the step process. Therefore, the practical use condition can be better met, and the application range of the method is expanded.
Referring now to fig. 3, the present application further provides an embodiment of an electronic device as an implementation of the method shown in the above-mentioned figures. The embodiment of the electronic device corresponds to the embodiment of the method shown in the above embodiments.
As shown in fig. 3, the electronic device 300 of the present embodiment may include: the processing module 301 is configured to determine whether the user side is a trusted user when detecting that login information sent by the same user side multiple times is verified incorrectly; the communication module 302 is configured to establish a login connection if the user terminal is determined to be a trusted user and correct login information sent by the user terminal is received.
In some optional implementations, the electronic device 300 may further include a timing module (not shown in fig. 3) configured to set a connection waiting duration if the user terminal cannot be determined to be a trusted user, wherein the login connection is not established within the connection waiting duration.
Optionally, the processing module 301 may be further configured to match the network address of the user end in a target address set, where the target address in the target address set is a network address successfully establishing a login connection with the system; and if the target address matched with the network address of the user side exists in the target address set, determining the user side as a trusted user.
Further, the processing module 301 may be further configured to further obtain the number of successful connections of the matched target address if a target address matching the network address of the user end exists in the target address set, and determine that the user end is a trusted user if the number of successful connections of the matched target address is greater than a first preset value.
In some embodiments, the processing module 301 may be further configured to match the login information with the multiple sent verified errors in a target information set, where the target information in the target information set is historical login information used for successfully establishing a login connection with the system; and if the login information which is repeatedly sent and is verified to be wrong contains the target information in the target information set, determining that the user side is a trusted user.
Further, the processing module 301 may be further configured to determine whether the user side is a trusted user according to a ratio of the included target information in the login information with the error verification if the login information with the error verification sent multiple times includes the target information in the target information set; and if the proportion of the contained target information in the log-in information with the wrong verification is larger than a second preset value, determining that the user side is a trusted user.
Optionally, the processing module 301 may be further configured to determine that the user side is a trusted user if the different number of the login information with the multiple times of verification errors is not greater than a third preset value.
In some application scenarios, the processing module 301 may be further configured to determine that the user terminal is a trusted user if the login information sent again by the user terminal is verified correctly.
Since the electronic device described in this embodiment is an electronic device corresponding to the system login method in this embodiment, based on the system login method in this embodiment, a person skilled in the art can understand a specific implementation of the electronic device in this embodiment and various variations thereof, and therefore, a detailed description of the electronic device is not given here. Electronic devices that implement the system login method in the embodiments of the present application are within the scope of the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing module of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing module of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (10)
1. A system login method, comprising:
under the condition that login information sent by the same user side for multiple times is detected to be verified incorrectly, judging whether the user side is a trusted user or not at least based on the proportion of target information in the login information with the verified error; the login information is login information input by a user;
if the user side is determined to be a trusted user and correct login information sent by the user side is received, establishing login connection;
the target information is historical login information used for successfully establishing login connection with the system.
2. The method of claim 1, wherein if the user side cannot be determined to be a trusted user, setting a connection waiting duration, wherein no login connection is established within the connection waiting duration.
3. The method of claim 1, wherein the determining whether the user side is a trusted user comprises:
matching the network address of the user side in a target address set, wherein the target address in the target address set is a network address which successfully establishes login connection with a system;
and if the target address matched with the network address of the user side exists in the target address set, determining that the user side is a trusted user.
4. The method of claim 3, wherein determining that the user terminal is a trusted user if a target address matching the network address of the user terminal exists in the target address set comprises:
if the target address set has a target address matched with the network address of the user side, further acquiring the times of successful connection of the matched target address, and if the times are greater than a first preset value, determining that the user side is a trusted user.
5. The method of claim 1, wherein the determining whether the user side is a trusted user comprises:
matching the login information which is repeatedly sent and is verified to be wrong in a target information set, wherein the target information in the target information set is historical login information used for successfully establishing login connection with a system;
and if the login information which is repeatedly sent and is verified to be wrong contains the target information in the target information set, determining that the user side is a trusted user.
6. The method of claim 5, wherein the determining that the user side is a trusted user if the login information with the multiple times of verification errors includes the target information in the target information set comprises:
if the login information which is verified to be wrong and sent for multiple times contains the target information in the target information set, whether the user side is a trusted user or not is further judged according to the proportion of the contained target information in the login information which is verified to be wrong;
and if the proportion of the contained target information in the log-in information with the wrong verification is larger than a second preset value, determining that the user side is a trusted user.
7. The method of claim 1, wherein the determining whether the user side is a trusted user comprises:
and if the different numbers of the login information which is verified to be wrong and sent for multiple times are not larger than a third preset value, determining that the user side is a trusted user.
8. The method of claim 1, wherein the determining whether the user side is a trusted user comprises:
and if the login information sent again by the user side is verified correctly, determining that the user side is a trusted user.
9. An electronic device, comprising:
the processing module is configured to judge whether the user side is a trusted user or not at least based on the proportion of target information in login information with errors in verification under the condition that login information sent by the same user side for multiple times is detected to be wrong in verification; the login information is login information input by a user;
the communication module is configured to establish login connection if the user side is determined to be a trusted user and correct login information sent by the user side is received;
the target information is historical login information used for successfully establishing login connection with the system.
10. The electronic device of claim 9, further comprising a timing module configured to set a connection wait duration if the user side cannot be determined to be a trusted user, wherein no login connection is established within the connection wait duration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910228238.2A CN110011992B (en) | 2019-03-25 | 2019-03-25 | System login method and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910228238.2A CN110011992B (en) | 2019-03-25 | 2019-03-25 | System login method and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110011992A CN110011992A (en) | 2019-07-12 |
| CN110011992B true CN110011992B (en) | 2022-07-26 |
Family
ID=67167958
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910228238.2A Active CN110011992B (en) | 2019-03-25 | 2019-03-25 | System login method and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110011992B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102761531A (en) * | 2011-04-29 | 2012-10-31 | 腾讯科技（深圳）有限公司 | Community authentication method and server |
| CN106603422A (en) * | 2016-12-09 | 2017-04-26 | 上海斐讯数据通信技术有限公司 | Network steal prevention method of wireless router, and wireless router |
| CN107135201A (en) * | 2017-04-01 | 2017-09-05 | 网易（杭州）网络有限公司 | A kind of webserver login authentication method and device |
| CN108494749A (en) * | 2018-03-07 | 2018-09-04 | 中国平安人寿保险股份有限公司 | Method, apparatus, equipment and the computer readable storage medium of IP address disabling |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3707381B2 (en) * | 2000-10-20 | 2005-10-19 | 日本電気株式会社 | Login control method, login control system, and information recording medium recording login control program |
| US9489503B2 (en) * | 2009-12-21 | 2016-11-08 | Paypal, Inc. | Behavioral stochastic authentication (BSA) |
| CN103581108B (en) * | 2012-07-19 | 2017-05-03 | 阿里巴巴集团控股有限公司 | Login authentication method, login authentication client, login authentication server and login authentication system |
| CN103532797B (en) * | 2013-11-06 | 2017-07-04 | 网之易信息技术（北京）有限公司 | A kind of User logs in method for monitoring abnormality and device |
| CN104767723B (en) * | 2014-01-08 | 2018-12-07 | 中国移动通信集团河北有限公司 | A kind of authentication method and device |
| CN105592014B (en) * | 2014-10-24 | 2019-02-15 | 阿里巴巴集团控股有限公司 | A kind of trusted terminal verification method, device |
| US10447692B2 (en) * | 2015-03-31 | 2019-10-15 | Oath Inc. | Auto-creation of application passwords |
| CN105897670A (en) * | 2015-11-13 | 2016-08-24 | 乐视云计算有限公司 | Website user login authentication method and system |
| CN107231346A (en) * | 2017-05-03 | 2017-10-03 | 北京海顿中科技术有限公司 | A kind of method of cloud platform identification |
| CN107172104B (en) * | 2017-07-17 | 2019-12-27 | 顺丰科技有限公司 | Login abnormity detection method, system and equipment |
| CN108092975B (en) * | 2017-12-07 | 2020-09-22 | 上海携程商务有限公司 | Abnormal login identification method, system, storage medium and electronic equipment |
| CN108965294A (en) * | 2018-07-16 | 2018-12-07 | 安徽信尔联信息科技有限公司 | A kind of user name and cipher protection system |
-
2019
- 2019-03-25 CN CN201910228238.2A patent/CN110011992B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102761531A (en) * | 2011-04-29 | 2012-10-31 | 腾讯科技（深圳）有限公司 | Community authentication method and server |
| CN106603422A (en) * | 2016-12-09 | 2017-04-26 | 上海斐讯数据通信技术有限公司 | Network steal prevention method of wireless router, and wireless router |
| CN107135201A (en) * | 2017-04-01 | 2017-09-05 | 网易（杭州）网络有限公司 | A kind of webserver login authentication method and device |
| CN108494749A (en) * | 2018-03-07 | 2018-09-04 | 中国平安人寿保险股份有限公司 | Method, apparatus, equipment and the computer readable storage medium of IP address disabling |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110011992A (en) | 2019-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11716324B2 (en) | Systems and methods for location-based authentication | |
| US11856132B2 (en) | Validating automatic number identification data | |
| CN105847245B (en) | Electronic mailbox login authentication method and device | |
| US9119076B1 (en) | System and method for authentication using a mobile communication device | |
| US8856892B2 (en) | Interactive authentication | |
| CN106453205B (en) | identity verification method and device | |
| US20160330240A1 (en) | Blocking via an unsolvable captcha | |
| CN107241336B (en) | Identity verification method and device | |
| CN110247897B (en) | System login method, device, gateway and computer readable storage medium | |
| US20160344752A1 (en) | Brute force attack prevention system | |
| JP2008181310A (en) | Authentication server and authentication program | |
| CN111182547A (en) | Login protection method, device and system | |
| CN107872588B (en) | Call processing method, related device and system | |
| CN102833247A (en) | Method for anti-sweeping ciphers in user login system and device thereof | |
| CN109784024A (en) | One kind authenticating FIDO method and system based on the polyfactorial quick online identity of more authenticators | |
| US20170063834A1 (en) | Multi-factor device registration for establishing secure communication | |
| KR101879843B1 (en) | Authentication mehtod and system using ip address and short message service | |
| CN110011992B (en) | System login method and electronic equipment | |
| CN111371811A (en) | Resource calling method, resource calling device, client and service server | |
| CN109460647B (en) | Multi-device secure login method | |
| CN111949952A (en) | Method for processing verification code request and computer-readable storage medium | |
| US20180109384A1 (en) | Brute force attack prevention system | |
| CN115174122A (en) | Verification code generation method, verification code verification method, device, equipment and medium | |
| CN111193687B (en) | Validity verification method, device, equipment and computer readable storage medium | |
| KR20130124447A (en) | Intelligent login authentication system and method thereof |
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 |