CN115834095A

CN115834095A - Multi-device collaborative login method, display device and server

Info

Publication number: CN115834095A
Application number: CN202111093415.4A
Authority: CN
Inventors: 薛健; 李金昆
Original assignee: Juhaokan Technology Co Ltd
Current assignee: Juhaokan Technology Co Ltd
Priority date: 2021-09-17
Filing date: 2021-09-17
Publication date: 2023-03-21

Abstract

The application discloses a multi-device collaborative login method, a display device and a server, wherein a primary device which logs in an account firstly sends an account login request to the server based on user login information generated by a user, receives primary token information generated after the server verifies the user login information, logs in a specified account, and automatically sends the primary token information to a slave device with a pairing relation. The slave device generates an automatic login request based on the master token information and sends the automatic login request to the server, and the slave token information is generated after the master token information is verified by the server, so that the slave device and the master device log in the same specified account based on the slave token information. Therefore, according to the method, the display equipment and the server, after the user preferentially logs in the account on one display equipment, the rest display equipment can log in automatically without manual login of the user, and the purpose of cooperatively logging in the account by multiple devices is achieved. The method and the device have the advantages that convenience is provided for users, and meanwhile account login efficiency is high.

Description

Multi-device collaborative login method, display device and server

Technical Field

The application relates to the technical field of device collaborative login, in particular to a multi-device collaborative login method, a display device and a server.

Background

Along with the rapid development of display devices, the functions of the display devices will be more and more abundant, and the performance of the display devices will also be more and more powerful. With the popularization of smart devices, a plurality of smart devices may exist in a user's home, such as a smart remote controller, a television, a refrigerator, an air conditioner, and the like.

In order to obtain rich functional experience, each device needs to log in the back of a user account to meet the optimal use requirement. The login method commonly adopted at present is that each device needs to log in an account independently, for example, a user actively scans a two-dimensional code on each device to log in. Therefore, the login mode is not convenient enough, so that the login efficiency is low and the user experience is not good.

Disclosure of Invention

The application provides a multi-device collaborative login method, a display device and a server, and aims to solve the problems that an existing login mode is not convenient enough and login efficiency is low.

In a first aspect, the present application provides a display device comprising: a display configured to present a user interface; a controller connected to the display, the controller configured to:

generating an account login request based on user login information generated by a user, and sending the account login request to a server, wherein the account login request is used for indicating the server to verify the user login information, and generating master token information after the verification is passed, and the master token information is used for realizing that a master device and a slave device login a specified account corresponding to the user login information;

receiving primary token information generated by the server after the user login information passes the verification, and logging in a corresponding specified account based on an account ID in the primary token information, wherein the primary token information comprises an account ID used for identifying the account corresponding to the user login information;

and sending the master token information to the slave equipment, wherein the master token information is used for indicating the slave equipment to request the slave token information from the server based on the master token information so as to log in a corresponding specified account based on the account ID in the slave token information, and the slave equipment is equipment in a pairing relation with the master equipment.

In a second aspect, the present application also provides a display device, including: a display configured to present a user interface; a controller connected with the display, the controller configured to:

receiving master token information sent by a master device after logging in a specified account based on user login information generated by a user, wherein the master token information is information generated by a server after the master device requests a server for verification based on the user login information, and the master token information comprises a user ID, an account ID, a token validity period and a token duration;

generating an automatic login request based on a slave device ID and a user ID, an account ID, a token validity period and a time length in the master token information, and sending the automatic login request to a server, wherein the automatic login request is used for indicating the server to verify the slave device ID and the master token information, and the slave token information is generated based on the master token information after the verification is passed, and comprises the user ID, the account ID, the slave token ID, the updated token validity period and the updated time length;

and receiving slave token information generated after the slave device ID and the master token information are verified by the server, and logging in a corresponding specified account based on the account ID in the slave token information.

In a third aspect, the present application further provides a server, including: a controller configured to:

responding to an account login request which is sent by a master device and carries user login information, verifying the user login information, generating master token information after the verification is passed, sending the master token information to the master device, enabling the master device to login a corresponding specified account based on an account ID in the master token information, and sending the master token information to a slave device, wherein the account ID is used for identifying the corresponding account after the user login information is verified;

the method comprises the steps that a slave device responds to an automatic login request generated by the slave device ID after receiving master token information sent by a master device, the slave device ID and the master token information carried in the automatic login request are checked, the slave token information is generated based on the master token information after the automatic login request passes the check and is sent to the slave device, the master token information comprises a user ID, an account ID, a token validity period and a time length, the slave token information comprises the user ID, the account ID, a slave token ID and an updated token validity period and time length, so that the slave device logs in the specified account based on the account ID in the slave token information, and the slave device is a device in a pairing relation with the master device.

In a fourth aspect, the present application further provides a multi-device collaborative login method, which is applied to a master device, and the method includes:

generating an account login request based on user login information generated by a user, and sending the account login request to a server, wherein the account login request is used for indicating the server to verify the user login information, and generating master token information after the verification is passed, and the master token information is used for realizing that a master device and a slave device log in a specified account corresponding to the user login information;

In a fifth aspect, the present application further provides a multi-device collaborative login method, which is applied to a slave device, and the method includes:

In a sixth aspect, the present application further provides a multi-device collaborative login method, which is applied to a server, and the method includes:

In a seventh aspect, the present application further provides a storage medium, where the storage medium may store a program, and when the program is executed, the program may implement some or all of the steps in the embodiments of the multi-device collaborative login method provided by the present application.

According to the technical scheme, the multi-device collaborative login method, the display device and the server provided by the embodiment of the invention have the advantages that the primary device which logs in the account firstly sends the account login request to the server based on the user login information generated by the user, the primary token information generated after the user login information is verified by the server is received, the specified account is logged in, and meanwhile, the primary token information is automatically sent to the slave device with the pairing relationship. The slave device generates an automatic login request based on the master token information and sends the automatic login request to the server, the slave token information is generated after the server verifies the master token information, and the slave device is allowed to login an account number, so that the slave device and the master device login the same specified account number based on the slave token information. Therefore, according to the method, the display equipment and the server, after the user preferentially logs in the account on one display equipment, the rest display equipment can log in automatically without manual login of the user, and the purpose of cooperatively logging in the account by multiple devices is achieved. The method and the device have the advantages that convenience is provided for users, account login efficiency is high, and user interaction experience is improved.

Drawings

In order to more clearly describe the technical solution of the present application, the drawings required to be used in the embodiments will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive labor.

FIG. 1 illustrates a schematic diagram of an operational scenario between a smart control device and a control apparatus, in accordance with some embodiments;

fig. 2 illustrates a hardware configuration block diagram of an intelligent control device 200 according to some embodiments;

fig. 3 shows a block diagram of a hardware configuration of the control apparatus 100 according to some embodiments;

FIG. 4 illustrates a software configuration diagram in the intelligent control device 200 according to some embodiments;

FIG. 5 illustrates an interaction diagram for multiple devices establishing a pairing relationship, according to some embodiments;

FIG. 6 illustrates a flow diagram of a multi-device collaborative login method performed by a master device, in accordance with some embodiments;

FIG. 7 illustrates an interaction diagram of a multi-device collaborative login method according to some embodiments;

FIG. 8 illustrates a schematic interface diagram of a primary device logging into an account, according to some embodiments;

FIG. 9 illustrates a flow diagram of a multi-device collaborative login method performed by a slave device, in accordance with some embodiments;

FIG. 10 illustrates a schematic diagram of presenting a reminder interface from a device, in accordance with some embodiments;

FIG. 11 illustrates a flow diagram of a multi-device collaborative login method performed by a server according to some embodiments.

Detailed Description

To make the purpose and embodiments of the present application clearer, the following will clearly and completely describe the exemplary embodiments of the present application with reference to the attached drawings in the exemplary embodiments of the present application, and it is obvious that the described exemplary embodiments are only a part of the embodiments of the present application, and not all of the embodiments.

It should be noted that the brief descriptions of the terms in the present application are only for convenience of understanding of the embodiments described below, and are not intended to limit the embodiments of the present application. These terms should be understood in their ordinary and customary meaning unless otherwise indicated.

The terms "first," "second," "third," and the like in the description and claims of this application and in the above-described drawings are used for distinguishing between similar or analogous objects or entities and not necessarily for describing a particular sequential or chronological order, unless otherwise indicated. It is to be understood that the terms so used are interchangeable under appropriate circumstances.

The terms "comprises" and "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a product or apparatus that comprises a list of elements is not necessarily limited to all elements expressly listed, but may include other elements not expressly listed or inherent to such product or apparatus.

The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and/or software code that is capable of performing the functionality associated with that element.

When the intelligent control device is a display device, introduction is performed based on the structure of the display device.

FIG. 1 illustrates a usage scenario of a smart control device according to some embodiments. As shown in fig. 1, the smart control device 200 is also in data communication with a server 400, and a user can operate the smart control device 200 through the smart device 300 or the control apparatus 100.

In some embodiments, the control apparatus 100 may be a remote controller, and the communication between the remote controller and the intelligent control device includes at least one of an infrared protocol communication or a bluetooth protocol communication, and other short-distance communication methods, and the intelligent control device 200 is controlled by a wireless or wired method. The user may input a user command through at least one of a button on a remote controller, a voice input, a control panel input, etc. to control the intelligent control device 200.

In some embodiments, the smart device 300 may include any of a mobile terminal, a tablet, a computer, a laptop, an AR/VR device, and the like.

In some embodiments, the smart device 300 may also be used to control the smart control device 200. For example, the smart control device 200 is controlled using an application program running on the smart device. In some embodiments, the smart device 300 and the smart control device may also be used for communication of data.

