Communication system

• US 20040133631A1
• Filed: 01/06/2003
• Published: 07/08/2004
• Est. Priority Date: 01/06/2003
• Status: Abandoned Application

• Current Assignee: Gatelinx Corporation
• Original Assignee: Gatelinx Corporation
• Inventors: Stefanik, Rick, Hagen, David A.
• Application Number:
  US10/337,155
• Publication Number:
  US 20040133631A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A communication system and method that provides efficient, global load balancing and enables data transfer over the internet without being blocked by firewalls an proxies. The system includes a plurality of remote portals that place requests and receive responses. A request is sent to a plurality of gateway servers. The first gateway server to respond, considering any performance delays, is selected to process the request. The request is then passed to a plurality of routers. The first router to respond, considering any performance delays, processes the request and converts it into a response. The response is sent back to the gateway server and then to the portal. Data is transferred between the portals using a transport module which is a client interface that establishes connections between portals, a transport channel that is an application interface that transmits timely data, and proxy that assists the transport module in bypassing firewalls.

Claims

1. A communication system comprising:

a plurality of remote portals on a network that are adapted to generate requests and receive responses; and

a plurality of gateway servers on the network that are adapted to accept requests from the plurality of portals;

wherein when a portal request is transmitted from a portal in the plurality of remote portals to the plurality of gateway servers, a performance level of each gateway server in the plurality of gateway servers is ascertained;

wherein the time it takes for a gateway server to respond to the portal request is delayed as the performance level of the gateway server degrades;

wherein any response delay of a gateway server is decreased as its performance level improves;

wherein each gateway server rejects requests if its performance level has reached a predetermined minimum;

wherein the first gateway server in the plurality of gateway servers that responds the portal request, considering any performance delays, is selected to process the portal request; and

wherein a connection is established between the requesting portal and the gateway server that is selected to process the request.

2. The system of claim 1 wherein the remote portals are selected from the group consisting of stationary kiosks, portable kiosks, desktop computers, laptops, handheld computers, set-top boxes, and personal digital assistants.

3. The system of claim 1 further comprising a plugin manager comprising at least one filter that filters the portal request before the request is processed by the selected gateway server.

4. The system of claim 1 further comprising a plurality of routing sites on the network comprising a plurality routers for processing the portal request, wherein the gateway server that is selected to process the portal request determines which routing site the request indicates should process it and transmits the portal request to the plurality of routers in that routing site.

5. The system of claim 4 wherein the selected gateway server requests an updated list of routing sites and corresponding routers in predetermined intervals.

6. The system of claim 4 wherein each router in the plurality of routers retrieves a list of blocked IP addresses for each portal request type so that when a router receives subsequent requests from a gateway server, the router can ascertain the IP address of the requesting portal and deny the request if the IP address is blocked.

7. The system of claim 4 wherein:

a performance level of each router in the selected routing site is ascertained;

the time it takes for a router to respond to the portal request is delayed as the performance level of the router degrades;

any response delay of a router is decreased as its performance level improves;

each router rejects requests if its performance level has reached a predetermined minimum; and

the first router in the plurality of routers that responds the portal request, considering any performance delays, is selected to process the portal request as the primary router.

8. The system of claim 7 wherein the primary router receives connection attempts from the plurality of routing sites until the primary router becomes overloaded with requests.

9. The system of claim 8 wherein when the primary router becomes overloaded with portal requests, the primary router is configured to refuse additional portal requests and a new primary router is selected to process the portal requests.

10. The system of claim 7 wherein the primary router processes the portal request as a series of jobs.

11. The system of claim 10 wherein the jobs are selected from the group consisting of handlers, servers, databases, and web servers.

12. The system of claim 10 wherein job plugins are developed to process the jobs.

13. The system of claim 7 wherein after processing the portal request, the primary router changes the request into a response that is transmitted back to the selected gateway server.

14. The system of claim 13 wherein the selected gateway server transmits the response to the requesting portal and the requesting portal then closes the connection.

15. The system of claim 14 wherein the selected gateway server receives a list of other nearby gateway servers on the network and a predetermined number of the nearby gateway servers on the list is transmitted to the requesting portal with the response.

16. The system of claim 15 wherein in predetermined intervals, the selected gateway server tests its connection time to a plurality of other gateway servers on the network and the connection times are used to generate the list of nearby gateway servers that is transmitted to the requesting portal.

17. The system of claim 1 further comprising a bulk insert library that stores a portal request'"'"'s source and destination information.

18. A method for providing efficient load balancing in a network comprising the steps of:

generating a portal request from a remote portal on a network;

transmitting said portal request to a plurality of gateway servers on the network;

ascertaining a performance level of each gateway server in the plurality of gateway servers that receive said portal request;

delaying the response time of a gateway server as its performance level degrades;

decreasing any response delay of a gateway server as its performance level improves;

rejecting requests to a gateway server if its performance level has reached a predetermined minimum;

selecting the gateway server that first responds to the portal request, considering any performance delays, to process the portal request; and

establishing a connection between the requesting portal and the gateway server that is selected to process the portal request.

19. The method of claim 18 further comprising the step of transmitting the portal request from the selected gateway server to a plurality of routers on the network.

20. The method of claim 19 further comprising the steps of:

ascertaining a performance level of each router in the plurality of routers that receive the portal request;

delaying the response time of a router as its performance level degrades;

decreasing any response delay of a router as its performance level improves;

rejecting requests to a router if its performance level has reached a predetermined minimum;

selecting the router that first responds to the portal request, considering any performance delays, to process the portal request as a primary router; and

transmitting the portal request to the primary router.

21. The method of claim 20 further comprising the step of the primary router processing the portal request as a series of jobs.

22. The method of claim 20 further comprising the steps of the router:

processing the portal request and changing the request into a response; and

transmitting the response back to the selected gateway server.

23. The method of claim 22 further comprising the steps of:

the selected gateway server testing its connection time to a plurality of other gateway servers on the network; and

utilizing the connection times to generate an updated list of nearby gateway servers to the requesting portal;

transmitting the updated list of nearby gateway servers to the requesting portal with the response.

24. A managed data transport system for transporting data between portals on a managed portal network comprising:

a transport module that establishes connections between at least two portals and coordinates data transfer over multiple channels;

a transport channel that transmits the data and ensures that the data is timely transmitted; and

a proxy that assists the transport module in bypassing firewalls when transmitting the data.

25. The system of claim 24 wherein the transport module utilizes only outbound connections to the proxy to simulate HTTP traffic.

26. The system of claim 24 wherein the proxy matches incoming connections from the transport modules of the at least two portals so that the data can be transmitted between the portals.

27. The system of claim 26 wherein a connection is established between the at least two portals by attempting to connect the at least two portals both peer-to-peer and through the proxy.

28. The system of claim 27 wherein if the peer-to-peer connection is successful, any proxy connection is dropped in favor of the peer-to-peer connection.

29. The system of claim 24 further comprising a proprietary transport port that is used for attempting connections between the at least two portals.

30. The system of claim 29 wherein when the proprietary port is blocked, a connection is attempted using an HTTP port.

31. The system of claim 30 wherein when the HTTP port is used, the data is wrapped with HTTP headers to simulate standard HTTP traffic and avoid firewalls.

32. The system of claim 24 wherein once a connection is established between the at least two portals, two socket connections to the same IP address are created and maintained such that one connection is assigned to incoming data and the other connection is assigned to outgoing data.

33. The system of claim 24 wherein data is sent over the transport channel using send data, which is data that is guaranteed to be transmitted, and/or stream data, which is data that is dropped in favor of more recently transmitted data.

34. The system of claim 33 wherein the stream data is stamped with a time-to-live (TTL) setting that sets a time limit on when the stream data expires and the send data is stamped with a TTL setting of zero indicating that send data never expires.

35. The system of claim 33 wherein send data and stream data are queued in the transport module until the transport module is ready to send the data.

36. The system of claim 35 wherein the transport module monitors a total available bandwidth of the multiple channels and maximizes usage of the bandwidth if all of the channels are not using their share.

37. The system of claim 36 wherein the multiple channels take turns inserting data into the transport module according to their bandwidth allotment.

38. The system of claim 35 wherein the transport module:

checks the TTL settings to determine whether the data is still valid for transmission;

transmits the data if the data is still valid; and

discards the data if the data has expired.

39. The system of claim 24 wherein in predetermined intervals, the data from the multiple channels is combined to create a single data packet that is compressed and transmitted.

40. The system of claim 39 wherein the single data packet is encrypted before it is transmitted.

41. The system of claim 39 wherein when an HTTP port is used to transmit the single data packet, the single data packet is sent as binary encoded data but fails over to text encoded data if necessary.

42. The system of claim 39 wherein when an HTTP port is used to transmit the single data packet, the data packet is wrapped with HTTP headers to simulate standard HTTP traffic and avoid firewalls.

43. The system of claim 39 wherein when the transport module receives data:

any HTTP headers are stripped, any encrypted data is decrypted, and any compressed data is decompressed;

the data from the multiple channels is sent to the respective destination channels;

each destination channel reassembles its partial data into the original data packet; and

the data is returned to an application using that channel.

44. The system of claim 24 wherein the transport module continually transmits data between connected portals so the transport module can identify failed connections and attempt to repair failed connections.

45. The system of claim 24 wherein:

the transport module attempts to connect to a plurality of target applications on the managed transport system;

the time it takes for a target application to respond to the transport module may be delayed; and

a connection is established between the transport module and the first target application to respond to the transport module, considering any delays.

46. The system of claim 24 wherein:

the transport module attempts to connect to a plurality of target applications ranked in order of priority;

the time it takes for a target application to respond to the transport module may be delayed;

a connection is established between the transport module and the highest ranked target application that responds to the transport module within a predetermined time, considering any delays.