Data access and firewall tunneling using a custom socket factory

• US 10,616,182 B1
• Filed: 11/30/2017
• Issued: 04/07/2020
• Est. Priority Date: 11/30/2017
• Status: Active Grant

• Current Assignee: Progress Software Corporation
• Original Assignee: Progress Software Corporation
• Inventors: Hensley, John Alan
• Primary Examiner(s): Giddins, Nelson S.
• Application Number:
  US15/828,003
• Time in Patent Office: 859 Days
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2553 Binding renewal aspects, e.g. using keep-alive messages
• CPC Class Codes: H04L 61/256 NAT traversal
• CPC Class Codes: H04L 61/2592 using tunnelling or encapsulation
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 67/01 Protocols
• 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/55 Push-based network services

Abstract

A method of tunneling through a network separation device such as a firewall or a Network Address Translator comprising establishing via a custom socket factory coupled with a host device, a connection with a cloud server by tunneling through a network separation device; maintaining, via the custom socket factory, the connection with the cloud server through the network separation device; receiving, via the connection between the custom socket factory and the cloud server, connection information; and directly connecting, via the custom socket factory, to a client device using the connection information received from the cloud server.

Claims

1. A method for connecting a host device to a client device through a network separation device comprising:

establishing, by a custom socket factory coupled with the host device, a first connection between the custom socket factory and a cloud server by tunneling through the network separation device;

maintaining, via the custom socket factory, the first connection between the custom socket factory and the cloud server through the network separation device;

receiving, at the custom socket factory, from the cloud server, connection information associated with the client device via the first connection; and

establishing, by the custom socket factory, a second connection directly connecting the custom socket factory to the client device using the connection information associated with the client device, the second connection connecting the custom socket factory to the client device through the network separation device and using a network.

2. The method of claim 1, wherein the custom socket factory lacks a listener port and includes an interface that appears to other devices like a default socket factory interface.

3. The method of claim 1, wherein the connection information is received responsive to the cloud server receiving a request from the client device.

4. The method of claim 1, wherein maintaining the first connection between the custom socket factory and the cloud server through the network separation device further comprises performing one of a push action and a long polling action.

5. The method of claim 1, wherein establishing the second connection directly connecting the custom socket factory to the client device further comprises:

causing the custom socket factory to open a new socket connection to the client device linking the host device to the client device through the network separation device.

6. The method of claim 5, wherein the new socket connection is a client socket connection.

7. The method of claim 5, wherein the custom socket factory implements an accept method to return the new socket connection to a software of the host device that is responsible for responding to a request from the client device.

8. The method of claim 1, wherein the connection information associated with the client device is received responsive to the cloud server signaling to the custom socket factory that a connection is requested.

9. The method of claim 1, wherein the connection information associated with the client device includes address information of the client device.

10. The method of claim 1, wherein the host device is behind the network separation device and the network separation device is one of a firewall and a network address translator.

11. A system for tunneling through a network separation device comprising:

a custom socket factory coupled to a host device behind the network separation device, wherein the custom socket factory is configured to;

establish a first connection between the custom socket factory and a cloud server through the network separation device;

detect, using the first connection, a signal from the cloud server that a client device has requested access to the host device;

receive connection information associated with the client device from the cloud server via the first connection; and

establish a second connection directly connecting the custom socket factory to the client device using the connection information associated with the client device, the second connection connecting the custom socket factory to the client device through the network separation device and using a network.

12. The system of claim 11, further comprising:

the cloud server configured to;

receive a request from the client device to connect to the host device; and

provide the signal to the custom socket factory that the client device has requested to connect to the host device.

13. The system of claim 11, wherein the custom socket factory lacks a listener port and includes an interface that appears to other devices like a default socket factory interface.

14. The system of claim 11, wherein the custom socket factory detects the signal from the cloud server by performing one of a push action and a long polling action.

15. The system of claim 11, wherein the custom socket factory establishes the second connection directly connecting the custom socket factory to the client device by opening a new socket connection to the client device.

16. The system of claim 15, wherein the custom socket factory implements an accept method to return the new socket connection to the host device.

17. The system of claim 11, wherein the connection information associated with the client device includes address information of the client device.

18. The system of claim 11, wherein the network separation device is one of a firewall and a network address translator.

19. A method of tunneling through a network separation device comprising:

establishing, by a custom socket factory coupled with a host device behind the network separation device, a first connection between the custom socket factory and a cloud server through the network separation device;

detecting, by the custom socket factory, a signal from the cloud server that a client device has requested access to the host device by long polling the cloud server using the first connection;

receiving, at the custom socket factory, connection information associated with the client device from the cloud server via the first connection responsive to detecting the signal from the cloud server; and

establishing, by the custom socket factory, a second connection directly connecting the custom socket factory to the client device using the connection information associated with the client device to open a new socket connector, the second connection connecting the custom socket factory to the client device through the network separation device and using a network.

20. The method of claim 19, wherein the custom socket factory lacks a listener port and includes an interface that appears to other devices like a default socket factory interface.