Equipment control method and device, equipment and medium

Abstract

The embodiment of the invention provides an equipment control method and device, equipment and a medium, and the method comprises the steps: determining an equipment state corresponding to multiple rounds of verification operation after triggering an equipment binding process; outputting guide information corresponding to the multiple rounds of verification operation, wherein the guide information is used for reminding a user to adjust the equipment to the equipment state corresponding to the multiple rounds of verification operation; and in response to the condition that the user adjusts the equipment to the equipment state corresponding to the multiple rounds of verification operation, finishing binding of the equipment. According to the embodiment of the invention, through the guide information corresponding to the multiple rounds of verification operation, the user is reminded to adjust the device to the device state corresponding to the multiple rounds of verification operation, it is ensured that only the user who succeeds in the multiple rounds of verification operation can complete device binding, and the safety of device binding is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of equipment control, and in particular to an equipment control method and an equipment control device. Background Art

[0002] By binding devices to user terminals, remote monitoring and control of devices can be achieved, improving user experience and convenience. For example, by binding an air conditioner to a user's mini-program, the user can control the air conditioner through the mini-program. In existing technologies, the binding process between devices and user terminals usually relies solely on scanning a QR code or manually entering the unit's built-in MAC address, which poses significant security risks. Simply binding by scanning a code or entering a MAC address is susceptible to security threats such as man-in-the-middle attacks and identity forgery, which can result in unauthorized users gaining control of the device, leading to the risk of privacy leakage or device abuse. Summary of the Invention

[0003] In view of the above problems, embodiments of the present invention are proposed to provide a device control method, apparatus, device, and medium that overcome the above problems or at least partially solve the above problems.

[0004] According to a first aspect of an embodiment of the present invention, a device control method is provided, the method comprising:

[0005] After triggering the device binding process, determine the device status corresponding to multiple rounds of verification operations;

[0006] Outputting guidance information corresponding to the multiple-round verification operation, wherein the guidance information is used to remind the user to adjust the device to a device state corresponding to the multiple-round verification operation;

[0007] In response to the user adjusting the device to a device state corresponding to the multiple rounds of verification operations, the binding of the device is completed.

[0008] Optionally, the method further includes:

[0009] Get a device binding request, which carries a device identifier

[0010] In response to the device binding request, a device binding process for the device corresponding to the device identifier is triggered.

[0011] Optionally, the method further includes:

[0012] In response to a permission sharing request for the device by the first user, the control permission of the device is shared with a second user corresponding to the permission sharing operation.

[0013] Optionally, the method further includes:

[0014] Obtaining a tree diagram corresponding to the device, where nodes of the tree diagram represent users, and edges between the nodes represent sharing relationships between users;

[0015] In the tree diagram corresponding to the device, a node of the second user is created, and the node of the second user is connected to the node of the first user to serve as a child node of the node of the first user.

[0016] Optionally, the method further includes:

[0017] In response to a user's permission query request, query the user's subordinate users; the subordinate users are users of each child node of the node corresponding to the user in the tree diagram;

[0018] In response to a user's permission modification request, the control permissions of subordinate users of the user are modified.

[0019] Optionally, in response to the first user's permission sharing request for the device, sharing the control permission of the device with the second user corresponding to the permission sharing operation includes:

[0020] In response to a first user's permission sharing request for the device, determining whether the number of sharing times corresponding to the first user is zero;

[0021] If the number of sharing times corresponding to the first user is not zero, the control authority of the device is shared with the second user corresponding to the authority sharing operation, and the number of sharing times corresponding to the first user is reduced by one.

[0022] Optionally, the method further includes:

[0023] When a user's control request for the device is detected, determining whether the user matches a node having control authority in the tree diagram corresponding to the device;

[0024] If the user matches a node with control authority in the tree diagram corresponding to the device, the device is controlled in response to the control request.

[0025] According to a second aspect of an embodiment of the present invention, there is provided a device control apparatus, characterized in that the apparatus comprises:

[0026] A first determination module is used to determine the device status corresponding to multiple rounds of verification operations after triggering the device binding process;

[0027] a first adjustment module, configured to output guidance information corresponding to the multiple-round verification operation, wherein the guidance information is used to remind the user to adjust the device to a device state corresponding to the multiple-round verification operation;

[0028] The first binding module is configured to complete the binding of the device in response to the user adjusting the device to a device state corresponding to the multiple rounds of verification operations.

[0029] Optionally, the device further includes:

[0030] The first acquisition module is used to obtain a device binding request, wherein the device binding request carries a device identifier.

[0031] The first triggering module is configured to respond to the device binding request and trigger a device binding process for the device corresponding to the device identifier.

