Control right sharing method, terminal device and readable storage medium
By displaying a list of accounts to be shared on the terminal device and dragging and dropping device elements to achieve permission sharing, the cumbersome binding problem under multi-device control is solved, the operation process is simplified, and the efficiency of permission sharing is improved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- ECOFLOW INC
- Filing Date
- 2023-03-20
- Publication Date
- 2026-06-26
AI Technical Summary
In scenarios where different terminal devices jointly control energy storage devices, the device binding process in existing technologies is cumbersome, especially when multiple energy storage devices need to share control permissions, making the operation complex and tedious.
The terminal device displays a list of accounts to be shared. The user selects the target account and drags and drops device elements in the permission receiving window. The terminal device sends a declaration to the server to grant control permissions to the target account, and the server realizes permission sharing.
It simplifies the process of sharing device permissions, reduces the need to repeatedly add accounts for each device, and improves the efficiency of sharing permissions across multiple devices.
Smart Images
Figure CN116430773B_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of energy storage equipment technology, and in particular relates to a control access sharing method, terminal equipment and readable storage medium. Background Technology
[0002] As energy storage devices are widely used across various industries, the demand for their control is also increasing. Typically, after a terminal device is bound to an energy storage device, it can be remotely controlled via an application installed on that device. However, in practical applications, there may be scenarios where different terminal devices jointly control one or more energy storage devices. In such scenarios, each terminal device needs to be bound to each of these devices separately, making the binding process cumbersome. Summary of the Invention
[0003] In view of this, embodiments of this application provide a control permission sharing method, a terminal device, and a readable storage medium to solve the problem in the prior art that the implementation process is relatively cumbersome in scenarios where different terminal devices need to jointly control one or more energy storage devices.
[0004] A first aspect of this application provides a method for controlling permission sharing, applied to a terminal device. The terminal device is logged into a first account, and the first account has control permissions over the device to be shared. The method includes: displaying a first interface, the first interface including a target account; displaying a second interface, the second interface including a permission receiving window for the target account, in response to a selection operation of the target account; adding device elements of the target device to the permission receiving window in response to a preset operation; wherein the device to be shared includes the target device; and sending a first declaration to a server, the first declaration indicating that the target account is granted permission to control the target device.
[0005] A second aspect of this application provides a method for controlling permission sharing, applied to a server, the method comprising: receiving a first statement, the first statement indicating permission to grant a target account to control a target device; and granting the target account permission to control the target device according to the first statement.
[0006] A third aspect of this application provides a server configured to perform the method described in the second aspect.
[0007] A fourth aspect of this application provides a control permission sharing system, including a terminal device and a server. The terminal device is logged into a first account, which has control permissions over a target device. The terminal device is configured to execute the method described in the first aspect, and the server is configured to execute the method described in the second aspect.
[0008] A fifth aspect of this application provides a control permission sharing device applied to a terminal device. The terminal device is logged into a first account, and the first account has control permissions over a target device. The device includes: a first display unit for displaying a first interface, the first interface including the target account; a second display unit for displaying a second interface in response to a selection operation on the target account, the second interface including a permission receiving window for the target account; an adding unit for adding device elements of the target device to the permission receiving window in response to a preset operation; wherein the device to be shared includes the target device; and a sending unit for sending a first declaration to a server, the first declaration indicating that the target account is granted permission to control the target device.
[0009] A sixth aspect of this application provides a terminal device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method as described in any of the first aspects.
[0010] A seventh aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method as described in any of the first aspects.
[0011] The beneficial effects of the embodiments of this application compared with the prior art are:
[0012] The control permission sharing method provided in this application simplifies the device permission sharing process by simply adding the device element to the permission receiving window of the target account when it is necessary to share the device control permission with the target account. Attached Figure Description
[0013] To more clearly illustrate the technical solutions in the embodiments of this application, 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.
[0014] Figure 1 This is a schematic diagram of the structure of a control permission sharing system applicable to embodiments of this application, provided in one of the embodiments of this application.
[0015] Figure 2 This is a schematic diagram of the interaction flow of a control permission sharing method provided in an embodiment of this application;
[0016] Figure 3 This is a schematic diagram of the bound device list of the terminal device provided in the embodiments of this application;
[0017] Figure 4 This is a schematic diagram of the first interface provided in an embodiment of this application;
[0018] Figure 5 This is a schematic diagram of the initial list of accounts to be shared in the first interface provided in this application embodiment;
[0019] Figure 6 This is a schematic diagram illustrating a scenario of adding an account to be shared, provided in one embodiment of this application.
[0020] Figure 7 This is a schematic diagram illustrating a user selecting a target account, provided in an embodiment of this application.
[0021] Figure 8 This is a schematic diagram of a second interface provided in an embodiment of this application;
[0022] Figure 9 This is a schematic diagram of a second interface provided in another embodiment of this application;
[0023] Figure 10 This is a schematic diagram of a scenario for adding device elements to a target device according to an embodiment of this application;
[0024] Figure 11 This is a schematic diagram of a scenario for canceling the addition of a device element of a target device according to an embodiment of this application;
[0025] Figure 12 This is a schematic diagram of a scenario for adding device elements to a target device according to another embodiment of this application;
[0026] Figure 13 This is a schematic diagram of an interface for displaying prompt information provided in an embodiment of this application;
[0027] Figure 14 This is a schematic diagram of the updated first interface provided in an embodiment of this application;
[0028] Figure 15 This is a schematic diagram of the updated second interface provided in an embodiment of this application.
[0029] Figure 16 This is a schematic diagram of the interaction process of the permission receiving device controlling and managing the target device according to an embodiment of this application;
[0030] Figure 17 This is a schematic diagram of a control permission sharing device provided in an embodiment of this application;
[0031] Figure 18 This is a schematic diagram of a terminal device provided in an embodiment of this application.
[0032] Icon labels:
[0033] 100 - Terminal device, 200 - Server, 300 - Device to be shared, 400 - Permission receiving device, 180 - Processor, 181 - Memory, 182 - Computer program. Detailed Implementation
[0034] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.
[0035] The technical solutions provided in this application will be explained in detail below with reference to specific embodiments.
[0036] As energy storage devices are widely used across various industries, the demand for their control is also increasing. Typically, after a terminal device is bound to an energy storage device, it can be remotely controlled via an application installed on that device. However, in practical applications, there may be scenarios where different terminal devices jointly control one or more energy storage devices. In such scenarios, each terminal device needs to be bound to each of these devices separately, making the binding process cumbersome.
[0037] Furthermore, in related technologies, when a terminal device shares control permissions with a target device among its bound devices, it does so by adding an account within the target device's control interface. For example, when a terminal device and a target device are bound, the user adds a permission recipient in the target device's control interface displayed on the terminal device. By entering the recipient's user account, control permissions for the target device are shared. However, this method requires the user to know the recipient's account and involves switching between multiple applications on each device, making it cumbersome. Moreover, in scenarios where multiple devices are shared to a single target account, the target account needs to be added to all devices, further complicating the process.
[0038] Based on this, the technical solution of this application provides a method for controlling permission sharing, which simplifies the operation process of sharing device permissions.
[0039] Figure 1 This is a schematic diagram of the structure of a control permission sharing system applicable to an embodiment of this application. See also... Figure 1 As shown, the control permission sharing system includes a terminal device 100, a server 200, a device to be shared 300, and a permission receiving device 400.
[0040] Specifically, the terminal device 100 is logged into a first account, which has control permissions over the device 300 to be shared with. In other words, the first account also has the right to share control permissions over the device 300. For example, if account A shares control permissions for the target device within the device 300 to account B, then account A has the permission to share control permissions, but account B only has control permissions for the target device and does not have the permission to share those control permissions.
[0041] Terminal device 100 is used to share control permissions of the target device in the device to be shared 300 to the target account through the first account that is logged in.
[0042] In some embodiments, after the terminal device 100 shares the control permissions of the target device with the target account through the logged-in first account, at the same time as sharing the control permissions of the target device with the target account, the target account may also be allowed to have the permission to share control permissions, that is, the user may be allowed to share the control permissions of the target device again through the target account.
[0043] In this embodiment, the terminal device 100 can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, smart TV, projector, etc., or it can be a wearable device (such as a smartwatch), in-vehicle device, augmented reality (AR) / virtual reality (VR) device, ultra-mobile personal computer (UMPC), netbook, etc. This application embodiment does not limit the specific type of the terminal device 100.
[0044] The device 300 to be shared is bound to the terminal device 100, and the terminal device 100 has control permissions over it, as well as the permission to share those control permissions. There can be one or more devices 300 to be shared; see [link to relevant documentation]. Figure 1 As shown, the device to be shared 300 includes a first device, a second device, and a third device. The terminal device 100 has control permissions and the right to share these control permissions with the first device, the second device, and the third device.
[0045] Server 200 is used to relay data or control commands between terminal device 100 and device 300 to be shared. Server 200 can communicate with terminal device 100 and device 300 via wireless network or wired network. For example, server 200 receives control commands sent by terminal device 100 and then sends the control commands to device 300 to be shared; or server 200 receives data information from device 300 to be shared and sends the data information to terminal device 100.
[0046] In this embodiment, the server is also configured to receive a first statement sent by the terminal device 100, the first statement being used to indicate that the target account is granted permission to control the target device; and to receive control instructions from the target account to the target device, and to control the target device according to the control instructions.
[0047] In one embodiment, the terminal device 100 and the sharing device 300 communicate via a server 200. The terminal device 100 can communicate with the server 200 via a wireless network (e.g., mobile network, WiFi, and Bluetooth) or a wired network (e.g., a communication bus). The sharing device 300 may be equipped with a wireless communication module, which also enables communication with the server 200.
[0048] The permission receiving device 400 is a device logged into with the target account information. After logging into the target account, the permission receiving device 400 gains control over the target device corresponding to that target account. This control includes the target account's control over the target device and / or the right to share that control. The permission receiving device provided in this embodiment can be a mobile phone, tablet, computer with wireless transceiver capabilities, smart TV, projector, etc., or it can be a wearable device (such as a smartwatch), in-vehicle device, augmented reality (AR) / virtual reality (VR) device, ultra-mobile personal computer (UMPC), netbook, etc. This application embodiment does not limit the specific type of the permission receiving device 400.
[0049] In this embodiment, when the terminal device 100 shares the control permissions of the target device in the sharing device 300 to the permission receiving device 400, it declares the control permissions of the sharing device 300 to the server 200, so that when the user sends control commands to the target device through the server 200 based on the permission receiving device 400, the target device can respond to the control operation from the permission receiving device 400.
[0050] Figure 2 A schematic diagram of the interaction flow of the control permission sharing method provided in an embodiment of this application is shown below. Figure 2 As shown, the method includes the following steps S201 to S206.
[0051] S201, The terminal device receives a display instruction, which is used to instruct the display of a list of accounts to be shared.
[0052] In this embodiment, the display command can be input by the user from the user input interface of the terminal device through a voice recognition control. For example, the user sends a display command to the terminal device saying "Display the list of accounts to be shared" through the voice recognition control. Alternatively, the terminal device can generate the display command in response to the user's selection operation of the device control permission sharing control on the terminal device. See [link to relevant documentation]. Figure 3 As shown in the image.
[0053] In practice, the permission sharing control can be a functional element displayed on the terminal device that represents the permission sharing function. The terminal device generates a display command in response to the user's selection of this functional element.
[0054] S202, the terminal device displays a first interface according to the display instruction, which includes a list of accounts to be shared.
[0055] See Figure 4 The figure shows a schematic diagram of the first interface U1 provided in an embodiment of this application. As shown, the first interface U1 includes element controls for each account in the list of accounts to be shared, such as... Figure 4 The diagram shows the element controls for Account 1, Account 2, Account 3, Account 4, and Account 5, as well as the account addition element control for adding accounts. The terminal device can respond to a user clicking on any account element control in the list of accounts to be shared to share control permissions for the device, and can also respond to a user clicking on the account addition element control to add an account to be shared.
[0056] In some embodiments, when no account information has been added to the terminal device, the terminal device displays a first interface U1 based on the display instruction, which is the initial list of accounts to be shared. That is, at this time, the first interface U1 only includes account addition element controls for adding accounts. See [link to relevant documentation]. Figure 5 As shown in the image.
[0057] In other embodiments, the terminal device responds to the user clicking the account addition element control to add the account to be shared through the following process:
[0058] See Figure 6 As shown, firstly, in response to the user's click on the account addition control, the terminal device displays a floating window U3. This floating window U3 includes an account input box Q1 and cancellation and addition element controls. The account input box Q1 is used to obtain the account information of the account to be entered. Then, the terminal device obtains the account information of the account to be entered through the account input box Q1. Finally, in response to the user clicking the addition element control, the terminal device displays the account to be entered in the first interface U1. In another embodiment of this example, if the user clicks the cancellation element control in the floating window U3, it indicates that the user has chosen to cancel the account addition operation. The terminal device, in response to the user clicking the cancellation element control, cancels the account addition operation to be shared.
[0059] S203, in response to the selection of a target account in the list of accounts to be shared, the terminal device displays a second interface, which includes a permission receiving window for the target account.
[0060] In this embodiment, the target account refers to any account selected by the user on the first interface U1. For example... Figure 7 As shown, when a user clicks the "Account 1" element control in the first interface U1, the selection operation of the target account in the first interface U1 is triggered. That is, Account 1 is the target account at this time.
[0061] It should be noted that in this embodiment, the accounts in the shareable account list of the first interface U1 are the accounts to be shared. When a user selects an account from the shareable account list, that account becomes the target account. Since any account in the shareable account list can be logged in and used on other terminal devices, when a user selects an account from the shareable account list as the target account, the terminal device responds to the selection operation by displaying a second interface U2 that includes a permission receiving window for the target account. After sharing or sharing control permissions for a target device through the second interface U2, the target account can be logged in on other terminal devices, giving those other terminal devices control permissions over the target device. In other words, the user can control the target device through other terminal devices.
[0062] In response to the selection of a target account from the list of accounts to be shared, the terminal device displays the second interface U2, see [link / reference]. Figure 8The diagram shown is a schematic of the second interface U2 displayed on the terminal device. It should be noted that when the terminal device shares control permissions for the bound devices, it is sharing or distributing control permissions for the devices that the first account can control. Therefore, the device control permission sharing page, i.e., the second interface U2, can include all or some of the device elements for the devices that the first account can control.
[0063] For example, see Figure 8 As shown, the device control permission sharing page includes a permission receiving window U21 for the target account and device elements of the device to be shared. In one embodiment, the device elements of the device to be shared are located outside the permission receiving window. In one embodiment of this example, if the first account logged into the terminal device has control permissions for four devices to be shared: device A1, device A2, device B1, and device B2, then the device elements S11, S12, S21, and S22 of the four devices to be shared can be displayed in the device control permission sharing interface. The device elements S11, S12, S21, and S22 of the devices to be shared can be displayed in a list or manifest in the second interface U2, and the specific selection can be made according to actual needs; this embodiment does not impose any restrictions.
[0064] In another embodiment of this example, the permission receiving window U21 of the target account includes a device adding control, which is used to add a target device to the target account. See [link to relevant documentation]. Figure 9 As shown in the image.
[0065] In another embodiment of this example, to inform the user of the purpose or use of the permission receiving window U21, the permission receiving window U21 may also display prompts instructing the user to perform drag-and-drop operations on device elements. For example, it may display the prompt "Drag the element here to complete permission sharing". Here, to avoid the prompts displayed in the permission receiving window U21 being mistaken for pop-up content, the font color of the prompts can be gray.
[0066] S204, the terminal device responds to a preset operation by adding the device element of the target device to the permission receiving window; wherein, the device to be shared includes the target device.
[0067] It should be noted that, in this embodiment, in combination with Figure 8 and Figure 9As shown in the diagram, S11, S12, S21, and S22 displayed in the second interface U2 are device elements of the device to be shared. When the user selects a device element of a device among the device elements of the device to be shared, that device becomes the target device, and the device element corresponding to that device becomes the device element of the target device.
[0068] In this embodiment, the preset operation can be the user dragging the target device's device element from outside the permission receiving window to the permission receiving window; or it can be the user long-pressing and selecting the target device's device element from the device elements of the device to be shared.
[0069] In some embodiments, the terminal device adds the device element of the target device from the device elements of the device to be shared to the permission receiving window in response to a preset operation, including: the terminal device adds the device element of the target device from outside the permission receiving window U21 to the permission receiving window U21 in response to an operation of dragging the device element of the target device from outside the permission receiving window U21 to the permission receiving window U21.
[0070] For example, a terminal device can respond to a user dragging at least one device element from device A1, device A2, device B1, and device B2 into the permission receiving window U21 of the target account, thereby enabling the sharing of control permissions for the corresponding devices. See also Figure 10 The diagram shown illustrates a scenario where a target device element is added to the permission receiving window according to an embodiment of this application. Figure 10 As shown, when a user drags and drops a device element of device A2, device A2 becomes the target device. The user then drags the device element of device A2 to the permission receiving window U21 of the target account. At this point, the device element of device A2 is displayed in the permission receiving window U21 of the target account. The display of the device element of device A2 in the permission receiving window U21 of the target account is to inform the user that control permissions for device A2 have been shared with the target account, i.e., account 1. In one implementation of this embodiment, when there are multiple device elements of target devices in the permission receiving window U21, the device elements of the target devices can also be displayed in the permission receiving window U21 in a list or manifest format. The specific selection can be made according to actual needs, and this embodiment does not impose any restrictions.
[0071] In another embodiment of this example, the terminal device responds to the user dragging the device element of the target device from the permission receiving window U21 of the target account to outside the permission receiving window U21, indicating that the control permission of the target account on the target device has been cancelled.
[0072] See Figure 11The image shown is a schematic diagram illustrating a scenario where the permission receiving window cancels the addition of a target device element, according to an embodiment of this application. Figure 11 As shown, when a user drags the device element of device A2 from the permission receiving window U21 of account 1 to outside the permission receiving window U21, the device element of device A2 will no longer be displayed in the permission receiving window U21 of account 1, that is, the control permission of account 1 over device A2 will be cancelled.
[0073] In other embodiments, the terminal device adds the device element of the target device from the device elements of the device to be shared to the permission receiving window U21 in response to a preset operation. This includes: the terminal device displaying the device elements of the device to be shared in response to an operation of adding a control to the device; and then, the terminal device adding the device elements of the target device to the permission receiving window in response to a selection operation of the device elements of the device to be shared. For example, see [link to example]. Figure 12 As shown, when a user triggers the device add control, and the user clicks to select the corresponding target device's device element from the device elements of the device to be shared, the terminal device adds the target device's device element to the permission receiving window.
[0074] In other words, see Figure 11 and Figure 12 As shown, in addition to dragging any one of the elements S11, S12, S21 and S22 in U2 to window U21, you can also set corresponding controls in window U21 to add any one of the elements S11, S12, S21 and S22, and determine the target device based on the addition result.
[0075] In this embodiment, the terminal device can also display a prompt message in response to operations on device elements of the target device. This prompt message includes the account with control permissions over the target device. Operations on device elements of the target device include drag-and-drop or selection operations. For example, see [link to example]. Figure 13 As shown, in response to a drag-and-drop operation on the device element of device A2, the terminal device displays the message "Control permissions for device A2 have been shared with accounts 2 and 3." This message also includes controls for canceling and continuing to add elements. When the user clicks the "continue adding" control, the terminal device displays the device element of device A2 in the permission receiving window U21 of account 1. In this embodiment, the message displayed by the terminal device is used to inform the user of the existing sharing status of control permissions for the target device, making it easy for the user to know which target accounts have shared control permissions for the target device.
[0076] S205, the terminal device sends a first statement to the server, which is used to indicate that the target account is granted permission to control the target device.
[0077] In step S204, once the terminal device displays the elements of the target device in the permission receiving window corresponding to the account, it indicates that the terminal device user has authorized the target account to control the target device. Therefore, the terminal device needs to send a declaration to the server sharing the control permissions of the target device with the target account, so that when the server receives a control command for the target device sent by the target account, it can control the target device according to the declaration.
[0078] In some embodiments, after removing the device element of the target device from the permission receiving window, the terminal device sends a second statement to the server, which instructs the target account to revoke its control over the target device. At this time, the terminal device sends permission cancellation information to the server, and the target account no longer has control over the target device.
[0079] In other embodiments, after sending the first declaration to the server, the terminal device updates the first interface U1; wherein the updated first interface U1 includes all device elements of the target devices that the target account can control. That is, when the terminal device displays the first interface U1 again after sending the first declaration to the server, the first interface U1 includes all device elements of the target devices that the target account can control. For example, see the figure below. Figure 14 As shown, in the updated first interface U1, since account 1 has already shared control permissions for device A2, a corresponding second child element D1 has been added to the element control of account 1 in the updated first interface U1. In this way, users can clearly understand that device A2 permissions have been shared with account 1.
[0080] In some other embodiments, after sending the first declaration to the server, the terminal device updates the second interface U2, wherein the device elements of the target device in the updated second interface U2 include a graphical identifier of the target account. For example, see the figure below. Figure 15 As shown, in the updated device control permission sharing interface, i.e., the second interface U2, corresponding sub-elements have been added to the device element of the target device. For example... Figure 15 As shown, the target device is device A2, and a first child element C1 of the target account (account 1) has been added to device A2. Optionally, this child element can be account 1's avatar, account name, or initials of the account name, etc. This method allows users to know which devices' control permissions have been shared, and to which users.
[0081] S206, The server receives the first statement and grants the target account permission to control the target device based on the first statement.
[0082] In this embodiment, the first declaration is used to indicate that the target account is granted permission to control the target device. Therefore, after receiving the first declaration, the server can grant the target account permission to control the target device.
[0083] Understandably, when a user controls a target device using a terminal device, they send control commands to the server, which then sends corresponding target commands to the target device based on those commands. Therefore, the server can be pre-configured with declarations of different functions, such as control protocol declarations and control permission declarations. Here, the first declaration indicates that the target account is granted permission to control the target device. After receiving this first declaration, the server can configure it into the corresponding control permission declaration, so that when the server receives a control command triggered by the target account to control the target device, it sends the corresponding target command to the target device based on the first declaration.
[0084] In some embodiments, the server is further configured to receive a second statement, which instructs the server to release the target account from controlling the target device. Upon receiving the second statement, the server releases the target account from controlling the target device in accordance with the second statement.
[0085] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0086] The above is an exemplary description of the control permission sharing method provided in the embodiments of this application. This method simplifies the device permission sharing process. Furthermore, in real-time scenarios where control permissions for multiple devices need to be shared with a target account, it is not necessary to add the target account for each device; simply drag and drop elements of multiple devices into the target account's sharing interface.
[0087] The control permission sharing method provided in this application allows a terminal device to share control permissions of a target device to a target account. After the target account logs in on the permission-receiving device, it can control and manage some functions of the target device using the permission-receiving device. The following explanation, in conjunction with specific embodiments, illustrates the process by which the permission-receiving device controls and manages the target device.
[0088] Figure 16 This is a schematic diagram illustrating the interaction process of an authorization receiving device controlling and managing a target device according to an embodiment of this application. (See also...) Figure 16 As shown, the method includes the following steps S1601 to S1604.
[0089] S1601, Access Receiving Device Login Target Account.
[0090] In this embodiment, the terminal device has shared the control permissions of the target device with the target account through the control permission sharing method. Therefore, the permission receiving device can control the target device after logging into the target account.
[0091] In one implementation of this embodiment, if a terminal device shares control permissions for multiple target devices with a target account, the permission receiving device can control the multiple target devices after logging into the target account.
[0092] S1602, the authorization receiving device sends control commands to the server.
[0093] For example, the control command can be used to instruct the target device to be turned on or off, or it can be other control commands used to instruct the target device to perform other functions. The authorization receiving device can send the target command to the server via wired or wireless communication.
[0094] S1603, the server generates target instructions based on the control instructions and sends them to the target device.
[0095] After receiving a control command, the server generates a target command that the target device can recognize, and then sends the target command to the target device. The server can send the target command to the target device via wired or wireless communication.
[0096] S1604, the target device completes the corresponding operation according to the target instruction.
[0097] In this embodiment, since the terminal device shares the control permissions of the target device with the target account and simultaneously sends the control permission declaration of the target device to the server, when the user sends control commands to the target device through the server based on the permission receiving device, the target device can respond to the control operation from the permission receiving device and complete the corresponding operation according to the received target command.
[0098] In summary, the control permission sharing method provided in this application is applied to a terminal device logged in with a first account, where the first account is an account that has control permissions over the device to be shared. The terminal device displays a list of accounts to be shared. The user clicks the "Add Account" element control in the list and enters the account information of the account to be shared. The terminal device then generates a sharing list with the target account based on this information. After the user selects the target account from the list, a sharing interface corresponding to that target account is displayed. Then, in response to the user dragging the target device's device element icon from the device element of the device to be shared to the permission receiving window, the terminal device sends a first declaration of the target device's permission authorization information to the server. This first declaration instructs the server to authorize control permissions for the target device for the target account based on the first declaration. After logging in on the permission receiving device, the target account can control and manage some functions of the target device using the permission receiving device. This method effectively solves the problem of cumbersome implementation processes in traditional technologies where different terminal devices need to jointly control one or more energy storage devices.
[0099] Figure 17 This is a schematic diagram of a control permission sharing device provided in an embodiment of this application. The device is applied to a terminal device, which is logged into a first account. This first account has control permissions for the device to be shared with, such as... Figure 17 As shown, the device includes:
[0100] The first display unit is used to display the first interface, which includes the target account.
[0101] The second display unit is used to display a second interface in response to the selection operation of the target account. The second interface includes the permission receiving window of the target account.
[0102] The add unit is used to add the device element of the target device to the permission receiving window in response to a preset operation; wherein, the device to be shared includes the target device.
[0103] The sending unit is used to send a first statement to the server, which indicates that the target account is granted permission to control the target device.
[0104] Figure 18 This is a schematic diagram of a terminal device provided in one embodiment of this application. Figure 18As shown, the terminal device 100 of this embodiment includes: a processor 180, a memory 181, and a computer program 182 stored in the memory 181 and executable on the processor 180, such as a control permission sharing program. When the processor 180 executes the computer program 182, it implements the steps in the various control permission sharing method embodiments described above. Alternatively, when the processor 180 executes the computer program 182, it implements the functions of each module / unit in the various device embodiments described above.
[0105] For example, the computer program 182 may be divided into one or more modules / units, which are stored in the memory 181 and executed by the processor 180 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program 182 in the terminal device 100.
[0106] The terminal device 100 may be a computing device such as a tablet computer, desktop computer, laptop computer, handheld computer, or cloud server. The terminal device may include, but is not limited to, a processor 180 and a memory 181. Those skilled in the art will understand that... Figure 18 This is merely an example of terminal device 100 and does not constitute a limitation on terminal device 100. It may include more or fewer components than shown, or combine certain components, or different components. For example, the terminal device may also include input / output devices, network access devices, buses, etc.
[0107] The processor 180 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.
[0108] The memory 181 can be an internal storage unit of the terminal device 100, such as a hard disk or memory of the terminal device 100. The memory 181 can also be an external storage device of the terminal device 100, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the terminal device 100. Furthermore, the memory 181 can include both internal and external storage units of the terminal device 100. The memory 181 is used to store the computer program and other programs and data required by the terminal device. The memory 181 can also be used to temporarily store data that has been output or will be output.
[0109] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.
[0110] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0111] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0112] In the embodiments provided in this application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0113] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0114] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0115] If the integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by hardware related to computer program instructions. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.
[0116] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.
Claims
1. A method for controlling access sharing, characterized in that, Applied to a terminal device, the terminal device is logged into a first account, and the first account has control permissions for the device to be shared with, as well as the permission to share with the device under control. The method includes: The first interface is displayed, and the first interface includes the target account; In response to the selection of the target account, a second interface is displayed, which includes a permission receiving window for the target account and a device element of the device to be shared located outside the permission receiving window. In response to a preset operation, the device element of the target device is added to the permission receiving window; wherein, the target device is the device corresponding to the selected device element among the device elements of the device to be shared; Send a first statement to the server, the first statement being used to indicate that the target account is granted the permission to control the target device and the permission to share the control permission of the target device; Update the first interface; wherein the updated first interface includes device elements of all target devices that the target account can control; The second interface is updated, wherein the device element of the target device in the updated second interface includes the graphic identifier of the target account.
2. The method according to claim 1, characterized in that, The second interface also includes a device element of the device to be shared, which is located outside the permission receiving window; The step of adding the device element of the target device to the permission receiving window in response to a preset operation includes: In response to the operation of dragging the device element of the target device from outside the permission receiving window to the permission receiving window, the device element of the target device is added to the permission receiving window.
3. The method according to claim 1, characterized in that, The permission receiving window includes a device adding control, and the step of adding the device element of the target device to the permission receiving window in response to a preset operation includes: In response to the operation of adding a control to the device, the device element of the device to be shared is displayed; In response to the selection operation of the target device's device element in the device elements of the device to be shared, the device element of the target device is added to the permission receiving window.
4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: After removing the device element of the target device from the permission receiving window, a second statement is sent to the server, which instructs the target account to release its control over the target device.
5. The method according to claim 2 or 3, characterized in that, The method further includes: In response to an operation on a device element of the target device, a prompt message is displayed, the prompt message including an account with control permissions over the target device; The operations on the device elements include drag-and-drop operations or selection operations.
6. The method according to claim 1, characterized in that, The first interface also includes an account addition control, and the method further includes: In response to the operation of adding a control to the account, the account input box is displayed; The target account is obtained through the account input box; The target account is displayed on the first interface.
7. A terminal device, characterized in that, The terminal device is configured to perform the method according to any one of claims 1 to 6.
8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 6.