Group compositing algorithms for presence

• US 8,301,581 B2
• Filed: 09/24/2009
• Issued: 10/30/2012
• Est. Priority Date: 09/24/2009
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Zmolek, Andrew
• Primary Examiner(s): Fernandez Rivas, Omar
• Application Number:
  US12/566,436
• Publication Number:
  US 20110071972A1
• Time in Patent Office: 1,132 Days
• Field of Search: None
• US Class Current: 706/62
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Systems and methods presented herein construct groups and determine the presence for the groups. The groups can be constructed based on business logic. A set of components can model a group from the business logic, can establish a membership for the group, can determine one or more rules that govern presence determination for the membership, and can provide the group model, membership information, and the one or more rules to a rules engine. The rules engine can evaluate presence within the group model based on the membership and the one or more rules. The group presence can then be provided to one or more entities, applications, or workflows that subscribe to the rules engine for the group presence.

Claims

1. A method for determining group presence, the method comprising:

a processor receiving a presence event;

in response to receiving of the presence event, the processor determining a hierarchy associated with the presence event, wherein the hierarchy is associated with a group having two or more nodes;

the processor traversing the hierarchy associated with the group to a selected one of the nodes;

the processor determining a presence for the selected node;

the processor determining if another node in the hierarchy exists for the group;

if another node exists for the group, determining a presence for the other node;

if another node in the hierarchy does not exist for the group, determining a presence for the group based on the presence for the nodes in the hierarchy; and

the processor publishing the group presence.

2. The method as defined in claim 1, wherein the node is associated with the presence of an individual person.

3. The method as defined in claim 1, wherein the node is associated with the presence of a sub-group, wherein the sub-group includes two or more individual persons.

4. The method as defined in claim 1, wherein the presence of the node is determined based on a membership for the node and a threshold.

5. The method as defined in claim 4, wherein the membership includes two or more individual persons, and wherein the threshold is determined by a rule that defines when the membership of the node is present.

6. The method as defined in claim 4, wherein the membership in the node is based on at least one attribute of an individual person as stored in an enterprise directory.

7. The method as defined in claim 6, wherein the processor retrieves an identity of an individual person having the attribute from the enterprise directory to determine the presence for the node.

8. The method as defined in claim 1, wherein the presence event is one of a group comprising a change in a presence status for an individual person, a change to a business objective that defines the group rule, a change in a membership of a node, a change to the hierarchy of the group, and a change to a node in the group.

9. A system comprising:

a presence server, the presence server operable to determine a presence status for two or more individual persons associated with a group and operable to provide the presence status as individual presence information;

a rules engine in communication with the presence server, the rules engine operable to receive the individual presence information for each of the two or more individual persons, operable to determine a group presence based on the received individual presence information, and operable to publish the group presence, wherein the rules engine determines the group presence based on a rule created from a business logic;

a rules database in communication with the rules engine, the rules database operable to store the rule;

an enterprise directory, the enterprise directory operable to provide the business logic;

a group definition component in communication with the rules database, the group definition component operable to define the group based on the business logic; and

a rules definition component in communication with the rules database and the group definition component, the rules definition component operable to define the rule based on at least one of the group and the business logic.

10. The system as defined in claim 9, wherein the rules engine executes on the presence server.

11. The system as defined in claim 9, wherein the group definition component creates a group definition data structure, the group definition data structure comprising at least one of:

a group identifier;

a hierarchy definition for the group, wherein the hierarchy includes two or more nodes;

two or more identifiers for the two or more nodes;

a membership for the group; and

a threshold for the group, wherein the threshold defines when the membership of the group is present.

12. The system as defined in claim 9, wherein the rules definition component creates a node definition data structure, the node definition data structure comprising at least one of:

a node identifier;

a membership for the node; and

a threshold for the node, wherein the threshold defines when the membership of the node is present.

13. The system as defined in claim 9, further comprising an LDAP database in communication with the rules engine, the LDAP database operable to store information about the two or more individual persons, wherein the information comprises attributes associated with the two or more individual persons, wherein the rules engine retrieves identities for the two or more individual persons based on attributes associated with the membership of the group.

14. A computer program product comprising computer executable instructions stored onto a non-transitory computer readable medium which, when executed by a processor of a computer, causes the processor to execute a method, the instructions comprising:

instructions to receive business logic that defines a membership for a group;

instructions to determine a structure for the group based on the business logic, wherein the structure comprises a hierarchy having two or more nodes;

instructions to determine the hierarchy of the group based on the business logic;

instructions to determine a membership for each of the two or more nodes in the group;

instructions to determine a threshold for each of the two or more nodes in the group, wherein the threshold defines if the membership of the node is present;

instructions to create a rule for the group based on the business logic; and

instructions to store the rule.

15. The computer program product as defined in claim 14, wherein the threshold for the node is determined by one of a group of algorithms comprising:

at least one individual of two or more individuals in the membership is present;

all individuals in the membership are present;

a predetermined percentage of all individual in the membership are present; and

a predetermined number of individuals of all individuals in the membership are present.

16. The computer program product as defined in claim 14, wherein the rule for the group can include at least one of a group comprising:

a time-of-day rule to limit presence of the group or a node based on the time of day;

a geographic location rule that limits a presence for the group or the node based on geophysical location;

a medium rule that limits a presence for the group or the node based on the medium or channel of communication available; and

a state limitation rule that limits presence for the group or the node based on a state.

17. The computer program product as defined in claim 14, wherein the membership of the group can be a collection of other groups or sub-groups.

18. The computer program product as defined in claim 14, wherein the membership of the group is defined by attributes derived from an enterprise directory.

19. The computer program product as defined in claim 14, wherein the rule changes if the business logic is changed.