In some embodiments, the intelligent control device 200 may also be controlled in a manner other than the control apparatus 100 and the intelligent device 300, for example, the voice instruction control of the user may be directly received by a module configured inside the intelligent control device 200 to obtain the voice instruction, or may be received by a voice control apparatus provided outside the intelligent control device 200.

In some embodiments, the smart control device 200 is also in data communication with the server 400. The intelligent control device 200 may be allowed to make communication connections through a Local Area Network (LAN), a Wireless Local Area Network (WLAN), and other networks. The server 400 may provide various contents and interactions to the smart control device 200. The server 400 may be a cluster or a plurality of clusters, and may include one or more types of servers.

In some embodiments, software steps executed by one step execution agent may be migrated on demand to another step execution agent in data communication therewith for execution. Illustratively, the software steps executed by the server may be migrated to be executed on the intelligent control device in data communication therewith, and vice versa, as needed.

Fig. 2 illustrates a block diagram of a hardware configuration of the control apparatus 100 according to some embodiments. As shown in fig. 2, the control device 100 includes a controller 110, a communication interface 130, a user input/output interface 140, a memory, and a power supply. The control apparatus 100 may receive an input operation instruction from a user and convert the operation instruction into an instruction recognizable and responsive by the smart control device 200, serving as an interaction intermediary between the user and the smart control device 200.

In some embodiments, the communication interface 130 is used for external communication, and includes at least one of a WIFI chip, a bluetooth module, NFC, or an alternative module. In some embodiments, the user input/output interface 140 includes at least one of a microphone, a touchpad, a sensor, a key, or an alternative module.

Fig. 3 illustrates a hardware configuration block diagram of the intelligent control device 200 according to some embodiments. Referring to fig. 3, in some embodiments, the intelligent control apparatus 200 includes at least one of a tuning demodulator 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, a user interface. In some embodiments, the controller includes a central processor, a video processor, an audio processor, a graphic processor, a RAM, a ROM, a first interface to an nth interface for input/output.

In some embodiments, the display 260 includes a display screen component for displaying pictures, and a driving component for driving image display, a component for receiving image signals from the controller output, displaying video content, image content, and menu manipulation interface, and a user manipulation UI interface, etc. In some embodiments, the display 260 may be at least one of a liquid crystal display, an OLED display, and a projection display, and may also be a projection device and a projection screen.

In some embodiments, the controller 250 and the modem 210 may be located in different separate devices, that is, the modem 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box. In some embodiments, controller 250 controls the operation of the intelligent control device and responds to user actions through various software control programs stored in memory. The controller 250 controls the overall operation of the intelligent control device 200. For example: in response to receiving a user command for selecting a UI object to be displayed on the display 260, the controller 250 may perform an operation related to the object selected by the user command.

In some embodiments, the object may be any one of selectable objects, such as a hyperlink, an icon, or other actionable control. Operations related to the selected object are: displaying an operation connected to a hyperlink page, document, image, or the like, or performing an operation of a program corresponding to the icon.

In some embodiments the controller comprises at least one of a Central Processing Unit (CPU), a video processor, an audio processor, a Graphics Processing Unit (GPU), a RAM Random Access Memory (RAM), a ROM (Read-Only Memory), a first to nth interface for input/output, a communication Bus (Bus), and the like.

In some embodiments, a user may enter user commands on a Graphical User Interface (GUI) displayed on display 260, and the user input interface receives the user input commands through the Graphical User Interface (GUI). Alternatively, the user may input the user command by inputting a specific sound or gesture, and the user input interface receives the user input command by recognizing the sound or gesture through the sensor.

In some embodiments, a "user interface" is a media interface for interaction and information exchange between an application or operating system and a user that enables conversion between an internal form of information and a form that is acceptable to the user. A commonly used presentation form of the User Interface is a Graphical User Interface (GUI), which refers to a User Interface related to computer operations and displayed in a graphical manner. It may be an interface element such as an icon, a window, a control, etc. displayed in a display screen of the electronic device, where the control may include at least one of an icon, a button, a menu, a tab, a text box, a dialog box, a status bar, a navigation bar, a Widget, etc. visual interface elements. In some embodiments, the user interface 280 is an interface that can be used to receive control inputs (e.g., physical buttons on the body of the smart control device, or the like).

Fig. 4 illustrates a software configuration diagram in the intelligent control device 200 according to some embodiments. Referring to fig. 4, in some embodiments, the system is divided into four layers, which are an Application (Applications) layer (abbreviated as "Application layer"), an Application Framework (Application Framework) layer (abbreviated as "Framework layer"), an Android runtime (Android runtime) and system library layer (abbreviated as "system runtime library layer"), and a kernel layer from top to bottom.

In some embodiments, at least one application program runs in the application program layer, and the application programs may be windows (windows) programs carried by an operating system, system setting programs, clock programs or the like; or an application developed by a third party developer. In particular implementations, the application packages in the application layer are not limited to the above examples.

The framework layer provides an Application Programming Interface (API) and a programming framework for the application. The application framework layer includes a number of predefined functions. The application framework layer acts as a processing center that decides to let the applications in the application layer act. The application program can access the resources in the system and obtain the services of the system in execution through the API interface.

As shown in fig. 4, in the embodiment of the present application, the application framework layer includes Managers (Managers), providers (Content providers), a network management system, and the like, where the Managers include at least one of the following modules: an Activity Manager (Activity Manager) is used for interacting with all activities running in the system; the Location Manager (Location Manager) is used for providing the system service or application with the access of the system Location service; a Package Manager (Package Manager) for retrieving various information related to an application Package currently installed on the device; a Notification Manager (Notification Manager) for controlling display and clearing of Notification messages; a Window Manager (Window Manager) is used to manage the icons, windows, toolbars, wallpapers, and desktop components on a user interface.

In some embodiments, an operating system is configured in the display device, and in order to obtain a richer functional experience provided by the operating system, the operating system generally needs to be used after logging in a system account. With the popularization of smart devices, a plurality of smart devices may exist in a user's home, such as a smart remote controller, a television, a refrigerator, an air conditioner, and the like.

In order to obtain rich functional experience, each device needs to log in the back of a user account to meet the optimal use requirement. The login method commonly adopted at present is that each device needs to log in an account independently, for example, a user actively scans a two-dimensional code on each device to log in. Therefore, the SSO (single sign on) method needs to actively trigger different devices to log in an account based on a user. The login mode is not convenient enough, so that the login efficiency is low, and the user experience is not good.

In order to improve user experience, the intelligent equipment can automatically log in the home environment under the condition that no human intervention exists among different equipment. Therefore, when multiple devices cooperatively log in an account, after one display device logs in the account, other display devices also automatically log in the same account, which provides convenience for users and improves the user experience.

Therefore, when a user logs in an account on only one device, the account can automatically log in on the device which the user wants to log in according to habits defined by the user, and the intelligent login is achieved while the user interaction experience is improved.

The embodiment of the invention provides a display device, which is a main device, namely a device for firstly performing account login. The display device includes: a display configured to present a user interface; a controller connected to the display. In order to realize the login of the collaborative account among the multiple devices, a pairing relationship needs to be established between the display devices in the home environment, and for this purpose, the controller is further configured to execute the following steps:

and step 01, starting the Bluetooth module configured at the local terminal.

For example, in the process of starting the system of the display device, the bluetooth module may be started along with the starting process, and the user may log in only after the system is started.

In some embodiments, the bluetooth module configured at the home terminal may also be started after the user logs in. For example, some terminal display devices may default to turning off the bluetooth function, so that the terminal display devices may select to turn on the bluetooth function and then start the bluetooth module configured at the home terminal at any time before or after the user logs in through a setting menu.

And 02, establishing a pairing relation with the slave device based on the Bluetooth module to perform data transmission with the slave device through the Bluetooth module, wherein the Bluetooth module configured by the slave device is in a starting state, the slave device is registered with a monitoring token event, and the monitoring token event is used for realizing the monitoring of the slave device on the token event sent by the master device.

Each display device in the home environment is configured with a bluetooth module, generally, in the networking state of the internet of things, the bluetooth module is configured to be opened by default or to be forcibly opened, so that when each display device is initialized, the respective bluetooth module is started, and the display devices are connected with other devices in a pairing relationship through the bluetooth module. After the pairing connection is performed, data transmission can be performed between the devices. The data transmission includes communication data transmission for guaranteeing communication between the devices and token data transmission for receiving master token information sent by the master device for the slave device.

In some embodiments, the display device may also manually turn on or turn off the bluetooth function according to a requirement, after the bluetooth function is turned off, the display device cannot be connected with other devices through the bluetooth module in a pairing manner, and after the bluetooth function is turned on, the display device can be connected with other devices through the bluetooth module in a pairing manner.

It should be noted that the multi-device collaborative login is applicable not only to each display device existing in the home environment, but also to each display device existing in a place such as a classroom or a mall. Each display device meets the requirement of distance connection, or is located in the same local area network, and the like.

FIG. 5 illustrates an interaction diagram for multiple devices establishing a pairing relationship, according to some embodiments. Referring to the example shown in part (a) of fig. 5, when the master device is the smart television and the slave devices are the magic cube screen and the refrigerator screen, the bluetooth modules of the smart television, the magic cube screen and the refrigerator screen are sequentially started. In the above example, the magic cube screen is a portable intelligent device having a display screen and a bluetooth module, and the refrigerator screen is a refrigerator provided with the display screen and the bluetooth module.

In some embodiments, the Bluetooth pairing connection between the smart television and the magic cube screen, the Bluetooth pairing connection between the smart television and the refrigerator screen, and the Bluetooth pairing connection between the magic cube screen and the refrigerator screen are sequentially realized through respective Bluetooth modules.

