PRIVATE CLOUD ROUTING SERVER, PRIVATE NETWORK SERVICE AND SMART DEVICE CLIENT ARCHITECTURE WITHOUT UTILIZING A PUBLIC CLOUD BASED ROUTING SERVER

• US 20140359704A1
• Filed: 08/01/2014
• Published: 12/04/2014
• Est. Priority Date: 09/09/2011
• Status: Active Grant

• Current Assignee: Kingston Digital, Inc. (Kingston Technology Corporation)
• Original Assignee: Kingston Digital, Inc. (Kingston Technology Corporation)
• Inventors: CHEN, Ben Wei
• Granted Patent: US 10,237,253 B2
• Time in Patent Office: Days
• US Class Current: 726/3
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• 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/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A method and system for use with a public cloud network is disclosed, wherein the public cloud network includes at least one private cloud routing server, at least one private network service and at least one smart device client in communication therewith. The method and system comprise setting up the at least one private cloud routing server, the at least one private network service and the at least one smart device client in a client server relationship. The at least one private cloud routing server includes a message box associated therewith. The first message box is located in the public network. The at least one smart client includes a second message box associated therewith. The second message box is located on the public network. The method includes passing session based message information between the at least one private cloud routing server and the at least one smart device client via the first message box and the second message box in a secure manner. The session based information is authenticated by the private cloud routing server and the at least one smart device client. The smart device client and the private cloud routing server can then communicate with each other after the session based information is authenticated. The at least one private network service is then manageable and accessible by the at least one smart device client from anywhere at anytime without utilizing a public cloud based routing server.

Claims

1. A method for use with a public cloud network, wherein the public cloud network includes at least one private cloud routing server, at least one private network service and at least one smart device client in communication therewith, the method comprising:

setting up the at least one private cloud routing server and the at least one smart device client in a client server relationship, wherein the at least one private cloud routing server includes a first message box associated therewith, the first message box being located on the public network;

wherein the at least one smart client includes a second message box associated therewith;

the second message box being located on the public cloud network; and

passing session based message information between the first message box and the second message box in a secure manner;

wherein the session base message is authenticated by the private cloud routing server and the at least one smart device client, wherein the smart device client and the private cloud routing server can communicate with each other after the session based message is authenticated, wherein the at least one private network service is then securely accessible by the smart device client through the public cloud network.

2. The method of claim 1, wherein the private cloud routing server comprises:

a computing device;

a connection through a router to a network;

a program that that enables the private cloud routing server to;

(a) create and manage an authorized client list to accommodate a plurality of smart device clients;

(b) send a session based invitation to the second message box of the smart device client;

(c) retrieve a session based access request of the smart device client from the first message box; and

(d) send a session based acknowledgement to the second message box of the smart device client.

3. The method of claim 2, wherein the program also enables the private cloud routing server to:

(e) send a communication request to the smart device client;

(f) punch a hole in the router to stay open pending smart device client response;

(g) wait for the router to bind the network connection between the smart device client and the private cloud routing server;

(h) route incoming request from the smart device client to the private cloud routing server;

(i) establish a secure peer-to-peer communication with the smart device client; and

(j) enable access of private network services from the smart device client.

4. The method of claim 2 wherein the smart device client comprises:

a computing device;

a connection through a router to a network;

wherein the router has a program that enables the smart device client to;

(a) retrieve a session based invitation from the smart device client message box;

(b) send a session based access request to the private cloud routing server message box;

(c) retrieve a session based acknowledgement from the smart device client message box;

(d) send a communication request to the private cloud routing server;

(e) punch a hole in the router to stay open pending the private cloud routing server response;

(f) wait for the router to bind the network connection between the private cloud routing server and the smart device client;

(g) route incoming request from the private cloud routing server to the smart device client;

(h) establish a secure peer-to-peer communication with the private cloud routing server; and

(i) access private network service through the private cloud routing server.

5. The method of claim 2 wherein a smart device client comprises:

a computing device;

a connection to a network, wired or wireless;

having an add-on program that enables the smart device client to;

