CN104601590A - Login method, server and mobile terminal - Google Patents
Login method, server and mobile terminal Download PDFInfo
- Publication number
- CN104601590A CN104601590A CN201510050671.3A CN201510050671A CN104601590A CN 104601590 A CN104601590 A CN 104601590A CN 201510050671 A CN201510050671 A CN 201510050671A CN 104601590 A CN104601590 A CN 104601590A
- Authority
- CN
- China
- Prior art keywords
- app
- login
- log
- mobile terminal
- identification code
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
An embodiment of the invention provides a login method. The login method comprises receiving login request information sent by a mobile terminal, wherein the login request information comprises a device ID of the mobile terminal and an app ID of an app requested to login; inquiring login data to determine whether other apps logs in the login terminal or not based on the device ID and the app ID included inside the received login request information; returning the login information to the mobile terminal according to a login query result for the app requested to login to login. The login method can provide shearing login states of a plurality of apps of an operator, simplifies the user login operation, brings good experience for a user, brings user conversion rate for an operating company and enhances the user adhesiveness. An embodiment of the invention provides a server and a mobile terminal.
Description
Technical field
Embodiments of the present invention relate to app application, and more specifically, embodiments of the present invention relate to a kind of login method, server and mobile terminal.
Background technology
This part embodiments of the present invention be intended to for stating in claims provide background or context.Description is not herein because be included in just admit it is prior art in this part.
The use of current portable electric appts is increasingly extensive, and each company is proposed a large amount of for the application program (app) of user at mobile terminal, such as Baidu's map, Baidu's mhkc, Baidu's video etc.For the app of same company (such as Baidu), mainly obtain logging status by communication between app at present, and then adopt a pass account current between each app.
But, communicate between app and substantially can not to realize in IOS system, and on other system, communication between 2 app still can realize, but app once there will be communication disaster more, such as 10 app cross-communication just need 10*9=90 communication, and the non-constant especially in enforceability of the communication between whole company app.
Summary of the invention
The reason of the disaster that communicates between app time large for app quantity, in the prior art, when user uses the app of same operator on same mobile terminal device, can not realize " share and log in " well.In the context of this application, " share and log in " and refer to: when an app has on mobile terminals been in logging status, when starting another app on this mobile terminal, without the need to again manually inputting account, password, the login account of the app being in logging status can be adopted to complete login.
In addition, when realizing sharing login, app publishes (logout) or all need when logging in first to input account, password, and this is very bothersome process.
For this reason, be starved of a kind of login method of improvement, to realize the shared login between app.
In the present context, embodiments of the present invention are expected to provide a kind of login method, server and mobile terminal.
In the first aspect of embodiment of the present invention, provide a kind of login method, such as, can comprise: the landing request information that mobile terminal receive sends, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of this mobile terminal and the app of request login; The EIC equipment identification code deviceID comprised based on received landing request information and app identification code appID, inquiry log database is to confirm whether this mobile terminal has other app log in; According to login Query Result, return log-on message to described mobile terminal, the app logged in for described request logs in.
In the second aspect of embodiment of the present invention, provide a kind of login method, such as, can comprise: send landing request information to server, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of mobile terminal and the app of request login; Receive the log-on message that described server returns, wherein, this log-on message is the EIC equipment identification code deviceID and app identification code appID that are comprised based on described landing request information by described server, inquire about log database to confirm whether this mobile terminal has other app log in, and generate according to login Query Result; According to described log-on message, the app that described request logs in is logged in.
In the third aspect of embodiment of the present invention, provide a kind of server, such as, can comprise: landing request information receiver module, for the landing request information that mobile terminal receive sends, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of this mobile terminal and the app of request login; Log in enquiry module, for the EIC equipment identification code deviceID that comprises based on received landing request information and app identification code appID, inquiry log database is to confirm whether this mobile terminal has other app log in; Login process module, for according to login Query Result, return log-on message to described mobile terminal, the app logged in for described request logs in.
In the fourth aspect of embodiment of the present invention, provide a kind of mobile terminal, such as, can comprise: landing request information sending module, for sending landing request information to server, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of mobile terminal and the app of request login; Log-on message receiver module, for receiving the log-on message that described server returns, wherein, this log-on message is the EIC equipment identification code deviceID and app identification code appID that are comprised based on landing request information by described server, inquire about log database to confirm whether this mobile terminal has other app log in, and generate according to login Query Result; App login module, for according to described log-on message, logs in the app that described request logs in.
By the login method of embodiment of the present invention, server and mobile terminal, shared login mechanism can be provided for multiple app of operator, thus simplify user login operation, for user brings better experience, and user's conversion ratio can be brought to operator, strengthen user's viscosity.
summary of the invention
Conventionally, when after a certain app that user starts on (such as activate, open) mobile terminal, first mobile terminal checks whether this locality stores corresponding token; If had, show that this app logs in, then send token directly to server, carry out checking by server according to the token stored and log in; If no, show that this app not yet logs in or publishes, then carry out " conventional login ", namely need that user manually inputs account, password logs in.Like this, user, when login account, operates more loaded down with trivial details.
For this reason, the invention provides a kind of shared login mechanism.Sharing the process logged in can be: mobile terminal sends landing request information to server; Server judges whether this mobile terminal has other app log in based on landing request information, and returns log-on message according to login Query Result to mobile terminal, and the app logged in for request logs in.Like this, when other app existing log in, user is without the need to repeating input pass account and/or login password, and the account only server need being selected to return can quick registration app.
Alternatively, when mobile terminal stores token, user also can select to initiate shared login process, realizes sharing the login account logged on other app.
Herein, other app can be the app of the same operator of app logged in request on same mobile terminal.
After describing general principle of the present invention, lower mask body introduces various non-limiting embodiment of the present invention.
application scenarios overview
First with reference to figure 1, server 100 can be pass server etc., and mobile terminal 200 can be mobile phone, panel computer etc.Such as can be communicated to connect by mobile Internet etc. between mobile terminal 200 and server 100.
Utilize the login method that the embodiment of the present invention provides, when user starts a certain app on (such as activate, open) mobile terminal 200, not yet log in as this app is in or has published state, then can trigger one and share login process: send landing request information to server 100 by mobile terminal 200; Server 100 is inquired about based on landing request information, and returns log-on message according to login Query Result to mobile terminal 200; User utilizes mobile terminal 200 to select to share the account logged in; Server 100 receives and authorizes the login of this account.Namely the shared login of app is achieved.
If app is logged with a certain account and not yet publish, namely all store corresponding logging on authentication (token) at mobile terminal 200 and server 100 place, then, when starting this app, checking login can be carried out by means of only token.
example devices
Below in conjunction with the application scenarios of Fig. 1, respectively the server 100 of exemplary embodiment of the invention, mobile terminal 200 are introduced with reference to figure 2, Fig. 3.
It should be noted that above-mentioned application scenarios is only that embodiments of the present invention are unrestricted in this regard for the ease of understanding spirit of the present invention and principle and illustrating.On the contrary, embodiments of the present invention can be applied to applicable any scene.
Such as, see Fig. 2, it is the device structure schematic diagram of the server 100 that the embodiment of the present invention provides.As shown in the figure, server 100 can comprise: landing request information receiver module 101, login enquiry module 102, login process module 103, log database 104.In addition, server 100 can also comprise logging on authentication generation module 105.
See Fig. 3, it is the device structure schematic diagram of the mobile terminal 200 that the embodiment of the present invention provides.As shown in the figure, mobile terminal 200 can comprise: landing request information sending module 201, log-on message receiver module 202, app login module 203.In addition, mobile terminal 200 can also comprise logging on authentication receiver module 204, memory 205.
With reference to Fig. 3, when user starts a certain app on (such as activate, open) mobile terminal 200, not yet log in if this app is in or has published state, then can trigger one and share login process.Landing request information sending module 201 in mobile terminal 200 sends landing request information to server 100, and wherein, this landing request information can comprise the appID of the deviceID of mobile terminal 200 and the app of request login.
As previously mentioned, the deviceID of mobile terminal 200 is the equipment unique identifiers generated according to the metadata of mobile terminal 200 by server 100, it is different that different platform generates scheme, generated by specific cipher mode, the appID of the app that request logs in generates based on the deviceID of mobile terminal 200 and the app names associate of this app.Alternatively, in login process, after server 100 receives the data of mobile terminal 200 transmission at every turn, deviceID and appID sent in data can be checked whether to mate, in case user utilizes the appID forging or distort to log in.
Then with reference to Fig. 2, the landing request information receiver module 101 in server 100 receives above-mentioned landing request information.Log in deviceID and appID that enquiry module 102 comprises based on received landing request information, inquiry log database 104, to confirm whether this mobile terminal 200 has other app to log in.
Particularly, for listed app, deviceID, appID, login account and logging status can be stored in log database 104 by server 100 explicitly, so that when receiving landing request information, inquire about.
Fig. 4 A-4B schematically show log database 104 store the data structure of content.
Such as, from Fig. 4 A, be the mobile terminal of " Terminal_Z " for deviceID, existing appID is that " Z_163_app1 " and " Z_163_app2 " two app log in.More specifically, for " Z_163_app1 ", listed account has Accout_A, Accout_B; For " Z_163_app2 ", listed account has Accout_A, Account_C.
In addition, as shown in Figure 4 A, corresponding logging on authentication can also be stored explicitly with listed app and account in log database 104.Such as, for " Z_163_app1 ", store logging on authentication token_1, token_3 of login account Account_A, Account_B respectively; For " Z_163_app2 ", store logging on authentication token_2, token_4 of login account Account_A, Account_C respectively.After account publishes (logout), logging on authentication associated therewith will lose efficacy.
In addition, one " logging status " can also be stored accordingly with deviceID in log database 4 and indicate, be used to indicate on the mobile terminal 200 corresponding to this deviceID whether existing app is in logging status.
Such as, as shown in Figure 4 A, for deviceID " Terminal_Z ", two app " Z_163_app1 ", " Z_163_app2 " are had to be in logging status, therefore " logging status " is masked as " Z_163_LOG_ON ", this means that other app can carry out " share and log in ".
As shown in Fig. 4 B, 4C, for deviceID " Terminal_Z ", although the app/ account being in logging status changes, " logging status " mark remains unchanged, and is still " Z_163_LOG_ON ".
Like this, server 100, when receiving the landing request information that mobile terminal 200 sends, only need be inquired about corresponding logging status and can know " whether mobile terminal 200 having other app log in ", to determine whether can carry out " share and log in ".
Continue with reference to Fig. 2, after login enquiry module 102 inquires about log database 104, login process module 103, according to login Query Result, returns log-on message to mobile terminal 200, and the app logged in for request logs in.
Particularly, if log in Query Result instruction to be in logging status without other app, then login process module 103 can return the log-on message of an instruction " conventional login " to mobile terminal 200, so that user inputs account and password logs in.
Other app are had to be in logging status if log in Query Result instruction, then login process module 103 can generate and return an instruction to mobile terminal 200 and can carry out sharing " log-on message " that log in, " log-on message " should comprise the listed account of other app.Like this, the app that user can log in for request selects account, carries out sharing logging in, and without the need to inputting login account and password.
Such as, as shown in Figure 4 B, according to the storage content of log database 104, for the app1 (appID:Z_163_app1) of mobile terminal 200 (deviceID:Terminal_Z), log in account Account_A.Like this, when user starts another app (appID:Z_163_app2), login process module 103 can return an instruction to mobile terminal 200 and " share and log in " and " log-on message " that comprise account Account_A.User selects this account Account_A, can realize the shared login of app2, and without the need to again manually inputting account and password.After app2 realizes sharing login, the storage content of log database 104 becomes as shown in Figure 4 C.
Alternatively, login process module 103 generates and can also comprise the operational credentials of the app logged in for request to " log-on message " that mobile terminal 200 returns.This operational credentials can be such as " identifying code " or " confirming to log in instruction ", and once effective.For identifying code, when can return " log-on message " by server 100, send to mobile terminal 200 in the lump, need user to select account and just can log in after correct input validation code.Instruction is logged in for confirmation, after user have selected login account, mobile terminal 200 can send to server 100 user's triggering " confirming to log in instruction ", server 100 is after receiving this " confirmation logs in instruction ", can only once effectively process, generate corresponding token, namely lost efficacy after completing, and can not reuse.
Continue with reference to Fig. 3, the log-on message that log-on message receiver module 202 reception server 100 in mobile terminal 200 returns, logs according to this log-on message for app login module 203.
Such as, if log-on message instruction " conventional login " (not having other app to be in logging status), then app login module 203 presents account, Password Input frame, inputs account and the password associated, log in for user.
Log in if log-on message instruction can be carried out sharing, then app login module 203 presents the login account that this log-on message is carried, and selects account, carries out sharing login for user.After user selects account, the account that user selects is sent to server 100 by app login module 203.
Alternatively, as previously mentioned, as server 100 to generate and " log-on message " that return also carries " operational credentials ", then app login module 203 can present corresponding operational credentials, performs corresponding operating for user/mobile terminal 200.
Server 100 receives the account that user selects, and this account logins successfully on the app of request login.The logging on authentication generation module 105 of server 100 can generate the logging on authentication token corresponding to this app and this account, and this logging on authentication and corresponding deviceID, appID, login account are stored in log database 104 explicitly, send to mobile terminal 200 simultaneously.The logging on authentication token that logging on authentication receiver module 204 reception server 100 of mobile terminal 200 returns, and by this logging on authentication token and deviceID, be stored in explicitly in memory 205 with appID, login account.
Like this, when user starts a certain app on (such as activate, open) mobile terminal 200, first mobile terminal 200 can judge whether store corresponding token in memory 205.If store corresponding token, show to log in, then mobile terminal 200 can send token directly to server 100, carries out checking and logs in.If also have other token that this app is corresponding in memory 205, namely user has logged in multiple account on this app, then user can pass through account switching mode, logs in other accounts.If do not store corresponding token, then show that app not yet logs in or publishes, shared login process can be initiated, send landing request information to server 100.
Alternatively, when there being token, user also can select to initiate shared login process, realizes sharing the login account logged on other app.
In the above-described embodiments, can referring again to shown in Fig. 4 A, such as, when user uses app1 (appID:Z_163_app1), the account of login is " Account_A ".After closing this app.If user starts app1 again, when mobile terminal is according to closedown app1, listed account is " Account_A ", and send the token_1 of storage to server, checking logs in this account.
Alternatively, if user wants to switch account, can trigger account handoff functionality on mobile terminals, mobile terminal detects that this locality also stores token_3, and the account " Account_B " of correspondence is presented to user.If switch this account, mobile terminal sends token_3 to server, and checking logs in this account.
Alternatively, if user wants to log in other accounts more, can initiate shared login process, as shown in Figure 4 A, mobile terminal can obtain account " Account_C ", presents to user, and user can select login account " Account_C " on app1.
Alternatively, if user's initiating switchup app3 (appID:Z_163_app3, figure do not show), mobile terminal detects that this locality does not store the corresponding token of app3.Then initiate to share login process, send landing request information to server.According to Fig. 4 A, mobile terminal can obtain account " Account_A " that server returns, " Account_B ", " Account_C ", selects for user.
In the above-described embodiments, the account achieving app shares login, simplifies register, improves the ease for use of app.
Alternatively, for guaranteeing safety, prevent assailant from forging request, between server 100 and mobile terminal 200, all transmitting procedures all can use key to encrypt, and all attach appID when each transmission, during the data that server 100 handle mobile terminal sends, whether the appID in meeting verification msg is effective, increases the reliability of transmission information.Such as, whether server 100 can mate by deviceID and appID in check data, in case user utilizes the appID forging or distort to log in.
Alternatively, server 100 can also take precautions against the scanning probe of mobile terminal 200 couples of deviceID by the number of times limiting same IP or the shared logging request of initiation of same appID unit interval (as one hour).Such as, when same IP, initiate in the same appID unit interval to share the number of times of logging request exceed pre-determined number time, shared login feature can be forbidden, and require that user carries out conventional login.
Alternatively, server 100 can add last layer mandate to app, to strengthen fail safe.Such as, each app can be built-in for encrypting the PKI with signature verification when issue, with server communication in can generate enciphered message with this PKI to protocol parameter, and the signing messages that server end returns to be verified.
The app realized by server and the mobile terminal of the above-mentioned execution mode of the present invention shares login mode, for multiple app of operator (same operator) provide shared logging status, emerge in multitude at current app especially, the app of an operator may be a lot, user login operation is simplified by this login mode, for user brings better experience, and huge user's conversion ratio can be brought to operator, strengthen user's viscosity.
illustrative methods
After the equipment describing exemplary embodiment of the invention, next, the login method with reference to figure 5 pairs of exemplary embodiment of the invention is introduced.
The schematic flow sheet of the login method that Fig. 5 provides for the embodiment of the present invention.Referring to this figure, the flow process of login method is described.
First, in step S701, user starts the app on mobile terminal (mobile terminal 200 as shown in Figure 1).
In step S702, mobile terminal judges whether this locality stores logging on authentication token.If result is "Yes", then proceed to step S703; If result is "No", then triggers and share login process, proceed to step S704.
In step S703, mobile terminal sends token directly to server (server 100 as shown in Figure 1), carries out checking and logs in.Alternatively, after checking logs in, user can select to initiate shared login process, realizes sharing the login account logged on other app.
In step S704, initiate to share login process, mobile terminal sends landing request information to server.Wherein, this landing request information can comprise the appID of the deviceID of mobile terminal and the app of request login.
In step S705, server receives landing request information.
In step S706, deviceID and appID that server comprises based on received landing request information, inquiry log database is to confirm whether this mobile terminal has other app log in.If result is "No", then proceed to step S707; If result is "Yes", then proceed to step S708.
In step S707, server can send the log-on message of " conventional login " to mobile terminal.In the case, user need input account, password carries out conventional login.
In step S708, server returns an instruction to mobile terminal can carry out sharing the log-on message logged in, and this log-on message can comprise the listed login account of other app.Alternatively, this log-on message can also comprise the once effective operational credentials of the app logged in for request.
In step S709, the log-on message that mobile terminal reception server returns.
In step S710, user selects the listed login account that mobile terminal presents according to log-on message, thus carries out sharing login.Alternatively, when log-on message comprises operational credentials, user/mobile terminal also needs to operate according to operational credentials.
In step S711, server logs in the login account that user selects.Further, this login account also for this app generates corresponding token, and this token and deviceID, appID, login account is stored explicitly, sends to mobile terminal simultaneously.
In step S712, the token that mobile terminal storage server returns, completes to share logging in.
By the login mode of the above-mentioned execution mode of the present invention, shared logging status can be provided for multiple app of operator, simplify user login operation, for user brings better experience, and huge user's conversion ratio can be brought to operator, strengthen user's viscosity.
Although it should be noted that the operation describing the inventive method in the accompanying drawings with particular order, this is not that requirement or hint must perform these operations according to this particular order, or must perform the result that all shown operation could realize expectation.Additionally or alternatively, some step can be omitted, multiple step be merged into a step and perform, and/or a step is decomposed into multiple step and perform.
Such as, the step S701, step S702, step S707, the step S712 that perform in mobile terminal side, the step S703 step, the S711 that perform in server side, be only the optional step implementing shared login of the present invention, lack some of them or all can not affect the realization of basic goal of the invention of the present invention.
In addition, although be referred to some modules of server, mobile terminal in above-detailed, this division is only not enforceable.In fact, according to the embodiment of the present invention, the Characteristic and function of two or more devices above-described can be specialized in one apparatus.Equally, the Characteristic and function of an above-described device also can Further Division for be specialized by multiple device.
Although describe spirit of the present invention and principle with reference to some embodiments, but should be appreciated that, the present invention is not limited to disclosed embodiment, can not combine to be benefited to the feature that the division of each side does not mean that in these aspects yet, this division is only the convenience in order to state.The present invention is intended to contain the interior included various amendment of spirit and scope and the equivalent arrangements of claims.
Accompanying drawing explanation
By reference to accompanying drawing reading detailed description hereafter, above-mentioned and other objects of exemplary embodiment of the invention, feature and advantage will become easy to understand.In the accompanying drawings, show some execution modes of the present invention by way of example, and not by way of limitation, wherein:
Fig. 1 schematically shows the application scenarios according to embodiment of the present invention;
Fig. 2 schematically shows the device structure schematic diagram of the server according to embodiment of the present invention;
Fig. 3 schematically shows the device structure schematic diagram of the mobile terminal according to embodiment of the present invention;
Fig. 4 A-4C schematically shows the data structure schematic diagram of the log database according to the embodiment of the present invention;
Fig. 5 schematically shows the schematic flow sheet of the login method according to embodiment of the present invention.
In the accompanying drawings, identical or corresponding label represents identical or corresponding part.
Embodiment
Below with reference to some illustrative embodiments, principle of the present invention and spirit are described.Should be appreciated that providing these execution modes is only used to enable those skilled in the art understand better and then realize the present invention, and not limit the scope of the invention by any way.On the contrary, provide these execution modes to be to make the disclosure more thorough and complete, and the scope of the present disclosure intactly can be conveyed to those skilled in the art.
Art technology technical staff know, embodiments of the present invention can be implemented as a kind of system, device, equipment, method or computer program.Therefore, the disclosure can be implemented as following form, that is: hardware, completely software (comprising firmware, resident software, microcode etc.) completely, or the form that hardware and software combines.
According to the embodiment of the present invention, a kind of login method, server and mobile terminal is proposed.
In this article, it is to be appreciated that in involved term:
1, EIC equipment identification code (deviceID): the equipment unique identifier generated according to the metadata of mobile terminal by server when app initiating switchup, it is different that different platform generates scheme, generated by the cipher mode specified.Such as, for android terminal, metadata can comprise mobile phone model, MAC Address (physical address), resolution, OS name etc.; For IOS terminal, metadata can comprise IDFV, keychain etc. that operating system provides.
2, app identification code (appID): give each app unique identifier (ID) distributed by server.AppID is app on mobile terminals when running first, and the deviceID sent based on mobile terminal and the app names associate of this app generate.Like this, in login process, after server receives the data of mobile terminal transmission at every turn, deviceID and appID sent in data can be checked whether to mate, in case user utilizes the appID forging or distort to log in.
3, logging on authentication (token): after the app of mobile terminal is with a certain account Successful login, server generates a token (corresponding to a deviceID, an appID and account).Token and deviceID, appID and login account can be stored in the addressable log database of server by server explicitly, can also mobile terminal be sent to preserve this token simultaneously.Like this, when user closes (but not publishing (logout)) app and again opens app, the token of preservation can send to server to verify to carry out mating with the token that server place stores by mobile terminal, when confirming coupling, automatically logs in.After account is published, corresponding token lost efficacy.Such as, server receives after account publishes instruction, deletes this token, and issues an instruction to mobile terminal, this token of the corresponding deletion of mobile terminal.
4, key: given the key encrypted for communication protocol between mobile terminal and server on each mobile terminal when app initiating switchup by server-assignment.
5, operational credentials: can be such as " identifying code " or " requiring to send the voucher confirming to log in instruction ", and once effective.For identifying code, when can issue login account by server, send to mobile terminal in the lump, need user to select account and just can log in after correct input validation code.For " requiring that transmission confirms to log in the voucher of instruction ", after user selects login account, mobile terminal can send one " confirming to log in instruction " to server, and server, after receiving this " confirmation logs in instruction ", completes login.
In addition, any number of elements in accompanying drawing is all unrestricted for example, and any name is all only for distinguishing, and does not have any limitation.
Below with reference to some representative embodiments of the present invention, explaination principle of the present invention and spirit in detail.
Claims (26)
1. a login method, comprising:
The landing request information that mobile terminal receive sends, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of this mobile terminal and the app of request login;
The EIC equipment identification code deviceID comprised based on received landing request information and app identification code appID, inquiry log database is to confirm whether this mobile terminal has other app log in;
According to login Query Result, return log-on message to described mobile terminal, the app logged in for described request logs in.
2. login method according to claim 1, wherein, described EIC equipment identification code deviceID, described app identification code appID, login account and logging status store by described log database explicitly.
3. login method according to claim 2, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, the step returning log-on message to described mobile terminal comprises:
Return the described listed login account of other app to described mobile terminal, the app logged in for described request selects this account and logs in.
4. login method according to claim 2, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, the method also comprises:
Generate the operational credentials of the app logged in for described request,
And the step wherein, returning log-on message to described mobile terminal comprises:
Return the operational credentials of the described listed login account of other app and the app for described request login to described mobile terminal, the app logged in for described request selects described listed login account also to carry out inputting, to log according to this operational credentials.
5. login method according to claim 4, wherein,
The once login of described operational credentials only for the app of described request login is effective.
6. login method according to claim 5, also comprises:
When the app Successful login that described request logs in, generate logging on authentication token, and store explicitly with described EIC equipment identification code deviceID, described app identification code appID, described login account in described log database, send to described mobile terminal simultaneously.
7. the login method according to any one of claim 1 to 6, wherein, described app identification code appID is app on the mobile terminal when running first, and the described EIC equipment identification code deviceID sent based on described mobile terminal and the app title of this app generate.
8. a login method, comprising:
Send landing request information to server, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of mobile terminal and the app of request login;
Receive the log-on message that described server returns, wherein, this log-on message is the EIC equipment identification code deviceID and app identification code appID that are comprised based on described landing request information by described server, inquire about log database to confirm whether this mobile terminal has other app log in, and generate according to login Query Result;
According to described log-on message, the app that described request logs in is logged in.
9. login method according to claim 8, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, according to described log-on message, comprises the step that the app of described request login logs in:
Receive the listed login account of other app described that described server returns, the app logged in for described request selects this account and logs in.
10. login method according to claim 8, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, according to described log-on message, comprises the step that the app of described request login logs in:
Receive the listed login account of other app described that described server sends and the operational credentials generated for the app that described request logs in;
Select described listed login account, and carry out inputting, to log according to described operational credentials.
11. login methods according to claim 10, wherein, the once login of described operational credentials only for the app of described request login is effective.
12. login methods according to claim 11, also comprise:
The reception logging on authentication token that server returns when the app Successful login that described request logs in, and store explicitly with described EIC equipment identification code deviceID, described app identification code appID, described login account in memory.
13. according to Claim 8 to the login method according to any one of 12, wherein, described app identification code appID is app on the mobile terminal when running first, generates based on the described EIC equipment identification code deviceID of described mobile terminal and the app title of this app.
14. 1 kinds of servers, comprising:
Landing request information receiver module, for the landing request information that mobile terminal receive sends, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of this mobile terminal and the app of request login;
Log in enquiry module, for the EIC equipment identification code deviceID that comprises based on received landing request information and app identification code appID, inquiry log database is to confirm whether this mobile terminal has other app log in;
Login process module, for according to login Query Result, return log-on message to described mobile terminal, the app logged in for described request logs in.
15. servers according to claim 14, wherein, described server also comprises: log database, for described EIC equipment identification code deviceID, described app identification code appID, login account and logging status being stored explicitly.
16. servers according to claim 15, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, described login process module is used for returning the described listed login account of other app to described mobile terminal, and the app logged in for described request selects this account and logs in.
17. servers according to claim 15, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, described login process module is for generating the operational credentials of the app logged in for described request;
And described login process module is also for returning the operational credentials of the described listed login account of other app and the app for described request login to described mobile terminal, the app logged in for described request selects described listed login account also to carry out inputting, to log according to this operational credentials.
18. servers according to claim 17, wherein,
The once login of described operational credentials only for the app of described request login is effective.
19. servers according to claim 18, also comprise:
Logging on authentication generation module, for when the app Successful login that described request logs in, generate logging on authentication token, and be stored in described log database explicitly with described EIC equipment identification code deviceID, described app identification code appID, described login account, send to described mobile terminal simultaneously.
20. servers according to any one of claim 14 to 19, wherein, it is app on the mobile terminal when running first that described server also comprises app identification code appID, and the described EIC equipment identification code deviceID sent based on described mobile terminal and the app title of this app generate.
21. 1 kinds of mobile terminals, comprising:
Landing request information sending module, for sending landing request information to server, this landing request information comprises the app identification code appID of the EIC equipment identification code deviceID of mobile terminal and the app of request login;
Log-on message receiver module, for receiving the log-on message that described server returns, wherein, this log-on message is the EIC equipment identification code deviceID and app identification code appID that are comprised based on landing request information by described server, inquire about log database to confirm whether this mobile terminal has other app log in, and generate according to login Query Result;
App login module, for according to described log-on message, logs in the app that described request logs in.
22. mobile terminals according to claim 21, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, the listed login account of other app described that described app login module returns for receiving described server, the app logged in for described request selects this account and logs in.
23. mobile terminals according to claim 21, wherein, if log in Query Result to represent that described mobile terminal has other app to log in, described app login module is for receiving the operational credentials of the listed login account of other app described of described server transmission and the app generation for described request login, described listed login account, and carry out inputting, to log according to described operational credentials.
24. mobile terminals according to claim 23, wherein,
The once login of described operational credentials only for the app of described request login is effective.
25. mobile terminals according to claim 24, also comprise:
Logging on authentication receiver module, the logging on authentication token that returns of server during for receiving the app Successful login when described request logs in;
Memory, for storing logging on authentication token and described EIC equipment identification code deviceID, described app identification code appID, described login account explicitly.
26. mobile terminals according to any one of claim 21 to 25, wherein, described app identification code appID is app on the mobile terminal when running first, generates based on the described EIC equipment identification code deviceID of described mobile terminal and the app title of this app.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510050671.3A CN104601590B (en) | 2015-01-30 | 2015-01-30 | A kind of login method, server and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510050671.3A CN104601590B (en) | 2015-01-30 | 2015-01-30 | A kind of login method, server and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104601590A true CN104601590A (en) | 2015-05-06 |
| CN104601590B CN104601590B (en) | 2018-02-27 |
Family
ID=53127095
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510050671.3A Active CN104601590B (en) | 2015-01-30 | 2015-01-30 | A kind of login method, server and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104601590B (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105045801A (en) * | 2015-05-20 | 2015-11-11 | 天脉聚源(北京)传媒科技有限公司 | Login avatar displaying method, apparatus and system |
| CN105072133A (en) * | 2015-08-28 | 2015-11-18 | 北京金山安全软件有限公司 | Login method and device for application program |
| CN105450637A (en) * | 2015-11-09 | 2016-03-30 | 歌尔声学股份有限公司 | Single sign-on method and device for multiple application systems |
| CN106161003A (en) * | 2016-08-21 | 2016-11-23 | 乐视控股（北京）有限公司 | Application program login method and terminal, system |
| CN106650351A (en) * | 2016-10-31 | 2017-05-10 | 维沃移动通信有限公司 | running method of application program and mobile terminal |
| CN107294967A (en) * | 2017-06-21 | 2017-10-24 | 浙江唯见科技有限公司 | One kind shares unrestricted login system and method |
| CN107517181A (en) * | 2016-06-15 | 2017-12-26 | 西安艾润物联网技术服务有限责任公司 | Using startup method and device |
| CN107645486A (en) * | 2016-12-28 | 2018-01-30 | 平安科技（深圳）有限公司 | Login authentication method and device |
| CN108200072A (en) * | 2018-01-12 | 2018-06-22 | 深圳市富途网络科技有限公司 | A kind of more Account Administration login systems |
| CN108259431A (en) * | 2016-12-29 | 2018-07-06 | 航天信息股份有限公司 | The method, apparatus and system of account information are shared between applying more |
| CN109150910A (en) * | 2018-10-11 | 2019-01-04 | 平安科技（深圳）有限公司 | Log in token generation and verification method, device and storage medium |
| CN109582450A (en) * | 2018-11-02 | 2019-04-05 | 平安科技（深圳）有限公司 | Application management method, device, medium and electronic equipment |
| WO2019079928A1 (en) * | 2017-10-23 | 2019-05-02 | 华为技术有限公司 | Access token management method, terminal and server |
| CN110011989A (en) * | 2019-03-21 | 2019-07-12 | 武汉炎阳在线科技有限公司 | A kind of account login method, answer method, display equipment and keeps |
| CN110633435A (en) * | 2019-08-22 | 2019-12-31 | 四川仁来仁网智能科技有限公司 | Browsing method between APPs based on content sharing |
| CN111598592A (en) * | 2020-05-27 | 2020-08-28 | 刘晏周 | Tracing certificate code anti-counterfeiting system and method thereof |
| CN113132362A (en) * | 2021-03-31 | 2021-07-16 | 青岛中瑞汽车服务有限公司 | Trusted authorization method, trusted authorization device, electronic equipment and storage medium |
| WO2021143028A1 (en) * | 2020-01-13 | 2021-07-22 | 平安科技（深圳）有限公司 | Internet of things equipment authentication method, electronic device and storage medium |
| CN113612756A (en) * | 2021-07-29 | 2021-11-05 | 广州博冠信息科技有限公司 | Shared login method and device, computer readable storage medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101960462A (en) * | 2008-02-28 | 2011-01-26 | 日本电信电话株式会社 | Authentication device, authentication method, and authentication program with the method mounted thereon |
| US20120291114A1 (en) * | 2011-05-13 | 2012-11-15 | Cch Incorporated | Single sign-on between applications |
| CN103188221A (en) * | 2011-12-28 | 2013-07-03 | 腾讯科技（深圳）有限公司 | Application login method, application login device and mobile terminal |
| CN104270399A (en) * | 2014-10-28 | 2015-01-07 | 用友软件股份有限公司 | Login method and login device for application program |
-
2015
- 2015-01-30 CN CN201510050671.3A patent/CN104601590B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101960462A (en) * | 2008-02-28 | 2011-01-26 | 日本电信电话株式会社 | Authentication device, authentication method, and authentication program with the method mounted thereon |
| US20120291114A1 (en) * | 2011-05-13 | 2012-11-15 | Cch Incorporated | Single sign-on between applications |
| CN103188221A (en) * | 2011-12-28 | 2013-07-03 | 腾讯科技（深圳）有限公司 | Application login method, application login device and mobile terminal |
| CN104270399A (en) * | 2014-10-28 | 2015-01-07 | 用友软件股份有限公司 | Login method and login device for application program |
Cited By (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105045801A (en) * | 2015-05-20 | 2015-11-11 | 天脉聚源(北京)传媒科技有限公司 | Login avatar displaying method, apparatus and system |
| CN105072133B (en) * | 2015-08-28 | 2018-07-10 | 北京金山安全软件有限公司 | Login method and device for application program |
| CN105072133A (en) * | 2015-08-28 | 2015-11-18 | 北京金山安全软件有限公司 | Login method and device for application program |
| CN105450637A (en) * | 2015-11-09 | 2016-03-30 | 歌尔声学股份有限公司 | Single sign-on method and device for multiple application systems |
| CN107517181B (en) * | 2016-06-15 | 2019-10-29 | 西安艾润物联网技术服务有限责任公司 | Using starting method and device |
| CN107517181A (en) * | 2016-06-15 | 2017-12-26 | 西安艾润物联网技术服务有限责任公司 | Using startup method and device |
| CN106161003A (en) * | 2016-08-21 | 2016-11-23 | 乐视控股（北京）有限公司 | Application program login method and terminal, system |
| CN106650351A (en) * | 2016-10-31 | 2017-05-10 | 维沃移动通信有限公司 | running method of application program and mobile terminal |
| CN107645486A (en) * | 2016-12-28 | 2018-01-30 | 平安科技（深圳）有限公司 | Login authentication method and device |
| CN108259431A (en) * | 2016-12-29 | 2018-07-06 | 航天信息股份有限公司 | The method, apparatus and system of account information are shared between applying more |
| CN107294967A (en) * | 2017-06-21 | 2017-10-24 | 浙江唯见科技有限公司 | One kind shares unrestricted login system and method |
| WO2019079928A1 (en) * | 2017-10-23 | 2019-05-02 | 华为技术有限公司 | Access token management method, terminal and server |
| US11736292B2 (en) | 2017-10-23 | 2023-08-22 | Huawei Technologies Co., Ltd. | Access token management method, terminal, and server |
| CN110121873A (en) * | 2017-10-23 | 2019-08-13 | 华为技术有限公司 | A kind of access token management method, terminal and server |
| CN110121873B (en) * | 2017-10-23 | 2021-06-01 | 华为技术有限公司 | Access token management method, terminal and server |
| CN108200072A (en) * | 2018-01-12 | 2018-06-22 | 深圳市富途网络科技有限公司 | A kind of more Account Administration login systems |
| CN109150910A (en) * | 2018-10-11 | 2019-01-04 | 平安科技（深圳）有限公司 | Log in token generation and verification method, device and storage medium |
| CN109582450A (en) * | 2018-11-02 | 2019-04-05 | 平安科技（深圳）有限公司 | Application management method, device, medium and electronic equipment |
| CN109582450B (en) * | 2018-11-02 | 2024-05-03 | 平安科技（深圳）有限公司 | Application program management method, device, medium and electronic equipment |
| CN110011989A (en) * | 2019-03-21 | 2019-07-12 | 武汉炎阳在线科技有限公司 | A kind of account login method, answer method, display equipment and keeps |
| CN110633435A (en) * | 2019-08-22 | 2019-12-31 | 四川仁来仁网智能科技有限公司 | Browsing method between APPs based on content sharing |
| WO2021143028A1 (en) * | 2020-01-13 | 2021-07-22 | 平安科技（深圳）有限公司 | Internet of things equipment authentication method, electronic device and storage medium |
| CN111598592A (en) * | 2020-05-27 | 2020-08-28 | 刘晏周 | Tracing certificate code anti-counterfeiting system and method thereof |
| CN113132362A (en) * | 2021-03-31 | 2021-07-16 | 青岛中瑞汽车服务有限公司 | Trusted authorization method, trusted authorization device, electronic equipment and storage medium |
| CN113132362B (en) * | 2021-03-31 | 2022-03-22 | 青岛中瑞汽车服务有限公司 | Trusted authorization method, trusted authorization device, electronic equipment and storage medium |
| CN113612756A (en) * | 2021-07-29 | 2021-11-05 | 广州博冠信息科技有限公司 | Shared login method and device, computer readable storage medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104601590B (en) | 2018-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104601590A (en) | Login method, server and mobile terminal | |
| CN108768970B (en) | Binding method of intelligent equipment, identity authentication platform and storage medium | |
| CN108462710B (en) | Authentication and authorization method, device, authentication server and machine-readable storage medium | |
| CN107241339B (en) | Identity authentication method, identity authentication device and storage medium | |
| CN107979514A (en) | A kind of method and apparatus bound to equipment | |
| CN105187450A (en) | Authentication method and device based on authentication equipment | |
| CN104125565A (en) | Method for realizing terminal authentication based on OMA DM, terminal and server | |
| CN104639562A (en) | Work method of authentication pushing system and equipment | |
| CN105187431A (en) | Log-in method, server, client and communication system for third party application | |
| US11177963B2 (en) | Method for authenticating a user based on an image relation rule and corresponding first user device, server and system | |
| CN105262588A (en) | Log-in method based on dynamic password, account number management server and mobile terminal | |
| CN114189863B (en) | Binding method and device of intelligent door lock, storage medium and electronic device | |
| CN105722072A (en) | Business authorization method, device, system and router | |
| EP3851983A1 (en) | Authorization method, auxiliary authorization component, management server and computer readable medium | |
| CN114390524B (en) | Method and device for realizing one-key login service | |
| CN109120611B (en) | User authentication method, apparatus, system and medium for address generation server | |
| CN105099686A (en) | Data synchronization method, server, terminal and system | |
| WO2018219260A1 (en) | Method, device and system for binding mobile phone number | |
| CN114157693A (en) | Power-on authentication method of communication equipment, communication module and server | |
| CN105141624A (en) | Login method, account management server and client system | |
| CN115840937B (en) | Control method and device and electronic equipment | |
| CN105553675B (en) | Log in the method and device of router | |
| CN106790364A (en) | A kind of remote entry method and device | |
| CN114158046B (en) | Method and device for realizing one-key login service | |
| CN105812138A (en) | Logging-in processing method, processing device, user terminal, and logging-in system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information |
Inventor after: Chen Liping Inventor after: Gu Feiyong Inventor after: Yu Lihua Inventor after: Wang Yuan Inventor after: Chen Gang Inventor before: Chen Liping Inventor before: Gu Feiyong |
|
| COR | Change of bibliographic data | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |