Remote port access (RPA) server

• US 8,812,616 B2
• Filed: 10/02/2009
• Issued: 08/19/2014
• Est. Priority Date: 10/03/2008
• Status: Active Grant

• Current Assignee: Systech Corporation
• Original Assignee: Systech Corporation
• Inventors: Armerding, Donald G.
• Primary Examiner(s): BAYARD, DJENANE M
• Application Number:
  US12/573,041
• Publication Number:
  US 20100088396A1
• Time in Patent Office: 1,782 Days
• Field of Search: 709/217, 709/218, 709/219
• US Class Current: 709/217
• CPC Class Codes: H04L 49/253 using establishment or release of connections between ports
• 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/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Systems and methods for accessing data from one or more remote devices and providing data to remote devices installed behind one or more firewalls are provided. The remote devices are configured to automatically detect network connectivity and to open a network connection to a remote port access (RPA) server. The remote devices initiate the connection with the RPA server enabling the connection to be established through the firewall. A client device establishes a network connection to the RPA server in order to access data from or to provide data to one or more of the remote devices. The RPA server acts as an intermediary between the RPA server and the remote devices that receives data from the client device and sends the data to the remote device and receives data from the remote devices and sends the data to the client device.

Claims

1. A method for use at a remote port access (RPA) server to provide access to data from an end device, the method comprising:

receiving a first connection request at the RPA server from a remote device, the first connection request received at a first predetermined port number, the remote device being located behind a firewall configured to allow outbound connections from the remote device and block inbound connections to the remote device, and the remote device being coupled to the end device;

in response to the first connection request, determining whether the remote device is associated with a client;

establishing a first network connection between the RPA server and the remote device through the firewall when the remote device is associated with the client;

receiving a second connection request at the RPA server from a client device, the second connection request received at a second predetermined port number, the client device being located outside the firewall and associated with the client;

establishing, in response to the second connection request, a second network connection between the RPA server and the client device;

receiving a request from the client device for data from the end device coupled to the remote device, the request received at the RPA server via the second network connection;

in response to the request for data, determining whether the remote device is associated with the client;

requesting data by the RPA server from the end device via the remote device and the first network connection when the remote device is associated with the client;

receiving the requested data at the RPA server from the remote device via the first network connection; and

providing the requested data from the RPA server to the client device via the second network connection.

2. The method of claim 1, further comprising:

listening for connection requests from the remote device at the first predetermined port number.

3. The method of claim 1, further comprising:

listening for connection requests from the client device at the second predetermined port number.

4. The method of claim 1 wherein the remote device is assigned a unique identifier at the time the device is manufactured, and wherein the first connection request received from the remote device includes the unique identifier assigned to the remote device.

5. The method of claim 4, further comprising:

comparing the unique identifier for the remote device received in the first connection request to a set of remote devices associated with a client; and

adding the unique identifier for the remote device a list of connected but unassigned remote devices if the unique identifier for the remote device is not included in the set of remote devices associated with a client.

6. The method of claim 4, wherein the first network connection is only established if the unique identifier was previously registered with the RPA server.

7. The method of claim 1 wherein the remote device is configured to automatically generate the first connection request in response to detecting network connectivity, wherein the first network connection is a Transport Control Protocol (TCP) connection through the firewall.

8. The method of claim 1, further comprising:

receiving data automatically transmitted from the remote device;

storing the data received from the remote device; and

transmitting the stored data to the client device.

9. The method of claim 8, wherein the data automatically transmitted from the remote device is data from the end device.

10. The method of claim 1, further comprising:

adding an identifier, corresponding to the remote device, to an unassigned-device listing when the remote device is not associated with a client; and

in further response to the request for data, providing the unassigned-device listing to the client device through a registration interface when the remote device is not associated with the first client.

11. A system comprising:

a remote device;

a client device; and

a remote port access server communicatively coupled to the remote device and the client device, and configured to

listen for connection requests from the remote device on a first set of predetermined ports and determine whether the remote device is associated with a client, the remote device being located behind a firewall configured to allow outbound connections from the remote device and block inbound connections to the remote device, and the remote device being coupled to an end device;

establish a first network connection with the remote device through the firewall in response to a connection request from the remote device when the remote device is associated with the client;

listen for connection requests from the client device on a second set of predetermined ports and determine whether the remote device is associated with the client, the client device being located outside of the firewall and associated with the client;

establish a second network connection with the client device in response to receiving a connection request from the client device;

receive a data request from the client device for data from the end device;

request from the end device, via the remote device, the data requested in the data request when the remote device is associated with the client;

receive the requested data from the remote device; and

transmit the requested data received from the remote device to the client.

12. The system of claim 11 wherein the remote device is assigned a unique identifier at the time the device is manufactured, and wherein the connection request received from the remote device includes the unique identifier assigned to the remote device.

13. The system of claim 12 wherein the remote port access server is further configured to:

compare the unique identifier for the remote device received in the connection request to a set of remote devices associated with a client; and

add the unique identifier for the remote device a list of connected but unassigned remote devices if the unique identifier for the remote device is not included in the set of remote devices associated with a client.

14. The system of claim 11 wherein the first network connection is Transport Control Protocol (TCP) connection through the firewall.

15. The system of claim 11 wherein the remote device is configured to automatically generate the connection request in response to detecting network connectivity.

16. A non-transitory computer-readable medium comprising processor-executable instructions that, when executed, direct a computer system to perform actions comprising:

receiving a first connection request from the remote device, the connection request from the remote device received at a first predetermined port number, the remote device being located behind a firewall configured to allow outbound connections from the remote device and block inbound connections to the remote device, and the remote device being coupled to the end device;

in response to the first connection request, determining whether the remote device is associated with a client;

establishing a first network connection with the remote device through the firewall when the remote device is associated with the client;

receiving, in response to the first connection request, a second connection request from a client device, the connection request from the client device received at a second predetermined port number, the client device being located outside the firewall and associated with the client;

establishing, in response to the second connection request, a second network connection with the client device;

receiving a request from the client device for data from the end device coupled to the remote device, the request received at the RPA server through the second network connection;

in response to the request for data, determining whether the remote device is associated with the client;

requesting data from the end device via the remote device and the first network connection when the remote device is associated with the client;

receiving the requested data from the remote device via the first network connection; and

providing the requested data to the client device via the second network connection.

17. The non-transitory computer readable medium of claim 16, further comprising instructions that, when executed, direct the computer system to perform actions comprising:

listening for connection requests from the remote device at the first predetermined port number.

18. The non-transitory computer readable medium of claim 16, further comprising instructions that, when executed, direct the computer system to perform actions comprising:

listening for connection requests from the client device at the second predetermined port number.

19. The non-transitory computer readable medium of claim 16 wherein the remote device is assigned a unique identifier at the time the device is manufactured, and wherein the first connection request received from the remote device includes the unique identifier assigned to the remote device.

20. The non-transitory computer readable medium of claim 19, further comprising instructions that, when executed, direct the computer system to perform actions comprising:

comparing the unique identifier for the remote device received in the first connection request to a set of remote devices associated with a client; and

adding the unique identifier for the remote device a list of connected but unassigned remote devices if the unique identifier for the remote device is not included in the set of remote devices associated with a client.

21. The non-transitory computer readable medium of claim 16 wherein the first network connection is Transport Control Protocol (TCP) connection through the firewall.

22. The non-transitory computer readable medium of claim 16 wherein the remote device is configured to automatically generate the connection request in response to detecting network connectivity.