Scene processing method, apparatus, device, storage medium, and product

Abstract

A scene processing method, device, equipment, storage medium and product belong to the technical field of Internet of Things. The method is executed by a client device, and the method comprises: obtaining device information of an Internet of Things device which is proxied by a proxy device (501); and creating an Internet of Things scene corresponding to the Internet of Things device according to the device information (502). The method can expand the creation and use of the Internet of Things scene, and improve the use flexibility of the Internet of Things scene.

Description

Scene processing method, device, equipment, storage medium and product Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a scene processing method, device, equipment, storage medium and product. Background Art

[0002] With the continuous development of Internet of Things (IoT) technology, more and more IoT devices have brought great convenience to users' production and life in many fields such as smart homes and industrial production.

[0003] In related technologies, multiple IoT devices can be connected to the same cloud server / hub device, and users can configure an IoT scenario with multiple devices linked together in the cloud server / hub device. The cloud server / hub device can control the linkage of multiple IoT devices involved in the IoT scenario.

[0004] Summary of the Invention

[0005] The present application provides a scene processing method, apparatus, device, storage medium, and product. The technical solution is as follows:

[0006] In one aspect, an embodiment of the present application provides a scene processing method, which is executed by a client device and includes:

[0007] Get the device information of the IoT device that the proxy device represents;

[0008] Create an IoT scenario corresponding to the IoT device based on the device information.

[0009] In one aspect, an embodiment of the present application provides a scenario processing method, which is performed by an agent device and includes:

[0010] The device information of the Internet of Things device represented by the proxy device is sent to the client device, so that the client device creates an Internet of Things scene corresponding to the Internet of Things device according to the device information.

[0011] On the other hand, an embodiment of the present application provides a scene processing device, the device comprising:

[0012] An information acquisition module, used to obtain device information of the IoT device that the proxy device represents;

[0013] A scenario creation module is used to create an Internet of Things scenario corresponding to the Internet of Things device based on the device information.

[0014] On the other hand, an embodiment of the present application provides a scene processing device, the device comprising:

[0015] The sending module is used to send the device information of the Internet of Things device represented by the proxy device to the client device, so that the client device creates an Internet of Things scene corresponding to the Internet of Things device according to the device information.

[0016] On the other hand, an embodiment of the present application provides a computer device, wherein the computer device is implemented as an information reporting device, and the computer device includes a processor, a memory, and a transceiver;

[0017] The memory stores a computer program, and the processor executes the computer program so that the computer device implements the above-mentioned scene processing method.

[0018] On the other hand, an embodiment of the present application provides a computer device, which includes a processor, a memory and a transceiver, wherein the memory stores a computer program, and the computer program is used to be executed by the processor to implement the above-mentioned scene processing method.

[0019] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement the above-mentioned scene processing method.

[0020] On the other hand, the present application also provides a chip, which includes a circuit structure, and the chip is used to run in a computer device so that the computer device executes the above-mentioned scene processing method.

[0021] In another aspect, the present application provides a computer program product, the computer program product including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the above-mentioned scene processing method.

[0022] On the other hand, the present application provides a computer program, which is executed by a processor of a computer device to implement the above-mentioned scene processing method.

[0023] Through the technical solution provided in the embodiments of the present application, the client device can obtain the device information of the IoT device represented by the proxy device, and create an IoT scene corresponding to the IoT device based on the device information obtained from the proxy device, thereby expanding the way of creating and using IoT scenes and improving the flexibility of using IoT scenes. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG1 is a schematic diagram of a network architecture of the Internet of Things provided by one embodiment of the present application;

[0025] FIG2 is a schematic diagram of an IoT agent discovery binding involved in this application;

[0026] FIG3 is a schematic diagram of an interconnection method involved in this application;

[0027] FIG4 is a schematic diagram of another interconnection method involved in this application;

[0028] FIG5 is a flowchart of a scene processing method provided by one embodiment of the present application;

[0029] FIG6 is a flowchart of a scene processing method provided by one embodiment of the present application;

[0030] FIG7 is a flowchart of a scene processing method provided by one embodiment of the present application;

[0031] FIG8 is a schematic diagram of the creation and control of an IoT scenario involved in this application;

[0032] FIG9 is a schematic diagram of the creation and control of an IoT scenario involved in this application;

[0033] FIG10 is a schematic diagram of the creation and control of an IoT scenario involved in this application;

[0034] FIG11 is a block diagram of a scene processing device provided by one embodiment of the present application;

[0035] FIG12 is a block diagram of a scene processing device provided by one embodiment of the present application;

[0036] FIG13 is a schematic diagram of the structure of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0037] Please refer to Figure 1, which shows a schematic diagram of the network architecture of the Internet of Things provided by one embodiment of the present application. The network architecture of the Internet of Things may include: Internet of Things devices 110 (shown in Figure 1 as Internet of Things devices 110a, 110b, 110c, and 110d), proxy devices 120 (shown in Figure 1 as proxy devices 120a and 120b), and vehicles 130 (shown in Figure 1 as vehicles 130a, 130b, and 130c); optionally, the network architecture may further include a bridge device 140; optionally, the network architecture may further include a cloud server 150.

[0038] The IoT device 110 may refer to a device in the IoT that is used to provide client functions or server functions corresponding to the IoT protocol.

[0039] For example, the IoT device 110 may be a smart home device, such as a smart TV, a smart speaker, a smart switch, a smart lamp, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, and the like.

[0040] Alternatively, the IoT device 110 may be an industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, and the like.

[0041] Alternatively, the IoT device 110 may be a commercial service device, such as an unmanned vending machine, etc.

[0042] Alternatively, the IoT device 110 may be a sensing device, such as a surveillance camera, an infrared sensor, a sound sensor, a temperature sensor, and the like.

[0043] In one possible implementation, the proxy device 120 is a user-side terminal device, such as a smartphone, tablet computer, smartwatch, or a personal computer, such as a desktop computer, laptop computer, or personal workstation.

[0044] In another possible implementation, the proxy device 120 refers to a client entity (which may be a virtual entity) running on a terminal device. For example, the proxy device 120 may be an application (APP) running in the terminal device for accessing, controlling, and managing IoT devices.

[0045] The vehicle 130 may be a vehicle / on-board device capable of communicating with the proxy device 120 , for example, the vehicle 130 may be an on-board device (such as a vehicle computer), etc. The vehicle 130 may be configured to provide client or server functionality corresponding to an IoT protocol.

[0046] The proxy device 120 may establish a connection with the vehicle 130 through the cloud server 150 .

[0047] The bridge device 140 is used to enable interaction between two devices supporting different IoT protocols. The bridge device 140 provides information conversion and transmission services between IoT devices 110 supporting different IoT protocols, or between an IoT device 110 supporting different IoT protocols and a proxy device 120.

