Devices for providing secure remote access

• US 9,391,966 B2
• Filed: 03/08/2013
• Issued: 07/12/2016
• Est. Priority Date: 03/08/2013
• Status: Active Grant

• Current Assignee: Snap One LLC (Snap One Holdings Corp.)
• Original Assignee: Control4 Corporation (Snap One Holdings Corp.)
• Inventors: Mar, John, Hudson, Charles Alexander, Perry, Clinton, Clark, William Richard, Smith, Wallace Eric, Van Uitert, Andrew
• Primary Examiner(s): Pwu, Jeffrey
• Assistant Examiner(s): Tran, Baotram
• Application Number:
  US13/790,538
• Publication Number:
  US 20140259108A1
• Time in Patent Office: 1,222 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

A method for providing secure remote access by a controller is described. The method includes sending one or more endpoint requests. The method also includes receiving authentication service endpoint information and connection service endpoint information. The method further includes requesting authentication based on the authentication service endpoint information. Requesting authentication includes requesting license validation. The method also includes sending one or more registration messages based on the connection service endpoint information. The method further includes receiving a session request. The method additionally includes determining controller candidate link information. The method also includes sending the controller candidate link information. The method further includes receiving an automation message based on the controller candidate link information.

Claims

1. A method for providing secure remote access by a controller, comprising:

sending one or more endpoint requests;

receiving authentication service endpoint information and connection service endpoint information;

requesting authentication based on the authentication service endpoint information, wherein requesting authentication comprises requesting license validation;

receiving, based at least upon the authentication request, a controller session token including at least a unique identifier associated with the controller;

sending one or more registration messages based on the connection service endpoint information, the one or more registration messages including at least an internal and an external internet protocol (IP) address associated with the controller and the controller session token, wherein registering with a connection service allows port forwarding to be avoided;

receiving a session request, wherein receiving the session request is based on the controller session token, and wherein the session request comprises device candidate link information and a device session token;

determining controller candidate link information, wherein the controller candidate link information comprises an internet protocol (IP) address and a port;

sending the controller candidate link information; and

receiving an automation message based on the controller candidate link information, the automation message including at least one or more instructions to initiate one or more automation tasks.

2. The method of claim 1, wherein receiving the automation message comprises receiving the automation message via at least one of a relay link and a peer-to-peer link.

3. A method for providing secure remote access to a controller by an electronic device, comprising:

sending one or more endpoint requests;

receiving authentication service endpoint information and connection service endpoint information;

requesting authentication based on the authentication service endpoint information, wherein requesting authentication comprises requesting license validation based on electronic device credentials;

receiving, based upon the authentication request, a device session token;

sending a session request based on the connection service endpoint information, the session request including at least device candidate link information, the device session token and an internet protocol (IP) address associated with the electronic device, wherein using a connection service allows port forwarding to be avoided;

receiving controller candidate link information, wherein the controller candidate link information comprises an internet protocol (IP) address and a port; and

sending an automation message based on the controller candidate link information, the automation message including at least one or more instructions to initiate one or more automation tasks.

4. The method of claim 3, wherein sending the automation message comprises sending the automation message via at least one of a relay link and a peer-to-peer link.

5. A controller for providing secure remote access, comprising:

a processor;

memory in electronic communication with the processor;

instructions stored in the memory, the instructions being executable to;

send one or more endpoint requests;

receive authentication service endpoint information and connection service endpoint information;

request authentication based on the authentication service endpoint information, wherein requesting authentication comprises requesting license validation;

receive, based at least upon the authentication request, a controller session token including at least a unique identifier associated with the controller;

send one or more registration messages based on the connection service endpoint information, the one or more registration messages including at least an internal and external internet protocol (IP) address associated with the controller and the controller session token, wherein registering with a connection service allows port forwarding to be avoided;

receive a session request, wherein receiving the session request is based on the controller session token, and wherein the session request comprises device candidate link information and a device session token;

determine controller candidate link information, wherein the controller candidate link information comprises an internet protocol (IP) address and a port;

send the controller candidate link information; and

receive an automation message based on the controller candidate link information, the automation message including at least one or more instructions to initiate one or more automation tasks.

6. The controller of claim 5, wherein receiving the automation message comprises receiving the automation message via at least one of a relay link and a peer-to-peer link.

7. An electronic device for providing secure remote access to a controller, the electronic device comprising:

a processor;

memory in electronic communication with the processor;

instructions stored in the memory, the instructions being executable to;

send one or more endpoint requests;

receive authentication service endpoint information and connection service endpoint information;

request authentication based on the authentication service endpoint information, wherein requesting authentication comprises requesting license validation based on electronic device credentials;

receive, based at least upon the authentication request, a device session token;

send a session request based on the connection service endpoint information, the session request including at least device candidate link information, the device session token and an internet protocol (IP) address of the electronic device, wherein using a connection service allows port forwarding to be avoided;

receive controller candidate link information, wherein the controller candidate link information comprises an internet protocol (IP) address and a port; and

send an automation message based on the controller candidate link information, the automation message including at least one or more instructions to initiate one or more automation tasks.

8. The electronic device of claim 7, wherein sending the automation message comprises sending the automation message via at least one of a relay link and a peer-to-peer link.