WO2021232197A1 - Procédé et appareil de surveillance d'état de dispositif, dispositif, et support de stockage - Google Patents

Procédé et appareil de surveillance d'état de dispositif, dispositif, et support de stockage Download PDF

Info

Publication number
WO2021232197A1
WO2021232197A1 PCT/CN2020/090874 CN2020090874W WO2021232197A1 WO 2021232197 A1 WO2021232197 A1 WO 2021232197A1 CN 2020090874 W CN2020090874 W CN 2020090874W WO 2021232197 A1 WO2021232197 A1 WO 2021232197A1
Authority
WO
WIPO (PCT)
Prior art keywords
target user
information
resource
subscription
belonging
Prior art date
Application number
PCT/CN2020/090874
Other languages
English (en)
Chinese (zh)
Inventor
吕小强
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2020/090874 priority Critical patent/WO2021232197A1/fr
Priority to CN202080099658.6A priority patent/CN115380256A/zh
Publication of WO2021232197A1 publication Critical patent/WO2021232197A1/fr

Links

Images

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B15/00Systems controlled by a computer
    • G05B15/02Systems controlled by a computer electric

Definitions

  • the Internet of Things technology has been rapidly applied, and more and more devices can be connected to the network to monitor and control the devices.
  • the Internet of Things there are more and more types of Internet of Things devices, and how to realize a unified remote control of the Internet of Things devices in the network is the key.
  • an embodiment of the present application provides a device status monitoring method, including:
  • a notification message is received from the cloud server, where the notification message includes: equipment belonging to the target user and/or equipment status change information.
  • an embodiment of the present application provides a device status monitoring method, including:
  • the subscription request includes: an identifier of the user terminal and/or an identifier of a target user corresponding to the user terminal;
  • the sending module is configured to send a subscription request to a cloud server, where the subscription request is used to instruct the cloud server to report to the user terminal corresponding to the target user when the device and/or device status of the target user is changed. Feedback change information;
  • an embodiment of the present application provides a device status monitoring device, including: a receiving module, a processing module, and a sending module;
  • the processing module is configured to monitor the equipment and/or equipment status of the target user according to the subscription request;
  • an embodiment of the present application provides a user terminal, including:
  • Processor memory, transceiver, and interface for communication with cloud server;
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the method described in the first aspect above.
  • the foregoing processor may be a chip.
  • Processor memory, transceiver, and interface for communication with user terminal;
  • the memory stores computer execution instructions
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the method described in the second aspect above.
  • the foregoing processor may be a chip.
  • the embodiments of the present application may provide a computer-readable storage medium having computer-executable instructions stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the first aspect The method described.
  • an embodiment of the present application provides a program, which is used to execute the method described in the first aspect when the program is executed by a processor.
  • an embodiment of the present application provides a program, when the program is executed by a processor, it is used to execute the method described in the second aspect.
  • an embodiment of the present application provides a chip, which includes a processing module and a communication interface, and the processing module can execute the method described in the first aspect.
  • 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 causes the processing module to execute the second aspect The method described.
  • 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
  • the execution of the instructions stored in the storage module causes the processing module to execute the second aspect The method described.
  • the user terminal sends a subscription request to the cloud server, and the cloud server can monitor the device and/or device status of the target user according to the received subscription request, and When the device and/or device status of the user changes, notification information is sent to the user terminal corresponding to the target user, so that the user terminal can timely and accurately obtain the device and/or device status change information that needs to be controlled, and improve The accuracy of the acquired status information of the Internet of Things device is improved, thereby improving the accuracy of device control.
  • FIG. 1 is a schematic structural diagram of a device monitoring system to which the device state monitoring method provided in an embodiment of the application is applicable;
  • FIG. 3 is an interaction schematic diagram of Embodiment 1 of the device status monitoring method provided by this application.
  • Embodiment 4 is a schematic diagram of interaction of Embodiment 2 of the device status monitoring method provided by this application;
  • FIG. 5 is a schematic diagram of interaction of Embodiment 3 of the device status monitoring method provided by this application.
  • FIG. 6 is a schematic diagram of interaction of Embodiment 4 of the device status monitoring method provided by this application.
  • FIG. 7 is a schematic diagram of interaction of Embodiment 5 of the device state monitoring method provided by this application.
  • FIG. 8 is an interactive schematic diagram of Embodiment 6 of the device status monitoring method provided by this application.
  • FIG. 9 is a schematic diagram of interaction of Embodiment 7 of the device state monitoring method provided by this application.
  • FIG. 10 is a schematic structural diagram of Embodiment 1 of a device state monitoring apparatus provided by this application.
  • FIG. 12 is a block diagram of a user terminal for implementing a method for monitoring device status provided by this application.
  • FIG. 1 is a schematic structural diagram of a device monitoring system to which the device state monitoring method provided in an embodiment of the application is applicable.
  • the system may include: a user terminal 11, a cloud platform 12 and at least one Internet of Things device 13.
  • the user terminal 11 and at least one Internet of Things device 13 can both be registered on the cloud platform 12, and the cloud platform is deployed with a cloud server 120. Therefore, the user terminal 11 and the cloud server 120, the cloud server 120, and the at least one Internet of Things device 13 Both can communicate with each other, and the cloud server 120 can uniformly manage all devices connected to the network.
  • the aforementioned at least one IoT device 13 belongs to a user corresponding to the user terminal 11, if the user terminal 11 and the aforementioned at least one IoT device 13 are in the same local area network, the user terminal 11 and the aforementioned at least one IoT device 13 are in the same local area network.
  • the devices 13 can also communicate with each other, and if the user terminal 11 and the aforementioned at least one IoT device 13 are in different local area networks, at this time, the user terminal 11 can communicate with the aforementioned at least one IoT device through the cloud server 120 on the cloud platform 12.
  • the device 13 communicates.
  • the user terminal 11 may be a terminal device such as a smart phone or a tablet computer.
  • the Internet of Things devices can be smart TVs, smart refrigerators, smart washing machines, smart air conditioners and other devices.
  • the embodiment of the present application does not limit the specific expression form of the user terminal 11 and the Internet of Things device, which can be determined according to actual conditions.
  • At least one application is installed on the user terminal 11, including an application for managing Internet of Things devices, and the application installed by the user through the user terminal 11 can realize communication with the cloud server 120 and the Internet of Things devices.
  • APP application for managing Internet of Things devices
  • 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 will be maintained in the /session resource;
  • the cloud server sets the login status corresponding to the device ID to true.
  • the cloud server corresponds to the device ID
  • the login status is set to false (false).
  • the embodiments of the present application provide a device status monitoring method, which sends a subscription request to a cloud server through a user terminal.
  • the cloud server can monitor the device and/or device status of the target user according to the received subscription request, and When the device and/or device status belonging to the user changes, notification information is sent to the user terminal corresponding to the target user, so that the user terminal can obtain the device and/or device status change information that needs to be controlled in time, which improves the access The accuracy of the status information of the Internet of Things devices, thereby improving the accuracy of device control.
  • the overall idea of the technical solution of this 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 use a specific uniform resource identifier (URI) ) Send a subscription request to the cloud server to complete the subscription to the information of the Internet of Things devices and the cloud server.
  • URI uniform resource identifier
  • news subscription (or push) technology can not only be applied to the information transmission between the device and cloud platform communication (device to cloud, D2C), but also can be applied to the terminal device.
  • Application service processing and information transmission between devices (device to device, D2D).
  • the mobile phone subscribes to the temperature of the 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.
  • S201 The client sends a subscription request to the server.
  • the type of the subscription request is Retrieve, and Observe is used to indicate that the subscription request is a subscription message.
  • the subscription request may include the following parameters:
  • message receiver used to receive the resource identifier subscribed by the client
  • Ri Request identifier, used to complete the binding of request and response
  • Operation type generally one of CURD, the CURD is a rest operation type, CURD corresponds to create Create, Update Update, retrieve retrieve, Delete Delete;
  • the server authenticates the received subscription request, and establishes a monitoring mechanism after authentication
  • S204 The server monitors that the resource information corresponding to the subscription request changes, and determines the resource change information
  • S205 The server sends the resource change information to the client.
  • the subscription request in S201 the subscription response in S203, and the resource change information in S205 carry the same Ri.
  • FIG. 3 is a schematic diagram of interaction of Embodiment 1 of the device status monitoring method provided by this application.
  • Fig. 3 explains the information interaction between the user terminal of the user and the cloud server.
  • the method may include the following steps:
  • the user terminal sends a subscription request to the cloud server.
  • the subscription request is used to instruct the cloud server to feed back the change information to the user terminal corresponding to the target user when the device and/or the device status of the target user is detected to be changed.
  • the subscription request includes: the identifier of the user terminal and/or the identifier of the target user corresponding to the user terminal. That is, the subscription request may include the identification of the user terminal, or the subscription request may include the identification of the target user corresponding to the user terminal, or the subscription request may include the identification of the user terminal and the identification of the target user corresponding to the user terminal.
  • the specific content included in the subscription request can be set according to the actual scenario, and will not be repeated here.
  • the uniform resource identifier (uniform resource identifier, URI) of the subscription request is used to indicate the subscription content corresponding to the subscription request.
  • 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 the embodiment of the present application, the user terminal may indicate the subscription content or subscription object and subscription content corresponding to the subscription request through the URI of 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 for Indicates the subscription object and subscription content corresponding to the subscription request, and 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.
  • the subscription object corresponding to the subscription request is any one of the following:
  • All devices belonging to the target user a collection of devices belonging to the target user, and one device belonging to the target user.
  • the subscription content corresponding to the subscription request may be any of the following:
  • Device registration information Device registration information, device deregistration information, device online information, device offline information, and device resource change information.
  • the user terminal can determine the content to be subscribed according to requirements, and send a subscription request to the cloud server, so that the cloud server can perform corresponding operations according to the received subscription request.
  • 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 for device registration information and/or device deregistration information corresponds to all the subscription requests under the target user. equipment.
  • the subscription of device online information, device offline information, and device resource change information can be for all devices and some devices under the target user corresponding to the user terminal. Therefore, the user terminal can be indicated by the URL of the subscription request based on the user's instruction
  • the corresponding subscription object and/or subscription content can be any of the following:
  • the subscription request is a subscription request for device registration information, and the URI of the subscription request is /devices/registration.
  • the subscription request means subscribing to the registration information reminder of all devices belonging to the target user;
  • the subscription request is a subscription request for device deregistration information, and the URI of the subscription request is /devices/deregistration.
  • the subscription request means subscribing to the deregistration information reminder of all devices belonging to the user;
  • the subscription request is a subscription request for the online information of the device
  • the subscription request means to subscribe to the online information reminder of all devices belonging to the target user;
  • the subscription request means subscribing to the online information reminder of a specific device belonging to the target user, and the identifier of the specific device is the deviceID;
  • the subscription request is a subscription request for device offline information
  • the subscription request means subscribing to the offline information reminder of all devices belonging to the target user;
  • the subscription request means subscribing to the offline information reminder of a specific device belonging to the target user, and the identifier of the specific device is the deviceID;
  • the subscription request is a subscription request for device resource information changes
  • 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 aimed at It is the change of the resource information of all devices belonging to the target user saved by the cloud platform.
  • the URI of the subscription request is /devices/ ⁇ deviceID ⁇ /propertychange.
  • the subscription request represents a subscription to the resource information change of a specific device under the target user. It is worth noting that in this example, if the cloud server wants to know the resource information change of a specific device in time, the cloud server needs to send a resource information change subscription request to the specific device, so that when the resource information of the specific device changes, the cloud server needs to send a resource information change subscription request. It can be pushed to the cloud server in time, and then pushed to the user terminal.
  • the specific manifestation 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.
  • S302 The cloud server monitors the equipment and/or equipment status of the target user according to the received subscription request.
  • the cloud server can receive the subscription request, and by analyzing the URI of the subscription request, determine the target user who sent the subscription request and the subscription request correspondence Subscription content or subscription content and subscription object. Therefore, the cloud server can monitor the device and/or device status of the target user according to the subscription content or subscription content and the subscription object corresponding to the subscription request.
  • monitoring devices belonging to a target user mainly refers to monitoring device registration and/or device deregistration information under the target user
  • monitoring device status belonging to the target user mainly refers to monitoring device online information and device offline information under the target user And at least one of device resource change information.
  • the cloud server generates notification information when determining that the device and/or device status of the target user has changed.
  • the notification message includes: equipment belonging to the target user and/or equipment status change information.
  • the cloud server when the cloud server receives the subscription request sent by the user device, it starts to monitor the device and/or device status of the target user in real time, and when it is determined that the device and/or device status of the target user occurs When a change is made, a notification message is generated.
  • determining that the device belonging to the target user has changed refers to detecting that a device is newly registered to the target user or a device is deregistered from the target user (also called de-registration); determining the device belonging to the target user State change refers to monitoring that the device under the target user changes from online to offline, or the device under the target user changes from offline to online, or the device resource information under the target user changes.
  • the cloud server sends a notification message to the user terminal.
  • the cloud server determines that the device belonging to the target user and/or the device status has changed, it sends the generated notification message to the user terminal, so that the target user can timely and accurately know the device information or device to be controlled. Device status information.
  • the cloud server when the cloud server receives the above subscription request and starts to monitor the device and/or device status of the target user, it will feed back the subscription response to the user terminal to instruct the cloud server The 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.
  • a user terminal sends a subscription request to a cloud server, and the cloud server can monitor the device and/or device status of the target user according to the received subscription request, and check the device and/or device status of the device belonging to the user. Or when the status of the device changes, notification information is sent to the user terminal corresponding to the target user, so that the user terminal can timely and accurately obtain the device that needs to be controlled and/or the change information of the device state, which improves the obtained IoT devices The accuracy of the status information, thereby improving the accuracy of equipment control.
  • the user terminal after the user terminal obtains the device and/or the change information of the device status information, it can remotely control the device to be controlled according to the status information of the device to be controlled.
  • FIG. 4 is an interaction schematic diagram of Embodiment 2 of the device status monitoring method provided by this application.
  • the user terminal wants to obtain the device information of the target user from the cloud platform, the user terminal needs to be registered 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 further include the following steps:
  • the device status monitoring system Internet of Things system
  • the user terminal needs to be registered on the cloud platform first; moreover, only after the device is registered on the cloud platform can the status of the device go online or offline will change.
  • the online and offline of the device is not necessarily related to the registration and deregistration of the device.
  • the cloud server may directly base on the received The subscription request obtains the identification of the target user, but if the subscription request includes the identification of the user terminal, but does not include the identification of the target user corresponding to the user terminal, then in S302 (the cloud server monitors the device belonging to the target user according to the received subscription request) And/or device status), the method may also include the following steps:
  • the cloud server determines the identity of the target user corresponding to the user terminal according to the identity of the user terminal.
  • the cloud server can first determine The identification of the user terminal that sent the subscription request is obtained, and then the identification of the target user is determined by combining the corresponding relationship between the identification of the user terminal and the identification of the target user stored in the cloud platform.
  • the corresponding relationship between the user terminal identifier stored in the cloud platform and the target user identifier is determined by the cloud server when the user terminal is registered to the cloud platform.
  • the user terminal before the user terminal sends a subscription request to the cloud server, it is determined that the user terminal corresponding to the target user has been registered in the cloud platform, which is the implementation of subsequent monitoring of the device and/or device status of the target user Prerequisite:
  • the subscription request includes the identity of the user terminal, but does not include the identity of the user terminal corresponding to the target user of the cloud server, according to the identity of the user terminal, the identity of the target user corresponding to the user terminal is determined, which can ensure that the cloud server timely determines the need for monitoring
  • the target users and the devices under the target users lay the foundation for the realization of this solution.
  • 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 changes information.
  • the cloud server monitors the device and/or the device status of the target user according to the received subscription request) according to the different subscription content corresponding to the subscription request will be described below.
  • the above S302 may be performed through the embodiment shown in FIG. 5 and the embodiment shown in FIG. 6 or the embodiment shown in FIG. 7 illustrate.
  • the above S302 can be described by the embodiment shown in FIG. 8. If the subscription content corresponding to the subscription request is device resource change information, the above S302 can be described by the embodiment shown in FIG. 9.
  • FIG. 5 is an interactive schematic diagram of Embodiment 3 of the device status monitoring method provided by this application.
  • the subscription content corresponding to the subscription request is device registration information or device deregistration information, as shown in FIG. 5, the above S302 can be implemented through the following steps:
  • S501 Monitor the account resources on the cloud platform according to the user terminal identification and/or the target user identification, and obtain the account resource monitoring result.
  • the cloud server since the registration and/or cancellation of the device is managed by the account resource (/account resource) inside the cloud platform, the cloud server first determines the target user of the subscription after receiving the subscription request from the user terminal , And then monitor the account resources on the cloud platform, that is, monitor the device information changes under the target user in the account resources, and obtain the account resource monitoring results corresponding to the target user.
  • S502 According to the account resource monitoring result, determine whether the device information belonging to the target user in the account resource has changed.
  • the cloud server determines whether the device information belonging to the target user has changed based on the obtained account resource monitoring result, that is, determines whether a new device has been added or deleted in the account resource, so as to determine whether it needs to be reported to the user.
  • the terminal pushes device change information.
  • the cloud server determines that the device information belonging to the target user in the account resource has changed, for example, the resource of a new device is added to the account resource or the resource of one or some devices is deleted from the account resource. , A notification message is generated, and then the notification message is used to indicate the device change information belonging to the target user.
  • the cloud server monitors the account resources on the cloud platform according to the user terminal identification and/or the target user identification, obtains the account resource monitoring result, and then determines the account resources belonging to the target user Whether the device information is changed, and finally, when the device information belonging to the target user in the account resource is changed, a notification message is generated, and the notification message is used to indicate the change information of the device belonging to the target user.
  • the cloud server can determine and generate notification messages in time when the device information belonging to the target user changes by monitoring account resources, which lays the foundation for the timely push of subsequent messages.
  • FIG. 6 is a schematic interaction diagram of Embodiment 4 of the device status monitoring method provided by this application.
  • the foregoing S503 can be specifically implemented through the following steps:
  • S601 When a first device belonging to the target user is added to the 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.
  • the cloud server monitors (perceives) that the first device belonging to the target user is added to the account resources, it means that the target user downloads A new device is registered on the cloud platform, so a notification message is generated.
  • 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.
  • the first device in this embodiment does not indicate a sequence. It is only used to indicate a device that is newly registered on the cloud platform and belongs to the target user.
  • the embodiment of this 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.
  • the method further includes:
  • the cloud server receives the registration request sent by the first device.
  • the registration request includes: the identity of the first device, the identity of the target user to which the first device belongs, and access token information.
  • the user can control the first device to send a registration request to the cloud server, that is, the first device actively sends a registration request to the cloud platform.
  • the cloud server sends a modification request to modify the /account resource in the cloud platform, and the cloud server can receive the registration request accordingly.
  • the registration request sent by the first device needs to carry the identification of the first device, the identification of the target user to which the first device belongs, and access token information ( AccessToken).
  • the access token information is used to verify the first device and is used as a necessary parameter for whether the modification can be executed. Only the registration request sent by the first device carries the access token information and the identity of the first device When the verification is passed, the cloud server will respond to it.
  • the cloud server when the cloud server determines that the registration request of the first device is legal based on the access token information, it can add the ID of the target user, the ID of the first device, and the access command to the /account resource.
  • Information such as card information, so that the correspondence between the identification of the first device and the identification of the target user to which the first device belongs is added to the account resources. Therefore, the cloud server can accurately and timely determine the registration of the new device by monitoring the account resources.
  • the cloud server When the cloud server determines that the first device is successfully registered to 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.
  • the first device after the first device determines that its function is registered to the cloud platform, it can publish its discovered resources to the cloud platform at a selected time, and the published resources can be /D resources such as device attribute resources of the first device.
  • the cloud server may also feed back a publishing completion notification to the first device.
  • the cloud server when the first device is successfully registered to the cloud platform, the cloud server can determine that the first device belonging to the target user is newly added to the account resource by monitoring the account resource, and generates a notification message to Indicate that the first device belonging to the target user is successfully registered on the cloud platform.
  • the cloud server when the cloud server detects changes in the device registration information of the target user, it can promptly feed back 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 .
  • FIG. 7 is an interaction schematic diagram of Embodiment 5 of the device status monitoring method provided by this application.
  • the foregoing S503 can be specifically implemented through the following steps:
  • the cloud server monitors (perceives) that the second device belonging to the target user is deleted from the account resources, it indicates that the target user’s second device is Second, the device has been logged off from the cloud platform, so a notification message is generated.
  • the specific meaning of the notification message is to indicate that the second device belonging to the target user has been logged off from the cloud platform.
  • the second device in this embodiment does not indicate a sequence, it is only used to indicate a device that belongs to the target user and is logged off from the cloud platform.
  • the embodiment of this application does not limit the specificity of the second device. Realization, which can be determined according to the scenario, and will not be repeated here.
  • the method further includes:
  • 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.
  • the user can control the second device to send a logout request to the cloud server to request the second device
  • the related resource information of is deleted from the cloud platform, and correspondingly, the cloud server can receive the logout request.
  • the log-out request sent by the second device carries the identification of the second device and the identification of the target user to which it belongs, so that the cloud server can perform the log-out request according to the identification and the identification of the second device in the log-out request.
  • the identification of the target user responds to the logout request.
  • the cloud server when the device is registered to the cloud platform, the cloud server adds the corresponding relationship between the identity of the registered device and the identity of the target user to which it belongs to the account resource. Therefore, when the second device needs to log off from the cloud platform, The corresponding relationship between the identification of the second device and the identification of the target user can be deleted from the account resources of the cloud platform, and thus the account resources on the cloud platform will also change. Therefore, the cloud server can accurately and timely sense the logout of the device by monitoring the account resources.
  • the cloud server When the cloud server determines that the second device has been logged off from the cloud platform, it can feed back a response message such as a logoff completion response to the second device to notify the second device of the logoff result.
  • the cloud server when the second device is logged off from the cloud platform, the cloud server can determine that the second device belonging to the target user is deleted from the account resource by monitoring the account resource, and generates a notification message to indicate that it belongs to The second device of the target user has been logged off from the cloud platform.
  • the cloud server when the cloud server detects the change of the device logout information of the target user, it can feed back the device logout information to the user terminal in time, so that the target user can obtain accurate device information, and also improves the subsequent device control accuracy.
  • FIG. 8 is an interactive schematic diagram of Embodiment 6 of the device state monitoring method provided by this application.
  • the subscription content corresponding to the subscription request is device online information or device offline information, as shown in FIG. 8, the above S302 can be implemented through the following steps:
  • S801 According to the identification of the user terminal and/or the identification of the target user, monitor the session resource used to maintain the device connection attribute information on the cloud platform to obtain the session resource monitoring result.
  • the session resource since the connection attribute information (for example, online and offline) of the device is managed by the session resource (/session resource) inside the cloud platform, the session resource maintains a relationship table between the device ID and the login status, and therefore After the cloud server receives the subscription request from the user terminal, it first determines the target user to subscribe, and then monitors the session resource on the cloud platform, that is, monitors the change in the login status of the device under the target user in the session resource to obtain the target The user's corresponding session resource monitoring result.
  • the cloud server receives the subscription request from the user terminal, it first determines the target user to subscribe, and then monitors the session resource on the cloud platform, that is, monitors the change in the login status of the device under the target user in the session resource to obtain the target The user's corresponding session resource monitoring result.
  • S802 Determine whether the device connection information belonging to the target user has changed according to the session resource monitoring result.
  • the cloud server determines whether the device connection information belonging to the target user has changed based on the obtained session resource monitoring result, that is, determines whether all devices belonging to the target user have changed from offline to online or from online Change to an offline device to determine whether it is necessary to push device status change information to the user terminal.
  • the cloud server when the cloud server determines that there is a device that changes from offline to online or from online to offline among all the devices belonging to the target user, it generates a notification message to indicate that the target user belongs to the target user by using the notification message The device status change information of.
  • S803 when the subscription content corresponding to the subscription request is device online information, S803 can be implemented through the following steps:
  • S803a2 Generate a notification message according to the identifiers of all devices whose values of the login attribute information have changed, where the notification message is used to instruct the device to change from an offline state to an online state with respect to the cloud server.
  • the value of the login attribute information of the device changes from false to true, that is It is considered that the device changes from an offline state to an online state with respect to the cloud server, and then generates a notification message and sends it to the user terminal to notify the user terminal of the online information of the device under the target user.
  • S803 when the subscription content corresponding to the subscription request is device offline information, S803 can be implemented through the following steps:
  • S803b2 Generate a notification message according to the identifiers of all devices whose values of the login attribute information have changed, where the notification message is used to indicate that the device changes from an online state to an offline state with respect to the cloud server.
  • the value of the login attribute information of the device changes from true to false, That is, it is considered that the device changes from an online state to an offline state with respect to the cloud server, and then generates a notification message and sends it to the user terminal to notify the user terminal of the offline information of the device under the target user.
  • the device status monitoring method monitors the session resources used to maintain device connection attribute information on the cloud platform according to the user terminal identification and/or the target user identification, obtains the session resource monitoring result, and monitors the session resource according to the session resource As a result, it is determined whether the device connection information belonging to the target user changes, and when the device connection information belonging to the target user changes, a notification message is generated to indicate the device status change information belonging to the target user.
  • the cloud server can determine and generate notification messages in time when the device status information belonging to the target user changes by monitoring the session resources, which lays the foundation for the timely push of subsequent messages.
  • FIG. 9 is an interactive schematic diagram of Embodiment 7 of the device status monitoring method provided by this application.
  • the subscription content corresponding to the subscription request is device resource change information, as shown in FIG. 9, the above S302 can be implemented through the following steps:
  • S901 Determine the resource release information of all devices under the target user on the cloud platform according to the identity of the user terminal and/or the identity of the target user.
  • the device since the device can publish resources on the cloud platform after being registered to the cloud platform, or not publish resources on the cloud platform, when the cloud server receives a subscription request for device resource change information, first Determine which devices of the target user have released resources on the cloud platform and which devices have not released resources on the cloud platform, and then perform different resource change monitoring processes for devices with different judgment results.
  • S902 For a device that has released resources on the cloud platform under the target user, monitor the released resources of the device.
  • the devices under the target user have already published resources on the cloud platform, they have subscribed to the resource changes of the published resources of these devices on the cloud platform.
  • they have subscribed to the resource changes of the published resources of these devices on the cloud platform.
  • by monitoring the published resources of these devices To determine whether there is a resource change.
  • the devices under the target user do not publish resources on the cloud platform, they subscribe to the subscription resources of these devices, that is, send subscription requests to these devices through the cloud server to subscribe to resource changes of these devices. And monitor whether these devices feed back resource change information.
  • S903 may be implemented through the following steps:
  • A1 Send a resource change subscription request to the device, where the resource change subscription request is used to request to feed back resource change information to the cloud server when the device's subscribeable resources change.
  • A2 Obtain the resource change information of the subscribeable resource of the device by receiving the resource change information sent by the device.
  • the cloud server wants to know in time the resource changes of the device under the target user that does not publish resources on the cloud platform, it can send a resource change subscription request to the device, so that when the device's subscribeable resources send changes,
  • the device can send resource change information to the cloud server, so that the cloud server can obtain the resource change information of the subscribed resources of the device according to the received resource change information, so as to realize timely detection of resource changes of the device.
  • S904 When a resource change occurs in the published resource and/or a subscribeable resource of at least one device changes, determine the device identifier that has the resource change, and the resource change information corresponding to the device identifier.
  • the cloud server determines that the published resource has changed by monitoring the published resource on the cloud platform, it determines the device identifier corresponding to the published resource and its corresponding resource Change information. If the cloud server subscribes to the device's subscribeable resource change information reminder, it can also determine the resource change information of the device's subscribeable resource by receiving the resource change information fed back by the device, and then determine the device identifier corresponding to the subscribed resource And its corresponding resource change information.
  • S905 Generate a notification message according to the device identifier of the resource change and the resource change information corresponding to the device identifier.
  • the cloud server when the cloud server determines the resource change information corresponding to the device identifier and the device identifier through the above S902 to S904, it can compare the resource change device identifier and the resource change information corresponding to the device identifier.
  • the change information is contained in a message to get a notification message.
  • the subscription of the device resource change information can be for all devices under the target user, or can be for a specific device under the target user.
  • the implementation schemes of the two are similar. I won't repeat it here.
  • the device status monitoring method determines the resource release information of all devices under the target user on the cloud platform according to the user terminal identification and/or the target user identification, and the target user has been released on the cloud platform
  • the resource device monitors the published resources of the device. For devices that do not publish resources on the cloud platform under the target user, the subscribed resources of the device are monitored, and then resource changes and/or availability of at least one device occur in the published resources.
  • the subscription resource changes determine the device identification of the resource change and the resource change information corresponding to the device identification, and then generate a notification message.
  • the user terminal subscribes to the device resource change information, so that the cloud server can feed back to the user terminal when it monitors that the resource information of the device changes, so that the user terminal can learn the resource changes of each device in time. It has laid the foundation for improving the accuracy of equipment control.
  • FIG. 10 is a schematic structural diagram of Embodiment 1 of a device state monitoring apparatus provided by this application.
  • the device can be integrated in the user terminal, and can also be implemented through the user terminal.
  • the device may include: a sending module 1001 and a receiving module 1002.
  • the sending module 1001 is configured to send a subscription request to the cloud server, and the subscription request is used to instruct the cloud server to report to the target user when it detects that the device belonging to the target user and/or the device status changes.
  • the user terminal feedbacks the change information;
  • the receiving module 1002 is configured to receive a notification message from the cloud server, where the notification message includes: equipment belonging to the target user and/or equipment status change information.
  • the subscription content corresponding to the subscription request is any one of the following:
  • Device registration information Device registration information, device deregistration information, device online information, device offline information, and device resource change information.
  • the uniform resource identifier of the subscription request is used to indicate the subscription content corresponding to the subscription request.
  • the uniform resource identifier 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 any one of the following:
  • All devices belonging to the target user a set of devices belonging to the target user, and one device belonging to the target user.
  • the device further includes: a processing module 1003.
  • the processing module 1003 is configured to determine that 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.
  • the device provided in this embodiment is used to implement the technical solutions of the user terminal in the embodiments shown in FIG. 3 to FIG.
  • FIG. 11 is a schematic structural diagram of Embodiment 2 of the device status monitoring apparatus provided by this application.
  • the device can be integrated in a cloud server, and can also be implemented through a cloud server.
  • the device may include: a receiving module 1101, a processing module 1102, and a sending module 1103.
  • the receiving module 1101 is configured to receive a subscription request sent by a user terminal, where the subscription request includes: the identifier of the user terminal and/or the identifier of the target user corresponding to the user terminal;
  • the processing module 1102 is configured to monitor the device and/or device status of the target user according to the subscription request;
  • the sending module 1103 is configured to send a notification message to the user terminal when the device and/or device status of the target user changes, the notification message includes: the device and/or device status of the target user Change information.
  • the subscription content corresponding to the subscription request is any one of the following:
  • Device registration information Device registration information, device deregistration information, device online information, device offline information, and device resource change information.
  • the uniform resource identifier of the subscription request is used to indicate the subscription content corresponding to the subscription request.
  • the uniform resource identifier 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 any one of the following:
  • All devices belonging to the target user a set of devices belonging to the target user, and one device belonging to the target user.
  • the processing module 1102 is further configured to Identification, which determines the identification of the target user corresponding to the user terminal.
  • the subscription content corresponding to the subscription request is device registration information or device deregistration information
  • processing module 1102 is specifically used for:
  • the account resource monitoring result determine whether the device information belonging to the target user in the account resource has changed
  • the notification message is generated, and the notification message is used to indicate the change information of the device belonging to the target user.
  • the processing module 1102 is configured to generate the notification message when the device information belonging to the target user in the account resource changes, Specifically:
  • the processing module 1102 is specifically configured to generate the notification message when a first device belonging to the target user is added to the account resource, where the notification message is used to indicate the first device belonging to the target user Successfully registered on the cloud platform.
  • the receiving module 1101 is further configured to receive all the resources before the processing module 1102 monitors the account resources on the cloud platform according to the identification of the user terminal and/or the identification of the target user, and obtains the monitoring result.
  • the registration request sent by the first device where the registration request includes: the identity of the first device, the identity of the target user to which the first device belongs, and access token information;
  • the processing module 1102 is further configured to add a correspondence between the identity of the first device and the identity of the target user to which the first device belongs to the account resource according to the access token information;
  • the sending module 1103 is further configured to feed back a registration completion response to the first device.
  • the processing module 1102 is configured to generate the notification message when the device information belonging to the target user in the account resource changes , specifically:
  • the processing module 1102 is specifically configured to generate the notification message when the second device belonging to the target user is deleted from the account resource, where the notification message is used to indicate that the second device belonging to the target user has Log off from the cloud platform.
  • the receiving module 1101 is further configured to receive all the resources before the processing module 1102 monitors the account resources on the cloud platform according to the identification of the user terminal and/or the identification of the target user, and obtains the monitoring result.
  • the 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;
  • 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 resource of the cloud platform according to the logout request;
  • the sending module 1103 is further configured to feed back a logout completion response to the second device.
  • the subscription content corresponding to the subscription request is device online information or device offline information
  • processing module 1102 is specifically used for:
  • the notification message is generated, and the notification message is used to indicate the status change information of the device belonging to the target user.
  • the processing module 1102 is configured to generate the notification message when the device connection information belonging to the target user changes, specifically:
  • the processing module 1102 is specifically configured to determine the identities of all devices whose values of login attribute information have changed when there are devices whose values of login attribute information are changed from false to true in the device connection information belonging to the target user , And generating the notification message according to the identifiers of all devices whose values of the login attribute information have changed, where the notification message is used to instruct the device to change from an offline state to an online state with respect to the cloud server.
  • the processing module 1102 is configured to generate the notification message when the device connection information belonging to the target user changes, specifically :
  • the processing module 1102 is specifically configured to determine the identities of all devices whose values of login attribute information have changed when there are devices whose values of login attribute information change from true to false in the device connection information belonging to the target user, And generating the notification message according to the identifiers of all devices whose values of the login attribute information have changed, where the notification message is used to indicate that the device changes from an online state to an offline state with respect to the cloud server.
  • the subscription content corresponding to the subscription request is device resource change information
  • processing module 1102 is specifically used for:
  • the notification message is generated according to the device identification of the resource change and the resource change information corresponding to the device identification.
  • the processing module 1102 is configured to monitor the subscribed resources of the device for the device that does not publish resources on the cloud platform under the target user, specifically:
  • the processing module 1102 is configured 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 that resource change information is fed back to the cloud server when the subscribeable resource of the device changes, And by receiving the resource change information sent by the device through the receiving module 1101, the resource change information of the subscribeable resource of the device is obtained.
  • the device provided in this embodiment is used to implement the technical solutions of the cloud server in the embodiments shown in FIG. 3 to FIG.
  • the division of the various modules of the above device is only a division of logical functions, and may be fully or partially integrated into a physical entity during actual implementation, or may be physically separated.
  • these modules can all be implemented in the form of software called by processing elements; they can also be implemented in the form of hardware; some modules can be implemented in the form of calling software by processing elements, and some of the modules can be implemented in the form of hardware.
  • the processing module may be a separate processing element, or it may be integrated in a chip of the above-mentioned device for implementation.
  • each step of the above method or each of the above modules can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.
  • 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 (ASIC), or one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (FPGA), etc.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • FPGA field programmable gate arrays
  • the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call program codes.
  • CPU central processing unit
  • these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • 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 a website, computer, server, or data center.
  • 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 a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • Fig. 12 is a block diagram of a user terminal for implementing a method for monitoring device status provided by this application.
  • the user terminal may include: a processor 1201, a memory 1202, a transceiver 1203, and an interface 1204 for communicating with other devices.
  • the other devices may be cloud servers or IoT devices.
  • the memory 1202 stores computer execution instructions
  • 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 foregoing method embodiments.
  • FIG. 13 is a block diagram of a cloud server for implementing a method for monitoring device status provided by this application.
  • the cloud server may include: a processor 1301, a memory 1302, a transceiver 1303, and an interface 1304 for communicating with other devices.
  • the other device may be a user terminal or an Internet of Things device.
  • the memory 1302 stores computer execution instructions
  • the processor 1301 executes the computer-executable instructions stored in the memory 1302, so that the processor 1301 executes the technical solution on the cloud server side as in any of the foregoing method embodiments.
  • the present application also provides a computer-readable storage medium in which computer-executable instructions are stored.
  • the computer-executable instructions are executed by a processor, they are used to implement the user terminal side in any of the foregoing method embodiments.
  • the present application also provides a computer-readable storage medium in which computer-executable instructions are stored.
  • the computer-executable instructions are executed by a processor, they are used to implement the cloud server side in any of the foregoing method embodiments.
  • the embodiment of the present application also provides a program, when the program is executed by the processor, it is used to execute the technical solution on the user terminal side in the foregoing method embodiment.
  • the embodiment of the present application also provides a program, which is used to execute the technical solution on the cloud server side in the foregoing method embodiment when the program is executed by the processor.
  • the embodiments of the present application also provide a computer program product, including program instructions, which are used to implement the technical solutions on the user terminal side in the foregoing method embodiments.
  • the embodiments of the present application also provide a computer program product, including program instructions, and the program instructions are used to implement the technical solutions on the cloud server side in the foregoing method embodiments.
  • the embodiment of the present application also provides a chip, which includes a processing module and a communication interface, and the processing module can execute the technical solution of the user terminal in the foregoing method embodiment.
  • 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 causes the processing module to execute the user terminal side Technical solutions.
  • 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
  • the execution of the instructions stored in the storage module causes the processing module to execute the user terminal side Technical solutions.
  • the embodiment of the present application also provides a chip, which includes a processing module and a communication interface, and the processing module can execute the technical solution on the cloud server side in the foregoing method embodiment.
  • the chip further 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 causes the processing module to execute the cloud server side Technical solutions.
  • 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
  • the execution of the instructions stored in the storage module causes the processing module to execute the cloud server side Technical solutions.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship; in the formula, the character “/” indicates that the associated objects before and after are in a “division” relationship.
  • “The following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple indivual.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)

