Dialogue-based device linkage method, apparatus, device, and storage medium

Abstract

The present disclosure provides a dialogue-based device linkage method, apparatus, device, and storage medium. The method comprises: monitoring a state change message sent by a triggering device in a pre-established device linkage group; upon monitoring a state change message, generating a control instruction for an execution device linked to the triggering device based on a pre-established linkage rule, and sending the control instruction to the execution device; receiving response data generated by the execution device in response to the control instruction, and based on the response data, controlling the execution device in the device linkage group to send a response message reflecting the response result of the execution device. The disclosed method can make the linkage control process between devices more intuitive and transparent.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet of Things application technology, and in particular to a dialogue-based device linkage method, apparatus, device, and storage medium. Background Art

[0002] Existing IoT device linkage is typically controlled directly through backend scripts. Users can only see the final state of the device, but are unable to perceive the linkage logic between devices. This indicates that existing device linkage methods lack intuitiveness and transparency. Therefore, improving the intuitiveness and transparency of device linkage methods is a pressing technical issue for those skilled in the art. Summary of the Invention

[0003] In view of this, the present disclosure proposes a dialogue-based device linkage method, apparatus, device, and storage medium, which can make the linkage control process between devices more intuitive and transparent.

[0004] According to a first aspect of the present disclosure, a method for device linkage based on a conversation is provided, comprising:

[0005] Monitor the status change messages sent by the triggering devices in the pre-built device linkage group;

[0006] When the state change message is monitored, based on a pre-established linkage rule, a control instruction for an execution device linked to the triggering device is generated, and the control instruction is sent to the execution device;

[0007] Response data generated by the execution device in response to the control instruction is received, and based on the response data, the execution device in the device linkage group is controlled to send a response message reflecting the response result of the execution device.

[0008] In a possible implementation, when constructing the device linkage group, the following steps are included:

[0009] Based on the trigger of building a chat group control, push a list of devices that can be controlled in conjunction with each other;

[0010] At least two devices that need to be linked and controlled are selected from the device list, and the selected devices are created into a chat group to obtain the device linkage group.

[0011] In a possible implementation, before monitoring the state change message sent by the triggering device in the pre-built device linkage group, the method further includes:

[0012] Acquire state change data sent by the triggering device;

[0013] Based on the state change data sent by the triggering device, the triggering device in the device linkage group is controlled to send the state change message.

[0014] In a possible implementation, the state change data includes at least one of: a message type, a message sending object, a message text content, and device control data;

[0015] The message type is used to represent the type of the message sending object, and the type of the message sending object includes at least one of a device, a person, and a designated member in the device linkage group.

[0016] In a possible implementation, controlling the triggering device in the device linkage group to send the state change message based on the state change data sent by the triggering device includes:

[0017] Parsing the state change data to obtain the message type, message sending object, and message text content;

[0018] When the message type indicates that the message sending object is a designated member in the device linkage group, the message sending object and the message text content are combined into the state change message, and the triggering device in the device linkage group is controlled to send the state change message.

[0019] In a possible implementation, the linkage rule is implemented based on a pre-built bubbling script, wherein the bubbling script refers to a linkage control program implemented based on a pre-defined code structure and API interface in a bubbling library.

[0020] In a possible implementation, the predefined API interface includes a first API interface for sending data and a second API interface for subscribing to data.

[0021] According to a second aspect of the present disclosure, there is provided an apparatus for dialogue-based device linkage, comprising:

[0022] A message monitoring module is used to monitor the status change messages sent by the triggering devices in the pre-built device linkage group;

[0023] a control instruction generating module for generating, upon monitoring the state change message, a control instruction for an execution device linked to the triggering device based on a pre-established linkage rule, and sending the control instruction to the execution device;

[0024] The execution result feedback module is used to receive the response data generated by the execution device in response to the control instruction, and based on the response data, control the execution device in the device linkage group to send a response message reflecting the response result of the execution device.

[0025] According to a third aspect of the present disclosure, a conversation-based device linkage device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the method described in the first aspect of the present disclosure.

[0026] According to a fourth aspect of the present disclosure, a non-volatile computer-readable storage medium is provided, on which computer program instructions are stored, wherein the computer program instructions, when executed by a processor, implement the method described in the first aspect of the present disclosure.

[0027] The present disclosure provides a device linkage method, apparatus, device and storage medium based on dialogue, the method comprising: monitoring a status change message sent by a trigger device in a pre-built device linkage group; in the case of monitoring a status change message, generating a control instruction for an execution device linked to the trigger device based on a pre-built linkage rule, and sending the control instruction to the execution device; receiving response data generated by the execution device in response to the control instruction, and based on the response data, controlling the execution device in the device linkage group to send a response message reflecting the response result of the execution device. In the present disclosure, a device linkage group is created in advance for devices that need to be linked and controlled, and linkage control between devices is achieved through message dialogues between the devices in the device linkage group, so that the linkage control between devices can be displayed in the form of dialogue, making the linkage control process between devices more intuitive and transparent.

[0028] Further features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0030] Figure 1 A flowchart showing a device linkage method based on a dialogue according to an embodiment of the present disclosure is shown;

[0031] Figure 2 A diagram showing a linkage control dialogue according to an embodiment of the present disclosure is shown;

[0032] Figure 3 A schematic block diagram illustrating a device linkage apparatus based on a dialogue according to an embodiment of the present disclosure is shown;

[0033] Figure 4 A schematic block diagram of a device linkage device based on dialogue according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0034] Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

[0035] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0036] In addition, numerous specific details are provided in the following detailed description to better illustrate the present disclosure. Those skilled in the art will appreciate that the present disclosure can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the main points of the present disclosure.

[0037] <Method Example>

[0038] Figure 1 FIG. 1 is a flow chart showing a device linkage method based on a dialogue according to an embodiment of the present disclosure. Figure 1 As shown, the method includes steps S1100-S1300.

[0039] S1100, monitor the status change message sent by the trigger device in the pre-built device linkage group; S1200, when the status change message is monitored, generate the control instruction of the execution device linked with the trigger device based on the pre-built linkage rule, and send the control instruction to the execution device; S1300, receive the response data generated by the execution device in response to the control instruction, and based on the response data, control the execution device in the device linkage group to send a response message reflecting the response result of the execution device.

[0040] In the present disclosure, a device linkage group is created in advance for devices that need to be linked controlled, and the linkage control between devices is realized through message dialogues between the devices in the device linkage group, so that the linkage control between devices can be displayed in the form of dialogues, making the linkage control process between devices more intuitive and transparent.

[0041] It should be noted here that the device linkage method disclosed in the present invention is implemented based on the device linkage control APP. Before executing the method disclosed in the present invention, it is necessary to first associate the user's Internet of Things device (hereinafter referred to as the device) that is compatible with the device linkage control APP to the device linkage control APP. In this way, the associated devices can be subsequently linked and controlled based on the device linkage control APP.

[0042] After associating the device with the device linkage control APP, you can build a device linkage group based on the user's device linkage control needs. When building a device linkage group, you can include the following steps:

[0043] First, based on the trigger of building a chat group control, a list of devices that can be controlled in conjunction with each other is pushed.

[0044] Specifically, a chat group building control is provided on the interface of the device linkage control APP. When the chat group building control is triggered, the device identification of each device associated with the device linkage control APP will be obtained, and the obtained device identifications will be pushed and displayed in the form of a device list for the user to select the device that needs linkage control.

[0045] In one possible implementation, the device list pushed and displayed does not include the device that the user needs to use. At this time, you can search for nearby devices, and select the required device from the searched devices and associate it with the device linkage control APP, and update its device identification to the device list, and then create a device linkage group based on the updated device list.

[0046] Second, select at least two devices from the device list that require coordinated control and create a chat group for each of them. This creates a device linkage group. The created device linkage group includes at least two devices that require coordinated control, a user, and a robot for group message monitoring. The devices, users, and robots in the device linkage group can achieve coordinated control with each other through natural language conversation.

[0047] After building a device linkage group, you can then perform linkage control on each device within the group. For clarity, the device used to trigger linkage control in the group is referred to as the triggering device, and the device that performs linkage operations with the triggering device is referred to as the executing device.

[0048] During the device linkage control process, when a triggering device in the device linkage group changes state, it will send state change data reflecting its state change to the device linkage control app. Specifically, when a state change occurs, the triggering device will generate corresponding state change data, and then send this state change data to the robots in the device linkage group by calling a first API interface predefined in the bubble library for data transmission. When called, the first API interface organizes the triggering device's state change data into a specified data structure and sends it to the device linkage control app.

