Data management profile for a fabric network

• US 9,410,712 B2
• Filed: 12/31/2014
• Issued: 08/09/2016
• Est. Priority Date: 10/08/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Smith, Zachary B., Erickson, Grant M., Logue, Jay D., Neeley, Matthew G.
• Primary Examiner(s): Ali, Mohammad
• Assistant Examiner(s): Karim, Ziaul
• Application Number:
  US14/588,086
• Publication Number:
  US 20160102878A1
• Time in Patent Office: 587 Days
• Field of Search: 700276-276
• US Class Current: 1/1
• CPC Class Codes: F24F 11/30 for purposes related to the operation of the system, e.g. for safety or monitoring
• CPC Class Codes: F24F 11/58 using Internet communication
• CPC Class Codes: F24F 11/62 characterised by the type of control or by internal processing, e.g. using fuzzy logic, adaptive control or estimation of values
• CPC Class Codes: F24F 11/63 Electronic processing
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 19/042 using digital processors G05B19/05 takes precedence
• CPC Class Codes: G05B 2219/2642 Domotique, domestic, home control, automation, smart house
• CPC Class Codes: G06F 16/33 Querying
• CPC Class Codes: G06F 16/38 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G08B 17/10 Actuation by presence of smoke or gases , e.g. automatic alarm devices for analysing flowing fluid materials by the use of optical means
• CPC Class Codes: G08B 25/001 Alarm cancelling procedures or alarm forwarding decisions, e.g. based on absence of alarm confirmation
• CPC Class Codes: G08B 29/02 Monitoring continuously signalling or alarm systems
• CPC Class Codes: H04L 12/2803 Home automation networks
• CPC Class Codes: H04L 12/2809 indicating that an appliance service is present in a home automation network monitoring functionality H04L43/0817; discovery or management thereof, e.g. service location protocol [SLP] or web services, H04L67/51
• CPC Class Codes: H04L 12/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 Class Codes: H04L 12/2818 from a device located outside both the home and the home network access arrangements H04L12/2856; for remote control or remote monitoring of applications H04L67/025; arrangements for transmitting signals characterised by the use of a wireless eletrical link G08C17/00; telephonic communication systems adapted for combination with remote control systems H04M11/007
• CPC Class Codes: H04L 12/2823 Reporting information sensed by appliance or service execution status of appliance services in a home automation network device-related reporting H04L43/065; arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom H04Q9/00
• CPC Class Codes: H04L 12/283 Processing of data at an internetworking point of a home automation network
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0816 : the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0886 : Fully automatic configuration
• CPC Class Codes: H04L 43/0805 : by checking availability
• CPC Class Codes: H04L 45/02 : Topology update or discovery
• CPC Class Codes: H04L 45/74 : Address processing for routing
• CPC Class Codes: H04L 61/4511 : using domain name system [DNS]
• CPC Class Codes: H04L 61/4541 : Directories for service discovery
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0823 : using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0876 : based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 65/1069 : Session establishment or de-establishment
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 : for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/04 : specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 : specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/143 : Termination or inactivation of sessions, e.g. event-controlled end of session
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/53 : using third party service providers
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/28 : Timers or timing mechanisms used in protocols
• CPC Class Codes: H04L 69/40 : for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04W 12/04 : Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/50 : Secure pairing of devices
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]

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.

Claims

1. A method for controlling data remotely comprising:

connecting to a remote device within a fabric of smart devices from a local smart device within the fabric of smart devices, wherein the remote device stores data locally, wherein the remote device comprises a smart device having at least one sensor; and

remotely controlling the data stored in the remote device from the local smart device connected to the fabric by transmitting a message to the remote device, wherein the transmitted message includes a profile identifier that causes a data management entity of the remote device to perform an indicated data management action, wherein the profile identifier identifies a data management profile, and the message includes a command tag that indicates the data management action to be performed, and wherein the data management action comprises;

a subscribe action configured to cause the remote device to store an indicator of the local smart device as a subscriber to the data, and the indicator of the local smart device as the subscriber is configured to cause the remote device to send the data to the local smart device;

wherein the subscribe action is configured to cause the remote device to send the data to the local smart device when;

the remote device determines that the data has changed from a state last sent to the local smart device; and

an interval for sending the data has expired;

a view action configured to send the data to be viewed that is stored locally on the remote device to the local smart device;

or

an update action configured to update the data stored locally to a value sent by the local smart device.

2. The method of claim 1, wherein the data comprises a state of the remote device, wherein the remote device comprises a radiator control valve and the state of the remote device comprises a heat state of a radiator controlled by the radiator control valve, and wherein the view action is configured to send the heat state of the radiator to the local smart device, and the update action is configured to update the heat state of the radiator.

3. The method of claim 1, wherein the data stored locally on the remote device comprises data stored using a second profile for the fabric network that is different than the data management profile identified in the profile identifier of the message, wherein the second profile comprises a core profile, a software update profile, and a heating-ventilating-and-air-conditioning (HVAC) profile.

4. A non-transitory, computer-readable medium having instructions stored thereon, wherein the instructions when executed are configured to cause a processor to:

connect to a remote device within a fabric of smart devices from a local smart device within the fabric of smart devices, wherein the remote device stores data locally, wherein the remote device comprises a smart device having at least one sensor; and

remotely control the data stored in the remote device from the local smart device connected to the fabric by transmitting a message to the remote device, wherein the transmitted message includes a profile identifier that causes a data management entity of the remote device to perform an indicated data management action, wherein the profile identifier identifies a data management profile, and the message includes a command tag that indicates the data management action to be performed, and wherein the data management action comprises;