In some embodiments, after completing pairing relationship connection among multiple devices, each device registers, in response to establishment of pairing connection, a monitoring token event for each connected display device, where the monitoring token event is used to implement monitoring of a token event sent by a master device, and the token event may be master token information sent by the master device.

In some embodiments, in a home environment, a display device which preferentially performs account login is a master device, and the rest of display devices which do not log in an account and can realize an automatic login function are slave devices.

In some embodiments, in order to improve system performance, monitoring of a token event of a master device by a slave device is only reserved, for example, if a user selects a smart television as the master device to perform the first account login, the token event of the smart television is cancelled, and the token event of a magic cube screen and a refrigerator screen is reserved, that is, the master device is not in a monitoring state, and other slave devices are all in the monitoring state. The master device not in the listening state has a function of receiving data and transmitting data, and the slave device in the listening state has only a function of receiving data and does not have a function of transmitting data.

However, since the bluetooth module can implement bidirectional communication between devices, the data type that the slave device in the listening state cannot send is token data, and the communication data can be normally transmitted. That is, after receiving the master token information sent by the master device and logging in the corresponding account, the slave device does not send token information to other devices in a connected state any more, but only sends related data such as bluetooth connection between the devices. The bluetooth connection between the slave device in the sniffing state and the other devices is not affected, for example, when a display device is newly started from the home environment and the bluetooth module of the device is in the start state, the slave device in the sniffing state can still perform bluetooth connection with the new device.

Because one device can send the master token information to other paired devices after logging in the account, the slave device in the monitoring state is only configured with the functions of receiving token data and communication data and sending communication data, but is not configured with the function of sending token data, so that the situation that one slave device sends the master token information to other slave devices after receiving the master token information sent by the master device to realize account login can be avoided, and further the situation that data transmission confusion occurs and the account login efficiency of other slave devices is influenced can be avoided. That is, each slave device may respond to the master token information and communication data transmitted by the master device that first logs in to the account, and respond to communication data transmitted by other slave devices without being able to transmit token information to other devices.

In some embodiments, if none of the three devices (the smart television, the magic cube screen, and the refrigerator screen) logs in to a certain account, after the three devices start the bluetooth module and perform bluetooth pairing connection with each other, all of the three devices register to monitor a token event respectively, and the three devices monitor each other. At this time, data transmission between the three devices is only normal communication data. And if one device preferentially performs account login and is determined as the master device, the monitoring token event of the device is cancelled and is switched to be not in a monitoring state. In this state, the device has a function of transmitting both communication data and token data. And the monitoring token events of the other two devices are reserved and determined as slave devices, and both the other two devices are continuously in a monitoring state, and the two devices only have a communication data transmission function. Therefore, it can be determined which device is the primary device of the prior login account based on the state change of the listening token event, and other devices are informed that the primary device of the login account already exists.

In some embodiments, the listening status of each display device may be switched in real-time based on the identity of the display device itself. For example, when the display device is used as a master device, the display device is not in a monitoring state; when the display device is used as a slave device, the display device is in a monitoring state.

In some embodiments, after each display device is paired and connected through its own bluetooth module, a user can preferentially log in an account on one of the display devices, and the other display devices can log in automatically, so as to achieve the purpose of cooperatively logging in an account by multiple devices.

In some embodiments, after each display device is paired and connected through its own bluetooth module, the other display devices can be automatically logged in according to the account login information on one display device, so as to achieve the purpose of cooperatively logging in accounts by multiple devices. For example, when the bluetooth module is not turned on, that is, when the pairing connection is not established, if a certain display device preferentially logs in to the account, and then the bluetooth module is turned on to establish the pairing connection with other devices, the master device of the preferentially logged in account can still send token information to other slave devices based on the account login information, so that each slave device can conveniently realize automatic login. Namely, under the scene that a certain display device firstly logs in an account and then starts Bluetooth pairing, other slave devices which do not log in the account can still realize automatic login.

FIG. 6 illustrates a flow diagram of a multi-device collaborative login method performed by a master device, in accordance with some embodiments; FIG. 7 illustrates an interaction diagram of a multi-device collaborative login method according to some embodiments. Specifically, after completing the pairing connection, each display device implements a multi-device collaborative login account, that is, when the multi-device collaborative login method shown in fig. 6 and 7 is executed, the controller in the master device is configured to execute the following steps:

and S11, generating an account login request based on user login information generated by a user, and sending the account login request to a server, wherein the account login request is used for indicating the server to verify the user login information, and generating master token information after the verification is passed, and the master token information is used for realizing the purpose that the master device and the slave device login the specified account corresponding to the user login information.

In a home environment, there are typically multiple display devices, one of which may be selected by a user as the primary device for the account to be logged in first.

FIG. 8 illustrates a diagram of an interface for a primary device to log into an account, according to some embodiments. Referring to the interface shown in fig. 8 (a), one possible way for the primary device to implement account login is to present a login two-dimensional code in a display of the primary device, and after scanning the login two-dimensional code in the display through the intelligent terminal, the user displays a login interface on the intelligent terminal. And a user name input box and a password input box are presented in the login interface, a user inputs a user name in the user name input box, and a password is input in the password input box to obtain user login information so as to perform account login of the primary equipment. The intelligent terminal can be a mobile phone, a Pad and other equipment with a scanning function.

Another possible way for the primary device to implement account login is to directly present a login interface in a display of the primary device, and after the user inputs a user name and a password, obtain user login information to perform account login of the primary device. The two ways for the user to input the user login information may be determined according to actual situations, or may adopt other input ways, which are not limited herein.

Referring to the content shown in part (a) of fig. 7, the user login information includes a user name, a password, and the like, and the user login information corresponds to a specific account. After the user inputs the user login information on the intelligent terminal, in order to realize the login of the user login information corresponding to the specified account, the main equipment requests the server to check the user login information, and after the check is passed, the account login can be realized.

At this time, the master device generates an account login request based on user login information input by the user, and transmits to the server to access a login (login) interface of the server. After receiving the account login request sent by the main device, the server can check the user login information carried in the account login request. The account login request carries user login information, a user ID and a device ID, wherein the user ID is used for identifying a user, and the device ID is used for identifying a device for realizing account login.

The database in the server stores account information generated when a user registers an account, and the account information comprises a registration user name and a registration password. Therefore, during verification, the server compares the user name and the password in the user login information with the registered user name and the registered password stored in the database configured by the server, if the user name and the password are consistent, the user name and the password input by the user are accurate, and account login can be performed.

After the user login information is verified, in order to facilitate the account login of the main equipment terminal, the server immediately generates corresponding main Token information (Token information), wherein the Token is a string of numbers and comprises a user ID, an equipment ID, the account ID, a Token validity period and a time length. The primary token information is used for realizing login of a primary device and a secondary device to a specified account corresponding to the user login information, the user ID is used for identifying the user, the device ID is used for identifying the device for realizing the account login, the account ID is used for identifying the account (user name and password), the token validity period is the valid time period of the token, and the duration is the valid duration of the token. For example, token validity period is from 9/1/2021 to 9/3/2021, and the corresponding token duration is 3 days. And the time starting point of the token validity period is calculated from the time when the server verifies that the user login information passes.

The server checks and passes user login information based on an account login request sent by the main device, acquires a user ID and a device ID carried in the account login request, acquires the account ID corresponding to the account information from a server database, generates token validity period and duration, immediately generates main token information based on the user ID, the device ID, the account ID and the token validity period and duration, and returns the main token information to the main device to realize account login of the main device.

In some embodiments, if there is a new device that newly starts a bluetooth module to perform pairing connection after the account login of the master device, after the pairing connection with the new device, in response to the bluetooth connection with the new device, the master device requests the server to return master token information according to information of the logged account, where the master token information is information for updating only the token validity period and duration, and the rest of the content is unchanged.

S12, receiving primary token information generated by the server after the user login information passes the verification, and logging in a corresponding specified account based on an account ID in the primary token information, wherein the primary token information comprises the account ID used for identifying the account corresponding to the user login information.

The method comprises the steps that a main device receives main token information generated after a server verifies user login information and passes the user login information, the main token information comprises a user ID, a device ID, an account ID, token validity period, duration and the like, and the device ID is used for identifying the main device. Therefore, referring to the interface shown in fig. 8 (b), the primary device may perform account login based on the account ID in the primary token information, that is, perform login of a specific account based on the user name and password input by the user, and present a login success interface in the display.

And S13, sending the master token information to the slave equipment, wherein the master token information is used for indicating the slave equipment to request the slave token information from the server based on the master token information so as to log in a corresponding specified account based on the account ID in the slave token information, and the slave equipment refers to equipment in a pairing relationship with the master equipment.

In a home environment, after one display device firstly logs in an account, in order to realize automatic account login of other display devices in the home environment, after the main device realizes the login of a specified account or after Bluetooth connection is newly established between the main device and other slave devices, the main token information for realizing the login of the specified account is automatically sent to each slave device through a Bluetooth module, and the slave devices refer to other display devices except the first display device for logging in the specified account in the home environment.

If five display devices exist in the home environment, the user selects the display device A as a master device to perform account login, and after the display device A finishes account login, the display device A sends master token information to the display device B, the display device C, the display device D and the display device E through the Bluetooth module, wherein the display device B, the display device C, the display device D and the display device E are all slave devices.

After receiving the master token information sent by the master device through the bluetooth module, each slave device can request the slave token information from the server based on the master token information, so as to log in a specified account corresponding to the user login information based on the account ID in the slave token information. At the moment, the main device and the slave device log in the same designated account, so that the user can automatically log in other devices of a family after logging in on one device, the user can log in conveniently, and the use experience of the user is improved.

