Intelligent sound box cross-device cooperative control method, device, equipment and medium

CN122933302APending Publication Date: 2026-10-16ZHEJIANG HUIYI NETWORK TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610976847.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-02
Publication Date
2026-10-16

AI Technical Summary

Technical Problem

然而,传统系统需要客人逐一发出多条指令,操作繁琐且体验差

Benefits of technology

[0010] The above description is merely an overview of the technical solutions of the embodiments of this application. In order to better understand the technical means of the embodiments of this application and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of this application more obvious and understandable, specific implementation methods of this application are described below.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122933302A_ABST
    Figure CN122933302A_ABST
Patent Text Reader

Abstract

The present disclosure provides a smart speaker cross-device cooperative control method, device, equipment and medium, comprising: in response to the request response package sent by the networking device, the device information of the networking device is entered into the device registry, and a unique device code is allocated for each registered device; if the device state of all registered devices is online, the device execution operation, operation control parameter, execution priority and device execution time limit are generated according to the cooperative device code; and the device execution operation, operation control parameter, execution priority and device execution time limit are sent; if there is an abnormal device with offline device state among all registered devices, the device execution operation, operation control parameter, execution priority and device execution time limit are generated according to the cooperative device code; and the corresponding device execution operation, operation control parameter, execution priority and device execution time limit are sent; and the execution exception prompt of the abnormal device is generated. Thus, the user satisfaction is effectively improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of this disclosure relate to the field of device control, and more specifically, to a method, apparatus, device, and medium for cross-device collaborative control of a smart speaker. Background Technology

[0002] With the rapid development of IoT and AI technologies, smart speakers have become the core control hub for intelligent hotel rooms. Through voice interaction, guests can control various devices such as lights, air conditioning, curtains, and televisions, greatly enhancing their stay experience.

[0003] In real-world applications, customer needs often involve the coordinated operation of multiple devices. For example, "sleep mode" requires simultaneously turning off lights, lowering the air conditioning temperature, closing curtains, and muting the TV; "movie mode" requires dimming lights, closing curtains, turning on the TV, and adjusting the volume. However, traditional systems require customers to issue multiple commands one by one, resulting in cumbersome operations and a poor user experience. Summary of the Invention

[0004] The embodiments described herein provide a method, apparatus, device, and medium for cross-device collaborative control of a smart speaker, overcoming the aforementioned problems.

[0005] In a first aspect, according to the present disclosure, a cross-device collaborative control method for a smart speaker is provided, applied to a smart speaker, comprising: A device discovery broadcast packet is sent to the local area network within the target area. The device discovery broadcast packet is used to discover and request networked devices within the target area to conduct communication interaction. In response to the request response packet sent by the networked device, the device information of the networked device is entered into the device registry, and a unique device code is assigned to each registered device to establish a communication connection with each registered device. The smart speaker is abstracted as the main intelligent agent, and the registered device is abstracted as a sub-intelligent agent; and a device state sharing mechanism is established between the sub-intelligent agent and the main intelligent agent. If the received user control instruction is a multi-device control instruction, then the user control instruction is defined as a multi-device collaborative control instruction sequence according to the scenario information. The multi-device collaborative control instruction sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit. If it is determined that all registered devices are online according to the device status sharing mechanism, then according to the collaborative device code in the multi-device collaborative control instruction sequence, the device execution operation, operation control parameters, execution priority, and device execution time limit of the corresponding sub-agent are generated; and the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit are sent to each sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation based on the operation execution parameters according to the execution priority; If, according to the device state sharing mechanism, it is determined that there are abnormal devices among all the registered devices whose device state is offline, then, based on the collaborative device code in the multi-device collaborative control instruction sequence, the device execution operation, operation control parameters, execution priority, and device execution time limit corresponding to each online registered device are generated; and the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit are sent to each online registered device's corresponding sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation according to the operation execution parameters based on the execution priority; and, an execution abnormality prompt for the abnormal device is generated.

[0006] Secondly, according to the present disclosure, a cross-device collaborative control device for a smart speaker is provided, applied to a smart speaker, comprising: The registration module is used to send device discovery broadcast packets to the local area network within the target area. The device discovery broadcast packets are used to discover and request networked devices within the target area to conduct communication interactions. In response to the request response packets sent by the networked devices, the module records the device information of the networked devices into the device registry and assigns a unique device code to each registered device to establish a communication connection with each registered device. A module is established to abstract the smart speaker as a main intelligent agent and the registered device as a sub-intelligent agent; and to establish a device state sharing mechanism between the sub-intelligent agent and the main intelligent agent. The definition module is used to define the received user control instruction as a multi-device collaborative control instruction sequence according to the scenario information if the received user control instruction is a multi-device control instruction. The multi-device collaborative control instruction sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit. The first generation module is configured to, if it is determined according to the device status sharing mechanism that all the registered devices are online, generate the device execution operation, operation control parameters, execution priority, and device execution time limit for the corresponding sub-agent based on the collaborative device code in the multi-device collaborative control instruction sequence; and send the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation based on the operation execution parameters according to the execution priority; The second generation module is configured to, if it is determined according to the device state sharing mechanism that there are abnormal devices among all the registered devices whose device state is offline, generate, according to the collaborative device code in the multi-device collaborative control instruction sequence, the device execution operation, operation control parameters, execution priority, and device execution time limit for each online registered device's corresponding sub-agent; and send the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each online registered device's corresponding sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation according to the operation execution parameters based on the execution priority; and generate an execution exception prompt for the abnormal device.

[0007] Thirdly, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the smart speaker cross-device collaborative control method as described in any of the above embodiments.

[0008] Fourthly, a computer-readable storage medium is provided, on which a computer program is stored, and when executed by a processor, the computer program implements the steps of the smart speaker cross-device collaborative control method as described in any of the above embodiments.

