IP Library Granted Patent US 11,356,417
Granted Patent B2
US 11,356,417 · App. 16/807,481 · Granted Jun 7, 2022

Private cloud routing server connection mechanism for use in a private communication architecture

Inventor: Ben Wei Chen (Fountain Valley, CA)
Assignee: Kingston Digital, Inc.
H04L63/0272H04L63/029H04L63/08H04L63/083H04L63/10H04L63/102H04L63/164H04L67/1002H04W12/06H04W12/069
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,356,417
App. No.
16/807,481
Granted
Jun 7, 2022
Kind
B2
Abstract

A private cloud routing server client device (PCRSCD) is disclosed which connects to a private cloud routing server (PCRS) by a connection based on whether the PCRS is in a same Local Area Network (LAN) as the PCRSCD and whether the PCRS is directly connected to the public cloud network.

Claims (58)

1. A private cloud routing server client device (PCRSCD), comprising:

a computing device;

a connection to a network;

an application utility private cloud routing server (PCRS) App, when executed by the computing device, causes a private cloud routing server (PCRS) to access one or more client message boxes located on a public cloud network; and

a private cloud routing server (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 the one or more client message boxes on the public cloud network in a security process,

wherein the PCRSCD is connected to the PCRS by at least one connection of:

when the PCRS is in a same Local Area Network (LAN) as the PCRSCD and the PCRS is connected to the public cloud network via a router, the PCRSCD connects to the PCRS using a private IP address of the PCRS,

when the PCRS is in the same LAN as the PCRSCD and the PCRS is connected to the public cloud network without a router, the PCRSCD connects to the PCRS using a public IP address of the PCRS, and

when the PCRS is not in the same LAN as the PCRSCD, the PCRSCD connects through a WAN to the public cloud network using a public IP address of the PCRS,

wherein the PCRS includes a routing server message box utility to access a first message box located on a public cloud network,

wherein the PCRS registers public and private IP addresses of the PCRSCD,

wherein the client message box utility accesses a second message box located on the public cloud network, and

wherein the PCRS sends a session based acknowledgement with public and private IP addresses of the PCRS to the second message box.

2. The private cloud routing server client device of claim 1 ,

wherein the routing server message box utility of the PCRS passes a session based message between the first message box and the second message box in a security process.

3. The private cloud routing server client device of claim 2 ,

wherein the security process to pass the session based message between the first message box and the second message box of the PCRS and the PCRSCD, respectively, includes 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, and changing a PCRS peer-to-peer password by the PCRSCD and connecting to the PCRS by the PCRSCD.

4. The private cloud routing server client device of claim 3 ,

wherein a secure session based message is authenticated by the PCRS and the PCRSCD.

5. The private cloud routing server client device of claim 4 ,

wherein the PCRSCD and the PCRS communicates with each other after the session based message is authenticated, and

wherein a private network service is then securely accessible by the PCRSCD through the public cloud network based upon the authenticated session based message.

6. The private cloud routing server client device of claim 5 ,

wherein the PCFRSD sets up at least another PCRSCD in a client server relationship with the PCRS,

wherein the PCRSCD and the at least another PCRSCD communicates with the PCRS after the session based message is authenticated, and

wherein the PCRSCD and the at least another PCRSCD privately and securely communicates with each other through the public cloud network.

7. A private cloud routing server (PCRS), comprising:

a computing device;

a connection to a network;

a private cloud routing server (PCRS) utility, when executed by the computing device, causes a private cloud routing server (PCRS) to access one or more routing server message boxes located on a public cloud network;

a routing server message box utility to access a first message box located on the public cloud network; and

a private cloud routing server (PCRS) Client database and a Routing Server Message Box utility;

wherein the PCRS Client database contains a registered list of private cloud routing server (PCRS) clients, and

wherein the Routing Server Message Box utility communicates with the one or more routing server message boxes on the public cloud network in a security process,

wherein a private cloud routing server client device (PCRSCD) is connected to the PCRS by at least one connection of:

when the PCRS is in a same Local Area Network (LAN) as the PCRSCD and the PCRS is connected to the public cloud network via a router, the PCRSCD connects to the PCRS using a private IP address of the PCRS,

when the PCRS is in the same LAN as the PCRSCD and the PCRS is connected to the public cloud network without a router, the PCRSCD connects to the PCRS using a public IP address of the PCRS, and

when the PCRS is not in the same LAN as the PCRSCD, the PCRSCD connects through a WAN to the public cloud network using a public IP address of the PCRS, and

wherein the security process includes 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, and changing a PCRS peer-to-peer password by the PCRSCD and connecting to the PCRS by the PCRSCD.

8. The private cloud routing server of claim 7 ,

wherein the PCRS registers public and private IP addresses of the PCRSCD.

9. The private cloud routing server of claim 8 ,

wherein the PCRSCD includes a client message box utility to access a second message box located on the public cloud network.

10. The private cloud routing server of claim 9 ,

wherein the PCRS sends a session based acknowledgement with public and private IP addresses of the PCRS to the second message box.

11. The private cloud routing server of claim 10 ,

wherein the routing server message box utility of the PCRS passes a session based message between the first message box and the second message box in a security process.

12. The private cloud routing server of claim 11 ,

wherein a secure session based message is authenticated by the PCRS and the PCRSCD.

13. The private cloud routing server of claim 12 ,

wherein the PCRSCD and the PCRS communicates with each other after the session based message is authenticated, and

wherein a private network service is then securely accessible by the PCRSCD through the public cloud network based upon the authenticated session based message.

14. The private cloud routing server of claim 13 ,

wherein the PCFRSD sets up at least another PCRSCD in a client server relationship with the PCRS,

wherein the PCRSCD and the at least another PCRSCD communicates with the PCRS after the session based message is authenticated, and

wherein the PCRSCD and the at least another PCRSCD privately and securely communicates with each other through the public cloud network.

Continuity (6)
Continuation 14741145 · Jun 16, 2015
Continuation In Part 14663244 · Mar 19, 2015
Continuation In Part 14526393 · Oct 28, 2014
Continuation In Part 14450104 · Aug 1, 2014
Continuation In Part 13229285 · Sep 9, 2011
Related Publication 20200204536A1 · Jun 25, 2020