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

Abstract

The invention discloses an equipment unbinding method and device, equipment, a storage medium and a program product, and belongs to the technical field of Internet of Things. The method is performed by a first device, the first device being one of a proxy device and a client device; the method comprises: when a binding relationship between the proxy device and the client device satisfies an unbinding condition, deleting binding information corresponding to the binding relationship in the first 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 safety of equipment control can be improved, and the effect of saving memory resources of the equipment can be achieved.

Description

Device unbinding method, apparatus, equipment, 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 unbinding 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 unbinding 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 unbinding method, the method being performed by a first device, the first device being one of a proxy device and a client device; the method comprising:

[0007] When the binding relationship between the proxy device and the client device meets the unbinding condition, the binding information corresponding to the binding relationship in the first device is deleted; the binding relationship is used by the client device to control the Internet of Things device connected to the proxy device through the proxy device.

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

[0009] A deletion module is configured to delete binding information corresponding to a binding relationship between a proxy device and a client device in a first device when the binding relationship between the proxy device and the client device satisfies an unbinding condition; the binding relationship is used by the client device to control the IoT device connected to the proxy device through the proxy device; and the first device is one of the proxy device and the client device.

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

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

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

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

[0014] 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 unbinding method.

[0015] In another aspect, the present application provides a computer program product, comprising 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 the processor executes the computer instructions, causing the computer device to perform the above-described device unbinding method.

[0016] 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 unbinding method.

[0017] Through the technical solution provided by the embodiments of the present application, when a binding relationship has been established between a proxy device and a client device, one of the proxy device and the client device can cancel the above binding relationship to delete the binding information related to the binding relationship in the device, thereby achieving the effect of improving the security of device control and saving the memory resources of the device. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0023] FIG5 is a flow chart of a device binding method provided by one embodiment of the present application;

[0024] FIG6 is a block diagram of a device unbinding apparatus provided by an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0045] In an embodiment of the present application, in order to enable a client device to control an IoT device in an IoT ecosystem connected to the proxy device through the proxy device, a binding relationship may be established between the proxy device and the client device. For example, in one possible implementation of the embodiment of the present application, the binding relationship may be initiated by the proxy device.

[0046] For example, the proxy device can 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.

[0047] In a possible implementation, during the process of establishing the binding relationship between the proxy device and the client device, the proxy device may add first binding device information corresponding to the client device to the first cluster.

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

[0049] Identification information of the client device;

[0050] Protocol version information of the client device;

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

[0052] Version information of the controllable device list.

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

[0054] Identification information of IoT devices;

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

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

[0057] Table 1

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

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

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

[0061] Table 2

[0062]

[0063]

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

[0065] Table 3

[0066]

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

[0068] Table 4

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

[0070] In an embodiment of the present application, during the binding relationship establishment process or after the binding relationship is established, the proxy device may notify the client device of the establishment of the binding relationship between the proxy device and the client device. The notification may include information such as the binding type and access type. Accordingly, the client device may also set corresponding binding information in the local second cluster.

[0071] 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 Table 5 below.

[0072] Table 5

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

[0074] The VendorID in Table 5 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.

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

[0076] Table 6

[0077]

[0078] Among them, AllDevices in Table 6 corresponds to the first support information mentioned above; DeviceTypeList in Table 6 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.

[0079] The clientBindingInfo structure in Table 5 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.

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

[0081] Table 7

[0082]

[0083]

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

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

[0086] After the above binding relationship is established between the proxy device and the client device, the client device can control the IoT devices in the IoT ecosystem to which the proxy device is connected through the proxy device.

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

[0088] Then, when the user no longer needs to use the client device and controls the IoT devices in the IoT ecosystem connected to the proxy device through the proxy device, the above binding relationship still exists in the proxy device and the client device. On the one hand, it will affect the security of subsequent control of the IoT devices. On the other hand, the information related to the binding relationship will occupy the storage resources of the proxy device and the client device.

[0089] To address the above issues, an embodiment of the present application provides a method for unbinding a device, which can release the binding relationship established between a proxy device and a client device.

