Device status monitoring method, device, equipment and storage medium

Abstract

The embodiment of the present application provides a device status monitoring method, apparatus, device and storage medium. The method includes: a user terminal sends a subscription request to a cloud server, and the cloud server can monitor the device and / or device status belonging to the target user according to the received subscription request, and when the device and / or device status belonging to the user changes, the cloud server sends notification information to the user terminal corresponding to the target user, so that the user terminal can timely and accurately obtain the change information of the device and / or device status that needs to be controlled, thereby improving the accuracy of the acquired status information of the Internet of Things device, and thus improving the accuracy of the device control.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of Internet of Things technology, and in particular to a device status monitoring method, apparatus, device and storage medium. Background Art

[0002] With the development of network and computer technology, the Internet of Things technology has been rapidly applied, and more and more devices can be connected to the network to achieve monitoring and control of the devices. In the process of the development of the Internet of Things, the types of Internet of Things devices are increasing. How to achieve unified remote control of Internet of Things devices in the network is the key.

[0003] In the prior art, all IoT devices in the network can be registered with the cloud platform, and the cloud platform will centrally manage the status of each device. That is, after registering with the cloud platform, the IoT device can publish its discoverable resources to the resource directory of the cloud platform. In this way, the user can find the IoT device that the user needs to control on the cloud platform through the user terminal, and control the target IoT device according to the acquired device status.

[0004] However, since the resources on the cloud platform used to manage device status such as device registration and / or device online and offline are unreadable by other devices, this may cause the user terminal to obtain inaccurate status information of the IoT device from the cloud platform, resulting in inaccurate device control. Summary of the invention

[0005] The embodiments of the present application provide a device status monitoring method, apparatus, device and storage medium, which are used to solve the problem in the prior art that the status information of the Internet of Things device obtained by the user terminal device from the cloud platform may be inaccurate, resulting in inaccurate device control.

[0006] In a first aspect, an embodiment of the present application provides a device status monitoring method, comprising:

[0007] Sending a subscription request to a cloud server, wherein the subscription request is used to instruct the cloud server to feedback change information to a user terminal corresponding to the target user when monitoring a change in a device and / or device status belonging to the target user;

[0008] A notification message is received from the cloud server, wherein the notification message includes: change information of a device and / or a device status belonging to the target user.

[0009] In a second aspect, an embodiment of the present application provides a device status monitoring method, including:

[0010] Receiving a subscription request sent by a user terminal, the subscription request including: an identifier of the user terminal and / or an identifier of a target user corresponding to the user terminal;

[0011] Monitoring a device and / or a device status belonging to the target user according to the subscription request;

[0012] When a device and / or a device status belonging to the target user changes, a notification message is sent to the user terminal, wherein the notification message includes: change information of the device and / or the device status belonging to the target user.

[0013] In a third aspect, an embodiment of the present application provides a device status monitoring apparatus, including: a sending module and a receiving module;

[0014] The sending module is used to send a subscription request to the cloud server, wherein the subscription request is used to instruct the cloud server to feedback the change information to the user terminal corresponding to the target user when monitoring that the device and / or device status belonging to the target user has changed;

[0015] The receiving module is used to receive a notification message from the cloud server, where the notification message includes: change information of the device and / or device status belonging to the target user.

[0016] In a fourth aspect, an embodiment of the present application provides a device status monitoring apparatus, comprising: a receiving module, a processing module and a sending module;

[0017] The receiving module is configured to receive a subscription request sent by a user terminal, wherein the subscription request includes: an identifier of the user terminal and / or an identifier of a target user corresponding to the user terminal;

[0018] The processing module is used to monitor the device and / or device status belonging to the target user according to the subscription request;

[0019] The sending module is used to send a notification message to the user terminal when the device and / or device status belonging to the target user changes, and the notification message includes: change information of the device and / or device status belonging to the target user.

[0020] In a fifth aspect, an embodiment of the present application provides a user terminal, including:

[0021] Processor, memory, transceiver, and interface for communicating with cloud servers;

[0022] The memory stores computer-executable instructions;

[0023] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in the first aspect above.

[0024] In one implementation, the processor may be a chip.

[0025] In a sixth aspect, an embodiment of the present application provides a cloud server, including:

[0026] Processor, memory, transceiver, and interface for communicating with user terminals;

[0027] The memory stores computer-executable instructions;

[0028] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in the second aspect above.

[0029] In one implementation, the processor may be a chip.

[0030] In a seventh aspect, an embodiment of the present application may provide a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect.

[0031] In an eighth aspect, an embodiment of the present application may provide a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the second aspect.

[0032] In a ninth aspect, an embodiment of the present application provides a program, which, when executed by a processor, is used to execute the method described in the first aspect.

[0033] In a tenth aspect, an embodiment of the present application provides a program, which, when executed by a processor, is used to execute the method described in the second aspect.

[0034] In an eleventh aspect, an embodiment of the present application provides a computer program product, including program instructions, and the program instructions are used to implement the method described in the first aspect.

[0035] In a twelfth aspect, an embodiment of the present application provides a computer program product, including program instructions, and the program instructions are used to implement the method described in the second aspect.

[0036] In a thirteenth aspect, an embodiment of the present application provides a chip, including: a processing module and a communication interface, and the processing module can execute the method described in the first aspect.

[0037] Furthermore, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the method described in the first aspect.

[0038] In a fourteenth aspect, an embodiment of the present application provides a chip, comprising: a processing module and a communication interface, and the processing module can execute the method described in the second aspect.

[0039] Furthermore, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the method described in the second aspect.

[0040] The device status monitoring method, apparatus, device and storage medium provided in the embodiments of the present application, the user terminal sends a subscription request to the cloud server, and the cloud server can monitor the device and / or device status belonging to the target user according to the received subscription request, and when the device and / or device status belonging to the user changes, the cloud server sends notification information to the user terminal corresponding to the target user, so that the user terminal can obtain the change information of the device and / or device status that needs to be controlled in a timely and accurate manner, thereby improving the accuracy of the status information of the IoT device obtained, and thereby improving the accuracy of the device control. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of the structure of a device monitoring system applicable to the device status monitoring method provided in an embodiment of the present application;

[0042] Figure 2 A schematic diagram of the interaction between the client and the server in the existing subscription technology;

[0043] Figure 3 An interactive schematic diagram of the first embodiment of the device status monitoring method provided by the present application;

[0044] Figure 4 This is an interactive diagram of Embodiment 2 of the device status monitoring method provided by this application;

[0045] Figure 5 This is an interactive diagram of Embodiment 3 of the device status monitoring method provided in this application;

[0046] Figure 6 This is an interactive diagram of Embodiment 4 of the device status monitoring method provided by this application;

[0047] Figure 7 This is an interactive diagram of Embodiment 5 of the device status monitoring method provided in this application;

[0048] Figure 8 This is an interactive diagram of Embodiment 6 of the device status monitoring method provided by this application;

[0049] Fig. 9 This is an interactive diagram of Embodiment 7 of the device status monitoring method provided by this application;

[0050] Fig.10 A schematic diagram of the structure of the first embodiment of the device status monitoring device provided by the present application;

[0051] Fig.11 A schematic diagram of the structure of the second embodiment of the device status monitoring device provided by the present application;

[0052] Fig.12 A block diagram of a user terminal for implementing a device status monitoring method provided by the present application;

[0053] Fig.13 A block diagram of a cloud server for implementing a device status monitoring method provided in this application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0055] The terms "first", "second", etc. in the specification, claims, and above-mentioned drawings of the embodiments of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0056] Figure 1 This is a schematic diagram of the structure of the device monitoring system to which the device status monitoring method provided in the embodiment of the present application is applicable. Figure 1 As shown, the system may include: a user terminal 11, a cloud platform 12 and at least one IoT device 13. The user terminal 11 and the at least one IoT device 13 may be registered on the cloud platform 12, and the cloud platform is deployed with a cloud server 120, so that the user terminal 11 and the cloud server 120, the cloud server 120 and the at least one IoT device 13 may communicate with each other, and the cloud server 120 may uniformly manage all devices connected to the network.

[0057] By way of example, in the embodiments of the present application, the at least one IoT device 13 belongs to the same user, and the user controls the IoT device through the user terminal 11. It is understandable that the IoT devices registered to the cloud server 120 may also belong to different users, which can be determined according to actual needs and are not limited here.

[0058] Exemplarily, when the at least one IoT device 13 belongs to the user corresponding to the user terminal 11, if the user terminal 11 and the at least one IoT device 13 are in the same local area network, the user terminal 11 and the at least one IoT device 13 can also communicate with each other. If the user terminal 11 and the at least one IoT device 13 are in different local area networks, at this time, the user terminal 11 can communicate with the at least one IoT device 13 through the cloud server 120 on the cloud platform 12.

[0059] For example, in actual applications, currently commonly used IoT devices can usually be registered on the cloud platform 12, and after registering on the cloud platform 12, the IoT devices can publish their discoverable resources to the resource directory ( / oic / rd directory) of the cloud platform 12, which will be saved and uniformly managed by the cloud server 120. In this way, the application of the user terminal 11 can discover the device under the target user and some attributes of the device by viewing the resource information saved by the cloud server 120. Exemplarily, the resources published by the IoT device to the resource directory may include the / res resources, / d resources, and other functional resources of the IoT device.

[0060] Among them, the / res resource contains the link of the discoverable resources published by the IoT device and the link of the / d resource; the / d resource is the device attribute resource of the IoT device, such as: the name of the IoT device, the identification (ID) of the IoT device and other information; other functional resources refer to the specific capability information of the IoT device, such as temperature resources, switch resources, etc. It can be understood that the IoT device needs to be discovered after registering on the cloud platform, so it can publish the resources that are allowed to be accessed to the / oic / rd resource directory of the cloud platform.

[0061] For example, in the embodiments of the present application, refer to Figure 1As shown, if the user terminal 11 belongs to the user 10, and the at least one IoT device 13 belonging to the user 10 will publish its discoverable resources to the resource directory of the cloud platform 12 after registering with the cloud platform 12, then the user 10 can use the user terminal 11 to discover the device to be controlled through the cloud platform 12, and obtain the resource information of the at least one IoT device 13, the registration / logout status on the cloud platform 12, the online and offline status (connected to the cloud server 120 or not connected to the cloud server 120) and other device status, and finally the device to be controlled can be remotely controlled according to the obtained resource information and device status.

[0062] In practical applications, the user terminal 11 may be a terminal device such as a smart phone or a tablet computer. The IoT device may be a smart TV, a smart refrigerator, a smart washing machine, a smart air conditioner, etc. The embodiment of the present application does not limit the specific manifestation of the user terminal 11 and the IoT device, which may be determined according to actual conditions.

[0063] At least one application (APP) is installed on the user terminal 11, including an application for managing IoT devices. The user can communicate with the cloud server 120 and IoT devices through the application installed on the user terminal 11.

[0064] In actual applications, there is an unreadable account resource ( / account resource) and an unreadable session resource ( / session resource) on the cloud platform 12 , which are maintained by the cloud server 120 .

[0065] Among them, the / account resource is mainly used to manage device registration. A correspondence between a device identifier (device ID) and a user identifier (User ID) is maintained in the / account resource; when a device is deregistered from the cloud platform 12, the cloud server 120 will delete the correspondence between the device identifier and the user identifier from the account directory.

[0066] The / session resource is mainly used to manage the online and offline status of the device, that is, whether the IoT device is connected to the cloud server or not; therefore, a relationship table between the device ID and the login status is maintained in the / session resource; when a device is connected to the cloud server, the cloud server sets the login status corresponding to the device ID to true; when a device is not connected to the cloud server, the cloud server sets the login status corresponding to the device ID to false.

[0067] In summary, in the prior art, user terminals can remotely control IoT devices registered to the cloud platform through the cloud platform. However, the premise of its control is to obtain all IoT devices under the user to which the user terminal belongs from the account resources on the cloud platform, and to obtain resources such as the device status of each IoT device from the session resources. However, the account resources and session resources on the cloud platform are unreadable by other devices, which may cause the user terminal to obtain inaccurate status information of the IoT device from the cloud platform, thereby causing the problem of inaccurate device control.

[0068] In response to the above problems, an embodiment of the present application provides a device status monitoring method, by which a subscription request is sent to a cloud server through a user terminal. The cloud server can monitor the devices and / or device status belonging to the target user according to the received subscription request, and when the devices and / or device status belonging to the user change, the cloud server sends notification information to the user terminal corresponding to the target user, so that the user terminal can obtain the change information of the devices and / or device status that need to be controlled in time, thereby improving the accuracy of the status information of the IoT devices obtained, and thereby improving the accuracy of the device control.

[0069] The overall concept of the technical solution of the present application is: based on the current development of subscription (or push) technology, the idea of ​​subscription technology can be applied to the Internet of Things system, that is, the user terminal can send a subscription request to the cloud server through a specific uniform resource identifier (URI), thereby completing the subscription to the information of the Internet of Things device and the cloud server, and by monitoring specific resources, timely discovering changes in the device and / or device status of a certain user, laying the foundation for subsequent accurate control of the Internet of Things device.

[0070] For example, in an embodiment of the present application, the subscription content corresponding to the subscription request may include device registration information, device deregistration information, device online and offline information, and resource change information. The cloud server can perceive information such as device registration and device deregistration by monitoring / account resources, perceive device online and offline by monitoring / session resources, and perceive resource change information of the target device by subscribing to the target device resources.

[0071] Before introducing the technical solution of the present application, the development of subscription technology is first explained.

[0072] With the development of Internet technology, the Internet of Things and smart home applications have gradually entered people's lives. The inventors have found that users can subscribe to favorite news topics (e.g., sports, celebrities, etc.) from news providers through the APP of the user terminal. When the subscribed news topic has news updates, the corresponding news message will be pushed to the APP of the user terminal, so that the user can read the news message in time.

[0073] Moreover, with the development of subscription (or push) technology, news subscription (or push) technology can be applied not only to information transmission between device and cloud platform communication (device to cloud, D2C), but also to application service processing in terminal devices and information transmission between devices (device to device, D2D). For example, a mobile phone subscribes to the temperature of a thermometer at home, and when the temperature of the thermometer is greater than or equal to the set temperature (for example, 26 degrees Celsius), the air conditioner is turned on.

[0074] For example, Figure 2 The following is a schematic diagram of the interaction between the client and the server in the existing subscription technology. The client can be an application installed on the user terminal, and the server can be a service function of the server. Figure 2 As shown, the interaction steps between the existing client and server are as follows:

[0075] S201. The client sends a subscription request to the server.

[0076] The type of the subscription request is Retrieve, and Observe is used to indicate that the subscription request is a subscription message. Exemplarily, the subscription request may include the following parameters:

[0077] Fr (from): the message initiator, specifically the identifier of the device where the client is located;

[0078] To: message receiver, used to receive the resource identifier subscribed by the client;

[0079] Ri (Request identifier): Request identifier, used to complete the binding of request and response;

[0080] Op (Operation): operation type, generally one of the CURDs. The CURD is the rest operation type. CURDs correspond to Create, Update, Retrieve, and Delete respectively.

[0081] Obs: Subscription ID.

[0082] S202, the server authenticates the received subscription request and establishes a monitoring mechanism after authentication;

[0083] S203, the server feeds back a subscription response to the client;

[0084] In this embodiment, the subscription response is a response message to the above subscription request, and its purpose is to respond to the subscription request of the client Client, that is, to inform the client that the server has received the subscription request and started monitoring.

[0085] S204, the server detects that the resource information corresponding to the subscription request has changed, and determines the resource change information;

[0086] S205: The server sends the resource change information to the client.

[0087] It can be understood that the Ri carried in the subscription request in S201, the subscription response in S203, and the resource change information in S205 are consistent.

[0088] From the above analysis, it can be seen that according to S201 to S205, a message subscription / notification cycle is completed. If the subscription to resource information needs to be canceled, the client sends a subscription cancellation request to the server, which is specifically reflected in the Obs parameter in the subscription cancellation request being set to the subscription cancellation identifier.

[0089] Combined with the above introduction to the equipment status monitoring system applicable to this application and the content of the knowledge involved, the following is a detailed description of the technical solution of this application through specific embodiments. It should be noted that the technical solution of this application may include part or all of the following contents, and the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0090] Figure 3 This is an interactive diagram of the first embodiment of the device status monitoring method provided by this application. Figure 3 Used to explain the information interaction between the user's user terminal and the cloud server. Figure 3 As shown, the method may include the following steps:

[0091] S301. The user terminal sends a subscription request to the cloud server.

[0092] The subscription request is used to instruct the cloud server to feed back change information to the user terminal corresponding to the target user when detecting that the device and / or device status belonging to the target user has changed.

[0093] In one implementation, the subscription request includes: an identifier of a user terminal and / or an identifier of a target user corresponding to the user terminal. That is, the subscription request may include an identifier of the user terminal, or the subscription request includes an identifier of a target user corresponding to the user terminal, or the subscription request includes an identifier of the user terminal and an identifier of the target user corresponding to the user terminal. The specific contents of the subscription request may be set according to the actual scenario, and will not be described in detail here.

[0094] For example, in one possible design of the present application, the uniform resource identifier (URI) of the subscription request is used to indicate the subscription content corresponding to the subscription request. In another possible design of the present application, the uniform resource identifier of the subscription request is used to indicate the subscription object and subscription content corresponding to the subscription request. That is, in an embodiment of the present application, the user terminal can indicate the subscription content or the subscription object and subscription content corresponding to the subscription request through the URI of the subscription request.

[0095] It can be understood that if the URI of the subscription request is only used to indicate the subscription content corresponding to the subscription request, the subscription object corresponding to the subscription request can be understood as all devices under the target user corresponding to the user terminal; if the URI of the subscription request is used to indicate the subscription object and subscription content corresponding to the subscription request, the subscription object corresponding to the subscription request is only a specific device or a specific set of devices under the target user corresponding to the user terminal.

[0096] That is, in the embodiment of the present application, the subscription object corresponding to the subscription request is any one of the following:

[0097] All devices belonging to the target user, a collection of devices belonging to the target user, a device belonging to the target user.

[0098] In addition, in the embodiment of the present application, the subscription content corresponding to the subscription request may be any of the following:

[0099] Device registration information, device deregistration information, device online information, device offline information, and device resource change information.

[0100] That is, the user terminal can determine the content to be subscribed according to the demand, and send a subscription request to the cloud server, so that the cloud server can perform corresponding operations according to the received subscription request.

[0101] It is understandable that in actual applications, the subscription of device registration information and device deregistration information is usually for the target user corresponding to the user terminal, that is, the subscription request of device registration information and / or device deregistration information corresponds to all devices under the target user. The subscription of device online information, device offline information, and device resource change information can be for all devices or certain devices under the target user corresponding to the user terminal. Therefore, the user terminal can indicate its corresponding subscription object and / or subscription content through the URL of the subscription request based on the user's instructions. Accordingly, depending on the subscription content and / or subscription object corresponding to the subscription request, the specific form of the subscription request can be any of the following:

[0102] 1. The subscription request is a subscription request for device registration information, and the URI of the subscription request is / devices / registration. In this case, the subscription request indicates subscribing to the registration information reminders of all devices belonging to the target user;

[0103] 2. The subscription request is a subscription request for device deregistration information, and the URI of the subscription request is / devices / deregistration. In this case, the subscription request indicates a subscription to the deregistration information reminder of all devices belonging to the user;

[0104] 3. The subscription request is a subscription request for device online information;

[0105] At this time, as an example, if the URI of the subscription request is / devices / Online, the subscription request indicates subscribing to online information reminders of all devices belonging to the target user;

[0106] As another example, if the URI of the subscription request is / devices / {deviceID} / Online, the subscription request indicates a subscription to an online information reminder of a specific device belonging to the target user, and the identifier of the specific device is the deviceID;

[0107] 4. The subscription request is a subscription request for device offline information;

[0108] At this time, as an example, if the URI of the subscription request is / devices / Offline, the subscription request indicates subscribing to offline information reminders of all devices belonging to the target user;

[0109] As another example, if the URI of the subscription request is / devices / {deviceID} / Offline, the subscription request indicates subscribing to offline information reminders of a specific device belonging to the target user, and the identifier of the specific device is deviceID;

[0110] 5. The subscription request is a subscription request for changing device resource information;

[0111] At this time, as an example, if the URI of the subscription request is / devices / propertychange, the subscription request means subscribing to the resource change information reminder of the published resources of all devices under the target user, that is, the subscription request is for the resource information changes of all devices belonging to the target user saved by the cloud platform.

[0112] As another example, the URI of the subscription request is / devices / {deviceID} / propertychange. In this case, the subscription request indicates subscribing to resource information changes of a specific device under the target user. It is worth noting that in this example, if the cloud server wants to be informed of resource information changes of a specific device in a timely manner, the cloud server needs to send a subscription request for resource information changes to the specific device, so that when resource information changes occur, the specific device can push them to the cloud server in a timely manner, and then push them to the user terminal.

[0113] For example, in the embodiments of the present application, the specific form of the subscription request can be determined according to actual needs, which will be introduced in the following embodiments respectively and will not be repeated here.

[0114] S302: The cloud server monitors the device and / or device status belonging to the target user according to the received subscription request.

[0115] In the embodiment of the present application, after the user terminal sends a subscription request to the cloud server, the cloud server can receive the subscription request, and determine the target user who sends the subscription request, and the subscription content or subscription content and subscription object corresponding to the subscription request by analyzing the URI of the subscription request. Therefore, the cloud server can monitor the device and / or device status belonging to the target user according to the subscription content or subscription content and subscription object corresponding to the subscription request.

[0116] In one embodiment, monitoring the device belonging to the target user mainly refers to monitoring the device registration and / or device deregistration information of the target user, and monitoring the device status of the target user mainly refers to monitoring at least one of the device online information, device offline information and device resource change information of the target user.

[0117] The specific implementation of this step can be found in the records in the following embodiments, which will not be repeated here.

[0118] S303: When determining that a device and / or device status belonging to the target user has changed, the cloud server generates notification information.

[0119] The notification message includes: change information of the device and / or device status belonging to the target user.

[0120] In an embodiment of the present application, upon receiving a subscription request sent by a user device, the cloud server begins to monitor the devices and / or device status of the target user in real time, and generates a notification message when it is determined that the devices and / or device status belonging to the target user have changed.

[0121] In one embodiment, determining that a device belonging to the target user has changed refers to monitoring that a device is newly registered to the target user or that a device is deregistered from the target user (also called deregistration); determining that the device status of the target user has changed refers to monitoring that the device under the target user has changed from online to offline or the device under the target user has changed from offline to online or the device resource information under the target user has changed, etc.

[0122] It is understandable that the embodiments of the present application do not limit the specific manifestations of the change in the device and / or device status belonging to the target user, which can be determined based on actual conditions.

[0123] S304: The cloud server sends a notification message to the user terminal.

[0124] In one embodiment, when the cloud server determines that the device and / or device status belonging to the target user has changed, it sends the generated notification message to the user terminal so that the target user can promptly and accurately obtain the device information or device status information that he wants to control.

[0125] It is understandable that in the embodiment of the present application, when the cloud server receives the above subscription request and starts monitoring the devices and / or device status of the target user, it will feedback a subscription response to the user terminal to indicate the cloud server's response to the received subscription request. The specific content of the response can be determined according to the subscription content corresponding to the subscription request, and will not be repeated here.

[0126] In the device status monitoring method provided in the embodiment of the present application, a user terminal sends a subscription request to a cloud server, and the cloud server can monitor the device and / or device status belonging to the target user according to the received subscription request, and when the device and / or device status belonging to the user changes, a notification message is sent to the user terminal corresponding to the target user, so that the user terminal can obtain the change information of the device and / or device status that needs to be controlled in a timely and accurate manner, thereby improving the accuracy of the status information of the IoT device obtained, and thereby improving the accuracy of the device control.

[0127] Furthermore, in an embodiment of the present application, after obtaining the change information of the device and / or the device status information, the user terminal can remotely control the device to be controlled according to the status information of the device to be controlled.

[0128] The embodiments of the present application do not limit the specific implementation of remote control, which can be implemented according to actual conditions and will not be described in detail here.

[0129] Exemplarily, based on the above embodiments, Figure 4 This is an interactive diagram of the second embodiment of the device status monitoring method provided by this application. Figure 4 As shown, if the user terminal wants to obtain the device information of the target user from the cloud platform, the user terminal needs to register on the cloud platform first. That is, before the above S301 (the user terminal sends a subscription request to the cloud server), the method may also include the following steps:

[0130] S401: Determine whether a user terminal corresponding to a target user has been registered in a cloud platform.

[0131] In the embodiments of the present application, in the device status monitoring system (Internet of Things system), generally speaking, only after all devices are registered on the cloud platform can conventional operations be performed through the cloud server on the cloud platform. Therefore, before the user terminal sends a subscription request to the cloud server, the user terminal needs to first register on the cloud platform; and only after the device is registered on the cloud platform will the device go online or offline. However, it is worth noting that the online and offline of the device is not necessarily related to the registration and deregistration of the device.

[0132] Further, in an embodiment of the present application, if the above-mentioned subscription request includes the identifier of the user terminal and the identifier of the target user corresponding to the user terminal, or the above-mentioned subscription request includes the identifier of the target user corresponding to the user terminal, the cloud server can directly obtain the identifier of the target user according to the received subscription request, but if the above-mentioned subscription request includes the identifier of the user terminal but does not include the identifier of the target user corresponding to the user terminal, then before the above-mentioned S302 (the cloud server monitors the device and / or device status belonging to the target user according to the received subscription request), the method may also include the following steps:

[0133] S402: The cloud server determines, based on the identifier of the user terminal, an identifier of a target user corresponding to the user terminal.

