Proxy binding methods and apparatuses, and device, storage medium and product

Abstract

Proxy binding methods and apparatuses, and a device, a storage medium and a product, which belong to the technical field of Internet of Things (IoT). A proxy binding method, executed by a proxy device, comprises: sending to a client device a proxy binding request (301), which is used for binding a first proxy in a proxy device to the client device, wherein the first proxy is one of a plurality of IoT proxies in the proxy device, the proxy binding request includes description information of the first proxy, and the description information is used for describing the first proxy in binding information stored in the client device.

Description

Proxy binding method, device, equipment, storage medium and product Technical Field

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

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

[0003] In related technologies, an IoT agent may be installed in a user's mobile phone, and the IoT agent may be bound to a client device so that subsequent client devices may implement client functions through the IoT agent.

[0004] Summary of the Invention

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

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

[0007] Sending a proxy binding request to a client device, wherein the proxy binding request is used to bind a first proxy in the proxy device to the client device;

[0008] The first agent is one of multiple IoT agents in the agent device; the agent binding request includes description information of the first agent; and the description information is used to describe the first agent in the binding information stored in the client device.

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

[0010] Receiving a proxy binding request sent by a proxy device, the proxy binding request being used to bind a first proxy in the proxy device to the client device; the first proxy being one of a plurality of IoT proxies in the proxy device; the proxy binding request including description information of the first proxy;

[0011] Binding information is established, where the binding information is used to indicate a binding relationship between the first agent and the client device, and the binding information includes the description information.

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

[0013] a sending module, configured to send a proxy binding request to a client device, wherein the proxy binding request is used to bind a first proxy in the proxy device to the client device;

[0014] The first agent is one of multiple IoT agents in the agent device; the agent binding request includes description information of the first agent; and the description information is used to describe the first agent in the binding information stored in the client device.

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

[0016] A receiving module, configured to receive a proxy binding request sent by a proxy device, wherein the proxy binding request is used to bind a first proxy in the proxy device to a client device; the first proxy is one of a plurality of IoT proxies in the proxy device; and the proxy binding request includes description information of the first proxy;

[0017] The binding module is configured to establish binding information, where the binding information is used to indicate a binding relationship between the first agent and the client device, and the binding information includes the description information.

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

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

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

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

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

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

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

[0025] Through the technical solution provided by the embodiments of the present application, when the proxy device sends a request to the client device to bind the first proxy in the proxy device with the client device, the request carries description information of the first proxy. When the user subsequently views the bound proxies on the client device side, the description information can be used to distinguish which proxy in the proxy device the first proxy is. This makes it applicable to scenarios in which the client device is bound to multiple proxies in a proxy device, thereby improving the applicable scenarios of proxy binding. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0029] FIG4 is a flowchart of a proxy binding method provided by an embodiment of the present application;

[0030] FIG5 is a process framework diagram of proxy binding provided by one embodiment of the present application;

[0031] FIG6 is a flowchart of an IoT agent binding vehicle computer involved in this application;

[0032] FIG7 is a flowchart of another IoT agent binding vehicle computer involved in this application;

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

[0034] FIG9 is a block diagram of a proxy binding device provided by one embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] 1) IoT agent discovery and binding

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

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

[0058] ②IOTAgent discovers the identifier of the IoTClient cluster of the IOTClient and determines whether it supports access to smart home capabilities;

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

[0060] ④[optional]IOTAgent obtains the device list supported by IOTClient: supporteddevicetype;

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

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

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

[0064] ⑧Notify IOTClient of the binding type;

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

[0066] 2) IoTClient cluster

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

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

[0069] Table 1

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

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

[0072] Table 2

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

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

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

[0076] Table 3

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

[0078] The above solution only considers the case where there is only one IoT agent in the mobile phone bound to the car. However, in practice, multiple IoT agents may run on the mobile phone, each corresponding to a different smart home app. The above solution is not suitable for the case where multiple IoT agents are bound to the car.

[0079] Please refer to FIG3 , which shows a flow chart of a proxy binding method provided by one 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:

[0080] Step 301: Send a proxy binding request to a client device. The proxy binding request is used to bind a first proxy in the proxy device to the client device. The first proxy is one of multiple IoT proxies in the proxy device. The proxy binding request includes description information of the first proxy. The description information is used to describe the first proxy in binding information stored on the client device.

[0081] The description information may be information that introduces the first agent, and is used to describe the first agent so that the user can intuitively understand which agent the first agent is.