The content in the master token information and the content in the slave token information are different except that the user ID and the account ID are the same, namely the equipment ID, the token validity period and the duration are updated. The specific implementation process of the slave device automatically logging in the same specified account based on the master token information sent by the master device may refer to the contents of steps S21 to S23 provided in the subsequent embodiments, which is not described herein again.

In some embodiments, after each display device completes account login, the account is typically automatically logged out after a period of time, for example, the token expiration date is expired, and then the corresponding display device needs to log in the account again when the user uses the device later.

The account number of the display device logging in again can be a designated account number of the previous login or a second account number which needs to be logged in currently. For example, if a certain slave device logs in a specified account, and the slave device switches to log in a second account in subsequent login, the master device that logs in the specified account needs to be notified, and the master device is notified that the master device does not need to send primary token information corresponding to the specified account to the slave device.

To this end, upon switching the login account from the device, the controller is further configured to perform the steps of:

step 141, when the account logged in from the device is switched from the specified account to a second account, receiving a monitoring cancellation instruction generated by the slave device;

and step 142, responding to the interception canceling instruction, stopping sending the master token information to the slave equipment.

When the login account of the slave device is switched from the specified account to the second account, the slave device cancels token event monitoring on the master device which logs in the specified account, namely the slave device generates a monitoring canceling instruction and sends the monitoring canceling instruction to the master device which logs in the specified account.

And the master device does not send the master token information for logging in the specified account to the slave device any more after receiving the monitoring canceling instruction sent by the slave device, so that the slave device receives the master token information sent by the new master device for logging in the second account.

In some embodiments, when the primary device and the secondary device that log in the designated account in the first round need to log in the account again, each device is in a monitoring state. If the user selects another device to log in the second account, the primary device which originally logs in the designated account does not log in the account preferentially in the current round, so that the primary device does not serve as the primary device to send information, but serves as the secondary device. In this scenario, the newly switched slave device and other slave devices respond to token information sent by the device that preferentially logs in the second account in this round, so as to implement login of the second account.

In some embodiments, in the case that both the first round of master device and the slave device log in the designated account, if the user operates any one of the slave devices to change the login account to the second account, at this time, the slave device that logs in the second account serves as the master device that logs in with the second round of account, cancels the monitoring state of the first round of master device, switches to the non-monitoring state, and generates a monitoring cancellation instruction. Because two primary devices logging in different accounts exist in the scene, a second round of new primary devices (original first round of slave devices) switching account logging can send a monitoring canceling instruction to the first round of primary devices so as to inform the first round of primary devices that the first round of primary devices do not need to send primary token information of the first round to the new primary devices, and confusion is avoided.

And under the scene of logging in the second account, other slave devices (other slave devices in the first round) still receive the token information sent by the new master device, and at the moment, a prompt interface can be displayed in a display screen of the slave device for a user to select to continuously keep the state of logging in the originally specified account or switch to log in the second account. If a certain slave device generates an instruction for logging in a second account, the slave device generates a monitoring cancellation instruction and sends the instruction to the master device in the first round, the monitoring of the token information of the master device in the first round is cancelled, and at the moment, the slave device monitors the token information of the new master device in the second round, so that the automatic logging in of the second account is realized. If an instruction for continuously keeping the login state of the original specified account number is generated on a certain slave device, the slave device generates a monitoring canceling instruction and sends the monitoring canceling instruction to the new master device in the second round, the monitoring of the token information of the new master device in the second round is canceled, and at the moment, the slave device can continuously monitor the token information of the master device in the first round and continuously keep the login state of the specified account number.

In some embodiments, the display device logged into the second account may be another display device in the home environment. For example, when the account number of the first round is logged in, the display device a is a master device, the display device B and the display device C are slave devices, and all three display devices are logged in with a specified account number.

Since each device may have the condition of re-logging in the account, when logging in the account in the second round, the user selects the display device B to log in the second account, the identity of the display device B is changed from the original slave device to the master device, and the display device a and the display device C are slave devices. At this time, token information for logging in the second account is transmitted to the slave devices (display device a and display device C) by the display device B belonging to the master device identity, facilitating the display device a and the display device C to log in the second account.

After the display device B logs in the second account, the identity of the display device B is changed from the original slave device to the master device, so that in order to facilitate the display device B to send master token information to the remaining slave devices, the monitoring token event of the display device B is cancelled and is in a non-monitoring state, so that the display device B has functions of receiving data and sending data. And then, the monitoring token event of the display equipment A is recovered and is in a monitoring state, so that the display equipment A only has the functions of receiving communication data and token data, sending the communication data and does not have the function of sending the token data. At this time, the display device B is not in the monitor state, and both the display device a and the display device C are in the monitor state.

After receiving the primary token information sent by the display device B as the second-round primary device, the display device C as the slave device switches the account number logged in by operating the display device C from the original specified account number to the second account number. At this time, after the login account is sent and switched, the display device B and the display device C both correspondingly generate a monitoring cancellation instruction, send the monitoring cancellation instruction to the display device a of the original login designated account, inform the display device a originally serving as the first-round master device, and stop sending the master token information corresponding to the designated account to the original slave devices (the display device B and the display device C).

In some embodiments, the display device that logs in the second account may also be the original primary device, i.e., the primary device that originally logged in the designated account. At this time, the identities of the master device and the slave device are both in the original configuration condition, and then, when the login of the second account is switched, the login process of the specified account can be directly referred to, and each slave device does not need to cancel the monitoring token event, namely, does not need to generate a monitoring cancel instruction. In the process, the master device is always in the non-monitoring state, and each slave device is always in the monitoring state.

As can be seen, according to the display device provided by the embodiment of the present invention, when a master device serving as a first login account performs a multi-device collaborative login account, an account login request is generated based on user login information generated by a user, and is sent to a server, and master token information generated by the server after the user login information is verified is received, and a specific account corresponding to an account ID in the master token information is logged in, and meanwhile, the master token information is automatically sent to a slave device having a pairing relationship, so that the slave device requests the server for slave device information based on the master token information, and then logs in the same specific account based on the account ID in the slave device information. Therefore, after a user preferentially logs in an account on one display device, the rest display devices can log in automatically without manual login of the user, and the purpose of cooperatively logging in the account by multiple devices is achieved. The method and the device improve the user interaction experience while providing convenience for the user.

Fig. 9 illustrates a flow diagram of a multi-device collaborative login method performed from a device, in accordance with some embodiments. The display device provided by the embodiment of the invention is a slave device, namely a device for executing automatic account login based on the master token information sent by the master device. The display device includes: a display configured to present a user interface; a controller connected to the display, the controller being configured to perform the following steps when executing the multi-device collaborative login method shown in fig. 7 and 9:

s21, receiving master token information sent by a master device after the master device logs in a specified account based on user login information generated by a user, wherein the master token information refers to information generated by a server after the master device requests a server for verification based on the user login information, and the master token information comprises a user ID, an account ID, a token validity period and a time length.

In a home environment, the display devices are connected in a pairing mode through respective Bluetooth modules. When account login is performed, a user selects one of the display devices as a device for logging in an account first, and then the device is a primary device. When the master device logs in a designated account (such as an account A) based on user login information generated by a user, the master device requests for verification from the server and receives master token information generated after the server passes the verification, and then the master device logs in the designated account based on the master token information and automatically sends the master token information to each slave device.

After receiving the master token information sent by the master device, each slave device can automatically log in a corresponding specified account based on the master token information, so that the slave device and the master device log in the same account.

And S22, generating an automatic login request based on the slave device ID and the user ID, the account ID, the token validity period and the time length in the master token information, sending the automatic login request to the server, wherein the automatic login request is used for indicating the server to verify the slave device ID and the master token information, and generating slave token information based on the master token information after the verification is passed, and the slave token information comprises the user ID, the account ID, the slave token ID and the updated token validity period and time length.

Because each display device in the home environment realizes mutual pairing connection through the Bluetooth module, the initial Bluetooth passwords of a plurality of Bluetooth devices are generally 0000 or 1234, even some Bluetooth pairs do not need passwords, and only long pressing is needed, so that the display devices of other users are also connected to the home environment Internet of things of the home user through the Bluetooth modules of the display devices of the other users, the display devices of the other users can also automatically log in the account used by the home user, and information leakage is caused.

Therefore, when the slave device receives the master token information sent by the master device and performs account registration, the slave device needs to perform information verification on the server, and after the verification is passed, registration of a specified account can be performed. At this time, the slave device generates an automatic login request by using its own slave device ID and the user ID, account ID, token validity period, and duration in the master token information, and sends the automatic login request to the server.

And the server responds to the automatic login request sent by the slave equipment and verifies the slave equipment ID and the master token information carried by the automatic login request. Checking the contents includes checking whether the slave device allows automatic login, whether the slave device to perform automatic login is a preset device, and whether the master token information is valid. The preset device refers to a display device in the same home environment, such as a display device in the same internet of things. This is because television devices in the same internet of things generally belong to the same user.

In some embodiments, the preset device may also be a device bound with an account, for example, according to the account information in the slave device ID and the master token information, whether a binding relationship exists between the slave device ID and the account information is queried in a mapping relationship between a prestored account and a device, if so, the validity of the master token is determined, and if not, the device is rejected from automatic login. Therefore, the user equipment can bind the account and the equipment ID through initial login or other terminal setting, and further can prevent the non-user equipment from automatically logging in the account of the user when the non-user equipment exists in the local communication network connected with the Bluetooth.