[0049] In one possible implementation, the state change data may include at least one of the following: message type, message object toObj, message text content, and device control data command. The message type type indicates the type of the message object, which can include at least one of a device in a device linkage group, a robot, and a designated person. When the message object is a device in a device linkage group, the message type is 0; when the message object is a designated person in a device linkage group, the message type is 1; and when the message object is a robot in a device linkage group, the message type is 2. The message object toObj records the specific identifier of the message object. For example, if the message object is a light in a device linkage group and the light identifier is ledLight, the message object toObj is ledLight. The message text content is the natural language text corresponding to the device status. It should be noted that the device status is typically represented by pre-defined fields and values ​​in the firmware. To clearly understand the current status of the device, the device status is converted into corresponding natural language text, allowing the user to intuitively understand the device status. For example, if a light is on, the message text corresponding to its status is set to "On." When the message is sent to robots or designated personnel in a device linkage group, the "Device Control Data Command" field is omitted. When the message is sent to a device in the device linkage group, the state change data includes the "Device Control Data Command," which contains the device control method and the corresponding attribute values. Once the device control method and the corresponding attribute values ​​are known, the device can be controlled based on the "Device Control Data Command."

[0050] When sending a message to a designated person or robot in a device linkage group, the state change data will include: message type type, message sending object toObj, and message text content content. At this time, the calling function of the first API interface can be as follows: sendMessage(type, toObj, content).

[0051] For example, when the human body sensor, a trigger device, senses that someone is coming, the message type type in the generated state change data is 2, the message sending object toObj is bot, and the message text content is someone is coming. At this time, the first API interface will call the function sendMessage(2,bot,'someone is coming') to send its state change data to the device linkage control APP, so that the device linkage control APP controls the human body sensor in the device linkage group to send the message content of someone is coming to the robots in the group.

[0052] When sending a message to a device in a device linkage group, the state change data will include: message type type, message sending object toObj, message text content content and device control data command. At this time, the calling function of the first API interface can be as follows: sendMessage(type, toObj, content, command).

[0053] Continuing with the above embodiment, after monitoring the message sent by the human body sensor to the robot in the device linkage group, it will be determined based on the pre-set linkage rules that the robot in the device linkage control group needs to send a state change message to the light in the device linkage group to control the light to turn on. At this time, the state change data corresponding to the robot will be generated based on the linkage rules, wherein the message type type in the state change data corresponding to the robot is 0, the message sending object toObj is light, the message text content conten is light turn on, the device control method in the device control data command is setSwith, and the corresponding attribute value is true. Then, the state change data corresponding to the robot is updated to the device linkage APP through the calling function of the following first API interface.

[0054] sendMessage(0,light,'Light on',{

[0055] method:'setSwitch',

[0056] params:true

[0057] })

[0058] After the device linkage control APP obtains the status change data of the triggering device, it will simultaneously control the triggering device in the device linkage group to send a status change message based on the status change data of the triggering device. Specifically, after receiving the status change data sent by the triggering device, the message type, message recipient, and message text content are first parsed from the status change data. Then, when the message type indicates that the message recipient is a specified member in the device linkage group, the message recipient and the message text content are combined into a status change message, and the triggering device in the device linkage group is controlled to send a status change message.

[0059] For example, when the triggering device is a human body sensor and the human body sensor senses that someone has come, it will generate corresponding status change data and send it to the device linkage control APP. Among them, the message type type in the status change data is 2, the message recipient toObj is the robot groupChat in the device linkage group (i.e., Figure 2 the Xudong Assistant bot in ), and the message text content content is someone has come. After the device linkage APP receives the status change data sent by the human body sensor, it will parse from the status change data that the message type is 2, the message recipient is groupChat, and the message text content is someone has come. At this time, @Xudong Assistant bot and someone has come are combined into the status change message of the human body sensor, and the human body sensor in the device linkage group is controlled to send the status change message of @Xudong Assistant someone has come, as specifically shown in Figure 2 As shown. In this way, the user can know that the human body sensor senses that someone has come at this time.

[0060] Similarly, after the device linkage control APP obtains the status change data corresponding to the robot, it will simultaneously control the robot in the device linkage group to send a status change message based on the status change data of the robot. Specifically, after receiving the status change data corresponding to the robot, the message type, message recipient, and message text content are first parsed from the status change data. Then, when the message type indicates that the message recipient is a specified member in the device linkage group, the message recipient and the message text content are combined into a status change message, and the triggering device in the device linkage group is controlled to send a status change message.