[0090] Please refer to FIG2 , which shows a flow chart of a device unbinding method provided by one embodiment of the present application. The method may be performed by a first device, which is one of a proxy device and a client device. For example, the proxy device may be the proxy device 120 in the network architecture shown in FIG1 , and the client device may be the client device 130 in the network architecture shown in FIG1 . The method may include the following steps:

[0091] Step 201: When the binding relationship between the proxy device and the client device meets the unbinding condition, the binding information corresponding to the binding relationship in the first device is deleted; the binding relationship is used by the client device to control the IoT device connected to the proxy device through the proxy device.

[0092] In a possible implementation, when the first device is a proxy device, deleting binding information corresponding to the binding relationship in the first device includes:

[0093] The first binding device information corresponding to the client device in the first cluster of proxy devices is deleted.

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

[0095] Identification information of the client device;

[0096] Protocol version information of the client device;

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

[0098] Version information of the controllable device list.

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

[0100] Identification information of IoT devices;

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

[0102] In a possible implementation, when the first device is a client device, deleting binding information corresponding to the binding relationship in the first device includes:

[0103] The first client binding information corresponding to the proxy device in the second cluster of client devices is deleted.

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

[0105] Identification information of the proxy device;

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

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

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

[0109] Delete the controllable device list stored in the client device; the controllable device list includes device information of IoT devices that the client device supports controlling among the IoT devices connected to the proxy device.

[0110] In one possible implementation, the unbinding condition includes any one of the following conditions:

[0111] In a case where the binding type of the binding relationship between the proxy device and the client device is long-term binding, a user instruction to release the binding relationship is received;

[0112] In a case where the binding type of the binding relationship between the proxy device and the client device is long-term binding, receiving an unbinding message sent by the second device;

[0113] In a case where the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, a user instruction to release the binding relationship is received;

[0114] Alternatively, when the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, it is detected that the secure connection between the proxy device and the client device is lost.

[0115] In a possible implementation, when the unbinding condition is that the binding type of the binding relationship between the proxy device and the client device is long-term binding and a user instruction to unbind the binding relationship is received, the method further includes:

[0116] An unbinding message is sent to a second device; the second device is another device among the proxy device and the client device except the first device; the unbinding message is used to instruct deletion of binding information corresponding to the binding relationship.

[0117] To summarize, in an embodiment of the present application, when a binding relationship has been established between a proxy device and a client device, one of the proxy device and the client device can cancel the binding relationship to delete the binding information related to the binding relationship in the device, thereby improving the security of device control and saving the memory resources of the device.

[0118] In the embodiment shown in FIG. 2 of the present application, the first device may be a proxy device or a client device, and the binding type of the binding relationship may be a long-term binding or a temporary binding.

[0119] In the case of long-term binding, the initiator of the above binding relationship can be a proxy device or a client device.

[0120] For example, taking the binding type of the above-mentioned binding relationship as long-term binding, and the user initiating unbinding from the proxy device as an example, please refer to FIG3 , which shows a flowchart of a device unbinding method provided by an embodiment of the present application. The method can be interactively executed by the proxy device and the client device; for example, the proxy device can be the proxy device 120 in the network architecture shown in FIG1 , and the client device can be the client device 130 in the network architecture shown in FIG1 ; the method can include the following steps:

[0121] Step 301: When the binding type of the binding relationship between the proxy device and the client device is long-term binding, the proxy device receives a user instruction to release the binding relationship.

[0122] In an embodiment of the present application, when the binding relationship is a long-term binding relationship, the proxy device may determine that the binding relationship satisfies the release condition when receiving a user instruction to release the binding relationship.

[0123] Step 302: The proxy device deletes the first binding device information corresponding to the client device in the first cluster of proxy devices.

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

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

[0126] Identification information of the client device;

[0127] Protocol version information of the client device;

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

[0129] Version information of the controllable device list.

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

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

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

[0133] Identification information of IoT devices;

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

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

[0136] The contents of the first cluster can be found in Tables 1 to 4 above, which will not be described in detail here.