[0032] Optionally, the device further includes:

[0033] The first sharing module is configured to share the control permission of the device with a second user corresponding to the permission sharing operation in response to a permission sharing request of the first user for the device.

[0034] Optionally, the device further includes:

[0035] A second acquisition module is configured to acquire a tree diagram corresponding to the device, wherein the nodes of the tree diagram represent users, and the edges between the nodes represent sharing relationships between users;

[0036] The first creation module is configured to create a node of the second user in the tree diagram corresponding to the device, and connect the node of the second user to the node of the first user as a child node of the node of the first user.

[0037] Optionally, the device further includes:

[0038] A first query module is configured to query subordinate users of the user in response to a permission query request of the user; the subordinate users are users of each child node of the node corresponding to the user in the tree diagram;

[0039] The first modification module is configured to modify the control authority of a subordinate user of the user in response to a permission modification request of the user.

[0040] Optionally, the first sharing module includes:

[0041] A first determining submodule is configured to determine, in response to a first user's permission sharing request for the device, whether the number of sharing times corresponding to the first user is zero;

[0042] The first sharing submodule is configured to share the control authority of the device with the second user corresponding to the authority sharing operation if the number of sharing times corresponding to the first user is not zero, and reduce the number of sharing times corresponding to the first user by one.

[0043] Optionally, the device further includes:

[0044] a second determining module, configured to, when detecting a user's request for controlling the device, determine whether the user matches a node having control authority in the tree diagram corresponding to the device;

[0045] The first control module is configured to respond to a control request and control the device if the user matches a node with control authority in the tree diagram corresponding to the device.

[0046] According to a third aspect of the present invention, a device is provided, comprising: a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the steps of the device control method as described in any one of the above items when executed by the processor.

[0047] According to a fourth aspect of the present invention, there is provided a computer-readable storage medium storing a computer program, wherein the computer program implements the steps of the device control method as described above when executed by a processor.

[0048] The technical solutions provided by the embodiments of the present invention may have the following beneficial effects:

[0049] Embodiments of the present invention provide a device control method, apparatus, device, and medium. After triggering a device binding process, the method determines the device state corresponding to a multi-round verification operation; outputs guidance information corresponding to the multi-round verification operation, the guidance information being used to remind the user to adjust the device to the device state corresponding to the multi-round verification operation; and completes device binding in response to the user adjusting the device to the device state corresponding to the multi-round verification operation. Embodiments of the present invention, through the guidance information corresponding to the multi-round verification operation, remind the user to adjust the device to the device state corresponding to the multi-round verification operation, ensuring that only users who have successfully completed multiple rounds of verification operations can complete device binding, thereby improving the security of device binding. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 This is a flowchart of a device control method provided by an embodiment of the present invention;

[0051] Figure 2 This is a page diagram of a device control method provided by an embodiment of the present invention;

[0052] Figure 3 This is a page diagram of another device control method provided by an embodiment of the present invention;

[0053] Figure 4 This is a tree diagram representing device control permissions provided by an embodiment of the present invention;

[0054] Figure 5 This is a structural block diagram of a device control apparatus provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0055] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0056] One of the core concepts of the embodiment of the present invention is to remind users to adjust their devices to the device status corresponding to the multiple rounds of verification operations through guidance information corresponding to the multiple rounds of verification operations, ensuring that only users who have successfully completed the multiple rounds of verification operations can complete the device binding, thereby improving the security of device binding.

[0057] Reference Figure 1 , shows a flowchart of a device control method provided by an embodiment of the present invention, the method may specifically include the following steps:

[0058] Step 101: After the device binding process is triggered, the device status corresponding to multiple rounds of verification operations is determined;

[0059] Device control can be applied to the server. After obtaining the binding process triggered by the user on the user terminal (such as a smartphone APP or mini program), the server determines the device status corresponding to the multi-round verification operation. The multi-round verification mechanism is designed to ensure a secure and reliable connection between the device and the user terminal, and provide users with effective control over the device. The device may include an air conditioner. Taking the air conditioner as an example, the device status includes but is not limited to the air conditioner's operating mode (such as cooling, heating, dehumidification, etc.), set temperature, and wind speed level and other parameters. These status information not only reflects the current operating status of the air conditioner, but also serves as the basis for achieving precise control.

[0060] Step 102: outputting guidance information corresponding to the multi-round verification operation, wherein the guidance information is used to remind the user to adjust the device to a device state corresponding to the multi-round verification operation;

