Account management method and interaction system

Abstract

The invention discloses an account management method and an interaction system. The method comprises the following steps: displaying an account binding two-dimensional code; a binding notification from the cloud server is received, the binding notification is sent to the screen end device after the cloud server completes binding based on the binding request, and the binding request is reported to the cloud server after the application program obtains the unique identification by scanning the account binding two-dimensional code; under the condition that the main account number information exists, displaying prompt information about whether to switch the main account number or not; in response to a main account switching operation triggered by the user based on the prompt information, obtaining related information and token information of the login account from the cloud server, the token information being generated for the login account after the cloud server receives the binding request; and displaying the related information of the login account number, namely the main account number information, displaying the original main account number information as the auxiliary account number information, storing the token information of the login account number, and deleting the token information corresponding to the original main account number.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of display devices, in particular to an account management method and an interaction system. BACKGROUND

[0002] To facilitate user operation, more and more devices begin to be configured with display screens, such as washing machines, refrigerators, televisions, etc. After the account of a device and an application program are bound, the user can control the device by using the application program, which greatly improves the convenience of controlling the device. At present, the device only supports binding one account, which cannot meet the demand that the device can be controlled by multiple accounts, resulting in that the convenience of controlling the device is still limited. SUMMARY

[0003] The present application provides an account management method and an interaction system to solve the problem of the convenience of controlling a device.

[0004] In a first aspect, some embodiments provide an account management method applied to a screen-side device, and the method comprises:

[0005] In response to a trigger operation of opening an account binding two-dimensional code, the account binding two-dimensional code is displayed, and the account binding two-dimensional code contains a unique identifier of the screen-side device;

[0006] A binding notification from a cloud server is received, the binding notification is sent to the screen-side device by the cloud server after the cloud server completes binding based on a binding request, the binding request is reported to the cloud server by an application program after the application program obtains the unique identifier by scanning the account binding two-dimensional code, and the binding request contains the unique identifier and related information of a current login account of the application program;

[0007] In the case where there is already main account information, prompt information about whether to switch the main account is displayed;

[0008] In response to an operation of switching the main account triggered by the user based on the prompt information, related information and token information of the login account are obtained from the cloud server, and the token information is generated by the cloud server for the login account after the cloud server receives the binding request;

[0009] The related information of the login account is displayed as main account information, the original main account information is displayed as secondary account information, the token information of the login account is stored, and the token information corresponding to the original main account is deleted.

[0010] In a second aspect, some embodiments provide an account management method applied to an application program, and the method comprises:

[0011] The unique identifier of the screen-side device is obtained by scanning the account binding two-dimensional code; the account binding two-dimensional code is displayed by the screen-side device in response to a trigger operation of opening the account binding two-dimensional code;

[0012] A binding request is sent to the cloud server, the binding request containing the unique identifier and the related information of the current login account of the application program; after the cloud server completes the binding based on the binding request, a binding notification is sent to the screen-side device to indicate the screen-side device to display prompt information of whether to switch the main account in the case that the main account information already exists; in response to the operation of switching the main account triggered by the user based on the prompt information, the related information and token information of the login account are obtained from the cloud server, the token information being generated by the cloud server for the login account after receiving the binding request; the related information of the login account is displayed as the main account information, the original main account information is displayed as the secondary account information, the token information of the login account is stored, and the token information corresponding to the original main account is deleted.

[0013] In a third aspect, some embodiments provide an account management method applied to a cloud server, the method comprising:

[0014] A binding request reported by an application program is received, the binding request containing the unique identifier and the related information of the current login account of the application program; the binding request is reported by the application program to the cloud server after the application program obtains the unique identifier by scanning the account binding two-dimensional code, the account binding two-dimensional code being displayed by the screen-side device in response to a trigger operation of opening the account binding two-dimensional code;

[0015] After the cloud server completes the binding based on the binding request, a binding notification is sent to the screen-side device to indicate the screen-side device to display prompt information of whether to switch the main account in the case that the main account information already exists; in response to the operation of switching the main account triggered by the user based on the prompt information, the related information and token information of the login account are obtained from the cloud server, the token information being generated by the cloud server for the login account after receiving the binding request; the related information of the login account is displayed as the main account information, the original main account information is displayed as the secondary account information, the token information of the login account is stored, and the token information corresponding to the original main account is deleted.

[0016] In a fourth aspect, some embodiments provide an interactive system, comprising: a screen-side device, a cloud server, and an application program;

[0017] The screen-side device is configured to display the account binding two-dimensional code in response to a trigger operation of opening the account binding two-dimensional code, the account binding two-dimensional code containing the unique identifier of the screen-side device.

[0018] The application program is used to obtain the unique identifier by scanning the account binding two-dimensional code, report a binding request to the cloud server, and the binding request contains the unique identifier and the related information of the current login account of the application program;

[0019] The cloud server is used to send a binding notification to the screen device after completing the binding based on the binding request;

[0020] The screen device is used to display prompt information of whether to switch the main account in the case that the main account information already exists, obtain the related information and token information of the login account from the cloud server in response to the operation of switching the main account triggered by the user based on the prompt information, the token information being generated by the cloud server for the login account after receiving the binding request, display the related information of the login account as the main account information, display the original main account information as the secondary account information, store the token information of the login account, and delete the token information corresponding to the original main account.

