Methods and apparatus for using smart environment devices via application program interfaces

Patent metadata

Field	Value
Publication number	US-9854386-B2
Application number	US-201514722012-A
Country	US
Kind code	B2
Filing date	May 26, 2015
Priority date	Jun 23, 2014
Publication date	Dec 26, 2017
Grant date	Dec 26, 2017

Abstract

Systems and Methods disclosed herein relate to provisioning vendor information to associate vendor data access rights, vendor data writing rights, or both, of a data model comprising information related to one or more smart-devices, one or more smart-device environment structures comprising the one or more smart-devices, or any combination thereof with the vendor; provisioning a particular electronic device type of the vendor by providing information about the particular electronic device type to a service that interprets this information to understand subsequent data submissions of the particular electronic device, wherein the provisioning of the particular electronic device is associated with the vendor; pairing the particular electronic device with a system hosting the data model by registering the particular electronic device with the system hosting the data model; and sending the subsequent data submissions from the one or more smart-devices to the service.

First claim

The invention claimed is:

1. A processor-implemented method, comprising:
provisioning vendor information to associate rights to access and write vendor data of a data model comprising information related to one or more smart-devices, one or more smart-device environment structures comprising the one or more smart-devices, or any combination thereof with a vendor;
provisioning a particular electronic device type of the vendor, for a particular electronic device, by providing compatibility information about the particular electronic device type to a service that interprets the compatibility information to understand subsequent data submissions of the particular electronic device, the provisioning of the particular electronic device type being associated with the vendor by associating the particular electronic device type with the provisioned vendor information;
provisioning the particular electronic device, comprising:
accessing one or more build-time profiles for the particular electronic device that provide a description of capabilities of the particular electronic device, metadata related to data provided by the particular electronic device, or both; and
using the one or more build-time profiles to understand the subsequent data submissions of the particular electronic device, by importing the one or more build-time profiles to the service and generating one or more device type manifests that are used to describe, translate, validate, or any combination thereof, the subsequent data submissions and any other data submissions by other devices having a device type in common with the particular electronic device;

pairing the particular electronic device with a system hosting the data model by registering the particular electronic device with the system hosting the data model by associating the particular electronic device with the provisioned particular electronic device type; and
sending the subsequent data submissions from the one or more smart-devices to the service after the particular electronic device is registered with the system hosting the data model.

2. The processor-implemented method of claim 1 , wherein provisioning the vendor comprises:
sending, receiving, or both a request from a vendor cloud or a vendor device to interact with the system hosting the data model;
sending, receiving, or both an identification of the vendor; and
upon approval of the request, generating an entry for the vendor in a vendor entity of a service tracking the vendor data access rights, vendor data writing rights, or both.

3. The processor-implemented method of claim 2 , comprising:
associating an application-layer protocol vendor identifier with the vendor by populating an application-layer protocol vendor identifier field in the entry of the vendor entity;
associating a vendor path with the vendor by populating a path field in the entry of the vendor entity;
associating a name with the vendor by populating a name field in the entry of the vendor entity; or
any combination thereof.

4. The processor-implemented method of claim 1 , comprising:
generating an entry for the device type of the particular electronic device in a device type entity.

5. The processor-implemented method of claim 4 , wherein provisioning the particular electronic device comprises:
associating the one or more device type manifests with the device type by populating a manifest field in the entry of the device type entity.

6. The processor-implemented method of claim 4 , wherein provisioning the particular electronic device comprises:
associating a path of the device type with the device type by populating a path field in the entry of the device type entity.

7. The processor-implemented method of claim 4 , wherein provisioning the particular electronic device comprises:
if the device type is compatible with an application-layer protocol, associating application-layer protocol compatibility information of the device type with the device type by populating an application-layer protocol profile identifier in the entry of the device type entity.

8. The processor-implemented method of claim 1 , wherein pairing the particular electronic device comprises:
generating an entry for the particular electronic device in a device entity of the system hosting the data model;
receiving a location of the particular electronic device, a unique identifier of the particular electronic device, or both; and
associating the location, the unique identifier, or both with the particular electronic device in the system hosting the data model by populating one or more fields in the entry of the device entity.

9. The processor-implemented method of claim 8 , if the particular electronic device is compatible with an application-layer protocol, associating application-layer protocol information of the device with the device by populating an application-layer protocol identifier in the entry of the device entity.

10. The processor-implemented method of claim 8 , comprising:
associating the particular electronic device with a smart-device environment structure housing the particular electronic device by populating a pairing status field of the device entity with an identifier of the smart-device environment structure housing the particular electronic device.

11. The processor-implemented method of claim 1 , comprising:
generating an entry for at least one of the smart-device environment structures in a structure entity, wherein the entry for the smart-device environment comprises a unique identifier and an indication of devices paired to the smart-device environment; or
generating an authorized user entry in an authorized user entity, the authorized user entry representative of a user associated with the smart-device environment structure; and
associating the authorized user entity with the structure entity; or
both.

12. The processor-implemented method of claim 1 , comprising:
each time an electronic device is paired, generating a pairing history entry in a device history entity, the pairing history entry noting a pairing of the electronic device with at least one of the smart-device environment structures.

13. A system, comprising:
a processor; and
memory, comprising instructions executable by the processor to configure the processor to:
provision vendor information to associate rights to access and write vendor data of a data model comprising information related to one or more smart-devices, one or more smart-device environment structures comprising the one or more smart-devices, or any combination thereof with a vendor;
provision a particular electronic device type of the vendor, by providing compatibility information about the particular electronic device type to a service that interprets the compatibility information to understand subsequent data submissions of the particular electronic device, the provisioning of the particular electronic device type being associated with the vendor by associating the particular electronic device type with the provisioned vendor information;
provision the particular electronic device by:
accessing one or more build-time profiles for the particular electronic device that provide a description of capabilities of the particular electronic device, metadata related to data provided by the particular electronic device, or both; and
using the one or more build-time profiles to understand the subsequent data submissions of the particular electronic device, by importing the one or more build-time profiles to the service and generating one or more device type manifests that are used to describe, translate, validate, or any combination thereof, the subsequent d

Assignees

• Google Inc

Inventors

• Karp Igor

Classifications

• H05B47/105

  in response to determined parameters · CPC title

• H05B47/19

  via wireless transmission · CPC title

• H04L12/282

  based on user interaction within the home (receiver circuitry for displaying additional information being controlled by a remote control apparatus H04N21/42204) · CPC title

• H04W4/60

  Subscription-based services using application servers or record carriers, e.g. SIM application toolkits · CPC title

• F24F11/30

  for purposes related to the operation of the system, e.g. for safety or monitoring · CPC title