The master token information comprises a user ID, a master device ID, an account ID, a token validity period and duration, wherein the master device ID is used for identifying the source of the master token information. Therefore, whether the slave device allows automatic login can be checked based on the user ID and the account ID, whether the slave device which needs automatic account login at present is a preset device is judged based on the slave device ID, and whether the master token information is valid is judged based on the token validity period and the duration. The three judgment processes can execute the next judgment process after the previous judgment process passes the verification, and the server can generate the slave token information after the three judgment processes pass the verification.

In some embodiments, when the server checks whether the slave device currently requesting for automatic account login is a preset device, another method may be further adopted: when the slave device uploads the master token information, the slave device ID is needed, after the server verifies that the slave device can realize the automatic account login function, the server analyzes account information from the master token information based on the account ID, and then obtains a device list bound or logged in by the account information. Judging whether the ID of the slave equipment is in the equipment list, if so, passing the verification, and then carrying out the main token information verification; if not, the slave device does not perform an auto-login process. Therefore, based on the comparison between the slave device ID and the device list of the logged-in account, if the slave device is the device of the other user, the device of the other user cannot log in the account originally, so that the device list cannot have the identifier of the device of the other user, and therefore, the comparison is not passed, and the automatic login of the account on the outsider device caused by the Bluetooth connection of the outsider device can be avoided. In this scenario, in order to enable the device list to have the identifier of each display device in the home internet of things, a user needs to actively log in an account in new devices once, so that the device ID of the new device is added to the device list corresponding to the account in the server.

After the server checks that the slave device can execute an automatic login process based on the master token information, the slave device is a preset device, and the master token information is valid, the verification of the master token information can be determined to be passed. The specific implementation process of the server performing the master token information verification may refer to steps S31 to S32 and related contents provided in the subsequent embodiments, which are not described herein again.

After the server verifies that the master token information carried in the automatic login request sent by the slave device passes the verification, the server generates slave token information for realizing the login of the specified account number by the slave device. The slave token information is obtained after being updated based on the master token information sent by the master device, and the slave device is used for account login, and the slave device and the master device need to login the same designated account. Therefore, the user ID and the account ID in the primary token information sent by the master device do not need to be updated, and the device ID for identifying the slave device and the token validity period and duration for the slave device to log in within the time limit need to be updated.

Updating the content comprises replacing the device ID of the original master device in the master token information with the device ID of the slave device, and updating the token validity period and the time length, so that the updated slave token information comprises the user ID, the slave device ID, the account ID, the new token validity period and the new time length. The time starting point of the validity period of the new token starts from the time when the server verifies that the master token information passes.

After the server verifies that the master token information carried in the automatic login request sent by the slave device passes, the slave token information generated synchronously is returned to the slave device, so that the slave device can conveniently log in the specified account based on the slave token information.

And S23, receiving slave token information generated after the slave device ID and the master token information are verified by the server, and logging in a corresponding specified account based on the account ID in the slave token information.

In a home environment, after one display device firstly logs in an account, in order to realize automatic account login of other display devices in the home environment, the master device can automatically send master token information for realizing the login of the specified account to other slave devices through the Bluetooth module after realizing the login of the specified account, and the slave devices refer to other display devices except the first login specified account in the home environment.

After the slave token information returned by the server is received by the slave device, the slave token information comprises a user ID, a slave device ID, an account ID, a new token validity period and new duration, namely, a specified account corresponding to the account ID can be logged in based on the slave token information, and the specified account is the same as the specified account logged in by the master device.

Referring to the content shown in parts (b) and (c) of fig. 7, when the master device is a smart television and the slave devices are a magic cube screen and a refrigerator screen, the smart television respectively sends master token information required when logging in a specified account (such as the account a) to the magic cube screen and the refrigerator screen through the bluetooth module, and then the magic cube screen (or the refrigerator screen) requests the server through the master token information to exchange slave token information required when logging in the account by the device. After receiving the slave token information returned by the server, the magic cube screen (or the refrigerator screen) can realize the login of the specified account. At this time, the smart television, the magic cube screen and the refrigerator screen all log in to the same account A, and the difference is that the smart television is a user manual login account, and the magic cube screen and the refrigerator screen are automatic login accounts and do not log in manually by the user.

As can be seen, in the display device provided in the embodiment of the present invention, when a slave device serving as an automatic login account performs a multi-device collaborative login account, the slave device receives master token information sent by a master device, generates an automatic login request, and sends the automatic login request to a server, after the master token information is verified by the server and passes, slave token information is generated based on slave device information, and the slave device logs in the same specified account with the master device based on the slave token information. Therefore, after a user preferentially logs in an account on one display device, the rest display devices can log in automatically without manual login of the user, and the purpose of cooperatively logging in the account by multiple devices is achieved. The user interaction experience is improved while convenience is provided for the user.

In some embodiments, after the primary device and the secondary device complete one account login, the corresponding token information is cached. After the main device realizes the login of the specified account number based on the user login information generated by the user, the main device stores corresponding main token information in a local cache of the main device; after the slave device realizes automatic login of a specified account based on the master token information sent by the master device, the slave device stores the corresponding slave token information in the local cache of the slave device.

The token information is cached, so that the login of the corresponding account can be performed by directly utilizing the token information in the cache in the subsequent login process. Thus, after completing one account login, the controller is further configured to: and after the same appointed account is logged in with the main equipment, caching slave token information returned by the server for realizing the login of the appointed account.

After the slave device logs in the corresponding same specified account based on the master token information sent by the master device, the slave token information returned by the server for realizing the login of the specified account is stored in a local cache of the slave device.

Referring to the content shown in part (b) of fig. 5 again, when the primary device (smart television) logs in the account a, the smart television respectively sends the primary token information corresponding to the account a to the secondary devices (the magic cube screen and the refrigerator screen). And after receiving the master token information corresponding to the account A, the magic cube screen and the refrigerator screen exchange the slave token information of the magic cube screen and the refrigerator screen for the server, and then the automatic login of the account A is realized based on the slave token information. After the magic cube screen and the refrigerator screen log in the account A, the slave token information for realizing the login of the account A is stored in respective local caches.

In some embodiments, after a period of time after each display device completes an account login, the account typically automatically logs out. Then the corresponding display device is required to re-log in the account upon subsequent use by the user.

The account number of the display device logging in again can be a designated account number of the previous login or a second account number which needs to be logged in currently, and the second account number is different from the designated account number.

In order to judge whether the received primary token information from the primary device is primary token information corresponding to the original specified login account when the secondary device logs in the account subsequently, the secondary device needs to compare the received new primary token information with secondary token information used for logging in the specified account in a local cache when receiving new primary token information, and determines whether the current account needing to be logged in is the original specified login account or not according to a comparison result, and determines the current target account needing to be logged in.

In some embodiments, upon a subsequent re-login to the account, the controller is further configured to perform the steps of:

and 241, when receiving the second token information sent by the master device, judging whether slave token information required for logging in the specified account exists in the local cache.

And 242, if the slave token information does not exist in the local cache, logging in a corresponding second account based on the second token information.

And 243, if the slave token information exists in the local cache, comparing whether the account ID in the slave token information is consistent with the account ID in the second token information.

And 244, if the account IDs are in accordance with each other, logging in the specified account corresponding to the account ID based on the second token information.

And step 245, if the account ID comparison is inconsistent, logging in a corresponding target account based on the selection operation of the user, wherein the target account comprises one of a specified account or a second account.

And when the slave equipment receives second token information sent by the master equipment, obtaining whether slave token information corresponding to the account before login is stored in a local cache. In the process of logging in the account later, the second token information refers to second token information sent by the host device, the first token information may be master token information used for logging in a specified account, and the second token information may be token information used for logging in other accounts.

In some embodiments, if the slave token information for logging in the specified account is not acquired in the local cache of the slave device, which indicates that the account login process of the current slave device is the first account login process, the received second token information is the first master token information sent by the master device. In this case, the slave device may log in the second account corresponding to the second token information after exchanging its own slave token information for the server based on the second token information.

In this scenario, the second token information received by the slave device from the master device is the first master token information received by the slave device (i.e., sent by the master device), and the slave device has not yet performed the post-account number login process, that is, the slave device has not yet stored the slave token information in the local cache.

Therefore, the process of determining whether the slave token information exists in the local cache may be applied to the process of step S21, that is, when the slave device receives the master token information sent by the master device, the slave device determines whether the slave token information required for logging in the specified account exists in the local cache. And when judging that the slave token information does not exist in the local cache, continuing to execute the processes of the steps S22 to S23 to complete the account login process for the first time. That is, the process of the slave device logging in the second account based on the second token information may refer to the implementation contents of steps S21 to S23, which are not described herein.

In some embodiments, if the slave token information for logging in the specified account can be obtained in the local cache of the slave device, it indicates that the current account login process of the slave device is the nth login process, that is, the slave device has performed N-1 account login processes, and belongs to the post-login account process. Then the received second token information is the nth master token information sent by the master device, and N is greater than or equal to 2.

When the slave token information exists in the local cache of the slave device, whether the slave device needs to perform account switching login is needed to be judged, that is, whether a second account corresponding to the second token information and a specified account corresponding to the slave token information are the same account is judged. At this time, the comparison of judging whether the accounts are the same can be realized through the account ID.

If the account ID in the slave token information is consistent with the account ID in the second token information in comparison, it is indicated that the master device corresponding to the second token information received by the current slave device is the same as the master device corresponding to the master token information received in the previous account login process, and the accounts needing to be logged in are also the same and are all designated accounts, and account switching login is not needed.

