Equipment control method and device, equipment and medium

Abstract

The invention discloses an equipment control method and device, equipment and a medium, and relates to the technical field of smart home / smart home, and the method comprises the steps: responding to a first operation of a user on a detail page of target control equipment, sending a control key splitting request of the target control equipment to an application server, sending the target control device to the application server, so that the application server performs control key splitting on each load device managed by the target control device, and synchronizes a first notification message that the control key splitting is completed through a cloud platform; wherein the load equipment after the control key is split is used as new control equipment; in response to the first notification message, sending an equipment list acquisition request to the application server; and receiving a control equipment list returned by the application server after the control keys are split, and displaying the control equipment list. According to the method, a user can directly control each piece of load equipment without entering a multi-level interface of the main equipment, so that interaction steps are reduced, rapid operation is realized, and user experience is enhanced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of smart home, in particular to a device control method and device, equipment and medium. BACKGROUND

[0002] With the continuous popularity of smart home systems, smart switches and central control panels have gradually become the core devices of home intelligent control. These devices connect various loads such as lamps, sockets, curtain motors, floor heating, exhaust fans and general switches, etc., to realize centralized control and intelligent management of home environment.

[0003] Under the traditional control architecture, the smart switch and the central control panel as the master device are only displayed as a single control unit in the user device list. The multiple load devices under it, such as multiple lamps or other auxiliary devices, are all encapsulated in the control interface of the master device. If the user wants to operate a specific load device, he must first enter the detail page of the master device, and then find and select the target device step by step for operation.

[0004] However, under the above operation mode, the user needs to go through multiple steps to control a specific load device, the user cannot quickly locate and operate a specific device, lacks flexibility in directly controlling each load device, the operation efficiency is low, and the user experience is affected. SUMMARY

[0005] To solve the above problems, the present application provides a device control method, device, equipment and medium.

[0006] In a first aspect, the present application provides a device control method, comprising:

[0007] In response to a first operation of a user on a detail page of a target control device, a control button splitting request of the target control device is sent to an application server, so that the application server splits the control buttons of each load device managed by the target control device, and synchronizes a first notification message of the completion of control button splitting through a cloud platform; wherein the load device after control button splitting is a new control device;

[0008] In response to the first notification message, a device list acquisition request is sent to the application server;

[0009] The control device list after control button splitting returned by the application server is received and displayed.

[0010] In a possible implementation manner, the method further comprises:

[0011] In response to the user’s second operation on the details page, a control button splitting and closing request for the target control device is sent to the application server, so that the application server deletes the control button splitting data of each load device managed by each control device, and synchronizes a second notification message of control button splitting and closing completion through the cloud platform.

[0012] In response to the second notification message, a device list retrieval request is sent to the application server;

[0013] Receive and display the list of control devices after the control buttons are split and turned off, returned by the application server.

[0014] Secondly, this application provides a device control method, including:

[0015] Receive a request from the client to split the control buttons of the target control device;

[0016] The control buttons of each load device managed by the target control device are split; wherein, the load device after the control buttons are split is used as a new control device;

[0017] The cloud platform sends a first notification message to the client indicating that the control button splitting is complete.

[0018] In response to the client's request to retrieve the device list triggered by the first notification message, a list of control devices after the control buttons have been split is returned to the client.

[0019] In one possible implementation, the step of splitting the control buttons for each load device managed by the target control device includes:

[0020] In response to the control button splitting request, the cloud platform is queried for the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and the control buttons; the attribute information is used to characterize the corresponding control scenario.

[0021] Based on the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and control buttons, control button splitting data for each load device is constructed.

[0022] In one possible implementation, returning the list of control devices after the control buttons have been split to the client includes:

[0023] The system obtains the user's control button splitting data and queries the user's control device card data from the cloud platform; the control button splitting data includes: card data of each load device after the control buttons are split.

[0024] By integrating the card data of the user's control device and the card data of each load device after the button is split, a list of control devices after the control button is split is obtained.

[0025] Return the list of control devices after the control buttons have been split to the client.

[0026] In one possible implementation, the method further includes:

[0027] Obtain the status data of the load device after the control buttons are split from the cloud platform;

[0028] If the status data of the load device changes, the list of control devices is updated and synchronized to the client.

[0029] In one possible implementation, the method further includes:

[0030] Receive a request from the client to split or turn off the control buttons of the target control device;

[0031] Delete the control button split data for each load device managed by each of the aforementioned control devices;

[0032] A second notification message is sent to the client via the cloud platform to indicate that the control button splitting and closing is complete;

[0033] In response to the client's request to retrieve the device list triggered by the second notification message, a list of control devices after the control buttons have been split and turned off is returned to the client.

[0034] Thirdly, this application provides a device control apparatus, comprising:

[0035] The sending module is used to respond to the user's first operation on the details page of the target control device, and send a control button splitting request for the target control device to the application server, so that the application server splits the control buttons for each load device managed by the control device, and synchronizes a first notification message on the cloud platform to complete the control button splitting; wherein, the load device after the control button splitting is used as the new control device.

[0036] The acquisition module is used to send a device list acquisition request to the application server in response to the first notification message;

[0037] The receiving module is used to receive and display the list of control devices after the control buttons are split from the control buttons returned by the application server.

[0038] In one possible implementation, the sending module is also used for:

[0039] In response to the user’s second operation on the details page, a control button splitting and closing request for the target control device is sent to the application server, so that the application server deletes the control button splitting data of each load device managed by each control device, and synchronizes a second notification message of control button splitting and closing completion through the cloud platform.

[0040] In response to the second notification message, a device list retrieval request is sent to the application server;

[0041] Receive and display the list of control devices after the control buttons are split and turned off, returned by the application server.

[0042] Fourthly, this application provides a device control apparatus, comprising:

[0043] The receiving module is used to receive control button splitting requests from the client for the target control device.

[0044] The splitting module is used to split the control buttons of each load device managed by the target control device; wherein the load device after splitting the control buttons is used as a new control device.

[0045] The sending module is used to send a first notification message to the client via the cloud platform indicating that the control button splitting is complete.

[0046] The return module is used to respond to the client's request to obtain the device list triggered by the first notification message, and return to the client a list of control devices after the control buttons have been split.

[0047] In one possible implementation, the split module 802 is specifically used for:

[0048] In response to the control button splitting request, the cloud platform is queried for the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and the control buttons; the attribute information is used to characterize the corresponding control scenario.

[0049] Based on the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and control buttons, control button splitting data for each load device is constructed.

[0050] In one possible implementation, the return module is specifically used for:

[0051] The system obtains the user's control button splitting data and queries the user's control device card data from the cloud platform; the control button splitting data includes: card data of each load device after the control buttons are split.

[0052] By integrating the card data of the user's control device and the card data of each load device after the button is split, a list of control devices after the control button is split is obtained.

[0053] Return the list of control devices after the control buttons have been split to the client.

[0054] In one possible implementation, the return module is also used for:

[0055] Obtain the status data of the load device after the control buttons are split from the cloud platform;

[0056] If the status data of the load device changes, the list of control devices is updated and synchronized to the client.

[0057] In one possible implementation, the split module is also used for:

[0058] Receive a request from the client to split or turn off the control buttons of the target control device;

[0059] Delete the control button split data for each load device managed by each of the aforementioned control devices;

[0060] A second notification message is sent to the client via the cloud platform to indicate that the control button splitting and closing is complete;

[0061] In response to the client's request to retrieve the device list triggered by the second notification message, a list of control devices after the control buttons have been split and turned off is returned to the client.

[0062] Fifthly, this application provides a computer-readable storage medium comprising a stored program, wherein the program, when executed, performs the method described in any one of the first and / or second aspects.

[0063] In a sixth aspect, this application provides an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to perform the method described in any one of the first and / or second aspects through the computer program.

[0064] The device control method, apparatus, equipment, and medium provided in this application send a button splitting request to the application server based on the user's first operation on the target control device details page. The application server then processes the control button splitting and synchronizes the splitting completion notification message via a cloud platform, presenting the split load devices as new control devices. Furthermore, the client responds to the notification, retrieves and displays the split control device list. This method, through button splitting, allows users to directly control each load device without navigating to multiple layers of the main device's interface. The load devices are displayed as independent control devices, allowing users to easily locate and operate the target device, significantly reducing interaction steps, enabling rapid operation, and enhancing the user experience. Attached Figure Description

[0065] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

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

[0067] Figure 1 This is a schematic diagram of a scenario according to an embodiment of this application;

[0068] Figure 2 This is a flowchart illustrating a device control method according to an embodiment of this application. Figure 1 ;

[0069] Figure 3 This is a schematic diagram of the user interface before the buttons are separated according to this embodiment;

[0070] Figure 4 This is a schematic diagram of the user interface after the buttons are split according to this embodiment;

[0071] Figure 5 This is a flowchart illustrating a device control method according to an embodiment of this application. Figure 2 ;

[0072] Figure 6 This is a flowchart illustrating a device control method according to an embodiment of this application. Figure 3 ;

[0073] Figure 7 This is a schematic diagram of the structure of a device control apparatus according to an embodiment of this application;

[0074] Figure 8This is a schematic diagram of the structure of a device control apparatus according to an embodiment of this application;

[0075] Figure 9 This is a hardware schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0076] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0077] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0078] To address the problems in existing technologies, this application provides a device control method. Taking the user's first operation on the target control device's details page as the trigger point, a button splitting request is sent to the application server. The application server then processes the control button splitting and synchronizes the splitting completion notification message using a cloud platform, presenting the split load devices as new control devices. Furthermore, the client responds to the notification, retrieves and displays the split control device list. This method, through button splitting, allows users to directly control each load device without navigating to multiple layers of the main device's interface. Load devices are displayed as independent control devices, allowing users to easily locate and operate the target device, significantly reducing interaction steps, enabling rapid operation, and enhancing the user experience.

[0079] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application. For example... Figure 1As shown, client 101 is used by users to view and control devices. Specifically, it can display the details page of the target controlled device, respond to user operations such as split button requests, send requests to application server 102, and receive and display the device list returned by application server 102. Application server 102 is used to handle business logic and coordinate communication between client 101 and cloud platform 103. Specifically, application server 102 can receive control button split requests sent by client 101, perform split operations, send notification messages to client 101 through cloud platform 103, and return the split device list after receiving device list retrieval requests from client 101. Cloud platform 103 serves as an intermediate layer for device management, data processing, and communication, connecting application server 102 and the actual hardware device 104. Specifically, cloud platform 103 can receive instructions from application server 102, perform device status updates and send notification information, ensuring the consistency of device status and the reliability of communication.

[0080] The aforementioned device control methods can be widely applied to whole-house intelligent digital control application scenarios such as smart homes, smart home ecosystems, and smart residential ecosystems. The devices used in this method are not limited to PCs, mobile phones, tablets, smart air conditioners, smart range hoods, smart refrigerators, smart ovens, smart stoves, smart washing machines, smart water heaters, smart washing equipment, smart dishwashers, smart projectors, smart TVs, smart clothes racks, smart curtains, smart audio-visual systems, smart sockets, smart speakers, smart speakers, smart ventilation systems, smart kitchen and bathroom equipment, smart bathroom fixtures, smart robot vacuums, smart window cleaning robots, smart mopping robots, smart air purifiers, smart steam ovens, smart microwave ovens, smart water heaters, smart air purifiers, smart water dispensers, and smart door locks.

[0081] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Where there is no conflict between the embodiments, the following embodiments and features can be combined with each other. Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0082] Figure 2 This is a flowchart illustrating a device control method according to an embodiment of this application. Figure 1 .like Figure 2 As shown, the method includes:

[0083] S201. In response to the user's first operation on the details page of the target control device, the client sends a control button splitting request for the target control device to the application server, so that the application server splits the control buttons of each load device managed by the target control device; wherein, the load device after the control button splitting is used as the new control device.

[0084] Correspondingly, the server receives a request from the client to split the control buttons of the target control device.

[0085] In this step, the client refers to the interface through which the user interacts with the system, which can be an application installed on the user's device (such as a smartphone, tablet, etc.). The target control device refers to the main device that the user wants to perform button-based operations on, such as a smart switch or a central control panel. As the main device, it can connect to and manage multiple load devices. In the client application, the user can click on the device card to enter its details page, which includes, but is not limited to, the target control device being able to control all load devices. Specifically, the details page may include buttons corresponding to each load device for controlling the load device's on / off state and other operations.

[0086] The first operation refers to a specific action performed by the user on the target control device's details page. This could be clicking a button (such as the "Split Button" button) to trigger the control button splitting process. The application server is a crucial component of the system backend, responsible for handling business logic and coordinating communication between the client and the cloud platform. It receives client requests, executes the corresponding business logic processing, and returns the results to the client. Load devices refer to various devices connected to the target control device, such as lighting fixtures, sockets, curtain motors, underfloor heating systems, exhaust fans, and general-purpose switches. These devices originally existed as sub-devices, relying on the target control device for management and control.

[0087] For example, on the details page, users can also trigger a split operation by long-pressing a button. After detecting the long-press event, the client displays a confirmation dialog box asking the user if they want to perform the split operation. If the user confirms, a control button split request is constructed and sent to the application server. This requires adding long-press event recognition and processing logic to the client's UI event listener.

[0088] For example, a "Split Button" button can also be set for each button on the details page of the smart switch or central control panel on the client side. When the user clicks this button, an event handler function is triggered, constructing a control button splitting request and sending it to the application server.

[0089] S202, The application server splits the control buttons of each load device managed by the target control device; wherein, the load device after the control buttons are split is used as a new control device.

[0090] S203. The application server sends a first notification message to the client via the cloud platform indicating that the control button splitting is complete.

[0091] It's important to note that after receiving a request, the application server can use SQL statements to query the target control device's records in the database to find its associated load device information. Then, it inserts a new database record for each load device, storing it as an independent control device. This includes operations such as generating a new device representation and copying or transforming related attributes. For example, using a relational database (such as MySQL or PostgreSQL), it can create new records for each load device by executing INSERT statements and update the corresponding foreign key relationships.

[0092] For example, in high-concurrency scenarios, application servers can also combine distributed caching (such as Redis) with databases. When a split request is received, the system first checks the cache for information about the target control device and its load devices. If the information exists in the cache, the split operation is performed directly based on the cached data, and the new control device information is written to both the cache and the database. If the information does not exist in the cache, the relevant data is retrieved from the database, cached, and then the split operation is performed. This improves the system's response speed and performance.

[0093] The cloud platform is a comprehensive service platform that provides functions such as device connectivity, device management, data storage, data processing, and message push. In smart home scenarios, the cloud platform acts as an intermediary layer between application servers and devices, responsible for coordinating communication between devices and applications. The first notification message refers to the notification message sent by the application server to the client through the cloud platform after completing the control button splitting operation. This message informs the client that the splitting operation is complete and that a new list of control devices can be obtained.

[0094] S204. In response to the first notification message, the client sends a device list retrieval request to the application server.

[0095] S205. In response to the client's request to obtain the device list triggered by the first notification message, the application server returns a list of control devices after the control buttons have been split to the client.

[0096] S206. The client receives and displays the list of control devices after the control buttons are split from the control device list returned by the application server.

[0097] It's important to note that after separating the control buttons, users need a clear and intuitive way to view and manage all independently controllable devices. After obtaining the latest device list, the client interface should be able to update and synchronize device status information in real time, ensuring that the device information displayed to the user is up-to-date and preventing operational errors due to information lag.

[0098] For example, after receiving the first notification message from the application server via the cloud platform indicating that the control button splitting is complete, the client can trigger a refresh operation on the user's device list. At this time, the client can call the application server's service to send a device list retrieval request to obtain the latest device list after the button splitting, so as to update the device card data displayed in the user interface and allow the user to view the split device information.

[0099] The application server responds to the client's device list retrieval request triggered by the first notification message. The application server first calls the cloud platform's device list service to query device card information related to the user. Then, the application server combines the queried device list service data with the user's key-based data to assemble complete, segmented device card data. This process can obtain basic device information from the cloud platform and retrieve data such as device relationships after key-based data storage from its own data storage, ultimately forming a complete and updated device list, ready to be returned to the client.

[0100] The client receives and displays a list of control devices after the control buttons have been split from the application server. The application server can merge the data from the regular device cards and the split device cards to form a complete device card list. Then, the application server can instruct the client to refresh the user card list. The client updates the user interface based on the received new device card list data, allowing the user to see the split control devices in the device list, including sub-devices that were originally load devices now being displayed as independent control devices.

[0101] For example, after receiving the list of controlled devices, the client can directly update the display of the device list on the current page or interface. For instance, in a mobile application, the ListView control can be refreshed to display new device list items. Fade-in / fade-out animations, sliding insertions, and other animation effects can also be added when updating the device list display to improve the user experience. Simultaneously, the entire view or relevant sections can be refreshed to ensure the new device list is fully displayed to the user.

[0102] For example, Figure 3This is a schematic diagram of the user interface before the buttons are split according to this embodiment. The main interface includes cards for multiple devices. After the user clicks on the card of the smart switch (i.e., the target control device), the details page of the smart switch is displayed. This details page includes control buttons for the chandelier, spotlights, and main light. When the user clicks a button to turn on the light, the color of the button changes from dark to bright, indicating that the light is on. The details page also includes a "Split Button" button. When the user clicks this split button, the relevant splitting operation is performed, and the user interface after splitting is displayed to the user. Figure 4 This is a schematic diagram of the user interface after the buttons are split according to this embodiment. After the user selects to split the buttons of the smart switch, the main interface will refresh and display device cards. At this time, it includes device cards for the chandelier, spotlights, and main light after the smart switch buttons are split, as well as other independent devices on the original main interface: air conditioner and television. The user controls the corresponding device by clicking the corresponding card.

[0103] The device control method provided in this application sends a button splitting request to the application server based on the user's first operation on the details page of the target control device. The application server then processes the control button splitting and synchronizes the splitting completion notification message via the cloud platform, presenting the split load devices as new control devices. Furthermore, the client responds to the notification, retrieves and displays the split control device list. This method, through button splitting, allows users to directly control each load device without navigating to multiple layers of the main device's interface. The load devices are displayed as independent control devices, allowing users to easily locate and operate the target device, significantly reducing interaction steps, enabling rapid operation, and enhancing the user experience.

[0104] Figure 5 This is a flowchart illustrating a device control method according to an embodiment of this application. Figure 2 .like Figure 5 As shown, the method includes:

[0105] S501. In response to the control button splitting request, query the cloud platform for the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and the control buttons; the attribute information is used to characterize the corresponding control scenario.

[0106] In this step, attribute information refers to detailed information about the functions and control methods of the target control device and its load devices. Specifically, attribute information is used to characterize the corresponding control scenario. The attribute information of the target control device includes, but is not limited to, device type (e.g., smart switch, central control panel), supported functions (e.g., single-button control, multi-button control), and physical button layout (e.g., number of buttons, button positions). The attribute information of the load devices includes, but is not limited to, the corresponding number of devices, device type (e.g., lamps, sockets, curtain motors), device functions (e.g., switch, dimming, color adjustment), and device status (e.g., on / off, brightness value). In some cases, each button in the target control device has a corresponding load device, but based on the control scenario of that button or load device, the load device may indicate a single physical device, or it may indicate a group of physical devices corresponding to a certain scenario, such as a group of devices corresponding to complex scenarios like "away mode" or "home mode".

[0107] The mapping relationship between load devices and control buttons refers to the load device and its control function corresponding to each control button. For example, button 1 on a smart switch controls the main light switch in the living room, button 2 controls the reading light switch in the bedroom, and button 3 controls the "away mode" (turns off all lights and unnecessary appliances).

[0108] For example, the application server can directly query the attribute information and mapping relationships of the target control device and its load devices by calling the device management API provided by the cloud platform. The application server can also query the identifier of the target control device from its own database, and then jointly query the cloud platform's database or data storage service to obtain the relevant attribute information and mapping relationships. Furthermore, the application server subscribes to the cloud platform's message queue. When the attribute information or mapping relationship of the target control device changes, the cloud platform sends an update message to the message queue. Upon receiving the message, the application server promptly updates its locally cached data, allowing it to directly use the locally cached data when queries are needed, thus improving query efficiency.

[0109] S502. Based on the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load device and the control button, construct the control button split data of each load device.

[0110] In this step, the control button split data includes, but is not limited to, the independent control information of each load device after splitting, such as device representation, device type, and the load device corresponding to the control button. When constructing the control button split data, according to predefined rules and strategies, the multiple load devices mounted inside the smart switch or central control panel, i.e., the target control device, are parsed, converted, and constructed into virtual device card data that can be independently displayed and controlled in the user's device list.

[0111] For example, a data model can be constructed in memory based on the retrieved attribute information and mapping relationships to represent the control button splitting data for each load device. This data model can be an object, a dictionary, or other data structure to facilitate subsequent processing and storage. The constructed control button splitting data is then inserted into or updated in the database. If the load device has already been split, its corresponding record is updated; otherwise, a new record is inserted. This ensures that the data in the database is up-to-date, providing accurate data support for subsequent queries and control. In addition to updating the database, the control button splitting data can also be updated in a local cache. The next time the device list is needed, data can be retrieved from the cache first, improving response speed.

[0112] S503. Send a first notification message to the client via the cloud platform indicating that the control button splitting is complete.

[0113] S504. In response to the device list retrieval request triggered by the client based on the first notification message, obtain the user's control button split data and query the user's control device card data from the cloud platform; the control button split data includes: card data of each load device after the control buttons are split.

[0114] S505. Merge the card data of the user's control device and the card data of each load device after the button is split to obtain a list of control devices after the control button is split.

[0115] S506. Return the list of control devices after the control buttons have been split to the client.

[0116] It's important to note that the control device card data refers to the data used to display control device information on the client side, including but not limited to the device's icon, name, control button data, and status. The control button split data contains detailed information about each individual load device after splitting, while the user's control device card data reflects the cards of all control devices originally displayed to the user; some are smart switches / central control panels, while others are ordinary devices. By merging the control button split data and the control device card data—that is, hiding the target control device's card before splitting while retaining the cards of ordinary devices—a complete device list can be constructed. This list includes not only ordinary control devices but also the split load devices.

[0117] For example, the application server can perform a data merging operation in memory, combining ordinary device card data and split device card data into a single list according to certain rules (such as device type, device location, etc.). The application server can also organize the ordinary device card data and split device card data into different view components, and then combine these components into a complete view structure, returning it to the client as the final list of controlled devices.

[0118] For example, the method further includes:

[0119] Obtain the status data of the load device after the control buttons are split from the cloud platform;

[0120] If the status data of the load device changes, the list of control devices is updated and synchronized to the client.

[0121] In this example, status data refers to the latest status of the load devices, including but not limited to whether the device is online, its on / off status, and its operating parameters. By monitoring the status changes of the load devices after the control buttons are split in real time, the control device list can be automatically updated when the status of a load device changes, ensuring that the device status seen by the user on the client is up-to-date. For example, if a light fixture is manually turned off, the client's device list will immediately reflect this change, displaying the light fixture as off.

[0122] The device control method provided in this application not only simplifies the user's operation path, allowing the user to operate the load device directly without having to enter the main device interface step by step, but also ensures that the user can keep track of the latest status of the device at any time by acquiring device attributes and mapping relationships in real time, thereby effectively improving the user experience and the flexibility of system interaction.

[0123] Figure 6 This is a flowchart illustrating a device control method according to an embodiment of this application. Figure 3 .like Figure 6 As shown, it includes:

[0124] S601. In response to the user's second operation on the details page, the client sends a request to the application server to split and turn off the control buttons of the target control device.

[0125] Correspondingly, the application server receives a request from the client to split or turn off the control buttons of the target control device.

[0126] S602, The application server deletes the control button splitting data of each load device managed by each of the aforementioned control devices.

[0127] It should be noted that users can further disable the control button splitting function as needed, restoring the original device control mode, that is, managing the load device again as a sub-device of the master device. After the user performs a specific operation on the target control device details page of the client (such as clicking the "Disable Split" button), the client generates a message and sends it to the application server to request the disabling of the previously enabled control button splitting function.

[0128] Furthermore, clean up the data related to the control button splitting to ensure a return to the unsplitted state, that is, to treat the load device as a sub-device of the master device again. Specifically, after the application server receives a control button splitting shutdown request, it queries the database or cache for splitting data related to the target control device. The application server then performs a data deletion operation, removing the split load device information and the associated mappings. If a caching mechanism is used, the cache also needs to be updated synchronously to ensure data consistency between the cache and the database.

[0129] S603. The application server sends a second notification message to the client via the cloud platform, indicating that the control button splitting and closing is complete.

[0130] S604. In response to the second notification message, the client sends a device list retrieval request to the application server.

[0131] S605. In response to the device list retrieval request triggered by the client based on the second notification message, the application server returns a list of control devices after the control buttons are split and turned off to the client.

[0132] S606. The client receives and displays the list of control devices after the control buttons are split and turned off, returned by the application server.

