IP Library Granted Patent US 10,505,903
Granted Patent B1
US 10,505,903 · App. 15/650,549 · Granted Dec 10, 2019

System and method of obtaining data from private cloud behind enterprise firewall

Inventors: Rohan Pednekar (Maharashtra, IN); Pramod Biradar (Maharashtra, IN); Ritansh Raj (Maharashtra, IN)
Assignee: EMC IP Holding Company LLC
H04L63/029G06F21/31H04L9/30H04L63/0428H04L63/061H04L63/08
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 10,505,903
App. No.
15/650,549
Filed
Jul 14, 2017
Granted
Dec 10, 2019
Kind
B1
Art Unit
2436
USPC
713/168
Abstract

A public cloud includes a processor. The processor obtains, from a client via a first network connection, a data access request that specifies data stored in a private cloud separated from the public cloud server by a firewall; sends the data access request to the private cloud through the firewall via a second network connection; receives the data stored in the private cloud via the second network connection; and forwards the received data stored in the private cloud to the client.

Claims (53)

1. A public cloud server in a public cloud, comprising:

a processor programmed to:

obtain, from a first client via a first network connection, a data access request that specifies data stored in a private cloud separated from the public cloud server by a firewall,

authenticate access to the data, for the first client, using credential data stored in the public cloud server,

send the data access request to the private cloud through the firewall via a second network connection,

receive the data stored in the private cloud via the second network connection, and

forward, using a virtual private network (VPN) interface table, the received data stored in the private cloud to the first client,

wherein the public cloud server comprises the VPN interface table, and

wherein the VPN interface table specifies logical network connections between the first client, the public cloud server, and the private cloud.

2. The public cloud server of claim 1 , wherein the second network connection is a secure socket layer connection.

3. The public cloud server of claim 1 , wherein the data access request is sent to the private cloud using the VPN interface table.

4. The public cloud server of claim 1 , wherein the logical network connections route IP traffic through a secure socket layer (SSL) connection.

5. The public cloud server of claim 4 , wherein the second network connection is a SSL connection, and wherein the first network connection is not a SSL connection.

6. The public cloud server of claim 1 , wherein the first network connection is a connection through the Internet.

7. The public cloud server of claim 1 , wherein the data access request comprises:

a first credential associated with the public cloud server; and

a second credential associated with the private cloud.

8. The public cloud server of claim 1 , wherein the processor is further programmed to:

obtain, from a second client, a second data access request that specifies second data stored in the private cloud;

in response to obtaining the second data access request, establish a third network connection, wherein the third network connection is a secure socket layer link connection between the public cloud server and the private cloud;

send the second data access request to a private cloud server via the third network connection;

receive the second data stored in the private cloud via the third network connection; and

forward the second data to the second client.

9. The public cloud server of claim 8 , wherein the processor is further programmed to:

after establishing the third network connection, establish a virtual private network (VPN),

wherein the VPN specifies logical connections between the second client, the public cloud, and the private cloud.

10. The public cloud server of claim 9 , wherein the second data access request is sent to the private cloud server using the VPN.

11. The public cloud server of claim 9 , wherein the second data is forwarded to the second client using the VPN.

12. The public cloud server of claim 1 , wherein the processor is further programmed to:

before sending the data access request to the private cloud, establish a virtual private network (VPN),

wherein the VPN specifies logical connections between the first client, the public cloud, and the private cloud.

13. The public cloud server of claim 12 , wherein the data access request is sent to the private cloud using the VPN.

14. The public cloud server of claim 12 , wherein the data is forwarded to the first client using the VPN.

15. A method of operating a public cloud server in a public cloud, comprising:

obtaining, by the public cloud server from a first client via a first network connection, a data access request that specifies data stored in a private cloud separated from the public cloud server by a firewall,

authenticating access to the data, for the first client, using credential data stored in the public cloud server,

sending, by the public cloud server, the data access request to the private cloud through the firewall via a second network connection,

receiving, by the public cloud server, the data stored in the private cloud via the second network connection, and

forwarding, by the public cloud server using a virtual private network (VPN) interface table, the received data stored in the private cloud to the first client,

wherein the VPN interface table specifies logical network connections between the first client, the public cloud server, and the private cloud.

16. The method of claim 15 , further comprising:

before sending the data access request to the private cloud, establishing a virtual private network (VPN),

wherein the VPN specifies logical connections between the first client, the public cloud, and the private cloud.

17. A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for operating a public cloud server in a public cloud, the method comprising:

obtaining, by the public cloud server from a first client via a first network connection, a data access request that specifies data stored in a private cloud separated from the public cloud server by a firewall,

authenticating access to the data, for the first client, using credential data stored in the public cloud server,

sending, by the public cloud server, the data access request to the private cloud through the firewall via a second network connection,

receiving, by the public cloud server, the data stored in the private cloud via the second network connection, and

forwarding, by the public cloud server using a virtual private network (VPN) interface table, the received data stored in the private cloud to the first client,

wherein the VPN interface table specifies logical network connections between the first client, the public cloud server, and the private cloud.

18. The non-transitory computer readable medium of claim 17 , wherein the method further comprises:

before sending the data access request to the private cloud, establishing a virtual private network (VPN),

wherein the VPN specifies logical connections between the first client, the public cloud, and the private cloud.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (043775/0082) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 060958/0468 →
RELEASE OF SECURITY INTEREST AT REEL 043772 FRAME 0750 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 058298/0606 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
PATENT SECURITY AGREEMENT (CREDIT) Recorded Sep 6, 2017
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 043772/0750 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Sep 6, 2017
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 043775/0082 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2017
From: RAJ, RITANSH; BIRADAR, PRAMOD; PEDNEKAR, ROHAN
To: EMC IP HOLDING COMPANY
Reel/Frame 043226/0044 →
Cited By (2)
US 12,306,977 US 12,355,767