[0134] In an embodiment of the present application, since the premise for the cloud server to monitor the devices under the target user is that the cloud server has obtained the identification of the target user, if the subscription request sent by the user terminal does not carry the identification of the target user, the cloud server can first determine the identification of the user terminal that sent the subscription request, and then determine the identification of the target user based on the correspondence between the identification of the user terminal stored in the cloud platform and the identification of the target user.

[0135] It is understandable that the correspondence between the identifier of the user terminal stored in the cloud platform and the identifier of the target user is determined and stored by the cloud server when the user terminal is registered to the cloud platform.

[0136] The device status monitoring method provided in the embodiment of the present application determines that the user terminal corresponding to the target user has been registered in the cloud platform before the user terminal sends a subscription request to the cloud server, which is a prerequisite for the subsequent monitoring of the device and / or device status under the target user; when the subscription request includes the identifier of the user terminal but does not include the identifier of the target user corresponding to the user terminal, the identifier of the target user corresponding to the user terminal is determined based on the identifier of the user terminal, which can ensure that the cloud server promptly determines the target user to be monitored and the device under the target user, laying a foundation for the implementation of this solution.

[0137] For example, from the above analysis, it can be seen that in each embodiment of the present application, the subscription content corresponding to the subscription request is any one of the following: device registration information, device deregistration information, device online information, device offline information, and device resource change information.

[0138] Exemplarily, the specific implementation of the above S302 (the cloud server monitors the device and / or device status belonging to the target user according to the received subscription request) is described below according to different subscription contents corresponding to the subscription request.

[0139] For example, if the subscription content corresponding to the subscription request is device registration information or device deregistration information, the above S302 can be performed as follows: Figure 5 The embodiment shown and Figure 6 The embodiment shown or Figure 7 The illustrated embodiment is described.

[0140] If the subscription content corresponding to the subscription request is device online information or device offline information, the above S302 can be performed as follows: Figure 8 If the subscription content corresponding to the subscription request is device resource change information, the above S302 can be performed as follows: Fig. 9 The illustrated embodiment is described.

[0141] For example, Figure 5This is an interactive diagram of the third embodiment of the device status monitoring method provided by this application. In this embodiment, when the subscription content corresponding to the subscription request is device registration information or device deregistration information, such as Figure 5 As shown, the above S302 can be implemented by the following steps:

[0142] S501: Monitor account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user, and obtain account resource monitoring results.

[0143] In an embodiment of the present application, since the registration and / or deregistration of the device is managed by the account resources ( / account resources) within the cloud platform, after the cloud server receives a subscription request from the user terminal, it first determines the target user of the subscription, and then monitors the account resources on the cloud platform, that is, monitors the changes in the device information under the target user in the account resources, and obtains the account resource monitoring result corresponding to the target user.

[0144] S502: Determine whether device information belonging to the target user in the account resources has changed according to the account resource monitoring result.

[0145] In one embodiment, the cloud server determines whether the device information belonging to the target user has changed based on the obtained account resource monitoring results, that is, determines whether a new device has been added or a device has been deleted in the account resources, thereby determining whether the device change information needs to be pushed to the user terminal.

[0146] Accordingly, in the embodiment of the present application, the above S303 can be implemented by the following steps:

[0147] S503: When the device information of the target user in the account resources is changed, a notification message is generated, where the notification message is used to indicate the device change information of the target user.

[0148] In an embodiment of the present application, if the cloud server determines that the device information belonging to the target user in the account resources has changed, for example, resources of new devices have been added to the account resources or resources of one or some devices have been deleted from the account resources, a notification message is generated, and the device change information belonging to the target user is indicated through the notification message.

[0149] In the device status monitoring method provided in the embodiment of the present application, the cloud server monitors the account resources on the cloud platform according to the identification of the user terminal and / or the identification of the target user, obtains the account resource monitoring results, and then determines whether the device information belonging to the target user in the account resources has changed, and finally generates a notification message when the device information belonging to the target user in the account resources has changed. The notification message is used to indicate the device change information belonging to the target user. In this solution, the cloud server can promptly determine and generate a notification message when the device information belonging to the target user has changed by monitoring the account resources, laying the foundation for the timely push of subsequent messages.

[0150] For example, in Figure 5 Based on the embodiment shown, Figure 6 This is an interactive diagram of the fourth embodiment of the device status monitoring method provided by this application. Figure 6 As shown, when the subscription content corresponding to the subscription request is device registration information, the above S503 can be specifically implemented through the following steps:

[0151] S601. When a first device belonging to a target user is added to an account resource, a notification message is generated, where the notification message is used to indicate that the first device belonging to the target user is successfully registered on the cloud platform.

[0152] In the embodiment of the present application, when the user terminal subscribes to the device registration information, when the cloud server monitors (senses) that the first device belonging to the target user is newly added to the account resources, it indicates that the target user has a new device registered on the cloud platform, so a notification message is generated. In this embodiment, the specific meaning of the notification message is to indicate that the first device belonging to the target user is successfully registered on the cloud platform.

[0153] It can be understood that the first device in this embodiment does not represent an order, it is only used to represent a device that is newly registered on the cloud platform and belongs to the target user. The embodiment of the present application does not limit the specific implementation of the first device, which can be determined according to the scenario and will not be repeated here.

[0154] In one implementation, when the cloud server determines that a first device is newly added to the target user, before that, an interaction process should be performed between the first device and the cloud platform to ensure that the first device is successfully registered on the cloud platform. Figure 6 As shown, before the above S501, the method further includes:

[0155] S600a. The cloud server receives a registration request sent by the first device.

[0156] The registration request includes: an identifier of the first device, an identifier of a target user to which the first device belongs, and access token information.

[0157] In an embodiment of the present application, for devices in an Internet of Things system, if the first device needs to be registered on a cloud platform, the user can control the first device to send a registration request to the cloud server, that is, the first device actively sends a modification request to the cloud server of the cloud platform to modify the / account resource in the cloud platform, and accordingly, the cloud server can receive the registration request.

[0158] For example, in order for the cloud server to distinguish the registered device and the user to which it belongs, the registration request sent by the first device needs to carry the identifier of the first device, the identifier of the target user to which the first device belongs, and the access token information (AccessToken). The access token information is used to verify the first device and is used as a necessary parameter to determine whether the modification can be executed. The cloud server will respond only when the registration request sent by the first device carries the access token information and the identity authentication of the first device is passed.

[0159] S600b: According to the access token information, a correspondence between the identifier of the first device and the identifier of the target user to which the first device belongs is added in the account resources.

[0160] In the embodiment of the present application, when the cloud server determines that the registration request of the first device is legitimate according to the access token information, it can add the target user's ID, the first device's ID, and the access token information in the / account resource, thereby adding the corresponding relationship between the first device's identifier and the identifier of the target user to which the first device belongs to the account resource. Therefore, the cloud server can accurately and timely determine the registration of new devices by monitoring the account resource.

[0161] S600c: Feedback a registration completion response to the first device.

[0162] When the cloud server determines that the first device is successfully registered with the cloud platform, it can feed back a response message such as a registration completion response to the first device to notify the first device of the registration result.

[0163] Further, in an embodiment of the present application, after the first device determines that it has successfully registered with the cloud platform, it can publish its resources that are allowed to be discovered on the cloud platform at a selected time, and the published resources can be device attribute resources of the first device, etc. / d resources. In one embodiment, when the above-mentioned published resources are successfully published to the cloud platform, the cloud server can also feedback a publishing completion notification to the first device.

[0164] In the device status monitoring method provided by the embodiment of the present application, when the first device is successfully registered with the cloud platform, the cloud server can determine that the first device belonging to the target user has been newly added to the account resources by monitoring the account resources, and generate a notification message to indicate that the first device belonging to the target user has been successfully registered with the cloud platform. In this solution, when the cloud server detects changes in the device registration information of the target user, it can promptly feedback the device registration information to the user terminal, so that the target user can obtain accurate device registration information, thereby improving the subsequent device control accuracy.

[0165] For example, in Figure 5 Based on the embodiment shown, Figure 7 This is an interactive diagram of the fifth embodiment of the device status monitoring method provided by this application. Figure 7 As shown, when the subscription content corresponding to the subscription request is device deregistration information, the above S503 can be specifically implemented through the following steps:

[0166] S701. When a second device belonging to a target user is deleted from an account resource, a notification message is generated, where the notification message is used to indicate that the second device belonging to the target user has been deregistered from the cloud platform.

[0167] In the embodiment of the present application, when the user terminal subscribes to the device deregistration information, when the cloud server monitors (perceives) that the second device belonging to the target user is deleted from the account resources, it indicates that the second device of the target user has been deregistered from the cloud platform, so a notification message is generated. In this embodiment, the specific meaning of the notification message is to indicate that the second device belonging to the target user has been deregistered from the cloud platform.

