Method and apparatus for processing device information, device, storage medium, and product

Abstract

A method and apparatus for processing device information, a device, a storage medium, and a product, relating to the technical field of the Internet of Things. The method is executed by a proxy device, and comprises: sending, to a client device, device information of an Internet of Things device (S401), the device information comprising identifier information of an application associated with the Internet of Things device. The above solution expands the range of information recognizable by the client device, so that the capability of the client device to manage the Internet of Things device and scenarios manageable thereby are expanded.

Description

Device information processing method, apparatus, 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 device information processing 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, IoT devices can be connected to terminal devices through proxy devices, so that users can manage, control, and perform other operations on the IoT devices in the terminal devices; for example, smart home devices (IoT devices) can be connected to cars / vehicle-mounted devices (terminal devices) through mobile phones (proxy devices).

[0004] Summary of the Invention

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

[0006] In one aspect, an embodiment of the present application provides a device information processing method, the method being executed by a proxy device, the method comprising:

[0007] Send device information of the Internet of Things device to the client device; the device information includes identification information of the application to which the Internet of Things device belongs.

[0008] In one aspect, an embodiment of the present application provides a method for processing device information, the method being executed by a client device, the method comprising:

[0009] Receive device information of an Internet of Things device; the device information includes identification information of an application to which the Internet of Things device belongs.

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

[0011] The sending module is used to send device information of the Internet of Things device to the client device; the device information includes identification information of the application program to which the Internet of Things device belongs.

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

[0013] The receiving module is used to receive device information of an Internet of Things device; the device information includes identification information of an application to which the Internet of Things device belongs.

[0014] On the other hand, an embodiment of the present application provides a computer device, the computer device being implemented as a proxy device or a client device, the computer device including a processor, a memory, and a transceiver;

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

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

[0017] 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 device information processing method.

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

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

[0020] Through the technical solution provided in the embodiments of the present application, the proxy device can send device information of the IoT device to the client device, and the device information includes identification information of the application to which the IoT device belongs, so that the client device can identify the application to which the IoT device represented by the proxy device belongs through the device information, thereby expanding the information that the client device can recognize, and further expanding the client device's management capabilities and management scenarios for the IoT device. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0023] FIG3 is a schematic diagram of an IoT device control method involved in this application;

[0024] FIG4 is a flowchart of a device information processing method provided by an embodiment of the present application;

[0025] FIG5 is a flowchart of a device information processing method provided by an embodiment of the present application;

[0026] FIG6 is a flowchart of a device information processing process according to an embodiment of the present application;

[0027] FIG7 is a schematic diagram of the process of binding an agent and a client involved in this application;

[0028] FIG8 is a schematic diagram of the process of binding an agent and a client involved in this application;

[0029] FIG9 is a block diagram of a device information processing apparatus provided by an embodiment of the present application;

[0030] FIG10 is a block diagram of a device information processing apparatus provided by an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

[0041] The proxy device 120 may directly establish a connection with the vehicle 130 . Alternatively, the proxy device 120 may also establish a connection with the vehicle 130 via the cloud server 150 .

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

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

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

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

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

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

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

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

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

[0051] 1) IoT agent discovery and binding

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

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

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

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

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

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

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

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

[0060] ⑧Notify IOTClient of the binding type;

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

[0062] 2) Control IoT devices (such as home appliances) through proxy devices

[0063] Please refer to FIG3 , which shows a schematic diagram of an IoT device control involved in this application. As shown in FIG3 , the IoT device control process is as follows:

[0064] ①IOTClient discovers the agent capability of IOTAgent;

[0065] ②IOTClient obtains the list of controllable devices: getDeviceListReq;

[0066] ③IOTAgent generates a list of controllable devices; if IOTAgent does not save the content, you need to go to IOTEcosystem to obtain it;

[0067] ④IOTClient sends the controllable device list to IOTAgent: getDeviceListResp;

[0068] ⑤IOTClient displays a list of controllable devices;

[0069] ⑥ The user issues a command to control the IOT device. The IOTClient sends the device control command to the IOTAgent. The relevant information of the control command is as follows:

[0070] Source: IOTClient; Destination: IOTAgent; path: targetNodeID / [targetOperationObject];

[0071] ⑦After receiving the above message, IOTAgent needs to convert the message and send it to the IOT ecological device (corresponding to the above IoT device). The relevant information of the converted message is as follows:

[0072] Source: IOTAgent; Destination: targetNodeID; path: targetNodeID / [targetOperationObject].

[0073] 3) IoT Client cluster

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

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

[0076] Table 1

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

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

[0079] Table 2

[0080] 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 DeviceTypeList is empty.

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

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

[0083] Table 3

[0084] AgentID contains the identifier of the agent that has established a binding relationship with the client device. The BindingType value indicates whether the binding relationship is long-term or temporary. When the BindingType value is 0, the binding relationship is temporary. After the client device completes controlling the IoT device connected to the device corresponding to the IoT agent ID, it does not need to save information such as the list of controllable devices sent by the device corresponding to the IoT agent ID. Conversely, when the BindingType value is 1, the binding relationship is long-term. After the client device completes controlling the IoT device connected to the device corresponding to the IoT agent ID, it can save information such as the list of controllable devices sent by the device corresponding to the IoT agent ID for use the next time it controls the IoT device connected to the device corresponding to the IoT agent ID. 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.

[0085] 4)IOT Agent cluster

[0086] Deployed on IoTAgent, it is used to proxy IoTClient's access to IoT ecological devices.

[0087] The properties of the IoT Agent cluster are defined in Table 4.

[0088] Table 4

[0089] The command definition of the IoT Agent cluster is shown in Table 5 below.

[0090] Table 5

[0091] The getDeviceListReq method corresponds to the request for obtaining a list of controllable devices. The getDeviceListReq method can be parameterless. The parameters included in the getDeviceListResq method are shown in Table 6 below.

[0092] Table 6

[0093] The above controllable device information may be the DeviceList in Table 6, wherein List[device_Info] may be composed of information of at least one IoT device, and each device_Info corresponds to information of an IoT device in the controllable device information.

[0094] The structure (struct) of the above device_Info is shown in Table 7 below.

[0095] Table 7

[0096] The structure of the endpoint information (endpoint_Info) is shown in Table 8 below.

[0097] Table 8

[0098] The structure of cluster information (cluster_Info) is shown in Table 9 below.

[0099] Table 9

[0100] The structure of attribute information (attribute_Info) is shown in Table 10 below.

[0101] Table 10

[0102] The structure of method information (command_Info) is shown in Table 11 below.

[0103] Table 11

[0104] The methods here can correspond to specific functions of the device, such as turning on, off, brightness adjustment, temperature adjustment, etc.

[0105] The structure of event information (event_Info) is shown in Table 12 below.

[0106] Table 12

[0107] An event can be an event reported by an IoT device to other devices, such as door lock_door not closed.

[0108] Subsequent embodiments of the present application provide a solution for transmitting device information of an IoT device between a client device and a proxy device. This solution can expand the data content carried by the device information, thereby expanding the client device's management capabilities and management scenarios for the IoT device.

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

[0110] Step 401: Send device information of an IoT device to a client device; the device information includes identification information of an application to which the IoT device belongs.

[0111] In an embodiment of the present application, multiple IoT-related applications can be installed in a proxy device, and each IoT-related application can connect to and / or manage one or more IoT devices; accordingly, the same IoT device can also be connected to one or more IoT-related applications at the same time, and / or the same IoT device can also be managed by one or more IoT-related applications at the same time.

[0112] For example, taking the proxy device as the user's mobile phone and the IoT device as a smart home device (such as a smart TV), different IoT device management apps (corresponding to the above-mentioned applications) can be installed in the mobile phone. When the IoT device management app is running, it can search for surrounding smart home devices (such as the above-mentioned smart TV) and establish connections to manage the smart TV. At this time, the IoT device management app can be called the application belonging to the smart TV. Optionally, multiple different apps can search for the smart TV and establish connections with the smart TV respectively. At this time, there are multiple applications belonging to the smart TV.

[0113] Among them, an IoT agent (IoT Agent) can also be installed and run in the proxy device. The IoT agent can be a program software that runs independently in the proxy device. For example, the IoT agent can be an independent application outside the above-mentioned multiple IoT-related applications, or the IoT agent can also be a software functional module that runs in dependence on other applications. For example, the IoT agent can also be a software functional module contained in each of the above-mentioned multiple IoT-related applications.

[0114] In an embodiment of the present application, the IoT agent can obtain the device information of the corresponding IoT devices from multiple IoT-related applications installed and running in the agent device. The device information of each IoT device includes the identification information of the application to which the IoT device belongs.

[0115] To sum up, in the scheme shown in the embodiment of the present application, the proxy device can send the device information of the IoT device to the client device, and the device information includes the identification information of the application to which the IoT device belongs, so that the client device can identify the application to which the IoT device represented by the proxy device belongs through the device information, thereby expanding the information that the client device can recognize, and further expanding the client device's management capabilities and management scenarios for the IoT device.

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

[0117] Step 501: Receive device information of an IoT device; the device information includes identification information of an application to which the IoT device belongs.

[0118] To sum up, in the scheme shown in the embodiment of the present application, the proxy device can send the device information of the IoT device to the client device, and the device information includes the identification information of the application to which the IoT device belongs, so that the client device can identify the application to which the IoT device represented by the proxy device belongs through the device information, thereby expanding the information that the client device can recognize, and further expanding the client device's management capabilities and management scenarios for the IoT device.

[0119] Please refer to FIG6 , which shows a flow chart of a device information processing 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 (such as other types of clients, such as a smart TV, etc.) in the network architecture shown in FIG1 . The method can include the following steps:

[0120] In step 601, the proxy device sends device information of the IoT device to the client device, and the client device receives the device information of the IoT device; the device information includes identification information of the application to which the IoT device belongs.

[0121] In an embodiment of the present application, the IoT Agent in the proxy device can obtain the device information of the IoT device corresponding to the IoT-related application installed in the proxy device, and send the obtained device information of the IoT device to the client device.

[0122] For example, after the client device discovers the IoT Agent in the proxy device, it can request the IoT Agent in the proxy device to obtain the device information of the IoT device. The IoT Agent will obtain the device information of the IoT device corresponding to the application from the IoT-related application and send it to the client device.

[0123] In some embodiments, the identification information of the application includes: an identification of the manufacturer of the application.

[0124] Among them, the identification information of the above-mentioned application can be implemented as the identification of the manufacturer of the application, such as the name of the manufacturer of the application, the manufacturer number of the application, etc., so that the subsequent client device can directly identify the manufacturer of the application through the manufacturer's identification of the application, thereby ensuring the efficiency of the client device in identifying the manufacturer of the application.

[0125] In some embodiments, the identification information of the above application may also include other information, such as the name of the application or the number of the application. The client device may subsequently identify the application or the manufacturer of the application based on the name of the application or the number of the application.

[0126] In some embodiments, the identification information of the application to which the IoT device belongs includes identification information of at least two applications.

[0127] In the above embodiment, an IoT device can simultaneously establish connections or bind to multiple applications in the same proxy device. Accordingly, the identification information of the application to which the IoT device belongs can simultaneously include the identification information of multiple applications, thereby supporting scenarios in which an IoT device can simultaneously establish connections or bind to multiple applications.

[0128] In step 602, the client device displays identification information of the application to which the IoT device belongs.

[0129] In an embodiment of the present application, after receiving the device information of the IoT device sent by the proxy device, the client device can display the identification information of the application to which the IoT device belongs when displaying the IoT device.

[0130] Among them, the above-mentioned display of the identification information of the application to which the IoT device belongs may include displaying the information content contained in the identification information of the application to which the IoT device belongs. For example, when the identification information of the above-mentioned application includes the name of the application, the client device can display the name of the application to which the IoT device belongs when displaying the IoT device.

[0131] The above-mentioned display of the identification information of the application to which the IoT device belongs may also include displaying other information content queried through the identification information of the application to which the IoT device belongs. For example, the client device can query the logo (LOGO) of the manufacturer of the application to which the IoT device belongs through the identification information of the application to which the IoT device belongs, and display the logo of the manufacturer of the application to which the IoT device belongs when displaying the IoT device.

[0132] In some embodiments, the method shown in FIG6 further includes:

[0133] The proxy device receives a registration request sent by the application, where the registration request includes identification information of the application.

[0134] Among them, during the operation of the application in the proxy device, a registration request can be sent to the IoT agent installed in the proxy device to register the identification information of the application in the IoT agent. Accordingly, the proxy device can receive the registration request and save the identification information of the application contained in the registration request, so as to subsequently carry the identification information of the application in the device information of the IoT device and send it to the client device, thereby ensuring the feasibility of the client device obtaining the identification information of the application belonging to the IoT device from the IoT agent.

[0135] For example, the above-mentioned IoT agent is a system-level IoT agent, or an IoT agent natively included in the operating system of the agent device. When the above-mentioned application is installed in the operating system of the agent device, the operating system provides the interface information of the IoT agent to the application. The application sends the above-mentioned registration request to the IoT agent based on the interface information of the IoT agent.

[0136] Among them, the above-mentioned interface information may include an application programming interface (API). The interface information of the above-mentioned IoT agent may refer to the API provided by the IoT agent to the outside world. Programs / functional components outside the IoT agent can pass data / requests / instructions to the IoT agent by calling the API provided by the IoT agent to the outside world.

[0137] In some embodiments, the registration request also includes interface information of the application.

[0138] Among them, the interface information of the above application may include the API provided by the application to the outside world. Other programs / functional components outside the application (such as the above IoT agent) can pass data / requests / instructions to the application by calling the API provided by the application to the outside world.

[0139] In an embodiment of the present application, in order to ensure that the IoT agent can initiate communication / send information to the application, the above-mentioned registration request can also carry the interface information of the application. That is, the interface information of the application and the identification information of the application can be sent to the IoT agent through the same request, which simplifies the data interaction between the application and the IoT agent, improves the interaction efficiency between the application and the IoT agent, and saves communication resources between the application and the IoT agent.

[0140] In some embodiments, the method shown in FIG6 further includes:

[0141] The proxy device obtains a first controllable device list from the application according to the interface information of the application, where the first controllable device list is used to indicate one or more IoT devices corresponding to the application.

[0142] Among them, after obtaining the interface information of the application, the IoT agent in the above-mentioned proxy device can send a request to the application through the interface information of the application (such as calling the API provided by the application to the outside world) to obtain the information of one or more IoT devices corresponding to the application. After receiving the request, the application can send a first controllable device list to the IoT agent.

[0143] The one or more IoT devices corresponding to the above application may refer to one or more IoT devices to which the application has established a connection or binding.

[0144] Among them, the above-mentioned first controllable device list may include relevant information of one or more IoT devices corresponding to the application, such as the information connected or bound to the application, such as identification information, attribute information, calling method / command and other information of the IoT device.

[0145] In the above embodiment, the IoT agent can request the application for relevant information of each IoT device that the application has been connected or bound to through the interface information of the application passed by the application, so that the device information of the IoT device can be provided to the client device subsequently, thereby ensuring the feasibility of the client device obtaining the device information of the IoT device from the IoT agent.

[0146] In some embodiments, the proxy device obtains the first controllable device list from the application based on the application's interface information, including: upon receiving a device list acquisition request, the proxy device obtains the first controllable device list from the application based on the application's interface information. Accordingly, the client device may send the device list acquisition request to the proxy device.

[0147] In the above embodiment, the client device can request the proxy device to obtain the device information of the Internet of Things device that the proxy device represents. At this time, the client device can send the above-mentioned device list acquisition request to the proxy device (for example, send the above-mentioned device list acquisition request to the IoT proxy in the proxy device). The device list acquisition request can trigger the IoT proxy in the proxy device to obtain the first controllable device list from the application in the proxy device. The above scheme can enable the IoT proxy to obtain the first controllable device list from the application when the client device needs it, thereby ensuring the validity and accuracy of the first controllable device list.

[0148] In other embodiments, the above-mentioned proxy device (such as the IoT agent in the proxy device) may also obtain the first controllable device list from the application based on the interface information of the application before receiving the device list acquisition request. In this way, when the device list acquisition request is subsequently received, the device information of the IoT device can be sent to the client device as soon as possible, thereby ensuring the efficiency of the device information transmission of the IoT device between the proxy device and the client device.

[0149] In some embodiments, the method shown in FIG6 further includes:

[0150] The proxy device generates device information of the IoT device according to the first controllable device list.

[0151] In the above embodiment, after the IoT agent in the proxy device obtains the first controllable device list from the application, the relevant information of the IoT device contained in the first controllable device list is merged with the identification information of the application to which the IoT device belongs, so as to obtain the device information of the IoT device, thereby ensuring the feasibility of the client device obtaining the device information of the IoT device from the IoT agent.

[0152] In some embodiments, generating device information of the Internet of Things device according to the first controllable device list includes: adding the device information of the Internet of Things device to the Internet of Things proxy cluster of the proxy device according to the first controllable device list.

