Private cloud server and client architecture without utilizing a routing server

• US 9,203,807 B2
• Filed: 09/09/2011
• Issued: 12/01/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, Yen, Chin-Tang, Zhao, Shi-Ming
• Primary Examiner(s): Nalven, Andrew
• Assistant Examiner(s): PHAM, QUY C
• Application Number:
  US13/229,285
• Publication Number:
  US 20130067550A1
• Time in Patent Office: 1,544 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 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks

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 server and at least one smart client device in communication therewith. The method and system comprise setting up the at least one private cloud server and the at least one smart client device in a client server relationship. The at least one private cloud 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 server and the at least one smart client device via the first message box and the second message box in a secure manner. The session base information is authenticated by the private cloud server and the at least one smart client device. The smart client device and the private cloud server can then communicate with each other after the session based information is authenticated.

Claims

1. A method comprising:

providing a private cloud server and a smart device client within a public cloud network, wherein the private cloud server includes a first message box and the smart device client includes a second message box; and

utilizing an authentication process to setup a client server relationship between the private cloud server and the smart device client, wherein the authentication process comprises;

creating, by the private cloud server, an authorized client list that includes an account name and unique public account information corresponding to the second message box of the smart device client,

transmitting, by the private cloud server, a session based invitation to the second message box of the smart device client, wherein the session based invitation includes the address of the first message box,

transmitting, by the smart device client, a session based access request to the first message box of the private cloud server, wherein the session based access request includes the address of the second message box, a public IP address of the smart device client, and a private IP address of the smart device client,

determining, by the private cloud server, whether the session based access request is valid,

in response to receiving a valid session based access request, registering, by the private cloud server, the address of the second message box and both the public and the private IP address of the smart device client, and

transmitting, by the private cloud server, a session based acknowledgment to the second message box of the smart device client, wherein the session based acknowledgment includes both a current public and a current private IP address of the private cloud server; and

determining, by the smart device client, that the session based acknowledgment is valid;

in response to receiving a valid session based acknowledgement, binding, by the smart device client, the public IP address and the private IP address of the private cloud server with the registered private IP address of the smart device client.

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

a computing device;

a connection through a router to a network;

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

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

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

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

send the 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 server to:

send a communication request to the smart device client;

maintain an open access route in the router so as to stay open pending smart device client response;

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

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

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

accept access of 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;

retrieve the session based invitation from the second message box;

send the session based access request to the first message box;

retrieve the session based acknowledgement from the second message box;

send a communication request to the private cloud server;

maintain an open access route in the router to stay open pending the private cloud server response;

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

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

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

access services from the private cloud server.

5. The method of claim 2, wherein the 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;

retrieve the session based invitation from the second message box;

send a session based access request to the first message box;

retrieve the session based acknowledgement from the second message box;

send a communication request to the private cloud server;

maintain an open access route in the router to stay open pending the private cloud server response;

wait for the private cloud server response;

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

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

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

access services from the private cloud server.

6. The method of claim 4, wherein the program of the smart device client provides for:

accessing the private cloud server from anywhere and at anytime;

accessing the private cloud server behind the firewall with fixed or dynamic IP addresses, wherein the smart device client requires no outside or third party routing server in a WAN, requires no additional router setup in a LAN, and establishes a secure peer-to-peer communication channel with the private cloud server; and

accessing services from the private cloud server.

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

accessing the private cloud server from anywhere and at anytime;

accessing the private cloud server behind the firewall with fixed or dynamic IP addresses, wherein the smart device client requires no outside or third party routing server in a WAN, requires no additional router setup in a LAN, and establishes a secure peer-to-peer communication with the private cloud server; and

accessing services from the private cloud server.

8. The method of claim 4, wherein the program of the smart device client provides for:

accessing the private cloud server from anywhere and at anytime;

accessing the private cloud server behind the firewall with fixed or dynamic IP addresses, wherein the smart device client requires no outside or third party routing server in a WAN, requires no additional router setup in a LAN, and establishes a secure peer-to-peer communication channel with the private cloud server;

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

accessing services from the private cloud server.

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

accessing the private cloud server from anywhere and at anytime;

accessing the private cloud server behind the firewall with fixed or dynamic IP addresses, wherein the smart device client requires no outside or third party routing server in a WAN, requires no additional router setup in a LAN, and establishes a secure peer-to-peer communication with the private cloud server;

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

accessing services from the private cloud server.