Abstract

Les modes de réalisation de la présente demande concernent un procédé et un appareil de surveillance d'état de dispositif, un dispositif, et un support de stockage. Le procédé comprend les étapes suivantes : un terminal utilisateur envoie une demande d'abonnement à un serveur en nuage; en fonction de la demande d'abonnement reçue, le serveur en nuage peut surveiller un dispositif appartenant à un utilisateur cible et/ou l'état du dispositif et, lorsque le dispositif appartenant à l'utilisateur et/ou l'état de dispositif change, envoie des informations de notification à un terminal d'utilisateur correspondant à l'utilisateur cible. Ainsi, le terminal d'utilisateur peut obtenir rapidement et avec précision des informations de changement du dispositif et/ou de l'état du dispositif qui doit être commandé, ce qui améliore la précision des informations d'état obtenues d'un dispositif de l'Internet des objets et améliore ainsi la précision de la commande du dispositif.
PCT/CN2020/090874 2020-05-18 2020-05-18 Procédé et appareil de surveillance d'état de dispositif, dispositif, et support de stockage WO2021232197A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/090874 WO2021232197A1 (fr) 2020-05-18 2020-05-18 Procédé et appareil de surveillance d'état de dispositif, dispositif, et support de stockage
CN202080099658.6A CN115380256A (zh) 2020-05-18 2020-05-18 设备状态监控方法、装置、设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/090874 WO2021232197A1 (fr) 2020-05-18 2020-05-18 Procédé et appareil de surveillance d'état de dispositif, dispositif, et support de stockage

