Federated scheduling method and system

• US 20060277282A1
• Filed: 06/02/2005
• Published: 12/07/2006
• Est. Priority Date: 06/02/2005
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Sundstrom, Robert J., Stern, Edith H., Christensen, James E., Levy, Stephen E., Sussman, Jeremy
• Application Number:
  US11/143,694
• Publication Number:
  US 20060277282A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

Disclosed above is a system and method for coordinating the exchange of information about an event. Specifically, the invention incorporates the use of a federated broker in the form of either a monolithic server or a network of servers for exchanging of information about an event between two or more entities. The broker is adapted to receive information about an event, including up-dates and presentation material, store the information and disseminate the information to other interested entities. Communication between the broker and the two entities is via a contact. For those entities maintaining a calendar system, the contact functions as an interchange agent that facilitates communications between the calendar system of the entity and the server. This interchange agent may be an automated mechanism.

Claims

1. A system for coordinating an exchange of information about an event, said system comprising:

a server in communication with a first contact of a first entity and a second contact of a second entity, wherein at least one of said first entity and said second entity maintains a calendar system which is in communication with said server via a corresponding one of said first contact and said second contact, and wherein said server comprises;

a receiver that is adapted to receive an initial indication of said event containing said information about said event from said first entity;

a processor, wherein said processor is adapted to review said information in order to identify said second entity and to determine a first contact address for said first contact and a second contact address for said second contact and wherein said processor is further adapted to associate said event with an event identifier;

a data storage device adapted for storing said information such that said information is retrievable by reference to said event identifier; and

a transmitter adapted to disseminate said information, including a reference to said event identifier, to said second contact address.

2. The system of claim 1, wherein said transmitter is further adapted to send to said first contact address an acknowledgement with a reference to said event identifier.

3. The system of claim 1, wherein said receiver is further adapted to receive additional information about said event from at least one of said first entity and said second entity,

wherein said data storage device is further adapted to store said additional information, and

wherein said transmitter is further adapted to disseminate said additional information, including said reference to said event identifier.

4. The system of claim 3, wherein said information about said event and said additional information about said event comprise at least one of a time, a date, a location, a conference call number, a session initiation protocol uniform resource locator, a list of at least two entities with an interest in said event, a list of attendees of said event, presentation material for said event, resources available for said event, and an agenda for said event.

5. The system of claim 4, wherein said processor is further adapted:

to identify an entity-specific identifier assigned to said event by one of said first entity and said second entity,

to associate said entity-specific identifier with said event identifier, and

to cross-reference said entity-specific identifier with said event identifier, when said additional information is received by said receiver with a reference to said entity-specific identifier and without a reference to said event identifier.

6. The system of claim 5, wherein said transmitter is further adapted to return an error message to said one of said first entity and said second entity, when said additional information is received without reference to said entity-specific identifier and without reference to said event identifier.

7. The system of claim 4, wherein said processor is further adapted to identify conflicts between said information in said initial indication and said additional information, and wherein said transmitter is further adapted to send an indication of said conflicts to at least one of said first entity and said second entity.

8. The system of claim 1, wherein one of said first entity and said second entity maintains said server such that communication with said server is coordinated via a corresponding one of said first contact and said second contact.

9. A system for coordinating an exchange of information about an event, said system comprising:

a set of servers in communication with a first contact of a first entity and a second contact of a second entity, wherein at least one of said first entity and said second entity maintains a calendar system which is in communication with said set of servers via a corresponding one of said first contact and said second contact and wherein said set of servers comprises;

at least one receiver adapted to receive an initial indication of said event containing said information about said event from said first entity;

at least one processor, wherein said processor is adapted to review said information in order to identify said second entity and to determine a first contact address for said first contact and a second contact address for said second contact, and wherein said processor is further adapted to associate said event with an event identifier;

at least one data storage device adapted for storing said information such that said information is retrievable by reference to said event identifier; and

at least one transmitter adapted to disseminate said information, including a reference to said event identifier, to said second contact address.

10. The system of claim 9, wherein said transmitter is further adapted to send to said first contact address an acknowledgement with a reference to said event identifier.

11. The system of claim 9, wherein said receiver is further adapted for receiving additional information about said event from one of said first entity and said second entity, wherein said data storage device is further adapted for storing said additional information, and wherein said transmitter is further adapted to disseminate said additional information, with said reference to said event identifier.

12. The system of claim 11, wherein said information about said event and said additional information about said event comprise at least one of a time, a date, a location, a conference call number, a session initiation protocol uniform resource locator, a list of at least two entities with an interest in said event, a list of attendees of said event, presentation material for said event, resources available for said event, and an agenda for said event.

13. The system of claim 11, wherein said processor is further adapted:

to identify an entity-specific identifier assigned to said event by one of said first entity and said second entity,

to associate said entity-specific identifier with said event identifier, and

to cross-reference said entity-specific identifier with said event identifier, when said additional information is received by said receiver with a reference to said entity-specific identifier and without a reference to said event identifier.

14. The system of claim 13, wherein said transmitter is further adapted to return an error message to said one of said first entity and said second entity, when said additional information is received without reference to said entity-specific identifies and without reference to said event identifier.

15. The system of claim 11, wherein said processor is further adapted to identify conflicts between said information in said initial indication and said additional information, and

wherein said transmitter is further adapted to send an indication of said conflicts to said first entity and said second entity.

16. The system of claim 11, wherein at least one server of said set of servers is maintained by at least one of said first entity and said second entity such that communication with said one server is coordinated via a corresponding one of said first contact and said second contact.

21. The method of claim 15, further comprising:

identifying an entity-specific identifier assigned to said event by one of said first entity and said second entity;

associating said entity-specific identifier with said event identifier; and

wherein said additional information is received with a reference to said entity-specific identifier and without a reference to said event identifier, cross-referencing said entity-specific identifier with said event identifier.

22. The method of claim 21, further comprising when said additional information is received without reference to said entity-specific identifier and without reference to said event identifier, returning an error message to said one of said first entity and said second entity.

17. A method for coordinating an exchange of information about an event, said method comprising:

receiving an initial indication of said event containing said information about said event from a first entity,

reviewing said information to identify a second entity,

determining a first contact and a first contact address for said first entity and a second contact and a second contact address for said second entity in order to communicate with said first entity and said second entity;

associating said event with an event identifier;

storing said information such that said information is retrievable by reference to said event identifier; and

disseminating said information, including a reference to said event identifier, to said second contact address,

wherein at least one of said first entity and said second entity maintains a calendar system and wherein communication with said calendar system is via a corresponding one of said first contact and said second contact.

18. The method of claim 17, further comprising sending an acknowledgement, which references said event identifier, to said first contact address.

19. There method of claim 17, further comprising:

receiving additional information about said event from one of said first entity and said second entity;

storing said additional information; and

disseminating said additional information, including said reference to said event identifier.

20. The method of claim 19, wherein said information and said additional information about said event comprise at least one of a time, a date, a location, a conference call number, a session initiation protocol uniform resource locator, a list of at least two entities with an interest in said event, a list of attendees of said event, presentation material for said event, resources available for said event, and an agenda for said event.

23. The method of claim 19, further comprising:

identifying conflicts between said information in said initial indication and said additional information; and

sending a notification of said conflicts to said first entity and said second entity.

24. A method for coordinating an exchange of information about an event, said method comprising:

receiving within a set of servers an initial indication of said event containing said information about said event from a first entity,

reviewing said information to identify a second entity,

determining a first contact and a first contact address for said first entity and a second contact and a second contact address for said second entity in order to communicate with said first entity and said second entity;

associating said event with an event identifier;

storing said information within said set of servers such that said information is retrievable by reference to said event identifier; and

disseminating said information, with a reference to said event identifier, to said second contact address,

wherein at least one of said first entity and said second entity maintains a calendar system and wherein communication with said calendar system is via a corresponding one of said first contact and said second contact.

25. The method of claim 24, further comprising sending an acknowledgement, which references said event identifier, to said first contact address.

26. There method of claim 24, further comprising:

receiving within said set of servers additional information about said event from one of said first entity and said second entity;

storing said additional information; and

disseminating said additional information with said reference to said event identifier.

27. The method of claim 26, wherein said information and said additional information about said event comprise at least one of a time, a date, a location, a conference call number, a session initiation protocol uniform resource locator, a list of entities with an interest in said event, a list of attendees of said event, presentation material for said event, resources available for said event, and an agenda for said event.

28. The method of claim 26, further comprising:

identifying an entity-specific identifier assigned to said event by one of said first entity and said second entity;

associating said entity-specific identifier with said event identifier; and

wherein said additional information is received with a reference to said entity-specific identifier and without a reference to said event identifier, cross-referencing said entity-specific identifier with said event identifier.

29. The method of claim 28, further comprising when said additional information is received without reference to said entity-specific identifier and without reference to said event identifier, returning an error message to said one of said first entity and said second entity.

30. The method of claim 26, further comprising:

identifying conflicts between said information in said initial indication and said additional information; and

sending a notification of said conflicts to said first entity and said second entity.