[0153] In an embodiment of the present application, the above-mentioned proxy device generates device information of the Internet of Things device, which may refer to adding the device information of the Internet of Things device to the device model in the proxy device (corresponding to the above-mentioned Internet of Things proxy cluster). For example, after the IoT agent in the proxy device obtains the first controllable device list from the application, the relevant information of the Internet of Things device included in the first controllable device list and the identification information of the application to which the Internet of Things device belongs are added to the Internet of Things proxy cluster (IoT Agent Cluster) and the device information (device_Info) structure corresponding to the Internet of Things device, thereby ensuring the feasibility of subsequent client devices being able to obtain the device information containing the identification information of the application from the IoT agent.

[0154] In other embodiments, the proxy device may first generate device information of the IoT device outside the IoT proxy cluster, and then add the generated device information of the IoT device to the IoT proxy cluster.

[0155] Among them, the IoT agent in the proxy device can correspond to multiple applications in the proxy device at the same time, and each application can connect to or bind to multiple IoT devices. Accordingly, the IoT agent cluster of the IoT agent can include the device information (device_Info) structure of the IoT devices to which the multiple applications corresponding to the IoT agent are respectively connected or bound; optionally, an IoT device can also be connected to or bound to multiple applications at the same time. At this time, in the IoT agent cluster, the device_Info structure of the IoT device can include the identification information of the multiple applications corresponding to the IoT device.

[0156] In some embodiments, the proxy device sends device information of the IoT device to the client device, including:

[0157] The proxy device sends a second controllable device list corresponding to the device list acquisition request to the client device, where the second controllable device list includes device information of one or more IoT devices corresponding to the proxy device.

[0158] Correspondingly, the client device receives the device information of the Internet of Things device, including: the client device receives the second controllable device list corresponding to the device list acquisition request sent by the proxy device.

[0159] In an embodiment of the present application, after receiving a device list acquisition request sent by a client device, the IoT agent in the above-mentioned proxy device can obtain device information of all or part of the IoT devices corresponding to the IoT agent. For example, the IoT agent can obtain device information of each IoT device included in the above-mentioned IoT agent cluster, and then send a second controllable device list containing the acquired device information of each IoT device to the client device; or, in other words, the IoT agent can send a second controllable device list consisting of the device_Info structure of each IoT device in the above-mentioned IoT agent cluster to the client device. Accordingly, the client device can receive the above-mentioned second controllable device list sent by the IoT agent.

[0160] When the proxy device sends the second controllable device list to the client device, the second controllable device list may include device_Info structures of all IoT devices in the IoT proxy cluster.

[0161] Alternatively, when the proxy device sends a second controllable device list to the client device, the second controllable device list may include the device_Info structure of some IoT devices in the IoT proxy cluster. For example, the above-mentioned device list acquisition request may carry the identification information of a specified application. When the proxy device sends a second controllable device list to the client device, the second controllable device list may include the device_Info structure of the IoT device in the IoT proxy cluster that contains the identification information of the specified application.

[0162] Through the above embodiments, the device information of IoT devices connected or bound to multiple applications can be transmitted between the proxy device and the client device, thereby supporting a scenario where one IoT proxy corresponds to multiple applications.

[0163] In some embodiments, the method shown in Figure 6 above also includes: the proxy device sends at least one of application quantity information and program identification information to the client device; wherein the application quantity information is used to indicate the number of each application corresponding to the proxy device; and the program identification information is used to indicate the identification information of each application corresponding to the proxy device.

[0164] Accordingly, the client device may receive at least one of the application quantity information and the program identification information sent by the proxy device.

[0165] In the above embodiment, the IoT agent in the proxy device can also notify the client device of the number and representation information of its corresponding applications; for example, before the proxy device sends the device information of the IoT device to the client device (for example, in the process of the client device discovering the IoT agent in the proxy device, or after the client device discovers the IoT agent in the proxy device), the IoT agent in the proxy device can send the number of applications corresponding to the IoT agent and the identification information of each application to the client device, so that the client device can subsequently know and display the applications corresponding to the IoT agent it discovered, thereby supporting the synchronization of application-related information between the IoT agent and the client device in the scenario where one IoT agent corresponds to multiple applications. For example, the user can trigger the client device on the client device side to selectively obtain the device information of the IoT devices connected or bound to some applications.

[0166] In some embodiments, the client device displays identification information of the application to which the IoT device belongs, including:

[0167] When the identification information of the application to which the IoT device belongs contained in the device information of the IoT device matches the identification information of each application corresponding to the proxy device indicated in the program identification information, the identification information of the application to which the IoT device belongs is displayed.

[0168] Among them, when the proxy device sends the second controllable device list to the client device, the second controllable device list may include the device_Info structure of all IoT devices in the IoT proxy cluster. The client device can match the identification information of the application to which the IoT device belongs contained in the device information of each IoT device with the identification information of each application corresponding to the proxy device indicated in the program identification information. If the two match, the identification information of the application to which each IoT device belongs can be displayed. Conversely, if the two do not match, an error may have occurred in the transmission of the device information of the IoT device (such as the transmission of the above-mentioned second controllable device list). For example, the device information of some IoT devices failed to be successfully sent to the client device, or the program identification information may have failed to be updated in time. At this time, the client device can display an error prompt to ensure the accuracy of the display of the identification information of the application to which the IoT device belongs.

[0169] In some embodiments, the method shown in FIG. 6 further includes: the proxy device sending system-level identification information to the client device, where the system-level identification information is used to indicate that the proxy device is a system-level IoT proxy.

[0170] Correspondingly, the client device can receive the system-level identification information sent by the proxy device, where the system-level identification information is used to indicate that the proxy device is a system-level IoT proxy.

[0171] In an embodiment of the present application, an IoT agent in a proxy device can correspond to multiple applications in the operating system at the same time. In this case, the IoT agent can be called a system-level IoT agent. Accordingly, when a client device obtains device information of an IoT device from the IoT agent, there may be a need to distinguish the applications to which the IoT device belongs. In this regard, in an embodiment of the present application, when the IoT agent in the proxy device is a system-level agent, system-level identification information can be sent to the client device to inform the client device that the IoT agent in the proxy device may correspond to multiple applications, thereby supporting the scenario where one IoT agent corresponds to multiple applications. The client device can identify whether the IoT device supports multiple applications, thereby being compatible with the scenario where one IoT agent corresponds to one / multiple applications.

[0172] In some embodiments, the proxy device sends system-level identification information to the client device, including: the proxy device writes the system-level identification information into the IoT client cluster of the client device and into binding information corresponding to the proxy device.

[0173] In other embodiments, the system-level identification information may be reflected as a feature in an IoT Agent cluster of the IoT agent, and the feature may be read by the client to determine whether the IoT agent is a system-level agent.

[0174] Accordingly, the client device receives the system-level identification information sent by the proxy device, including: the client device writes the system-level identification information into the IoT client cluster of the client device and the binding information corresponding to the proxy device.

[0175] In an embodiment of the present application, during the process of / after a client device discovers the IoT agent in the proxy device and binds the client device to the IoT agent, the IoT agent in the proxy device can write system-level identification information into the IoT client cluster of the client device and into the binding information corresponding to the proxy device through the command / method corresponding to the IoT client cluster, so that the client device can identify whether the IoT agent has the function of corresponding to multiple applications through the IoT client cluster, so that it can subsequently accurately obtain or manage information about the IoT devices connected or bound to the applications corresponding to the IoT agent.

[0176] The following describes two technical solutions as examples to describe the solutions provided by any of the embodiments shown in FIG. 4 to FIG. 6 .

[0177] Technical solution 1:

[0178] The IoT proxy is a system-level proxy that can proxy multiple apps. Taking the client device as a car / vehicle-mounted device, the proxy device as the user's mobile phone, and the IoT device as a smart home device as an example, when mapping the IoT device connected to each app to a car-home interconnected device, the corresponding app's vendor information is added to the mapped car-home interconnected device.

[0179] The added device_Info structure is shown in Table 13 below.

[0180] Table 13

[0181] DeviceType identifies the device type. DeviceID is the device ID in the car-home interconnection. Vendor indicates the manufacturer ID of the IoT device. ModelID identifies the model of the IoT device. Endpoints indicates the endpoint information of the IoT device. AppVendor indicates the manufacturer ID of the app mapped to the device. For example, if a smart home app from manufacturer 1 on a phone is mapped to an air conditioner from manufacturer 2 on the proxy, the Vendor is "Manufacturer 2" and the AppVendor is "Manufacturer 1."

[0182] After obtaining the IoTAgent's device list, the IOTClient maps the IoT devices in the list to their APPVendors. When displaying these information to the user, the APPVendor information can be used to distinguish devices, helping users identify the source of IoT device information. For example, if the IoTAgent proxies App 1 from Vendor 1 and App 2 from Vendor 3, the devices in the mapped device list will be labeled "APP 1" or "APP 2" (or "Vendor 1" / "Vendor 3"), respectively.

[0183] 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 a schematic diagram of the agent and client binding process involved in this application. The process can be as follows:

[0184] S71, the IoT APP registers with the IoT agent. The registration interface includes the APP's VendorID and interaction interface.

[0185] S72: After the car and the mobile phone are connected, the user starts the binding process on the mobile phone.

[0186] S73 , the IoT agent of the mobile phone discovers the identifier of the smarthomeClient cluster of the IoT client of the car and determines whether it supports access to the smart home capability.

[0187] S74: The IoT client returns the supported protocol version: version id.

[0188] S75, the user selects temporary binding or long-term binding; if it is long-term binding, the binding relationship needs to be set in the binding table.

[0189] S76, the IoT agent writes the agentID, binding type and VendorID=0x0000 into the clientBindingInfo list of the IoT client, where VendorID=0x0000 indicates that the IoT agent is a system-level agent.

[0190] S77: The IoT client confirms that the IoT agent is a system-level agent based on the VendorID of the IoT agent.

[0191] S78: The IoT client obtains a list of controllable devices: getDeviceListReq.

[0192] S79, the IoT agent obtains the controllable device list of APP A through the interaction interface registered by APP A.

[0193] S710 , APP A returns a list of controllable devices to the IoT proxy.

[0194] S711: The IoT agent obtains the controllable device list of APP B through the interaction interface registered by APP B.

[0195] S712, APP B returns a list of controllable devices to the IoT proxy.

[0196] S713, the IoT agent generates a multi-APP platform device model. Specifically, the IoT agent maps the acquired controllable devices to the car-home interconnection device model, and adds an APPVendor field in each device, whose value is the same as the VendorID registered by the corresponding APP.

[0197] S714, the IoT agent returns the generated controllable device list with APPVendor to the IoT client.

[0198] S715 , the IoT client loads and displays a list of controllable devices to the user, and displays the corresponding APPVendor for each device in the list.

[0199] After binding, the IOTClient can retrieve the IoT devices managed by the two smart home apps corresponding to the IoTAgent and display them in the controllable device list on the control interface. Furthermore, the IOTClient can use the VendorIDs of the two smart home apps to find the corresponding vendor information 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.

[0200] Technical solution 2:

[0201] (1) The IoT agent is a system-level agent that can proxy multiple apps. The number of apps it proxies and the list of app vendor information are displayed in the properties of its IoT Agent cluster.

[0202] The clientBindingInfo structure is defined as shown in Table 14 below.

[0203] Table 14

[0204] APPNumber represents the number of smart home apps proxied by the IoTAgent. For example, if a phone contains two smart home apps, A and B, both proxied by the IoTAgent, the value of APPNumber is 2. The value range of APPNumber is an integer not less than 1. APPVendors represents the vendor information of the smart home apps proxied by the IoTAgent.

[0205] When the IoTAgent maps each app-connected IoT device to a car-home interconnection device, it adds the corresponding app's vendor information to the mapped car-home interconnection device. The device_Info structure after the addition is shown in Table 13 above.

