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

Abstract

The invention discloses an equipment binding method and device, equipment, a storage medium and a program product, and belongs to the technical field of Internet of Things. The method comprises: establishing a binding relationship between a proxy device and a client device (201); the binding relationship is used for the client device to control the Internet of Things device connected with the proxy device through the proxy device. 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 binding 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 binding 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 binding 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 binding method, which is performed by a proxy device and includes:

[0007] A binding relationship is established between the proxy device and the client device; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

[0008] In one aspect, an embodiment of the present application provides a device binding method, which is performed by a client device and includes:

[0009] Send device control capability information to the proxy device; the device control capability information is used to indicate the control capability of the client device over the Internet of Things device, so that the proxy device establishes a binding relationship between the proxy device and the client device based on the device control capability information; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

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

[0011] The binding relationship establishment module is used to establish a binding relationship between the proxy device and the client device; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

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

[0013] A sending module is used to send device control capability information to the proxy device; the device control capability information is used to indicate the control capability of the client device over the Internet of Things device, so that the proxy device establishes a binding relationship between the proxy device and the client device based on the device control capability information; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

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

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

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

[0017] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is loaded and executed by a processor to implement the above-mentioned device binding method.

[0018] 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 binding method.

[0019] 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 binding method.

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

[0021] Through the technical solution provided in the embodiments of the present application, the proxy device can establish a binding relationship between the proxy device and the client device, so that the client device can control the IoT device to which the proxy device is connected through the proxy device based on the above binding relationship, 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

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

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

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

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

[0026] FIG4 is a flow chart of a device binding method provided by an embodiment of the present application;

[0027] FIG5 is a schematic diagram of a binding process of a smart home scenario involved in the embodiment shown in FIG4 ;

[0028] FIG6 is a schematic diagram of a binding process for another smart home scenario involved in the embodiment shown in FIG4 ;

[0029] FIG7 is a block diagram of a device binding apparatus provided by an embodiment of the present application;

[0030] FIG8 is a block diagram of a device binding apparatus provided by one embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0051] Please refer to FIG2 , which shows a flow chart of a device binding 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:

[0052] Step 201: Establish a binding relationship between the proxy device and the client device; the binding relationship is used for the client device to control the IoT device connected to the proxy device through the proxy device.

[0053] In one possible implementation, establishing a binding relationship between the proxy device and the client device includes:

[0054] First binding device information corresponding to the client device is added to the first cluster.

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

[0056] Identification information of the client device;

[0057] Protocol version information of the client device;

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

[0059] Version information of the controllable device list.

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

[0061] Identification information of IoT devices;

[0062] The online status of an IoT device; the online status includes online or offline.

[0063] In one possible implementation, the method further includes:

[0064] Obtain device control capability information of the client device; the device control capability information is used to indicate the control capability of the client device over the IoT device;

[0065] Establishing a binding relationship between the proxy device and the client device includes:

[0066] A binding relationship is established between the proxy device and the client device based on the device control capability information.

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

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

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

[0070] In one possible implementation, establishing a binding relationship between the proxy device and the client device according to the device control capability information includes:

[0071] In the case that there is an IoT device matching the device control capability information among the IoT devices connected to the proxy device, a binding relationship between the proxy device and the client device is established according to the device control capability information.

[0072] In one possible implementation, obtaining device control capability information of a client device includes:

[0073] Send a control capability acquisition request to the client device;

[0074] The device control capability information is received from the client device in response to the control capability acquisition request.

[0075] In one possible implementation, establishing a binding relationship between the proxy device and the client device includes:

[0076] Send a capability query request to the client device; the capability query request is used to query whether the client device supports controlling the IoT device;

[0077] receiving protocol version information of the client device returned by the client device in response to the capability query request;

[0078] When the protocol version information of the client device indicates that the client device supports controlling the IoT device, a binding relationship is established between the proxy device and the client device.

[0079] In one possible implementation, establishing a binding relationship between the proxy device and the client device includes:

[0080] Obtain identification information of each cluster set in the client device;

[0081] In a case where the identification information of each cluster includes the identification information of the second cluster, a binding relationship is established between the proxy device and the client device.

[0082] In a possible implementation, adding first binding device information corresponding to the client device in the first cluster includes:

[0083] Get the binding type of the binding relationship; the binding type includes temporary binding or long-term binding;

[0084] In a case where the binding type of the binding relationship includes long-term binding, first binding device information corresponding to the client device is added to the first cluster.

[0085] In one possible implementation, the method further includes:

[0086] The binding type information is sent to the client device, where the binding type information is used to indicate the binding type of the binding relationship.

[0087] In one possible implementation, the method further includes:

[0088] Gets 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.

[0089] In one possible implementation, the method further includes:

[0090] Send access type information to the client device, where the access type information is used to indicate the access type of the client device to the IoT device connected to the proxy device.

[0091] In one possible implementation, the method further includes:

[0092] Send a binding relationship notification to the client device; the binding relationship notification is used to indicate the binding relationship.

[0093] To sum up, in the embodiments of the present application, the proxy device can establish a binding relationship between the proxy device and the client device, so that the client device can control the IoT device to which the proxy device is connected through the proxy device based on the above binding relationship, thereby expanding the control scenario of the client device over the IoT device and improving the control efficiency of the IoT device.

[0094] Please refer to FIG3 , which shows a flow chart of a device binding method provided by one embodiment of the present application. The method may be performed 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:

[0095] Step 301: Send device control capability information to the proxy device; the device control capability information is used to indicate the control capability of the client device over the IoT device, so that the proxy device establishes a binding relationship between the proxy device and the client device based on the device control capability information; the binding relationship is used for the client device to control the IoT device connected to the proxy device through the proxy device.

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

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

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

