Methods and systems for time-based delivery of calls

• US 7,822,186 B1
• Filed: 02/20/2003
• Issued: 10/26/2010
• Est. Priority Date: 02/21/2002
• Status: Expired due to Fees

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Laboratories Incorporated (Verizon Communications Inc.)
• Inventors: Boni, Piotr
• Primary Examiner(s): Harper; Vincent P
• Assistant Examiner(s): Sabouri; Mazda
• Application Number:
  US10/370,850
• Time in Patent Office: 2,805 Days
• Field of Search: 379/202.01, 379/203.01, 379/204.01, 379/205.01, 379/206.01, 379/207.01, 379/207.02, 379/207.03
• US Class Current: 379/210.01
• CPC Class Codes: H04M 2203/2072 Schedules, e.g. personal calendars
• CPC Class Codes: H04M 2203/5063 Centrally initiated conference, i.e. conference server dials participants
• CPC Class Codes: H04M 3/432 Arrangements for calling a subscriber at a specific time, e.g. morning call service
• CPC Class Codes: H04M 3/56 Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities video conference systems H04N7/15
• CPC Class Codes: H04M 3/565 relating to time schedule aspects

Abstract

Methods and systems are provided for managing the scheduling of calls and automating the process of making and delivering such calls. Any endpoint (e.g., telephony-enabled) device can be used with a PSTN, cellular, and VoIP network. Different types of devices and interfaces may be used for provisioning users, conferring calling events, scheduling events, and/or delivering calls. Among other things, this increases user mobility. Also, automated retrying and rescheduling of calls, which may use updated data, reduces the likelihood of missed calls.

Claims

1. A method for making a call that invokes a call-transfer function, wherein the call-transfer function enables a user to connect at least three endpoint devices to form a call on a network, the method comprising:

provisioning, via a web interface, a call request in accordance with a schedule;

formulating the call request in accordance with the schedule, wherein the formulating includes identification of at least two endpoint devices for the network to establish a call using a call-transfer function;

establishing a first call leg to a first endpoint device of the at least three endpoint devices;

establishing a second call leg to a second endpoint device of the at least three endpoint devices;

sending a call-transfer signal to a server associated with the network to use the call-transfer function to bridge the first call leg and the second call leg, to connect the first endpoint device and the second endpoint device via a direct channel in accordance with the call request and the schedule and without an intermediary that maintains multiple outbound call connections forming an indirect channel between the first endpoint device and the second endpoint device;

establishing a third call leg to a third endpoint device of the at least three endpoint devices;

connecting at least the first, second, and third call legs in accordance with the call request and the schedule; and

rescheduling the call request based on one or more user preferences if the call request is not connected successfully,

wherein the third call leg is established and connected automatically and independent of parties to the call at the first endpoint device and the second endpoint device.

2. The method of claim 1 further comprising receiving a trigger, wherein the formulating is in response to the receiving.

3. The method of claim 2 further comprising generating a trigger, wherein the receiving is in response to the generating.

4. The method of claim 1 wherein the provisioning comprises:

receiving user information from the user; and

storing the user information in a database.

5. The method of claim 4 wherein the receiving comprises receiving data selected from a group consisting of user identification data, user preference data, and a combination thereof.

6. The method of claim 5 wherein the user preference data comprises at least one calling service selected from a group consisting of a person-to-person telephony calling service, a break-in service, an information service, a traffic report service, and any combination thereof.

7. The method of claim 1 further comprising configuring the call, wherein the configuring comprises:

receiving call information; and

storing the call information in a database.

8. The method of claim 7 wherein the configuring further comprises storing in the database additional data selected from a group consisting of text, pre-recorded voice, pre-recorded music, pre-recorded video, and any combination thereof.

9. The method of claim 8 wherein the formulating comprises retrieving the additional data from the database.

10. The method of claim 9 wherein the retrieving additional data is repeated until the call is either successfully delivered or cancelled.

41. The method of claim 1 further comprising providing an option to continue with the call request in accordance with the schedule, reschedule the call request, or discard the call request.

11. A method for establishing a call between at least three parties, the method comprising:

provisioning a call via a voice portal;

scheduling the call;

triggering the call by generating a trigger in accordance with a schedule;

dispatching the call, wherein the dispatching comprises receiving the trigger and formulating a call request that invokes a call-transfer function;

sending the call request to a server;

delivering the call with the server at a delivery time upon the server receiving the request from the notification dispatcher using the call-transfer function;

establishing a first call leg to a first party of the at least three parties;

establishing a second call leg to a second party of the at least three parties,

wherein the call-transfer function connects the first party and the second party via a call connection to bridge the first call leg and the second call leg, to establish a direct channel between the first party and the second party and does not connect the first party and the second party via an intermediary that maintains multiple outbound call connections forming an indirect channel between the first party and the second party;

establishing a third call leg to a third party of the at least three parties;

connecting at least the first, second, and third call legs in accordance with the call request and the schedule; and

rescheduling the call based on one or more user preferences if the call is not connected successfully,

wherein the third call leg is established and connected automatically and independent of the first party and the second party.

12. The method of claim 11 wherein the provisioning comprises:

receiving user information from a user; and

storing the user information in a database.

13. The method of claim 12 wherein the receiving comprises receiving data selected from a group consisting of user identification data, user preference data, and a combination thereof.

14. The method of claim 13 wherein the user preference data comprises at least one calling service selected from a group consisting of a person-to-person telephony calling service, a break-in service, an information service, a traffic report service, and any combination thereof.

15. The method of claim 11 further comprising configuring the call, wherein the configuring comprises:

receiving call information; and

storing the call information in the database.

16. The method of claim 11 wherein the formulating comprises retrieving additional data from the database.

17. The method of claim 11 wherein the scheduling comprises:

receiving the call information;

inserting the call information into the database;

retrieving the call information from the database; and

preparing the trigger using the call information.

18. The method of claim 17 wherein the retrieving comprises retrieving call information selected from a group consisting of a call date, a call time, a requesting party identifier, a requested party identifier, and any combination thereof.

19. The method of claim 18 wherein the formulating comprises:

retrieving the requesting party identifier from the scheduler; and

determining a requesting party endpoint device address using the requesting party identifier, and wherein the dispatching further comprises passing a call request to a server that includes at least the requesting party endpoint device address.

20. The method of claim 19 wherein the determining comprises using a database that includes a plurality of possible endpoint device addresses to identify the requesting party endpoint device address.

21. The method of claim 11 wherein the formulating comprises:

retrieving a requested party identifier from the scheduler;

determining a requested party endpoint device address using the requested party identifier; and

wherein the dispatching further comprises passing a call request to a server that includes at least the requested party endpoint device address.

22. The method of claim 21 wherein the determining comprises using a database that includes a plurality of possible endpoint device addresses to identify the requested party endpoint device address.

23. The method of claim 22 wherein the determining is performed at the delivery time.

24. The method of claim 11 wherein the dispatching comprises parsing the content of the trigger to determine the type of call to be executed against the server and any resources needed to perform the call.

25. The method of claim 11 wherein the dispatching comprises:

receiving a call status from the server; and

reporting that status to a user.

26. The method of claim 25 wherein, upon the receiving of a call status that is completed, the dispatching further comprises causing a database management application to delete data stored in the database related to the call.

27. The method of claim 11 wherein the bridging comprises forming a real-time communication session between two or more participants.

28. The method of claim 11 wherein the establishing the first call leg comprises causing the server to query the requesting party for further information before the establishing of the second call leg.

29. The method of claim 28 wherein the causing the server to query comprises requesting permission to perform the establishing of the second call.

30. A method for making a call that invokes a call-transfer function, wherein the call-transfer function enables a user to connect at least three endpoint devices to form a call on a network, the method comprising:

provisioning, via a web interface, a call request in accordance with a schedule;

formulating the call request, wherein the call request invokes a call-transfer function in accordance with the schedule;

placing a call on the network in accordance with the call request;

establishing a first call leg to a first endpoint device of the at least three endpoint devices; and

establishing a second call leg to a second endpoint device of the at least three endpoint devices,

wherein the call-transfer function connects the first endpoint device and the second endpoint device via a call connection by bridging the first call leg and the second call leg, to establish a direct channel between the first endpoint device and the second endpoint device and without an intermediary that maintains multiple outbound call connections forming an indirect channel between the first endpoint device and the second endpoint device;

establishing a third call leg to a third endpoint device of the at least three endpoint devices;

connecting at least the first, second, and third call legs; and

rescheduling the call request based on one or more user preferences if the call request is not connected successfully,

wherein the third call leg is established and connected automatically and independent of parties to the call at the first endpoint device and the second endpoint device.

31. A system for scheduling services and delivering calls, wherein the system comprises:

a device for receiving, via a web interface, at least one scheduling entry relating to a call;

a database for storing the information;

a scheduler for generating a trigger for the at least one entry at a calling time;

a notification dispatcher that formulates a call request in response to receiving the trigger, wherein the call request invokes a call-transfer function; and

a server that establishes a first call leg to a first party of at least three parties, establishes a second call leg to a second party of the at least three parties, and establishes a third call leg to a third party of the at least three parties;

wherein the notification dispatcher reschedules the call based on one or more user preferences if the call is not connected successfully,

wherein the call-transfer function connects the first party and the second party via a call connection by bridging the first call leg and the second call leg, to establish a direct channel between the first party and the second party, and does not connect the first party and the second party via an intermediary that maintains multiple outbound call connections forming an indirect channel between the first party and the second party, and

wherein the server connects the third party to the first party and the second party, automatically and independent of the first party and the second party.

32. The system of claim 31 wherein the device comprises an interface selected from a group consisting of a computer-based user interface, a telephony-based interface, and a combination thereof.

33. The system of claim 31 wherein the device interoperates with the scheduler to store data selected from a group consisting of the user information, the at least one scheduling entry, and a combination thereof.

34. The system of claim 31 wherein the scheduler uses calendar software based, at least in part, on an iCalendar specification RFC 2445.

35. The system of claim 31 wherein the scheduler comprises a trigger application that invokes the notification dispatcher when a scheduling entry is due.

36. The system of claim 31 wherein the dispatcher identifies a physical address of an endpoint device of at least one call recipient that will participate in the call.

37. The system of claim 36 wherein the server identifies a physical address by using call recipient identification information selected from a group consisting of a call recipient name and a call recipient logical address.

38. The system of claim 37 wherein the dispatcher uses the call recipient identification information by retrieving the call recipient identification information from a source selected from a group consisting of a database, a directory, an address book, and any combination thereof.

39. The system of claim 31 wherein the server is a logical device with call control functionality capable of creating and delivering calls to endpoint devices in a domain selected from a group consisting of a VoIP domain, a PSTN domain, and a cellular domain.

40. The system of claim 39 wherein the server is selected from a group consisting of a VoIP gateway, a softswitch, a SIT proxy server, a VoiceXML platform, a Media/Announcement Server, a PSTN AIN service node, an SCP, PSTN switch, and any combination thereof.