CN104601590B - A kind of login method, server and mobile terminal - Google Patents

A kind of login method, server and mobile terminal Download PDF

Info

Publication number
CN104601590B
CN104601590B CN201510050671.3A CN201510050671A CN104601590B CN 104601590 B CN104601590 B CN 104601590B CN 201510050671 A CN201510050671 A CN 201510050671A CN 104601590 B CN104601590 B CN 104601590B
Authority
CN
China
Prior art keywords
app
login
mobile terminal
logged
log
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201510050671.3A
Other languages
Chinese (zh)
Other versions
CN104601590A (en
Inventor
陈李平
顾费勇
余利华
汪源
陈刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Netease Hangzhou Network Co Ltd
Original Assignee
Netease Hangzhou Network Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Netease Hangzhou Network Co Ltd filed Critical Netease Hangzhou Network Co Ltd
Priority to CN201510050671.3A priority Critical patent/CN104601590B/en
Publication of CN104601590A publication Critical patent/CN104601590A/en
Application granted granted Critical
Publication of CN104601590B publication Critical patent/CN104601590B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815Network 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)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Embodiments of the present invention provide a kind of login method.This method includes:The landing request information that mobile terminal is sent is received, the landing request information includes the deviceID of the mobile terminal and asks the app appID logged in;The deviceID and appID included based on the landing request information received, log database is inquired about to confirm whether there are other app to log on the mobile terminal;According to Query Result is logged in, log-on message is returned to the mobile terminal, so that the app that the request logs in is logged in.By the method for the above-mentioned embodiment of the present invention, shared logging status can be provided for multiple app of operator, simplify user login operation, more preferable experience is brought for user, and user's conversion ratio can be brought to operator, enhancing user's viscosity.In addition, embodiments of the present invention provide a kind of server and mobile terminal.

Description