[0082] The proxy device may be installed with multiple IoT agents, each of which may be an application, or the IoT agent may be implemented as a part of the functionality of an application.

[0083] The binding of the first agent to the client device may be establishing a binding relationship between the first agent and the client device in the client device, for example, adding binding information indicating the binding relationship between the first agent and the client device in the client device.

[0084] In an embodiment of the present application, a first agent in a proxy device, or an application corresponding to the first agent, may send a proxy binding request to a client device to request that the first agent be bound to the client device. Furthermore, the proxy binding request may carry description information of the first agent, so that when binding the first agent, the client device may also store the description information of the first agent, thereby facilitating a subsequent user on the client device side to more intuitively understand which agent in the proxy device the first agent represents.

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

[0086] When the first agent discovers the client device, a binding notification is triggered; the binding notification is used to indicate whether to determine to bind the first agent to the client device;

[0087] The above-mentioned sending of a proxy binding request to the client device includes:

[0088] When a binding instruction is obtained, an agent binding request is sent to the client device; the binding instruction is an instruction generated by triggering an operation to bind the first agent to the client device based on the binding notification.

[0089] In some embodiments, the proxy binding request further includes binding type information and identification information of the first proxy, where the binding type information is used to indicate the binding type between the first proxy and the client device;

[0090] The binding type includes long-term binding or temporary binding.

[0091] In some embodiments, the binding instruction is further used to indicate the binding type.

[0092] In some embodiments, the description information includes one or more of the following information:

[0093] Manufacturer information of the first agent;

[0094] Label information of the first agent.

[0095] In some embodiments, when the description information includes tag information of the first agent, the method further includes:

[0096] Displaying a label setting interface, which includes label setting items for the first agent;

[0097] According to the setting operation in the tag setting item, the tag information of the first agent is obtained.

[0098] To summarize, in the solution shown in the embodiment of the present application, when the proxy device sends a request to the client device to bind the first proxy in the proxy device with the client device, the request carries description information of the first proxy. When the user subsequently views the bound proxies on the client device side, the description information can be used to distinguish which proxy in the proxy device the first proxy is, thereby being applicable to scenarios in which the client device is bound to multiple proxies in a proxy device, thereby improving the applicable scenarios of proxy binding.

[0099] Please refer to FIG4 , which shows a flowchart of a proxy binding method provided by one embodiment of the present application. The method may be executed by a client device, for example, the client device may be the vehicle 130 or the IoT device 110 in the network architecture shown in FIG1 . The method may include the following steps:

[0100] Step 401: Receive a proxy binding request sent by a proxy device, where the proxy binding request is used to bind a first proxy in the proxy device to a client device; the first proxy is one of multiple IoT proxies in the proxy device; and the proxy binding request includes description information of the first proxy.

[0101] Step 402: Establish binding information, where the binding information is used to indicate a binding relationship between the first proxy and the client device, and the binding information includes description information.

[0102] In some embodiments, the proxy binding request and the binding information further include binding type information and identification information of the first proxy, where the binding type information is used to indicate the binding type between the first proxy and the client device.

[0103] In some embodiments, the client device includes a client functional unit; the client functional unit indicates an IoT agent bound to the client device;

[0104] The above binding information includes:

[0105] Establish binding information in the client functional unit.

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

[0107] When displaying the binding relationship between the first agent and the client device, description information is displayed.

[0108] To summarize, in the solution shown in the embodiment of the present application, when the proxy device sends a request to the client device to bind the first proxy in the proxy device with the client device, the request carries description information of the first proxy. The client device can establish binding information containing the description information based on the request. When the user subsequently views the bound proxies on the client device side, the description information can be used to distinguish which proxy in the proxy device the first proxy is, thereby being applicable to scenarios in which the client device is bound to multiple proxies in a proxy device, thereby improving the applicable scenarios of proxy binding.

[0109] Please refer to FIG5 , which shows a flowchart of a proxy binding method provided by one embodiment of the present application. The method can be interactively executed by a proxy device and a client device. For example, the proxy device can be the proxy device 120 in the network architecture shown in FIG1 , and the client device can be the vehicle 130 or the IoT device 110 in the network architecture shown in FIG1 . The method can include the following steps:

[0110] Step 501: When a first agent discovers a client device, the agent device triggers a binding notification; the binding notification is used to indicate whether to determine to bind the first agent to the client device.

[0111] The first agent is one of multiple Internet of Things (IoT) agents in the agent device.

[0112] In an embodiment of the present application, multiple IoT agents in the proxy device can respectively execute the discovery process of the client device.

[0113] For example, multiple IoT agents in a proxy device can respectively send a first device discovery signal, such as a WiFi wireless signal or a Bluetooth wireless signal, through the short-range wireless communication component of the proxy device. The first device discovery signal can include information about the IoT agent (such as identification information of the IoT agent and identification information of the proxy device). After the client device receives the first device discovery signal sent by an IoT agent, if it determines that a binding relationship has not been established with the IoT agent, it can return a first device discovery response to the proxy device. The first device discovery response can include device information of the client device. After receiving the first device discovery response, the IoT agent determines that a client device that can be bound has been found.

[0114] For another example, the client device may send a second device discovery signal, which may include information about the client device, such as identification information of the client device. After receiving the device discovery signal, the proxy device sends the information about the client device in the device discovery signal to multiple IoT proxies respectively. When the IoT proxy determines that it has not yet bound to the client device based on the information of the client device, it can determine that a client device that can be bound has been found.

[0115] Among them, after the first IoT agent discovers a client device that can be bound, it can trigger the display of a binding notification in the agent device. The user can use the binding notification to trigger the binding process between the first agent and the client device, or trigger not to perform the binding between the first agent and the client device.

[0116] Step 502: After obtaining the binding instruction, the proxy device sends a proxy binding request to the client device. Accordingly, the client device receives the proxy binding request. The proxy binding request includes description information of the first proxy.

[0117] The binding instruction is an instruction generated by triggering an operation to bind the first agent to the client device, which is executed based on the binding notification.

[0118] For example, after the proxy device displays the above-mentioned binding notification, the user can click on the binding notification to trigger the proxy device to display a binding interface. The binding interface may display a control for confirming the binding and a control for canceling the binding. If the user is sure that the first proxy is to be bound to the client device, the user can click on the control for confirming the binding, thereby triggering the generation of a binding instruction. If the user is sure that the first proxy does not need to be bound to the client device, the user can click on the control for canceling the binding, and no binding instruction will be generated at this time.

[0119] The first agent in the agent device may generate an agent binding request after obtaining the binding instruction generated by the agent device, wherein the agent binding request includes the description information of the first agent.

[0120] In some embodiments, the proxy binding request further includes binding type information and identification information of the first proxy, where the binding type information is used to indicate the binding type between the first proxy and the client device;

[0121] The binding type includes long-term binding or temporary binding.

[0122] In some embodiments, the binding instruction is further used to indicate the binding type.

[0123] The identification information of the first agent may include the identification of the first agent (such as the node ID of the first agent) and the identification of the agent device (such as the name of the agent device, the node ID, etc.).

[0124] The above-mentioned binding type can be set by the user. For example, in the above-mentioned binding interface, the control for determining binding may include a control for long-term binding and a control for temporary binding. If the user determines that the first agent wants to bind the client device to the long-term binding, the user may click the control for long-term binding. In this case, the first agent may obtain a binding instruction indicating long-term binding, and the proxy binding request generated by the first agent may include binding type information indicating long-term binding; alternatively, if the user determines that the first agent wants to bind the client device to the temporary binding, the user may click the control for temporary binding. In this case, the first agent may obtain a binding instruction indicating temporary binding, and the proxy binding request generated by the first agent may include binding type information indicating temporary binding.

[0125] In some embodiments, the binding type may also be determined by other means besides the binding interface. For example, the first agent may default to long-term binding or temporary binding. In this case, the binding type information in the proxy binding request generated by the first agent fixedly indicates long-term binding or temporary binding. For another example, after receiving the binding instruction, the first agent may display a binding type setting interface, in which the user may set the binding type. The first agent may then set the binding type information in the proxy binding request based on the binding type set by the user in the binding type setting interface.

[0126] In some embodiments, the description information includes one or more of the following information:

[0127] Manufacturer information of the first agent;

[0128] Label information of the first agent.

[0129] The description information of the first agent may include the manufacturer information of the first agent, so that when a user subsequently views the first agent in a client device, he or she can intuitively know which manufacturer's IoT agent the first agent is from.

[0130] The description information of the first agent may also include tag information of the first agent, so that when a user subsequently views the first agent in a client device, the user can intuitively know which of the multiple IoT agents of the agent device the first agent is through the tag information.