[0048] The bridge device 140 may be a device dedicated to bridging, or the bridge device 140 may be an intelligent device with a bridging function, such as a gateway or a router.

[0049] The cloud server 150 is used to provide a connection service between the IoT device 110 and other devices outside the IoT ecosystem (such as the aforementioned proxy device 120). The cloud server 150 can be a cloud platform server of the IoT ecosystem.

[0050] The proxy device 120 may also directly establish a connection with the IoT device 110 .

[0051] Alternatively, the proxy device 120 may also establish a connection with the IoT device 110 through the cloud server 150 .

[0052] Alternatively, the proxy device 120 may also establish a connection with the IoT device 110 through the bridge device 140 .

[0053] In the embodiment of the present application, the IoT device 110, proxy device 120, and bridge device 140 may be electronic devices that comply with the same or different IoT protocols. For example, they may be electronic devices that comply with the Matter protocol under the Connectivity Standards Alliance (CSA).

[0054] In FIG1 , when the IoT device 110 a and the IoT device 110 c support the same protocol specification, a secure connection may be established between the IoT device 110 a and the IoT device 110 c , for example, a secure connection may be established based on the Matter specification.

[0055] When the IoT device 110 b and the IoT device 110 d support different protocol specifications, for example, the IoT device 110 b is a Zigbee device and the IoT device 110 d is a Matter device, the IoT device 110 b and the IoT device 110 d may be connected via the bridge device 140 .

[0056] 1) IoT agent discovery and binding

[0057] Taking the example of a car computer being used to implement the client function in the IoT protocol, the user can bind the IoT agent on the mobile phone to the IoT client on the car computer, so that the car computer client can access the IoT devices managed on the mobile phone. Please refer to Figure 2, which shows a schematic diagram of an IoT agent discovery binding involved in this application. As shown in Figure 2, the binding process is as follows:

[0058] ①The user starts the binding process on the mobile phone;

[0059] ② The IOTAgent discovers the identifier of the IoT Client cluster of the IOT Client and determines whether it supports access to smart home capabilities. The IoT Client cluster may store information such as various attributes of the IoT Client.

[0060] ③Return the protocol version supported by IOTClient: version id;

[0061] ④[Optional] The IoT Agent obtains the list of devices supported by the IoT Client, such as the supported device type information (supporteddevicetype); the supporteddevicetype may include the types of devices supported by the IoT Client;

[0062] ⑤Return the list of supported controllable devices;

[0063] ⑥ The user chooses temporary binding or long-term binding;

[0064] ⑦ If it is a long-term binding, the binding relationship needs to be set in the binding table;

[0065] ⑧Notify IOTClient of the binding type;

[0066] ⑨IOTClient sets the binding type to the IoTClient cluster.

[0067] 2) IoTClient cluster

[0068] The IoT Client functional unit (IoTClient cluster) is deployed on the IoT Client (IOTClient) and records the IOTClient's ability to access IoT ecological devices.

[0069] The properties of the IoT Client Cluster are defined in Table 1.

[0070] Table 1

[0071] Among them, VendorID is the manufacturer identifier; SupportedDeviceTypes is the device type of IoT devices supported by the client device, and the value is a list of device types; bindingSource corresponds to the client binding information list.

[0072] The deviceTypeList structure (struct) in Table 1 above is shown in Table 2 below.

[0073] Table 2

[0074] Among them, when AllDevices is FALSE, the device type list contains the device type identification (Identity, ID) of one or more IoT devices that the client device supports controlling; and when AllDevices is TRUE, the value of AllDevices is empty.

[0075] The clientBindingInfo structure in Table 2 above is used to record the binding relationship between the client device and the IOT agent. Based on this information, the IOT Client can determine whether to save the list of controllable devices sent by the IOT Agent and other information during the subsequent device control process.

[0076] The clientBindingInfo structure is shown in Table 3 below.

[0077] Table 3

[0078] AgentID contains the identifier of the agent that has established a binding relationship with the client device. The value of BindingType indicates whether the binding relationship is a long-term binding or a temporary binding. When the value of the above BindingType is 0, it means that the binding relationship is a temporary binding. After the subsequent client device controls the IoT device connected to the device corresponding to the IOT agent ID, it is not necessary to save the list of controllable devices and other information sent by the device corresponding to the IOT agent ID. On the contrary, when the value of the above BindingType is 1, it means that the binding relationship is a long-term binding. After the subsequent client device controls the IoT device connected to the device corresponding to the IOT agent ID, it is possible to save the list of controllable devices and other information sent by the device corresponding to the IOT agent ID for use next time when controlling the IoT device connected to the device corresponding to the IOT agent ID.

[0079] For example, if the client device is a vehicle-mounted device, the proxy device is the user's mobile phone, and the IoT device is a piece of furniture, a unified interconnection interface is used between the proxy and the vehicle client. There are two possible interconnection methods.

[0080] ① Please refer to Figure 3, which shows a schematic diagram of an interconnection method involved in this application. As shown in Figure 3, different apps on the mobile phone are interconnected with the car client through a unified IOT proxy.

[0081] ②Please refer to Figure 4, which shows another interconnection method involved in this application. As shown in Figure 4, each home APP implements its own IOT agent and interconnects with the car client respectively.

[0082] Subsequent embodiments of the present application provide a solution for creating and maintaining IoT scenarios involving client devices through client devices in an architecture in which client devices and IoT devices are interconnected through proxy devices.

[0083] Please refer to FIG5 , which shows a flow chart of a scene processing method provided by one embodiment of the present application. The method may be executed by a client device. For example, the client device may be the vehicle 130 in the network architecture shown in FIG1 , or may be another type of client, such as a smart TV. The method may include the following steps:

[0084] Step 501: Obtain device information of the IoT device that is represented by the proxy device.

[0085] In the embodiment of the present application, the proxy device is connected to one or more IoT devices via an IoT interface, and the proxy device is also connected to a client device.

[0086] For example, one or more IOT Agents are installed and running in the agent device (for example, the IOT Agent can be an APP or a plug-in in the APP), each IOT Agent is connected to one or more IoT devices, and each IOT Agent is also connected to the IOT Client in the client device.

[0087] In some embodiments, the IoT device and the client device may belong to different IoT ecosystems; or, the IoT device and the client device may belong to the same IoT ecosystem.

[0088] In an embodiment of the present application, a client device can discover surrounding proxy devices. After discovering the proxy device, it can establish a connection with the proxy device and obtain device information of the IoT device that the proxy device represents from the proxy device.

[0089] Step 502: Create an IoT scene corresponding to the IoT device based on the device information.

[0090] Among them, the above-mentioned IoT scenario can also be called an IoT linkage scenario, which refers to a scenario in which one or more IoT devices perform corresponding functional operations under the triggering of pre-set conditions / rules.