A kind of login method, server and mobile terminal
Technical field
Embodiments of the present invention are related to app application fields, more specifically, embodiments of the present invention are related to a kind of login Method, server and mobile terminal.
Background technology
This part is it is intended that the embodiments of the present invention stated in claims provide background or context.Herein Description recognizes it is prior art not because not being included in this part.
The use of portable electric appts is increasingly extensive at present, and each company is proposed largely to be made for user in mobile terminal Application program (app), such as Baidu map, Baidu's mhkc, Baidu's video etc..For same company (such as Baidu) App, presently mainly by being communicated between app to obtain logging status, and then using a pass account each app it Between pass through.
It is logical between 2 app but communication can not be realized substantially in IOS systems between app, and in other systems Letter is still realized, but app occurs that communication disaster, such as 10 app cross-communications just need 10*9=90 to lead to more once Letter, and the communication between whole company app is even more excessively poor in enforceability.
The content of the invention
The reason for disaster that communicated when app quantity is big between app, in the prior art, user sets in same mobile terminal When on standby using the app of same operator, it is impossible to realize well " shared to log in ".In the context of this application, it is " shared to step on Record " refers to:It is another on the mobile terminal is started in the case that an app on mobile terminals is in logging status During app, without being manually entered account, password again, you can complete to step on using the login account of the app in logging status Record.
In addition, in the case where that can not realize shared log in, app has published (logout) or has been required for when first logging into defeated Enter account, password, this is very bothersome process.
Therefore, a kind of improved login method is highly desirable to, to realize the shared login between app.
In the present context, embodiments of the present invention it is expected to provide a kind of login method, server and mobile terminal.
In the first aspect of embodiment of the present invention, there is provided a kind of login method, for example, can include:Receive and move The landing request information that dynamic terminal is sent, the landing request information include the EIC equipment identification code deviceID of the mobile terminal and asked Seek the app of login app identification codes appID;The EIC equipment identification code included based on the landing request information received DeviceID and app identification code appID, log database is inquired about to confirm whether there are other app to log on the mobile terminal; According to Query Result is logged in, log-on message is returned to the mobile terminal, so that the app that the request logs in is logged in.
In the second aspect of embodiment of the present invention, there is provided a kind of login method, for example, can include:Transmission is stepped on Solicited message is recorded to server, the landing request information includes the EIC equipment identification code deviceID of mobile terminal and asks what is logged in App app identification codes appID;The log-on message that the server returns is received, wherein, the log-on message is by the service EIC equipment identification code deviceID and app the identification code appID that device is included based on the landing request information, inquire about logon data Storehouse to confirm whether there are other app to log on the mobile terminal, and according to log in Query Result generate;According to the login Information, the app logged in the request are logged in.
In the third aspect of embodiment of the present invention, there is provided a kind of server, for example, can include:Logging request Information receiving module, for receiving the landing request information of mobile terminal transmission, the landing request information includes the mobile terminal EIC equipment identification code deviceID and request log in app app identification codes appID;Enquiry module is logged in, for based on being connect EIC equipment identification code deviceID and app the identification code appID that the landing request information of receipts includes, inquiry log database is with true Whether recognize on the mobile terminal has other app to log in;Login process module, for according to log in Query Result, to the shifting Dynamic terminal returns to log-on message, so that the app that the request logs in is logged in.
In the fourth aspect of embodiment of the present invention, there is provided a kind of mobile terminal, for example, can include:Logging in please Information sending module is sought, the equipment for including mobile terminal to server, the landing request information for sending landing request information The app identification codes appID for the app that identification code deviceID and request log in;Log-on message receiving module, for receiving the clothes The log-on message that business device returns, wherein, the log-on message is the equipment included by the server based on landing request information Identification code deviceID and app identification code appID, log database is inquired about to confirm whether there are other app on the mobile terminal It has been logged in that, and generated according to login Query Result;App login modules, for according to the log-on message, being stepped on to the request The app of record is logged in.
Can be that multiple app of operator are carried by the login method, server and mobile terminal of embodiment of the present invention For sharing login mechanism, so as to simplify user login operation, more preferable experience is brought for user, and operator can be given Bring user's conversion ratio, enhancing user's viscosity.
Brief description of the drawings
Detailed description below, above-mentioned and other mesh of exemplary embodiment of the invention are read by reference to accompanying drawing , feature and advantage will become prone to understand.In the accompanying drawings, if showing the present invention's by way of example, and not by way of limitation Dry embodiment, 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 show the data structure schematic diagram of log database according to embodiments 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
The principle and spirit of the present invention is described below with reference to some illustrative embodiments.It should be appreciated that provide this A little embodiments are not with any just for the sake of better understood when those skilled in the art and then realize the present invention Mode limits the scope of the present invention.On the contrary, these embodiments are provided so that the disclosure is more thorough and complete, and energy It is enough that the scope of the present disclosure is intactly communicated to those skilled in the art.
Art technology technical staff knows, embodiments of the present invention can be implemented as a kind of system, device, equipment, Method or computer program product.Therefore, the disclosure can be implemented as following form, i.e.,:It is complete hardware, complete soft Part (including firmware, resident software, microcode etc.), or the form that hardware and software combines.
According to the embodiment of the present invention, it is proposed that a kind of login method, server and mobile terminal.
Herein, it is to be understood that in involved term:
1st, EIC equipment identification code (deviceID):Given birth to when app starts first by server according to the metadata of mobile terminal Into equipment unique identifier, different platform generation scheme is different, is generated by defined cipher mode.For example, for android Terminal, metadata can include mobile phone model, MAC Address (physical address), resolution ratio, OS name etc.;It is whole for IOS End, metadata can include IDFV, keychain that operating system provides etc..
2nd, app identification codes (appID):Each app unique identifiers (ID) of distribution are given by server.AppID is to move When app in dynamic terminal is run first, the deviceID and the app that are sent based on mobile terminal app names associates generation. So, in login process, after server receives the data of mobile terminal transmission every time, it can examine and send in data Whether deviceID and appID matches, and is logged in prevent user using the appID for forging or distorting.
3rd, logging on authentication (token):After the app of mobile terminal is with a certain account Successful login, server generates one Token (corresponds to a deviceID, appID and account).Server can by token and deviceID, AppID and login account are stored in the addressable log database of server in association, while can also be by the token Mobile terminal is sent to be preserved.So, when user closes (rather than publishing (logout)) app and is again turned on app, move The token of preservation can be sent to server to carry out matching checking with the token stored at server by dynamic terminal, work as confirmation During matching, automated log on.After account is published, corresponding token failures.For example, server is received after account publishes instruction, delete Except the token, and issue one and instruct and accordingly delete the token to mobile terminal, mobile terminal.
4、key:It is used for mobile terminal and service on each mobile terminal by server-assignment when app starts first The key that communication protocol is encrypted between device.
5th, operational credentials:Such as can be " identifying code " or " it is required that sending the voucher for confirming to log in instruction ", and once Effectively.For identifying code, when can issue login account by server, mobile terminal is sent in the lump, needs user to select account And it could be logged in after correctly entering identifying code.For " it is required that sending the voucher for confirming to log in instruction ", stepped in user's selection After record account, mobile terminal can send one " confirming to log in instruction " to server, and receiving this, " confirmation logs in server After instruction ", complete to log in.
In addition, any number of elements in accompanying drawing is used to example and unrestricted, and any name is only used for distinguishing, Without any restrictions implication.
Below with reference to the principle and spirit of some representative embodiments of the present invention, in detail the explaination present invention.
Summary of the invention
Conventionally, after user starts a certain app on (such as activation, opening) mobile terminal, mobile terminal is examined first Look into and locally whether be stored with corresponding token;If so, showing that the app has been logged in, then token directly is sent to server, by taking Business device carries out checking login according to the token of storage;If not provided, showing that the app is not yet logged in or published, then carry out " often Rule log in ", that is, need that user is manually entered account, password is logged in.So, for user in login account, operation is comparatively laborious.
Therefore, the invention provides a kind of shared login mechanism.Sharing the process logged in can be:Mobile terminal is to service Device sends landing request information;Server judges whether have other app to log on the mobile terminal based on landing request information, And log-on message is returned to mobile terminal according to Query Result is logged in, the app logged in for request is logged in.So, existing In the case that other app are logged in, user need not repeatedly input pass account and/or login password, need to only select server to return The account returned can quick registration app.
Alternatively, in the case where mobile terminal is stored with token, user can also select to initiate shared login process, Realize the shared login account logged on other app.
Herein, other app can be the app of the same operators of app logged on same mobile terminal with request.
After the general principle of the present invention is described, lower mask body introduces the various non-limiting embodiment party of the present invention Formula.
Application scenarios overview
With reference first to Fig. 1, server 100 can be pass server etc., and mobile terminal 200 can be mobile phone, flat board Computer etc..Between mobile terminal 200 and server 100 such as can by mobile Internet be communicatively coupled.
Using login method provided in an embodiment of the present invention, when user starts on (such as activation, opening) mobile terminal 200 A certain app when, not yet log in or published state as the app is in, then can trigger a shared login process:By mobile terminal 200 send landing request information to server 100;Server 100 is inquired about based on landing request information, and is looked into according to login Ask result and return to log-on message to mobile terminal 200;User utilizes the shared account logged in of the selection of mobile terminal 200;Server 100 receive and authorize the login of the account.Realize app shared login.
If app is logged and not yet publish with a certain account, i.e., equal at mobile terminal 200 and server 100 Corresponding logging on authentication (token) is stored with, then when starting the app, checking login only can be carried out by token.
Example devices
With reference to Fig. 1 application scenarios, with reference to figure 2, Fig. 3 respectively to the server of exemplary embodiment of the invention 100th, mobile terminal 200 is introduced.
Understand spirit and principles of the present invention it should be noted that above-mentioned application scenarios are for only for ease of and show, this The embodiment of invention is unrestricted in this regard.On the contrary, embodiments of the present invention can apply to it is applicable any Scene.
For example, with reference to Fig. 2, for the device structure schematic diagram of server 100 provided in an embodiment of the present invention.As illustrated, Server 100 can include:Landing request information receiving module 101, log in enquiry module 102, login process module 103, step on Record database 104.In addition, server 100 can also include logging on authentication generation module 105.
Referring to Fig. 3, for the device structure schematic diagram of mobile terminal 200 provided in an embodiment of the present invention.It is as illustrated, mobile Terminal 200 can include:Landing request information sending module 201, log-on message receiving module 202, app login modules 203.This Outside, mobile terminal 200 can also include logging on authentication receiving module 204, memory 205.
Reference picture 3, when user starts a certain app on (such as activation, opening) mobile terminal 200, if at the app In not yet logging in or having published state, then a shared login process can be triggered.Landing request information hair in mobile terminal 200 Module 201 is sent to send landing request information to server 100, wherein, the landing request information can include mobile terminal 200 The appID for the app that deviceID and request log in.
As it was previously stated, the deviceID of mobile terminal 200 is to be given birth to by server 100 according to the metadata of mobile terminal 200 Into equipment unique identifier, different platform generation scheme is different, is generated by specific cipher mode, asks the app logged in AppID be that deviceID based on mobile terminal 200 and app app names associates generate.Alternatively, logged Cheng Zhong, after server 100 receives the data of the transmission of mobile terminal 200 every time, the deviceID sent in data can be examined Whether match with appID, logged in prevent user using the appID for forging or distorting.
Referring next to Fig. 2, the landing request information receiving module 101 in server 100 receives above-mentioned landing request information. DeviceID and appID that enquiry module 102 is included based on the landing request information received are logged in, inquires about log database 104, to confirm whether there are other app to log on the mobile terminal 200.
Specifically, can be by deviceID, appID, login account and login for listed app, server 100 State is stored in log database 104 in association, when receiving landing request information, to be inquired about.
Fig. 4 A-4B schematically show the data structure of 104 storage contents of log database.
For example, it was found from Fig. 4 A, for the mobile terminal that deviceID is " Terminal_Z ", existing appID is " Z_ 163_app1 " and " Z_163_app2 " two app are logged 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, it can also be stored in association with listed app and account in log database 104 Corresponding logging on authentication.For example, for " Z_163_app1 ", login account Account_A, Account_B are stored respectively Logging on authentication token_1, token_3;For " Z_163_app2 ", login account Account_A, Account_ are stored respectively C logging on authentication token_2, token_4.After account publishes (logout), logging on authentication associated therewith will fail.
In addition, one " logging status " mark can also be accordingly stored in log database 4 with deviceID, for referring to Show on the mobile terminal 200 corresponding to the deviceID that whether having app is in logging status.
For example, as shown in Figure 4 A, for deviceID " Terminal_Z ", there are two app " Z_163_app1 ", " Z_ 163_app2 " is in logging status, and therefore " logging status " is masked as " Z_163_LOG_ON ", it means that other app can be with Carry out " shared to log in ".
As shown in Fig. 4 B, 4C, for deviceID " Terminal_Z ", although the app/ accounts in logging status have change Change, still " logging status " mark keeps constant, is still " Z_163_LOG_ON ".
So, server 100 need to only be inquired about correspondingly when receiving the landing request information that mobile terminal 200 is sent Logging status " whether having other app to log on mobile terminal 200 " would know that, it is " shared to step on to determine whether to carry out Record ".
With continued reference to Fig. 2, after logging in enquiry module 102 and inquiring about log database 104, the basis of login process module 103 Query Result is logged in, log-on message is returned to mobile terminal 200, so that the app that request logs in is logged in.
Specifically, indicate to be in logging status without other app if logged on Query Result, then login process module 103 can To return to the log-on message of an instruction " conventional login " to mobile terminal 200, so that user's input account and password are logged in.
There are other app to be in logging status if logged on Query Result instruction, then login process module 103 can generate simultaneously " log-on message " of shared login can be carried out by returning to an instruction to mobile terminal 200, be somebody's turn to do " log-on message " and stepped on including other app The account of record.So, user can be directed to the app selection accounts that request logs in, and carry out shared login, account is logged in without inputting Number and password.
For example, as shown in Figure 4 B, according to the storage content of log database 104, for (the deviceID of mobile terminal 200: Terminal_Z app1 (appID):Z_163_app1), logged in account Account_A.So, start in user another app(appID:Z_163_app2 in the case of), it is " shared that login process module 103 can return to an instruction to mobile terminal 200 Login " and " log-on message " including account Account_A.User selects account Account_A, you can realizes being total to for app2 Login is enjoyed, without being manually entered account and password again.After app2 realizes shared log in, the storage of log database 104 Content is changed into as shown in Figure 4 C.
Alternatively, " log-on message " that login process module 103 is generated and returned to mobile terminal 200 can also include pin The app logged in request operational credentials.The operational credentials for example can be " identifying code " or " confirm log in instruction ", and one It is secondary effective.For identifying code, when can return to " log-on message " by server 100, mobile terminal 200 is sent in the lump, needs to use Family selects account and could logged in after correctly entering identifying code.For confirming to log in instruction, login account is have selected in user After number, mobile terminal 200 can send " the confirming to log in instruction " of user's triggering to server 100, and server 100 is connecing After receiving " confirm log in instruction ", once can only effectively be handled, token corresponding to generation, after the completion of fail, and It can not reuse.
With continued reference to Fig. 3, login that the reception server 100 of log-on message receiving module 202 in mobile terminal 200 returns Information, so that app login modules 203 are logged according to the log-on message.
For example, if logged on information instruction " conventional login " (being in logging status without other app), then app logs in mould Account, Password Input frame is presented in block 203, so that user inputs account and the password associated, is logged in.
Shared login can be carried out if logged on information instruction, then stepping on for log-on message carrying is presented in app login modules 203 Account is recorded, account is selected for user, carries out shared login.After user selects account, app login modules 203 select user Account is sent to server 100.
Alternatively, as it was previously stated, as server 100 generate and " log-on message " that returns also carry " operate with Card ", then corresponding operational credentials can be presented in app login modules 203, so that user/mobile terminal 200 performs corresponding operating.
Server 100 receives the account of user's selection, and the account logins successfully on the app that request logs in.Server 100 Logging on authentication generation module 105 can generate logging on authentication token corresponding to the app and the account, and by the login with Card is stored in log database 104 in association with corresponding deviceID, appID, login account, while is sent to movement Terminal 200.The logging on authentication token that the reception server 100 of logging on authentication receiving module 204 of mobile terminal 200 returns, and will Logging on authentication token is stored in memory 205 in association with deviceID, with appID, login account.
So, when user starts a certain app on (such as activation, opening) mobile terminal 200, mobile terminal 200 can To first determine whether corresponding token whether is stored with memory 205.If being stored with corresponding token, show to have logged in, then move Dynamic terminal 200 directly can send token to server 100, carry out checking login.If there is this app pairs in memory 205 Other token answered, i.e. user have logged in multiple accounts on the app, then user can log in it by account switching mode His account.If not storing corresponding token, show that app is not yet logged in or published, shared login process can be initiated, to Server 100 sends landing request information.
Alternatively, in the case where there is token, user can also select to initiate shared login process, realize shared log in Login account on other app.
In the above-described embodiments, can be referring again to shown in Fig. 4 A, for example, user uses app1 (appID:Z_163_app1) When, the account of login is " Account_A ".After closing the app.If user is again started up app1, mobile terminal is according to closing During app1, listed account is " Account_A ", sends the token_1 of storage to server, verifies and log in the account.
Alternatively, if user wants to switch account, account handoff functionality, mobile terminal inspection can be triggered on mobile terminals Measure and be locally also stored with token_3, corresponding account " Account_B " is presented to user.It is mobile if switching the account Terminal sends token_3 to server, the checking login account.
Alternatively, if user wants to log in other more accounts, shared login process can be initiated, as shown in Figure 4 A, Mobile terminal can obtain account " Account_C ", be presented to user, and user can select the login account on app1 “Account_C”。
Alternatively, if user starts app3 (appID first:Z_163_app3, not shown), mobile terminal detects this Ground does not store the corresponding token of app3.Shared login process is then initiated, landing request information is sent to server.According to figure Shown in 4A, mobile terminal can obtain the account " Account_A " of server return, " Account_B ", " Account_C ", supply User selects.
In the above-described embodiments, the app shared login of account is realized, register is simplified, improves the easy-to-use of app Property.
Alternatively, to guarantee safety, prevent attacker from forging request, own between server 100 and mobile terminal 200 Transmitting procedure can be encrypted using key, and appID is all attached in each transmission, and server 100 handles mobile terminal hair During the data sent, it can verify whether the appID in data is effective, to increase the reliability of transmission information.For example, server 100 Whether can be matched with the deviceID in inspection data and appID, be stepped on to prevent user using the appID for forging or distorting Record.
Alternatively, server 100 can also be by limiting the same IP or same appID unit interval (such as one hour) The number of shared logging request is initiated to take precautions against scanning probe of the mobile terminal 200 to deviceID.For example, when same IP, When the number of the shared logging request of initiation exceedes pre-determined number in the same appID unit interval, shared login work(can be disabled Can, and require user and carry out conventional login.
Alternatively, server 100 can add last layer mandate to app, to strengthen security.For example, each app is being issued When built-in can be used to encrypt and the public key of signature verification, can be with this public key to agreement when with server communication Parameter generates encryption information, and the signing messages returned to server end is verified.
The app realized by the server and mobile terminal of the above-mentioned embodiment of the present invention shares login mode, for operation Multiple app of business (same operator) provide shared logging status, are especially emerged in multitude in current app, operator App may be a lot, and user login operation is simplified by the login mode, and more preferable experience is brought for user, and can To bring huge user's conversion ratio, enhancing user's viscosity to operator.
Illustrative methods
After the equipment of exemplary embodiment of the invention is described, next, with reference to figure 5 to the exemplary reality of the present invention The login method for applying mode is introduced.
Fig. 5 is the schematic flow sheet of login method provided in an embodiment of the present invention.Referring to the figure to login method Flow is described.
First, the app on mobile terminal (mobile terminal 200 as shown in Figure 1) is started in step S701, user.
In step S702, mobile terminal judges locally whether be stored with logging on authentication token.If result is "Yes", Proceed to step S703;If result is "No", shared login process is triggered, proceeds to step S704.
In step S703, mobile terminal directly sends token to server (server 100 as shown in Figure 1), carries out Checking logs in.Alternatively, after checking logs in, user can select to initiate shared login process, realize shared log on other app Login account.
In step S704, shared login process is initiated, mobile terminal sends landing request information to server.Wherein, should Landing request information can include the deviceID of mobile terminal and the app of request login appID.
In step S705, server receives landing request information.
In the deviceID and appID that step S706, server are included based on the landing request information received, inquiry Log database is to confirm whether have other app to log on the mobile terminal.If result is "No", proceed to step S707;If result is "Yes", proceed to step S708.
In step S707, server can send the log-on message of " conventional login " to mobile terminal.In the case, use Family need to input account, password carries out conventional login.
In step S708, server returns to an instruction to mobile terminal can carry out the log-on message of shared login, the login Information can include the listed login accounts of other app.Alternatively, the log-on message can also include what is logged in for request App's once operates effectively voucher.
In the log-on message that step S709, mobile terminal the reception server are returned.
In step S710, the listed login account that user shows to mobile terminal according to log-on message selects Select, so as to carry out shared login.Alternatively, in the case where log-on message includes operational credentials, user/mobile terminal need to also be according to Operated according to operational credentials.
In step S711, the login account that server is selected user logs in.Also, step on also directed to the app this Record account and generate corresponding token, and the token and deviceID, appID, login account are stored in association, together When be sent to mobile terminal.
In the token that step S712, mobile terminal storage server are returned, shared log in is completed.
By the login mode of the above-mentioned embodiment of the present invention, shared login shape can be provided for multiple app of operator State, user login operation is simplified, bring more preferable experience for user, and huge user can be brought to operator Conversion ratio, enhancing user's viscosity.
It should be noted that although describing the operation of the inventive method with particular order in the accompanying drawings, still, this is not required that Or imply and must perform these operations according to the particular order, or the operation having to carry out shown in whole could realize the phase The result of prestige.Additionally or alternatively, it is convenient to omit some steps, multiple steps are merged into a step and performed, and/or will One step is decomposed into execution of multiple steps.
For example, the step S701 performed in mobile terminal side, step S702, step S707, step S712, in server Step S703 steps that side performs, S711, are only the optional steps for implementing the shared login of the present invention, lack it is some of or The realization of the basic goal of the invention of the present invention is not interfered with all.
In addition, although being referred to some modules of server, mobile terminal in above-detailed, but this division It is only not enforceable.In fact, according to the embodiment of the present invention, the feature of two or more above-described devices and Function can embody in one apparatus.Equally, the feature of an above-described device and function can also further be drawn It is divided into by multiple devices to embody.
Although describe spirit and principles of the present invention by reference to some embodiments, it should be appreciated that, this Invention is not limited to disclosed embodiment, and the division to each side does not mean that the feature in these aspects can not yet Combination is to be benefited, and this division is merely to the convenience of statement.It is contemplated that cover appended claims spirit and In the range of included various modifications and equivalent arrangements.

Claims (26)

1. a kind of login method, including:
The landing request information that mobile terminal is sent is received, the landing request information includes the EIC equipment identification code of the mobile terminal The app identification codes appID for the app that deviceID and request log in;
EIC equipment identification code deviceID and app the identification code appID included based on the landing request information received, inquiry are stepped on Database is recorded to confirm whether there are other app to log on the mobile terminal;
Conventional login information is returned to when logging in Query Result instruction and being in logging status without other app, when login Query Result Instruction has other app to return to shared log-on message when being in logging status, so that the app that the request logs in is logged in.
2. login method according to claim 1, wherein, the log database is by the EIC equipment identification code DeviceID, app identification codes appID, login account and the logging status are stored in association.
3. login method according to claim 2, wherein, represent there is it on the mobile terminal if logged on Query Result His app has been logged in, and is included to the step of mobile terminal return conventional login information or shared log-on message:
The listed login accounts of other described app are returned to the mobile terminal, so that the app selections that the request logs in should Account is simultaneously logged in.
4. login method according to claim 2, wherein, represent there is it on the mobile terminal if logged on Query Result His app has been logged in, and this method also includes:
The operational credentials for the app that generation logs in for the request,
And the step of wherein, returning to conventional login information or shared log-on message to the mobile terminal includes:
The listed login accounts of other app and the app logged in for the request behaviour are returned to the mobile terminal Make voucher, inputted for the app selections listed login account for asking to log in and according to the operational credentials, To be logged in.
5. login method according to claim 4, wherein,
The once login for the app that the operational credentials log in only for the request is effective.
6. login method according to claim 5, in addition to:
When it is described request log in app Successful logins when, generate logging on authentication token, and in the log database with institute State EIC equipment identification code deviceID, the app identification codes appID, the login account to be stored in association, send simultaneously To the mobile terminal.
7. the login method according to any one of claim 1 to 6, wherein, the app identification codes appID is described When app on mobile terminal is run first, the EIC equipment identification code deviceID and the app that are sent based on the mobile terminal App titles generation.
8. a kind of login method, including:
Landing request information is sent to server, the landing request information include mobile terminal EIC equipment identification code deviceID and Ask the app app identification codes appID logged in;
Conventional login information or the shared log-on message that the server returns are received, wherein, the conventional login information or shared Log-on message is to be identified by the server based on the EIC equipment identification code deviceID and app that the landing request information includes Code appID, inquiry log database are tied with confirming whether have other app to log on the mobile terminal according to inquiry is logged in Fruit generation;Wherein, when login Query Result instruction is in logging status without other app, generation is conventional login information, When login Query Result instruction has other app to be in logging status, generation is shared log-on message;
According to the conventional login information or shared log-on message, the app logged in the request is logged in.
9. login method according to claim 8, wherein, represent there is it on the mobile terminal if logged on Query Result His app has been logged in, and according to the conventional login information or shared log-on message, the app of the request login is logged in Step includes:
The listed login accounts of other app that the server returns are received, the app selections logged in for the request The account is simultaneously logged in.
10. login method according to claim 8, wherein, represent have on the mobile terminal if logged on Query Result Other app have been logged in, and according to the conventional login information or shared log-on message, the app logged in the request is logged in The step of include:
The app for receiving the server listed login accounts of other described app sent and being logged in for the request gives birth to Into operational credentials;
The listed login account is selected, and is inputted according to the operational credentials, to be logged in.
11. login method according to claim 10, wherein, the app that the operational credentials log in only for the request Once login it is effective.
12. login method according to claim 11, in addition to:
Receive when it is described request log in app Successful logins when server return logging on authentication token, and in memory with The EIC equipment identification code deviceID, the app identification codes appID, the login account are stored in association.
13. the login method according to any one of claim 8 to 12, wherein, the app identification codes appID is in institute When stating the app on mobile terminal and running first, the EIC equipment identification code deviceID's and the app based on the mobile terminal The generation of app titles.
14. a kind of server, including:
Landing request information receiving module, for receiving the landing request information of mobile terminal transmission, the landing request information bag Include the EIC equipment identification code deviceID of the mobile terminal and the app of request login app identification codes appID;
Enquiry module is logged in, for the EIC equipment identification code deviceID and app included based on the landing request information received Identification code appID, log database is inquired about to confirm whether there are other app to log on the mobile terminal;
Login process module, for returning to conventional login letter when logging in Query Result instruction and being in logging status without other app Breath, shared log-on message is returned to when logging in Query Result instruction and there are other app to be in logging status, so that the request logs in App logged in.
15. server according to claim 14, wherein, the server also includes:Log database, for by described in EIC equipment identification code deviceID, app identification codes appID, login account and the logging status are stored in association.
16. server according to claim 15, wherein, represent there is it on the mobile terminal if logged on Query Result His app has been logged in, and the login process module is used to return to the listed login accounts of other described app to the mobile terminal Number, so that the app that the request logs in selects the account and is logged in.
17. server according to claim 15, wherein, represent there is it on the mobile terminal if logged on Query Result His app has been logged in, and the login process module is used for the operational credentials for generating the app logged in for the request;
And the login process module be additionally operable to the mobile terminal return the listed login accounts of other app and The app logged in for the request operational credentials, so that the app that the request logs in selects the listed login account And inputted according to the operational credentials, to be logged in.
18. server according to claim 17, wherein,
The once login for the app that the operational credentials log in only for the request is effective.
19. server according to claim 18, in addition to:
Logging on authentication generation module, for when it is described request log in app Successful logins when, generate logging on authentication token, and with The EIC equipment identification code deviceID, the app identification codes appID, the login account are stored in the login in association In database, while it is sent to the mobile terminal.
20. the server according to any one of claim 14 to 19, wherein, the server also includes app identification codes When appID is that app on the mobile terminal is run first, the EIC equipment identification code that is sent based on the mobile terminal What deviceID and app app titles generated.
21. a kind of mobile terminal, including:
Landing request information sending module, include movement for sending landing request information to server, landing request information The app identification codes appID for the app that the EIC equipment identification code deviceID of terminal and request log in;
Log-on message receiving module, for receiving conventional login information or the shared log-on message that the server returns, wherein, The conventional login information or shared log-on message are the EIC equipment identification codes included by the server based on landing request information DeviceID and app identification code appID, log database is inquired about to confirm whether there are other app to log on the mobile terminal, And generated according to login Query Result;Wherein, when login Query Result instruction is in logging status without other app, generation Be conventional login information, when logging in Query Result instruction and having other app be in logging status, generation is that shared log in is believed Breath;
App login modules, for according to the conventional login information or shared log-on message, the app logged in the request to enter Row logs in.
22. mobile terminal according to claim 21, wherein, represent have on the mobile terminal if logged on Query Result Other app have been logged in, and the app login modules are used to receive the listed logins of other app that the server returns Account, so that the app that the request logs in selects the account and is logged in.
23. mobile terminal according to claim 21, wherein, represent have on the mobile terminal if logged on Query Result Other app have been logged in, and the app login modules are used to receive the listed logins of other app that the server is sent The operational credentials that account and the app logged in for the request are generated, the listed login account, and according to the operation Voucher inputted, to be logged in.
24. mobile terminal according to claim 23, wherein,
The once login for the app that the operational credentials log in only for the request is effective.
25. mobile terminal according to claim 24, in addition to:
Logging on authentication receiving module, for receive when it is described request log in app Successful logins when server return login with Demonstrate,prove token;
Memory, for by logging on authentication token and the EIC equipment identification code deviceID, the app identification codes appID, institute Login account is stated to be stored in association.
26. the mobile terminal according to any one of claim 21 to 25, wherein, the app identification codes appID is in institute When stating the app on mobile terminal and running first, the EIC equipment identification code deviceID's and the app based on the mobile terminal The generation of app titles.
CN201510050671.3A 2015-01-30 2015-01-30 A kind of login method, server and mobile terminal Active CN104601590B (en)

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 CN104601590A (en) 2015-05-06
CN104601590B true 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)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105045801B (en) * 2015-05-20 2019-01-18 天脉聚源(北京)传媒科技有限公司 The display methods of head portrait, apparatus and system when a kind of login
CN105072133B (en) * 2015-08-28 2018-07-10 北京金山安全软件有限公司 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
CN106161003A (en) * 2016-08-21 2016-11-23 乐视控股(北京)有限公司 Application program login method and terminal, system
CN106650351B (en) * 2016-10-31 2018-12-04 维沃移动通信有限公司 A kind of operation method and mobile terminal of application program
CN107645486B (en) * 2016-12-28 2018-08-21 平安科技(深圳)有限公司 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
US11736292B2 (en) 2017-10-23 2023-08-22 Huawei Technologies Co., Ltd. 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
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
CN111259371B (en) * 2020-01-13 2023-08-18 平安科技(深圳)有限公司 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
CN113132362B (en) * 2021-03-31 2022-03-22 青岛中瑞汽车服务有限公司 Trusted authorization method, trusted authorization device, electronic equipment and storage medium
CN113612756B (en) * 2021-07-29 2023-06-27 广州博冠信息科技有限公司 Shared login method and device, computer readable storage medium and electronic equipment