[0168] It can be understood that the second device in this embodiment does not represent an order, it is only used to represent a device belonging to the target user and logged out from the cloud platform. The embodiment of the present application does not limit the specific implementation of the second device, which can be determined according to the scenario and will not be repeated here.

[0169] In one embodiment, when the cloud server determines that the target user has lost the second device, before that, an interaction process should have been performed between the second device and the cloud platform to ensure that the second device has been deregistered from the cloud platform. Figure 7 As shown, before the above S501, the method further includes:

[0170] S700a. The cloud server receives a logout request sent by the second device, where the logout request includes: an identifier of the second device and an identifier of a target user to which the second device belongs.

[0171] In an embodiment of the present application, for a device that has been registered on a cloud platform, if a second device needs to be deregistered from the cloud platform, the user can control the second device to send a deregistration request to the cloud server to request that the relevant resource information of the second device be deleted from the cloud platform. Accordingly, the cloud server can receive the deregistration request.

[0172] In one embodiment, in order to ensure that the cloud server deregisters the correct device, the deregistration request sent by the second device carries the identifier of the second device and the identifier of the target user to which it belongs, so that the cloud server responds to the deregistration request based on the identifier of the second device and the identifier of the target user in the deregistration request.

[0173] S700b. According to the deregistration request, the correspondence between the identifier of the second device and the identifier of the target user is deleted from the account resources of the cloud platform.

[0174] In the embodiment of the present application, when a device is registered to the cloud platform, the cloud server adds the correspondence between the identifier of the registered device and the identifier of the target user to which it belongs to the account resource. Therefore, when the second device needs to be deregistered from the cloud platform, the correspondence between the identifier of the second device and the identifier of the target user can be deleted from the account resource of the cloud platform, and thus the account resource on the cloud platform will also change. Therefore, the cloud server can accurately and timely perceive the deregistration of the device by monitoring the account resource.

[0175] S700c. Feedback a deregistration completion response to the second device.

[0176] When the cloud server determines that the second device has been deregistered from the cloud platform, it can feed back a response message such as a deregistration completion response to the second device to notify the second device of the deregistration result.

[0177] In the device status monitoring method provided by the embodiment of the present application, when the second device is deregistered from the cloud platform, the cloud server can determine that the second device belonging to the target user is deleted from the account resources by monitoring the account resources, and generate a notification message to indicate that the second device belonging to the target user has been deregistered from the cloud platform. In this solution, when the cloud server monitors the change of the device deregistration information of the target user, it can promptly feedback the device deregistration information to the user terminal, so that the target user can obtain accurate device information, which also improves the subsequent device control accuracy.

[0178] For example, Figure 8 This is an interactive diagram of the sixth embodiment of the device status monitoring method provided by this application. In this embodiment, when the subscription content corresponding to the subscription request is device online information or device offline information, such as Figure 8 As shown, the above S302 can be implemented by the following steps:

[0179] S801. Monitor session resources on a cloud platform for maintaining device connection attribute information according to an identifier of a user terminal and / or an identifier of a target user, and obtain session resource monitoring results.

[0180] In an embodiment of the present application, since the connection attribute information of the device (for example, online and offline) is managed by the session resource ( / session resource) inside the cloud platform, a relationship table between the device ID and the login status is maintained on the session resource. Therefore, after the cloud server receives a subscription request from the user terminal, it first determines the target user of the subscription, and then monitors the session resources on the cloud platform, that is, monitors the login status changes of the device under the target user in the session resource, and obtains the session resource monitoring result corresponding to the target user.

[0181] Specifically, the cloud platform maintains the connection relationship between the cloud server and each device through the / session resource; the / session resource maintains information such as DeviceID\UserID\AccessToken\Login, where login=true indicates that the device is online, and login=false indicates that the device is offline; when the cloud server receives a subscription request for device online information or device offline information, it starts to monitor the / session resource and obtains the session resource monitoring result.

[0182] S802: Determine whether the device connection information of the target user has changed according to the session resource monitoring result.

[0183] In one embodiment, the cloud server determines whether the device connection information belonging to the target user has changed based on the obtained session resource monitoring results, that is, determines whether there are any devices belonging to the target user that have changed from offline to online or from online to offline, so as to determine whether it is necessary to push device status change information to the user terminal.

[0184] Accordingly, in the embodiment of the present application, the above S303 can be implemented by the following steps:

[0185] S803: When the device connection information belonging to the target user changes, a notification message is generated, where the notification message is used to indicate the device status change information belonging to the target user.

[0186] In an embodiment of the present application, when the cloud server determines that there is a device among all devices belonging to the target user that has changed from offline to online or from online to offline, a notification message is generated to indicate the device status change information belonging to the target user.

[0187] For example, in one embodiment of the present application, when the subscription content corresponding to the subscription request is device online information, S803 may be implemented by the following steps:

[0188] S803a1. When there is a device whose login attribute information value changes from false to true in the device connection information belonging to the target user, determine the identifiers of all devices whose login attribute information value changes.

[0189] S803a2. Generate a notification message based on the identifiers of all devices whose values ​​of the login attribute information have changed. The notification message is used to indicate that the device has changed from an offline state to an online state relative to the cloud server.

[0190] Exemplarily, when a device or some devices belonging to the target user go online, it will be reflected in the corresponding login attribute (= true); therefore, when the value of the device's login attribute information changes from false to true, it is considered that the device has changed from an offline state to an online state relative to the cloud server, and then a notification message is generated and sent to the user terminal to notify the user terminal of the device online information under the target user.

[0191] Exemplarily, in another embodiment of the present application, when the subscription content corresponding to the subscription request is device offline information, S803 may be implemented by the following steps:

[0192] S803b1. When there is a device whose login attribute information value changes from true to false in the device connection information belonging to the target user, determine the identifiers of all devices whose login attribute information value changes;

[0193] S803b2. Generate a notification message based on the identifiers of all devices whose values ​​of the login attribute information have changed. The notification message is used to indicate that the device has changed from an online state to an offline state relative to the cloud server.

[0194] Exemplarily, when a device or some devices belonging to the target user go offline, it will be reflected in the corresponding login attribute (=false); therefore, when the value of the device's login attribute information changes from true to false, it is considered that the device has changed from an online state to an offline state relative to the cloud server, and a notification message is generated and sent to the user terminal to notify the user terminal of the device offline information of the target user.

[0195] It is worth noting that in the embodiment of the present application, the device online information or device offline information subscribed by the user terminal can be for all devices under the target user, or only for a specific device under the target user. The implementation schemes of the two are similar and will not be repeated here.

[0196] The device status monitoring method provided in the embodiment of the present application monitors the session resources on the cloud platform for maintaining device connection attribute information according to the identifier of the user terminal and / or the identifier of the target user, obtains the session resource monitoring result, determines whether the device connection information belonging to the target user has changed according to the session resource monitoring result, and generates a notification message to indicate the device status change information belonging to the target user when the device connection information belonging to the target user has changed. In this solution, the cloud server can timely determine and generate a notification message when the device status information belonging to the target user has changed by monitoring the session resources, laying the foundation for the timely push of subsequent messages.

[0197] For example, Fig. 9 This is an interactive diagram of Embodiment 7 of the device status monitoring method provided by this application. In this embodiment, when the subscription content corresponding to the subscription request is device resource change information, such as Fig. 9 As shown, the above S302 can be implemented by the following steps:

[0198] S901. Determine resource publishing information of all devices of the target user on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user.

[0199] In an embodiment of the present application, since the device can publish resources on the cloud platform or not publish resources on the cloud platform after registering with the cloud platform, when the cloud server receives a subscription request for device resource change information, it first determines which devices under the target user have published resources on the cloud platform and which devices have not published resources on the cloud platform, and then performs different resource change monitoring processes for devices with different judgment results.

[0200] S902: For a device of a target user that has published resources on the cloud platform, monitor the published resources of the device.

[0201] In an embodiment of the present application, if the devices under the target user have published resources on the cloud platform, the resource changes of the resources published by these devices on the cloud platform are subscribed to. Accordingly, by monitoring the published resources of these devices, it is determined whether there are any resource changes.

[0202] S903: For a device of the target user that has not published resources on the cloud platform, monitor the subscribable resources of the device.

[0203] In an embodiment of the present application, if the devices under the target user have not published resources on the cloud platform, the subscription resources of these devices are subscribed, that is, subscription requests are sent to these devices through the cloud server to subscribe to the resource changes of these devices, and monitor whether these devices feedback resource change information.

[0204] For example, in an embodiment of the present application, S903 may be implemented by the following steps:

[0205] A1. Send a resource change subscription request to the device, where the resource change subscription request is used to request that resource change information be fed back to the cloud server when the subscribable resources of the device change.

[0206] A2. Obtain resource change information of subscribable resources of the device by receiving the resource change information sent by the device.

[0207] In one embodiment, if the cloud server wants to promptly obtain information about resource changes of a target user's device that has not published resources on the cloud platform, it can send a resource change subscription request to the device, so that when the device's subscribable resources send changes, the device can send resource change information to the cloud server. In this way, the cloud server can obtain the resource change information of the device's subscribable resources based on the received resource change information, thereby realizing timely discovery of changes in the device's resources.

[0208] Accordingly, in the embodiment of the present application, the above S303 can be implemented by the following steps:

[0209] S904: When a resource change occurs in a published resource and / or a subscribable resource of at least one device changes, determine a device identifier of the device where the resource change occurs and resource change information corresponding to the device identifier.

[0210] Exemplarily, based on the above S902 or S903, if the cloud server determines that the published resources have changed by monitoring the published resources on the cloud platform, the device identifier corresponding to the published resource and the corresponding resource change information are determined. If the cloud server subscribes to the change information reminder of the subscribable resources of the device, the resource change information of the subscribable resources of the device can also be determined by receiving the resource change information fed back by the device, and then the device identifier corresponding to the subscribable resource and the corresponding resource change information are determined.

[0211] S905: Generate a notification message according to the device identifier of the resource change and the resource change information corresponding to the device identifier.

[0212] In an embodiment of the present application, when the cloud server determines the device identification where resource changes have occurred and the resource change information corresponding to the device identification through the above S902 to S904, it can include the device identification where resource changes have occurred and the resource change information corresponding to the device identification in one message, thereby obtaining a notification message.

[0213] It is worth noting that, in the embodiment of the present application, the subscription of the device resource change information can be for all devices under the target user, or for a specific device under the target user. The implementation schemes of the two are similar and will not be repeated here.

[0214] The device status monitoring method provided in the embodiment of the present application determines the resource publishing information of all devices under the target user on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user, monitors the published resources of the device for the devices under the target user that have published resources on the cloud platform, and monitors the subscribable resources of the device for the devices under the target user that have not published resources on the cloud platform, and then determines the device identifier of the resource change and the resource change information corresponding to the device identifier when a resource change occurs in the published resources and / or a change occurs in the subscribable resources of at least one device, and then generates a notification message. In this technical solution, the user terminal subscribes to the device resource change information, so that the cloud server can provide feedback to the user terminal when it detects that the resource information of the device has changed, so that the user terminal can be informed of the resource changes of each device in a timely manner, laying a foundation for subsequently improving the accuracy of device control.

[0215] The above describes the specific implementation of the device status monitoring method mentioned in the embodiment of the present application. The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0216] Fig.10 This is a schematic diagram of the structure of the first embodiment of the device status monitoring device provided by this application. The device can be integrated in a user terminal or implemented through a user terminal. Fig.10 As shown, the device may include: a sending module 1001 and a receiving module 1002.

[0217] The sending module 1001 is used to send a subscription request to the cloud server, wherein the subscription request is used to instruct the cloud server to feedback the change information to the user terminal corresponding to the target user when the device and / or device status belonging to the target user is detected to have changed;

[0218] The receiving module 1002 is used to receive a notification message from the cloud server, where the notification message includes: change information of the device and / or device status belonging to the target user.

[0219] In one implementation, the subscription content corresponding to the subscription request is any one of the following:

[0220] Device registration information, device deregistration information, device online information, device offline information, and device resource change information.

[0221] As an example, the uniform resource identifier of the subscription request is used to indicate the subscription content corresponding to the subscription request.

[0222] As another example, the uniform resource identifier of the subscription request is used to indicate the subscription object and subscription content corresponding to the subscription request.

[0223] In one implementation, the subscription object corresponding to the subscription request is any one of the following:

[0224] All devices belonging to the target user, a set of devices belonging to the target user, a device belonging to the target user.

[0225] In a possible design of the present application, the device also includes: a processing module 1003.

[0226] The processing module 1003 is used to determine whether the user terminal corresponding to the target user has been registered in the cloud platform before the sending module 1001 sends a subscription request to the cloud server.

[0227] The device provided in this embodiment is used to perform the above Figures 3 to 9 The technical solution of the user terminal in the illustrated embodiment has similar implementation principles and technical effects, which will not be repeated here.

[0228] Fig.11 This is a schematic diagram of the structure of the second embodiment of the device status monitoring device provided by this application. The device can be integrated in a cloud server or implemented through a cloud server. Fig.11 As shown, the device may include: a receiving module 1101, a processing module 1102 and a sending module 1103.

[0229] The receiving module 1101 is configured to receive a subscription request sent by a user terminal, wherein the subscription request includes: an identifier of the user terminal and / or an identifier of a target user corresponding to the user terminal;

[0230] The processing module 1102 is used to monitor the device and / or device status belonging to the target user according to the subscription request;

[0231] The sending module 1103 is used to send a notification message to the user terminal when the device and / or device status belonging to the target user changes, and the notification message includes: change information of the device and / or device status belonging to the target user.

[0232] In one implementation, the subscription content corresponding to the subscription request is any one of the following:

[0233] Device registration information, device deregistration information, device online information, device offline information, and device resource change information.

[0234] As an example, the uniform resource identifier of the subscription request is used to indicate the subscription content corresponding to the subscription request.

[0235] As another example, the uniform resource identifier of the subscription request is used to indicate the subscription object and subscription content corresponding to the subscription request.

[0236] In one implementation, the subscription object corresponding to the subscription request is any one of the following:

[0237] All devices belonging to the target user, a set of devices belonging to the target user, a device belonging to the target user.

[0238] In a possible design of the present application, when the subscription request includes the identifier of the user terminal but does not include the identifier of the target user corresponding to the user terminal, the processing module 1102 is further used to determine the identifier of the target user corresponding to the user terminal based on the identifier of the user terminal.

[0239] In another possible design of the present application, the subscription content corresponding to the subscription request is device registration information or device deregistration information;

[0240] In this possible design, the processing module 1102 is specifically configured to:

[0241] Monitoring account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user to obtain an account resource monitoring result;

[0242] Determining, based on the account resource monitoring result, whether device information belonging to the target user in the account resource has changed;

[0243] When the device information belonging to the target user in the account resource changes, the notification message is generated, and the notification message is used to indicate the device change information belonging to the target user.

[0244] As an example, when the subscription content corresponding to the subscription request is device registration information, the processing module 1102 is used to generate the notification message when the device information belonging to the target user in the account resource changes, specifically:

[0245] The processing module 1102 is specifically configured to generate the notification message when a first device belonging to the target user is newly added to the account resources, wherein the notification message is used to indicate that the first device belonging to the target user is successfully registered on the cloud platform.

[0246] In this example, the receiving module 1101 is further used to receive a registration request sent by the first device before the processing module 1102 monitors the account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user and obtains the monitoring result, wherein the registration request includes: the identifier of the first device, the identifier of the target user to which the first device belongs, and access token information;

[0247] Correspondingly, the processing module 1102 is further configured to add, in the account resource, a correspondence between the identifier of the first device and the identifier of the target user to which the first device belongs, according to the access token information;

[0248] The sending module 1103 is further configured to feed back a registration completion response to the first device.

[0249] As another example, when the subscription content corresponding to the subscription request is device deregistration information, the processing module 1102 is used to generate the notification message when the device information belonging to the target user in the account resource changes, specifically:

[0250] The processing module 1102 is specifically used to generate the notification message when the second device belonging to the target user is deleted from the account resources, and the notification message is used to indicate that the second device belonging to the target user has been deregistered from the cloud platform.

[0251] In this example, the receiving module 1101 is further used to receive a logout request sent by the second device before the processing module 1102 monitors the account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user and obtains the monitoring result, wherein the logout request includes: the identifier of the second device and the identifier of the target user to which the second device belongs;

[0252] Correspondingly, the processing module 1102 is further configured to delete the correspondence between the identifier of the second device and the identifier of the target user from the account resources of the cloud platform according to the deregistration request;

[0253] The sending module 1103 is further configured to feed back a deregistration completion response to the second device.

[0254] In another possible design of the present application, the subscription content corresponding to the subscription request is device online information or device offline information;

[0255] Accordingly, the processing module 1102 is specifically configured to:

[0256] Monitoring session resources on the cloud platform for maintaining device connection attribute information according to the identifier of the user terminal and / or the identifier of the target user, and obtaining session resource monitoring results;

[0257] Determining, according to the session resource monitoring result, whether the device connection information belonging to the target user changes;

[0258] When the device connection information belonging to the target user changes, the notification message is generated, and the notification message is used to indicate the device status change information belonging to the target user.