Publications (1)

Publication Number Publication Date
WO2021232197A1 true WO2021232197A1 (fr) 2021-11-25

Family

ID=78708985

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/090874 WO2021232197A1 (fr) 2020-05-18 2020-05-18 Procédé et appareil de surveillance d'état de dispositif, dispositif, et support de stockage

Country Status (2)

Country Link
CN (1) CN115380256A (fr)
WO (1) WO2021232197A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114301962A (zh) * 2021-11-26 2022-04-08 杭州中恒电气股份有限公司 一种基于物联网云平台的充电桩通信方法和系统
CN114416389A (zh) * 2021-12-01 2022-04-29 荣耀终端有限公司 一种活动识别方法以及相关设备
CN114520827A (zh) * 2022-02-16 2022-05-20 广东美房智高机器人有限公司 一种消息接收方法、推送方法、系统及介质
CN114924806A (zh) * 2022-04-07 2022-08-19 南京慧尔视软件科技有限公司 一种配置信息的动态同步方法、装置、设备及介质
WO2023141834A1 (fr) * 2022-01-26 2023-08-03 Oppo广东移动通信有限公司 Procédé et appareil de surveillance de performance de modèle, dispositif et support
WO2024040390A1 (fr) * 2022-08-22 2024-02-29 Oppo广东移动通信有限公司 Procédé et appareil de déconnexion de dispositif

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014047385A2 (fr) * 2012-09-22 2014-03-27 Nest Labs, Inc. Mécanismes de notification d'abonnement pour la synchronisation d'états distribués
CN106169967A (zh) * 2016-07-14 2016-11-30 美的集团股份有限公司 一种用户客户端、家用电器及其控制方法
CN108600295A (zh) * 2018-02-28 2018-09-28 青岛海尔科技有限公司 一种实现设备状态信息通知的方法、设备及介质
CN110716439A (zh) * 2019-10-21 2020-01-21 合肥美的电冰箱有限公司 家电设备状态同步方法、家电设备及介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108712485B (zh) * 2018-05-10 2019-12-20 海信集团有限公司 一种物联网设备的资源订阅方法和装置
CN109525966B (zh) * 2018-09-07 2022-05-06 北京小米移动软件有限公司 智能设备的查询方法、装置和存储介质
CN110798471B (zh) * 2019-10-31 2022-01-25 宁波奥克斯电气股份有限公司 空调管理方法及相关装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014047385A2 (fr) * 2012-09-22 2014-03-27 Nest Labs, Inc. Mécanismes de notification d'abonnement pour la synchronisation d'états distribués
CN106169967A (zh) * 2016-07-14 2016-11-30 美的集团股份有限公司 一种用户客户端、家用电器及其控制方法
CN108600295A (zh) * 2018-02-28 2018-09-28 青岛海尔科技有限公司 一种实现设备状态信息通知的方法、设备及介质
CN110716439A (zh) * 2019-10-21 2020-01-21 合肥美的电冰箱有限公司 家电设备状态同步方法、家电设备及介质

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114301962A (zh) * 2021-11-26 2022-04-08 杭州中恒电气股份有限公司 一种基于物联网云平台的充电桩通信方法和系统
CN114416389A (zh) * 2021-12-01 2022-04-29 荣耀终端有限公司 一种活动识别方法以及相关设备
CN114416389B (zh) * 2021-12-01 2023-03-03 荣耀终端有限公司 一种活动识别方法以及相关设备
WO2023141834A1 (fr) * 2022-01-26 2023-08-03 Oppo广东移动通信有限公司 Procédé et appareil de surveillance de performance de modèle, dispositif et support
CN114520827A (zh) * 2022-02-16 2022-05-20 广东美房智高机器人有限公司 一种消息接收方法、推送方法、系统及介质
CN114520827B (zh) * 2022-02-16 2024-05-10 广东美房智高机器人有限公司 一种消息接收方法、推送方法、系统及介质
CN114924806A (zh) * 2022-04-07 2022-08-19 南京慧尔视软件科技有限公司 一种配置信息的动态同步方法、装置、设备及介质
CN114924806B (zh) * 2022-04-07 2024-03-26 南京慧尔视软件科技有限公司 一种配置信息的动态同步方法、装置、设备及介质
WO2024040390A1 (fr) * 2022-08-22 2024-02-29 Oppo广东移动通信有限公司 Procédé et appareil de déconnexion de dispositif