[0061] For example, in the state change data corresponding to the robot, the message type type is 0, the message sending object toObj is light, the message text content conten is light on, and the device control method in the device control data command is setSwith. When the corresponding attribute value is true, the message type will be parsed from the state change data as 0, the message sending object is light, and the message text content is light on. At this time, @light and light on are combined to form the state change message corresponding to the robot, and the robots in the device linkage group are controlled to send the state change message @light light on.

[0062] Furthermore, during the process of device linkage control, the device linkage control APP will monitor the messages in the device linkage group in real time. After monitoring the status change message issued by the trigger device in the device linkage group, it will simultaneously generate control instructions for the execution device linked to the trigger device based on the pre-built linkage rules, and send the control instructions to the execution device.

[0063] In one possible implementation, the linkage rules are implemented based on a pre-built bubble script, wherein the bubble script refers to a linkage control program implemented based on the pre-defined code structure and API interface in the bubble library. By running the linkage control program, control instructions for the execution device linked to the trigger device can be generated, and the control instructions can be sent to the execution device.

[0064] It should be noted that to reduce the difficulty of developing device linkage programs, a pre-built bubble library has been built. This bubble library pre-defines the code structure and API interface for device linkage development. The pre-defined code structure includes the device declaration code structure and the initialization code structure. The API interface includes a first API interface for data transmission and a second API interface for data subscription.

[0065] The code structure of the device declaration is used to define the device used by the bubble script and associate the bubble script with the device associated with the device linkage control app. The code structure of the device declaration can be as follows:

[0066] const create=async()=>{

[0067] global.rotaryEncoder = createJeejioXieDevice("rotary encoder");

[0068] };

[0069] The initialization code structure is used to save the context data (data storage center) that you want to record during the program running process. The initialization code structure can be as follows: const init = async () = > {

[0070] const state = {};

[0071] saveState(state);

[0072] };

[0073] The first API interface is used for sending data, that is, for sending messages to devices, people or robots in the device linkage group. The calling function of the first API interface is described above and will not be repeated here.

[0074] The second API interface is used for data subscription, that is, for receiving messages sent by devices, people or robots in the device linkage group. The calling function of the second API interface is as follows: subscribe(maopaoMsg);

[0075] Among them, maopaoMsg is the message content structure, which includes the message source type, specific message content, message source ID and message data content, etc.

[0076] The message content structure of maopaoMsg is as follows:

[0077] {

[0078] type:0, / / Message source type: 0 indicates that the message comes from a device in the device linkage group, 1 indicates that the message comes from a person in the device linkage group, and 2 indicates that the message comes from a robot in the device linkage group;

[0079] content: 'xxx', / / Specific message content, which can be a device notification message from the device linkage group, a message sent by a person in the device linkage group, or a robot message from the device linkage group;

[0080] from:”, / / Device id from, human, robot;

[0081] contentType:0, / / Reserved field, can identify different transmission data content, support more complex scenarios, IM reserved message types, text, voice, image, video reserved data:{

[0082] buttonStatus:'CLICK', / / Take device properties as an example

[0083] }

[0084] }

[0085] Case 1: Real-time subscription of device messages in the device linkage group: message of rotary encoder pressing, subscription

[0086] subscribe(maopaoMsg)

[0087] async subscribe=async(maopaoMsg)=>{

[0088] if(maopaoMsg.type===0){

[0089] if(maopaoMsg.data.buttonStatus=='CLICK'){

[0090] }

[0091] }

[0092] }

[0093] Case 2: Real-time subscription to messages from people in the device linkage group. The messages from subscribers are all text messages with the data field.

[0094] async subscribe=async(maopaoMsg)=>{

[0095] if(maopaoMsg.type===1){

[0096] if(maopaoMsg.content==='Like'){

[0097] }

[0098] }

[0099] }

[0100] After building the Bubble Library, you can develop a device linkage program based on the code structure and API interfaces defined in the Bubble Library. The following example illustrates the device linkage program using a specific scenario.

[0101] The device linkage program is applicable to the scenario where pressing a button turns the light on, and pressing the button again turns the light off. The device linkage code built based on the code structure and API interface defined in the bubble library can be as follows:

[0102]

[0103]

