Data management profile for a fabric network

Patent metadata

Field	Value
Publication number	US-10084745-B2
Application number	US-201615228939-A
Country	US
Kind code	B2
Filing date	Aug 4, 2016
Priority date	Oct 8, 2014
Publication date	Sep 25, 2018
Grant date	Sep 25, 2018

Abstract

Method and systems for controlling data remotely that includes connecting to a remote device within a fabric of smart devices. The remote device stores data locally. Controlling the data includes remotely controlling the data stored in the remote device from another device connected to the fabric by transmitting a message to the remote device. Moreover, the transmitted message includes a profile identifier that causes a data management entity of the remote device to perform an indicated data management action. Furthermore, the profile identifier identifies a data management profile, and the message includes a command tag that indicates the data management action to be performed.

First claim

The invention claimed is:

1. A method for controlling a remote device configured as a publisher device, the method comprising:
transmitting, by a subscriber device, a request to the publisher device within a fabric of smart devices, the publisher device including at least one sensor, the request causing the publisher device to establish a subscription to data related to a state or the at least one sensor of the publisher device;
encoding a data management action into a message for transmission to the publisher device, the encoded message including a profile identifier that causes a data management entity of the publisher device to perform the data management action, the profile identifier identifying a data management profile, and the encoded message including a command tag that encodes the data management action to be performed;
transmitting the encoded message to the publisher device, the transmitting the encoded message causing the publisher device to:
send the data related to the state or the at least one sensor of the publisher device to the subscriber device upon an event; or
send the data related to the state or the at least one sensor of the publisher device, that is stored locally on the publisher device, to the subscriber device;

receiving the data related to the state or the at least one sensor of the publisher device; and
based upon the receiving the data, performing, by the subscriber device, a control action based on the data related to the state or the at least one sensor of the publisher device.

2. The method of claim 1 , wherein the event comprises a determination that the data has changed from a state since a last sent data was sent to the subscriber device.

3. The method of claim 2 , wherein sending the data is suppressed if the last sent data was sent less than a threshold interval prior to the event.

4. The method of claim 1 , wherein the event comprises an update interval that has elapsed since a last sent data update was sent.

5. The method of claim 1 , wherein the encoded data management action comprises:
a subscribe action;
a view action; and
a update action.

6. The method of claim 1 , wherein the data comprises a state of the publisher device, wherein the publisher device comprises a radiator control valve and the state of the publisher device comprises a heat state of a radiator controlled by the radiator control valve, and wherein the data management action is related to the heat state of the radiator.

7. A non-transitory, computer-readable medium comprising instructions for a subscriber device, the instructions executable by a processor to configure the subscriber device to:
transmit a request to a publisher device within a fabric of smart devices, the publisher device including at least one sensor, the request being configured to cause the publisher device to establish a subscription to data related to a state or the at least one sensor of the publisher device;
encode a data management action into a message for transmission to the publisher device, the encoded message including a profile identifier that causes a data management entity of the publisher device to perform the data management action, the profile identifier identifying a data management profile, and the encoded message including a command tag that encodes the data management action to be performed;
transmit the encoded message to the publisher device, the transmission of the encoded message being effective to cause the publisher device to:
send the data related to the state or the at least one sensor of the publisher device to the subscriber device upon an event; or
send the data related to the state or the at least one sensor of the publisher device that is stored locally on the publisher device to the subscriber device;

receive the data related to the state or the at least one sensor of the publisher device; and
based upon the reception of the data, perform a control action based on the data related to the state or the at least one sensor of the publisher device.

8. The non-transitory, computer-readable medium of claim 7 , wherein the instructions are executable by the processor to configure the subscriber device to peer publish the data to a subscribing device in the fabric by binding the data to the subscriber device so that any requests to modify the data are sent to a node corresponding to a subscribing device such that the subscribing device receives information about the data that is stored locally on the publisher device even when requests to modify the data do not include an encoded destination address for the subscriber device when the subscriber device is a subscribing device.

9. The non-transitory, computer-readable medium of claim 8 , wherein the instructions are executable to cause the subscriber device to:
receive the data based on the binding; and
publish the data to connected devices in the fabric that are connected to the subscriber device, wherein the instructions are executable to cause the subscriber device to determine that the data pertains to the connected devices.

10. The non-transitory, computer-readable medium of claim 7 , wherein the instructions are executable to cause the subscriber device to receive the data based on filtering.

11. The non-transitory, computer-readable medium of claim 10 , wherein the filtering comprises filtering potential events to determine the event based on a threshold number of times that updates have been sent to the publisher device.

12. The non-transitory, computer-readable medium of claim 10 , wherein event comprises a change of the data.

13. The non-transitory, computer-readable medium of claim 10 , wherein the filtering comprises filtering potential events to determine the event based on whether a degree of the change of data surpasses a threshold amount of change.

14. The non-transitory, computer-readable medium of claim 10 , wherein filtering comprises the publisher device determining whether the subscriber device has a current version of the data.

15. The non-transitory, computer-readable medium of claim 7 , wherein the transmitted message includes:
a pathlist profile identifier that identifies a profile within which the data is located;
a version for the data; and
a pathlist that locates a location of the data within the profile.

16. An electronic device comprising:
one or more network interfaces configured to connect the electronic device to a fabric of smart devices;
a processor;
memory comprising instructions executable by the processor to configure the electronic device to:
transmit a request to a publisher device within a fabric of smart devices from the electronic device as a subscriber device, the publisher device including at least one sensor, the request being configured to cause the publisher device to establish a subscription to data related to a state or the at least one sensor of the publisher device;
encode a data management action into a message for transmission to the publisher device, the encoded message including a profile identifier that causes a data management entity of the publisher device to perform the data management action, the profile identifier identifying a data management profile, and the encoded message including a command tag that encodes the data management action to be performed;
transmit the encoded message to the publisher device, the transmission of the encoded message being effective to cause the publisher device to:
send the data related to the state or the at least one sensor of the publisher device to the electronic device upon an event; or
send the data related to the

Assignees

• Google Inc
• Google Llc

Inventors

• Smith Zachary B
• Erickson Grant M
• Logue Jay D
• Neeley Matthew G

Classifications

• H04L45/74

  Address processing for routing · CPC title

• H04L12/281

  indicating a format for calling an appliance service function in a home automation network (for remote control or remote monitoring of applications H04L67/025) · CPC title

• G06F16/38

  Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually · CPC title

• F24F11/62

  characterised by the type of control or by internal processing, e.g. using fuzzy logic, adaptive control or estimation of values · CPC title

• H04L67/141

  Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title