Source: http://www.google.com/patents/US7266190?dq=6650327
Timestamp: 2017-09-22 07:23:29
Document Index: 502070002

Matched Legal Cases: ['arty 442', 'arty 442', 'arty 448', 'arty 448', 'arty 442', 'arty 448', 'arty 442', 'arty 442', 'arty 442', 'arty 448', 'arty 448', 'arty 448', 'arty 448', 'arty 448', 'arty 448', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 442', 'arty 448', 'arty 448', 'arty 442', 'arty 442', 'arty 448', 'arty 442', 'arty 448', 'arty 448', 'arty 442', 'arty 514', 'arty 514', 'arty 514', 'arty 512', 'arty 514', 'arty 514', 'arty 512', 'arty 514', 'arty 514', 'arty 514', 'arty 514', 'arty 512', 'arty 514', 'arty 512', 'arty 510', 'arty 514', 'arty 510', 'arty 510', 'arty 512', 'arty 510', 'arty 510', 'arty 512', 'arty 512', 'arty 512', 'arty 604', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 620', 'arty 622', 'arty 606', 'arty 606', 'arty 606', 'arty 606', 'arty 620', 'arty 622', 'arty 622', 'arty 606', 'arty 620', 'arty 622', 'arty 606', 'arty 622', 'arty 606', 'arty 606', 'arty 622', 'arty 606', 'arty 620', 'arty 620', 'arty 606', 'arty 620']