[0099] In one possible implementation, sending device control capability information to the proxy device includes:

[0100] The device control capability information included in the second cluster is sent to the proxy device.

[0101] In a possible implementation, the second cluster further includes at least one of the following information:

[0102] Manufacturer information of the client device;

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

[0104] 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 second cluster includes at least one of the following information:

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

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

[0107] In one possible implementation, the method further includes:

[0108] The first client binding information corresponding to the binding relationship between the proxy device and the client device is added to the client binding information list.

[0109] In one possible implementation, the first client binding information includes at least one of the following information:

[0110] Identification information of the proxy device;

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

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

[0113] In one possible implementation, sending device control capability information to the proxy device includes:

[0114] Receive a control capability acquisition request sent by a proxy device;

[0115] In response to the control capability acquisition request, the device control capability information is sent to the proxy device.

[0116] In one possible implementation, the method further includes:

[0117] Receive a capability query request sent by the proxy device; the capability query request is used to query whether the client device supports controlling the IoT device;

[0118] In response to the capability query request, protocol version information of the client device is returned to the proxy device.

[0119] In one possible implementation, the method further includes:

[0120] The binding type information sent by the proxy device is received, where the binding type information 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.

[0121] In one possible implementation, the method further includes:

[0122] Receive access type information sent by the proxy device, where the access type information is used to indicate the type of access the client device has to the IoT device connected to the proxy device; the access type includes bridge access or proxy access.

[0123] In one possible implementation, the method further includes:

[0124] Receive a binding relationship notification sent by the proxy device; the binding relationship notification is used to indicate the binding relationship between the proxy device and the client device.

[0125] To sum up, in the embodiments of the present application, the client device can send device control capability information indicating its own control capability over the IoT device to the proxy device, so that the proxy device can establish a binding relationship between the proxy device and the client device, thereby enabling the client device to control the IoT device to which the proxy device is connected through the proxy device based on the above binding relationship, thereby expanding the control scenarios of the client device over the IoT device and improving the control efficiency of the IoT device.

[0126] Please refer to FIG4 , which shows a flow chart of a device binding 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:

[0127] Step 401: The proxy device obtains the device control capability information of the client device; accordingly, the client device sends the device control capability information to the proxy device.

[0128] The device control capability information is used to indicate the control capability of the client device over the IoT device.

[0129] In an exemplary embodiment of the present application, the proxy device may be a user's smart phone, smart watch, or other mobile smart terminal or wearable smart terminal. The client device may be a vehicle-mounted device or other computer device that is not connected to the Internet of Things (IoT) via the proxy device.

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

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

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

[0133] In embodiments of the present application, the device control capability information may be used to indicate which types of IoT devices the client device controls. For example, the device types may include switches, lighting, air conditioners, and the like. Embodiments of the present application do not limit the manner in which the device types are classified.

[0134] And / or, the device control capability information may be used to indicate the control capabilities supported by the client device; for example, the control capabilities may include switch control capability, brightness adjustment control capability, temperature adjustment control capability, etc. The embodiment of the present application does not limit the division method of the control capabilities.

[0135] In a possible implementation, the proxy device obtains the device control capability information of the client device, and the step of the client device sending the device control capability information to the proxy device may include:

[0136] The proxy device sends a control capability acquisition request to the client device; the client device receives the control capability acquisition request sent by the proxy device;

[0137] The client device sends device control capability information to the proxy device in response to the control capability acquisition request; the proxy device receives the device control capability information sent by the client device.

[0138] In an embodiment of the present application, the proxy device may send a request to the client device to obtain device control capability information (i.e., the above-mentioned control capability acquisition request). After receiving the request, the client device may send its own device control capability information to the proxy device.

[0139] In a possible implementation, the step of the client device sending the device control capability information to the proxy device may include:

[0140] The client device sends the device control capability information contained in the second cluster to the proxy device.

[0141] In an embodiment of the present application, a cluster may be set in the client device to support controlling other IoT devices through a proxy device, wherein the device control capability information may be set in the second cluster.

[0142] In the embodiment of the present application, the second cluster may be referred to as an IoT client cluster. Optionally, the cluster may be a cluster with other names, and the embodiment of the present application does not limit the name of the second cluster.

[0143] In a possible implementation, the second cluster further includes at least one of the following information:

[0144] Manufacturer information of the client device;

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

[0146] The manufacturer information may be a manufacturer identifier of the client device.

[0147] The above client binding information list may include multiple client binding information, each of which may correspond to an established binding relationship between a client device and another device (proxy device) (used to control IoT devices connected to other devices using the other device as a proxy).

[0148] 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 second cluster includes at least one of the following information:

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

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

[0151] Among them, the value of the above-mentioned first support information can be a bool value. When the value of the first support information is true (True), it indicates that the client device supports controlling all types of IoT devices; when the value of the first support information is false (False), it indicates that the client device does not support controlling all types of IoT devices.

[0152] The above device type list may include one or more device type identifiers, which are used to indicate that the client device supports controlling the IoT devices corresponding to these device types.

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

[0154] Table 1

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

[0156] The VendorID in Table 1 above indicates the manufacturer; SupportedDeviceTypes corresponds to the device types of IoT devices that the client device in the device control capability information above supports controlling, and the value is a list of device types; bindingSource corresponds to the client binding information list.

[0157] The structure (struct) of deviceTypeList in Table 1 above may be as shown in Table 2 below.

[0158] Table 2

[0159]