[0061] Reference Figure 2 , shows a page schematic diagram of a device control method provided by an embodiment of the present invention. The page takes a 5-round verification mechanism as an example. Each round can be set to be fully adjusted using the remote control. The guidance information for the second round can be 25°C, dehumidification, and low wind speed. The user can click Return or Next according to the completion of the guidance information.

[0062] For example, in the device binding process, in order to ensure security and accuracy, the system will design multiple rounds of verification operations and generate corresponding guidance information for each round to guide the user to adjust the device status. These guidance messages specifically describe the state to which the user needs to set the device (such as air conditioning), such as a specific working mode, temperature setting or wind speed level. For example, the status of each round is randomly determined by the server, and once determined, it is immediately sent to the user terminal, and then displayed to the user through the user terminal. Such a mechanism not only increases the complexity and security of the verification process, but also effectively prevents the preset status from being predicted or tampered with.

[0063] When the device binding process is triggered, the server begins to generate multiple rounds of verification status. For example, one of the rounds may require the air conditioner to be in cooling mode, the temperature set to 25 degrees Celsius, and the wind speed to be medium. The status information is then pushed to the user's smartphone APP or mini program for display. Next, the user uses the designated control device (such as a remote control) to make corresponding adjustments to the air conditioner according to the guidance information received. After the adjustment is completed, the user can confirm the completion of the operation through the terminal, and the system will perform status matching verification.

[0064] The presence of guidance information enhances the security and reliability of the entire binding process. Because each round of verification is independently and randomly generated, unauthorized access is more difficult, effectively preventing man-in-the-middle attacks and other security threats. Furthermore, by forcing users to complete all specified status adjustments within a specified timeframe, the system further confirms the authenticity of the device and the legitimacy of the user, thus ensuring connection security.

[0065] Step 103 : In response to the user adjusting the device to a device state corresponding to the multiple rounds of verification operations, the binding of the device is completed.

[0066] Reference Figure 3 , shows a page diagram of another device control method provided by an embodiment of the present invention. After the device is bound, the user can control the switch status and mode status of the device on this page. For example, the temperature can be set to 18°C and the wind speed can be set to medium speed.

[0067] For example, the user manually operates the designated control device according to the guidance information received to make the target device reach the specified state, ensuring that only users who own the designated control device can participate in the binding. Every time the user completes a round of status adjustment, it is necessary to confirm that the operation is complete through the user terminal. At this time, the system will match and verify the actual state of the device with the instructions issued by the server. If the device state meets the requirements of this round, it is deemed that this round of verification is successful. The system then enters the next round of verification until all scheduled rounds are completed. The user who completes the device binding for the first time is identified as the device owner. After binding, the device owner can directly control the bound device. The entire binding process effectively improves the security and reliability of device management in smart home or industrial automation scenarios through dynamic adjustment and multi-level verification.

[0068] For example, during the device binding process, in addition to using a designated control device to perform multiple rounds of status adjustments to ensure a secure and reliable connection between the device and the user terminal (such as a smartphone app or mini-program), a pre-set adjustment time can also be used to complete the binding. This approach not only increases flexibility but also improves the security and accuracy of the verification process. For example, after triggering the device binding process, the system generates device status guidance information corresponding to multiple rounds of verification operations and sends it to the user's terminal device for display. The user needs to follow these guidance information and adjust the device (such as an air conditioner) status accordingly within the specified time using a designated control device (such as a remote control, smart speaker, etc.). A visual countdown can also be introduced alongside the guidance information, such as alternating red 10 seconds and green 5 seconds. This design requires the user to accurately complete the device operation within the green 5-second time window and wait for server verification confirmation. For example, within this 5-second window, the server will check whether the current unit has correctly performed the startup or other specified operation. Only after each verification is successfully completed can the next or multiple verification rounds be continued until the device binding is finally completed.

[0069] These methods greatly enhance the user experience and sense of interaction. Through intuitive visual feedback (such as color changes), users can clearly understand the remaining time and operation timing, reducing failed attempts due to operation delays or errors. Secondly, the short and strict time window (such as 5 seconds) forces users to concentrate and respond quickly within a short period of time, ensuring the authenticity and accuracy of each operation, thereby effectively preventing unauthorized access attempts and improving overall security. The combination of using designated control devices for status adjustment and setting preset adjustment times not only improves the flexibility and adaptability of the device binding process, but also enhances the overall security and reliability of the system. Whether through traditional remote controls or modern intelligent control solutions, users can choose the most suitable method to complete device binding according to their actual situation. This design embodies a people-oriented concept, aiming to create a more intelligent and humane interactive experience, allowing users to manage and control their devices more conveniently.

[0070] In one embodiment, the method further includes: obtaining a device binding request, the device binding request carrying a device identifier; and responding to the device binding request to trigger a device binding process for a device corresponding to the device identifier.

