Methods and systems for pausing and resuming a meeting session

1. A method comprising:

creating meeting-session data based at least in part on one or more applications running on one or more devices connected to a meeting session, wherein the meeting-session data comprises one or more device IDs corresponding to the one or more devices, and further wherein the meeting-session data comprises data linking the one or more applications to the one or more device IDs;

storing the meeting-session data in a database;

pausing the meeting session, wherein pausing the meeting session comprises disconnecting the one or more devices from the meeting session; and

resuming the meeting session, wherein resuming the meeting session comprises:

configuring at least one of the one or more devices to run at least one of the one or more applications using the meeting-session data; and

joining the configured devices to the resumed meeting session.

2. The method of claim 1 , wherein the meeting-session data is further created based at least in part on a state of the one or more applications running on the one or more devices connected to the meeting session.

3. The method of claim 2 , wherein the meeting-session data is further created based at least in part on a meeting-session ID.

4. The method of claim 2 , wherein the meeting-session data is further created based at least in part on a version ID of a file open in at least one of the one or more applications, wherein configuring at least one of the one or more devices when resuming the meeting session further comprises:

loading a version of the file corresponding to the version ID; and

running the one or more applications in the state of the one or more applications prior to, or during, the pausing of the meeting session.

5. The method of claim 1 , wherein the meeting-session data is further created based at least in part on data acquired at a plurality of different times during the meeting session, wherein resuming the meeting session further comprises:

providing the configured devices with context information created by analyzing changes in the meeting-session data over time.

6. The method of claim 1 , wherein resuming the meeting session further comprises:

providing the one or more devices with a notification that the meeting session is being resumed; and

enabling the one or more devices to determine whether to join the resumed meeting session.

7. The method of claim 1 , further comprising:

detecting a predetermined change in location of at least one of the one or more devices and, responsive thereto, pausing of the meeting session.

8. A device comprising:

one or more processors;

one or more memories;

program code stored on the one or more memories, which, when executed by the one or more processors, cause the device to perform a method of:

creating meeting-session data based at least in part on one or more applications running on one or more devices connected to a meeting session, wherein the meeting-session data comprises one or more device IDs corresponding to the one or more devices, and further wherein the meeting-session data comprises data linking the one or more applications to the one or more device IDs;

storing the meeting-session data in a database;

pausing the meeting session, wherein pausing the meeting session comprises disconnecting the one or more devices from the meeting session; and

resuming the meeting session, wherein resuming the meeting session comprises:

configuring at least one of the one or more devices to run at least one of the one or more applications using the meeting-session data; and

joining the configured devices to the resumed meeting session.

9. The device claim 8 , wherein the meeting-session data is further created based at least in part on a state of the one or more applications running on the one or more devices connected to the meeting session.

10. The device of claim 9 , wherein the meeting-session data is further created based at least in part on a meeting-session ID.

11. The device of claim 9 , wherein the meeting session data is further created based at least in part on a version ID of a file open in at least one of the one or more applications, wherein configuring at least one of the one or more devices when resuming the meeting session further comprises:

loading a version of the file corresponding to the version ID; and

running the one or more applications in the state of the one or more applications prior to, or during, the pausing of the meeting session.

12. The device of claim 8 , wherein the meeting-session data is further created based at least in part on data acquired at a plurality of different times during the meeting session, wherein resuming the meeting session further comprises:

providing the configured devices with context information created by analyzing changes in the meeting-session data over time.

13. The device of claim 8 , wherein resuming the meeting session further comprises:

providing the one or more devices with a notification that the meeting session is being resumed; and

enabling the one or more devices to determine whether to join the resumed meeting session.

14. The device of claim 8 , further comprising program code operable, when executed by one or more processors, to perform:

detecting a predetermined change in location of at least one of the one or more devices and, responsive thereto, performing the pausing of the meeting session.

15. A device comprising:

one or more processors configured to execute modules; and

one or more memories storing the modules, the modules comprising:

a data storage and retrieval module configured to communicate with a database;

a state monitoring module configured to monitor one or more applications; and

a control module configured to communicate with the data storage and retrieval module and the state monitoring module, and to:

create meeting-session data based at least in part on the one or more applications running on one or more devices connected to a meeting session, wherein the meeting-session data comprises one or more device IDs corresponding to the one or more devices, and further wherein the meeting-session data comprises data linking the one or more applications to the one or more device IDs;

store the meeting-session data in the database;

pause the meeting session, wherein pausing the meeting session comprises disconnecting the one or more devices from the meeting session; and

resume the meeting session, wherein resuming the meeting session comprises:

configuring at least one of the one or more devices to run at least one of the one or more applications using the meeting-session data; and

joining the configured devices to the resumed meeting session.

16. The device of claim 15 , wherein the meeting-session data is further created based at least in part on a state of the one or more applications running on the one or more devices connected to the meeting session.

17. The device of claim 16 , wherein the meeting session data is further created based at least in part on a version ID of a file open in at least one of the one or more applications, wherein configuring at least one of the one or more devices when resuming the meeting session further comprises:

loading a version of the file corresponding to the version ID; and

running the one or more applications in the state of the one or more applications prior to, or during, the pausing of the meeting session.

18. The device of claim 15 , wherein the meeting-session data is further created based at least in part on data acquired at a plurality of different times during the meeting session, wherein resuming the meeting session further comprises:

providing the configured devices with context information created by analyzing changes in the meeting-session data over time.

19. The device of claim 15 , wherein resuming the meeting session further comprises:

providing the one or more devices with a notification that the meeting session is being resumed; and

enabling the one or more devices to determine whether to join the resumed meeting session.

20. The device of claim 15 , wherein the control module is further configured to:

detect a predetermined change in location of at least one of the one or more devices and, responsive thereto, pause the meeting session.