[0021] The account management method and the interactive system, the screen device displays the account binding two-dimensional code in response to the triggering operation of opening the account binding two-dimensional code, the account binding two-dimensional code contains the unique identifier of the screen device, receives the binding notification from the cloud server, the binding notification being sent to the screen device by the cloud server after completing the binding based on the binding request, the binding request being reported to the cloud server by the application program after obtaining the unique identifier by scanning the account binding two-dimensional code, the binding request containing the unique identifier and the related information of the current login account of the application program, displaying prompt information of whether to switch the main account in the case that the main account information already exists, obtaining the related information and token information of the login account from the cloud server in response to the operation of switching the main account triggered by the user based on the prompt information, the token information being generated by the cloud server for the login account after receiving the binding request, displaying the related information of the login account as the main account information, displaying the original main account information as the secondary account information, and the token information corresponding to the login account being used for interaction with the cloud server. Multiple accounts can be bound, the demand that the screen device can be controlled by multiple accounts is met, device control is more convenient, and in the binding process, the user can switch the main account according to the actual demand, and the account management is more flexible and convenient. BRIEF DESCRIPTION OF DRAWINGS

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application;

[0024] Figure 2 This is a schematic diagram of the hardware configuration of a display device provided in some embodiments of this application;

[0025] Figure 3 This is a schematic diagram of the hardware configuration of the control device provided in some embodiments of this application;

[0026] Figure 4 This is a schematic diagram of the software configuration of a display device provided in some embodiments of this application;

[0027] Figure 5 A flowchart illustrating an account management method provided in some embodiments of this application;

[0028] Figure 6 A schematic diagram illustrating the account binding process provided in some embodiments of this application;

[0029] Figure 7 This application provides a schematic diagram of the account unbinding process for some embodiments. Figure 1 ;

[0030] Figure 8 This application provides a schematic diagram of the account unbinding process for some embodiments. Figure 2 ;

[0031] Figure 9 This is a schematic diagram illustrating the process of restoring factory settings provided in some embodiments of this application. Detailed Implementation

[0032] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.

[0033] It should be noted that the brief description of the terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of the application. Unless otherwise specified, these terms should be understood according to their ordinary and general meanings.

[0034] The terms "first", "second", "third" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean a specific order or sequence, unless otherwise noted. It should be understood that the terms used in this way can be interchanged under appropriate circumstances.

[0035] The terms "include" and "have" and any variations thereof are intended to cover but not exclusive inclusion, for example, a product or device including a series of components does not necessarily limit to all components clearly listed, but can include other components not clearly listed or inherent to these products or devices.

[0036] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic or combination of hardware or / and software code capable of performing functions related to the element.

[0037] In the embodiments of the present application, the display device 200 generally refers to a device with picture display and data processing capability. For example, the display device 200 includes but is not limited to smart television, mobile terminal, computer, monitor, advertising screen, wearable device, virtual reality device, augmented reality device, etc.

[0038] Figure 1 The schematic diagram of the operation scenario between the display device and the control device provided by some embodiments of the present application is shown. As shown in Figure 1 The user can operate the display device 200 through touch operation, mobile terminal 300 and control device 100. For example, the control device 100 can be a remote controller, a touch pen, a handle, etc.

[0039] The mobile terminal 300 can be used as a kind of control device for performing human-computer interaction between the user and the display device 200. The mobile terminal 300 can also be used as a kind of communication device for establishing communication connection with the display device 200 and performing data interaction. In some embodiments, the mobile terminal 300 can install software application with the display device 200, realize connection communication through network communication protocol, realize one-to-one control operation and data communication purpose. The audio and video content displayed on the mobile terminal 300 can also be transmitted to the display device 200 to realize synchronous display function.

[0040] As shown in Figure 1It is also shown that the display device 200 also communicates data with the server 400 through various communication modes. The display device 200 can be allowed to communicate through a local area network (LAN), a wireless local area network (WLAN) and other networks.

[0041] The display device 200 can provide a broadcast receiving television function, and can also provide an intelligent network television function of computer support function, including but not limited to, a network television, a smart television, an Internet protocol television (IPTV) and the like.

[0042] Figure 2 The display device 200 provided by some embodiments of the present application Figure 1 The hardware configuration block diagram of the display device 200 is shown in the figure.

[0043] In some embodiments, the display device 200 can include at least one of a tuning demodulator 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0044] In some embodiments, the detector 230 is used to collect signals of external environment or external interaction. For example, the detector 230 includes a light receiver for collecting ambient light intensity, or the detector 230 includes an image collector such as a camera, which can be used to collect external environment scenes, user attributes or user interaction gestures, or the detector 230 includes a sound collector such as a microphone, etc., for receiving external sound.

[0045] In some embodiments, the display 260 includes a display function component for presenting a picture, and a driving component for driving image display. The display 260 is used to receive image signals output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, components of a menu control interface and a user control UI interface, etc.

[0046] In some embodiments, the communication device 220 is a component for communicating with external devices or the server 400 according to various communication protocol types. The display device 200 can be provided with multiple communication devices 220 according to different supported communication modes. For example, when the display device 200 supports wireless network communication, the display device 200 can be provided with a communication device 220 containing WiFi function. When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 containing Bluetooth function.

[0047] The communication device 220 enables the display device 200 to communicate with external devices or the server 400 via wireless or wired connections. Wired connections utilize data cables, interfaces, or other components to connect the display device 200 to external devices. Wireless connections utilize wireless signals or wireless networks. The display device 200 can directly establish a connection with external devices or indirectly through gateways, routers, or other connection devices.

[0048] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and a first to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in memory. The controller 250 controls the overall operation of the display device 200.

[0049] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 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.

[0050] In some embodiments, a user can input user commands through a graphical user interface (GUI) displayed on a display 260, and the user input interface receives user input commands through the graphical user interface (GUI).

[0051] In some embodiments, the audio output device 270 can be a built-in speaker of the display device 200 or an external audio output device connected to the display device 200. For the external audio output device connected to the display device 200, the display device 200 may also be provided with an external audio output terminal, through which the audio output device can be connected to the display device 200 to output sound from the display device 200.

