WO2015196817A1 - 账号登录方法、装置及系统 - Google Patents
账号登录方法、装置及系统 Download PDFInfo
- Publication number
- WO2015196817A1 WO2015196817A1 PCT/CN2015/072924 CN2015072924W WO2015196817A1 WO 2015196817 A1 WO2015196817 A1 WO 2015196817A1 CN 2015072924 W CN2015072924 W CN 2015072924W WO 2015196817 A1 WO2015196817 A1 WO 2015196817A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- login
- account
- unified communication
- communication client
- string
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
Definitions
- the present invention relates to the field of communications, and in particular, to an account login method, apparatus, and system.
- Unified communications platform also known as unified communications system.
- the core content is: let people freely communicate data, images and sounds through any device, any network, anytime, anywhere.
- the unified communications system effectively integrates various communication devices, media and applications, and makes communication more convenient, more organized, planned, and scalable. In other words, it can use a variety of terminals, integrating instant messaging, SMS, email, voice, video, data and other media, integrated calls, instant messaging, video conferencing and other applications, thus giving people the freedom of choice. And efficiency gains. It is different from the interconnection at the network level, but the integration and collaboration of the people-oriented application level. It is a higher level concept, a new generation of communication and IT industry.
- the unified communication service generally provides an account for each user.
- the user logs in to the unified communication system through the account on each device, and the unified communication system is uniquely distinguished by the account for each login of the user, that is, if the user Use account 1 to log in to the unified communication system on device A. If you use account 1 to log in to the unified address book system on device B, the unified communication server will consider that user account 1 is logged in, and the previously logged in user will be logged in.
- the user switches back to device A if you want to use the unified communication service function again, you must use account 1 to log in again. If the user frequently switches between multiple devices, it will be very complicated, and you must log in again after each switch.
- the embodiment of the present invention provides a login processing method and device, and a unified communication server, to at least solve the problem in the related art, when a user needs to log in to the unified communication client by using the same login account on multiple terminals of different system types. Need to switch frequently, and you need to log in again every time you switch.
- an account login method including: receiving a login request initiated by a first unified communication client, where the login request carries an account and a device login verification string, and different system types The device login verification string of the account acquired by the device is different; determining whether there is another unified communication client using the device login verification string has logged into the account; if the determination result is no, the The unified communication client returns a response to successfully log in to the account.
- Determining whether there is another unified communication client using the device to log in the verification string and having logged in to the account further includes: if the determination result is yes, signing out the account that is logged in by the other unified communication client, and The first unified communication client returns a response to successfully log in to the account.
- the method further includes: verifying the device login check string.
- the checking of the device login check string includes: determining whether the device login check string is consistent with a device login check string corresponding to the first system type saved in the server, where the first system type is the The system type of the terminal where the first unified communication client is located; if yes, the verification is passed; otherwise, the login request is rejected.
- the method further includes: receiving a login query request sent by the first unified communications client, where the login query request carries a setting to describe the first unified a description identifier of a system type of the terminal where the communication client is located; and assigning the device login verification string to the first unified communication client according to the description identifier.
- the assigning a device login check string to the first unified communication client according to the description identifier includes: determining, according to the description identifier, whether the device login check string corresponding to the system type already exists; If not, generating the device login check string, and returning the generated device login check string to the first unified communication client; and/or, if the determination result is yes, Returning the device login check string corresponding to the system type to the first unified communication client.
- Returning the device registration check string corresponding to the system type to the first unified communication client includes: determining whether the device login check string is still valid; and when the determining result is that the device is logged in Test Returning the device login check string to the first unified communication client when the string is still valid; and/or regenerating the device when the judgment result is that the device login check string has expired The device logs the verification string, and returns the regenerated device login check string to the first unified communication client.
- an account login method including: a first unified communication client acquiring a device login check string, wherein the device login check string of an account acquired by a device of a different system type Differently, the device login verification string is set to be determined by the server to determine whether there is another unified communication client that has logged into the account using the device login verification string, and if the determination result is no, the unified communication client is The terminal returns a response to successfully log in to the account; the first unified communication client initiates a login request to the server, where the login request carries the account and the device login check string.
- an account login device located in a server, and includes: a receiving module, configured to receive a login request initiated by a first unified communication client, where the login The request carries an account and a device login check string, and the device login check string of the account obtained by the device of different system types is different; the determining module is configured to determine whether another unified communication client uses the device to log in to the school. The verification string has been logged into the account; the processing module is configured to return a response to the unified communication client to log in to the unified communication client if the determination result is negative.
- an account login device is provided.
- the account login device is located in the first unified communication client, and includes: an obtaining module configured to acquire a device login check string, wherein different system types The device login verification string of the account acquired by the device is different, and the device login verification string is set to determine whether the other unified communication client uses the device login verification string to log in to the account, and is determined. If the result is no, the response to the successful login of the account is returned to the unified communication client; and the sending module is configured to initiate, by the first unified communication client, a login request to the server, where the login request is Carrying the account and the device login check string.
- an account login system including the account login device located in the server, and the account login device located in the first unified communication client.
- the login request initiated by the first unified communication client is received, where the login request carries the account and the device login verification string, and the device login of the account acquired by the device of different system types is obtained.
- the verification string is different; determining whether there is another unified communication client using the device to log in the verification string has logged into the account; if the determination result is no, returning the login to the unified communication client is successful.
- the response method solves the problem that the single account that exists in the related technology can only log in to the unified communication server on one terminal.
- the unified communication server can only judge users based on user accounts. Whether the problem of login, and thus the same account can log in to the unified communication server on multiple devices at the same time, so that when switching between devices, you do not need to re-login frequently, you can use unified on each logged-in device.
- the communication service function provides convenience for users to use the unified service.
- FIG. 1 is a flowchart 1 of an account login method according to an embodiment of the present invention.
- FIG. 2 is a second flowchart of an account login method according to an embodiment of the present invention.
- FIG. 3 is a structural block diagram 1 of an account login device according to an embodiment of the present invention.
- FIG. 4 is a structural block diagram 2 of an account login device according to an embodiment of the present invention.
- FIG. 5 is a structural block diagram of an account login system according to an embodiment of the present invention.
- FIG. 6 is a network diagram of a device for simultaneously logging in to a unified communication server by a single account and multiple devices according to a preferred embodiment of the present invention
- FIG. 7 is a flow chart of interaction of a single account multi-device simultaneously logging into a unified communication server according to a preferred embodiment of the present invention
- FIG. 8 is a flow chart of a unified communication server querying a client for a login request in accordance with a preferred embodiment of the present invention
- FIG. 9 is a flow diagram of a process for a unified communication server to officially log in to a client in accordance with a preferred embodiment of the present invention.
- FIG. 1 is a flowchart 1 of an account login method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:
- Step S102 Receive a login request initiated by the first unified communication client, where the login request carries an account and a device login check string, and the device login check string of the account acquired by the device of different system types is different;
- Step S104 determining whether there is another unified communication client that has logged in to the account by using the device login verification string
- step S106 if the determination result is no, the response to the successful registration of the account is returned to the unified communication client.
- the login request initiated by the first unified communication client is received, where the login request carries the account and the device login check string, and the device login check string of the account acquired by the device of different system types is different;
- the other unified communication client uses the above device login check string to log in to the above account; if the judgment result is negative, the method of returning the successful login response to the above account is returned to the unified communication client, because the device of different system types is obtained.
- the device login check string of the same account is different, and when the device login check string carried by each device is different, all of them can be successfully logged in, and the simultaneous operation can be simultaneously performed on terminals of different system types.
- the account registered by the other unified communication client may be signed out, and a response to successfully log in to the account may be returned to the first unified communication client.
- This method can ensure that only one device of the same system type can successfully log in to the account and conform to the user's operating habits.
- the received device login check string can also be checked first. This can avoid illegal user intrusion and maintain the legitimate rights and interests of users of unified communication clients.
- the device login check string is verified by the method of: determining whether the device login check string is consistent with a device login check string corresponding to the first system type saved in the server, where the first system type is The system type of the terminal where the first unified communication client is located; if yes, the verification is passed; otherwise, the login request is rejected.
- the above method provides a secure and reliable login environment to better protect the interests of users.
- the first unified communications client may also apply for a device login check string to the unified communications server.
- the server may And receiving, by the first unified communication client, a login query request, where the login query request carries a description identifier that is set to describe a system type of the terminal where the first unified communication client is located;
- the communication client allocates a device login check string.
- the description identifier of the system type can be unique for the same type of device, such as an Android phone, the description identifier of the system type can be unique; and the description identifiers of different devices can be kept different, such as Android phones and Apple phones.
- the description identifier can be different.
- the device registration check string when the device registration check string is allocated, the device registration check string can be encrypted, and the security is improved.
- the first unified communication client can also obtain the device login verification string by other methods.
- the device login verification string can also be automatically generated by the first unified communication client during the login process, that is, the first unified communication.
- the client generates the device login check string according to the unified preset rule according to the system type of the terminal where the client is located.
- the device login check string is assigned to the first unified communication client according to the description identifier, if the device login check string of the system type already exists, the device may be directly sent to the client, otherwise it may be generated and then sent.
- the method is as follows: determining, according to the description identifier, whether the device login check string corresponding to the system type already exists; if the determination result is no, generating a device login check string, and returning the generated device login check string to And the first unified communication client; and/or, when the determination result is yes, returning the device login verification string corresponding to the system type to the first unified communication client.
- an expiration date may be set for the existing device login check string. For example, when the device login check string corresponding to the system type is returned to the first unified communication client, it may be determined whether the device login check string is still in the Validity period; when the judgment result is that the device login check string is still valid, the device login check string is returned to the first unified communication client; and/or, when the judgment result is that the device login check string has expired, Regenerate the device login check string and return the regenerated device login check string to the first unified communication client. It can be seen from the above preferred embodiment that when the expiration date is exceeded, the device login check string needs to be regenerated. In addition, when the device login check string is returned to the unified communication client, the returned device login check string can also be Perform encryption processing. It can be more secure and controllable by setting the expiration date and performing encryption processing.
- FIG. 2 is a flowchart 2 of an account login method according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
- the first unified communication client obtains a device login check string, where the device login check string of the account acquired by the device of different system types is different, and the device login check string is set to determine whether there are other unified communication clients.
- the device uses the device to log in to the verification string and has logged in to the account, and if the determination result is negative, returns a response to the unified communication client to log in to the unified account;
- Step S204 The first unified communication client initiates a login request to the server, where the login request carries the account and the device login check string.
- the device uses the first unified communication client to obtain a device login check string.
- the device login check string of the account acquired by the device of different system types is different, and the device login check string is set to determine whether there is another unified device.
- the communication client uses the device to log in the verification string and has logged in to the account, and if the judgment result is no, returns a response to the unified communication client to log in to the unified account; the first unified communication client initiates a login request to the server.
- the device that carries the above-mentioned account and the device login check string in the login request, because the device login check string of the same account obtained by the device of different system types is different, and the device carried when each device logs in If the login checksum is different, the login can be successfully performed.
- the same account can be simultaneously logged in the terminal of different system types.
- the single account that exists in the related technology can only be logged in on one terminal.
- Communication server when needed on multiple different system types of terminals When a login account is used to log in to the unified communication client, you need to log in frequently.
- the unified communication server can only determine whether the user is logged in according to the user account. In this way, the same account can log in to the unified communication on multiple devices at the same time.
- the server so that when switching between devices, you do not need to log in again frequently, you can use the unified communication service function on each logged-in device, which provides convenience for users to use unified services.
- an account login device is also provided in the embodiment, and the device is configured to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
- the term "module” may implement a combination of software and/or hardware of a predetermined function.
- the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
- FIG. 3 is a structural block diagram of an account login device according to an embodiment of the present invention.
- the device is located in a server. As shown in FIG. 3, the device includes a receiving module 32, a determining module 34, and a processing module 36. Description.
- the receiving module 32 is configured to receive a login request initiated by the first unified communications client, where the login request carries the account and the device login check string, and the device login check string of the account acquired by the device of different system types is different;
- the module 34 is connected to the receiving module 32, and is configured to determine whether there is another unified communication client that has logged in to the account by using the device login verification string; the processing module 36 is connected to the determining module 34. When the determination result of the determination module 34 is negative, the response to the successful registration of the account is returned to the unified communication client.
- FIG. 4 is a structural block diagram 2 of an account login device according to an embodiment of the present invention.
- the device is located in a first unified communication client. As shown in FIG. 4, the device includes an obtaining module 42 and a sending module 44. Be explained.
- the obtaining module 42 is configured to obtain a device login check string, where the device login check string of the account acquired by the device of different system types is different, and the device login check string is set to determine whether the other unified communication client uses the device.
- the login verification string has been logged in to the account, and if the determination result is no, the response to the successful registration of the account is returned to the unified communication client; the sending module 44 is connected to the obtaining module 42 and configured as the first unified
- the communication client initiates a login request to the server, where the login request carries the account and the device login check string.
- FIG. 5 is a structural block diagram of an account login system according to an embodiment of the present invention.
- the account login system 50 includes the above-mentioned account login device 52 located in the server, and further includes the above-mentioned first unified communication client.
- the account registration device 54 in the middle.
- the following preferred embodiment provides a method and apparatus for simultaneously logging in to a unified communication server by a single account and multiple devices.
- a method or a device for simultaneously logging in to a unified communication server by using a single account and multiple devices which allows a user to simultaneously log in to the unified communication server using the same account on multiple devices, and simultaneously use
- the various functions of the unified communication service do not need to be re-registered when switching between devices.
- the core is: in the preferred embodiment, a device for simultaneously logging in to the unified communication server by a single account and multiple devices is composed of the following parts, and the terminal device (including a computer, a tablet, a mobile phone, etc.) with the unified communication client software is installed, and the user uses the
- the unified communication client software installed on the device logs in to the unified communication server and uses the functions of unified communication; the unified communication server realizes various business logics of unified communication, and provides various unified communication business function services to users.
- the terminal device and the unified communication server are connected through the network, and only network intercommunication is required, and there is no other special connection requirement.
- the method for simultaneously logging in to the unified communication server by a single account multi-device is as follows (mainly describes the core ideas, algorithms and operation steps of the implementation):
- the core algorithm is:
- the unified communication client on the device type A takes the account, the password, and the description identifier of the device type to the unified server client to initiate a query login request.
- the step may further comprise the following steps:
- the user inputs a unified communication account and password on the unified communication client on device type A;
- the unified communication client obtains the description identifier of the device type A according to the installed device (the device description identifier is unique for the same type of device, such as the Android device, the device description identifier is unique; and different devices at the same time The description identifier remains different, such as on Android phones and Apple phones, the device description identifier is different);
- the unified communication client initiates a query login request to the unified communication server with the account, password and device description identifier entered by the user.
- the unified communication server verifies the query login request of the client.
- the step may further comprise the following steps:
- the unified communication server verifies the account and password of the login request of the client. If the account does not exist, the direct return user does not exist; if the password is incorrect, the return password is incorrect;
- the unified communication server obtains the device description identifier in the client login request, and determines whether the unified communication server has previously assigned the device login check string to the type of device of the account:
- the unified communication server automatically generates the device login check string of the account on the device type and saves it in the server, and returns the device login check string to the client (the returned device login check string is performed). Encryption processing);
- the unified communication server determines whether the device login check string is within the validity period:
- the device login check string of the account on the device type is regenerated and updated to the server, and the device login check string is returned to the client (the returned device login check string is encrypted) deal with);
- the device login check string is directly returned to the client (the returned device login check string is encrypted).
- the unified communication client obtains the device login verification string in the response of the unified communication server, and takes the account, password, and device login verification string to the server to initiate an official login request.
- the step may further comprise the following steps:
- the unified communication client decrypts the query login response from the unified communication server to obtain the device login check string of the account on the device type;
- the unified communication client carries the user account, password, device login check string (for encryption processing) to the unified communication server to initiate an official login request;
- the unified communication server verifies the official login request of the client.
- the step may further comprise the following steps:
- the unified communication server verifies the account and password of the login request of the client. If the account does not exist, the direct return user does not exist; if the password is incorrect, the return password is incorrect;
- the unified communication server obtains the device login check string in the client login request, and determines whether the login check string is consistent with the device login check string allocated by the service side. If not, the login failure is returned; if they are consistent, the user is judged. If the account is used, the device type A has been logged in. If you have logged in, the previous login of the device type A is checked out.
- the unified communication server saves the login data area of the account on the device type A to the user account data area of the server side, and returns a login success response to the client;
- the user account is successfully logged in to the unified communication server on device type A.
- the subsequent user uses the user account to log in on the new device type such as device type B and device type C.
- the process and steps are the same as above.
- the effect that a single account can log in to the unified communication server and use unified communication functions on multiple device types is achieved, thereby improving the user experience of using unified communication, and bringing great convenience to the user. .
- a device login verification string is extended during the login process from the unified communication client to the unified communication server.
- the device login verification string of each user account remains different, and the unified communication server is combined with the user account.
- Log in to the device to check whether the user logs in to the device.
- the same user account can log in at the same time and does not sign each other.
- the same account is used to log in. You can sign each other and retain some of the user's existing experience.
- the device login check string is generated by the unified communication server, but the login check string can also be automatically generated by the client during the login process, and the single account can be simultaneously logged in on multiple devices. That is, the alternative can achieve the same effect.
- the alternative can achieve the same function, and in the formal solution, the device login check string can be uniformly generated and allocated by the server side and has a certain validity period, which is more secure and controllable.
- the following steps can also be used for processing.
- the steps are as follows:
- the unified communication client on device type A brings the user input account, password, and device check string to the unified server client to initiate an official login request.
- This step can further include the following steps:
- the user inputs a unified communication account and password on the unified communication client on device type A;
- the unified communication client automatically generates a login device verification string according to the installed device type A.
- the login device verification string is unique for the same account and the same type of device, such as an Android mobile phone, and the user account 1 is on the device.
- the login identifier strings are the same; at the same time, the same user account has different login device verification strings on different device types, such as Android phone and Apple mobile phone, user account 1 login device verification on the two types of device types. String is different);
- the unified communication client initiates a login request to the unified communication server with the account, password, and login device verification string entered by the user.
- the unified communication server verifies the login request of the client.
- This step can further include the following steps:
- the unified communication server verifies the account and password of the login request of the client. If the account does not exist, the direct return user does not exist; if the password is incorrect, the return password is incorrect;
- the unified communication server obtains the device login check string in the client login request, and determines whether the user has logged in to the device type A. If the user has logged in, the account is previously logged off at the device type A.
- the unified communication server saves the login data area of the account on the device type A to the user account data area of the server side, and returns a login success response to the client;
- the user account is successfully logged in to the unified communication server on device type A.
- the subsequent user uses the user account to log in on the new device type such as device type B and device type C.
- the process and steps are the same as above.
- FIG. 6 is a network diagram of a device for simultaneously logging in to a unified communication server by a single account and multiple devices according to a preferred embodiment of the present invention, as shown in FIG. 6.
- the hardware part consists of a unified communication client, a terminal device installed by the client, a unified communication server, and a network connecting the terminal device and the unified communication server.
- the terminal device 601, the terminal device 602, the terminal device 603, and the terminal device 604 are set, and the unified communication client software is installed on the terminal device;
- the device is unified with the communication server host 606, and the unified communication server software is deployed on the host;
- the processing steps for the unified communication client to log in to the unified communication server in the software section are as follows: Take the unified communication account 1 to log in to the unified communication server on device type A and device type B as an example:
- FIG. 7 is an interaction flowchart of a single account multi-device simultaneously logging in to a unified communication server according to a preferred embodiment of the present invention, wherein the login process of device type A and device type B is consistent. As shown in FIG. 7, the interaction process includes the following steps:
- Step S702 the unified communication client software initiates a query login request to the unified communication server, and the step can be further divided into:
- the unified communication client software obtains the description identifier of the device type A according to the installed device (the device description identifier is unique for the same type of device, such as the Android device, the device description identifier is unique; At the same time, the description identifiers of different devices remain different, such as Android phones and Apple phones, the device description identifier is different);
- the unified communication client software initiates a query login request to the unified communication server, and the request includes a device type description identifier with the user account 1, the password, and the device type A.
- Step S704 the unified communication server receives the query login request of the client software, checks the request, and returns a device login check string.
- FIG. 8 is a unified communication server inquiring the client to query the login request according to a preferred embodiment of the present invention. The flowchart, as shown in FIG. 8, further includes the following steps in step S704:
- Step S7041 The unified communication server performs account verification on the login request of the client.
- Step S7042 if the account does not exist, the direct return user does not exist;
- Step S7043 In the case that the account exists, determine whether the password is correct
- Step S7044 if the password is wrong, the password is returned incorrectly;
- Step S7045 in the case that the password is correct, the unified communication server acquires the device description identifier in the client login request;
- Step S7046 determining whether the unified login server has previously assigned the device login check string to the user account 1 on the device type A;
- Step S7047 if not allocated, the unified communication server automatically generates the device login verification string of the user account 1 on the device type A and saves it in the server, and returns the device login check string to the client (returned device login) Check string for encryption processing);
- Step S7048 If the user account 1 has been assigned a device login check string on the device type A, the unified communication server determines whether the device login check string is within the validity period;
- step S7049 if the expiration date has expired, the device login verification string of the user account 1 on the device type A is regenerated and updated to the server, and the device login verification string is returned to the client (the returned device login verification string) Perform encryption processing);
- step S70410 if it is still valid, the device login check string is directly returned to the client (the returned device login check string is encrypted).
- the step S702 and the step S704 are the process of the unified communication server querying the login request by the client.
- FIG. 9 is a flowchart of a process for a unified communication server to officially log in to a client according to a preferred embodiment of the present invention, which will be described below with reference to FIG. 9.
- Step S706 The unified communication client obtains the device login verification string in the response of the unified communication server, and takes the user account 1, the password, and the device login verification string to the server to initiate an official login request.
- This step can further include the following steps:
- the unified communication client software decrypts the device login verification string of the user account 1 on the device type A from the query login response of the unified communication server;
- the unified communication client carries the user account 1, password, device login check string (for encryption processing) to the unified communication server to initiate an official login request.
- Step S708 the unified communication server verifies the official login request of the client, saves the login data area, and returns a login success response.
- This step may further include the following steps:
- Step S7081 The unified communication server performs account verification on the login request of the client.
- Step S7082 if the account does not exist, the direct return user does not exist;
- Step S7083 if the account exists, determine whether the password is correct
- Step S7084 if the password is wrong, the password is returned incorrectly;
- Step S7085 in the case that the password is correct, the unified communication server acquires the device login check string in the client login request;
- Step S7086 determining whether the login check string is consistent with the device login check string allocated by the previous service side for the user account 1 on the device type A;
- Step S7087 if the inconsistency, returning the login failure
- step S7088 if they are consistent, it is determined whether the user has used the user account 1 to log in on the device type A. If the user has logged in, the login of the previous user account 1 in the device type A is signed off; the unified communication server will be the user account 1 The login data area on device type A is saved in the user account 1 data area on the server side, and the login success response is returned to the client.
- user account 1 is successfully logged in on device type A.
- the user account 1 finishes logging in to the unified communication server at the same time on different device types.
- the foregoing embodiments and preferred embodiments overcome the shortcomings of the related art that a single account can only log in to the unified communication server on one device at the same time.
- the unified communication server existing in the prior art only determines whether the user logs in according to the user account.
- the problem to be solved by the preferred embodiment is that when the user uses the unified communication service between multiple devices, the same account can be used to log in to the unified communication server at the same time on multiple devices, and the switching between devices does not need to be repeated frequently. By logging in again, you can use the unified communication service function on each logged-in device, which greatly facilitates the user experience and provides convenience for users to use unified services.
- modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the account login method, device, and system provided by the embodiments of the present invention have the following beneficial effects: the single account that exists in the related art can only log in to the unified communication server on one terminal, when needed When you use the same login account to log in to the unified communication client on a terminal of different system types, you need to log in frequently again.
- the unified communication server can only determine whether the user is logged in based on the user account, and thus the same account can be implemented.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
本发明提供了账号登录方法、装置及系统，该方法包括：采用接收第一统一通讯客户端发起的登录请求，其中，该登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的账号的设备登录校验串不同；判断是否存在其他统一通讯客户端使用上述设备登录校验串已经登录上述账号；在判断结果为否的情况下，向上述统一通讯客户端返回登录上述账号成功的响应。解决了多个不同系统类型的终端上使用同一个登录账号登录统一通讯客户端时，需要频繁地重新登录的问题，进而实现了同个帐号可以在多设备上同时登录到统一通讯服务器，给用户使用统一业务提供了方便。
Description
本发明涉及通信领域，具体而言，涉及账号登录方法、装置及系统。
随着互联网的发展，融合各种通讯手段的统一通讯业务(社交，即时消息，状态呈现，群组，聊天室)发展迅速。统一通讯平台,也叫统一通讯系统。其核心内容是：让人们无论任何时间、任何地点，都可以通过任何设备、任何网络，获得数据、图像和声音的自由通信。统一通信系统有效地整合了各种通信设备、媒体和应用，并且使通信更加方便，更加具有组织性、计划性、可扩展性。也就是说，它能够使用多样化的终端，融合即时消息、手机短信、邮件、语音、视频、数据等多种媒体，综合呼叫、即时通信、视频会议等应用，从而为人们带来选择的自由和效率的提升。它区别于网络层面的互联互通，而是以人为本的应用层面的融合与协同，是更高一个层次的理念，新一代通信与IT产业。
随着现在人们使用的各种上网设备的增加，在各种场景下，用户随时随地可接入到统一通讯系统，使用统一通讯的业务功能，各种移动设备可以随时随地方便的上网方式，正在改变人们的生活习惯。统一通讯业务一般针对每个用户都提供一个帐号，用户在各个设备上都通过此帐号登录到统一通讯系统，而统一通讯系统针对用户的每次登录，都是通过帐号唯一进行区分，即如果用户使用帐号1在设备A上登录了统一通讯系统，如果此时再在设备B上使用帐号1登录统一通讯录系统，此时统一通讯服务器会认为用户帐号1已经登录，从而会将之前登录的用户进行签退掉，当用户再切换回设备A时，如果要想再使用统一通讯业务功能，就必须要再使用帐号1重新进行登录。如果用户在多设备间频繁地切换使用的话，会非常繁锁，每切换一次都要重新登录下。
因此，在相关技术中，存在着当用户需要在多个不同系统类型的终端上使用同一个登录账号登录统一通讯客户端时，需要频繁切换使用，每次切换都需要重新登录的问题。
发明内容
本发明实施例提供了一种登录处理方法、装置及统一通讯服务器，以至少解决相关技术中存在的当用户需要在多个不同系统类型的终端上使用同一个登录账号登录统一通讯客户端时，需要频繁切换使用，每次切换都需要重新登录的问题。
根据本发明的一实施例，提供了一种账号登录方法，包括：接收第一统一通讯客户端发起的登录请求，其中，所述登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的所述账号的所述设备登录校验串不同；判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号；在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应。
判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号还包括：在判断结果为是的情况下，签退所述其他统一通讯客户端登录的所述账号，并向所述第一统一通讯客户端返回登录所述账号成功的响应。
在判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号之前，还包括：对所述设备登录校验串进行校验。
对所述设备登录校验串进行校验包括：判断所述设备登录校验串是否与服务器中保存的第一系统类型对应的设备登录校验串一致，其中所述第一系统类型为所述第一统一通讯客户端所在终端的系统类型；如果是，则校验通过；否则，拒绝所述登录请求。
在接收第一统一通讯客户端发起的登录请求之前，还包括：接收所述第一统一通讯客户端发送的登录查询请求，其中，所述登录查询请求中携带有设置为描述所述第一统一通讯客户端所在终端的系统类型的描述标识符；根据所述描述标识符为所述第一统一通讯客户端分配所述设备登录校验串。
根据所述描述标识符为所述第一统一通讯客户端分配设备登录校验串包括：根据所述描述标识符判断是否已经存在所述系统类型对应的所述设备登录校验串；在判断结果为否的情况下，生成所述设备登录校验串，并将生成的所述设备登录校验串返回给所述第一统一通讯客户端；和/或，在判断结果为是的情况下，将所述系统类型对应的所述设备登录校验串返回给所述第一统一通讯客户端。
将所述系统类型对应的所述设备登录校验串返回给所述第一统一通讯客户端包括：判断所述设备登录校验串是否仍在有效期；当所述判断结果为所述设备登录校验
串仍在有效期时，将所述设备登录校验串返回给所述第一统一通讯客户端；和/或，当所述判断结果为所述设备登录校验串已过有效期时，重新生成所述设备登录校验串，并将重新生成的所述设备登录校验串返回给所述第一统一通讯客户端。
根据本发明的另一实施例，提供了一种账号登录方法，包括：第一统一通讯客户端获取设备登录校验串，其中，不同系统类型的设备获取的账号的所述设备登录校验串不同，所述设备登录校验串设置为服务器判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号，并在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应；所述第一统一通讯客户端向所述服务器发起登录请求，其中，所述登录请求中携带所述账号和所述设备登录校验串。
根据本发明的再一实施例，提供了一种账号登录装置，所述账号登录装置位于服务器中，包括：接收模块，设置为接收第一统一通讯客户端发起的登录请求，其中，所述登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的所述账号的所述设备登录校验串不同；判断模块，设置为判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号；处理模块，设置为在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应。
根据本发明的又一实施例，提供了一种账号登录装置，所述账号登录装置位于第一统一通讯客户端中，包括：获取模块，设置为获取设备登录校验串，其中，不同系统类型的设备获取的账号的所述设备登录校验串不同，所述设备登录校验串设置为服务器判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号，并在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应；发送模块，设置为所述第一统一通讯客户端向所述服务器发起登录请求，其中，所述登录请求中携带所述账号和所述设备登录校验串。
根据本发明的另一实施例，提供了一种账号登录系统，包括所述的位于服务器中的账号登录装置，还包括所述的位于第一统一通讯客户端中的账号登录装置。
通过本发明实施例，采用接收第一统一通讯客户端发起的登录请求，其中，所述登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的所述账号的所述设备登录校验串不同；判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号；在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应的方式，解决了相关技术中存在的单帐号只能在一台终端上登录统一通讯服务器，当需要在多个不同系统类型的终端上使用同一个登录账号登录统一通讯客户端时，需要频繁地重新登录，并且的统一通讯服务器只能根据用户帐号来判断用户
是否登录的问题，进而实现了同个帐号可以在多设备上同时登录到统一通讯服务器，从而在设备间切换时，不需要再频繁地重新登录，即可在每个已登录的设备上使用统一通讯业务功能，给用户使用统一业务提供了方便。
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的账号登录方法的流程图一；
图2是根据本发明实施例的账号登录方法的流程图二；
图3是根据本发明实施例的账号登录装置的结构框图一；
图4是根据本发明实施例的账号登录装置的结构框图二；
图5是根据本发明实施例的账号登录系统的结构框图；
图6是根据本发明优选实施例的单帐号多设备同时登录统一通讯服务器的装置的设备组网图；
图7是根据本发明优选实施例的单账号多设备同时登录统一通信服务器的交互流程图；
图8是根据本发明优选实施例的统一通讯服务器对客户端查询登录请求的流程图；
图9是根据本发明优选实施例的统一通讯服务器对客户端正式登录请求的处理流程图。
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种账号登录方法，图1是根据本发明实施例的账号登录方法的流程图一，如图1所示，该流程包括如下步骤：
步骤S102，接收第一统一通讯客户端发起的登录请求，其中，该登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的账号的设备登录校验串不同；
步骤S104，判断是否存在其他统一通讯客户端使用上述设备登录校验串已经登录上述账号；
步骤S106，在判断结果为否的情况下，向上述统一通讯客户端返回登录上述账号成功的响应。
通过上述步骤，采用接收第一统一通讯客户端发起的登录请求，其中，该登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的账号的设备登录校验串不同；判断是否存在其他统一通讯客户端使用上述设备登录校验串已经登录上述账号；在判断结果为否的情况下，向上述统一通讯客户端返回登录上述账号成功的响应的方式，由于不同系统类型的设备获取的同一个账号的设备登录校验串是不同的，而当各个设备登录时携带的设备登录校验串不同时，则其均可以登录成功，实现了可以同时在不同的系统类型的终端上同时登录同一个账号，解决了相关技术中存在的单帐号只能在一台终端上登录统一通讯服务器，当需要在多个不同系统类型的终端上使用同一个登录账号登录统一通讯客户端时，需要频繁地重新登录，并且的统一通讯服务器只能根据用户帐号来判断用户是否登录的问题，进而实现了同个帐号可以在多设备上同时登录到统一通讯服务器，从而在设备间切换时，不需要再频繁地重新登录，即可在每个已登录的设备上使用统一通讯业务功能，给用户使用统一业务提供了方便。
优选地，如果上述步骤S104的判断结果为是，还可以签退上述其他统一通讯客户端登录的上述账号，并向上述第一统一通讯客户端返回登录上述账号成功的响应。这种方式能够保证同种系统类型的设备仅有一个能够登录该账号成功，并且符合用户的操作习惯。
在一个优选实施例中，还可以对收到的设备登录校验串先进行校验。这样可以避免非法用户入侵，维护统一通讯客户端使用者的合法权益。
优选地，可以通过如下方法对上述设备登录校验串进行验证：判断上述设备登录校验串是否与服务器中保存的第一系统类型对应的设备登录校验串一致，其中该第一系统类型为上述第一统一通讯客户端所在终端的系统类型；如果是，则校验通过；否则，拒绝上述登录请求。也就是说，通过对比统一通讯客户端发送的设备登录校验串与统一通讯服务器中预先保存的设备登录校验串是否一致来判断需要接入服务器的统一通讯客户端是否合法，当校验结果为二者一致时，说明验证通过，允许该统一通讯客户端连接到服务器中，如果校验结果不一致，则说明没有权限登录统一通讯服务器，
拒绝客户端的登录请求。此时用户可以重新申请一个新的设备登录校验串。上述方法提供了一种安全可靠的登录环境，可以更好地维护用户的利益。
在另一个优选实施例中，在接收第一统一通讯客户端发起的登录请求之前，第一统一通讯客户端还可以向统一通讯服务器申请一个设备登录校验串，在这种情况下，服务器可以接收第一统一通讯客户端发送的登录查询请求，其中，该登录查询请求中携带有设置为描述第一统一通讯客户端所在终端的系统类型的描述标识符；根据该描述标识符为第一统一通讯客户端分配设备登录校验串。该系统类型的描述标识符针对相同类型的设备可以保持唯一，如安卓手机上，该系统类型的描述标识符可以是唯一的；同时不同设备的描述标识符可以保持不同，如安卓手机和苹果手机上，该描述标识符可以是不同的。并且，在进行设备登录校验串的分配时，可以对该设备登录校验串进行加密处理，提高了安全性。当然，第一统一通讯客户端也可以通过其他的方法获取设备登录校验串，例如，该设备登录校验串也可以由第一统一通信客户端在登录过程中自动生成，即第一统一通讯客户端根据其所在终端的系统类型，按照统一预设的规则生成该设备登录校验串。
根据描述标识符为第一统一通讯客户端分配设备登录校验串时，如果已经存在该系统类型的设备登录校验串，则可以直接发送给该客户端，否则可以生成后再发送，具体可以通过如下方法：根据描述标识符判断是否已经存在上述系统类型对应的设备登录校验串；在判断结果为否的情况下，生成设备登录校验串，并将生成的设备登录校验串返回给第一统一通讯客户端；和/或，在判断结果为是的情况下，将系统类型对应的设备登录校验串返回给第一统一通讯客户端。
并且，还可以对已存在的设备登录校验串设置一个有效期，例如，在将系统类型对应的设备登录校验串返回给第一统一通讯客户端时，可以判断设备登录校验串是否仍在有效期；当判断结果为设备登录校验串仍在有效期时，将设备登录校验串返回给上述第一统一通讯客户端；和/或，当判断结果为设备登录校验串已过有效期时，重新生成设备登录校验串，并将重新生成的设备登录校验串返回给第一统一通讯客户端。由上述优选实施例可知，当超过设置的有效期时，需要重新生成设备登录校验串，此外，在将设备登录校验串返回给统一通讯客户端时，还可以对返回的设备登录校验串进行加密处理。通过设置有效期和进行加密处理可以更加安全和可控。
在本实施例中还提供了一种账号登录方法，图2是根据本发明实施例的账号登录方法的流程图二，如图2所示，该流程包括如下步骤：
步骤S202，第一统一通讯客户端获取设备登录校验串，其中，不同系统类型的设备获取的账号的设备登录校验串不同，该设备登录校验串设置为服务器判断是否存在其他统一通讯客户端使用该设备登录校验串已经登录该账号，并在判断结果为否的情况下，向上述统一通讯客户端返回登录上述账号成功的响应；
步骤S204，第一统一通讯客户端向服务器发起登录请求，其中，该登录请求中携带上述账号和上述设备登录校验串。
通过上述步骤，采用第一统一通讯客户端获取设备登录校验串，其中，不同系统类型的设备获取的账号的设备登录校验串不同，该设备登录校验串设置为服务器判断是否存在其他统一通讯客户端使用该设备登录校验串已经登录该账号，并在判断结果为否的情况下，向上述统一通讯客户端返回登录上述账号成功的响应；第一统一通讯客户端向服务器发起登录请求，其中，该登录请求中携带上述账号和上述设备登录校验串的方式，由于不同系统类型的设备获取的同一个账号的设备登录校验串是不同的，而当各个设备登录时携带的设备登录校验串不同时，则其均可以登录成功，实现了可以同时在不同的系统类型的终端上同时登录同一个账号，解决了相关技术中存在的单帐号只能在一台终端上登录统一通讯服务器，当需要在多个不同系统类型的终端上使用同一个登录账号登录统一通讯客户端时，需要频繁地重新登录，并且的统一通讯服务器只能根据用户帐号来判断用户是否登录的问题，进而实现了同个帐号可以在多设备上同时登录到统一通讯服务器，从而在设备间切换时，不需要再频繁地重新登录，即可在每个已登录的设备上使用统一通讯业务功能，给用户使用统一业务提供了方便。
对应于上述方法，在本实施例中还提供了一种账号登录装置，该装置设置为实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的账号登录装置的结构框图一，该装置位于服务器中，如图3所示，该装置包括接收模块32、判断模块34和处理模块36，下面对该装置进行说明。
接收模块32，设置为接收第一统一通讯客户端发起的登录请求，其中，该登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的账号的设备登录校验串不同；判断模块34，连接至上述接收模块32，设置为判断是否存在其他统一通讯客户端使用上述设备登录校验串已经登录上述账号；处理模块36，连接至上述判断模块34，
设置为在判断模块34的判断结果为否的情况下，向上述统一通讯客户端返回登录上述账号成功的响应。
图4是根据本发明实施例的账号登录装置的结构框图二，该装置位于第一统一通讯客户端中，如图4所示，该装置包括获取模块42和发送模块44，下面对该装置进行说明。
获取模块42，设置为获取设备登录校验串，其中，不同系统类型的设备获取的账号的设备登录校验串不同，设备登录校验串设置为服务器判断是否存在其他统一通讯客户端使用该设备登录校验串已经登录上述账号，并在判断结果为否的情况下，向上述统一通讯客户端返回登录上述账号成功的响应；发送模块44，连接至上述获取模块42，设置为上述第一统一通讯客户端向上述服务器发起登录请求，其中，该登录请求中携带上述账号和上述设备登录校验串。
图5是根据本发明实施例的账号登录系统的结构框图，如图5所示，该账号登录系统50包括上述的位于服务器中的账号登录装置52，还包括上述的位于第一统一通讯客户端中的账号登录装置54。
下面结合优选实施例进行说明，以下优选实施例结合了上述实施例及其优选实施方式。
以下优选实施例提供了一种单账号多设备同时登录统一通讯服务器的方法及装置。
在一个可选的实施例中，提供了一种使用单帐号多设备同时登录统一通讯服务器的方法或装置，可以让用户在多个设备上，使用同一个帐号同时登录到统一通讯服务器，同时使用统一通讯业务的各种功能，后续在设备间切换时，不需要再重新进行登录。
核心是：本优选实施例中一种单帐号多设备同时登录统一通讯服务器的装置由以下几部分组成，安装有统一通讯客户端软件的终端设备(包括电脑、平板、手机等)，用户使用该设备上安装的统一通讯客户端软件，登录到统一通讯服务器，使用统一通讯的各项功能；统一通讯服务器，实现统一通讯的各种业务逻辑，向用户提供各种统一通讯的业务功能服务。终端设备与统一通讯服务器间通过网络连接，只需要网络互通即可，无其它特殊连接要求。
本优选实施例中提供的一种单帐号多设备同时登录统一通讯服务器的方法如下(主要描述实现的核心思想、算法和操作步骤)：
核心算法是：
第一步，设备类型A上的统一通讯客户端带上用户输入的帐号，密码，以及设备类型的描述标识符到统一服务器客户端发起查询登录请求。
优选地，该步骤又可以包括下列步骤：
1用户在设备类型A上的统一通讯客户端输入统一通讯帐号和密码；
2统一通讯客户端根据所安装的设备获取设备类型A的描述标识符(该设备描述标识符针对相同类型的设备保持唯一，如安卓手机上，该设备描述标识符都是唯一的；同时不同设备的描述标识符保持不同，如安卓手机和苹果手机上，该设备描述标识符是不同的)；
3统一通讯客户端带上用户输入的帐号、密码及设备描述标识符向统一通讯服务器发起查询登录请求。
第二步，统一通讯服务器对客户端的查询登录请求进行校验。
优选地，该步骤又可以包括下列步骤：
1统一通讯服务器对客户端的登录请求进行帐号和密码的校验，如果帐号不存在，则直接返回用户不存在；如果密码错误，则返回密码错误；
2统一通讯服务器获取客户端登录请求中的设备描述标识符，判断统一通讯服务器之前是否给该帐号该类型设备分配过设备登录校验串：
2.1如果未分配过，则统一通讯服务器自动生成该帐号在设备类型上的设备登录校验串并保存在服务器中，同时将设备登录校验串返回给客户端(返回的设备登录校验串进行加密处理)；
2.2如果已给该帐号该设备类型分配过设备登录校验串，则统一通讯服务器判断该设备登录校验串是否在有效期内：
2.2.1如果已过有效期，则重新生成该帐号在设备类型上的设备登录校验串并更新到服务器中，同时将设备登录校验串返回给客户端(返回的设备登录校验串进行加密处理)；
2.2.2如果仍在有效内，则直接将设备登录校验串返回给客户端(返回的设备登录校验串进行加密处理)。
第三步，统一通讯客户端获取统一通讯服务器响应中的设备登录校验串，带上帐号、密码、设备登录校验串到服务器发起正式登录请示。
优选地，该步骤又可以包括下列步骤：
1统一通讯客户端从统一通讯服务器的查询登录响应中解密获取到该帐号在该设备类型上设备登录校验串；
2统一通讯客户端带上用户帐号，密码，设备登录校验串(进行加密处理)到统一通讯服务器发起正式登录请求；
第四步，统一通讯服务器对客户端的正式登录请求进行校验。
优选地，该步骤又可以包括下列步骤：
1统一通讯服务器对客户端的登录请求进行帐号和密码的校验，如果帐号不存在，则直接返回用户不存在；如果密码错误，则返回密码错误；
2统一通讯服务器获取客户端登录请求中的设备登录校验串，判断该登录校验串是否之前服务侧分配的设备登录校验串一致，如果不一致，则返回登录失败；如果一致，则判断用户是否使用该帐号在设备类型A已经登录过，如果登录过，则将之前该帐号之前在设备类型A的登录签退掉；
3统一通讯服务器将该帐号在设备类型A上的登录数据区保存到服务器侧的用户帐号数据区中，同时给客户端返回登录成功响应；
至此，用户帐号在设备类型A上登录统一通讯服务器成功，后面用户使用该用户帐号在设备类型B，设备类型C等新设备类型上登录，流程和步骤与上面的一致。
根据上述优选实施例，达到了单帐号在多设备类型上同时可登录统一通讯服务器并使用统一通讯各项功能的效果，提高了用户使用统一通讯的体验，给用户带来了极大的方便性。
本优选实施例通过在统一通讯客户端到统一通讯服务器登录过程中扩展一个设备登录校验串，不同类型的设备上，每个用户帐号的设备登录校验串保持不同，统一通讯服务器结合用户帐号和设备登录校验串，来判断用户是否在该类型设备上登录，不同类型的设备上，同个用户帐号可以同时登录，不会互相签退；同个设备类型上，同个帐号登录，仍然可以互相签退，保留了用户已有的一些体验习惯。
在上述的实施例中，设备登录校验串是由统一通讯服务器生成，但是这个登录校验串也是可以由客户端在登录过程中自动生成，可以实现单帐号在多设备上同时登录的功能，即该替代方案也可实现相同的效果。
相较于上述的正式方案，替代方案也可以达到相同的功能，并且在正式方案中，设备登录校验串可以由服务器侧统一生成并分配且有一定的有效期，更加的安全和可控。
优选地，还可以采用如下步骤进行处理，替代方案中，步骤如下：
第一步，设备类型A上的统一通讯客户端带上用户输入的帐号，密码，以及设备校验串到统一服务器客户端发起正式登录请求。
本步骤又可以包括下列步骤：
1用户在设备类型A上的统一通讯客户端输入统一通讯帐号和密码；
2统一通讯客户端根据所安装的设备类型A自动生成登录设备校验串(该登录设备校验串针对相同帐号和相同类型的设备保持唯一，如安卓手机上，用户帐号1在该设备上的登录标识串都是相同的；同时相同的用户帐号在不同设备类型上的登录设备校验串保持不同，如安卓手机和苹果手机上，用户帐号1在该两类设备类型上的登录设备校验串是不同的)；
3统一通讯客户端带上用户输入的帐号、密码及登录设备校验串向统一通讯服务器发起登录请求。
第二步，统一通讯服务器对客户端的登录请求进行校验。
本步骤又可以包括下列步骤：
1统一通讯服务器对客户端的登录请求进行帐号和密码的校验，如果帐号不存在，则直接返回用户不存在；如果密码错误，则返回密码错误；
2统一通讯服务器获取客户端登录请求中的设备登录校验串，判断用户是否使用该帐号在设备类型A已经登录过，如果登录过，则将该帐号之前在设备类型A的登录签退掉；
3统一通讯服务器将该帐号在设备类型A上的登录数据区保存到服务器侧的用户帐号数据区中，同时给客户端返回登录成功响应；
至此，用户帐号在设备类型A上登录统一通讯服务器成功，后面用户使用该用户帐号在设备类型B，设备类型C等新设备类型上登录，流程和步骤与上面的一致。
下面结合图6对本优选实施例中的技术方案的实施作进一步的详细描述：图6是根据本发明优选实施例的单帐号多设备同时登录统一通讯服务器的装置的设备组网图，如图6所示，硬件部分由统一通讯客户端，客户端所安装的终端设备，统一通讯服务器，以及连接终端设备与统一通讯服务器的网络组成。
设置好终端设备601，终端设备602，终端设备603，终端设备604若干，并在终端设备上安装统一通讯客户端软件；
设备好统一通讯服务器主机606，并在主机上部署好统一通讯服务器软件；
设备好终端设备和统一通讯服务器主机通讯的网络605。
软件部分中统一通讯客户端登录统一通讯服务器的处理步骤如下(以用户使用统一通讯帐号1在设备类型A和设备类型B上登录统一通讯服务器为例)：
图7是根据本发明优选实施例的单账号多设备同时登录统一通信服务器的交互流程图，其中，设备类型A和设备类型B的登录过程一致。如图7所示，该交互过程包括如下步骤：
步骤S702，统一通讯客户端软件向统一通讯服务器发起查询登录请求，本步骤又可分为：
(1)统一通讯客户端软件根据所安装的设备获取设备类型A的描述标识符(该设备描述标识符针对相同类型的设备保持唯一，如安卓手机上，该设备描述标识符都是唯一的；同时不同设备的描述标识符保持不同，如安卓手机和苹果手机上，该设备描述标识符是不同的)；
(2)统一通讯客户端软件向统一通讯服务器发起查询登录请求，请求中包含带上用户帐号1、密码及设备类型A的设备类型描述标识符。
步骤S704，统一通讯服务器收到客户端软件的查询登录请求，对请求进行校验，并返回设备登录校验串，图8是根据本发明优选实施例的统一通讯服务器对客户端查询登录请求的流程图，如图8所示，步骤S704中又包含如下步骤：
步骤S7041，统一通讯服务器对客户端的登录请求进行帐号校验；
步骤S7042，如果帐号不存在，则直接返回用户不存在；
步骤S7043，在账号存在的情况下，判断密码是否正确；
步骤S7044，如果密码错误，则返回密码错误；
步骤S7045，在密码正确的情况下，统一通讯服务器获取客户端登录请求中的设备描述标识符；
步骤S7046，判断统一通讯服务器之前是否给用户帐号1在设备类型A上分配过设备登录校验串；
步骤S7047，如果未分配过，则统一通讯服务器自动生成用户帐号1在设备类型A上的设备登录校验串并保存在服务器中，同时将设备登录校验串返回给客户端(返回的设备登录校验串进行加密处理)；
步骤S7048，如果已给用户帐号1在设备类型A上分配过设备登录校验串，则统一通讯服务器判断该设备登录校验串是否在有效期内；
步骤S7049，如果已过有效期，则重新生成用户帐号1在设备类型A上的设备登录校验串并更新到服务器中，同时将设备登录校验串返回给客户端(返回的设备登录校验串进行加密处理)；
步骤S70410，如果仍在有效内，则直接将设备登录校验串返回给客户端(返回的设备登录校验串进行加密处理)。
其中，上述步骤S702和步骤S704是统一通讯服务器对客户端查询登录请求的流程，对于查询登录请求的流程可具体参见图8。
在完成了客户端的查询登录请求之后，需要对客户端的正式登录请求进行处理。图9是根据本发明优选实施例的统一通讯服务器对客户端正式登录请求的处理流程图，下面结合图9进行说明。
步骤S706，统一通讯客户端获取统一通讯服务器响应中的设备登录校验串，带上用户帐号1、密码、设备登录校验串到服务器发起正式登录请示。本步骤又可以包括下列步骤：
(1)统一通讯客户端软件从统一通讯服务器的查询登录响应中解密获取到用户帐号1在设备类型A上的设备登录校验串；
(2)统一通讯客户端带上用户帐号1，密码，设备登录校验串(进行加密处理)到统一通讯服务器发起正式登录请求。
步骤S708，统一通讯服务器对客户端的正式登录请求进行校验，保存登录数据区，并返回登录成功响应，本步骤又可以包括下列步骤：
步骤S7081，统一通讯服务器对客户端的登录请求进行帐号校验；
步骤S7082，如果帐号不存在，则直接返回用户不存在；
步骤S7083，在账号存在的情况下，判断密码是否正确；
步骤S7084，如果密码错误，则返回密码错误；
步骤S7085，在密码正确的情况下，统一通讯服务器获取客户端登录请求中的设备登录校验串；
步骤S7086，判断该登录校验串是否与之前服务侧为用户帐号1在设备类型A上分配的设备登录校验串一致；
步骤S7087，如果不一致，则返回登录失败；
步骤S7088，如果一致，则再判断用户是否使用用户帐号1在设备类型A已经登录过，如果登录过，则将之前用户帐号1在设备类型A的登录签退掉；统一通讯服务器将用户帐号1在设备类型A上的登录数据区保存到服务器侧的用户帐号1数据区中，同时给客户端返回登录成功响应。
至此用户帐号1在设备类型A上登录成功。
步骤S710-S716，用户再使用用户帐号1在设备类型B(也可以还有其他设备类型如C等)上登录，处理流程与上面步骤S702-S708一致。
至此，用户帐号1完成在不同设备类型上的同时登录到统一通讯服务器。
通过上述实施例及优选实施例克服了相关技术中的单帐号只能同时在一台设备上登录统一通讯服务器的缺点，解决现有技术中存在的统一通讯服务器只根据用户帐号来判断用户是否登录的问题。并且本优选实施例所要解决的问题是当用户在多设备间上使用统一通讯业务时，可以在多设备上使用同个帐号同时登录到统一通讯服务器，在设备间切换时，不需要再频繁地重新登录，即可在每个已登录的设备上使用统一通讯业务功能，大大方便了用户的使用体验，给用户使用统一业务提供方便性。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
如上所述，本发明实施例提供的一种账号登录方法、装置及系统，具有以下有益效果：解决了相关技术中存在的单帐号只能在一台终端上登录统一通讯服务器，当需要在多个不同系统类型的终端上使用同一个登录账号登录统一通讯客户端时，需要频繁地重新登录，并且的统一通讯服务器只能根据用户帐号来判断用户是否登录的问题，进而实现了同个帐号可以在多设备上同时登录到统一通讯服务器，从而在设备间切换时，不需要再频繁地重新登录，即可在每个已登录的设备上使用统一通讯业务功能，给用户使用统一业务提供了方便。
Claims (11)
- 一种账号登录方法，包括：接收第一统一通讯客户端发起的登录请求，其中，所述登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的所述账号的所述设备登录校验串不同；判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号；在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应。
- 根据权利要求1所述的方法，其中，判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号还包括：在判断结果为是的情况下，签退所述其他统一通讯客户端登录的所述账号，并向所述第一统一通讯客户端返回登录所述账号成功的响应。
- 根据权利要求1所述的方法，其中，在判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号之前，还包括：对所述设备登录校验串进行校验。
- 根据权利要求3所述的方法，其中，对所述设备登录校验串进行校验包括：判断所述设备登录校验串是否与服务器中保存的第一系统类型对应的设备登录校验串一致，其中所述第一系统类型为所述第一统一通讯客户端所在终端的系统类型；如果是，则校验通过；否则，拒绝所述登录请求。
- 根据权利要求1所述的方法，其中，在接收第一统一通讯客户端发起的登录请求之前，还包括：接收所述第一统一通讯客户端发送的登录查询请求，其中，所述登录查询请求中携带有设置为描述所述第一统一通讯客户端所在终端的系统类型的描述标识符；根据所述描述标识符为所述第一统一通讯客户端分配所述设备登录校验串。
- 根据权利要求5所述的方法，其中，根据所述描述标识符为所述第一统一通讯客户端分配设备登录校验串包括：根据所述描述标识符判断是否已经存在所述系统类型对应的所述设备登录校验串；在判断结果为否的情况下，生成所述设备登录校验串，并将生成的所述设备登录校验串返回给所述第一统一通讯客户端；和/或，在判断结果为是的情况下，将所述系统类型对应的所述设备登录校验串返回给所述第一统一通讯客户端。
- 根据权利要求6所述的方法，其中，将所述系统类型对应的所述设备登录校验串返回给所述第一统一通讯客户端包括：判断所述设备登录校验串是否仍在有效期；当所述判断结果为所述设备登录校验串仍在有效期时，将所述设备登录校验串返回给所述第一统一通讯客户端；和/或，当所述判断结果为所述设备登录校验串已过有效期时，重新生成所述设备登录校验串，并将重新生成的所述设备登录校验串返回给所述第一统一通讯客户端。
- 一种账号登录方法，包括：第一统一通讯客户端获取设备登录校验串，其中，不同系统类型的设备获取的账号的所述设备登录校验串不同，所述设备登录校验串设置为服务器判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号，并在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应；所述第一统一通讯客户端向所述服务器发起登录请求，其中，所述登录请求中携带所述账号和所述设备登录校验串。
- 一种账号登录装置，位于服务器中，包括：接收模块，设置为接收第一统一通讯客户端发起的登录请求，其中，所述登录请求中携带账号和设备登录校验串，不同系统类型的设备获取的所述账号的所述设备登录校验串不同；判断模块，设置为判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号；处理模块，设置为在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应。
- 一种账号登录装置，位于第一统一通讯客户端中，包括：获取模块，设置为获取设备登录校验串，其中，不同系统类型的设备获取的账号的所述设备登录校验串不同，所述设备登录校验串设置为服务器判断是否存在其他统一通讯客户端使用所述设备登录校验串已经登录所述账号，并在判断结果为否的情况下，向所述统一通讯客户端返回登录所述账号成功的响应；发送模块，设置为所述第一统一通讯客户端向所述服务器发起登录请求，其中，所述登录请求中携带所述账号和所述设备登录校验串。
- 一种账号登录系统，包括如权利要求9所述的位于服务器中的账号登录装置，还包括如权利要求10所述的位于第一统一通讯客户端中的账号登录装置。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410298136.5 | 2014-06-26 | ||
| CN201410298136.5A CN105306203A (zh) | 2014-06-26 | 2014-06-26 | 账号登录方法、装置及系统 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2015196817A1 true WO2015196817A1 (zh) | 2015-12-30 |
Family
ID=54936705
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2015/072924 WO2015196817A1 (zh) | 2014-06-26 | 2015-02-12 | 账号登录方法、装置及系统 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105306203A (zh) |
| WO (1) | WO2015196817A1 (zh) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017092701A1 (zh) * | 2015-12-02 | 2017-06-08 | 中兴通讯股份有限公司 | 一种终端登录方法、服务器及系统 |
| CN112465322A (zh) * | 2020-11-19 | 2021-03-09 | 许继集团有限公司 | 一种应用于变电站自动化系统的用户管理装置 |
| CN113158173A (zh) * | 2021-05-13 | 2021-07-23 | 杭州朗和科技有限公司 | 账号分配方法、介质、装置和计算设备 |
| CN113746794A (zh) * | 2020-11-20 | 2021-12-03 | 北京沃东天骏信息技术有限公司 | 账号的处理方法、装置、电子设备和计算机存储介质 |
| CN113923010A (zh) * | 2021-09-30 | 2022-01-11 | 上海影创信息科技有限公司 | 基于虚拟现实的头显设备单点登录方法和系统 |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106846201B (zh) * | 2017-01-25 | 2021-04-27 | 福建天晴数码有限公司 | 一种基于网络教育的学时管理方法 |
| CN111064915B (zh) * | 2019-11-18 | 2021-05-14 | 北京小米移动软件有限公司 | 音视频通话的方法、装置、设备及可读存储介质 |
| CN113518091B (zh) * | 2021-07-19 | 2023-04-28 | 中移（杭州）信息技术有限公司 | 多用户认证方法、装置、系统及存储介质 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252548A (zh) * | 2008-01-28 | 2008-08-27 | 北京亿企通信息技术有限公司 | 一种在即时通信工具中多点登录的方法 |
| CN102025648A (zh) * | 2009-09-16 | 2011-04-20 | 腾讯科技（深圳）有限公司 | 一种即时通讯的方法和服务器 |
| CN103259770A (zh) * | 2012-02-17 | 2013-08-21 | 腾讯科技（深圳）有限公司 | 登录方法及登录服务器 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140173269A1 (en) * | 2012-12-18 | 2014-06-19 | Apple Inc. | Event Sharing Protocol for Data Processing Devices |
-
2014
- 2014-06-26 CN CN201410298136.5A patent/CN105306203A/zh not_active Withdrawn
-
2015
- 2015-02-12 WO PCT/CN2015/072924 patent/WO2015196817A1/zh active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252548A (zh) * | 2008-01-28 | 2008-08-27 | 北京亿企通信息技术有限公司 | 一种在即时通信工具中多点登录的方法 |
| CN102025648A (zh) * | 2009-09-16 | 2011-04-20 | 腾讯科技（深圳）有限公司 | 一种即时通讯的方法和服务器 |
| CN103259770A (zh) * | 2012-02-17 | 2013-08-21 | 腾讯科技（深圳）有限公司 | 登录方法及登录服务器 |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017092701A1 (zh) * | 2015-12-02 | 2017-06-08 | 中兴通讯股份有限公司 | 一种终端登录方法、服务器及系统 |
| CN112465322A (zh) * | 2020-11-19 | 2021-03-09 | 许继集团有限公司 | 一种应用于变电站自动化系统的用户管理装置 |
| CN113746794A (zh) * | 2020-11-20 | 2021-12-03 | 北京沃东天骏信息技术有限公司 | 账号的处理方法、装置、电子设备和计算机存储介质 |
| CN113158173A (zh) * | 2021-05-13 | 2021-07-23 | 杭州朗和科技有限公司 | 账号分配方法、介质、装置和计算设备 |
| CN113923010A (zh) * | 2021-09-30 | 2022-01-11 | 上海影创信息科技有限公司 | 基于虚拟现实的头显设备单点登录方法和系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105306203A (zh) | 2016-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2015196817A1 (zh) | 账号登录方法、装置及系统 | |
| US9722984B2 (en) | Proximity-based authentication | |
| CN111010372A (zh) | 区块链网络身份认证系统、数据处理方法及网关设备 | |
| WO2017036365A1 (zh) | 一种语音通信处理方法、电子设备、系统及存储介质 | |
| US20160125416A1 (en) | Authentication system | |
| EP3164793B1 (en) | Dual channel identity authentication | |
| US11159522B2 (en) | Method for authentication, server, device and data carrier | |
| US9009793B2 (en) | Dynamic pin dual factor authentication using mobile device | |
| WO2018184433A1 (zh) | 一种物联网认证系统和物联网认证方法 | |
| TW201706900A (zh) | 終端的認證處理、認證方法及裝置、系統 | |
| CN106921663B (zh) | 基于智能终端软件/智能终端的身份持续认证系统及方法 | |
| CN107086979B (zh) | 一种用户终端验证登录方法及装置 | |
| CN104883367B (zh) | 一种辅助验证登陆的方法、系统和应用客户端 | |
| CN105656850B (zh) | 一种数据处理方法、相关装置及系统 | |
| WO2016045484A1 (zh) | 一种实现远程控制的方法和终端 | |
| WO2016078419A1 (zh) | 一种开放授权方法、装置及开放平台 | |
| WO2017076216A1 (zh) | 服务器、移动终端、网络实名认证系统及方法 | |
| US11388159B2 (en) | Variable-step authentication for communications in controlled environment | |
| US11856130B2 (en) | Privileged electronic communications with inmates | |
| JP2023145552A (ja) | 装置への安全な資格情報転送を認証するための方法およびシステム | |
| CN105357224A (zh) | 一种智能家居网关注册、移除方法及系统 | |
| WO2014169802A1 (zh) | 终端、网络侧设备、终端应用控制方法及系统 | |
| CN109756469B (zh) | 一种公用账号管理方法、装置及计算机可读存储介质 | |
| US11575667B1 (en) | System and method for secure communications | |
| CN105635060B (zh) | 一种获取应用数据的方法、鉴权认证服务器及网关 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15811634 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 15811634 Country of ref document: EP Kind code of ref document: A1 |