At this time, the slave device can directly log in the specified account based on the slave token information in the local cache without exchanging new slave token information for the server based on the second token information again. The reason is that the slave device exchanges new slave token information with the server based on the second token information, and the new slave token information is the same as the slave token information in the local cache, and account login is directly performed based on the slave token information in the local cache, so that account login efficiency can be improved.

However, since the token validity period and duration from the token information are used to characterize the validity of the corresponding token information. If the token validity period and the duration represent that the slave token information in the local cache is invalid, the slave device needs to exchange new slave token information for the server based on the second token information and then perform the specified account login.

If the account ID in the slave token information is inconsistent with the account ID in the second token information in comparison, the account which needs to be logged in currently is different from the specified account corresponding to the slave token information, and account switching login needs to be performed. At this time, since the second account currently required to be logged in by the slave device is different from the account in the local cache, a corresponding target account needs to be logged in based on a selection operation of the user, where the target account includes one of a specified account and the second account.

In some embodiments, the controller is further configured to, if the account ID comparison is inconsistent, log in the corresponding target account based on a selection operation of the user:

and 2451, when the account ID comparison is inconsistent, generating a prompt interface, and displaying the prompt interface in the user interface, wherein the prompt interface comprises a specified account option corresponding to the slave token information and a second account option corresponding to the second token information.

Step 2452, in response to the login instruction of the user triggering the designated account option, login to the corresponding designated account based on the slave token information.

Step 2453, in response to the login instruction that the user triggers the second account option, logging in the corresponding second account based on the second token information.

When the slave device needs to perform account switching login, at this time, the user is required to perform selection operation. In order to facilitate the slave device to log in the account in time, when the account ID corresponding to the second token information is inconsistent with the account ID stored in the local cache of the slave device, a prompt interface is presented in the display of the slave device.

FIG. 10 illustrates a schematic diagram of presenting a reminder interface from a device, according to some embodiments. Referring to part (c) of fig. 5 and fig. 10, when the account ID comparison is inconsistent, the specified account option and the second account option are presented in the prompt interface. The specified account option is used for realizing login of the specified account corresponding to the token information, and the second account option is used for realizing login of a second account (such as account B) corresponding to the second token information.

If the user still wants to log in the designated account before the device logs in, the designated account option is triggered, and meanwhile a corresponding login instruction is generated. And the slave equipment logs in the corresponding specified account according to the slave token information in the local cache based on the login instruction. Since the slave token information in the local cache of the slave device is the slave token information required by the previous slave device for requesting the server to exchange the self login account number based on the master token information, the slave token information can directly realize the login of the specified account number, and therefore, the slave device can directly login the specified account number based on the slave token information in the local cache without requesting the slave token information from the server.

However, if the token validity period and duration in the slave token information in the local cache indicate that the slave token information in the local cache has failed, the slave device needs to perform the specified account login after exchanging new slave token information from the user ID, the account ID and the slave device ID in the token information in the local cache, and the content updated in the new slave token information is the token validity period and duration.

And if the user wants to log in a new account from the equipment, triggering a second account option, and generating a corresponding login instruction at the moment. The slave device exchanges brand-new slave token information with the server according to the second token information based on the login instruction so as to login the second token information to login the corresponding second account (such as account B). The implementation process of the slave device logging in the corresponding second account based on the second token information may refer to the content of the foregoing steps S22 to S23, and details are not repeated here.

In some embodiments, if the slave device changes the login account number in the subsequent account login process, that is, the slave device is switched from the originally logged specified account number to the second account number, the master device logging in the specified account number needs to be notified, and the master device is informed that the master device does not need to send the master token information corresponding to the specified account number to the slave device.

Thus, when switching account logins from a device, the controller is further configured to perform the steps of:

step 251, when the logged account is switched from the specified account to the second account, generating a monitoring cancellation instruction, where the monitoring cancellation instruction is used to instruct the slave device to stop receiving the master token information sent by the master device.

And 252, sending the monitoring canceling instruction to the master equipment, and stopping receiving the master token information sent by the master equipment.

The scene that each display device executes account switching login includes a scene that the primary device and the secondary device of the first round login designated account need to log in the account again, and a scene that the user operates any secondary device to change the login account into a second account when the primary device and the secondary device of the first round login designated account both log in the designated account, and the like.

In some embodiments, when the primary device and the secondary device that log in the designated account in the first round need to log in the account again, each device is in a monitoring state. If the user selects another device to log in the second account, the primary device which originally logs in the designated account does not log in the account preferentially in the current round, so that the primary device does not serve as the primary device to send information, but serves as the secondary device. In this scenario, the newly switched slave device and other slave devices respond to token information sent by the device which preferentially logs in the second account in the current round, so as to realize the login of the second account.

In some embodiments, in the case that both the first round of master device and the slave device normally log in to the designated account, if the user operates any one of the slave devices to change the login account into the second account, at this time, the slave device that logs in to the second account serves as the master device that logs in to the second round of account, and cancels the monitoring state of the first round of master device, switches to the non-monitoring state, and generates a monitoring cancellation instruction. Because two primary devices logging in different accounts exist in the scene, a second round of new primary devices (original first round of slave devices) switching account logging can send a monitoring canceling instruction to the first round of primary devices so as to inform the first round of primary devices that the first round of primary devices do not need to send primary token information of the first round to the new primary devices, and confusion is avoided.

And the master device does not send the master token information for logging in the specified account to the slave device any more after receiving the monitoring canceling instruction sent by the slave device, so that the slave device receives the master token information sent by the master device for logging in the second account. For the related implementation process, reference may be made to the contents of steps 141 to 142 in the foregoing embodiments, and details are not repeated here.

In some embodiments, in a scenario where slave token information for logging in a specified account can be acquired in a local cache of a slave device, if the received second token information is consistent with an account ID of the slave token information in comparison, it indicates that a master device generating the second token information may be a master device that originally logged in the specified account.

If the account ID comparison is inconsistent, two situations exist, namely, the primary device which originally logs in the specified account switches to log in the second account, so that the primary device which generates the second token information is still the primary device which originally logs in the specified account. At this point, token listening need not be cancelled. And secondly, logging in the second account as another main device, and at the moment, switching the main device to ensure that the main device generating the second token information is switched to another display device, which is different from the main device originally logging in the specified account. At this point, token snooping needs to be cancelled. The foregoing contents may be referred to for corresponding implementation processes, which are not described herein in detail.

In some embodiments, in the foregoing embodiments, the process of determining, by the slave device, whether the slave token information exists in the local cache occurs in a scenario where the slave device receives the second token information, by determining whether the slave token information exists in the local cache and a result of comparing the second token information with an account ID of the slave token information, target token information required for account login is determined, and a target account to be logged in by the slave device is determined, so that account automatic login of the slave device is achieved.

In other embodiments, the process of the slave device determining whether the slave token information exists in the local cache may also occur in any scenario where the slave device is in a listening state, such as a re-automatic login process of a subsequent account login. At this time, the slave device does not need to trigger the judgment process after receiving the second token information sent by the master device, and as long as the slave device needs to log in the account again, the slave token information in the local cache can be read in real time to realize account login. For example, after each device logs in a specific account in the first round, if the specific account of the master device still logs in and the account of a certain slave device automatically logs out, at this time, the slave device logs in the specific account again, and under the condition that new token information sent by other master devices is not received, the slave token information can be directly obtained from the local cache of the slave device to realize the login of the specific account. And if the slave token information in the local cache fails, new slave token information needs to be exchanged to the server side again to realize the login of the specified account.

The specific implementation process can comprise the following steps: in the process of automatic account login, if the slave device needs to log in the account again, the slave device acquires login information from a local cache, wherein the login information is slave token information required for logging in a previous account.

If the local cache has no login information, continuing to monitor the event of token coming. And if a token event from the main equipment is received, automatically executing a corresponding account login process based on the main token information sent by the main equipment. If the local cache has the login information, the corresponding account can be directly logged in based on the login information, and the automatic login of the account is realized.

If new token information (such as second token information) is received, switching login information can be prompted through an interface when the account ID in the new token information is inconsistent with the account ID of the login information in the cache. The process can refer to the implementation contents of steps 243 to 245 and steps 2451 to 2453 in the foregoing embodiments, and will not be described herein again.

As can be seen, when the display device provided in the embodiment of the present invention performs a multi-device collaborative login account as a slave device of an automatic login account, in a later account login process, an implementation scenario may be as follows: and if the local cache does not have login information, monitoring an event coming from the token, and automatically logging in after receiving the event. And if the login information exists in the cache and the cache is not invalid, directly and automatically logging in. If the new token information is received, the account ID is inconsistent with the cached information, and the login information can be switched through interface prompt. Another implementation scenario may be: and when the slave equipment receives second token information sent by the master equipment, if the login information does not exist in the local cache, logging in the corresponding account based on the second token information. And if the login information exists in the local cache, and the account ID in the login information is in accordance with the account ID in the second token information, automatically logging in based on the login information in the cache. And if the account number contrast is inconsistent, switching login information can be prompted through an interface. Therefore, in the later account login process, the slave device can realize automatic login of the account based on the local cache so as to login the same account with the master device, and the purpose of cooperatively logging in the account by multiple devices is realized without manual login of a user. The user interaction experience is improved while convenience is provided for the user.

FIG. 11 illustrates a flow diagram of a multi-device collaborative login method performed by a server according to some embodiments. The embodiment of the invention provides a server, which comprises: a controller configured to perform the following steps when the multi-device collaborative login method shown in fig. 7 and 11 is executed:

s31, responding to an account login request which is sent by the master device and carries user login information, verifying the user login information, generating master token information after the verification is passed, sending the master token information to the master device, enabling the master device to log in a corresponding specified account based on an account ID in the master token information, and sending the master token information to the slave device, wherein the account ID is used for identifying the corresponding account after the user login information is verified.