[0052] In some embodiments, the user input interface 280 can be used to receive instructions from user input.

[0053] Figure 3 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of the central control device. (Example) Figure 3 As shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0054] The control device 100 is configured to control the display device 200, and can receive the input operation instruction of the user, and convert the operation instruction into an instruction that the display device 200 can recognize and respond to, and play a role of an intermediary in the interaction between the user and the display device 200.

[0055] In some embodiments, the control device 100 can be a smart device. For example, the control device 100 can install various applications for controlling the display device 200 according to the user's needs.

[0056] In some embodiments, as shown in FIG. 3, the mobile terminal 300 or other smart electronic device can play a similar function of the control device 100 after installing the application for controlling the display device 200. Figure 1

[0057] The controller 110 includes a processor 112 and a RAM 113 and a ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation and operation of the control device 100, and the communication and cooperation between the internal components, and the data processing function of the external and internal.

[0058] The communication interface 130 realizes the communication of the control signal and the data signal between the display device 200 under the control of the controller 110. The communication interface 130 can include at least one of the WiFi chip 131, the Bluetooth module 132, the NFC module 133 and other near field communication modules.

[0059] The user input / output interface 140, wherein the input interface includes at least one of the microphone 141, the touchpad 142, the sensor 143, the key 144 and other input interfaces.

[0060] In some embodiments, the control device 100 includes at least one of the communication interface 130 and the input / output interface 140. The control device 100 is configured with a communication interface 130, such as a WiFi, Bluetooth, NFC module, which can encode the user input instruction through a WiFi protocol, or a Bluetooth protocol, or an NFC protocol, and send it to the display device 200.

[0061] The storage 190 is used to store the driving and control of the control device 100 under the control of the controller. Various running programs, data and applications. The storage 190 can store various control signal instructions input by the user.

[0062] The power supply 180 is used to provide operating power support for each element of the control device 100 under the control of the controller.

[0063] ​To perform user interactions, in some embodiments, the display device 200 can run an operating system. The operating system is a computer program for managing and controlling hardware resources and software resources in the display device 200. The operating system can provide a user interface to allow a user to interact with the display device 200 and support running various application programs.

[0064] It should be noted that the operating system can be a native operating system based on a specific operating platform, a third-party operating system deeply customized based on a specific operating platform, or an independent operating system specially developed for the display device.

[0065] The operating system can be divided into different modules or levels according to the implemented functions, for example, as shown in FIG. 1, in some embodiments, the system is divided into four layers, from top to bottom, the application layer (referred to as “application layer”), the application framework layer (referred to as “framework layer”), the system library layer, and the kernel layer. Figure 4

[0066] In some embodiments, the application layer is used to provide services and interfaces for application programs, so that the display device 200 can run application programs and interact with users based on the application programs. At least one application program can run in the application layer, which can be a window (Window) program, a system setting program, or a clock program provided by the operating system, or an application program developed by a third-party developer. In specific implementation, the application programs in the application layer are not limited to the above examples.

[0067] The framework layer provides application programming interfaces (APIs) and programming frameworks for application programs. The application framework layer includes some pre-defined functions. The application framework layer is equivalent to a processing center that decides which application program in the application layer to act. The application program can access the resources in the system and obtain the services of the system through the API interface in the execution.

[0068] As shown in FIG. 1, in some embodiments, the system library layer includes a system library, which is a collection of pre-written code that provides common functionality for use by applications. The system library layer is equivalent to a library that provides a set of functions that can be called from an application program. The system library layer provides a set of functions that can be called from an application program. Figure 4 ​As shown, the application framework layer in this embodiment includes a view system, managers, and content providers. The view system designs and implements the application's interface and interactions, and includes lists, grids, text boxes, and buttons. The managers include at least one of the following modules: an activity manager for interacting with all running activities in the system; a location manager for providing system services or applications with access to system location services; a package manager for retrieving various information related to application packages currently installed on the device; a notification manager for controlling the display and clearing of notification messages; and a window manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0069] In some embodiments, the Activity Manager manages the lifecycle of individual applications and common navigation and back functions, such as controlling application exit, opening, and back actions. The Window Manager manages all window programs, such as obtaining the screen size, determining if a status bar is present, locking the screen, capturing the screen, and controlling changes to the display window, such as shrinking the display window, shaking the display, or distorting the display.

[0070] In some embodiments, the system runtime library layer can provide support for the framework layer. When the framework layer is used, the operating system runs the instruction library contained in the system runtime library layer, such as the C / C++ instruction library, to implement the functions to be performed by the framework layer.

[0071] In some embodiments, the kernel layer is a functional layer situated between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. For example, ... Figure 4 As shown, hardware drivers can be configured in the kernel layer. The kernel layer can contain at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.

[0072] It should be noted that the above examples are only a simple division of the operating system function, and do not constitute a limitation on the specific operating system form of the display device 200 in the embodiments of the present application. According to the function of the display device, the type of the operating system, and other factors, the number and specific type of the levels contained in the operating system can be in other forms.

[0073] In some embodiments, an interactive system is provided, which includes a screen-side device, a cloud-side server and an application program. Through the interaction of the three, functions such as account binding, account unbinding and master account switching can be realized.

[0074] In some embodiments, an account management method is provided, which can be applied to a screen-side device. The method includes the following steps, as shown in Figure 5

[0075] Step 501, in response to a trigger operation of opening an account binding two-dimensional code, display the account binding two-dimensional code, which contains a unique identifier of the screen-side device.

[0076] Optionally, the user can perform a trigger operation of opening an account binding two-dimensional code on the screen-side device. In response to the trigger operation, the screen-side device will display the account binding two-dimensional code.

