IP Library Granted Patent US 9,648,082
Granted Patent B2
US 9,648,082 · App. 14/928,547 · Granted May 9, 2017

Functionality inoperable unless node registered at remote site

Inventors: Babak Rezvani (Saint Petersburg, FL); Edward B. Kalin (Easton, CT); Jack L. Chen (Princeton, NJ); Reza Jalili (Sandy, UT)
Assignee: Google Inc.
H04L67/025G06F3/0482G06F3/04817G06F3/04842G06F3/04847G06F21/31G06Q10/06G06Q20/3672G06Q50/188G08B17/02G08B21/02G08C17/02H04L12/24H04L12/2801H04L12/2803H04L12/2809H04L12/2818H04L12/2836H04L29/06H04L29/12113H04L41/00H04L41/0806H04L41/0813H04L41/22H04L43/0817H04L43/50H04L61/1541H04L63/0876H04L63/102H04L65/1073H04L67/02H04L67/1095H04L67/16H04L67/42H04M1/725H04M1/72533H04N5/23206H04N5/23216H04W4/003H04W4/008H04W8/18H04W60/00H04W60/04G08C2201/20G08C2201/93H04L12/2807H04L43/10H04L67/2823H04L69/329H04L2012/285H04L2012/2841H04L2012/2845H04L2012/2849H04W24/00H04W28/04H04W88/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,648,082
App. No.
14/928,547
Granted
May 9, 2017
Kind
B2
Abstract

Systems and methods for providing registration at a remote site that may include, for example, a monitoring module that may communicate with a remote site. A registration protocol may be used by the monitoring module and the remote site in generating the messages communicated during the registration process. The monitoring module may gather and generate various identification information to be included in the registration protocol messages. The registration information provided by the monitoring module may be stored at the remote site in a database server having a database. A confirmation message may be communicated from the remote site to the monitoring module that may either acknowledge successful registration or report that an error occurred during the registration process.

Claims (47)

1. A system, comprising:

a node being disposed at a location, the node having node functionality that facilitates remote access to the node, wherein the remote access to the node enables a user of a user device to remotely access the node via the user device; and

a remote site being remote from the node, the remote site being remote from the user device of the user, the remote site having remote access functionality that facilitates the remote access to the node, wherein the remote access functionality of the remote site facilitates the remote access to the node by intermediating one or more requests or responses between the user device of the user and the node, wherein the node functionality of the node facilitates the remote access to the node by receiving or outputting the one or more requests or responses intermediated by the remote site, wherein the remote site is configured to be capable of:

registering the node at the remote site by associating in a data store (i) node identifying information that identifies the node and (ii) location identifying information that identifies the location where the node is disposed; and

causing the remote access to the node to be inoperable if the node has not been registered at the remote site.

2. The system of claim 1 , further comprising:

a user application being configured to run on the user device, the user device being configured to facilitate communication between the user application and the remote site, the user application being configured to facilitate the remote access to the node by:

displaying, via the user device, a user interface for remotely accessing the node, the user interface including a graphical component that virtually represents at least an aspect of the node, wherein the graphical component that virtually represents at least the aspect of the node is useable by the user to remotely access the node; and

responsive to use of the graphical component that virtually represents at least the aspect of the node, outputting a request or response to be transmitted to the node, wherein the request or response corresponds to the use of the graphical component.

3. The system of claim 1 , wherein the remote site is configured to be capable of intermediating the one or more requests or responses by:

receiving a request or response outputted by the user device, wherein the request or response includes the node identifying information that identifies the node;

access the location identifying information, wherein the location identifying information is associated in the data store with the node identifying information that is included in the request or response outputted by the user device, wherein the node identifying information is used to locate in the data store the location identifying information;

retrieve from the location identifying information an Internet address that is usable for sending data communications via the Internet to the node disposed at the location; and

sending the request or response outputted by the user device to the Internet address that is usable for sending data communications via the Internet to the node disposed at the location.

4. The method of claim 1 , wherein the remote site is configured to determine that the node is not registered at the remote site if the location identifying information is not associated in the data store with the node identifying information that is included in the request or response outputted by the user device.

5. The system of claim 1 , wherein the remote access to the node enables the user to remotely (i) control a function or state of the node, (ii) monitor a status of the function or the state of the node, or (iii) monitor information sensed by the node at the location where the node is disposed, wherein the one or more requests or responses that the remote site intermediates between the node and the user device include (i) information for controlling the function or state of the node, (ii) information indicative of the status of the function or state of the node, or (iii) information indicative of the information sensed by the node at the location.

6. The system of claim 1 , wherein the user device is a cellular mobile telephone, a mobile computing device, or a personal computer.

7. The system of claim 1 , wherein the node is a hub or system controller provided in communication with a device disposed at the location, wherein the hub or system controller intermediates communication between the device disposed at the location and the remote site or the user device, wherein the device disposed at the location is a camera, a radio, a smoke or fire detector, a contact sensor, a light switch, a light, an audio device, a video device, a display device, a washer, a dryer, a microwave oven, a cooking range, a car alarm, a plant watering device, a sprinkler, a carbon monoxide detector, a humidistat, or a rain gauge.

8. The system of claim 1 , wherein the node is a camera, a radio, a smoke or fire detector, a contact sensor, a light switch, a light, an audio device, a video device, a display device, a washer, a dryer, a microwave oven, a cooking range, a car alarm, a plant watering device, a sprinkler, a carbon monoxide detector, a humidistat, or a rain gauge.

9. A node, comprising:

processing components;

communication components being configured to output or receive data communications;

memory components being configured to store (i) node identifying information that identifies the node and (ii) location identifying information that identifies a location where the node is disposed, wherein the node identifying and the location identifying information is used to register the node at a remote site, wherein registering the node at the remote site includes associating in a data store (i) the node identifying information that identifies the node and (ii) the location identifying information that identifies the location where the node is disposed; and

software being configured to be executable by the processing components of the node, the software being configured to be capable of:

facilitating registration of the node at the remote site, wherein the software is configured to be capable of facilitating registration of the node at the remote site by causing the communication components to output for receipt by the remote site (i) the node identifying information that identifies the node and (ii) the location identifying information that identifies the location where the node is disposed; and

facilitating remote access to the node, wherein the remote access to the node enables a user of a user device to remotely access the node via the user device, wherein the software is configured to be capable of facilitating the remote access to the node by receiving or outputting one or more requests or responses that the remote site intermediates between the node and the user device;

wherein the remote access to the node is inoperable if the node has not been registered at the remote site.

10. The node of claim 9 , wherein the remote site intermediates the one or more requests or responses by:

receiving a request or response outputted by a user application running on the user device, wherein the request or response includes the node identifying information that identifies the node, wherein the user application is configured to output the request or response by:

displaying, via the user device, a user interface for remotely accessing the node, the user interface including a graphical component that virtually represents at least an aspect of the node, wherein the graphical component that virtually represents at least the aspect of the node is useable by the user to remotely access the node; and

generating the request or response according a use of the graphical component that virtually represents at least the aspect of the node;

access the location identifying information, wherein the location identifying information is associated in the data store with the node identifying information that is included in the request or response outputted by the user application, wherein the remote site uses the node identifying information to access the location identifying information;

retrieve from the location identifying information an Internet address that is usable for sending data communications via the Internet to the node disposed at the location; and

sending the request or response outputted by the user application to the Internet address that is usable for sending data communications via the Internet to the node disposed at the location.

11. The node of claim 9 , wherein the remote access to the node enables the user to remotely (i) control a function or a state of the node, (ii) monitor a status of the function or the state of the node, or (iii) monitor information sensed by the node at the location where the node is disposed.

12. The node of claim 11 , wherein the one or more requests or responses that the remote site intermediates between the node and the user device include (i) information for controlling the function or state of the node, (ii) information indicative of the status of the function or state of the node, or (iii) information indicative of the information sensed by the node at the location.

13. The node of claim 9 , wherein the user device is a cellular mobile telephone, a mobile computing device, or a personal computer.

14. The node of claim 9 , wherein the node is a hub or system controller provided in communication with a device disposed at the location, wherein the hub or system controller intermediates communication between the device disposed at the location and the remote site or the user device, wherein the device disposed at the location is a camera, a radio, a smoke or fire detector, a contact sensor, a light switch, a light, an audio device, a video device, a display device, a washer, a dryer, a microwave oven, a cooking range, a car alarm, a plant watering device, a sprinkler, a carbon monoxide detector, a humidistat, or a rain gauge.

