WO2006095256A2 - System and method for routing voip ( voice over internet protocol) calls - Google Patents
System and method for routing voip ( voice over internet protocol) calls Download PDFInfo
- Publication number
- WO2006095256A2 WO2006095256A2 PCT/IB2006/000528 IB2006000528W WO2006095256A2 WO 2006095256 A2 WO2006095256 A2 WO 2006095256A2 IB 2006000528 W IB2006000528 W IB 2006000528W WO 2006095256 A2 WO2006095256 A2 WO 2006095256A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- local
- routes
- endpoint
- routing
- route
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 22
- 238000012544 monitoring process Methods 0.000 claims abstract description 15
- 238000005259 measurement Methods 0.000 claims description 5
- 238000013507 mapping Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 239000004744 fabric Substances 0.000 description 2
- 230000002411 adverse Effects 0.000 description 1
- 230000002542 deteriorative effect Effects 0.000 description 1
- 238000002592 echocardiography Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
- H04L45/3065—Route determination based on the nature of the carried application for real time traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1023—Media gateways
- H04L65/103—Media gateways in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1033—Signalling gateways
- H04L65/104—Signalling gateways in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
Definitions
- VoIP Voice over Internet Protocol
- QoS Quality of Service
- PSTN Public Switched Telephone Network
- voice call routing only exists in the voice network domain, which is characterized by logical trunk groups interconnecting switches in the network. Voice routing in this context involves routing on circuits or logical trunk groups.
- the IP network routing function previously only operate in the data network domain and is not operable with the applications operating in the application layer.
- FIGURE 1 is a simplified block diagram of an embodiment of a VoIP network
- FIGURE 2 is a simplified logical block diagram of an embodiment of a system for VoIP call routing
- FIGURE 3 is a simplified flowchart of an embodiment of a method for VoIP call routing.
- FIGURE 1 is a simplified block diagram of an embodiment of a VoIP network 10.
- VoIP network 10 is shown comprising a plurality of media gateway nodes 12-14 interconnected by logical trunk groups 16-18 and the Internet 20, however, it should be understood that the network configuration shown in FIGURE 1 is merely exemplary.
- Logical trunk groups 16-18 comprise a plurality of circuits or transmission channels that are capable of interconnecting telephony calls.
- Media gateway nodes 12-14 each comprises a plurality of multimedia media gateways (MG) 22-27 coupled to a multimedia gateway controller (MGC) 30-32, which is sometimes referred to as a Softswitch.
- Multimedia gateways 22-27 each may comprise one or more switching fabric of the same or different types for routing telephony calls.
- the switching fabrics may be packet-switching matrices and/or non-packet switching matrices.
- the multimedia gateways may be coupled to their respective multimedia gateway controller via an ATM (Asynchronous Transfer Mode) or IP (Internet Protocol) backbone network, for example.
- Multimedia gateway controllers 30-32 provides call processing control and user interface functions for TDM (Time Division Multiplex), ATM, IP, and other traffic processed, switched and routed by multimedia gateways 22-27 '.
- the multimedia gateways coupled to a multimedia gateway controller may be geographically distributed.
- the VoIP path bearer between the media gateway nodes may comprise ATM, MPLS (Multi- Protocol Label Switching), IP, or other bearer paths.
- VoIP network 10 enables two users using IP telephone devices such as a telephone operating pursuant to SIP (Session Initiation Protocol) or another suitable protocol to communicate with one another.
- SIP Session Initiation Protocol
- the multimedia gateway nodes may convert data from a format, protocol, and/or type required for one network to another format, protocol, and/or type required for another network, and/or otherwise convert data from a first type of data on a first transmission link to a second type of data on a second transmission link.
- the multimedia gateway nodes may terminate channels from a circuit-switched network and pass streaming media for a packet-switched network, such as Real-Time Transport Protocol (RTP) streams transported via User Datagram Protocol (UDP) in an IP network.
- RTP Real-Time Transport Protocol
- UDP User Datagram Protocol
- Input data for the media gateway may include audio, video, and/or T.120 (real-time multi-point communications), among others, which the media gateway may handle simultaneously or otherwise.
- FIGURE 2 is a simplified logical block diagram of an embodiment of a system for VoIP call routing 40.
- System 40 may reside within each multimedia gateway controller.
- System 40 which may also be referred to as a VoIP call routing engine, comprises at least three logical modules: a VoP resource manager 42, a data measurement module 44, and a route decision module 46.
- System 40 is operable to intelligently route VoIP calls around segments of the network that experience congestion, link failure, node failure or other problems. Because voice calls are very sensitive to adverse network conditions that cause packet delay, out-of-order delivery, packet loss and other problems, the avoidance of congested network segments significantly improves the QoS of the VoIP call. Referring also to FIGURE 3, the operation of system 40 is described below.
- FIGURE 3 is a simplified flowchart of an embodiment of a method for VoIP call routing.
- data measurement module 44 actively monitors the call resources to determine their availability and current status.
- a call resource may be defined as a logical trunk group and the local IP endpoint. This call resource may be so defined as a routing object according to object oriented programming.
- the local IP endpoint may be a local multimedia gateway coupled to the multimedia gateway controller.
- the state of the routing object is based on the availability of connections between the local IP endpoint to all remote IP endpoints reachable by the respective logical trunk group. For example, the state of the routing object based on multimedia gateway 23 and logical trunk group 16 is based on the aggregated data on connection availability between multimedia gateway 23 to multimedia gateway 24 and to multimedia gateway 25. Therefore, if a determination is made that there is a reliability issue associated with the local IP endpoint communicating with all remote IP endpoints referenced by the respective logical trunk group, then that route object is noted as being congested and not available.
- step 52 data measurement module 44 updates VoIP resource manager 42 on the measured resource status.
- step 54 the resource status results is then used to formulate a route list or routing table by VoIP resource manager 42.
- the route list identifies IP endpoint to IP endpoint routes that are not experiencing problems.
- the routes in the route list may include IP paths as well as TDM paths.
- the route list may be prioritized by some predetermined criteria such as reachability and availability.
- the route list is then made available to route decision module 46 each time it is updated or refreshed.
- the route list may include TDM paths as well as IP paths.
- the route list may be prioritized or other organized according to some predetermined criteria, such as availability or amount of congestion.
- route decision module 46 determines the best route based on the route list.
- the best route may include TDM paths as well as IP paths.
- the voice call is set up and routed using the best route determined by route decision module 46.
- the best route may be defined as a route that contains paths or segments that best meets a predetermined requirement, such as exceeding a predetermined threshold of availability.
- network may be used to refer to an entire network or to a network portion, a network application, and/or network apparatus.
- one or more instances of the multimedia gateway and/or Softswitch, or components thereof may be singularly or collectively employed to bridge two or more networks, including those of PSTNs and voice-over-packet (VoP) networks, among others.
- PSTN networks may employ TDM, among other non-packet formats and/or protocols.
- VoP networks may employ ATM, VoIP, universal-mobile-telecommunications-service (UTMS), code-division-multiple-access (CDMA, such as CDMA2000 and/or W-CDMA), voice-over- digital-subscriber-line (VoDSL), other formats and/or protocols, and/or combinations thereof.
- UTMS universal-mobile-telecommunications-service
- CDMA code-division-multiple-access
- VoDSL voice-over- digital-subscriber-line
- other formats and/or protocols and/or combinations thereof.
- Voice call routing previously only exists in the voice network domain, which is characterized by logical trunk groups interconnecting switches in the network. Voice routing in this context involves routing on logical trunk groups.
- the IP network routing function previously only operate in the data network domain and is not operable with the applications operating in the application layer. Information relating to problems detected in the network previously has not been used in routing voice calls.
Abstract
A method of routing a voice call from a local media gateway to a terminating media gateway comprises determining IP network connectivity between the local media gateway and terminating media gateway and generating monitoring results, updating network resource status according to the monitoring results, generating a plurality of routes between the local media gateway and the termininating media gateway in response to the updated network resource status, determining a best route from the plurality of routes, and routing the voice call using the best route.
Description
SYSTEM AND METHOD FOR ROUTING VoIP CALLS
BACKGROUND
Connectivity and voice quality are key reliability issues in today's VoIP (voice over Internet Protocol) networks. Today's VoIP users increasingly expect the Quality of Service (QoS) of the call to be equal or close to that of the Public Switched Telephone Network (PSTN). Because network conditions may change rapidly and continuously, connectivity for a VoIP call cannot be guaranteed. Further, IP network problems such as packet loss, packet delay, and out of order delivery may lead to deteriorating quality of VoIP voice calls.
Unlike data connections, a real-time application like voice calls place much stricter requirements on packet delivery sequence and time. Significant packet loss, packet delay, and out of order delivery problems make telephone conversations difficult. Users may experience echoes and talk overlap that are perceived as significant indicators of inferior QoS.
Previously, voice call routing only exists in the voice network domain, which is characterized by logical trunk groups interconnecting switches in the network. Voice routing in this context involves routing on circuits or logical trunk groups. The IP network routing function previously only operate in the data network domain and is not operable with the applications operating in the application layer.
Therefore, routing voice calls on a data network to satisfy QoS remained a challenge unconquered by the industry.
BRIEF DESCRIPTION OF THE DRAWINGS Aspects of the present disclosure are best understood from the following detailed description when read with the accompanying figures. It is emphasized that, in accordance with the standard practice in the industry, various features are not drawn to scale. In fact, the dimensions of the various features may be arbitrarily increased or reduced for clarity of discussion.
FIGURE 1 is a simplified block diagram of an embodiment of a VoIP network; FIGURE 2 is a simplified logical block diagram of an embodiment of a system for VoIP call routing; and
FIGURE 3 is a simplified flowchart of an embodiment of a method for VoIP call routing.
DETAILED DESCRIPTION It is to be understood that the following disclosure describes many different examples for implementing different features of various embodiments. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and
clarity and does not in itself dictate a relationship between the various embodiments and/or configurations unless otherwise specified.
FIGURE 1 is a simplified block diagram of an embodiment of a VoIP network 10. VoIP network 10 is shown comprising a plurality of media gateway nodes 12-14 interconnected by logical trunk groups 16-18 and the Internet 20, however, it should be understood that the network configuration shown in FIGURE 1 is merely exemplary. Logical trunk groups 16-18 comprise a plurality of circuits or transmission channels that are capable of interconnecting telephony calls. Media gateway nodes 12-14 each comprises a plurality of multimedia media gateways (MG) 22-27 coupled to a multimedia gateway controller (MGC) 30-32, which is sometimes referred to as a Softswitch. Multimedia gateways 22-27 each may comprise one or more switching fabric of the same or different types for routing telephony calls. The switching fabrics may be packet-switching matrices and/or non-packet switching matrices. The multimedia gateways may be coupled to their respective multimedia gateway controller via an ATM (Asynchronous Transfer Mode) or IP (Internet Protocol) backbone network, for example. Multimedia gateway controllers 30-32 provides call processing control and user interface functions for TDM (Time Division Multiplex), ATM, IP, and other traffic processed, switched and routed by multimedia gateways 22-27 '. The multimedia gateways coupled to a multimedia gateway controller may be geographically distributed. The VoIP path bearer between the media gateway nodes may comprise ATM, MPLS (Multi- Protocol Label Switching), IP, or other bearer paths. VoIP network 10 enables two users using IP telephone devices such as a telephone operating pursuant to SIP (Session Initiation Protocol) or another suitable protocol to communicate with one another.
The multimedia gateway nodes may convert data from a format, protocol, and/or type required for one network to another format, protocol, and/or type required for another network, and/or otherwise convert data from a first type of data on a first transmission link to a second type of data on a second transmission link. The multimedia gateway nodes may terminate channels from a circuit-switched network and pass streaming media for a packet-switched network, such as Real-Time Transport Protocol (RTP) streams transported via User Datagram Protocol (UDP) in an IP network. Input data for the media gateway may include audio, video, and/or T.120 (real-time multi-point communications), among others, which the media gateway may handle simultaneously or otherwise.
FIGURE 2 is a simplified logical block diagram of an embodiment of a system for VoIP call routing 40. System 40 may reside within each multimedia gateway controller. System 40, which may also be referred to as a VoIP call routing engine, comprises at least three logical modules: a VoP resource manager 42, a data measurement module 44, and a route decision module 46. System 40 is operable to intelligently route VoIP calls around segments of the network that experience congestion, link failure, node failure or other problems. Because voice calls are very sensitive to adverse network conditions that cause packet delay, out-of-order delivery, packet loss and other problems, the avoidance of congested network segments significantly improves the QoS of the VoIP call.
Referring also to FIGURE 3, the operation of system 40 is described below. FIGURE 3 is a simplified flowchart of an embodiment of a method for VoIP call routing. In step 50, data measurement module 44 actively monitors the call resources to determine their availability and current status. In step 50, a call resource may be defined as a logical trunk group and the local IP endpoint. This call resource may be so defined as a routing object according to object oriented programming. The local IP endpoint may be a local multimedia gateway coupled to the multimedia gateway controller. The state of the routing object is based on the availability of connections between the local IP endpoint to all remote IP endpoints reachable by the respective logical trunk group. For example, the state of the routing object based on multimedia gateway 23 and logical trunk group 16 is based on the aggregated data on connection availability between multimedia gateway 23 to multimedia gateway 24 and to multimedia gateway 25. Therefore, if a determination is made that there is a reliability issue associated with the local IP endpoint communicating with all remote IP endpoints referenced by the respective logical trunk group, then that route object is noted as being congested and not available.
In step 52, data measurement module 44 updates VoIP resource manager 42 on the measured resource status. In step 54, the resource status results is then used to formulate a route list or routing table by VoIP resource manager 42. The route list identifies IP endpoint to IP endpoint routes that are not experiencing problems. The routes in the route list may include IP paths as well as TDM paths. The route list may be prioritized by some predetermined criteria such as reachability and availability. The route list is then made available to route decision module 46 each time it is updated or refreshed. The route list may include TDM paths as well as IP paths. The route list may be prioritized or other organized according to some predetermined criteria, such as availability or amount of congestion. In step 56, for each voice call, route decision module 46 determines the best route based on the route list. The best route may include TDM paths as well as IP paths. In step 58, the voice call is set up and routed using the best route determined by route decision module 46. The best route may be defined as a route that contains paths or segments that best meets a predetermined requirement, such as exceeding a predetermined threshold of availability.
One method to perform resource monitoring and assessment is described in co-pending patent application entitled "System and Method for Determining Network Quality for VoIP Calls," Attorney Docket No. 34986.36, incorporated herein by reference. However, other means for monitoring and measuring the IP network condition may instead be employed. For example, a connectivity check or diagnostic tool may be used to determine network conditions such as congestion or node/link failure.
As employed herein, the term "network" may be used to refer to an entire network or to a network portion, a network application, and/or network apparatus. To that end, one or more instances of the multimedia gateway and/or Softswitch, or components thereof, may be singularly or collectively employed to bridge two or more networks, including those of PSTNs and voice-over-packet (VoP) networks, among others. PSTN networks may employ TDM, among other non-packet formats and/or
protocols. VoP networks may employ ATM, VoIP, universal-mobile-telecommunications-service (UTMS), code-division-multiple-access (CDMA, such as CDMA2000 and/or W-CDMA), voice-over- digital-subscriber-line (VoDSL), other formats and/or protocols, and/or combinations thereof.
Previously, there were no routing engines that integrate IP -based networks and traditional voice networks to determine the best route to route voice calls. Voice call routing previously only exists in the voice network domain, which is characterized by logical trunk groups interconnecting switches in the network. Voice routing in this context involves routing on logical trunk groups. The IP network routing function previously only operate in the data network domain and is not operable with the applications operating in the application layer. Information relating to problems detected in the network previously has not been used in routing voice calls.
Claims
1. A method of routing a voice call from a local media gateway to a terminating media gateway, comprising: determining IP network connectivity between the local media gateway and terminating media gateway and generating monitoring results; updating network resource status according to the monitoring results; generating a plurality of routes between the local media gateway and the terminating media gateway in response to the updated network resource status; determining a best route from the plurality of routes; and routing the voice call using the best route.
2. The method of claim 1, wherein determining IP network connectivity comprises continuously monitoring network connectivity between a local IP endpoint associated with the local media gateway and all IP endpoints reachable by a logical trunk group associated with the local IP endpoint.
3. The method of claim 1, wherein determining IP network connectivity comprises continuously monitoring network connectivity between all local IP endpoints associated with the local media gateway to all IP endpoints reachable by a logical trunk group associated with the local IP endpoints.
4. The method of claim 1, wherein generating a plurality of routes comprises generating a plurality of routes comprising data and voice paths.
5. The method of claim 1, wherein generating a plurality of routes comprises generating a plurality of routes comprising IP and TDM paths.
6. The method of claim 1, wherein determining a best route comprises selecting a route that best meets a predetermined criteria.
7. The method of claim 1, wherein determining a best route comprises selecting a route that is least congested.
8. A method of routing a VoIP call from a local IP endpoint to a terminating switch, comprising: defining a routing object having the local IP endpoint and a logical trunk group associated with the local IP endpoint; determining the state of the routing object; and routing the VoIP call based on the state of the routing object.
9. The method of claim 8, wherein determining the state of the routing object comprises determining connection between the local IP endpoint and all remote IP endpoints reachable by the logical trunk group.
10. The method of claim 8, further comprising generating a plurality of routes between the local IP endpoint and the terminating switch in response to at least the state of the routing object.
11. The method of claim 10, further comprising determine a best route from the plurality of routes.
12. The method of claim 10, wherein generating a plurality of routes comprises generating a plurality of IP, TDM and IP/TDM routes.
13. The method of claim 10, wherein determining a best route comprises selecting a route that best meets a predetermined criteria.
14. The method of claim 10, wherein determining a best route comprises selecting a route that is least congested.
15. A VoIP call routing engine comprises : a data measurement module operable to monitor network connectivity between a local IP endpoint and a terminating media gateway and generating monitoring results; a VoIP resource manager operable to generate a plurality of routes between the local IP endpoint and the terminating media gateway in response to the monitoring results; and a route decision module operable to determine a best route from the plurality of routes and route the VoIP call using the best route.
16. A method of routing a VoIP call comprising: means for continuously monitoring network connectivity between a local IP endpoint and a terminating switch and generating monitoring results; means for updating network resource status according to the monitoring results; means for generating a plurality of routes between the local D? endpoint and the terminating switch in response to the updated network resource status; means for determine a best route from the plurality of routes; and means for routing the VoIP call using the best route.
17. The VoIP call routing engine of claim 15, further comprising a routing object associated with the local IP endpoint and a logical trunk group.
18. A VoIP system comprising: a logical trunk group between a local IP endpoint and a media gateway; a data measurement module operable to monitor network connectivity between the local IP endpoint and the media gateway and generating monitoring results; a VoIP resource manager operable to generate a plurality of routes between the local IP endpoint and the media gateway via mapping a logical circuit contained in the logical trunk group to the IP endpoint, in response to the monitoring results; and a route decision module operable to determine a best route from the plurality of routes and route the VoIP call using the best route.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/078,531 | 2005-03-11 | ||
US11/078,531 US8031696B2 (en) | 2005-03-11 | 2005-03-11 | System and method for routing VoIP calls |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006095256A2 true WO2006095256A2 (en) | 2006-09-14 |
WO2006095256A3 WO2006095256A3 (en) | 2007-04-05 |
Family
ID=36579984
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2006/000528 WO2006095256A2 (en) | 2005-03-11 | 2006-03-10 | System and method for routing voip ( voice over internet protocol) calls |
Country Status (2)
Country | Link |
---|---|
US (1) | US8031696B2 (en) |
WO (1) | WO2006095256A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2064909A2 (en) * | 2006-09-18 | 2009-06-03 | Nokia Corporation | Resource management techniques for wireless networks |
US7995557B2 (en) | 2005-03-11 | 2011-08-09 | Genband Us Llc | System and method for determining network quality for voIP calls |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100399773C (en) * | 2005-04-29 | 2008-07-02 | 华为技术有限公司 | Interconnection between domains |
US20060262776A1 (en) * | 2005-05-23 | 2006-11-23 | Pollock Graham S | System and method for auto-discovery of peering and routing in a combined circuit -switched/packet-switched communication network using trip protocol |
JP4681480B2 (en) * | 2006-03-23 | 2011-05-11 | 富士通株式会社 | Traffic control device, traffic control system, and traffic control method |
CN101365169B (en) | 2007-08-09 | 2011-11-02 | 华为技术有限公司 | Routing control implementing method, system, media gateway and media gateway controller |
US9288309B1 (en) * | 2013-09-25 | 2016-03-15 | Amazon Technologies, Inc. | Quality-based phone routing |
US10498647B2 (en) * | 2017-02-16 | 2019-12-03 | Timur Voloshin | Method and program product for electronic communication based on user action |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6330316B1 (en) * | 1999-03-12 | 2001-12-11 | Nortel Networks Limited | Alternate routing schemes using quality of service information for calls involving unreliable networks |
WO2002005068A2 (en) * | 2000-07-07 | 2002-01-17 | Xybridge Technologies, Inc. | End-to-end qos in a softswitch based network |
WO2004030288A1 (en) * | 2002-09-30 | 2004-04-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Combining narrowband applications with broadband transport |
US6748433B1 (en) * | 1999-07-12 | 2004-06-08 | Ectel, Ltd. | Method and system for controlling quality of service over a telecommunication network |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6683877B1 (en) * | 1999-02-16 | 2004-01-27 | Noetel Networks Limited | Carrying voice traffic over broad band networks |
US6680952B1 (en) | 1999-06-01 | 2004-01-20 | Cisco Technology, Inc. | Method and apparatus for backhaul of telecommunications signaling protocols over packet-switching networks |
US6832254B1 (en) * | 1999-08-23 | 2004-12-14 | Nortel Networks Limited | Method and apparatus for associating an end-to-end call identifier with a connection in a multimedia packet network |
US6799210B1 (en) * | 2000-06-21 | 2004-09-28 | Nortel Networks Limited | Dynamic association of endpoints to media gateway controllers |
US20020131604A1 (en) | 2000-11-08 | 2002-09-19 | Amine Gilbert A. | System and method for measuring and enhancing the quality of voice communication over packet-based networks |
US6947434B2 (en) | 2000-11-16 | 2005-09-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Subgroup multicasting in a communications network |
US7173910B2 (en) | 2001-05-14 | 2007-02-06 | Level 3 Communications, Inc. | Service level agreements based on objective voice quality testing for voice over IP (VOIP) networks |
DE60222478T2 (en) | 2002-07-25 | 2008-06-12 | Telefonaktiebolaget Lm Ericsson (Publ) | END TO END TESTS BETWEEN GATEWAYS IN AN IP NETWORK |
US7333500B2 (en) | 2002-09-24 | 2008-02-19 | Nortel Networks Limited | Methods for discovering network address and port translators |
US7203172B2 (en) * | 2002-09-27 | 2007-04-10 | Telcordia Technologies | Internodal routing engine for a next generation network |
US7313098B2 (en) | 2002-09-30 | 2007-12-25 | Avaya Technology Corp. | Communication system endpoint device with integrated call synthesis capability |
US7486621B2 (en) * | 2003-05-30 | 2009-02-03 | Alcatel-Lucent Usa Inc. | Method and apparatus for load sharing and overload control for packet media gateways under control of a single media gateway controller |
US7031264B2 (en) | 2003-06-12 | 2006-04-18 | Avaya Technology Corp. | Distributed monitoring and analysis system for network traffic |
ATE387782T1 (en) | 2003-08-28 | 2008-03-15 | Ericsson Telefon Ab L M | RESOURCE MANAGEMENT SYSTEM AND METHOD FOR ENSURE QOS IN NETWORKS WITH INTERNET PROTOCOL (IP) |
US6956820B2 (en) * | 2003-10-01 | 2005-10-18 | Santera Systems, Inc. | Methods, systems, and computer program products for voice over IP (VoIP) traffic engineering and path resilience using network-aware media gateway |
WO2005071890A1 (en) | 2004-01-27 | 2005-08-04 | Actix Limited | Monitoring system for a mobile communication network for traffic analysis using a hierarchial approach |
US7864665B2 (en) * | 2004-10-07 | 2011-01-04 | Tekelec | Methods and systems for detecting IP route failure and for dynamically re-routing VoIP sessions in response to failure |
US20070183339A1 (en) | 2005-02-18 | 2007-08-09 | Rousell Graham P | System and method of producing statistical information about call durations |
US7995557B2 (en) | 2005-03-11 | 2011-08-09 | Genband Us Llc | System and method for determining network quality for voIP calls |
-
2005
- 2005-03-11 US US11/078,531 patent/US8031696B2/en active Active
-
2006
- 2006-03-10 WO PCT/IB2006/000528 patent/WO2006095256A2/en not_active Application Discontinuation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6330316B1 (en) * | 1999-03-12 | 2001-12-11 | Nortel Networks Limited | Alternate routing schemes using quality of service information for calls involving unreliable networks |
US6748433B1 (en) * | 1999-07-12 | 2004-06-08 | Ectel, Ltd. | Method and system for controlling quality of service over a telecommunication network |
WO2002005068A2 (en) * | 2000-07-07 | 2002-01-17 | Xybridge Technologies, Inc. | End-to-end qos in a softswitch based network |
WO2004030288A1 (en) * | 2002-09-30 | 2004-04-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Combining narrowband applications with broadband transport |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7995557B2 (en) | 2005-03-11 | 2011-08-09 | Genband Us Llc | System and method for determining network quality for voIP calls |
EP2064909A2 (en) * | 2006-09-18 | 2009-06-03 | Nokia Corporation | Resource management techniques for wireless networks |
EP2064909A4 (en) * | 2006-09-18 | 2013-02-20 | Nokia Corp | Resource management techniques for wireless networks |
US8774100B2 (en) | 2006-09-18 | 2014-07-08 | Nokia Corporation | Resource management techniques for wireless networks |
Also Published As
Publication number | Publication date |
---|---|
US20060203803A1 (en) | 2006-09-14 |
US8031696B2 (en) | 2011-10-04 |
WO2006095256A3 (en) | 2007-04-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7995557B2 (en) | System and method for determining network quality for voIP calls | |
US8031696B2 (en) | System and method for routing VoIP calls | |
US7715312B2 (en) | Methods and systems for maintaining quality of service (QOS) levels for data transmissions | |
EP1805939B1 (en) | METHODS AND SYSTEMS FOR DETECTING IP ROUTE FAILURE AND FOR DYNAMICALLY RE-ROUTING VoIP SESSIONS IN RESPONSE TO FAILURE | |
US7424025B2 (en) | Methods and systems for per-session dynamic management of media gateway resources | |
EP1850541B1 (en) | Controlling time-sensitive data in a packet-based network | |
US7936694B2 (en) | Sniffing-based network monitoring | |
US7480283B1 (en) | Virtual trunking over packet networks | |
US20060018255A1 (en) | Defining a static path through a communications network to provide wiretap law compliance | |
US7746771B1 (en) | Method and apparatus for controlling logging in a communication network | |
US20090274040A1 (en) | Mid-call Redirection of Traffic Through Application-Layer Gateways | |
JP2006504293A (en) | Monitoring communication network status | |
US7733769B1 (en) | Method and apparatus for identifying a media path in a network | |
US20070291655A1 (en) | Waveform Quality Feedback for Internet Protocol Traffic | |
EP1583304B1 (en) | Media gateway | |
Ohms et al. | Providing of qos-enabled flows in sdn exemplified by voip traffic | |
EP1493251B1 (en) | Virtual trunking over packet networks | |
US11770419B2 (en) | Devices and systems for voice over internet protocol codec selection | |
Jîtaru et al. | Evaluation of Carrier Supporting Carrier networks for various types of services | |
Sidiropoulou | VoIP Operators: From a Carrier Point of View | |
Ohms et al. | Providing of QoS-Enabled Flows in SDN |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 06727299 Country of ref document: EP Kind code of ref document: A2 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 6727299 Country of ref document: EP |