(a) retrieve a session based invitation from the smart device client message box;

(b) send a session based reply to the private cloud routing server message box;

(c) retrieve a session based acknowledgement from the smart device client message box;

(d) send an access request to the private cloud routing server;

(e) wait for private cloud routing server response;

(f) bind the network connection between the private cloud routing server and the smart device client;

(g) route incoming request from the private cloud routing server to the smart device client;

(h) establish a secure peer-to-peer communication with the private cloud routing server; and

(i) access private network service through the private cloud routing server.

6. The method of claim 4 wherein the programs provide for

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication channel with the private cloud routing server; and

access private network service through the private cloud routing server.

7. The method of claim 5, wherein the program provides for:

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication with the server; and

accessing private network service through the private cloud routing server.

8. The method of claim 4, wherein the programs provide for

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication channel with the private cloud routing server;

mapping local physical I/O to virtual private cloud routing server I/O; and

accessing private network service through the private cloud routing server.

9. The method of claim 5, wherein the program provides for:

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication with the server;

mapping local physical I/O to virtual server I/O; and

accessing private network service through the private cloud routing server.

10. A private cloud routing server comprising:

a computing device;

a connection through a router to a network; and

a program executed by the computing device that enables the private cloud routing server to;

create and manage an authorized client list to accommodate a plurality of smart device clients;

send a session based invitation to a second message box of the smart device client;

retrieve a session based access request of the smart device client from a first message box;

send a session based acknowledgement to the second message box of the smart device client; and

enable access of private network services from the smart device client.

11. The private cloud routing server of claim 10, wherein the program provides:

sending a communication request to the smart device client;

punching a hole in the router to stay open pending smart device client response;

waiting for the router to bind the network connection between the smart device client and the private cloud routing server;

routing incoming request from the smart device client to the private cloud routing server;

establishing a secure peer-to-peer communication with the smart device client; and

enable access of private network services from the smart device client.

12. A smart device client comprising:

a computing device; and

a connection through a router to a network;

wherein the router has a program that enables the smart device client to;

retrieve a session based invitation from the smart device client message box;

send a session based access request to a private cloud routing server message box;

retrieve a session based acknowledgement from the smart device client message box;

send an communication request to the private cloud routing server;

punch a hole in the router to stay open pending the private cloud routing server response;

wait for the router to bind the network connection between the private cloud routing server and the smart device client;

route incoming request from the private cloud routing server to the smart device client;

establish a secure peer-to-peer communication with the private cloud routing server; and

access private network service through the private cloud routing server.

13. The smart device client of claim 12, wherein the program provides for:

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication channel with the private cloud routing server; and

accessing private network service through the private cloud routing server.

17. The smart device client of claim 12, wherein the program provides for:

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication with the server;

mapping local physical I/O to virtual server I/O; and

accessing private network service through the private cloud routing server.

14. A smart device client comprises:

a computing device;

a connection to a network; and

a program that enables the smart device client to;

retrieve a session based invitation from the smart device client message box;

send a session based reply to a private cloud routing server message box;

retrieve a session based acknowledgement from the smart device client message box;

send an access request to a private cloud routing server;

wait for the private cloud routing server response;

bind a network connection between the private cloud routing server and the smart device client;

route incoming request from the private cloud routing server to the smart device client;

establish a secure peer-to-peer communication with the private cloud routing server; and

access private network service through the private cloud routing server.

15. The smart device client of claim 14, wherein the program provides for:

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication with the server; and

accessing private network service through the private cloud routing server.

16. The smart device client of claim 14, wherein the program provides for:

accessing the private cloud routing server from anywhere at anytime;

accessing the private cloud routing server behind the firewall with fixed or dynamic IP addresses;

wherein the smart device client requires no outside or public cloud based routing server in the WAN;

requires no additional router setup in the LAN;

establishes a secure peer-to-peer communication channel with the private cloud routing server;

mapping local physical I/O to virtual private cloud routing server I/O; and

accessing private network service through the private cloud routing server.