Content router gateway

• US 20070038703A1
• Filed: 07/14/2005
• Published: 02/15/2007
• Est. Priority Date: 07/14/2005
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Srinivasan, Venkatachary, Tendjoukian, Meher
• Application Number:
  US11/183,073
• Publication Number:
  US 20070038703A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

A gateway is provided which includes an interface to a command memory of a content routing server, interfaces to different types of content nodes, protocol translators to transform communications between the command memory of the content routing server and the interfaces to the content nodes. The gateway may interface to content nodes that are servers or to content nodes that are client. The gateway provides a common interface to the command memory of the content routing server for coupling content and metadata to content nodes operating disparate protocols.

Claims

1. A server gateway for routing changes to information between a plurality of user accounts and a command memory of a content routing server, the server gateway comprising:

a first protocol translator for;

modeling a client of a first user account server, wherein the first user account server includes a first user account;

routing commands between the first user account server and the command memory of the content routing server; and

transforming the commands between a first server protocol and a common protocol, wherein the first server protocol is used to communicate with the first user account server, and wherein the common protocol is used to communicate to the command memory of the content routing server; and

a second protocol translator for;

modeling a client of a second user account server, wherein the second user account server includes a second user account;

routing commands between the second user account server and the command memory of the content routing server; and

transforming the commands between a second server protocol and the common protocol, wherein the second server protocol is used to communicate with the second user account server, and wherein the second server protocol differs from the first server protocol.

2. The server gateway of claim 1, wherein the common protocol includes a remote procedure calling (RPC) protocol.

3. The server gateway of claim 2, wherein the RPC protocol includes an XML-RPC protocol.

4. The server gateway of claim 1, wherein the common protocol includes a Remote Method Invocation (RMI) protocol.

5. The server gateway of claim 4, wherein the RMI protocol includes a Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP).

6. The server gateway of claim 1, wherein the first user account server is operable to communicate content of a first content type and the second user account server is operable to communicate content of a second content type different than the first content type.

7. The server gateway of claim 6, wherein the first content type includes an email content type and the second content type includes a PIM content type.

8. The server gateway of claim 6, wherein the first content type includes an email content type and the second content type includes a media content type.

9. The server gateway of claim 6, wherein the first content type includes an email content type and the second content type includes a contacts content type.

10. The server gateway of claim 1, further comprising a plurality of protocol translators for transforming commands between a correspond one of a plurality of different server protocols and the common protocol, wherein each of the plurality of protocol translators models a client of a corresponding user account server and models a client of the command memory of the content routing server.

11. The server gateway of claim 1, wherein the first user account server further includes a plurality of first user accounts.

12. The server gateway of claim 11, wherein the second user account server further includes a plurality of second user accounts.

13. The server gateway of claim 1, further comprising:

memory for holding outgoing commands received from the command memory of the content routing server and destined for the first user account; and

processing logic, coupled to the memory, for selecting a non-FIFO order for sending the outgoing commands to the first user account.

14. The server gateway of claim 13, wherein selecting the non-FIFO order includes selecting an outgoing command based on content of the outgoing command.

15. The server gateway of claim 13, wherein selecting the non-FIFO order includes selecting an outgoing command based on a content type of the outgoing command.

16. The server gateway of claim 13, wherein selecting the non-FIFO order includes selecting an outgoing command to add content before selecting an outgoing command to modify content.

17. The server gateway of claim 16, wherein the outgoing command to add content includes an outgoing command to add an email message, and wherein the outgoing command to modify content includes a modification to a state of an existing email message.

18. The server gateway of claim 13, wherein selecting the non-FIFO order includes selecting an outgoing command to add a second email message before selecting an outgoing command to add a first email message, wherein a date and time of the first email message indicates generation before a date and time of the second email message.

19. The server gateway of claim 13, wherein selecting the non-FIFO order includes selecting a plurality of outgoing commands to add recent email messages before selecting an outgoing command to add an older email message.