[0077] In a possible implementation, the screen-side device is provided with an account binding page. The user can operate the screen-side device to open the account binding page. The account binding page displays an account binding two-dimensional code.

[0078] Optionally, the account binding two-dimensional code contains the unique identifier of the screen-side device.

[0079] Step 502, receive a binding notification from the cloud-side server, the binding notification being sent to the screen-side device by the cloud-side server after completing binding based on binding information, the binding information being reported to the cloud-side server by the application program after obtaining the unique identifier by scanning the account binding two-dimensional code, the binding information containing the unique identifier and related information of the login account of the application program.

[0080] Optionally, the user can log in to the application program using a registered account, and then open the code scanning function of the application program to scan the above-mentioned account binding two-dimensional code. The application program will obtain the unique identifier of the screen-side device by scanning the above-mentioned account binding two-dimensional code.

[0081] Optionally, after obtaining the unique identifier of the screen-side device, the screen-side device reports a binding request to the cloud-side server, the binding request containing the unique identifier and related information of the current login account of the application program.

[0082] ​Optionally, the information related to the current login account of the application includes: an account and user information, the user information including a user ID, an email, a name, etc., and the embodiments of the present application do not limit this.

[0083] Optionally, after receiving the binding request, the cloud server completes the binding based on the binding request. Specifically, the cloud server can generate a set of binding data based on the information contained in the binding request for storage, thereby completing the binding. After completing the binding, the cloud server sends a binding notification to the screen device.

[0084] Step 503: In the case where the main account information already exists, display prompt information on whether to switch the main account.

[0085] Optionally, after receiving the binding notification, the screen device judges whether the main account information already exists, and if so, displays prompt information on whether to switch the main account.

[0086] Illustratively, the prompt information on whether to switch the main account can be displayed in the form of a pop-up window, a floating layer, a page, etc., and the embodiments of the present application do not limit this.

[0087] Step 504: In response to an operation on switching the main account triggered by the user based on the prompt information, obtain the information related to the login account and token information from the cloud server, the token information being generated by the cloud server for the login account after receiving the binding information.

[0088] Optionally, after seeing the above prompt information, the user can decide whether to switch the main account according to actual needs, and if so, can trigger an operation on switching the main account. In response to the triggering operation, the screen device can send an information obtaining request to the cloud server, and the cloud server returns the information related to the login account to the screen device after receiving the information obtaining request. The screen device can also send a token obtaining request to the cloud server, and the cloud server returns the token information generated for the login account to the screen device after receiving the token obtaining request.

[0089] Step 505: Display the information related to the login account as main account information, display the original main account information as secondary account information, store the token information of the login account, and delete the token information corresponding to the original main account.

[0090] Optionally, after receiving the information related to the login account and the token information, the screen device displays the information related to the login account as main account information, displays the original main account information as secondary account information, and deletes the token information corresponding to the original main account.

[0091] Optionally, the account in the primary account information is the primary account, and for the primary account, the data in the application and the data of the screen-side device are consistent. For example, the screen-side device is a refrigerator, and after the user logs in the application using the primary account, a plurality of recipes are added on the application, and the added recipes are also synchronized to the screen-side device. Similarly, after the user adds a plurality of recipes on the screen-side device, the recipes are also synchronized to the application when the user logs in the application using the primary account. The screen-side device only stores the token information corresponding to the primary account, and the token information can be used to interact with the cloud server to realize the synchronization of the data.

[0092] Optionally, the account in the secondary account information is the secondary account, and for the secondary account, after the user logs in the application using the secondary account, the user can control the screen-side device through the application, for example, the screen-side device is an air conditioner, and the user can adjust the temperature of the air conditioner through the application, but cannot synchronize the data with the screen-side device.

[0093] In the above embodiment, the screen-side device displays the account binding two-dimensional code in response to a trigger operation of opening the account binding two-dimensional code, and the account binding two-dimensional code contains a unique identifier of the screen-side device; receives a binding notification from the cloud server, the binding notification is sent to the screen-side device by the cloud server after completing the binding based on a binding request, the binding request is reported to the cloud server by the application after scanning the account binding two-dimensional code to obtain the unique identifier, and the binding request contains the unique identifier and related information of the current login account of the application; in the case where there is already primary account information, display prompt information whether to switch the primary account; in response to the operation of switching the primary account triggered by the user based on the prompt information, obtain the related information and token information of the login account from the cloud server, the token information is generated by the cloud server for the login account after receiving the binding request; display the related information of the login account as the primary account information, display the original primary account information as the secondary account information, and the token information corresponding to the login account is used to interact with the cloud server. Multiple accounts can be bound to meet the demand that the screen-side device can be controlled by multiple accounts, the device control is more convenient, and in the binding process, the user can switch the primary account according to the actual demand, and the account management is more flexible and convenient.

[0094] In some embodiments, the account management method provided by the embodiment of the application further includes: in the case where there is no primary account information, obtaining the related information and token information of the login account from the cloud server; displaying the related information of the login account as the primary account information, and the token information corresponding to the login account is used to interact with the cloud server.

[0095] As described above, after the screen terminal device receives the binding notification, it is determined whether the primary account information already exists. If not, the relevant information and token information of the login account are directly obtained from the cloud server. The relevant information of the login account is displayed as the primary account information, and the token information of the login account is stored. As described above, the token information corresponding to the login account is used for interaction with the cloud server.

[0096] In the above embodiment, there is no primary account information when initially binding. In this case, the relevant information and token information of the login account are directly obtained from the cloud server. The relevant information of the login account is displayed as the primary account information, and the token information of the login account is stored. This scanning two-dimensional code binding method greatly improves the account binding efficiency.