[0009] The smart speaker cross-device collaborative control method provided in this application embodiment sends a device discovery broadcast packet to the local area network within the target area. The device discovery broadcast packet is used to discover and request networked devices within the target area to conduct communication interaction. In response to the request response packet sent by the networked device, the device information of the networked device is recorded in the device registry, and a unique device code is assigned to each registered device to establish a communication connection with each registered device. The smart speaker is abstracted as a main intelligent agent, and the registered devices are abstracted as sub-intelligent agents. A device state sharing mechanism is established between the sub-intelligent agents and the main intelligent agent. If the received user control command is a multi-device control command, the user control command is defined as a multi-device collaborative control command sequence according to the scene information. The multi-device collaborative control command sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit. If it is determined that the device status of all registered devices is online according to the device state sharing mechanism, the corresponding sub-intelligent agent is generated according to the collaborative device code in the multi-device collaborative control command sequence. The system assigns device execution operations, operation control parameters, execution priorities, and execution time limits to each sub-agent. It then sends these parameters to each sub-agent, enabling them to control the corresponding registered device to perform the operation based on the execution parameters when the execution time limit is reached. If, based on the device state sharing mechanism, there are offline abnormal devices among all registered devices, the system generates device execution operations, operation control parameters, execution priorities, and execution time limits for each online registered device's corresponding sub-agent based on the collaborative device code in the multi-device collaborative control instruction sequence. This information is then sent to the corresponding online registered device's corresponding sub-agent, ensuring that when the execution time limit is reached, the sub-agent controls the corresponding registered device to perform the operation according to the execution parameters based on the execution priority. An execution exception message for the abnormal device is also generated. In this way, complex scenario setups can be quickly completed through multi-device collaborative control, reducing user operation steps and effectively improving user satisfaction.

[0010] The above description is merely an overview of the technical solutions of the embodiments of this application. In order to better understand the technical means of the embodiments of this application and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of this application more obvious and understandable, specific implementation methods of this application are described below. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments will be briefly described below. It should be understood that the drawings described below only relate to some embodiments of this disclosure and are not intended to limit this disclosure, wherein: Figure 1 This is a flowchart illustrating a cross-device collaborative control method for smart speakers provided in this disclosure.

[0012] Figure 2 This is a schematic diagram of the structure of a smart speaker cross-device collaborative control device provided in this disclosure.

[0013] Figure 3 This is a schematic diagram of the structure of a computer device provided in this disclosure.

[0014] It should be noted that the elements in the attached diagram are schematic and not drawn to scale. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are also within the scope of protection of this disclosure.

[0016] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this subject matter pertains. It will be further understood that terms such as those defined in commonly used dictionaries shall be interpreted as having the meaning consistent with their meaning in the context of the specification and in the relevant art, and shall not be interpreted in an idealized or overly formal form unless otherwise explicitly defined herein. As used herein, the statement of “connecting” or “coupling” two or more parts together shall mean that these parts are directly joined together or joined through one or more intermediate components.

[0017] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of the phrase "embodiment" in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0018] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists, A and B exist simultaneously, or B exists. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Terms such as "first" and "second" are only used to distinguish one component (or part of a component) from another component (or another part of a component).

[0019] In the description of this application, unless otherwise stated, "multiple" means two or more (including two), and similarly, "multiple groups" means two or more (including two groups).

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

[0021] Figure 1 This is a flowchart illustrating a cross-device collaborative control method for a smart speaker provided in an embodiment of this disclosure, applied to a smart speaker. For example... Figure 1 As shown, the specific process of the smart speaker cross-device collaborative control method includes: S110. Send a device discovery broadcast packet to the local area network within the target area. The device discovery broadcast packet is used to discover and request networked devices within the target area to conduct communication interaction. In response to the request response packet sent by the networked device, record the device information of the networked device into the device registry and assign a unique device code to each registered device to establish a communication connection with each registered device.

[0022] For example, after the smart speaker is turned on, it can proactively send a device discovery broadcast packet based on MQTT-SN / SSDP to the local area network in the guest room. The device discovery broadcast packet contains the speaker device ID, communication protocol type, service port and device discovery request command.

[0023] The network-connected controllable devices in the guest room (such as lights, air conditioners, curtains, TVs, etc.) have built-in protocol parsing modules. After receiving a device discovery broadcast packet, if it matches the preset communication protocol, it will automatically return a device response packet (i.e., a request response packet) to the smart speaker. The request response packet contains the device's unique identifier, device type, device model, set of executable operations (such as turning lights on / off, adjusting brightness; adjusting air conditioner temperature, switching modes, etc.), status reporting address, and communication parameters.

[0024] After receiving response packets from all devices, the smart speaker verifies and deduplicates device information, eliminating invalid or offline device information. Verified device information is then entered into the device registry, assigning each device a unique in-room device code and establishing a mapping between device type and executable operations. Upon completion of registration, the smart speaker sends a registration confirmation command to each registered device. Once the registered device returns a confirmation receipt, the entire device registration process is complete. Simultaneously, the smart speaker synchronizes the device registry to the hotel's cloud management platform, achieving cloud backup of device information.

[0025] S120. Abstract the smart speaker into a main intelligent agent and the registered device into a sub-intelligent agent; and establish a device state sharing mechanism between the sub-intelligent agents and the main intelligent agent.

[0026] Each device can be abstracted as an agent, and devices collaborate through message passing. Specifically, each registered device is encapsulated as an agent: each registered guest room device is abstracted into an agent, and each device agent contains five core modules: a perception module, a decision-making module, a communication module, an execution module, and a status module. Each module operates independently but communicates with each other. The perception module is used to collect the device's own status, environmental data, and instructions issued by the speaker; the decision-making module is used to determine its own execution capabilities and execution strategies based on instructions and device constraints; the communication module is used to realize message passing between agents and between agents and smart speakers based on the MQTT protocol; the execution module is used to execute the final device operation instructions; and the status module is used to store the device's operating status and the agent's execution status in real time.

[0027] Configure Agent identity and communication address for each registered device: Assign a unique Agent ID to each device Agent, which is mapped one-to-one with the device code. At the same time, configure a unique communication address for the Agent and establish a guest room Agent communication topology network. The smart speaker acts as the main Agent, which is responsible for coordinating the work of all device Agents. Each device Agent is a sub-Agent, which can realize point-to-point direct communication.

[0028] Define a message passing protocol: unify the message passing format between agents. Message types include instruction requests, execution capability feedback, dependency notifications, execution status reports, and exception alarms. All messages are encapsulated in JSON format, including the sender agent ID, receiver agent ID, message type, message content, timestamp, and signature information.

[0029] Preset Agent Collaboration Rules: Preset collaboration rules between the main agent and sub-agents, and among sub-agents. Specific rules may include "main agent commands have higher priority than sub-agent interaction commands," "sub-agents must immediately report any execution errors to the main agent," and "sub-agents with dependencies must synchronize messages in advance." Agent Lifecycle Management: The smart speaker, acting as the main agent, monitors the operational status of each sub-agent in real time. When a sub-agent goes online / offline / abnormal, the agent topology network is automatically updated and reported to the hotel cloud to ensure the integrity of the collaborative network.

[0030] The device status sharing mechanism enables real-time synchronization of the current status of all devices to the smart speaker. Status updates utilize a publish-subscribe model, proactively pushing updates when device status changes to ensure the speaker is up-to-date. This mechanism is a distributed status synchronization system built on a publish-subscribe (Pub / Sub) model, covering the smart speaker and all controllable devices in the guest room. The smart speaker serves as the core status hub, with each device acting as a status publishing node, and the speaker simultaneously acting as a subscription node for all device statuses. This enables real-time collection, transmission, storage, and synchronization of device status, ensuring that the speaker and the hotel cloud can obtain the true operating status of all devices in real time, providing a data foundation for collaborative control.

[0031] Specifically, a local status theme subscription server can be built using smart speakers to create a dedicated status theme (e.g., / hotel / room101 / light / main / state) for each registered device in the guest room, while also creating a global status theme for the scene (e.g., / hotel / room101 / global / state). Protocol adaptation is performed for each controllable device, adding a protocol conversion module for devices that do not natively support Pub / Sub mode to ensure all devices can publish status information to their dedicated status themes. Device status proactive reporting rules are configured: when a device status undergoes a proactive change (e.g., user manually adjusting air conditioning temperature), a passive change (e.g., speaker controlling light to turn off), or a timed heartbeat (default 30 seconds), the current status data is automatically reported. The status data (including status value, change time, and change trigger method) is encapsulated in JSON format and published to its own dedicated status theme. The smart speaker continuously subscribes to the dedicated status themes of all devices. After receiving status data, it updates the local device status library in real time and pushes the status change information to the scene-wide status theme. It also establishes a status anomaly detection rule: if the speaker does not receive heartbeat / status data from a device for more than 60 seconds, it immediately sends a status query command to the device. If there is no response after 3 consecutive queries, the device is marked as "offline," and the device status library and cloud information are updated. The hotel cloud management platform subscribes to the scene-wide status theme of each guest room to realize remote synchronization of guest room device status, providing data support for hotel operation and maintenance. This establishes a device status sharing mechanism between the sub-smart agent and the master smart agent.

[0032] S130. If the received user control instruction is a multi-device control instruction, the user control instruction is defined as a multi-device collaborative control instruction sequence according to the scenario information. The multi-device collaborative control instruction sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit.

[0033] The device execution operation is such as "increase / decrease air conditioner temperature", the operation control parameter is such as "+5℃", and the device execution time limit is such as "after five minutes" or "3:00-4:00". The execution priority can be determined by weighting user preference (devices that users frequently adjust have higher priority), dependency relationship (devices that are depended on have higher priority), and response time (devices with slower response times are started first).

[0034] In some embodiments, user control instructions are defined as a multi-device collaborative control instruction sequence based on scenario information, including: semantic parsing of user control instructions to extract target objects, expected states, and time constraints; matching scenario information with a preset scenario template library to determine the set of registered devices required for linkage in the user's scenario and their collaborative relationships; generating corresponding device execution operations and operation control parameters for each registered device in the set based on the expected state and time constraints, and determining the execution priority of each registered device according to the dependencies and execution sequence between each registered device; and assigning a corresponding device execution time limit to each registered device according to the time constraints and system load information, thereby obtaining a multi-device collaborative control instruction sequence containing collaborative device codes, device execution operations, operation control parameters, execution priorities, and device execution time limits.

[0035] The scene template library contains a variety of typical guest room scene templates, such as "Sleep Mode", "Wake-up Mode", and "Movie Viewing Mode". Each scene template defines the set of devices that are activated by default in that scene, the basic status parameters of each device, and the standard collaborative relationships between devices.

[0036] Dependencies can be determined based on the physical and logical dependencies between registered devices. Physical dependencies are the prerequisite hardware conditions required for a device to start or perform a specific operation, such as the color temperature adjustment of smart lights depending on the lights being turned on. Logical dependencies are the timing requirements defined by the business scenario, such as the requirement in "sleep mode" that the lights will only dim after the curtains are completely closed, in order to avoid discomfort caused by direct eye contact with the light source.

[0037] Additionally, user habits can be learned, such as scene trigger time (when users typically activate a scene); parameter preferences (user preferences for parameters such as temperature and brightness); manual adjustments (user manual adjustment behavior after scene activation); usage frequency (frequency of use for each scene); and automatic optimization of scene parameters. For example, in various smart scenes of a hotel, configurable quantifiable indicators / operation command values ​​related to the operating status of controllable devices and scene execution logic are the core configuration items for scene linkage. The core parameters of different scenes are strongly correlated with guest room equipment. For example, the scene type is "sleep mode"; the devices involved include lights, air conditioning, curtains, and television; the scene parameters are: light brightness (0%), light color temperature (none), air conditioning temperature (°C), air conditioning fan speed, air conditioning mode (cooling / heating / sleep), curtain opening degree (0%), television volume (0%), and television on / off. The scene type is "Movie Viewing Mode"; the equipment involved includes lights, curtains, TV, and audio equipment; the scene parameters are: main light brightness (0%), ambient light brightness (30%), ambient light color temperature (3000K), curtain opening degree (0%), TV switch (on), TV volume (15), audio volume (20), and audio mode (cinema). The scene type is "Reading Mode"; the equipment involved includes bedside lamps, floor lamps, and air conditioners; the scene parameters are: bedside lamp brightness (60%), bedside lamp color temperature (4000K), floor lamp brightness (50%), air conditioner temperature (°C), and air conditioner fan speed (low). The scene type is "Check-in Mode"; the equipment involved includes all equipment; the scene parameters are: total light brightness (80%), curtain opening degree (100%), air conditioner temperature (25°C), TV switch (on), TV volume (10), and fresh air system fan speed (medium).