[0133] It should be noted that after receiving the notification that the split has been closed, the client sends a request to the application server to obtain a list of devices reflecting the status after the split has been closed, so that it can be displayed on the client and allow users to see the status of the devices after the split has been closed.

[0134] For example, after receiving a device list retrieval request, the application server can query the database or cloud platform to obtain information about the target control device and its load devices, directly retrieve the original device list data in its unsplit state from the database or cache, encapsulate the retrieved data into a device list, and return it to the client.

[0135] The device control method provided in this application allows users to flexibly switch control modes for smart home devices by enabling them to disable the control button splitting function on the client side. When users no longer need split control, they can restore the original master-sub-device control mode with one click, simplifying the operation process. After deleting the split data, the device list in the unsplit state is quickly rebuilt and synchronized, ensuring that users can view and control the latest status of the devices in real time, improving the smoothness of the user experience and the usability of the system.

[0136] Corresponding to the above method, this application also provides a device control apparatus. Figure 7 This is a schematic diagram of the structure of a device control apparatus according to an embodiment of this application; as shown below. Figure 7 As shown, the device includes:

[0137] The sending module 701 is used to respond to the user's first operation on the details page of the target control device, send a control button splitting request of the target control device to the application server, so that the application server splits the control buttons of each load device managed by the control device, and synchronizes a first notification message of the completion of control button splitting through the cloud platform; wherein, the load device after control button splitting is used as the new control device.

[0138] The acquisition module 702 is used to send a device list acquisition request to the application server in response to the first notification message;

[0139] The receiving module 703 is used to receive and display the list of control devices after the control buttons are split from the control device list returned by the application server.

[0140] In one possible implementation, the sending module 701 is further configured to:

[0141] In response to the user’s second operation on the details page, a control button splitting and closing request for the target control device is sent to the application server, so that the application server deletes the control button splitting data of each load device managed by each control device, and synchronizes a second notification message of control button splitting and closing completion through the cloud platform.

[0142] In response to the second notification message, a device list retrieval request is sent to the application server;

[0143] Receive and display the list of control devices after the control buttons are split and turned off, returned by the application server.

[0144] Corresponding to the above method, this application also provides a device control apparatus. Figure 8 This is a schematic diagram of the structure of a device control apparatus according to an embodiment of this application; as shown below. Figure 8 As shown, the device includes:

[0145] The receiving module 801 is used to receive the control button splitting request of the target control device sent by the client;

[0146] The splitting module 802 is used to split the control buttons of each load device managed by the target control device; wherein the load device after the control buttons are split is used as a new control device.

[0147] Sending module 803 is used to send a first notification message to the client via the cloud platform indicating that the control button splitting is complete;

[0148] The return module 804 is used to respond to the client's request to obtain the device list triggered by the first notification message, and return to the client a list of control devices after the control buttons are split.

[0149] In one possible implementation, the split module 802 is specifically used for:

[0150] In response to the control button splitting request, the cloud platform is queried for the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and the control buttons; the attribute information is used to characterize the corresponding control scenario.

[0151] Based on the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and control buttons, control button splitting data for each load device is constructed.

[0152] In one possible implementation, the return module 804 is specifically used for:

[0153] The system obtains the user's control button splitting data and queries the user's control device card data from the cloud platform; the control button splitting data includes: card data of each load device after the control buttons are split.

[0154] By integrating the card data of the user's control device and the card data of each load device after the button is split, a list of control devices after the control button is split is obtained.

[0155] Return the list of control devices after the control buttons have been split to the client.

[0156] In one possible implementation, the return module 804 is also used for:

[0157] Obtain the status data of the load device after the control buttons are split from the cloud platform;

[0158] If the status data of the load device changes, the list of control devices is updated and synchronized to the client.

[0159] In one possible implementation, the split module 802 is also used for:

[0160] Receive a request from the client to split or turn off the control buttons of the target control device;

[0161] Delete the control button split data for each load device managed by each of the aforementioned control devices;

[0162] A second notification message is sent to the client via the cloud platform to indicate that the control button splitting and closing is complete;

[0163] In response to the client's request to retrieve the device list triggered by the second notification message, a list of control devices after the control buttons have been split and turned off is returned to the client.