[0259] As an example, when the subscription content corresponding to the subscription request is device online information, the processing module 1102 is used to generate the notification message when the device connection information belonging to the target user changes, specifically:

[0260] Processing module 1102 is specifically used to determine the identifiers of all devices whose login attribute information has changed values ​​when there is a device whose login attribute information has changed values ​​from false in the device connection information belonging to the target user, and generate the notification message based on the identifiers of all devices whose login attribute information has changed values, wherein the notification message is used to indicate that the device has changed from an offline state to an online state relative to the cloud server.

[0261] As another example, when the subscription content corresponding to the subscription request is device offline information, the processing module 1102 is used to generate the notification message when the device connection information belonging to the target user changes, specifically:

[0262] Processing module 1102 is specifically used to determine the identifiers of all devices whose login attribute information has changed values ​​when there is a device whose login attribute information has changed values ​​from true to false in the device connection information belonging to the target user, and generate the notification message based on the identifiers of all devices whose login attribute information has changed values, wherein the notification message is used to indicate that the device has changed from an online state to an offline state relative to the cloud server.

[0263] In another possible design of the present application, the subscription content corresponding to the subscription request is device resource change information;

[0264] Accordingly, the processing module 1102 is specifically configured to:

[0265] Determine resource publishing information of all devices under the target user on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user;

[0266] For a device of the target user that has published resources on the cloud platform, monitoring the published resources of the device;

[0267] For a device under the target user that has not published resources on the cloud platform, monitoring subscribable resources of the device;

[0268] When a resource change occurs to the published resource and / or a subscribable resource of the at least one device changes, determining an identifier of the device where the resource change occurs, and resource change information corresponding to the identifier of the device;

[0269] The notification message is generated according to the device identifier of the resource change and the resource change information corresponding to the device identifier.

[0270] In this possible design, the processing module 1102 is used to monitor the subscribable resources of the device when the target user has a device that has not published resources on the cloud platform, specifically:

[0271] The processing module 1102 is used to send a resource change subscription request to the device through the sending module 1103, and the resource change subscription request is used to request feedback of resource change information to the cloud server when the subscribable resources of the device change, and receive the resource change information sent by the device through the receiving module 1101 to obtain the resource change information of the subscribable resources of the device.

[0272] The device provided in this embodiment is used to perform the above Figures 3 to 9 The technical solution of the cloud server in the illustrated embodiment has similar implementation principles and technical effects, which will not be repeated here.

[0273] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the processing module can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The function of the above-mentioned module is determined. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0274] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, when a module above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0275] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

[0276] Fig.12 This is a block diagram of a user terminal for implementing a device status monitoring method provided by the present application. Fig.12As shown, the user terminal may include: a processor 1201, a memory 1202, a transceiver 1203, and an interface 1204 for communicating with other devices. In this embodiment, the other device may be a cloud server or an IoT device.

[0277] Among them, the memory 1202 stores computer-executable instructions;

[0278] The processor 1201 executes the computer-executable instructions stored in the memory 1202, so that the processor 1201 executes the technical solution on the user terminal side in any of the aforementioned method embodiments.

[0279] Fig.13 A block diagram of a cloud server for implementing a device status monitoring method provided in this application. Fig.13 As shown, the cloud server may include: a processor 1301, a memory 1302, a transceiver 1303, and an interface 1304 for communicating with other devices. In this embodiment, the other device may be a user terminal or an IoT device.

[0280] Among them, the memory 1302 stores computer-executable instructions;

[0281] The processor 1301 executes the computer execution instructions stored in the memory 1302, so that the processor 1301 executes the technical solution on the cloud server side in any of the aforementioned method embodiments.

[0282] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the technical solution on the user terminal side in any of the aforementioned method embodiments.

[0283] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the technical solution on the cloud server side in any of the aforementioned method embodiments.

[0284] The embodiment of the present application also provides a program, which, when executed by a processor, is used to execute the technical solution on the user terminal side in the aforementioned method embodiment.

[0285] The embodiment of the present application also provides a program, which, when executed by a processor, is used to execute the technical solution on the cloud server side in the aforementioned method embodiment.

[0286] The embodiment of the present application also provides a computer program product, including program instructions, which are used to implement the technical solution on the user terminal side in the aforementioned method embodiment.

[0287] The embodiment of the present application also provides a computer program product, including program instructions, which are used to implement the technical solution on the cloud server side in the aforementioned method embodiment.

[0288] The embodiment of the present application also provides a chip, including: a processing module and a communication interface, wherein the processing module can execute the technical solution of the user terminal in the aforementioned method embodiment.

[0289] Furthermore, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the technical solution on the user terminal side.

[0290] The embodiment of the present application also provides a chip, including: a processing module and a communication interface, and the processing module can execute the technical solution on the cloud server side in the aforementioned method embodiment.

[0291] Furthermore, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the technical solution on the cloud server side.

[0292] In the present application, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula, the character " / " indicates that the previous and next associated objects are in a "division" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0293] It is to be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not intended to limit the scope of the embodiments of the present application. In the embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Claims

1. A device status monitoring method, characterized in that: include: receiving a subscription request sent by a user terminal, the subscription request including: an identifier of the user terminal and / or an identifier of a target user corresponding to the user terminal; monitoring, according to the subscription request, devices and / or device states of subscription objects belonging to the target user, wherein the subscription objects are: all devices belonging to the target user, or a set of devices belonging to the target user; When it is detected that at least one device and / or device status in the subscription object belonging to the target user has changed, a notification message is sent to the user terminal, wherein the notification message includes: change information of the device and / or device status that has changed in the subscription object belonging to the target user; The monitoring of the device and / or device status of the subscription object of the target user according to the subscription request includes: Monitoring account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user to obtain an account resource monitoring result; Determining, according to the account resource monitoring result, whether device information of the subscription object belonging to the target user in the account resource has changed; When the device information of the subscription object belonging to the target user in the account resource changes, the notification message is generated, where the notification message is used to indicate the device change information corresponding to the device that has changed in the subscription object belonging to the target user; The subscription content corresponding to the subscription request includes device registration information, and when the device information of the subscription object belonging to the target user in the account resource changes, the notification message is generated, including: When a first device belonging to the target user is newly added to the account resources, the notification message is generated, and the notification message is used to indicate that the first device belonging to the target user is successfully registered on the cloud platform.

2. The method according to claim 1, characterized in that The subscription content corresponding to the subscription request also includes any of the following: Device deregistration information, device online information, device offline information, and device resource change information.

3. The method according to claim 1, characterized in that The subscription object is all devices belonging to the target user, and the uniform resource identifier of the subscription request is used to indicate the subscription content corresponding to the subscription request.

4. The method according to claim 1, characterized in that: The subscription object is a set of devices belonging to the target user, and the uniform resource identifier of the subscription request is used to indicate the subscription object and subscription content corresponding to the subscription request.

5. The method according to claim 1, characterized in that When the subscription request includes the identifier of the user terminal but does not include the identifier of the target user corresponding to the user terminal, the method further includes: An identifier of a target user corresponding to the user terminal is determined according to the identifier of the user terminal.

6. The method according to claim 1, characterized in that Before monitoring the account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user to obtain the monitoring result, the method further includes: receiving a registration request sent by the first device, the registration request including: an identifier of the first device, an identifier of a target user to which the first device belongs, and access token information; According to the access token information, adding a correspondence between the identifier of the first device and the identifier of the target user to which the first device belongs in the account resource; A registration completion response is fed back to the first device.

7. The method according to claim 2, characterized in that: When the subscription content corresponding to the subscription request includes device deregistration information, when the device information of the subscription object belonging to the target user in the account resource changes, generating the notification message includes: When the second device belonging to the target user is deleted from the account resources, the notification message is generated, and the notification message is used to indicate that the second device belonging to the target user has been deregistered from the cloud platform.

8. The method according to claim 7, characterized in that Before monitoring the account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user to obtain the monitoring result, the method further includes: receiving a deregistration request sent by the second device, the deregistration request including: an identifier of the second device and an identifier of a target user to which the second device belongs; Deleting, according to the deregistration request, the correspondence between the identifier of the second device and the identifier of the target user from the account resources of the cloud platform; A deregistration completion response is fed back to the second device.

9. The method according to any one of claims 2 to 5, characterized in that: When the subscription content corresponding to the subscription request includes device online information or device offline information, monitoring the device and / or device status of the subscription object of the target user according to the subscription request includes: Monitoring session resources on the cloud platform for maintaining device connection attribute information according to the identifier of the user terminal and / or the identifier of the target user, and obtaining session resource monitoring results; Determining, according to the session resource monitoring result, whether device connection information of the subscription object belonging to the target user changes; When the device connection information of the subscription object belonging to the target user changes, the notification message is generated, and the notification message is used to indicate the device status change information of the subscription object belonging to the target user.