[0091] In an embodiment of the present application, after obtaining the device information of the IoT device represented by the proxy device, the client device can automatically match the appropriate IoT scenario according to the device information of the IoT device and establish the corresponding IoT scenario.

[0092] Alternatively, after obtaining the device information of the IoT device represented by the proxy device, the client device can also display the device information of the IoT device to the user of the client device. The user can manually configure the IoT scenario based on the device information of the IoT device, and the client device generates the above-mentioned IoT scenario according to the user's configuration operations.

[0093] To sum up, the client device can obtain the device information of the IoT device represented by the proxy device, and create the IoT scene corresponding to the IoT device based on the device information obtained from the proxy device, thereby expanding the way of creating and using IoT scenes and improving the flexibility of using IoT scenes.

[0094] Please refer to FIG6 , which shows a flow chart of a scenario processing method provided by an embodiment of the present application. The method may be performed by a proxy device. For example, the proxy may be the proxy device 120 in the network architecture shown in FIG1 . The method may include the following steps:

[0095] Step 601: Send device information of the Internet of Things device represented by the proxy device to the client device, so that the client device creates an Internet of Things scene corresponding to the Internet of Things device according to the device information.

[0096] To sum up, the client device can obtain the device information of the IoT device represented by the proxy device, and create the IoT scene corresponding to the IoT device based on the device information obtained from the proxy device, thereby expanding the way of creating and using IoT scenes and improving the flexibility of using IoT scenes.

[0097] Please refer to FIG7 , which shows a flowchart of a scenario processing method provided by an embodiment of the present application. The method can be interactively executed by a proxy device and a client device. For example, the proxy device can be the proxy device 120 in the network architecture shown in FIG1 , and the client device can be the vehicle 130 or the IoT device 110 (such as other types of clients, such as a smart TV, etc.) in the network architecture shown in FIG1 . The method can include the following steps:

[0098] In step 701, the proxy device sends device information of the Internet of Things device that the proxy device represents to the client device; the client device receives the device information of the Internet of Things device.

[0099] The proxy device may be a physical device, or the proxy device may be a proxy APP installed and running in a physical device.

[0100] In an embodiment of the present application, the client device may perform proxy discovery after startup or at a certain period to discover surrounding proxy devices and establish a connection with the proxy device; thereafter, the client device may send device information of each client device proxied by the proxy device to the proxy device, and correspondingly, the proxy device sends the device information of the client devices it proxies to the client device.

[0101] In some embodiments, the device information of the IoT device includes one or more of the following: identification information of the IoT device, and capability information of the IoT device.

[0102] In an embodiment of the present application, the proxy device can send the identification information of the IoT device and / or the capability information of the IoT device to the client device, so that the client device can subsequently determine the functions that the IoT device can support based on the identification information of the IoT device and / or the capability information of the IoT device, thereby accurately establishing the corresponding IoT scenario.

[0103] In step 702, the client device creates an IoT scene corresponding to the IoT device according to the device information.

[0104] In an embodiment of the present application, the client device creates an IoT scene corresponding to the IoT device, which may refer to creating and storing scene information of the IoT scene.

[0105] In some embodiments, the client device creates an IoT scenario corresponding to the IoT device based on the device information, which may include:

[0106] The client device creates and saves scene information of the IoT scene in the client device; or,

[0107] The client device sends a scene setting instruction to the proxy device, which includes the scene information of the Internet of Things device. The scene setting instruction is used to instruct the proxy device to save the scene information of the Internet of Things scene; accordingly, the proxy device receives the scene setting instruction sent by the client device and saves the scene information of the Internet of Things scene.

[0108] In an embodiment of the present application, the client device can locally create and save the scene information of the Internet of Things scene. The client device can subsequently control the Internet of Things scene based on the scene information of the Internet of Things scene stored locally, thereby facilitating the subsequent control of the Internet of Things scene through the client device and ensuring the control efficiency of the Internet of Things scene.

[0109] Alternatively, the client device may also save the scene information of the IoT scene to the proxy device after creating the scene information of the IoT scene. Specifically, the client device may send a scene setting instruction containing the scene information of the IoT scene to the proxy device after creating the scene information of the IoT scene. After receiving the scene setting instruction, the proxy device saves the scene information of the IoT scene in the scene setting instruction in a local cluster (Cluster, such as a scene Cluster); subsequently, when the scene information of the IoT scene in the client device is cleared, the scene information of the IoT scene may also be obtained from the proxy device and the IoT scene may be controlled to ensure the effectiveness of the control of the IoT scene.

[0110] In some embodiments, the scene information includes scene content; the scene content includes one or more of the following information:

[0111] Identification information of IoT devices, identification information of proxy devices, and sequence information involved in IoT scenarios;

[0112] The sequence information is used to indicate the order and / or priority of calling IoT devices when an IoT scenario is triggered.

[0113] In an embodiment of the present application, the above-mentioned scenario information can indicate the IoT devices, proxy devices involved in the IoT scenario, and the order and / or priority of calling the IoT devices when the IoT scenario is triggered, ensuring that each IoT device can be accurately controlled to perform corresponding operations through the scenario information, thereby ensuring the accuracy of the execution of the IoT scenario.

[0114] In some embodiments, when the scene information is stored in the client device, the scene information also includes trigger mode information, and the trigger mode information is used to indicate one or more of the following trigger modes:

[0115] Triggered by time, manually, or by the status of other devices.

[0116] In an embodiment of the present application, the above-mentioned scenario information can also indicate the triggering method of the Internet of Things scenario, thereby supporting Internet of Things scenarios with multiple different triggering methods and improving the application scope of the Internet of Things scenario.

[0117] In some embodiments, the scene information further includes trigger time information; the trigger time information takes effect when the trigger mode information indicates a mode triggered by time.

[0118] In an embodiment of the present application, when the trigger mode information indicates a mode triggered by time, the scene information may also indicate trigger time information to ensure the accuracy of the execution of the IoT scene triggered by the trigger time.

[0119] In some embodiments, the trigger time information includes one or more of the following information:

[0120] Cycle information is used to indicate whether the IoT scenario is cyclic. For example, the cycle information can be represented by a specific character. For example, when the cycle information is 1, it indicates a cyclic trigger, and when the cycle information is 0, it indicates a non-cyclic trigger; or, when the cycle information is 0, it indicates a cyclic trigger, and when the cycle information is 1, it indicates a non-cyclic trigger;

[0121] Period information, used to indicate the time period within a period when the IoT scenario is triggered; for example, the period may be a week, and the above time period may be every day of the week (24 hours);

[0122] The startup time information is used to indicate the startup time of the IoT scenario. For example, the startup time can be an absolute time, such as 7:00 a.m.

