WO2015180589A1 - 终端设备的登录方法、终端设备和云端服务器 - Google Patents

终端设备的登录方法、终端设备和云端服务器 Download PDF

Info

Publication number
WO2015180589A1
WO2015180589A1 PCT/CN2015/079579 CN2015079579W WO2015180589A1 WO 2015180589 A1 WO2015180589 A1 WO 2015180589A1 CN 2015079579 W CN2015079579 W CN 2015079579W WO 2015180589 A1 WO2015180589 A1 WO 2015180589A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
cloud server
group
shared
device group
Prior art date
Application number
PCT/CN2015/079579
Other languages
English (en)
French (fr)
Inventor
彭卫
Original Assignee
阿里巴巴集团控股有限公司
彭卫
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 彭卫 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2015180589A1 publication Critical patent/WO2015180589A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present invention relates to the technical field of a terminal device logging in to a cloud server, and more particularly to a method for logging in a terminal device, a terminal device, and a cloud server.
  • terminal devices have network functions, such as smart phones, tablet computers (PADs), notebook computers, desktop computers, smart TVs, set-top boxes, routers and other devices.
  • PDAs tablet computers
  • notebook computers notebook computers
  • desktop computers smart TVs
  • smart TVs set-top boxes
  • routers routers and other devices.
  • the login information can be transmitted through the NFC function between devices. That is, after a device logs in, the device transmits the login information to another device through NFC communication. So that another device can also log in using this login information.
  • this process is a one-time operation. After the login is completed, the devices cannot continue to be associated with each other. If the next login is required, the above process needs to be repeated. Therefore, it is necessary to propose an improved technical means to solve the above problem.
  • the main purpose of the present application is to provide a method for logging in a terminal device, a terminal device, and a cloud server, so as to overcome the problem that a plurality of terminal devices that exist in the prior art need to input login information separately to reduce efficiency.
  • the embodiment of the present application provides a method for logging in a terminal device, which includes: a cloud server adds a plurality of terminal devices having a connection relationship with a cloud server to a pre-established shared device group; and the cloud server generates Authentication information is sent to the plurality of terminals
  • the cloud server of the device receives the login request message sent by the first terminal device of the shared device group, and verifies whether the first terminal device is the device of the shared device group according to the login request message, and if the verification succeeds, The first terminal device sends a login success message.
  • the method for logging in to the terminal device further includes: the first terminal device joins the shared device group pre-established by the cloud server, and the second terminal device in the shared device group successfully logs in to the cloud server.
  • the first terminal device sends a login request message to the cloud server to request the cloud server to verify that the first terminal device is a device of the shared device group; the first terminal device receives the cloud server The login success message sent.
  • the embodiment of the present application further provides a cloud server, including: a shared device group maintenance module, configured to add a plurality of terminal devices having a connection relationship with the cloud server to a pre-established shared device group; and a receiving module, configured to receive the The login request information sent by the first terminal device of the shared device group; the login management module is configured to verify, according to the login request information, whether the first terminal device is a device of the shared device group, and if the verification is passed, the permission is The first terminal device logs in to the cloud server.
  • a shared device group maintenance module configured to add a plurality of terminal devices having a connection relationship with the cloud server to a pre-established shared device group
  • a receiving module configured to receive the The login request information sent by the first terminal device of the shared device group
  • the login management module is configured to verify, according to the login request information, whether the first terminal device is a device of the shared device group, and if the verification is passed, the permission is The first terminal device logs in to the cloud server.
  • the embodiment of the present application further provides a terminal device, including: a joining module, configured to join a shared device group pre-established by the cloud server, and a sending module, configured to send a login request message to the cloud server to request the cloud
  • the server verifies that the terminal device is a device of the shared device group, and the receiving module is configured to receive a login success message sent by the cloud server.
  • FIG. 1 is a flowchart showing a login method of a terminal device according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of an application scenario according to an embodiment of the present application.
  • FIG. 3 is a flowchart of a terminal device joining a shared device group according to an embodiment of the present application
  • FIG. 4 is a structural block diagram of a cloud server according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a login method of a terminal device according to another embodiment of the present application.
  • FIG. 6 is a flowchart of device login processing of the same shared device group according to an embodiment of the present application.
  • FIG. 7 is a structural block diagram of a terminal device according to an embodiment of the present application.
  • the main idea of the present application is to establish a cloud-based shared device group through NFC function interaction between multiple terminal devices (including smart phones, tablet computers, smart TVs, set-top boxes, etc.), and log in to the cloud server in any device in the device group. After that, other devices in the group share the login status and can log in to the cloud server only after being authenticated, without providing login information such as a user name and password, thereby realizing the technology of automatically logging in to other devices of the same group after a device is logged in. effect.
  • FIG. 1 is a flowchart showing a login method of a terminal device according to an embodiment of the present application. As shown in Figure 1, the method includes:
  • step S102 the cloud server joins a plurality of terminal devices having a connection relationship with the cloud server to a pre-established shared device group.
  • the shared device group is a virtual device group, and multiple terminal devices in the device group share the login status.
  • other terminal devices in the group share the login status of the logged-in terminal device, and thus Other terminal devices can log in to the cloud server without having to provide login information.
  • the shared device group is responsible for establishing and managing by the cloud server, and is responsible for maintaining the description information of the shared device group, where the description information includes: group identification information (GID) of the shared device group, The identification information (ID) of each terminal device included in the shared device group.
  • the identification information of the terminal device may be a Universally Unique Identifier (UUID) or a Media Access Control (Media Access Control).
  • MAC An address or an IP address that uniquely identifies the device. This application does not limit this.
  • the cloud server establishes a shared device group, the shared device group is assigned a globally unique group identification information (ID).
  • the plurality of terminal devices are provided with a network connection function, and the cloud server establishes a connection with a plurality of terminal devices by using a wireless or a wired manner.
  • the cloud server uses a socket socket (using TCP, RUDP, etc.) to establish a long connection channel with the terminal device, so that the cloud server communicates with the terminal device through the channel, and transmits data information between each other.
  • the plurality of terminal devices are provided with short-range communication functions, including but not limited to: smart phones, tablet computers (PADs), notebook computers, desktop computers, smart TVs, set-top boxes, routers, and the like.
  • the short-range communication function may be a wireless technology such as near field communication (NFC) or contactless radio frequency identification (RFID) or Bluetooth, which is not limited in this application.
  • NFC near field communication
  • RFID contactless radio frequency identification
  • Bluetooth Bluetooth
  • the NFC function of the device is no longer required to communicate, that is, the NFC function of the device is used only in the process of establishing a shared device group based on the cloud server.
  • the device can be logged out or quit the device group. After the device is logged off, the device group is logged off together, and after the device quits, the device group still exists and is not logged out.
  • Device A notifies the user whether to log out the other devices in the device group.
  • the device A notifies the cloud server to clear the login tokens of the device group; the cloud server notifies other devices to clear the login state through the long connection channel;
  • the steps for the device to exit the device group are as follows:
  • the device logs out of the login state and chooses not to log off other devices in the device group. At this time, the device automatically Exit the device group;
  • the cloud server receives the login request message sent by the first terminal device of the shared device group, and verifies whether the first terminal device is the device of the shared device group according to the login request message, if The verification succeeds by sending a login success message to the first terminal device.
  • a terminal device (second terminal device) in the shared device group has been logged into the cloud server.
  • the second terminal device can log in to the cloud server by using a general login mode. For example, the second terminal device enters a login information such as a user name and a password on the user login interface of the cloud server to initiate login, and the cloud server verifies the second terminal device to log in after the login information is verified.
  • the cloud server After the second terminal device of the shared device group successfully logs in to the cloud server, the cloud server generates an authentication key (key) and stores it in the description information of the shared device group, where the authentication key may be pre-configured or random. Any string generated is not limited in this application. Then, the cloud server sends the generated authentication key to each device in the group through the long connection channel. Obviously, the first terminal device of the shared device group also receives the authentication key. Then, the first terminal device performs encryption calculation on the authentication key and the identification information of the first terminal device to generate identity verification information by using a preset encryption algorithm (for example, MD5, RC4, DES, etc.), and sends the identity verification information to the cloud server, including the identity verification.
  • the login request information includes information to request the cloud server to verify the identity of the first terminal device according to the authentication information.
  • the cloud server After receiving the login request message sent by the first terminal device of the shared device group, the cloud server verifies the identity of the first terminal device according to the identity verification information carried therein. Specifically, the verification process includes: the cloud server obtains the authentication key and the identification information of the first terminal device in the description information of the shared device group, and uses the same encryption algorithm as the encryption algorithm configured in the first terminal device (for example, MD5, RC4, DES, etc.) encrypts the obtained authentication key and the identification information of the first terminal device, and compares it with the authentication information. If the same, the authentication is performed, allowing the first terminal device to log in to the cloud server, and the cloud server The first terminal device sends a login success message.
  • the cloud server obtains the authentication key and the identification information of the first terminal device in the description information of the shared device group, and uses the same encryption algorithm as the encryption algorithm configured in the first terminal device (for example, MD5, RC4, DES, etc.) encrypts the obtained authentication key and the identification information of the first terminal device, and
  • the shared login status achieves the effect of logging in to the cloud server without inputting login information.
  • an NFC-enabled device such as a mobile phone 204, a smart TV 206, and a router 208 is included in a home user.
  • the cloud server 202 and the terminal devices establish a long connection channel, and the terminal devices join the cloud server 202. Shared device group.
  • the IP address of the mobile phone 204 is "192.168.0.1”
  • the IP address of the smart TV 206 is "192.168.0.2”
  • the IP address of the router 208 is "192.168.0.3”
  • the cloud server 202 assigns the group identifier to the shared device group.
  • the information is G-1, and then the cloud server 202 records the above information in the description information of the group.
  • the mobile phone 204 When the mobile phone 204 logs in to the cloud server 202, as the first device in the group, the mobile phone 204 successfully logs in to the cloud server 202 after inputting information such as the user name and the login password on the login interface. Then, the cloud server 202 randomly generates an authentication key (token) stored locally, and then sends the authentication token to the other devices smart TV 206 and router 208 in the group through the long connection channel. After receiving the authentication token, the smart TV 206 encrypts the authentication token and the IP address "192.168.0.2" of the smart TV 206 using the MD5 algorithm, and uses the obtained hash value as the authentication information, and sends the authentication to the cloud server 202, including the identity verification. Login request information for information.
  • an authentication key token
  • the cloud server 202 After receiving the login request information sent by the smart TV 206, the cloud server 202 encrypts the locally stored authentication token and the IP address "192.168.0.2" of the smart TV 206 using the same MD5 algorithm and obtains a hash value, if the hash The column value coincides with the hash value in the login request information, and it is confirmed that the smart TV 206 and the mobile phone 204 are devices of the same shared device group, that is, the identity of the smart TV 206 is verified, and the smart TV 206 is allowed to log in to the cloud server 202. In this way, the smart TV 206 can access the cloud server 202 without inputting a username and a login password. Similarly, the router 208 logs in to the cloud server 202 by using the same login mode, and details are not described herein.
  • the IP address of the terminal device is used as the identification information, but the application is not limited thereto, and the UUID code or MAC address of the terminal device may be used as the identification information. Narration.
  • FIG. 3 is a flowchart of a device login process of a shared device group according to an embodiment of the present application.
  • devices A and B join the same shared device group, and devices A and B pass through the cloud server.
  • Established long connection channel transfer data As shown in Figure 3, the following steps are included:
  • step S302 the device A inputs a username and password on the login interface of the cloud server, and initiates login to the cloud server.
  • step S304 after the cloud server verifies the user name and password input through the device A, an authentication key is generated and stored in the description information of the cloud device group together with the user name.
  • step S306 the cloud server sends the login information including the authentication token to the other device (for example, device B) of the shared device group where the device A is located through the long connection channel.
  • step S308 device B receives the login information through the long connection channel, and then uses an encryption algorithm (eg, MD5, RC4, DES, etc.) to encrypt the authentication token and device B's globally unique identifier (eg, UUID or MAC address) to generate identity verification. Information and send the verification information to the cloud server for authentication.
  • an encryption algorithm eg, MD5, RC4, DES, etc.
  • step S310 the cloud server decrypts by the same encryption algorithm (for example, MD5, RC4, DES, etc.), confirms that the login request of device B is legal, and sends a login success notification to device B.
  • the same encryption algorithm for example, MD5, RC4, DES, etc.
  • the cloud server includes at least: a shared device group maintenance module 402, a receiving module 404, a login management module 406, and a shared device group establishing module 408.
  • the channel establishing module 410, the key generating module 412, and the sending module 414, the structure and function of the cloud server are described in detail below.
  • a shared device group maintenance module 402 configured to add a plurality of terminal devices that have a connection relationship with the cloud server to a pre-established shared device group;
  • the receiving module 404 is configured to receive login request information sent by the first terminal device of the shared device group. Specifically, the login request information received by the receiving module 404 includes: the authentication key and the identifier information of the first terminal device.
  • the login management module 406 is configured to verify, according to the login request information, whether the first terminal device is a device of the shared device group, and if the verification is passed, the first terminal device is allowed to log in to the cloud server. Specifically, the login management module 406 verifies whether the first terminal device is a device of the shared device group according to the authentication key and the identifier information of the first terminal device.
  • the shared device group establishing module 408 is configured to establish the shared device group.
  • the shared device group maintenance module 402 is further configured to maintain description information of the shared device group, where the description packet is The group identification information of the shared device group and the identification information of each terminal device included in the shared device group.
  • the channel establishing module 410 is configured to establish a connection channel with the plurality of terminal devices.
  • the receiving module 404 receives the login information sent by the second terminal device of the shared device group through the connection channel.
  • the login management module 406 is further configured to verify that the second terminal device is logged in to the cloud server by using the login information.
  • the key generation module 412 is configured to generate an authentication key.
  • the sending module 414 is configured to send the authentication key to the first terminal device by using the connection channel.
  • a method for logging in a terminal device As shown in FIG. 5, the method includes:
  • step S502 the first terminal device joins the shared device group pre-established by the cloud server, and the second terminal device in the shared device group successfully logs in to the cloud server;
  • the first terminal device and the second terminal device are provided with a short-range communication function (for example, NFC), and the first terminal device and the second terminal device mutually negotiate through a short-range communication function, and join the shared device. group.
  • a short-range communication function for example, NFC
  • step S602 device A obtains the shared device group ID in which it is located, and device B acquires the shared device group ID in which it is located.
  • the device group to which the device resides is the device group that the device has joined. If the device has not been added to the device group, the device group ID obtained is empty or the procedure is omitted.
  • step S604 device A is close to device B, and device A transmits the device group ID to device B through the NFC function.
  • step S606 it is determined whether the device group ID of the device A is valid. If the device group ID of the device A is valid, step S608 is performed, and if not, step S614 is performed.
  • the group ID cannot be obtained, or the device has been added to the device group but the group has been revoked. In these cases, the device group ID is invalid.
  • step S608 it is determined whether the device group ID of the device B is valid. If the device group ID of the device B is valid, step S610 is performed, and if not, step S612 is performed.
  • step S610 the device group IDs of both the device A and the device B are valid.
  • the user may be prompted to select whether the device is the device in which the device A joins the device B or the device B joins the device in which the device A belongs. Or add a device to the same group as another device according to the preset rules.
  • the group in which device B joins device A is taken as an example for description.
  • Device B notifies the cloud server, and device B exits the original device group and joins the shared device group where A is located.
  • step S612 the device group ID of the device A is valid and the device group ID of the device B is invalid.
  • the device B notifies the cloud server to join the device group where A is located, and notifies that the device group that A has joined the A. .
  • step S614 it is determined whether the device group ID of the device B is valid. If the device group ID of the device B is valid, step S616 is performed, and if not, step S618 is performed.
  • step S616 the device group ID of the device A is invalid and the device group ID of the device B is valid.
  • the device B notifies the device A to join its own device group.
  • the device A After receiving the message, the device A notifies the cloud server that the device A Join the shared device group where device B is located.
  • step S618 the device group IDs of the device A and the device B are invalid.
  • the device B communicates with the cloud server, acquires a new shared device group ID, and joins the new device group to write the local device.
  • the storage is then transmitted to device A.
  • device A After receiving the device, device A notifies the cloud to join the shared device group where device B is located.
  • the two terminal devices join the same shared device group through NFC communication, including the above four cases.
  • the process of adding the two terminal devices to the same shared device group and the multiple devices joining the same shared device group are similar to the above, and are not described here.
  • the terminal device joins the shared device group it performs interactive communication through the short-range communication function. After that, the terminal devices in the group do not need to periodically connect and interact, that is, the terminal device only uses the short-range communication function to perform a process. Interactive communication.
  • the identification information of the terminal device group to which the terminal device is added is sent to the cloud server, and the cloud server stores the identification information of the terminal.
  • step S504 the first terminal device sends a login request message to the cloud server, to request the cloud server to verify that the first terminal device is a device of the shared device group;
  • the first terminal device receives the authentication key sent by the cloud server, and the login request message sent by the first terminal device to the cloud server includes: the authentication key and the Identification information of a terminal device.
  • the cloud server authenticates the identity of the first terminal according to the authentication key and the identifier information of the first terminal device. If the authentication succeeds, the cloud server is allowed to access the cloud server, so that the login success message is sent to the first terminal device.
  • step S506 the first terminal device receives the login success message sent by the cloud server.
  • the terminal device includes:
  • the module 702 is added to join the shared device group pre-established by the cloud server.
  • the terminal device has a short-range communication function (for example, NFC), and joins the shared device group through mutual negotiation with other terminal devices through the short-range communication function.
  • NFC short-range communication function
  • the sending module 704 is configured to send a login request message to the cloud server, to request the cloud server to verify that the terminal device is a device of the shared device group.
  • the sending module 704 is further configured to send the identifier information of the terminal device group to which the joining device is added to the cloud server.
  • the receiving module 706 is configured to receive a login success message sent by the cloud server.
  • the receiving module 706 is further configured to receive the authentication key sent by the cloud server, where the sending request message sent by the sending module 704 to the cloud server includes: the authentication key and the terminal Identification information of the device.
  • the technical solution of the present application when multiple devices are added to the shared device group of the cloud server, when one device in the group logs in, the other devices in the group are free to input the login information through the shared login state.
  • the effect of logging in to the cloud server is achieved. After a device is logged in, other devices in the same group can be automatically logged in, which simplifies the login operation and improves efficiency.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computing device includes one or more processors (CPUs), inputs/ Output interface, network interface, and memory.
  • processors CPUs
  • inputs/ Output interface outputs/Output interface
  • network interface network interface
  • memory memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