Also Published As

Publication number Publication date
CN115380256A (zh) 2022-11-22

Similar Documents

Publication Publication Date Title
WO2021232197A1 (fr) Procédé et appareil de surveillance d'état de dispositif, dispositif, et support de stockage
KR102116401B1 (ko) M2m 서비스 계층에 대한 교차 리소스 가입
US10313455B2 (en) Data streaming service for an internet-of-things platform
KR102046700B1 (ko) 메시지 버스 서비스 디렉토리
US10015684B2 (en) Method and apparatus for managing specific resource in wireless communication system
US11677850B2 (en) Method, apparatus and system for notification
US8942213B2 (en) Method and system for accessing storage devices
WO2020237548A1 (fr) Procédé, dispositif, et serveur d'abonnement à des ressources, et support d'enregistrement informatique
KR101705279B1 (ko) 단말 관리 서비스를 제공하는 서버 및 방법 그리고 상기 단말 관리 서비스를 제공받는 단말
KR102500594B1 (ko) 통신 네트워크에서의 서비스 계층 메시지 템플릿들
WO2016164899A1 (fr) Gestion d'enregistrement dans la couche de service
CN111130905A (zh) 基于分布式集群的日志级别动态调整方法
US20150149629A1 (en) User online state querying method and apparatus
US11930499B2 (en) Network monitoring in service enabler architecture layer (SEAL)
CN113196721B (zh) 物联网设备的发现方法、装置及终端设备
EP3622734B1 (fr) Activation de services m2m/iot fiables et distribués
EP3320650B1 (fr) Couche de service anycast et somecast
CN108833331B (zh) 一种资源对象创建、资源对象状态上报方法及装置
US10511682B2 (en) Group resource updating processing methods, devices and system, and CSEs
CN111182066A (zh) 基于token认证的日志级别动态调整方法
JP2019506785A (ja) リソース取得方法および装置
US10659938B2 (en) Registration method and communication method for application dedicated node (ADN), and nodes
CN112995095B (zh) 数据处理方法、装置及计算机可读存储介质
US20220124008A1 (en) Automated Service Layer Message Flow Management In A Communications Network
CN110855785B (zh) 一种数据处理的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20936666

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20936666

Country of ref document: EP

Kind code of ref document: A1