Packet redirection and message stream management

• US 20050195836A1
• Filed: 09/30/2004
• Published: 09/08/2005
• Est. Priority Date: 01/31/2000
• Status: Active Grant

• Current Assignee: Richard H. Janow, Steven Lloyd Greenspan
• Original Assignee: Richard H. Janow, Steven Lloyd Greenspan
• Inventors: Greenspan, Steven Lloyd, Janow, Richard H.
• Granted Patent: US 7,508,753 B2
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 45/125 based on throughput or bandwidth
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer

Abstract

A stream manager provides a way of redirecting and managing messaging and information access in a packet network environment. The stream manager is linked to a packet network, such as the Internet. The stream manager receives over the packet network a message from a user'"'"'s host server initiated by a user and intended for a destination site. The message bears an address for the stream manager which is provided to the host server by the address server for the packet network, such as a server utilized as part of the domain name system. The stream manager determines the availability of at least one destination server at the destination site to receive and process the message. If a destination server at the destination site is available to receive and process the message, the stream manager selects a destination server from those available.

Claims

1. A method comprising the steps of:

at a gateway in a packet network, selecting a destination server from at least two destination servers available to receive and process a message initiated by a user, the message comprising a DNS-supplied gateway address and an identifier for a destination site; and

initiating routing of the message to the selected destination server.

2. The method according to claim 1, further comprising:

receiving at the gateway, information about congestion at the destination site, the information about congestion including a measure of message traffic load relative to available capacity for each available destination server.

3. The method according to claim 1, further comprising:

receiving at the gateway, information about congestion at the destination site, the information about congestion transmitted over a communications link with the destination site, the communications link excluding the packet network.

4. The method according to claim 1, further comprising:

directing replies from the destination site to the user through the gateway to measure,service quality relating to the destination site.

5. The method according to claim 1, further comprising:

if no destination server is available, reporting information indicative of unavailability to the user.

6. The method according to claim 1, further comprising:

if no destination server is available, informing the user that requested information will be e-mailed.

7. The method according to claim 1, further comprising:

sending promotional information to the user.

8. The method according to claim 1, further comprising:

sending customer care information to the user.

9. The method according to claim 1, further comprising:

rerouting reply messages intended for the user from the destination server to a front-end mailbox associated with the user.

10. The method according to claim 1, further comprising:

selecting the gateway from a plurality of gateways.

11. The method according to claim 1, further comprising:

selecting, from a plurality of packet networks, a transmission packet network for transmitting the message.

12. The method according to claim 1, further comprising:

routing the message to the selected destination server over a determined packet network.

13. The method according to claim 1, wherein the message comprises information that originates from a Plain Old Telephone Service.

14. The method according to claim 1, wherein the message comprises information that originates from a video camera.

15. The method according to claim 1, wherein the message comprises information that originates from a database.

16. The method according to claim 1, wherein the message comprises multimedia information.

17. The method according to claim 1, wherein the identifier is an IP address.

18. The method according to claim 1, wherein the identifier is a URL.

19. The method according to claim 1, wherein the message is routed via a private network.

20. The method according to claim 1, wherein the step of initiating routing of the message to the selected destination server comprises changing the identifier.

21. The method according to claim 1, wherein the step of initiating the routing of the message to the selected destination server comprises routing the message through the packet network to an address for the selected destination server.

22. The method according to claim 1, wherein the step of initiating routing of the message to the selected destination server comprises routing the message through a network other than the packet network.

23. The method according to claim 1, wherein the step of initiating the routing of the message to the selected destination server comprises returning an address for the selected destination server to a host server associated with the user for use in sending messages from the user to the selected destination server.

24. The method according to claim 1, wherein the step of selecting a destination server includes determining which one of the at least two destination servers has a lowest message traffic load relative to that server'"'"'s available capacity.

25. The method according to claim 1, wherein the step of selecting a destination server includes determining which one of the at least two destination servers is appropriate for handling the message based upon information about the user.

26. The method according to claim 1, wherein the gateway'"'"'s interaction with any messages to which the user and the destination site are parties is controlled by the destination site after the selected destination server has been successfully reached with the message.

27. The method according to claim 1, wherein the gateway is coupled to a plurality of gateways through an internal network.

28. The method according to claim 1, wherein the packet network is one of a plurality of packet networks.

29. A gateway comprising:

a communications interface compatible with a packet network; and

a processor adapted to;

select a destination server from at least two destination servers available to receive and process a message initiated by a user, the message comprising a DNS-supplied gateway address and an identifier for a destination site; and

initiate the routing of the message to the selected destination server.

30. A machine readable medium comprising instructions adapted to:

at a gateway in a packet network, selecting a destination server from at least two destination servers available to receive and process a message initiated by a user, the message comprising a DNS-supplied gateway address and an identifier for a destination site; and

initiating routing of the message to the selected destination server.