In a home environment, a user wants to perform account login on a plurality of display devices, and based on the multi-device collaborative login method provided by the application, when performing account login, the user can perform manual account login on only one display device, and the rest display devices can all realize automatic account login.

The display equipment for manual account login of the user is the master equipment, and the rest display equipment for automatic account login is the slave equipment. The main device generates an account login request based on user login information input by a user, and sends the account login request to the server so as to access a login (login) interface of the server. After receiving an account login request sent by the main device, the server can check user login information carried in the account login request, wherein the user login information comprises a user name and a password. The account login request carries user login information, a user ID and a device ID, wherein the user ID is used for identifying a user, and the device ID is used for identifying a device for realizing account login.

During verification, the server compares the user name and the password in the user login information with the user name and the password stored in a database configured by the server, if the user name and the password are consistent, the user name and the password input by the user are accurate, and account login can be performed.

After the user login information is verified, in order to facilitate the account login of the main equipment terminal, the server immediately generates corresponding main Token information (Token information), wherein the Token is a string of numbers and comprises a user ID, an equipment ID, the account ID, a Token validity period and a time length. The primary token information is used for realizing login of a primary device and a secondary device to a designated account corresponding to the user login information, the user ID is used for identifying the user, the device ID is used for identifying the device for realizing account login, the account ID is used for identifying the account (user name and password) which passes the verification, the token validity period is the valid time period of the token, and the duration is the valid duration of the token.

After the primary device receives primary token information generated after the server verifies the user login information and passes the user login information, the primary device can perform corresponding account login based on the account ID in the primary token information, namely, login of a specified account is realized based on the user name and the password input by the user.

Meanwhile, in order to facilitate that other display devices in the home environment can automatically log in the account, the master device sends master token information to the slave device, the slave device is used for requesting slave token information from the server based on the master token information so as to log in a specified account corresponding to user login information based on an account ID in the slave token information, and the slave device is a device in a pairing relationship with the master device. The main device and the slave device log in the same designated account, so that the user can automatically log in other devices of a family after logging in on one device, the user can log in conveniently, and the use experience of the user is improved.

S32, responding to an automatic login request generated by the slave device based on the slave device ID after the slave device receives the master token information sent by the master device, verifying the slave device ID and the master token information carried in the automatic login request, generating slave token information based on the master token information after the verification is passed, and sending the slave token information to the slave device, wherein the master token information comprises a user ID, an account ID, a token validity period and a time length, the slave token information comprises the user ID, the account ID, the slave token ID and an updated token validity period and time length, so that the slave device can login a specified account based on the account ID in the slave token information, and the slave device is a device in a pairing relationship with the master device.

After each slave device receives the master token information sent by the master device, each slave device can request the server for slave token information based on the master token information, and automatically logs in a specified account corresponding to the specified ID in the slave token information, so that the slave device and the master device log in the same account.

When the slave device automatically logs in the same specified account based on the master token information sent by the master device, information authority verification needs to be carried out on the server, and the specified account can be logged in after the verification is passed. At this time, the slave device generates an automatic login request based on the master token information, and transmits the automatic login request to the server.

In order to avoid that display devices of other users are connected to the home environment internet of things of the home terminal user through the Bluetooth modules of the display devices of the other users, so that the display devices of the other users also automatically log in an account used by the home terminal user to cause information leakage, the slave devices requesting automatic login need to be checked, and therefore the slave devices ID needs to be carried in automatic login requests generated by the slave devices to identify the slave devices. At this time, the slave device generates an automatic login request by using its own slave device ID and the user ID, account ID, token validity period, and duration in the master token information, and sends the automatic login request to the server.

And the server responds to the automatic login request sent by the slave equipment and verifies the slave equipment ID and the master token information carried by the automatic login request. Checking the contents includes checking whether the slave device allows automatic login, whether the slave device to perform automatic login is a preset device, and whether the master token information is valid. The preset device refers to a display device in the same home environment, such as a display device in the same internet of things.

In some embodiments, the controller, in executing an automatic login request generated based on the slave ID after the slave device receives the master token information sent by the master device, checks the slave ID and the master token information carried in the automatic login request, and is further configured to execute the following steps:

step 321, in response to the automatic login request generated by the slave device based on the slave device ID after receiving the master token information sent by the master device, obtaining the account ID, the token validity period and the duration in the master token information.

Step 322, if a registered account ID for identifying a specified account for the master device to log in exists in the server, allowing the slave device to perform an automatic login process, and verifying whether a display device corresponding to the slave device ID is a preset device, where the preset device is a display device in the same internet of things for performing bluetooth pairing connection;

step 323, if the display device corresponding to the slave device ID is a preset device, checking whether the token validity period and duration are valid.

And step 324, if the token validity period and duration are valid, determining that the slave device ID and the master token information carried in the automatic login request sent by the slave device pass verification.

After receiving an automatic login request sent by any slave device, the server acquires the slave device ID, the user ID, the account ID, the token validity period and the time length carried in the automatic login request so as to check whether the slave device allows automatic login and check whether login information is valid.

When checking whether the slave device allows automatic login, comparing an account ID in the primary token information carried in an automatic login request sent by the slave device with a registered account ID stored by a server, wherein the registered account ID is used for identifying the account which the master device has logged in. If a certain account is logged in by the primary device, the server side stores corresponding account information, such as a logged-in ID. Therefore, if the server side stores the registered account ID, the account ID is consistent with the registered account ID in comparison, and the specified account corresponding to the account ID is logged in by the master device, and the slave device is allowed to respond to the token information of the master device, so that the automatic login of the corresponding account is realized. If the server side does not store the account ID, the comparison between the account ID and the registered account ID is inconsistent, and the specified account corresponding to the account ID is not logged in by the master device, so that the slave device is not allowed to execute the automatic account logging process.

The conditions for performing the auto-login procedure from the device include: responding to the primary token information sent by the primary device (namely, triggering the automatic account login of the secondary device by the primary device), and the primary device is already logged in the corresponding account.

When the server checks that the server stores the registered account ID which is in accordance with the account ID carried in the automatic login request, the specified account corresponding to the login of the primary device is indicated, and the automatic account login process of the secondary device is triggered by the primary device, so that the server can determine that the secondary device can allow the automatic login process.

After the slave device is allowed to perform the automatic login process, performing the next verification process, namely verifying whether the display device corresponding to the slave device ID is a preset device, wherein the preset device is a display device which is in the same Internet of things and performs Bluetooth pairing connection.

In some embodiments, when the server checks whether the slave device currently sending the automatic login request is a preset device, the server may compare the slave device ID of the slave device with an ID of a display device, which is stored in the server and is in the same internet of things as the master device for bluetooth pairing connection, and if the slave device ID is consistent with one of IDs of display devices in the same internet of things, it may be determined that the slave device is the preset device, and an automatic account login process may be performed. If the comparison is inconsistent, the slave device is the display device of other users, and the slave device cannot log in the same account with the display device of the home terminal user, so that information leakage is avoided, and a subsequent automatic account logging process cannot be executed.

In some embodiments, when the server checks whether the slave device currently requesting automatic account login is a preset device, another method may be further adopted: when the slave device uploads the master token information, the slave device ID is needed, after the server verifies that the slave device can realize the automatic account login function, the server analyzes account information from the master token information based on the account ID, and then obtains a device list bound or logged in by the account information. Judging whether the ID of the slave equipment is in the equipment list, if so, passing the verification, and then performing the verification of the master token; if not, the slave device does not perform an auto-login process. Therefore, based on the comparison between the slave device ID and the device list of the logged-in account, if the slave device is the device of the other user, the device of the other user cannot log in the account originally, so that the device list cannot have the identifier of the device of the other user, the comparison is not passed, and the automatic login of the account on the outsider device caused by the Bluetooth connection of the outsider device can be avoided. In this scenario, in order to enable the device list to have the identifier of each display device in the home internet of things, a user needs to actively log in an account in new devices once, so that the device ID of the new device is added to the device list corresponding to the account in the server.

After the display device corresponding to the slave device ID is verified to be the preset device, the next verification process can be carried out, namely whether the login information is valid or not is verified. At the moment, the token validity period and duration in the master token information carried by the automatic login request are obtained, so as to judge whether the master token information is valid or not based on the token validity period and duration.

And if the token validity period and the time length both meet the corresponding time conditions, determining that the token validity period and the time length both are valid. For example, if the token validity period has not expired and the generation duration of the master token information has not exceeded the duration threshold, it may be determined that both the token validity period and the duration are valid.

After the server checks that the slave device is allowed to automatically log in based on the master token information, the slave device is a preset device, and the login information (master token information) is valid, the slave device ID and the master token information carried in the automatic login request sent by the slave device can be determined to pass verification.

After verifying that the slave device ID and the master token information carried in the automatic login request sent by the slave device pass, the server generates slave token information for implementing the specified account login of the slave device. The slave token information is obtained after being updated based on the master token information sent by the master device, and the slave device is used for account login, and the slave device and the master device need to login the same designated account. Therefore, the user ID and the account ID in the primary token information sent by the master device do not need to be updated, and the device ID for identifying the slave device and the token validity period and duration for the slave device to log in within the time limit need to be updated.

After the slave device receives the slave token information returned by the server, the slave token information comprises a user ID, a slave device ID, an account ID, a new token validity period and new duration, namely a specified account corresponding to the account ID can be logged in based on the slave token information, and the specified account is the same as the specified account logged in by the master device.