[0071] For example, after a user enters a device ID into a user terminal, the user terminal sends a binding request with the device ID to the server. The server receives the binding request and, upon verifying that the device ID in the request is correct, triggers the binding process for the device corresponding to the device ID. The device ID (such as a serial number or MAC address) serves as a unique identifier for the device. It not only helps the system accurately identify each device to be bound, but also effectively prevents identity forgery and unauthorized access, thereby improving the security of the entire system.

[0072] For example, by requiring the user to provide a device ID, the system can confirm the target device for the operation and avoid misoperation or confusion between different devices. This is especially important in a multi-device environment. For example, there may be multiple air conditioners or lamps of the same model in a smart home system. The device type alone cannot distinguish the specific device that needs to be bound. Therefore, accurate device identification is the basis for achieving precise control. Device identification also plays an important role in subsequent service support and technical maintenance. Once the device is bound, manufacturers and service providers can track the operating status of the device based on the device ID and provide personalized after-sales service and support, such as remote fault diagnosis and software update push. This not only improves the user experience, but also helps to detect and solve problems in a timely manner, extending the service life of the device.

[0073] In one embodiment, the method further includes: in response to a permission sharing request of the first user for the device, sharing the control permission of the device with a second user corresponding to the permission sharing operation.

[0074] The first user can be the device owner, or a user with sharing permissions set by the device owner. The second user can be the user who receives the sharing permissions from the first user. Sharing the control permissions of the device to the second user in response to the first user's permission sharing request for the device is an important mechanism to improve user experience, enhance flexibility and promote resource sharing. In a smart home or Internet of Things environment, an individual may own multiple smart devices, such as air conditioners, lighting systems, etc., and want to share control of these devices with family members, friends or colleagues so that they can adjust the environment settings as needed. Through the permission sharing function, the first user can easily authorize other users to operate specific devices without the need to repeatedly configure or replace the control terminal.

[0075] This permission-sharing mechanism greatly improves the convenience of use and the efficiency of collaboration. First, it allows different users to independently operate the device according to their own needs and preferences, avoiding operational conflicts or inconveniences caused by a single control source. Secondly, by precisely setting the permission level of the sharee (such as viewing status only, limited operation permissions, or full control permissions), the device owner can maintain ultimate control over the device while sharing, ensuring security and privacy protection. In addition, some advanced systems can also record the specific circumstances of each permission sharing and all subsequent operations, making it easier to track responsibility and further enhancing the transparency and security of the system.

[0076] Furthermore, the permission sharing mechanism also supports dynamic adjustment and revocation functions. If shared permissions are no longer needed, the first user can revoke the authorization for the second user at any time, ensuring that device control rights are always within controllable range. This flexibility not only facilitates users' daily use, but also provides an effective solution for dealing with emergencies. In short, by responding to the first user's permission sharing request and sharing the device's control rights with the corresponding second user, not only does it greatly improve the convenience and flexibility of device use, but it also helps to build a more open and secure IoT ecosystem, allowing technology to better serve people's daily lives and work. This mechanism embodies a people-oriented design concept, aiming to create a more intelligent and humane interactive experience.

[0077] In one embodiment, the method further includes: obtaining a tree diagram corresponding to the device, the nodes of the tree diagram representing users, and the edges between the nodes representing sharing relationships between users; in the tree diagram corresponding to the device, creating a node for the second user, and connecting the node of the second user to the node of the first user as a child node of the node of the first user.

[0078] Reference Figure 4, shows a tree diagram representing device control permissions provided by an embodiment of the present invention. In the tree diagram, user 1 can represent the current device owner, and user 2 and user 3 can represent two second users with whom user 1 shares permissions. User 4 and user 5 can represent two second users with whom user 2 shares permissions, and user 6 and user 7 can represent two second users with whom user 3 shares permissions. The node where user 1 is located is the root node, and the nodes where user 2, user 3, user 4, user 5, user 6, and user 7 are located are child nodes corresponding to the root node of user 1. The user represented by the root node can see all child nodes corresponding to its root node in the tree diagram.