[0123] Multiple types of information in the above-mentioned trigger time information can be used in combination; for example, when it is assumed that the cycle information indicates a cyclic trigger, the period information indicates Monday to Friday of each week, and the start time information indicates 7:00 a.m., it means that the Internet of Things scene is triggered at 7:00 a.m. from Monday to Friday of each week; for another example, when it is assumed that the cycle information indicates no cyclic triggering, and the start time information indicates 7:00 a.m., it means that the Internet of Things scene is triggered at 7:00 a.m. next time.

[0124] In an embodiment of the present application, when the trigger mode information indicates a time-triggered mode, the above-mentioned trigger time information can support multiple time-triggered modes such as cyclic triggering, periodic triggering, and specific time triggering, further improving the application scope of the Internet of Things scenario.

[0125] In some embodiments, the scene information further includes trigger status information; the trigger status information is effective when the trigger mode information indicates a mode triggered by the status of other devices.

[0126] The trigger state information may indicate the properties of the state of other devices when triggering the IoT scene. For example, if the IoT scene is triggered by the brightness state detected by a light sensor, and the IoT scene is triggered when the brightness state detected by the light sensor is greater than a brightness threshold, the trigger state information may indicate that the IoT scene is triggered when the brightness state detected by the light sensor is greater than the brightness threshold.

[0127] In an embodiment of the present application, when the trigger mode information indicates a mode triggered by the status of other devices, the scene information may also indicate trigger status information to ensure the accuracy of the execution of the IoT scene triggered by the trigger time.

[0128] In some embodiments, the trigger status information includes one or more of the following information:

[0129] The identification information of the agent corresponding to the device that triggers the IoT scenario;

[0130] Identification information of the device that triggers the IoT scenario;

[0131] Attribute information of the device that triggers the IoT scene; wherein, the attribute information may include the status of the device that triggers the IoT scene, such as the brightness threshold mentioned above.

[0132] In an embodiment of the present application, when the trigger mode information indicates a mode triggered by the status of other devices, the scene information can indicate the agent, device, and device attributes corresponding to the device that triggers the IoT scene, thereby ensuring the accuracy of triggering the IoT scene through the status of other devices.

[0133] In some embodiments, when the scene information is stored in the proxy device, the scene content further includes scene priority information and / or sharing information;

[0134] The scenario priority information is used to indicate the priority of the IoT scenario;

[0135] Sharing information is used to indicate whether to allow sharing of IoT scenarios with other devices.

[0136] When the scene information is stored in the proxy device, a proxy device may establish connections with multiple client devices. Accordingly, different client devices may create different IoT scenes and store them in the proxy device. Therefore, it is possible that multiple IoT scenes corresponding to a proxy device are triggered at the same time; or, multiple IoT scenes may involve the same one or more IoT devices. When the execution time periods of multiple IoT scenes overlap, it may be necessary to consider which IoT scene the one or more IoT devices should execute the corresponding operation; in this regard, in an embodiment of the present application, the above-mentioned scene information may include scene priority information, so that when multiple IoT scenes corresponding to a proxy device are triggered at the same time, the execution priority of multiple IoT scenes can be controlled to ensure the accuracy of the execution of multiple IoT scenes.

[0137] In addition, when the scene information is stored in the proxy device, a proxy device may establish connections with multiple client devices. Accordingly, when other client devices establish connections with the proxy device, they may need to obtain the IoT scene saved in the proxy device. In this regard, in an embodiment of the present application, the above-mentioned scene information may include sharing information to indicate whether the IoT scene is allowed to be shared, thereby ensuring the sharing efficiency and security of the IoT scene.

[0138] In some embodiments, when the scene information is stored in the proxy device,

[0139] The identification information of the IoT scenario is generated by the client device; or, the identification information of the IoT scenario is generated by the proxy device.

[0140] In an embodiment of the present application, when the scene information is stored in the proxy device, the client device can directly generate identification information of the Internet of Things scene, thereby ensuring the efficiency of scene information generation of the Internet of Things scene.

[0141] Alternatively, when the scene information is stored in the proxy device, a proxy device may establish connections with multiple client devices. Accordingly, different client devices may create different IoT scenes and store them in the proxy device. Therefore, it is possible that the identification information of multiple IoT scenes corresponding to a proxy device is the same. At this time, the identification information of the IoT scene can be generated by the proxy device to avoid conflicts in the identification information of multiple IoT scenes.

[0142] In some embodiments, when the identification information of the IoT scenario is generated by a proxy device, the method further includes:

[0143] The client device receives the identification information of the Internet of Things scenario sent by the proxy device; and associates the identification information of the Internet of Things scenario with the Internet of Things scenario.

[0144] Accordingly, in the case where the identification information of the IoT scenario is generated by the proxy device, the proxy device sends the identification information of the IoT scenario to the client device so that the client device associates the identification information of the IoT scenario with the IoT scenario.

[0145] For example, after the client device sends a scene setting instruction to the proxy device, the proxy device extracts and saves the scene information of the Internet of Things scene according to the scene setting instruction, and generates identification information of the Internet of Things scene. On the one hand, the identification information of the Internet of Things scene is associated with the scene information of the Internet of Things scene, for example, the identification information of the Internet of Things scene is added to the identification information of the Internet of Things scene. On the other hand, the identification information of the Internet of Things scene is returned to the client device, and the client device associates the identification information of the Internet of Things scene with the scene information of the Internet of Things scene, for example, the identification information of the Internet of Things scene is added to the identification information of the Internet of Things scene locally stored on the client device, thereby ensuring the uniformity of the identification information of the Internet of Things scenes on the client device and the proxy device side, and then ensuring the accuracy of the triggering and execution of subsequent Internet of Things scenes.

[0146] In some embodiments, the client device may also send a management instruction to the proxy device, where the management instruction is used to modify or delete the IoT scenario. Optionally, the management instruction may include identification information of the IoT scenario.

[0147] In some embodiments, the method further includes: when the IoT scenario is triggered, the client device sends control commands corresponding to the IoT scenario to each IoT device involved in the IoT scenario in sequence.

[0148] In an embodiment of the present application, when an IoT scenario is triggered, the client device can, upon determining that the IoT scenario is triggered, send control commands corresponding to the IoT scenario to each IoT device involved in the IoT scenario in sequence according to the triggering order and / or priority of each IoT device involved in the IoT scenario (for example, sending control commands to the IoT device through the corresponding proxy device), thereby ensuring the accuracy of the execution of the IoT scenario.

[0149] In some embodiments, the method further comprises:

[0150] When an IoT scenario is triggered, the client device sends a scenario execution instruction to the proxy device, which includes the IoT scenario's identification information. Correspondingly, the proxy device receives the scenario execution instruction sent by the client device when the IoT scenario is triggered, which includes the IoT scenario's identification information.

