CN105656948A - Account login method and device - Google Patents
Account login method and device Download PDFInfo
- Publication number
- CN105656948A CN105656948A CN201610194789.8A CN201610194789A CN105656948A CN 105656948 A CN105656948 A CN 105656948A CN 201610194789 A CN201610194789 A CN 201610194789A CN 105656948 A CN105656948 A CN 105656948A
- Authority
- CN
- China
- Prior art keywords
- login
- terminal
- account
- target account
- login confirmation
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000012790 confirmation Methods 0.000 claims abstract description 223
- 230000004044 response Effects 0.000 claims abstract description 114
- 238000012545 processing Methods 0.000 claims description 34
- 238000010586 diagram Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- 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/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/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
-
- 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/3271—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 challenge-response
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention relates to an account login method and device. The account login method includes transmitting account login requests through a receiving terminal, wherein the account login requests include account information of a target account and identification of the terminal; judging whether or not the identification of the terminal is the identification of a device bound with the target account after the account information is authenticated; if the identification of the terminal is not the identification of the device bound with the target account, transmitting login confirmation request to the preset main device, wherein the login confirmation request is used for requesting whether the target account can be logged in the terminal or not to the main device; finally receiving the login conformation response transmitted by the main device, wherein the login conformation response is used for indicating whether the target account can be logged in the terminal or not; allowing or forbidding the target account to log in the terminal according to the login conformation response. With the account login method, the risk of leak of users' privacy as other people log in the account in the other terminals when the account and its passwords are stolen, and safety of the account is improved.
Description
Technical Field
The disclosure relates to the field of electronic technology application, and in particular, to an account login method and device.
Background
With the development of science and technology, electronic products are more and more widely applied, a user can log in the same account number in a plurality of terminals at the same time, and the contents of pictures, notebooks, short messages and the like in the terminals used by the user are stored in a server through a cloud storage technology.
In the related art, when a user logs in an account of a server through a terminal, the terminal sends an account login request to the server, where the account login request includes account information, and the account information may include: the server performs authentication processing (also called user authentication) on the account information, and after the authentication is successful, the server allows the account to be logged in on the terminal.
However, when the account and the password of the user are leaked, the server cannot prohibit the login of the account in time, and an illegal user can access the content stored in the server according to the stolen account and the password, so that the risk of leaking the privacy of the user may exist.
Disclosure of Invention
In order to overcome the problems in the related art, the disclosure provides an account login method and device.
According to a first aspect of the embodiments of the present disclosure, there is provided an account login method for a server, including:
receiving an account login request sent by a terminal, wherein the account login request comprises: account information of the target account and the identification of the terminal;
after the account information is successfully authenticated, judging whether the identifier of the terminal is the identifier of the device bound with the target account;
when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal;
receiving a login confirmation response sent by the main device, wherein the login confirmation response is used for indicating whether the terminal is allowed to log in the target account;
and allowing or prohibiting the target account to log in the terminal according to the login confirmation response.
Optionally, the method further includes:
when a login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request, sequentially sending the login confirmation request to other equipment in the equipment bound with the target account according to a preset sequence, and allowing or forbidding the target account to log in the terminal according to the login confirmation response received for the first time;
or, when a login confirmation response sent by the master device is not received within a preset time period from the time when the login confirmation request is sent, allowing the target account to log in the terminal.
Optionally, the method further includes:
when a login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request, obtaining a historical login confirmation response sent by the main equipment before the login confirmation request is sent;
according to the historical login confirmation response, counting the historical times of allowing the terminal to log in the target account;
when the historical times are larger than a preset time threshold, allowing the target account to log in the terminal;
and when the historical times are not greater than a preset time threshold, forbidding the target account to log in the terminal.
Optionally, the device bound to the target account is the primary device.
According to a second aspect of the embodiments of the present disclosure, there is provided an account login method for a primary device, including:
receiving a login confirmation request sent by a server, wherein the login confirmation request is sent to a preset main device when the server judges that the identifier of a terminal contained in an account login request is not the identifier of a device bound with a target account after successfully authenticating account information of the target account contained in the account login request sent by a terminal, and the login confirmation request is used for requesting the main device whether to allow the terminal to log in the target account;
presenting the login confirmation request to a user;
generating a login confirmation response according to the operation of the user on the login confirmation request, wherein the login confirmation response is used for indicating whether the login of the target account is allowed to be performed on the terminal;
and sending the login confirmation response to the server.
Optionally, the login confirmation request includes: the identification of the terminal and the current position information of the terminal.
According to a third aspect of the embodiments of the present disclosure, there is provided an account login apparatus, for a server, including:
the terminal comprises a receiving module and a sending module, wherein the receiving module is configured to receive an account login request sent by the terminal, and the account login request comprises: account information of the target account and the identification of the terminal;
the judging module is configured to judge whether the identifier of the terminal is the identifier of the device bound with the target account number after the account number information is successfully authenticated;
the request module is configured to send a login confirmation request to a preset main device when the identifier of the terminal is not the identifier of the device bound with the target account, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal;
the receiving module is further configured to receive a login confirmation response sent by the master device, where the login confirmation response is used to indicate whether to allow the terminal to log in the target account;
and the processing module is configured to allow or prohibit the target account to log in the terminal according to the login confirmation response.
Optionally, the processing module is further configured to:
and when the identifier of the terminal is the identifier of the equipment bound with the target account, allowing the target account to log in the terminal.
Optionally, the request module is further configured to: when a login confirmation response sent by the master device is not received within a preset time period from the time when the login confirmation request is sent, sequentially sending the login confirmation request to other devices in the devices bound to the target account according to a preset sequence, wherein the processing module is further configured to: allowing or prohibiting the target account to log in the terminal according to the first received login confirmation response;
alternatively, the processing module is further configured to: and when the login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request, allowing the target account to log in the terminal.
Optionally, the apparatus further comprises:
the acquisition module is configured to acquire a historical login confirmation response sent by the main equipment before the login confirmation request is sent when the login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request;
a counting module configured to count the number of history times of allowing the login of the target account at the terminal according to the history login confirmation response;
the processing module is further configured to allow the target account to log in the terminal when the historical times are greater than a preset time threshold;
the processing module is further configured to prohibit the target account from logging in the terminal when the historical times are not greater than a preset times threshold.
Optionally, the device bound to the target account is the primary device.
According to a fourth aspect of the embodiments of the present disclosure, there is provided an account login apparatus, configured to a primary device, including:
the system comprises a receiving module, a login confirmation request and a processing module, wherein the login confirmation request is sent to preset main equipment when the server judges that the identifier of a terminal contained in an account login request is not the identifier of equipment bound with a target account after successfully authenticating account information of the target account contained in the account login request sent by a terminal, and the login confirmation request is used for requesting the main equipment whether to allow the terminal to log in the target account;
a display module configured to present the login confirmation request to a user;
a response module configured to generate a login confirmation response according to an operation of a user on the login confirmation request, where the login confirmation response is used to indicate whether to allow the login of the target account in the terminal;
a sending module configured to send the login confirmation response to the server.
Optionally, the login confirmation request includes: the identification of the terminal and the current position information of the terminal.
According to a fifth aspect of the embodiments of the present disclosure, there is provided an account login apparatus, for a server, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving an account login request sent by a terminal, wherein the account login request comprises: account information of the target account and the identification of the terminal;
after the account information is successfully authenticated, judging whether the identifier of the terminal is the identifier of the device bound with the target account;
when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal;
receiving a login confirmation response sent by the main device, wherein the login confirmation response is used for indicating whether the terminal is allowed to log in the target account;
and allowing or prohibiting the target account to log in the terminal according to the login confirmation response.
According to a sixth aspect of the embodiments of the present disclosure, there is provided an account login apparatus, for a primary device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving a login confirmation request sent by a server, wherein the login confirmation request is sent to a preset main device when the server judges that the identifier of a terminal contained in an account login request is not the identifier of a device bound with a target account after successfully authenticating account information of the target account contained in the account login request sent by a terminal, and the login confirmation request is used for requesting the main device whether to allow the terminal to log in the target account;
presenting the login confirmation request to a user;
generating a login confirmation response according to the operation of the user on the login confirmation request, wherein the login confirmation response is used for indicating whether the login of the target account is allowed to be performed on the terminal;
and sending the login confirmation response to the server.
According to a seventh aspect of embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium having instructions which, when executed by a processor of a mobile terminal, enable the mobile terminal to perform an account login method for a server, the method comprising: receiving an account login request sent by a terminal, wherein the account login request comprises: account information of the target account and the identification of the terminal; after the account information is successfully authenticated, judging whether the identifier of the terminal is the identifier of the device bound with the target account; when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal; receiving a login confirmation response sent by the main device, wherein the login confirmation response is used for indicating whether the terminal is allowed to log in the target account; and allowing or prohibiting the target account to log in the terminal according to the login confirmation response.
According to an eighth aspect of the embodiments of the present disclosure, there is provided another non-transitory computer-readable storage medium, wherein instructions, when executed by a processor of a mobile terminal, enable the mobile terminal to perform an account login method for a primary device, the method comprising: receiving a login confirmation request sent by a server, wherein the login confirmation request is sent to a preset main device when the server judges that the identifier of a terminal contained in an account login request is not the identifier of a device bound with a target account after successfully authenticating account information of the target account contained in the account login request sent by a terminal, and the login confirmation request is used for requesting the main device whether to allow the terminal to log in the target account; presenting the login confirmation request to a user; generating a login confirmation response according to the operation of the user on the login confirmation request, wherein the login confirmation response is used for indicating whether the login of the target account is allowed to be performed on the terminal; and sending the login confirmation response to the server.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
the method comprises the following steps of receiving an account login request sent by a terminal, wherein the account login request comprises: the account information of the target account and the identifier of the terminal are authenticated successfully, and whether the identifier of the terminal is the identifier of the device bound with the target account is judged; when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal; finally, receiving a login confirmation response sent by the main device, wherein the login confirmation response is used for indicating whether the terminal is allowed to log in the target account; and allowing or prohibiting the target account to log in the terminal according to the login confirmation response. According to the method and the device, the danger that privacy of the user is revealed because other people can log in the account through other terminals when the account and the password are revealed can be avoided, and the safety of the account is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic diagram of an implementation environment according to various embodiments of the present disclosure.
Fig. 2 is a flowchart illustrating an account login method according to an exemplary embodiment.
Fig. 3 is a flowchart illustrating another account login method according to an example embodiment.
Fig. 4 is a flowchart illustrating an account login method according to an example embodiment.
Fig. 5 is a flowchart illustrating another account login method according to an example embodiment.
Fig. 6 is a flowchart illustrating yet another account login method according to an example embodiment.
Fig. 7 is a block diagram illustrating an account login device according to an example embodiment.
Fig. 8 is a block diagram illustrating another account login device according to an example embodiment.
Fig. 9 is a block diagram illustrating another account login device according to an example embodiment.
Fig. 10 is a block diagram illustrating an account login device according to an example embodiment.
Fig. 11 is a block diagram illustrating an account login device according to an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Before introducing the account login method provided by the present disclosure, an application scenario related to the present disclosure is first introduced, and fig. 1 is a schematic structural diagram of an implementation environment related to each embodiment of the present disclosure. Referring to fig. 1, the implementation environment may include: a plurality of terminals, 3 terminals in fig. 1 are taken as an example, and as shown in fig. 1, the terminals 100, 200, and 300 are respectively terminals 100, 200, and 300, the terminal 100 is a master device, and the implementation environment further includes a server 400, where the terminals 100, 200, and 300 and the server 400 may establish communication connection with the server 400 in a wireless or wired manner, and the terminals 100, 200, and 300 may request login to the server 400 using the same account. The terminal 100, the terminal 200, and the terminal 300 may be, for example, a mobile terminal such as a smart phone, a tablet computer, a smart television, a smart watch, a PDA (personal digital assistant), a portable computer, or a fixed terminal such as a desktop computer, and the server 400 may be a server, a server cluster including a plurality of servers, or a cloud computing service center.
Fig. 2 is a flowchart illustrating an account login method according to an exemplary embodiment, which may be used for a server, which may be the server 400 in the implementation environment shown in fig. 1, and as shown in fig. 2, the method includes the following steps.
Step 201, receiving an account login request sent by a terminal, where the account login request includes: account information of the target account and the identifier of the terminal.
Step 202, after the account information is successfully authenticated, whether the identifier of the terminal is the identifier of the device bound with the target account is judged.
Step 203, when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, where the login confirmation request is used to request the main device whether to allow the login of the target account in the terminal.
And 204, receiving a login confirmation response sent by the main device, wherein the login confirmation response is used for indicating whether the terminal is allowed to log in the target account.
And step 205, allowing or prohibiting the target account to log in the terminal according to the login confirmation response.
The terminal in each step may be a terminal that is not a master device, such as the terminal 200 or the terminal 300 in the implementation environment shown in fig. 1, and in addition, the terminal that is a master device is preset, for example, a first terminal bound to a target account may be set as the master device by default, or a user may designate one of a plurality of terminals bound to the target account as the master device, and after the master device is determined, the terminal that is the master device may be changed as needed, and of course, consideration of security may first pass security verification of the user when the terminal that is the master device is changed.
Fig. 3 is a flowchart illustrating another account login method according to an exemplary embodiment, where the method may be used for a primary device, which may be the terminal 100 in the implementation environment shown in fig. 1, and as shown in fig. 3, the method includes the following steps.
Step 301, receiving a login confirmation request sent by a server, where the login confirmation request is sent to a preset host device when the server determines that an identifier of a terminal included in an account login request sent by a terminal is not an identifier of a device bound with a target account after successfully authenticating account information of the target account included in the account login request sent by the terminal, and the login confirmation request is used to request the host device whether to allow the terminal to log in the target account.
Step 302, a login confirmation request is presented to the user.
Step 303, generating a login confirmation response according to the operation of the user on the login confirmation request, wherein the login confirmation response is used for indicating whether the login of the target account in the terminal is allowed.
Step 304, send login confirmation response to server.
The terminal in each step may be a terminal that is not a master device, such as the terminal 200 or the terminal 300 in the implementation environment shown in fig. 1, and in addition, the terminal that is a master device is preset, for example, a first terminal bound to a target account may be set as the master device by default, or a user may designate one of a plurality of terminals bound to the target account as the master device, and after the master device is determined, the terminal that is the master device may be changed as needed, and of course, consideration of security may first pass security verification of the user when the terminal that is the master device is changed.
According to the account login method provided by the embodiment of the invention, after receiving an account login request which is sent by a terminal and comprises account information of a target account and an identifier of the terminal, a server authenticates the account information, and after the account information is successfully authenticated, whether the identifier of the terminal is the identifier of equipment bound with the target account is judged; when the identifier of the terminal is not the identifier of the device bound with the target account, the server sends a login confirmation request to a preset main device, the login confirmation request is used for requesting the main device whether to allow the terminal to log in the target account, finally, the server receives a login confirmation response sent by the main device, the login confirmation response is used for indicating whether to allow the terminal to log in the target account, and the server allows or prohibits the target account from logging in the terminal according to the login confirmation response. According to the method and the device, the danger that privacy of the user is revealed because other people can log in the account through other terminals when the account and the password are revealed can be avoided, and the safety of the account is improved.
Fig. 4 is a flowchart illustrating an account login method according to an exemplary embodiment, where the method may be used in the implementation environment shown in fig. 1, in this embodiment, a server may be the server 400 in the implementation environment shown in fig. 1, and a master device may be the terminal 100 in the implementation environment shown in fig. 1, and as shown in fig. 4, the method includes the following steps.
In step 401, the server receives an account login request sent by a terminal, where the account login request includes: account information of the target account and the identifier of the terminal.
The account information of the target account includes an account name and a login password of the target account, and the identifier of the terminal may be, for example, an IMEI (international mobile equipment identity) address, an MAC (media access control) address, and the like of the terminal.
In step 402, after the server successfully authenticates the account information, it determines whether the identifier of the terminal is an identifier of a device bound to the target account.
After receiving an account login request sent by a terminal, a server performs authentication according to account information in the account login request, where the authentication process may be, for example, to determine whether an account name of a target account included in the account information matches a login password, and if the login password matches the account name, the authentication is successful. And after the authentication is passed, judging whether the terminal is the identifier of the equipment bound with the target account according to the identifier of the terminal, thereby identifying whether the terminal is the terminal bound with the target account. When the identifier of the terminal is not the identifier of the device bound to the target account, performing step 403; and when the identifier of the terminal is the identifier of the equipment bound with the target account, allowing the target account to log in the terminal.
In step 403, when the identifier of the terminal is not the identifier of the device bound to the target account, the server sends a login confirmation request to a preset host device, where the login confirmation request is used to request the host device whether to allow the login of the target account in the terminal.
In step 404, the master device presents a login confirmation request to the user.
For example, the login confirmation request may include an identifier of the terminal and a current location of the terminal, where the identifier of the terminal may be an IMEI, a MAC address, and the like of the terminal, and the location information may be location information of the terminal, such as longitude and latitude coordinates. Therefore, when a login confirmation request is presented to a user, the terminal can be positioned on a map according to the position information when the identifier of the terminal is displayed, so that the user can judge whether the terminal which requests to login a target account currently is a known terminal or not through the identifier of the terminal, and judge whether the terminal is safe or not according to the position information of the terminal, thereby further determining whether the terminal is allowed to login the target account or not.
In step 405, a login confirmation response is generated according to the operation of the user on the login confirmation request, and the login confirmation response is used for indicating whether the login of the target account is allowed to be performed in the terminal.
The operation of the user on the login confirmation request may include an operation of allowing the terminal to login the target account and an operation of prohibiting the terminal from login the target account, and correspondingly, login confirmation responses generated according to the two operations are also used to indicate whether the terminal is allowed to login the target account or is prohibited from login the target account.
In step 406, the master device sends a login confirmation response to the server.
In step 407, the server allows or prohibits the target account to log on the terminal according to the login confirmation response.
Fig. 5 is a flowchart illustrating another account login method according to an exemplary embodiment, and as shown in fig. 5, on the basis of the method shown in fig. 4, the method may further include:
in step 408, when a login confirmation response sent by the primary device is not received within a preset time period from the time when the login confirmation request is sent, the server sequentially sends the login confirmation requests to other devices in the devices bound with the target account according to a preset sequence, and allows or prohibits the target account from logging in the terminal according to the login confirmation response received for the first time.
Or,
in step 409, when a login confirmation response sent by the host device is not received within a preset time period from the time when the login confirmation request is sent, the server allows the target account to log in the terminal.
Fig. 6 is a flowchart illustrating a further account login method according to an exemplary embodiment, and as shown in fig. 6, on the basis of the method shown in fig. 4, the method may further include:
in step 410, when the login confirmation response sent by the host device is not received within a preset time period from the time when the login confirmation request is sent, the server obtains a history login confirmation response sent by the host device before the login confirmation request is sent.
In step 411, the server counts the number of times of history of allowing the login of the target account at the terminal based on the history login confirmation response.
In step 412, when the historical times is greater than a preset time threshold, allowing the target account to log in on the terminal.
In step 413, when the historical number of times is not greater than the preset number threshold, the target account is prohibited from logging in the terminal.
Optionally, in order to further improve the security of the account number, the device bound to the target account number is the primary device, and under this condition, step 402 may be understood as determining whether the identifier of the terminal is the identifier of the primary device bound to the target account number, so as to identify whether the terminal requesting to log in the target account number is the primary device, and when the terminal is not the identifier of the primary device, sending a login confirmation request to a preset primary device, which is inconvenient for subsequent steps and is not described again.
According to the account login method provided by the embodiment of the invention, after receiving an account login request which is sent by a terminal and comprises account information of a target account and an identifier of the terminal, a server authenticates the account information, and after the account information is successfully authenticated, whether the identifier of the terminal is the identifier of equipment bound with the target account is judged; when the identifier of the terminal is not the identifier of the device bound with the target account, the server sends a login confirmation request to a preset main device, the login confirmation request is used for requesting the main device whether to allow the terminal to log in the target account, finally, the server receives a login confirmation response sent by the main device, the login confirmation response is used for indicating whether to allow the terminal to log in the target account, and the server allows or prohibits the target account from logging in the terminal according to the login confirmation response. According to the method and the device, the danger that privacy of the user is revealed because other people can log in the account through other terminals when the account and the password are revealed can be avoided, and the safety of the account is improved.
Fig. 7 is a block diagram of an account registration apparatus according to an exemplary embodiment, which may be used to execute the method shown in fig. 2 or fig. 4, the account registration apparatus 700 may be used in a server, the account registration apparatus 700 may form part or all of the server in software or hardware or a combination of the two, and the server may be the server 400 shown in the implementation environment shown in fig. 1. Referring to fig. 7, the apparatus includes a receiving module 710, a determining module 720, a requesting module 730, and a processing module 740.
A receiving module 710 configured to receive an account login request sent by a terminal, where the account login request includes: account information of the target account and the identification of the terminal;
a determining module 720, configured to determine whether the identifier of the terminal is an identifier of a device bound to the target account after the account information is successfully authenticated;
a request module 730, configured to send a login confirmation request to a preset primary device when the identifier of the terminal is not the identifier of the device bound to the target account, where the login confirmation request is used to request the primary device whether to allow the login of the target account in the terminal;
the receiving module 710 is further configured to receive a login confirmation response sent by the master device, where the login confirmation response is used to indicate whether to allow the terminal to log in the target account;
and the processing module 740 is configured to allow or prohibit the target account to log in the terminal according to the login confirmation response.
Optionally, the processing module 740 is further configured to:
and when the identifier of the terminal is the identifier of the equipment bound with the target account, allowing the target account to log in the terminal.
Optionally, the request module 730 is further configured to: when a login confirmation response sent by the master device is not received within a preset time period from the time when the login confirmation request is sent, sequentially sending the login confirmation request to other devices in the devices bound to the target account according to a preset sequence, wherein the processing module is further configured to: allowing or prohibiting the target account to log in the terminal according to the first received login confirmation response;
alternatively, the processing module 740 is further configured to: and when the login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request, allowing the target account to log in the terminal.
Optionally, fig. 8 is a block diagram of another account login apparatus according to an exemplary embodiment, as shown in fig. 8, on the basis of the apparatus shown in fig. 7, the apparatus 700 further includes:
an obtaining module 750 configured to obtain a historical login confirmation response sent by the host device before sending the login confirmation request when a login confirmation response sent by the host device is not received within a preset time period from a time when the login confirmation request is sent;
a counting module 760 configured to count the number of history times of allowing the login of the target account at the terminal according to the history login confirmation response;
the processing module 740 is further configured to allow the target account to log in the terminal when the historical times are greater than a preset time threshold;
the processing module 740 is further configured to prohibit the target account from logging in the terminal when the historical times are not greater than a preset time threshold.
The account login device provided by the embodiment of the disclosure receives an account login request sent by a terminal, wherein the account login request comprises: the account information of the target account and the identifier of the terminal are judged, and whether the identifier of the terminal is the identifier of the device bound with the target account is judged after the account information is successfully authenticated; when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal; finally, receiving a login confirmation response sent by the main equipment, wherein the login confirmation response is used for indicating whether the login of the target account is allowed to be carried out at the terminal; and according to the login confirmation response, allowing or prohibiting the target account to login on the terminal. According to the method and the device, the danger that privacy of the user is revealed because other people can log in the account through other terminals when the account and the password are revealed can be avoided, and the safety of the account is improved.
Fig. 9 is a block diagram of another account registration apparatus according to an exemplary embodiment, which may be used to execute the method shown in fig. 3 or fig. 4, where the account registration apparatus 900 may be used in a host device, and the account registration apparatus 900 may form part or all of the host device in software or hardware or a combination of the two, and the host device may be the terminal 100 shown in the implementation environment shown in fig. 1. Referring to fig. 9, the apparatus includes: a receiving module 910, a display module 920, a response module 930, and a transmitting module 940.
A receiving module 910, configured to receive a login confirmation request sent by a server, where the login confirmation request is sent to a preset primary device when the server determines that an identifier of a terminal included in an account login request sent by a terminal is not an identifier of a device bound to a target account after successfully authenticating account information of the target account included in the account login request sent by the terminal, and the login confirmation request is used to request the primary device whether to allow the terminal to log in the target account;
a display module 920 configured to present the login confirmation request to a user;
a response module 930 configured to generate a login confirmation response according to an operation of the user on the login confirmation request, where the login confirmation response is used to indicate whether to allow the login of the target account in the terminal;
a sending module 940 configured to send the login confirmation response to the server.
Wherein the login confirmation request comprises: the identification of the terminal and the current position information of the terminal.
In summary, the account login device provided by the present disclosure can avoid the danger of privacy disclosure of a user caused by the fact that others can log in the account through other terminals when the account and the password are revealed, and improve the security of the account.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 10 is a block diagram illustrating an account login apparatus 1000 according to an exemplary embodiment. For example, the apparatus 1000 may be provided as a server, such as the server 400 shown in fig. 1. Referring to fig. 10, the apparatus 1000 includes a processing component 1022 that further includes one or more processors and memory resources, represented by memory 1032, for storing instructions, such as application programs, that are executable by the processing component 1022. The application programs stored in memory 1032 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1022 is configured to execute instructions to perform the account login method described above.
The device 1000 may also include a power supply component 1026 configured to perform power management for the device 1000, a wired or wireless network interface 1050 configured to connect the device 1000 to a network, and an input/output (I/O) interface 1058. The device 1000 may operate based on an operating system stored in memory 1032, such as a Windows Server, MacOSXTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
Fig. 11 is a block diagram illustrating an account login apparatus 1100 according to an example embodiment. It is applicable to a terminal, which may be a master device, such as the terminal 100 shown in fig. 1. The apparatus 1100 may be, for example, a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 11, apparatus 1100 may include one or more of the following components: a processing component 1102, a memory 1104, a power component 1106, a multimedia component 1108, an audio component 1110, an input/output (I/O) interface 1112, a sensor component 1114, and a communication component 1116.
The processing component 1102 generally controls the overall operation of the device 1100, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. Processing component 1102 may include one or more processors 1120 to execute instructions to perform all or a portion of the steps of the account login method described above. Further, the processing component 1102 may include one or more modules that facilitate interaction between the processing component 1102 and other components. For example, the processing component 1102 may include a multimedia module to facilitate interaction between the multimedia component 1108 and the processing component 1102.
The memory 1104 is configured to store various types of data to support operations at the apparatus 1100. Examples of such data include instructions for any application or method operating on device 1100, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1104 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
Power components 1106 provide power to the various components of device 1100. The power components 1106 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the apparatus 1100.
The multimedia component 1108 includes a screen that provides an output interface between the device 1100 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1108 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 1100 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 1110 is configured to output and/or input audio signals. For example, the audio component 1110 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 1100 is in operating modes, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 1104 or transmitted via the communication component 1116. In some embodiments, the audio assembly 1110 further includes a speaker for outputting audio signals.
The I/O interface 1112 provides an interface between the processing component 1102 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 1114 includes one or more sensors for providing various aspects of state assessment for the apparatus 1100. For example, the sensor assembly 1114 may detect an open/closed state of the apparatus 1100, the relative positioning of components, such as a display and keypad of the apparatus 1100, the sensor assembly 1114 may also detect a change in position of the apparatus 1100 or a component of the apparatus 1100, the presence or absence of user contact with the apparatus 1100, orientation or acceleration/deceleration of the apparatus 1100, and a change in temperature of the apparatus 1100. The sensor assembly 1114 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1114 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1114 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 1116 is configured to facilitate wired or wireless communication between the apparatus 1100 and other devices. The apparatus 1100 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1116 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1116 also includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 1100 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above account login methods.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 1104 comprising instructions, executable by the processor 1120 of the device 1100 to perform the account login method described above is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (16)
1. An account login method is used for a server and comprises the following steps:
receiving an account login request sent by a terminal, wherein the account login request comprises: account information of the target account and the identification of the terminal;
after the account information is successfully authenticated, judging whether the identifier of the terminal is the identifier of the device bound with the target account;
when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal;
receiving a login confirmation response sent by the main device, wherein the login confirmation response is used for indicating whether the terminal is allowed to log in the target account;
and allowing or prohibiting the target account to log in the terminal according to the login confirmation response.
2. The method of claim 1, further comprising:
and when the identifier of the terminal is the identifier of the equipment bound with the target account, allowing the target account to log in the terminal.
3. The method of claim 1, further comprising:
when a login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request, sequentially sending the login confirmation request to other equipment in the equipment bound with the target account according to a preset sequence, and allowing or forbidding the target account to log in the terminal according to the login confirmation response received for the first time;
or, when a login confirmation response sent by the master device is not received within a preset time period from the time when the login confirmation request is sent, allowing the target account to log in the terminal.
4. The method of claim 1, further comprising:
when a login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request, obtaining a historical login confirmation response sent by the main equipment before the login confirmation request is sent;
according to the historical login confirmation response, counting the historical times of allowing the terminal to log in the target account;
when the historical times are larger than a preset time threshold, allowing the target account to log in the terminal;
and when the historical times are not greater than a preset time threshold, forbidding the target account to log in the terminal.
5. The method of any one of claims 1 to 4, wherein the device bound to the target account is the primary device.
6. An account login method is used for a primary device, and comprises the following steps:
receiving a login confirmation request sent by a server, wherein the login confirmation request is sent to a preset main device when the server judges that the identifier of a terminal contained in an account login request is not the identifier of a device bound with a target account after successfully authenticating account information of the target account contained in the account login request sent by a terminal, and the login confirmation request is used for requesting the main device whether to allow the terminal to log in the target account;
presenting the login confirmation request to a user;
generating a login confirmation response according to the operation of the user on the login confirmation request, wherein the login confirmation response is used for indicating whether the login of the target account is allowed to be performed on the terminal;
and sending the login confirmation response to the server.
7. The method of claim 6, wherein the login confirmation request comprises: the identification of the terminal and the current position information of the terminal.
8. An account login device, for a server, comprising:
the terminal comprises a receiving module and a sending module, wherein the receiving module is configured to receive an account login request sent by the terminal, and the account login request comprises: account information of the target account and the identification of the terminal;
the judging module is configured to judge whether the identifier of the terminal is the identifier of the device bound with the target account number after the account number information is successfully authenticated;
the request module is configured to send a login confirmation request to a preset main device when the identifier of the terminal is not the identifier of the device bound with the target account, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal;
the receiving module is further configured to receive a login confirmation response sent by the master device, where the login confirmation response is used to indicate whether to allow the terminal to log in the target account;
and the processing module is configured to allow or prohibit the target account to log in the terminal according to the login confirmation response.
9. The apparatus of claim 8, wherein the processing module is further configured to:
and when the identifier of the terminal is the identifier of the equipment bound with the target account, allowing the target account to log in the terminal.
10. The apparatus of claim 8,
the request module is further configured to: when a login confirmation response sent by the master device is not received within a preset time period from the time when the login confirmation request is sent, sequentially sending the login confirmation request to other devices in the devices bound to the target account according to a preset sequence, wherein the processing module is further configured to: allowing or prohibiting the target account to log in the terminal according to the first received login confirmation response;
alternatively, the processing module is further configured to: and when the login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request, allowing the target account to log in the terminal.
11. The apparatus of claim 8, further comprising:
the acquisition module is configured to acquire a historical login confirmation response sent by the main equipment before the login confirmation request is sent when the login confirmation response sent by the main equipment is not received within a preset time period from the moment of sending the login confirmation request;
a counting module configured to count the number of history times of allowing the login of the target account at the terminal according to the history login confirmation response;
the processing module is further configured to allow the target account to log in the terminal when the historical times are greater than a preset time threshold;
the processing module is further configured to prohibit the target account from logging in the terminal when the historical times are not greater than a preset times threshold.
12. The apparatus according to any one of claims 8 to 11, wherein the device bound to the target account is the primary device.
13. An account login apparatus, for a primary device, comprising:
the system comprises a receiving module, a login confirmation request and a processing module, wherein the login confirmation request is sent to preset main equipment when the server judges that the identifier of a terminal contained in an account login request is not the identifier of equipment bound with a target account after successfully authenticating account information of the target account contained in the account login request sent by a terminal, and the login confirmation request is used for requesting the main equipment whether to allow the terminal to log in the target account;
a display module configured to present the login confirmation request to a user;
a response module configured to generate a login confirmation response according to an operation of a user on the login confirmation request, where the login confirmation response is used to indicate whether to allow the login of the target account in the terminal;
a sending module configured to send the login confirmation response to the server.
14. The apparatus of claim 13, wherein the login confirmation request comprises: the identification of the terminal and the current position information of the terminal.
15. An account login device, for a server, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving an account login request sent by a terminal, wherein the account login request comprises: account information of the target account and the identification of the terminal;
after the account information is successfully authenticated, judging whether the identifier of the terminal is the identifier of the device bound with the target account;
when the identifier of the terminal is not the identifier of the device bound with the target account, sending a login confirmation request to a preset main device, wherein the login confirmation request is used for requesting the main device whether to allow the login of the target account in the terminal;
receiving a login confirmation response sent by the main device, wherein the login confirmation response is used for indicating whether the terminal is allowed to log in the target account;
and allowing or prohibiting the target account to log in the terminal according to the login confirmation response.
16. An account login apparatus, for a primary device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving a login confirmation request sent by a server, wherein the login confirmation request is sent to a preset main device when the server judges that the identifier of a terminal contained in an account login request is not the identifier of a device bound with a target account after successfully authenticating account information of the target account contained in the account login request sent by a terminal, and the login confirmation request is used for requesting the main device whether to allow the terminal to log in the target account;
presenting the login confirmation request to a user;
generating a login confirmation response according to the operation of the user on the login confirmation request, wherein the login confirmation response is used for indicating whether the login of the target account is allowed to be performed on the terminal;
and sending the login confirmation response to the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610194789.8A CN105656948A (en) | 2016-03-30 | 2016-03-30 | Account login method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610194789.8A CN105656948A (en) | 2016-03-30 | 2016-03-30 | Account login method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105656948A true CN105656948A (en) | 2016-06-08 |
Family
ID=56495942
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610194789.8A Pending CN105656948A (en) | 2016-03-30 | 2016-03-30 | Account login method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105656948A (en) |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105915947A (en) * | 2016-06-29 | 2016-08-31 | 乐视控股（北京）有限公司 | Method, apparatus and system for maintaining watching tickets for online cinema |
| CN106127482A (en) * | 2016-06-30 | 2016-11-16 | 联想(北京)有限公司 | A kind of information processing method and electronic equipment |
| CN106656985A (en) * | 2016-10-25 | 2017-05-10 | 广东欧珀移动通信有限公司 | Backup account login method, device and system |
| CN106656978A (en) * | 2016-10-19 | 2017-05-10 | 广东欧珀移动通信有限公司 | Account login method and server |
| CN106993003A (en) * | 2017-06-08 | 2017-07-28 | 湖南暄程科技有限公司 | A kind of hospital's outer net login method and system |
| CN107222481A (en) * | 2017-05-31 | 2017-09-29 | 深圳云天励飞技术有限公司 | The method and apparatus of User logs in data query system |
| CN107229846A (en) * | 2017-05-31 | 2017-10-03 | 奇酷互联网络科技（深圳）有限公司 | Information protecting method, device, mobile terminal and read/write memory medium |
| WO2017177571A1 (en) * | 2016-04-14 | 2017-10-19 | 北京小米移动软件有限公司 | Method, device and system for executing service processing |
| CN107612902A (en) * | 2017-09-11 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of Windows system logins authentication method and system |
| CN107819786A (en) * | 2017-11-28 | 2018-03-20 | 郑州云海信息技术有限公司 | A kind of operating system login system and method based on QQ certifications |
| CN107888592A (en) * | 2017-11-13 | 2018-04-06 | 杭州迪普科技股份有限公司 | A kind of VPN login authentication methods and device |
| CN108156169A (en) * | 2017-12-28 | 2018-06-12 | 惠州Tcl家电集团有限公司 | Account login validation method, system and computer readable storage medium |
| CN108200192A (en) * | 2018-01-30 | 2018-06-22 | 北京小米移动软件有限公司 | The method and device of control terminal apparatus bound |
| CN109040146A (en) * | 2018-10-25 | 2018-12-18 | 平安科技（深圳）有限公司 | Account logs in authorization method, server, computer equipment and storage medium |
| CN109474838A (en) * | 2018-11-01 | 2019-03-15 | 腾讯科技（深圳）有限公司 | A kind of data processing method, equipment, system and storage medium |
| CN109684799A (en) * | 2018-08-21 | 2019-04-26 | 平安普惠企业管理有限公司 | Account logon method, entering device, Account Logon equipment and storage medium |
| CN111539737A (en) * | 2020-04-27 | 2020-08-14 | 支付宝(杭州)信息技术有限公司 | Account risk detection method, device and equipment |
| CN111581616A (en) * | 2020-05-11 | 2020-08-25 | 青岛聚好联科技有限公司 | Multi-terminal login control method and device |
| CN111582876A (en) * | 2020-05-09 | 2020-08-25 | 腾讯科技（深圳）有限公司 | Operation authentication method, device, storage medium and electronic device |
| CN111741466A (en) * | 2020-06-15 | 2020-10-02 | 北京智明星通科技股份有限公司 | Method, device and equipment for retrieving password by linking equipment based on game account |
| CN112069486A (en) * | 2020-09-01 | 2020-12-11 | 中国联合网络通信集团有限公司 | Multi-device account login method, account platform and first device |
| CN113162935A (en) * | 2021-04-25 | 2021-07-23 | 东风汽车集团股份有限公司 | Method and system for preventing abnormal login of vehicle-mounted terminal vehicle owner account |
| CN113557703A (en) * | 2019-03-19 | 2021-10-26 | 华为技术有限公司 | Authentication method and device for network camera |
| CN113595871A (en) * | 2021-06-30 | 2021-11-02 | 深圳市广和通无线股份有限公司 | Account login method and device, computer equipment and storage medium |
| CN114172716A (en) * | 2021-12-02 | 2022-03-11 | 北京金山云网络技术有限公司 | Login method, login device, electronic equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104125062A (en) * | 2013-04-26 | 2014-10-29 | 腾讯科技（深圳）有限公司 | Login method, device, login authentication device, server, terminals and system |
-
2016
- 2016-03-30 CN CN201610194789.8A patent/CN105656948A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104125062A (en) * | 2013-04-26 | 2014-10-29 | 腾讯科技（深圳）有限公司 | Login method, device, login authentication device, server, terminals and system |
Cited By (34)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017177571A1 (en) * | 2016-04-14 | 2017-10-19 | 北京小米移动软件有限公司 | Method, device and system for executing service processing |
| CN105915947A (en) * | 2016-06-29 | 2016-08-31 | 乐视控股（北京）有限公司 | Method, apparatus and system for maintaining watching tickets for online cinema |
| CN106127482A (en) * | 2016-06-30 | 2016-11-16 | 联想(北京)有限公司 | A kind of information processing method and electronic equipment |
| CN106656978A (en) * | 2016-10-19 | 2017-05-10 | 广东欧珀移动通信有限公司 | Account login method and server |
| CN106656985B (en) * | 2016-10-25 | 2020-03-10 | Oppo广东移动通信有限公司 | Backup account login method, device and system |
| CN106656985A (en) * | 2016-10-25 | 2017-05-10 | 广东欧珀移动通信有限公司 | Backup account login method, device and system |
| CN107222481A (en) * | 2017-05-31 | 2017-09-29 | 深圳云天励飞技术有限公司 | The method and apparatus of User logs in data query system |
| CN107229846A (en) * | 2017-05-31 | 2017-10-03 | 奇酷互联网络科技（深圳）有限公司 | Information protecting method, device, mobile terminal and read/write memory medium |
| CN106993003A (en) * | 2017-06-08 | 2017-07-28 | 湖南暄程科技有限公司 | A kind of hospital's outer net login method and system |
| CN107612902A (en) * | 2017-09-11 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of Windows system logins authentication method and system |
| CN107612902B (en) * | 2017-09-11 | 2020-09-18 | 苏州浪潮智能科技有限公司 | Windows system login authentication method and system |
| CN107888592A (en) * | 2017-11-13 | 2018-04-06 | 杭州迪普科技股份有限公司 | A kind of VPN login authentication methods and device |
| CN107819786A (en) * | 2017-11-28 | 2018-03-20 | 郑州云海信息技术有限公司 | A kind of operating system login system and method based on QQ certifications |
| CN107819786B (en) * | 2017-11-28 | 2021-06-15 | 郑州云海信息技术有限公司 | QQ authentication-based operating system login system and method |
| CN108156169A (en) * | 2017-12-28 | 2018-06-12 | 惠州Tcl家电集团有限公司 | Account login validation method, system and computer readable storage medium |
| CN108200192A (en) * | 2018-01-30 | 2018-06-22 | 北京小米移动软件有限公司 | The method and device of control terminal apparatus bound |
| CN109684799B (en) * | 2018-08-21 | 2023-12-26 | Tcl金融科技(深圳)有限公司 | Account login method, login device, account login equipment and storage medium |
| CN109684799A (en) * | 2018-08-21 | 2019-04-26 | 平安普惠企业管理有限公司 | Account logon method, entering device, Account Logon equipment and storage medium |
| CN109040146A (en) * | 2018-10-25 | 2018-12-18 | 平安科技（深圳）有限公司 | Account logs in authorization method, server, computer equipment and storage medium |
| CN109474838B (en) * | 2018-11-01 | 2020-10-30 | 腾讯科技（深圳）有限公司 | Data processing method, device, system and storage medium |
| CN109474838A (en) * | 2018-11-01 | 2019-03-15 | 腾讯科技（深圳）有限公司 | A kind of data processing method, equipment, system and storage medium |
| CN113557703B (en) * | 2019-03-19 | 2024-05-14 | 华为技术有限公司 | Authentication method and device of network camera |
| CN113557703A (en) * | 2019-03-19 | 2021-10-26 | 华为技术有限公司 | Authentication method and device for network camera |
| CN111539737A (en) * | 2020-04-27 | 2020-08-14 | 支付宝(杭州)信息技术有限公司 | Account risk detection method, device and equipment |
| CN111582876A (en) * | 2020-05-09 | 2020-08-25 | 腾讯科技（深圳）有限公司 | Operation authentication method, device, storage medium and electronic device |
| CN111581616A (en) * | 2020-05-11 | 2020-08-25 | 青岛聚好联科技有限公司 | Multi-terminal login control method and device |
| CN111741466A (en) * | 2020-06-15 | 2020-10-02 | 北京智明星通科技股份有限公司 | Method, device and equipment for retrieving password by linking equipment based on game account |
| CN112069486A (en) * | 2020-09-01 | 2020-12-11 | 中国联合网络通信集团有限公司 | Multi-device account login method, account platform and first device |
| CN112069486B (en) * | 2020-09-01 | 2023-05-12 | 中国联合网络通信集团有限公司 | Multi-device account login method, account platform and first device |
| CN113162935B (en) * | 2021-04-25 | 2022-06-24 | 东风汽车集团股份有限公司 | Method and system for preventing abnormal login of vehicle-mounted terminal vehicle owner account |
| CN113162935A (en) * | 2021-04-25 | 2021-07-23 | 东风汽车集团股份有限公司 | Method and system for preventing abnormal login of vehicle-mounted terminal vehicle owner account |
| CN113595871B (en) * | 2021-06-30 | 2022-10-14 | 深圳市广和通无线股份有限公司 | Account login method and device, computer equipment and storage medium |
| CN113595871A (en) * | 2021-06-30 | 2021-11-02 | 深圳市广和通无线股份有限公司 | Account login method and device, computer equipment and storage medium |
| CN114172716A (en) * | 2021-12-02 | 2022-03-11 | 北京金山云网络技术有限公司 | Login method, login device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105656948A (en) | Account login method and device | |
| CN106603667B (en) | Screen information sharing method and device | |
| CN106453052B (en) | Message interaction method and device | |
| EP2985975A1 (en) | Method, apparatus and system for authenticating access and computer program | |
| US20170163626A1 (en) | Method and device for network access of a smart terminal device | |
| US10608988B2 (en) | Method and apparatus for bluetooth-based identity recognition | |
| US10102505B2 (en) | Server-implemented method, terminal-implemented method and device for acquiring business card information | |
| CN105847243B (en) | Method and device for accessing intelligent camera | |
| CN106209800B (en) | Equipment Authority sharing method and apparatus | |
| US10313870B2 (en) | Identity verification method and apparatus, and storage medium | |
| CN105491229B (en) | The method and apparatus of remote control mobile terminal | |
| CN106790043B (en) | Method and device for sending message in live broadcast application | |
| US20170105237A1 (en) | Methods and apparatuses for network connection | |
| US20160294805A1 (en) | Method and terminal device for accessing network | |
| CN109039860B (en) | Method and device for sending and displaying message and method and device for identity authentication | |
| CN108811179B (en) | Wireless network connection method, device and storage medium | |
| CN106210238B (en) | Short message storage method and device | |
| CN110049062B (en) | Verification code verification method, device, system, server, electronic equipment and storage medium | |
| US20180341953A1 (en) | Method and apparatus for reporting loss of card or device associated with account number or stolen of account number | |
| CN104703252A (en) | Terminal device accessing into wireless network method and device | |
| CN107959757B (en) | User information processing method and device, APP server and terminal equipment | |
| CN106302528B (en) | Short message processing method and device | |
| EP3226128A1 (en) | Method and device for online payment | |
| CN105681261A (en) | Security authentication method and apparatus | |
| CN107231338B (en) | Network connection method, device and device for network connection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160608 |