[0160] Among them, AllDevices in Table 2 corresponds to the first support information mentioned above; DeviceTypeList in Table 2 corresponds to the device type list mentioned above. When AllDevices is FALSE, the device type list contains the device type IDs of one or more IoT devices that the client device supports controlling; and when AllDevices is TRUE, the value of AllDevices is empty.

[0161] The clientBindingInfo structure in Table 1 above is used to record the binding relationship between the IOT Client (i.e., the client device) and the IOT Agent (i.e., the agent device). 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.

[0162] The structure of clientBindingInfo may be as shown in Table 3 below.

[0163] Table 3

[0164]

[0165] In Table 3 above, AgentID includes the ID of the device that has established a binding relationship with the client device. The value of BindingType in Table 3 above indicates whether the binding relationship is a long-term binding or a temporary binding.

[0166] Optionally, when the value of the above BindingType is 0, it indicates that the binding relationship is a temporary binding. After the subsequent client device completes controlling the IoT device connected to the device corresponding to the IOT proxy ID, the list of controllable devices and other information sent by the device corresponding to the IOT proxy ID may not be saved. Conversely, when the value of the above BindingType is 1, it indicates that the binding relationship is a long-term binding. After the subsequent client device completes controlling the IoT device connected to the device corresponding to the IOT proxy ID, the list of controllable devices and other information sent by the device corresponding to the IOT proxy ID may be saved for use the next time the IoT device connected to the device corresponding to the IOT proxy ID is controlled.

[0167] Step 402: The proxy device establishes a binding relationship between the proxy device and the client device according to the device control capability information.

[0168] The binding relationship is used by the client device to control the IoT device connected to the proxy device through the proxy device.

[0169] In the embodiment of the present application, the binding relationship between the proxy device and the client device may be initiated and established by the proxy device.

[0170] Among them, the process of the above-mentioned proxy device establishing a binding relationship between the proxy device and the client device may include creating a new binding project in the proxy device, wherein the binding project includes relevant information binding with the client device and / or information required to support the client device to control the Internet of Things device using the proxy device as an agent.

[0171] In a possible implementation, the process of the proxy device establishing a binding relationship with the client device may include:

[0172] The proxy device adds first binding device information corresponding to the client device in the first cluster.

[0173] The first cluster may include one or more pieces of binding device information, and each piece of binding device information corresponds to a binding relationship between a proxy device and a client.

[0174] In the embodiment of the present application, the first cluster may be referred to as an IOT Agent Binding Cluster.

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

[0176] Identification information of the client device;

[0177] Protocol version information of the client device;

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

[0179] Version information of the controllable device list.

[0180] The protocol version information may be the version number of the IoT protocol supported by the client device.

[0181] Since a client device may only support controlling some of the IoT devices among the IoT devices connected to the proxy device, and different client devices may support controlling different types of IoT devices, in an embodiment of the present application, a controllable device list can be set in the binding device information corresponding to each client device to save the device information of the IoT devices that can be controlled by the client device.

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

[0183] Identification information of IoT devices;

[0184] The online status of an IoT device; the online status includes online or offline.

[0185] The online status of the IoT device can be used to indicate whether the IoT device can currently be controlled.

[0186] The attributes included in the above-mentioned IOT Agent Binding Cluster may be as shown in the following Table 4.

[0187] Table 4

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

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

[0190] The structure of bindingDeviceInfo in Table 4 above may be as shown in Table 5 below.

[0191] Table 5

[0192]

[0193]

[0194] Among them, the structure of onlineStatus in the above Table 5 can be shown in the following Table 6.

[0195] Table 6

[0196]

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

[0198] Table 7

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

[0200] In a possible implementation, the process of the proxy device adding first binding device information corresponding to the client device in the first cluster may include:

[0201] Get the binding type of the binding relationship; the binding type includes temporary binding or long-term binding;

[0202] In a case where the binding type of the binding relationship includes long-term binding, first binding device information corresponding to the client device is added to the first cluster.

[0203] In the embodiment of the present application, the process of obtaining the binding type of the binding relationship may include:

[0204] A user instruction for setting a binding type is received, and the binding type of the binding relationship is obtained according to the user instruction.

[0205] That is to say, the binding type in the embodiment of the present application can be set by the user.

[0206] In an embodiment of the present application, if the binding type set by the user is temporary binding, it may be that the user only needs to temporarily control the IoT device connected to the proxy device through the client device, and may not control the IoT device connected to the proxy device later. At this time, the proxy device does not need to add the first binding device information corresponding to the client device in the first cluster.

[0207] On the contrary, if the binding type set by the user is long-term binding, it may be that the user needs to control the IoT device connected to the proxy device through the client device for a long time, that is, the IoT device connected to the proxy device may be controlled later. At this time, the proxy device can add the first binding device information corresponding to the client device in the first cluster.

[0208] In a possible implementation, the proxy device may further send binding type information to the client device, where the binding type information is used to indicate the binding type of the binding relationship. Correspondingly, the client device receives the binding type information sent by the proxy device.

[0209] In the embodiment of the present application, after obtaining the binding type of the binding relationship, the proxy device may notify the client device of the binding type.

[0210] In a possible implementation, the proxy device may further obtain an access type of the client device to the IoT device connected to the proxy device; the access type includes bridge access or proxy access.

[0211] In an embodiment of the present application, the proxy device can determine the above-mentioned access type based on the IOT protocol supported by the client device; for example, when the IOT protocol supported by the client device is the same as the protocol of the IOT system to which the proxy device is connected, the access type is determined to be proxy access; otherwise, the access type is determined to be bridge access.

[0212] In one possible implementation, the proxy device may further send access type information to the client device, where the access type information indicates the type of access the client device has to the IoT device connected to the proxy device. Accordingly, the client device receives the access type information sent by the proxy device.

[0213] In the embodiment of the present application, after obtaining the access type of the binding relationship, the proxy device may notify the client device of the access type.

[0214] In a possible implementation, the process of the proxy device establishing a binding relationship between the proxy device and the client device according to the device control capability information may include:

[0215] In the case that there is an IoT device matching the device control capability information among the IoT devices connected to the proxy device, a binding relationship between the proxy device and the client device is established according to the device control capability information.

[0216] In an embodiment of the present application, before establishing a binding relationship between the proxy device and the client device, the proxy device may first determine, based on the device control capability information of the client device, whether there is an IoT device in the IO ecosystem to which it is connected that can be controlled by the client device. If so, a binding relationship between the proxy device and the client device may be established; otherwise, the proxy device may not establish a binding relationship between the proxy device and the client device and exit the binding process.

[0217] In a possible implementation, the process of the proxy device establishing a binding relationship with the client device may include:

[0218] Send a capability query request to the client device; the capability query request is used to query whether the client device supports controlling the IoT device;

[0219] receiving protocol version information of the client device returned by the client device in response to the capability query request;

[0220] When the protocol version information of the client device indicates that the client device supports controlling the IoT device, a binding relationship is established between the proxy device and the client device.

[0221] Accordingly, the client device may receive a capability query request sent by the proxy device; the capability query request is used to query whether the client device supports controlling the IoT device; and in response to the capability query request, the client device's protocol version information is returned to the proxy device.

[0222] Since there may be differences in the protocol versions of the client device and the proxy device, the proxy device is incompatible with the protocol version of the client device, which in turn causes the client device to be unable to control the IoT device through the proxy device. In this regard, in an embodiment of the present application, the proxy device can first query the protocol version information of the client device through a capability query request (indicating the IoT protocol version supported by the client device, for example, the protocol version information can include the version number of the IoT protocol supported by the client device). When the proxy device determines that it supports the protocol version of the client device, the proxy device can execute the above-mentioned steps of establishing a binding relationship between the proxy device and the client device.

[0223] In a possible implementation, the process of the proxy device establishing a binding relationship between the proxy device and the client device may include: obtaining identification information of each cluster set in the client device; and establishing the binding relationship between the proxy device and the client device when the identification information of each cluster includes identification information of the second cluster.

[0224] In an embodiment of the present application, the proxy device can query the client device about which clusters are set in the client device. For example, there is an endpointList on the client device, which is used to identify the endpoint list existing on the client device. Under each endpoint in the endpointList, there can be a specific cluster: a descriptor cluster, in which all clusters supported by the endpoint can be listed; after the client device establishes a connection with the proxy device, the endpointList or the descriptor cluster contained in the endpointList can be actively or passively sent to the proxy device. After the proxy device inquires about which clusters are set in the client device, it can further determine whether the second cluster is included. If so, it means that the client device has the function of using other devices as agents to control the device. At this time, the proxy device can only perform the above-mentioned process of establishing a binding relationship between the proxy device and the client device.

[0225] In an embodiment of the present application, the step of obtaining identification information of each cluster set in the client device may be performed before step 401. In this case, the proxy device may perform step 401 if it is determined that the identification information of each cluster includes identification information of the second cluster.

[0226] Alternatively, the step of obtaining identification information of each cluster set in the client device may be performed after step 401. In this case, the proxy device may perform step 402 if it is determined that the identification information of each cluster includes identification information of the second cluster.

[0227] Step 403: The proxy device sends a binding relationship notification to the client device; the binding relationship notification is used to indicate the above binding relationship; the client device receives the binding relationship notification.

[0228] In the embodiment of the present application, the proxy device may notify the client device of the establishment of the binding relationship between the proxy device and the client device during the binding relationship establishment process or after the binding relationship establishment is completed.

[0229] The above-mentioned binding relationship notification may be a notification message for carrying the above-mentioned binding type information and / or access type information, or the above-mentioned binding type information and / or access type information may also be sent through other messages other than the binding relationship notification.

[0230] Step 404: The client device sets a binding relationship.

[0231] In a possible implementation, the client device may add the first client binding information corresponding to the binding relationship between the proxy device and the client device to the client binding information list of the second cluster.

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

[0233] Identification information of the proxy device;

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

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

[0236] The content included in the first client binding information may refer to Table 3. It should be noted that, based on Table 3, access type information may be further added.

[0237] After the client device and the proxy device execute the above solution, the IoT devices in the IoT ecosystem to which the proxy device is connected can be controlled through the proxy device.

[0238] For example, the client device can obtain controllable device information from the proxy device, and the proxy device sends the controllable device information to the client device; the controllable device information includes information of at least one IoT device connected to the proxy device; the client device sends a control instruction to the proxy device based on the above controllable device information; the proxy device receives the control instruction sent by the client device based on the controllable device information; the control instruction is used to control a target device in at least one IoT device; the proxy device sends the control instruction to the target device.

[0239] Please refer to Figure 5, which shows a schematic diagram of the binding process of a smart home scenario involved in an embodiment of the present application. Among them, the binding part mainly completes the binding of the IOT Client and the IOT Agent. After binding, the IOT Client can access the IOT ecosystem through the IOT Agent. Before the binding process, the IOT Client has completed the establishment of a communication channel with the IOT Agent. As shown in Figure 5, the binding process can be as follows:

[0240] S51, the user starts the binding process on the mobile phone side (IOT Agent).

[0241] S52, the IOT Agent discovers the identifier of the IOT Client cluster of the IOT Client and queries whether it supports smart home capabilities.

[0242] S53, the IOT Client returns the protocol version supported by the IOT Client: version id to the IOT Agent.

[0243] S54, the IOT Agent obtains a list of device types supported by the IOT Client: supporteddevicetype. This step S54 is optional.

[0244] S55: The IOT Client returns a list of supported device types.

[0245] S56: The user selects a binding type of temporary binding or long-term binding.

[0246] S57, if it is a long-term binding, the IOT Agent sets the binding relationship in the binding table (IOT Agent Binding cluster).

[0247] Among them, when the binding type is long-term binding, the IOT Agent sets the corresponding binding information (ie, the above-mentioned binding device information) in the IOT Agent Binding Cluster.

[0248] S58, the IOT Agent notifies the IOT Client of the binding type through the binding relationship notification.

[0249] S59, the IOT Client sets the binding type to the IOT Client cluster.

[0250] Among them, the IOT Client can set the binding type to the client binding information corresponding to the IOT Agent.

[0251] From now on, the IOT Client can access the IOT ecological devices through the IOT Agent.

[0252] Please refer to Figure 6, which shows a schematic diagram of the binding process of another smart home scenario involved in an embodiment of the present application. As shown in Figure 6, the binding process can be as follows:

[0253] S61, the user starts the binding process on the mobile phone side (IOT Agent).

[0254] S62, the IOT Agent discovers the identifier of the IOT Client cluster of the IOT Client and determines whether it supports smart home capabilities.

[0255] S63, the IOT Client returns the protocol version supported by the IOT Client: version id to the IOT Agent.

[0256] S64, the IOT Agent obtains a list of device types supported by the IOT Client: supporteddevicetype. Step S54 is optional.

[0257] S65: The IOT Client returns a list of supported device types.

[0258] S66: The user selects a binding type of temporary binding or long-term binding.

[0259] If the user selects temporary binding, the IOT Client needs to delete the device list and other information after the connection ends. If it is long-term binding, the IOT Client needs to save the necessary information.

[0260] S67, the IOT Agent determines whether the access type is bridge or proxy.

[0261] Among them, the IOT Agent can determine whether to use bridge or proxy according to the protocol type of the IOT Client. If it is a heterogeneous protocol, the bridge access type is adopted; if it is a homogeneous protocol, the proxy access type is adopted.

[0262] Among them, Bridge refers to the protocol between the IOT Agent and the subsequent smart home system, which is inconsistent with the protocol between the IOT Client and the IOT Agent. Protocol conversion is required when forwarding subsequent control commands.

[0263] Proxy refers to the protocol between the IOT Agent and the subsequent smart home system, which is consistent with the protocol between the IOT Client and the IOT Agent. Subsequent control command forwarding does not require protocol conversion, but requires the relay capability of the IOT Agent.

[0264] S68, the IOT Agent sets the access method to the IOT Client: access type, binding type.

[0265] S69, the IOT Client returns a response message to the IOT Agent, indicating that the access mode setting message has been received and the access mode setting is completed.

[0266] S610, the IOT Agent completes the setting of device binding information.

[0267] Among them, when the binding type is long-term binding, the IOT Agent sets the corresponding binding information (ie, the above-mentioned binding device information) in the IOT Agent Binding Cluster.

[0268] Taking the above solution as an example of applying it to the Internet of Vehicles (IoV) scenario, the solution shown in the embodiments of this application allows the vehicle-mounted device to be bound via a mobile phone, and using the mobile phone's capabilities to connect to the IoT ecosystem, thereby controlling IoT devices within the IoT ecosystem. For example, by binding the vehicle-mounted device to the mobile phone, the user can control the air conditioner in the smart home system from the vehicle-mounted device, turning it on or off.

[0269] To sum up, in the embodiments of the present application, the proxy device can establish a binding relationship between the proxy device and the client device, so that the client device can control the IoT device to which the proxy device is connected through the proxy device based on the above binding relationship, thereby expanding the control scenario of the client device over the IoT device and improving the control efficiency of the IoT device.

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

[0271] The binding relationship establishing module 701 is used to establish a binding relationship between a proxy device and a client device; the binding relationship is used for the client device to control the IoT device connected to the proxy device through the proxy device.

[0272] In a possible implementation, the binding relationship establishing module 701 is configured to add first binding device information corresponding to the client device in the first cluster.

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

[0274] identification information of the client device;

[0275] protocol version information of the client device;

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

[0277] Version information of the controllable device list.

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

[0279] Identification information of the IoT device;

[0280] The online status of the IoT device; the online status includes online or offline.

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

[0282] A first acquisition module is configured to acquire device control capability information of the client device; the device control capability information is used to indicate the control capability of the client device over the IoT device;

[0283] The binding relationship establishing module 701 is configured to establish a binding relationship between the proxy device and the client device according to the device control capability information.

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

[0285] The device type of the IoT device that the client device supports controlling;

[0286] And, the control capability of the IoT device supported by the client device.

[0287] In one possible implementation, the binding relationship establishing module 701 is used to establish a binding relationship between the proxy device and the client device according to the device control capability information when there is an IoT device matching the device control capability information among the IoT devices connected to the proxy device.

[0288] In a possible implementation, the first acquisition module is configured to:

[0289] Sending a control capability acquisition request to the client device;

[0290] The device control capability information is received, which is sent by the client device in response to the control capability acquisition request.

[0291] In a possible implementation, the binding relationship establishing module 701 is used to:

[0292] Sending a capability query request to the client device; the capability query request is used to query whether the client device supports controlling the Internet of Things device;

[0293] receiving protocol version information of the client device returned by the client device in response to the capability query request;

[0294] In a case where the protocol version information of the client device indicates that the client device supports controlling the Internet of Things device, a binding relationship is established between the proxy device and the client device.

[0295] In a possible implementation, the binding relationship establishing module 701 is used to:

[0296] Obtaining identification information of each cluster set in the client device;

[0297] In a case where the identification information of each cluster includes the identification information of the second cluster, a binding relationship is established between the proxy device and the client device.

[0298] In a possible implementation, the binding relationship establishing module 701 is used to:

[0299] Obtaining a binding type of the binding relationship; the binding type includes temporary binding or long-term binding;

[0300] In a case where the binding type of the binding relationship includes long-term binding, first binding device information corresponding to the client device is added to the first cluster.

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

[0302] The first sending module is configured to send binding type information to the client device, where the binding type information is used to indicate the binding type of the binding relationship.

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

[0304] The second acquisition module is used to obtain the access type of the client device to the Internet of Things device connected to the proxy device; the access type includes bridge access or proxy access.

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

[0306] The second sending module is used to send access type information to the client device, where the access type information is used to indicate the access type of the client device to the Internet of Things device connected to the proxy device.

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

[0308] The third sending module is configured to send a binding relationship notification to the client device; the binding relationship notification is used to indicate the binding relationship.

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

[0310] The sending module 801 is used to send device control capability information to the proxy device; the device control capability information is used to indicate the control capability of the client device over the IoT device, so that the proxy device establishes a binding relationship between the proxy device and the client device based on the device control capability information; the binding relationship is used by the client device to control the IoT device connected to the proxy device through the proxy device.

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

[0312] The device type of the IoT device that the client device supports controlling;

[0313] And, the control capability of the IoT device supported by the client device.

[0314] In a possible implementation, the sending module 801 is configured to send the device control capability information contained in the second cluster to the proxy device.

[0315] In a possible implementation, the second cluster further includes at least one of the following information:

[0316] Manufacturer information of the client device;

[0317] And, a client binding information list; the client binding information list includes client binding information of established binding relationships.

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

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

[0320] And, a device type list; the device type list includes type identification information of device types of the Internet of Things devices supported by the client device for control.

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

[0322] An adding module is configured to add first client binding information corresponding to the binding relationship between the proxy device and the client device to the client binding information list.

[0323] In a possible implementation, the first client binding information includes at least one of the following information:

[0324] identification information of the proxy device;

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

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

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

[0328] receiving a control capability acquisition request sent by the proxy device;

[0329] In response to the control capability acquisition request, the device control capability information is sent to the proxy device.

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

[0331] A first receiving module is configured to receive a capability query request sent by the proxy device; the capability query request is used to query whether the client device supports controlling the IoT device;

[0332] The sending module 801 is further configured to return the protocol version information of the client device to the proxy device in response to the capability query request.

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

[0334] The second receiving module is configured to receive binding type information sent by the proxy device, where the binding type information indicates a binding type of a binding relationship between the proxy device and the client device; the binding type includes temporary binding or long-term binding.

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

[0336] The third receiving module is used to receive access type information sent by the proxy device, where 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.

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

[0338] The fourth receiving module is configured to receive a binding relationship notification sent by the proxy device; the binding relationship notification is used to indicate a binding relationship between the proxy device and the client device.

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

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

[0341] Please refer to FIG9 , which shows a schematic diagram of the structure of a computer device 900 provided in one embodiment of the present application. The computer device 900 may include: a processor 901 , a receiver 902 , a transmitter 903 , a memory 904 , and a bus 905 .

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

[0343] The receiver 902 and the transmitter 903 may be implemented as a communication component, which may be a communication chip, which may also be called a transceiver.

[0344] The memory 904 is connected to the processor 901 via a bus 905 .

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

[0346] In addition, the memory 904 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.

[0347] In an exemplary scenario, when the computer device 900 is implemented as the above-mentioned proxy device, the receiving processor is used to establish a binding relationship between the proxy device and the client device; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

[0348] The process executed by the processor 901 and / or the transceiver in the computer device 900 may refer to the steps executed by the proxy device in the method shown in either FIG. 2 or FIG. 4 .

[0349] In an exemplary scenario, when the computer device 900 is implemented as a client device, the transceiver is used to send device control capability information to the proxy device; the device control capability information is used to indicate the client device's control capability over the IoT device, so that the proxy device establishes a binding relationship between the proxy device and the client device based on the device control capability information; the binding relationship is used for the client device to control the IoT device connected to the proxy device through the proxy device.

[0350] The process executed by the processor 901 and / or the transceiver in the computer device 900 may refer to the steps executed by the client device in the method shown in either FIG. 3 or FIG. 4 .

[0351] 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 4 above.

[0352] 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 4 above.

[0353] 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 4 above.

[0354] 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 4 above.

[0355] 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 medium that facilitates the transmission of computer programs from one place to another. The storage medium can be an available medium that can be accessed by a general-purpose or special-purpose computer.

[0356] 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 binding method, characterized in that: The method is performed by an agent device, and includes: A binding relationship is established between the proxy device and the client device; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

2. The method according to claim 1, characterized in that The establishing of a binding relationship between the proxy device and the client device includes: First binding device information corresponding to the client device is added to the first cluster.

3. The method according to claim 2, characterized in that The first bound device information includes at least one of the following information: identification information of the client device; protocol version information of the client device; 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; Version information of the controllable device list.

4. The method according to claim 3, characterized in that The device information of the IoT device includes at least one of the following information: Identification information of the IoT device; The online status of the IoT device; the online status includes online or offline.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Obtaining device control capability information of the client device; the device control capability information is used to indicate the control capability of the client device over the Internet of Things device; The establishing of a binding relationship between the proxy device and the client device includes: A binding relationship is established between the proxy device and the client device according to the device control capability information.

6. The method according to claim 5, characterized in that The device control capability information includes at least one of the following information: The device type of the IoT device that the client device supports controlling; And, the control capability of the IoT device supported by the client device.

7. The method according to claim 5 or 6, characterized in that The establishing a binding relationship between the proxy device and the client device according to the device control capability information includes: In a case where there is an IoT device matching the device control capability information among the IoT devices connected to the proxy device, a binding relationship is established between the proxy device and the client device according to the device control capability information.

8. The method according to any one of claims 5 to 7, characterized in that: The acquiring device control capability information of the client device includes: Sending a control capability acquisition request to the client device; The device control capability information is received, which is sent by the client device in response to the control capability acquisition request.

9. The method according to any one of claims 1 to 8, characterized in that: The establishing of a binding relationship between the proxy device and the client device includes: Sending a capability query request to the client device; the capability query request is used to query whether the client device supports controlling the Internet of Things device; receiving protocol version information of the client device returned by the client device in response to the capability query request; In a case where the protocol version information of the client device indicates that the client device supports controlling the Internet of Things device, a binding relationship is established between the proxy device and the client device.

10. The method according to any one of claims 1 to 9, characterized in that: The establishing of a binding relationship between the proxy device and the client device includes: Obtaining identification information of each cluster set in the client device; In a case where the identification information of each cluster includes the identification information of the second cluster, a binding relationship is established between the proxy device and the client device.

11. The method according to any one of claims 2 to 4, characterized in that: Adding first binding device information corresponding to the client device in the first cluster includes: Obtaining a binding type of the binding relationship; the binding type includes temporary binding or long-term binding; In a case where the binding type of the binding relationship includes long-term binding, first binding device information corresponding to the client device is added to the first cluster.

12. The method according to claim 11, characterized in that The method further comprises: Sending binding type information to the client device, where the binding type information is used to indicate the binding type of the binding relationship.

13. The method according to any one of claims 1 to 12, characterized in that: The method further comprises: Obtain an access type of the client device to the IoT device connected to the proxy device; the access type includes bridge access or proxy access.

14. The method according to claim 13, characterized in that The method further comprises: Access type information is sent to the client device, where the access type information is used to indicate an access type of the client device to the Internet of Things device connected to the proxy device.

15. The method according to any one of claims 1 to 14, characterized in that: The method further comprises: A binding relationship notification is sent to the client device; the binding relationship notification is used to indicate the binding relationship.

16. A device binding method, characterized in that: The method is performed by a client device, and includes: Send device control capability information to the proxy device; the device control capability information is used to indicate the control capability of the client device over the Internet of Things device, so that the proxy device establishes a binding relationship between the proxy device and the client device based on the device control capability information; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

17. The method according to claim 16, characterized in that The device control capability information includes at least one of the following information: The device type of the IoT device that the client device supports controlling; And, the control capability of the IoT device supported by the client device.

18. The method according to claim 16 or 17, characterized in that The sending of the device control capability information to the proxy device includes: The device control capability information contained in the second cluster is sent to the proxy device.

19. The method according to claim 18, characterized in that The second cluster further includes at least one of the following information: Manufacturer information of the client device; And, a client binding information list; the client binding information list includes client binding information of established binding relationships.

20. The method according to claim 18 or 19, characterized in that In a case where the device control capability information includes the device type of the IoT device that the client device supports controlling, the second cluster includes at least one of the following information: First support information; the first support information is used to indicate whether the client device supports controlling all types of IoT devices; And, a device type list; the device type list includes type identification information of device types of the Internet of Things devices supported by the client device for control.

21. The method according to claim 19, wherein The method further comprises: The first client binding information corresponding to the binding relationship between the proxy device and the client device is added to the client binding information list.

22. The method according to claim 21, characterized in that The first client binding information includes at least one of the following information: identification information of the proxy device; 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; And, access type information; the access type information is used to indicate the access type of the client device to the Internet of Things device connected to the proxy device; the access type includes bridge access or proxy access.

23. The method according to any one of claims 16 to 22, characterized in that The sending of the device control capability information to the proxy device includes: receiving a control capability acquisition request sent by the proxy device; In response to the control capability acquisition request, the device control capability information is sent to the proxy device.

24. The method according to any one of claims 16 to 23, characterized in that The method further comprises: Receive a capability query request sent by the proxy device; the capability query request is used to query whether the client device supports controlling the Internet of Things device; In response to the capability query request, protocol version information of the client device is returned to the proxy device.

25. The method according to any one of claims 16 to 24, characterized in that The method further comprises: Receive binding type information sent by the proxy device, where the binding type information is used to indicate a binding type of a binding relationship between the proxy device and the client device; the binding type includes temporary binding or long-term binding.

26. The method according to any one of claims 16 to 25, characterized in that The method further comprises: Receive access type information sent by the proxy device, where the access type information is used to indicate an access type of the client device to the IoT device connected to the proxy device; the access type includes bridge access or proxy access.

27. The method according to any one of claims 16 to 26, characterized in that The method further comprises: A binding relationship notification sent by the proxy device is received; the binding relationship notification is used to indicate a binding relationship between the proxy device and the client device.

28. A device binding apparatus, characterized in that: The device comprises: The binding relationship establishment module is used to establish a binding relationship between the proxy device and the client device; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

29. The device according to claim 28, characterized in that The binding relationship establishing module is used to add first binding device information corresponding to the client device in the first cluster.

30. The device according to claim 29, characterized in that The first bound device information includes at least one of the following information: identification information of the client device; protocol version information of the client device; 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; Version information of the controllable device list.

31. The device according to claim 30, characterized in that The device information of the IoT device includes at least one of the following information: Identification information of the IoT device; The online status of the IoT device; the online status includes online or offline.

