System and method for deriving affinity relationships between objects

• US 20060149731A1
• Filed: 01/05/2005
• Published: 07/06/2006
• Est. Priority Date: 01/05/2005
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Schirmer, Andrew Lewis, Rokosz, Vaughn Theodore
• Application Number:
  US11/028,576
• Publication Number:
  US 20060149731A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06F 16/9024 Graphs; Linked lists G06F16/9027 takes precedence

Abstract

A system and method are provided for deriving affinity relationships between objects. A plurality of objects may be stored in a database. When two or more of these objects interact, the system and method may create an entry in a database defining the interaction. A counter may be incremented each time an interaction occurs between a pair of objects. If the counter exceeds a predefined threshold, the objects in the interacting object pair may be classified as having an affinity for each other.

Claims

1. A method for deriving affinity relationships for one or more of a plurality of objects comprising:

monitoring one or more of the plurality of objects to determine whether two of the plurality of objects interact;

in response to determining that two of the plurality of objects have interacted;

collecting data defining the interaction;

determining whether an entry has been created in a relationship database for the interacting objects and wherein an entry has not been created, creating said entry; and

incrementing an affinity counter located in said entry to keep track of a number of interactions between two of said plurality of objects;

wherein said affinity relationship is based on said affinity counter.

2. The method of claim 1 wherein said collected data includes a name for each of said two interacting objects and one or more of a time the interaction occurs, a type of interaction, and one or more properties associated with each of said two objects.

3. The method of claim 1 further comprising:

determining whether the affinity counter exceeds a predefined threshold; and

wherein the affinity counter exceeds the predetermined threshold, providing indicia in said entry in said relationship database indicating the objects have an affinity for each other.

4. The method of claim 1 wherein each entry includes a timestamp indicating a last interaction and wherein the method further comprises:

determining whether a predetermined time period has elapsed since the last interaction; and

wherein said predetermined time period has elapsed, resetting said affinity counter.

5. The method of claim 1 further comprising:

examining each entry in said relationship database;

determining whether two or more objects in said relationship database share a common property; and

wherein two or more objects in said relationship database share a common property, defining an aggregate affinity relationship among said two or more objects sharing a common property.

6. The method of claim 1 further comprising:

defining a set of one or more objects from said plurality of objects that are of interest; and

monitoring said defined set of objects to determine whether two or more of said defined set of objects interact.

7. The method of claim 1 further comprising:

defining a set of one or more interactions that are of interest, wherein said one or more interactions occur among said plurality of objects; and

collecting data associated with two or more objects when said two or more objects interact via one of said one or more actions that are of interest.

8. The method of claim 1 wherein said objects database includes one or more metadata attributes describing each of said objects.

9. The method of claim 8 further comprising:

determining whether two or more of said plurality of objects share a common metadata attribute; and

wherein two or more of said plurality of objects share a common metadata attribute, assigning said two or more objects to an object class.

10. The method of claim 9 further comprising:

determining whether an interaction occurs between one of said plurality of objects stored in said objects database and said object class;

wherein an entry interaction has occurred, updating an entry in said relationship database indicating said interaction.

11. The method of claim 10 wherein updating said entry includes:

wherein an entry has not been created, creating said entry; and

updating an affinity counter.

12. The method of claim 1 wherein the plurality of objects are stored in an objects database and wherein said objects database includes a name for each object and one or more properties associated with each object.

13. A system for deriving affinity relationships for one or more of a plurality of objects comprising:

an objects database configured to store said plurality of objects and one or more properties associated with each of said plurality of objects;

a discovery server configured to determine whether an interaction has occurred between two of said plurality of objects, wherein upon making a determination that an interaction has occurred, the discovery server annotates at least an object name and the one or more properties associated with the object for said two interacting objects; and

a relationship database configured to store one or more entries defining said affinity relationship between said two interacting objects, wherein said affinity relationship is based on at least a number of interactions that have occurred between said two objects.

14. The system of claim 13 wherein said discovery server comprises:

an interaction assessment module for determining whether an entry has been made in said relationship database for said two interacting objects, and wherein an entry has not been made, creating an entry; and

an affinity calculation module, said affinity calculation module configured to maintain a plurality of counters wherein one of said plurality of counters corresponds to each of said one or more entries in said relationship database.

15. The system of claim 13 wherein said one or more entries defining said affinity relationship includes a name field for each of said two interacting objects and one or more of a time the interaction occurred, a type of interaction, and one or more properties associated with each of said two interacting objects.

16. The system of claim 13 further comprising a user interface module configured to provide a graphical user interface wherein said graphical user interface enables a user to perform a query of said relationship database.

17. A computer implemented system for deriving affinity relationships for one or more of a plurality of objects comprising:

means for monitoring one or more of the plurality of objects, wherein the plurality of objects are stored in an objects database and wherein said objects database includes a name for each object and one or more properties associated with each object, to determine whether two of the plurality of objects interact;

in response to a determination that two of the plurality of objects have interacted;

means for collecting data defining the interaction;

means for determining whether an entry has been created in a relationship database for the interacting objects and wherein an entry has not been created, creating said entry; and

means for incrementing an affinity counter located in said entry wherein said affinity counter keeps track of a number of interaction that occur between two or said plurality of objects.

18. The system of claim 17 further comprising:

means for determining whether the affinity counter exceeds a predefined threshold; and

wherein the affinity counter exceeds the predetermined threshold, means for providing indicia in said entry in said relationship database indicating the objects have an affinity for each other.

19. The system of claim 17 further comprising:

means for examining each entry in said relationship database;

means for determining whether two or more objects in said relationship database share a common property; and

wherein two or more objects in said relationship database share a common property, means for defining an aggregate affinity relationship among said two or more objects sharing a common property.