[0131] The tag information may be information preset in the first agent, or the tag information may be information customized by the user.

[0132] In some embodiments, when the description information includes tag information of the first agent, the method further includes:

[0133] Displaying a label setting interface, which includes label setting items for the first agent;

[0134] According to the setting operation in the tag setting item, the tag information of the first agent is obtained.

[0135] In the implementation of this application, the user can set label information for each IoT agent in the proxy device in advance. For example, when the IoT agent in the proxy device is installed or started for the first time, the user can be prompted to set the label information of the IoT agent, that is, the above-mentioned label setting interface is displayed, and the user enters the label information of the first agent in the label setting interface. The label information can be one or more paragraphs of text used to describe the first agent.

[0136] Alternatively, the tag information may be set when the first agent is bound to the client device. For example, when the first agent discovers a bindable client device and the user decides to bind the first agent to the client device, the tag setting interface may be displayed, and the user may enter the tag information of the first agent in the tag setting interface. The tag setting interface may be the binding interface or the binding type setting interface, or may be a setting interface different from the binding interface and the binding type setting interface.

[0137] Step 503: The client device establishes binding information, where the binding information is used to indicate a binding relationship between the first agent and the client device. The binding information includes description information.

[0138] In an embodiment of the present application, when establishing a binding relationship between the first agent and the client device, the client device may generate and store binding information indicating the binding relationship between the first agent and the client device in the client device, and write the description information of the first agent into the description information.

[0139] In some embodiments, the client device includes a client functional unit; the client functional unit indicates an IoT agent bound to the client device;

[0140] Establish binding information, including:

[0141] Establish binding information in the client functional unit.

[0142] For example, the client functional unit may be an IOT Client Cluster, and the binding information may be clientBindingInfo in the IOT Client Cluster. That is, a field is added to the clientBindingInfo structure to store the description information of the corresponding IoT agent.

[0143] For example, the clientBindingInfo structure may be as shown in Table 4 below.

[0144] Table 4

[0145] Step 504: The client device displays description information when displaying the binding relationship between the first agent and the client device.

[0146] In an embodiment of the present application, after the client device is bound to the first agent, the user can subsequently view the binding relationship between the first agent and the client device on the client device side. At this time, the client device can display the description information of the first agent so that the user can intuitively distinguish which IoT agent the first agent is.

[0147] Based on the above embodiment, the solution shown in the above embodiment is introduced below by taking the proxy device being the user's mobile phone and the client device being the vehicle computer device in the vehicle as an example.

[0148] Option 1:

[0149] When setting up a binding relationship, the IoT agent writes its own vendor ID, which is then stored in the IOTClient by the vehicle. After obtaining the IoTAgent's device list, the IOTClient matches the IoT devices in the list with the IoT agent's vendor ID. When displaying the information to the user, the vendor ID can be used to distinguish the devices, helping them identify the source of the IoT device information.

[0150] The clientBindingInfo structure is defined as shown in Table 5 below.

[0151] Table 5

[0152] VendorID represents the vendor identifier of the IoT agent. For example, a mobile phone contains two smart home apps, one from manufacturer A and one from manufacturer B. Each app implements an IoT agent. The VendorIDs of the two IoT agents are the identifiers of manufacturer A and manufacturer B, respectively.

[0153] In the above case, the user can connect to the car through the mobile phone and select the IoT agent to bind with the car client. Please refer to Figure 6, which shows a flowchart of an IoT agent binding car client involved in this application. The process can be as follows:

[0154] 1) Establish a connection between the phone and the car.

[0155] 2) IOTAgent discovers the identifier of the IoTClient cluster of the IOTClient and determines whether it supports access to smart home capabilities.

[0156] 3) Returns the protocol version supported by IOTClient: version id. Optionally, IOTAgent can further obtain the list of devices supported by IOTClient.

[0157] 4) IOTAgent pushes a notification to the user, informing them that the smart home client on the car has been discovered.

[0158] 5) When the user receives notification that two IOTAgents have discovered the client, they can choose to bind both IOTAgents to the client, or just one of them.

[0159] 6) The user selects IOTAgent from manufacturer A and sets the binding type to long-term binding.

[0160] 7) Manufacturer A's IOTAgent sends the agentID, VendorID, and binding type to the IOTClient for binding.

[0161] 8) After receiving the message, IOTClient binds it and saves the information of IOTAgent based on the long-term binding relationship.