[0038] Based on historical data from the user behavior database, the scene parameters can be automatically updated through a weighted iterative optimization algorithm. Specifically, taking a single user / room as the unit, relevant data of the target scene can be extracted from the user behavior database, including scene trigger records, manual device adjustment records after the scene starts, adjustment time, adjustment parameter values ​​and usage frequency; the user's manual adjustment behavior is marked. If the user adjusts a device parameter within 5 minutes after the scene starts, it is determined that "the user is not satisfied with the default value of the parameter". The parameter difference before and after the adjustment and the final stable value are recorded; the weight of each adjustment is calculated according to formula (1) (λ is 0.001, and the time unit is minutes). The more recent the adjustment behavior, the higher the weight and the greater the impact on parameter optimization.

[0039] (1) In formula (1), λ represents the attenuation coefficient; t now Indicates the current time. t i Indicates the first i The timing will be adjusted.

[0040] According to formula (2), with the final stable value manually adjusted by the user as the objective, the optimal value of the scene parameters is calculated, and the loss function is used. The mean square error between the default parameter value and the user-adjusted value.

[0041] (2) In formula (2), Indicates the optimal scenario parameters; N Indicates the number of times the user has made adjustments in history; Indicates the first i The weight of each adjustment (the more recent the adjustment, the greater the weight); Indicates parameters and user's first i The loss function is adjusted; the optimization objective is to find the parameter configuration that minimizes the user's adjustment requirements.

[0042] The system replaces the original default parameters of the scenario with the calculated optimal parameters, generates a personalized scenario parameter configuration file, and automatically takes effect the next time the user triggers the scenario. The system recalculates user behavior data every 24 hours and iteratively updates scenario parameters based on the latest user habits to ensure that the parameters always match user preferences.

[0043] In some embodiments, the method further includes: if the received user control instruction is a single-device control instruction, generating a single-device independent control instruction sequence for the corresponding registered device based on the user control instruction, wherein the single-device independent control instruction sequence includes: independent device code, device execution operation, operation control parameters, and device execution time limit; sending the device execution operation, operation control parameters, and device execution time limit to the corresponding sub-agent of the independent device code, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation based on the operation execution parameters.

[0044] For example, if the user control command is "adjust the brightness of the master bedroom lamp to 50%", the generated single-device independent control command sequence includes: independent device code: bedroom_lamp_001; device operation: adjust brightness; operation control parameter: 50%; device execution time limit: current time + 200 milliseconds. The smart speaker can send the single-device independent control command sequence to the sub-agent responsible for the master bedroom lighting. The sub-agent caches the command locally and starts a timed detection. When the system time reaches the set execution time limit, it immediately sends a dimming command to the lamp, ensuring that the response delay is controlled within 200 milliseconds, facilitating fast and accurate user control of a single device.

[0045] S140. If it is determined that all registered devices are online according to the device status sharing mechanism, then generate the corresponding sub-agent's device execution operation, operation control parameters, execution priority, and device execution time limit according to the collaborative device code in the multi-device collaborative control instruction sequence; and send the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each sub-agent.

[0046] For example, the user control command is "movie viewing mode." This scenario requires simultaneous adjustment of multiple devices, including the main living room light, ambient light, curtains, and projector. The multi-device collaborative control command sequence includes: Collaborative device code set: [living_main_light_001, living_ambient_light_002, living_curtain_003, living_projector_004]; The device operation for the main living room light is to turn off the light, with the operation control parameters being immediate execution, execution priority 1, and device execution time limit of current time + 300 milliseconds. The device operation for the ambient light is to turn on warm light, with the operation control parameters being color temperature 2700K and brightness 30%, execution priority 2, and device execution time limit of current time + 350 milliseconds; the device operation for the curtains is to close to 0%, with the operation control parameters being uniform speed operation, execution priority 1, and device execution time limit of current time + 300 milliseconds; the device operation for the projector is to turn on and switch the signal source, with the operation control parameters being HDMI1 input, execution priority 3, and device execution time limit of current time + 500 milliseconds. The smart speaker sends the above instructions to the corresponding sub-intelligent agents. Each sub-intelligent agent autonomously sorts the execution according to priority. High-priority devices (main light, curtains) respond synchronously within 300 milliseconds, ambient lights complete the light environment transition in 350 milliseconds, and the projector starts last to avoid light source interference.

[0047] By sending the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each sub-agent, the corresponding sub-agent can control the corresponding registered device to perform the device execution operation based on the operation execution parameters according to the execution priority when it detects that the device execution time limit has been reached, which facilitates the realization of multi-device collaborative control.

[0048] S150. If, according to the device status sharing mechanism, it is determined that there are abnormal devices among all registered devices whose device status is offline, then, based on the collaborative device code in the multi-device collaborative control instruction sequence, generate the device execution operation, operation control parameters, execution priority, and device execution time limit for the corresponding sub-agent of each online registered device; and send the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to the corresponding sub-agent of each online registered device; and generate an execution exception prompt for the abnormal device.

[0049] Specifically, by sending the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to the corresponding sub-agent of each online registered device, the corresponding sub-agent can control the corresponding registered device to perform the device execution operation according to the operation execution parameters based on the execution priority when it detects that the device execution time limit has been reached.

[0050] In some embodiments, after generating an execution exception message for the abnormal device, the process further includes: sending an execution interruption instruction to the corresponding sub-agent of each online registered device; assessing the execution capability of the abnormal device; if it is determined that the abnormal device has lost its execution capability, then regenerating the device execution operation, operation control parameters, execution priority, and device execution time limit for each online registered device's corresponding sub-agent according to the collaborative device code in the multi-device collaborative control instruction sequence; and sending the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each online registered device's corresponding sub-agent.

