Equipment control method and device, equipment, storage medium and program product

Abstract

The invention discloses an equipment control method and device, equipment, a storage medium and a program product, and belongs to the technical field of Internet of Things. The method is performed by a proxy device, comprising: sending controllable device information to a client device (201); the controllable equipment information comprises information of at least one piece of Internet of Things equipment connected with the proxy equipment; receiving a control instruction sent by the client device according to the controllable device information (202); the control instruction is used for controlling target equipment in the at least one piece of Internet of Things equipment; and sending the control instruction to the target device (203). According to the scheme, the control scene of the client device on the Internet of Things device is expanded, and the control efficiency of the Internet of Things device is improved.

Description

Device control method, apparatus, device, storage medium and program product Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a device control method, apparatus, device, storage medium, and program 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, IoT devices can typically be controlled by client devices. Specifically, a client device can access the IoT and establish a connection with the IoT device. Through the established connection, it can send control instructions to the IoT device to achieve control of the IoT device.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a device control method, apparatus, device, storage medium, and program product. The technical solution is as follows:

[0006] In one aspect, an embodiment of the present application provides a device control method, which is performed by a proxy device and includes:

[0007] Sending controllable device information to the client device; the controllable device information includes information of at least one IoT device connected to the proxy device;

[0008] receiving a control instruction sent by the client device according to the controllable device information; the control instruction is used to control a target device in the at least one IoT device;

[0009] The control instruction is sent to the target device.

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

[0011] Acquire controllable device information from the proxy device; the controllable device information includes information of at least one IoT device connected to the proxy device;

[0012] A control instruction is sent to the proxy device according to the controllable device information, so that the proxy device sends the control instruction to a target device in the at least one IoT device; the control instruction is used to control the target device.

[0013] On the other hand, an embodiment of the present application provides a device control apparatus, the apparatus comprising:

[0014] A sending module, configured to send controllable device information to a client device; the controllable device information includes information about at least one IoT device connected to the proxy device;

[0015] A receiving module, configured to receive a control instruction sent by the client device according to the controllable device information; the control instruction is used to control a target device in the at least one IoT device;

[0016] A sending module is used to send the control instruction to the target device.

[0017] On the other hand, an embodiment of the present application provides a device control apparatus, the apparatus comprising:

[0018] An acquisition module, configured to acquire controllable device information from a proxy device; the controllable device information includes information of at least one IoT device connected to the proxy device;

[0019] A sending module is used to send a control instruction to the proxy device according to the controllable device information, so that the proxy device sends the control instruction to the target device in the at least one Internet of Things device; the control instruction is used to control the target device.

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

[0021] The memory stores a computer program, and the processor executes the computer program to enable the computer device to implement the above-mentioned device control method.

[0022] 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 device control method.

[0023] 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 device control method.

[0024] On the other hand, the present application also provides a chip, which is used to run in a computer device so that the computer device executes the above-mentioned device control method.

[0025] 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 device control method.

[0026] 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 device control method.

[0027] Through the technical solution provided in the embodiments of the present application, the client device can send control instructions to the IoT device connected to the proxy device through the proxy device based on the controllable device information obtained from the proxy device, so as to control the IoT device connected to the proxy device through the proxy device, thereby expanding the control scenarios of the client device over the IoT device and improving the control efficiency of the IoT device. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

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

[0030] FIG2 is a flow chart of a device control method provided by an embodiment of the present application;

[0031] FIG3 is a flow chart of a device control method provided by an embodiment of the present application;

[0032] FIG4 is a flow chart of device control provided by one embodiment of the present application;

[0033] FIG5 is a flow chart of a device control method provided by an embodiment of the present application;

[0034] FIG6 is a schematic diagram of a device control process involved in the embodiment shown in FIG5 ;

[0035] FIG7 is a schematic diagram of another device control process involved in the embodiment shown in FIG5 ;

[0036] FIG8 is a block diagram of a device control apparatus provided by an embodiment of the present application;

[0037] FIG9 is a block diagram of a device control apparatus provided by one embodiment of the present application;

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

[0039] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0040] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0041] 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, and client devices 130; optionally, the network architecture may also include a bridge device 140; optionally, the network architecture may also include a cloud server 150.

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

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

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

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

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

[0047] In one possible implementation, the proxy device 120 is a user-side terminal device. For example, the proxy device 120 may be a smart controller, a smart remote control, a smartphone, a tablet computer, a smart watch, a smart TV, a smart speaker, or the like. Alternatively, the proxy device 120 may be a personal computer, such as a desktop computer, a laptop computer, or a personal workstation.

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

[0049] The client device 130 may be a device capable of communicating with the proxy device 120 . For example, the client device 130 may be an in-vehicle device (such as a vehicle computer device), a smart speaker, a smart TV, and the like.

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

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

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

[0053] The proxy device 120 may establish a connection with the IoT device 110 through the cloud server 150 .

[0054] Alternatively, the proxy device 120 may also directly establish a connection with the IoT device 110 .

[0055] 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).

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

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

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

[0059] Step 201: Send controllable device information to the client device; the controllable device information includes information of at least one IoT device connected to the proxy device.

[0060] In an embodiment of the present application, the controllable device information may include identification information, attribute status information, control method information, event information, etc. of at least one IoT device to which the proxy device is connected.

[0061] The at least one IoT device connected to the proxy device may be an IoT device in the IoT ecosystem to which the proxy device is connected. The proxy device may establish a connection with a cloud server in the IoT ecosystem to achieve an indirect connection with the IoT device; alternatively, the proxy device may directly connect to the IoT device in the IoT ecosystem.

[0062] That is, the connection between the proxy device and the IoT device may refer to an indirect connection established between the proxy device and the IoT device through the cloud server, or may refer to a direct connection between the proxy device and the IoT device.

[0063] In a possible implementation, a binding relationship may be pre-established between the client device and the proxy device for enabling the client device to control the IoT device using the proxy device as a proxy.

[0064] Step 202: Receive a control instruction sent by a client device according to the controllable device information; the control instruction is used to control a target device in at least one IoT device.

[0065] Step 203: Send the control instruction to the target device.

[0066] In one possible implementation, sending controllable device information to the client device includes:

[0067] Receive a controllable device request sent by a client device; the controllable device request is used to request information about IoT devices that the client device supports controlling;

[0068] Send controllable device information to the client device based on the controllable device request.

[0069] In a possible implementation, the controllable device request is used to obtain the controllable device information from the third cluster once; the third cluster is used to support the proxy capability of the proxy device;

[0070] Send controllable device information to the client device based on the controllable device request, including:

[0071] A device information acquisition response corresponding to the controllable device request is sent to the client device; the device information acquisition response includes controllable device information.

[0072] In a possible implementation, the controllable device information includes a device information list; the device information list includes information of endpoints in at least one IoT device that the client device supports controlling.

[0073] In one possible implementation, the method further includes: sending a device status notification message to the client device when a first subscription relationship already exists; the device status notification message includes status information of changes in the Internet of Things device corresponding to the controllable device information; wherein the first subscription relationship includes the client device's subscription relationship to the status information of the Internet of Things device corresponding to the controllable device information.

[0074] In a possible implementation, the first subscription relationship includes a subscription relationship of the client device to status information of the Internet of Things device corresponding to the controllable device information stored in the third cluster.

[0075] In a possible implementation, the first subscription relationship corresponds to at least one subscription target path;

[0076] The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

[0077] In one possible implementation, the method according to the embodiment of the present application further includes:

[0078] Query whether the third cluster contains controllable device information; the third cluster is used to support the proxy capability of the proxy device;

[0079] In a case where the third cluster includes controllable device information, the controllable device information is sent to the client device.

[0080] In one possible implementation, the method according to the embodiment of the present application further includes:

[0081] When the third cluster does not include the controllable device information, the controllable device information is obtained from the ecosystem where the IoT device to which the proxy device is connected resides.

[0082] To sum up, in the embodiments of the present application, the client device can send control instructions to the IoT device connected to the proxy device through the proxy device based on the controllable device information obtained from the proxy device, so as to control the IoT device connected to the proxy device through the proxy device, thereby expanding the control scenarios of the client device over the IoT device and improving the control efficiency of the IoT device.

[0083] Please refer to FIG3 , which shows a flow chart of a device control 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 client device 130 in the network architecture shown in FIG1 . The method may include the following steps:

[0084] Step 301: Acquire controllable device information from a proxy device; the controllable device information includes information of at least one IoT device connected to the proxy device.

[0085] Step 302: Send a control instruction to the proxy device according to the controllable device information, so that the proxy device sends the control instruction to a target device in at least one IoT device; the control instruction is used to control the target device.

[0086] In one possible implementation, obtaining controllable device information from a proxy device includes:

[0087] Sending a controllable device request to the proxy device; the controllable device request is used to request information about IoT devices that the client device supports controlling;

[0088] The controllable device information is received from the proxy device according to the controllable device request.

[0089] In a possible implementation, the controllable device request is used to obtain the controllable device information from the third cluster once; the third cluster is used to support the proxy capability of the proxy device;

[0090] The receiving agent sends controllable device information according to the controllable device's request, including:

[0091] A device information acquisition response corresponding to the controllable device request and sent by the proxy device is received; the device information acquisition response includes the controllable device information.

[0092] In a possible implementation, the controllable device information includes a device information list; the device information list includes information of endpoints in at least one IoT device that the client device supports controlling.

[0093] In a possible implementation, the method further includes:

[0094] In the case where a first subscription relationship already exists, receiving a device status notification message sent by the proxy device; the device status notification message includes status information of a change in the IoT device corresponding to the controllable device information;

[0095] The first subscription relationship includes a subscription relationship between the client device and the status information of the IoT device corresponding to the controllable device information.

[0096] In a possible implementation, the first subscription relationship includes a subscription relationship of the client device to status information of an IoT device corresponding to the controllable device information stored in a third cluster;

[0097] The third cluster is used to support the proxy capability of the proxy device.

[0098] In a possible implementation, the first subscription relationship corresponds to at least one subscription target path;

[0099] The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

[0100] In one possible implementation, the method according to the embodiment of the present application further includes:

[0101] Check whether a long-term binding relationship exists between the client device and the proxy device. The binding relationship is used by the client device to control the IoT device connected to the proxy device through the proxy device.

[0102] Obtain controllable device information from the proxy device, including:

[0103] When it is found that a binding relationship of a long-term binding type exists between the client device and the proxy device, the controllable device information is obtained from the proxy device.

[0104] In one possible implementation, querying whether a binding relationship of a long-term binding type exists between the client device and the proxy device includes:

[0105] Querying whether there is client binding information corresponding to the proxy device in the second cluster; the second cluster is used to support the client device to use other devices as proxies to control IoT devices connected to other devices;

[0106] When it is found that the client binding information corresponding to the proxy device exists in the second cluster, obtaining the binding type in the client binding information corresponding to the proxy device;

[0107] When the binding type in the client binding information corresponding to the proxy device is long-term binding, it is determined that a binding relationship of the long-term binding type exists between the client device and the proxy device.

[0108] In one possible implementation, the method according to the embodiment of the present application further includes:

[0109] In the case that it is found that no binding relationship with a binding type of long-term binding exists between the client device and the proxy device, a binding relationship with a binding type of long-term binding is established between the client device and the proxy device.

[0110] To sum up, in the embodiments of the present application, the proxy device can send controllable device information to the client device, so that the client device sends control instructions to the IoT device connected to the proxy device through the proxy device, so as to realize control of the IoT device connected to the proxy device through the proxy device, thereby expanding the control scenario of the client device over the IoT device and improving the control efficiency of the IoT device.

[0111] Through the solutions shown in Figures 2 and 3 of the present application, the client device can control the IoT device connected to the proxy device through the controllable device information provided by the proxy device.

[0112] Taking the proxy device as a smartphone, the client device as a vehicle-mounted device, and the smartphone connected to the IoT device via a cloud server as an example, please refer to FIG4 , which shows a process framework diagram of device control provided by an embodiment of the present application. In a possible application scenario, as shown in FIG4 , a smartphone 41 is connected to a cloud server 42 in an IoT ecosystem (for example, the IoT ecosystem can be a smart home system), and the smart home system includes one or more IoT devices (two shown in FIG4 ) including a home camera 43; at the same time, the smartphone 41 can establish a connection and binding relationship with the vehicle-mounted device 44.

[0113] When the user is in a vehicle and needs to turn on the home camera to shoot pictures, the vehicle-mounted device 44 can obtain the controllable device information of the smart home system from the smartphone 41, which includes the information of each IoT device (step S1), and display it through the screen of the vehicle system; the user executes the operation of controlling the home camera 43 to turn on according to the information displayed by the vehicle-mounted device 44, and the vehicle-mounted device 44 generates a control instruction for turning on the home camera 43, and sends the control instruction to the smartphone 41 (step S2); the smartphone 41 sends the control instruction to the home camera 43 through the cloud server 42 (step S3); thereafter, the home camera 43 can execute the control instruction to turn on and capture images.

[0114] Please refer to FIG5 , which shows a flow chart of a device control method provided by an embodiment of the present application. The method may be interactively executed by a proxy device and a client device. The proxy device and the client device may be the proxy device 120 and the client device 130 in the network architecture shown in FIG1 , respectively. The method may include the following steps:

[0115] Step 501: The client device sends a controllable device request to the proxy device; correspondingly, the proxy device receives the controllable device request.

[0116] The controllable device request is used to request information about IoT devices that the client device supports controlling.

[0117] In an embodiment of the present application, a binding relationship may be established between the client device and the proxy device, so that the client device uses the proxy device as a proxy to control the IoT device connected to the proxy device.

[0118] Optionally, when establishing a binding relationship between the client device and the proxy device, the proxy device may add first binding device information corresponding to the client device to the first cluster.

[0119] The first cluster may be a cluster that supports using a proxy device as a proxy to control an IoT device connected to the proxy device.

[0120] In a possible implementation, the first bound device information includes at least one of the following information:

[0121] Identification information of the client device;

[0122] Protocol version information of the client device;

[0123] A list of controllable devices of the client device; the list of controllable devices includes device information of IoT devices connected to the proxy device and supported by the client device;

[0124] Version information of the controllable device list.

[0125] In one possible implementation, the device information includes at least one of the following information:

[0126] Identification information of the IoT device corresponding to the device information;

[0127] The online status of the IoT device corresponding to the device information; the online status includes online or offline.

[0128] Taking the first cluster being an IOT Agent Binding Cluster as an example, the attributes included in the IOT Agent Binding Cluster may be as shown in Table 1 below.

[0129] Table 1

[0130] Identifier Name Type Description 0bindingIOTClientInfoList[bindingDeviceInfo] Binding information

[0131] Table 1 above shows that the IOT Agent Binding Cluster includes a binding IOT Client Info attribute, and the value of the attribute is a list including one or more binding device information (bindingDeviceInfo).

[0132] The structure of bindingDeviceInfo in Table 1 above may be as shown in Table 2 below.

[0133] Table 2

[0134]

[0135] The structure of onlineStatus in Table 2 above may be as shown in Table 3 below.

[0136] Table 3

[0137]

[0138]

[0139] The commands corresponding to the above IOT Agent Binding Cluster may be shown in Table 4 below.

[0140] Table 4

[0141] Identification Name Direction Response Necessity Description 0deregisterIOTClientC->SYM Unbind IOTClient

[0142] In an exemplary solution of an embodiment of the present application, the binding type of the above binding relationship can be divided into temporary binding and long-term binding.

[0143] Optionally, when the binding type of the binding relationship is long-term binding, the proxy device may add the first binding device information to the first cluster. When the binding type of the binding relationship is temporary binding, the proxy device may not add the first binding device information to the first cluster.

[0144] Alternatively, no matter whether the binding type of the binding relationship is temporary binding or long-term binding, the proxy device may add the first binding device information to the first cluster.

[0145] Optionally, when establishing a binding relationship between the client device and the proxy device, the client device may add the first client binding information corresponding to the proxy device to the second cluster. The second cluster is configured to enable the client device to use other devices as proxies to control IoT devices connected to the other devices.

[0146] In an embodiment of the present application, a cluster may be set in the client device to support control of other IoT devices through a proxy device.

[0147] In an exemplary solution of an embodiment of the present application, the second cluster may be referred to as an Internet of Things client cluster (IOT Client Cluster).

[0148] In a possible implementation, the second cluster may include at least one of the following information:

[0149] Manufacturer information of the client device;

[0150] Device control capability information;

[0151] and a client binding information list; the client binding information list includes client binding information of established binding relationships.

[0152] In one possible implementation, the device control capability information includes at least one of the following information:

[0153] The device types of IoT devices that the client device supports controlling;

[0154] As well as the control capabilities of IoT devices supported by client devices.

[0155] In one possible implementation, when the device control capability information includes the device type of the IoT device that the client device supports controlling, the device control capability information includes at least one of the following information:

[0156] First support information: The first support information is used to indicate whether the client device supports controlling all types of IoT devices;

[0157] And, a device type list; the device type list includes type identification information of device types of IoT devices that the client device supports controlling.

[0158] In one possible implementation, the first client binding information may include at least one of the following information:

[0159] Identification information of the proxy device;

[0160] Binding type information; the binding type is used to indicate the binding type of the binding relationship between the proxy device and the client device; the binding type includes temporary binding or long-term binding;

[0161] And, access type information; the access type information is used to indicate the access type of the client device to the IoT device connected to the proxy device; the access type includes bridge access or proxy access.

[0162] In an exemplary solution, taking the second cluster being an IOT Client Cluster as an example, the definition of the IOT Client Cluster may be as shown in Table 5 below.

[0163] Table 5

[0164] Identification name type description 0VendorIDstring manufacturer identification 1SupportedDeviceTypesdeviceTypeList possible device list supported 2bindingSourceList[clientBindingInfo] binding information

[0165] The structure (struct) of deviceTypeList in Table 5 above may be as shown in Table 6 below.

[0166] Table 6

[0167]

[0168] The structure of clientBindingInfo may be as shown in Table 7 below.

[0169] Table 7

[0170]

[0171] Optionally, when the value of BindingType in Table 7 above is 0, it indicates that the binding relationship is a temporary binding. After the client device completes controlling the IoT device connected to the device corresponding to the IOT proxy ID, the client device may not save the list of controllable devices and other information (i.e., the above-mentioned controllable device information) sent by the device corresponding to the IOT proxy ID. Conversely, when the value of BindingType above is 1, it indicates that the binding relationship is a long-term binding. After the client device completes controlling the IoT device connected to the device corresponding to the IOT proxy ID, the client device may save the list of controllable devices and other information sent by the device corresponding to the IOT proxy ID for use next time when controlling the IoT device connected to the device corresponding to the IOT proxy ID.

[0172] In one possible implementation, under both temporary binding and long-term binding, the client device can obtain controllable device information from the proxy device and control the IoT device connected to the proxy device based on the controllable device information.

[0173] In another possible implementation, the client device may query whether a binding relationship of long-term binding type exists between the client device and the proxy device; if it is found that a binding relationship of long-term binding type exists between the client device and the proxy device, the client device may obtain controllable device information from the proxy device, such as sending a controllable device request to the proxy device.

[0174] In another exemplary solution of the embodiment of the present application, the client device may obtain the controllable device information from the proxy device only when a long-term binding relationship exists between the client device and the proxy device.

[0175] In a possible implementation, the step of querying whether a binding relationship of a long-term binding type exists between the client device and the proxy device may include:

[0176] The client device queries whether there is client binding information corresponding to the proxy device in the second cluster; if the client binding information corresponding to the proxy device is found in the second cluster, the binding type in the client binding information corresponding to the proxy device is obtained; if the binding type in the client binding information corresponding to the proxy device is long-term binding, it is determined that there is a binding relationship with the binding type of long-term binding between the client device and the proxy device.

[0177] For example, in an exemplary solution, the client device may query the client binding information list of the second cluster to see whether there is first client binding information containing identification information of the proxy device. If so, the value of BindingType in the first client binding information is further read. If the value of BindingType is 1, it indicates that a binding relationship with a binding type of long-term binding exists between the client device and the proxy device. If the value of BindingType is 0, it indicates that no binding relationship with a binding type of long-term binding exists between the client device and the proxy device.

[0178] In a possible implementation, when it is found that no binding relationship of long-term binding type exists between the client device and the proxy device, a binding relationship of long-term binding type may be established between the client device and the proxy device.

[0179] In an embodiment of the present application, when it is found that there is no binding relationship with a binding type of long-term binding between the client device and the proxy device, the client device can display a prompt message for establishing a long-term binding to prompt the user to initiate the establishment of a long-term binding between the client device and the proxy device on the proxy device side.

[0180] Alternatively, if a query finds that no binding relationship with a long-term binding type exists between the client device and the proxy device, the client device may send a binding trigger message to the proxy device to trigger the proxy device to initiate the establishment of a long-term binding between the client device and the proxy device. For example, the client device may display a prompt message for establishing a long-term binding, and when the user performs an operation on the client device to establish a long-term binding, the client device may send a binding trigger message to the proxy device.

[0181] Step 502: The proxy device sends controllable device information to the client device according to the controllable device request. Correspondingly, the client device receives the controllable device information sent by the proxy device according to the controllable device request.

[0182] The controllable device information includes information about at least one IoT device to which the proxy device is connected and which the client device supports controlling.

[0183] In an embodiment of the present application, after receiving the above-mentioned controllable device request, the proxy device can send information about at least one IoT device to which the proxy device is connected and which the client device supports controlling to the client device so that the client device can display it to the user.

[0184] In one possible implementation, when the controllable device request is used to obtain controllable device information from the third cluster once, the proxy device may send a device information acquisition response corresponding to the controllable device request to the client device; the device information acquisition response includes the controllable device information; accordingly, the client device receives the device information acquisition response corresponding to the controllable device request sent by the proxy device.

[0185] In the embodiment of the present application, when the client device sends a request for obtaining controllable device information from the third cluster once to the proxy device, the proxy device may carry the controllable device information in a response message to the request.

[0186] The third cluster is used to support the proxy capability of the proxy device.

[0187] For example, in the embodiment of the present application, the third cluster may be referred to as an IOT Agent cluster. For example, the definition of the attributes of the IOT Agent cluster may be as shown in Table 8 below.

[0188] Table 8

[0189] Identification Name Type Description 0DeviceListList[IOTDevice_Info] Controllable device list

[0190] In a possible implementation, the controllable device information includes a device information list; the device information list includes information of endpoints in at least one IoT device that the client device supports controlling.

[0191] In an embodiment of the present application, a device model of an IoT device may include one or more endpoints, and each endpoint may correspond to one or more functional services.

[0192] The information of each endpoint may include information of a service cluster in the endpoint, and the information of the service cluster may include information such as properties, methods, and events corresponding to a service.

[0193] In a possible implementation, the solution shown in the embodiment of the present application further includes:

[0194] If a first subscription relationship already exists, the proxy device sends a device status notification message to the client device. The device status notification message includes status information about changes in the IoT device corresponding to the controllable device information. The first subscription relationship includes the client device's subscription to the status information of the IoT device corresponding to the controllable device information. Accordingly, if the first subscription relationship already exists, the client device receives the device status notification message sent by the proxy device.

[0195] In a possible implementation, the first subscription relationship includes a subscription relationship of the client device to status information of the Internet of Things device corresponding to the controllable device information stored in the third cluster.

[0196] In one embodiment, a client device sends a device status subscription request to a proxy device to subscribe to status information of an IoT device corresponding to controllable device information in a third cluster. Upon receiving the device status subscription request, the proxy device may establish a first subscription relationship and subsequently send a device status notification message corresponding to the first subscription relationship to the client device. The device status notification message includes status information about changes in the IoT device corresponding to the controllable device information. Accordingly, the client device receives the device status notification message corresponding to the first subscription relationship sent by the proxy device.

[0197] In an embodiment of the present application, when a client device sends a device status subscription request to a proxy device, triggering the proxy device to establish a first subscription relationship, the proxy device may send a device status notification message to the client device when the device status subsequently changes. The device status notification message carries status information of the changed service cluster of the IoT device corresponding to the above-mentioned controllable device information, which may specifically be the attribute status of the changed service cluster; or, the above-mentioned device status notification message may also include information about endpoints in newly added IoT devices in the IoT ecosystem; or, the above-mentioned device status notification message may also include identifiers of endpoints in IoT devices removed from the IoT ecosystem.

[0198] In a possible implementation, the first subscription relationship corresponds to at least one subscription target path. For example, a device status subscription request may include at least one subscription target path to request the proxy device to establish the first subscription relationship.

[0199] The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

[0200] In an exemplary solution, the message (command) corresponding to the third cluster may be as shown in Table 9 below.

[0201] Table 9

[0202]

[0203] In Table 9 above, getDeviceListReq corresponds to the controllable device request above. getDeviceListReq may have no parameters. The parameters included in getDeviceListResq may be as shown in Table 10 below.

[0204] Table 10

[0205] Identification Name Type Description 0DeviceListList[device_Info] Controllable device list

[0206] Among them, the above-mentioned controllable device information can be DeviceList in Table 10, wherein List[device_Info] can be composed of information of at least one IoT device, and each device_Info corresponds to the information of an IoT device in the controllable device information.

[0207] The structure (struct) of device_Info in the above Table 10 can be as shown in the following Table 11.

[0208] Table 11

[0209]

[0210] The structure of the endpoint information (endpoint_Info) in Table 11 above may be as shown in Table 12 below.

[0211] Table 12

[0212]

[0213] The structure of the cluster information (cluster_Info) in Table 12 above can be as shown in Table 13 below.

[0214] Table 13

[0215] Identifier Name Type Description 0clusterIDUint16 Device type (cluster identifier) ​​1attributeList[attribute_Info] Attribute set: device status 2commandList[command_Info] Method set: start device behavior 3eventList[event_Info] Event set: reported events

[0216] The structure of the attribute information (attribute_Info) in Table 13 above can be as shown in Table 14 below.

[0217] Table 14

[0218] Identifier Name Type Description 0attributeIDUint16 Attribute Identifier 1Value Current attribute status

[0219] The structure of the method information (command_Info) in Table 13 above may be as shown in Table 15 below.