[0137] In the embodiment of the present application, the agent device deleting the first binding device information corresponding to the client device in the first cluster of agent devices may refer to deleting the binding device information (bindingDeviceInfo) corresponding to the client device in the IOT Agent Binding Cluster.

[0138] Step 303: The proxy device sends an unbinding message to the client device; the client device receives the unbinding message.

[0139] In the embodiment of the present application, the unbinding message may be used to instruct the client device to delete the binding information corresponding to the binding relationship in the client device.

[0140] Among them, if the client device is regarded as the first device and the proxy device is regarded as the second device, then when the binding type of the binding relationship between the proxy device and the client device is long-term binding, the client device receives the unbinding message sent by the proxy device and can determine that the above binding relationship meets the unbinding condition.

[0141] The proxy device sending the unbinding message to the client device may be referred to as a unbinding relationship notification.

[0142] Step 304: The client device deletes the first client binding information corresponding to the proxy device in the second cluster of client devices.

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

[0144] Manufacturer information of the client device;

[0145] Device control capability information of the client device;

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

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

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

[0149] 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:

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

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

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

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

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

[0155] Identification information of the proxy device;

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

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

[0158] The second cluster and the information in the second cluster can be referred to in Tables 5 to 7 above, and will not be described in detail here.

[0159] In an embodiment of the present application, when a client device deletes the first client binding information corresponding to the proxy device in the second cluster of the client device, the client binding information (clientBindingInfo) corresponding to the proxy device in the IOT Client Cluster shown in Table 5 above may be deleted.

[0160] In a possible implementation, the client device may also delete a controllable device list stored in the client device; wherein the controllable device list includes device information of IoT devices that the client device supports controlling among IoT devices connected to the proxy device.

[0161] In an embodiment of the present application, when a user uses a client device to control the IoT devices connected to the proxy device with the proxy device as the agent, the user can first obtain a list of controllable devices from the proxy device, which includes the device information of each IoT device that the client device supports controlling among the IoT devices connected to the proxy device.

[0162] The device information of each IoT device is also referred to as controllable device information, which may include information of endpoints in the IoT device.

[0163] For example, the device information of each of the aforementioned IoT devices may be a device information list, and the content of the device information list may refer to Table 8 above.

[0164] Table 8

[0165] Identifier Name Type Description 0DeviceListList[device_Info]Device information list

[0166] The structure (struct) of device_Info in Table 8 above can refer to Table 9 below.

[0167] Table 9

[0168]

[0169] The structure of the endpoint information (endpoint_Info) in Table 9 above can refer to Table 10 below.

[0170] Table 10

[0171]

[0172] The structure of the cluster information (cluster_Info) in Table 10 above can refer to Table 11 below.

[0173] Table 11

[0174] Identifier Name Type Description 0clusterIDUint16 Device type (cluster identifier)

[0175] 1attributeList[attribute_Info] attribute set: device status 2commandList[command_Info] method set: start device behavior 3eventList[event_Info] event set: reported events

[0176] Among them, the method set in the above Table 11 includes specific functions of the corresponding device.

[0177] The events in Table 11 above may be events reported by an IoT device to other devices (eg, an APP), such as door lock_door not closed, etc.

[0178] The structure of the attribute information (attribute_Info) in Table 11 above can refer to Table 12 below.

[0179] Table 12

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

[0181] The structure of the method information (command_Info) in Table 11 above can refer to Table 13 below.

[0182] Table 13

[0183] Identifier Name Type Description 0commandIDUint16 Command Identifier

[0184] The structure of the event information (event_Info) in Table 11 above can refer to Table 14 below.

[0185] Table 14

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

[0187] In an embodiment of the present application, when the client device deletes the above binding relationship, the device information of each IoT device obtained from the proxy device can be deleted together.

[0188] To sum up, in an embodiment of the present application, when a long-term binding relationship has been established between the proxy device and the client device, the user can trigger the proxy device to cancel the above binding relationship to delete the binding information related to the binding relationship in the proxy device, and the proxy device can also notify the IoT device to cancel the above binding relationship, thereby achieving the effect of improving the security of device control and saving the device's memory resources.