Abstract

本申请的主要目的在于提供一种终端设备的登录方法、终端设备和云端服务器，其中终端设备的登录方法包括：云端服务器将与其云端服务器具有连接关系的多个终端设备加入预先建立的共享设备组；所述云端服务器生成鉴权信息并发送至所述多个终端设备所述云端服务器接收所述共享设备组的第一终端设备发送的登录请求消息，根据所述登录请求消息验证所述第一终端设备是否为所述共享设备组的设备，若验证通过则向所述第一终端设备发送登录成功消息。通过本申请实施例，当共享设备组内一个设备登录后，组内的其他设备通过共享登录状态实现了登录云端服务器的效果。

Description

终端设备的登录方法、终端设备和云端服务器 技术领域
本申请涉及终端设备登录云端服务器的技术领域，尤其涉及一种终端设备的登录方法、终端设备和云端服务器。
背景技术
随着互联网技术的飞速发展，越来越多的终端设备具备网络功能，例如，智能手机、平板电脑(PAD)、笔记本电脑、台式机、智能电视、机顶盒、路由器等设备。
这些设备通过连接网络服务器使用其提供的服务，当每个设备登录服务器时，需要分别提供用户名和密码等登录信息。当多个终端设备需要连接并登录服务器时，这些多个设备需要分别在登录界面输入用户名和密码，以获取登录授权，这对多个设备来说在每次登录输入登录信息是十分耗时的，由此降低了效率。
如果设备具备NFC(Near Field Communication，近场通信)等近距离通信功能，则可以通过设备间的NFC功能传输登录信息，即一个设备登录后，该设备通过NFC通信把登录信息传送到另一个设备，使得另一个设备也能够使用该登录信息登录。但是，这个过程属于一次性操作，完成登录以后设备之间无法再继续关联，如果下次再登录则还需要重复上述过程，因此，有必要提出改进的技术手段解决上述问题。
发明内容
本申请的主要目的在于提供一种终端设备的登录方法、终端设备和云端服务器，以克服现有技术中存在的多个终端设备登录时需要分别输入登录信息导致降低效率的问题。
为解决上述问题，根据本申请实施例提供了一种终端设备的登录方法，其包括：云端服务器将与其云端服务器具有连接关系的多个终端设备加入预先建立的共享设备组；所述云端服务器生成鉴权信息并发送至所述多个终端 设备所述云端服务器接收所述共享设备组的第一终端设备发送的登录请求消息，根据所述登录请求消息验证所述第一终端设备是否为所述共享设备组的设备，若验证通过则向所述第一终端设备发送登录成功消息。
根据本申请实施例还提供一种终端设备的登录方法，其包括：第一终端设备加入云端服务器预先建立的共享设备组，并且所述共享设备组中的第二终端设备成功登录所述云端服务器；所述第一终端设备向所述云端服务器发送登录请求消息，以请求所述云端服务器验证所述第一终端设备为所述共享设备组的设备；所述第一终端设备接收所述云端服务器发送的登录成功消息。
根据本申请实施例还提供一种云端服务器，其包括：共享设备组维护模块，用于将与云端服务器具有连接关系的多个终端设备加入预先建立的共享设备组；接收模块，用于接收所述共享设备组的第一终端设备发送的登录请求信息；登录管理模块，用于根据所述登录请求信息验证所述第一终端设备是否为所述共享设备组的设备，若验证通过则允许所述第一终端设备登录所述云端服务器。
根据本申请实施例还提供一种终端设备，其包括：加入模块，用于加入云端服务器预先建立的共享设备组；发送模块，用于向所述云端服务器发送登录请求消息，以请求所述云端服务器验证所述终端设备为所述共享设备组的设备；接收模块，用于接收所述云端服务器发送的登录成功消息。
与现有技术相比，根据本申请的技术方案，通过将多个设备加入云端服务器的共享设备组，当组中的一个设备登录后，组内的其他设备通过共享登录状态在免输入登录信息的情况下实现了登录云端服务器的效果，实现了一个设备登录后同组的其他设备能够自动登录，从而简化了登录操作，提高了效率。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的 不当限定。在附图中：
图1示出根据本申请一个实施例的终端设备的登录方法的流程图；
图2示出根据本申请实施例的应用场景的示意图；
图3示出根据本申请实施例的终端设备加入共享设备组的流程图；
图4是根据本申请实施例的云端服务器的结构框图；
图5是根据本申请另一实施例的终端设备的登录方法的流程图；
图6是根据本申请实施例的同一共享设备组的设备登录处理的流程图；
图7是根据本申请实施例的终端设备的结构框图。
具体实施方式
本申请的主要思想在于，多个终端设备(包括智能手机、平板电脑、智能电视、机顶盒等)之间通过NFC功能交互建立一个基于云端的共享设备组，在设备组内任一个设备登录云端服务器后，组内其他设备共享登录状态并仅在通过身份验证后就能够登录该云端服务器，而不需要提供用户名和密码等登录信息，从而实现了一个设备登录后其他的同组设备自动登录的技术效果。
为使本申请的目的、技术方案和优点更加清楚，以下结合附图及具体实施例，对本申请作进一步地详细说明。
参考图1，图1示出根据本申请一个实施例的终端设备的登录方法的流程图。如图1所示，该方法包括：
在步骤S102中，云端服务器将与其具有连接关系的多个终端设备加入预先建立的共享设备组。
所述共享设备组是一个虚拟的设备组，设备组内的多个终端设备共享登录状态，当一个终端设备登录后，组内其他的终端设备共享该已登录的终端设备的登录状态，从而这些其他的终端设备不必再提供登录信息就可以实现登录云端服务器。
共享设备组由云端服务器负责建立和管理，负责维护所述共享设备组的描述信息，其中所述描述信息包括：该共享设备组的组标识信息(GID)、 该共享设备组包括的各终端设备的标识信息(ID)，在实际应用中，终端设备的标识信息可以是通用唯一识别码(Universally Unique Identifier，简称UUID)或媒体访问控制(Media Access Control，简称MAC)地址或IP地址等能够唯一标识设备的信息，本申请对此不进行限制。当云端服务器建立一个共享设备组后，为该共享设备组分配全局唯一的组标识信息(ID)。
所述多个终端设备具备网络连接功能，云端服务器通过无线或有线方式与多个终端设备建立连接。例如，云端服务器使用套接字socket(采用TCP、RUDP等协议)与终端设备之间建立长连接通道，从而云端服务器通过该通道与终端设备进行通信，相互之间传送数据信息。
在本申请中，所述多个终端设备具备近距离通信功能，这些终端设备包括但不限于：智能手机、平板电脑(PAD)、笔记本电脑、台式机、智能电视、机顶盒、路由器等设备。在实际应用中，所述近距离通信功能可以是近场通信(NFC)或非接触式射频识别(RFID)或蓝牙等无线技术，本申请不进行限制。在采用NFC或RFID技术进行交互时，设备之间不需要配对，直接靠近就可以完成通信。所述多个终端设备通过近距离通信功能进行相互协商，加入同一个共享设备组。
一般地，设备加入共享设备组之后，便不再需要设备的NFC功能进行通信，即设备的NFC功能只在建立基于云端服务器的共享设备组的过程中使用。在实际应用中，设备加入设备组之后，如果终端设备不需要再保持设备组的共享关系，则可以进行注销或者退出设备组的处理。设备注销之后设备组一起注销，而设备退出后设备组还存在并不注销，具体地：
设备注销流程的步骤如下：
(1)设备A注销登录账号；
(2)设备A通知用户是否注销设备组其它设备，用户确认注销时，设备A通知云端服务器清除设备组各个登录token；云端服务器通过长连接通道通知其它设备清除登录状态；以及
设备退出设备组的步骤如下：
(1)设备注销登录状态，并选择不注销设备组其它设备，此时设备自动 退出设备组；
(2)设备加入一个新的设备组，设备自动退出原有设备组。
在步骤S104中，所述云端服务器接收所述共享设备组的第一终端设备发送的登录请求消息，根据所述登录请求消息验证所述第一终端设备是否为所述共享设备组的设备，若验证通过则向所述第一终端设备发送登录成功消息。
在本申请的一个实施例中，在步骤S104之前还包括有，共享设备组中的一个终端设备(第二终端设备)已登录云端服务器。在实际应用中，该第二终端设备可以使用一般的登录方式登录云端服务器。例如，第二终端设备在云端服务器的用户登录界面输入用户名、密码等登录信息发起登录，云端服务器验证通过登录信息后允许第二终端设备登录。
在共享设备组的第二终端设备成功登录云端服务器后，云端服务器生成鉴权密钥(token)并存储在该共享设备组的描述信息中，其中该鉴权密钥可以是预先配置的或随机生成的任意字符串，本申请不进行限定。接着，云端服务器通过长连接通道将生成的鉴权密钥发送给该组内的每个设备，显然该共享设备组的第一终端设备也接收到该鉴权密钥。然后，第一终端设备使用预先设置的加密算法(例如MD5、RC4、DES等)对鉴权密钥和第一终端设备的标识信息进行加密计算生成身份验证信息，并向云端服务器发送包括身份验证信息在内的登录请求信息，以请求云端服务器根据身份验证信息对第一终端设备的身份进行验证。
云端服务器接收到共享设备组的第一终端设备发送的登录请求消息后，根据其中携带的身份验证信息对第一终端设备的身份进行验证。具体地验证过程包括：云端服务器在该共享设备组的描述信息中取得鉴权密钥和第一终端设备的标识信息，使用与在第一终端设备配置的加密算法相同的加密算法(例如MD5、RC4、DES等)对取得的鉴权密钥和第一终端设备的标识信息进行加密计算，并与身份验证信息进行比较，如果相同则通过验证，允许第一终端设备登录云端服务器，云端服务器向第一终端设备发送登录成功消息。
通过上述实施例，当共享设备组内一个设备登录后，组内的其他设备通 过共享登录状态在免输入登录信息的情况下实现了登录云端服务器的效果。
下面结合一个具体示例详细说明。参考图2，在一个家庭用户中包括有手机204、智能电视206和路由器208等具有NFC功能的设备，云端服务器202和这些终端设备建立有长连接通道，并且这些终端设备加入云端服务器202建立的共享设备组。其中手机204的IP地址为“192.168.0.1”、智能电视206的IP地址为“192.168.0.2”、路由器208的IP地址为“192.168.0.3”，云端服务器202为该共享设备组分配的组标识信息为G-1，然后云端服务器202将上述信息记录在该组的描述信息中。当手机204登录云端服务器202时，作为该组内第一个登录的设备，手机204在登录界面输入用户名和登录密码等信息后成功登录云端服务器202。接着，云端服务器202随机生成一个鉴权密钥(token)存储在本地，然后通过长连接通道将该鉴权token发送给组内的其他设备智能电视206和路由器208。智能电视206接收到鉴权token后，使用MD5算法加密鉴权token和智能电视206的IP地址“192.168.0.2”，将得到的散列值作为身份验证信息，并向云端服务器202发送包括身份验证信息的登录请求信息。云端服务器202接收到智能电视206发送的登录请求信息后，使用同样的MD5算法加密在本地存储的鉴权token和智能电视206的IP地址“192.168.0.2”并得到一个散列值，如果该散列值与登录请求信息中的散列值一致，则确认智能电视206与手机204是同一个共享设备组的设备，即验证通过智能电视206的身份，允许智能电视206登录云端服务器202。这样，智能电视206不需要输入用户名和登录密码就可以访问云端服务器202。同样地，路由器208采用同样的登录方式登录云端服务器202，不再赘述。
需要说明，为简明在以上的实例中以终端设备的IP地址作为标识信息进行说明，但是本申请并不以此为限，还可以采用终端设备的UUID码或MAC地址作为标识信息，此处不赘述。
下面结合图3详细描述上述处理过程。图3是根据本申请实施例的共享设备组的设备登录处理的流程图，在图3所示的实施例中，设备A和B加入同一个共享设备组，且设备A和B通过与云端服务器建立的长连接通道传送 数据。如图3所示包括以下步骤：
在步骤S302中，设备A在云端服务器的登录界面输入用户名和密码，发起登录云端服务器。
在步骤S304中，云端服务器验证通过设备A输入的用户名和密码后，生成鉴权密钥(token)，并与用户名一起并保存在云端设备组的描述信息中。
在步骤S306中，云端服务器通过长连接通道将包括鉴权token的登录信息发送给设备A所在共享设备组的其它设备(例如设备B)。
在步骤S308中，设备B通过长连接通道接收到登录信息，然后使用加密算法(例如MD5、RC4、DES等)加密鉴权token和设备B的全局唯一标识(例如UUID或MAC地址)生成身份验证信息，并将该验证信息发送给云端服务器请求身份验证。
在步骤S310中，云端服务器通过同样的加密算法(例如MD5、RC4、DES等)解密，确认设备B的登录请求合法，并给设备B发送登录成功通知。
下面结合图4描述根据本申请实施例的云端服务器的结构，如图4所示，该云端服务器至少包括：共享设备组维护模块402、接收模块404、登录管理模块406、共享设备组建立模块408、通道建立模块410、密钥生成模块412和发送模块414，下面详细描述云端服务器的结构和功能。
共享设备组维护模块402，用于将与云端服务器具有连接关系的多个终端设备加入预先建立的共享设备组；
接收模块404，用于接收所述共享设备组的第一终端设备发送的登录请求信息。具体地，所述接收模块404接收的登录请求信息中包括：所述鉴权密钥和所述第一终端设备的标识信息。
登录管理模块406，用于根据所述登录请求信息验证所述第一终端设备是否为所述共享设备组的设备，若验证通过则允许所述第一终端设备登录所述云端服务器。具体地，所述登录管理模块406根据所述鉴权密钥和第一终端设备的标识信息，验证所述第一终端设备是否为所述共享设备组的设备。
共享设备组建立模块408，用于建立所述共享设备组。所述共享设备组维护模块402还用于维护所述共享设备组的描述信息，其中所述描述信息包 括：该共享设备组的组标识信息、该共享设备组包括的各终端设备的标识信息。
通道建立模块410，用于建立与所述多个终端设备之间的连接通道。所述接收模块404通过所述连接通道接收所述共享设备组的第二终端设备发送的登录信息。所述登录管理模块406还用于验证通过所述登录信息，允许第二终端设备登录所述云端服务器。
密钥生成模块412，用于生成鉴权密钥。
发送模块414，用于通过所述连接通道将所述鉴权密钥发送至所述第一终端设备。
根据本申请实施例还提供一种终端设备的登录方法，如图5所示，该方法包括：
在步骤S502中，第一终端设备加入云端服务器预先建立的共享设备组，并且所述共享设备组中的第二终端设备成功登录所述云端服务器；
所述第一终端设备和所述第二终端设备具备近距离通信功能(例如NFC)，所述第一终端设备和所述第二终端设备通过近距离通信功能进行相互协商，加入所述共享设备组。
下面结合图6详细描述两个终端设备加入同一个共享设备组的过程。参考图6，设备A和设备B加入共享设备组的步骤如下：
在步骤S602中，设备A获取其所在的共享设备组ID，设备B获取其所在的共享设备组ID。设备所在的共享设备组就是设备已加入的设备组，如果设备还未加入过设备组则获取到的设备组ID为空或者省略此步骤。
在步骤S604中，设备A与设备B靠近，设备A通过NFC功能把设备组ID传给设备B。
在步骤S606中，判断设备A的设备组ID是否有效，如果设备A的设备组ID有效则执行步骤S608，如果无效则执行步骤S614。
如果设备本身还没有加入设备组则不能获取到组ID，或者设备加入过设备组但是该组已被撤销，在这些情况下，都属于设备组ID无效的情况。
在步骤S608中，判断设备B的设备组ID是否有效，如果设备B的设备组ID有效则执行步骤S610，如果无效则执行步骤S612。
在步骤S610中，设备A与设备B的设备组ID均有效，在这种情况下，可以提示用户，由用户选择设备是设备A加入设备B所在的组，还是设备B加入设备A所在的组；或者根据预设的规则将一个设备加入另一个设备所在的组。在本实施例中，以设备B加入设备A所在的组为例进行描述。设备B通知云端服务器，设备B退出原有设备组，并加入A所在的共享设备组。
在步骤S612中，设备A的设备组ID有效且设备B的设备组ID无效，在这种情况下，设备B通知云端服务器，加入A所在的设备组，并通知A已加入A所在的设备组。
在步骤S614中，判断设备B的设备组ID是否有效，如果设备B的设备组ID有效则执行步骤S616，如果无效则执行步骤S618。
在步骤S616中，设备A的设备组ID无效且设备B的设备组ID有效，在这种情况下，设备B通知设备A加入自己的设备组，设备A收到消息后通知云端服务器，设备A加入设备B所在的共享设备组。
在步骤S618中，设备A与设备B的设备组ID均无效，在这种情况下，设备B与云端服务器通讯，获取新的共享设备组ID，并加入这个新的设备组，写入本地设备存储，然后传给设备A；设备A收到后，通知云端加入设备B所在的共享设备组。
一般情况下，两个终端设备通过NFC通讯加入同一个共享设备组包括以上四种情况。通过上述过程，两个终端设备加入到同一个共享设备组，多个设备加入到同一个共享设备组的过程与上述情况类似，此处不再赘述。实际上，终端设备在加入共享设备组时通过近距离通信功能进行交互通信，在此之后组内的终端设备之间不需要经常性地连接交互，即终端设备只使用近距离通信功能进行一个过程的交互通信。在多个终端设备加入到同一个共享设备组之后，将其加入的终端设备组的标识信息发送至云端服务器，由云端服务器存储终端的标识信息。
在步骤S504中，所述第一终端设备向所述云端服务器发送登录请求消息，以请求所述云端服务器验证所述第一终端设备为所述共享设备组的设备；
在步骤S504之前，第一终端设备接收云端服务器发送的鉴权密钥，所述第一终端设备向所述云端服务器发送的所述登录请求消息中包括：所述鉴权密钥和所述第一终端设备的标识信息。云端服务器根据鉴权密钥和第一终端设备的标识信息对第一终端进行身份鉴权，如果鉴权通过则允许访问云端服务器，从而向第一终端设备发送登录成功消息。
在步骤S506中，所述第一终端设备接收所述云端服务器发送的登录成功消息。
下面结合图7描述终端设备的结构，如图7所示，所述终端设备包括：
加入模块702，用于加入云端服务器预先建立的共享设备组。该终端设备具有近距离通信功能(例如NFC)，并通过近距离通信功能与其他的终端设备相互协商加入所述共享设备组。
发送模块704，用于向所述云端服务器发送登录请求消息，以请求所述云端服务器验证所述终端设备为所述共享设备组的设备。所述发送模块704还用于将其加入的终端设备组的标识信息发送至所述云端服务器。
接收模块706，用于接收所述云端服务器发送的登录成功消息。
所述接收模块706还用于接收所述云端服务器发送的鉴权密钥，所述发送模块704向所述云端服务器发送的所述登录请求消息中包括：所述鉴权密钥和所述终端设备的标识信息。
综上所述，根据本申请的技术方案，通过将多个设备加入云端服务器的共享设备组，当组中的一个设备登录后，组内的其他设备通过共享登录状态在免输入登录信息的情况下实现了登录云端服务器的效果，实现了一个设备登录后同组的其他设备能够自动登录，从而简化了登录操作，提高了效率。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/ 输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (19)

  1. 一种终端设备的登录方法，其特征在于，包括：
    云端服务器将与其具有连接关系的多个终端设备加入预先建立的共享设备组；
    所述云端服务器接收所述共享设备组的第一终端设备发送的登录请求消息，根据所述登录请求消息验证所述第一终端设备是否为所述共享设备组的设备，若验证通过则向所述第一终端设备发送登录成功消息。
  2. 根据权利要求1所述的方法，其特征在于，所述云端服务器将与其具有连接关系的多个终端设备加入预先建立的共享设备组的步骤，包括：
    所述云端服务器建立所述共享设备组，并将与其具有连接关系的多个终端设备加入所述共享设备组；
    所述云端服务器维护所述共享设备组的描述信息，所述描述信息包括：该共享设备组的组标识信息、该共享设备组包括的各终端设备的标识信息。
  3. 根据权利要求2所述的方法，其特征在于，还包括：
    所述云端服务器建立与所述多个终端设备之间的连接通道，
    所述云端服务器通过所述连接通道接收所述共享设备组的第二终端设备发送的登录信息，并验证通过所述登录信息。
  4. 根据权利要求3所述的方法，其特征在于，还包括：
    所述云端服务器生成鉴权密钥，并通过所述连接通道将所述鉴权密钥发送至所述第一终端设备。
  5. 根据权利要求4所述的方法，其特征在于，所述云端服务器接收的第一终端设备发送的登录请求消息中包括：所述鉴权密钥和所述第一终端设备的标识信息；
    所述方法还包括：所述云端服务器根据所述鉴权密钥和所述第一终端设备的标识信息，验证所述第一终端设备是否为所述共享设备组的设备。
  6. 一种终端设备的登录方法，其特征在于，包括：
    第一终端设备加入云端服务器预先建立的共享设备组，并且所述共享设备组中的第二终端设备成功登录所述云端服务器；
    所述第一终端设备向所述云端服务器发送登录请求消息，以请求所述云端服务器验证所述第一终端设备为所述共享设备组的设备；
    所述第一终端设备接收所述云端服务器发送的登录成功消息。
  7. 根据权利要求6所述的方法，其特征在于，所述第一终端设备和所述第二终端设备具备近距离通信功能，所述第一终端设备和所述第二终端设备通过近距离通信功能进行相互协商，加入所述共享设备组。
  8. 根据权利要求7所述的方法，其特征在于，所述第一终端设备加入所述共享设备组的步骤，包括：
    所述第一终端设备通过近距离通信功能将其加入的共享设备组的组标识信息发送给所述第二终端设备；
    若所述第一终端设备和所述第二终端设备的组标识信息均无效，则所述第一终端设备加入所述云端服务器新建立的一个共享设备组，并将该组的组标识信息发送至所述第二终端设备，从而所述第二终端设备加入该新的共享设备组；
    若所述第一终端设备的组标识信息有效且所述第二终端设备的组标识信息无效，则所述第二终端设备加入所述第一终端设备所在的共享设备组；
    若所述第一终端设备的组标识信息无效且所述第二终端设备的组标识信息有效，则所述第一终端设备加入所述第二终端设备所在的共享设备组；
    若所述第一终端设备和所述第二终端设备的组标识信息均有效，则所述第一终端设备退出其所在的共享设备组，并加入所述第二终端设备所在的共享设备组。
  9. 根据权利要求8所述的方法，其特征在于，所述第一终端设备和/或所述第二终端设备将其加入的终端设备组的标识信息发送至所述云端服务器。
  10. 根据权利要求9所述的方法，其特征在于，在所述第一终端设备向所述云端服务器发送登录请求消息之前，所述方法还包括：
    所述第一终端设备接收所述云端服务器发送的鉴权密钥；
    所述第一终端设备向所述云端服务器发送的所述登录请求消息中包括：所述鉴权密钥和所述第一终端设备的标识信息。
  11. 一种云端服务器，其特征在于，包括：
    共享设备组维护模块，用于将与云端服务器具有连接关系的多个终端设备加入预先建立的共享设备组；
    接收模块，用于接收所述共享设备组的第一终端设备发送的登录请求信息；
    登录管理模块，用于根据所述登录请求信息验证所述第一终端设备是否为所述共享设备组的设备，若验证通过则允许所述第一终端设备登录所述云端服务器。
  12. 根据权利要求11所述的云端服务器，其特征在于，还包括：
    共享设备组建立模块，用于建立所述共享设备组；
    所述共享设备组维护模块还用于维护所述共享设备组的描述信息，所述描述信息包括：该共享设备组的组标识信息、该共享设备组包括的各终端设备的标识信息。
  13. 根据权利要求12所述的云端服务器，其特征在于，还包括：
    通道建立模块，用于建立与所述多个终端设备之间的连接通道；
    所述接收模块还用于通过所述连接通道接收所述共享设备组的第二终端设备发送的登录信息；
    所述登录管理模块还用于验证通过所述登录信息。
  14. 根据权利要求13所述的云端服务器，其特征在于，还包括：
    密钥生成模块，用于生成鉴权密钥；
    发送模块，用于通过所述连接通道将所述鉴权密钥发送至所述第一终端设备。
  15. 根据权利要求14所述的云端服务器，其特征在于，
    所述接收模块接收的登录请求信息中包括：所述鉴权密钥和所述第一终端设备的标识信息；
    所述登录管理模块根据所述鉴权密钥和第一终端设备的标识信息，验证所述第一终端设备是否为所述共享设备组的设备。
  16. 一种终端设备，其特征在于，包括：
    加入模块，用于加入云端服务器预先建立的共享设备组；
    发送模块，用于向所述云端服务器发送登录请求消息，以请求所述云端服务器验证所述终端设备为所述共享设备组的设备；
    接收模块，用于接收所述云端服务器发送的登录成功消息。
  17. 根据权利要求16所述的终端设备，其特征在于，所述终端设备具有近距离通信功能，并通过近距离通信功能与其他的终端设备相互协商加入所述共享设备组。
  18. 根据权利要求16所述的终端设备，其特征在于，所述发送模块还用于将其加入的终端设备组的标识信息发送至所述云端服务器。
  19. 根据权利要求17所述的终端设备，其特征在于，还包括：
    所述接收模块还用于接收所述云端服务器发送的鉴权密钥；
    所述发送模块向所述云端服务器发送的所述登录请求消息中包括：所述鉴权密钥和所述终端设备的标识信息。