[0162] 9) The user can also select IOTAgent from manufacturer B and set the binding type to temporary binding.

[0163] 10) Manufacturer B's IOTAgent sends the agentID, VendorID, and binding type to the IOTClient for binding.

[0164] 11) After receiving the message, IOTClient binds it and saves the information of IOTAgent based on the temporary binding relationship.

[0165] After binding, the IOTClient can retrieve the IoT devices managed by the smart home apps corresponding to the two IoTAgents and display them in the controllable device list on the control interface. Furthermore, the IOTClient can find the corresponding vendor information based on the VendorIDs of the two IoTAgents and display the controllable devices based on the vendor information, for example, by adding the logo of vendor A or vendor B to the device icon.

[0166] Option 2:

[0167] When setting up a binding relationship, the IoT agent writes the IoT agent's tag, which is then stored by the vehicle in the IOTClient. After obtaining the IoTAgent's device list, the IOTClient matches the IoT devices in the list with the IoT agent's tag. When displaying the device list to the user, the tag information can be used to distinguish the devices, helping users identify the source of the IoT device information.

[0168] The clientBindingInfo structure is defined as shown in Table 6 below.

[0169] Table 6

[0170] The agentTag above represents a user-defined tag for an IoT agent. For example, a mobile phone contains two smart home apps, A and B. Each app implements an IoT agent. The user can set the tags "A" and "B" for the two IoT agents, respectively.

[0171] In the above case, the user can connect to the car through the mobile phone and select the IoT agent to bind with the car client. Please refer to Figure 7, which shows another flow chart of binding the IoT agent to the car involved in this application. The process can be as follows:

[0172] 1) Establish a connection between the phone and the car.

[0173] 2) IOTAgent discovers the identifier of the IoTClient cluster of the IOTClient and determines whether it supports access to smart home capabilities.

[0174] 3) Returns the protocol version supported by IOTClient: version id. Optionally, IOTAgent can further obtain the list of devices supported by IOTClient.

[0175] 4) IOTAgent pushes a notification to the user, informing them that the smart home client on the car has been discovered.

[0176] 5) When the user receives notification that two IOTAgents have discovered the client, they can choose to bind both IOTAgents to the client, or just one of them.

[0177] 6) The user selects IOTAgent A, sets the binding type to long-term binding, and sets the label “Factory A Home” for it.

[0178] 7) A's IOTAgent sends the agentID, label "A Factory Home", and binding type to the IOTClient for binding.

[0179] 8) After receiving the message, IOTClient binds it and saves the information of IOTAgent based on the long-term binding relationship.

[0180] 9) The user can also select B's IOTAgent, set the binding type to temporary binding, and set the label "B Factory Home" for it.

[0181] 10) Manufacturer B's IOTAgent sends the agentID, label "Manufacturer B Home", and binding type to the IOTClient for binding.

[0182] 11) After receiving the message, IOTClient binds it and saves the information of IOTAgent based on the temporary binding relationship.

[0183] After binding, the IOTClient can retrieve the IoT devices managed by the smart home apps corresponding to the two IoTAgents and display them in the controllable device list on the control interface. Furthermore, the IOTClient can display controllable devices based on the tags of the two IoTAgents. For example, the lists "Factory A Home" and "Factory B Home" can contain devices from IoTAgents A and B, respectively; or the tags "Factory A Home" or "Factory B Home" can be displayed under each device icon.

[0184] The above solution introduces a multi-IoT proxy binding process and adds a proxy tag in the binding information, so that the vehicle client can support binding multiple IoT proxies on the mobile phone and display the proxy IoT device control interface to the user according to its source.

[0185] Please refer to Figure 8, which shows a block diagram of a proxy binding device provided by an embodiment of the present application. The proxy binding device 800 has the functions of implementing the methods shown in Figures 3, 4, or 5 above, which are performed by the proxy device. As shown in Figure 8, the device may include:

[0186] A sending module 801 is configured to send a proxy binding request to a client device, wherein the proxy binding request is used to bind a first proxy in the proxy device to the client device;

[0187] The first agent is one of multiple IoT agents in the agent device; the agent binding request includes description information of the first agent; and the description information is used to describe the first agent in the binding information stored in the client device.

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

[0189] a notification module, configured to trigger a binding notification when the first agent discovers the client device; the binding notification is used to indicate whether to determine to bind the first agent to the client device;