[0151] In an embodiment of the present application, when an IoT scenario is triggered, the client device also sends an execution scenario instruction to the proxy device to indicate the IoT scenario that is triggered for execution. The proxy device can record the triggering situation according to the IoT scenario, verify or authenticate the control command corresponding to the IoT scenario sent by the client device, and ensure the accuracy of the execution of the IoT scenario.

[0152] This application introduces the solution shown in the above embodiment with the following three specific examples.

[0153] Option 1

[0154] Please refer to Figure 8, which shows a schematic diagram of the creation and control of an IoT scenario involved in this application. As shown in Figure 8, the creation and control process of the IoT scenario is as follows:

[0155] S81-S82: The IoT client discovers the IoT agent. For example, the IoT client discovers how many IoT agents exist on the mobile phone.

[0156] S83-S84, the IOT client obtains the device list and device capabilities (corresponding to the device information of the aforementioned IoT devices). For example, it may include the IOT agent ID and List{device ID, device capabilities}.

[0157] Optionally, device capabilities can refer to the information in Endpoints->clusters->{attributes commands events} contained in the device.

[0158] S85, IOT client manages each IoT device, such as information storage, binding, etc.

[0159] S86, setting an IoT scene on the IoT client. The scene information of the IoT scene may include the content shown in Table 4 below. Since it is saved on the client, no other device is required to trigger the creation and saving.

[0160] Table 4

[0161] S87-S88, the IOT client triggers the scenario according to the trigger condition and uses sequenceNo to determine the order in which the trigger instructions are sent to the agent.

[0162] Option 2

[0163] Please refer to Figure 9, which shows a schematic diagram of the creation and control of an IoT scenario involved in this application. As shown in Figure 9, the creation and control process of the IoT scenario is as follows:

[0164] S91-S92: The IoT client discovers the IoT agent. For example, the IoT client discovers how many IoT agents exist on the mobile phone.

[0165] S93-S94, the IOT client obtains the device list and device capabilities (corresponding to the device information of the aforementioned IoT devices). For example, it may include the IOT agent ID and List {device ID, device capabilities}.

[0166] Optionally, device capabilities can refer to the information in Endpoints->clusters->{attributes commands events} contained in the device.

[0167] S95-S98, the IOT client sets the scene content to the proxy device; the IOT client saves the scene.

[0168] The data model for saving scenes on the proxy device can be as shown in Table 5 below. The IoT client can operate scenes on the proxy device by creating, modifying, and deleting scenes. Attributes refer to scene saving, and commands refer to scene operations.

[0169] Table 5

[0170] S99, the IOT client sends an execution scenario instruction to the IOT agent.

[0171] S910, the IOT client triggers the scenario according to the trigger condition and uses sequenceNo to determine the order of sending trigger instructions to the agent.

[0172] Option 3

[0173] Please refer to Figure 10, which shows a schematic diagram of the creation and control of an IoT scenario involved in this application. As shown in Figure 10, the creation and control process of the IoT scenario is as follows:

[0174] The main difference between Solution 2 and Solution 3 is that when the IOTClient sets a scene, it does not set a SceneID. Instead, the IOTAgent automatically generates a SceneID and returns it to the IOTClient. In theory, the IOTAgent can ensure that the SceneID is a unique identifier, making it easier for the IOTAgent to manage the scene.

[0175] S1001-S1002, discover the IoT agent device.

[0176] S1003-S1004, discover the device list and device capabilities.

[0177] S1005, setting the scene, during the setting process, includes the scene name and the specific operation information of the scene.

[0178] S1006-S1007: IOTAgent generates a SceneID, saves the scene, and returns the SceneID to IOTClient.

[0179] S1008, after receiving the SceneID, the IOT Client uniformly manages the SceneIDs returned by multiple agents that constitute a scene, for example, associates them with the scene content of the IoT scene created above to form a complete IoT scene.

[0180] S1009-S1012, same as S95-S98.

[0181] Through the above-mentioned solution of this application, scene information can be stored between the IoT client and multiple IoT agents. When the IoT client is replaced, the IoT agent can quickly adapt to the scenes set by different IoT clients. The set scene content can also be shared between different IoT clients, and the scene can be set to be shared or exclusive according to user needs.

[0182] S1013, the IOT client sends an execution scenario instruction to the IOT agent.

[0183] S1014, the IOT client triggers the scenario according to the trigger condition and uses sequenceNo to determine the order of sending trigger instructions to the agent.

[0184] Please refer to Figure 11, which shows a block diagram of a scene processing device provided by an embodiment of the present application. The scene processing device 1100 has the functions of implementing the methods shown in Figures 5, 6, or 7 above, which are performed by the client device. As shown in Figure 11, the device may include:

[0185] The information acquisition module 1101 is used to obtain device information of the IoT device that the proxy device represents;

[0186] The scene creation module 1102 is used to create an Internet of Things scene corresponding to the Internet of Things device according to the device information.

[0187] In some embodiments, the scene creation module is used to:

[0188] Creating and saving scene information of the Internet of Things scene in the client device; or,

[0189] A scene setting instruction is sent to the proxy device, where the scene setting instruction includes scene information of the Internet of Things device, and the scene setting instruction is used to instruct the proxy device to save the scene information of the Internet of Things scene.

[0190] In some embodiments, the scene information includes scene content; the scene content includes one or more of the following information:

[0191] Identification information of the IoT device involved in the IoT scenario, identification information of the proxy device, and sequence information;

[0192] The sequence information is used to indicate the order and / or priority of calling the IoT devices when the IoT scenario is triggered.

[0193] In some embodiments, when the scene information is stored in the client device, the scene information further includes trigger mode information, where the trigger mode information is used to indicate one or more of the following trigger modes:

[0194] Triggered by time, manually, or by the status of other devices.

[0195] In some embodiments, the scene information further includes trigger time information; the trigger time information takes effect when the trigger mode information indicates a mode triggered by time.

[0196] In some embodiments, the trigger time information includes one or more of the following information:

[0197] Cycle information, used to indicate whether the IoT scenario is cyclic;

[0198] Cycle information, used to indicate the time period of the IoT scenario triggering in a cycle;

[0199] The startup time information is used to indicate the startup time of the IoT scenario.

[0200] In some embodiments, the scenario information further includes trigger status information; the trigger status information is effective when the trigger mode information indicates a mode triggered by the status of other devices.

[0201] In some embodiments, the trigger status information includes one or more of the following information:

[0202] Identification information of the agent corresponding to the device that triggers the IoT scenario;

[0203] Identification information of the device that triggers the IoT scenario;

[0204] Attribute information of the device that triggers the IoT scenario.

[0205] In some embodiments, when the scene information is stored in the proxy device, the scene content further includes scene priority information and / or sharing information;

[0206] The scenario priority information is used to indicate the priority of the IoT scenario;

