Deferred Automatic Creation of Human Readable Meeting Placeholder Join Links Based on a Calendar Entry

• US 20160247124A1
• 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,722
• Publication Number:
  US 20160247124A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/1095 Meeting or appointment
• CPC Class Codes: H04L 65/1076 Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Computer-implemented methods are performed at a user device and a server. At the user device, a meeting calendar identifier is retrieved for a previously scheduled virtual meeting. The user device sends to a server a join link request for the scheduled virtual meeting, the join link request including the meeting calendar identifier. The user device receives from the server a first join link for the scheduled virtual meeting, the first join link mapped by the server to a second join link that is used by the server to connect a user device to the scheduled virtual meeting. The second join link is generated based on the meeting calendar identifier and has more characters than the first join link. The first join link is “human readable” insofar as it includes a human readable portion that includes a string of random or non-random characters.

Claims

1. A computer-implemented method comprising:

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

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

sending to a server a join link request for the scheduled virtual meeting, the join link request including the meeting calendar identifier;

receiving from the server a first join link for the scheduled virtual meeting, the first join link mapped by the server to a second join link that is used by the server to connect a user device to the scheduled virtual meeting, the second join link having been generated based on the meeting calendar identifier and having more characters than the first join link; and

storing the first join link.

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

3. The method of claim 2, wherein the first join link is a URI with a scheme for the Session Initiation Protocol (SIP).

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

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

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

7. The method of claim 1, further comprising:

activating the first join link to connect to a server which uses the second join link corresponding to the first join link to connect the user device to the schedule virtual meeting.

8. The method of claim 1, wherein the first join link includes a human readable portion that includes a random or non-random string of characters.

9. The method of claim 1, wherein receiving comprises receiving a plurality of first 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 may be joined.

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

10. A computer-implemented method comprising:

receiving from a user device a join link request for a previously scheduled virtual meeting, the join link request including a meeting calendar identifier for the scheduled virtual meeting;

generating a first join link and a second join link for the scheduled virtual meeting, the second join link being generated based on the meeting calendar identifier and having more characters than the first join link;

storing data that maps the first join link to the second join link for the scheduled virtual meeting; and

sending the first join link to the user device.

11. The method of claim 10, wherein receiving comprises receiving a meeting organizer identifier for the scheduled virtual meeting, and wherein generating comprises generating the second join link based further on a meeting organizer identifier for the scheduled virtual meeting.

12. The method of claim 10, wherein the first join link is a Uniform Resource Identifier (URI) of any URI scheme.

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

14. The method of claim 10, wherein the first join link includes a human readable portion that includes a random or non-random string of characters.

15. The method of claim 10, further comprising:

receiving from another user device a join link request for the scheduled virtual meeting;

determining that the first join link for the scheduled virtual meeting has already been generated;

sending the first join link for the scheduled virtual meeting to the other user device.

17. A computer-implemented method comprising:

for each of a plurality of previously scheduled virtual meetings, generating a first join link and a second join link, the second join link being generated based on a meeting calendar identifier associated with a corresponding scheduled virtual meeting and having more characters than the first join link;

storing the first join link and the second join link for each of the plurality of previously scheduled virtual meetings, including information mapping the first join link to the second join link for each associated scheduled virtual meeting;

receiving a communication from a user device using a particular first join link to join a particular scheduled virtual meeting;

retrieving a particular second join link that is mapped to the particular first join link; and

using the particular second join link, connecting the user device to a meeting service that supports the particular scheduled virtual meeting.

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

19. The method of claim 17, wherein generating comprises generating a plurality of first join links for a given scheduled virtual meeting, each of the plurality of first meeting join links for a different communication protocol by which the given scheduled virtual meeting may be joined.

20. The method of claim 19, further comprising receiving communications from multiple user devices each using a first join link for a different communication protocol for a given scheduled virtual meeting, and connecting the multiple user devices joining with first join links for different communication protocols into the same virtual meeting.

21. An apparatus comprising:

a network interface unit configured for communications over a network;

a memory;

a processor coupled to the network interface and the memory, wherein the processor is configured to;

receive from a user device a join link request for a previously scheduled virtual meeting, the join link request including a meeting calendar identifier for the scheduled virtual meeting;

generate a first join link and a second join link for the scheduled virtual meeting, the second join link being generated based on the meeting calendar identifier and having more characters than the first join link; and

store in the memory data that maps the first join link to the second join link for the scheduled virtual meeting.

22. The apparatus of claim 21, wherein the processor is further configured to send the first join link to the user device.

23. The apparatus of claim 21, wherein the first join link includes a human readable portion that includes a random or non-random string of characters.

24. The apparatus of claim 21, wherein the processor is further configured to:

receive from another user device a join link request for the scheduled virtual meeting;

determine that the first join link for the scheduled virtual meeting has already been generated; and

send the first join link for the scheduled virtual meeting to the other user device.

25. The apparatus of claim 21, wherein the processor is configured to generate a plurality of first join links each associated with the scheduled virtual meeting, each of the plurality of first meeting join links for a different communication protocol by which the scheduled virtual meeting may be joined.