[0164] Figure 9 This is a hardware schematic diagram of an electronic device according to an embodiment of this application. For example... Figure 9 As shown, the electronic device 90 provided in this embodiment includes at least one processor 901 and a memory 902. The device 90 also includes a communication component 903. The processor 901, memory 902, and communication component 903 are connected via a bus 904.

[0165] In a specific implementation, at least one processor 901 executes computer execution instructions stored in the memory 902, causing at least one processor 901 to perform the above method.

[0166] The specific implementation process of processor 901 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0167] In the above Figure 9 In the illustrated embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0168] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0169] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0170] This application also provides a computer-readable storage medium storing computer-executable instructions / computer programs, which, when executed by a processor, implement the method described above.

[0171] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0172] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0173] The division of units described herein is merely a logical functional division. 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 coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0174] 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.

[0175] In addition, the functional units in the various embodiments of the present invention 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.

[0176] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0177] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0178] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above 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 or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A device control method, characterized in that, include: In response to the user's first operation on the details page of the target control device, a control button splitting request for the target control device is sent to the application server, so that the application server splits the control buttons for each load device managed by the target control device, and synchronizes a first notification message on the cloud platform to complete the control button splitting; wherein, the load device after the control button splitting is used as the new control device. In response to the first notification message, a device list retrieval request is sent to the application server; Receive and display the list of control devices after the control buttons are split from the control buttons returned by the application server.

2. The equipment control method according to claim 1, characterized in that, The method further includes: In response to the user’s second operation on the details page, a control button splitting and closing request for the target control device is sent to the application server, so that the application server deletes the control button splitting data of each load device managed by each control device, and synchronizes a second notification message of control button splitting and closing completion through the cloud platform. In response to the second notification message, a device list retrieval request is sent to the application server; Receive and display the list of control devices after the control buttons are split and turned off, returned by the application server.

3. A device control method, characterized in that, include: Receive a request from the client to split the control buttons of the target control device; The control buttons of each load device managed by the target control device are split; wherein, the load device after the control buttons are split is used as a new control device; The cloud platform sends a first notification message to the client indicating that the control button splitting is complete. In response to the client's request to retrieve the device list triggered by the first notification message, a list of control devices after the control buttons have been split is returned to the client.

4. The equipment control method according to claim 3, characterized in that, The step of splitting the control buttons for each load device managed by the target control device includes: In response to the control button splitting request, the cloud platform is queried for the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and the control buttons; the attribute information is used to characterize the corresponding control scenario. Based on the attribute information of the target control device, the attribute information of each load device, and the mapping relationship between the load devices and control buttons, control button splitting data for each load device is constructed.

5. The equipment control method according to claim 3, characterized in that, The step of returning the list of control devices after the control buttons have been split to the client includes: The system acquires the user's control button breakdown data and queries the user's control device card data from the cloud platform; the control button breakdown data includes: card data of each load device after the control buttons are broken down. By integrating the card data of the user's control device and the card data of each load device after the button is split, a list of control devices after the control button is split is obtained. Return the list of control devices after the control buttons have been split to the client.

6. The equipment control method according to claim 3 or 5, characterized in that, The method further includes: Obtain the status data of the load device after the control buttons are split from the cloud platform; If the status data of the load device changes, the list of control devices is updated and synchronized to the client.

7. The equipment control method according to claim 4, characterized in that, The method further includes: Receive a request from the client to split or turn off the control buttons of the target control device; Delete the control button split data for each load device managed by each of the aforementioned control devices; A second notification message is sent to the client via the cloud platform to indicate that the control button splitting and closing is complete; In response to the client's request to retrieve the device list triggered by the second notification message, a list of control devices after the control buttons have been split and turned off is returned to the client.

8. A device control apparatus, characterized in that, include: The sending module is used to respond to the user's first operation on the details page of the target control device, and send a control button splitting request for the target control device to the application server, so that the application server splits the control buttons for each load device managed by the control device, and synchronizes a first notification message on the cloud platform to complete the control button splitting; wherein, the load device after the control button splitting is used as the new control device. The acquisition module is used to send a device list acquisition request to the application server in response to the first notification message; The receiving module is used to receive and display the list of control devices after the control buttons are split from the control buttons returned by the application server.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method of any one of claims 1 to 7.

10. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method of any one of claims 1 to 7 through the computer program.

Images