Controller for the intelligent interconnection of two communication networks, and method of use for same

Information

  • Patent Grant
  • 9083719
  • Patent Number
    9,083,719
  • Date Filed
    Wednesday, May 29, 2013
    10 years ago
  • Date Issued
    Tuesday, July 14, 2015
    8 years ago
Abstract
A caller ID based call routing feature. A processing system in the public switched telephone network (PSTN) receives first identifying information for identifying the source of a telephone call and associates additional information stored in a memory with the first identifying information. The additional information may then be transmitted to the subscriber via the Internet for display. Another feature is a branch calling feature where the subscriber may program a processing system within the PSTN to forward an incoming call to two or more end units (e.g., telephones) simultaneously. If the call at an end unit is answered, answer supervision signaling is transmitted back to the processing system which then terminates all other calls. The processing system then connects the calling party to the subscriber. The branch calling may be made for any combination of local, long distance, and cellular telephone numbers.
Description
FIELD OF THE INVENTION

This invention relates to telephone services and, in particular, to a system for allowing a subscriber to select features of the subscriber's telephone service and to various novel features that can be selected.


BACKGROUND OF THE INVENTION

People have used various means for limiting interruptions due to the telephone. In the past, people used switchboards and secretaries to screen incoming, or inbound, calls. Voice mail systems took over some of this role both in the home and in the central office. Today, there are web-based companies managing 3rd-party call control, via the toll-switch network, which allow users to enter call control information through a web portal. There are also edge devices in each of the public telephone company's central offices which provide local control, but offer an extremely limited number of features and do not provide true 3rd-party call control.


The web-based toll systems provide good user interaction but they are not economical and cannot take advantage of local number portability because they do not provide local control and connectivity.


The Public Switched Telephone Network (PSTN) consists of a plurality of edge switches connected to telephones on one side and to a network of tandem switches on the other. The tandem switch network allows connectivity between all of the edge switches, and a signaling system is used by the PSTN to allow calling and to transmit both calling and called party identity.


Until now, optional features were provided by the local service telephone company (telco) through the edge switch at the central office (CO). It was not possible to provide optional features through any other means. Control of these features was done through the first party (calling party) or the second party (called party), or worse yet, manually by calling the business office.


In the past, numerous devices have been built that allow the connection of two lines together at an edge switch. These devices can be used to add features to a telephone network by receiving a call on one line and then dialing out on another line. The problem with these devices is that, because they are connected through an edge switch, transmission losses and impairments occur, degrading the overall connection. In addition, signaling limitations prevent full control, by the subscriber or the system, over the call.


A preferred embodiment of the inventive system described herein connects at the tandem, thereby eliminating these problems.


In the edge devices residing in the PSTN central offices, the 1st party (the calling party) has numerous features available (dialing options). The 2nd party (called party) also has options available such as call forwarding, but these features typically require access from the first or second party's device and are extremely awkward to program. The user interaction is not only awkward, it is limited and requires interaction with the telephone company to provision them. In other words, past systems for provisioning, meaning addition, modification, or control of telephone features, required a subscriber to make the feature selection through the telephone business office. Central office workers would then implement the provisioning under request of the business office.


Call Forwarding is one popular provision. There is signification transmission degradation for Call Forwarding to take place. The calling party pays for a call to the edge device, and the edge subscriber, the called party, pays for the call to the forwarding number. For enhanced inbound call control to occur, a direct 3rd-party call control means is needed.


A variety of services have arisen to address the problems mentioned above. Many of these systems allow the called party to make changes to his/her call forwarding attributes which do not allow direct 3rd-party call control. These services provide good user interaction, some via the internet, but they rely upon the toll network through the use of “800” numbers.


This requires the subscriber to pay by the minute and does not allow the subscriber to take advantage of number portability in order to obtain 3rd-party call control. There are other toll network mechanisms for remote call forwarding. For example, MCI offers a service where the customer can remotely change the forwarding target number for “800” numbers. Contacting the ultimate end-user before terminating the first incoming call is similar to the manner in which “800” credit calls and collect calls are processed, but these are not done at the local subscriber level.


In addition to these toll services, there are edge devices that perform some of the same services. Edge devices such as phones and PBXs that include voice mail, inter-active voice response, call forwarding, speed calling, etc., have been used to provide additional call control. These devices allow the phone user direct control over incoming and outgoing calls. The disadvantage of edge devices is that they add cost, degrade voice and transmission quality, can be difficult to program, are not easily programmed remotely, can require the user to pay for two lines, provide lower quality of service, and cannot provide the same level of functionality as a system that controls the PSTN directly. There are Voice Over Internet Protocol (VoiP) products emerging that provide better user interfaces and control but they do not take advantage and voice quality of the PSTN.


BRIEF SUMMARY OF THE INVENTION

A method comprising receiving at a controller call data which is associated with a first call via a first communication network, accessing control criteria by the controller based upon the call data, initiating a second call via a second communication network by the controller using the call data and the control criteria, wherein the first and the second communication networks are each a voice over IP (VOIP) network, and enabling communication between the first call and the second call by the controller.


A controller including circuitry and/or software configured to receive call data which is associated with a first call via a first communication network, access control criteria based upon the call data, initiate a second call via the second communication network using the call data and the control criteria, wherein the first and the second communication networks are each a voice over IP (VOIP) network, and enable communication between the first call and the second call.


Other objects and features of the present invention will become apparent by a review of the specification, claims and appended figures.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates the tandem access controller (TAC) in one embodiment of the present invention connected to the existing PSTN tandem switch, the TAC providing features for the subscriber's telephone as requested by the subscriber via the web.



FIG. 2 illustrates a system similar to FIG. 1 but showing multiple tandem switches and TACs and also showing how the subscriber may, in additional to using the standard telephone, make phone calls using Voice Over IP via a conventional digital telephone.



FIGS. 3A and 3B is a flowchart of one method that a person may use to set up a subscriber account and to designate features the subscriber would like for his/her telephone.



FIG. 4 is a flowchart of a method that can be performed by the TAC in response to the subscriber (or other service) controlling the TAC, using the web (or other packet-based system), to change the subscriber's telephone provisioning or perform another function, such as make a VoIP call.



FIG. 5 is a flowchart of a method that can be performed by the TAC in response to an inbound call to the subscriber.



FIG. 6 is a flowchart of a method performed by the subscriber and the TAC when the subscriber desires to make an outbound call via the web or using a conventional telephone.



FIG. 7 illustrates a system, using the TAC, that allows wireless cell phones to obtain the same provisioning options as the conventional telephones.



FIG. 8 illustrates a system, using the TAC, that allows fax and modem calls to benefit from the provisioning offered by the TAC.



FIG. 9 is a flowchart of possible scenarios using the caller ID based feature.



FIG. 10 is a flowchart of possible scenarios using the branch calling feature.





DETAILED DESCRIPTION OF THE INVENTION


FIG. 1 shows a tandem access controller (TAC) 10 that allows an authorized subscriber 12 to establish 3rd-party control criteria for calls to the subscriber's telephone 14 (having a “public” phone number that callers dial). In one embodiment, the TAC 10 is a programmed processor. The TAC 10 may use any combination of hardware, firmware, or software and, in one embodiment, is a conventional computer programmed to carry out the functions described herein.


The TAC 10 is connected to or inside the conventional PSTN tandem switch 16 such that calls may flow through the TAC 10 in the same manner as the existing PSTN tandem switch, except that additional 3rd-party features are applied to the call. As is well known, PSTN tandem switches are exchanges that direct telephone calls (or other traffic) to central offices 17,18 or to other tandem switches. Details of the operation of the existing phone network may be found in the publication entitled “New Net SS7 Tutorial,” by ADC Telecommunications, copyright 1999, incorporated herein by reference. Additional details may be found in the numerous books describing the PSTN.