[0079] Graph databases, due to their unique data model and processing capabilities, are ideal for storing user permission sharing information. In the field of device management and permission control, permission sharing relationships between users can be extremely complex, involving multiple layers of sharing links and diverse sharing relationships. Graph databases intuitively represent these complex relationship networks through nodes (representing users or devices) and edges (representing sharing relationships between users or device connections). Each node can contain detailed user information or device status, while edges describe the specific details of permission sharing, such as the time, scope, and permission level. Graph databases can efficiently store and query complex hierarchical structures. For example, in a smart home environment, one family member may share air conditioner control permissions with another family member, who may in turn share them with a friend. This hierarchical sharing relationship can be clearly represented and easily tracked using nodes and edges. Using a graph database, the system can quickly locate the source of any user's permissions and the underlying sharing links, which is particularly important for managing and revoking permissions. Furthermore, graph databases excel at handling relational queries. Because permission sharing often involves relationships between multiple users and devices, traditional tabular databases can encounter performance bottlenecks when executing relational queries. Graph databases excel at handling this type of highly interconnected data, quickly responding to complex queries such as "find all permissions shared from a specific user." This not only improves system responsiveness but also makes permissions management more flexible and efficient. Furthermore, graph databases allow for easy updating or modification of node information without requiring significant changes to existing data structures, ensuring system flexibility and adaptability. Whether adding new user information fields or adjusting existing sharing rules, these can be easily accomplished.

[0080] Within the framework of device management and permission sharing, in order to intuitively display and manage the sharing relationships between users, the system will generate a tree diagram on the preset page of the user terminal to represent these relationships. Each node in this tree diagram represents a user, and the edges between the nodes represent the permission sharing relationship between users. For example, when the first user decides to share the control permission of the device with the second user, the system first obtains the existing tree diagram corresponding to the device. This tree diagram depicts all users who currently have control permission for the device and their sharing relationships with each other, forming a hierarchical structure.

[0081] When preparing to add the second user's control rights to this management system, the system will create a new node in the tree diagram to represent the second user, and connect this new node to the first user's node through an edge as its child node, such as Figure 4 In the example, User 2 can be a child node of User 1. This means that the second user has obtained partial or full control of the device from the first user, and also indicates a direct sharing relationship between the two. This tree structure not only clearly shows the original permission holder (the root node), but also shows the branches formed by each subsequent sharing operation, helping to understand and track how permissions are transferred between different users.

[0082] For example, in a smart home environment, if a family member wishes to allow a visiting friend to temporarily control the smart air conditioner, they can initiate a permission-sharing request through the app. Once the request is approved, the system creates a child node for the friend in the tree diagram and connects it to the node of the family member who initiated the sharing. This approach provides a visual management tool that makes permission assignments clear at a glance, making it easier to track and manage complex permission hierarchies. It also facilitates revocation operations, as permissions can be revoked by simply disconnecting the corresponding edge or clicking the corresponding child node. The child node can contain the second user's information (such as name, profile picture, de-identified phone number, and number of shareable times). Including the second user's name and profile picture not only enhances user identification but also improves the system user experience, allowing users to quickly understand who is authorized to control the device. Including the de-identified phone number helps protect user privacy. Privacy protection is crucial in modern data processing environments. By displaying only a partially hidden phone number, necessary identification is ensured while preventing the leakage of complete personal information. This is crucial for maintaining user privacy and complying with relevant laws and regulations. Furthermore, recording the number of times a child node can share is crucial for managing and limiting the scope of shared permissions. This allows the system to precisely control each user's sharing permissions, avoiding the security risks associated with excessive sharing. For example, if a user is granted a limited number of sharing permissions, they can only share permissions with lower-level users within the specified number of times, effectively preventing the unauthorized large-scale spread of permissions. Furthermore, this mechanism facilitates administrators' permission auditing and tracking, allowing them to quickly identify and resolve any issues discovered.

[0083] This tree-based permission management approach also helps enhance system security. Because each sharing relationship is clearly documented, any unusual access attempts can be quickly located and addressed. This architecture also facilitates technical support and services for device manufacturers and service providers, as they can accurately understand which users have control over a device and how these permissions are distributed. In summary, using a tree-based representation of device permission sharing relationships not only simplifies device management in multi-user environments but also provides users with a transparent and controllable way to share their smart device resources. Furthermore, sub-nodes can include information about secondary users, improving the efficiency and transparency of permission sharing management while enhancing system security and user privacy. This design leverages the advantages of graph databases, providing a powerful and flexible solution for scenarios such as smart homes and industrial automation. It embodies the advanced concepts of modern technology in managing complex data relationships and ensuring information security. This approach embodies the design philosophy of modern IoT technology, which prioritizes user privacy and data security while enhancing the user experience.

[0084] In one embodiment, the method further includes: in response to a user's permission query request, querying the user's subordinate users; the subordinate users are users of each child node of the node corresponding to the user in the tree diagram; in response to the user's permission modification request, modifying the control authority of the user's subordinate users.