[0220] Table 15

[0221] Identifier Name Type Description 0commandIDUint16 Command Identifier

[0222] In an embodiment of the present application, each service cluster may include properties, events, and methods, where the methods may correspond to specific functions of the device, such as turning on, off, brightness adjustment, temperature adjustment, and the like.

[0223] The structure of the event information (event_Info) in Table 13 above can be as shown in Table 16 below.

[0224] Table 16

[0225] Identifier Name Type Description 0 eventID Uint16 event identifier

[0226] In an embodiment of the present application, the above-mentioned event can be an event reported by an IoT device to other devices. For example, the above-mentioned event can be an event reported by a smart home device to an agent device (such as an APP), such as door lock_door not closed.

[0227] The parameters of subscribeDevSta in Table 9 above may be as shown in Table 17 below.

[0228] Table 17

[0229]

[0230] In Table 17, Path can be the target path of the subscription, for example: node id / endpoint id / cluster id / [attributes id|event id].

[0231] The parameters of subscribeResp in Table 9 above may be as shown in Table 18 below.

[0232] Table 18

[0233]

[0234] The parameters of devStaNotify in the above Table 9 can be as shown in the following Table 19.

[0235] Table 19

[0236] Identifier Name Type Description 0subscirbeID 1targetPathList[path]Changed element 2NewvalueList[value]1State corresponding to the element

[0237] In an embodiment of the present application, the definition of an event may be as shown in Table 20 below.

[0238] Table 20

[0239] Identification name type 0online online 1offline offline 2deviceFault device fault 3alert alarm information 4deviceListChanged controllable device list change

[0240] In a possible implementation, the proxy device may query whether the third cluster includes the controllable device information; if the third cluster includes the controllable device information, the proxy device sends the controllable device information to the client device.

[0241] In a possible implementation, when the third cluster does not include the controllable device information, the controllable device information is obtained from the ecosystem where the Internet of Things device to which the proxy device is connected resides.

[0242] In an embodiment of the present application, after the proxy device receives a controllable device request, it can first check whether the controllable device information required by the client device (i.e., the information of the Internet of Things device to which the proxy device is connected and that the client device supports controlling) is stored locally. If the controllable device information required by the client device exists locally, the controllable device information is directly sent to the client device; if the controllable device information required by the client device does not exist locally, or the locally stored controllable device information is incomplete, the proxy device can obtain the controllable device information from the ecosystem where the Internet of Things device to which the proxy device is connected is located; for example, the proxy device can query the cloud server in the ecosystem where the Internet of Things device to which the proxy device is connected is located for the above-mentioned controllable device information; or, the proxy device can directly query the Internet of Things device for the above-mentioned controllable device information.

[0243] Step 503: The client device sends a control instruction to the proxy device according to the controllable device information. Correspondingly, the proxy device receives the control instruction.

[0244] The control instruction is used to control a target device in at least one IoT device.

[0245] In an embodiment of the present application, after receiving the controllable device information, the client device can display the controllable device information to the user, allowing the user to select a target device from at least one IoT device connected to the proxy device to control it. Upon detecting the user's control operation on the target device based on the controllable device information, the client device generates a corresponding control instruction and sends the control instruction to the proxy device.

[0246] Step 504: The proxy device sends the control instruction to a target device in at least one IoT device.

[0247] After receiving the control instruction, the proxy device may forward the control instruction to the target device, so as to implement a process of controlling the target device on the client device side through the proxy device acting as a proxy.

[0248] In the embodiment of the present application, the proxy device may execute the forwarding process of the control instruction based on the access type corresponding to the binding relationship between the proxy device and the client device.

[0249] For example, when the access type is bridge, the proxy device may forward the control instruction to the target device in a bridging manner; when the access type is proxy, the proxy device may forward the control instruction to the target device in a relay manner.

[0250] Please refer to Figure 6, which shows a schematic diagram of a device control process involved in an embodiment of the present application. Taking the device control process for a smart home scenario, the client device is an IOT Client, and the proxy device is an IOT Agent as an example, the binding relationship between the IOT Client and the IOT Agent has been established, as shown in Figure 6, the device control process is as follows:

[0251] S601: The IOT Client discovers that the IOT Agent has proxy capabilities.

[0252] S602: The IOT Client obtains controllable device information from the IOT Agent, that is, sends a controllable device request (such as getDeviceListReq) to the IOT Agent.

[0253] S603: The IOT Agent generates controllable device information (such as the controllable device list shown in Table 9 above).

[0254] If the IoT Agent does not save the content, it can obtain it from the IoT ecosystem.

[0255] S604, the IOT Agent sends controllable device information to the IOT Client. For example, the IOT Agent sends a controllable device list to the IOT Client through getDeviceListResp.

[0256] S605, the IOT Client displays the controllable device information.

[0257] S606: The user performs an operation to control the IoT ecological device, and the IoT Client sends a device control instruction to the IoT Agent.

[0258] The device control instructions may be as follows:

[0259] Source:IOT Client;

[0260] Destination:IOT Agen;

[0261] path:targetNodeID / [targetOperationObject].

[0262] The NodeID is the device identifier; the targetOperationObject is the path and identifier of the resource under the device.

[0263] Messages exchanged between client devices and agent devices must go through an "access control process," meaning that specific devices can access specific functions. In this embodiment of the present application, the access permissions from the IoT client to the IoT agent can be set to "accessible to any device," meaning that any IoT client can access a specific IoT agent. The IoT agent can store a list of controllable devices sent to the IoT client. The IoT client can access the devices on the controllable device list.

[0264] S607, after receiving the above message, the IOT Agent performs message conversion, obtains the following message and sends it to the IOT ecological device.

[0265] Source:IOT Agent;

[0266] Destination:targetNodeID;

[0267] path:targetNodeID / [targetOperationObject].

[0268] In the above step 607, when the access type of the binding relationship between the IOT Client and the IOT Agent is Bridge, the IOT Agent converts the message into Source:IOT Agent, Destination:targetNodeID; path:targetNodeID / [targetOperationObject]. Protocol conversion is also required, that is, the message corresponding to the protocol between the IOT Client and the IOT Agent is converted into the message corresponding to the protocol between the IOT Agent and the IOT ecosystem.

[0269] Please refer to Figure 7, which shows a schematic diagram of another device control process involved in an embodiment of the present application. Taking the device control process for a smart home scenario, the client device is an IOT Client, the proxy device is an IOT Agent as an example, the IOT Client and the IOT Agent have completed the establishment of a binding relationship, and the IOT Client performs device control under the condition of a long-term binding relationship with the IOT Agent, as shown in the figure, the device control process is as follows:

[0270] S701, the user starts the smart home function.