[0051] For example, if the curtain agent gets stuck while performing the "close" operation, it reports an "execution anomaly" to the main agent. The main agent immediately triggers a renegotiation process: it issues an "execution pause" command to all sub-agents; it reassesses the curtain agent's execution capability and determines it to be "temporarily unable to execute"; it negotiates a new execution plan with other sub-agents, retaining the operations of executable devices and marking the curtain agent as "abnormal and pending"; it generates a new global execution plan and distributes it to each sub-agent to continue executing other operations in the movie-watching mode. This allows for adaptive handling of single-point failures, preventing the interruption of the entire collaborative task due to an malfunction of a single device, and significantly improving the robustness and reliability of multi-device collaborative control.

[0052] In some embodiments, after generating the execution exception message for the abnormal device, the method further includes: sending the execution exception message for the abnormal device to the operation and maintenance control terminal.

[0053] Among them, after detecting an abnormal device malfunction, an alarm for the curtain device can be sent to the hotel's operations and maintenance department to remind staff to inspect and repair it. This facilitates timely detection and handling of equipment failures and reduces the impact of equipment malfunctions on the guest experience.

[0054] In some embodiments, the method further includes: if it is detected that the environmental data of the current scene in which the user is located does not match the operation control parameters, then adjusting the device execution operation and operation control parameters according to the environmental data; sending the adjusted device execution operation and operation control parameters to the sub-agent corresponding to the registered device, so that the corresponding sub-agent controls the registered device to execute the adjusted device execution operation according to the adjusted operation control parameters.

[0055] For example, environmental data can be collected in real time by using environmental sensing sensors (temperature and humidity sensors, light sensors, PM2.5 sensors, and human body sensors) in guest rooms, and environmental parameter-scene parameter mapping rules can be preset to achieve dynamic adaptive adjustment of scene parameters.

[0056] Specifically, the system includes real-time environmental data collection: environmental sensors in guest rooms collect data every 10 seconds, including indoor temperature, relative humidity, light intensity, PM2.5 concentration, and the presence of people indoors. This data is uploaded in real-time to the smart speaker's environmental database. Environmental condition determination: real-time environmental data is compared with preset environmental threshold ranges to determine the current environmental type (e.g., high temperature, high humidity, strong light, weak light, smog, etc.). Mapping rule matching: for different scenarios, a preset mapping rule library between environmental parameters and scenario parameters is used. The rule library contains the correspondence between "environmental conditions - parameter adjustment direction - adjustment magnitude," allowing maintenance personnel to visualize the process. Customizable interface; Dynamic parameter calculation: Based on the matched mapping rules, combined with real-time environmental data and basic scene parameters, dynamic scene parameters are calculated for the current environment. The adjustment range is positively correlated with the degree to which the environmental data deviates from the threshold; Parameter delivery and execution: During user-triggered / continuous scene operation, the smart speaker uses dynamic scene parameters as control commands to deliver them to the corresponding devices, enabling real-time parameter adjustment; Rule self-iteration: User feedback after environmental adjustments (whether manual adjustment is needed again) is incorporated into rule optimization. If a parameter adjustment under a certain environmental condition is repeatedly approved by the user, the priority of that rule is increased; if it is repeatedly rejected, the adjustment range is automatically corrected. For example, the basic air conditioning temperature for sleep mode is 25℃, and the preset mapping rule is "Indoor real-time temperature > 28℃, air conditioning temperature decreases by 2℃; 26-28℃, decreases by 1℃; 22-24℃, increases by 1℃". If the indoor real-time temperature rises to 29℃ at night, when sleep mode is triggered, the air conditioning temperature will be dynamically adjusted to 23℃ without requiring manual adjustment by the user, further enhancing the user experience.

[0057] In some embodiments, the method further includes: predicting user-triggered scenarios within a preset future time period based on user application scenarios and user historical habits; and recommending user-triggered scenarios to users through voice prompts.

[0058] By analyzing users' historical habits and summarizing their usage patterns, the system can discover user behavior patterns and proactively recommend scenarios. For example, if it's discovered that after a user triggers "shower mode," there's an 85% probability that they will trigger "sleep mode" within 5 minutes, the system will increase the recommendation probability of sleep mode to 0.9 within 5 minutes. When the user finishes showering and returns to the bedroom, the smart speaker will proactively ask, "Do you want to turn on sleep mode for you?" This proactively prepares for high-probability scenarios, reduces response delays, and effectively improves user convenience.

[0059] The recommendation probability of a scenario can be calculated using the following formula (3).

[0060] (3) In formula (3), Indicates time t ,Week d ,history h Recommended scenarios under certain conditions j The probability of; Indicates the total number of scenes; , indicating a scene j , characteristic function freq j ( t ) for scene j In time t Historical usage frequency habit j ( d ) for scene j On week d usage habits, recent j (h) represents the scene. j Recent usage information.

[0061] In addition, this embodiment can also identify and resolve conflict types during device collaborative control. Conflict types include: timing conflicts, logical conflicts, and priority conflicts. Conflict resolution adopts a multi-level conflict resolution mechanism: priority rules: user manual commands > user voice commands > scene automation > scheduled tasks; time window merging: if (command interval < 2 seconds && target device is the same): retain the last command and cancel the preceding commands; intelligent arbitration: if (conflict cannot be automatically resolved): ask the user: "A light control conflict has been detected, should it remain on?", wait for user confirmation, and execute the user's selection.

[0062] In this embodiment, a device discovery broadcast packet is sent to the local area network within the target area. This packet is used to discover and request networked devices within the target area to engage in communication. In response to a request-response packet sent by a networked device, the device information of the networked device is entered into the device registry, and a unique device code is assigned to each registered device to establish a communication connection. The smart speaker is abstracted as the main agent, and the registered devices are abstracted as sub-agents. A device state sharing mechanism is established between the sub-agents and the main agent. If the received user control command is a multi-device control command, it is defined as a multi-device collaborative control command sequence based on the scenario information. This sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit. If the device state sharing mechanism determines that all registered devices are online, the corresponding sub-agent's device execution operation is generated based on the collaborative device code in the multi-device collaborative control command sequence. The system generates and sends the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each sub-agent. This ensures that when the execution time limit is reached, the corresponding sub-agent controls the registered device to perform the operation based on the operation execution parameters according to the execution priority. If, based on the device state sharing mechanism, there are abnormal devices among all registered devices that are offline, the system generates the device execution operation, operation control parameters, execution priority, and device execution time limit for each online registered device's corresponding sub-agent according to the collaborative device code in the multi-device collaborative control instruction sequence. This information is then sent to the corresponding sub-agent of each online registered device, ensuring that when the execution time limit is reached, the corresponding sub-agent controls the registered device to perform the operation according to the operation execution parameters according to the execution priority. An execution exception message for the abnormal device is also generated. In this way, complex scenario settings can be quickly completed through multi-device collaborative control, reducing user operation steps and effectively improving user satisfaction.

