Conversation-based equipment linkage method and device, equipment and storage medium

Abstract

The invention provides a conversation-based equipment linkage method and device, equipment and a storage medium. The method comprises the following steps: monitoring a state change message sent by triggering equipment in a pre-constructed equipment linkage group; under the condition that the state change message is monitored, based on a pre-constructed linkage rule, generating a control instruction of an execution device linked with the trigger device, and sending the control instruction to the execution device; and receiving response data generated by the execution equipment in response to the control instruction, and based on the response data, controlling the execution equipment in the equipment linkage group to send a response message reflecting a response result of the execution equipment. By means of the method, the linkage control process between the devices can be more visual 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] The linkage of existing IoT devices is usually directly controlled by running scripts in the background. Users can only see the final state of the device, but cannot perceive the linkage logic between devices. It can be seen that the device linkage method in the prior art lacks intuitiveness and transparency. Therefore, how to improve the intuitiveness and transparency of the device linkage method is a technical problem that needs to be solved urgently by 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] Listen to the status change messages sent by the trigger devices in the pre-built device linkage group;

[0006] In the case of monitoring the state change message, generating a control instruction of an execution device linked with the trigger device based on a pre-built linkage rule, and sending the control instruction to the execution device;

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

[0008] In a possible implementation, when constructing the device linkage group, it includes:

[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 trigger device in the pre-built device linkage group, the method further includes:

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

[0013] Based on the state change data sent by the trigger device, the trigger 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 object to which the message is sent, and the type of the object to which the message is sent includes at least one of a device, a person, and a designated member in the device linkage group.

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

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

[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 trigger 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 manner, the predefined API interface includes a first API interface for data transmission and a second API interface for data subscription.

[0021] According to a second aspect of the present disclosure, a device for dialogue-based device linkage is provided, 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 generation module is used to generate a control instruction for an execution device linked with the trigger device based on a pre-built linkage rule when the state change message is monitored, and send 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 dialogue-based device linkage device is provided, comprising: a processor; 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, equipment and storage medium based on dialogue, the method comprising: monitoring the state change message sent by the trigger device in the pre-built device linkage group; in the case of monitoring the state change message, based on the pre-built linkage rule, generating a control instruction of the execution device linked with the trigger device, and sending the control instruction to the execution device; receiving the 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 the devices that need to be linked control, and the linkage control between the devices is realized through the message dialogue between the devices in the device linkage group, so that the linkage control between the devices can be displayed in the form of dialogue, making the linkage control process between the 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 linkage control dialogue display diagram according to an embodiment of the present disclosure is shown;

[0032] Figure 3 A schematic block diagram showing 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 a conversation 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 specified.

[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, in order to better illustrate the present disclosure, numerous specific details are given in the following specific embodiments. It should be understood by those skilled in the art that the present disclosure can also be implemented without certain specific details. In some examples, methods, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present disclosure.

[0037] <Method Example>

[0038] Figure 1 FIG. 1 is a flow chart showing a method for device linkage 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 state change message sent by the trigger device in the pre-built device linkage group; S1200, when the state 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 dialogue, 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 to the device linkage control APP, you can build a device linkage group according to 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 is obtained, and the obtained device identifications are 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. In this case, you can search for nearby devices, select the required device from the searched devices, 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, at least two devices that need to be linked and controlled are selected from the device list, and each selected device is created into a chat group to obtain a device linkage group. The created device linkage group will include at least two devices that need to be linked and controlled, a user, and a robot for group message monitoring. Each device, user, and robot in the device linkage group can achieve linkage control with each other through natural language dialogue.

[0047] After the device linkage group is built, the linkage control of each device in the group can be performed based on the device linkage group. It should be noted here that for the sake of clarity, the device used to trigger the linkage control in the group is described as a triggering device, and the device that performs linkage operations with the triggering device is described as an execution device.

[0048] During the device linkage control process, when the state of the trigger device in the device linkage group changes, it will send state change data reflecting its state change to the device linkage control APP. Specifically, when the state of the trigger device changes, it will generate corresponding state change data, and then send the state change data to the robots in the device linkage group by calling the first API interface for data transmission predefined in the bubble library. When the first API interface is called, it will organize the state change data of the trigger device into a specified data structure and send it to the device linkage control APP.

[0049] In a possible implementation, the state change data may include at least one of: a message type type, a message sending object toObj, a message text content content, and a device control data command. The message type type is used to characterize the type of the message sending object, and the type of the message sending object may include at least one of a device, a robot, and a designated person in a device linkage group. When the message sending object is a device in a device linkage group, the message type is recorded as 0; when the message sending object is a designated person in a device linkage group, the message type is recorded as 1; when the message sending object is a robot in a device linkage group, the message type is 2. The message sending object toObj is used to record the specific identification of the message sending object. For example, when the message sending object is the device "lamp" in the device linkage group and the identification of the lamp is ledLight, the message sending object toObj is recorded as ledLight. The message text content content is the natural language text corresponding to the device status. It should be noted here that the status of the device is usually characterized by the fields and values ​​pre-set in the firmware. In order to allow the user to clearly understand the current status of the device, the status of the device is converted into the corresponding natural language text, so that the user can intuitively understand the status of the device. For example, when the light is on, the message text content corresponding to its status is set to "turned on". When the message is sent to a robot or a designated person in a device linkage group, the device control data command field is omitted. When the message is sent to a device in a device linkage group, the state change data will include the device control data command, which includes the device control method and the attribute value corresponding to the device control method. When the device control method and the attribute value corresponding to the device control method are clarified, 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 state change data will be sent to the device linkage control APP through the calling function sendMessage(2,bot,'Someone is coming') of the first API interface, so that the human body sensor in the device linkage group will be controlled by the device linkage control APP to send the message content of someone 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 lights in the device linkage group to control the lights 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 turn on the lights, the device control method in the device control data command is setSwith, and the corresponding attribute value is true, and 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 sensor, and the human 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 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, the @Xudong Assistant bot and someone has come are combined into the status change message of the human sensor, and the human 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 shown. In this way, the user can know that the human 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 the 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 the light on. At this time, @light and the light on are combined to form the state change message corresponding to the robot, and the robot in the device linkage group is controlled to send the @light light on state change message.

[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 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. By running the linkage control program, control instructions for an execution device that is linked to the trigger device can be generated and the control instructions can be sent to the execution device.

[0064] It should be noted here that in order to reduce the difficulty of developing device linkage programs, a bubble library is pre-built, which pre-defines the code structure and API interface for device linkage development. Among them, the pre-defined code structure includes the code structure for device declaration and the code structure for initialization. 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 is desired to be recorded 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 as mentioned 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, including 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, human, robot;

[0081] contentType:0, / / Reserved field, can identify different transmitted data contents, support more complex application 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 to 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 the 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 build the device linkage program based on the code structure and API interface defined in the bubble library. The following example illustrates the built device linkage program in conjunction with 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 rules are 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 with 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 call the corresponding third API interface in the bubble library based on the parsed device control data command, so as to realize 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 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 realize the control operation of the execution device through the corresponding third API interface.

[0106] After the execution device operation is completed, the state of the execution device will be monitored. After the state of the execution device changes, the state change data of the execution device will be generated in accordance with the triggering device. The state change data of the execution device is the response data generated by the execution device in response to the control instruction, that is, the response data is the same as the state change data, and both include at least one of the message type type, message sending object toObj, message text content content and device control data command described above. After the response data is generated, the response data is sent to the device linkage control APP, so that the device linkage control APP can receive 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's 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 execution device linked to the human body sensor is a lamp. When the sensor detects that someone is coming, the lamp will turn on the light and send a message in the device linkage group that the light is turned on. In this way, users can clearly understand the linkage operation between the human body sensor and the lamp.

[0108] Therefore, the method disclosed in the present invention can clearly understand the linkage operation between devices through the natural language dialogue between devices in the device linkage group, which not only increases the fun of the 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] A message monitoring module 110 is used to monitor the state 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 with the trigger device based on a pre-built 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 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.

[0114] <Equipment Embodiment>

[0115] Figure 4 FIG. 1 is 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] Here, it should be noted that the number of processors 210 may be one or more. Meanwhile, in the dialogue-based device linkage device 200 of the embodiment of the present disclosure, an input device 230 and an output device 240 may also be included. The processor 210, the memory 220, the input device 230 and the output device 240 may be connected via a bus or in other ways, which are not specifically limited here.

[0117] The memory 220 is a computer-readable storage medium that can be used to store software programs, computer executable programs, and various modules, such as the program or module corresponding to the dialogue-based device linkage method of the embodiment of the present disclosure. The processor 210 executes various functional applications and data processing of the dialogue-based device linkage device 200 by running the software programs or modules stored in the memory 220.

[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 display devices such as display screens.

[0119] <Storage Medium Embodiment>

[0120] According to a fourth aspect of the present disclosure, a non-volatile computer-readable storage medium is also 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] The embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or technical improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A device linkage method based on dialogue, characterized in that: include: Listen to the status change messages sent by the trigger devices in the pre-built device linkage group; In the case of monitoring the state change message, generating a control instruction of an execution device linked with the trigger device based on a pre-built linkage rule, and sending the control instruction to the execution device; 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.

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 Before monitoring the status change message sent by the trigger device in the pre-built device linkage group, it also includes: Acquire the state change data sent by the trigger device; Based on the state change data sent by the trigger device, the trigger device in the device linkage group is controlled to send the state change message.

4. The method according to claim 3, characterized in that The state change data includes: at least one of: message type, message sending object, message text content and device control data; The message type is used to represent the type of the object to which the message is sent, and the type of the object to which the message is sent includes at least one of a device, a person, and a designated member in the device linkage group.

5. The method according to claim 4, characterized in that When the trigger device in the device linkage group is controlled to send the state change message based on the state change data sent by the trigger device, the method includes: Parsing the message type, message sending object and message text content from the state change data; 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 trigger device in the device linkage group is controlled to send the state change message.

6. 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.

7. The method according to claim 6, characterized in that The predefined API interface includes a first API interface for data transmission and a second API interface for data subscription.

8. 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 generation module is used to generate a control instruction for an execution device linked with the trigger device based on a pre-built linkage rule when the state change message is monitored, and send the control instruction to the execution device; 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.

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

10. 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 7 is implemented.

Images