[0271] S702: The IOT Client establishes a secure connection with the IOT Agent.

[0272] S703, the IOT Client queries whether there is a long-term binding relationship with the currently connected IOT Agent device.

[0273] Among them, the IOT Client can query whether there is a long-term binding relationship with the currently connected IOT Agent device through the IOT Client cluster.

[0274] S704: If there is no long-term binding relationship, a binding process is performed to establish a long-term binding relationship between the IOT Client and the IOT Agent.

[0275] S705: If a long-term binding relationship exists, obtain controllable device information (such as the controllable device list shown in Table 9 above) from the IOT Agent.

[0276] S706: The IOT Client loads the controllable device information.

[0277] S707, the IOT Client controls the IOT ecological device through the IOT Agent according to the user's operation.

[0278] The execution process of the above steps S705 to S707 may refer to the solution shown in FIG6 , which will not be described in detail here.

[0279] To sum up, in the embodiments of the present application, the client device can send control instructions to the IoT device connected to the proxy device through the proxy device based on the controllable device information obtained from the proxy device, so as to control the IoT device connected to the proxy device through the proxy device, thereby expanding the control scenarios of the client device over the IoT device and improving the control efficiency of the IoT device.

[0280] Please refer to Figure 8, which shows a block diagram of a device control apparatus provided by an embodiment of the present application. The device control apparatus 800 has the function of implementing the method shown in Figure 2 or Figure 5 above, which is performed by the proxy device. As shown in Figure 8, the apparatus may include:

[0281] The sending module 801 is configured to send controllable device information to the client device; the controllable device information includes information about at least one IoT device connected to the proxy device;

[0282] A receiving module 802 is configured to receive a control instruction sent by the client device according to the controllable device information; the control instruction is used to control a target device in the at least one IoT device;

[0283] The sending module 801 is further configured to send the control instruction to the target device.

[0284] In a possible implementation, the sending module 801 is configured to:

[0285] Receive a controllable device request sent by the client device; the controllable device request is used to request information about the Internet of Things devices that the client device supports controlling;

[0286] According to the controllable device request, the controllable device information is sent to the client device.

[0287] In a possible implementation, the controllable device request is used to obtain the controllable device information from a third cluster once; the third cluster is used to support the proxy capability of the proxy device;

[0288] The sending module 801 is configured to send a device information acquisition response corresponding to the controllable device request to the client device; the device information acquisition response includes the controllable device information.

[0289] In a possible implementation, the controllable device information includes a device information list; the device information list includes information of endpoints in the at least one IoT device that the client device supports controlling.

[0290] In one possible implementation, the sending module 801 is further configured to send a device status notification message to the client device when a first subscription relationship already exists; the device status notification message includes status information of changes in the IoT device corresponding to the controllable device information;

[0291] The first subscription relationship includes a subscription relationship between the client device and the status information of the IoT device corresponding to the controllable device information.

[0292] In a possible implementation, the first subscription relationship includes a subscription relationship of the client device to status information of an IoT device corresponding to the controllable device information stored in a third cluster;

[0293] The third cluster is used to support the proxy capability of the proxy device.

[0294] In a possible implementation, the first subscription relationship corresponds to at least one subscription target path;

[0295] The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

[0296] In a possible implementation, the apparatus further includes:

[0297] A query module, configured to query whether the third cluster contains the controllable device information; the third cluster is configured to support the proxy capability of the proxy device;

[0298] The sending module 801 is configured to send the controllable device information to the client device when the third cluster includes the controllable device information.

[0299] In a possible implementation, the apparatus further includes:

[0300] An acquisition module is configured to acquire the controllable device information from the ecosystem where the Internet of Things device connected to the proxy device is located when the third cluster does not include the controllable device information.

[0301] Please refer to Figure 9, which shows a block diagram of a device control apparatus provided by an embodiment of the present application. The device control apparatus 900 has the functions of implementing the methods shown in Figures 3 or 5 above, which are performed by the client device. As shown in Figure 9, the apparatus may include:

[0302] An acquisition module 901 is configured to acquire controllable device information from a proxy device; the controllable device information includes information about at least one IoT device connected to the proxy device;

[0303] The sending module 902 is used to send a control instruction to the proxy device according to the controllable device information, so that the proxy device sends the control instruction to the target device in the at least one IoT device; the control instruction is used to control the target device.

[0304] In a possible implementation, the acquisition module 901 is configured to:

[0305] Sending a controllable device request to the proxy device; the controllable device request is used to request information about the IoT devices that the client device supports controlling;

[0306] The controllable device information is received, which is sent by the proxy device according to a request from the controllable device.

[0307] In a possible implementation, the controllable device request is used to obtain the controllable device information from a third cluster once; the third cluster is used to support the proxy capability of the proxy device;

[0308] The acquisition module 901 is configured to receive a device information acquisition response sent by the proxy device, corresponding to the controllable device request; the device information acquisition response includes the controllable device information.

[0309] In a possible implementation, the controllable device information includes a device information list; the device information list includes information of endpoints in the at least one IoT device that the client device supports controlling.

[0310] In a possible implementation, the apparatus further includes:

[0311] A receiving module, configured to receive a device status notification message sent by the proxy device when a first subscription relationship already exists; the device status notification message includes status information of a change in the IoT device corresponding to the controllable device information;

[0312] The first subscription relationship includes a subscription relationship between the client device and the status information of the IoT device corresponding to the controllable device information.

[0313] In a possible implementation, the first subscription relationship includes a subscription relationship of the client device to status information of an IoT device corresponding to the controllable device information stored in a third cluster;

[0314] The third cluster is used to support the proxy capability of the proxy device.

[0315] In a possible implementation, the first subscription relationship corresponds to at least one subscription target path;

[0316] The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

[0317] In a possible implementation, the apparatus further includes:

[0318] A query module, configured to query whether a binding relationship of a long-term binding type exists between the client device and the proxy device; the binding relationship is used for the client device to control the IoT device connected to the proxy device through the proxy device;

[0319] The acquisition module 901 is configured to acquire the controllable device information from the proxy device when it is found that a binding relationship of a long-term binding type exists between the client device and the proxy device.

[0320] In a possible implementation, the query module is used to:

[0321] querying whether there is client binding information corresponding to the proxy device in the second cluster; the second cluster is used to support the client device to use other devices as proxies to control the IoT devices connected to the other devices;

[0322] When it is found that the client binding information corresponding to the proxy device exists in the second cluster, obtaining the binding type in the client binding information corresponding to the proxy device;

[0323] In a case where the binding type in the client binding information corresponding to the proxy device is long-term binding, it is determined that a binding relationship of the long-term binding type exists between the client device and the proxy device.