PCT/CN2015/079579 2014-05-29 2015-05-22 终端设备的登录方法、终端设备和云端服务器 WO2015180589A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410234534.0A CN105141645A (zh) 2014-05-29 2014-05-29 终端设备的登录方法、终端设备和云端服务器
CN201410234534.0 2014-05-29

Publications (1)

Publication Number Publication Date
WO2015180589A1 true WO2015180589A1 (zh) 2015-12-03

Family

ID=54698076

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/079579 WO2015180589A1 (zh) 2014-05-29 2015-05-22 终端设备的登录方法、终端设备和云端服务器

Country Status (3)

Country Link
CN (1) CN105141645A (zh)
HK (1) HK1215767A1 (zh)
WO (1) WO2015180589A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108833378A (zh) * 2018-05-31 2018-11-16 上海康斐信息技术有限公司 一种多帐号登陆的处理方法及系统
CN110855598A (zh) * 2018-08-20 2020-02-28 北京场景互娱传媒科技有限公司 终端应用的管理方法、终端设备、云端服务器及存储介质
CN112104567A (zh) * 2020-09-03 2020-12-18 中国银联股份有限公司 流量控制方法、装置、设备及介质
CN112235116A (zh) * 2020-10-14 2021-01-15 北京金山云网络技术有限公司 业务处理方法、装置和电子设备
CN113206817A (zh) * 2020-02-03 2021-08-03 中移物联网有限公司 一种设备连接确认方法和区块链网络

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453372B (zh) * 2016-11-03 2019-10-25 努比亚技术有限公司 一种终端、服务器和账户登录方法
CN109272665A (zh) * 2018-09-11 2019-01-25 深圳数位科技有限公司 一种共享设备的使用方法及系统
CN111353142A (zh) * 2019-02-15 2020-06-30 鸿合科技股份有限公司 一种用户信息共享方法及装置、电子设备
CN111447208A (zh) * 2020-03-24 2020-07-24 维沃移动通信有限公司 信息共享方法及电子设备
CN111639014A (zh) * 2020-05-14 2020-09-08 深圳市筑泰防务智能科技有限公司 模拟成多台终端对服务器进行测试的测试方法、装置、终端及可读存储介质
CN114650147A (zh) * 2020-12-02 2022-06-21 成都鼎桥通信技术有限公司 登录方法及设备
CN112261708B (zh) * 2020-12-18 2021-07-20 深圳市晶讯技术股份有限公司 一种自动化批量配置WiFi设备的系统和方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102075546A (zh) * 2011-02-18 2011-05-25 北京积木恒硕科技有限公司 一种基于云计算的在线操作系统
CN103188237A (zh) * 2011-12-30 2013-07-03 盛大计算机（上海）有限公司 单点登录系统及方法
CN103475476A (zh) * 2013-09-02 2013-12-25 小米科技有限责任公司 多终端登录服务器的方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102647291B (zh) * 2011-02-17 2014-08-13 三星电子（中国）研发中心 基于账户群组的多设备智能管理方法
CN103152399B (zh) * 2013-02-07 2016-05-25 百度在线网络技术（北京）有限公司 登录方法、系统和云端服务器
CN103457951B (zh) * 2013-09-02 2018-04-27 小米科技有限责任公司 多终端登录服务器的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102075546A (zh) * 2011-02-18 2011-05-25 北京积木恒硕科技有限公司 一种基于云计算的在线操作系统
CN103188237A (zh) * 2011-12-30 2013-07-03 盛大计算机（上海）有限公司 单点登录系统及方法
CN103475476A (zh) * 2013-09-02 2013-12-25 小米科技有限责任公司 多终端登录服务器的方法及装置

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108833378A (zh) * 2018-05-31 2018-11-16 上海康斐信息技术有限公司 一种多帐号登陆的处理方法及系统
CN110855598A (zh) * 2018-08-20 2020-02-28 北京场景互娱传媒科技有限公司 终端应用的管理方法、终端设备、云端服务器及存储介质
CN113206817A (zh) * 2020-02-03 2021-08-03 中移物联网有限公司 一种设备连接确认方法和区块链网络
CN113206817B (zh) * 2020-02-03 2022-07-12 中移物联网有限公司 一种设备连接确认方法和区块链网络
CN112104567A (zh) * 2020-09-03 2020-12-18 中国银联股份有限公司 流量控制方法、装置、设备及介质
CN112104567B (zh) * 2020-09-03 2022-11-18 中国银联股份有限公司 流量控制方法、装置、设备及介质
CN112235116A (zh) * 2020-10-14 2021-01-15 北京金山云网络技术有限公司 业务处理方法、装置和电子设备