The PSTN tandem switch 16 directs a first call (from the calling party 20 to the subscriber's phone 14 using the subscriber's public phone number) to the TAC 10, which in turn places a second call, subject to 3rd-party control information, to the subscriber's “private” phone number without yet terminating the first call. The TAC 10 is connected within the subscriber's local service area so calls from TAC 10 to the subscriber do not incur a toll. When the subscriber 12 terminates (or answers) the second call, the TAC 10 terminates the first call and connects it to the second call, thereby connecting the calling party 20 to the subscriber 12. Hence, the calling party essentially calls the TAC 10, using the subscriber's public phone number, and the TAC 10, after processing the call using the selected features, calls the subscriber, as appropriate, using the subscriber's private phone number and connects the two calls. The process is transparent to the parties.


The TAC 10 is connected inside the PSTN in the sense that it is not an edge device such as a PBX or central office (CO) switch because it does not connect directly to subscribers. Rather, it redirects calls to subscribers. The TAC 10 provides intelligent interconnection between a calling party and a subscriber.


The reader should keep in mind that although only one tandem switch 16 is shown in FIG. 1, the invention will apply equally well to a network of tandem switches, as shown in FIG. 2. FIG. 2 also illustrates how the subscriber can make calls using voice over IP via a conventional digital telephone 21.



FIG. 1 illustrates the preferred method for an authorized subscriber to modify the 3rd-party control criteria by means of the world wide web 22 (and web server 23) using an internet browser. By “authorized” we mean a subscriber who is registered and has logged-in with appropriate security and password controls. The subscriber 12 interacts with the web 22 via the Internet to quickly and easily specify the enhanced 3rd-party call control features. Web 22 then relays this information, in appropriate form, to the TAC 10. Preferably, the link to the TAC 10 uses a secure protocol. Examples of features that can be selected by the subscriber include: conditional call blocking, call forwarding, call altering, time of day conditions, day of week conditions, follow-me, caller recognition/password, caller ID, call screening/retrieval from voice mail, speed dialing, interactive voice response, and speech recognition. Any other feature could be added. These features can be implemented in the TAC 10 using known software techniques since such features are known. Message outgoing call control includes: click-to-dial calling and group calling/messaging.


The invention may also include ivr/vm/voverip.



FIG. 1 uses a public internet portal connected via a data link to the TAC 10 or other interface system. As a registered subscriber, a user logs onto the portal (FIGS. 3A/3B) and is granted access, allowing the user to make additions or changes to features such as speed calling, call forwarding, selection of such descriptors as time of day, busy status, caller ID status, etc. A user-friendly web page leads the subscriber through the various procedures and available features. The selections made by the subscriber are translated into provisioning data and transmitted to the TAC 10. The TAC 10 in turn keeps track of incoming and outgoing calls based on this information.


The subscriber can also program a set of the call control features via a telephone link in the event a data link connection is unavailable.



FIG. 4 is a flowchart of actions that may be taken by the TAC 10 in response to the subscriber (or other service) controlling the TAC, using the web or other packet-based system, to change the subscriber's telephone provisioning or perform another function, such as make a VoIP call.