15. The node of claim 9 , wherein the node is a camera, a radio, a smoke or fire detector, a contact sensor, a light switch, a light, an audio device, a video device, a display device, a washer, a dryer, a microwave oven, a cooking range, a car alarm, a plant watering device, a sprinkler, a carbon monoxide detector, a humidistat, or a rain gauge.

16. A method, comprising:

causing, by a remote site, functionality that facilitates remote access to a node to be inoperable if the node is not registered at the remote site, wherein the node is disposed at a location remote from the remote site, wherein the remote access to the node enables a user to remotely access the node via a user device located remote from the remote site, wherein registering the node at the remote site includes associating in a data store (i) node identifying information that identifies the node and (ii) location identifying information that identifies the location where the node is disposed, wherein the functionality that is caused to be inoperable includes intermediating one or more requests or responses between the user device and the node.

17. The method of claim 16 , wherein, before causing the functionality that facilitates the remote access to the node to be inoperable, the remote site:

receives from the user device a request to access the node, wherein the request includes the node identifying information that identifies the node; and

determines the node is not registered at the remote site if the node identifying information that identifies the node is not associated in the data store with the location identifying information that identifies the location where the node is disposed.

18. The method of claim 17 , wherein causing the functionality that facilitates the remote access to the node to be inoperable includes denying access to an Internet address for sending data communications via the Internet to the node disposed at the location.

19. The method of claim 16 , wherein the node is a hub or system controller provided in communication with a device disposed at the location, wherein the hub or system controller intermediates communication between the device disposed at the location and the remote site or the user device, wherein the device disposed at the location is a camera, a radio, a smoke or fire detector, a contact sensor, a light switch, a light, an audio device, a video device, a display device, a washer, a dryer, a microwave oven, a cooking range, a car alarm, a plant watering device, a sprinkler, a carbon monoxide detector, a humidistat, or a rain gauge.

20. The method of claim 16 , wherein the node is a camera, a radio, a smoke or fire detector, a contact sensor, a light switch, a light, an audio device, a video device, a display device, a washer, a dryer, a microwave oven, a cooking range, a car alarm, a plant watering device, a sprinkler, a carbon monoxide detector, a humidistat, or a rain gauge.

Assignments (8)
CHANGE OF NAME Recorded Oct 2, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044097/0658 →
CORRECTIVE ASSIGNMENT TO CORRECT THE SPELLING OF RECEIVING PARTY NAME PREVIOUSLY RECORDED ON REEL 043156 FRAME 0049. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 15, 2017
From: INTELLECTUAL VENTURES HOLDING 92 LLC
To: NEST LABS, INC
Reel/Frame 043969/0381 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 9, 2017
From: NEST LABS, INC
To: GOOGLE INC
Reel/Frame 043244/0155 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 1, 2017
From: INTELLECTUAL VENTURES HOLDING 92 LLC
To: NEST LABS INC
Reel/Frame 043156/0049 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 28, 2017
From: MANJOTRE DATA LLC
To: INTELLECTUAL VENTURES HOLDING 92 LLC
Reel/Frame 043129/0305 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 28, 2017
From: XANBOO INC
To: MANJOTRE DATA LLC
Reel/Frame 043129/0174 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CORRECTION TO SPELLING OF THE THIRD INVENTOR'S NAME PREVIOUSLY RECORDED ON REEL 043077 FRAME 0682. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF ASSIGNORS INTEREST. Recorded Jul 27, 2017
From: REZVANI, BABAK; KALIN, EDWARD B.; CHEN, JACK L.; JALILI, REZA
To: XANBOO INC
Reel/Frame 043478/0609 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2017
From: REZVANI, BABAK; KALIN, EDWARD B.; CHEN, JACK I.; JALILI, REZA
To: XANBOO INC
Reel/Frame 043077/0682 →
Continuity (9)
Continuation 14484135 · Sep 11, 2014
Continuation 14104936 · Dec 12, 2013
Continuation 12853140 · Aug 9, 2010
Continuation 11823870 · Jun 27, 2007
Continuation 11143920 · Jun 1, 2005
Continuation 10664609 · Sep 16, 2003
Continuation 09709688 · Nov 10, 2000
Provisional Application 60230318 · Sep 6, 2000
Related Publication 20160057198A1 · Feb 25, 2016