Also Published As

Publication number Publication date
HK1215767A1 (zh) 2016-09-09
CN105141645A (zh) 2015-12-09

Similar Documents

Publication Publication Date Title
WO2015180589A1 (zh) 终端设备的登录方法、终端设备和云端服务器
US10412061B2 (en) Method and system for encrypted communications
JP6571250B2 (ja) ある装置を使用して別の装置をアンロックする方法
US10547613B1 (en) Simplified association of devices with a network using unique codes on the devices and side channel communication
KR102113440B1 (ko) 디바이스들에 대한 동적 그룹 멤버십
WO2017190616A1 (zh) 无线网络连接方法、无线接入点、服务器及系统
US20160269176A1 (en) Key Configuration Method, System, and Apparatus
CN109479049B (zh) 用于密钥供应委托的系统、设备和方法
EP2974213B1 (en) Seamless device configuration in a communication network
KR101508360B1 (ko) 데이터 전송 장치 및 방법, 그리고 그 방법을 컴퓨터에서 실행시키기 위한 프로그램을 기록한 기록매체
US11736304B2 (en) Secure authentication of remote equipment
US20150215128A1 (en) Mobile device user strong authentication for accessing protected network resources
US20210377047A1 (en) Systems, methods, and apparatuses for network management
JP7292263B2 (ja) デジタル証明書を管理するための方法および装置
CN103873487A (zh) 一种基于智能家居设备安全挂件的家居信任组网的实现方法
EP3794852B1 (en) Secure methods and systems for identifying bluetooth connected devices with installed application
WO2022100356A1 (zh) 身份认证系统、方法、装置、设备及计算机可读存储介质
WO2023174038A1 (zh) 数据传输方法及相关设备
US20220070172A1 (en) Methods and systems for enabling identity-based services using a random identifier
EP3163841A1 (en) A method, system, server, client and application for sharing digital content between communication devices within an internet network
WO2023207113A1 (zh) 一种设备互联安全认证系统、方法、装置、服务器及介质
WO2023141876A1 (zh) 数据传输方法、装置、系统、电子设备及可读介质
TWI835491B (zh) 一種設備互聯安全認證系統、方法、裝置、伺服器及介質
US11343675B2 (en) Communication device authentication for multiple communication devices
CN117939450A (zh) 蓝牙mesh网络的连接方法、装置和蓝牙通信系统

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: 15800220

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: 15800220

Country of ref document: EP

Kind code of ref document: A1