[0207] The sharing information is used to indicate whether to allow sharing of the IoT scenario with other devices.

[0208] In some embodiments, when the scene information is stored in the proxy device,

[0209] The identification information of the Internet of Things scenario is generated by the client device; or,

[0210] The identification information of the Internet of Things scenario is generated by the proxy device.

[0211] In some embodiments, when the identification information of the Internet of Things scenario is generated by the proxy device, the apparatus further includes:

[0212] A receiving module, configured to receive identification information of the Internet of Things scenario sent by the proxy device;

[0213] An association module is used to associate the identification information of the Internet of Things scenario with the Internet of Things scenario.

[0214] In some embodiments, the apparatus further comprises:

[0215] The first sending module is used to send control commands corresponding to the Internet of Things scenario in sequence to each Internet of Things device involved in the Internet of Things scenario when the Internet of Things scenario is triggered.

[0216] In some embodiments, the apparatus further comprises:

[0217] The first sending module is used to send an execution scenario instruction to the proxy device when the Internet of Things scenario is triggered, and the execution scenario instruction includes identification information of the Internet of Things scenario.

[0218] In some embodiments, the device information of the IoT device includes one or more of the following:

[0219] The identification information of the IoT device and the capability information of the IoT device.

[0220] Please refer to Figure 12, which shows a block diagram of a scene processing device provided by an embodiment of the present application. The scene processing device 1200 has the functions of implementing the methods shown in Figures 5, 6, or 7 above, which are performed by the proxy device. As shown in Figure 12, the device may include:

[0221] The sending module 1201 is configured to send device information of the IoT device represented by the proxy device to a client device, so that the client device creates an IoT scenario corresponding to the IoT device according to the device information.

[0222] In some embodiments, the scene information of the IoT device is stored in the client device; or, the apparatus further includes:

[0223] A first receiving module is configured to receive a scene setting instruction sent by the client device, wherein the scene setting instruction includes scene information of the IoT device;

[0224] The storage module is used to store the scene information of the Internet of Things scene.

[0225] In some embodiments, the scene information includes scene content; the scene content includes one or more of the following information:

[0226] Identification information of the IoT device involved in the IoT scenario, identification information of the proxy device, and sequence information;

[0227] The sequence information is used to indicate the order and / or priority of calling the IoT devices when the IoT scenario is triggered.

[0228] In some embodiments, when the scene information is stored in the client device, the scene information further includes trigger mode information, where the trigger mode information is used to indicate one or more of the following trigger modes:

[0229] Triggered by time, manually, or by the status of other devices.

[0230] In some embodiments, the scene information further includes trigger time information; the trigger time information takes effect when the trigger mode information indicates a mode triggered by time.

[0231] In some embodiments, the trigger time information includes one or more of the following information:

[0232] Cycle information, used to indicate whether the IoT scenario is cyclic;

[0233] Cycle information, used to indicate the time period of the IoT scenario triggering in a cycle;

[0234] The startup time information is used to indicate the startup time of the IoT scenario.

[0235] In some embodiments, the scenario information further includes trigger status information; the trigger status information is effective when the trigger mode information indicates a mode triggered by the status of other devices.

[0236] In some embodiments, the trigger status information includes one or more of the following information:

[0237] Identification information of the agent corresponding to the device that triggers the IoT scenario;

[0238] Identification information of the device that triggers the IoT scenario;

[0239] Attribute information of the device that triggers the IoT scenario.

[0240] In some embodiments, when the scene information is stored in the proxy device, the scene content further includes scene priority information and / or sharing information;

[0241] The scenario priority information is used to indicate the priority of the IoT scenario;

[0242] The sharing information is used to indicate whether to allow sharing of the IoT scenario with other devices.

[0243] In some embodiments, when the scene information is stored in the proxy device,

[0244] The identification information of the Internet of Things scenario is generated by the client device; or,

[0245] The identification information of the Internet of Things scenario is generated by the proxy device.

[0246] In some embodiments, when the identification information of the Internet of Things scenario is generated by the proxy device, the sending module is further used to send the identification information of the Internet of Things scenario to the client so that the client device associates the identification information of the Internet of Things scenario with the Internet of Things scenario.

[0247] In some embodiments, the apparatus further comprises:

[0248] The second receiving module is used to receive an execution scenario instruction sent by the client device when the Internet of Things scenario is triggered, and the execution scenario instruction includes identification information of the Internet of Things scenario.

[0249] In some embodiments, the device information of the IoT device includes one or more of the following:

[0250] The identification information of the IoT device and the capability information of the IoT device.

[0251] Please refer to FIG13 , which shows a schematic diagram of the structure of a computer device 1300 provided in one embodiment of the present application. The computer device 1300 may include: a processor 1301 , a receiver 1302 , a transmitter 1303 , a memory 1304 , and a bus 1305 .

[0252] Processor 1301 includes one or more processing cores. Processor 1301 executes various functional applications and information processing by running software programs and modules. Receiver 1302 and transmitter 1303 can be implemented as a communication component, which can be a communication chip. This communication chip can also be called a transceiver. Memory 1304 is connected to processor 1301 via bus 1305. Memory 1304 can be used to store computer programs, and processor 1301 is used to execute these computer programs to implement the various steps in the above-described method embodiments.

[0253] In addition, the memory 1304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disk or optical disk, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0254] In an exemplary embodiment, when computer device 1300 is implemented as the aforementioned proxy device, processor 1301 and / or transceiver is configured to transmit device information of an IoT device proxied by the proxy device to a client device, so that the client device creates an IoT scenario corresponding to the IoT device based on the device information. The processes performed by processor 1301 and / or transceiver in computer device 1300 may refer to the steps performed by the proxy device in the method shown in either FIG. 5 or FIG. 7 .

[0255] In one exemplary embodiment, when computer device 1300 is implemented as a client device, processor 1301 and / or transceiver are configured to obtain device information of an IoT device represented by a proxy device and create an IoT scenario corresponding to the IoT device based on the device information. The processes performed by processor 1301 and / or transceiver in computer device 1300 can refer to the steps performed by the client device in the method shown in either FIG. 5 or FIG. 7 .

[0256] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. The computer program is loaded and executed by a processor to implement all or part of the steps performed by the proxy device or the client device in the method shown in Figure 5, Figure 6 or Figure 7 above.

[0257] The present application also provides a chip, which includes a circuit structure and is used to run in a computer device so that the computer device executes all or part of the steps performed by the proxy device or client device in the method shown in Figure 5, Figure 6 or Figure 7 above.

[0258] The present application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform all or part of the steps performed by the proxy device or client device in the method shown in Figures 5, 6, or 7 above.

[0259] The present application also provides a computer program, which is executed by a processor of a computer device to implement all or part of the steps performed by the proxy device or the client device in the method shown in Figure 5, Figure 6 or Figure 7 above.

