INTEGRATION OF PRE-MEETING AND POST-MEETING EXPERIENCE INTO A MEETING LIFECYCLE

• US 20100235216A1
• Filed: 03/16/2009
• Published: 09/16/2010
• Est. Priority Date: 03/16/2009
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bhattacharjee, Avronil, Hehmeyer, Alexander M., Gupta, Amit, Zybura, John H., Wong, Felix W.
• Application Number:
  US12/404,356
• Publication Number:
  US 20100235216A1
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

Architecture that synchronizes meeting information (e.g., documents, agenda, action items, notes, attendees, join information, etc.) across the different stages of a meeting lifecycle. The architecture provides client-side synchronization across meeting lifecycle services that can include a scheduling server, content management server, and meeting server, as well as other lifecycle servers that may be employed. Information from the scheduling server can be written asynchronously to the other lifecycle servers, updates made to the content management server are synchronized to the other servers, and updates made to the meeting server are synchronized to the other servers.

Claims

1. A computer-implemented meeting lifecycle framework, comprising:

meeting lifecycle components for generating and processing meeting information associated with multiple stages of a meeting lifecycle; and

a synchronization component for automatically synchronizing the meeting information among one or more of the lifecycle components.

2. The framework of claim 1, wherein the lifecycle components include at least two of a scheduling component, a meeting component, or a content management component, the combination of which provide a seamless end-to-end user experience during the meeting lifecycle.

3. The framework of claim 2, wherein the synchronization component is associated with at least one of a client application of the scheduling component, a client application of the meeting component, or a client application of the content management component, one or more of the clients that synchronize the meeting information to all of the lifecycle components.

4. The framework of claim 1, wherein the multiple stages include scheduling, pre-meeting, joining, in-meeting, and post-meeting.

5. The framework of claim 1, wherein the synchronization component is part of a client, the synchronization component enqueues data for synchronization when the client goes offline and completes synchronization of the data when the client goes online.

6. The framework of claim 1, further comprising a user interface component for accessing and presenting the meeting information associated with the multiple stages.

7. The framework of claim 1, wherein the lifecycle components include a meeting component for creating and storing a meeting recording and, a content management component for storage and playback of the meeting recording.

8. The framework of claim 1, wherein the lifecycle components include a scheduling component for synchronizing permissions for a meeting invitation.

9. The framework of claim 1, wherein the synchronization to one of the lifecycle components automatically initiates synchronization to the remaining lifecycle components.

10. A computer-implemented meeting lifecycle framework, comprising:

meeting lifecycle components for generating and processing meeting information associated with multiple stages of a meeting lifecycle;

a client-based synchronization component for automatically synchronizing the meeting information among one or more of the lifecycle components; and

a user interface component for accessing and presenting the meeting information as a seamless end-to-end meeting experience associated with the multiple stages.

11. The framework of claim 10, wherein the lifecycle components include a meeting component for creating and storing a meeting recording, a content management component for storage and playback of the meeting recording, and a scheduling component for synchronizing permissions for a meeting invitation.

12. The framework of claim 10, wherein the multiple stages include a scheduling stage, a pre-meeting stage, a joining stage, an in-meeting stage, and a post-meeting stage, and the lifecycle components include a scheduling component, a meeting component, or a content management component, the lifecycle components interacting during the stages to create, update, and store the meeting information throughout the stages.

13. The framework of claim 10, wherein the synchronization of the meeting information to one of the lifecycle components automatically initiates synchronization of portions of the meeting information to one or more of other lifecycle components.

14. The framework of claim 10, wherein the lifecycle components include a content management component for presenting aspects of the meeting that are interesting based on a stage of the lifecycle framework.

15. A computer-implemented meeting lifecycle method, comprising:

preparing and conducting a meeting according to different stages of a meeting lifecycle;

generating and managing meeting information during the meeting lifecycle using lifecycle servers; and

synchronizing the meeting information among the lifecycle servers.

16. The method of claim 15, further comprising presenting relevant data of the meeting information during a stage of the meeting lifecycle.

17. The method of claim 15, wherein the meeting information is synchronized among the lifecycle servers via a client application associated with one of the lifecycle servers.

18. The method of claim 15, further comprising linking a content management server to a scheduling server to update invitation text.

19. The method of claim 15, further comprising storing and playing back a meeting recording during a stage of the meeting lifecycle.

20. The method of claim 15, further comprising synchronizing permissions for a meeting invitation among the lifecycle servers.