Systems and methods for managing an event scheduling request in a telephony system

Patent metadata

Field	Value
Publication number	US-9888125-B2
Application number	US-201514955234-A
Country	US
Kind code	B2
Filing date	Dec 1, 2015
Priority date	Dec 9, 2014
Publication date	Feb 6, 2018
Grant date	Feb 6, 2018

Abstract

Systems and methods are disclosed for managing an event scheduling request in a telephony system. According to certain embodiments, a call between a first communication device and a second communication device is established. Upon authenticating a user identity associated with the second communication device, an event scheduling request is determined based on one or more attributes provided to the first communication device. A notification is provided to the second communication device based on the event scheduling request.

First claim

What is claimed is:

1. A computer-implemented method for managing an event scheduling request, comprising:
establishing a call with voice communication between a first communication device and a second communication device;
while the call with voice communication is in progress,
obtaining event scheduling information for scheduling a future event based on one or more attributes of the call;
obtaining, from the first communication device, calendar information associated with a user of the first communication device, based on the event scheduling information;
providing the calendar information to the second communication device;
acquiring an event scheduling request for scheduling a future event from the second communication device, the event scheduling request including a calendar invitation generated based on the calendar information; and
providing a notification regarding the future event to the second communication device.

2. The method of claim 1 , further comprising authenticating a user identity associated with the second communication device based on at least one of: a phone number, a caller identification (caller ID), an internet protocol (IP) address, a certificate, or a voice print identification.

3. The method of claim 1 , wherein the one or more attributes of the call include at least one of content from the call or contextual information associated with the call.

4. The method of claim 3 ,
wherein obtaining the event scheduling information comprises obtaining the event scheduling information based on at least one of the content from the call or the contextual information, the event scheduling information including event scheduling details of the future event, and
wherein the calendar information associated with the user of the first communication device indicates availability of the user of the first communication device.

5. The method of claim 4 , wherein the obtaining of the event scheduling information is based on at least one of voice recognition of the content from the call, interactive voice responses (IVRs), or dual-tone multi-frequency (DTMF) tones.

6. The method of claim 4 , wherein the calendar information associated with the user of the first communication device indicates the availability of the user of the first communication device without indicating a reason associated with the availability.

7. The method of claim 1 ,
wherein providing the notification comprises:
sending a confirmation of scheduling the future event; or sending a proposal of an alternative time for scheduling the future event.

8. The method of claim 1 , wherein the method is being performed in one communication channel that provides voice and data communication capability.

9. A server, comprising:
at least one processor configured to:
establish a call with voice communication between a first communication device and a second communication device;
while the call with voice communication is in progress,
obtain event scheduling information for scheduling a future event based on one or more attributes of the call;
obtain, from the first communication device, calendar information associated with a user of the first communication device, based on the event scheduling information;
provide the calendar information to the second communication device;
acquire an event scheduling request for scheduling a future event from the second communication device, the event scheduling request including a calendar invitation generated based on the calendar information; and
providing a notification regarding the future event to the second communication device.

10. The server of claim 9 , further comprising authenticating a user identity associated with the second communication device based on at least one of: a phone number, a caller identification (caller ID), an internet protocol (IP) address, a certificate, or a voice print identification.

11. The server of claim 9 , wherein the one or more attributes of the call include at least one of content from the call or contextual information associated with the call.

12. The server of claim 11 , wherein the at least one processor is configured to:
obtain the event scheduling information based on at least one of the content from the call or the contextual information, the event scheduling information including event scheduling details of the future event;
wherein the calendar information associated with the user of the first communication device indicates availability of the user of the first communication device.

13. The server of claim 12 , wherein the obtaining of the calendar information associated with the user of the first communication device is based on at least one of voice recognition of the content from the call, interactive voice responses (IVRs), or dual-tone multi-frequency (DTMF) tones.

14. The server of claim 12 , wherein the calendar information associated with the user of the first communication device indicates the availability of the user of the first communication device without indicating a reason associated with the availability.

15. The server of claim 9 , wherein the at least one processor is configured to provide a notification to the second communication device by:
sending a confirmation of scheduling the future event; or
sending a proposal of an alternative time for scheduling the future event.

16. The server of claim 9 , wherein the at least one processor is configured to communicate in one communication channel that provides voice, and data communication capability.

17. A non-transitory computer-readable storage medium that comprises a set of instructions that are executable by at least one processor to cause the at least one processor to perform a method for managing an event scheduling request, the method comprising:
establishing a call with voice communication between a first communication device and a second communication device;
while the call with voice communication is in progress,
obtaining event scheduling information for scheduling a future event based on one or more attributes of the call;
obtaining, from the first communication device, calendar information associated with a user of the first communication device, based on the event scheduling information;
providing the calendar information to the second communication device;
acquiring an event scheduling request for scheduling a future event from the second communication device, the event scheduling request including a calendar invitation generated based on the calendar information; and
providing a notification regarding the future event to the second communication device.

18. The computer-readable storage medium of claim 17 , wherein the one or more attributes of the call include at least one of content from the call or contextual information associated with the call.

19. The computer-readable storage medium of claim 18 ,
wherein the event scheduling information includes event scheduling details of a future event, and
wherein the calendar information indicates availability of the user of the first communication device.

20. The computer-readable storage medium of claim 19 , wherein the obtaining of the event scheduling information is based on at least one of voice recognition of the content from the call, interactive voice responses (IVRs), or dual-tone multi-frequency (DTMF) tones.

Assignees

• Ringcentral Inc

Inventors

• Van Rensburg Christopher
• Petrov Aleksei

Classifications

• H04M2203/2038

  Call context notifications · CPC title

• H04M3/563

  User guidance or feature selection · CPC title

• H04M2203/6054

  Biometric subscriber identification · CPC title

• G06Q10/1093

  Calendar-based scheduling for persons or groups · CPC title

• H04M2203/6045

  Identity confirmation · CPC title