Source: http://www.google.com/patents/US6907031?dq=6175559
Timestamp: 2014-12-22 15:49:06
Document Index: 105307786

Matched Legal Cases: ['arty 12', 'arty 12', 'arty 12', 'arty 12', 'arty 18', 'arty 18', 'arty 16', 'arty 12', 'arty 14', 'arty 14', 'arty 16', 'arty 18', 'arty 16', 'arty 16', 'arty 18', 'arty 18', 'arty 12', 'arty 12', 'arty 12', 'arty 12', 'arty 16', 'arty 16', 'arty 16']

Patent US6907031 - Customer premises equipment call re-routing technique - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA call from a calling party (12) is routed to at least one called party (14, 16, and 18) in accordance with the network preference of the calling party while taking into account the network capability of the called party. The calling party initiates an attempt to the called party over a preferred network...http://www.google.com/patents/US6907031?utm_source=gb-gplus-sharePatent US6907031 - Customer premises equipment call re-routing techniqueAdvanced Patent SearchPublication numberUS6907031 B1Publication typeGrantApplication numberUS 09/793,641Publication dateJun 14, 2005Filing dateFeb 26, 2001Priority dateFeb 26, 2001Fee statusPaidPublication number09793641, 793641, US 6907031 B1, US 6907031B1, US-B1-6907031, US6907031 B1, US6907031B1InventorsJames Ehlinger, Paul J. Fellingham, Christopher P GilboyOriginal AssigneeAt&T Corp.Export CitationBiBTeX, EndNote, RefManPatent Citations (13), Referenced by (24), Classifications (16), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetCustomer premises equipment call re-routing techniqueUS 6907031 B1Abstract A call from a calling party (12) is routed to at least one called party (14, 16, and 18) in accordance with the network preference of the calling party while taking into account the network capability of the called party. The calling party initiates an attempt to the called party over a preferred network (32) by first querying a database (40) containing records, each indicating the network capability of a corresponding called party. If the called party has the capability of receiving a call on the preferred network, the call is routed over that network. Otherwise, the call is routed over an alternate network (30) on which the called party has the capability of receiving a call.
1. A method for routing a call from a calling a party to a called party in accordance with a network preference of the calling party while accounting for a network capability of the called party, comprising the steps of:
receiving in a first network preferred by the calling party a call attempt to reach the called party; querying a database, containing records of called parties, each specifying a network capability of corresponding called party, to ascertain whether said called party has the capability of receiving the call through the preferred network, and if so; routing the call over the preferred network, otherwise; ascertaining whether a gateway exists between the preferred network and an alternate network over which the called party has the capability of receiving the call, and if so, routing the call through the gateway, otherwise; sending a redirect message to the calling party to redirect the call entirely over the alternate network; wherein the call is routed entirely over the alternate network if no response is received from the database within a prescribed interval. 2. The method according to claim 1 wherein the database is queried by receiving a telephone number associated with said called party.
3. The method according to claim 2 wherein said database is updated by a provider of telecommunications service.
4. The method according to claim 2 wherein said database is updated by the called party.
5. The method according to claim 2 wherein said database is updated by the called party CPE device.
6. The method according to claim 1 wherein the querying step includes the step of ascertaining whether the called party has the capability of receiving calls through both the preferred and alternate networks, and if so, then routing the call over the network having the least cost.
7. The method according to claim 1 wherein said preferred network is determined by using least cost routing criteria of the preferred and alternate networks.
8. A method for routing a call from a calling party to a called party over an IP network preferred by the calling party while accounting for a network capability of the called party, comprising the steps of:
receiving in the IP network a call attempt to reach the called party; querying through the IP network a database, containing records of called parties, each specifying a network capability of corresponding called party, to ascertain whether said called party has the capability of receiving the call through the IP network, and if so: routing the call over the IP network, otherwise; ascertaining whether a gateway exists between the IP network and an alternate network over which the called party has the capability of receiving the call, and if so, routing the call through the gateway, otherwise; sending a redirect message to the calling party to redirect the call entirely over the alternate network; wherein the call is routed entirely over the PSTN if no response is received from the database within a prescribed interval. 9. The method according to claim 8 wherein the database is queried by receiving a telephone number associated with said called party.
10. The method according to claim 8 wherein said database is updated by a provider of telecommunications service.
11. The method according to claim 8 wherein said database is updated by the called party.
12. The method according to claim 8 wherein said database is updated by the called party CPE device.
13. The method according to claim 8 wherein the querying step includes the step of ascertaining whether the called party has the capability of receiving calls through both the IP network and the PSTN, and if so, then routing the call over the network having the least cost.
14. The method according to claim 8 wherein said preferred network is determined by using least cost routing criteria of the preferred and alternate networks.
15. A method for routing a call from a calling party to a called party in accordance with a least cost network preference of the calling party while accounting for a network capability of the called party, comprising the steps of:
receiving from the calling party in an originating network a call attempt to reach the called party; querying a database, containing records of called parties, each record specifying a network capability of a corresponding called party, including cost information for routing a call on each network on which the called party can receive a call, to ascertain whether said called party has the capability of receiving the call through two or more networks, and if so; routing the call over at least a portion of the network having a least cost, otherwise; routing the call over at least a portion of an alternate network on which the called party can receive the call; wherein the call is routed entirely over the alternate network if no response is received from the database within a prescribed interval. 16. The method according to claim 15 wherein the call to the called party is routed over the originating network to the least cost network when a gateway exists between the originating and least cost networks.
17. The method according to claim 15 wherein the call is routed entirely over the least cost network when no gateway exists between the originating and least cost networks.
18. The method according to claim 15 wherein the database is queried by receiving a telephone number associated with said called party.
19. The method according to claim 18 wherein said database is updated by a provider of telecommunications service.
20. The method according to claim 18 wherein said database is updated by the called party.
21. The method according to claim 18 wherein said database is updated by the called party CPE device.
22. The method according to claim 15 wherein the step of routing the call over at least a portion of an alternate network on which the called party can receive the call further comprises:
ascertaining whether a gateway exists between the originating network and the alternate network, and if so, routing the call through the gateway, otherwise; sending a redirect message to the calling party to redirect the call entirely over the alternate network.
TECHNICAL FIELD This invention relates to a technique for determining how to best route a call to a subscriber.
BACKGROUND ART Many providers of traditional circuit-switched telephony service, such as AT&T, now offer at least some subscribers the capability to complete voice calls over the Internet. Indeed, the total number of minutes of Voice Over Internet Prtocol (VOIP) calls continues to grow each year because subscribers find such calls more economical by virtue of the fact that such calls often cost less than traditional circuit-switched calls. Unfortunately, the present lack of compatible common gateways has limited deployment of VOIP service. In addition, VOIP telephony does not yet enjoy the reliability of conventional circuit-switched telephony.
In an effort to address the issue of the reliability, U.S. Pat. No. 6,064,727 issued May 16, 2000, to AT&T, the present assignee, proposes a technique for offering a telephone subscriber uninterrupted service by routing a call over an alternate communications channel (e.g., a PSTN link) if call routing cannot occur over a primary communications channel, for example a cable television link. The technique for maintaining uninterrupted telecommunications service disclosed in the '727 patent concerns the availability of the primary communications channel, as well as the characteristics of the call. However, the '727 patent does not address the communications capability of the called party, and in particular, whether the called party has the ability to receive calls over a particular network.
Thus, there is a need for a technique that affords improved reliability while addressing the communications capability of the called party.
BRIEF SUMMARY OF THE INVENTION Briefly, in accordance with a preferred embodiment, the present invention provides a technique for routing a call over at least one of a plurality of diverse networks from a calling party to a called party in accordance with the network preference of the calling party while accounting for the network capability of the called party. In response to a call attempt launched by the calling party over a preferred network, a query is made to a database to ascertain the network capability of the called party. Within the database are records, each indicating the network capability of a corresponding called party, that is the ability of each called party to receive calls over one or more diverse networks. In response to the query, the database returns the network capability of the called party. A determination is then made whether a call can be routed over the preferred network in accordance with the network capability of the called party. If the called party has the capability to receive the call over the preferred network, the call is routed over that network. Otherwise, the call is routed over another network on which the called party has the capability of receiving a call. For example, the calling party may prefer to route calls over an IP network. If the called party has the capability of receiving a call over the IP network, then the call is routed to the called party over that network. If the called party lacks such a capability, then the call is routed over another network, such as the PSTN network, assuming that the called party has the capability of receiving calls over that network.
The network capability of the called party stored in the database is updated on a regular basis to reflect changes in the connectivity of the called party. Further, the network capability information also includes information regarding the cost associated with such calls. Thus, the determination of whether to route calls over the preferred network takes into account not only the called party's physical capability to receive a call on a network, but the relative economic cost of doing so relative to other networks.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 illustrates a block schematic diagram of a communications network for practicing call routing technique of the invention; and
FIG. 2 illustrates in flow chart form the steps by which a call is routed through the network of FIG. 1.
DETAILED DESCRIPTION FIG. 1 illustrates a block schematic diagram of a composite network 10 for routing a call from a calling party 12 to one of a plurality of called parties 14, 16, and 18, respectively, in accordance with a network preference of the calling party while accounting for the network capability of the called party in accordance with the invention. In the embodiment of FIG. 1, the calling party 12 possesses one or more communications devices at its premises, illustratively represented by voice station set 20 and a personal computer 22, both linked to a first Customer Premises Equipment (CPE) device 24 typically taking the form of a Broadband Telephony Interface (BTI) or Multimedia Terminal Adapter (MTA) as are known in the art.
The CPE device 24 functions to interface both the telephone set 20 and the personal computer 22 to both a Local Exchange Carrier (LEC) baseband access network 26 and to a local access data network 28. In practice, the local access data network 28 may take the form of a Hybrid Fiber Coax network, a Digital Subscriber Line (DSL) network, a fixed wireless network, or an Internet Service Provider network. By linking both the telephone set 20 and the computer 22 to the LEC access network 26, the CPE device 24 enables the calling party 12 to launch a conventional or Plain Old Telephone Service (POTS) call through the LEC baseband network to a Public Switched Telephone Network (PSTN) 30, such as the PSTN maintained by AT&T. Upon receipt of a POTS call from the LEC baseband network 26, the PSTN 30 routes the call to one or more of the called parties, such as called parties 14 and 16 who each enjoy a link to the PSTN via the same or separate LEC networks (not shown) that each provide the called parties with POTS service.
The CPE device 24 serves to convert a voice call originated on either the telephone set 20 or the computer 22 into VOIP calls for transmission through the local data network 28 into an IP network 32. Conversely, the CPE device 24 will convert a VOIP call received from IP network 32 through the local access data network 28 into a voice call for receipt on either the telephone set 20 or computer 22. The IP Network 32 carries a VOIP call originated by the calling party 12 to an IP-enabled called party, such as called party 18 that also enjoys a link to the IP network 32 through a local access data network (not shown) similar to the data network 28. In the illustrated embodiment, the called party 18 has a communications device 32, typically a telephone set (or a personal computer, not shown), coupled to the IP network 32 through a second CPE device 34 having the same capabilities as the CPE device 24 for converting a voice call to a VOIP call and vice versa.
An IP call gateway 36 links the IP network 32 to the PSTN 30 to permit a call originating in one network to pass into the other and vice versa. To this end, the gateway 36 converts a POTS call from the PSTN 30 into a VOIP call for receipt in the IP network 32, and likewise converts a VOIP call from the IP network into a POTS call for receipt in the PSTN network. In this way, the called party 16, which enjoys a link through the PSTN 30 to the gateway 36, can receive a POTS call that originated as a VOIP call launched from the one of the parties 12 and 18.
In accordance with the invention, a call from a calling party (i.e., calling party 12) is routed to one or more called parties (e.g., called parties 14, 16, and 18) in accordance with a network preference of the calling party, while taking into account the network capability of the called party. To accomplish such routing, the network 10 includes a database 40 that contains a record for each called party indexed by the called party's telephone number (or numbers). Each record specifies the network capability of the associated called party, i.e., the ability of that party to receive calls over a particular network. Thus, upon receipt of the called party's number, the database 40 will return that called party's network capability. For example, the record for the called party 14 specifies that this party only has the capability to receive POTS calls via the PSTN 30 and thus, upon receiving the telephone number of the called party 14, the database will return such information. By contrast, the record in the database 40 for the called party 16 specifies this party has the ability to receive POTS directly from the PSTN and also has the ability to receive calls via the gateway 36. The database record for the called party 18 specifies that this party is IP-enabled, and can receive IP calls directly from the IP network 32 and also can receive calls via the gateway 36, as well as the ability to receive calls that are redirected back to CPE 24 for completion via LEC baseband access network 26 and PSTN 30.
If desired, the network capability information in each record for a given called party may include cost information for the routing of a call on each network on which the called party can receive a call. For example, the called party 16 can receive calls both through the PSTN 30 and through gateway 36 from the IP network. Associated with routing a call over each network is a transport cost. In determining the network capability of a called party having access through two or more networks, the CPE device 24 receiving the response from the database 40 to the original query may compare the prices and choose to route the call on over the least cost network. For example, since the called party 16 may receive a call over both the PSTN 30 and over the IP network 32 via the gateway 32, the CPE device 24 could choose to route a call to that called party over the lower cost route.
Updates to the records in the database 40 occur in response to changes in the network capability of the called parties. For example, once the called party 18 becomes available to receive VOIP calls, that status information passes to the database 40 for updating of the record associated with the called party 18. Thus, the called party may effectuate an update of the database 40. Similarly, changes in network capability and other factors such as network cost for each called party also pass to the database 40 for updating of the corresponding called party records. Thus, the provider of network service may also update the database.
FIG. 2 depicts the steps executed by the network 10 to route a call originated by the calling party 12 to one of the called parties 14, 16, and 18 in accordance with the network preference of the calling party while taking into account the capability of the called party. The process commences at the entry step (step 100), whereupon the network 10 then waits for the calling party 12 to go off hook (step 120). Once the calling party 12 goes off hook the CPE 24 initially tries to set-up a call to the called party over a network preferred by the calling party, say the IP network 32 (step 130).
As discussed previously, not every called party has the capability to receive a VOIP call launched on the IP network 32. Therefore, following step 130, the CPE device 24 of FIG. 1 launches a query to the database 40 to get the status of the call destination (step 140). In other words, the CPE device 24 of FIG. 1 queries the database 40 to access the record of the called party in accordance with that party's telephone number to ascertain the status (network capability) of the called party. Having accessed the called party's record, a check is made whether the called party is IP-enabled, (i.e., whether the called party is a destination reachable through the IP network 32 of FIG. 1) (step 150). If the called party is indeed IP-enabled, and thus reachable through the IP network 32 of FIG. 1, the call will complete over the IP network (step 160), provided no other rationale, such as cost, exists for not completing the call. Thereafter, the CPE device exits the process (step 170).
If the called party is not a destination on the IP network 32, then a determination is made during step 180 whether the called party is reachable through the gateway 36. For example, when the calling party 12 seeks to reach the called party 16, the database query made during step 140 will reveal that the called party 16 is not a destination on the IP network 32, but is nonetheless reachable through the gateway 36. Following step 180, for a called party (e.g., called party 16) reachable through the gateway 36, the CPE device 24 of FIG. 1 effects routing of the call through the gateway (step 190) and thereafter, CPE device 24 exits the process.
If the called party is not a destination on the IP network 32, and is not reachable through the gateway 36 of FIG. 1, then the IP network 32 of FIG. 1 sends a redirect request back to the CPE device 24 of FIG. 1 during step 210 of FIG. 2. whereupon the CPE device 24 redirects the call into an alternate (second) network, such as the PSTN network 30 (step 220). The CPE device 24 will also re-direct the call to the second (alternate) network following step 230 during which a check is made whether any response has been received from the IP network 32 upon querying the database 40 of FIG. 1 during step 140 of FIG. 2. Following redirection of the call to the second network, the CPE device 24 exits the process (step 24).
The foregoing describes a technique for routing a call to a called party in accordance with a network preference of the calling party while taking into account the network capability of the called party.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5999525 *Nov 18, 1996Dec 7, 1999Mci Communications CorporationMethod for video telephony over a hybrid networkUS6064653 *Jan 7, 1997May 16, 2000Bell Atlantic Network Services, Inc.Internetwork gateway to gateway alternative communicationUS6064727Oct 6, 1998May 16, 2000At&T CorpMethod and apparatus for maintaining uninterrupted telecommunications serviceUS6185204 *Dec 10, 1999Feb 6, 2001Bell Atlantic Network Services, Inc.Internet phone to PSTN cellular/PCS systemUS6253249 *Aug 31, 1998Jun 26, 2001Nortel Networks LimitedMethod and devices for bridging data and telephone networksUS6282192 *May 9, 2000Aug 28, 2001Cisco Technology, Inc.PSTN fallback using dial on demand routing schemeUS6304565 *May 20, 1998Oct 16, 2001At&T Corp.Method of completing long distance pots calls with IP telephony endpointsUS6330316 *Mar 12, 1999Dec 11, 2001Nortel Networks LimitedAlternate routing schemes using quality of service information for calls involving unreliable networksUS6337858 *Oct 10, 1997Jan 8, 2002Nortel Networks LimitedMethod and apparatus for originating voice calls from a data networkUS6363065 *Nov 10, 1999Mar 26, 2002Quintum Technologies, Inc.okApparatus for a voice over IP (voIP) telephony gateway and methods for use thereinUS6389005 *Dec 1, 1997May 14, 2002Nortel Networks LimitedAutomatic backup trunking for voice over the internetUS6510219 *Sep 30, 1999Jan 21, 2003Nortel Networks LimitedAlternate network fallback for IP telephonyWO1999005590A2 *Jul 22, 1998Feb 4, 1999Starvox IncApparatus and method for integrated voice gateway* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7437162 *Feb 10, 2003Oct 14, 2008Sprint Spectrum L.P.Method and system for dynamically delivering a voice call as voice or data depending on data-mode of destination terminalUS7460480Mar 11, 2005Dec 2, 2008I2Telecom International, Inc.Dynamically adapting the transmission rate of packets in real-time VoIP communications to the available bandwidthUS7492879Dec 28, 2005Feb 17, 2009United Services Automobile Association (Usaa)System and method for reducing toll charges to a customer service center using VoIPUS7555113 *Oct 31, 2005Jun 30, 2009At&T Corp.Method and apparatus for providing customer premise equipment based routingUS7606217 *Jul 22, 2003Oct 20, 2009I2 Telecom International, Inc.System and method for routing telephone calls over a voice and data networkUS7668302 *Dec 28, 2005Feb 23, 2010United Services Automobile Association (Usaa)System and method for reducing toll charges to a customer service center using VoIPUS7676599Jan 26, 2005Mar 9, 2010I2 Telecom Ip Holdings, Inc.System and method of binding a client to a serverUS7724727 *Jan 30, 2002May 25, 2010Cisco Technology, Inc.Communicating calls from analog devices using voice over packet technologyUS7782878Aug 11, 2005Aug 24, 2010I2Telecom Ip Holdings, Inc.System and method for sharing an IP addressUS7957401Jul 3, 2003Jun 7, 2011Geos Communications, Inc.System and method for using multiple communication protocols in memory limited processorsUS8005068 *Oct 2, 2001Aug 23, 2011Sonera OyjMethod of setting up a connection for callsUS8085912Dec 28, 2005Dec 27, 2011United Services Automobile AssociationSystem and method for reducing toll charges to a customer service center using VolPUS8126131 *Jun 15, 2005Feb 28, 2012Alcatel LucentCall blocking based on the network access type for the called partyUS8335232Oct 31, 2008Dec 18, 2012Geos Communications IP Holdings, Inc., a wholly owned subsidiary of Augme Technologies, Inc.Method and system of renegotiating end-to-end voice over internet protocol CODECsUS8504048Apr 7, 2008Aug 6, 2013Geos Communications IP Holdings, Inc., a wholly owned subsidiary of Augme Technologies, Inc.Systems and methods of making a callUS8538004 *Jan 8, 2009Sep 17, 2013Sony Corporation Sony Mobile Communications ABMethod and apparatus for relaying callsUS8606874Aug 31, 2009Dec 10, 2013Hipcricket, Inc.System and method of binding a client to a serverUS8630400 *Aug 6, 2009Jan 14, 2014Nec CorporationTelephone relay system, telephone relay apparatus, recording medium and data processing methodUS8718604 *Nov 21, 2012May 6, 2014Kseek Co., Ltd.Method and apparatus for providing alternative telephony service, and method of computing inverse call charge using the sameUS8804758Feb 6, 2013Aug 12, 2014Hipcricket, Inc.System and method of media over an internet protocol communicationUS8842568Nov 26, 2012Sep 23, 2014Hipcricket, Inc.Method and system of renegotiating end-to-end voice over internet protocol CODECsUS20090097476 *Jun 1, 2007Apr 16, 2009Motorola, Inc.Method and apparatus for supporting voice communicationsUS20100040223 *Aug 6, 2009Feb 18, 2010Shinya AraoTelephone relay system, telephone relay apparatus, recording medium and data processing methodUS20100166170 *Jan 8, 2009Jul 1, 2010Sony Ericsson Mobile Communications AbMethod and Apparatus for Relaying Calls* Cited by examinerClassifications U.S. Classification370/352, 370/401, 370/254International ClassificationH04L12/56, H04L12/66, H04Q3/66Cooperative ClassificationH04Q2213/13034, H04Q2213/13389, H04Q2213/13196, H04Q3/66, H04Q2213/13282, H04L45/22, H04Q2213/13145, H04Q2213/13141European ClassificationH04L45/22, H04Q3/66Legal EventsDateCodeEventDescriptionOct 4, 2012FPAYFee paymentYear of fee payment: 8Sep 18, 2008FPAYFee paymentYear of fee payment: 4Feb 26, 2001ASAssignmentOwner name: AT&T CORP., NEW YORKFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EHLINGER, JAMES;FELLINGHAM, PAUL J;GILBOY, CHRISTOPHER P;REEL/FRAME:011606/0014Effective date: 20010223Owner name: AT&T CORP. 32 AVENUE OF THE AMERICASNEW YORK, NEWFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EHLINGER, JAMES /AR;REEL/FRAME:011606/0014RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google