Converting Scheduling Information into Different Conferencing Domains

• US 20160247123A1
• Filed: 02/24/2015
• Published: 08/25/2016
• Est. Priority Date: 02/24/2015
• Status: Abandoned Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Holst, Magnus Aaen, Grdum, Nicolai
• Application Number:
  US14/629,716
• Publication Number:
  US 20160247123A1
• Time in Patent Office: Days
• US Class Current: 1/1
• 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: H04M 2201/14 Delay circuits; Timers
• CPC Class Codes: H04M 2203/5054 Meet-me conference, i.e. participants dial-in
• CPC Class Codes: H04M 3/565 relating to time schedule aspects

Abstract

A user device that is capable of scheduling a meeting or receiving an invitation to a meeting, generates a meeting join link for a scheduled virtual meeting. A meeting calendar identifier for the scheduled virtual meeting is retrieved. A meeting join link for the scheduled virtual meeting is generated based on the meeting calendar identifier. Thereafter, the user device may user the meeting join link to join the scheduled virtual meeting. The user device connects to a server that joins/connects the user device to the scheduled virtual meeting based on the meeting join link.

Claims

1. A computer-implemented method comprising:

in a user device capable of scheduling a meeting or receiving an invitation to a meeting;

retrieving a meeting calendar identifier for a scheduled virtual meeting; and

generating based on the meeting calendar identifier a meeting join link that is associated with the scheduled virtual meeting.

2. The method of claim 1, wherein retrieving comprises retrieving a meeting organizer identifier associated with the scheduled virtual meeting, and generating is based further on the meeting organizer identifier.

3. The method of claim 1, further comprising the user device communicating with a server using the meeting join link to be connected by server to the virtual meeting that is associated with the meeting join link.

4. The method of claim 1, wherein the meeting join link is a Uniform Resource Identifier (URI) of any URI scheme.

5. The method of claim 4, wherein the meeting join link is a URI with a scheme for the Session Initiation Protocol (SIP).

6. The method of claim 4, wherein the meeting join link is a URI with a scheme for the Hypertext Transport Protocol (HTTP).

7. The method of claim 4, wherein the meeting join link is a URI with a scheme for the Hypertext Transport Protocol Secure (HTTPS).

8. The method of claim 1, wherein the meeting calendar identifier is an identifier compliant with the iCalendar standard of RFC 5545.

9. The method of claim 1, wherein the generating is performed using a predetermined procedure on each of a plurality of user devices that are to participate in the scheduled virtual meeting using the meeting calendar identifier for the scheduled virtual meeting so that each of the plurality of user devices can generate the same one or more meeting join links associated with the scheduled virtual meeting using the predetermined procedure.

10. The method of claim 1, wherein generating comprises generating a plurality of meeting join links each associated with the scheduled virtual meeting, each of the plurality of meeting join links for a different communication protocol by which the scheduled virtual meeting can be joined.

11. A method comprising:

at each of a plurality of user devices capable of scheduling a meeting or receiving an invitation to a meeting;

retrieving a meeting calendar identifier for a scheduled virtual meeting; and

generating based on the meeting calendar identifier a meeting join link that is associated with the scheduled virtual meeting;

at a server;

receiving a communication from a particular user device of the plurality of user devices, the communication made using the meeting join link;

determining whether the scheduled virtual meeting for the meeting join link has already been activated;

if it is determined that the scheduled virtual meeting has not yet been activated, activating the scheduled virtual meeting and connecting the particular user device into the scheduled virtual meeting; and

if it is determined that the scheduled virtual meeting has already been activated, connecting the particular user device into the scheduled virtual meeting that has already been activated.

12. The method of claim 11, wherein the generating is performed using a predetermined procedure on each of the plurality of user devices that are to participate in the scheduled virtual meeting using the meeting calendar identifier for the scheduled virtual meeting so that each of the plurality of user devices can generate the same one or more meeting join links associated with the scheduled virtual meeting using the predetermined procedure.

13. The method of claim 11, wherein retrieving further comprises retrieving a meeting organizer identifier associated with the scheduled virtual meeting, and generating is based further on the meeting organizer identifier.

14. The method of claim 11, wherein the meeting join link includes is a Uniform Resource Identifier (URI) of any URI scheme.

15. The method of claim 11, wherein the meeting join link points to a domain of the server.

16. The method of claim 11, wherein the meeting join link points to a domain associated with an email address of a meeting organizer associated with the scheduled virtual meeting.

17. The method of claim 11, wherein generating comprises generating a plurality of meeting join links each associated with the scheduled virtual meeting, each of the plurality of meeting join links for a different communication protocol by which the scheduled virtual meeting can be joined.

18. A computer-implemented method comprising:

receiving a communication from a user device, the communication made using a meeting join link that is associated with a scheduled virtual meeting, the meeting join link having been previously generated by the user device based on a meeting calendar identifier associated with the scheduled virtual meeting;

determining whether the scheduled virtual meeting for the meeting join link has already been activated;

if it is determined that the scheduled virtual meeting has not yet been activated, activating the scheduled virtual meeting and connecting the user device into the scheduled virtual meeting; and

if it is determined that the scheduled virtual meeting has already been activated, connecting the user device into the scheduled virtual meeting that has already been activated.

19. The method of claim 18, wherein the meeting join link is a Uniform Resource Identifier (URI) of any URI scheme.

20. The method of claim 18, wherein receiving comprises receiving a communication from each of a plurality of user devices each using the same one or more meeting join links for the scheduled virtual meeting and having been separately previously generated by the respective user devices based on the meeting calendar identifier of the scheduled virtual meeting.

21. The method of claim 18, wherein receiving comprises receiving communications from each of a plurality of user devices using meeting join links of a different communication protocol but associated with the scheduled virtual meeting, and further comprising connecting the plurality of user devices into the same virtual meeting.

22. One or more non-transitory computer readable storage media encoded with instructions that, when executed by a computer processor, cause the computer processor to perform operations comprising:

retrieving a meeting calendar identifier for a scheduled virtual meeting; and

generating based on the meeting calendar identifier a meeting join link that is associated with the scheduled virtual meeting.

23. The non-transitory computer readable storage media of claim 22, wherein the instructions for retrieving include instructions for retrieving a meeting organizer identifier associated with the scheduled virtual meeting, and the instructions for generating the meeting join link are based further on the meeting organizer identifier.

24. The non-transitory computer readable storage media of claim 22, further comprising instructions for communicating with a server using the meeting join link to be connected by the server to the virtual meeting that is associated with the meeting join link.

25. The non-transitory computer readable storage media of claim 22, wherein the meeting join link is a Uniform Resource Identifier (URI) of any URI scheme.