[0097] In some embodiments, the account management method provided by the embodiments of the present application further includes: in response to the operation of not switching the primary account triggered by the user based on the prompt information, obtaining the relevant information of the login account from the cloud server; and displaying the relevant information of the login account as secondary account information.

[0098] As described above, after the screen terminal device receives the binding notification, it is determined whether the primary account information already exists. If not, the relevant information and token information of the login account are directly obtained from the cloud server. The relevant information of the login account is displayed as the primary account information, and the token information of the login account is stored. As described above, the token information corresponding to the login account is used for interaction with the cloud server.

[0099] In the above embodiment, in the case where the user does not switch the primary account, the screen terminal device only obtains the relevant information of the login account from the cloud server, without obtaining the token information. This allows the user to switch the primary account according to actual needs during the binding process, and the account management is more flexible.

[0100] For example, refer to Figure 6As shown, the account binding process includes the following processes: 1, when the user binds the account for the first time, trigger to open the account binding two-dimensional code on the screen terminal device. 1.1, the screen terminal device generates and displays the account binding two-dimensional code. 2, after the user logs in to the APP using the account, scan the account binding two-dimensional code using the APP. 2.1, the APP reports a binding request to the cloud server. 2.1.1, after the cloud server receives the binding request, completes the device binding based on the binding request. 2.1.2, the cloud server sends a binding notification to the screen terminal device. 3, the screen terminal device obtains the related information of the login account (including user information) from the cloud server. 4, the screen terminal device obtains the token information of the login account from the cloud server. 5, the screen terminal device updates the UI according to the related information of the login account. 6, when the user binds the account again, trigger to open the account binding two-dimensional code on the screen terminal device. 6.1, the screen terminal device generates and displays the account binding two-dimensional code. 7, after the user logs in to the APP using another account, scan the account binding two-dimensional code using the APP. 7.1, the APP reports a binding request to the cloud server. 7.1.1, after the cloud server receives the binding request, completes the device binding based on the binding request. 7.1.2, the cloud server sends a binding notification to the screen terminal device. 7.1.2.1, the screen terminal device displays prompt information whether to switch the primary account. When the user triggers the operation of not switching the primary account, 8, obtain the related information of the login account from the cloud server. 9, the screen terminal device updates the UI according to the related information of the login account. When the user triggers the operation of switching the primary account, 10, the screen terminal device obtains the token information of the login account from the cloud server. 11, the screen terminal device obtains the related information of the login account (including user information) from the cloud server. 12, the screen terminal device updates the UI according to the related information of the login account.

[0101] In some embodiments, the account management method provided by the embodiments of the present application further includes: in response to the user triggering the operation of unbinding the target secondary account, sending an unbinding request to the cloud server, the unbinding request carrying the related information of the target secondary account; after receiving the unbinding success indication from the cloud server, deleting the secondary account information corresponding to the target secondary account on the user interface.

[0102] Optionally, the screen-side device is provided with an account unbinding page, and the account unbinding page displays main account information and secondary account information. The secondary account information can be one or multiple. The user can trigger an operation of unbinding a target secondary account on the account unbinding page. In response to the operation, the screen-side device sends an unbinding request to the cloud server, and the unbinding request carries relevant information of the target secondary account. After receiving the unbinding request, the cloud server deletes corresponding binding data, thus completing unbinding. After the cloud server completes unbinding, the cloud server sends an unbinding success indication to the screen-side device. After receiving the unbinding success indication, the screen-side device deletes secondary account information corresponding to the target secondary account on the user interface.

[0103] In the above embodiment, the specific implementation process of unbinding a secondary account is introduced. This method of supporting binding of multiple accounts meets the demand that the screen-side device can be controlled by multiple accounts.

[0104] In some embodiments, the account management method provided by the embodiment of the application further includes: in response to an operation of unbinding a main account triggered by a user, sending an unbinding request to the cloud server, and the unbinding request carries main account information; after receiving an unbinding success indication from the cloud server, deleting the main account information and corresponding token information in the absence of secondary account information; in the presence of one secondary account information, displaying a login two-dimensional code associated with the secondary account information, and after the application successfully logs in by scanning the login two-dimensional code, obtaining token information corresponding to the secondary account information from the cloud server; displaying the secondary account information as main account information and storing token information corresponding to the secondary account information; in the presence of multiple secondary account information, in response to target secondary account information selected by a user, displaying a login two-dimensional code associated with the target secondary account information, and after the application successfully logs in by scanning the login two-dimensional code, obtaining token information corresponding to the target secondary account information from the cloud server; displaying the target secondary account information as main account information and storing token information corresponding to the target secondary account information.

[0105] As described above, the screen-side device is provided with an account unbinding page, and the account unbinding page displays main account information and secondary account information. The user can trigger an operation of unbinding a main account on the account unbinding page. In response to the operation, the screen-side device sends an unbinding request to the cloud server, and the unbinding request carries main account information. After receiving the unbinding request, the cloud server deletes corresponding binding data, thus completing unbinding. After the cloud server completes unbinding, the cloud server sends an unbinding success indication to the screen-side device.

[0106] Optionally, after receiving the unbinding success indication, the screen-side device judges the secondary account information, and there are the following three kinds of judgment results: no secondary account information, one secondary account information, and multiple secondary account information.

[0107] In the case of no secondary account information, the primary account information and the corresponding token information are deleted.