[0085] In order to effectively manage and monitor the allocation of permissions between users, the system provides an intuitive display method based on a tree diagram to help administrators or device owners understand and operate permission relationships. When a user issues a permission query request, the system automatically retrieves and displays all subordinate users of the user, that is, the users corresponding to all child nodes under the user node in the tree diagram, such as Figure 4 As shown in the figure, when user 1 issues a permission query request, the system automatically retrieves and displays all subordinate users of user 1, namely user 2, user 3, user 4, user 5, user 6, and user 7. This allows the permission holder to clearly see which users have been granted access to specific resources or devices and make further decisions based on this.

[0086] For example, once a user's permission query request is received, the system will traverse the entire tree diagram, locate the node corresponding to the requesting user, and identify all its direct or indirect child nodes, such as Figure 4 In the example, the node corresponding to User 2 is a direct child of User 1, and the node corresponding to User 4 is an indirect child of User 1. These child nodes represent other users who have acquired a certain degree of control from the current user. This approach not only clarifies the scope of each user's permissions but also tracks the specific path of permission propagation, ensuring both reasonable and secure permission allocation.

[0087] If a user wishes to modify the control permissions of their subordinate users, such as adding, reducing, or adjusting permission details, they can do so by sending a permission modification request to the system. After receiving such a request, the system first verifies the identity of the requester and the level of permissions they possess to ensure that only authorized personnel can perform such sensitive operations. After confirmation, the system updates the permission settings of the relevant users based on the request content. For example, new permissions can be added to a subordinate user, or their existing permissions can be restricted. This flexibility allows permission holders to quickly respond to changing needs based on actual conditions while maintaining secure control over resources. In addition, device owners can control the permissions of their subordinate users at all levels.

[0088] This mechanism is crucial for maintaining a multi-layered, complex user permission system. It not only supports dynamic adjustment of permission structures but also facilitates the implementation of more refined permission management strategies. Whether controlling access to important data and systems within an enterprise or managing the operational permissions of family members and visitors to smart devices in a smart home environment, the tree-based permission query and modification functionality provides a powerful tool. It makes permission management more transparent and efficient, while also enhancing security and reducing the risk of unauthorized access. Overall, this solution demonstrates how technological advancements are helping to build a more secure and convenient digital environment, giving users greater control over their resources.

[0089] In one embodiment, in response to the first user's permission sharing request for the device, sharing the control permission of the device with the second user corresponding to the permission sharing operation includes: in response to the first user's permission sharing request for the device, determining whether the number of sharing times corresponding to the first user is zero; if the number of sharing times corresponding to the first user is not zero, sharing the control permission of the device with the second user corresponding to the permission sharing operation, and reducing the number of sharing times corresponding to the first user by one.

[0090] Each first user who has device control rights will be given a certain number of sharing times by the device owner (the user who first binds the device), which can be regarded as a resource quota. This quota limits the total number of times they can share control rights with other users. For example, in Figure 4 In the example, user 2 is given 5 shares by user 1, Figure 4 It can be seen that the control permission was only shared with user 4 and user 5, and only shared twice. Then the number of shares for user 2 is 5 times left, and the number of shares is not zero. User 2 can continue to share, and the number of shares will be reduced by 1 for each additional share.

[0091] Limiting the number of times a user can share can enhance security and effectively reduce potential risk points. Without sharing limits, anyone granted permission can continue to share it with more people indefinitely, increasing the potential for unauthorized access and making accountability more difficult. Setting a maximum number of shares helps control the spread of permissions and mitigate security risks. Limiting the number of shares can also simplify management. For large organizations or multi-user home environments, excessive sharing of permissions can significantly increase management complexity. By pre-setting the number of shares, administrators can more easily predict and manage who has permissions and how these permissions are distributed, simplifying the overall permissions management system. Furthermore, limiting the number of shares can encourage responsible use, encouraging users to choose who they share with more carefully and share permissions only when necessary. This approach encourages more responsible behavior and prevents resource misuse or misuse caused by indiscriminate sharing.

[0092] Therefore, when responding to the first user's permission sharing request, the system first confirms the remaining number of shares. If it is found that the number of shares is not zero, the sharing operation is allowed, that is, the control permission of the device is granted to the second user, and the first user's sharing record is updated synchronously, which is reduced by one. On the contrary, if the number of shares has reached the upper limit, the request is rejected, and the user is prompted that no further sharing operations can be performed. This method not only ensures order and security in the permission sharing process, but also provides users with a clear and predictable operating framework, promoting the effective use and safe management of devices. Throughout the process, the system plays a key role, ensuring the autonomy of users and maintaining the security and stability of the entire network environment.

[0093] In one embodiment, the method further includes: when a user's control request for the device is detected, determining whether the user matches a node with control authority in the tree diagram corresponding to the device; if the user matches a node with control authority in the tree diagram corresponding to the device, responding to the control request and controlling the device.