FIG. 5 is a flowchart of actions taken by the TAC 10 in response to an inbound call (using the subscriber's public phone number) to the subscriber. Examples of some of the actions taken by the TAC 10 are:

    • Receives SS7 data indicating an incoming call
    • Stores phone numbers downloaded from provisioning system
    • Charts identity of calling party
    • Checks time of day
    • Stores lists of numbers in groups used for processing incoming calls
    • Places outgoing calls in response to incoming calls according to information downloaded on the data link.


Incoming call data is received by the TAC 10 from the tandem switch 16. The TAC 10 processor checks calling and called numbers, class of service, time of day, number lists, etc. In some cases additional data is gathered from the calling party via a DSP (Digital Signal Processing) system and stored in the system memory. The DSP system is used to play call progress tones and voice announcements as required. Voice announcements can be played through the DSP system. In response to the call data, an outgoing call to the subscriber 12 may be placed back through the tandem switch 16 by TAC 10. The TAC 10 links the two calls and monitors the connection.


Information about the call may be collected by the TAC 10 and sent to the subscriber or a 3rd party for display. Such information may be the length of the call or information used to bill the subscriber for the use of the system. The provisioning system can also collect control information from a 3rd party and relay it back to the TAC 10, which will then affect the call accordingly.



FIG. 6 is a flowchart of actions taken by the subscriber 12 and the TAC 10 when the subscriber desires to make an outbound call via the web or using a conventional telephone. When using the web to place a call, the subscriber may simply click a name on the computer screen 26 using a mouse.



FIG. 7 illustrates a system, using the TAC 10, that allows wireless cell phones 28 to obtain the same provisioning options as the conventional telephones 14. A local cell 30 and a cell switch 32 are also shown in FIG. 7.



FIG. 8 illustrates a system, using the TAC 10, that allows fax and modem calls to benefit from the provisioning offered by the TAC 10. The TAC 10 may interface the ISP 36 through the web 22.


One embodiment of the invention allows a subscriber to view the current state of his/her telephone via the Internet. Internet is a term of art by which we mean an interconnection of packet switched networks. Prior to this system there was no way for a user to examine the status of a telephone line. Recently, several products have been introduced that provide a means of examining the voice message boxes.


An internet portal is connected via a data link to the TAC 10. When a user logs onto the internet portal and is granted access to an individual subscription, the user can examine the status of calls/features. This information is transmitted from the TAC 10 to the web portal and translated into user viewables. The TAC 10 keeps track of incoming and outgoing calls based on this information.


The TAC 10 may be implemented using conventional processor hardware. The connection to the tandem switch 16 may be as simple as a telephone circuit, since the TAC 10 receives an incoming call from a caller and processes the call. Devising the software/firmware use to control the TAC 10 is well within the capability of those skilled in the art since the various control features that can be made available are generally already known.


Certain advantages that can be obtained using the invention include the following:

















Web-Based Telecom Navigator



 Manage Incoming Call Control



  Conditional Call Blocking/Forwarding/Alerting



  Time-of-Day, Day-of-Week, Follow-Me,



  Caller Recognition/Password



  Caller ID, etc.



  Call Screening/Retrieval from Voice Mail



  Interactive Voice Response and Speech Recognition



 Manage Outgoing Call Control



  Click-to-Dial Calling



  Group Calling and Messaging



 Web-Based Billing



Web-Driven Personal Communications Management



  Cost-Effective Single Phone Number Access



  On-Line “Personal Digital Assistant”



  On-Line “Telcom Navigator”



  Inspired User Interaction



  Secure and Reliable Technology



Cost-Effective Single Phone Number Access



 CLEC Status



  Free Local Calls, Incoming Calls (not 800 Toll Service)



  Retain Current Number (Local Number Portability)



  Low-Cost Calling Throughout LATA



  Flat-Rate Foreign Exchange



  Single Installation Covers Entire LATA



  VoIP Toll-Bypass



 Compatible With Existing Devices, Standards



  Standard DTMF and VoIP Phones



  Wireless Phones



  Standard Wired/Wireless and PIM Browsers



Web-Based Personal Digital Assistant



 Centralized and Consistent Personal Data



  Build Once, Use Anywhere



  Private/Public Phone Directories and Calendars



  “Post-It” Style Annotation of Numbers



 Web Dialing



  Click-to-Dial from Web Pages, Directories, Calendars



  Multiple Phone List Management



 Unified Messaging



  Voice Mail Access, Prompts, Alert Via Web



User Interaction



 Expected Behavior



  Compatible with Familiar Products (e.g. Palm Pilot)



  Commonality Between All Wired and Wireless



 Mode-Based Definition and Selection



  Vacation, Dinner Time, Go Away, Family Call Waiting



  Templates



 Learning Modes



    Persona-Based User Interaction Design



    Speech recognition



    Windows drag and drop



    Automatic Data Capture



    Build Phone List Based on Collected Usage Information



    Drag and Drop Into Lists



Secure and Reliable Technology



 Separate Web-Site and Link Gateway



   No Direct External Access to Gateway



   Additional Security Layer



   No Denial-of-Service to Voice Links



  VoIP Link Degradation Detection



   Automatic Cutover to PSTN



  E-Commerce Security



   Billing Encryption Caller










ID Based Call Routing


One advantage of using TAC 10 is its ability to enhance caller ID information. Caller ID is a common feature where a calling party's telephone number is transmitted to the called party's telephone so it can be displayed on a small display screen in the telephone. This caller ID information is provided by the calling party's central office switch. Signaling System No. 7 (SS7) is a global standard for telecommunications and defines the procedures and protocol by which network elements in the PSTN exchange information (including the caller ID) over the telephone network for call set up, routing, and control. In some telephone sets, including wireless telephones, the name of the caller associated with the telephone number is also displayed on the called party's display screen.


TAC 10 can use this automatically generated caller ID signal to provide an enhanced set of caller ID related features. One such feature is the association of the standard caller ID information with additional information about the caller stored in a memory addressed by TAC 10. The enhanced caller ID information provided through TAC 10 provides a valuable tool to the subscriber in handling incoming calls. The basic caller ID information, such as the caller's telephone number and name, can still be sent to the subscriber's phone and displayed in a conventional manner while the enhanced caller ID information may be displayed on the phone display or on the subscriber's computer monitor via the web.


The caller ID signals, pursuant to the SS7 protocol, are detected by TAC 10 when a calling party calls the subscriber using the subscriber's public telephone number, as previously described. TAC 10 then uses the basic caller ID data to address a look-up table (LUT) containing any additional information that the subscriber has entered into the LUT's memory locations for association with that caller ID data. FIG. 8 shows such a LUT 40 within or connected to TAC 10.


In one example, the subscriber may identify a prospective calling party's telephone number to TAC 10 via the Internet and then associate the number with any other information for storing in LUT 40. Such other information may be all the possible callers using the calling telephone, personal information regarding the calling party, billing information, business information, account numbers, past discussions with the caller, or any other information. When TAC 10 detects the caller ID signals, TAC 10 addresses LUT 40 and downloads the retrieved information to the subscriber's telephone display or to the subscriber's computer via the web. Since TAC 10 (including LUT 40) stores this additional information, the subscriber is not required to personally provide processing or memory devices for this feature.


Multiple subscribers use the same TAC 10 and LUT 40 but only the memory locations in LUT 40 authorized for access by a particular subscriber are available to that subscriber.


A subscriber may program TAC 10 using the various means described previously to perform any number of features on an incoming telephone call based upon the caller ID data. Such features include forwarding a call associated with that particular caller ID data to one or more other telephones, or blocking calls associated with that particular caller ID data. Such calls may be forwarded or blocked only at certain times or on certain days as requested by the subscriber. All of the other features previously described may also be applied based upon the caller ID.


When the calling party elects to block her caller ID information, displaying the caller's number and name on the subscriber's telephone may violate the privacy act, so such a restriction should be programmed into the system. However, TAC 10 may still use the caller ID information for various legal purposes. For example, the subscriber may not wish to receive phone calls from a particular phone number or calling party. The subscriber may transmit to TAC 10 the caller ID information (e.g., the telephone number and/or the name) and instruct TAC 10 to either forward the call, block the call, or transmit any additional information from LUT 40 to the subscriber's phone display or computer monitor for screening the caller.


If caller ID information does not exist, such as where the local telephone company does not offer caller ID, TAC 10, when receiving the incoming call, can transmit an automatic message to the caller to enter identification information. TAC 10 then uses that information to address LUT 40 to identify any associated information in LUT 40 for transmission to the subscriber. TAC 10, in a recorded or simulated voice, can request the caller to enter her phone number via the telephone keypad. Alternatively, TAC can request that the caller speak her name or number, which would then be played to the subscriber or converted to text or a code by TAC 10 to address LUT 40. Alternatively, the caller can enter a personal identification number or any other type of code (e.g., the caller's name) via the keypad, which would identify the caller to TAC 10. Once obtained, the caller ID information entered can be used to route the incoming call via TAC 10 in any way programmed by the subscriber. Call routing can be based on time of day, the caller ID, any web input instructions, a direction by the calling party itself, or any other variable.


This technique is contrasted with 800-type services, which are reverse long distance services requiring the owner of the 800 number to pay for the incoming call. With 800 numbers, the caller ID must be unblocked to identify the amount of the toll. With the inventive technique, even blocked caller ID calls can result in information about the caller being transmitted to the subscriber or used by TAC 10 to selectively perform a function.



FIG. 9 is a flowchart of various scenarios that may be carried out using the caller ID feature.


In step 50 of FIG. 9, an incoming call is received by TAC 10, as previously described, by a calling party calling the subscriber's public telephone number. In all embodiments described herein, the end unit called may be a residential telephone or other communication device connected to the PSTN via a central office, such as a computer, fax machine, or other communication device. The services provided by TAC 10 may be for residential telephone service or for business telephone service.


In step 52, using the SS7 protocol, TAC 10 detects the caller ID signal (CID), if any. Even if the calling party has a blocked CID, the CID is still transmitted to TAC 10; however the blocked caller ID cannot be displayed on the called party's telephone. If the CID is detected, the process continues to steps 54 and 56, which determine whether the CID is associated with any data in a look-up table. Existing data in the look-up table associated with the CID indicates that the caller is a previous caller. If caller ID information is known without ever previously receiving a call from that party, the additional information can still be entered into the look-up table, and the calling party will be treated as not a new caller in step 54.


Assuming the caller has information stored in the look-up table, this additional information is retrieved by TAC 10 and displayed on a web page (step 58) that is accessible by the subscriber via the web. In addition, the caller's name and telephone number may also by displayed (step 60). The information may also be transmitted to the subscriber's telephone for display.


In step 62, TAC 10 performs any programmed function on the call, such as forwarding the call to the subscriber's private telephone number or another number.


The placing of the second call by TAC 10 causes the called phone to ring (step 64) as well as causes the CID and additional information to be available to the subscriber (step 66) on the subscriber's telephone display. When the subscriber answers the phone, TAC 10 completes the connection between the two parties.


The retrieved information from LUT 40 that is transmitted over the web may appear as a screen pop-up on the subscriber's monitor. This CID information can then be reviewed and edited to include new information about the caller provided during the call. The subscriber then downloads this edited information to TAC 10 so future calls from the same caller would display the new information.


In step 54 if it is determined that the CID information is not associated with any existing information in the look-up table, TAC 10 determines whether the CID is blocked (identified in the SS7 protocol) in step 68. If the CID is not blocked, then the CID information is transmitted to the subscriber's telephone when TAC 10 places the call to the subscriber's private number (or any other forwarding number), and the CID is displayed on the subscriber's phone.


In step 68, if it is determined that the CID is blocked, TAC 10 will prompt the caller, via a recorded message or a simulated voice, to press the appropriate touch tone buttons to unblock the CID (step 70). For example, TAC 10 may be programmed to detect that a “1” key is pressed by the caller to unblock CID and then treat the CID information as unblocked. Alternatively, the caller may be required to call back after pressing the proper touch tone keys to unblock the CID in a conventional way.


In step 72, if the CID is now unblocked, the CID is obtained from the caller in step 74. The process also goes to step 74 if, in step 52, the CID is not initially obtained.


In step 76, TAC 10 determines whether the CID signal has been provided by the calling party from either the automatic CID signals or from the caller manually entering the caller's telephone number, name, or PIN, as previously described. If yes, then in step 54 TAC 10 uses the CID information to determine whether the caller is a new caller, and the remainder of the process continues as previously described.


In step 72, if it is determined that the CID remains blocked after TAC 10 has prompted the caller to unblock the CID, then in step 74 it is determined by TAC 10 is step 77 (after reviewing the subscriber's programmed instructions) whether the subscriber is accepting blocked calls. If yes, TAC 10 then places a call to the subscriber's private number or any other number identified by the subscriber, and puts the blocked call through. The blocked CID information would not be transmitted to the subscriber's phone.


If the subscriber's instructions are to not accept blocked calls, then in step 78 the blocked call is not forwarded to the subscriber's phone, or the blocked call is sent to voice mail. Voice mail may be a memory internal to TAC 10, or TAC 10 may transmit a special code to the subscriber's phone that automatically causes the call to be routed to a private voice mail system.


As seen, as long as the caller ID data received by TAC 10 has information associated with it in the look-up table, the stored information can be transmitted to the subscriber even if the caller ID is blocked. Further, even blocked caller IDs can still be used by TAC 10 to perform a routing function on the call. The caller ID feature may be implemented by a software program run by the processing system in TAC 10.


Because the conventional blocked CID information provided by the phone company is never displayed to the subscriber, the tagging system does not violate the privacy act. Known features such as call trace (where CID is provided to law enforcement people), or call return (where the blocked caller can be called back) have established a legal precedent that it is ok to use blocked CID information for certain purposes as long as the caller ID is not disclosed to the called party


Branch Calling


Branch calling is an enhanced telephone feature not believed to be provided on today's public telephone networks. This feature can be easily provided using TAC 10.


Branch calling is a technique where a caller places a first call intended for a called party to TAC 10. After receiving the call, TAC 10 looks up the call handling instructions programmed into TAC 10 by the subscriber via the web, via the telephone, or via any other technique. One set of these instructions is branch calling, which instructs TAC 10 to simultaneously call any number of different telephone numbers programmed into TAC 10 by the subscriber. The called phone numbers may be any combination of local, long distance, or cellular numbers.


When a party answers one of the ringing lines, the answering party is connected to the calling party, and the other calls are abandoned.


For branch calling to operate in the most desirable manner, the system must detect that a call has been answered in order to terminate the calls to the other telephones (or other end units). Accordingly, some form of answer supervision must be present. Answer supervision is implemented inside the PSTN but generally not available to private networks (e.g., PABXs). Since SS7 signaling supports answer supervision, it is easy for this branch calling feature to be provided through TAC 10 since TAC 10 is connected inside the PSTN.


Prior art systems without answer supervision must call each forwarding number sequentially, whereby after a certain number of preprogrammed rings, the calling stops and the next number is called until someone answers the phone. Because a ringing time-out must occur before the next call can be tried, an unrealistically long delay can occur before the call is placed to the proper telephone and finally answered. In contrast, the present invention allows TAC 10 to ring all the numbers simultaneously so the call can be answered quickly.


It is desirable that the answer supervision signaling not be delayed so that the calling and called parties may be connected quickly when the call is answered and so that during the delay time two parties do not answer two different ringing phones.



FIG. 10 is a flowchart of some scenarios in branch calling, whereby an incoming call to TAC 10 causes TAC 10 to place at least two new calls simultaneously and, when one of these phones is answered, the remaining calls are abandoned.


In step 80 of FIG. 10, TAC 10 receives an incoming call.


In step 82, TAC 10 looks up the routing instructions for the DNIS (Dialed Number Identification Service) and caller ID (if any). The DNIS identifies the number that was called, and the caller ID (CID) identifies the calling telephone number and sometimes the caller. DNIS works by transmitting the touch tone digits to TAC 10. A subscriber for TAC 10 may program TAC 10, as previously described, to perform any number of functions based upon the DNIS number, the CID, the time of day, or based upon any other factor. Such instructions may be stored in a look-up table addressed by the subscriber's public phone number (identified by the DNIS number). Since multiple subscribers will be using the same TAC 10, TAC 10 needs to know what number was dialed in order to perform the function on the call selected by the subscriber.


In step 86, TAC 10 identifies the features to apply to the incoming call. If the instructions are to block the call, then TAC 10 blocks the call in step 87. In the present example, it is assumed that the feature the subscriber wants to apply is a branch calling feature where two telephone numbers are to be called by TAC 10.


In step 88, TAC 10 generates a ring back tone to the caller to indicate that a telephone is ringing.


In step 90, TAC 10 places a call to a first telephone number, which causes the called phone to ring (step 92). Parallel operations are performed for a second phone number in steps 93 and 95.


In step 96, it is determined by TAC 10 whether the first phone has been answered using answer supervision signaling provided by SS7 (step 98).


In response to the answer supervision signaling, TAC 10 abandons the other call to the second telephone (step 100).


In step 102, TAC 10 completes the phone call by connecting the calling party to the answered telephone. This process may be applied to other than telephones, such as computers or other types of communication equipment.


In step 96, if the call is not answered after the ring, it is determined whether the other telephone has been answered (step 104). If not, the two phones continue to ring.


If it is determined in step 104 that another telephone has been answered (i.e., the answer supervision signal has been received by TAC 10), the call to the first telephone is abandoned (step 106).


The same operation is performed with respect to the second telephone call in steps 108-113.


Any number of telephone calls may be simultaneously placed by TAC 10 in response to a branch calling instruction.


In step 86, if the instructions programmed by the subscriber are to block the call, then TAC 10 blocks the call in step 87.


While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that changes and modifications may be made without departing from this invention in its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications that fall within the true spirit and scope of this invention.


Acronyms

    • PPN—Public Phone Number allocated by oneCloud (known to public, on business cards, etc., rings oneCloud).
    • LPN—Local Phone Number from local telco (rings user's phone but is only known to oneCloud and local telco).
    • UIS—User Interaction System—web site user interfaces with in order to control phone features.
    • TAC—Tandem Access Controller—System that directly accesses the PSTN.

Claims
  • 1. A method comprising: receiving at a controller call data which is associated with a first call via a first communication network;accessing control criteria by the controller based upon the call data;initiating a second call via a second communication network by the controller using the call data and the control criteria, wherein the first and the second communication networks are each a voice over IP (VOIP) network; andenabling communication between the first call and the second call by the controller.
  • 2. The method of claim 1, wherein the call data includes a call request.
  • 3. The method of claim 1, wherein the call data includes a telephone number.
  • 4. The method of claim 1, wherein the call data includes an IP address.
  • 5. The method of claim 1, wherein the call data includes a VOIP signaling message.
  • 6. The method of claim 1, wherein the control criteria includes security measures.
  • 7. The method of in claim 1, wherein the control criteria includes a selection of a telephone number.
  • 8. The method of claim 1, wherein the control criteria includes a feature selection.
  • 9. The method of claim 6, wherein the security measures include call logging.
  • 10. The method of claim 6, wherein the security measures include web based billing.
  • 11. The method of claim 6, wherein the security measures include a prevention of denial of service attacks.
  • 12. The method of claim 6, wherein the security measures include authentication of a calling party of the first call.
  • 13. The method of claim 6, wherein the security measures include no direct access to a gateway.
  • 14. The method of claim 1, further comprising: supplying the control criteria via a packet interface.
  • 15. The method of claim 1, wherein the control criteria is derived from entries made by a user.
  • 16. The method of claim 1, wherein the control criteria had been previously downloaded to the controller.
  • 17. The method of claim 1, wherein the enabled communication between the first call and the second call is routed through the controller.
  • 18. The method of claim 1, wherein the enabled communication between the first call and the second call is enabled via an external device.
  • 19. The method of claim 1, wherein the controller comprises a distributed architecture spanning multiple discrete devices.
  • 20. The method of claim 1, wherein the controller is located at a border between the first communication network and the second communication network.
  • 21. The method of claim 1 wherein one of the first and second calls is a voice call.
  • 22. The method of claim 1 wherein one of the first and second calls is a data call.
  • 23. The method of claim 1 wherein one of the first and second calls is a fax call.
  • 24. The method of claim 1 wherein one of the first and second calls is a short text message.
  • 25. The method of claim 1 wherein one of the first and second calls is a VOIP session.
  • 26. The method of claim 1 wherein the second call is a call leg.
  • 27. The method of claim 1, wherein one of the first and the second communication networks is coupled to one of a plurality of switching facilities of a third communication network, wherein the third communication network comprises: edge switches for routing calls from and to subscribers within a local geographic area, andthe plurality of switching facilities each for routing calls to the edge switches or to others of the plurality of switching facilities.
  • 28. The method of claim 27, wherein one of the first and second communication networks is coupled to the one switching facility via a gateway.
  • 29. The method of claim 27, wherein the one switching facility is a PSTN Tandem Switch, and the controller is a Tandem Access Controller.
  • 30. The method of claim 29, wherein the coupling to the Tandem Switch includes an STP.
  • 31. The method of claim 30, wherein the coupling to the Tandem Switch uses SS7 signaling.
  • 32. A controller including circuitry and/or software configured to: receive call data which is associated with a first call via a first communication network;access control criteria based upon the call data;initiate a second call via a second communication network using the call data and the control criteria, wherein the first and the second communication networks are each a voice over IP (VOIP) network; andenable communication between the first call and the second call.
  • 33. The controller of claim 32, wherein the call data includes a call request.
  • 34. The controller of claim 32, wherein the call data includes a telephone number.
  • 35. The controller of claim 32, wherein the call data includes an IP address.
  • 36. The controller of claim 32, wherein the call data includes a VOIP signaling message.
  • 37. The controller of claim 32, wherein the control criteria includes security measures.
  • 38. The controller of claim 32, wherein the control criteria includes a selection of a telephone number.
  • 39. The controller of claim 32, wherein the control criteria includes a feature selection.
  • 40. The controller of claim 37, wherein the security measures include call logging.
  • 41. The controller of claim 37, wherein the security measures include web based billing.
  • 42. The controller of claim 37, wherein the security measures include a prevention of denial of service attacks.
  • 43. The controller of claim 37, wherein the security measures include authentication of a calling party of the first call.
  • 44. The controller of claim 37, wherein the security measures include no direct access to a gateway.
  • 45. The controller of claim 37, wherein the security measures include conditional call blocking.
  • 46. The controller of claim 32, wherein the enabled communication between the first call and the second call is routed through the controller.
  • 47. The controller of claim 32, wherein the controller is configured to enable the communication between the first call and the second call via an external device.
  • 48. The controller of claim 32, wherein the controller comprises a distributed architecture spanning multiple discrete devices.
  • 49. The controller of claim 32, wherein the controller is located at a border between the first communication network and the second communication network.
  • 50. The controller of claim 32 wherein one of the first and second calls is a voice call.
  • 51. The controller of claim 32 wherein one of the first and second calls is a data call.
  • 52. The controller of claim 32 wherein one of the first and second calls is a fax call.
  • 53. The controller of claim 32 wherein one of the first and second calls is a short text message.
  • 54. The controller of claim 32 wherein one of the first and second calls is a VOIP session.
  • 55. The controller of claim 32 wherein the second call is a call leg.
  • 56. The method of claim 6, wherein the security measures include conditional call blocking.
RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 12/821,119, filed Jun. 22, 2010, which is a continuation of U.S. application Ser. No. 11/948,965, filed Nov. 30, 2007, now U.S. Pat. No. 7,764,777, which is a divisional of U.S. application Ser. No. 10/426,279, filed Apr. 30, 2003, now U.S. Pat. No. 7,324,635, which is a continuation-in-part of U.S. application Ser. No. 09/565,565, filed May 4, 2000, now U.S. Pat. No. 6,574,328. The subject matter in the above-identified co-pending and commonly owned applications is incorporated herein by reference.

US Referenced Citations (357)
Number Name Date Kind
4100377 Flanagan Jul 1978 A
4238851 Takahashi et al. Dec 1980 A
4310726 Asmuth Jan 1982 A
4313035 Jordan et al. Jan 1982 A
4348554 Asmuth Sep 1982 A
4569041 Takeuchi et al. Feb 1986 A
4608685 Jain et al. Aug 1986 A
4611094 Asmuth et al. Sep 1986 A
4611096 Asmuth et al. Sep 1986 A
4630260 Toy et al. Dec 1986 A
4630262 Callens et al. Dec 1986 A
4661947 Lea et al. Apr 1987 A
4674082 Flanagin et al. Jun 1987 A
4679190 Dias et al. Jul 1987 A
4679191 Nelson et al. Jul 1987 A
4707831 Weir et al. Nov 1987 A
4715026 Eberspaecher Dec 1987 A
4723238 Isreal et al. Feb 1988 A
4757497 Beierle et al. Jul 1988 A
4761779 Nara et al. Aug 1988 A
4771425 Baran et al. Sep 1988 A
4815071 Shimizu Mar 1989 A
4819228 Baran et al. Apr 1989 A
4862451 Closs et al. Aug 1989 A
4866704 Bergman Sep 1989 A
4872159 Hemmady et al. Oct 1989 A
4872160 Hemmady et al. Oct 1989 A
4885739 Read et al. Dec 1989 A
4903261 Baran et al. Feb 1990 A
4926416 Weik May 1990 A
4932022 Keeney et al. Jun 1990 A
4933931 Kokubo Jun 1990 A
4953158 Schreur Aug 1990 A
4953198 Daly et al. Aug 1990 A
4958341 Hemmady et al. Sep 1990 A
4962497 Ferenc et al. Oct 1990 A
4969184 Gordon et al. Nov 1990 A
4970721 Aczel et al. Nov 1990 A
4973837 Bradbeer Nov 1990 A
4975695 Almond et al. Dec 1990 A
4996685 Farese et al. Feb 1991 A
4996885 Asbill, III Mar 1991 A
5008929 Olsen et al. Apr 1991 A
5014266 Bales et al. May 1991 A
5018136 Gollub May 1991 A
5020058 Holden et al. May 1991 A
5022071 Mozer et al. Jun 1991 A
5048081 Gavaras et al. Sep 1991 A
5051983 Kammerl Sep 1991 A
5051993 DeLuca et al. Sep 1991 A
5093827 Franklin et al. Mar 1992 A
5115431 Williams et al. May 1992 A
5150357 Hopner et al. Sep 1992 A
5157662 Tadamura et al. Oct 1992 A
5197067 Fujimoto et al. Mar 1993 A
5208806 Hasegawa May 1993 A
5218602 Grant et al. Jun 1993 A
5231633 Hluchyj et al. Jul 1993 A
5241588 Babson, III et al. Aug 1993 A
5247571 Kay et al. Sep 1993 A
5268900 Hluchyj et al. Dec 1993 A
5274635 Rahman et al. Dec 1993 A
5291489 Morgan et al. Mar 1994 A
5297191 Gerszberg Mar 1994 A
5301189 Schmidt et al. Apr 1994 A
5305308 English et al. Apr 1994 A
5311582 Davenport et al. May 1994 A
5327428 Van As et al. Jul 1994 A
5341374 Lewen et al. Aug 1994 A
5351276 Doll, Jr. et al. Sep 1994 A
5351286 Nici Sep 1994 A
5353283 Tsuchiya Oct 1994 A
5359598 Steagall et al. Oct 1994 A
5365521 Ohnishi et al. Nov 1994 A
5379293 Kanno et al. Jan 1995 A
5381405 Daugherty et al. Jan 1995 A
5381466 Shibayama et al. Jan 1995 A
5383183 Yoshida Jan 1995 A
5384840 Blatchford et al. Jan 1995 A
5385521 Weissbuch Jan 1995 A
5390184 Morris Feb 1995 A
5396491 Newman Mar 1995 A
5396542 Alger Mar 1995 A
5420858 Marshall et al. May 1995 A
5422882 Hiller et al. Jun 1995 A
5423003 Berteau Jun 1995 A
5426636 Hiller et al. Jun 1995 A
5428607 Hiller et al. Jun 1995 A
5428616 Field et al. Jun 1995 A
5428663 Grimes et al. Jun 1995 A
5430719 Weisser, Jr. Jul 1995 A
5434913 Tung et al. Jul 1995 A
5436898 Bowen et al. Jul 1995 A
5438614 Rozman et al. Aug 1995 A
5444709 Riddle Aug 1995 A
5448623 Wiedeman et al. Sep 1995 A
5452289 Sharma et al. Sep 1995 A
5453986 Davis et al. Sep 1995 A
5455853 Cebulka et al. Oct 1995 A
5457684 Bharucha et al. Oct 1995 A
5469500 Satter et al. Nov 1995 A
5471470 Sharma et al. Nov 1995 A
5471616 Johnson et al. Nov 1995 A
5479411 Klein Dec 1995 A
5485457 Aramaki Jan 1996 A
5495567 Iizawa et al. Feb 1996 A
5497339 Bernard Mar 1996 A
5521914 Mavraganis et al. May 1996 A
5526353 Henley et al. Jun 1996 A
5537403 Cloonan et al. Jul 1996 A
5541917 Farris Jul 1996 A
5544161 Bigham et al. Aug 1996 A
5544163 Madonna Aug 1996 A
5544164 Baran Aug 1996 A
5544168 Jeffrey et al. Aug 1996 A
5553063 Dickson Sep 1996 A
5557658 Gregorek et al. Sep 1996 A
5563937 Bruno et al. Oct 1996 A
5566236 MeLampy et al. Oct 1996 A
5568475 Doshi et al. Oct 1996 A
5570355 Dail et al. Oct 1996 A
5572583 Wheeler, Jr. et al. Nov 1996 A
5577038 Miyahara Nov 1996 A
5577041 Sharma et al. Nov 1996 A
5579308 Humpleman Nov 1996 A
5590181 Hogan et al. Dec 1996 A
5592477 Farris et al. Jan 1997 A
5592538 Kosowsky et al. Jan 1997 A
5594732 Bell et al. Jan 1997 A
5596579 Yasrebi Jan 1997 A
5600643 Robrock, II Feb 1997 A
5600649 Sharma et al. Feb 1997 A
5602991 Berteau Feb 1997 A
5604737 Iwami et al. Feb 1997 A
5606594 Register et al. Feb 1997 A
5608786 Gordon Mar 1997 A
5613069 Walker Mar 1997 A
H1641 Sharman Apr 1997 H
5621727 Vaudreuil Apr 1997 A
5625677 Feiertag et al. Apr 1997 A
5628004 Gormley et al. May 1997 A
5631897 Pacheco et al. May 1997 A
5640446 Everett et al. Jun 1997 A
5646945 Bergler Jul 1997 A
5650999 Dickson Jul 1997 A
5654957 Koyama Aug 1997 A
5659541 Chan Aug 1997 A
5659542 Bell et al. Aug 1997 A
5673262 Shimizu Sep 1997 A
5680437 Segal Oct 1997 A
5684799 Bigham et al. Nov 1997 A
5689553 Ahuja et al. Nov 1997 A
5689563 Brown et al. Nov 1997 A
5692126 Templeton et al. Nov 1997 A
5701301 Weisser, Jr. Dec 1997 A
5706286 Reiman et al. Jan 1998 A
5710769 Anderson et al. Jan 1998 A
5712903 Bartholomew et al. Jan 1998 A
5712908 Brinkman et al. Jan 1998 A
5724412 Srinivasan Mar 1998 A
5727057 Emery et al. Mar 1998 A
5729544 Lev et al. Mar 1998 A
5732074 Spaur et al. Mar 1998 A
5732078 Arango Mar 1998 A
5732216 Logan et al. Mar 1998 A
5737320 Madonna Apr 1998 A
5737331 Hoppal et al. Apr 1998 A
5737333 Civanlar et al. Apr 1998 A
5737533 De Hond Apr 1998 A
5740164 Liron Apr 1998 A
5740231 Cohn et al. Apr 1998 A
5742596 Baratz et al. Apr 1998 A
5742905 Pepe et al. Apr 1998 A
5751706 Land et al. May 1998 A
5751968 Cohen May 1998 A
5754641 Voit et al. May 1998 A
5764628 Davis et al. Jun 1998 A
5764736 Shachar et al. Jun 1998 A
5764750 Chau et al. Jun 1998 A
5764756 Onweller Jun 1998 A
5777991 Adachi et al. Jul 1998 A
5790538 Sugar Aug 1998 A
5793762 Penners et al. Aug 1998 A
5793771 Darland et al. Aug 1998 A
5799072 Vulcan et al. Aug 1998 A
5799154 Kuriyan Aug 1998 A
5802160 Kugell et al. Sep 1998 A
5805587 Norris et al. Sep 1998 A
5805588 Petersen Sep 1998 A
5806057 Gormley et al. Sep 1998 A
5809022 Byers et al. Sep 1998 A
5809128 McMullin Sep 1998 A
5812534 Davis et al. Sep 1998 A
5815505 Mills Sep 1998 A
5818912 Hammond Oct 1998 A
5825771 Cohen et al. Oct 1998 A
5828666 Focsaneanu et al. Oct 1998 A
5838665 Kahn et al. Nov 1998 A
5848140 Foladare et al. Dec 1998 A
5850433 Rondeau Dec 1998 A
5859972 Subramaniam et al. Jan 1999 A
5867494 Krishnaswamy et al. Feb 1999 A
5867495 Elliott et al. Feb 1999 A
5875405 Honda Feb 1999 A
5878113 Bhusari Mar 1999 A
5878418 Polcyn et al. Mar 1999 A
5881060 Morrow et al. Mar 1999 A
5881131 Farris et al. Mar 1999 A
5889774 Mirashrafi et al. Mar 1999 A
5894473 Dent Apr 1999 A
5894595 Foladare et al. Apr 1999 A
5907811 Foladare May 1999 A
5913029 Shostak Jun 1999 A
5915008 Dulman Jun 1999 A
5918172 Saunders et al. Jun 1999 A
5922047 Newlin et al. Jul 1999 A
5930700 Pepper et al. Jul 1999 A
5933490 White et al. Aug 1999 A
5933778 Buhrmann et al. Aug 1999 A
5938757 Bertsch Aug 1999 A
5946386 Rogers et al. Aug 1999 A
5946684 Lund Aug 1999 A
5953392 Rhie et al. Sep 1999 A
5954799 Goheen et al. Sep 1999 A
5958016 Chang et al. Sep 1999 A
5960340 Fuentes Sep 1999 A
5963551 Minko Oct 1999 A
5970059 Ahopelto et al. Oct 1999 A
5974449 Chang et al. Oct 1999 A
5982866 Kowalski Nov 1999 A
5991291 Asai et al. Nov 1999 A
5991310 Katko Nov 1999 A
5991394 Dezonno et al. Nov 1999 A
5999525 Krishnaswamy et al. Dec 1999 A
6005870 Leung et al. Dec 1999 A
6006272 Aravamudan et al. Dec 1999 A
6009469 Mattaway et al. Dec 1999 A
6012088 Li et al. Jan 2000 A
6014437 Acker et al. Jan 2000 A
6020916 Gerszberg et al. Feb 2000 A
6026083 Albrow et al. Feb 2000 A
6028917 Creamer et al. Feb 2000 A
6031836 Haserodt Feb 2000 A
6031904 An et al. Feb 2000 A
6041325 Shah et al. Mar 2000 A
6044403 Gerszberg et al. Mar 2000 A
6069890 White et al. May 2000 A
6075992 Moon et al. Jun 2000 A
6078581 Shtivelman et al. Jun 2000 A
6084584 Nahi et al. Jul 2000 A
6094478 Shepherd et al. Jul 2000 A
6104800 Benson Aug 2000 A
6118780 Dunn et al. Sep 2000 A
6134235 Goldman et al. Oct 2000 A
6141341 Jones et al. Oct 2000 A
6161128 Smyk Dec 2000 A
6161134 Wang et al. Dec 2000 A
6163598 Moore Dec 2000 A
6167040 Haeggstrom Dec 2000 A
6175860 Gaucher Jan 2001 B1
6185285 Relyea et al. Feb 2001 B1
6188688 Buskirk, Jr. Feb 2001 B1
6212261 Meubus et al. Apr 2001 B1
6216158 Luo et al. Apr 2001 B1
6240097 Wesloek et al. May 2001 B1
6243373 Turock Jun 2001 B1
6259692 Shtivelman et al. Jul 2001 B1
6262978 Bruno et al. Jul 2001 B1
6266539 Pardo Jul 2001 B1
6278707 MacMillan et al. Aug 2001 B1
6301609 Aravamudan et al. Oct 2001 B1
6308201 Pivowar et al. Oct 2001 B1
6324183 Miller et al. Nov 2001 B1
6327258 Deschaine et al. Dec 2001 B1
6334126 Nagatomo et al. Dec 2001 B1
6337858 Petty et al. Jan 2002 B1
6339594 Civanlar et al. Jan 2002 B1
6359892 Szlam Mar 2002 B1
6381323 Schwab et al. Apr 2002 B1
6385308 Cohen et al. May 2002 B1
6404764 Jones et al. Jun 2002 B1
6411615 DeGolia et al. Jun 2002 B1
6411965 Klug Jun 2002 B2
6414962 Hall et al. Jul 2002 B1
6418198 Brablec et al. Jul 2002 B2
6421235 Ditzik Jul 2002 B2
6438124 Wilkes Aug 2002 B1
6445694 Swartz Sep 2002 B1
6445697 Fenton Sep 2002 B1
6446127 Schuster et al. Sep 2002 B1
6448978 Salvador et al. Sep 2002 B1
6456594 Kaplan et al. Sep 2002 B1
6456601 Kozdon et al. Sep 2002 B1
6459780 Wurster et al. Oct 2002 B1
6477565 Daswani et al. Nov 2002 B1
6477576 Angwin et al. Nov 2002 B2
6483902 Stewart et al. Nov 2002 B1
6493338 Preston et al. Dec 2002 B1
6496477 Perkins et al. Dec 2002 B1
6498797 Anerousis Dec 2002 B1
6526462 Elabd Feb 2003 B1
6539359 Ladd et al. Mar 2003 B1
6577622 Schuster et al. Jun 2003 B1
6577718 Kalmanek Jun 2003 B1
6584490 Schuster et al. Jun 2003 B1
6614781 Elliott et al. Sep 2003 B1
6643282 Christie Nov 2003 B1
6650901 Schuster et al. Nov 2003 B1
6681252 Schuster et al. Jan 2004 B1
6697461 Middleswarth et al. Feb 2004 B1
6731630 Schuster et al. May 2004 B1
6741586 Schuster et al. May 2004 B1
6744759 Sidhu Jun 2004 B1
6775264 Kurganov Aug 2004 B1
6775284 Calvignac Aug 2004 B1
6785229 McNiff et al. Aug 2004 B1
6785266 Swartz Aug 2004 B2
6788775 Simpson Sep 2004 B1
6795429 Schuster et al. Sep 2004 B1
6804224 Schuster et al. Oct 2004 B1
6807257 Kurganov Oct 2004 B1
6816582 Levine Nov 2004 B2
6822957 Schuster et al. Nov 2004 B1
6853714 Liljestrand et al. Feb 2005 B2
6856616 Shuster et al. Feb 2005 B1
6857021 Sidhu et al. Feb 2005 B1
6857072 Shuster et al. Feb 2005 B1
6870830 Shuster et al. Mar 2005 B1
6914897 Shuster et al. Jul 2005 B1
6937699 Shuster et al. Aug 2005 B1
6937713 Kung Aug 2005 B1
6956941 Duncan et al. Oct 2005 B1
7069291 Graves et al. Jun 2006 B2
7123708 Gavillet Oct 2006 B1
7184527 Lin Feb 2007 B1
7233658 Koser Jun 2007 B2
7242759 Sanchez et al. Jul 2007 B1
7272115 Maher et al. Sep 2007 B2
7436851 Chambers et al. Oct 2008 B1
7733821 Kolor et al. Jun 2010 B2
20010022784 Menon et al. Sep 2001 A1
20010030950 Chen et al. Oct 2001 A1
20030026403 Clapper Feb 2003 A1
20030040325 Clark Feb 2003 A1
20030095650 Mize May 2003 A1
20030133553 Khakoo et al. Jul 2003 A1
20030156693 Goldman Aug 2003 A1
20030194078 Wood et al. Oct 2003 A1
20040029568 DeLuca et al. Feb 2004 A1
20040151294 Baniak et al. Aug 2004 A1
20040240657 Camarillo Dec 2004 A1
20040264673 Novack Dec 2004 A1
20050041526 Esmersoy et al. Feb 2005 A1
20050141500 Bhandari et al. Jun 2005 A1
20050169445 Harris Aug 2005 A1
20050207557 Dolan et al. Sep 2005 A1
20070041526 Hill et al. Feb 2007 A1
Foreign Referenced Citations (147)
Number Date Country
19813179 Sep 1999 DE
0 578 374 Jan 1994 EP
0578374 Jan 1994 EP
0 704 788 Apr 1996 EP
0704788 Apr 1996 EP
0 738 093 Oct 1996 EP
0738093 Oct 1996 EP
0 789 470 Aug 1997 EP
0 794 650 Sep 1997 EP
0 794 850 Sep 1997 EP
0 797 373 Sep 1997 EP
0 824 298 Feb 1998 EP
0 829 995 Mar 1998 EP
0 841 831 May 1998 EP
0 847 176 Jun 1998 EP
0 851 653 Jul 1998 EP
0 851 883 Jul 1998 EP
0 853 411 Jul 1998 EP
0 853 411 Jul 1998 EP
0 858 202 Aug 1998 EP
0858202 Aug 1998 EP
0 866 596 Sep 1998 EP
0 886 598 Sep 1998 EP
0 869 688 Oct 1998 EP
0 872 998 Oct 1998 EP
0 918 423 Oct 1998 EP
0869688 Oct 1998 EP
0918423 Oct 1998 EP
0 881 848 Dec 1998 EP
0881848 Dec 1998 EP
0 898 431 Feb 1999 EP
0898431 Feb 1999 EP
2 315 190 Jan 1998 GB
2 315 190 Jan 1998 GB
10-023067 Jan 1998 JP
10-23067 Jan 1998 JP
10-51453 Feb 1998 JP
10-051453 Feb 1998 JP
10-164135 Jun 1998 JP
10-164257 Jun 1998 JP
WO 9714234 Jan 1991 WO
WO 9714238 Jan 1997 WO
WO9405111 Mar 1994 WO
WO 9405111 Mar 1994 WO
WO 9534985 Dec 1995 WO
WO9534985 Dec 1995 WO
WO 9608935 Mar 1996 WO
WO 9615598 May 1996 WO
WO 9828885 Jul 1996 WO
WO 9714234 Apr 1997 WO
WO 9714238 Apr 1997 WO
WO 9716007 May 1997 WO
WO 9722216 Jun 1997 WO
WO 9723078 Jun 1997 WO
WO 9727692 Jul 1997 WO
WO 9727892 Jul 1997 WO
WO 9728628 Aug 1997 WO
WO 9728828 Aug 1997 WO
WO 9729581 Aug 1997 WO
WO 9731492 Aug 1997 WO
WO9731492 Aug 1997 WO
WO 9733412 Sep 1997 WO
WO 9733421 Sep 1997 WO
WO9733421 Sep 1997 WO
WO 9738511 Oct 1997 WO
WO 9738511 Oct 1997 WO
WO 9738551 Oct 1997 WO
WO 9739560 Oct 1997 WO
WO 9744943 Nov 1997 WO
WO9744943 Nov 1997 WO
WO 9745073 Dec 1997 WO
WO 9746073 Dec 1997 WO
WO 9747118 Dec 1997 WO
WO 9750217 Dec 1997 WO
WO 9750271 Dec 1997 WO
WO 9750277 Dec 1997 WO
WO 9750277 Dec 1997 WO
WO9800988 Jan 1998 WO
WO 9800988 Jan 1998 WO
WO9804065 Jan 1998 WO
WO 9804065 Jan 1998 WO
WO 9804989 Feb 1998 WO
WO 9508935 Mar 1998 WO
WO 9810538 Mar 1998 WO
WO9810838 Mar 1998 WO
WO 9811704 Mar 1998 WO
WO 9812850 Mar 1998 WO
WO 9812860 Mar 1998 WO
WO 9813974 Apr 1998 WO
WO 9816051 Apr 1998 WO
WO9816051 Apr 1998 WO
WO 9818238 Apr 1998 WO
WO 9818289 Apr 1998 WO
WO 9815598 May 1998 WO
WO 9819425 May 1998 WO
WO 9819445 May 1998 WO
WO 9820701 May 1998 WO
WO9821911 May 1998 WO
WO 9821911 May 1998 WO
WO 9823067 May 1998 WO
WO 9823080 May 1998 WO
WO 9826543 Jun 1998 WO
WO 9828885 Jul 1998 WO
WO 9830007 Jul 1998 WO
WO 9830008 Jul 1998 WO
WO9830008 Jul 1998 WO
WO 9636543 Aug 1998 WO
WO 9834391 Aug 1998 WO
WO 9834399 Aug 1998 WO
WO 9836543 Aug 1998 WO
WO9837665 Aug 1998 WO
WO 9837665 Aug 1998 WO
WO 9837688 Aug 1998 WO
WO 9837688 Aug 1998 WO
WO 9839897 Sep 1998 WO
WO 9842104 Sep 1998 WO
WO 9842107 Sep 1998 WO
WO 9842146 Sep 1998 WO
WO 9847256 Oct 1998 WO
WO 9847256 Oct 1998 WO
WO 9851063 Nov 1998 WO
WO9912365 Mar 1999 WO
WO 9912365 Mar 1999 WO
WO 9919988 Apr 1999 WO
WO9919988 Apr 1999 WO
WO 9920059 Apr 1999 WO
WO9920059 Apr 1999 WO
WO9935802 Jul 1999 WO
WO 9935802 Jul 1999 WO
WO 9945687 Sep 1999 WO
WO9945687 Sep 1999 WO
WO 0105078 Jan 2001 WO
WO0105078 Jan 2001 WO
WO 0124496 Apr 2001 WO
WO0124496 Apr 2001 WO
WO0124498 Apr 2001 WO
WO 0124498 Apr 2001 WO
WO0124500 Apr 2001 WO
WO 0124500 Apr 2001 WO
WO0124501 Apr 2001 WO
WO 0124501 Apr 2001 WO
WO 0124502 Apr 2001 WO
WO0124502 Apr 2001 WO
WO 0124503 Apr 2001 WO
WO0124503 Apr 2001 WO
WO 0184859 Nov 2001 WO
WO0184859 Nov 2001 WO
Non-Patent Literature Citations (25)
Entry
RFC 3298 Service in the PSTN, Aug. 2002.
Implementing Automatic Location Update for Follow-Me database using VoIP and Bluetooth Technologies, IEEE Transaction on computers, vol. 51, No. 10, Oct. 2002.
New services demand integration, Electronic Engineering Times, Aug. 28, 2000, Iss. 1128; p. 110.
Natural Microsystems, M2 Presswire. Coventry: Aug, 18, 2000.
This pipe dream will come true: Voice Over Internet Protocol (VoIP) technology will make the phone Box something that really talks, Businessline, Chennai: Apr. 17, 2002.
Using Optimization to Achieve Efficient Quality of Service in Voice over IP Networks, IEEE 2003.
Broadsoft literature Broadworks overview, Copyright date 2002.
BroadSoft introduces industry's first complete service delivery and creation product suite for enhanced telephony services Broadworks, ATM Newsletter: Boston: Mar. 2000, vol. 9, Iss. 3, p. 13.
BroadSoft unveils advanced architecture for the rapid and cost effective delivery of enhanced communications services, Website, Aug. 25, 1999, Press releases, 3 pages.
ADC Telecommunications; SS7 New Net SS7 Tutorial; Copyright 1999.
Mary Carmichael, “Calls That Follow you Anywhere” Newsweek, Apr. 28, 2003, p. 43.
U.S. Appl. No. 09/406,322, Schuster et al., filed Sep. 27, 1999.
U.S. Appl. No. 09/515,798, Schuster et al., filed Feb. 29, 2000.
RFC 3296 Service in the FSTN, Aug. 2002.
Natural Microsystems, M2 Presswire. Coventry: Aug. 18, 2000.
This pipe-dream will come true: Voice Over Internet Protocol (VoIP) technology will make the phone Box something that really talks, Businessline; Chennai: Apr. 17, 2002.
Using Optimization to Achieve Efficient Quality of Service in Voice over IP Nerworks, IEEE 2003.
BroadSoft unveils advanced architecture for the rapid and obst effective delivery of enhanced communications services, Website, Aug. 25, 1999. Press releases, 3 pages.
Dowden, Douglas C., et al., “The Future of Network-Provided Communications Services,” Bell Labs Technical Journal, Jul.-Sep. 2000, pp. 3-10.
Foerd C.F., “Teaming Switches and Computers for Customer Applications.” AT&T Technology, 1991; 6, 4; Research Library, pp. 32-38.
Foster, Robin Harris, “Computer-Telephone Integration Goes Global,” AT&T Technology, Autumn 1995; 10, 3; Research Library , pp. 18-22.
Kozik, Jack, et al., “On Opening PSTN to Enhanced Voice/Data Services—The PINT Protocol Solution,” Bell Labs Technical Journal, Jul.-Sep. 2000, pp. 153-165.
Lui, Anthony Y., et al., “The Enhanced Service Manager: A Service Management System for Next-Generation Networks,” Bell Labs Technical Journal, Jul.-Sep. 2000, pp. 130-144.
Reisfield, E.S., “Customers Take Control of the AT&T Network,” AT&T Technology, 1991; 6,1; Research Library, pp. 44-48.
Sijben, Paul G., et al, “Bridging the Gap to IP Telephony,” Bell Labs Technical Journal, Oct.-Dec. 1998; pp. 192-207.
Related Publications (1)
Number Date Country
20130322431 A1 Dec 2013 US
Divisions (1)
Number Date Country
Parent 10426279 Apr 2003 US
Child 11948965 US
Continuations (2)
Number Date Country
Parent 12821119 Jun 2010 US
Child 13905036 US
Parent 11948965 Nov 2007 US
Child 12821119 US
Continuation in Parts (1)
Number Date Country
Parent 09565565 May 2000 US
Child 10426279 US