Packet redirection and message stream management

• US 6,850,484 B1
• Filed: 07/20/1998
• Issued: 02/01/2005
• Est. Priority Date: 08/21/1997
• Status: Expired due to Fees

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Greenspan, Steven Lloyd, Janow, Richard H.
• Primary Examiner(s): HSU, ALPUS
• Application Number:
  US09/485,051
• Time in Patent Office: 2,388 Days
• Field of Search: 370/218, 370/229, 370/230, 370/231, 370/235, 370/236, 370/352, 370/389, 370/400, 370/401, 370/428, 379/88, 379/17, 379/93.01, 379/93.07, 379/100.08, 379/100.12, 709/201, 709/203, 709/223, 709/224, 709/231, 709/238, 709/249
• US Class Current: 370/218
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A stream manager provides a way of redirecting and managing messaging and information access in a packet network environment. The stream manager can include a computer-based router or server that behaves as if it were a gateway for a sub-network of destination site servers, and 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, and initiates the routing of the message to the selected destination server. If a destination site is unavailable, the stream manager may report that to the host server, along with other information (such as customer care or promotional information).

Claims

1. A method of operating a stream manager in a packet network environment, comprising the steps of:

a. receiving over the packet network at the stream manager a message initiated by a user, said message included in a DNS-originated packet comprising a first address for the stream manager and a second address for a destination site;

b. determining the availability of a plurality of destination servers at the destination site to receive and process the message; and

c. if at least two of the plurality of destination servers at the destination site are available to receive and process the message;

i selecting a destination server from the at least two available destination servers; and

ii initiating the routing of the message to the selected destination server.

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

3. The method according to claim 2, 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.

4. The method according to claim 3, wherein the address for the selected destination server is determined in accordance with the an identifier corresponding to the destination site.

5. The method according to claim 4, further comprising the step of determining the identifier corresponding to the destination site.

6. The method according to claim 5, wherein the step of determining the identifier corresponding to the destination site comprises extracting an address for the destination site from the packet header of a packet containing at least part of the message.

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

8. The method according to claim 2, 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.

9. The method according to claim 8, wherein the address for the selected destination server is determined in accordance with the an identifier corresponding to the destination site.

10. The method according to claim 9, further comprising the step of determining the identifier corresponding to the destination site.

11. The method according to claim 10, wherein the step of determining the identifier corresponding to the destination site comprises extracting an address for the destination site from the packet header of a packet containing at least part of the message.

12. 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.

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

14. The method according to claim 13, further comprising the step of receiving at the stream manager information about congestion at the destination site, said congestion information including a measure of the message traffic load relative to the available capacity for each available destination server.

15. The method according to claim 14, wherein the step of receiving information about congestion at the destination site comprises receiving data over an established communications link with the destination site, said communications link excluding the packet network.

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

17. The method according to claim 1, further comprising the step of directing replies from the destination site to the user through the stream manager to measure service quality relating to the destination site.

18. The method according to claim 1, wherein the stream manager'"'"'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 a message initiated by the user.

19. The method according to claim 1, further comprising the step of rerouting reply messages from the destination server intended for the user to a front-end mailbox associated with the user.

20. The method according to claim 1, wherein the stream manager comprises a gateway coupled to a plurality of stream manager servers through an internal network.

21. The method according to claim 20, further comprising the step of determining one stream manager server from the plurality of stream manager servers to handle the message.

22. The method according to claim 1, further comprising the step of if no destination server is available, sending information to the user reporting the fact of unavailability.

23. The method according to claim 22, wherein the information sent to the user includes information of a promotional nature.

24. The method according to claim 22, wherein the information sent to the user includes customer care information.

25. A method of operating a stream manager in an environment having a plurality of packet networks, comprising the steps of:

a. receiving at the stream manager, over one of the plurality of packet networks, a message initiated by a user, said message included in a DNS-originated packet comprising a first address for the stream manager and a second address for a destination site;

b. determining the availability of a plurality of destination servers at the destination site to receive and process the message;

c. if at least two of the plurality of destination servers are available;

i selecting a destination server from the at least two available destination servers;

ii determining from the plurality of packet networks a packet network over which the message should be routed to the destination server; and

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

26. The method according to claim 25, wherein the step of selecting a destination server includes determining which one of the plurality of destination servers has the lowest message traffic load relative to that servers available capacity.

27. The method according to claim 26, further comprising the step of receiving at the stream manager information about congestion at the destination site, said congestion information including a measure of the message traffic load relative to the available capacity for each available destination server.

28. The method according to claim 27, wherein the step of receiving information about congestion at the destination site comprises receiving data over an established communications link with the destination site, said communications link excluding the determined packet network.

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

30. The method according to claim 25, further comprising the step of directing replies from the destination site to the user through the stream manager to measure service quality relating to the destination site.

31. The method according to claim 25, wherein the stream manager'"'"'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 a message initiated by the user.

32. The method according to claim 25, further comprising the step of rerouting reply messages from the destination server intended for the user to a front-end mailbox associated with the user.

33. The method according to claim 25, wherein the stream manager comprises a gateway coupled to a plurality of stream manager servers through an internal network.

34. The method according to claim 33, further comprising the step of determining one stream manager server from the plurality of stream manager servers to handle the message.

35. The method according to claim 25, further comprising the step of if no destination server is available, sending information to the user reporting the fact of unavailability.

36. The method according to claim 35, wherein the information sent to the user includes information of a promotional nature.

37. The method according to claim 35, wherein the information sent to the user includes customer care information.

38. A stream manager that operates in a packet network environment, comprising:

a. a communications interface compatible with the packet network; and

b. a processor, wherein said processor is programmed to execute the steps of;

i receiving at the stream manager, over the packet network, a message initiated by a user, said message included in a DNS-originated packet comprising a first address for the stream manager and a second address for a destination site;

ii determining the availability of a plurality of destination servers at the destination site to receive and process the message; and

iii if at least two of the plurality of destination servers at the destination site is available to receive and process the message;

(a) selecting a destination server from the at least two available destination servers; and

(b) initiating the routing of the message to the selected destination server.

39. The method according to claim 38, wherein the step of initiating the routing of the message to the selected destination server comprises changing the second address.

40. The stream manager according to claim 39, wherein the processor-executable 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.

41. The stream manager according to claim 40, wherein the address for the selected destination server is determined in accordance with the an identifier corresponding to the destination site.

42. The stream manager according to claim 41, wherein the processor is further programmed to execute the step of determining the identifier corresponding to the destination site.

43. The stream manager according to claim 42, wherein the processor-executable step of determining the identifier corresponding to the destination site comprises extracting an address for the destination site from the packet header of a packet containing at least part of the message.

44. The stream manager according to claim 39, wherein the processor-executable step of initiating the routing of the message to the selected destination server comprises routing the message through a network other than the packet network to the selected destination server.

45. The stream manager according to claim 39, wherein the processor-executable 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.

46. The stream manager according to claim 45, Wherein the address for the selected destination server is determined in accordance with an identifier corresponding to the destination site.

47. The stream manager according to claim 46, wherein the processor is further programmed to execute the step of determining the identifier corresponding to the destination site.

48. The stream manager according to claim 47, wherein the processor-executable step of determining the identifier corresponding to the destination site comprises extracting an address for the destination site from the packet header of a packet containing at least part of the message.

49. The stream manager according to claim 38, wherein the processor-executable 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.

50. The stream manager according to claim 38, wherein the processor-executable step of selecting a destination server includes determining which one of the plurality of destination servers has the lowest message traffic load relative to that server'"'"'s available capacity.

51. The stream manager according to claim 50, wherein the processor is further programmed to execute the step of receiving at the stream manager information about congestion at the destination site, said congestion information including a measure of the message traffic load relative to the available capacity for each available destination server.

52. The stream manager according to claim 51, wherein the processor-executable step of receiving information about congestion at the destination site comprises receiving data over an established communications link with the destination site, said communications link excluding the packet network.

53. The stream manager according to claim 38, wherein the processor-executable step of selecting a destination server includes determining which one of the plurality of destination servers is appropriate for handling the message from the user based upon information about the user.

54. The stream manager according to claim 38, wherein the processor is further programmed to execute the step of directing replies from the destination site to the user through the stream manager to measure service quality relating to the destination site.

55. The stream manager according to claim 38, wherein the stream managers 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 a message initiated by the user.

56. The stream manager according to claim 38, wherein the processor is further programmed to execute the step of rerouting reply messages from the destination server intended for the user to a front-end mailbox associated with the user.

57. The stream manager according to claim 38, wherein the processor is further programmed to execute the step of sending information to the user reporting the fact of unavailability if no destination server is available.

58. The stream manager according to claim 57, wherein the information sent to the user includes information of a promotional nature.

59. The stream manager according to claim 57, wherein the information sent to the user includes customer care information.

60. A stream manager that operates in an environment having a plurality of packet networks, comprising:

a. a communications interface compatible with the packet network; and

b. a processor, wherein said processor is programmed to execute the steps of;

i receiving at the stream manager, over one of the plurality of packet networks, a message initiated by a user, said message included in a DNS-originated packet comprising a first address for the stream manager and a second address for a destination site;

ii determining the availability of a plurality of destination servers at the destination site to receive and process the message; and

iii if at least two of the plurality of destination servers are available;

(a) selecting a destination server from the at least two available destination servers;

(b) determining from the plurality of packet networks a packet network over which the message should be routed to the destination server; and

(c) routing the message to the selected destination server over the determined packet network.

61. The stream manager according to claim 60, wherein the processor-executable step of selecting a destination server includes determining which one of the plurality of destination servers has the lowest message traffic load relative to that server'"'"'s available capacity.

62. The stream manager according to claim 61, wherein the processor is further programmed to execute the step of receiving at the stream manager information about congestion at the destination site, said congestion information including a measure of the message traffic load relative to the available capacity for each available destination server.

63. The stream manager according to claim 62, wherein the processor-executable step of receiving information about congestion at the destination site comprises receiving data over an established communications link with the destination site, said communications link excluding the determined packet network.

64. The stream manager according to claim 60, wherein the processor-executable step of selecting a destination server includes determining which one of the plurality of destination servers is appropriate for handling the message from the user based upon information about the user.

65. The stream manager according to claim 60, wherein the processor is further programmed to execute the step of directing replies from the destination site to the user through the stream manager to measure service quality relating to the destination site.

66. The stream manager according to claim 60, wherein the stream manager'"'"'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 a message initiated by the user.

67. The stream manager according to claim 60, wherein the processor is further programmed to execute the step of rerouting reply messages from the destination server intended for the user to a front-end mailbox associated with the user.

68. The stream manager according to claim 60, wherein the processor is further programmed to execute the step of sending information to the user reporting the fact of unavailability if no destination server is available.

69. The stream manager according to claim 68, wherein the information sent to the user includes information of a promotional nature.

70. The stream manager according to claim 68, wherein the information sent to the user includes customer care information.

71. A stream manager that operates in a packet network environment, comprising:

a. a communications interface compatible with the packet network;

b. a network internal to the stream manager;

c. a plurality of stream manager servers coupled to the internal network; and

d. a gateway coupled to the internal network, said gateway comprising a processor programmed to execute the steps of;

i receiving at the stream manager, over the packet network, a message initiated by a user, said message included in a DNS-originated packet comprising a first address for the stream manager and a second address for a destination site;

ii selecting one server from the plurality of stream manager servers to handle the message; and

iii forwarding the message to the selected stream manager server.

72. The stream manager according to claim 71, wherein the selected server comprises:

a. a communications interface compatible with the packet network; and

b. a processor programmed to execute the steps of;

i determining the availability of at least one destination server at the destination site to receive and process the message; and

ii if at least one destination server at the destination site is available to receive and process the message;

(a). selecting a destination server from the at least one available destination server; and

(b). initiating the routing of the message to the selected destination server.

73. A stream manager that operates in an environment having a plurality of packet networks, comprising:

a. a communications interface compatible with a least one of the plurality of packet networks;

b. a network internal to the stream manager;

c. a plurality of stream manager servers coupled to the internal network; and

d. a gateway coupled to the internal network, said gateway comprising a processor programmed to execute the steps of;

i receiving, at the stream manager, over one of the plurality of packet networks, a message initiated by a user, said message included in a DNS-originated packet comprising a first address for the stream manager and a second address for a destination site;

ii selecting one server from the plurality of stream manager servers to handle the message; and

iii forwarding the message to the selected stream manager server.

74. The stream manager according to claim 73, wherein the selected server comprises:

a. a communications interface compatible with at least one of the plurality of packet networks; and

b. a processor programmed to execute the steps of;

i determining the availability of at least one destination server at the destination site to receive and process the message; and

ii if at least one destination server at the destination site is available to receive and process the message;

(a) selecting a destination server from the at least one available destination server; and

(b) determining from the plurality of packet networks a packet network over which the message should be routed to the destination server; and

(c) routing the message to the selected destination server over the determined packet network.