[0094] When the system detects a device control request initiated by a user, it first needs to determine whether the user matches a node with control permissions in the tree diagram corresponding to the device. This node-based tree diagram permission verification mechanism provides an intuitive and efficient method to manage complex multi-level user permission systems, such as Figure 4 In the embodiment, when a user's control request for a device is detected, it is determined whether the user matches a user represented by a node with control authority in a tree diagram representing node authority corresponding to the device, and the control request is responded to if a match occurs.

[0095] For example, the tree diagram corresponding to a device is a hierarchical structure, where each node represents a user, and edges represent the permission-sharing relationships between users. The root node is typically the device owner or initial permission holder. From here, the tree diagram descends layer by layer to each child node, representing other users who have obtained partial or full device control permissions through direct or indirect sharing. Therefore, each node with control permissions corresponds to a user who can perform operations on that device. When a user control request is received, the system automatically checks the identity of the requesting user and compares it with the node information in the tree diagram representing device control permissions. This process is intended to confirm whether the user has indeed been granted the corresponding control permissions. If the user is found to match a node with control permissions in the tree diagram, indicating that the user is authorized to operate the device, the system will respond to the control request and allow the user to execute the corresponding device control commands based on their permission level, such as adjusting settings, starting or stopping the device, etc.

[0096] A strict permission verification process effectively prevents unauthorized access and operation, significantly enhancing system security. Any attempt to circumvent permission checks will be denied, ensuring that devices can only be controlled by authorized users according to established rules. The tree-like structure supports complex permission assignment models, allowing administrators to flexibly set different levels of access based on actual needs. For example, in a smart home environment, family members may have different permission levels; in an enterprise environment, employees may have varying device control permissions based on their responsibilities. Since each permission assignment is recorded in the tree-like structure, it facilitates subsequent troubleshooting and accountability. If an anomaly occurs, the tree-like structure allows for quick identification of the source of the problem and prompt resolution. For administrators, using a tree-like structure to organize and display permission relationships is both intuitive and easy to understand and maintain. Adding new users, adjusting permissions for existing users, and revoking permissions can all be accomplished through a simple graphical interface, significantly simplifying management.

[0097] An embodiment of the present invention provides a device control method. After triggering a device binding process, the method determines the device state corresponding to a multi-round verification operation; outputs guidance information corresponding to the multi-round verification operation, which is used to remind the user to adjust the device to the device state corresponding to the multi-round verification operation; and completes device binding in response to the user adjusting the device to the device state corresponding to the multi-round verification operation. By using the guidance information corresponding to the multi-round verification operation, the embodiment of the present invention reminds the user to adjust the device to the device state corresponding to the multi-round verification operation, ensuring that only users who have successfully completed multiple rounds of verification operations can complete device binding, thereby improving the security of device binding.

[0098] It should be noted that for the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0099] Reference Figure 5 , shows a structural block diagram of a device control device provided by an embodiment of the present invention, which may specifically include the following modules:

[0100] A first determination module 501 is configured to determine the device status corresponding to multiple rounds of verification operations after the device binding process is triggered;

[0101] A first adjustment module 502 is configured to output guidance information corresponding to the multi-round verification operation, wherein the guidance information is configured to remind the user to adjust the device to a device state corresponding to the multi-round verification operation;

[0102] The first binding module 503 is configured to complete the binding of the device in response to the user adjusting the device to a device state corresponding to the multiple rounds of verification operations.

[0103] In one embodiment, the apparatus further comprises:

[0104] The first acquisition module is used to obtain a device binding request, wherein the device binding request carries a device identifier.

[0105] The first triggering module is configured to respond to the device binding request and trigger a device binding process for the device corresponding to the device identifier.

[0106] In one embodiment, the apparatus further comprises:

[0107] The first sharing module is configured to share the control permission of the device with a second user corresponding to the permission sharing operation in response to a permission sharing request of the first user for the device.

[0108] In one embodiment, the apparatus further comprises:

[0109] A second acquisition module is configured to acquire a tree diagram corresponding to the device, wherein the nodes of the tree diagram represent users, and the edges between the nodes represent sharing relationships between users;

[0110] The first creation module is configured to create a node of the second user in the tree diagram corresponding to the device, and connect the node of the second user to the node of the first user as a child node of the node of the first user.

[0111] In one embodiment, the apparatus further comprises:

[0112] A first query module is configured to query subordinate users of the user in response to a permission query request of the user; the subordinate users are users of each child node of the node corresponding to the user in the tree diagram;