[0206] 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 8, which shows a schematic diagram of the agent and client binding process involved in this application. The process can be as follows:

[0207] S81, the IoT APP registers with the IoT agent. The registration interface includes the APP's VendorID and interaction interface.

[0208] S82: After the car and the mobile phone are connected, the user starts the binding process on the mobile phone.

[0209] S83, the IoT agent of the mobile phone discovers the identifier of the smarthomeClient cluster of the IoT client of the car and determines whether it supports access to the smart home capability.

[0210] S84: The IoT client returns the supported protocol version: version id.

[0211] S85, the user selects temporary binding or long-term binding; if it is long-term binding, the binding relationship needs to be set in the binding table.

[0212] S86, the IoT agent writes the agentID, binding type, and VendorID=0x0000 into the clientBindingInfo list of the IoT client, where VendorID=0x0000 indicates that the IoT agent is a system-level agent.

[0213] S87: The IoT client confirms that the IoT agent is a system-level agent based on the VendorID of the IoT agent.

[0214] S88, the IoT client reads the APPNumber attribute of the IoT Agent cluster.

[0215] S89, the IoT agent returns the value of APPNumber, which is the same as the number of apps registered in step 1.

[0216] S810: The IoT client reads the APPVendors attribute of the IoT Agent cluster.

[0217] S811: The IoT agent returns the APPVendors attribute list. Each item in the list is the VendorID registered by the APP in step 1. The number of items is the same as the APPNumber.

[0218] S812: The IoT client obtains a list of controllable devices: getDeviceListReq.

[0219] S813: The IoT agent obtains the controllable device list of APP A through the interaction interface registered by APP A.

[0220] S814, APP A returns a list of controllable devices to the IoT proxy.

[0221] S815, the IoT agent obtains the controllable device list of APP B through the interaction interface registered by APP B.

[0222] S816, APP B returns a list of controllable devices to the IoT proxy.

[0223] S817, the IoT agent maps the acquired controllable devices to the car-home interconnection device model, and adds an APPVendor field in each device, whose value is the same as the VendorID registered by the corresponding APP.

[0224] S818, the IoT agent returns the generated controllable device list with APPVendor to the IoT client.

[0225] S819, the IoT client confirms that the obtained APPVendor information of all devices is consistent with the attribute values ​​of APPNumber and APPVendors, loads and displays the controllable device list to the user, and displays the corresponding APPVendor on each device in the list.

[0226] After binding, the IOTClient can retrieve the IoT devices managed by the two smart home apps corresponding to the IoTAgent and display them in the controllable device list on the control interface. Furthermore, the IOTClient can use the VendorIDs of the two smart home apps to find the corresponding vendor information 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.

[0227] The solutions shown in the above embodiments of this application disclose a method in which an IoTAgent on a mobile phone acts as a proxy for multiple apps and binds them to a vehicle client:

[0228] 1) By identifying the IoTAgent, the client can identify the system-level IoTAgent. The client can further obtain the number of apps and manufacturer information that the IoTAgent represents;

[0229] 2) IoTAgent adds the manufacturer information of the device APP to the constructed car-home interconnected device model to indicate to the user on the client which APP each device comes from.

[0230] The solutions shown in the above-mentioned embodiments of this application, by introducing system-level IoT agent special identification, proprietary attributes and multi-APP platform device models, enable the IoT agent to provide proxy capabilities for multiple smart home apps and support binding with the car client, while enabling the car client to display the proxy IoT device control interface to the user according to its source.

[0231] Please refer to Figure 9, which shows a block diagram of a device information processing apparatus provided by one embodiment of the present application. The device information processing apparatus 900 has the functions of implementing the methods shown in Figures 4, 5, or 6 above, which are performed by the proxy device. As shown in Figure 9, the apparatus may include:

[0232] The sending module 901 is configured to send device information of an IoT device to a client device; the device information includes identification information of an application to which the IoT device belongs.

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

[0234] The receiving module is configured to receive a registration request sent by the application, wherein the registration request includes identification information of the application.

[0235] In some embodiments, the registration request also includes interface information of the application.

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

[0237] An acquisition module is used to obtain a first controllable device list from the application according to the interface information, where the first controllable device list is used to indicate one or more IoT devices corresponding to the application.

[0238] In some embodiments, the acquisition module is configured to acquire the first controllable device list from the application according to the interface information when a device list acquisition request is received.

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

[0240] A generating module is used to generate device information of the Internet of Things device according to the first controllable device list.

[0241] In some embodiments, the generating module is configured to add the device information of the IoT device to the IoT proxy cluster of the proxy device according to the first controllable device list.

[0242] In some embodiments, the sending module 901 is used to send a second controllable device list corresponding to the device list acquisition request to the client device, where the second controllable device list includes the device information of one or more IoT devices corresponding to the proxy device.

[0243] In some embodiments, the sending module 901 is further configured to send system-level identification information to the client device, where the system-level identification information is used to indicate that the proxy device is a system-level IoT proxy.

[0244] In some embodiments, the sending module 901 is configured to write the system-level identification information into the IoT client cluster of the client device and into the binding information corresponding to the proxy device.

[0245] In some embodiments, the sending module 901 is further configured to send at least one of application quantity information and program identification information to the client device;

[0246] The application quantity information is used to indicate the quantity of each application corresponding to the proxy device;

[0247] The program identification information is used to indicate the identification information of each application corresponding to the proxy device.

[0248] In some embodiments, the identification information of the application includes: an identification of the manufacturer of the application.

[0249] In some embodiments, the identification information of the application to which the IoT device belongs includes identification information of at least two of the applications.

[0250] Please refer to Figure 10, which shows a block diagram of a device information processing apparatus provided by one embodiment of the present application. The device information processing apparatus 1000 has the functions of implementing the methods shown in Figures 4, 5, or 6 above, which are performed by the client device. As shown in Figure 10, the apparatus may include:

[0251] The receiving module 1001 is configured to receive device information of an IoT device; the device information includes identification information of an application to which the IoT device belongs.

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

[0253] The display module is used to display the identification information of the application to which the Internet of Things device belongs.

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

[0255] A sending module, used to send a device list acquisition request to the proxy device;

[0256] The receiving module 1001 is configured to receive a second controllable device list corresponding to the device list acquisition request, where the second controllable device list includes the device information of one or more IoT devices corresponding to the proxy device.

[0257] In some embodiments, the receiving module 1001 is further configured to receive system-level identification information sent by the proxy device, where the system-level identification information is used to indicate that the proxy device is a system-level IoT proxy.

[0258] In some embodiments, the receiving module 1001 is configured to write the system-level identification information into the IoT client cluster of the client device and into the binding information corresponding to the proxy device.

[0259] In some embodiments, the receiving module 1001 is further configured to receive at least one of application quantity information and program identification information sent by the proxy device;

[0260] The application quantity information is used to indicate the quantity of each application corresponding to the proxy device;

[0261] The program identification information is used to indicate the identification information of each application corresponding to the proxy device.

[0262] In some embodiments, the display module is used to display the identification information of the application to which the Internet of Things device belongs when the identification information of the application to which the Internet of Things device belongs contained in the device information of the Internet of Things device matches the identification information of each application corresponding to the proxy device indicated in the program identification information.

[0263] In some embodiments, the identification information of the application includes: an identification of the manufacturer of the application.

[0264] In some embodiments, the identification information of the application to which the IoT device belongs includes identification information of at least two of the applications.

[0265] Please refer to FIG11 , which shows a schematic diagram of the structure of a computer device 1100 provided in one embodiment of the present application. The computer device 1100 may include: a processor 1101 , a receiver 1102 , a transmitter 1103 , a memory 1104 , and a bus 1105 .

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

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

[0268] In an exemplary embodiment, when computer device 1100 is implemented as the aforementioned proxy device, processor 1101 and / or transceiver is configured to transmit device information of an IoT device to a client device; the device information includes identification information of the application to which the IoT device belongs. The processes executed by processor 1101 and / or transceiver in computer device 1100 can refer to the steps performed by the proxy device in the method illustrated in either FIG4 or FIG6 .

[0269] In one exemplary embodiment, when computer device 1100 is implemented as a client device, processor 1101 and / or transceiver is configured to receive device information from an IoT device; the device information includes identification information of an application program associated with the IoT device. The processes performed by processor 1101 and / or transceiver in computer device 1100 may refer to the steps performed by the client device in the method illustrated in either FIG. 5 or FIG. 6 .

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

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

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

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

Claims

1. A method for processing device information, characterized in that, The method is executed by a proxy device, and the method includes: Sending device information of an Internet of Things (IoT) device to a client device; the device information includes identification information of an application to which the IoT device belongs.

2. The method according to claim 1, wherein The method further includes: Receiving a registration request sent by the application, where the registration request includes the identification information of the application.

3. The method according to claim 2, wherein The registration request further includes interface information of the application.

4. The method according to claim 3, wherein The method further includes: Obtaining a first list of controllable devices from the application according to the interface information, where the first list of controllable devices is used to indicate one or more of the IoT devices corresponding to the application.

5. The method according to claim 4, wherein The obtaining a first list of controllable devices from the application according to the interface information includes: When receiving a device list obtaining request, obtaining the first list of controllable devices from the application according to the interface information.

6. The method according to claim 4 or 5, characterized in that, The method further includes: Generating device information of the IoT device according to the first list of controllable devices.

7. The method according to claim 6, wherein The generating device information of the IoT device according to the first list of controllable devices includes: Adding the device information of the IoT device to an IoT proxy cluster of the proxy device according to the first list of controllable devices.

8. The method according to claim 5, characterized in that, The sending device information of the IoT device to the client device includes: Sending a second list of controllable devices corresponding to the device list obtaining request to the client device, where the second list of controllable devices includes the device information of one or more of the IoT devices corresponding to the proxy device.

9. The method according to any one of claims 1 to 8, characterized in that The method further includes: Sending system-level identification information to the client device, where the system-level identification information is used to indicate that the proxy device is a system-level IoT proxy.

10. The method according to claim 9, characterized in that, The sending system-level identification information to the client device includes: Writing the system-level identification information into binding information corresponding to the proxy device in an IoT client cluster of the client device.

11. According to the method described in any one of claims 1 to 10, characterized in that, The method further includes: Sending at least one of application number information and program identification information to the client device; wherein, the application number information is used to indicate the number of each application corresponding to the proxy device; the program identification information is used to indicate the respective identification information of each application corresponding to the proxy device.

12. The method according to any one of claims 1 to 11, characterized in that, The identification information of the application includes: the identification of the manufacturer of the application.

13. The method according to any one of claims 1 to 12, characterized in that, The identification information of the application to which the IoT device belongs includes identification information of at least two applications.

14. A method for processing device information, characterized in that, The method is executed by a client device, and the method includes: Receiving device information of an IoT device; the device information includes identification information of an application to which the IoT device belongs.

15. The method according to claim 14, wherein The method further includes: Displaying the identification information of the application to which the IoT device belongs.

16. The method according to claim 14 or 15, characterized in that The method further includes: Sending a device list obtaining request to a proxy device; The receiving device information of the IoT device includes: Receive a second list of controllable devices corresponding to the device list acquisition request, where the second list of controllable devices contains the device information of one or more of the Internet of Things devices corresponding to the proxy device.

17. The method according to claim 16, wherein The method further includes: Receiving system-level identification information sent by the proxy device, where the system-level identification information is used to indicate that the proxy device is a system-level Internet of Things proxy.

18. The method according to claim 17, wherein The receiving the system-level identification information sent by the proxy device includes: Writing the system-level identification information into the binding information corresponding to the proxy device in the Internet of Things client cluster of the client device.