Patent US7266190 - System and method for managing communications - Google Patents
A communications network-based system and service is disclosed. The service permits subscribers to control and manage incoming telephone calls. Subscribers can establish preferences and set encumbrances. The service also connects calls to a called party otherwise prevented from receiving calls due to...http://www.google.com/patents/US7266190?utm_source=gb-gplus-sharePatent US7266190 - System and method for managing communications
Publication number US7266190 B1
Application number US 10/108,347
Also published as US20070127675
Publication number 10108347, 108347, US 7266190 B1, US 7266190B1, US-B1-7266190, US7266190 B1, US7266190B1
Original Assignee At&T Intellectual Property, Inc.
Patent Citations (58), Non-Patent Citations (13), Referenced by (26), Classifications (7), Legal Events (5)
System and method for managing communications
US 7266190 B1
A communications network-based system and service is disclosed. The service permits subscribers to control and manage incoming telephone calls. Subscribers can establish preferences and set encumbrances. The service also connects calls to a called party otherwise prevented from receiving calls due to line encumbrances, permitting preselected or predesignated parties to by-pass line encumbrances.
1. A method for establishing preferences for a communications service and for providing the communications service comprising the steps of:
receiving identifying data from a probable subscriber of a service through computer interface system;
determining if the probable subscriber is a valid subscriber by comparing the identifying data to an identifying-data record;
if the probable subscriber is a valid subscriber, sending stored and default information to the subscriber through the computer interface system, wherein the stored and default information is displayed to the subscriber on a graphical user interface (GUI) executing on a computer and comprises at least encumbered-line bypass list data, forwarding numbers, an on/off setting for the entire communications service and links to one or more other available services, wherein further the encumbered-line bypass list data comprises bypass times for one or more phone numbers and one or more pass-codes;
receiving a second item of information from the subscriber through the computer interface system, wherein the second item of information is related to a calling party that has been preselected to by-pass an encumbered line; and
storing the second item of information in a database accessible by a communications network thereby updating the stored and default information.
2. The method of claim 1, further comprising the step of sending at least one call marker, relating to at least one telephone call made from the subscriber, to the subscriber by the computer interface system.
3. The method of claim 2, wherein the call markers include a phone number of a party called by the subscriber.
4. The method of claim 2, wherein the call marker includes a caller identification of a party that called the subscriber.
5. The method of claim 2, wherein the call marker includes a timestamp related to a time a party was called by the subscriber.
6. The method of claim 1, wherein the step of sending default information to the subscriber through the computer interface system further comprises the step of sending one or more phone numbers or pass-codes stored in an encumbered-line bypass list to the subscriber through the computer interface system.
7. A method for receiving encumbered-line bypass list information through an IVR system, comprising the steps of:
receiving identifying data from a probable subscriber of a service through an IVR system;
providing an option choice to the subscriber comprising toggling the service between on and off, setting a schedule for the service, setting an encumbered-line bypass list and selecting a forwarding number;
if setting a schedule for the service is selected, then playing the schedule to the subscriber through the IVR system, wherein the subscriber sets a time of day during which encumbrance-line bypass list is enabled;
if setting an encumbered-line bypass list is selected, then playing information in the encumbered-line bypass list to the subscriber through the IVR system;
receiving modifications to the encumbered-line bypass list information from the subscriber through the IVR system; and
storing the modified encumbered-line bypass list information in a database accessible by a communications network.
8. The method of claim 7, wherein the encumbered-line bypass list information is related to at least one calling party preselected by the subscriber to bypass an encumbrance on the subscriber's line.
9. A method of connecting a calling party with a called party comprising the steps of:
receiving a call from a calling party over a telecommunications system which includes a database containing subscriber information, wherein the subscriber information includes an encumbered-line bypass list of phone numbers;
determining that a line associated with the called party is encumbered;
communicating one or more identifiers related to the calling party to the called party where the identifiers are presented to the called party and wherein further the identifiers include the calling party's phone number, the calling party's name, the time the calling party called, pass-code and any additional information input by the calling party including audible input;
querying the database for the called party's call reception status, wherein if the call reception status is a restricted status then the call is connected to a third party and if the call receptions status is not a restricted status then the call is placed to the called party, wherein the method further comprises determining whether an instruction is received from the called party to set the call reception status to a restricted status after the one or more identifiers are received by the called party;
if the call reception status is set to a restricted status, comparing one or more identifiers of the calling party with the encumbered-line bypass list of phone numbers; and
if one of the identifier(s) of the calling party matches an identifier in the encumbered-line bypass list, then connecting the calling party to the called party by bypassing the encumbrance unless the called party has prevented the call from bypassing a restricted status by imposing a restriction on all calls based on time of day.
contacting the called party to determine if the called party wishes to receive a call from the calling party; and
receiving, from the called party, an assent for the communications network to connect the calling party to the called party.
11. The method of claim 10, wherein the step of contacting the called party to determine if the called party wishes to receive the call of the calling party is in the form of a text-based message.
12. The method of claim 11, wherein the step of receiving, from the called party, an assent for the communications network to connect the calling party to the called party is received as a text-based response to the text-based message.
13. The method of claim 12, wherein the communications network first disconnects the called party from a third party prior to connecting the calling party to the called party.
14. The method of claim 10, wherein the step of contacting the called party to determine if the called party wishes the communications network to connect the calling party to the called party is performed by the communications network through an audible message.
15. The method of claim 14, wherein the step of receiving from the called party an assent for the communications network to connect the calling party to the called party is received by the communications network through an audible response.
16. The method of claim 9, wherein the called party is permitted to change the encumbered-line bypass list by calling a number and communicating with the communications network by communicating with an interactive voice response system to modify the encumbered-line bypass list.
17. The method of claim 9, wherein the called party is permitted to change the encumbered-line bypass list by communicating with an interface system to modify the encumbered-line bypass list.
18. A method of directing a call comprising the steps of:
determining the identity of a called party;
communicating one or more identifiers related to the calling party to the called party where the identifiers are presented to the called party and wherein further the identifiers include the calling party's phone number, the calling party's name, the time the calling party called, pass-code and any additional information input by the called party including audible input;
comparing one or more identifiers of the calling party with information received from the called party;
querying the database for the called party's call reception status, wherein if the call reception status is a restricted status then the call is connected to a third party and if the call receptions status is not a restricted status then the call is placed to the called party, wherein the method further comprises determining whether the called party has set the call reception status to a restricted status after the one or more identifiers are received by the called party; and
connecting the call to the called party if one of the identifier(s) corresponds to the information received from the called party, unless the called party has prevented the call from bypassing a restricted status by imposing a restriction on all calls based on time of day, and connecting the call to a third party if none of the identifier(s) corresponds to the information received from the called party.
19. The method of claim 18, wherein the identifier(s) are associated with the calling party.
20. The method of claim 19, wherein one of the identifier(s) is the phone number from which the calling party called and the information received from the called party comprises an encumbered-line bypass list.
21. The method of claim 20, wherein one of the identifier(s) is communicated to the communications network as part of the call.
22. The method of claim 18, wherein one of the identifier(s) is received from the calling party.
23. The method of claim 22, wherein one of the identifier(s) is a pass-code and the information comprises one or more pass-codes on an encumbered-line bypass list.
24. The method of claim 23, wherein the third party plays an automated announcement to the calling party.
The present invention relates to a system and method for managing communications.
Many telephone customers do not wish to be disturbed by unwanted telephone calls. In an effort to prevent disruptive telephone calls, many customers subscribe to services provided by service providers that restrict calls from being connected to the subscriber. Some of these services prevent all calls from being connected to the subscriber, such as call-forwarding. One of the problems with these services is that they prevent calls from being connected that the subscriber may want to take.
Further, even without subscribing to such a service, many telephone customers miss important calls and are not connected to calling parties that they wish to be connected for various reasons. One such example is when the customer is already on the line. Typically in such a case, the feature the service provider provides is to play a busy signal to the calling party and to not connect the calling party. Another typical feature, sometimes called “call waiting,” informs the customer that he or she has received another call. One problem with this feature, however, is that the customer first has to talk with the calling party without knowing whether or not the customer wishes to take the call.
In another aspect, the communications network includes an intelligent communications network that includes three communications network elements and a database.
In another aspect, the communications network allows a subscriber of the encumbered-line bypass feature to provision his or her preferences through an interface system and method.
In still another aspect, the communications network allows a subscriber of the encumbered-line bypass feature to provision his or her preferences through an interactive voice response system and method.
As an additional example, the subscriber could set his or her preferences to a restricted call reception status lasting from 5 p.m. to 7 p.m. weekdays and from 10:30 p.m. to 7 a.m. all days. An exemplary embodiment of these preferences is shown in FIG. 9, time periods 1406 and 1402, for a particular weekday. Also, the subscriber could, for example, include two phone numbers (e.g., the subscriber's mother and daughter) on an encumbered-line bypass list; one number (e.g., the subscriber's daughter) allowed to bypass a restricted call reception status from 8 a.m. to 10 p.m. and one phone number (e.g., the subscriber's mother) for all times. By so doing, the communications network would prevent all calls from ringing to the subscriber's landline, home telephone from Monday through Friday from 5 p.m. to 7 p.m. except calls from the subscriber's mother and sister.
Typically, when calling party 442 makes the call, calling party 442 desires to be connected to called party 448. A non-limiting example of this common practice is: someone dials another person's phone number. If Jane, for instance, wants to call Bill, she picks up her phone (cell phone, landline phone, hand-held text-based device, or what-have-you) and dials Bill's number. Jane is trying to be connected to Bill's phone.
In another embodiment, also shown in FIG. 4, as part of this communication step 104, communications network 450 communicates with called party 448 according to step 304. In this embodiment, communications network 450 preferably communicates one or more identifiers related to calling party 442 to called party 448. These identifiers may include calling party 442's phone number, calling party 442's name, the time calling party 442 called, and/or whatever identifiers or other information is available to communications network 450. Communications network 450 can communicate one, several, or all of the identifiers to called party 448.
In one embodiment of the invention, step 106 is performed as shown, in part, through FIG. 4. FIG. 4 shows, in part, a flow diagram of this embodiment of step 106. In this embodiment, communications network 450 determines whether or not called party 448 has set a forwarding number, step 306. If called party 448 has set a forwarding number, or one is otherwise set, communications network 450 connects the call to the call forwarding number, step 308. (Called party 448 may also, in another embodiment, set the forwarding number after the call has been placed. This gives called party 448 the power to selectively forward calls to particular forwarding numbers.) The forwarding number may be a voicemail receiver, another phone number of called party 448, or otherwise.
In this embodiment, shown in part in FIG. 5, after determining that the call reception status is set to a restricted call reception status, step 408 and 410, communications network 450 compares one or more identifiers, step 420, of calling party 442. The identifiers may include any data related to calling party 442 or the phone number from which calling party 442 called. These identifiers may include: the phone number from which calling party 442 called; a pass-code entered by calling party 442 or attached to calling party 442 or the number from which calling party 442 called; voice-recognition data entered by calling party 442; data within the string of data received by communications network 450 when calling party 442 made the call; data related to calling party 442 or calling party 442's phone number known by or found out by communications network 450 by various means; or other data that identifies calling party 442.
The information within database 444 may be any information by which communications network 450 may determine if the call from calling party 442 is desired by called party 448 to be connected to called party 448. In one embodiment the information is an encumbered-line bypass list and one of the identifier(s) is the phone number from which calling party 442 called. In another embodiment the information is an encumbered-line bypass list and one of the identifier(s) is a pass-code entered by calling party 442.
In this embodiment where one of the identifier(s) is a pass-code and the information is an encumbered-line bypass list, a calling party, even if his or her phone number is not on the encumbered-line bypass list, may enter a pass-code after making a call to called party 448. If the pass-code entered by calling party 442 matches a pass-code within the encumbered-line bypass list, communications network 450 may connect the call to called party 448 if called party 448 has not otherwise restricted the entered pass-code, such as by not allowing the call to bypass a restricted status or an encumbrance based on the time of day or week that communications network 450 received calling party 442's call.
Second communications network element 506 also is configured to communicate with third party 514, as set forth above and additionally below. Second communications network element 506 also may communicate with third party 514, providing information to third party 514, such as how long calling party 512 remains on the line, the calling party's phone number and name, and the like. Such information may be stored at third party 514. Second communications network element 506 preferably communicates with third party 514 to connect the call from calling party 512 to third party 514. Second communications network element 506 may also command third party 514 or third party 514 may be programmed to perform, in cases where third party 514 is a fourth communications network element or the service node, to play particular announcements or messages to calling party 512. Preferably, third party 514, when the fourth communications network element or the service node, plays a ring announcement, followed by a message. Preferably the message informs calling party 512 that called party 510 is not available. Third party 514 may, however, plays many types of messages, either chosen by communications network 450 or by called party 510.
Second communications network element 506 also is configured to communicate with called party 510, as set forth above and additionally. Second communications network element 506 preferably communicates identifiers of calling party 512 to called party 510. Second communications network element 506 does so preferably inaudibly so as not to disturb called party 510. In an exemplary embodiment, second communications network element 506 communicates identifiers of calling party 512 through a text-based display, such as a liquid crystal display. In another exemplary embodiment, second communications network element 506 communicates identifiers of calling party 512 through a test-based display without any audible communication, such as called party 512's phone ringing.
In the embodiment previously discussed, communications network 450 restricts calls from connecting to a called party that subscribes to the restricted status service. Communications network 450 also provides features where certain calls bypass the restricted status service, as well as other services and/or features that encumber a phone line, by connecting calls to the called party even though the called party's line is encumbered.
Interface system 602 preferably communicates information regarding status, settings and/or preferences and can also provide the information in a format appropriate for whatever device the subscriber is using. As an example, interface system 602 can display an existing encumbered-line bypass list of phone numbers and pass-codes in columns, allowing easy deletion from the list or adjustment to the details, bypass times, or other information related to each phone number and pass-code on the encumbered-line bypass list.
Preferably before calling party 604 made the call to called party 606, however, called party 606 established his or her preferences and determined which calling parties would bypass an encumbrance to called party 606's line. In an exemplary embodiment, called party 606 may choose which parties would bypass and at what times of the day or week based on the phone number from which they call or their entry of a certain pass-code.
In one embodiment, called party 606 may contact IVR system 600 through a telephone call to the system, and through IVR system 600 set his or her preferences. These preferences may include phone numbers of potential calling parties that may bypass an encumbrance as well as pass-codes whereby calling parties may bypass an encumbrance. These preferences may also include times of the day that potential calling parties may bypass encumbrances and other times or days that certain potential calling parties may not bypass encumbrances.
Called party 606 communicates with information network 612 with communication device 613. Communication device 613 may be a computer, a wireless device, or any device allowing a person to communicate with an information network. Preferably these devices allow for the display of a monitor screen 614.
Called party 606's preferences may include phone numbers of calling parties that may bypass an encumbrance as well as pass-codes whereby calling parties may bypass an encumbrance. These preferences may also include times of the day that potential calling parties may bypass encumbrances and other times or days that certain potential calling parties may not bypass encumbrances, well as other options.
In this embodiment, interface system 602 sends information to called party 606. Communication device 613 displays, through screen 614, called party 606's times of the day that called party 606's line is set to a restricted status or is otherwise encumbered. Screen 614 shows an exemplary embodiment, showing called party 606 a graph 624 of the hours in a day, including those where called party 606's line is encumbered and unencumbered. Screen 614 also shows an “on setting” and an “off setting,” either of which may be used to override the restricted and non-restricted statuses shown in graph 624. Preferably interface system 602 sends information such that communication device 613 displays this graph in varying colors, such that called party 606 may easily discern which times of the day called party 606's line is encumbered.
In the example show in graph 624, called party 606's line is encumbered from 10:30 p.m. to 7:00 a.m. and from 5:00 p.m. to 7:00 p.m. Neither the on setting or the off setting are chosen. Recall that one example of an encumbered line is a call blocking feature where incoming calls are either sent to another number, or a signal is sent to the calling party indicating the unavailability of the called party. While not shown, interface system 602 may send information such that the communication device displays multiple graphs representing times for each day of the week or month that called party 606's line is encumbered.
Preferably called party 606 also may communicate with interface system 602 using screen 614 to select preferences for the encumbered-line bypass feature. A portion of screen 614 includes a list 626 of telephone numbers. Another portion of screen 614 includes pass-codes. In addition to the telephone numbers and pass-codes, additional fields of data may be presented. For example, a name or other detail associated with the phone number or pass-code, as well as other information may also be included, as shown in the example in FIG. 9, screen 614.
As shown in FIG. 9, called party 606 has established certain preferences for his or her encumbered-line bypass list. Specifically, calls from phone numbers 404-555-1111 and 404-555-3333 have been selected as telephone numbers to bypass encumbrances on called party 606's line during certain times of the day or week, shown under “Bypass Times”.
Given these preferences, if either a first calling party 620, having a telephone number of 404-555-1111, or a second calling party 622, having a telephone number of 404-555-2222, calls called party 606 at 1 p.m., both will be connected to called party 606 unless called party 606's line is encumbered is some way, for example, if the line is busy. This is because, as shown in graph 624, the called party has not chosen to selectively restrict or otherwise encumber his or her line to prevent unwanted calls at 1 p.m. Because called party 606's line is not encumbered at 1 p.m., first calling party 620 and second calling party 622 may be connected by communications network 608. This is true even though second calling party 622 is not on called party 606's encumbered-line bypass list 626.
As another example, if either the first calling party 620 or the second calling party 622 calls called party 606 at 3 a.m., second calling party 622 will not be connected to called party 606 because called party 606 has selected his or her line to be encumbered at 3 a.m., as shown in graph 624, and because second calling party 622's phone number is not on called party 606's encumbered-line bypass list 626. First calling party 620, however, may be connected because calling party 620's phone number is on encumbered-line bypass list 626, and called party 606 has designated first calling party 620 as a party that should be connected despite encumbrances. Another caller calling from 404-555-3333, shown in list 626, may not be connected by virtue of the phone number from which she called if she calls at 3 a.m., because her bypass times only allow bypass of an encumbrance from 8 a.m. to 10 p.m.
Each of these preferences, whether they be set to times of a restricted call reception status (an example of an encumbrance) and a non-restricted call reception status, an on setting or off setting, phone numbers and pass-codes for an encumbered-line bypass list, names and/or details associated with the phone numbers and pass-codes, and the bypass times for each phone number and pass-code, may be modified by the subscriber as set forth in FIG. 10.
As part of this preferred embodiment, in step 652 the interface system receives a subscriber's attempt to access a URL to communicate with the communications network. Typically, subscribers attempt to access the URL to update a particular service, but may do so for other reasons. Services may include a restricted status service, another service capable of encumbering a phone line, or another type of service.
Proceeding to step 664, the interface system sends subscriber-based service settings. These service settings can then be displayed, reviewed, and modified by the subscriber. Preferably, these service settings can include stored or default encumbered-line bypass list data, forwarding numbers, pass-codes, and an on or off setting for the entire service. The stored or default encumbered-line bypass list data preferably includes phone numbers and pass-codes stored in the stored encumbered-line bypass list data. In an exemplary embodiment, the stored or default encumbered-line bypass list data is presented to the subscriber through the interface system in an easy-to-update table. These service settings also preferably include applicable categories and/or links. Further, these service settings and/or applicable categories or links data are related to one or more services to which the subscriber subscribes. As part of step 664, the interface system may also send information related to services to which the subscriber does not yet subscribe.
In an exemplary embodiment, the interface system sends one or more call markers relating to one or more telephone calls made from or received by the subscriber to the subscriber through the interface system. Preferably, the call markers include the phone number of one or more parties that called or were called by the subscriber. Also preferably, the call markers include a caller identification of a party that called or was called by the subscriber. The caller identification may include the calling party's name, location from which the calling party called, a timestamp of the time a party called or was called by the subscriber, or otherwise.
In step 666, the interface system receives desired changes from the subscriber, which may include new data on changes to the subscriber's encumbered-line bypass list, other preferences shown on screen 614, or other preferences and options discussed or implied herein. Preferably, such changes may be completed with a minimum number of keystrokes. In an exemplar embodiment, the subscriber may click on each call marker listed in a table (step 664) to add that phone number to his or her encumbered-line bypass list, along with associated details to an accompanying name/detail list. Also preferably, the interface system allows the subscriber to add services and other features and details. The interface system then waits to receive such changes or an indication that the subscriber has completed his or her communication.
FIGS. 13–16 are flow diagrams showing examples of preferred embodiments of a method in accordance with the present invention. These figures and the description set forth below describe a method whereby an Interactive Voice Response (IVR) system interacts with a subscriber.
In step 1002 the IVR system receives identifying data from the subscriber. Preferably this data is based on the phone number from which the subscriber is calling, or a subscriber-code that the subscriber enters. After receiving the identifying data from the subscriber, the IVR system validates, in step 1004, the subscriber as a subscriber of a service by comparing the identifying data with an identifying-data record. The identifying-data record is preferably stored in a database accessible by the communications network.
In step 1206, if the IVR system receives, for example, a one-digit, the IVR system collects that digit according to step 1208, proceeds to step 1210, and then to step 1212 where it plays back the phone numbers in the encumbered-line bypass list. As part of step 1212, the IVR system preferably guides the subscriber by presenting each of the phone numbers or pass-codes within the encumbered-line bypass list to the subscriber in order. The IVR system can also include particular details. These particular details could, for example, include information such as the name of the person associated with the phone number. The name of the person could be associated with the number by public record, by receipt from the person having such number, by receipt from the subscriber, by having been previously received from the subscriber and stored in information manager 610 or database 502, or by some other means.
In step 1214 the IVR system prompts the subscriber to keep or change a particular phone number or pass-code in the encumbered-line bypass list. Preferably the IVR system also prompts the subscriber to edit the phone numbers and pass-codes and associated details that are on the subscriber's encumbered-line bypass list.
With the above steps proceeding from step 1206 described, the following sets forth another set of steps potentially proceeding from step 1206. As set forth above, the IVR system prompts the subscriber according to step 1206. If the IVR system receives a two-digit, for example, rather than a one-digit as set forth above, the IVR system collects that digit according to step 1208 and proceeds to step 1224 and then to step 1226. In step 1226 the IVR system prompts the subscriber to enter new phone numbers and pass-codes to add to the subscriber's encumbered-line bypass list, and preferably associated details for those numbers, or to enter a star-digit if the subscriber is finished.
From step 1226, the IVR system collects digits from the subscriber according to step 1228. If the IVR system collects a phone number or pass-code, the IVR system plays such number back to the subscriber, step 1230. After playing back the number according to step 1230 the IVR system prompts the subscriber to either keep or change the phone number or pass-code that the subscriber just entered, step 1232.
In step 1234 the IVR system collects, for example, either a one-digit or a two-digit from the subscriber. In cases where the IVR system collects the one-digit, step 1236, it then saves the phone number or pass-code that the subscriber previously entered, step 1222. Preferably it saves the phone number or pass-code by storing it with the encumbered-line bypass list in a database accessible by a communications network. Also preferably, the IVR system updates the encumbered-line bypass list when it receives changes to the phone numbers and pass-codes. In cases where the IVR system collects the two-digit, step 1238, the IVR system proceeds to step 1226.
Preferably, the IVR system then allows the subscriber to continue to input numbers until the phone numbers and pass-codes are correct and continue to be able to keep correcting them or allowing the subscriber to continue entering additional phone numbers and pass-codes into the encumbered-line bypass list until the subscriber is satisfied, either by the process described in FIG. 15 or some other similar process.
If, after prompting the subscriber according to step 1226, the IVR system receives an asterisk from the subscriber, step 1228, the IVR system proceeds to step 1240, then proceeds to step 1244. In step 1244, the IVR system sends updates to the phone numbers and pass-codes, associated details, or other information to the information manager. Preferably the IVR system also sends the update to an intelligent peripheral of the communications network. In an exemplary embodiment, the IVR system sends an update list to an SCP of the communications network. After so doing, the IVR system returns to the main menu, step 1246.
Returning to step 1206. In cases where the IVR system has been requested to play back the phone numbers and pass-codes on the subscriber encumbered-line bypass list and every number in the subscriber encumbered-line bypass list has been played back to the subscriber, the IVR system proceeds to step 1242.
In step 1242 the IVR system, if it does not reach the maximum number of phone numbers and pass-codes in an encumbered-line bypass list, returns to step 1226. In cases where the maximum number of phone numbers and pass-codes that is allowed in the encumbered-line bypass list has been reached, the IVR system, according to step 1242 proceeds to step 1244. The system then updates the communications network according to step 1244 and returns the subscriber to the main menu, step 1246.
US4634811 Jun 28, 1984 Jan 6, 1987 Amtel Communications, Inc. Call screening system
US4825462 Dec 4, 1987 Apr 25, 1989 Jacques Lewiner Devices for delivering information on their communications to subscribers of telephone lines
US5579379 Oct 18, 1994 Nov 26, 1996 Bell Atlantic Network Services, Inc. Personal communications service having a calling party pays capability
US5651055 Jun 29, 1995 Jul 22, 1997 Lucent Technologies Inc. Digital secretary
US5757899 Aug 28, 1997 May 26, 1998 Boulware; Joni R. Call screening using subscriber specified timers and schedules
US5809114 Aug 15, 1997 Sep 15, 1998 The Telephone Connection Anonymous interactive telephone system
US5812656 Nov 15, 1995 Sep 22, 1998 Lucent Technologies, Inc. System for providing prioritized connections in a public switched network
US5999613 * Sep 25, 1997 Dec 7, 1999 U. S. West, Inc. Method and system for processing incoming calls during calls-in-progress
US6115457 Dec 12, 1997 Sep 5, 2000 Northern Telcom Limited Marking and screening telephone calls
US6243459 Jan 20, 1998 Jun 5, 2001 Agere Systems Guardian Corp. Telephone with adaptive speed dial mechanism
US6289092 Jan 30, 1998 Sep 11, 2001 Fujitsu Limited Method and apparatus for selectively suspending or activating a call waiting service
US6295355 Mar 31, 1999 Sep 25, 2001 Microsoft Corporation Learned speed dialing
US6404860 Feb 9, 2000 Jun 11, 2002 Ss8 Networks, Inc. System and method for internet call management with text-to-speech messaging
US6459706 Nov 18, 1998 Oct 1, 2002 Nec Corporation Message-passing communication system generating task for monitoring a specific communication path
US6519331 Sep 1, 2000 Feb 11, 2003 Alcatel Telecommunications system, service control point and method for pre-screening telephone calls to help prevent telephone toll fraud
US6542596 Aug 12, 1999 Apr 1, 2003 Bellsouth Intellectual Property Corporation System and method for privacy management
US6647108 Jan 2, 2001 Nov 11, 2003 Verizon Services Corp. Internet call manager
US6724878 Oct 11, 2001 Apr 20, 2004 At&T Corp. Method and system for processing a telephone call
US6775370 Oct 19, 2001 Aug 10, 2004 At&T Corp. Method and system for processing a telephone call while on-line
US6950402 Feb 15, 2001 Sep 27, 2005 Persona Software, Inc. Web-enabled call management method and apparatus
US20020064272 Nov 30, 2000 May 30, 2002 David Naghi Call-waiting apparatus and method
US20020076022 Dec 20, 2000 Jun 20, 2002 Bedingfield James C. System and method for monitoring incoming communications to a telecommunications device
US20020080944 Dec 21, 2000 Jun 27, 2002 J. Carl Bedingfield System and method for preserving caller privacy
US20020146107 * Apr 10, 2001 Oct 10, 2002 Baals Kimberly A. Selective call waiting
US20030076941 * Oct 24, 2001 Apr 24, 2003 Sbc Technology Resources, Inc. System and method for restricting and monitoring telephone calls
US20030112930 Dec 18, 2001 Jun 19, 2003 Bosik Barry S. Call management system responsive to network presence
US20030142807 Sep 26, 2002 Jul 31, 2003 Dolan Robert A. Method and apparatus for providing expanded telecommunications service
1 ADSL 98-107 "Core Network Architectures for ADSL", Access Systems, Mar. 1998.
2 Andrew S. Tanebaum, Computer Network, Pretence Hall, (3rd ed. 1996).
3 K.R. Frank, et al., "Fast Access ADSL Architecture Description," TM-ATSEC-01-98-084.
4 U.S. Appl. No. 09/372,676, filed Aug. 12, 1999.
5 U.S. Appl. No. 09/372,746, filed Aug. 10, 1999.
6 U.S. Appl. No. 09/454,917, filed Dec. 6, 1999.
7 U.S. Appl. No. 09/456,316, filed Dec. 8, 1999.
8 U.S. Appl. No. 10/108,706, filed Mar. 29, 2002.
9 U.S. Appl. No. 10/183,388, filed Jun. 28, 2002.
10 U.S. Appl. No. 10/183,850, filed Jun. 28, 2002.
11 U.S. Appl. No. 113,698, filed Mar. 30, 2002.
12 www.granitestatetelephone.com/sfh<SUB>-</SUB>selacc.html, 2002, 2 pages.
13 www.paulbunyan.net/telephone/rates/features/selectcallaccept.html , 2001, 1 page.
US7454003 * Mar 21, 2006 Nov 18, 2008 Miller Asset, Llc. Telephone call control methods
US7769146 * May 3, 2006 Aug 3, 2010 Sprint Spectrum L.P. Method and system for connecting calling and called parties when called party is leaving message for calling party
US7844034 Jul 6, 2005 Nov 30, 2010 Sprint Spectrum L.P. Method and system for bridging third parties into calls
US7848503 * Jul 27, 2006 Dec 7, 2010 Cycos Aktiengesellschaft Method for processing an untaken call on a called communication terminal
US7886232 Sep 12, 2006 Feb 8, 2011 Edmund J Fish Presence and geographic location notification based on a delegation model
US8352872 May 11, 2007 Jan 8, 2013 Facebook, Inc. Geographic location notification based on identity linking
US9281961 Jan 28, 2011 Mar 8, 2016 Facebook, Inc. Presence and geographic location notification based on a delegation model
US9712672 * Oct 1, 2009 Jul 18, 2017 Avaya Inc. Call response system
US20060178173 * Mar 21, 2006 Aug 10, 2006 Larry Miller Telephone call control methods
US20080043966 * Jul 27, 2006 Feb 21, 2008 Cycos Aktiengesellschaft Method for processing an untaken call on a called communication terminal
US20090103701 * Oct 17, 2007 Apr 23, 2009 Avaya Technology Llc Call Screening Via Observing Called-Party Behavior
US20090172564 * May 11, 2007 Jul 2, 2009 Aol Llc Geographic Location Notification Based On Identity Linking
U.S. Classification 379/211.02, 379/210.02
Cooperative Classification H04M3/436, H04M2203/2005, H04M3/53308
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MULLIS, KAREN;SIMPSON, ANITA HOGANS;REEL/FRAME:012980/0314