Techniques for resolving conflicts in scheduling conferences

• US 20060047557A1
• Filed: 10/05/2004
• Published: 03/02/2006
• Est. Priority Date: 09/01/2004
• Status: Abandoned Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Ethier, Randall, Bieselin, David
• Application Number:
  US10/958,523
• Publication Number:
  US 20060047557A1
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06Q 10/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: H04L 12/1818 Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties

Abstract

Techniques for scheduling a conference among multiple persons includes receiving a conference request to schedule a particular conference. The conference request includes quorum data and limit data. The quorum data indicates a quorum of persons to conduct the particular conference. The limit data indicates a limit on a property of the particular conference, such as a limit on the date, time, location, language, or travel cost. The method also includes receiving availability data from a shared database that includes information about a recorded commitment of time for each person of a population. Also received is priority data that indicates an importance to an organization that a particular recorded commitment of a particular person is honored. A proposed time interval for the particular conference is determined based on the conference request and the availability data and the priority data.

Claims

1. A method for scheduling a conference among multiple persons, comprising the steps of:

receiving a conference request to schedule a particular conference by receiving quorum data that indicates a quorum of persons to conduct the particular conference and receiving limit data that indicates a limit on a property of the particular conference;

receiving availability data from a shared database that includes information about a recorded commitment of time for each person of a population plurality of persons that includes all persons indicated in the quorum data;

receiving priority data that indicates an importance to an organization that a particular recorded commitment of a particular person of the population plurality of persons is honored; and

determining a proposed time interval for the particular conference based on the conference request and the availability data and the priority data.

2. The method as recited in claim 1, said step of receiving availability data further comprising receiving at least one of scheduled availability data based on data in a shared calendar database and current availability data based on presence data.

3. The method as recited in claim 1, said step of receiving priority data further comprising receiving priority data based on data in a shared calendar database.

4. The method as recited in claim 1, said step of determining the proposed time interval for the particular conference further comprising the steps of

determining a conflicted person whose recorded commitment blocks the particular conference;

determining a priority of the recorded commitment based on the priority data;

determining whether the priority of the recorded commitment is lower than a priority of the particular conference; and

if it is determined that the priority of the recorded commitment is lower than the priority of the particular conference, then rendering the conflicted person available for the particular conference during a time interval of the recorded commitment.

5. The method as recited in claim 4, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving echelon data that indicates whether a first organizer of the particular conference is at a higher echelon in the organization than is a second organizer for the recorded commitment.

6. The method as recited in claim 4, said step of determining the priority of the recorded commitment further comprises determining the priority of the recorded commitment based on a highest echelon of all attendees of a second conference corresponding to the recorded commitment.

7. The method as recited in claim 6, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving echelon data that indicates whether an attendee of the particular conference is at a higher echelon in the organization than are all attendees of the second conference.

8. The method as recited in claim 5, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving input data indicating whether the first organizer has determined that the priority of the recorded commitment is lower than the priority of the particular conference.

9. The method as recited in claim 4, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving data indicating whether a priority associated with a token obtained by an organizer of the particular conference from a member of a higher echelon than the organizer is greater than the priority of the recorded commitment.

10. The method as recited in claim 4, further comprising the steps of:

determining whether the conflicted person becomes committed to the particular conference; and

if it is determined that the conflicted person becomes committed to the particular conference, then alerting an organizer for the recorded commitment that the conflicted person is breaking the recorded commitment.

11. The method as recited in claim 1, wherein said step of receiving the conference request further comprises the step of receiving conference priority data that indicates an importance to the organization that the particular conference is held.

12. The method as recited in claim 11, said step of determining the proposed time interval for the particular conference further comprising the steps of:

determining a person whose recorded commitment blocks the particular conference;

determining a priority of the recorded commitment based on the priority data;

determining a priority of the particular conference based on the conference priority data;

determining whether the priority of the recorded commitment is lower than the priority of the particular conference; and

if it is determined that the priority of the recorded commitment is lower than the priority of the particular conference, then rendering the person available for the particular conference during a time interval of the recorded commitment.

13. The method as recited in claim 1, said step of receiving the quorum data further comprising receiving quorum data that indicates that the quorum for the particular conference includes a minimum number of persons in a first group of persons of the population plurality of persons and less than all persons from the first group of persons, whereby the first group is a representative group of persons.

14. The method as recited in claim 1, said step of receiving the quorum data further comprising receiving quorum data that indicates no person at an echelon in the organization which is higher by more than a particular difference above a conference echelon obtained by an organizer of the particular conference.

15. The method as recited in claim 14, said step of receiving the quorum data further comprising receiving quorum data that indicates a conference echelon obtained by an organizer of the particular conference is the same as an echelon of the organizer.

16. The method as recited in claim 14, said step of receiving the quorum data further comprising receiving quorum data that indicates a conference echelon obtained by an organizer of the particular conference is greater than an echelon of the organizer.

17. The method as recited in claim 1, said step of receiving the limit data further comprising receiving limit data that indicates that said property of the particular conference includes at least one of a date, a time of day, a location, a common language, and a travel cost.

18. The method as recited in claim 11, said step of determining the proposed time interval for the particular conference further comprising the steps of:

determining whether a conflict exists that blocks the particular conference; and

if it is determined that a conflict does not exist, then associating the priority of the particular conference with an invitation to attend the particular conference at the proposed time.

19. The method as recited in claim 18, the method further comprising the steps of:

receiving a commitment to attend the particular conference from a person whose attendance satisfies the quorum; and

storing the priority of the particular conference in association with availability data that indicates the commitment to attend the particular conference by the person whose attendance satisfies the quorum.

20. A method for scheduling a conference among multiple persons, comprising the steps of:

receiving a conference request to schedule a particular conference by receiving quorum data that indicates a quorum of persons to conduct the particular conference and receiving limit data that indicates a limit on a property of the particular conference;

receiving availability data from a shared database that includes information about a commitment of time for each person of a population plurality of persons that includes all persons indicated in the quorum data;

receiving priority data that indicates an importance to an organization that a particular recorded commitment of a particular person of the population plurality of persons is honored; and

determining a proposed time interval for the particular conference based on the conference request and the availability data and the priority data, including;

determining a conflicted person whose recorded commitment blocks the particular conference;

determining a priority of the recorded commitment based on the priority data;

determining whether the priority of the recorded commitment is lower than a priority of the particular conference by receiving echelon data that indicates at least one of

whether a first organizer of the particular conference is at a higher echelon in the organization than is a second organizer for the recorded commitment,

whether an attendee of the particular conference is at a higher echelon in the organization than are all attendees of a second conference for the recorded commitment

whether the first organizer has determined that the priority of the recorded commitment is lower than the priority of the particular conference, and

whether a priority associated with a token obtained by an organizer of the particular conference from a member of a higher echelon than the organizer is greater than the priority of the recorded commitment;

if it is determined that the priority of the recorded commitment is lower than the priority of the particular conference, then rendering the conflicted person available for the particular conference during a time interval of the recorded commitment;

determining whether the conflicted person becomes committed to the particular conference; and

if it is determined that the conflicted person becomes committed to the particular conference, then alerting an organizer for the recorded commitment that the conflicted person is breaking the recorded commitment.

21. A computer-readable medium carrying one or more sequences of instructions for scheduling a conference among multiple persons, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:

receiving a conference request to schedule a particular conference by receiving quorum data that indicates a quorum of persons to conduct the particular conference and receiving limit data that indicates a limit on a property of the particular conference;

receiving availability data from a shared database that includes information about a commitment of time for each person of a population plurality of persons that includes all persons indicated in the quorum data;

receiving priority data that indicates an importance to an organization that a particular recorded commitment of a particular person of the population plurality of persons is honored; and

determining a proposed time interval for the particular conference based on the conference request and the availability data and the priority data.

22. The computer-readable medium as recited in claim 21, said step of receiving availability data further comprising receiving at least one of scheduled availability data based on data in a shared calendar database and current availability data based on presence data.

23. The computer-readable medium as recited in claim 21, said step of receiving priority data further comprising receiving priority data based on data in a shared calendar database.

24. The computer-readable medium as recited in claim 21, said step of determining the proposed time interval for the particular conference further comprising the steps of

determining a person whose recorded commitment blocks the particular conference;

determining a priority of the recorded commitment based on the priority data;

determining whether the priority of the recorded commitment is lower than a priority of the particular conference; and

if it is determined that the priority of the recorded commitment is lower than the priority of the particular conference, then breaking the recorded commitment to render the person available for the particular conference.

25. The computer-readable medium as recited in claim 24, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving echelon data that indicates whether a first organizer of the particular conference is at a higher echelon in the organization than is a second organizer for the recorded commitment.

26. The computer-readable medium as recited in claim 25, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving input data indicating whether the first organizer has determined that the priority of the recorded commitment is lower than the priority of the particular conference.

27. The computer-readable medium as recited in claim 24, wherein execution of the one or more sequences of instructions further causes the one or more processors to perform the steps of:

determining whether the person is committed to the particular conference; and

if it is determined that the person is committed to the particular conference, then alerting an organizer for the recorded commitment that the person is breaking the recorded commitment.

28. The computer-readable medium as recited in claim 21, wherein said step of receiving the conference request further comprises the step of receiving conference priority data that indicates an importance to the organization that the particular conference is held.

29. The computer-readable medium as recited in claim 28, said step of determining the proposed time interval for the particular conference further comprising the steps of:

determining a person whose recorded commitment blocks the particular conference;

determining a priority of the recorded commitment based on the priority data;

determining a priority of the particular conference based on the conference priority data;

determining whether the priority of the recorded commitment is lower than the priority of the particular conference; and

if it is determined that the priority of the recorded commitment is lower than the priority of the particular conference, then breaking the recorded commitment to render the person available for the conference.

30. The computer-readable medium as recited in claim 21, said step of receiving the quorum data further comprising receiving quorum data that indicates that the quorum for the particular conference includes a minimum number of persons in a first group of persons of the population plurality of persons and less than all persons from the first group of persons, whereby the first group is a representative group of persons.

31. The computer-readable medium as recited in claim 21, said step of receiving the limit data further comprising receiving limit data that indicates that said property of the particular conference includes at least one of a date, a time of day, a location, a common language, and a travel cost.

32. The computer-readable medium as recited in claim 28, said step of determining the proposed time interval for the particular conference further comprising the steps of:

determining whether a conflict exists that blocks the particular conference; and

if it is determined that a conflict does not exist, then associating the priority of the particular conference with an invitation to attend the particular conference at the proposed time.

33. The computer-readable medium as recited in claim 32, wherein execution of the one or more sequences of instructions further causes the one or more processors to perform the steps of

receiving a commitment to attend the particular conference from a person whose attendance satisfies the quorum;

and

storing the priority of the particular conference in association with availability data that indicates the commitment to attend the particular conference by the person whose attendance satisfies the quorum.

34. An apparatus for scheduling a conference among multiple persons, comprising:

means for receiving a conference request to schedule a particular conference by receiving quorum data that indicates a quorum of persons to conduct the particular conference and receiving limit data that indicates a limit on a property of the particular conference;

means for receiving availability data from a shared database that includes information about a recorded commitment of time for each person of a population plurality of persons that includes all persons indicated in the quorum data;

means for receiving priority data that indicates an importance to an organization that a particular recorded commitment of a particular person of the population plurality of persons is honored; and

means for determining a proposed time interval for the particular conference based on the conference request and the availability data and the priority data.

35. An apparatus for scheduling a conference among multiple persons, comprising:

a network interface that is coupled to a network for communicating one or more packet flows therewith;

one or more processors; and

one or more stored sequences of instructions which, when executed by the one or more processors, cause the one or more processors to carry out the steps of;

receiving a conference request to schedule a particular conference by receiving quorum data that indicates a quorum of persons to conduct the particular conference and receiving limit data that indicates a limit on a property of the particular conference;

receiving availability data from a shared database that includes information about a recorded commitment of time for each person of a population plurality of persons that includes all persons indicated in the quorum data;

receiving priority data that indicates an importance to an organization that a particular recorded commitment of a particular person of the population plurality of persons is honored; and

determining a proposed time interval for the particular conference based on the conference request and the availability data and the priority data.

36. The apparatus as recited in claim 35, said step of receiving availability data further comprising receiving at least one of scheduled availability data based on data in a shared calendar database and current availability data based on presence data.

37. The apparatus as recited in claim 35, said step of receiving priority data further comprising receiving priority data based on data in a shared calendar database.

38. The apparatus as recited in claim 35, said step of determining the proposed time interval for the particular conference further comprising the steps of:

determining a conflicted person whose recorded commitment blocks the particular conference;

determining a priority of the recorded commitment based on the priority data;

determining whether the priority of the recorded commitment is lower than a priority of the particular conference; and

if it is determined that the priority of the recorded commitment is lower than the priority of the particular conference, then rendering the conflicted person available for the particular conference during a time interval of the recorded commitment.

39. The apparatus as recited in claim 38, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving echelon data that indicates whether a first organizer of the particular conference is at a higher echelon in the organization than is a second organizer for the recorded commitment.

40. The apparatus as recited in claim 38, said step of determining the priority of the recorded commitment further comprises determining the priority of the recorded commitment based on a highest echelon of all attendees of a second conference corresponding to the recorded commitment.

41. The apparatus as recited in claim 40, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving echelon data that indicates whether an attendee of the particular conference is at a higher echelon in the organization than are all attendees of the second conference.

42. The apparatus as recited in claim 39, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving input data indicating whether the first organizer has determined that the priority of the recorded commitment is lower than the priority of the particular conference.

43. The apparatus as recited in claim 38, said step of determining whether the priority of the recorded commitment is lower than the priority of the particular conference further comprises the step of receiving data indicating whether a priority associated with a token obtained by an organizer of the particular conference from a member of a higher echelon than the organizer is greater than the priority of the recorded commitment.

44. The apparatus as recited in claim 38, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to carry out the steps of:

determining whether the conflicted person becomes committed to the particular conference; and

if it is determined that the conflicted person becomes committed to the particular conference, then alerting an organizer for the recorded commitment that the conflicted person is breaking the recorded commitment.

45. The apparatus as recited in claim 35, said step of receiving the conference request further comprises the step of receiving conference priority data that indicates an importance to the organization that the particular conference is held.

46. The apparatus as recited in claim 45, said step of determining the proposed time interval for the particular conference further comprising the steps of:

determining a person whose recorded commitment blocks the particular conference;

determining a priority of the recorded commitment based on the priority data;

determining a priority of the particular conference based on the conference priority data;

determining whether the priority of the recorded commitment is lower than the priority of the particular conference; and

if it is determined that the priority of the recorded commitment is lower than the priority of the particular conference, then rendering the person available for the particular conference during a time interval of the recorded commitment.

47. The apparatus as recited in claim 35, said step of receiving the quorum data further comprising receiving quorum data that indicates that the quorum for the particular conference includes a minimum number of persons in a first group of persons of the population plurality of persons and less than all persons from the first group of persons, whereby the first group is a representative group of persons.

48. The apparatus as recited in claim 35, said step of receiving the quorum data further comprising receiving quorum data that indicates no person at an echelon in the organization which is higher by more than a particular difference above a conference echelon obtained by an organizer of the particular conference.

49. The apparatus as recited in claim 48, said step of receiving the quorum data further comprising receiving quorum data that indicates a conference echelon obtained by an organizer of the particular conference is the same as an echelon of the organizer.

50. The apparatus as recited in claim 48, said step of receiving the quorum data further comprising receiving quorum data that indicates a conference echelon obtained by an organizer of the particular conference is greater than an echelon of the organizer.

51. The apparatus as recited in claim 35, said step of receiving the limit data further comprising receiving limit data that indicates that said property of the particular conference includes at least one of a date, a time of day, a location, a common language, and a travel cost.

52. The apparatus as recited in claim 45, said step of determining the proposed time interval for the particular conference further comprising the steps of:

determining whether a conflict exists that blocks the particular conference; and

if it is determined that a conflict does not exist, then associating the priority of the particular conference with an invitation to attend the particular conference at the proposed time.

53. The apparatus as recited in claim 52, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to carry out the steps of:

receiving a commitment to attend the particular conference from a person whose attendance satisfies the quorum; and

storing the priority of the particular conference in association with availability data that indicates the commitment to attend the particular conference by the person whose attendance satisfies the quorum.