19. The method according to claim 15, wherein The method further includes: receiving at least one of the application program quantity information and the program identification information sent by the proxy device; wherein the application program quantity information is used to indicate the quantity of each application program corresponding to the proxy device; the program identification information is used to indicate the identification information of each application program corresponding to the proxy device.

20. The method according to claim 19, wherein The displaying the identification information of the application program to which the Internet of Things device belongs includes: When the identification information of the application program to which the Internet of Things device belongs included in the device information of the Internet of Things device matches the identification information of each application program corresponding to the proxy device indicated in the program identification information, displaying the identification information of the application program to which the Internet of Things device belongs.

21. The method according to any one of claims 14 to 20, characterized in that The identification information of the application program includes: the identification of the manufacturer of the application program.

22. The method according to any one of claims 14 to 21, characterized in that The identification information of the application program to which the Internet of Things device belongs includes at least two pieces of identification information of the application programs.

23. An apparatus for processing device information, characterized in that, The device includes: A sending module, configured to send device information of an Internet of Things device to a client device; the device information contains the identification information of the application program to which the Internet of Things device belongs.

24. The device according to claim 23, wherein, The device further includes: A receiving module, configured to receive a registration request sent by the application program, where the registration request contains the identification information of the application program.

25. The device according to claim 24, characterized in that, The registration request further contains the interface information of the application program.

26. The device according to claim 25, characterized in that, The device further includes: An obtaining module, configured to obtain a first list of controllable devices from the application program according to the interface information, where the first list of controllable devices is used to indicate one or more of the Internet of Things devices corresponding to the application program.

27. The device according to claim 26, characterized in that, The obtaining module is configured to, when receiving a device list acquisition request, obtain the first list of controllable devices from the application program according to the interface information.

28. The device according to claim 26 or 27, characterized in that, The device further includes: A generating module, configured to generate the device information of the Internet of Things device according to the first list of controllable devices.

29. The device according to claim 28, characterized in that, The generating module is configured to add the device information of the Internet of Things device to the Internet of Things proxy cluster of the proxy device according to the first list of controllable devices.

30. The device according to claim 27, characterized in that, The sending module is configured to send a second list of controllable devices corresponding to the device list acquisition request to the client device, where the second list of controllable devices contains the device information of one or more of the Internet of Things devices corresponding to the proxy device.

31. The device according to any one of claims 23 to 30, characterized in that, The sending module is further configured to send system-level identification information to the client device, where the system-level identification information is used to indicate that the proxy device is a system-level Internet of Things proxy.

32. The device according to claim 31, wherein The sending module is configured to write the system-level identification information into the binding information corresponding to the proxy device in the Internet of Things client cluster of the client device.

33. The device according to any one of claims 23 to 32, characterized in that, The sending module is further configured to send at least one of the application program quantity information and the program identification information to the client device; wherein, the application program quantity information is used to indicate the quantity of each application program corresponding to the proxy device; The program identification information is used to indicate the identification information of each application program corresponding to the proxy device.

34. The device according to any one of claims 23 to 33, characterized in that, The identification information of the application program includes: the identification of the manufacturer of the application program.

35. The device according to any one of claims 23 to 34, characterized in that, The identification information of the application program to which the Internet of Things device belongs includes the identification information of at least two of the application programs.

36. An apparatus for processing device information, characterized in that, The device includes: a receiving module, configured to receive device information of an Internet of Things device; the device information includes the identification information of the application program to which the Internet of Things device belongs.

37. The device according to claim 36, characterized in that, The device further includes: a display module, configured to display the identification information of the application program to which the Internet of Things device belongs.

38. The device according to claim 36 or 37, characterized in that, The device further includes: a sending module, configured to send a device list acquisition request to a proxy device; the receiving module, configured to receive a second controllable device list corresponding to the device list acquisition request, where the second controllable device list includes the device information of one or more Internet of Things devices corresponding to the proxy device.

39. The device according to claim 38, characterized in that, The receiving module is further configured to receive the system-level identification information sent by the proxy device, where the system-level identification information is used to indicate that the proxy device is a system-level Internet of Things proxy.

40. The device according to claim 39, wherein, The receiving module is configured to write the system-level identification information into the binding information corresponding to the proxy device in the Internet of Things client cluster of the client device.

41. The device according to claim 37, wherein The receiving module is further configured to receive at least one of the application program quantity information and the program identification information sent by the proxy device; wherein, the application program quantity information is used to indicate the quantity of each application program corresponding to the proxy device; The program identification information is used to indicate the identification information of each application program corresponding to the proxy device.

42. The device according to claim 41, characterized in that, The display module is configured to display the identification information of the application program to which the Internet of Things device belongs when the identification information of the application program to which the Internet of Things device belongs included in the device information of the Internet of Things device matches the identification information of each application program corresponding to the proxy device indicated in the program identification information.

43. The device according to any one of claims 36 to 42, characterized in that, The identification information of the application program includes: the identification of the manufacturer of the application program.

44. The device according to any one of claims 36 to 43, characterized in that, The identification information of the application program to which the Internet of Things device belongs includes the identification information of at least two of the application programs.

45. A computer device, characterized in that, The computer device includes a processor, a memory, and a transceiver; a computer program is stored in the memory, and the processor executes the computer program to enable the computer device to implement the device information processing method according to any one of claims 1 to 22 above.

46. A computer-readable storage medium, characterized in that, A computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the device information processing method according to any one of claims 1 to 22.

47. A chip, characterized in that, The chip includes a circuit structure, and the chip is used to run in a computer device so that the computer device executes the device information processing method according to any one of claims 1 to 22.

48. A computer program product, characterized in that, The computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, so that the computer device executes the device information processing method according to any one of claims 1 to 22.

49. A computer program, characterized in that, The computer program is executed by a processor of a computer device to implement the device information processing method according to any one of claims 1 to 22.

Images