[0113] The first modification module is configured to modify the control authority of a subordinate user of the user in response to a permission modification request of the user.

[0114] In one embodiment, the first sharing module includes:

[0115] A first determining submodule is configured to determine, in response to a first user's permission sharing request for the device, whether the number of sharing times corresponding to the first user is zero;

[0116] The first sharing submodule is configured to share the control authority of the device with the second user corresponding to the authority sharing operation if the number of sharing times corresponding to the first user is not zero, and reduce the number of sharing times corresponding to the first user by one.

[0117] In one embodiment, the apparatus further comprises:

[0118] a second determining module, configured to, when detecting a user's request for controlling the device, determine whether the user matches a node having control authority in the tree diagram corresponding to the device;

[0119] The first control module is configured to respond to a control request and control the device if the user matches a node with control authority in the tree diagram corresponding to the device.

[0120] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0121] An embodiment of the present invention provides a device control method. After triggering a device binding process, the method determines the device state corresponding to a multi-round verification operation; outputs guidance information corresponding to the multi-round verification operation, which is used to remind the user to adjust the device to the device state corresponding to the multi-round verification operation; and completes device binding in response to the user adjusting the device to the device state corresponding to the multi-round verification operation. By using the guidance information corresponding to the multi-round verification operation, the embodiment of the present invention reminds the user to adjust the device to the device state corresponding to the multi-round verification operation, ensuring that only users who have successfully completed multiple rounds of verification operations can complete device binding, thereby improving the security of device binding.

[0122] An embodiment of the present invention further provides an electronic device, including:

[0123] It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned device control method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0124] An embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned device control method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0125] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0126] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, apparatus, or computer program products. Thus, embodiments of the present invention may take the form of a fully hardware embodiment, a fully software embodiment, or an embodiment combining software and hardware. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0127] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the process in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0128] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0129] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0130] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they become aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0131] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

[0132] The above is a detailed introduction to a device control method and a device control device provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the ideas of the present invention, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A device control method, characterized in that: The method comprises: After triggering the device binding process, determine the device status corresponding to multiple rounds of verification operations; Outputting guidance information corresponding to the multiple-round verification operation, wherein the guidance information is used to remind the user to adjust the device to a device state corresponding to the multiple-round verification operation; In response to the user adjusting the device to a device state corresponding to the multiple rounds of verification operations, the binding of the device is completed.

2. The device control method according to claim 1, wherein: The method further comprises: Obtaining a device binding request, wherein the device binding request carries a device identifier; In response to the device binding request, a device binding process for the device corresponding to the device identifier is triggered.

3. The device control method according to claim 1, wherein: The method further comprises: In response to a permission sharing request for the device by the first user, the control permission of the device is shared with a second user corresponding to the permission sharing operation.

4. The device control method according to claim 3, characterized in that: The method further comprises: Obtaining a tree diagram corresponding to the device, where nodes of the tree diagram represent users, and edges between the nodes represent sharing relationships between users; In the tree diagram corresponding to the device, a node of the second user is created, and the node of the second user is connected to the node of the first user to serve as a child node of the node of the first user.

5. The device control method according to claim 4, characterized in that: The method further comprises: In response to a user's permission query request, query the user's subordinate users; the subordinate users are users of each child node of the node corresponding to the user in the tree diagram; In response to a user's permission modification request, the control permissions of subordinate users of the user are modified.

6. The device control method according to claim 3, characterized in that: The step of responding to a permission sharing request from a first user for the device, sharing the control permission of the device with a second user corresponding to the permission sharing operation, includes: In response to a first user's permission sharing request for the device, determining whether the number of sharing times corresponding to the first user is zero; If the number of sharing times corresponding to the first user is not zero, the control authority of the device is shared with the second user corresponding to the authority sharing operation, and the number of sharing times corresponding to the first user is reduced by one.

7. The device control method according to claim 4, characterized in that: The method further comprises: When a user's control request for the device is detected, determining whether the user matches a node having control authority in the tree diagram corresponding to the device; If the user matches a node with control authority in the tree diagram corresponding to the device, the device is controlled in response to the control request.

8. A device control device, characterized in that: The device comprises: A first determination module is used to determine the device status corresponding to multiple rounds of verification operations after triggering the device binding process; a first adjustment module, configured to output guidance information corresponding to the multiple-round verification operation, wherein the guidance information is used to remind the user to adjust the device to a device state corresponding to the multiple-round verification operation; The first binding module is configured to complete the binding of the device in response to the user adjusting the device to a device state corresponding to the multiple rounds of verification operations.

9. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the steps of the device control method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the device control method according to any one of claims 1 to 7 are implemented.

Images