[0108] In the case of one secondary account information, a login two-dimensional code associated with the secondary account information is displayed, the user logs in the application program using the secondary account in the secondary account information, scans the login two-dimensional code using the application program, the application program sends a login request to the cloud server, the screen-side device polls the login result, in the case of successful login, sends a request for obtaining token information to the cloud server, the cloud server generates a unique token information for the secondary account information, and returns the token information to the screen-side device. The screen-side device displays the secondary account information as the primary account information, and stores the token information corresponding to the secondary account information.

[0109] In the case of multiple secondary account information, the user can select one as the primary account, in response to the user selecting the target secondary account information, the screen-side device displays a login two-dimensional code associated with the target secondary account information, the user logs in the application program using the secondary account in the target secondary account information, and scans the login two-dimensional code using the application program, the application program sends a login request to the cloud server, the screen-side device polls the login result, in the case of successful login, sends a request for obtaining token information to the cloud server, the cloud server generates a unique token information for the target secondary account information, and returns the token information to the screen-side device. The screen-side device displays the target secondary account information as the primary account information, and stores the token information corresponding to the target secondary account information.

[0110] In the above embodiments, when the user triggers the unbinding of the primary account, if there is no secondary account information, the primary account information and the corresponding token information are directly deleted, if there is one secondary account information, it is directly set as the primary account information, and if there are multiple secondary account information, the user can select one as the primary account information, thereby improving the convenience of switching the primary account.

[0111] For example, referring to Figure 7As shown, the account unbinding process includes the following flow: 1, the user triggers the operation of unbinding the target secondary account. 1.1, the screen-side device reports the unbinding request to the cloud-side server. After the cloud-side server completes the unbinding, it sends an unbinding success indication to the screen-side device. 1.2, the screen-side device pulls the primary account information and secondary account information (including user information) from the cloud-side server again. 1.3, the screen-side device updates the UI according to the pulled information. 2, the user triggers the operation of unbinding the primary account. 2.1, the screen-side device reports the unbinding request to the cloud-side server. After the cloud-side server completes the unbinding, it sends an unbinding success indication to the screen-side device. In the case where there is no secondary account information, 3, delete the primary account information and the corresponding token information. 4, update the UI. In the case where there is one secondary account information, 5, display the login two-dimensional code associated with the secondary account information. 6, the user logs in to the application program using the secondary account in the secondary account information, and uses the application program to scan the login two-dimensional code. 6.1, the application program sends a login request to the cloud-side server. 7, the screen-side device polls the login result, and in the case of successful login, sends a request to the cloud-side server to obtain token information. 8, the screen-side device takes the secondary account information as the primary account information. 9, update the UI. In the case where there are multiple secondary account information, 10, display all secondary account information. 11, the user can select one secondary account information from them. In response to the user's selection of the target secondary account information, the screen-side device displays the login two-dimensional code associated with the target secondary account information. 12, the user logs in to the application program using the secondary account in the target secondary account information, and uses the application program to scan the login two-dimensional code. 12.1, the application program sends a login request to the cloud-side server. 13, the screen-side device polls the login result, and in the case of successful login, sends a request to the cloud-side server to obtain token information. 14, the screen-side device takes the target secondary account information as the primary account information. 15, update the UI.

[0112] In some embodiments, the user can trigger the unbinding of the account on the application program. Referring to Figure 8As shown, specifically includes the following flow: 1, the user triggers the operation of unbinding the target secondary account on the APP. 1.1, the APP reports the unbinding request to the cloud server. 1.1.1, after the cloud server completes the unbinding, sends the unbinding success notification to the screen device. 1.1.1.1, the screen device pulls the primary account information and secondary account information (including user information) from the cloud server again. 1.1.1.2, the screen device updates the UI according to the pulled information. 2, the user triggers the operation of unbinding the primary account on the APP. 2.1, the APP reports the unbinding request to the cloud server. 2.1.1, after the cloud server completes the unbinding, sends the unbinding success notification to the screen device. In the case where there is no secondary account information, 3, the screen device deletes the primary account information and the corresponding token information. 4, update the UI. In the case where there is one secondary account information, 5, the screen device displays the login two-dimensional code associated with the secondary account information. 6, the user logs in to the application using the secondary account in the secondary account information, and scans the login two-dimensional code using the application. 6.1, the application sends a login request to the cloud server. 7, the screen device polls the login result, and in the case of successful login, sends a request to the cloud server to obtain token information. 8, the screen device takes the secondary account information as the primary account information. 9, update the UI. In the case where there are multiple secondary account information, 10, display all secondary account information. 11, the user can select one secondary account information from it. In response to the user's selection of the target secondary account information, the screen device displays the login two-dimensional code associated with the target secondary account information. 12, the user logs in to the application using the secondary account in the target secondary account information, and scans the login two-dimensional code using the application. 12.1, the application sends a login request to the cloud server. 13, the screen device polls the login result, and in the case of successful login, sends a request to the cloud server to obtain token information. 14, the screen device takes the target secondary account information as the primary account information. 15, update the UI.

[0113] In some embodiments, the account management method provided by the embodiments of the application further includes: in the case where the screen device is connected to a network, in response to a trigger operation of restoring the factory settings, sending a request to unbind all accounts to the cloud server to instruct the cloud server to unbind all accounts; receiving the cloud server after unbinding all accounts Send the user interface to the factory interface.

[0114] Optionally, the screen-side device is provided with a related control for restoring factory settings, and the user can trigger the control to realize the restoration of factory settings. In response to the user's triggering operation on the control, in the case that the screen-side device is connected to the network, the screen-side device sends a request for unbinding all accounts to the cloud server, and the cloud server deletes all the binding data corresponding to the screen-side device after receiving the request, so as to complete the unbinding of all accounts. After the cloud server unbinds all accounts, it sends an unbinding success notification to the screen-side device, and the screen-side device restores the user interface to the factory interface after receiving the unbinding success notification.