[0190] The sending module is configured to send the agent binding request to the client device when a binding instruction is obtained; the binding instruction is an instruction triggered by an operation executed based on the binding notification to determine the binding of the first agent with the client device.

[0191] In some embodiments, the proxy binding request further includes binding type information and identification information of the first proxy, where the binding type information is used to indicate a binding type between the first proxy and the client device;

[0192] The binding type includes long-term binding or temporary binding.

[0193] In some embodiments, the binding instruction is further used to indicate the binding type.

[0194] In some embodiments, the description information includes one or more of the following information:

[0195] Manufacturer information of the first agent;

[0196] Label information of the first agent.

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

[0198] an interface display module, configured to display a label setting interface including label setting items of the first agent when the description information includes label information of the first agent;

[0199] The tag acquisition module is used to acquire the tag information of the first agent according to the setting operation in the tag setting item.

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

[0201] A receiving module 901 is configured to receive a proxy binding request sent by a proxy device, wherein the proxy binding request is used to bind a first proxy in the proxy device to a client device; the first proxy is one of multiple IoT proxies in the proxy device; and the proxy binding request includes description information of the first proxy.

[0202] The binding module 902 is configured to establish binding information, where the binding information is used to indicate a binding relationship between the first agent and the client device, and the binding information includes the description information.

[0203] In some embodiments, the proxy binding request and the binding information further include binding type information and identification information of the first proxy, where the binding type information is used to indicate a binding type between the first proxy and the client device.

[0204] In some embodiments, the client device includes a client functional unit; the client functional unit indicates an IoT agent bound to the client device;

[0205] The binding module is used to establish the binding information in the client functional unit.

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

[0207] The display module is configured to display the description information when displaying the binding relationship between the first agent and the client device.

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

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

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

[0211] In an exemplary embodiment, when computer device 1000 is implemented as the aforementioned proxy device, the processor 1001 and / or transceiver is configured to send a proxy binding request to a client device, wherein the proxy binding request is configured to bind a first proxy in the proxy device to the client device; wherein the first proxy is one of multiple IoT proxies in the proxy device; the proxy binding request includes description information of the first proxy; and the description information is configured to describe the first proxy in the binding information stored by the client device. The process executed by processor 1001 and / or transceiver in computer device 1000 may refer to the steps executed by the proxy device in the method shown in either FIG. 3 or FIG. 5 .

[0212] In an exemplary embodiment, when the computer device 1000 is implemented as a client device, the processor 1001 and / or transceiver is configured to receive a proxy binding request sent by a proxy device, wherein the proxy binding request is configured to bind a first proxy in the proxy device to a client device; the first proxy is one of multiple IoT proxies in the proxy device; the proxy binding request includes description information of the first proxy; and binding information is established, wherein the binding information is configured to indicate a binding relationship between the first proxy and the client device, and the binding information includes the description information. The process performed by the processor 1001 and / or transceiver in the computer device 1000 may refer to the steps performed by the client device in the method shown in either FIG. 4 or FIG. 5 .

[0213] 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 the method shown in Figure 3, Figure 4 or Figure 5 above.

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

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

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

Claims

1. A proxy binding method, characterized in that, the method is executed by a proxy device, and the method includes: sending a proxy binding request to a client device, where the proxy binding request is used to bind a first proxy in the proxy device to the client device; wherein, the first proxy is one of multiple Internet of Things (IoT) proxies in the proxy device; the proxy binding request contains description information of the first proxy; the description information is used to describe the first proxy in the binding information stored in the client device.

2. The method according to claim 1, characterized in that, the method further includes: triggering a binding notification when the first proxy discovers the client device; the binding notification is used to indicate whether it is determined to bind the first proxy to the client device; the sending a proxy binding request to the client device includes: sending the proxy binding request to the client device when a binding instruction is obtained; the binding instruction is an instruction generated by an operation that determines to bind the first proxy to the client device and is executed based on the binding notification.

3. The method according to claim 2, characterized in that, the proxy binding request further includes binding type information and identification information of the first proxy, and the binding type information is used to indicate the binding type between the first proxy and the client device; wherein, the binding type includes long-term binding or temporary binding.

4. The method according to claim 3, characterized in that, the binding instruction is further used to indicate the binding type.

5. The method according to any one of claims 1 to 4, characterized in that, the description information includes one or more of the following information: manufacturer information of the first proxy; tag information of the first proxy.

