CN104917755A - Login method based on mobile communication terminal and short message - Google Patents
Login method based on mobile communication terminal and short message Download PDFInfo
- Publication number
- CN104917755A CN104917755A CN201510225152.6A CN201510225152A CN104917755A CN 104917755 A CN104917755 A CN 104917755A CN 201510225152 A CN201510225152 A CN 201510225152A CN 104917755 A CN104917755 A CN 104917755A
- Authority
- CN
- China
- Prior art keywords
- user
- login
- authentication data
- application system
- mobile communication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
- H04L63/067—Network architectures or network communication protocols for network security for supporting key management in a packet data network using one-time keys
-
- 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/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a login method based on a mobile communication terminal and a short message. The method comprises the following steps: when a user uses an application client to access an application system, the application system sends login identification data 1 to a mobile communication terminal of the user through a short message sending and receiving system on one hand, and on the other hand, the application system returns login identification data 2 to the application client and displays the login identification data 2 in the form of a barcode; the user uses the mobile communication terminal to scan the barcode displayed on the application client, and a mobile login assistant in the mobile communication terminal acquires the login identification data 2 from the barcode and the login identification data 1 from a short message box of the mobile communication terminal, combines the login identification data 1 and the login identification data 2, and submits the combined login identification data to the application system or sends the combined login identification data to the short message sending and receiving system for acquisition by the application system; and the application system determines whether the user passes login identification and decides whether or not to allow the user to access the application system by judging whether the received or acquired combined login identification data conforms to the requirements of login identification. By adopting the method, user password theft by Trojans and listeners is avoided. The method is safe and easy to operate.
Description
Technical field
The invention belongs to field of information security technology, particularly a kind of login (Logon or Login) method based on mobile communication terminal and note.
Background technology
Account name/password is that current information system (application system) user logs in method the most frequently used in discriminating, but common user name/static password scheme is dangerous is well-known: one is conveniently, people usually adopt simply, the password of easily memory, this causes password to be easy to be guessed, two is PE online in Internet bar etc., and password is easy to be stolen by wooden horse, keyboard oracle listener.
For the unsafe problem of static password, in the occasion that some safety requirements are higher, people have employed dynamic password (also claiming one-time password) scheme, but this scheme also has problems: although one is that safety wanted in dynamic password relative quiescent password, but the program is attacked and causes the thing of user's property loss still to happen occasionally, Dynamic Password Scheme as certain famous online game provider domestic suffers attack to cause player to occur loss of assets, the dynamic password system of certain bank net domestic is caused the Event Descriptions such as the wealth loss of client dynamic password also to there is weakness by attack, two is that dynamic password requirement user uses a special hardware unit being called dynamic password token, this brings extra cost burden to user.Along with the appearance of mobile phone, mobile phone dynamic password also starts to log in discriminating for the user of information system, but this scheme uses the attack still cannot resisting wooden horse, keyboard oracle listener in the public place such as Internet bar: wooden horse, keyboard oracle listener intercept and capture user by the dynamic password of input through keyboard after send the Hacker Program in a machine or strange land immediately to, thus fake user login system (this is to static password and all effective attack method of dynamic password).
In the information system (as Net silver) that some safety requirements are very high, people adopt USB Key hardware cryptographic device to carry out login and differentiate, deposit digital certificate and the private key thereof of user in USB Key, realize user security log in by cryptographic technique.Although this user logs in authentication schemes safety, also have problems: one is at public internet café, and the USB interface of computer is usually sealed up for safekeeping or unloads, therefore, you cannot use USB Key to carry out register at all, and two is use USB Key to produce extra-pay, and user is generally unwilling to adopt.
Summary of the invention
The object of the invention is to propose that a kind of safe and convenient and applicable public place uses based on the login method of mobile communication terminal and note.
To achieve these goals, the technical solution adopted in the present invention is:
Based on a login method for mobile communication terminal and note, described method is as follows:
User is bound with the mobile communication number (i.e. phone number) of user the account of application system; Described application system is a system being provided function services by network to user; User is by operating in the applications client access application system in subscriber computer; Described applications client comprises private client and browser general purpose client; For the session connection between applications client and application system, application system is assigned a Session ID (Sess ion ID) and establishment and maintenance have a session object, session object is associated with the Session ID of the session connection between applications client with application system, thus session connection is corresponding with session object; Described session connection refers to that the logic between applications client and application system connects; Be provided with in described session object and indicate that whether user is by logging in the mark differentiated;
User mobile communication terminal (i.e. mobile phone) in installs and run one be called mobile login assistant for help user application system complete log in discriminating program; Described mobile communication terminal is the mobile communication terminal device that the user of access application system holds; Described mobile communication terminal has camera and bar code scan program (comprising the program of dynamic base, class libraries and independent operating) to read for bar code scan and barcode data; Described bar code scan program is moved mobile login assistant and calls, for obtaining the login authentication data that applications client shows with bar code form;
Install and run one for sending the short message receiving and sending system logging in authentication data and receive the login authentication data that mobile login assistant is sent by mobile communication terminal to the mobile communication terminal of user; Described short message receiving and sending system is the independently assembly of application system that will access of system or user; Described short message receiving and sending system is to there being a mobile communication number;
The operation process that user logs in application system is as follows:
The first step: user uses applications client request to log in application system and submits the account name in application system to;
Second step: application system obtains the mobile communication number (i.e. phone number) of user by the account name that user submits to from the user account database of application system, then by short message receiving and sending system, login authentication data 1 is sent to user's mobile communication terminal on the one hand, on the other hand user is logged in authentication data 2 and turn back to the applications client of user and the login authentication data 2 returned is shown in applications client with the form of bar code (as Quick Response Code);
3rd step: user uses the bar code (namely family logs in authentication data 2) running the mobile communication terminal scanning applications client display having mobile login assistant;
4th step: mobile login assistant obtains the login authentication data 2 of user from the bar code of scanning, obtains the login authentication data 1 that application system sends from the note case of mobile communication terminal; Combination logs in authentication data 1 and logs in authentication data 2 and forms the login authentication data after merging;
5th step: the login authentication data after merging is submitted to application system by data network by mobile communication terminal by mobile login assistant, or the login authentication data after merging is sent to short message receiving and sending system with short message mode and is obtained by application system;
6th step: application system is received or gets user and moves login assistant and to be submitted to by mobile communication terminal or after login authentication data after the merging that sends, check determine user move login assistant submit to or send merging after login authentication data whether meet log in differentiate requirement, if meet, be then differentiated user label by logging in, and allow user to log in application system by applications client; Otherwise refusal user accesses and continues to require that user carries out login and differentiates.
The login authentication data 1 that described application system is sent to user's mobile communication terminal at described second step and turn back to user's applications client login authentication data 2 in comprise following information simultaneously: the Session ID (Session ID) of the session connection between user's applications client and application system and random word string, wherein, logging in authentication data 1 with logging in the Session ID comprised in authentication data 2 is identical (for being associated with login authentication data 2 by login authentication data 1), and the random word string comprised is then different; And application system turns back to the mobile communication number also including short message receiving and sending system in the login authentication data 2 of applications client;
If the login authentication data after merging is submitted to application system in described 5th step (by mobile communication terminal) by data network by described mobile login assistant, then include the network address (as http address) of application system in the login authentication data 1 that sends of application system and/or the login authentication data 2 that returns.
Described mobile login assistant obtains the mobile communication number of short message receiving and sending system authentication data 2 from logging in, and number obtains the login authentication data 1 that application system sends in the note case of mobile communication terminal accordingly.
After described mobile login assistant obtains the login authentication data 1 that application system sends and the login authentication data 2 turning back to applications client, the random word string logged in two in authentication datas merges, and forms the login authentication data after merging; Include the Session ID identical with logging in authentication data 2 with logging in authentication data 1 in login authentication data after merging, and have the random word string after merging.
Login authentication data 1 to be sent to mobile communication terminal and while authentication data 2 turns back to applications client by login at described second step by application system, is kept in session object corresponding to session connection between application system with applications client after the random word string the two comprised merges.
Described application system is received by data network or gets user from short message receiving and sending system and moves login assistant and to be submitted to by mobile communication terminal or after login authentication data after the merging that sends, check that determining whether the login authentication data after merging meets to log in differentiates requirement as follows, and after inspection is determined to meet the requirements by user label for differentiating by logging in:
The random word string after the random word string obtaining the login authentication data 1 that (before) is preserved in the session object corresponding to the Session ID (in application system) the login authentication data after the merging of login assistant submission or transmission and the random word string merging logging in authentication data 2 is moved from user, then compare the random word string after the merging obtained from session object with user move login assistant to be submitted to by mobile communication terminal or random word string after merging in login authentication data after the merging that sends whether identical, if identical, then determine user move login assistant submit to or send merging after login authentication data meet log in differentiate requirement, and be differentiated user ID by logging in session object, otherwise, determine user move login assistant submit to or send merging after login authentication data do not meet log in differentiate requirement.
If user is exactly the mobile communication number of user at the account name of application system, then at described second step, whether application system has corresponding account by the inquiring user in the user account database of application system of the mobile communication number as account name that user submits to, if have, then by short message receiving and sending system, login authentication data 1 is sent to user's mobile communication terminal.
Dual login is adopted to differentiate if user logs in application system, then user also submits entry password to while the described first step submits account name to, or user also will use the identity documents (as user name/password, digital certificate, privacy key) of oneself to carry out register in application system when the login authentication data after merging is submitted to application system by described 5th moved further login assistant.
By describing above and can seeing, when substance logs in discriminating, user is without the need to inputting password on computers by keyboard, therefore, even if at PEs such as Internet bars, wooden horse, keyboard oracle listener also cannot obtain user password, simultaneously, user only need sweep to sweep just can complete to log in mobile communication terminal and differentiate operation, therefore, can accomplish safe and convenient; When dual login is differentiated, can improve when not adding users burden and troublesome poeration the fail safe logging in discriminating.
Accompanying drawing explanation
Fig. 1 is that the login authentication data after merging is submitted to the schematic diagram of the embodiment of application system by the present invention.
Fig. 2 is that the login authentication data after merging is submitted to the schematic diagram of the embodiment of short message receiving and sending system by the present invention.
Embodiment
Below in conjunction with drawings and Examples, the invention will be further described.
Mobile login assistant can use the development technique exploitation being suitable for user's mobile communication terminal used, such as J2ME can be used to develop for Android mobile phone; Objective-C can be used to develop for iOS mobile phone.Current mobile phone has camera.Have a lot of mobile telephone bar code scan A PP or dynamic base, class libraries at present, mobile login assistant directly can utilize these bar code scans APP, or uses various bar code scan, the dynamic base of identification, class libraries (even oneself exploitation).
Short message receiving and sending system can be purchased short message receiving and sending system or adopt existing various Short Messaging Service, or purchases note cat and develop.
Key in the invention process is the maintenance mechanism of session connection between applications client and application system, session object, and the submission of login authentication data after merging and processing mode, these are Web system with application system or are non-Web system, and mobile login assistant by data network, the login authentication data after merging directly is submitted to application system or the login authentication data after merging is sent to short message receiving and sending system and is obtained by application system relevant.Be briefly described with regard to the concrete enforcement of different situations respectively below.
Embodiment 1: application system is Web system, the login authentication data after merging is directly submitted to application system by data network by mobile login assistant.
In this case, session connection between application system and applications client is safeguarded by the conversation mechanism of Web system (J2EE Web Container, ASP.NET runtime) self, as safeguarded by Cookie, Session ID is exactly for identifying the Session ID (Session ID) of session connection in Web system session maintenance mechanism, session object (SessionObject) is exactly the session object of Web system self maintained, as the Java session object of J2EE, the session object etc. of ASP.NET.Application system connects without the need to oneself maintain sessions and comprises the Session ID turning back to applications client, creates session object without the need to oneself.When user logs in application system, application system sends login authentication data 1 by short message receiving and sending system and turns back to user browser to user's mobile communication terminal and by login authentication data 2, and is kept in the session object of Web system maintenance after the random word string logged in authentication data 1 and the random word string logged in authentication data 2 being merged.
Now, login authentication data after merging is directly submitted to application system in HTTP request mode by data network by mobile login assistant (by mobile communication terminal), wherein the way of submission of Session ID submits the mode of Session ID identical (as passed through Cookie) to applications client (i.e. browser), and other data in the login authentication data after merging are then submitted to application system in the mode of the Query String of Form data or URL; After login authentication data after merging is submitted to application system, session connection between application system with applications client is associated with session object by Session ID by Web system automatically, then the login authentication data after the merging received by application program process, and check that determining whether the login authentication data received meets to log in differentiates requirement, if meet the requirements, then by application program in session object by user label be by log in differentiate, and by log in differentiate result turn back to user's mobile communication terminal; Afterwards, user can use applications client (i.e. browser) to enter application system.
Embodiment 2: application system is Web system, the login authentication data after merging is sent to short message receiving and sending system and is obtained by application system by mobile login assistant.
In this case, the maintenance mode of the session connection between application system and applications client, Session ID, session object, and it is identical with embodiment 1 to return the mode logging in the random word string in authentication data with the login authentication data sent, preservation.
Mobile login assistant points out user to continue to use applications client access application system after the login authentication data after merging being submitted to short message receiving and sending system by mobile communication terminal with note.When user uses applications client (i.e. browser) to continue access application system, by session object, application system is checked whether user has been flagged as and is differentiated by logging in, if so, then allow user's access; Otherwise application system obtains the login authentication data after the merging of user's mobile communication terminal from short message receiving and sending system (mobile communication number by user); Login authentication data after the merging that user sent by mobile communication terminal if cannot obtain, or obtain to log in authentication data but log in authentication data and do not meet login discriminating requirement, then continue to require that user carries out login and differentiates (logging in authentication data as returned and send); If application system can obtain the login authentication data after the merging that user sent by mobile communication terminal, and the login authentication data obtained meets login discriminating requirement, then user label is differentiated by logging in by application system in session object, allows user to use applications client to enter application system.
Embodiment 3: application system is non-Web system, the login authentication data after merging is directly submitted to application system by data network by mobile login assistant.
In this case, the session connection between application system and applications client is safeguarded by application system oneself.Application system is that each session connection creates a Session ID (Session ID be at least unique for simultaneously session connection that is online, that keep active state), for each session connection creates a session object, and session object being kept in a global session Object table, the Session ID of its correspondence of each session object in global session Object table identifies and identifies; Whether user differentiates by logging in have corresponding mark to indicate in each session object; Application system is kept in session object after the random word string in the login authentication data 1 and 2 returning and send being merged.
Now, the login authentication data after merging is directly submitted to application system by data network by mobile login assistant (by mobile communication terminal); After application system receives the login authentication data after the merging of mobile login assistant submission, in global session Object table, corresponding session object is found by logging in Session ID in authentication data, check whether the login authentication data after determining the merging received meets to log in and differentiate requirement, if meet the requirements, be then differentiated user label by logging in session object, and login result is turned back to user's mobile communication terminal; Afterwards, user can use applications client to enter application system.
Embodiment 4: application system is non-Web system, the login authentication data after merging is sent to short message receiving and sending system and is obtained by application system by mobile login assistant.
In this case, the maintenance mode of the session connection between application system and applications client, Session ID, session object, and it is identical with embodiment 3 to return the mode logging in the random word string in authentication data with the login authentication data sent, preservation.
Mobile login assistant points out user to continue to use applications client access application system after the login authentication data after merging being sent to short message receiving and sending system by mobile communication terminal with note.User uses applications client to continue access application system; Whether application system is checked in the request that applications client is submitted to has Session ID and in global session Object table, whether has the session object corresponding with Session ID (thus determine between client whether built vertical session connection), if do not have, then require that user carries out register (this shows not set up session connection between applications client), otherwise, by session object, application system is checked whether user has been flagged as and is differentiated by logging in, if so, user's access is then allowed; Otherwise application system obtains the login authentication data after the merging of user's mobile communication terminal from short message receiving and sending system (passing through mobile communication number); Login authentication data after the merging that user sent by mobile communication terminal if cannot obtain, or obtain to log in authentication data but log in authentication data and do not meet login discriminating requirement, then continue to require that user carries out login and differentiates (logging in authentication data as returned and send); If application system can obtain the login authentication data after the merging that user sent by mobile communication terminal, and the login authentication data obtained meets login discriminating requirement, then user label is differentiated by logging in by application system in session object, allows user to use applications client to enter application system.
Other unaccounted concrete technology are implemented, and are well-known, self-explantory for those skilled in the relevant art.
Claims (8)
1., based on a login method for mobile communication terminal and note, it is characterized in that:
User is bound with the mobile communication number of user the account of application system; Described application system is a system being provided function services by network to user; User is by operating in the applications client access application system in subscriber computer; Described applications client comprises private client and browser general purpose client; For the session connection between applications client and application system, application system is assigned a Session ID and establishment and maintenance have a session object, session object is associated with the Session ID of the session connection between applications client with application system, thus session connection is corresponding with session object; Described session connection refers to that the logic between applications client and application system connects; Be provided with in described session object and indicate that whether user is by logging in the mark differentiated;
Install in the mobile communication terminal of user and run one be called mobile login assistant for help user application system complete log in differentiate program; Described mobile communication terminal is the mobile communication terminal device that the user of access application system holds; Described mobile communication terminal has camera and bar code scan program to read for bar code scan and barcode data; Described bar code scan program is moved mobile login assistant and calls, for obtaining the login authentication data that applications client shows with bar code form;
Install and run one for sending the short message receiving and sending system logging in authentication data and receive the login authentication data that mobile login assistant is sent by mobile communication terminal to the mobile communication terminal of user; Described short message receiving and sending system is the independently assembly of application system that will access of system or user; Described short message receiving and sending system is to there being a mobile communication number;
The operation process that user logs in application system is as follows:
The first step: user uses applications client request to log in application system and submits the account name in application system to;
Second step: application system obtains the mobile communication number of user by the account name that user submits to from the user account database of application system, then by short message receiving and sending system, login authentication data 1 is sent to user's mobile communication terminal on the one hand, on the other hand user is logged in authentication data 2 and turn back to the applications client of user and the login authentication data 2 returned is shown in applications client with the form of bar code;
3rd step: user uses the bar code running the mobile communication terminal scanning applications client display having mobile login assistant;
4th step: mobile login assistant obtains the login authentication data 2 of user from the bar code of scanning, obtains the login authentication data 1 that application system sends from the note case of mobile communication terminal; Combination logs in authentication data 1 and logs in authentication data 2 and forms the login authentication data after merging;
5th step: the login authentication data after merging is submitted to application system by data network by mobile communication terminal by mobile login assistant, or the login authentication data after merging is sent to short message receiving and sending system with short message mode and is obtained by application system;
6th step: application system is received or gets user and moves login assistant and to be submitted to by mobile communication terminal or after login authentication data after the merging that sends, check determine user move login assistant submit to or send merging after login authentication data whether meet log in differentiate requirement, if meet, be then differentiated user label by logging in, and allow user to log in application system by applications client; Otherwise refusal user accesses and continues to require that user carries out login and differentiates.
2. the login method based on mobile communication terminal and note according to claim 1, is characterized in that:
The login authentication data 1 that described application system is sent to user's mobile communication terminal at described second step and turn back to user's applications client login authentication data 2 in comprise following information simultaneously: the Session ID of the session connection between user's applications client and application system and random word string, wherein, it is identical for logging in authentication data 1 and logging in the Session ID comprised in authentication data 2, and the random word string comprised is then different; And application system turns back to the mobile communication number also including short message receiving and sending system in the login authentication data 2 of applications client;
If the login authentication data after merging is submitted to application system in described 5th step by data network by described mobile login assistant, then include the network address of application system in the login authentication data 1 that sends of application system and/or the login authentication data 2 that returns.
3. the login method based on mobile communication terminal and note according to claim 2, is characterized in that:
Described mobile login assistant obtains the mobile communication number of short message receiving and sending system authentication data 2 from logging in, and number obtains the login authentication data 1 that application system sends in the note case of mobile communication terminal accordingly.
4. the login method based on mobile communication terminal and note according to claim 2, is characterized in that:
After described mobile login assistant obtains the login authentication data 1 that application system sends and the login authentication data 2 turning back to applications client, the random word string logged in two in authentication datas merges, and forms the login authentication data after merging; Include the Session ID identical with logging in authentication data 2 with logging in authentication data 1 in login authentication data after merging, and have the random word string after merging.
5. the login method based on mobile communication terminal and note according to claim 2, is characterized in that:
Login authentication data 1 to be sent to mobile communication terminal and while authentication data 2 turns back to applications client by login at described second step by application system, is kept in session object corresponding to session connection between application system with applications client after the random word string the two comprised merges.
6. the login method based on mobile communication terminal and note according to claim 5, is characterized in that:
Described application system is received by data network or gets user from short message receiving and sending system and moves login assistant and to be submitted to by mobile communication terminal or after login authentication data after the merging that sends, check that determining whether the login authentication data after merging meets to log in differentiates requirement as follows, and after inspection is determined to meet the requirements by user label for differentiating by logging in:
The random word string after the random word string obtaining the login authentication data 1 of preservation in the session object corresponding to the Session ID the login authentication data after the merging of login assistant submission or transmission and the random word string merging logging in authentication data 2 is moved from user, then compare the random word string after the merging obtained from session object with user move login assistant to be submitted to by mobile communication terminal or random word string after merging in login authentication data after the merging that sends whether identical, if identical, then determine user move login assistant submit to or send merging after login authentication data meet log in differentiate requirement, and be differentiated user ID by logging in session object, otherwise, determine user move login assistant submit to or send merging after login authentication data do not meet log in differentiate requirement.
7. the login method based on mobile communication terminal and note according to claim 1, is characterized in that:
If user is exactly the mobile communication number of user at the account name of application system, then at described second step, whether application system has corresponding account by the inquiring user in the user account database of application system of the mobile communication number as account name that user submits to, if have, then by short message receiving and sending system, login authentication data 1 is sent to user's mobile communication terminal.
8. the login method based on mobile communication terminal and note according to claim 1, is characterized in that:
Dual login is adopted to differentiate if user logs in application system, then user also submits entry password to while the described first step submits account name to, or user also will use the identity documents of oneself to carry out register in application system when the login authentication data after merging is submitted to application system by described 5th moved further login assistant.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510225152.6A CN104917755B (en) | 2015-05-05 | 2015-05-05 | A kind of login method based on mobile communication terminal and short message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510225152.6A CN104917755B (en) | 2015-05-05 | 2015-05-05 | A kind of login method based on mobile communication terminal and short message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104917755A true CN104917755A (en) | 2015-09-16 |
| CN104917755B CN104917755B (en) | 2018-05-18 |
Family
ID=54086461
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510225152.6A Active CN104917755B (en) | 2015-05-05 | 2015-05-05 | A kind of login method based on mobile communication terminal and short message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104917755B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109257338A (en) * | 2018-08-29 | 2019-01-22 | 厦门快快网络科技有限公司 | A kind of System and method for of server log re-authentication |
| TWI670618B (en) * | 2017-05-26 | 2019-09-01 | 台新國際商業銀行股份有限公司 | Login system implemented along with a mobile device without password and method thereof |
| US11588808B2 (en) * | 2019-11-01 | 2023-02-21 | Gotrustid Inc. | Operating system with automatic login mechanism and automatic login method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040083297A1 (en) * | 2002-10-25 | 2004-04-29 | Yahoo!, Inc. | Centrally controllable instant messaging system |
| CN102231716A (en) * | 2011-06-30 | 2011-11-02 | 重庆新媒农信科技有限公司 | Instant communication service login method |
| CN102510378A (en) * | 2011-10-31 | 2012-06-20 | 福建天晴数码有限公司 | Method for logging in online game through mobile equipment |
| CN104202162A (en) * | 2014-08-12 | 2014-12-10 | 武汉理工大学 | System for login based on mobile phone and login method |
| CN104270338A (en) * | 2014-09-01 | 2015-01-07 | 刘文印 | A method and system of electronic identity registration and authentication login |
-
2015
- 2015-05-05 CN CN201510225152.6A patent/CN104917755B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040083297A1 (en) * | 2002-10-25 | 2004-04-29 | Yahoo!, Inc. | Centrally controllable instant messaging system |
| CN102231716A (en) * | 2011-06-30 | 2011-11-02 | 重庆新媒农信科技有限公司 | Instant communication service login method |
| CN102510378A (en) * | 2011-10-31 | 2012-06-20 | 福建天晴数码有限公司 | Method for logging in online game through mobile equipment |
| CN104202162A (en) * | 2014-08-12 | 2014-12-10 | 武汉理工大学 | System for login based on mobile phone and login method |
| CN104270338A (en) * | 2014-09-01 | 2015-01-07 | 刘文印 | A method and system of electronic identity registration and authentication login |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI670618B (en) * | 2017-05-26 | 2019-09-01 | 台新國際商業銀行股份有限公司 | Login system implemented along with a mobile device without password and method thereof |
| CN109257338A (en) * | 2018-08-29 | 2019-01-22 | 厦门快快网络科技有限公司 | A kind of System and method for of server log re-authentication |
| US11588808B2 (en) * | 2019-11-01 | 2023-02-21 | Gotrustid Inc. | Operating system with automatic login mechanism and automatic login method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104917755B (en) | 2018-05-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9887999B2 (en) | Login method and apparatus | |
| US9882916B2 (en) | Method for verifying sensitive operations, terminal device, server, and verification system | |
| US8522010B2 (en) | Providing remote user authentication | |
| KR101589192B1 (en) | Identity authentication and management device and method thereof | |
| KR101214836B1 (en) | Authentication method and authentication system | |
| US20210099431A1 (en) | Synthetic identity and network egress for user privacy | |
| US20080168546A1 (en) | Randomized images collection method enabling a user means for entering data from an insecure client-computing device to a server-computing device | |
| CN102073822A (en) | Method and system for preventing user information from leaking | |
| CN101897166A (en) | Systems and methods for establishing a secure communication channel using a browser component | |
| KR20060047252A (en) | Account creation via a mobile device | |
| CN105407074A (en) | Authentication method, apparatus and system | |
| JP2007264835A (en) | Authentication method and system | |
| CN107809438A (en) | A kind of network authentication method, system and its user agent device used | |
| CN105162773B (en) | A kind of convenient login method of Web system based on mobile terminal | |
| CN112131564A (en) | Encrypted data communication method, apparatus, device, and medium | |
| TWI668586B (en) | Data communication method and system, client and server | |
| JP2008242926A (en) | Authentication system, authentication method and authentication program | |
| JP2015099470A (en) | System, method, and server for authentication, and program | |
| CN104618356B (en) | Auth method and device | |
| CN109740319B (en) | Digital identity verification method and server | |
| CN104917755B (en) | A kind of login method based on mobile communication terminal and short message | |
| KR20090097036A (en) | Otp generating method for using the sms, and personal identification method and system for using the same | |
| CN106888200B (en) | Identification association method, information sending method and device | |
| US8532271B2 (en) | Cybercrime detecting and preventing method and system established by telephone number code, authorization codes and source identification code | |
| Varshney et al. | Push notification based login using BLE devices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20190813 Address after: 314112 2 Floor 2, No. 383 Huimin Avenue, Huimin Street, Jiashan County, Jiaxing City, Zhejiang Province Patentee after: Jiaxing Guao Gene Technology Co., Ltd. Address before: 430070 Hubei Province, Wuhan city Hongshan District Luoshi Road No. 122 Patentee before: Wuhan University of Technology |