# US 8,787,541 B1 · System and method for quality auto-blending in call routing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,787,541 B1 - Document ID: US8787541B1 - Status: Granted - Kind: B1 - Application number: 13/770,103 - Filed: 2013-02-19 - Granted: 2014-07-22 - Earliest claimed: 2013-02-19 - Assignees: Tata Communications (America) Inc. - Applicants: Tata Communications (America), Inc. - Inventors: Aakratee Saini; Avanish Pande; Joseph F. Conrey; Roy Ho - Web page: https://patentgrep.com/patent/US8787541B1 ## CPC - H04M 3/367: {Traffic or load control} - H04M 7/128: {Details of addressing, directories or routing tables} - H04M 7/1285: {Details of finding and selecting a gateway for a particular call} - H04Q 3/66: Traffic distributors - H04M 15/8044: {Least cost routing} - H04Q 2213/13141: Hunting for free outlet, circuit or channel - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) - H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W) ## Abstract A system and method blend particular quality considerations into the process of expanding the route choices in a route table, such that more calls can be successfully routed while maximizing certain objectives. The quality considerations drive how additional routes are chosen for the route table and how call volumes are allocated to the chosen routes so that overall profitability can be maximized within the governing constraints of quality targets, route quality, predicted traffic, and route capacity. ## Claims ### Claim 1 A method comprising: generating, by a telecommunications system, a route table for a predicted traffic, wherein the generating is based at least in part on: (i) a first threshold value of a first quality metric for the predicted traffic, wherein the first quality metric is based on a ratio of answered calls to call seizures, and (ii) the predicted traffic; wherein at least some of the predicted traffic is allocated in the route table to one or more routes chosen from a plurality of routes that are candidates for carrying the predicted traffic; and routing, by the telecommunications system, a plurality of calls according to the route table. ### Claim 2 (depends on 1) The method of claim 1 wherein the generating is further based on (iii) a second threshold value of a second quality metric for the predicted traffic, wherein the second quality metric measures call duration per answered call. ### Claim 3 (depends on 1) The method of claim 1 wherein the generating is further based on (iv) a capacity characteristic for each of the plurality of candidate routes. ### Claim 4 (depends on 1) The method of claim 1 wherein the route table maximizes a profitability metric for the predicted traffic. ### Claim 5 (depends on 1) The method of claim 1 wherein the route table maximizes a profitability metric for the predicted traffic, and further wherein the profitability metric is a total margin based on the number of allocated calls according to the route table. ### Claim 6 (depends on 1) The method of claim 1 wherein the route table maximizes a profitability metric for the predicted traffic, and further wherein at least one route in the route table is characterized by a higher cost than a minimum cost among the plurality of candidate routes. ### Claim 7 (depends on 1) The method of claim 1 wherein the routing of the plurality of calls according to the route table comprises routing based on: (A) the first quality metric, and (B) a second quality metric that measures call duration per answered call. ### Claim 8 A system comprising: a route table generator that is configured to generate a route table for a predicted traffic based at least in part on: (i) a first threshold value of a first quality metric for the predicted traffic, wherein the first quality metric is based on a ratio of answered calls to call seizures, and (ii) the predicted traffic; and wherein at least some of the predicted traffic is allocated in the route table to one or more routes chosen from a plurality of routes that are candidates for carrying the predicted traffic; and a route server that is configured to route a plurality of calls according to the route table. ### Claim 9 (depends on 8) The system of claim 8 wherein the route table generator is further configured to generate the route table based on (iii) a second threshold value of a second quality metric for the predicted traffic, wherein the second quality metric measures call duration per answered call. ### Claim 10 (depends on 8) The system of claim 8 wherein the route table generator is further configured to generate the route table based on (iv) a capacity characteristic for each of the plurality of candidate routes. ### Claim 11 (depends on 8) The system of claim 8 wherein the route table generator is further configured to generate the route table such that the route table maximizes a profitability metric for the predicted traffic. ### Claim 12 (depends on 8) The system of claim 8 wherein the route table generator is further configured to generate the route table such that the route table maximizes a profitability metric for the predicted traffic, and further wherein the profitability metric is a total margin based on the number of allocated calls according to the route table. ### Claim 13 (depends on 8) The system of claim 8 wherein the route table generator is further configured to generate the route table such that the route table maximizes a profitability metric for the predicted traffic, and further wherein at least one route in the route table is characterized by a higher cost than a minimum cost among the plurality of candidate routes. ### Claim 14 (depends on 8) The system of claim 8 wherein the route server being configured to route a plurality of calls according to the route table is further based on: (A) the first quality metric, and (B) a second quality metric that measures call duration per answered call. ### Claim 15 A method comprising: receiving, by a route-table generator, a predicted traffic; generating, by the route-table generator, a first route table for the predicted traffic, wherein the generating is based at least in part on: (i) a first threshold value of a first quality metric for the predicted traffic, wherein the first quality metric is based on a ratio of answered calls to call seizures, and (ii) a capacity characteristic for each of a plurality of routes that are candidates for carrying the predicted traffic, and (iii) the predicted traffic; and wherein at least some of the predicted traffic is allocated in the route table to one or more routes chosen from the plurality of candidate routes. ### Claim 16 (depends on 15) The method of claim 15 wherein the first route table maximizes a profitability metric for the predicted traffic. ### Claim 17 (depends on 15) The method of claim 15 further comprising: for each route in the first route table, computing, by the route-table generator, a predicted value of the first quality metric based on the first route table; for each route in the first route table, computing, by the route-table generator, a predicted value of a second quality metric based on the first route table, wherein the second quality metric measures call duration per answered call; when (A) the predicted value of the first quality metric for each route in the first route table passes the first threshold value, and (B) the predicted value of the second quality metric for each route in the first route table passes a second threshold value for the second quality metric, and (C) there is sufficient capacity among the routes in the first route table to carry the predicted traffic, routing, by a route server, a plurality of calls according to the first route table. ### Claim 18 (depends on 15) The method of claim 15 further comprising: for each route in the first route table, computing, by the route-table generator, a predicted value of a second quality metric based on the first route table, wherein the second quality metric measures call duration per answered call; when a route from the first route table has a predicted value for the second quality metric that passes a second threshold for the second quality metric, designating the route a retained route; when a route from the first route table has a predicted value for the second quality metric that does not pass the second threshold, generating a second route table for the predicted traffic based at least in part on: (i) a third threshold value of the first quality metric that is lower than the first threshold value, and (ii) a fourth threshold value of the second quality metric that is lower than the second threshold value; and wherein the second route table comprises (A) the retained routes from the first route table, and (B) at least one other route that has a predicted value of the second quality metric that passes the fourth threshold value and does not pass the second threshold value; and routing, by a route server, a plurality of calls according to the second route table. ### Claim 19 (depends on 15) The method of claim 15 further comprising: for each route in the first route table, computing, by the route-table generator, a predicted value of a second quality metric based on the first route table, wherein the second quality metric measures call duration per answered call; when a route from the first route table has a predicted value for the second quality metric that passes a second threshold for the second quality metric, designating the route a retained route; when the retained routes lack sufficient capacity to carry the predicted traffic, generating a second route table for the predicted traffic based at least in part on: (i) a third threshold value of the first quality metric that is lower than the first threshold value, and (ii) a fourth threshold value of the second quality metric that is lower than the second threshold value; and wherein the second route table comprises (A) the retained routes from the first route table, and (B) at least one other route that is not a retained route; and routing, by a route server, a plurality of calls according to the second route table. ### Claim 20 (depends on 15) The method of claim 15 further comprising: when a route from the first route table has a predicted value for a second quality metric that does not pass a second threshold value, wherein the second quality metric measures call duration per answered call, generating, by the route table generator, a second route table that is based on the first route table and is further based on a relaxed threshold for at least one of (A) the first quality metric and (B) the second quality metric; and routing, by a route server, a plurality of calls according to the second route table, wherein the routing is based on (A) the first quality metric and (B) the second quality metric.