# US 12,010,017 B2 · Routing online application traffic based on path fate sharing metrics > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,010,017 B2 - Document ID: US12010017B2 - Status: Granted - Kind: B2 - Application number: 17/533,649 - Filed: 2021-11-23 - Published: 2023-06-01 - Granted: 2024-06-11 - Earliest claimed: 2021-11-23 - Assignees: Cisco Technology, Inc. - Applicants: Cisco Technology, Inc. - Inventors: Jean-Philippe Vasseur; Eduard Schornig; Vinay Kumar Kolar; Grégory Mermoud - Web page: https://patentgrep.com/patent/US12010017B2 ## CPC - H04L 45/70: {Routing based on monitoring results} - H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] - H04L 41/5019: Ensuring fulfilment of SLA - H04L 43/045: for graphical visualisation of monitoring data - H04L 43/16: Threshold monitoring - H04L 45/08: {Learning-based routing, e.g. using neural networks or artificial intelligence} - H04L 45/121: by minimising delays - H04L 45/123: {Evaluation of link metrics (techniques for monitoring network metrics H04L43/08)} - H04L 45/124: {using a combination of metrics} - H04L 45/22: {Alternate routing} - H04L 45/24: Multipath - H04L 47/125: by balancing the load, e.g. traffic engineering - H04L 41/142: using statistical or mathematical methods - H04L 41/147: for predicting network behaviour - H04L 41/16: using machine learning or artificial intelligence - H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract In one embodiment, a device identifies a plurality of paths between a pair of network addresses, wherein one of the pair of network addresses is associated with an online application. The device obtains telemetry data from the plurality of paths for the online application. The device computes, based on the telemetry data, fate sharing metrics for the plurality of paths. The device controls routing of application traffic between the pair of network addresses, based on the fate sharing metrics for the plurality of paths. ## Claims ### Claim 1 A method comprising: identifying, by a device, a plurality of paths between a pair of network addresses, wherein one of the pair of network addresses is associated with an online application; obtaining, by the device, telemetry data from the plurality of paths for the online application; computing, by the device and based on the telemetry data, fate sharing metrics for the plurality of paths, wherein the fate sharing metrics indicate how likely the plurality of paths are to provide acceptable or unacceptable application experience during any given time period; and controlling, by the device, routing of application traffic for the online application between the pair of network addresses, based on the fate sharing metrics for the plurality of paths. ### Claim 2 (depends on 1) The method as in claim 1, wherein the telemetry data is indicative of one or more of: latency, jitter, or loss. ### Claim 3 (depends on 1) The method as in claim 1, further comprising: providing, by the device, an indication of the fate sharing metrics for display. ### Claim 4 (depends on 3) The method as in claim 3, wherein the device provides the indication when one or more of the fate sharing metrics crosses a threshold. ### Claim 5 (depends on 1) The method as in claim 1, wherein controlling routing of application traffic for the online application between the pair of network addresses comprises: causing the application traffic to be load balanced over two or more of the plurality of paths, based on those paths having fate sharing metrics indicating low or no fate sharing among them. ### Claim 6 (depends on 1) The method as in claim 1, wherein computing the fate sharing metrics comprises: computing correlations between the telemetry data from the plurality of paths for the online application. ### Claim 7 (depends on 1) The method as in claim 1, wherein the fate sharing metrics are based on service level agreement violations indicated by the telemetry data. ### Claim 8 (depends on 1) The method as in claim 1, wherein the fate sharing metrics are based on service level agreement violations predicted by a machine learning model from the telemetry data. ### Claim 9 (depends on 1) The method as in claim 1, wherein the device identifies the plurality of paths based in part on an amount of the application traffic for the online application that they convey. ### Claim 10 (depends on 1) The method as in claim 1, wherein the online application is a software-as-a-service (SaaS) application. ### Claim 11 An apparatus, comprising: one or more network interfaces; a processor coupled to the one or more network interfaces and configured to execute one or more processes; and a memory configured to store a process that is executable by the processor, the process when executed configured to: identify a plurality of paths between a pair of network addresses, wherein one of the pair of network addresses is associated with an online application; obtain telemetry data from the plurality of paths for the online application; compute, based on the telemetry data, fate sharing metrics for the plurality of paths, wherein the fate sharing metrics indicate how likely the plurality of paths are to provide acceptable or unacceptable application experience during any given time period; and control routing of application traffic for the online application between the pair of network addresses, based on the fate sharing metrics for the plurality of paths. ### Claim 12 (depends on 11) The apparatus as in claim 11, wherein the telemetry data is indicative of one or more of: latency, jitter, or loss. ### Claim 13 (depends on 11) The apparatus as in claim 11, wherein the process when executed is further configured to: provide an indication of the fate sharing metrics for display. ### Claim 14 (depends on 13) The apparatus as in claim 13, wherein the apparatus provides the indication when one or more of the fate sharing metrics crosses a threshold. ### Claim 15 (depends on 11) The apparatus as in claim 11, wherein the apparatus controls routing of application traffic for the online application between the pair of network addresses by: causing the application traffic to be load balanced over two or more of the plurality of paths, based on those paths having fate sharing metrics indicating low or no fate sharing among them. ### Claim 16 (depends on 11) The apparatus as in claim 11, wherein the apparatus computes the fate sharing metrics by: computing correlations between the telemetry data from the plurality of paths for the online application. ### Claim 17 (depends on 11) The apparatus as in claim 11, wherein the fate sharing metrics are based on service level agreement violations indicated by the telemetry data. ### Claim 18 (depends on 11) The apparatus as in claim 11, wherein the fate sharing metrics are based on service level agreement violations predicted by a machine learning model from the telemetry data. ### Claim 19 (depends on 11) The apparatus as in claim 11, wherein the apparatus identifies the plurality of paths based in part on an amount of the application traffic for the online application that they convey. ### Claim 20 A tangible, non-transitory, computer-readable medium storing program instructions that cause a device to execute a process comprising: identifying, by the device, a plurality of paths between a pair of network addresses, wherein one of the pair of network addresses is associated with an online application; obtaining, by the device, telemetry data from the plurality of paths for the online application; computing, by the device and based on the telemetry data, fate sharing metrics for the plurality of paths, wherein the fate sharing metrics indicate how likely the plurality of paths are to provide acceptable or unacceptable application experience during any given time period; and controlling, by the device, routing of application traffic for the online application between the pair of network addresses, based on the fate sharing metrics for the plurality of paths.