[0063] This embodiment takes the triggering of a hotel room's "movie viewing mode" as an example. When the scene command is issued, each intelligent agent collaboratively decides the execution order and parameters. Specifically, receiving the scene command: The user sends a voice command to the smart speaker, "Turn on movie viewing mode." The speaker's main agent receives the scene command and parses out all the sub-agents that need to be controlled for movie viewing mode and the basic operation requirements. Each intelligent agent assesses its own execution capabilities and constraints: The main agent issues execution capability query commands to the main light, ambient light, curtain, TV, and speaker agents. Each sub-agent assesses its own status and provides feedback: Main light agent: Online, can execute the "off" operation, no constraints; Ambient light agent: Online, can execute the "on + brightness 30% + color temperature 3000K" operation, no constraints; Curtain agent: Online, can execute the "off" operation, no constraints; TV agent: Online, can execute the "on + volume 15" operation, no constraints; Speaker agent: Online, can execute the "on + volume 20 + cinema mode" operation, with the constraint "must be executed after the TV is turned on." Negotiating Execution Order (Considering Dependencies): After collecting feedback from all sub-agents, the main agent organizes them to negotiate the execution order. Based on the device collaboration priority formula, the execution priority of each agent is calculated, and the final execution order is determined by negotiating dependencies: Phase 1: Main Light Agent (Off), Curtain Agent (Off) (Parallel, no dependency, high priority); Phase 2: TV Agent (On + Volume 15) (Depends on Phase 1 completion, medium priority); Phase 3: Ambient Light Agent (On + Parameter Configuration) (Parallel with Phase 2, no dependency); Phase 4: Speaker Agent (On + Parameter Configuration) (Depends on TV Agent being on, lowest priority). Generating a Global Execution Plan: Based on the negotiated execution order, the main agent generates a global execution plan for the movie-watching mode. The plan includes the execution operations, execution time windows, preconditions, execution priorities, and exception handling schemes for each agent, and is distributed to all sub-agents and synchronized to the cloud. Parallel / Serial Execution as Planned: Each sub-Agent executes its operations according to the global execution plan: Phase 1: The main light agent turns off the main light, and the curtain agent closes the curtains; both execute in parallel, taking 2 seconds. Phase 2: After receiving the completion status message from Phase 1, the TV agent turns on the TV and adjusts the volume to 15, taking 3 seconds. Phase 3: The ambient light agent and the TV agent execute in parallel, turning on the ambient light and configuring the brightness to 30% and the color temperature to 3000K, taking 1 second. Phase 4: After receiving the TV agent's turn-on status message, the speaker agent turns on the speakers, adjusts the volume to 20, and switches to cinema mode, taking 2 seconds. Real-time Monitoring of Execution Status: The main agent receives real-time execution status reports from each sub-Agent, monitoring that all agents complete their operations as planned and are in normal condition with no abnormal triggers.In case of an anomaly, a renegotiation is triggered: If the curtain agent gets stuck while performing the "close" operation in this case, it reports an "execution anomaly" to the main agent. The main agent immediately triggers the renegotiation process: it issues an "execution pause" command to all sub-agents; it reassesses the curtain agent's execution capability and determines it to be "temporarily unable to execute"; it negotiates a new execution plan with other sub-agents, retains the operations of executable devices, and marks the curtain agent as "anomaly pending"; it generates a new global execution plan, distributes it to each sub-agent, and continues to execute other operations in the movie-watching mode; at the same time, it sends an alarm for the curtain device anomaly to the hotel's operations and maintenance department, reminding staff to inspect it.

[0064] In summary, this embodiment effectively achieves multi-device collaborative control, enabling complex scene settings to be completed with a single sentence, improving operational efficiency, optimizing scene parameters through self-learning, adapting to user habits within 7 days, increasing user satisfaction, achieving a conflict detection accuracy rate of >95%, an intelligent resolution success rate of >90%, and a scene response time of <1 second, 60% faster than traditional solutions. It reduces operational steps, improves scene matching, increases user satisfaction, and lowers complaint rates. Self-learning capability: No manual configuration required, automatically adapting to user habits; proactive service: Scene recommendation accuracy >80%; predictive preparation: Response time reduced by 75%; continuous optimization: Becomes smarter with prolonged use. Automatic conflict resolution: Avoids device malfunctions; anomaly recovery mechanism: Automatic degradation in case of device failure; state consistency guarantee: Device status synchronized in real time; strong fault tolerance: Single device failure does not affect the overall system.

[0065] Figure 2 This is a schematic diagram of a cross-device collaborative control device for a smart speaker provided in this embodiment. Applied to a smart speaker, the cross-device collaborative control device for a smart speaker may include: The registration module 210 is used to send device discovery broadcast packets to the local area network in the target area. The device discovery broadcast packets are used to discover and request networked devices in the target area to conduct communication interactions. In response to the request response packets sent by the networked devices, the device information of the networked devices is entered into the device registry, and a unique device code is assigned to each registered device to establish a communication connection with each registered device.

[0066] Module 220 is established to abstract the smart speaker as the main intelligent agent and the registered device as a sub-intelligent agent; and to establish a device state sharing mechanism between the sub-intelligent agent and the main intelligent agent.

[0067] The definition module 230 is used to define the received user control instruction as a multi-device collaborative control instruction sequence according to the scenario information if the received user control instruction is a multi-device control instruction. The multi-device collaborative control instruction sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit.