[0189] For another example, taking the binding type of the above-mentioned binding relationship as long-term binding, and the user initiating unbinding from the client device side as an example, please refer to FIG4 , which shows a flowchart of a device unbinding method provided by an embodiment of the present application. The method can be interactively executed by a proxy device and a client device; for example, the proxy device can be the proxy device 120 in the network architecture shown in FIG1 , and the client device can be the client device 130 in the network architecture shown in FIG1 ; the method can include the following steps:

[0190] Step 401: When the binding type of the binding relationship between the proxy device and the client device is long-term binding, the client device receives a user instruction to release the binding relationship.

[0191] In an embodiment of the present application, when the binding relationship is a long-term binding relationship, the client device may determine that the binding relationship satisfies the release condition when receiving a user instruction to release the binding relationship.

[0192] Step 402: The client device deletes the first client binding information corresponding to the proxy device in the second cluster of client devices.

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

[0194] Manufacturer information of the client device;

[0195] Device control capability information of the client device;

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

[0197] 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:

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

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

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

[0201] Identification information of the proxy device;

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

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

[0204] The second cluster and the information in the second cluster can be referred to in Tables 5 to 7 above, and will not be described in detail here.

[0205] In an embodiment of the present application, when a client device deletes the first client binding information corresponding to the proxy device in the second cluster of the client device, the client binding information (clientBindingInfo) corresponding to the proxy device in the IOT Client Cluster shown in Table 5 above may be deleted.

[0206] In a possible implementation, the client device may also delete a controllable device list stored in the client device; wherein the controllable device list includes device information of IoT devices that the client device supports controlling among IoT devices connected to the proxy device.

[0207] The execution process of step 402 may refer to the description under step 304 in the embodiment shown in FIG. 3 , and will not be repeated here.

[0208] Step 403: The client device sends an unbinding message to the proxy device; the proxy device receives the unbinding message.

[0209] In the embodiment of the present application, the unbinding message may be used to instruct the proxy device to delete the binding information corresponding to the binding relationship in the proxy device.

[0210] Among them, if the proxy device is regarded as the first device and the client device is regarded as the second device, then when the binding type of the binding relationship between the proxy device and the client device is long-term binding, the proxy device receives the unbinding message sent by the client device and can determine that the above binding relationship meets the unbinding condition.

[0211] The unbinding message sent by the client device to the proxy device may be referred to as a binding relationship deletion request.

[0212] Step 404: The proxy device deletes the first bound device information corresponding to the client device in the first cluster of proxy devices.

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

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

[0215] Identification information of the client device;

[0216] Protocol version information of the client device;

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

[0218] Version information of the controllable device list.

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

[0220] Identification information of IoT devices;

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

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

[0223] The contents of the first cluster can be found in Tables 1 to 4 above, which will not be described in detail here.

[0224] In the embodiment of the present application, the agent device deleting the first binding device information corresponding to the client device in the first cluster of agent devices may refer to deleting the binding device information (bindingDeviceInfo) corresponding to the client device in the IOT Agent Binding Cluster.

[0225] The execution process of step 404 may refer to the description under step 302 in the embodiment shown in FIG. 3 , and will not be repeated here.

[0226] Optionally, after deleting the first bound device information corresponding to the client device in the first cluster of proxy devices, the proxy device may further return a notification of completion of terminating the binding relationship to the client device.

[0227] To summarize, in an embodiment of the present application, when a long-term binding relationship has been established between a proxy device and a client device, a user can trigger the client device to cancel the above-mentioned binding relationship to delete the binding information and device information list related to the binding relationship in the client device. In addition, the client device can also notify the proxy device to cancel the above-mentioned binding relationship, thereby achieving the effect of improving the security of device control and saving the memory resources of the device.

[0228] For another example, taking the binding type of the above-mentioned binding relationship as an example, which may be a short-term binding, please refer to FIG5 , which shows a flowchart of a device unbinding method provided by an 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:

[0229] Step 501: When the binding type of the binding relationship between the proxy device and the client device is temporary binding, the client device detects that the binding relationship meets a release condition.

