Private cloud routing server, private network service and smart device client architecture without utilizing a public cloud based routing server

• US 10,237,253 B2
• Filed: 08/01/2014
• Issued: 03/19/2019
• 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
• Primary Examiner(s): Le, Chau
• Application Number:
  US14/450,104
• Publication Number:
  US 20140359704A1
• Time in Patent Office: 1,691 Days
• 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 that includes a private cloud routing server, a private router, a private network service, and a smart device client, the method comprising:

processing an initial setup of a private cloud routing server and a smart device client in a client server relationship, wherein the private cloud routing server is associated with a server message box located on a public cloud network separate from the private cloud routing server, and wherein the smart device client is associated with a client message box located on the public cloud network separate from the smart device client, the initial setup including;

sending, by the private cloud routing server, a session based invitation to the client message box of the smart device client,

retrieving, by the smart device client, the session based invitation of the private cloud routing server from the client message box of the smart device client,

validating, by the smart device client, the session based invitation,

in response to validating the session based invitation, transmitting, by the smart device client, a session based access request that includes a public IP address and a private IP address of the smart device client to the server message box of the private cloud routing server,

retrieving, by the private cloud routing server, the session based access request of the smart device client from the server message box,

validating, by the private cloud routine server, the session based access request;

in response to the validating the session based access request, registering, by the private cloud routing server, the public IP address and the private IP address of the smart device client to allow access to the private cloud routing server by the smart device client,

sending, by the private cloud routing server, a session based acknowledgment with a public IP address and a private IP address of the private cloud routing server to the client message box of the smart device client, and

enabling the smart device client to securely access a private network service via the public cloud network after registration of the public and private IP address of the private cloud routing server; and

connecting the private cloud routing server and smart device client by at least one connection of;

in response to the private IP address of the private cloud routing server being in a same first Local Area Network (LAN) as the smart device client, the smart device client directly connects to the private cloud routing server using the private IP address of the private cloud routing server, and

in response to the private IP address of the private cloud routine server not being in the same first LAN as the smart device client, the smart device client connects through a first WAN to the public cloud network using the public IP address of the private cloud routine server.

2. The method of claim 1, further comprising:

creating and managing, by the private cloud routing server, an authorized client list including corresponding message box information of a plurality of smart device clients.

3. The method of claim 2, wherein the initial setup further includes:

sending a communication request to the smart device client;

punching a hole in the router to stay open for a 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

enabling access of the private network service from the smart device client.

4. The method of claim 2, wherein the initial setup further includes:

retrieving the session based invitation from the device message box;

retrieving the session based acknowledgement from the client message box;

sending a communication request to the private cloud routing server;

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

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

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

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

accessing the private network service through the private cloud routing server.

5. The method of claim 4, wherein the initial setup further includes:

accessing the private cloud routing server;

accessing the private cloud routing server behind a 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), and establishes a secure peer-to-peer communication channel with the private cloud routing server; and

accessing the private network service through the private cloud routing server.

6. The method of claim 4, wherein the initial setup further includes:

accessing the private cloud routing server;

accessing the private cloud routing server behind a 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), and establishes a secure peer-to-peer communication channel with the private cloud routing server;

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

accessing the private network service through the private cloud routing server.

7. The method of claim 2, wherein the initial setup further includes:

retrieving the session based invitation from the client message box;

sending a session based reply to the server message box;

retrieving the session based acknowledgement from the client message box;

waiting for a private cloud routing server response;

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

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

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

accessing the private network service through the private cloud routing server.

8. The method of claim 7 wherein the initial setup further includes:

accessing the private cloud routing server;

accessing the private cloud routing server behind a 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), and establishes a secure peer-to-peer communication with the server; and

accessing the private network service through the private cloud routing server.

9. The method of claim 7, wherein the initial setup further includes:

accessing the private cloud routing server;

accessing the private cloud routing server behind a 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), and establishes a secure peer-to-peer communication with the server;

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

accessing the private network service through the private cloud routing server.

10. A private cloud routing server, comprising:

a computing device;

a network connection through a router to a network; and

a program when executed by the computing device 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 client message box of a smart device client of the plurality of smart device clients;

retrieve a session based access request of the smart device client from a server message box, wherein a public IP address and a private IP address of both the private cloud routing server and the smart device client is registered;

send a session based acknowledgement to the client message box of the smart device client, wherein the session based acknowledgment includes a current public IP address and a current private IP address of the private cloud routing server; and

enable access of private network services from the smart device client; and

connect the private cloud routing server and smart device client by at least one connection of;

in response to the private IP address of the private cloud routine server being in a same first Local Area Network (LAN) as the smart device client, the smart device client directly connects to the private cloud routine server using the private IP address of the private cloud routine server, and

in response to the private IP address of the private cloud routine server not being in the same first LAN as the smart device client, the smart device client connects through a first WAN to the public cloud network using the public IP address of the private cloud routing server.

11. A smart device client, comprising:

a computing device; and

a network connection through a router to a network, wherein the router has a program that in response to execution by the computing device enables the smart device client to;

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

send a session based access request to a private cloud routing server message box, wherein a public IP address and a private IP address of both a private cloud routing server and the smart device client is registered;

retrieve a session based acknowledgement from the smart device client message box, wherein the session based acknowledgment includes a current public IP address and a current private IP address of the private cloud routing server;

send a communication request to the private cloud routing server;

punch a hole in the router to stay open pending a 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 an 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;

access a private network service through the private cloud routing server; and

connect the private cloud routing server and smart device client by at least one connection of;

in response to the private IP address of the private cloud routing server being in a same first Local Area Network (LAN) as the smart device client, the smart device client directly connects to the private cloud routing server using the private IP address of the private cloud routine server, and

in response to the private IP address of the private cloud routine server not being in the same first LAN as the smart device client, the smart device client connects through a first WAN to the public cloud network using the public IP address of the private cloud routing server.