Citations (3)

* Cited by examiner, † Cited by third party
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
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

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8839395B2 (en) * 2011-05-13 2014-09-16 Cch Incorporated Single sign-on between applications

Patent Citations (3)

* Cited by examiner, † Cited by third party
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
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

Also Published As

Publication number Publication date
CN104601590A (en) 2015-05-06

Similar Documents

Publication Publication Date Title
CN104601590B (en) A kind of login method, server and mobile terminal
CN108881232B (en) Sign-on access method, apparatus, storage medium and the processor of operation system
CN108768970B (en) Binding method of intelligent equipment, identity authentication platform and storage medium
CN112738805B (en) Device control method and apparatus, storage medium, and electronic device
CN107332808B (en) Cloud desktop authentication method, server and terminal
US11539690B2 (en) Authentication system, authentication method, and application providing method
CN109309683A (en) The method and system of client identity verifying based on token
CN105554098B (en) A kind of equipment configuration method, server and system
CN112559993B (en) Identity authentication method, device and system and electronic equipment
CN103609090A (en) Method and device for identity login
CN108880822A (en) A kind of identity identifying method, device, system and a kind of intelligent wireless device
CN108462710A (en) Authentication authority method, device, certificate server and machine readable storage medium
US11177963B2 (en) Method for authenticating a user based on an image relation rule and corresponding first user device, server and system
CN110535648A (en) Electronic certificate is generated and verified and key controlling method, device, system and medium
CN113538739B (en) Pairing method of intelligent lock, electronic device and storage medium
CN105959942A (en) Identification authentication system and identification authentication method based on wireless access
CN105992204A (en) Access authentication method of applications of mobile intelligent terminal and device
CN109831435A (en) A kind of database operation method, system and proxy server and storage medium
CN106161475A (en) The implementation method of subscription authentication and device
CN106453349A (en) An account number login method and apparatus
CN114189863A (en) Binding method and device of intelligent door lock, storage medium and electronic device
CN108140079A (en) Device authentication system
US20130305334A1 (en) Single sign-on for disparate servers
CN114362931A (en) Internet of things equipment registration and security authentication connection and instruction interaction method
CN109948330A (en) Implementation method, device, equipment and the storage medium of application management service

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