Aggregating network activity using software provenance data

• US 20070266166A1
• Filed: 03/31/2006
• Published: 11/15/2007
• Est. Priority Date: 03/31/2006
• Status: Active Grant

• Current Assignee: The Invention Science Fund I, L.L.C. (Intellectual Ventures LLC)
• Original Assignee: Searete LLC (Intellectual Ventures LLC)
• Inventors: Cohen, Alexander J., Lord, Robert W., Jung, Edward K.Y., Levien, Royce A., Malamud, Mark A., Rinaldo, John D., Wood, Lowell L.
• Granted Patent: US 7,865,583 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H01L 2924/00 Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
• CPC Class Codes: H01L 2924/0002 Not covered by any one of groups H01L24/00, H01L24/00 and H01L2224/00
• CPC Class Codes: H04L 41/048 mobile agents
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A method and system are described for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node and executing one or more instructions received from the second node, on the first node.

Claims

1. A method comprising:

receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node; and

executing one or more instructions received from the second node, on the first node.

6. The method of claim 1, in which executing one or more instructions received from the second node, on the first node comprises:

receiving a mobile agent as the one or more instructions.

9. The method of claim 1, in which receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

receiving a memory address as the handle relating to the first software program active on the second node, as a portion of the provenance data.

26. The method of claim 1, in which executing one or more instructions received from the second node, on the first node comprises:

receiving an indication that at least an additional node has an available capacity; and

transmitting at least the one or more received instructions to the additional node.

2-5. -5. (canceled)

7-8. -8. (canceled)

10-25. -25. (canceled)

27-28. -28. (canceled)

29. A method comprising:

obtaining an association at least between a first registry state and an event indication from a first device;

obtaining an association at least between a second registry state and a failure indication from a second device; and

transmitting a message partly based on the first registry state and partly based on the second registry state.

30. The method of claim 29, in which obtaining an association at least between a first registry state and an event indication from a first device comprises:

receiving, at a third device, the association at least between the first registry state and the event indication from the first device.

32. The method of claim 29, in which obtaining an association at least between a second registry state and a failure indication from a second device comprises:

including an indication of an attribute of the second device in the association also.

31. (canceled)

33-37. -37. (canceled)

38. A method comprising:

obtaining a resource status indication relating to a first node, in the first node;

obtaining a resource status indication relating to a second node, in the first node; and

transmitting a provenance component, responsive to the obtained resource status indication relating to the first node and to the obtained resource status indication relating to the second node.

39. The method of claim 38, in which obtaining a resource status indication relating to a second node, in the first node comprises:

receiving the resource status indication relating to the second node, after transmitting a request from the first node.

43. The method of claim 38, in which transmitting a provenance component, responsive to the obtained resource status indication relating to the first node and to the obtained resource status indication relating to the second node comprises:

including a timestamp in the provenance component.

40-42. -42. (canceled)

44. (canceled)

45. A system comprising:

means for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node; and

means for executing one or more instructions received from the second node, on the first node.

51. The system of claim 45, in which the means for executing one or more instructions received from the second node, on the first node comprises:

means for receiving one or more signals including at least the one or more instructions, at the first node; and

means for sending one or more responses to the one or more signals, from the first node.

52. The system of claim 45, in which the means for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

means for receiving an indication of a partial completion of a task by the first software program.

59. The system of claim 45, in which the means for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

means for receiving a user handle as an additional portion of the provenance data.

71. The system of claim 45, in which the means for executing one or more instructions received from the second node, on the first node comprises:

means for requesting an indication of one or more additional nodes having an available capacity.

46-50. -50. (canceled)

53-58. -58. (canceled)

60-70. -70. (canceled)

72. (canceled)

73. A system comprising:

means for obtaining an association at least between a first registry state and an event indication from a first device;

means for obtaining an association at least between a second registry state and a failure indication from a second device; and

means for transmitting a message partly based on the first registry state and partly based on the second registry state.

79. The system of claim 73, in which the means for transmitting a message partly based on the first registry state and partly based on the second registry state comprises:

means for associating one or more index values with at least one of a hypothesis or a suggestion.

81. The system of claim 73, in which the means for transmitting a message partly based on the first registry state and partly based on the second registry state comprises:

means for including in the message at least a portion of the first registry state and at least a portion of the second registry state.

74-78. -78. (canceled)

80. (canceled)

82. A system comprising:

means for obtaining a resource status indication relating to a first node, in the first node;

means for obtaining a resource status indication relating to a second node, in the first node; and

means for transmitting a provenance component, responsive to the obtained resource status indication relating to the first node and to the obtained resource status indication relating to the second node.

84. The system of claim 82, in which the means for obtaining a resource status indication relating to a second node, in the first node comprises:

means for storing the resource status indication relating to the second node.

86. The system of claim 82, in which the means for transmitting a provenance component, responsive to the obtained resource status indication relating to the first node and to the obtained resource status indication relating to the second node comprises:

means for generating the provenance component responsive to obtaining the resource status indication relating to the second node; and

means for transmitting the generated provenance component responsive to receiving a data request from a third node.

83. (canceled)

85. (canceled)

87-88. -88. (canceled)

89. A system comprising:

circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node; and

circuitry for executing one or more instructions received from the second node, on the first node.

90. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving a handle relating to a second software program active on the second node, as a portion of the provenance data.

91. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving a failure indication relating to a portion of the first software program active on the second node, as a portion of the provenance data.

92. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving a subroutine identifier as the handle relating to the first software program active on the second node, as a portion of the provenance data.

93. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving a mobile agent identifier as the handle relating to the first software program active on the second node, as a portion of the provenance data.

98. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving an operating system identifier as the handle relating to the first software program active on the second node, as a portion of the provenance data.

100. The system of claim 89, in which the circuitry for executing one or more instructions received from the second node, on the first node comprises:

circuitry for transmitting to a third node at least a handle relating to the one or more instructions.

101. The system of claim 89, in which the circuitry for executing one or more instructions received from the second node, on the first node comprises:

circuitry for receiving additional provenance data at the first node after receiving the one or more instructions from the second node.

104. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving a timestamp as an additional portion of the provenance data.

105. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving a database handle as an additional portion of the provenance data.

107. The system of claim 89, in which the circuitry for executing one or more instructions received from the second node, on the first node comprises:

circuitry for transmitting an availability indication from the first node.

109. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for transmitting at least the handle and an identifier of the second node to a zonal registry.

110. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving an indication of the first software program being active on a third node also, as an additional portion of the provenance data.

111. The system of claim 89, in which the circuitry for receiving, at a first node, provenance data including at least a handle relating to a first software program active on a second node comprises:

circuitry for receiving a spawning mode as an additional portion of the provenance data.

113. The system of claim 89, in which the circuitry for executing one or more instructions received from the second node, on the first node comprises:

circuitry for transmitting at least the one or more received instructions to a third node, responsive to an indication that one or more spawning criteria have been met.

116. The system of claim 89, in which the circuitry for executing one or more instructions received from the second node, on the first node comprises:

circuitry for transmitting at least a handle relating to the one or more received instructions and an identifier of the first node to a zonal registry.

94-97. -97. (canceled)

99. (canceled)

102-103. -103. (canceled)

106. (canceled)

108. (canceled)

112. (canceled)

114-115. -115. (canceled)

117. A system comprising:

circuitry for obtaining an association at least between a first registry state and an event indication from a first device;

circuitry for obtaining an association at least between a second registry state and a failure indication from a second device; and

circuitry for transmitting a message partly based on the first registry state and partly based on the second registry state.

119. The system of claim 117, in which the circuitry for obtaining an association at least between a second registry state and a failure indication from a second device comprises:

circuitry for storing the association at least between the second registry state and the failure indication from the second device.

124. The system of claim 117, in which the circuitry for transmitting a message partly based on the first registry state and partly based on the second registry state comprises:

circuitry for using at least a portion of the first registry state and at least a portion of the second registry state in one or more search criteria.

118. (canceled)

120-123. -123. (canceled)

125. (canceled)

126. A system comprising:

circuitry for obtaining a resource status indication relating to a first node, in the first node;

circuitry for obtaining a resource status indication relating to a second node, in the first node; and

circuitry for transmitting a provenance component, responsive to the obtained resource status indication relating to the first node and to the obtained resource status indication relating to the second node.

129. The system of claim 126, in which the circuitry for obtaining a resource status indication relating to a second node, in the first node comprises:

circuitry for receiving the resource status indication relating to the second node from a third node.

132. The system of claim 126, in which the circuitry for transmitting a provenance component, responsive to the obtained resource status indication relating to the first node and to the obtained resource status indication relating to the second node comprises:

circuitry for transmitting the provenance component, responsive also to a provenance inclusion mode.

127-128. -128. (canceled)

130-131. -131. (canceled)