20. The server gateway of claim 1, further including the content routing server.

111. The computer program product of claim 10, wherein the second user device further includes a plurality of second devices.

116. The computer program product of claim 115, wherein the outgoing command to add content includes an outgoing command to add an email message, and wherein the outgoing command to modify content includes a modification to a state of an existing email message.

21. A method for routing changes to information between a plurality of user accounts and a command memory of a content routing server, the method comprising, at a server gateway:

modeling a client of a first user account server, wherein the first user account server includes a first user account;

routing commands between the first user account server and the command memory of the content routing server;

transforming the commands between a first server protocol and a common protocol, wherein the first server protocol is used to communicate with the first user account server, and wherein the common protocol is used to communicate to the command memory of the content routing server; and

modeling a client of a second user account server, wherein the second user account server includes a second user account;

routing commands between the second user account server and the command memory of the content routing server; and

transforming the commands between a second server protocol and the common protocol, wherein the second server protocol is used to communicate with the second user account server, and wherein the second server protocol differs from the first server protocol.

22. The method of claim 21, wherein the common protocol includes a remote procedure calling (RPC) protocol.

23. The method of claim 22, wherein the RPC protocol includes an XML-RPC protocol.

24. The method of claim 21, wherein the common protocol includes a Remote Method Invocation (RMI) protocol.

25. The method of claim 24, wherein the RMI protocol includes a Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP).

26. The method of claim 21, wherein the first user account server is operable to communicate content of a first content type and the second user account server is operable to communicate content of a second content type different than the first content type.

27. The method of claim 26, wherein the first content type includes an email content type and the second content type includes a PIM content type.

28. The method of claim 26, wherein the first content type includes an email content type and the second content type includes a media content type.

29. The method of claim 26, wherein the first content type includes an email content type and the second content type includes a contacts content type.

30. The method of claim 21, further comprising transforming commands between a correspond one of a plurality of different server protocols and the common protocol, wherein each of the plurality of protocol translators models a client of a corresponding user account server and models a client of the command memory of the content routing server.

31. The method of claim 21, wherein the first user account server further includes a plurality of first user accounts.

32. The method of claim 31, wherein the second user account server further includes a plurality of second user accounts.

33. The method of claim 21, further comprising:

saving to memory outgoing commands received from the command memory of the content routing server and destined for the first user account; and

selecting a non-FIFO order for sending the outgoing commands to the first user account.

34. The method of claim 33, wherein selecting the non-FIFO order includes selecting an outgoing command based on content of the outgoing command.

35. The method of claim 33, wherein selecting the non-FIFO order includes selecting an outgoing command based on a content type of the outgoing command.

36. The method of claim 33, wherein selecting the non-FIFO order includes selecting an outgoing command to add content before selecting an outgoing command to modify content.

37. The method of claim 36, wherein the outgoing command to add content includes an outgoing command to add an email message, and wherein the outgoing command to modify content includes a modification to a state of an existing email message.

38. The method of claim 33, wherein selecting the non-FIFO order includes selecting an outgoing command to add a second email message before selecting an outgoing command to add a first email message, wherein a date and time of the first email message indicates generation before a date and time of the second email message.

39. The method of claim 31, wherein selecting the non-FIFO order includes selecting a plurality of outgoing commands to add recent email messages before selecting an outgoing command to add an older email message.

40. A computer program product comprising program code for use in a server gateway including processing logic for communicating commands between a command memory of a content routing server and user accounts, the computer program product comprising:

program code for modeling a client of a first user account server, wherein the first user account server includes a first user account;

program code for routing commands between the first user account server and the command memory of the content routing server;

program code for transforming the commands between a first server protocol and a common protocol, wherein the first server protocol is used to communicate with the first user account server, and wherein the common protocol is used to communicate to the command memory of the content routing server; and

program code for modeling a client of a second user account server, wherein the second user account server includes a second user account;

program code for routing commands between the second user account server and the command memory of the content routing server; and

program code for transforming the commands between a second server protocol and the common protocol, wherein the second server protocol is used to communicate with the second user account server, and wherein the second server protocol differs from the first server protocol.

41. The computer program product of claim 40, wherein the common protocol includes a remote procedure calling (RPC) protocol.

42. The computer program product of claim 41, wherein the RPC protocol includes an XML-RPC protocol.

43. The computer program product of claim 40, wherein the common protocol includes a Remote Method Invocation (RMI) protocol.

44. The computer program product of claim 43, wherein the RMI protocol includes a Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP).

45. The computer program product of claim 40, wherein the first user account server is operable to communicate content of a first content type and the second user account server is operable to communicate content of a second content type different than the first content type.

46. The computer program product of claim 45, wherein the first content type includes an email content type and the second content type includes a PIM content type.

47. The computer program product of claim 45, wherein the first content type includes an email content type and the second content type includes a media content type.

48. The computer program product of claim 45, wherein the first content type includes an email content type and the second content type includes a contacts content type.

49. The computer program product of claim 40, further comprising program code for transforming commands between a correspond one of a plurality of different server protocols and the common protocol, wherein each of the plurality of protocol translators models a client of a corresponding user account server and models a client of the command memory of the content routing server.

50. The computer program product of claim 40, wherein the first user account server further includes a plurality of first user accounts.

51. The computer program product of claim 50, wherein the second user account server further includes a plurality of second user accounts.

52. The computer program product of claim 40, further comprising:

program code for saving to memory outgoing commands received from the command memory of the content routing server and destined for the first user account; and

program code for selecting a non-FIFO order for sending the outgoing commands to the first user account.

53. The computer program product of claim 52, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command based on content of the outgoing command.

54. The computer program product of claim 52, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command based on a content type of the outgoing command.

55. The computer program product of claim 52, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command to add content before selecting an outgoing command to modify content.

56. The computer program product of claim 55, wherein the outgoing command to add content includes an outgoing command to add an email message, and wherein the outgoing command to modify content includes a modification to a state of an existing email message.

57. The computer program product of claim 52, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command to add a second email message before selecting an outgoing command to add a first email message, wherein a date and time of the first email message indicates generation before a date and time of the second email message.

58. The computer program product of claim 52, wherein the program code for selecting the non-FIFO order includes program code for selecting a plurality of outgoing commands to add recent email messages before selecting an outgoing command to add an older email message.

59. A device gateway for routing changes to information between a plurality of user devices and a command memory of a content routing server, the device gateway comprising:

a first protocol translator for;

modeling a server of a first user device;

routing commands between the first user device and the command memory of the content routing server; and

transforming the commands between a first device protocol and a common protocol, wherein the first device protocol is used to communicate with the first user device, and wherein the common protocol is used to communicate to the command memory of the content routing server; and

a second protocol translator for;

modeling a server of a second user device;

routing commands between the second user device and the command memory of the content routing server; and

transforming the commands between a second device protocol and the common protocol, wherein the second device protocol is used to communicate with the second user device, and wherein the second device protocol differs from the first device protocol.

60. The device gateway of claim 59, wherein the common protocol includes a remote procedure calling (RPC) protocol.

61. The device gateway of claim 60, wherein the RPC protocol includes an XML-RPC protocol.

62. The device gateway of claim 59, wherein the common protocol includes a Remote Method Invocation (RMI) protocol.

63. The device gateway of claim 62, wherein the RMI protocol includes a Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP).

64. The device gateway of claim 59, wherein the first user device is operable to communicate content of a first content type and the second user device is operable to provide content of a second content type different than the first content type.

65. The device gateway of claim 64, wherein the first content type includes an email content type and the second content type includes a PIM content type.

66. The device gateway of claim 64, wherein the first content type includes an email content type and the second content type includes a media content type.

67. The device gateway of claim 64, wherein the first content type includes an email content type and the second content type includes a contacts content type.

68. The device gateway of claim 59, further comprising a plurality of protocol translators for transforming commands between a correspond one of a plurality of different device protocols and the common protocol, wherein each of the plurality of protocol translators models a server of a corresponding user device and models a client of the command memory of the content routing server.

69. The device gateway of claim 59, wherein the first user device further includes a plurality of first user devices.

70. The device gateway of claim 69, wherein the second user device further includes a plurality of second user devices.

71. The device gateway of claim 59, further comprising:

memory for holding outgoing commands received from the command memory of the content routing server and destined for the first user device; and

processing logic, coupled to the memory, for selecting a non-FIFO order for sending the outgoing commands to the first user device.

72. The device gateway of claim 71, wherein selecting the non-FIFO order includes selecting an outgoing command based on content of the outgoing command.

73. The device gateway of claim 71, wherein selecting the non-FIFO order includes selecting an outgoing command based on a content type of the outgoing command.

74. The device gateway of claim 71, wherein selecting the non-FIFO order includes selecting an outgoing command to add content before selecting an outgoing command to modify content.

75. The device gateway of claim 74, wherein the outgoing command to add content includes an outgoing command to add an email message, and wherein the outgoing command to modify content includes a modification to a state of an existing email message.

76. The device gateway of claim 71, wherein selecting the non-FIFO order includes selecting an outgoing command to add a second email message before selecting an outgoing command to add a first email message, wherein a date and time of the first email message indicates generation before a date and time of the second email message.

77. The device gateway of claim 71, wherein selecting the non-FIFO order includes selecting a plurality of outgoing commands to add recent email messages before selecting an outgoing command to add an older email message.

78. The device gateway of claim 59, further including the content routing server.

79. The device gateway of claim 59, further including a server gateway comprising:

a first server protocol translator for;

modeling a client of a first user account server, wherein the first user account server includes a first user account;

routing commands between the first user account server and the command memory of the content routing server; and

transforming the commands between a first server protocol and the common protocol, wherein the first server protocol is used to communicate with the first user account server; and

a second server protocol translator for;

modeling a client of a second user account server, wherein the second user account server includes a second user account;

routing commands between the second user account server and the command memory of the content routing server; and

transforming the commands between a second server protocol and the common protocol, wherein the second server protocol is used to communicate with the second user account server, and wherein the second server protocol differs from the first server protocol.

80. The device gateway of claim 79, further including the content routing server.

81. A method for routing changes to information between a plurality of user devices and a command memory of a content routing server, the method comprising, at a device gateway:

modeling a server of a first user device;

routing commands between the first user device and the command memory of the content routing server;

transforming the commands between a first device protocol and a common protocol, wherein the first device protocol is used to communicate with the first user device, and wherein the common protocol is used to communicate to the command memory of the content routing server; and

modeling a server of a second user device;

routing commands between the second user device and the command memory of the content routing server; and

transforming the commands between a second device protocol and the common protocol, wherein the second device protocol is used to communicate with the second user device, and wherein the second device protocol differs from the first device protocol.

82. The method of claim 81, wherein the common protocol includes a remote procedure calling (RPC) protocol.

83. The method of claim 82, wherein the RPC protocol includes an XML-RPC protocol.

84. The method of claim 81, wherein the common protocol includes a Remote Method Invocation (RMI) protocol.

85. The method of claim 84, wherein the RMI protocol includes a Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP).

86. The method of claim 81, wherein the first user device is operable to communicate content of a first content type and the second user device is operable to communicate content of a second content type different than the first content type.

87. The method of claim 86, wherein the first content type includes an email content type and the second content type includes a PIM content type.

88. The method of claim 86, wherein the first content type includes an email content type and the second content type includes a media content type.

89. The method of claim 86, wherein the first content type includes an email content type and the second content type includes a contacts content type.

90. The method of claim 81, further comprising transforming commands between a correspond one of a plurality of different device protocols and the common protocol, wherein each of the plurality of protocol translators models a server of a corresponding user device and models a client of the command memory of the content routing server.

91. The method of claim 81, wherein the first user device further includes a plurality of first user devices.

92. The method of claim 91, wherein the second user device further includes a plurality of second user devices.

93. The method of claim 81, further comprising:

saving to memory outgoing commands received from the command memory of the content routing server and destined for the first user device; and

selecting a non-FIFO order for sending the outgoing commands to the first user device.

94. The method of claim 93, wherein selecting the non-FIFO order includes selecting an outgoing command based on content of the outgoing command.

95. The method of claim 93, wherein selecting the non-FIFO order includes selecting an outgoing command based on a content type of the outgoing command.

96. The method of claim 93, wherein selecting the non-FIFO order includes selecting an outgoing command to add content before selecting an outgoing command to modify content.

97. The method of claim 96, wherein the outgoing command to add content includes an outgoing command to add an email message, and wherein the outgoing command to modify content includes a modification to a state of an existing email message.

98. The method of claim 93, wherein selecting the non-FIFO order includes selecting an outgoing command to add a second email message before selecting an outgoing command to add a first email message, wherein a date and time of the first email message indicates generation before a date and time of the second email message.

99. The method of claim 93, wherein selecting the non-FIFO order includes selecting a plurality of outgoing commands to add recent email messages before selecting an outgoing command to add an older email message.

100. A computer program product comprising program code for use in a device gateway including processing logic for communicating commands between a content router and user devices, the computer program product comprising:

program code for modeling a server of a first user device;

program code for routing commands between the first user device and the command memory of the content routing server;

program code for transforming the commands between a first device protocol and a common protocol, wherein the first device protocol is used to communicate with the first user device, and wherein the common protocol is used to communicate to the command memory of the content routing server; and

program code for modeling a server of a second user device;

program code for routing commands between the second user device and the command memory of the content routing server; and

program code for transforming the commands between a second device protocol and the common protocol, wherein the second device protocol is used to communicate with the second user device, and wherein the second device protocol differs from the first device protocol.

101. The computer program product of claim 100, wherein the common protocol includes a remote procedure calling (RPC) protocol.

102. The computer program product of claim 101, wherein the RPC protocol includes an XML-RPC protocol.

103. The computer program product of claim 101, wherein the common protocol includes a Remote Method Invocation (RMI) protocol.

104. The computer program product of claim 103, wherein the RMI protocol includes a Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP).

105. The computer program product of claim 100, wherein the first user device is operable to communicate content of a first content type and the second user device is operable to communicate content of a second content type different than the first content type.

106. The computer program product of claim 105, wherein the first content type includes an email content type and the second content type includes a PIM content type.

107. The computer program product of claim 105, wherein the first content type includes an email content type and the second content type includes a media content type.

108. The computer program product of claim 105, wherein the first content type includes an email content type and the second content type includes a contacts content type.

109. The computer program product of claim 100, further comprising program code for transforming commands between a correspond one of a plurality of different device protocols and the common protocol, wherein each of the plurality of protocol translators models a client of a corresponding user device and models a client of the command memory of the content routing server.

110. The computer program product of claim 100, wherein the first user device further includes a plurality of first devices.

112. The computer program product of claim 100, further comprising:

program code for saving to memory outgoing commands received from the command memory of the content routing server and destined for the first user device; and

program code for selecting a non-FIFO order for sending the outgoing commands to the first user device.

113. The computer program product of claim 112, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command based on content of the outgoing command.

114. The computer program product of claim 112, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command based on a content type of the outgoing command.

115. The computer program product of claim 112, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command to add content before selecting an outgoing command to modify content.

117. The computer program product of claim 112, wherein the program code for selecting the non-FIFO order includes program code for selecting an outgoing command to add a second email message before selecting an outgoing command to add a first email message, wherein a date and time of the first email message indicates generation before a date and time of the second email message.

118. The computer program product of claim 112, wherein the program code for selecting the non-FIFO order includes program code for selecting a plurality of outgoing commands to add recent email messages before selecting an outgoing command to add an older email message.