Time variant data profile for a fabric network

• US 9,967,228 B2
• Filed: 06/20/2016
• Issued: 05/08/2018
• Est. Priority Date: 10/08/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Logue, Jay D., Erickson, Grant M., Gujjaru, Sunny Vardhan, Dixon, Michael, Lu, Jiakang
• Primary Examiner(s): Maung, Zarni
• Application Number:
  US15/187,531
• Publication Number:
  US 20160306879A1
• Time in Patent Office: 687 Days
• 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

Systems and methods for exchanging a data stream of information that varies over time using a message format. The message format includes a version field that indicates a version of a structure of the message format. The message format also includes one or more resources fields that each identifies a resource to be imported into the data stream exchanging the data stream. Moreover, the message format includes one or more records that represent time-variant data samples being exchanged in the message. Furthermore, the message format includes one or more descriptor fields, wherein each descriptor field corresponds to at least one respective record of the one or more records and contains metadata describing data contained within the at least one record.

Claims

1. A non-transitory, tangible, and computer-readable medium comprising instructions for exchanging time-variant data, that is indicative of an environmental condition and generated by a sensor, using a message format, the instructions executable by one or more processors to configure an electronic device to:

encode the time-variant data, using the message format, the message format comprising;

one or more resources fields that each identifies a resource to be imported into the time-variant data;

one or more records that represent data samples comprising the time-variant data being exchanged in the message;

a descriptor field corresponding to at least one respective record of the one or more records and containing metadata describing the time-variant data contained within the at least one record; and

a description field having a human-readable string to describe from where the data samples are derived.

2. The non-transitory, tangible, and computer-readable medium of claim 1, wherein the time-variant data comprises periodic data.

3. The non-transitory, tangible, and computer-readable medium of claim 1, wherein the time-variant data comprises real-time data.

4. The non-transitory, tangible, and computer-readable medium of claim 3, wherein the real-time data comprises a current temperature, a current density, a current time of day, or a combination thereof.

5. The non-transitory, tangible, and computer-readable medium of claim 1, wherein the time-variant data comprises non-real-time data.

6. The non-transitory, tangible, and computer-readable medium of claim 5, wherein the non-real-time data comprises historical data.

7. The non-transitory, tangible, and computer-readable medium of claim 4, wherein the description field indicates a data stream and is configured to enable later analysis of an exchange of the data stream.

8. The non-transitory, tangible, and computer-readable medium of claim 1, wherein each of the one or more resource fields comprises a string comprising a Uniform Resource Identifier (URI) that maps to a resource to be imported into the message, wherein each URI is a string that identifies a location of the resource to be imported.

9. The non-transitory, tangible, and computer-readable medium of claim 8, wherein each of the one or more resource fields comprise a source indication that identifies a specific location within the resource from which imported time-variant data is to be derived, wherein the source indication comprises:

an explicit indication that explicitly states where the imported time-variant data is specifically located within the resource;

or

an implicit indication when an explicit indication is lacking, wherein the implicit indication indicates that the specific location of the imported time-variant data is in a root location of the resource.

10. The non-transitory, tangible, and computer-readable medium of claim 1, wherein the message format comprises a version field that indicates a version of a structure of the message format.

11. An electronic device comprising:

a sensor for generating time-variant data indicative of an environmental condition;

a processor; and

a memory comprising instructions for causing the processor to encode the time-variant data indicative of the environmental condition using a message format, the message format comprising;

one or more resources fields that each identifies a resource to be imported into the time-variant data;

one or more records that represent data samples comprising the time-variant data being exchanged in the message;

a descriptor field corresponding to at least one respective record of the one or more records and containing metadata describing the time-variant data contained within the at least one record; and

a description field having a human-readable string to describe from where the time-variant data samples are derived.

12. The electronic device of claim 11, wherein the descriptor field comprises a 16-bit unsigned fixed-point value identifier that matches a corresponding identifier in a corresponding record to indicate that the descriptor field describes time-variant data found in the record is described by the metadata in the descriptor field.

13. The electronic device of claim 11, wherein the resource indicated in a location external to the electronic device, the time-variant data in the external resource is formatted in tag-length-value (TLV) format, a profile tag for the descriptor field may be context-specific by using a top level profile tag to indicate the descriptor field refers to an exterior resource by tagging the descriptor field with a 0x02 value in an ExtDescriptors tag.

14. The electronic device of claim 11, wherein the descriptor field includes a stream periodicity indicator that indicates whether the time-variant data in a stream is periodic or aperiodic using a flag, wherein when the flag is positive, the flag indicates that the stream is periodic, and when the flag is negative, the flag indicates that the stream is aperiodic having irregular intervals of time between samples in the stream.

15. The electronic device of claim 11, wherein the descriptor field comprises a type element that is a caller-assigned 16-bit or 32-bit unsigned fixed-point value that represents a type of data present in the stream, wherein the type element applies to field elements found in the descriptor field unless explicitly overridden by another type element contained in a respective field element of the descriptor.

16. The electronic device of claim 15, wherein the type comprises length, mass, time, current, temperature, luminous intensity, area, volume, velocity, acceleration, density, magnetic field strength, luminance, molar concentration, number concentration, molality, frequency, force, pressure, energy, power, electric charge, capacitance, electrical resistance, magnetic flux, electrical resistance, radioactivity, depth, height, or humidity.

17. A method for conveying time-variant data, indicative of an environmental condition, by an electronic device in a fabric network, the method comprising:

encoding, by the electronic device, the time-variant data indicative of an environmental condition, that is generated by a sensor, using a message format that comprises;

one or more resources fields that each identifies a resource to be imported into the time-variant data;

one or more records that represent data samples comprising the time-variant data being exchanged in the message;

a descriptor field corresponding to at least one respective record of the one or more records and containing metadata describing time-variant data contained within the at least one record;

a description field having a human-readable string to describe from where the data samples are derived; and

transmitting, by the electronic device, over the fabric network, the encoded time-variant data using the message format.

18. The method of claim 17, wherein the description field indicates a data stream and is configured to enable later analysis of an exchange of the data stream.

19. The method of claim 17, wherein the descriptor element comprises a field element that describes the format of one or more data samples found in the message, wherein the field element comprises:

a valid element that is a Boolean flag used to indicate whether the field contains alignment padding or valid data;

a relative element that is a conditional Boolean flag that is used to indicate whether the samples are measured absolutely or relative to each other;

a signed element that indicates whether the data samples are signed or unsigned values;

one or more size elements that are each an 8-bit unsigned fixed-point value that indicates a size of corresponding data sample; and

a count element is an 8-bit unsigned fixed-point value that indicates a number of size elements for the field element.

20. The method of claim 19, wherein the field element comprises:

an exponent element that is an 8-bit value used to indicate an exponent of the time-variant data to preserve resolution while scaling the data samples; and

a units element that includes metadata describing units of measure represented by the data samples;

one or more overriding elements configured to override, for the field element, metadata referring to the one or more records, wherein the one or more overriding elements comprise a data type or a description for the data samples.