[0230] In an embodiment of the present application, when the binding type of the binding relationship between the proxy device and the client device is temporary binding, the proxy device may not have binding information corresponding to the binding relationship. Accordingly, the client device only needs to cancel the binding relationship.

[0231] The release condition may be: when the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, a user instruction to release the binding relationship is received.

[0232] Alternatively, when the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, it is detected that the secure connection between the proxy device and the client device is lost.

[0233] Among them, when the binding type of the binding relationship between the proxy device and the client device is temporary binding, when the client device receives a user instruction initiated by the user to release the binding relationship (active release), or when the client device detects that the secure connection between the proxy device and the client device is lost (passive release), the client device can determine that the above binding relationship meets the release condition.

[0234] Step 502: The client device deletes the first client binding information corresponding to the proxy device in the second cluster of client devices.

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

[0236] Manufacturer information of the client device;

[0237] Device control capability information of the client device;

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

[0239] 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:

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

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

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

[0243] Identification information of the proxy device;

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

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

[0246] The second cluster and the information in the second cluster can be referred to in Tables 5 to 7 above, and will not be described in detail here.

[0247] In an embodiment of the present application, when a client device deletes the first client binding information corresponding to the proxy device in the second cluster of the client device, the client binding information (clientBindingInfo) corresponding to the proxy device in the IOT Client Cluster shown in Table 5 above may be deleted.

[0248] In a possible implementation, the client device may also delete a controllable device list stored in the client device; wherein the controllable device list includes device information of IoT devices that the client device supports controlling among IoT devices connected to the proxy device.

[0249] The execution process of step 502 may refer to the description under step 304 in the embodiment shown in FIG. 3 , and will not be repeated here.

[0250] Optionally, when the above release condition is that the binding type of the binding relationship between the proxy device and the client device is temporary binding, when the client device receives a user instruction to release the binding relationship, the client device may terminate the connection with the proxy device after releasing the above binding relationship.

[0251] To summarize, in an embodiment of the present application, when a temporary binding relationship has been established between a proxy device and a client device, the user can trigger the client device to cancel the above binding relationship, or the client device can cancel the above binding relationship when it detects that the secure connection between the proxy device and the client device is lost, thereby achieving the effect of improving the security of device control and saving the memory resources of the device.

[0252] In the solution involved in the embodiment of the present application, the above-mentioned unbinding relationship is divided into the unbinding of long-term binding relationship and the unbinding of temporary binding relationship. Long-term binding relationship can be divided into the unbinding relationship initiated by IOT Client and the unbinding relationship initiated by IOT Agent. Among them, since temporary binding is not recorded in the IOT Agent Binding cluster on the IOT Agent, the unbinding of temporary binding is divided into the unbinding initiated by the user on the IOT Client and the passive unbinding after the IOT Client detects the loss of connection. The unbinding relationship involved in the above embodiment of the present application may include the following steps:

[0253] 1. The user cancels the long-term binding from the client device:

[0254] S10: The user initiates the removal of the long-term binding relationship between the IOT Client and the IOT Agent on the IOT Client.

[0255] S11, the IOT Client deletes the binding information and device information list corresponding to the above long-term binding relationship in the IOT Client.

[0256] S12, the IOT Client notifies the IOT Agent to delete the binding information corresponding to the above long-term binding relationship in the IOT Agent Binding cluster.

[0257] S13, the IOT Agent deletes the binding information corresponding to the above long-term binding relationship.

[0258] S14, the IOT Agent notifies the IOT Client that the above long-term binding relationship has been deleted.

[0259] 2. User cancels long-term binding from the proxy device:

[0260] S20: The user initiates the cancellation of the long-term binding relationship between the IOT Client and the IOT Agent on the IOT Agent.

[0261] S21, the IOT Agent deletes the binding information corresponding to the above long-term binding relationship in the IOT Agent Binding cluster.

[0262] S22, the IOT Agent notifies the IOT Client to delete the above long-term binding relationship.

[0263] S23, the IOT Agent deletes the binding information and device information list corresponding to the above long-term binding relationship in the IOT Client.

[0264] 3. The user cancels the temporary binding from the client device:

[0265] S30: When the user actively initiates to end the binding relationship, the IOT Client deletes the binding information and device information list corresponding to the temporary binding in the IOT Client.

[0266] S31, IOT Client initiates the connection termination.

[0267] 4. The client device automatically cancels the temporary binding:

[0268] S40: The IOT Client detects that the secure connection is lost.

[0269] S41, the IOT Client automatically deletes the binding information and device information list corresponding to the temporary binding in the IOT Client.

[0270] Please refer to Figure 6, which shows a block diagram of a device unbinding device provided by an embodiment of the present application. The device unbinding device 600 has the function of implementing the method shown in any of Figures 2 to 5 above, which is performed by the proxy device or the client device. As shown in Figure 7, the device may include:

[0271] Deletion module 601 is configured to delete binding information corresponding to a binding relationship between a proxy device and a client device in a first device when the binding relationship between the proxy device and the client device satisfies an unbinding condition; the binding relationship is used by the client device to control the IoT device connected to the proxy device through the proxy device; and the first device is one of the proxy device and the client device.

[0272] In a possible implementation, the deleting module 601 is configured to delete, when the first device is the proxy device, the first bound device information corresponding to the client device in the first cluster of proxy devices.

[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 deleting module 601 is configured to, when the first device is the client device, delete the first client binding information corresponding to the proxy device in the second cluster of client devices.

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

[0283] identification information of the proxy device;

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

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

[0286] In a possible implementation, the deletion module 601 is further used to delete the controllable device list stored in the client device; the controllable device list includes device information of the IoT devices connected to the proxy device and supported by the client device for control.

[0287] In a possible implementation, the unbinding condition includes: when the binding type of the binding relationship between the proxy device and the client device is long-term binding, receiving a user instruction to release the binding relationship.

[0288] In a possible implementation, the unbinding condition includes: when the binding type of the binding relationship between the proxy device and the client device is long-term binding, receiving an unbinding message sent by the second device.

[0289] In a possible implementation, the unbinding condition includes: when the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, receiving a user instruction to release the binding relationship.

[0290] In a possible implementation, the unbinding condition includes: when the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, detecting that the secure connection between the proxy device and the client device is lost.

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

[0292] A sending module is configured to send an unbinding message to a second device when the unbinding condition is that the binding type of the binding relationship between the proxy device and the client device is long-term binding and a user instruction to unbind the binding relationship is received; the second device is another device between the proxy device and the client device other than the first device; and the unbinding message is used to indicate deletion of binding information corresponding to the binding relationship.

[0293] Please refer to FIG7 , which shows a schematic diagram of the structure of a computer device 700 provided in one embodiment of the present application. The computer device 700 may include: a processor 701 , a receiver 702 , a transmitter 703 , a memory 704 , and a bus 705 .

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

[0295] The receiver 702 and the transmitter 703 may be implemented as a communication component, which may be a communication chip, which may also be called a transceiver.

[0296] The memory 704 is connected to the processor 701 via a bus 705 .

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

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

[0299] In an exemplary scenario, when the computer device 700 is implemented as the above-mentioned first device, the receiving processor is used to delete the binding information corresponding to the binding relationship in the first device when the binding relationship between the proxy device and the client device meets the unbinding condition; 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; the first device is one of the proxy device and the client device.

[0300] The process executed by the processor 701 and / or the transceiver in the computer device 700 may refer to the steps executed by the proxy device or the client device in any of the methods shown in FIG. 2 to FIG. 5 .

[0301] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement all or part of the steps performed by the proxy device or the client device in any of the methods shown in Figures 2 to 5 above.

[0302] 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 any of the methods shown in Figures 2 to 5 above.

[0303] 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 the client device in any of the methods shown in Figures 2 to 5 above.

[0304] 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 any of the methods shown in Figures 2 to 5 above.

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

[0306] 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 unbinding method, characterized in that: The method is performed by a first device, which is one of a proxy device and a client device; the method includes: When the binding relationship between the proxy device and the client device meets the unbinding condition, the binding information corresponding to the binding relationship in the first device is deleted; the binding relationship is used by 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 In a case where the first device is the proxy device, the deleting the binding information corresponding to the binding relationship in the first device includes: The first binding device information corresponding to the client device in the first cluster of the proxy devices is deleted.

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 claim 1, wherein In a case where the first device is the client device, the deleting the binding information corresponding to the binding relationship in the first device includes: The first client binding information corresponding to the proxy device in the second cluster of client devices is deleted.

6. The method according to claim 5, 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.

7. The method according to claim 5 or 6, characterized in that The method further comprises: Delete the controllable device list stored in the client device; the controllable device list includes device information of the Internet of Things devices connected to the proxy device and the Internet of Things devices that the client device supports controlling.

8. The method according to any one of claims 1 to 7, characterized in that: The unbinding conditions include: In a case where the binding type of the binding relationship between the proxy device and the client device is long-term binding, a user instruction to release the binding relationship is received.

9. The method according to any one of claims 1 to 7, characterized in that: The unbinding conditions include: In a case where the binding type of the binding relationship between the proxy device and the client device is long-term binding, an unbinding message sent by the second device is received.

10. The method according to any one of claims 1 to 7, characterized in that: The unbinding conditions include: In a case where the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, a user instruction to release the binding relationship is received.

11. The method according to any one of claims 1 to 7, characterized in that: The unbinding conditions include: When the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, it is detected that the secure connection between the proxy device and the client device is lost.

12. The method according to claim 11, characterized in that When the unbinding condition is that the binding type of the binding relationship between the proxy device and the client device is long-term binding, and a user instruction to unbind the binding relationship is received, the method further includes: An unbinding message is sent to a second device; the second device is another device among the proxy device and the client device except the first device; the unbinding message is used to instruct deletion of binding information corresponding to the binding relationship.

13. A device unbinding device, characterized in that: The device comprises: A deletion module is configured to delete binding information corresponding to a binding relationship between a proxy device and a client device in a first device when the binding relationship between the proxy device and the client device satisfies an unbinding condition; the binding relationship is used by the client device to control the IoT device connected to the proxy device through the proxy device; and the first device is one of the proxy device and the client device.

14. The device according to claim 13, characterized in that The deleting module is configured to, when the first device is the proxy device, The first binding device information corresponding to the client device in the first cluster of the proxy devices is deleted.

15. The device according to claim 14, 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.

16. The device according to claim 15, 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.

17. The device according to claim 13, characterized in that The deleting module is configured to delete the first client binding information corresponding to the proxy device in the second cluster of client devices when the first device is the client device.

18. The device according to claim 17, 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.

19. The device according to claim 17 or 18, characterized in that The deletion module is further used to delete the controllable device list stored in the client device; the controllable device list includes device information of the Internet of Things devices connected to the proxy device and supported by the client device for control.

20. The device according to any one of claims 13 to 19, characterized in that The unbinding conditions include: In a case where the binding type of the binding relationship between the proxy device and the client device is long-term binding, a user instruction to release the binding relationship is received.

21. The device according to any one of claims 13 to 19, characterized in that The unbinding conditions include: In a case where the binding type of the binding relationship between the proxy device and the client device is long-term binding, an unbinding message sent by the second device is received.

22. The device according to any one of claims 13 to 19, characterized in that The unbinding conditions include: In a case where the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, a user instruction to release the binding relationship is received.

23. The device according to any one of claims 13 to 19, characterized in that The unbinding conditions include: When the binding type of the binding relationship between the proxy device and the client device is temporary binding and the first device is the client device, it is detected that the secure connection between the proxy device and the client device is lost.

24. The device according to claim 23, characterized in that The device further comprises: A sending module is configured to send an unbinding message to a second device when the unbinding condition is that the binding type of the binding relationship between the proxy device and the client device is long-term binding and a user instruction to unbind the binding relationship is received; the second device is another device between the proxy device and the client device other than the first device; and the unbinding message is used to indicate deletion of binding information corresponding to the binding relationship.

25. 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 unbinding method as described in any one of claims 1 to 12 above.

26. 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 unbinding method according to any one of claims 1 to 12.

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

28. 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 unbinding method as described in any one of claims 1 to 12.

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

Images