[0115] In the above embodiment, the implementation manner of unbinding accounts in the case that the screen-side device is connected to the network is provided, and the unbinding process is fast and efficient.

[0116] In some embodiments, the account management method provided by the embodiments of the present application further includes: in the case that the screen-side device is not connected to the network, restoring the user interface to the factory interface in response to the triggering operation of the restoration of factory settings; and after being connected to the network, sending a request for unbinding all accounts to the cloud server to instruct the cloud server to unbind all accounts.

[0117] As described above, the screen-side device is provided with a related control for restoring factory settings, and the user can trigger the control to realize the restoration of factory settings. In response to the user's triggering operation on the control, in the case that the screen-side device is not connected to the network, the user interface is first restored to the factory interface, and after the network is restored, a request for unbinding all accounts is sent to the cloud server, and the cloud server deletes all the binding data corresponding to the screen-side device after receiving the request, so as to complete the unbinding of all accounts.

[0118] In the above embodiment, the implementation manner of unbinding accounts in the case that the screen-side device is not connected to the network is provided, and the unbinding process is fast and efficient.

[0119] For example, referring to Figure 9As shown, the process of restoring factory settings includes: 1, the user triggers to unbind all accounts on the screen terminal device. The screen terminal device sends a request to unbind all accounts to the cloud server. After the cloud server receives the request, it deletes all binding data corresponding to the screen terminal device to complete the unbinding of all accounts. After the cloud server unbinds all accounts, it sends a successful unbinding notification to the screen terminal device. 2, the screen terminal device receives the successful unbinding notification and restores the user interface to the factory interface. 3, the cloud server sends a message to the APP to notify the APP to unbind the account. In the case where the screen terminal device is not connected to the network, 4, the user triggers to restore the factory settings on the screen terminal device, and the screen terminal device restores the user interface to the factory interface. After the network is restored, 5, the screen terminal device sends a request to unbind all accounts to the cloud server. After the cloud server receives the request, it deletes all binding data corresponding to the screen terminal device to complete the unbinding of all accounts. 6, the cloud server sends a message to the APP to notify the APP to unbind the account.

[0120] In some embodiments, a method for managing an account is provided, which is applied to an application program, and the method comprises: scanning an account binding two-dimensional code to obtain a unique identifier of a screen terminal device; the account binding two-dimensional code is displayed by the screen terminal device in response to a trigger operation of opening the account binding two-dimensional code; sending a binding request to a cloud server, the binding request containing the unique identifier and related information of a current login account of the application program; after the cloud server completes the binding based on the binding request, sending a binding notification to the screen terminal device to indicate the screen terminal device to display prompt information of whether to switch a main account in the case where main account information already exists; in response to an operation of switching the main account triggered by a user based on the prompt information, obtaining the related information and token information of the login account from the cloud server, the token information being generated by the cloud server for the login account after receiving the binding request; displaying the related information of the login account as main account information, displaying the original main account information as secondary account information, storing the token information of the login account, and deleting the token information corresponding to the original main account. For details, see the foregoing, which will not be repeated here.

[0121] In some embodiments, a method for account management is provided, applied to a cloud server, the method comprising: receiving a binding request reported by an application, the binding request containing a unique identifier and information related to a current login account of the application; the binding request is reported by the application to the cloud server after the application obtains the unique identifier by scanning the account binding QR code; the account binding QR code is displayed by the screen device in response to a trigger operation of opening the account binding QR code; sending a binding notification to the screen device after completing the binding based on the binding request, to instruct the screen device to display prompt information whether to switch the main account in the case that there is already main account information; in response to the operation of switching the main account triggered by the user based on the prompt information, obtaining information related to the login account and token information from the cloud server, the token information is generated by the cloud server for the login account after receiving the binding request; displaying the information related to the login account as main account information, displaying the original main account information as secondary account information, storing the token information of the login account, and deleting the token information corresponding to the original main account. For details, see the foregoing, which will not be repeated here.

[0122] In some embodiments, an interactive system is provided, comprising: a screen device, a cloud server and an application; the screen device is used to display an account binding QR code in response to a trigger operation of opening the account binding QR code, the account binding QR code contains a unique identifier of the screen device; the application is used to obtain the unique identifier by scanning the account binding QR code, and report a binding request to the cloud server, the binding request contains the unique identifier and information related to a current login account of the application; the cloud server is used to send a binding notification to the screen device after completing the binding based on the binding request; the screen device is used to display prompt information whether to switch the main account in the case that there is already main account information; in response to the operation of switching the main account triggered by the user based on the prompt information, obtaining information related to the login account and token information from the cloud server, the token information is generated by the cloud server for the login account after receiving the binding request; displaying the information related to the login account as main account information, displaying the original main account information as secondary account information, storing the token information of the login account, and deleting the token information corresponding to the original main account. For details, see the foregoing, which will not be repeated here.

[0123] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit the present application; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can still be modified, or some or all of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

[0124] The foregoing description has been presented for the purpose of illustration and description. It is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or can be acquired from practice of the embodiments. The described embodiments were chosen and described in order to best explain the principles of the application and its practical application to thereby enable others skilled in the art to best use the application in various embodiments and with various modifications as are suited to the particular use contemplated.

Claims