[0104] After monitoring the state change message sent by the trigger device in the device linkage group, the linkage rule is run to obtain the state change data corresponding to the state change message sent by the trigger device, and then based on the acquired state change data of the trigger device, the execution device linked to the trigger device is determined, and the control instruction of the execution device is generated. Among them, the control instruction also includes at least one of the message type type, the message sending object toObj, the message text content content and the device control data command. After the control instruction of the execution device is generated, the control instruction is sent to the corresponding execution device by calling the first API interface. When the first API interface is called, it will organize the control instruction into a specified data structure and send it to the corresponding execution device.

[0105] When the execution device receives the control instruction, it will parse the device control data command from the control instruction, and based on the parsed device control data command, it will call the corresponding third API interface in the bubble library to implement the control operation of the execution device through the third API interface. It should be noted here that in addition to the above code structure and API interface pre-set in the bubble library, the corresponding third API interface is also abstracted for the various functions of various IoT devices on the market. In this way, after parsing the device control data command, the corresponding third API interface can be called based on the parsed command to implement the control operation of the execution device through the corresponding third API interface.

[0106] After the execution device operation is completed, the execution device's status is monitored. If the execution device's status changes, state change data for the execution device is generated in the same manner as the triggering device. This state change data is the response data generated by the execution device in response to the control instruction. That is, the response data is identical to the state change data, and both include at least one of the message type, the message object toObj, the message text content, and the device control data command described above. After the response data is generated, it is sent to the device linkage control app, which then receives the response data generated by the execution device in response to the control instruction.

[0107] After receiving the response data generated by the execution device response control instruction, the device linkage control APP will control the execution device in the device linkage group to send a response message reflecting the response result of the execution device based on the response data. Specifically, when the device linkage control APP receives the response data, it parses the message text content from the response data, and uses the parsed message text content as the response message, and controls the execution device in the device linkage group to send the response message. In this way, the user can clearly understand the execution device and the response result of the execution device through the response message. For example, in Figure 2 In the example shown, the actuator device linked to the human presence sensor is a light. When the sensor detects a person approaching, the light turns on and sends a message to the device linkage group indicating that the light has been turned on. This allows users to clearly understand the linkage between the human presence sensor and the light.

[0108] Therefore, the method disclosed in the present invention can clearly understand the linkage operation between devices through natural language dialogue between devices in the device linkage group, which not only increases the fun of linkage control, but also makes the linkage control process intuitive and transparent.

[0109] <Device Example>

[0110] Figure 3 FIG. 1 is a schematic block diagram of a device linkage apparatus based on a dialogue according to an embodiment of the present disclosure. Figure 3 As shown, the device 100 includes:

[0111] The message monitoring module 110 is used to monitor the status change messages sent by the triggering devices in the pre-built device linkage group;

[0112] The control instruction generation module 120 is used to generate a control instruction for an execution device linked to the triggering device based on a pre-established linkage rule when a state change message is monitored, and send the control instruction to the execution device;

[0113] The execution result feedback module 130 is configured to receive response data generated by the execution device in response to the control instruction, and based on the response data, control the execution device in the device linkage group to send a response message reflecting the response result of the execution device.

[0114] <Equipment Example>

[0115] Figure 4 FIG. 1 shows a schematic block diagram of a device linkage device based on a dialogue according to an embodiment of the present disclosure. Figure 4As shown, the conversation-based device linkage device 200 includes: a processor 210 and a memory 220 for storing executable instructions of the processor 210. The processor 210 is configured to implement any of the above-mentioned conversation-based device linkage methods when executing the executable instructions.

[0116] It should be noted that there may be one or more processors 210. Furthermore, the conversation-based device linkage device 200 of the disclosed embodiment may also include an input device 230 and an output device 240. The processor 210, memory 220, input device 230, and output device 240 may be connected via a bus or other means, which are not specifically limited herein.

[0117] Memory 220, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and various modules, such as the programs or modules corresponding to the conversation-based device linkage method according to the embodiments of the present disclosure. Processor 210 executes the software programs or modules stored in memory 220 to execute various functional applications and data processing of conversation-based device linkage device 200.

[0118] The input device 230 may be used to receive input numbers or signals. The signals may be key signals related to user settings and function control of the device / terminal / server. The output device 240 may include a display device such as a display screen.

[0119] <Storage Medium Embodiment>

[0120] According to a fourth aspect of the present disclosure, a non-volatile computer-readable storage medium is further provided, on which computer program instructions are stored. When the computer program instructions are executed by the processor 210, any of the above-mentioned dialogue-based device linkage methods is implemented.

