Content router notification

• US 20070014300A1
• Filed: 07/14/2005
• Published: 01/18/2007
• Est. Priority Date: 07/14/2005
• Status: Active Grant

• Current Assignee: R2 Solutions LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Breuer, Matthias, Srinivasan, Venkatachary, Boerries, Marco, Meyer, Markus
• Granted Patent: US 7,623,515 B2
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/2871 Implementation details of single intermediate entities
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54

Abstract

An apparatus, method and computer program product for communicating an outgoing command from a command memory of a content router to a content node using a notification signal to a gateway.

Claims

1. A gateway for communicating an outgoing command from a command memory of a content router to a content node, the gateway comprising:

logic for receiving, from the command memory of the content router, a notification signal, wherein the received notification signal indicates a content type of an outgoing command in the command memory of the content router available for the content node;

logic for sending, to the command memory of the content router, a request for the outgoing command, the request including the content type;

logic for receiving, from the command memory of the content router, a response including the outgoing command;

logic for preparing, in response to receiving the outgoing command, an outgoing message including the outgoing command; and

logic for sending, to the content node, the message including the outgoing command.

2. The gateway of claim 1, further comprising logic for receiving, from the content node, a response acknowledging that the outgoing command was received by the content node.

3. The gateway of claim 1, wherein the logic for sending, to the content node, the message including the outgoing command includes logic for sending the outgoing command in a notification signal to the content node.

4. The gateway of claim 3, further comprising logic for delaying sending for a duration of time based on a connection type between the gateway and the content node.

5. The gateway of claim 4, wherein the duration of time is further based on a duration of time to a previous communication between the gateway and the content node.

6. The gateway of claim 3, wherein the outgoing command includes metadata and an identification of content.

7. The gateway of claim 6, wherein the metadata includes a flag.

8. The gateway of claim 6, wherein the identification of content identifies an email message on the content node.

9. The gateway of claim 8, wherein the metadata indicates a read/unread state of the email.

10. The gateway of claim 3, further comprising:

logic for sending, to the command memory of the content router, a request including an acknowledgement indicating that the outgoing command may be discarded; and

logic for receiving, from the command memory of the content router, a response including an indication that the request including the acknowledgement was received by the command memory of the content router.

11. The gateway of claim 3, wherein the logic for sending the outgoing command in the notification signal includes logic for sending the outgoing command as an encoded binary sequence of bits.

12. The gateway of claim 3, wherein the logic for sending, to the content node, the command in the notification signal includes logic for using an SMS gateway.

13. The gateway of claim 1, wherein the logic for sending, to the content node, the message including the outgoing command includes logic for sending a request including the command, the gateway further comprising logic for receiving, from the content node, a response indicating that the request including the command was received by the content node.

14. The gateway of claim 13, further comprising:

logic for sending, to the command memory of the content router, a request including an acknowledgement indicating that the outgoing command may be discarded, wherein the sending is in response to receiving, from the content node, the response indicating that the request including the command was received by the content node; and

logic for receiving, from the command memory of the content router, a response including an indication that the request including the acknowledgement was received by the command memory of the content router.

15. The gateway of claim 1, wherein the content node is a user device.

16. The gateway of claim 15, wherein the user device includes a mobile phone.

17. The gateway of claim 1, wherein the content node is a user account.

18. The gateway of claim 17, wherein the user account includes an email account.

19. The gateway of claim 1, wherein the logic for preparing the outgoing message includes logic for converting the outgoing command in a first protocol to the outgoing messages in a second protocol.

20. The gateway of claim 19, wherein the first protocol includes a Remote Gateway Invocation (RMI) protocol.

21. The gateway of claim 20, wherein the RMI protocol includes an RMI protocol over Internet Inter-ORB protocol (RMI-IIOP).

22. The gateway of claim 19, wherein the first protocol includes a Remote Procedure Calling (RPC) protocol.

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

24. The gateway of claim 19, wherein the second protocol includes a Remote Procedure Calling (RPC) protocol.

25. The gateway of claim 24, wherein the RPC protocol includes an XML-RPC protocol.

26. The gateway of claim 19, wherein the second protocol includes a device based protocol.

27. The gateway of claim 1, further including:

logic for sending, to the content node, a notification excluding the content type;

logic for receiving, from the content node, a request requesting a content type of the outgoing command;

logic for sending, to the content node, a response including the content type of the outgoing command; and

logic for receiving, from the content node, a request requesting the outgoing command, wherein the request includes the content type.

28. The gateway of claim 1, wherein the logic for sending, to the content node, the message including the outgoing command includes logic for sending a plurality of outgoing commands.

29. The gateway of claim 1, further comprising the content router.

30. The gateway of claim 1, wherein the logic for receiving, from the command memory of the content router, the notification signal includes logic for receiving the notification signal from store and forward logic of the content router.

31. A method for communicating an outgoing command from a content router to a content node using a gateway, the method comprising, at the gateway:

receiving, from the command memory of the content router, a notification signal, wherein the received notification signal indicates a content type of an outgoing command in the command memory of the content router available for the content node;

sending, to the command memory of the content router, a request for the outgoing command, the request including the content type;

receiving, from the command memory of the content router, a response including the outgoing command;

preparing, in response to receiving the outgoing command, an outgoing message including the outgoing command; and

sending, to the content node, the message including the outgoing command.

32. The method of claim 31, further comprising receiving, from the content node, a response acknowledging that the outgoing command was received by the content node.

33. The method of claim 31, wherein sending, to the content node, the message including the outgoing command includes sending the outgoing command in a notification signal to the content node.

34. The method of claim 33, further comprising delaying sending for a duration of time based on a connection type between the gateway and the content node.

35. The method of claim 34, wherein the duration of time is further based on a duration of time to a previous communication between the gateway and the content node.

36. The method of claim 33, wherein the outgoing command includes metadata and an identification of content.

37. The method of claim 36, wherein the metadata includes a flag.

38. The method of claim 36, wherein the identification of content identifies an email message on the content node.

39. The method of claim 38, wherein the metadata indicates a read/unread state of the email.

40. The method of claim 33, further comprising:

sending, to the command memory of the content router, a request including an acknowledgement indicating that the outgoing command may be discarded; and

receiving, from the command memory of the content router, a response including an indication that the request including the acknowledgement was received by the command memory of the content router.

41. The method of claim 33, wherein sending the outgoing command in the notification signal includes sending the outgoing command as an encoded binary sequence of bits.

42. The method of claim 33, wherein sending, to the content node, the command in the notification signal includes using an SMS gateway.

43. The method of claim 31, wherein sending, to the content node, the message including the outgoing command includes sending a request including the command, the method further comprising receiving, from the content node, a response indicating that the request including the command was received by the content node.

44. The method of claim 43, further comprising:

sending, to the command memory of the content router, a request including an acknowledgement indicating that the outgoing command may be discarded, wherein the sending is in response to receiving, from the content node, the response indicating that the request including the command was received by the content node; and

receiving, from the command memory of the content router, a response including an indication that the request including the acknowledgement was received by the command memory of the content router.

45. The method of claim 31, wherein the content node is a user device.

46. The method of claim 45, wherein the user device includes a mobile phone.

47. The method of claim 31, wherein the content node is a user account.

48. The method of claim 47, wherein the user account includes an email account.

49. The method of claim 31, wherein preparing the outgoing message includes converting the outgoing command in a first protocol to the outgoing messages in a second protocol.

50. The method of claim 49, wherein the first protocol includes a Remote Method Invocation (RMI) protocol.

51. The method of claim 50, wherein the RMI protocol includes an RMI protocol over Internet Inter-ORB protocol (RMI-IIOP).

52. The method of claim 49, wherein the first protocol includes a Remote Procedure Calling (RPC) protocol.

53. The method of claim 52, wherein the RPC protocol includes an XML-RPC protocol.

54. The method of claim 49, wherein the second protocol includes a Remote Procedure Calling (RPC) protocol.

55. The method of claim 54, wherein the RPC protocol includes an XML-RPC protocol.

56. The method of claim 49, wherein the second protocol includes a device based protocol.

57. The method of claim 31, further including:

sending, to the content node, a notification excluding the content type;

receiving, from the content node, a request requesting a content type of the outgoing command;

sending, to the content node, a response including the content type of the outgoing command; and

receiving, from the content node, a request requesting the outgoing command, wherein the request includes the content type.

58. The method of claim 31, wherein sending, to the content node, the message including the outgoing command includes sending a plurality of outgoing commands.

59. A computer program product comprising program code for use in a gateway including processing logic for communicating an outgoing command from a content router to a content node, the computer program product comprising:

program code for receiving, from the command memory of the content router, a notification signal, wherein the received notification signal indicates a content type of an outgoing command in the command memory of the content router available for the content node;

program code for sending, to the command memory of the content router, a request for the outgoing command, the request including the content type;

program code for receiving, from the command memory of the content router, a response including the outgoing command;

program code for preparing, in response to receiving the outgoing command, an outgoing message including the outgoing command; and

program code for sending, to the content node, the message including the outgoing command.

60. The computer program product of claim 59, further comprising program code for receiving, from the content node, a response acknowledging that the outgoing command was received by the content node.

61. The computer program product of claim 59, wherein the program code for sending, to the content node, the message including the outgoing command includes program code for sending the outgoing command in a notification signal to the content node.

62. The computer program product of claim 61, further comprising program code for delaying sending for a duration of time based on a connection type between the gateway and the content node.

63. The computer program product of claim 62, wherein the duration of time is further based on a duration of time to a previous communication between the gateway and the content node.

64. The computer program product of claim 61, wherein the outgoing command includes metadata and an identification of content.

65. The computer program product of claim 64, wherein the metadata includes a flag.

66. The computer program product of claim 64, wherein the identification of content identifies an email message on the content node.

67. The computer program product of claim 66, wherein the metadata indicates a read/unread state of the email.

68. The computer program product of claim 61, further comprising:

program code for sending, to the command memory of the content router, a request including an acknowledgement indicating that the outgoing command may be discarded; and

program code for receiving, from the command memory of the content router, a response including an indication that the request including the acknowledgement was received by the command memory of the content router.

69. The computer program product of claim 61, wherein the program code for sending the outgoing command in the notification signal includes program code for sending the outgoing command as an encoded binary sequence of bits.

70. The computer program product of claim 61, wherein the program code for sending, to the content node, the command in the notification signal includes program code for using an SMS gateway.

71. The computer program product of claim 59, wherein the program code for sending, to the content node, the message including the outgoing command includes program code for sending a request including the command, the computer program product further comprising program code for receiving, from the content node, a response indicating that the request including the command was received by the content node.

72. The computer program product of claim 71, further comprising:

program code for sending, to the command memory of the content router, a request including an acknowledgement indicating that the outgoing command may be discarded, wherein the sending is in response to receiving, from the content node, the response indicating that the request including the command was received by the content node; and

program code for receiving, from the command memory of the content router, a response including an indication that the request including the acknowledgement was received by the command memory of the content router.

73. The computer program product of claim 59, wherein the content node is a user device.

74. The computer program product of claim 73, wherein the user device includes a mobile phone.

75. The computer program product of claim 59 wherein the content node is a user account.

76. The computer program product of claim 75, wherein the user account includes an email account.

77. The computer program product of claim 59, wherein the program code for preparing the outgoing message includes program code for converting the outgoing command in a first protocol to the outgoing messages in a second protocol.

78. The computer program product of claim 77, wherein the first protocol includes a Remote Computer program product Invocation (RMI) protocol.

79. The computer program product of claim 78, wherein the RMI protocol includes an RMI protocol over Internet Inter-ORB protocol (RMI-IIOP).

80. The computer program product of claim 77, wherein the first protocol includes a Remote Procedure Calling (RPC) protocol.

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

82. The computer program product of claim 77, wherein the second protocol includes a Remote Procedure Calling (RPC) protocol.

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

84. The computer program product of claim 77, wherein the second protocol includes a device based protocol.

85. The computer program product of claim 59, further including:

program code for sending, to the content node, a notification excluding the content type;

program code for receiving, from the content node, a request requesting a content type of the outgoing command;

program code for sending, to the content node, a response including the content type of the outgoing command; and

receiving, from the content node, a request requesting the outgoing command, wherein the request includes the content type.

86. The computer program product of claim 59, wherein the program code for sending, to the content node, the message including the outgoing command includes program code for sending a plurality of outgoing commands.

87. A content router for communicating outgoing commands from the content router to a plurality of content nodes, the content router comprising:

command memory for holding incoming and outgoing commands; and

processing logic, coupled to the command memory, for;

saving to the command memory an incoming command received from a first content node and associated with a content type;

selecting a set of destination content nodes based on the content type and one or more routing parameters; and

for each of the selected destination content nodes;

saving an outgoing command to the command memory;

sending, to a gateway, a notification signal, wherein the sent notification signal indicates the content type of the outgoing command in the command memory available for the destination content node;

receiving, from the gateway, a request for the outgoing command, the request including the content type;

sending, to the gateway, a response including the outgoing command;

receiving, from the gateway, a request including an acknowledgement indicating that the outgoing command may be discarded;

removing the outgoing command from the command memory; and

sending, to the gateway, a response including an indication that the request including the acknowledgement was received by the content router.

88. The content router of claim 87, wherein the outgoing command includes metadata and an identification of content.

89. The content router of claim 88, wherein the metadata includes a flag.

90. The content router of claim 88, wherein the identification of content identifies an email message on the destination content node.

91. The content router of claim 90, wherein the metadata indicates a read/unread state of the email.

92. The content router of claim 87, wherein the destination content node is a user device.

93. The content router of claim 92, wherein the user device includes a mobile phone.

94. The content router of claim 87, wherein the destination content node is a user account.

95. The content router of claim 94, wherein the user account includes an email account.

96. The content router of claim 87, wherein sending, to the gateway, the response including the outgoing command includes sending the outgoing command in a Remote Method Invocation (RMI) protocol.

97. The content router of claim 96, wherein the RMI protocol includes an RMI protocol over Internet Inter-ORB protocol (RMI-IIOP).

98. The content router of claim 87, wherein sending, to the gateway, the response including the outgoing command includes sending the outgoing command in a Remote Procedure Calling (RPC) protocol.

99. The content router of claim 98, wherein the RPC protocol includes an XML-RPC protocol.

100. The content router of claim 87, further comprising the gateway.

101. The content router of claim 87, further comprising a connected data set configuration, coupled to the processing logic, for holding the one or more routing parameters.

102. The content router of claim 87, further comprising store and forward logic including the command memory and the processing logic.

103. A method for communicating an outgoing command from a content router to a content node, the method comprising, at the content router:

sending, to a gateway, a notification signal, wherein the sent notification signal indicates a content type of an outgoing command in the content router available for the content node;

receiving, from the gateway, a request for the outgoing command, the request including the content type;

sending, to the gateway, a response including the outgoing command;

receiving, from the gateway, a request including an acknowledgement indicating that the outgoing command may be discarded; and

sending, to the gateway, a response including an indication that the request including the acknowledgement was received by the content router.

104. The method of claim 103, wherein the outgoing command includes metadata and an identification of content.

105. The method of claim 104, wherein the metadata includes a flag.

106. The method of claim 104, wherein the identification of content identifies an email message on the content node.

107. The method of claim 106, wherein the metadata indicates a read/unread state of the email.

108. The method of claim 103, wherein the content node is a user device.

109. The method of claim 108, wherein the user device includes a mobile phone.

110. The method of claim 103, wherein the content node is a user account.

111. The method of claim 110, wherein the user account includes an email account.

112. The method of claim 103, wherein sending, to the gateway, the response including the outgoing command includes sending the outgoing command in a Remote Method Invocation (RMI) protocol.

113. The method of claim 112, wherein the RMI protocol includes an RMI protocol over Internet Inter-ORB protocol (RMI-IIOP).

114. The method of claim 103, wherein sending, to the gateway, the response including the outgoing command includes sending the outgoing command in a Remote Procedure Calling (RPC) protocol.

115. The method of claim 114, wherein the RPC protocol includes an XML-RPC protocol.

116. A computer program product comprising program code for use in a content router including processing logic for communicating an outgoing command from the content router to a content node, the computer program product comprising:

program code for sending, to a gateway, a notification signal, wherein the sent notification signal indicates a content type of an outgoing command in the content router available for the content node;

program code for receiving, from the gateway, a request for the outgoing command, the request including the content type;

program code for sending, to the gateway, a response including the outgoing command;

program code for receiving, from the gateway, a request including an acknowledgement indicating that the outgoing command may be discarded; and

program code for sending, to the gateway, a response including an indication that the request including the acknowledgement was received by the content router.

117. The computer program product of claim 116, wherein the outgoing command includes metadata and an identification of content.

118. The computer program product of claim 117, wherein the metadata includes a flag.

119. The computer program product of claim 117, wherein the identification of content identifies an email message on the content node.

120. The computer program product of claim 119, wherein the metadata indicates a read/unread state of the email.

121. The computer program product of claim 116, wherein the content node is a user device.

122. The computer program product of claim 121, wherein the user device includes a mobile phone.

123. The computer program product of claim 116, wherein the content node is a user account.

124. The computer program product of claim 123, wherein the user account includes an email account.

125. The computer program product of claim 116, wherein the program code for sending, to the gateway, the response including the outgoing command includes program code for sending the outgoing command in a Remote Method Invocation (RMI) protocol.

126. The computer program product of claim 125, wherein the RMI protocol includes an RMI protocol over Internet Inter-ORB protocol (RMI-IIOP).

127. The computer program product of claim 116, wherein the program code for sending, to the gateway, the response including the outgoing command includes program code for sending the outgoing command in a Remote Procedure Calling (RPC) protocol.

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