[0324] In a possible implementation, the apparatus further includes:

[0325] The establishing module is configured to establish a binding relationship of long-term binding type between the client device and the proxy device when it is found that no binding relationship of long-term binding type exists between the client device and the proxy device.

[0326] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0327] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0328] Please refer to FIG10 , which shows a schematic diagram of the structure of a computer device 1000 provided in one embodiment of the present application. The computer device 1000 may include: a processor 1001 , a receiver 1002 , a transmitter 1003 , a memory 1004 , and a bus 1005 .

[0329] The processor 1001 includes one or more processing cores. The processor 1001 executes various functional applications and information processing by running software programs and modules.

[0330] The receiver 1002 and the transmitter 1003 may be implemented as a communication component, which may be a communication chip, which may also be called a transceiver.

[0331] The memory 1004 is connected to the processor 1001 via a bus 1005 .

[0332] The memory 1004 may be used to store a computer program, and the processor 1001 may be used to execute the computer program to implement each step in the above method embodiment.

[0333] In addition, the memory 1004 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 random access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0334] In an exemplary scenario, when the computer device 1000 is implemented as the above-mentioned proxy device, the transceiver is used to send controllable device information to the client device; the controllable device information includes information of at least one Internet of Things device connected to the proxy device; receive control instructions sent by the client device according to the controllable device information; the control instructions are used to control a target device among the at least one Internet of Things device; and send the control instructions to the target device.

[0335] The process executed by the processor 1001 and / or the transceiver in the computer device 1000 may refer to the steps executed by the proxy device in the method shown in either FIG. 2 or FIG. 5 .

[0336] In an exemplary scenario, when the computer device 1000 is implemented as a client device, the transceiver is used to obtain controllable device information from a proxy device; the controllable device information includes information of at least one IoT device connected to the proxy device; a control instruction is sent to the proxy device based on the controllable device information, so that the proxy device sends the control instruction to a target device among the at least one IoT device; and the control instruction is used to control the target device.

[0337] The process executed by the processor 1001 and / or the transceiver in the computer device 1000 may refer to the steps executed by the client device in the method shown in either FIG. 3 or FIG. 5 .

[0338] 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 2, Figure 3 or Figure 5 above.

[0339] The present application also provides a chip, which 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 the client device in the method shown in Figure 2, Figure 3 or Figure 5 above.

[0340] 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 2, 3, or 5 above.

[0341] 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 2, Figure 3 or Figure 5 above.

[0342] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0343] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A device control method, characterized in that: The method is performed by an agent device, and includes: Sending controllable device information to the client device; the controllable device information includes information of at least one IoT device connected to the proxy device; receiving a control instruction sent by the client device according to the controllable device information; the control instruction is used to control a target device in the at least one IoT device; The control instruction is sent to the target device.

2. The method according to claim 1, characterized in that The sending of controllable device information to the client device includes: Receive a controllable device request sent by the client device; the controllable device request is used to request information about the Internet of Things devices that the client device supports controlling; According to the controllable device request, the controllable device information is sent to the client device.

3. The method according to claim 2, characterized in that The controllable device request is used to obtain the controllable device information from the third cluster once; the third cluster is used to support the proxy capability of the proxy device; The sending the controllable device information to the client device according to the controllable device request includes: Sending a device information acquisition response corresponding to the controllable device request to the client device; The device information acquisition response includes the controllable device information.

4. The method according to claim 3, characterized in that The controllable device information includes a device information list; the device information list includes information of endpoints in the at least one IoT device that the client device supports controlling.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: In the case where a first subscription relationship already exists, sending a device status notification message to the client device; the device status notification message includes status information of changes in the Internet of Things device corresponding to the controllable device information; The first subscription relationship includes a subscription relationship between the client device and the status information of the IoT device corresponding to the controllable device information.

6. The method according to claim 5, characterized in that The first subscription relationship includes a subscription relationship between the client device and the status information of the Internet of Things device corresponding to the controllable device information stored in the third cluster; The third cluster is used to support the proxy capability of the proxy device.

7. The method according to claim 5 or 6, characterized in that The first subscription relationship corresponds to at least one subscription target path; The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: querying whether the third cluster contains the controllable device information; the third cluster is used to support the agent capability of the agent device; The sending of controllable device information to the client device includes: In a case where the third cluster includes the controllable device information, the controllable device information is sent to the client device.

9. The method according to claim 8, characterized in that The method further comprises: In a case where the third cluster does not include the controllable device information, the controllable device information is obtained from the ecosystem where the Internet of Things device connected to the proxy device is located.

10. A device control method, characterized in that: The method is performed by a client device, and includes: Acquire controllable device information from the proxy device; the controllable device information includes information of at least one IoT device connected to the proxy device; A control instruction is sent to the proxy device according to the controllable device information, so that the proxy device sends the control instruction to a target device in the at least one IoT device; the control instruction is used to control the target device.

11. The method according to claim 10, characterized in that The obtaining of controllable device information from the proxy device includes: Sending a controllable device request to the proxy device; the controllable device request is used to request information about the IoT devices that the client device supports controlling; The controllable device information is received, which is sent by the proxy device according to a request from the controllable device.

12. The method according to claim 11, characterized in that The controllable device request is used to obtain the controllable device information from the third cluster once; the third cluster is used to support the proxy capability of the proxy device; The receiving the controllable device information sent by the proxy device according to the request of the controllable device includes: receiving a device information acquisition response sent by the proxy device corresponding to the controllable device request; The device information acquisition response includes the controllable device information.

13. The method according to claim 12, characterized in that The controllable device information includes a device information list; the device information list includes information of endpoints in the at least one IoT device that the client device supports controlling.

14. The method according to any one of claims 10 to 13, characterized in that: The method further comprises: In the case where a first subscription relationship already exists, receiving a device status notification message sent by the proxy device; the device status notification message includes status information of a change in the IoT device corresponding to the controllable device information; The first subscription relationship includes a subscription relationship between the client device and the status information of the IoT device corresponding to the controllable device information.

15. The method according to claim 14, characterized in that The first subscription relationship includes a subscription relationship between the client device and the status information of the Internet of Things device corresponding to the controllable device information stored in the third cluster; The third cluster is used to support the proxy capability of the proxy device.

16. The method according to claim 14 or 15, characterized in that The first subscription relationship corresponds to at least one subscription target path; The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

17. The method according to any one of claims 10 to 16, characterized in that: The method further comprises: Querying whether a binding relationship of a long-term binding type exists between the client device and the proxy device; the binding relationship is used for the client device to control the IoT device connected to the proxy device through the proxy device; The obtaining of controllable device information from the proxy device includes: In a case where it is found that a binding relationship of a long-term binding type exists between the client device and the proxy device, the controllable device information is obtained from the proxy device.