[0068] a first generation module 240, configured to: if it is determined according to a device state sharing mechanism that the device states of all registered devices are online, generate a device execution operation, an operation control parameter, an execution priority and a device execution time limit of a corresponding sub-agent according to a collaborative device code in the multi-device collaborative control instruction sequence; and send the corresponding device execution operation, operation control parameter, execution priority and device execution time limit to each sub-agent, so that the corresponding sub-agent controls, when detecting that the device execution time limit expires, the corresponding registered device to perform the device execution operation based on the operation execution parameter according to the execution priority.

[0069] a second generation module 250, configured to: if it is determined according to the device state sharing mechanism that there is an abnormal device with an offline device state among all the registered devices, generate a device execution operation, an operation control parameter, an execution priority and a device execution time limit of a sub-agent corresponding to each online registered device according to the collaborative device code in the multi-device collaborative control instruction sequence; and send the corresponding device execution operation, operation control parameter, execution priority and device execution time limit to the sub-agent corresponding to each online registered device, so that the corresponding sub-agent controls, when detecting that the device execution time limit expires, the corresponding registered device to perform the device execution operation according to the operation execution parameter based on the execution priority; and generate an execution abnormality prompt for the abnormal device.

[0070] In some embodiments, the defining module 230 is specifically configured to: perform semantic parsing on a user control instruction, and extract a target object, an expected state and a time constraint in the user control instruction; match scene information with a preset scene template library, and determine a set of registered devices that need to be linked in the scene where the user is located and a collaboration relationship thereof; generate, for each registered device in the set of registered devices, a corresponding device execution operation and operation control parameter based on the expected state and the time constraint, and determine the execution priority of each registered device according to the dependency relationship and execution sequence between the registered devices; and allocate a corresponding device execution time limit to each registered device according to the time constraint and system load information, to obtain the multi-device collaborative control instruction sequence including the collaborative device code, the device execution operation, the operation control parameter, the execution priority and the device execution time limit.

[0071] In some embodiments, the system further comprises: a first processing module.

[0072] The first processing module is used to send execution interruption instructions to the corresponding sub-agents of each online registered device; and to evaluate the execution capability of the abnormal device; if it is determined that the abnormal device has lost its execution capability, then according to the cooperative device code in the multi-device cooperative control instruction sequence, it regenerates the device execution operation, operation control parameters, execution priority, and device execution time limit of the corresponding sub-agents of each online registered device; and sends the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to the corresponding sub-agents of each online registered device.

[0073] In some embodiments, a second processing module is also included.

[0074] The second processing module is used to send execution error prompts for abnormal devices to the operation and maintenance control terminal.

[0075] In some embodiments, a third processing module is also included.

[0076] The third processing module is used to adjust the device execution operation and operation control parameters according to the environmental data if it is detected that the environmental data of the current scene where the user is located does not match the operation control parameters; and to send the adjusted device execution operation and operation control parameters to the sub-agent corresponding to the registered device so that the corresponding sub-agent controls the registered device to execute the adjusted device execution operation according to the adjusted operation control parameters.

[0077] In some embodiments, a fourth processing module is also included.

[0078] The fourth processing module is used to predict user-triggered scenarios within a preset future time period based on user application scenarios and user historical habits; and recommend user-triggered scenarios to users through voice prompts.

[0079] In some embodiments, an update module is also included.

[0080] The update module is used to generate a sequence of independent control instructions for the corresponding registered device if the received user control instruction is a single device control instruction. The sequence of independent control instructions includes: independent device code, device execution operation, operation control parameters, and device execution time limit. The module sends the device execution operation, operation control parameters, and device execution time limit to the corresponding sub-agent of the independent device code, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation based on the operation execution parameters.

[0081] The smart speaker cross-device collaborative control device provided in this disclosure can execute the above-described method embodiments. Its specific implementation principle and technical effects can be found in the above-described method embodiments, and will not be repeated here.

[0082] This application also provides a computer device. Please refer to the following for details. Figure 3 , Figure 3 This is a basic structural block diagram of the computer device in this embodiment.

[0083] The computer device includes a memory 310 and a processor 320 that are interconnected via a system bus. It should be noted that only a computer device with memory 310 and processor 320 is shown in the figure; however, it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented alternatively. Those skilled in the art will understand that the computer device described herein is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0084] Computer devices can include desktop computers, laptops, handheld computers, and cloud servers. These devices allow for human-computer interaction with users through keyboards, mice, remote controls, touchpads, or voice-activated devices.

[0085] The memory 310 includes at least one type of readable storage medium, including non-volatile memory or volatile memory, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. RAM may include static RAM or dynamic RAM. In some embodiments, the memory 310 may be an internal storage unit of a computer device, such as the hard disk or memory of the computer device. In other embodiments, the memory 310 may also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, or flash card equipped on the computer device. Of course, the memory 310 may include both internal storage units and external storage devices of the computer device. In this embodiment, the memory 310 is typically used to store the operating system and various application software installed on the computer device, such as the program code of the method described above. In addition, the memory 310 can also be used to temporarily store various types of data that have been output or will be output.

[0086] Processor 320 is typically used to perform overall operations of a computer device. In this embodiment, memory 310 is used to store program code or instructions, including computer operation instructions, and processor 320 is used to execute the program code or instructions stored in memory 310 or process data, such as program code that runs the methods described above.

[0087] In this article, 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. This bus system can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0088] Another embodiment of this application also provides a computer-readable medium, which may be a computer-readable signal medium or a computer-readable medium. A processor in a computer reads computer-readable program code stored in the computer-readable medium, enabling the processor to execute the functional actions specified in each step or combination of steps in the above method; and to generate means for implementing the functional actions specified in each block or combination of blocks in the block diagram.

[0089] Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared memory or semiconductor systems, devices or apparatuses, or any suitable combination thereof, wherein the memory is used to store program code or instructions, the program code including computer operation instructions, and the processor is used to execute the program code or instructions of the above-described methods stored in the memory.

[0090] The definitions of memory and processor can be found in the description of the foregoing computer device embodiments, and will not be repeated here.

[0091] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0092] In the various embodiments of this application, the functional units or modules can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0093] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part 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.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. 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.