32. The device according to any one of claims 28 to 31, characterized in that The device further comprises: A first acquisition module is configured to acquire device control capability information of the client device; the device control capability information is used to indicate the control capability of the client device over the IoT device; The binding relationship establishing module is configured to establish a binding relationship between the proxy device and the client device according to the device control capability information.

33. The device according to claim 32, characterized in that The device control capability information includes at least one of the following information: The device type of the IoT device that the client device supports controlling; And, the control capability of the IoT device supported by the client device.

34. The device according to claim 32 or 33, characterized in that The binding relationship establishing module is used to establish a binding relationship between the proxy device and the client device according to the device control capability information when there is an IoT device matching the device control capability information among the IoT devices connected to the proxy device.

35. The device according to any one of claims 32 to 34, characterized in that The first acquisition module is used to: Sending a control capability acquisition request to the client device; The device control capability information is received, which is sent by the client device in response to the control capability acquisition request.

36. The device according to any one of claims 28 to 35, characterized in that The binding relationship establishing module is used to: Sending a capability query request to the client device; the capability query request is used to query whether the client device supports controlling the Internet of Things device; receiving protocol version information of the client device returned by the client device in response to the capability query request; In a case where the protocol version information of the client device indicates that the client device supports controlling the Internet of Things device, a binding relationship is established between the proxy device and the client device.

37. The device according to any one of claims 28 to 36, characterized in that The binding relationship establishing module is used to: Obtaining identification information of each cluster set in the client device; In a case where the identification information of each cluster includes the identification information of the second cluster, a binding relationship is established between the proxy device and the client device.

38. The device according to any one of claims 29 to 31, characterized in that The binding relationship establishing module is used to: Obtaining a binding type of the binding relationship; the binding type includes temporary binding or long-term binding; In a case where the binding type of the binding relationship includes long-term binding, first binding device information corresponding to the client device is added to the first cluster.

39. The device according to claim 38, characterized in that The device further comprises: The first sending module is configured to send binding type information to the client device, where the binding type information is used to indicate the binding type of the binding relationship.

40. The device according to any one of claims 28 to 39, characterized in that The device further comprises: The second acquisition module is used to obtain the access type of the client device to the Internet of Things device connected to the proxy device; the access type includes bridge access or proxy access.

41. The device according to claim 40, characterized in that The device further comprises: The second sending module is used to send access type information to the client device, where the access type information is used to indicate the access type of the client device to the Internet of Things device connected to the proxy device.

42. The device according to any one of claims 28 to 41, characterized in that The device further comprises: The third sending module is configured to send a binding relationship notification to the client device; the binding relationship notification is used to indicate the binding relationship.

43. A device binding apparatus, characterized in that: The device comprises: A sending module is used to send device control capability information to the proxy device; the device control capability information is used to indicate the control capability of the client device over the Internet of Things device, so that the proxy device establishes a binding relationship between the proxy device and the client device based on the device control capability information; the binding relationship is used for the client device to control the Internet of Things device connected to the proxy device through the proxy device.

44. The device according to claim 43, characterized in that The device control capability information includes at least one of the following information: The device type of the IoT device that the client device supports controlling; And, the control capability of the IoT device supported by the client device.

45. The device according to claim 43 or 44, characterized in that The sending module is configured to send the device control capability information contained in the second cluster to the proxy device.

46. ​​The device according to claim 45, characterized in that The second cluster further includes at least one of the following information: Manufacturer information of the client device; And, a client binding information list; the client binding information list includes client binding information of established binding relationships.

47. The device according to claim 45 or 46, characterized in that In a case where the device control capability information includes the device type of the IoT device that the client device supports controlling, the second cluster includes at least one of the following information: First support information; the first support information is used to indicate whether the client device supports controlling all types of IoT devices; And, a device type list; the device type list includes type identification information of device types of the Internet of Things devices supported by the client device for control.

48. The device according to claim 46, characterized in that The device further comprises: An adding module is configured to add first client binding information corresponding to the binding relationship between the proxy device and the client device to the client binding information list.

49. The device according to claim 48, characterized in that The first client binding information includes at least one of the following information: identification information of the proxy device; 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; And, access type information; the access type information is used to indicate the access type of the client device to the Internet of Things device connected to the proxy device; the access type includes bridge access or proxy access.

50. The device according to any one of claims 43 to 49, characterized in that The sending module is used to: receiving a control capability acquisition request sent by the proxy device; In response to the control capability acquisition request, the device control capability information is sent to the proxy device.

51. The device according to any one of claims 43 to 50, characterized in that The device further comprises: A first receiving module is configured to receive a capability query request sent by the proxy device; the capability query request is used to query whether the client device supports controlling the IoT device; The sending module is further configured to return the protocol version information of the client device to the proxy device in response to the capability query request.

52. The device according to any one of claims 43 to 51, characterized in that The device further comprises: The second receiving module is configured to receive binding type information sent by the proxy device, where the binding type information indicates a binding type of a binding relationship between the proxy device and the client device; the binding type includes temporary binding or long-term binding.

53. The device according to any one of claims 43 to 52, characterized in that The device further comprises: The third receiving module is used to receive access type information sent by the proxy device, where 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.

54. The device according to any one of claims 43 to 53, characterized in that The device further comprises: The fourth receiving module is configured to receive a binding relationship notification sent by the proxy device; the binding relationship notification is used to indicate a binding relationship between the proxy device and the client device.

55. 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 binding method as described in any one of claims 1 to 27.

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

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

58. 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 performs the device binding 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 device binding method according to any one of claims 1 to 27.

Images