10. The method according to claim 9, characterized in that The subscription object is all devices belonging to the target user. When the subscription content corresponding to the subscription request includes device online information, when the device connection information of the subscription object belonging to the target user changes, generating the notification message includes: When there is a device whose login attribute information value changes from false to true in the device connection information belonging to the target user, determining the identifiers of all devices whose login attribute information value changes; The notification message is generated according to the identification of all devices whose values ​​of the login attribute information are changed, and the notification message is used to indicate that the device is changed from an offline state to an online state relative to the cloud server.

11. The method according to claim 9, characterized in that The subscription object is all devices belonging to the target user. When the subscription content corresponding to the subscription request includes device offline information, when the device connection information of the subscription object belonging to the target user changes, generating the notification message includes: When there is a device whose login attribute information value changes from true to false in the device connection information belonging to the target user, determining the identifiers of all devices whose login attribute information value changes; The notification message is generated according to the identifiers of all devices whose values ​​of the login attribute information are changed, and the notification message is used to indicate that the device has changed from an online state to an offline state relative to the cloud server.

12. The method according to any one of claims 2 to 5, characterized in that: The subscription objects are all devices belonging to the target user. When the subscription content corresponding to the subscription request includes device resource change information, monitoring the devices and / or device states of the subscription objects belonging to the target user according to the subscription request includes: Determine resource publishing information of all devices under the target user on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user; For a device of the target user that has published resources on the cloud platform, monitoring the published resources of the device; For a device under the target user that has not published resources on the cloud platform, monitoring subscribable resources of the device; When a resource change occurs to the published resource and / or a subscribable resource of the at least one device changes, determining an identifier of the device where the resource change occurs, and resource change information corresponding to the identifier of the device; The notification message is generated according to the device identifier of the resource change and the resource change information corresponding to the device identifier.

13. The method according to claim 12, characterized in that When the target user has a device that has not published resources on the cloud platform, monitoring the subscribable resources of the device includes: Sending a resource change subscription request to the device, wherein the resource change subscription request is used to request feedback of resource change information to the cloud server when a subscribable resource of the device changes; By receiving the resource change information sent by the device, the resource change information of the subscribable resources of the device is obtained.

14. A device status monitoring device, characterized in that: include: Receiving module, processing module and sending module; The receiving module is configured to receive a subscription request sent by a user terminal, wherein the subscription request includes: an identifier of the user terminal and / or an identifier of a target user corresponding to the user terminal; The processing module is used to monitor the devices and / or device states of the subscription objects belonging to the target user according to the subscription request, wherein the subscription objects are: all devices belonging to the target user, or a set of devices belonging to the target user; The sending module is used to send a notification message to the user terminal when it is detected that at least one device and / or device status in the subscription object belonging to the target user has changed, and the notification message includes: change information of the device and / or device status that has changed in the subscription object belonging to the target user; The processing module is used to: Monitoring account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user to obtain an account resource monitoring result; Determining, according to the account resource monitoring result, whether device information of the subscription object belonging to the target user in the account resource has changed; When the device information of the subscription object belonging to the target user in the account resource changes, the notification message is generated, where the notification message is used to indicate the device change information corresponding to the device that has changed in the subscription object belonging to the target user; The subscription content corresponding to the subscription request includes device registration information. The processing module is used to generate the notification message when the device information of the subscription object belonging to the target user in the account resource changes, specifically: When the first device belonging to the target user is newly added to the account resources, the processing module generates the notification message, where the notification message is used to indicate that the first device belonging to the target user is successfully registered on the cloud platform.

15. The device according to claim 14, characterized in that The subscription content corresponding to the subscription request also includes any of the following: Device deregistration information, device online information, device offline information, and device resource change information.

16. The device according to claim 14, characterized in that The subscription object is all devices belonging to the target user, and the uniform resource identifier of the subscription request is used to indicate the subscription content corresponding to the subscription request.

17. The device according to claim 14, characterized in that The subscription object is a set of devices belonging to the target user, and the uniform resource identifier of the subscription request is used to indicate the subscription object and subscription content corresponding to the subscription request.

18. The device according to claim 14, characterized in that When the subscription request includes the identifier of the user terminal but does not include the identifier of the target user corresponding to the user terminal, the processing module is further configured to determine the identifier of the target user corresponding to the user terminal according to the identifier of the user terminal.

19. The device according to claim 14, characterized in that The receiving module is further configured to receive a registration request sent by the first device before the processing module monitors the account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user and obtains the monitoring result, wherein the registration request includes: the identifier of the first device, the identifier of the target user to which the first device belongs, and access token information; The processing module is further configured to add, in the account resource, a correspondence between an identifier of the first device and an identifier of a target user to which the first device belongs, according to the access token information; The sending module is further configured to feed back a registration completion response to the first device.

20. The device according to claim 15, characterized in that When the subscription content corresponding to the subscription request includes device deregistration information, the processing module is used to generate the notification message when the device information of the subscription object belonging to the target user in the account resource changes, specifically: When the processing module deletes the second device belonging to the target user from the account resources, the processing module generates the notification message, where the notification message is used to indicate that the second device belonging to the target user has been deregistered from the cloud platform.

21. The device according to claim 20, characterized in that The receiving module is further configured to receive a logout request sent by the second device before the processing module monitors the account resources on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user and obtains the monitoring result, wherein the logout request includes: the identifier of the second device and the identifier of the target user to which the second device belongs; The processing module is further configured to delete the correspondence between the identifier of the second device and the identifier of the target user from the account resources of the cloud platform according to the deregistration request; The sending module is further configured to feed back a logout completion response to the second device.

22. The device according to any one of claims 15 to 18, characterized in that The subscription content corresponding to the subscription request includes device online information or device offline information; The processing module is specifically used for: Monitoring session resources on the cloud platform for maintaining device connection attribute information according to the identifier of the user terminal and / or the identifier of the target user, and obtaining session resource monitoring results; Determining, according to the session resource monitoring result, whether device connection information of the subscription object belonging to the target user changes; When the device connection information of the subscription object belonging to the target user changes, the notification message is generated, and the notification message is used to indicate the device status change information of the subscription object belonging to the target user.

23. The device according to claim 22, characterized in that The subscription object is all devices belonging to the target user. When the subscription content corresponding to the subscription request includes device online information, the processing module is used to generate the notification message when the device connection information of the subscription object belonging to the target user changes, specifically: When there is a device whose login attribute information value changes from false to true in the device connection information belonging to the target user, the processing module determines the identifiers of all devices whose login attribute information value changes, and generates the notification message based on the identifiers of all devices whose login attribute information value changes, wherein the notification message is used to indicate that the device has changed from an offline state to an online state relative to the cloud server.

24. The device according to claim 22, characterized in that The subscription object is all devices belonging to the target user. When the subscription content corresponding to the subscription request includes device offline information, the processing module is used to generate the notification message when the device connection information of the subscription object belonging to the target user changes, specifically: When there is a device whose login attribute information value changes from true to false in the device connection information belonging to the target user, the processing module determines the identifiers of all devices whose login attribute information values ​​have changed, and generates the notification message based on the identifiers of all devices whose login attribute information values ​​have changed. The notification message is used to indicate that the device has changed from an online state to an offline state relative to the cloud server.

25. The device according to any one of claims 15 to 18, characterized in that The subscription content corresponding to the subscription request includes device resource change information; The processing module is specifically used for: Determine resource publishing information of all devices under the target user on the cloud platform according to the identifier of the user terminal and / or the identifier of the target user; For a device of the target user that has published resources on the cloud platform, monitoring the published resources of the device; For a device under the target user that has not published resources on the cloud platform, monitoring subscribable resources of the device; When a resource change occurs to the published resource and / or a subscribable resource of the at least one device changes, determining an identifier of the device where the resource change occurs, and resource change information corresponding to the identifier of the device; The notification message is generated according to the device identifier of the resource change and the resource change information corresponding to the device identifier.

26. The device according to claim 25, characterized in that The processing module is used to monitor the subscribable resources of the device when the target user has a device that has not published resources on the cloud platform, specifically: The processing module sends a resource change subscription request to the device through the sending module, and the resource change subscription request is used to request feedback of resource change information to the cloud server when the subscribable resources of the device change, and receives the resource change information sent by the device through the receiving module to obtain the resource change information of the subscribable resources of the device.

27. A cloud server, characterized in that: include: Processors, memory, transceivers, and interfaces for communicating with other devices; The memory stores computer instructions; The processor executes the computer instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 13.

28. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, which are used to implement the method according to any one of claims 1 to 13 when executed by a processor.

Images