CN104486747A - Method and device for cross-terminal account login - Google Patents
Method and device for cross-terminal account login Download PDFInfo
- Publication number
- CN104486747A CN104486747A CN201410797971.3A CN201410797971A CN104486747A CN 104486747 A CN104486747 A CN 104486747A CN 201410797971 A CN201410797971 A CN 201410797971A CN 104486747 A CN104486747 A CN 104486747A
- Authority
- CN
- China
- Prior art keywords
- terminal
- device identifier
- information
- account information
- available target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000008569 process Effects 0.000 claims description 15
- 238000006243 chemical reaction Methods 0.000 claims description 3
- 238000013475 authorization Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
An embodiment of the invention discloses a method and a device for cross-terminal account login and is applied to a server. The method comprises steps as follows: receiving a login request of a first terminal, wherein the login request carries a first device identifier of the first terminal and is generated after the first terminal responds to a start instruction of an application program; acquiring device-identifier-associated information corresponding to the first device identifier; determining available target account information corresponding to the first terminal; feeding back the available target account information to the first terminal so as to enable the first terminal to use the available target account information to log in the application program. Compared with the prior art, the method has the advantages that the method is controlled by the program to be finished automatically, so that operations are simpler and more convenient, and the user experience is better.
Description
Technical Field
The embodiment of the invention relates to the field of terminal application, in particular to a cross-terminal account login method and device.
Background
With the rapid development of science and technology, various application programs on the terminal are continuously enriched and facilitate the lives of the public. The user usually logs in the corresponding application program through the account corresponding to the account, and then performs corresponding operations. The account login of one terminal cannot meet the requirements of a user, and the user urgently needs a cross-terminal account login method, namely, a plurality of terminals can log in an application program corresponding to the account through the same account so as to operate the application program more conveniently.
In the prior art, two methods can realize cross-terminal account login. The first method is to directly input the account and the password of the application program on the terminal which does not log in the account for logging in, and the method can realize cross-terminal account logging, but is extremely inconvenient to operate, and needs to manually input characters, and particularly for the terminal which is very difficult to input, such as a network television, the login intention of a user is reduced. In the second method, the two-dimensional code on the terminal which does not log in the account is scanned by using the terminal which logs in the account to log in, although the inconvenience of inputting characters manually by a user is avoided, the scanning and shooting process is complex, so that the user experience is poor.
In summary, how to realize the cross-terminal account login under the premise of simple and convenient operation becomes an urgent problem to be solved.
Disclosure of Invention
Based on the above problems, the embodiment of the invention discloses a method and a device for cross-terminal account login, which can realize cross-terminal account login by simple and convenient operation. The technical scheme is as follows:
in a first aspect, an embodiment of the present invention provides a method for cross-terminal account login, which is applied to a server, and the method includes:
receiving a login request of a first terminal, wherein the login request is a request which is generated by the first terminal after responding to a starting instruction of an application program and carries a first equipment identifier of the first terminal;
obtaining device identifier association information corresponding to the first device identifier, wherein the device identifier association information is association relationship information between the first device identifier and a second device identifier associated with the first device identifier;
determining available target account information corresponding to the first terminal, wherein the available target account information is account information utilized by a second terminal with the second device identifier to log in the application program;
and feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information.
Optionally, the determining the available target account information corresponding to the first terminal includes:
sending inquiry information to a second terminal with the second device identifier, wherein the inquiry information inquires whether the first terminal is allowed to log in the application program by using account information uploaded by the second terminal and used for logging in the application program by the first terminal;
and after receiving a login permission instruction sent by the user based on the inquiry information and fed back by the second terminal, taking the account information as the available target account information corresponding to the first terminal.
Optionally, the determining the available target account information corresponding to the first terminal includes:
and directly taking account information uploaded by the second terminal with the second equipment identifier and utilized by logging in the application program as available target account information corresponding to the first terminal.
Optionally, the determining the available target account information corresponding to the first terminal includes:
sending inquiry information to a second terminal with the second device identifier, wherein the inquiry information inquires whether the first terminal is allowed to log in the application program by using account information used by the second terminal for logging in the application program currently;
and after receiving a login permission instruction sent by the user based on the inquiry information and fed back by the second terminal, further requesting to obtain account information uploaded by the second terminal and utilized by the current login application program, and taking the account information as available target account information corresponding to the first terminal.
Optionally, the process of generating the device identifier association information includes:
when detecting that both the first terminal and the second terminal have historical login records aiming at the account information, respectively sending binding requests to the first terminal and the second terminal so that both the first terminal and the second terminal output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and associating the first device identifier with the second device identifier to generate the device identifier association information after receiving a binding permission instruction sent by the respective user based on the corresponding inquiry information.
Optionally, the process of generating the device identifier association information includes:
receiving space coordinates of positions where the first terminal and the second terminal are located;
sending binding requests to the first terminal and the second terminal corresponding to the two spatial coordinates respectively, so that the first terminal and the second terminal both output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and associating the first device identifier with the second device identifier to generate the device identifier association information after receiving a binding permission instruction sent by the respective user based on the corresponding inquiry information.
Optionally, the device identifier association information is binding relationship information between the first device identifier uploaded by the second terminal and a second device identifier associated with the first device identifier;
wherein the process of generating the device identifier association information by the second terminal includes:
acquiring the first equipment identifier through a USB connecting line, and associating the second equipment identifier with the first equipment identifier to generate equipment identifier association information;
or,
acquiring the first device identifier by using a device discovery protocol of a local area network, and associating the second device identifier with the first device identifier to generate device identifier association information;
or,
and acquiring the first equipment identifier which is manually input by a user and is displayed in clear text by the first terminal, and associating the second equipment identifier with the first equipment identifier to generate equipment identifier association information.
Optionally, the obtaining, by the second terminal, the first device identifier by using a device discovery protocol of a local area network includes:
deploying software on the first terminal and the second terminal, so that the first device identifier is transmitted to the second terminal through the software, and then the first device identifier is received;
or,
converting an IP address of the first terminal into a MAC address using an ARP protocol (address resolution protocol);
determining the converted MAC address as the first device identifier.
In a second aspect, an embodiment of the present invention further provides a device for logging in across terminal accounts, which is applied to a server, and the device includes:
a login request receiving unit, configured to receive a login request of a first terminal, where the login request is a request that is generated by the first terminal after responding to a start instruction of an application and carries a first device identifier of the first terminal;
an equipment identifier association information obtaining unit, configured to obtain equipment identifier association information corresponding to the first equipment identifier, where the equipment identifier association information is association relationship information between the first equipment identifier and a second equipment identifier associated with the first equipment identifier;
an available target account information determining unit, configured to determine available target account information corresponding to the first terminal, where the available target account information is account information used by a second terminal having the second device identifier to log in the application program;
and the available target account information feedback unit is used for feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information.
Optionally, the available target account information determining unit includes:
an inquiry information sending subunit, configured to send inquiry information to a second terminal having the second device identifier, the inquiry information inquiring whether the first terminal allows the first terminal to log in the application program using account information uploaded by the second terminal and used for logging in the application program by itself;
and the available target account information determining subunit is configured to, after receiving a login permission instruction sent by the user based on the query information and fed back by the second terminal, use the account information as available target account information corresponding to the first terminal.
Optionally, the available target account information determining unit is specifically configured to:
and directly taking account information uploaded by the second terminal with the second equipment identifier and utilized by logging in the application program as available target account information corresponding to the first terminal.
Optionally, the available target account information determining unit includes:
an inquiry information sending subunit, configured to send inquiry information to a second terminal having the second device identifier, the inquiry information inquiring whether the first terminal is allowed to log in the application program by using account information used by the second terminal itself to currently log in the application program;
and the available target account information determining subunit is configured to, after receiving a login permission instruction sent by the user based on the query information and fed back by the second terminal, further request to obtain account information used by the current login application program uploaded by the second terminal, and use the account information as available target account information corresponding to the first terminal.
Optionally, the device identifier association information is generated by a device identifier association information generation unit;
wherein the device identifier association information generation unit includes:
a binding request sending subunit, configured to, when it is detected that both the first terminal and the second terminal have a history login record for the account information, send a binding request to the first terminal and the second terminal, respectively, so that both the first terminal and the second terminal output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and the device identifier association information generation subunit is configured to, after receiving a binding permission instruction issued by a respective user based on the corresponding inquiry information, associate the first device identifier with the second device identifier to generate the device identifier association information.
Optionally, the device identifier association information is generated by a device identifier association information generation unit;
wherein the device identifier association information generation unit includes:
the space coordinate receiving subunit is used for receiving space coordinates of positions where the first terminal and the second terminal are located;
a binding request sending subunit, configured to send a binding request to the first terminal and the second terminal corresponding to two spatial coordinates, respectively, so that the first terminal and the second terminal both output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and the device identifier association information generation subunit is configured to, after receiving a binding permission instruction issued by a respective user based on the corresponding inquiry information, associate the first device identifier with the second device identifier to generate the device identifier association information.
Optionally, the device identifier association information is binding relationship information between the first device identifier uploaded by the second terminal and a second device identifier associated with the first device identifier;
wherein the device identifier association information is generated by a device identifier association information generation unit of the second terminal;
wherein the device identifier association information generation unit includes:
a first obtaining subunit, configured to obtain the first device identifier through a USB connection line; a first association information generation subunit, configured to associate the second device identifier with the first device identifier, and generate device identifier association information;
or,
the device identifier association information generation unit includes:
a second obtaining subunit, configured to obtain the first device identifier using a device discovery protocol of a local area network; a second association information generation subunit, configured to associate the second device identifier with the first device identifier, and generate device identifier association information;
or,
the device identifier association information generation unit includes:
the third acquisition subunit is used for acquiring the first equipment identifier which is manually input by a user and is displayed in the clear text of the first terminal; and the third association information generation subunit is configured to associate the second device identifier with the first device identifier, and generate device identifier association information.
Optionally, the second obtaining subunit includes:
a software deployment module for deploying software on itself and the first terminal such that the first device identifier is transmitted to the second terminal by the software;
a first device identifier receiving module for receiving the first device identifier;
or,
the second acquisition subunit includes:
a conversion module for converting an IP address of the first terminal into an MAC address using an ARP protocol (address resolution protocol);
a first device identifier determining module for determining the converted MAC address as the first device identifier.
In the embodiment of the invention, a server receives a login request of a first terminal, wherein the login request is a request which is generated by the first terminal after responding to a starting instruction of an application program and carries a first equipment identifier of the first terminal; obtaining device identifier association information corresponding to the first device identifier, wherein the device identifier association information is association relationship information between the first device identifier and a second device identifier associated with the first device identifier; determining available target account information corresponding to the first terminal, wherein the available target account information is account information utilized by a second terminal with the second device identifier to log in the application program; and feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information. Compared with the prior art, the method is automatically completed under the control of a program, so that the operation is simpler and more convenient, and the user experience is better.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flowchart of a cross-terminal account login method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a cross-terminal account login device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
First, a method for cross-terminal account login provided by the embodiment of the present invention is explained, where the method is applied to a server and may include the following steps:
receiving a login request of a first terminal, wherein the login request is a request which is generated by the first terminal after responding to a starting instruction of an application program and carries a first equipment identifier of the first terminal;
obtaining device identifier association information corresponding to the first device identifier, wherein the device identifier association information is association relationship information between the first device identifier and a second device identifier associated with the first device identifier;
determining available target account information corresponding to the first terminal, wherein the available target account information is account information utilized by a second terminal with the second device identifier to log in the application program;
and feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information.
It should be noted that the server is a server corresponding to an application program opened by a user, where the application program allows the user to log in on different terminals by using the same account information, for example: an instant messenger program (i.e., a WeChat program, a QQ program, etc.), a video playback program, a music playback program, etc., are all reasonable.
The method in the embodiment of the invention is automatically completed under the control of the program, so the operation is simpler and more convenient, and the user experience is better.
The steps of the embodiments of the present invention are described in detail below.
Fig. 1 is a flowchart of a method for cross-terminal account login in an embodiment of the present invention, which is applied to a server and may include the following steps:
s101, receiving a login request of a first terminal, wherein the login request is a request which is generated by the first terminal after responding to a starting instruction of an application program and carries a first equipment identifier of the first terminal;
it should be noted that the application is installed in the first terminal and runs by using the first terminal environment. After the user executes the operation of starting the application program, the first terminal may receive a start instruction of the application program, and then make a corresponding response to the start instruction. For example, the operation of starting the application program may be: double-clicking on the shortcut icon for an application, or clicking on the menu option for that application in the "start" menu, etc. The first device identifier and the first terminal are uniquely corresponding, the uniquely corresponding first terminal can be found through the first device identifier, and the first device identifier can be used as a terminal number of the first terminal. In general, the first device identifier may include: network card address (MAC address) or mobile equipment international identity (IMEI).
In this step, after the first terminal responds to the application program, those skilled in the art can understand that the first terminal automatically constructs a login request and sends the login request to the server, and the construction process is within the scope known to those skilled in the art and will not be described herein. The login request carries a first identifier of the first terminal. Therefore, the server receives the login request, and accordingly determines the first terminal to be logged in, and then the step S102 is performed.
S102, obtaining the device identifier associated information corresponding to the first device identifier;
wherein the device identifier association information is association relationship information between the first device identifier and a second device identifier associated with the first device identifier; the device identifier association information embodies a device binding relationship between the first terminal having the first device identifier and the second terminal having the second device identifier. It should be noted that, in the embodiment of the present invention, the form of device binding is an example of association of device identifiers, but the device binding is not necessarily embodied only by association of device identifiers, and may also be embodied in other forms known to those skilled in the art, and the embodiment of the present invention does not limit this form. The device identifier association information may be generated locally in the server, or may be generated by the second terminal and reported to the server. For clarity of layout, the generation of the device identifier association information will be described in detail later.
Specifically, after receiving the login request of the first terminal in S101, the first device identifier of the first terminal may be known, and since the server locally stores the device identifier association information, the server may automatically search whether the device identifier association information including the first device identifier exists, and when the device identifier association information exists locally, the server obtains the device identifier association information, that is, obtains the second device identifier therefrom. Because the device identifier association information is generated along with the binding relationship between the first terminal and the second terminal, the device identifier association information includes the first device identifier and the second device identifier corresponding to the second terminal, and therefore the device identifier association information is searched, that is, the second device identifier is obtained correspondingly, and the step S103 is further performed.
S103, determining available target account information corresponding to the first terminal;
the available target account information is account information used by the second terminal having the second device identifier to log in the application program, and in actual application, the account information may be historical log-in account information of the second terminal or current log-in account information of the second terminal. It is understood that the second terminal can log in the application program by using the account information, and the first terminal can also log in the application program by using the account information if the account information is obtained.
Specifically, in S102, the device identifier association information is obtained, the second device identifier is correspondingly obtained, the second terminal can be determined by the second device identifier, the available target account information is account information uploaded to the server by the second terminal, and the available target account information corresponding to the first terminal can be determined by using the account information. Several ways of determining the available target account information corresponding to the first terminal are listed below:
in a specific embodiment of the present invention, determining available target account information corresponding to the first terminal specifically includes:
sending inquiry information to a second terminal with the second device identifier, wherein the inquiry information inquires whether the first terminal is allowed to log in the application program by using account information uploaded by the second terminal and used for logging in the application program by the first terminal;
and after receiving a login permission instruction sent by the user based on the inquiry information and fed back by the second terminal, taking the account information as the available target account information corresponding to the first terminal.
Specifically, in this implementation manner, the second terminal uploads, to the server, account information used for logging in the application program by itself in advance, where the account information may be historical account information for logging in the application program by the second terminal, or account information used for currently logging in the application program, and the embodiment of the present invention is not limited thereto. The server may receive the account information uploaded by the second terminal, and after obtaining the second device identifier in S102, automatically send an inquiry message to the second terminal having the second device identifier, the inquiry message inquiring whether the first terminal allows the first terminal to log in the application program by using the account information uploaded by the second terminal, the account information being used as the available target account information of the first terminal after receiving the instruction of allowing the second terminal to log in.
In the embodiment, the authorization of the second terminal is firstly acquired by sending the inquiry information, and then the account information of the second terminal is used as the available target account information of the first terminal to perform the subsequent steps, so that the security of the account information is ensured, the dominance of the second terminal to the account information is ensured, and the user experience is improved.
In another specific embodiment of the present invention, the determining the available target account information corresponding to the first terminal may specifically be:
and directly taking account information uploaded by the second terminal with the second equipment identifier and utilized by logging in the application program as available target account information corresponding to the first terminal.
Specifically, the present embodiment manages the account information in a pre-authorization manner. The second terminal uploads account information used for logging in the application program to the server in advance, where the account information may be historical account information of the second terminal logging in the application program or account information used for currently logging in the application program, and the embodiment of the present invention is not limited thereto. The server may receive the account information uploaded by the second terminal, because the second terminal is pre-authorized to the server, and all terminals bound to the second terminal are allowed to log in the account information, so that after the second device identifier is obtained in S102, the server directly uses the account information as the available target account information of the first terminal.
In the specific embodiment, the account information is managed in a pre-authorization mode, so that the server can quickly determine the available target account information of the first terminal, and the method is simpler and more convenient and better in user experience.
In another specific embodiment of the present invention, the determining the available target account information corresponding to the first terminal may specifically be:
sending inquiry information to a second terminal with the second device identifier, wherein the inquiry information inquires whether the first terminal is allowed to log in the application program by using account information used by the second terminal for logging in the application program currently;
and after receiving a login permission instruction sent by the user based on the inquiry information and fed back by the second terminal, further requesting to obtain account information uploaded by the second terminal and utilized by the current login application program, and taking the account information as available target account information corresponding to the first terminal.
Specifically, in this implementation manner, after the second device identifier is obtained in S102, an inquiry message inquiring whether the first terminal is allowed to register the application program by using the account information used by the second terminal to currently register the application program by the user is automatically sent to the second terminal having the second device identifier, when the second terminal is allowed to register, an instruction for allowing to register and the account information used by the second terminal to currently register the application program are sent to the server, and accordingly, after the server receives the account information, the account information is used as the available target account information of the first terminal.
In the embodiment, the authorization of the second terminal is firstly acquired by sending the inquiry information, then the current login account information of the second terminal is received, and the account information is used as the available target account information of the first terminal to perform the subsequent steps, so that the domination right of the second terminal to the account information is ensured, the real-time performance and the login performance of the account information are also ensured, and the use of the user is facilitated.
S104, feeding back the available target account information to the first terminal, so that the first terminal can log in the application program by using the available target account information.
Specifically, in S103, the available target account information corresponding to the first terminal is determined, and the available target account information is sent to the first terminal, and those skilled in the art can understand that the first terminal can directly log in the application program by using the available target account information.
The following describes a method for generating device identifier association information in detail.
In a first implementation manner, the device identifier association information may be generated at a server, and the process of generating the device identifier association information specifically includes:
when detecting that both the first terminal and the second terminal have historical login records aiming at the account information, respectively sending binding requests to the first terminal and the second terminal so that both the first terminal and the second terminal output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and associating the first device identifier with the second device identifier to generate the device identifier association information after receiving a binding permission instruction sent by the respective user based on the corresponding inquiry information.
Specifically, in this implementation, the device identifier association information is generated locally at the server, and as will be understood by those skilled in the art, the server may detect whether the first terminal and the second terminal have a history log-in record for the application, this implementation method utilizes this point, and when the presence is detected, automatically sends a binding request to the first terminal and the second terminal, respectively, where the binding request may be output in a pop-up window form on the first terminal and the second terminal, or may be output in a message alert form, and the embodiment of the present invention is not limited thereto. When the user holding the first terminal and the user holding the second terminal both allow binding, the server associates the first device identifier and the second device identifier together and stores them locally after receiving the instruction to allow binding. For example, if the first device identifier is denoted by D1 and the device identifier is denoted by D2, the device identifier association information is < D1, D2 >.
In a second implementation manner, the device identifier association information may be generated at a server, and the process of generating the device identifier association information specifically includes:
receiving space coordinates of positions where the first terminal and the second terminal are located;
sending binding requests to the first terminal and the second terminal corresponding to the two spatial coordinates respectively, so that the first terminal and the second terminal both output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and associating the first device identifier with the second device identifier to generate the device identifier association information after receiving a binding permission instruction sent by the respective user based on the corresponding inquiry information.
Specifically, the first terminal and the second terminal actively upload the spatial coordinates of their current positions to the server, and then the server sends a binding request to the first terminal and the second terminal at the positions indicated by the two received spatial coordinates, where the binding request may be output in a pop-up window form on the first terminal and the second terminal, or may be output in a message reminding manner, which is not limited in the embodiment of the present invention. When the user holding the first terminal and the user holding the second terminal both allow binding, the server associates the first device identifier and the second device identifier together and stores them locally after receiving the instruction to allow binding. For example, if the first device identifier is denoted by D1 and the device identifier is denoted by D2, the device identifier association information is < D1, D2 >.
In a third implementation manner, the device identifier association information may be generated in the second terminal, and the process of generating the device identifier association information specifically includes:
acquiring the first equipment identifier through a USB connecting line, and associating the second equipment identifier with the first equipment identifier to generate equipment identifier association information;
specifically, in this implementation manner, the second terminal serves as a host, the first terminal serves as an external device, and after the first terminal is successfully connected to the second terminal through the USB connection line, the first terminal transmits data to the outside through the USB interface, where the data includes related parameters such as a first device identifier and a model of the first terminal, so that the second terminal obtains the first device identifier after receiving the data, and further associates the first device identifier with its own second device identifier to generate device identifier association information. For example, if the first device identifier is denoted by D1 and the device identifier is denoted by D2, the device identifier association information is < D1, D2 >. In a subsequent step, the device identifier association information is uploaded to a server.
In a fourth implementation manner, the device identifier association information may be generated in the second terminal, and the process of generating the device identifier association information specifically includes:
acquiring the first device identifier by using a device discovery protocol of a local area network, and associating the second device identifier with the first device identifier to generate device identifier association information;
the obtaining of the first device identifier by using a device discovery protocol of a local area network may be implemented in two ways:
first, deploying software on itself and the first terminal so that the first device identifier is transmitted to the second terminal through the software, and then receiving the first device identifier;
specifically, software is installed on the first terminal and the second terminal, the first terminal and the second terminal can be connected in the local area network through the software, and in the connection process, the first terminal registers and propagates a message by using a first device identifier of the first terminal at a control port of the local area network. According to the simple service discovery protocol, the second terminal may discover the first terminal in the local area network, and accordingly, the first device identifier corresponding to the first terminal is obtained according to the propagation message, and the first device identifier is further associated with the second device identifier of the second terminal to generate device identifier association information. For example, if the first device identifier is denoted by D1 and the device identifier is denoted by D2, the device identifier association information is < D1, D2 >. In a subsequent step, the device identifier association information is uploaded to a server.
Second, an IP address of the first terminal is converted into a MAC address using an ARP protocol (address resolution protocol), and the converted MAC address is determined as the first device identifier.
Specifically, the arp (address Resolution protocol) protocol is an address Resolution protocol, which is a TCP/IP protocol for acquiring a MAC address (physical address). In IP-ethernet, ARP provides the MAC address of a node when an upper layer protocol is to send a packet, with the IP address of the node. When the first terminal and the second terminal are connected to a network in the same local area network, those skilled in the art can understand that the second terminal can easily obtain the IP address of the first terminal, and then convert the IP address of the first terminal into the MAC address by using the ARP protocol, and the MAC address can be used as the device identifier of the first terminal, so as to obtain the first device identifier corresponding to the first terminal, and further associate the first device identifier with the second device identifier of the second terminal to generate the device identifier association information. For example, if the first device identifier is denoted by D1 and the device identifier is denoted by D2, the device identifier association information is < D1, D2 >. In a subsequent step, the device identifier association information is uploaded to a server.
In a fifth implementation manner, the device identifier association information may be generated in the second terminal, and the process of generating the device identifier association information specifically includes:
and acquiring the first equipment identifier which is manually input by a user and is displayed in clear text by the first terminal, and associating the second equipment identifier with the first equipment identifier to generate equipment identifier association information.
Specifically, the first device identifier may be displayed on the corresponding first terminal, so that a user holding the second terminal may directly and manually input the first device identifier on the own device, and the second terminal associates the obtained first device identifier with the own second device identifier to generate device identifier association information. For example, if the first device identifier is denoted by D1 and the device identifier is denoted by D2, the device identifier association information is < D1, D2 >. In a subsequent step, the device identifier association information is uploaded to a server.
In the embodiment of the invention, a server receives a login request of a first terminal, wherein the login request is a request which is generated by the first terminal after responding to a starting instruction of an application program and carries a first equipment identifier of the first terminal; obtaining device identifier association information corresponding to the first device identifier, wherein the device identifier association information is association relationship information between the first device identifier and a second device identifier associated with the first device identifier; determining available target account information corresponding to the first terminal, wherein the available target account information is account information utilized by a second terminal with the second device identifier to log in the application program; and feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information. Compared with the prior art, the method is automatically completed under the control of a program, so that the operation is simpler and more convenient, and the user experience is better.
Corresponding to the above method embodiment, an embodiment of the present invention further provides a device for logging in a cross-terminal account, as shown in fig. 2, where the device is applied to a server, and may include the following units:
a login request receiving unit 210, configured to receive a login request of a first terminal, where the login request is a request that is generated by the first terminal after responding to a start instruction of an application and carries a first device identifier of the first terminal;
an apparatus identifier association information obtaining unit 220, configured to obtain apparatus identifier association information corresponding to the first apparatus identifier, where the apparatus identifier association information is association relationship information between the first apparatus identifier and a second apparatus identifier associated with the first apparatus identifier;
an available target account information determining unit 230, configured to determine available target account information corresponding to the first terminal, where the available target account information is account information used by a second terminal having the second device identifier to log in the application;
an available target account information feedback unit 240, configured to feed back the available target account information to the first terminal, so that the first terminal logs in the application program by using the available target account information.
In the embodiment of the invention, a server receives a login request of a first terminal, wherein the login request is a request which is generated by the first terminal after responding to a starting instruction of an application program and carries a first equipment identifier of the first terminal; obtaining device identifier association information corresponding to the first device identifier, wherein the device identifier association information is association relationship information between the first device identifier and a second device identifier associated with the first device identifier; determining available target account information corresponding to the first terminal, wherein the available target account information is account information utilized by a second terminal with the second device identifier to log in the application program; and feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information. Compared with the prior art, the method is automatically completed under the control of a program, so that the operation is simpler and more convenient, and the user experience is better.
Optionally, the available target account information determining unit 230 includes:
an inquiry information sending subunit, configured to send inquiry information to a second terminal having the second device identifier, the inquiry information inquiring whether the first terminal allows the first terminal to log in the application program using account information uploaded by the second terminal and used for logging in the application program by itself;
and the available target account information determining subunit is configured to, after receiving a login permission instruction sent by the user based on the query information and fed back by the second terminal, use the account information as available target account information corresponding to the first terminal.
Optionally, the available target account information determining unit 230 is specifically configured to:
and directly taking account information uploaded by the second terminal with the second equipment identifier and utilized by logging in the application program as available target account information corresponding to the first terminal.
Optionally, the available target account information determining unit 230 includes:
an inquiry information sending subunit, configured to send inquiry information to a second terminal having the second device identifier, the inquiry information inquiring whether the first terminal is allowed to log in the application program by using account information used by the second terminal itself to currently log in the application program;
and the available target account information determining subunit is configured to, after receiving a login permission instruction sent by the user based on the query information and fed back by the second terminal, further request to obtain account information used by the current login application program uploaded by the second terminal, and use the account information as available target account information corresponding to the first terminal.
Optionally, the device identifier association information is generated by a device identifier association information generation unit;
wherein the device identifier association information generation unit includes:
a binding request sending subunit, configured to, when it is detected that both the first terminal and the second terminal have a history login record for the account information, send a binding request to the first terminal and the second terminal, respectively, so that both the first terminal and the second terminal output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and the device identifier association information generation subunit is configured to, after receiving a binding permission instruction issued by a respective user based on the corresponding inquiry information, associate the first device identifier with the second device identifier to generate the device identifier association information.
Optionally, the device identifier association information is generated by a device identifier association information generation unit;
wherein the device identifier association information generation unit includes:
the space coordinate receiving subunit is used for receiving space coordinates of positions where the first terminal and the second terminal are located;
a binding request sending subunit, configured to send a binding request to the first terminal and the second terminal corresponding to two spatial coordinates, respectively, so that the first terminal and the second terminal both output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and the device identifier association information generation subunit is configured to, after receiving a binding permission instruction issued by a respective user based on the corresponding inquiry information, associate the first device identifier with the second device identifier to generate the device identifier association information.
Optionally, the device identifier association information is binding relationship information between the first device identifier uploaded by the second terminal and a second device identifier associated with the first device identifier;
wherein the device identifier association information generating unit of the second terminal includes:
a first obtaining subunit, configured to obtain the first device identifier through a USB connection line;
a first association information generation subunit, configured to associate the second device identifier with the first device identifier, and generate device identifier association information;
or,
the device identifier association information generation unit includes:
a second obtaining subunit, configured to obtain the first device identifier using a device discovery protocol of a local area network;
a second association information generation subunit, configured to associate the second device identifier with the first device identifier, and generate device identifier association information;
or,
the device identifier association information generation unit includes:
the third acquisition subunit is used for acquiring the first equipment identifier which is manually input by a user and is displayed in the clear text of the first terminal;
and the third association information generation subunit is configured to associate the second device identifier with the first device identifier, and generate device identifier association information.
Optionally, the second obtaining subunit includes:
a software deployment module for deploying software on itself and the first terminal such that the first device identifier is transmitted to the second terminal by the software;
a first device identifier receiving module for receiving the first device identifier;
or,
the second acquisition subunit includes:
a conversion module for converting an IP address of the first terminal into an MAC address using an ARP protocol (address resolution protocol);
a first device identifier determining module for determining the converted MAC address as the first device identifier.
For system or apparatus embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for relevant points.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Those skilled in the art will appreciate that all or part of the steps in the above method embodiments may be implemented by a program to instruct relevant hardware to perform the steps, and the program may be stored in a computer-readable storage medium, which is referred to herein as a storage medium, such as: ROM/RAM, magnetic disk, optical disk, etc.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (16)
1. A method for logging in across terminal accounts is applied to a server, and the method comprises the following steps:
receiving a login request of a first terminal, wherein the login request is a request which is generated by the first terminal after responding to a starting instruction of an application program and carries a first equipment identifier of the first terminal;
obtaining device identifier association information corresponding to the first device identifier, wherein the device identifier association information is association relationship information between the first device identifier and a second device identifier associated with the first device identifier;
determining available target account information corresponding to the first terminal, wherein the available target account information is account information utilized by a second terminal with the second device identifier to log in the application program;
and feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information.
2. The method of claim 1, wherein the determining the available target account information corresponding to the first terminal comprises:
sending inquiry information to a second terminal with the second device identifier, wherein the inquiry information inquires whether the first terminal is allowed to log in the application program by using account information uploaded by the second terminal and used for logging in the application program by the first terminal;
and after receiving a login permission instruction sent by the user based on the inquiry information and fed back by the second terminal, taking the account information as the available target account information corresponding to the first terminal.
3. The method of claim 1, wherein the determining the available target account information corresponding to the first terminal comprises:
and directly taking account information uploaded by the second terminal with the second equipment identifier and utilized by logging in the application program as available target account information corresponding to the first terminal.
4. The method of claim 1, wherein the determining the available target account information corresponding to the first terminal comprises:
sending inquiry information to a second terminal with the second device identifier, wherein the inquiry information inquires whether the first terminal is allowed to log in the application program by using account information used by the second terminal for logging in the application program currently;
and after receiving a login permission instruction sent by the user based on the inquiry information and fed back by the second terminal, further requesting to obtain account information uploaded by the second terminal and utilized by the current login application program, and taking the account information as available target account information corresponding to the first terminal.
5. The method of claim 1, wherein the step of generating the device identifier association information comprises:
when detecting that both the first terminal and the second terminal have historical login records aiming at the account information, respectively sending binding requests to the first terminal and the second terminal so that both the first terminal and the second terminal output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and associating the first device identifier with the second device identifier to generate the device identifier association information after receiving a binding permission instruction sent by the respective user based on the corresponding inquiry information.
6. The method of claim 1, wherein the step of generating the device identifier association information comprises:
receiving space coordinates of positions where the first terminal and the second terminal are located;
sending binding requests to the first terminal and the second terminal corresponding to the two spatial coordinates respectively, so that the first terminal and the second terminal both output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and associating the first device identifier with the second device identifier to generate the device identifier association information after receiving a binding permission instruction sent by the respective user based on the corresponding inquiry information.
7. The method according to claim 1, wherein the device identifier association information is binding relationship information of the first device identifier uploaded by the second terminal and a second device identifier associated with the first device identifier;
wherein the process of generating the device identifier association information by the second terminal includes:
acquiring the first equipment identifier through a USB connecting line, and associating the second equipment identifier with the first equipment identifier to generate equipment identifier association information;
or,
acquiring the first device identifier by using a device discovery protocol of a local area network, and associating the second device identifier with the first device identifier to generate device identifier association information;
or,
and acquiring the first equipment identifier which is manually input by a user and is displayed in clear text by the first terminal, and associating the second equipment identifier with the first equipment identifier to generate equipment identifier association information.
8. The method of claim 7, wherein the second terminal obtains the first device identifier using a device discovery protocol of a local area network, comprising:
deploying software on the first terminal and the second terminal, so that the first device identifier is transmitted to the second terminal through the software, and then the first device identifier is received;
or,
converting an IP address of the first terminal into a MAC address using an ARP protocol (address resolution protocol);
determining the converted MAC address as the first device identifier.
9. An apparatus for logging in across terminal accounts, which is applied to a server, the apparatus comprising:
a login request receiving unit, configured to receive a login request of a first terminal, where the login request is a request that is generated by the first terminal after responding to a start instruction of an application and carries a first device identifier of the first terminal;
an equipment identifier association information obtaining unit, configured to obtain equipment identifier association information corresponding to the first equipment identifier, where the equipment identifier association information is association relationship information between the first equipment identifier and a second equipment identifier associated with the first equipment identifier;
an available target account information determining unit, configured to determine available target account information corresponding to the first terminal, where the available target account information is account information used by a second terminal having the second device identifier to log in the application program;
and the available target account information feedback unit is used for feeding back the available target account information to the first terminal so that the first terminal can log in the application program by using the available target account information.
10. The apparatus of claim 9, wherein the available target account information determining unit comprises:
an inquiry information sending subunit, configured to send inquiry information to a second terminal having the second device identifier, the inquiry information inquiring whether the first terminal allows the first terminal to log in the application program using account information uploaded by the second terminal and used for logging in the application program by itself;
and the available target account information determining subunit is configured to, after receiving a login permission instruction sent by the user based on the query information and fed back by the second terminal, use the account information as available target account information corresponding to the first terminal.
11. The apparatus according to claim 9, wherein the available target account information determining unit is specifically configured to:
and directly taking account information uploaded by the second terminal with the second equipment identifier and utilized by logging in the application program as available target account information corresponding to the first terminal.
12. The apparatus of claim 9, wherein the available target account information determining unit comprises:
an inquiry information sending subunit, configured to send inquiry information to a second terminal having the second device identifier, the inquiry information inquiring whether the first terminal is allowed to log in the application program by using account information used by the second terminal itself to currently log in the application program;
and the available target account information determining subunit is configured to, after receiving a login permission instruction sent by the user based on the query information and fed back by the second terminal, further request to obtain account information used by the current login application program uploaded by the second terminal, and use the account information as available target account information corresponding to the first terminal.
13. The apparatus according to claim 9, wherein the device identifier association information is generated by a device identifier association information generation unit;
wherein the device identifier association information generation unit includes:
a binding request sending subunit, configured to, when it is detected that both the first terminal and the second terminal have a history login record for the account information, send a binding request to the first terminal and the second terminal, respectively, so that both the first terminal and the second terminal output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and the device identifier association information generation subunit is configured to, after receiving a binding permission instruction issued by a respective user based on the corresponding inquiry information, associate the first device identifier with the second device identifier to generate the device identifier association information.
14. The apparatus according to claim 9, wherein the device identifier association information is generated by a device identifier association information generation unit;
wherein the device identifier association information generation unit includes:
the space coordinate receiving subunit is used for receiving space coordinates of positions where the first terminal and the second terminal are located;
a binding request sending subunit, configured to send a binding request to the first terminal and the second terminal corresponding to two spatial coordinates, respectively, so that the first terminal and the second terminal both output inquiry information for inquiring whether respective users allow the first terminal and the second terminal to be bound;
and the device identifier association information generation subunit is configured to, after receiving a binding permission instruction issued by a respective user based on the corresponding inquiry information, associate the first device identifier with the second device identifier to generate the device identifier association information.
15. The apparatus according to claim 9, wherein the device identifier association information is binding relationship information between the first device identifier uploaded by the second terminal and a second device identifier associated with the first device identifier;
wherein the device identifier association information is generated by a device identifier association information generation unit of the second terminal;
wherein the device identifier association information generation unit includes:
a first obtaining subunit, configured to obtain the first device identifier through a USB connection line; a first association information generation subunit, configured to associate the second device identifier with the first device identifier, and generate device identifier association information;
or,
the device identifier association information generation unit includes:
a second obtaining subunit, configured to obtain the first device identifier using a device discovery protocol of a local area network; a second association information generation subunit, configured to associate the second device identifier with the first device identifier, and generate device identifier association information;
or,
the device identifier association information generation unit includes:
the third acquisition subunit is used for acquiring the first equipment identifier which is manually input by a user and is displayed in the clear text of the first terminal; and the third association information generation subunit is configured to associate the second device identifier with the first device identifier, and generate device identifier association information.
16. The apparatus of claim 15, wherein the second obtaining subunit comprises:
a software deployment module for deploying software on itself and the first terminal such that the first device identifier is transmitted to the second terminal by the software;
a first device identifier receiving module for receiving the first device identifier;
or,
the second acquisition subunit includes:
a conversion module for converting an IP address of the first terminal into an MAC address using an ARP protocol (address resolution protocol);
a first device identifier determining module for determining the converted MAC address as the first device identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410797971.3A CN104486747A (en) | 2014-12-19 | 2014-12-19 | Method and device for cross-terminal account login |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410797971.3A CN104486747A (en) | 2014-12-19 | 2014-12-19 | Method and device for cross-terminal account login |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104486747A true CN104486747A (en) | 2015-04-01 |
Family
ID=52761237
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410797971.3A Pending CN104486747A (en) | 2014-12-19 | 2014-12-19 | Method and device for cross-terminal account login |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104486747A (en) |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105100071A (en) * | 2015-06-30 | 2015-11-25 | 华为技术有限公司 | Login method, device and system |
| CN105187511A (en) * | 2015-08-13 | 2015-12-23 | 网易传媒科技（北京）有限公司 | Method and device for logging applications on multiple terminals |
| CN105429943A (en) * | 2015-10-28 | 2016-03-23 | 腾讯科技（深圳）有限公司 | Information processing method and terminal thereof |
| CN105429947A (en) * | 2015-10-28 | 2016-03-23 | 腾讯科技（深圳）有限公司 | Information processing method and system, terminal and server |
| CN105871903A (en) * | 2016-05-25 | 2016-08-17 | 努比亚技术有限公司 | Information security control method and system as well as mobile terminal |
| CN106130881A (en) * | 2016-07-07 | 2016-11-16 | 腾讯科技（深圳）有限公司 | A kind of account number login method and device |
| WO2017000830A1 (en) * | 2015-07-02 | 2017-01-05 | 阿里巴巴集团控股有限公司 | Cross-terminal login-free method and device |
| CN106453372A (en) * | 2016-11-03 | 2017-02-22 | 努比亚技术有限公司 | Terminal, server and account login method |
| CN106899574A (en) * | 2017-01-13 | 2017-06-27 | 努比亚技术有限公司 | Application program login method and terminal |
| CN107454040A (en) * | 2016-05-30 | 2017-12-08 | 腾讯科技（深圳）有限公司 | The login method and device of application |
| CN107483503A (en) * | 2017-09-28 | 2017-12-15 | 深圳市口袋网络科技有限公司 | A kind of application program login method, apparatus and system |
| CN108011887A (en) * | 2017-12-14 | 2018-05-08 | 维沃移动通信有限公司 | A kind of account management method and equipment |
| CN108768956A (en) * | 2018-05-04 | 2018-11-06 | 北京信安世纪科技股份有限公司 | A kind of application program login method and device |
| CN108965255A (en) * | 2018-06-13 | 2018-12-07 | 中国联合网络通信集团有限公司 | Multiple terminals account management method, platform, equipment and computer readable storage medium |
| CN108989328A (en) * | 2018-08-07 | 2018-12-11 | 北京优酷科技有限公司 | A kind of method, client and server for sharing account |
| CN109213530A (en) * | 2018-08-13 | 2019-01-15 | 百富计算机技术（深圳）有限公司 | A kind of communication connecting method based on USB, mobile terminal and storage medium |
| CN109460647A (en) * | 2018-11-12 | 2019-03-12 | 商客通尚景信息技术江苏有限公司 | A kind of method that more equipment safeties log in |
| CN109508527A (en) * | 2018-11-16 | 2019-03-22 | 聚好看科技股份有限公司 | A kind of method that realizing that different terminals account is unified, terminal and server |
| CN111460356A (en) * | 2020-04-23 | 2020-07-28 | 北京信安世纪科技股份有限公司 | Automatic login method, device, medium and equipment |
| CN111597540A (en) * | 2020-04-28 | 2020-08-28 | 维沃移动通信有限公司 | Login method of application program, electronic device and readable storage medium |
| WO2020191539A1 (en) * | 2019-03-22 | 2020-10-01 | 华为技术有限公司 | Communication method, apparatus and system |
| CN111756669A (en) * | 2019-03-26 | 2020-10-09 | 阿里巴巴集团控股有限公司 | Login request processing method, mobile device and intelligent hardware device |
| CN112448928A (en) * | 2019-08-31 | 2021-03-05 | 华为技术有限公司 | Credential obtaining method and device |
| CN114258006A (en) * | 2020-09-23 | 2022-03-29 | 华为技术有限公司 | Method, device and system for acquiring credential |
| CN114500091A (en) * | 2022-02-23 | 2022-05-13 | 九恒星(武汉)信息技术有限公司 | Login method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685025A (en) * | 2011-03-17 | 2012-09-19 | 深圳市同洲软件有限公司 | Multi-terminal service switching method, terminal and system |
| CN103118032A (en) * | 2013-03-01 | 2013-05-22 | 北京奇艺世纪科技有限公司 | Method, terminals and server for synchronization of terminal login accounts |
| CN103248489A (en) * | 2013-05-17 | 2013-08-14 | 刘琦 | Method for realizing client login through intelligent terminal, server and intelligent terminal |
| CN103414740A (en) * | 2013-07-01 | 2013-11-27 | 深圳Tcl新技术有限公司 | Private cloud account configuration method and device |
| CN103457951A (en) * | 2013-09-02 | 2013-12-18 | 小米科技有限责任公司 | Method and device for allowing multiple terminals to login to server |
| US20140089416A1 (en) * | 2012-08-28 | 2014-03-27 | Tencent Technology (Shenzhen) Company Limited | Systems and methods for sharing data among multiple end user devices |
| CN103763327A (en) * | 2014-01-28 | 2014-04-30 | 宇龙计算机通信科技(深圳)有限公司 | Account number logging-in method and system |
| CN104158883A (en) * | 2014-08-20 | 2014-11-19 | 乐视网信息技术（北京）股份有限公司 | Method, device, equipment and system for carrying out user login through cross-terminal equipment |
-
2014
- 2014-12-19 CN CN201410797971.3A patent/CN104486747A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685025A (en) * | 2011-03-17 | 2012-09-19 | 深圳市同洲软件有限公司 | Multi-terminal service switching method, terminal and system |
| US20140089416A1 (en) * | 2012-08-28 | 2014-03-27 | Tencent Technology (Shenzhen) Company Limited | Systems and methods for sharing data among multiple end user devices |
| CN103118032A (en) * | 2013-03-01 | 2013-05-22 | 北京奇艺世纪科技有限公司 | Method, terminals and server for synchronization of terminal login accounts |
| CN103248489A (en) * | 2013-05-17 | 2013-08-14 | 刘琦 | Method for realizing client login through intelligent terminal, server and intelligent terminal |
| CN103414740A (en) * | 2013-07-01 | 2013-11-27 | 深圳Tcl新技术有限公司 | Private cloud account configuration method and device |
| CN103457951A (en) * | 2013-09-02 | 2013-12-18 | 小米科技有限责任公司 | Method and device for allowing multiple terminals to login to server |
| CN103763327A (en) * | 2014-01-28 | 2014-04-30 | 宇龙计算机通信科技(深圳)有限公司 | Account number logging-in method and system |
| CN104158883A (en) * | 2014-08-20 | 2014-11-19 | 乐视网信息技术（北京）股份有限公司 | Method, device, equipment and system for carrying out user login through cross-terminal equipment |
Cited By (47)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105100071A (en) * | 2015-06-30 | 2015-11-25 | 华为技术有限公司 | Login method, device and system |
| US10742640B2 (en) | 2015-07-02 | 2020-08-11 | Alibaba Group Holding Limited | Identification of a related computing device for automatic account login |
| JP2018523229A (en) * | 2015-07-02 | 2018-08-16 | アリババ グループ ホウルディング リミテッド | Login-free method and apparatus between terminals |
| CN106330844B (en) * | 2015-07-02 | 2020-08-04 | 阿里巴巴集团控股有限公司 | A cross-terminal free login method and device |
| US11025617B2 (en) | 2015-07-02 | 2021-06-01 | Advanced New Technologies Co., Ltd. | Identification of a related computing device for automatic account login |
| EP3319293A4 (en) * | 2015-07-02 | 2018-07-04 | Alibaba Group Holding Limited | Cross-terminal login-free method and device |
| WO2017000830A1 (en) * | 2015-07-02 | 2017-01-05 | 阿里巴巴集团控股有限公司 | Cross-terminal login-free method and device |
| CN106330844A (en) * | 2015-07-02 | 2017-01-11 | 阿里巴巴集团控股有限公司 | A cross-terminal free login method and device |
| US11349830B2 (en) | 2015-07-02 | 2022-05-31 | Advanced New Technologies Co., Ltd. | Identification of a related computing device for automatic account login |
| CN105187511B (en) * | 2015-08-13 | 2019-03-15 | 网易传媒科技（北京）有限公司 | It is a kind of to apply the method and apparatus logged in over multiple terminals |
| CN105187511A (en) * | 2015-08-13 | 2015-12-23 | 网易传媒科技（北京）有限公司 | Method and device for logging applications on multiple terminals |
| CN105429943A (en) * | 2015-10-28 | 2016-03-23 | 腾讯科技（深圳）有限公司 | Information processing method and terminal thereof |
| CN105429947A (en) * | 2015-10-28 | 2016-03-23 | 腾讯科技（深圳）有限公司 | Information processing method and system, terminal and server |
| CN105429947B (en) * | 2015-10-28 | 2020-03-17 | 腾讯科技（深圳）有限公司 | Information processing method, system, terminal and server |
| CN105871903A (en) * | 2016-05-25 | 2016-08-17 | 努比亚技术有限公司 | Information security control method and system as well as mobile terminal |
| CN107454040A (en) * | 2016-05-30 | 2017-12-08 | 腾讯科技（深圳）有限公司 | The login method and device of application |
| CN107454040B (en) * | 2016-05-30 | 2020-02-28 | 腾讯科技（深圳）有限公司 | Application login method and device |
| US10911430B2 (en) | 2016-07-07 | 2021-02-02 | Tencent Technology (Shenzhen) Company Limited | Account login connection method and apparatus, and storage medium |
| CN106130881A (en) * | 2016-07-07 | 2016-11-16 | 腾讯科技（深圳）有限公司 | A kind of account number login method and device |
| CN106453372B (en) * | 2016-11-03 | 2019-10-25 | 努比亚技术有限公司 | A kind of terminal, server and account logon method |
| CN106453372A (en) * | 2016-11-03 | 2017-02-22 | 努比亚技术有限公司 | Terminal, server and account login method |
| CN106899574A (en) * | 2017-01-13 | 2017-06-27 | 努比亚技术有限公司 | Application program login method and terminal |
| CN107483503A (en) * | 2017-09-28 | 2017-12-15 | 深圳市口袋网络科技有限公司 | A kind of application program login method, apparatus and system |
| CN108011887A (en) * | 2017-12-14 | 2018-05-08 | 维沃移动通信有限公司 | A kind of account management method and equipment |
| CN108768956A (en) * | 2018-05-04 | 2018-11-06 | 北京信安世纪科技股份有限公司 | A kind of application program login method and device |
| CN108965255A (en) * | 2018-06-13 | 2018-12-07 | 中国联合网络通信集团有限公司 | Multiple terminals account management method, platform, equipment and computer readable storage medium |
| CN108965255B (en) * | 2018-06-13 | 2021-06-29 | 中国联合网络通信集团有限公司 | Multi-terminal account management method, platform, device and computer-readable storage medium |
| CN108989328A (en) * | 2018-08-07 | 2018-12-11 | 北京优酷科技有限公司 | A kind of method, client and server for sharing account |
| CN109213530B (en) * | 2018-08-13 | 2021-08-10 | 百富计算机技术（深圳）有限公司 | USB-based communication connection method, mobile terminal and storage medium |
| CN109213530A (en) * | 2018-08-13 | 2019-01-15 | 百富计算机技术（深圳）有限公司 | A kind of communication connecting method based on USB, mobile terminal and storage medium |
| CN109460647A (en) * | 2018-11-12 | 2019-03-12 | 商客通尚景信息技术江苏有限公司 | A kind of method that more equipment safeties log in |
| CN109508527A (en) * | 2018-11-16 | 2019-03-22 | 聚好看科技股份有限公司 | A kind of method that realizing that different terminals account is unified, terminal and server |
| WO2020191539A1 (en) * | 2019-03-22 | 2020-10-01 | 华为技术有限公司 | Communication method, apparatus and system |
| US11601517B2 (en) | 2019-03-22 | 2023-03-07 | Huawei Technologies Co., Ltd. | Communications method, and communications apparatus and system |
| CN113302878A (en) * | 2019-03-22 | 2021-08-24 | 华为技术有限公司 | Communication method, device and system |
| CN113302878B (en) * | 2019-03-22 | 2022-08-09 | 华为技术有限公司 | Communication method, device and system |
| CN111756669A (en) * | 2019-03-26 | 2020-10-09 | 阿里巴巴集团控股有限公司 | Login request processing method, mobile device and intelligent hardware device |
| CN111756669B (en) * | 2019-03-26 | 2023-06-16 | 阿里巴巴集团控股有限公司 | Login request processing method, mobile device and intelligent hardware device |
| CN112448928A (en) * | 2019-08-31 | 2021-03-05 | 华为技术有限公司 | Credential obtaining method and device |
| CN112448928B (en) * | 2019-08-31 | 2022-04-05 | 华为技术有限公司 | A method and device for obtaining credentials |
| CN111460356A (en) * | 2020-04-23 | 2020-07-28 | 北京信安世纪科技股份有限公司 | Automatic login method, device, medium and equipment |
| CN111460356B (en) * | 2020-04-23 | 2024-03-12 | 北京信安世纪科技股份有限公司 | Automatic login method, device, medium and equipment |
| CN111597540B (en) * | 2020-04-28 | 2022-01-28 | 维沃移动通信有限公司 | Login method of application program, electronic device and readable storage medium |
| CN111597540A (en) * | 2020-04-28 | 2020-08-28 | 维沃移动通信有限公司 | Login method of application program, electronic device and readable storage medium |
| CN114258006A (en) * | 2020-09-23 | 2022-03-29 | 华为技术有限公司 | Method, device and system for acquiring credential |
| CN114258006B (en) * | 2020-09-23 | 2023-07-18 | 华为技术有限公司 | Method, device and system for acquiring credentials |
| CN114500091A (en) * | 2022-02-23 | 2022-05-13 | 九恒星(武汉)信息技术有限公司 | Login method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104486747A (en) | Method and device for cross-terminal account login | |
| CN108964994B (en) | Replacement method of intelligent household equipment | |
| JP6280641B2 (en) | Account login method, device and system | |
| US10911430B2 (en) | Account login connection method and apparatus, and storage medium | |
| CN110602087A (en) | Intelligent screen projection method and device, intelligent terminal and server | |
| KR102015236B1 (en) | A method, terminal device, and server system for connecting communication devices | |
| WO2017024842A1 (en) | Internet access authentication method, client, computer storage medium | |
| CN102387156B (en) | Equipment logging treatment method, device and system | |
| US20190014532A1 (en) | Adss enabled global roaming system | |
| CN103298072A (en) | Method, system and mobile communication terminal for automatically connecting to WiFi access point | |
| CN105188013A (en) | Network hotspot sharing method, device and system | |
| JP6071947B2 (en) | Terminal for position information service, wireless signal detection device and server | |
| CN104853449B (en) | A kind of network-building method of wireless sound box, apparatus and system | |
| CN107124337A (en) | Equipment configuration method, device, system and centralized control terminal | |
| CN112684995B (en) | Cross-screen input method and device | |
| CN118413322B (en) | Password resetting method, device, system, terminal, management device and medium | |
| CN104618818B (en) | A kind of TV homepage configuration method and device | |
| CN109040331A (en) | The processing method of electronic business card, calculates equipment and storage medium at device | |
| CN109981558B (en) | Authentication method, equipment and system of intelligent household equipment | |
| CN101035126B (en) | Method for authorizing control of device and device using same | |
| CN105635059A (en) | WLAN access authentication method, related equipment, and system | |
| WO2024087384A1 (en) | Bluetooth connection establishment method, electronic device and computer storage medium | |
| CN106470281A (en) | A kind of crosstalk reminding method and device | |
| CN115665091A (en) | Automatic addressing method, system and storage medium | |
| CN114040403A (en) | Equipment synchronization method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150401 |
|
| RJ01 | Rejection of invention patent application after publication |