In-meeting graphical user interface display using calendar information and system

• US 10,592,867 B2
• Filed: 11/11/2016
• Issued: 03/17/2020
• Est. Priority Date: 11/11/2016
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Rosenberg, Jonathan
• Primary Examiner(s): Harrell, Robert B
• Application Number:
  US15/349,818
• Publication Number:
  US 20180139246A1
• Time in Patent Office: 1,222 Days
• Field of Search: 348 1403, 348 1408, 709206, 379158, 37920201
• CPC Class Codes: G06Q 10/1095 Meeting or appointment
• 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
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15

Abstract

A meeting application can gather calendar information from a calendaring service, even if that calendaring service is independent from (e.g., a “third party to”) the meeting service. The meeting application can incorporate the calendar information into an in-meeting graphical user interface so that the calendar information can be displayed with the meeting. In some embodiments, this includes listing all invitees and participants alongside their associated acceptance status (e.g., are they present, did they accept, did they decline, etc.). In some embodiments, the calendar information can inform a meeting timer that can indicate the remaining time for the meeting. In some embodiments, the calendar information can inform individual timers that indicate how much time individual participants have before their next appointment.

Claims

1. A non-transitory computer-readable medium comprising computer executable instructions stored thereon, the instructions when executed are effective to cause a computer to:

display, via a display, a meeting-in-progress graphical user interface for a meeting hosted by a meeting application, the graphical user interface including a roster of invited meeting participants based on an acceptance status for each of the invited meeting participants, the roster including a first listing of any present ones of the invited meeting participants, a second listing of any accepted ones of the invited meeting participants, and a third listing of any declined ones of the invited meeting participants,

wherein,

at least one of the first listing, the second listing, or the third listing of the acceptance status includes a first menu of available actions for a first grouping of the invited meeting participants,

another one of the first listing, the second listing, or the third listing of the acceptance status includes a second menu of available actions for a second grouping of the invited meeting participants, and

selection of one or more actions in the first menu of available actions or the second menu of available actions causes the one or more actions to be executed for every participant listed in a corresponding one of the first grouping of the invited meeting participants or the second grouping of the invited meeting participants.

2. The computer-readable medium of claim 1, wherein the meeting-in-progress graphical user interface includes a contact-participant user interface object, the contact-participant user interface object being effective to receive a selection of the contact-participant user interface object, and after receipt of the selection, contact one or more of the invited meeting participants.

3. The computer-readable medium of claim 2, wherein the instructions are effective to cause the computer to automatically contact one or more of the invited meeting participants by:

creating an instant message using an instant message application and delivering the instant message to the one or more of the invited meeting participants.

4. The computer-readable medium of claim 2, wherein the instructions are effective to cause the computer to contact one or more of the invited meeting participants by:

prompting a user to enter a message to create an instant message using an instant message application and delivering the instant message to the one or more of the invited meeting participants.

5. The computer-readable medium of claim 1,

wherein,

the first menu of available actions includes a first plurality of interaction options,

the first plurality of interaction options includes mute, email, and instant message,

the second menu of available actions includes a second plurality of interaction options,

the second plurality of interaction options includes call to join and remind via calendar,

the first menu includes at least one action not listed via the second menu, and

the first menu is displayed at a different time than the second menu.

6. The computer-readable medium of claim 1, wherein the meeting-in-progress graphical user interface includes a contact-participant user interface object next to the meeting participants organized into the accepted status, wherein an accepted status means that the participant has accepted a meeting invitation but has not joined the meeting, the contact-participant user interface object being effective to contact the meeting participants organized into the accepted status.

7. The computer-readable medium of claim 1, wherein the instructions are effective to cause the computer to:

retrieve the roster of invited meeting participants and the acceptance status for each of the invited meeting participants through a request to an API of a calendaring service.

8. The computer-readable medium of claim 1, wherein the instructions are effective to cause the computer to:

receive one or more notifications from a calendaring service, the one or more notifications comprising one or more of the roster of invited meeting participants and the acceptance status for each of the invited meeting participants.

9. The computer-readable medium of claim 1, wherein the meeting-in-progress graphical user interface for the meeting application is configured to display a meeting timer, the meeting timer displaying an amount of time left in the meeting, the amount of time left in the meeting being calculated by:

receiving a scheduled meeting time from a calendaring service and determining the remaining amount of time until an end of the scheduled meeting time.

10. A system comprising:

a processor;

a display; and

memory including instructions that when executed by the processor, cause the system to;

display, via the display, a meeting-in-progress graphical user interface for a meeting hosted by a meeting application, the graphical user interface including a roster of invited meeting participants based on an acceptance status for each of the invited meeting participants, the roster including a first listing of any present ones of the invited meeting participants, a second listing of any accepted ones of the invited meeting participants, and a third listing of any declined ones of the invited meeting participants,

wherein,

at least one of the first listing, the second listing, or the third listing of the acceptance status includes a first menu of available actions for a first grouping of the invited meeting participants,

another one of the first listing, the second listing, or the third listing of the acceptance status includes a second menu of available actions for a second grouping of the invited meeting participants, and

selection of one or more actions in the first menu of available actions or the second menu of available actions causes the one or more actions to be executed for every participant listed in a corresponding one of the first grouping of the invited meeting participants or the second grouping of the invited meeting participants.

11. The system of claim 10, wherein the meeting-in-progress graphical user interface includes a contact-participant user interface object, the contact-participant user interface object being effective to receive a selection of the contact-participant user interface object, and after receipt of the selection, contact one or more of the invited meeting participants.

12. The system of claim 11, wherein the instructions are effective to cause the system to automatically contact one or more of the invited meeting participants by:

creating an instant message using an instant message application and delivering the instant message to the one or more of the invited meeting participants.

13. The system of claim 11, wherein the instructions are effective to cause the system to contact one or more of the invited meeting participants by:

prompting a user to enter a message to create an instant message using an instant message application and delivering the instant message to the one or more of the invited meeting participants.

14. The system of claim 10,

wherein,

the first menu of available actions includes a first plurality of interaction options,

the first plurality of interaction options includes mute, email, and instant message,

the second menu of available actions includes a second plurality of interaction options,

the second plurality of interaction options includes call to join and remind via calendar,

the first menu includes at least one action not listed via the second menu, and

the first menu is displayed at a different time than the second menu.

15. The system of claim 10, wherein the meeting-in-progress graphical user interface includes a contact-participant user interface object next to the meeting participants organized into the accepted status, wherein an accepted status means that the participant has accepted a meeting invitation but has not joined the meeting, the contact-participant user interface object being effective to contact the meeting participants organized into the accepted status.

16. The system of claim 10, wherein the instructions are effective to cause the system to:

retrieve the roster of invited meeting participants and the acceptance status for each of the invited meeting participants through a request to an API of a calendaring service.

17. The system of claim 10, wherein the instructions are effective to cause the system to:

receive one or more notifications from a calendaring service, the one or more notifications comprising one or more of the roster of invited meeting participants and the acceptance status for each of the invited meeting participants.

18. The system of claim 10, wherein the meeting-in-progress graphical user interface for the meeting application is configured to display a meeting timer, the meeting timer displaying an amount of time left in the meeting, the amount of time left in the meeting being calculated by:

receiving a scheduled meeting time from a calendaring service and determining the remaining amount of time until an end of the scheduled meeting time.

19. A method comprising:

displaying, via a display, a meeting-in-progress graphical user interface for a meeting hosted by a meeting application, the graphical user interface including a roster of invited meeting participants based on an acceptance status for each of the invited meeting participants, the roster including a first listing of any present ones of the invited meeting participants, a second listing of any accepted ones of the invited meeting participants, and a third listing of any declined ones of the invited meeting participants,

wherein,

at least one of the first listing, the second listing, or the third listing of the acceptance status includes a first menu of available actions for a first grouping of the invited meeting participants,

another one of the first listing, the second listing, or the third listing of the acceptance status includes a second menu of available actions for a second grouping of the invited meeting participants, and

selection of one or more actions in the first menu of available actions or the second menu of available actions causes the one or more actions to be executed for every participant listed in a corresponding one of the first grouping of the invited meeting participants or the second grouping of the invited meeting participants.

20. The method of claim 19, wherein the meeting-in-progress graphical user interface includes a contact-participant user interface object, the contact-participant user interface object being effective to receive a selection of the contact-participant user interface object, and after receipt of the selection, contact one or more of the invited meeting participants.

21. The method of claim 20, further comprising, automatically contacting one or more of the invited meeting participants by:

creating an instant message using an instant message application and delivering the instant message to the one or more of the invited meeting participants.

22. The method of claim 20, further comprising contacting one or more of the invited meeting participants by:

prompting a user to enter a message to create an instant message using an instant message application and delivering the instant message to the one or more of the invited meeting participants.

23. The method of claim 19,

wherein,

the first menu of available actions includes a first plurality of interaction options,

the first plurality of interaction options includes mute, email, and instant message,

the second menu of available actions includes a second plurality of interaction options,

the second plurality of interaction options includes call to join and remind via calendar,

the first menu includes at least one action not listed via the second menu, and

the first menu is displayed at a different time than the second menu.

24. The method of claim 19, wherein the meeting-in-progress graphical user interface includes a contact-participant user interface object next to the meeting participants organized into the accepted status, wherein an accepted status means that the participant has accepted a meeting invitation but has not joined the meeting, the contact-participant user interface object being effective to contact the meeting participants organized into the accepted status.

25. The method of claim 19, further comprising:

retrieving the roster of invited meeting participants and the acceptance status for each of the invited meeting participants through a request to an API of a calendaring service.

26. The method of claim 19, further comprising:

receiving one or more notifications from a calendaring service, the one or more notifications comprising one or more of the roster of invited meeting participants and the acceptance status for each of the invited meeting participants.