1. An account management method, characterized by, The method applied to a screen terminal device comprises: In response to a trigger operation of opening an account binding two-dimensional code, the account binding two-dimensional code is displayed, and the account binding two-dimensional code contains a unique identifier of the screen terminal device; A binding notification is received from a cloud server, the binding notification is sent to the screen terminal device by the cloud server after the cloud server completes binding based on a binding request, the binding request is reported to the cloud server by an application program after the application program obtains the unique identifier by scanning the account binding two-dimensional code, and the binding request contains the unique identifier and related information of a current login account of the application program; In a case where main account information already exists, prompt information of whether to switch the main account is displayed; In response to an operation of switching the main account triggered by a user based on the prompt information, related information and token information of the login account are obtained from the cloud server, the token information is generated by the cloud server for the login account after the cloud server receives the binding request; The related information of the login account is displayed as the main account information, the original main account information is displayed as secondary account information, the token information of the login account is stored, and the token information corresponding to the original main account is deleted.

2. The method of claim 1, wherein, The method further comprises: In a case where main account information does not exist, related information and token information of the login account are obtained from the cloud server; The related information of the login account is displayed as the main account information, the token information of the login account is stored, and the token information corresponding to the login account is used for interaction with the cloud server.

3. The method of claim 1, wherein, The method further comprises: In response to an operation of not switching the main account triggered by a user based on the prompt information, related information of the login account is obtained from the cloud server, and the related information of the login account is displayed as secondary account information.

4. The method of claim 1, wherein, The method further comprises: In response to an operation of unbinding a target secondary account triggered by a user, an unbinding request is sent to the cloud server, the unbinding request carries related information of the target secondary account, and after a unbinding success indication is received from the cloud server, secondary account information corresponding to the target secondary account on a user interface is deleted.

5. The method of claim 1, wherein, The method further comprises: In response to an operation of unbinding the main account triggered by a user, an unbinding request is sent to the cloud server, the unbinding request carries main account information; After a unbinding success indication is received from the cloud server, in a case where secondary account information does not exist, the main account information and corresponding token information are deleted; In a case where one secondary account information exists, a login two-dimensional code associated with the secondary account information is displayed, after the application program successfully logs in by scanning the login two-dimensional code, token information corresponding to the secondary account information is obtained from the cloud server, the secondary account information is displayed as main account information, and the token information corresponding to the secondary account information is stored. In the presence of multiple sub-account information, in response to the target sub-account information selected by the user, the login two-dimensional code associated with the target sub-account information is displayed, and after the application successfully logs in by scanning the login two-dimensional code, the token information corresponding to the target sub-account information is obtained from the cloud server; the target sub-account information is displayed as the main account information, and the token information corresponding to the target sub-account information is stored.

6. The method of claim 1, wherein, The method further comprises: In the case of networking of the screen terminal device, in response to the trigger operation of restoring the factory settings, a request for unbinding all accounts is sent to the cloud server to instruct the cloud server to unbind all accounts; After receiving the unbinding success notification sent by the cloud server after unbinding all accounts, the user interface is restored to the factory interface.

7. The method of claim 1, wherein, The method further comprises: In the case that the screen terminal device is not connected to the network, in response to the trigger operation of restoring the factory settings, the user interface is restored to the factory interface; After networking, a request for unbinding all accounts is sent to the cloud server to instruct the cloud server to unbind all accounts.

8. An account management method characterized by comprising: Applied to an application program, the method comprises: Scanning an account binding two-dimensional code to obtain a unique identifier of a screen terminal device; the account binding two-dimensional code is displayed by the screen terminal device in response to a trigger operation of opening the account binding two-dimensional code; Sending a binding request to a cloud server, the binding request containing the unique identifier and related information of the current login account of the application program; after the cloud server completes the binding based on the binding request, sending a binding notification to the screen terminal device to instruct the screen terminal device to display prompt information whether to switch the main account in the case that there is already a main account information; in response to the operation of switching the main account triggered by the user based on the prompt information, obtaining the related information and token information of the login account from the cloud server, the token information being generated by the cloud server for the login account after receiving the binding request; displaying the related information of the login account as the main account information, displaying the original main account information as the sub-account information, storing the token information of the login account, and deleting the token information corresponding to the original main account.

9. An account management method characterized by comprising: Applied to a cloud server, the method comprises: Receiving a binding request reported by an application program, the binding request containing a unique identifier and related information of a current login account of the application program; the binding request is reported by the application program to the cloud server after the application program obtains the unique identifier by scanning an account binding two-dimensional code, and the account binding two-dimensional code is displayed by a screen terminal device in response to a trigger operation of opening the account binding two-dimensional code; After the binding is completed based on the binding request, a binding notification is sent to the screen-side device to indicate the screen-side device to display prompt information whether to switch the main account number in the case that the main account number information already exists; in response to the operation of switching the main account number triggered by the user based on the prompt information, the related information and token information of the login account are obtained from the cloud server, the token information is generated by the cloud server for the login account after the binding request is received; the related information of the login account is displayed as the main account number information, the original main account number information is displayed as the secondary account number information, the token information of the login account is stored, and the token information corresponding to the original main account number is deleted.

10. An interactive system, characterized by Comprise: A screen-side device, a cloud server and an application program; The screen-side device is configured to display an account binding two-dimensional code in response to a trigger operation of opening the account binding two-dimensional code, the account binding two-dimensional code containing a unique identifier of the screen-side device; The application program is configured to obtain the unique identifier by scanning the account binding two-dimensional code, report a binding request to the cloud server, the binding request containing the unique identifier and the related information of the current login account of the application program; The cloud server is configured to send a binding notification to the screen-side device after the binding is completed based on the binding request; The screen-side device is configured to display prompt information whether to switch the main account number in the case that the main account number information already exists; In response to the operation of switching the main account number triggered by the user based on the prompt information, the related information and token information of the login account are obtained from the cloud server, the token information is generated by the cloud server for the login account after the binding request is received; The related information of the login account is displayed as the main account number information, the original main account number information is displayed as the secondary account number information, the token information of the login account is stored, and the token information corresponding to the original main account number is deleted.

Images