6. The method according to claim 5, characterized in that, when the description information includes the tag information of the first proxy, the method further includes: displaying a tag setting interface, where the tag setting interface includes a tag setting item for the first proxy; obtaining the tag information of the first proxy according to a setting operation in the tag setting item.

7. A proxy binding method, characterized in that, the method is executed by a client device, and the method includes: receiving a proxy binding request sent by a proxy device, where the proxy binding request is used to bind a first proxy in the proxy device to the client device; the first proxy is one of multiple Internet of Things (IoT) proxies in the proxy device; the proxy binding request contains description information of the first proxy; establishing binding information, where the binding information is used to indicate the binding relationship between the first proxy and the client device, and the binding information includes the description information.

8. The method according to claim 7, characterized in that, the proxy binding request and the binding information further include binding type information and identification information of the first proxy, and the binding type information is used to indicate the binding type between the first proxy and the client device.

9. The method according to claim 7 or 8, wherein, the client device includes a client function unit; the client function unit instructs an IoT agent bound to the client device; the establishment of the binding information includes: establishing the binding information in the client function unit.

10. The method according to any one of claims 7 to 9, wherein, the method further includes: when displaying the binding relationship between the first agent and the client device, displaying the description information.

11. An agent binding device, wherein, the device includes: a sending module, configured to send an agent binding request to a client device, where the agent binding request is used to bind a first agent in the agent device to the client device; wherein, the first agent is one of multiple Internet of Things (IoT) agents in the agent device; the agent binding request includes description information of the first agent; the description information is used to describe the first agent in the binding information stored in the client device.

12. The device according to claim 11, wherein, the device further includes: a notification module, configured to trigger a binding notification when the first agent discovers the client device; the binding notification is used to indicate whether to determine to bind the first agent to the client device; the sending module, configured to send the agent binding request to the client device when a binding instruction is obtained; the binding instruction is an instruction generated by an operation that determines to bind the first agent to the client device and is executed based on the binding notification.

13. The device according to claim 12, wherein, the agent binding request further includes binding type information and identification information of the first agent, and the binding type information is used to indicate the binding type between the first agent and the client device; wherein, the binding type includes long-term binding or temporary binding.

14. The device according to claim 13, wherein, the binding instruction is further used to indicate the binding type.

15. The device according to any one of claims 11 to 14, wherein, the description information includes one or more of the following information: manufacturer information of the first agent; tag information of the first agent.

16. The device according to claim 15, wherein, the device further includes: an interface display module, configured to display a tag setting interface when the description information includes the tag information of the first agent, and the tag setting interface includes a tag setting item for the first agent; a tag acquisition module, configured to acquire the tag information of the first agent according to a setting operation in the tag setting item.

17. An agent binding device, wherein, the device includes: A receiving module, configured to receive a proxy binding request sent by a proxy device, where the proxy binding request is used to bind a first proxy in the proxy device to a client device; the first proxy is one of multiple Internet of Things (IoT) proxies in the proxy device; and the proxy binding request includes description information of the first proxy. A binding module, configured to establish binding information, where the binding information is used to indicate the binding relationship between the first proxy and the client device, and the binding information includes the description information.

18. The apparatus according to claim 17, wherein, the proxy binding request and the binding information further include binding type information and identification information of the first proxy, and the binding type information is used to indicate the binding type between the first proxy and the client device.

19. The apparatus according to claim 17 or 18, wherein, the client device includes a client functional unit; the client functional unit indicates an IoT proxy bound to the client device; the binding module is configured to establish the binding information in the client functional unit.

20. The apparatus according to any one of claims 17 to 19, wherein, the apparatus further includes: a display module, configured to display the description information when displaying the binding relationship between the first proxy and the client device.

21. A computer device, wherein, the computer device includes a processor, a memory, and a transceiver; a computer program is stored in the memory, and the processor executes the computer program to enable the computer device to implement the proxy binding method according to any one of claims 1 to 10 above.

22. A computer-readable storage medium, wherein, a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the proxy binding method according to any one of claims 1 to 10.

23. A chip, wherein, the chip includes a circuit structure, and the chip is used to run in a computer device to enable the computer device to execute the proxy binding method according to any one of claims 1 to 10.

24. A computer program product, wherein, the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions to enable the computer device to execute the proxy binding method according to any one of claims 1 to 10.

25. A computer program, wherein, the computer program is executed by a processor of a computer device to implement the proxy binding method according to any one of claims 1 to 10.

Images