As can be seen, when a plurality of display devices perform a collaborative login account, based on an account login request sent by a master device, a server according to an embodiment of the present invention generates master token information after user login information is verified, so that the master device can conveniently log in a specific account corresponding to the user login information, and automatically send the master token information to a slave device having a pairing relationship. And based on an automatic login request generated by the slave device according to the master token information, generating slave token information after the master token information is verified, and allowing the slave device to login an account, so that the slave device and the master device can conveniently login the same specified account based on the slave token information. Therefore, after a user preferentially logs in an account on one display device, the rest display devices can log in automatically without manual login of the user, and the purpose of cooperatively logging in the account by multiple devices is achieved. The user interaction experience is improved while convenience is provided for the user.

Fig. 6 illustrates a flow diagram of a multi-device collaborative login method performed by a master device, according to some embodiments. Referring to fig. 6, the present application further provides a multi-device collaborative login method, which is applied to a master device, and the method includes:

s11, generating an account login request based on user login information generated by a user, and sending the account login request to a server, wherein the account login request is used for indicating the server to verify the user login information, and generating master token information after the verification is passed, and the master token information is used for realizing that a master device and a slave device log in a specified account corresponding to the user login information;

s12, receiving primary token information generated by the server after the user login information passes the verification, and logging in a corresponding specified account based on an account ID in the primary token information, wherein the primary token information comprises the account ID used for identifying the account corresponding to the user login information;

and S13, sending the master token information to a slave device, wherein the master token information is used for indicating the slave device to request slave token information from a server based on the master token information so as to log in a corresponding specified account based on an account ID in the slave token information, and the slave device is a device in a pairing relationship with the master device.

Fig. 9 illustrates a flow diagram of a multi-device collaborative login method performed from a device, in accordance with some embodiments. Referring to fig. 9, the present application further provides a multi-device collaborative login method, applied to a slave device, where the method includes:

s21, receiving master token information sent by a master device after the master device logs in a specified account based on user login information generated by a user, wherein the master token information is information generated by a server after the master device requests a server for verification based on the user login information, and the master token information comprises a user ID, an account ID, a token validity period and a duration;

s22, generating an automatic login request based on a slave device ID and a user ID, an account ID, a token validity period and time length in the master token information, sending the automatic login request to a server, wherein the automatic login request is used for indicating the server to verify the slave device ID and the master token information, and generating slave token information based on the master token information after the verification is passed, and the slave token information comprises the user ID, the account ID, the slave token ID, the updated token validity period and time length;

s23, receiving slave token information generated after the slave device ID and the master token information of the server are verified, and logging in a corresponding specified account based on the account ID in the slave token information.

FIG. 11 illustrates a flow diagram of a multi-device collaborative login method performed by a server according to some embodiments. Referring to fig. 11, the present application further provides a multi-device collaborative login method, which is applied to a server, and the method includes:

s31, responding to an account login request which is sent by a master device and carries user login information, verifying the user login information, generating master token information after the verification is passed, sending the master token information to the master device, enabling the master device to log in a corresponding specified account based on an account ID in the master token information, and sending the master token information to a slave device, wherein the account ID is used for identifying the corresponding account after the user login information is verified;

s32, responding to an automatic login request generated by slave equipment based on a slave equipment ID after the slave equipment receives master token information sent by the master equipment, verifying the slave equipment ID and the master token information carried in the automatic login request, generating slave token information based on the master token information after the verification is passed, and sending the slave token information to the slave equipment, wherein the master token information comprises a user ID, an account ID, a token validity period and a time length, the slave token information comprises the user ID, the account ID, a slave token ID and an updated token validity period and a time length, so that the slave equipment logs in the specified account based on the account ID in the slave token information, and the slave equipment is equipment in a pairing relationship with the master equipment.

According to the technical scheme, the multi-device collaborative login method, the display device and the server provided by the embodiment of the invention have the advantages that the primary device which logs in the account firstly sends the account login request to the server based on the user login information generated by the user, the primary token information generated after the user login information is verified by the server is received, the specified account is logged in, and meanwhile, the primary token information is automatically sent to the slave device with the pairing relationship. The slave device generates an automatic login request based on the master token information and sends the automatic login request to the server, the slave token information is generated after the master token information is verified by the server, and the slave device is allowed to login an account, so that the slave device and the master device login the same specified account based on the slave token information. Therefore, according to the method, the display equipment and the server, after the user preferentially logs in the account on one display equipment, the rest display equipment can log in automatically without manual login of the user, and the purpose of cooperatively logging in the account by multiple devices is achieved. The method and the device have the advantages that convenience is provided for users, account login efficiency is high, and user interaction experience is improved.

In a specific implementation, the present invention further provides a storage medium, where the storage medium may store a program, and when the program is executed, the program may include some or all of the steps in each embodiment of the multi-device collaborative login method provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).

Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in the form of software products, which may be stored in storage media, such as ROM/RAM, magnetic disk, optical disk, and so on.

The same and similar parts in the various embodiments in this specification may be referred to each other. Especially, for the embodiment of the multi-device collaborative login method, since it is basically similar to the embodiment of the display device and the server, the description is relatively simple, and the relevant points can be referred to the description in the embodiment of the display device and the server.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and these modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present application.

The foregoing description, for purposes of explanation, has been presented in conjunction with specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the embodiments to the precise forms disclosed above. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles and the practical application, to thereby enable others skilled in the art to best utilize the embodiments and various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A display device, comprising:

a display configured to present a user interface;

a controller connected to the display, the controller configured to:

2. The display device of claim 1, wherein the controller is further configured to:

starting a Bluetooth module configured at the local terminal;

the method comprises the steps that a pairing relation is established between the Bluetooth module and the slave device, so that data transmission is carried out between the Bluetooth module and the slave device, wherein the Bluetooth module configured by the slave device is in a starting state, a monitoring token event is registered in the slave device, and the monitoring token event is used for realizing monitoring of the token event sent by the master device by the slave device.

3. The display device according to claim 1, wherein the controller is further configured to:

when the account logged in by the slave device is switched from the specified account to a second account, receiving a monitoring canceling instruction generated by the slave device;

and stopping sending the master token information to the slave equipment in response to the interception cancellation instruction.

4. A display device, comprising:

a display configured to present a user interface;

a controller connected with the display, the controller configured to:

5. The display device of claim 4, wherein the controller is further configured to:

after the same specified account is logged in with the primary device, caching slave token information returned by the server for realizing the login of the specified account.

6. The display device according to claim 5, wherein the controller is further configured to:

when second token information sent by the main equipment is received, judging whether slave token information required for logging in a specified account exists in a local cache or not;

if the slave token information does not exist in the local cache, logging in a corresponding second account based on the second token information;

if the slave token information exists in the local cache, comparing whether the account ID in the slave token information is consistent with the account ID in the second token information;

if the account ID comparison is consistent, logging in the specified account corresponding to the account ID based on second token information;

and if the account ID comparison is inconsistent, logging in a corresponding target account based on the selection operation of the user, wherein the target account comprises one of a designated account or a second account.

7. The display device according to claim 6, wherein the controller, in executing the logging in of the corresponding target account based on the selection operation of the user if the account ID comparison is inconsistent, is further configured to:

when the account ID comparison is inconsistent, generating a prompt interface, and displaying the prompt interface in a user interface, wherein the prompt interface comprises a specified account option corresponding to the slave token information and a second account option corresponding to the second token information;

responding to a login instruction of a user for triggering the designated account option, and logging in the corresponding designated account based on the slave token information;

and responding to a login instruction of a user for triggering the second account option, and logging in the corresponding second account based on the second token information.

8. The display device according to claim 7, wherein the controller is further configured to:

when the logged account is switched from the specified account to a second account, generating a monitoring canceling instruction, wherein the monitoring canceling instruction is used for indicating slave equipment to stop receiving master token information sent by the master equipment;

and sending the monitoring canceling instruction to the master equipment, and stopping receiving the master token information sent by the master equipment.

9. A server, comprising:

a controller configured to:

10. The server according to claim 9, wherein the controller, in executing the auto-login request generated based on a slave ID in response to the slave device after receiving the master token information sent by the master device, checks the slave ID and the master token information carried in the auto-login request, and is further configured to:

the method comprises the steps that after slave equipment receives master token information sent by master equipment, an automatic login request generated based on an ID of the slave equipment is responded, and an account ID, a token validity period and a duration in the master token information are obtained;

if the server has a registered account ID for identifying a specified account number for logging in by the master device, allowing the slave device to perform an automatic login process, and checking whether a display device corresponding to the slave device ID is a preset device, wherein the preset device is a display device which is in the same Internet of things and performs Bluetooth pairing connection;

if the display equipment corresponding to the slave equipment ID is preset equipment, checking whether the token validity period and the duration are valid;

and if the token validity period and the token duration are valid, determining that the slave equipment ID and the master token information carried in the automatic login request sent by the slave equipment pass verification.

11. A multi-device cooperative login method is applied to a main device, and is characterized by comprising the following steps:

and sending the master token information to a slave device, wherein the master token information is used for indicating the slave device to request slave token information from a server based on the master token information so as to log in a corresponding specified account based on an account ID in the slave token information, and the slave device is a device in a pairing relationship with the master device.

12. A multi-device cooperative login method is applied to a slave device, and is characterized by comprising the following steps:

generating an automatic login request based on a slave device ID and a user ID, an account ID, a token validity period and a time length in the master token information, and sending the automatic login request to a server, wherein the automatic login request is used for indicating the server to check the slave device ID and the master token information, and after the check is passed, slave token information is generated based on the master token information, and the slave token information comprises the user ID, the account ID, the slave token ID, the updated token validity period and the updated time length;

13. A multi-device collaborative login method is applied to a server, and is characterized by comprising the following steps: