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

US9241073B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-9241073-B1
Application numberUS-201414565389-A
CountryUS
Kind codeB1
Filing dateDec 9, 2014
Priority dateDec 9, 2014
Publication dateJan 19, 2016
Grant dateJan 19, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method for managing an event scheduling request, comprising: establishing a call between a first communication device and a second communication device; upon authenticating a user identity associated with the second communication device, and while the first communication device and the second communication device are engaged in the call, determining an event scheduling request for scheduling a future event based on one or more attributes of the call; and providing the event scheduling request to at least one of the first communication device and the second communication device, 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, wherein determining the event scheduling request based on the one or more attributes of the call comprises: acquiring 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; obtaining calendar information associated with the first communication device based on the event scheduling information, the calendar information indicating the availability of a user of the first communication device; providing the calendar information to the second communication device; and acquiring the event scheduling request from the second communication device, wherein the event scheduling request is a calendar invitation generated based on the calendar information associated with the first communication device. 2. The method of claim 1 , wherein authenticating the user identity associated with the second communication device is 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 a calendar invitation is generated also based on at least one of the content of the call or the contextual information. 4. The method of claim 1 , wherein the acquiring of the event scheduling information is also 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. 5. The method of claim 1 , wherein the calendar information associated with the first communication device indicates the availability of the user of the first communication device without indicating the reason associated with the availability. 6. The method of claim 1 , further comprising providing a notification based on the event scheduling request to the second communication device, wherein providing the notification comprises: sending a confirmation of scheduling the future event; or sending a notification indicating the unavailability of a user of the first communication device. 7. The method of claim 1 , wherein the method is being performed in one communication channel that provides voice and data communication capability. 8. A server, comprising: at least one processor configured to: establish a call between a first communication device and a second communication device; upon authenticating a user identity associated with the second communication device, and while the first communication device and the second communication device are engaged in the call, determine an event scheduling request for scheduling a future event based on one or more attributes of the call; and provide the event scheduling request to at least one of the first communication device and the second communication device, 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, wherein the at least one processor is configured to determine the event scheduling request by: acquiring 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; obtaining calendar information associated with the first communication device based on the event scheduling information, the calendar information indicating the availability of a user of the first communication device; providing the calendar information to the second communication device; and acquiring the event scheduling request from the second communication device, wherein the event scheduling request is a calendar invitation generated based on the calendar information associated with the first communication device. 9. The server of claim 8 , wherein the authenticating of the user identity associated with the second communication device is 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. 10. The server of claim 8 , wherein the obtaining of the calendar information associated with the first communication device is also 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. 11. The server of claim 8 , wherein the calendar information associated with the first communication device indicates the availability of the user of the first communication device without indicating the reason associated with the availability. 12. The server of claim 8 , 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 notification indicating the unavailability of a user of the first communication device. 13. The server of claim 8 , wherein the at least one processor is configured to communicate in one communication channel that provides voice, and data communication capability. 14. 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 between a first communication device and a second communication device; upon authenticating a user identity associated with the second communication device, and while the first communication device and the second communication device are engaged in the call, determining an event scheduling request for scheduling a future event based on one or more attributes of the call; and provide the event scheduling request to at least one of the first communication device and the second communication device, 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, wherein the set of instructions cause the at least one processor to determine the event scheduling request by: acquiring 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; obtaining calendar information associated with the first communication device based on the event scheduling information, the calendar information indicating the availability of a user of the first communication device; providing the calendar information to the second communication device; and acquiring the event scheduling request from the second communication device, wherein the event scheduling request is a calendar invitation generated based on the calendar information associated with the firs

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9241073B1 cover?
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 …
Who is the assignee on this patent?
Ringcentral Inc
What technology area does this patent fall under?
Primary CPC classification H04M3/563. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jan 19 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).