Claims

1. A scene processing method, characterized in that, The method is executed by a client device, and the method includes: Obtaining device information of an Internet of Things (IoT) device proxied by a proxy device; Creating an IoT scenario corresponding to the IoT device according to the device information.

2. The method according to claim 1, wherein The creating an IoT scenario corresponding to the IoT device according to the device information includes: Creating and saving scenario information of the IoT scenario in the client device; or, Sending a set scenario instruction to the proxy device, where the set scenario instruction includes scenario information of the IoT device, and the set scenario instruction is used to instruct the proxy device to save the scenario information of the IoT scenario.

3. The method according to claim 2, characterized in that, The scenario information includes scenario content; the scenario content includes one or more of the following information: Identification information of the IoT device involved in the IoT scenario, identification information of the proxy device, sequence information; The sequence information is used to indicate the order and / or priority of invoking the IoT device when the IoT scenario is triggered.

4. The method according to claim 3, wherein When the scenario information is saved in the client device, the scenario information further includes trigger mode information, and the trigger mode information is used to indicate one or more of the following trigger modes: Triggering by time, triggering manually, triggering by the status of other devices.

5. The method according to claim 4, wherein The scenario information further includes trigger time information; the trigger time information takes effect when the trigger mode information indicates a mode of triggering by time.

6. The method according to claim 5, wherein The trigger time information includes one or more of the following information: Loop information, used to indicate whether the IoT scenario loops; Period information, used to indicate the time period in a cycle when the IoT scenario is triggered; Start time information, used to indicate the start time of the IoT scenario.

7. The method according to claim 4, wherein The scenario information further includes trigger status information; the trigger status information takes effect when the trigger mode information indicates a mode of triggering by the status of other devices.

8. The method according to claim 7, wherein The trigger status information includes one or more of the following information: Identification information of the proxy corresponding to the device that triggers the IoT scenario; Identification information of the device that triggers the IoT scenario; Attribute information of the device that triggers the IoT scenario.

9. The method according to claim 3, characterized in that, When the scenario information is saved in the proxy device, the scenario content further includes scenario priority information, and / or sharing information; The scenario priority information is used to indicate the priority of the IoT scenario; The sharing information is used to indicate whether sharing the IoT scenario with other devices is allowed.

10. The method according to claim 3 or 9, characterized in that When the scenario information is saved in the proxy device, The identification information of the IoT scenario is generated by the client device; or, The identification information of the IoT scenario is generated by the proxy device.

11. The method according to claim 10, wherein When the identification information of the IoT scenario is generated by the proxy device, the method further includes: Receiving the identification information of the IoT scenario sent by the proxy device; Associating the identification information of the IoT scenario with the IoT scenario.

12. The method according to any one of claims 2 to 11, characterized in that, The method further includes: When the Internet of Things (IoT) scenario is triggered, control commands corresponding to the IoT scenario are sequentially sent to each IoT device involved in the IoT scenario.

13. The method according to any one of claims 1 to 12, characterized in that, The method further includes: When the IoT scenario is triggered, an execution scenario instruction is sent to the proxy device, and the execution scenario instruction includes the identification information of the IoT scenario.

14. The method according to any one of claims 1 to 13, characterized in that, The device information of the IoT device includes one or more of the following: The identification information of the IoT device, the capability information of the IoT device.

15. A method for scene processing, characterized in that, The method is executed by a proxy device, and the method includes: Sending the device information of the IoT devices proxied by the proxy device to a client device, so that the client device creates an IoT scenario corresponding to the IoT device according to the device information.

16. The method according to claim 15, wherein The scenario information of the IoT device is saved in the client device; Alternatively, the method further includes: receiving a set scenario instruction sent by the client device, and the set scenario instruction includes the scenario information of the IoT device; Saving the scenario information of the IoT scenario.

17. The method according to claim 16, wherein The scenario information includes scenario content; the scenario content includes one or more of the following information: The identification information of the IoT devices involved in the IoT scenario, the identification information of the proxy device, sequence information; The sequence information is used to indicate the order and / or priority of calling the IoT devices when the IoT scenario is triggered.

18. The method according to claim 17, wherein When the scenario information is saved in the client device, the scenario information further includes trigger mode information, and the trigger mode information is used to indicate one or more of the following trigger modes: Triggered by time, triggered manually, triggered by the status of other devices.

19. The method according to claim 18, wherein The scenario information further includes trigger time information; the trigger time information takes effect when the trigger mode information indicates a mode triggered by time.

20. The method according to claim 19, wherein The trigger time information includes one or more of the following information: Loop information, used to indicate whether the IoT scenario loops; Period information, used to indicate the time period in a cycle when the IoT scenario is triggered; Start time information, used to indicate the start time of the IoT scenario.

21. The method according to claim 18, characterized in that, The scenario information further includes trigger status information; the trigger status information takes effect when the trigger mode information indicates a mode triggered by the status of other devices.

22. The method according to claim 21, wherein The trigger status information includes one or more of the following information: The identification information of the proxy corresponding to the device that triggers the IoT scenario; The identification information of the device that triggers the IoT scenario; The attribute information of the device that triggers the IoT scenario.

23. The method according to claim 17, wherein When the scenario information is saved in the proxy device, the scenario content further includes scenario priority information, and / or sharing information; The scenario priority information is used to indicate the priority of the IoT scenario; The sharing information is used to indicate whether it is allowed to share the IoT scenario with other devices.

24. The method according to claim 17 or 23, characterized in that, When the scenario information is saved in the proxy device, The identification information of the IoT scenario is generated by the client device; or, The identification information of the Internet of Things (IoT) scenario is generated by the proxy device.

25. The method according to claim 24, wherein When the identification information of the IoT scenario is generated by the proxy device, the method further includes: Sending the identification information of the IoT scenario to the client device so that the client device can associate the identification information of the IoT scenario with the IoT scenario.

26. The method according to any one of claims 15 to 25, characterized in that, The method further includes: Receiving an execution scenario instruction sent by the client device when the IoT scenario is triggered, where the execution scenario instruction contains the identification information of the IoT scenario.

27. The method according to any one of claims 15 to 26, characterized in that The device information of the IoT device includes one or more of the following: The identification information of the IoT device, the capability information of the IoT device.

28. A scene processing device, characterized in that, The apparatus includes: An information acquisition module, configured to acquire the device information of the IoT device proxied by the proxy device; A scenario creation module, configured to create an IoT scenario corresponding to the IoT device according to the device information.

29. The device according to claim 28, characterized in that, The scenario creation module is configured to, Create and save the scenario information of the IoT scenario in the client device; or, Send a set scenario instruction to the proxy device, where the set scenario instruction contains the scenario information of the IoT device, and the set scenario instruction is used to instruct the proxy device to save the scenario information of the IoT scenario.