[0121] While various embodiments of the present disclosure have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or technical improvements to existing technologies, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A device linkage method based on dialogue, characterized in that: include: Listen for status change messages sent by trigger devices in a pre-built device linkage group. The device linkage group includes at least two devices that require linkage control, a user, and a robot for group message monitoring. The devices, users, and robots in the device linkage group communicate with each other through natural language. When the state change message is monitored, based on a pre-established linkage rule, a control instruction for an execution device linked to the triggering device is generated, and the control instruction is sent to the execution device; receiving response data generated by the execution device in response to the control instruction, and controlling the execution device in the device linkage group to send a response message reflecting the response result of the execution device based on the response data; Before monitoring the state change message sent by the trigger device in the pre-built device linkage group, the method further includes: obtaining the state change data sent by the trigger device, parsing the message type, message sending object and message text content from the state change data, wherein the message type is 2, indicating that the message sending object is a specified member in the device linkage group, the message sending object is a robot in the device linkage group, and the message text content is a natural language text corresponding to the state of the trigger device; combining the message sending object and the message text content to obtain the state change message of the trigger device, and controlling the trigger device in the device linkage group to send a state change message with a natural language text corresponding to the state of the trigger device to the robot; After monitoring a trigger device in a device linkage group to send a state change message containing natural language text corresponding to the state of the trigger device to the robot, state change data corresponding to the robot is generated based on the linkage rules. In the state change data corresponding to the robot, a message type of 0 indicates that the message is sent to a device in the device linkage group, the message is sent to the device identifier of the execution device linked to the trigger device, as determined based on the linkage rules, and the message text is a natural language description of the control instruction that the execution device needs to execute, as determined based on the linkage rules. After generating the robot's state change data, based on the robot's state change data, the robots in the control device linkage group send a state change message to the execution device with a natural language description of the control instructions that need to be executed by the execution device, so as to control the execution device to execute the corresponding control instructions and clearly trigger the device's control logic for the execution device.

2. The method according to claim 1, characterized in that When constructing the device linkage group, it includes: Based on the trigger of building a chat group control, push a list of devices that can be controlled in conjunction with each other; At least two devices that need to be linked and controlled are selected from the device list, and the selected devices are created into a chat group to obtain the device linkage group.

3. The method according to claim 1, characterized in that The linkage rules are implemented based on a pre-built bubbling script, wherein the bubbling script refers to a linkage control program implemented based on a pre-defined code structure and API interface in a bubbling library.

4. The method according to claim 3, characterized in that The predefined API interface includes a first API interface for sending data and a second API interface for subscribing to data.

5. A device linkage device based on dialogue, characterized in that: include: A message monitoring module is used to monitor the status change messages sent by the triggering devices in the pre-built device linkage group; a control instruction generating module for generating, upon monitoring the state change message, a control instruction for an execution device linked to the triggering device based on a pre-established linkage rule, and sending the control instruction to the execution device; an execution result feedback module, configured to receive response data generated by the execution device in response to the control instruction, and based on the response data, control the execution device in the device linkage group to send a response message reflecting the response result of the execution device; Before monitoring the state change message sent by the trigger device in the pre-built device linkage group, the method further includes: obtaining the state change data sent by the trigger device, parsing the message type, message sending object and message text content from the state change data, wherein the message type is 2, indicating that the message sending object is a specified member in the device linkage group, the message sending object is a robot in the device linkage group, and the message text content is a natural language text corresponding to the state of the trigger device; combining the message sending object and the message text content to obtain the state change message of the trigger device, and controlling the trigger device in the device linkage group to send a state change message with a natural language text corresponding to the state of the trigger device to the robot; After monitoring a trigger device in a device linkage group to send a state change message containing natural language text corresponding to the state of the trigger device to the robot, state change data corresponding to the robot is generated based on the linkage rules. In the state change data corresponding to the robot, a message type of 0 indicates that the message is sent to a device in the device linkage group, the message is sent to the device identifier of the execution device linked to the trigger device, as determined based on the linkage rules, and the message text is a natural language description of the control instruction that the execution device needs to execute, as determined based on the linkage rules. After generating the robot's state change data, based on the robot's state change data, the robots in the control device linkage group send a state change message to the execution device with a natural language description of the control instructions that need to be executed by the execution device, so as to control the execution device to execute the corresponding control instructions and clearly trigger the device's control logic for the execution device.

6. A device linkage device based on dialogue, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to implement the method according to any one of claims 1 to 4 when executing the executable instructions.

7. A non-volatile computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images