This invention relates generally to the communication field, and more specifically to a new and useful system and method for improving routing in a distributed communication platform in the communication field.
In communication, different communication paths will have different characteristics. Not only can these characteristics result in a wide range of communication properties such as from media quality and latency. Additionally, the resources involved in routing a communication can constantly change. Resources can fail, new resources can be added, and operating properties of a resource could change. Further more there are functionality, technical, and business related restrictions on establishing a communication. Thus, there is a need in the communication field to create a new and useful system and method for improving routing in a distributed communication platform. This invention provides such a new and useful system and method.
The following description of preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.
1. Method for Routing Communication
As shown in
The method can be particularly applicable to communication platforms that operate on a distributed computing infrastructure, and, more specifically, in communication platforms that facilitate additional media or signaling functionality. For example, a communication platform may provide media functionality such as recording, transcription services, conferencing, application processing and other suitable communication functionality such as those provided in the communication platform described in U.S. Pat. No. 8,306,021 issued 6 Nov. 2012, which is incorporated in its entirety by this reference.
The method is preferably employed to establish a communication path between two endpoints where the path reflects the routing prioritization while also balancing resources of the network with other routing requests. The best route (i.e., a preferred route in consideration of multiple factors) can be automatically detected and used in routing. Such routing can be invoked when an error occurs to route around a failed node, to determine routes in complex routing scenarios (e.g., a phone number in Brazil is calling a number in Spain but a required resource is only available in the US or Asia), other suitable scenarios. The method can preferably balance a number of technical considerations, business considerations, and user considerations without depending on pre-set heuristics. The method also takes into account that there will be additional traffic in addition to the immediate request, and traffic can be distributed across multiple routes. For example, a VoiP provider can use the system to provide substantially high quality media communication while balancing the contractual obligations to route a set portion of traffic through particular carrier nodes.
The method can have further beneficial application in other scenarios. In one case the communication platform may include multiple modes of communication, PSTN, SIP, WebRTC, client application (e.g., VoIP application, mobile application, browser application, etc), or other suitable mode that can be available to a particular endpoint. Such complicating factors can additionally be seamlessly integrated so that the method can be applied to situations where multiple forms of communication are available. In the case of client applications, a client application could connect to multiple datacenters to open up multiple access nodes to open up more routing options for that particular client application endpoint For example if a client application happens to be in Central America and dials a US number then the best route is preferably one with a leg connected to a US region. However, if the client application dials another endpoint in Rio, then the leg that is established may use the node connected through a Sao Paolo data center. Such automatic flexibility is preferably a benefit of such a routing method.
The method is preferably applied to establishing routing of a media channel but may alternatively or additionally be applied to routing of signaling or any suitable communication channel. More specifically, the method can be applied to SIP based media routing within a VoIP-based communication platform. Herein, SIP is described as a preferred signaling and media protocol, but any suitable signaling, media, or form of communication channel can be used. The VoIP provider even though it internally uses Sip can preferably interface with other forms of communication such as PSTN. The medium of communication can be voice, video, screen sharing, multi-media streaming, IP based data transfers, and/or any suitable medium of communication. In one preferred variation, the method can be used to dynamically select a routing profile to use at least two different routing preferences depending on the particular communication session.
Block S110, which includes generating edge cost scores in a communication network, functions to establish the base scoring of the network of a provider. The provider is preferably a VoIP provider with a plurality of edge nodes and a plurality of internal nodes. The internal nodes are preferably media-related processing nodes such as such as application nodes, transcoding resources, recording resources, simple pass through routers, quality of service enforcement nodes, speech recognition resources, text-to-speech resources, media mixers, and other suitable media resource nodes. An edge cost score is preferably a measure of an assigned cost to route from one node to a second node. The cost score can be an integer value, a number within a range of values, a classification, or any suitable value that can be used as a metric of comparison when applying the selection algorithm to generate a determined route. The cost scores of connected legs are preferably combinable either through some mathematical operation (e.g., summing) or function. The internal network of the communication platform up to and preferably including nodes that bridge out of the network are preferably scored. In some variations, not all edges (or “routes”) may have an assigned edge cost and a default cost may be used.
The network is preferably defined within at least one layer of a communication stack for a communication platform. In one example, the set of network nodes preferably includes more application layer defined computing nodes that provide high level signaling and media functionality such as routing, recording, business logic, conferencing, and other higher level media functionality. In another example, the nodes can be defined as different regional centers such that the method is used when routing between computing resources of the regional center. Other layers may employ routing approaches independent of the prioritized routing approach. For example, lower level IP based routing can use alternative routing approach within the nodes, while the method of routing is used for routing between the nodes. A substantial portion of the nodes preferably will be assigned an edge cost score. Alternatively, only the edges selected or pre-defined may have an edge cost score. For example, outbound edges between the communication network and an external resource (e.g., a carrier network) may be the most significant routing decisions and will be those that are considered in the method. If an edge is new or for any suitable reason has not had an edge cost assigned, a default edge cost, an average edge cost, a manually assigned edge cost, an edge cost from a substantially similar edge, or any suitably generated edge cost may be used.
Generating an edge cost across all or a substantial portion of the communication network may include simulating communication network traffic with an at least partially defined route. Simulated communication functions to collect data for at least one edge of the communication. When simulating communication network traffic, at least one edge is pre-selected to be used during the communication. If a new machine is deployed to the communication network, communication traffic may be initially simulated to establish the initial cost score. As shown in
Block S112, which includes collecting network factors, functions to obtain input data to compute a cost score for direct paths between nodes. The network factors can includes various properties, performance patterns, assigned values, measurements, and/or any suitable metric. In a communication platform the communication factors can include network latency between hops, audio/media jitter (the interval delay as defined by RFC3550), current load of a node, delay through a host, delay through a host, average call length of previously placed call (e.g., length of calls through a particular carrier to a particular number series), packet loss, post dial delay (PDD) (i.e., time for carrier to indicate the other side is ringing), time to failure (i.e., time it took for a carrier to fail a call), monetary cost to the platform provider, monetary price charged to account holder, media quality, and/or any suitable factor. The factors can be metrics measured in different dimensions. Network latency, audio jitter, delay through a host, average call length, PDD, and time to failure can be measured as a time metric (e.g., milliseconds). Current load of a node can be measured in percentage of capacity. Monetary cost and price can be measured in a currency value. Media quality may be an arbitrary measurement scale.
One or more factor can be collected for use in calculating the cost score as shown in
Block S114, which includes calculating cost scores, functions to synthesize the collected network factors into a single cost score for a routing option along an edge. For each edge, a function is applied to the factors to result in a single cost estimate. However, not all factors may be measured in the same dimension, have the same scale, or even units. The function is preferably set according to heuristics that prioritize different factors. For example, factors that impact final audio quality may be used within the function to result in a proportionally greater impact on the final cost score than factors with less prioritization such as possible price. In one variation, the function is a fixed function pre-configured in the communication platform. In another variation, the function may be machine learned or automatically optimized according to feedback.
As one example function, the cost function can depend on the total latency between two nodes (latency and host delay) and the jitter. In this example, the function may be designed to result in a target cost value if the total latency is less than 200 ms and the jitter is less than 10 ms, which are exemplary settings for acceptable performance. The function may designed so that if jitter is above 10 ms then the resulting cost goes up exponentially and if total latency exceeds 200 ms the resulting cost goes up exponentially. The cost function can be customized for any suitable response to input factors.
As described more below, there can be multiple routing profile classes as shown in
Block S120, which includes assigning distribution values, functions to define proportioning of distribution between selected routes. The distribution values can include a set of values. The distribution values are preferably applied/used after the routes have been narrowed based on cost and the score tolerance. The distribution values may be assigned to an edge, to a node, or to specific route. The distribution values are preferably pre-configured to be assigned within the route—a distributed value or values can be obtained for any suitable route. In some cases a route may not have an explicitly assigned distribution value, in which case a default value may be used. Preferably, the distributed values are assigned according to external factors around preference for how traffic is distributed across multiple equivalent routes. In the variation, where the distribution value is assigned to an edge and/or a node, a calculated route distributed value(s) is preferably calculated through the processing of the elemental distributed values of edges and/or nodes contained in a route. For example, a weight value may be assigned to two edges. The resulting weight value of a route that passes through those two edges may be the sum of the weights. Similarly, the weights could be the average or any suitable calculated result. In another variation, the distributed values are assigned on a per route basis, the full set of possible routes may be calculated and a weight assigned to each possible route. Such a system may employ sparse over-ride assignment or any suitable defining approach.
In one preferred variation, the distribution values include a weight. A weight is preferably a value defined to indicate preference of how often one path should be selected over other possible paths. The weights function to distribute communication over multiple routes in some determined ratio for a set of similar traffic. As described below, the weight value is applied in selecting between routes that are determined equivalent through the cost score and the score tolerance. For two routes (with the same cost score), the route with a weight of 80 will be selected 80% of the time if the other route has a weight of 20, which would be selected 20% of the time. Weight values that are the same are preferably deemed equal preference. For two routes with the same cost score have weights of 35, they each would be selected half the time.
In another, preferred variation, the distribution values can additionally include a priority value. The priority values can be similarly assigned to an edge and a default value may be assumed if a value is not assigned. The priority value preferably defines classes of preference between equivalent routes. They can be used to narrow the consideration pool. Routes assigned the same priority value are considered for selection as a group. In the case of a telecommunication platform, there may be top tier network carriers, middle-tier carriers, and bottom tier carriers. The nodes routing to these carriers can be assigned priority according to those three classes so that if there is a top tier carrier node, then middle or bottom tier options are not considered. The value of the priority value may use a greater value to indicate stronger preference such that priority values can be added across edges in a route. Alternatively, the priority values may use smaller values to indicate greater priority. The priority values can be an initial layer of distribution, and the weighted distribution can be applied afterwards. Other variations may apply any suitable distribution value to define how route selection is distributed between “equivalent” routes (after considering score tolerance).
Priority and weighting can function to enable external factors to be considered when determining network routing. In the case of a communication platform with supporting nodes that serve particular carriers, there will often be business arrangements, partnerships, contracts, and other obligations that create an obligation or an incentive to use particular nodes. For example, one phone carrier may establish a contract with the communication platform dictating that some minimum volume of traffic will be serviced by the carrier node. Another phone carrier may offer similar performance in terms of the cost score, but if no contract is place or the conditions of the contract are less restrictive, the first carrier node may result in corresponding routes to be more greatly weighted than the second carrier node. Other factors, such as resource limitations, technical tradeoffs, and other considerations of different nodes or routes may additionally or alternatively be considered when assigning a weight.
Block S130, which includes setting a score tolerance, functions to establish a range of “fuzziness”. The score tolerance is preferably a value that defines when cost scores should be considered equivalent—defines the range that cost scores can deviate and be considered for selection. In execution, if two routes through a network have similar cost scores, the effective performance may be substantially similar and accordingly the method preferably treats the cost scores as equivalent. When used in performing the network graph search, the score tolerance is preferably applied to the lowest cost score (i.e., best cost score). The score tolerance is preferably added to the lowest cost score, and the (inclusive or exclusive) range sets what cost scores deemed equivalent. For example, if the best route based on the cost score is 10 and the score tolerance is set to a value of 2 then another route with a score of 11 is considered but a route with a score of 15 is not. Herein, lower scores are the better routes based on the cost function but alternative implementations may use a higher score to indicate a better route or a score closer to a target value, the route selection deviation range can be applied in any suitable way to establish a fuzziness in distinguishing between cost scores that are near the same value. The score tolerance is preferably a fixed value, but the score tolerance may be a defined as a sliding scale, a function of score tolerance, or a probabilistic module of tolerance, or any suitable function to determine a range of values to consider.
Block S140, which includes receiving a communication directive, functions to trigger establishing, upgrading, or otherwise setup communication routing through the network of the communication platform. In one variation receiving a communication directive specifies establishing a new communication session and accordingly occurs at the beginning of a session. As shown in
In addition to receiving a communication directive, the method can include determining functional media communication resources to support the communication session S142, which functions to select the types of nodes, sequencing/organization of the types nodes, and/or basic topology of the network routing to support the communication session. For example, as shown in
Block S150, which includes performing network graph search with a route selection process that includes considering cost score within a score tolerance, and distributing selection in accordance to a distribution value, functions to use defined distribution values such as weights and/or prioritization when selecting between substantially equivalent routes for serving a particular instance of communication routing. The network graph search preferably considers multiple factors to adequately determine a route, path or at least a portion of a routing for communication. The network graph problem in one scenario, as shown in
In another scenario, performing network graph search can solve routing from one internal node of the communication platform to an outlet of a communication platform as shown in
Additionally, a communication route may have defined intermediary nodes, which can have a defined network graph sequence and/or topology. As shown in
Performing network graph search preferably includes applying the selection process of: identifying a lowest cost route according to the total cost score of each route from a set S152, setting a consideration pool to routes with cost scores within a range tolerance of the identified lowest cost route S156, and selecting a route based on at least one distribution values of the routes in the consideration pool S158. In one variation, the distribution value of the route includes a weight value, which defines a distribution of communications over those set of considered routes as shown in
Performing network graph search preferably includes traversing the network graph to identify at least one route according to the cost score S154. Traversing the network graph functions to inspect the route options of the network between at least a source node and a goal node. The method preferably depends on consideration of a set of suitable routes and accordingly operates with a modified form of graph search. Traversing the network graph preferably identifies the best score in addition to at least the routes within the score tolerance as shown in
The traversal heuristics are preferably augmented to accommodate modified consideration pool of routes and performing network graph search preferably includes setting a consideration pool to routes with cost scores within a range defined by the score tolerance S156. The consideration pool is preferably a collection or set of routes that are considered equivalent to the best route according to cost. The score tolerance is preferably a range determined by adding a discrete value to the best route cost. Alternatively, the range may be a probabilistic distribution of equivalency to the best routing option. The distribution can additionally contribute to the distribution values described below. In this case, each route may be included in the consideration pool but the probability of selection for use goes down with the distance from the best route score. In one variation, the network traversal algorithm can be modified to accommodate for cost score equivalence and optionally distribution values. In one variation, performing network graph search preferably includes traversing the network graph in identifying a least cost route while factoring in a score tolerance of the costs. This can be performed in any suitable approach while traversing the network graph. In one variation, performing a best-first traversal approach can traverse the best route, and once one is found traversing all routes that are and remain within the score tolerance. In other variations, the score tolerance can be considered while traversing the network graph.
Performing a network graph search additionally includes selecting a route based on a distribution values of the routes in the pool S158, which functions to allow communication to be shared amongst routes that are substantially equivalent as defined by the score tolerance. The distribution value is preferably the sum of the edge distribution values along a route. Alternatively, the distribution of a route can be the maximum value, the minimum value, the average value, the median value, or any suitable value calculated from the individual edge or node associated distribution values. As mentioned above, in a telecommunications application, weights are preferably assigned to different carrier nodes, which determine which external partner is engaged when establishing communication outside the communication platform. Such external entities can have related business contracts that dictate how much traffic should be terminated or serviced through them by the network. Such carrier node preference can be embodied in the relative distribution values. Additionally or alternatively, distribution values can be applied to place preference to use (or not use) particular resources within the route.
In one preferred implementation the distribution value includes a weight. The weigh value is preferably a value that indicates the target distribution of communication through a consideration pool of routes. Selecting a route preferably substantially promotes a distribution between the routes in the consideration pool to be in proportion to the weights. The proportion is approximated over total or eventual traffic. The weighting preferably functions to achieve some balancing across a set of substantially equivalent routing options. As a basic example, if the consideration pool of routes includes a route A with a weight of 80 and a route B with a weight of 20 then 80% of communication with the same parameters (e.g., same start and end destinations) will go through route A and 20% through route B. The weights are preferably normalized across the considered routes. For example a route C with a weight of 100 was also considered in that pool, then traffic would be distributed as 40% route A, 10% route B, and 50% route C. When distributing traffic, the selection can be applied randomly with the weighted distribution, may be made in round-robin/alternating fashion according to distribution, or in any suitable manner.
In another preferred implementation, the distribution value of a route can include a priority and a weight. The priority value preferably defines an additional mechanism through which distribution can be controlled. Priority can add an additional filter where only routes of the highest level of priority in the consideration pool are considered. Priority is preferably evaluated based on the highest priority value such that priorities of multiple edges in a route can be summed and used as a route prioritization. Alternatively, the greatest priority value (whether communicated in a larger or lesser value) within any given edge of a route can be use. Any suitable approach can be used to define the route prioritization. Applying the prioritization value preferably results in a prioritized consideration pool. For example, if a consideration pool includes route A with priority 5, route B with priority 3, and route C with priority 5, then route A and C are in the prioritized consideration pool. After the priority is used to select the top priority equivalent routes, weight values can be used to distribute the communication in manner similar to above. Other distribution heuristics may alternatively or additionally be applied such as including a fuzziness of prioritization, using a continuation distribution function, or any suitable approach to impact distribution.
Block S160, which includes establishing the media routing through the network resources specified between the originating endpoint and the destination endpoint, functions to use the route selected in accordance to performing the network graph search. The media is preferably routed through the selected resources and communication is established. In the case, where the method is applied to other forms of communication such as signaling, then the communication is executed over the selected route in the corresponding mode. In the case of a VoIP provider, establishing the media routing can include negotiating and performing any suitable form of handshaking through signaling to setup the media communication channel. If the communication is a new communication, the communication is established for the first time for that communication session. If the communication session existed previously, but was modified (e.g., to include new required media resources), then the signaling preferably handles removing/unsubscribing un-used resources and inviting new resources to modify the previous route to conform to the newly selected route. The method is preferably applied in distributed computing infrastructures. A distributed infrastructure can include multiple datacenters or regions. The different regions can be separated by geographically significant distance (e.g., greater than 1000 miles or 2000 miles). As the communication platform can include these different regions, the media routing can included routing between the different regions.
The method can additionally include selecting a cost function according to a routing profile S170, which functions to allow the cost function to vary between communication instances on the communication platform. In implementation, the use of different route profiles can allow two communication requests within the platform to use different cost score functions within block S114 as shown in
In one variation, the type of routing profile is determined by account settings. An account within a multitenant communication platform can pre-configure the account to use one type of account profile. For example, one account may set the account to use best media quality, another account may want to minimize price, and an account using a free trial may be forced into an account profile that prioritizes lower cost to the platform.
In another variation, the type of routing profile is specified for the current communication session, which functions to allow the preference to be set on a call-by-call basis. The account profile can additionally be updated during a communication session. For example, a marketing application may make thousands of calls using lowest cost routing profile, and after a caller picks up and engages with the marketing representative, the routing profile can be updated to a media quality routing profile when updating the routing.
In yet another variation, a routing profile class can alternatively be set based on the type of communication (e.g., video uses quality-prioritized scores, voice uses price-prioritized scores). Other variations may enable a function to be customized by an administrator, account holder, or any suitable entity.
2. Example Scenarios
In one exemplary scenario of applying the method can involve a network, as shown in
If the distribution step does not consider the priority value and only applies weighting within the consideration pool, then the traffic will be distributed across all three routes with a distribution proportion of approximately A-D-E 23%, A-C-E 62%, and A-B-E 15%. If the cost tolerance is 3, then A-D-E is the only route in the consideration pool and all traffic is distributed to that route. As shown in this example, cost takes precedence. The route with the lowest cost is selected over a path with a higher cost. However, costs that are “close enough” are considered equal in order to allow for some “fuzziness” of the cost tolerance. And finally, paths with greatest priority value receive traffic distribution corresponding to normalized weight ratios.
As one exemplary use within a VoIP provider, an inbound call may be received and signaled through different nodes of the VoIP provider as shown in
In a related example, an in-session communication may be previously established, but business/control logic may trigger a change in the media resource requirements. For example, a recording resource may need to be added to record the message. The method can be applied with updated resource requirements to determine a new preferred route. The application logic preferably triggers reconfiguring the route to achieve the new route. Reconfiguring can include adding, removing, and updating resources. Such reconfiguring is preferably achieved through a sequence of signaling messages to the appropriate resources. Even though a media mixer was still required in the new route, the method determines that different media mixer node would provide better performance.
3. System for Routing Communication
As shown in
The communication resource nodes can be any suitable nodes. Preferably the nodes are an abstracted view of the resources and the complete routing hops. For example, a host that may have multiple virtual hosts or services may be viewed as a single resource. As another example, the same type of resource within one data center may be abstracted as the same node since networking and load balancing between the resources within a datacenter may be handled in an alternative lower level approach. While the actual set of resources can vary depending on the communication platform, one preferred implementation includes carrier gateways that interface with different carrier networks. The carrier networks will additionally include different access to endpoints—a carrier gateway may only be capable of accessing a set number of endpoints. For example, a US-based carrier A may not be able to access UK-based phone numbers. Other edge gateways may include SIP-edge gateways that interface with public SIP based devise, client application protocol (e.g., different IP based applications that can act as a communication endpoint), and other suitable forms of communication.
The set of communication resource nodes can additionally include an application node that facilitates determining basic network topology of a route. The network topology preferably describes the node types required for a route, the optional nodes in a route, mandatory nodes, order/configuration of different node types, and other basic route requirements to fulfill a request. The application node preferably facilitates the selection of functionality requirements of the route and can manage establishing the route. In a basic communication such resource functionality requirements may be predefined.
The system and methods of the preferred embodiment and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the communication platform. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.
This application claims the benefit of U.S. Provisional Application Ser. No. 61/791,800, filed on 15 Mar. 2013, which is incorporated in its entirety by this reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5274700 | Gechter et al. | Dec 1993 | A |
| 5526416 | Dezonno et al. | Jun 1996 | A |
| 5581608 | Jreij et al. | Dec 1996 | A |
| 5598457 | Foladare et al. | Jan 1997 | A |
| 6026440 | Shrader et al. | Feb 2000 | A |
| 6094681 | Shaffer et al. | Jul 2000 | A |
| 6138143 | Gigliotti et al. | Oct 2000 | A |
| 6185565 | Meubus et al. | Feb 2001 | B1 |
| 6192123 | Grunsted et al. | Feb 2001 | B1 |
| 6223287 | Douglas et al. | Apr 2001 | B1 |
| 6269336 | Ladd et al. | Jul 2001 | B1 |
| 6373836 | Deryugin et al. | Apr 2002 | B1 |
| 6425012 | Trovato et al. | Jul 2002 | B1 |
| 6430175 | Echols et al. | Aug 2002 | B1 |
| 6434528 | Sanders | Aug 2002 | B1 |
| 6445694 | Swartz | Sep 2002 | B1 |
| 6445776 | Shank et al. | Sep 2002 | B1 |
| 6459913 | Cloutier | Oct 2002 | B2 |
| 6493558 | Bernhart et al. | Dec 2002 | B1 |
| 6496500 | Nance et al. | Dec 2002 | B2 |
| 6501832 | Saylor et al. | Dec 2002 | B1 |
| 6507875 | Mellen-Garnett et al. | Jan 2003 | B1 |
| 6600736 | Ball et al. | Jul 2003 | B1 |
| 6606596 | Zirngibl et al. | Aug 2003 | B1 |
| 6614783 | Sonesh et al. | Sep 2003 | B1 |
| 6625258 | Ram et al. | Sep 2003 | B1 |
| 6625576 | Kochanski et al. | Sep 2003 | B2 |
| 6636504 | Albers et al. | Oct 2003 | B1 |
| 6662231 | Drosset et al. | Dec 2003 | B1 |
| 6704785 | Koo et al. | Mar 2004 | B1 |
| 6707889 | Saylor et al. | Mar 2004 | B1 |
| 6711249 | Weissman et al. | Mar 2004 | B2 |
| 6738738 | Henton | May 2004 | B2 |
| 6757365 | Bogard | Jun 2004 | B1 |
| 6765997 | Zirngibl et al. | Jul 2004 | B1 |
| 6768788 | Langseth et al. | Jul 2004 | B1 |
| 6778653 | Kallas et al. | Aug 2004 | B1 |
| 6785266 | Swartz | Aug 2004 | B2 |
| 6788768 | Saylor et al. | Sep 2004 | B1 |
| 6792086 | Saylor et al. | Sep 2004 | B1 |
| 6798867 | Zirngibl et al. | Sep 2004 | B1 |
| 6807529 | Johnson et al. | Oct 2004 | B2 |
| 6807574 | Partovi et al. | Oct 2004 | B1 |
| 6819667 | Brusilovsky et al. | Nov 2004 | B1 |
| 6829334 | Zirngibl et al. | Dec 2004 | B1 |
| 6834265 | Balasuriya | Dec 2004 | B2 |
| 6836537 | Zirngibl et al. | Dec 2004 | B1 |
| 6842767 | Partovi et al. | Jan 2005 | B1 |
| 6850603 | Eberle et al. | Feb 2005 | B1 |
| 6870830 | Schuster et al. | Mar 2005 | B1 |
| 6873952 | Bailey et al. | Mar 2005 | B1 |
| 6874084 | Dobner et al. | Mar 2005 | B1 |
| 6885737 | Gao et al. | Apr 2005 | B1 |
| 6888929 | Saylor et al. | May 2005 | B1 |
| 6895084 | Saylor et al. | May 2005 | B1 |
| 6898567 | Balasuriya | May 2005 | B2 |
| 6912581 | Johnson et al. | Jun 2005 | B2 |
| 6922411 | Taylor | Jul 2005 | B1 |
| 6931405 | El-Shimi et al. | Aug 2005 | B2 |
| 6937699 | Schuster et al. | Aug 2005 | B1 |
| 6940953 | Eberle et al. | Sep 2005 | B1 |
| 6941268 | Porter et al. | Sep 2005 | B2 |
| 6947417 | Laursen et al. | Sep 2005 | B2 |
| 6947988 | Saleh | Sep 2005 | B1 |
| 6961330 | Cattan et al. | Nov 2005 | B1 |
| 6964012 | Zirngibl et al. | Nov 2005 | B1 |
| 6970915 | Partovi et al. | Nov 2005 | B1 |
| 6977992 | Zirngibl et al. | Dec 2005 | B2 |
| 6985862 | Stroem et al. | Jan 2006 | B2 |
| 7003464 | Ferrans et al. | Feb 2006 | B2 |
| 7006606 | Cohen et al. | Feb 2006 | B1 |
| 7010586 | Allavarpu et al. | Mar 2006 | B1 |
| 7020685 | Chen et al. | Mar 2006 | B1 |
| 7039165 | Saylor et al. | May 2006 | B1 |
| 7062709 | Cheung | Jun 2006 | B2 |
| 7076037 | Gonen et al. | Jul 2006 | B1 |
| 7076428 | Anastasakos et al. | Jul 2006 | B2 |
| 7089310 | Ellerman et al. | Aug 2006 | B1 |
| 7103003 | Brueckheimer et al. | Sep 2006 | B2 |
| 7103171 | Annadata et al. | Sep 2006 | B1 |
| 7106844 | Holland | Sep 2006 | B1 |
| 7111163 | Haney | Sep 2006 | B1 |
| 7140004 | Kunins et al. | Nov 2006 | B1 |
| 7143039 | Stifelman et al. | Nov 2006 | B1 |
| 7197331 | Anastasakos et al. | Mar 2007 | B2 |
| 7197461 | Eberle et al. | Mar 2007 | B1 |
| 7197462 | Takagi et al. | Mar 2007 | B2 |
| 7197544 | Wang et al. | Mar 2007 | B2 |
| 7225232 | Elberse | May 2007 | B2 |
| 7227849 | Raesaenen | Jun 2007 | B1 |
| 7260208 | Cavalcanti | Aug 2007 | B2 |
| 7266181 | Zirngibl et al. | Sep 2007 | B1 |
| 7269557 | Bailey et al. | Sep 2007 | B1 |
| 7272212 | Eberle et al. | Sep 2007 | B2 |
| 7272564 | Phillips et al. | Sep 2007 | B2 |
| 7277851 | Henton | Oct 2007 | B1 |
| 7283515 | Fowler | Oct 2007 | B2 |
| 7286521 | Jackson et al. | Oct 2007 | B1 |
| 7287248 | Adeeb | Oct 2007 | B1 |
| 7289453 | Riedel et al. | Oct 2007 | B2 |
| 7296739 | Mo et al. | Nov 2007 | B1 |
| 7298732 | Cho | Nov 2007 | B2 |
| 7308085 | Weissman | Dec 2007 | B2 |
| 7308408 | Stifelman et al. | Dec 2007 | B1 |
| 7324633 | Gao et al. | Jan 2008 | B2 |
| 7324942 | Mahowald et al. | Jan 2008 | B1 |
| 7330463 | Bradd et al. | Feb 2008 | B1 |
| 7330890 | Partovi et al. | Feb 2008 | B1 |
| 7340040 | Saylor et al. | Mar 2008 | B1 |
| 7349714 | Lee et al. | Mar 2008 | B2 |
| 7369865 | Gabriel et al. | May 2008 | B2 |
| 7376223 | Taylor et al. | May 2008 | B2 |
| 7376586 | Partovi et al. | May 2008 | B1 |
| 7376740 | Porter et al. | May 2008 | B1 |
| 7412525 | Cafarella et al. | Aug 2008 | B2 |
| 7428302 | Zirngibl et al. | Sep 2008 | B2 |
| 7440898 | Eberle et al. | Oct 2008 | B1 |
| 7447299 | Partovi et al. | Nov 2008 | B1 |
| 7454459 | Kapoor et al. | Nov 2008 | B1 |
| 7457397 | Saylor et al. | Nov 2008 | B1 |
| 7486780 | Zirngibl et al. | Feb 2009 | B2 |
| 7496054 | Taylor | Feb 2009 | B2 |
| 7500249 | Kampe et al. | Mar 2009 | B2 |
| 7505951 | Thompson et al. | Mar 2009 | B2 |
| 7519359 | Chiarulli et al. | Apr 2009 | B2 |
| 7522711 | Stein et al. | Apr 2009 | B1 |
| 7536454 | Balasuriya | May 2009 | B2 |
| 7552054 | Stifelman et al. | Jun 2009 | B1 |
| 7571226 | Partovi et al. | Aug 2009 | B1 |
| 7613287 | Stifelman et al. | Nov 2009 | B1 |
| 7623648 | Oppenheim et al. | Nov 2009 | B1 |
| 7630900 | Strom | Dec 2009 | B1 |
| 7631310 | Henzinger | Dec 2009 | B1 |
| 7644000 | Strom | Jan 2010 | B1 |
| 7657433 | Chang | Feb 2010 | B1 |
| 7657434 | Thompson et al. | Feb 2010 | B2 |
| 7668157 | Weintraub et al. | Feb 2010 | B2 |
| 7672295 | Andhare et al. | Mar 2010 | B1 |
| 7675857 | Chesson | Mar 2010 | B1 |
| 7676221 | Roundtree et al. | Mar 2010 | B2 |
| 7715547 | Ibbotson et al. | May 2010 | B2 |
| 7779065 | Gupta et al. | Aug 2010 | B2 |
| 7882253 | Pardo-Castellote et al. | Feb 2011 | B2 |
| 7920866 | Bosch et al. | Apr 2011 | B2 |
| 7926099 | Chakravarty et al. | Apr 2011 | B1 |
| 7936867 | Hill et al. | May 2011 | B1 |
| 7962644 | Ezerzer et al. | Jun 2011 | B1 |
| 7979555 | Rothstein et al. | Jul 2011 | B2 |
| 8023425 | Raleigh | Sep 2011 | B2 |
| 8081958 | Soederstroem et al. | Dec 2011 | B2 |
| 8103725 | Gupta et al. | Jan 2012 | B2 |
| 8126128 | Hicks, III et al. | Feb 2012 | B1 |
| 8149716 | Ramanathan et al. | Apr 2012 | B2 |
| 8150918 | Edelman et al. | Apr 2012 | B1 |
| 8233611 | Zettner | Jul 2012 | B1 |
| 8243889 | Taylor et al. | Aug 2012 | B2 |
| 8266327 | Kumar et al. | Sep 2012 | B2 |
| 8295272 | Boni et al. | Oct 2012 | B2 |
| 8306021 | Lawson et al. | Nov 2012 | B2 |
| 8326805 | Arous et al. | Dec 2012 | B1 |
| 8346630 | McKeown | Jan 2013 | B1 |
| 8355394 | Taylor et al. | Jan 2013 | B2 |
| 8462670 | Chien et al. | Jun 2013 | B2 |
| 8509068 | Begall et al. | Aug 2013 | B2 |
| 8532686 | Schmidt et al. | Sep 2013 | B2 |
| 8542805 | Agranovsky et al. | Sep 2013 | B2 |
| 8611338 | Lawson et al. | Dec 2013 | B2 |
| 8649268 | Lawson et al. | Feb 2014 | B2 |
| 8675493 | Buddhikot et al. | Mar 2014 | B2 |
| 8755376 | Lawson et al. | Jun 2014 | B2 |
| 8837465 | Lawson et al. | Sep 2014 | B2 |
| 8838707 | Lawson et al. | Sep 2014 | B2 |
| 20010043684 | Guedalia et al. | Nov 2001 | A1 |
| 20020006124 | Jimenez et al. | Jan 2002 | A1 |
| 20020006125 | Josse et al. | Jan 2002 | A1 |
| 20020006193 | Rodenbusch et al. | Jan 2002 | A1 |
| 20020077833 | Arons et al. | Jun 2002 | A1 |
| 20020126813 | Partovi et al. | Sep 2002 | A1 |
| 20020136391 | Armstrong | Sep 2002 | A1 |
| 20030006137 | Wei et al. | Jan 2003 | A1 |
| 20030018830 | Chen et al. | Jan 2003 | A1 |
| 20030026426 | Wright et al. | Feb 2003 | A1 |
| 20030046366 | Pardikar et al. | Mar 2003 | A1 |
| 20030051037 | Sundaram et al. | Mar 2003 | A1 |
| 20030058884 | Kallner et al. | Mar 2003 | A1 |
| 20030059020 | Meyerson et al. | Mar 2003 | A1 |
| 20030060188 | Gidron et al. | Mar 2003 | A1 |
| 20030061317 | Brown et al. | Mar 2003 | A1 |
| 20030061404 | Atwal et al. | Mar 2003 | A1 |
| 20030088421 | Maes et al. | May 2003 | A1 |
| 20030103620 | Brown et al. | Jun 2003 | A1 |
| 20030123640 | Roelle et al. | Jul 2003 | A1 |
| 20030195990 | Greenblat | Oct 2003 | A1 |
| 20030196076 | Zabarski et al. | Oct 2003 | A1 |
| 20030211842 | Kempf et al. | Nov 2003 | A1 |
| 20030231647 | Petrovykh | Dec 2003 | A1 |
| 20040044953 | Watkins et al. | Mar 2004 | A1 |
| 20040052349 | Creamer et al. | Mar 2004 | A1 |
| 20040071275 | Bowater et al. | Apr 2004 | A1 |
| 20040101122 | Da Palma et al. | May 2004 | A1 |
| 20040165569 | Sweatman et al. | Aug 2004 | A1 |
| 20040172482 | Weissman et al. | Sep 2004 | A1 |
| 20040213400 | Golitsin et al. | Oct 2004 | A1 |
| 20040218748 | Fisher | Nov 2004 | A1 |
| 20050010483 | Ling | Jan 2005 | A1 |
| 20050025303 | Hostetler | Feb 2005 | A1 |
| 20050038772 | Colrain | Feb 2005 | A1 |
| 20050043952 | Sharma et al. | Feb 2005 | A1 |
| 20050047579 | Salame | Mar 2005 | A1 |
| 20050128961 | Miloslavsky et al. | Jun 2005 | A1 |
| 20050135578 | Ress et al. | Jun 2005 | A1 |
| 20050147088 | Bao et al. | Jul 2005 | A1 |
| 20050177635 | Schmidt et al. | Aug 2005 | A1 |
| 20050238153 | Chevalier | Oct 2005 | A1 |
| 20050240659 | Taylor | Oct 2005 | A1 |
| 20050243977 | Creamer et al. | Nov 2005 | A1 |
| 20050246176 | Creamer et al. | Nov 2005 | A1 |
| 20060008073 | Yoshizawa et al. | Jan 2006 | A1 |
| 20060015467 | Morken et al. | Jan 2006 | A1 |
| 20060047666 | Bedi et al. | Mar 2006 | A1 |
| 20060067506 | Flockhart et al. | Mar 2006 | A1 |
| 20060129638 | Deakin | Jun 2006 | A1 |
| 20060143007 | Koh et al. | Jun 2006 | A1 |
| 20060168334 | Potti et al. | Jul 2006 | A1 |
| 20060203979 | Jennings | Sep 2006 | A1 |
| 20060209695 | Archer et al. | Sep 2006 | A1 |
| 20060212865 | Vincent et al. | Sep 2006 | A1 |
| 20060215824 | Mitby et al. | Sep 2006 | A1 |
| 20060217823 | Hussey | Sep 2006 | A1 |
| 20060217978 | Mitby et al. | Sep 2006 | A1 |
| 20060256816 | Yarlagadda et al. | Nov 2006 | A1 |
| 20060262915 | Marascio et al. | Nov 2006 | A1 |
| 20060285489 | Francisco et al. | Dec 2006 | A1 |
| 20070002744 | Mewhinney et al. | Jan 2007 | A1 |
| 20070036143 | Alt et al. | Feb 2007 | A1 |
| 20070050306 | Mcqueen | Mar 2007 | A1 |
| 20070070906 | Thakur | Mar 2007 | A1 |
| 20070070980 | Phelps et al. | Mar 2007 | A1 |
| 20070071223 | Lee et al. | Mar 2007 | A1 |
| 20070074174 | Thornton | Mar 2007 | A1 |
| 20070121651 | Casey et al. | May 2007 | A1 |
| 20070127691 | Lert | Jun 2007 | A1 |
| 20070127703 | Siminoff | Jun 2007 | A1 |
| 20070130260 | Weintraub et al. | Jun 2007 | A1 |
| 20070133771 | Stifelman et al. | Jun 2007 | A1 |
| 20070153711 | Dykas et al. | Jul 2007 | A1 |
| 20070167170 | Fitchett et al. | Jul 2007 | A1 |
| 20070192629 | Saito | Aug 2007 | A1 |
| 20070208862 | Fox et al. | Sep 2007 | A1 |
| 20070242626 | Altberg et al. | Oct 2007 | A1 |
| 20070265073 | Novi et al. | Nov 2007 | A1 |
| 20070286180 | Marquette et al. | Dec 2007 | A1 |
| 20070291905 | Halliday et al. | Dec 2007 | A1 |
| 20070295803 | Levine et al. | Dec 2007 | A1 |
| 20080025320 | Bangalore et al. | Jan 2008 | A1 |
| 20080037715 | Prozeniuk et al. | Feb 2008 | A1 |
| 20080040484 | Yardley | Feb 2008 | A1 |
| 20080052395 | Wright et al. | Feb 2008 | A1 |
| 20080091843 | Kulkarni | Apr 2008 | A1 |
| 20080104348 | Kabzinski et al. | May 2008 | A1 |
| 20080134049 | Gupta et al. | Jun 2008 | A1 |
| 20080146268 | Gandhi et al. | Jun 2008 | A1 |
| 20080152101 | Griggs | Jun 2008 | A1 |
| 20080154601 | Stifelman et al. | Jun 2008 | A1 |
| 20080155029 | Helbling et al. | Jun 2008 | A1 |
| 20080162482 | Ahern et al. | Jul 2008 | A1 |
| 20080165708 | Moore et al. | Jul 2008 | A1 |
| 20080177883 | Hanai et al. | Jul 2008 | A1 |
| 20080209050 | Li | Aug 2008 | A1 |
| 20080222656 | Lyman | Sep 2008 | A1 |
| 20080232574 | Baluja et al. | Sep 2008 | A1 |
| 20080235230 | Maes | Sep 2008 | A1 |
| 20080256224 | Kaji et al. | Oct 2008 | A1 |
| 20080275741 | Loeffen | Nov 2008 | A1 |
| 20080313318 | Vermeulen et al. | Dec 2008 | A1 |
| 20080317222 | Griggs et al. | Dec 2008 | A1 |
| 20090052437 | Taylor et al. | Feb 2009 | A1 |
| 20090052641 | Taylor et al. | Feb 2009 | A1 |
| 20090074159 | Goldfarb et al. | Mar 2009 | A1 |
| 20090075684 | Cheng et al. | Mar 2009 | A1 |
| 20090083155 | Tudor et al. | Mar 2009 | A1 |
| 20090089165 | Sweeney | Apr 2009 | A1 |
| 20090089699 | Saha et al. | Apr 2009 | A1 |
| 20090093250 | Jackson et al. | Apr 2009 | A1 |
| 20090125608 | Werth et al. | May 2009 | A1 |
| 20090129573 | Gavan et al. | May 2009 | A1 |
| 20090136011 | Goel | May 2009 | A1 |
| 20090171659 | Pearce et al. | Jul 2009 | A1 |
| 20090171669 | Engelsma et al. | Jul 2009 | A1 |
| 20090171752 | Galvin et al. | Jul 2009 | A1 |
| 20090217293 | Wolber et al. | Aug 2009 | A1 |
| 20090220057 | Waters | Sep 2009 | A1 |
| 20090221310 | Chen et al. | Sep 2009 | A1 |
| 20090222341 | Belwadi et al. | Sep 2009 | A1 |
| 20090225748 | Taylor | Sep 2009 | A1 |
| 20090232289 | Drucker et al. | Sep 2009 | A1 |
| 20090235349 | Lai et al. | Sep 2009 | A1 |
| 20090252159 | Lawson et al. | Oct 2009 | A1 |
| 20090288165 | Qiu et al. | Nov 2009 | A1 |
| 20090316687 | Kruppa | Dec 2009 | A1 |
| 20100037204 | Lin et al. | Feb 2010 | A1 |
| 20100070424 | Monk | Mar 2010 | A1 |
| 20100082513 | Liu | Apr 2010 | A1 |
| 20100087215 | Gu et al. | Apr 2010 | A1 |
| 20100088187 | Courtney et al. | Apr 2010 | A1 |
| 20100088698 | Krishnamurthy | Apr 2010 | A1 |
| 20100115041 | Hawkins et al. | May 2010 | A1 |
| 20100142516 | Lawson et al. | Jun 2010 | A1 |
| 20100150139 | Lawson et al. | Jun 2010 | A1 |
| 20100167689 | Sepehri-Nik et al. | Jul 2010 | A1 |
| 20100188979 | Thubert et al. | Jul 2010 | A1 |
| 20100191915 | Spencer | Jul 2010 | A1 |
| 20100208881 | Kawamura | Aug 2010 | A1 |
| 20100217837 | Ansari et al. | Aug 2010 | A1 |
| 20100217982 | Brown et al. | Aug 2010 | A1 |
| 20100232594 | Lawson et al. | Sep 2010 | A1 |
| 20100235539 | Carter et al. | Sep 2010 | A1 |
| 20100251329 | Wei | Sep 2010 | A1 |
| 20100251340 | Martin et al. | Sep 2010 | A1 |
| 20100281108 | Cohen | Nov 2010 | A1 |
| 20110029882 | Jaisinghani | Feb 2011 | A1 |
| 20110053555 | Cai et al. | Mar 2011 | A1 |
| 20110078278 | Cui et al. | Mar 2011 | A1 |
| 20110081008 | Lawson et al. | Apr 2011 | A1 |
| 20110083179 | Lawson et al. | Apr 2011 | A1 |
| 20110096673 | Stevenson et al. | Apr 2011 | A1 |
| 20110110366 | Moore et al. | May 2011 | A1 |
| 20110170505 | Rajasekar et al. | Jul 2011 | A1 |
| 20110176537 | Lawson et al. | Jul 2011 | A1 |
| 20110211679 | Mezhibovsky et al. | Sep 2011 | A1 |
| 20110255675 | Jasper et al. | Oct 2011 | A1 |
| 20110265172 | Sharma et al. | Oct 2011 | A1 |
| 20110267985 | Wilkinson et al. | Nov 2011 | A1 |
| 20110276892 | Jensen-Horne et al. | Nov 2011 | A1 |
| 20110276951 | Jain | Nov 2011 | A1 |
| 20110280390 | Lawson et al. | Nov 2011 | A1 |
| 20110283259 | Lawson et al. | Nov 2011 | A1 |
| 20110289126 | Aikas et al. | Nov 2011 | A1 |
| 20110299672 | Chiu et al. | Dec 2011 | A1 |
| 20110320449 | Gudlavenkatasiva | Dec 2011 | A1 |
| 20110320550 | Lawson et al. | Dec 2011 | A1 |
| 20120017222 | May | Jan 2012 | A1 |
| 20120036574 | Heithcock et al. | Feb 2012 | A1 |
| 20120039202 | Song | Feb 2012 | A1 |
| 20120114112 | Rauschenberger et al. | May 2012 | A1 |
| 20120149404 | Beattie et al. | Jun 2012 | A1 |
| 20120173610 | Bleau et al. | Jul 2012 | A1 |
| 20120198004 | Watte | Aug 2012 | A1 |
| 20120201238 | Lawson et al. | Aug 2012 | A1 |
| 20120226579 | Ha et al. | Sep 2012 | A1 |
| 20120239757 | Firstenberg et al. | Sep 2012 | A1 |
| 20120281536 | Gell et al. | Nov 2012 | A1 |
| 20120288082 | Segall | Nov 2012 | A1 |
| 20120290706 | Lin et al. | Nov 2012 | A1 |
| 20120304245 | Lawson et al. | Nov 2012 | A1 |
| 20120316809 | Egolf et al. | Dec 2012 | A1 |
| 20130058262 | Parreira | Mar 2013 | A1 |
| 20130156024 | Burg | Jun 2013 | A1 |
| 20130244632 | Spence et al. | Sep 2013 | A1 |
| 20140064467 | Lawson et al. | Mar 2014 | A1 |
| 20140106704 | Cooke et al. | Apr 2014 | A1 |
| 20140153565 | Lawson et al. | Jun 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1684587 | Mar 1971 | DE |
| 0282126 | Sep 1988 | EP |
| 1464418 | Oct 2004 | EP |
| 1770586 | Apr 2007 | EP |
| 2134107 | Sep 1999 | ES |
| 10294788 | Apr 1998 | JP |
| 2004166000 | Jun 2004 | JP |
| 2004220118 | Aug 2004 | JP |
| 2006319914 | Nov 2006 | JP |
| 9732448 | Sep 1997 | WO |
| 02087804 | Nov 2002 | WO |
| 2006037492 | Apr 2006 | WO |
| 2009018489 | Feb 2009 | WO |
| 2009124223 | Oct 2009 | WO |
| 2010037064 | Apr 2010 | WO |
| 2010040010 | Apr 2010 | WO |
| 2010101935 | Sep 2010 | WO |
| 2011091085 | Jul 2011 | WO |
| Entry |
|---|
| Complaint for Patent Infringement, Telinit Technologies, LLC v. Twilio Inc., dated Oct. 12, 2012. |
| Number | Date | Country | |
|---|---|---|---|
| 20140269333 A1 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61791800 | Mar 2013 | US |