30. The device according to claim 29, wherein The scenario information includes scenario content; the scenario content includes one or more of the following information: The identification information of the IoT device involved in the IoT scenario, the identification information of the proxy device, sequence information; The sequence information is used to indicate the order and / or priority of invoking the IoT device when the IoT scenario is triggered.

31. The device according to claim 30, characterized in that, When the scenario information is saved in the client device, the scenario information further includes trigger mode information, and the trigger mode information is used to indicate one or more of the following trigger modes: Triggered by time, triggered manually, triggered by the state of other devices.

32. The device according to claim 31, characterized in that, The scenario information further includes trigger time information; the trigger time information takes effect when the trigger mode information indicates a mode triggered by time.

33. The device according to claim 32, characterized in that, The trigger time information includes one or more of the following information: Loop information, used to indicate whether the IoT scenario loops; Period information, used to indicate the time period in a cycle when the IoT scenario is triggered; Start time information, used to indicate the start time of the IoT scenario.

34. The device according to claim 31, characterized in that, The scenario information further includes trigger status information; the trigger status information takes effect when the trigger mode information indicates a mode triggered by the state of other devices.

35. The device according to claim 34, characterized in that, The trigger status information includes one or more of the following information: The identification information of the proxy corresponding to the device that triggers the IoT scenario; The identification information of the device that triggers the IoT scenario; The attribute information of the device that triggers the IoT scenario.

36. The device according to claim 30, characterized in that, When the scenario information is saved in the proxy device, the scenario content further includes scenario priority information, and / or, sharing information; The scenario priority information is used to indicate the priority of the IoT scenario; The shared information is used to indicate whether sharing the IoT scenario with other devices is allowed.

37. The device according to claim 30 or 36, characterized in that, When the scenario information is saved in the proxy device, the identification information of the IoT scenario is generated by the client device; or, the identification information of the IoT scenario is generated by the proxy device.

38. The device according to claim 37, wherein, When the identification information of the IoT scenario is generated by the proxy device, the apparatus further includes: a receiving module, configured to receive the identification information of the IoT scenario sent by the proxy device; an association module, configured to associate the identification information of the IoT scenario with the IoT scenario.

39. The device according to any one of claims 29 to 38, characterized in that, The apparatus further includes: a first sending module, configured to sequentially send control commands corresponding to the IoT scenario to each IoT device involved in the IoT scenario when the IoT scenario is triggered.

40. The device according to any one of claims 28 to 39, characterized in that, The apparatus further includes: a first sending module, configured to send an execution scenario instruction to the proxy device when the IoT scenario is triggered, where the execution scenario instruction includes the identification information of the IoT scenario.

41. The device according to any one of claims 28 to 40, characterized in that, The device information of the IoT device includes one or more of the following: the identification information of the IoT device, the capability information of the IoT device.

42. A scene processing device, characterized in that, The apparatus includes: a sending module, configured to send the device information of the IoT device proxied by the proxy device to the client device, so that the client device creates an IoT scenario corresponding to the IoT device according to the device information.

43. The device according to claim 42, characterized in that, The scenario information of the IoT device is saved in the client device; or, the apparatus further includes: a first receiving module, configured to receive a set scenario instruction sent by the client device, where the set scenario instruction includes the scenario information of the IoT device; a saving module, configured to save the scenario information of the IoT scenario.

44. The device according to claim 43, characterized in that, The scenario information includes scenario content; the scenario content includes one or more of the following information: the identification information of the IoT device involved in the IoT scenario, the identification information of the proxy device, sequence information; The sequence information is used to indicate the order and / or priority of invoking the IoT device when the IoT scenario is triggered.

45. The device according to claim 44, characterized in that, When the scenario information is saved in the client device, the scenario information further includes trigger mode information, and the trigger mode information is used to indicate one or more of the following trigger modes: triggered by time, triggered manually, triggered by the status of other devices.

46. The device according to claim 45, characterized in that, The scenario information further includes trigger time information; the trigger time information takes effect when the trigger mode information indicates a mode triggered by time.

47. The apparatus according to claim 46, wherein The trigger time information includes one or more of the following information: cycle information, used to indicate whether the IoT scenario loops; period information, used to indicate the time period of the IoT scenario trigger in a cycle; start time information, used to indicate the start time of the IoT scenario.

48. The device according to claim 45, characterized in that, The scenario information further includes trigger status information; the trigger status information takes effect when the trigger mode information indicates a mode triggered by the status of other devices.

49. The device according to claim 48, characterized in that, The triggered status information includes one or more of the following information: The identification information of the agent corresponding to the device that triggers the Internet of Things scenario; The identification information of the device that triggers the Internet of Things scenario; The attribute information of the device that triggers the Internet of Things scenario.

50. The device according to claim 45, characterized in that, When the scenario information is stored in the proxy device, the scenario content further includes scenario priority information, and / or, sharing information; The scenario priority information is used to indicate the priority of the Internet of Things scenario; The sharing information is used to indicate whether to allow sharing the Internet of Things scenario with other devices.

51. The device according to claim 45 or 50, characterized in that, When the scenario information is stored in the proxy device, the identification information of the Internet of Things scenario is generated by the client device; or, the identification information of the Internet of Things scenario is generated by the proxy device.

52. The apparatus according to claim 51, wherein When the identification information of the Internet of Things scenario is generated by the proxy device, the sending module is further configured to send the identification information of the Internet of Things scenario to the client, so that the client device associates the identification information of the Internet of Things scenario with the Internet of Things scenario.

53. The device according to any one of claims 42 to 52, characterized in that, The device further includes: A second receiving module, configured to receive an execution scenario instruction sent by the client device when the Internet of Things scenario is triggered, where the execution scenario instruction includes the identification information of the Internet of Things scenario.

54. The device according to any one of claims 42 to 53, characterized in that, The device information of the Internet of Things device includes one or more of the following: The identification information of the Internet of Things device, the capability information of the Internet of Things device.

55. A computer device, characterized in that, The computer device includes a processor, a memory, and a transceiver; A computer program is stored in the memory, and the processor executes the computer program to enable the computer device to implement the scenario processing method as described in any one of claims 1 to 27 above.

56. A computer-readable storage medium, characterized in that, A computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the scenario processing method as described in any one of claims 1 to 27.

57. A chip, characterized in that, The chip includes a circuit structure, and the chip is used to run in a computer device to enable the computer device to execute the scenario processing method as described in any one of claims 1 to 27.

58. A computer program product, characterized in that, The computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions to enable the computer device to execute the scenario processing method as described in any one of claims 1 to 27.

59. A computer program, characterized in that, The computer program is executed by a processor of a computer device to implement the scenario processing method as described in any one of claims 1 to 27.

Images