a subscribe action configured to cause the remote device to store an indicator of the local smart device as a subscriber to the data, and the indicator of the local smart device as the subscriber is configured to cause the remote device to send the data to the local smart device;

wherein the subscribe action is configured to cause the remote device to send the data to the local smart device when;

the remote device determines that the data has changed from a state last sent to the local smart device; and

an interval for sending the data has expired;

a view action configured to send the data to be viewed that is stored locally on the remote device to the local smart device;

or

an update action configured to update the data stored locally to a value sent by the local smart device, and the data comprises a state of the remote device.

5. The non-transitory, computer-readable medium of claim 4, wherein the instructions when executed are configured to cause the processor to peer publish the data to a subscribing device in the fabric by binding the data to the local smart 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 remote device even when requests to modify the data do not include an encoded destination address for the local smart device when the local smart device is a subscribing device.

6. The non-transitory, computer-readably medium of claim 5, wherein the instructions are configured to cause the processor to:

receive the data based on the binding; and

publish the data to connected devices in the fabric that are connected to the local smart device, wherein the instructions are configured to cause the processor to determine that the data pertains to the connected devices.

7. The non-transitory, computer-readable medium of claim 4, wherein the instructions are configured to cause the local smart device to receive a filtered version of the data after the remote device has determined whether the local smart device has a current version of a portion of the data, wherein the received filtered version of the data comprises the data with the portion of the data omitted.

8. The non-transitory, computer-readable medium of claim 4, wherein the instructions when executed are configured to cause the processor to broadcast publish the bind the data to be multicast when a bind request includes a multicast value that indicates that the data is to be multicast instead of unicast to a specific device so that any requests to modify the data are bound to connected nodes so that devices in the fabric receive information about the data that is stored locally on the remote device as a multicast.

9. The non-transitory, computer-readable medium of claim 4, wherein the transmitted message comprises:

a path list profile identifier that identifies a profile within which the data is located;

a version for the data; and

the path list that locates a location of the data within the profile.

10. An electronic device comprising:

one or more network interfaces configured to connect the electronic device to a fabric of smart devices;

memory;

a processor configured to;

connect to a remote device within the fabric of smart devices from a local smart device within the fabric of smart devices, wherein the remote device stores data locally, wherein the remote device comprises a smart device having at least one sensor; and

remotely control the data stored in the remote device from the local smart device connected to the fabric by transmitting a message to the remote device, wherein the transmitted message includes a profile identifier that causes a data management entity of the remote device to perform an indicated data management action, wherein the profile identifier identifies a data management profile, and the message includes a command tag that indicates the data management action to be performed, and wherein the data management action comprises;

a subscribe action configured to cause the remote device to store an indicator of the local smart device as a subscriber to the data, and the indicator of the local smart device as the subscriber is configured to cause the remote device to send the data to the local smart device;

wherein the subscribe action is configured to cause the remote device to send the data to the local smart device when;

the remote device determines that the data has changed from a state last sent to the local smart device; and

an interval for sending the data has expired;

a view action configured to send the data to be viewed that is stored locally on the remote device to the local smart device;

or

an update action configured to update the data stored locally to a value sent by the local smart device.

11. The electronic device of claim 10, wherein the electronic device comprises a data management entity that communicates with the data management entity of the remote device through the fabric, wherein the data management entity of the electronic device comprises:

an upper sublayer data manager that manages and tracks data access; and

a lower sublayer protocol engine that manages communication formats.

12. The electronic device of claim 11, wherein the upper sublayer data manager is configured to:

maintain an internal model for the data;

provide access to data based on a set of predefined paths established by a profile definition;

track changes to the data; and

resolve conflicts that may arise between multiple updaters of the data set.

13. The electronic device of claim 11, wherein the lower sublayer protocol engine is configured to:

bind requests to a particular node or remote service endpoint;

maintain transactions for the data management entity to local smart data management entities of connected devices in the fabric;

encode communications a predefined format; and

interact with a fabric exchange manager to facilitate communication with the local smart data management entities of the connected devices.

14. The electronic device of claim 10, wherein the processor is configured to:

establish a connection to a indirect connection device, wherein the indirect connection device does not directly communicate to the remote device, wherein sending the transmitted message comprises receiving the transmitted message from the indirect connection device;

send received data designating the indirect connection device as a destination to the indirect connection device.

15. The electronic device of claim 14, wherein the indirect connection device comprises:

a non-fabric device that is not directly connected to the fabric;

or

a single connection device on the fabric that connects to the fabric or a local area network that corresponds to the fabric, wherein the single connection device connects only to the fabric or the local area network through the electronic device as a gateway to the fabric or the local area network.

16. The electronic device of claim 10 wherein the processor is configured to:

receive, through the one or more network interfaces, a received message with the profile identifier that causes a data management entity of the electronic device to perform a received indicated data management action for local data stored in the memory; and

performing the receiving indicated data management action on the local data.

17. The electronic device of claim 16, wherein the processor is configured to:

receive a first request to update the local data from a first device in the fabric;

update the local data as a first update using the first request;

during the first update, receive a second request to update the local data from a second device in the fabric;

update the local data as a second update after the first update has completed;

merging the local data with the first and second updates after the first and second updates have completed; and

sending the merged local data as an outgoing update to the first and second devices.

18. The electronic device of claim 10, wherein the locally stored data comprises sensor data from the at least one sensor.