[0094] In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" as described in this application does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims listing several means, several units of these means may be embodied by the same item of hardware. The use of "first," "second," and "third," etc., does not indicate any order and these words should be interpreted as names. Unless otherwise specified, the steps in the above embodiments should not be construed as limiting the order of execution.

[0095] 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 of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for cross-device collaborative control of a smart speaker, characterized in that, Applications in smart speakers include: A device discovery broadcast packet is sent to the local area network within the target area. The device discovery broadcast packet is used to discover and request networked devices within the target area to conduct communication interaction. In response to the request response packet sent by the networked device, the device information of the networked device is entered into the device registry, and a unique device code is assigned to each registered device to establish a communication connection with each registered device. The smart speaker is abstracted as the main intelligent agent, and the registered device is abstracted as a sub-intelligent agent; and a device state sharing mechanism is established between the sub-intelligent agent and the main intelligent agent. If the received user control instruction is a multi-device control instruction, then the user control instruction is defined as a multi-device collaborative control instruction sequence according to the scenario information. The multi-device collaborative control instruction sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit. If it is determined that all registered devices are online according to the device status sharing mechanism, then according to the collaborative device code in the multi-device collaborative control instruction sequence, the device execution operation, operation control parameters, execution priority, and device execution time limit of the corresponding sub-agent are generated; and the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit are sent to each sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation based on the operation execution parameters according to the execution priority; If, according to the device state sharing mechanism, it is determined that there are abnormal devices among all the registered devices whose device state is offline, then, based on the collaborative device code in the multi-device collaborative control instruction sequence, the device execution operation, operation control parameters, execution priority, and device execution time limit corresponding to each online registered device are generated; and the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit are sent to each online registered device's corresponding sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation according to the operation execution parameters based on the execution priority; and, an execution abnormality prompt for the abnormal device is generated.

2. The method according to claim 1, characterized in that, Based on the scenario information, the user control commands are defined as a multi-device collaborative control command sequence, including: Semantic parsing is performed on the user control instructions to extract the target object, desired state, and time constraints from the user control instructions; Match scene information with a preset scene template library to determine the set of registered devices that need to be linked in the user's scene and their collaborative relationships; based on the expected state and the time constraint, generate corresponding device execution operations and operation control parameters for each registered device in the set of registered devices, and determine the execution priority of each registered device according to the dependency relationship and execution sequence between each registered device; Based on the time constraints and system load information, a corresponding device execution time limit is assigned to each registered device, resulting in a multi-device collaborative control instruction sequence that includes collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit.

3. The method according to claim 1, characterized in that, After generating the execution exception message for the abnormal device, the process also includes: Send an execution interruption command to the sub-agent corresponding to each of the registered online devices; and assess the execution capability of the abnormal device; If it is determined that the abnormal device has lost its ability to execute, then according to the collaborative device code in the multi-device collaborative control instruction sequence, the device execution operation, operation control parameters, execution priority and device execution time limit of the sub-agent corresponding to each online registered device are regenerated. Send the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to the corresponding sub-agent of each online registered device.

4. The method according to claim 1, characterized in that, After generating the execution exception message for the abnormal device, the process also includes: Send an execution error message for the abnormal device to the operation and maintenance control terminal.

5. The method according to claim 1, characterized in that, Also includes: If the environmental data of the user's current scene is detected to be mismatched with the operation control parameters, the device's operation execution and operation control parameters are adjusted according to the environmental data. The adjusted device execution operation and the operation control parameters are sent to the sub-agent corresponding to the registered device, so that the corresponding sub-agent controls the registered device to execute the adjusted device execution operation according to the adjusted operation control parameters.

6. The method according to claim 1, characterized in that, Also includes: Based on user application scenarios and user historical habits, predict user-triggered scenarios within a preset future time period; The user-triggered scenarios are recommended to the user through voice prompts.

7. The method according to claim 1, characterized in that, Also includes: If the received user control instruction is a single device control instruction, then a single device independent control instruction sequence for the corresponding registered device is generated based on the user control instruction. The single device independent control instruction sequence includes: independent device code, device operation, operation control parameters, and device execution time limit. The corresponding sub-agent of the independent device code sends the device execution operation, operation control parameters, and device execution time limit, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation based on the operation execution parameters.

8. A smart speaker cross-device collaborative control device, characterized in that, Applications in smart speakers include: The registration module is used to send device discovery broadcast packets to the local area network within the target area. The device discovery broadcast packets are used to discover and request networked devices within the target area to conduct communication interactions. In response to the request response packets sent by the networked devices, the module records the device information of the networked devices into the device registry and assigns a unique device code to each registered device to establish a communication connection with each registered device. A module is established to abstract the smart speaker as a main intelligent agent and the registered device as a sub-intelligent agent; and to establish a device state sharing mechanism between the sub-intelligent agent and the main intelligent agent. The definition module is used to define the received user control instruction as a multi-device collaborative control instruction sequence according to the scenario information if the received user control instruction is a multi-device control instruction. The multi-device collaborative control instruction sequence includes: collaborative device code, device execution operation, operation control parameters, execution priority, and device execution time limit. The first generation module is configured to, if it is determined according to the device status sharing mechanism that all the registered devices are online, generate the device execution operation, operation control parameters, execution priority, and device execution time limit for the corresponding sub-agent based on the collaborative device code in the multi-device collaborative control instruction sequence; and send the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation based on the operation execution parameters according to the execution priority; The second generation module is configured to, if it is determined according to the device state sharing mechanism that there are abnormal devices among all the registered devices whose device state is offline, generate, according to the collaborative device code in the multi-device collaborative control instruction sequence, the device execution operation, operation control parameters, execution priority, and device execution time limit for each online registered device's corresponding sub-agent; and send the corresponding device execution operation, operation control parameters, execution priority, and device execution time limit to each online registered device's corresponding sub-agent, so that when the corresponding sub-agent detects that the device execution time limit has been reached, it controls the corresponding registered device to perform the device execution operation according to the operation execution parameters based on the execution priority; and generate an execution exception prompt for the abnormal device.

9. A computer device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the smart speaker cross-device collaborative control method as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the smart speaker cross-device collaborative control method as described in any one of claims 1 to 7.