PRIVATE CLOUD ROUTING SERVER CONNECTION MECHANISM FOR USE IN A PRIVATE COMMUNICATION ARCHITECTURE

• US 20150288678A1
• Filed: 06/16/2015
• Published: 10/08/2015
• 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,601,810 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/164 at the network layer
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys

Abstract

A method is disclosed for providing a secure session based message connection mechanism between a private cloud routing server (PCRS) and at least one smart device client in a PCRS network. The method includes initializing and provisioning of the PCRS. The method also includes creating a PCRS Client and viewing the PCRS Client. In addition, the method includes editing a peer-to-peer password and status of the PCRS. The method also includes changing the peer-to-peer password by the at least one smart device client. The method also includes resetting the peer-to-peer password and status by an administrator from a PCRS LAN. Finally, the method includes connecting to the PCRS by the at least one smart device client.

Claims

1. A method for use with a public cloud network, the method comprising:

setting up at least one private cloud routing server and 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 a public cloud 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;

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

wherein a secure session based message connection mechanism between the private cloud routing server (PCRS) and the at least one smart device client comprises initializing and provisioning of the PCRS, creation of a PCRS Client, viewing the PCRS Client, editing a peer-to-peer password and status of the PCRS, changing the PCRS peer-to-peer password by the at least one smart device client and connecting to the PCRS by the at least one smart device client;

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

setting up at least another smart device client in a client server relationship with the at least one private cloud routing server;

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

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

a computing device;

a connection to a network;

a program that enables the at least one 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;

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

(d) send a session based acknowledgement to the second message box.

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

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

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

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

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

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

(j) enable access of the at least one private network service from the at least one smart device client; and

(k) enable private and secure communication between the at least one smart device client and the at least another smart device client.

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

a computing device;

a connection through a router to a network;

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

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

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

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

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

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

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

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

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

(i) access the at least one private network service through the at least one private cloud routing server; and

(k) communicate with at least another smart device client through the private cloud routing server.

5. The method of claim 2 wherein the at least one smart device client comprises:

a computing device;

a connection to a network, wired or wireless;

having a program that enables the at least one smart device client to;

(a) retrieve a session based invitation from the at least one 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 at least one smart device client message box;

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

(e) wait for the at least one private cloud routing server response;

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

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

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

(i) access the at least one private network service through the at least one private cloud routing server; and

(j) communicate with the at least another smart device client through the at least one private cloud routing server.

6. The method of claim 4 wherein the program provides for:

accessing the at least one private cloud routing server from anywhere at anytime;

accessing the at least one private cloud routing server behind a firewall with fixed or dynamic IP addresses;

wherein the at least one smart device client requires no outside or public cloud based routing server in a wide area network (WAN);

requires no additional router setup in a local area network (LAN);

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

accessing private network service through the private cloud routing server; and

communicating with at least another smart device client 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 a wide area network (WAN);

requires no additional router setup in a local area network (LAN);

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

accessing private network service through the at least one private cloud routing server; and

communicating with the at least another smart device client through the at least one private cloud routing server.

8. The method of claim 4, wherein the program provides for

accessing the at least one private cloud routing server from anywhere at anytime;

accessing the at least one private cloud routing server behind a firewall with fixed or dynamic IP addresses;

wherein the at least one smart device client requires no outside or public cloud based routing server in a wide area network (WAN);

requires no additional router setup in the a local area network (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;

accessing private network service through the private cloud routing server; and

communicating with at least another smart device client 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 a wide area network (WAN);

requires no additional router setup in a local area network (LAN);

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

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

accessing private network service through the private cloud routing server; and

communicating with the at least another smart device client through the private cloud routing server.

10. A method for providing a secure session based message connection mechanism between a private cloud routing server (PCRS) and at least one smart device client in a PCRS network comprises:

initializing and provisioning of the PCRS;

creating a PCRS Client;

viewing the PCRS Client;

editing a peer-to-peer password and status of the PCRS;

changing the peer-to-peer password by the at least one smart device client;

resetting the peer-to-peer password and status by an administrator from a PCRS LAN; and

connecting to the PCRS by the at least one smart device client.

11. A method for a communication flow of a connection mechanism between a private cloud routing server (PCRS) and a PCRS Client Device through a Cloud Network;

the method comprising;

requesting by a client device application to connect to a PCRS Utility through a Client Message Box;

wherein a server portion of the PCRS Utility receives a registration through a routing server message box;

requesting by the PCRS Client Device to a server portion of the PCRS Utility through the Client Message Box connection to a client portion of the PCRS Utility;

receiving by the server portion of the PCRS Utility the request through a Routing Server Message Box;

notifying the client portion of the PCRS Utility by the server portion of the PCRS utility of the server portion'"'"'s intention to connect;

replying by the client portion of the PCRS Utility to the server portion of the PCRS Utility with its own registration;

responding by the server portion of the PCRS Utility to the Client Device Application through the Routing Server Message Box;

punching holes through a firewall of the client portion of the PCRS Utility;

punching holes through a firewall of the PCRS Client Device;

starting peer-to-peer communication between the PCRS Client Device and the client portion of the PCRS Utility;

wherein all information exchange between the PCRS Utility and the PCRS Client Device is through the Routing Server Message Box and the Client Message Box.

12. The method of claim 11, wherein either of the Routing Server Message Box or the Client Message Box, are hosted inside an email server, text message server, web server, or a server that is configured to host secure message for information exchange between the PCRS, and the PCRS Client Device;

wherein the Routing Server Message Box or the Client Message Box, is accessible and under the secure and private control of either the PCRS or the PCRS Client Device;

wherein if the Routing Server Message Box or the Client Message Box is down, either can be replaced or redeployed immediately without jeopardizing the communication between the PCRS and the PCRS Client Device in the Cloud Network.

13. A private cloud routing server (PCRS) device client application utility comprising:

a PCRS Server database and a Client Message Box utility;

wherein the PCRS Server database contains a registered list of PCRS servers;

wherein the Client Message Box utility communicates with one or more client message boxes.

14. A private cloud routing server (PCRS) utility comprising:

a PCRS Client database and a Routing Server Message Box utility;

wherein the PCRS Client database contains a registered list of PCRS clients;

wherein the a Routing Server Message Box utility communicates with one or more routing server message boxes.