18. The method according to claim 17, characterized in that The querying whether a binding relationship of a long-term binding type exists between the client device and the proxy device includes: querying whether there is client binding information corresponding to the proxy device in the second cluster; the second cluster is used to support the client device to use other devices as proxies to control the IoT devices connected to the other devices; When it is found that the client binding information corresponding to the proxy device exists in the second cluster, obtaining the binding type in the client binding information corresponding to the proxy device; In a case where the binding type in the client binding information corresponding to the proxy device is long-term binding, it is determined that a binding relationship of the long-term binding type exists between the client device and the proxy device.

19. The method according to claim 17 or 18, characterized in that The method further comprises: In the case that it is found that no binding relationship of long-term binding type exists between the client device and the proxy device, a binding relationship of long-term binding type is established between the client device and the proxy device.

20. A device control device, characterized in that: The device comprises: A sending module, configured to send controllable device information to a client device; the controllable device information includes information about at least one IoT device connected to the proxy device; A receiving module, configured to receive a control instruction sent by the client device according to the controllable device information; the control instruction is used to control a target device in the at least one IoT device; The sending module is further configured to send the control instruction to the target device.

21. The device according to claim 20, characterized in that The sending module is used to: Receive a controllable device request sent by the client device; the controllable device request is used to request information about the Internet of Things devices that the client device supports controlling; According to the controllable device request, the controllable device information is sent to the client device.

22. The device according to claim 21, characterized in that The controllable device request is used to obtain the controllable device information from the third cluster once; the third cluster is used to support the proxy capability of the proxy device; The sending module is configured to send a device information acquisition response corresponding to the controllable device request to the client device; the device information acquisition response includes the controllable device information.

23. The device according to claim 22, characterized in that The controllable device information includes a device information list; the device information list includes information of endpoints in the at least one IoT device that the client device supports controlling.

24. The device according to any one of claims 20 to 23, characterized in that The sending module is further configured to send a device status notification message to the client device when a first subscription relationship already exists; the device status notification message includes status information of changes in the IoT device corresponding to the controllable device information; The first subscription relationship includes a subscription relationship between the client device and the status information of the IoT device corresponding to the controllable device information.

25. The device according to claim 24, characterized in that The first subscription relationship includes a subscription relationship between the client device and the status information of the Internet of Things device corresponding to the controllable device information stored in the third cluster; The third cluster is used to support the proxy capability of the proxy device.

26. The device according to claim 24 or 25, characterized in that The first subscription relationship corresponds to at least one subscription target path; The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

27. The device according to any one of claims 20 to 26, characterized in that The device further comprises: A query module, configured to query whether the third cluster contains the controllable device information; the third cluster is configured to support the proxy capability of the proxy device; The sending module is configured to send the controllable device information to the client device when the third cluster includes the controllable device information.

28. The device according to claim 27, characterized in that The device further comprises: An acquisition module is configured to acquire the controllable device information from the ecosystem where the Internet of Things device connected to the proxy device is located when the third cluster does not include the controllable device information.

29. A device control device, characterized in that: The device comprises: An acquisition module, configured to acquire controllable device information from a proxy device; the controllable device information includes information of at least one IoT device connected to the proxy device; A sending module is used to send a control instruction to the proxy device according to the controllable device information, so that the proxy device sends the control instruction to the target device in the at least one Internet of Things device; the control instruction is used to control the target device.

30. The device according to claim 29, characterized in that The acquisition module is used to: Sending a controllable device request to the proxy device; the controllable device request is used to request information about the IoT devices that the client device supports controlling; The controllable device information is received, which is sent by the proxy device according to a request from the controllable device.

31. The device according to claim 30, characterized in that The controllable device request is used to obtain the controllable device information from the third cluster once; the third cluster is used to support the proxy capability of the proxy device; The acquisition module is configured to receive a device information acquisition response sent by the proxy device and corresponding to the controllable device request; the device information acquisition response includes the controllable device information.

32. The device according to claim 31, characterized in that The controllable device information includes a device information list; the device information list includes information of endpoints in the at least one IoT device that the client device supports controlling.

33. The device according to any one of claims 29 to 32, characterized in that The device further comprises: A receiving module, configured to receive a device status notification message sent by the proxy device when a first subscription relationship already exists; the device status notification message includes status information of a change in the IoT device corresponding to the controllable device information; The first subscription relationship includes a subscription relationship between the client device and the status information of the IoT device corresponding to the controllable device information.

34. The device according to claim 33, characterized in that The first subscription relationship includes a subscription relationship between the client device and the status information of the Internet of Things device corresponding to the controllable device information stored in the third cluster; The third cluster is used to support the proxy capability of the proxy device.

35. The device according to claim 33 or 34, characterized in that The first subscription relationship corresponds to at least one subscription target path; The controllable device information includes the subscription target path whose state has changed, and the changed state corresponding to the subscription target path whose state has changed.

36. The device according to any one of claims 29 to 35, characterized in that The device further comprises: A query module, configured to query whether a binding relationship of a long-term binding type exists between the client device and the proxy device; the binding relationship is used for the client device to control the IoT device connected to the proxy device through the proxy device; The acquisition module is configured to acquire the controllable device information from the proxy device when it is found that a binding relationship of a long-term binding type exists between the client device and the proxy device.

37. The device according to claim 36, characterized in that The query module is used to: querying whether there is client binding information corresponding to the proxy device in the second cluster; the second cluster is used to support the client device to use other devices as proxies to control the IoT devices connected to the other devices; When it is found that the client binding information corresponding to the proxy device exists in the second cluster, obtaining the binding type in the client binding information corresponding to the proxy device; In a case where the binding type in the client binding information corresponding to the proxy device is long-term binding, it is determined that a binding relationship of the long-term binding type exists between the client device and the proxy device.

38. The device according to claim 36 or 37, characterized in that The device further comprises: The establishing module is configured to establish a binding relationship of long-term binding type between the client device and the proxy device when it is found that no binding relationship of long-term binding type exists between the client device and the proxy device.

39. A computer device, characterized in that: The computer device includes a processor, a memory and a transceiver; The memory stores a computer program, and the processor executes the computer program so that the computer device implements the device control method according to any one of claims 1 to 19.

40. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the device control method according to any one of claims 1 to 19.

41. A chip, characterized in that: The chip is used to run in a computer device, so that the computer device executes the device control method according to any one of claims 1 to 19.

42. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; the processor of the computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, so that the computer device executes the device control method as described in any one of claims 1 to 19.

43. A computer program, characterized in that The computer program is executed by a processor of a computer device to implement the device control method according to any one of claims 1 to 19.

Images