Internet listener/publisher

• US 7,146,420 B2
• Filed: 11/20/2003
• Issued: 12/05/2006
• Est. Priority Date: 11/20/2003
• Status: Active Grant

• Current Assignee: Square D Company (Schneider Electric SE)
• Original Assignee: Square D Company (Schneider Electric SE)
• Inventors: Pyle, Michael W., Dahlman, Roger A.
• Primary Examiner(s): Jean, Frantz B.
• Application Number:
  US10/717,750
• Publication Number:
  US 20050114509A1
• Time in Patent Office: 1,111 Days
• Field of Search: 709/224, 709/225, 709/226, 715/505.1, 719/328, 719/331
• US Class Current: 709/225
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A communication scheme which allows Internet access to selected services behind a corporate firewall on a corporate Intranet with a publisher on the Intranet in communication with the Intranet web services and a listener on the Internet and is responsive to select requests from an Internet user which are embedded in responses received from the listener responding to queries from the publisher.

Claims

1. A communication system responsive to internet user access requests to an intranet-based web server across a firewall, comprising:

a listener on said internet side of said firewall responsive to said access requests from said internet user, and

a publisher on said intranet side of said firewall having access to said web server, maintaining a communication link with said listener, wherein said listener embeds said access requests within responses to communication requests from said publisher.

2. A communication system as recited in claim 1, wherein said publisher maintains an open hypertext transfer protocol (HTTP) or HTTP layer over the secure socket layer (HTTPS) connection with said listener.

3. A communication system as recited in claim 1, wherein said listener maintains an HTTP or HTTP layered over the secure socket layer (HTTPS) Internet connection.

4. A communication system as recited in claim 1, wherein said listener embeds requests of its own within responses to communication requests from said publisher.

5. The communication system of claim 1, wherein said publisher allows outbound traffic only.

6. A method of communicating intranet services access requests from an internet user across a fire wall to an intranet-based web service, including:

maintaining a communication link between an intranet publisher and said web server;

maintaining a communication link between an internet listener and said internet user;

maintaining a communication link between said publisher and said listener; and

embedding, by said internet listener, said internet user access requests within responses to communication requests from said publisher.

7. The communication method of claim 6 using an HTTP or HTTP layered over the secure socket layer (HTTPS) connection between said publisher and said listener.

8. The communication method of claim 6 in which said listener maintains an HTTP or HTTPS internet connection.

9. The method of claim 6, wherein said intranet publisher allows outbound traffic only.

10. A method of communicating intranet services access requests from a requesting internet user, across a firewall, to an intranet-based service, including:

receiving communication requests from the intranet side of a firewall;

receiving said access request from said internet user on the internet side of said firewall;

encapsulating, on the internet side of said firewall, said access request in a response message;

sending said response message in response to said communication request from the internet side across said firewall to the intranet side;

forwarding said response message to an intranet-based web service;

forwarding outward bound intranet-based web service responses across a firewall; and

forwarding said intranet-based web service responses to said requesting internet user.

11. The communication method of claim 10 and further, wherein said access request is assigned a transaction ID.

12. The communication method of claim 10 and further, wherein said web service response is forwarded to said internet user based on said transaction ID.

13. The communication method of claim 10 and further, wherein said access request fails if said communication request has not been received within a timeout period.

14. The communication method of claim 10 and further, wherein said communication request is an HTTP wait request.

15. The communication method of claim 10 and further, wherein said access request is over an HTTP or HTTPS connection.

16. The communication method of claim 10 and further, wherein said communication request is over an HTTP connection.

17. The method of claim 10, further comprising disallowing, on the intranet side of said firewall, inbound access requests from said internet user.