Techniques and system for optimization driven by dynamic resilience

Patent metadata

Field	Value
Publication number	US-11237930-B2
Application number	US-202016931618-A
Country	US
Kind code	B2
Filing date	Jul 17, 2020
Priority date	Nov 27, 2018
Publication date	Feb 1, 2022
Grant date	Feb 1, 2022

Abstract

Disclosed are hardware and techniques for testing computer processes in a network system by simulating computer process faults and identifying risk associated with correcting the simulated fault and identifying computer processes that may depend on the corrected computer process. The interdependent computer processes in a network may be determined by evaluating a risk matrix having a risk score and non-functional requirement score. An analysis of the risk score and non-functional requirement score accounts for interdependencies between computer processes and identified corrective actions that may be used to determine an optimal network environment. The optimal network environment may be updated dynamically based on changing computer process interdependencies and the determined risk and robustness scores.

First claim

What is claimed is:

1. A method, comprising:
monitoring, by a monitoring component, a simulation instance of a network environment;
generating a pre-breakage snapshot of a process health of a computer-implemented process, wherein the pre-breakage snapshot includes:
a non-functional requirement score indicating the process health of the computer-implemented process of a plurality of computer-implemented processes, and
a risk score indicating a threshold between automated correction and manual correction of a degrading system;

generating, by a simulation processing component executing the simulation instance, a simulated break event flag indicating a process volatility in a test computer-implemented process from the computer-implemented processes;
generating, by the monitoring component in response to the simulated break event flag generated by the simulation processing component process, a simulation result snapshot of process health of the test computer-implemented, wherein the simulation result snapshot includes an updated non-functional requirement score and an updated risk score for the test computer-implemented process;
identifying, based on the simulated break event flag, a runbook in a library of runbooks;
simulating implementation of a final response strategy selected from the runbook in the simulation instance of the network environment to cure the indicated process volatility of the test computer-implemented process;
generating, by the monitoring component in response to the simulated implementation of the final response strategy, a cure result snapshot of process health of each of the plurality of computer-implemented processes;
evaluating the pre-breakage snapshot, the simulation result snapshot, and the cure result snapshot with reference to one another; and
based on results of the evaluation, identifying a network environment architecture as an optimal network architecture that cures the process volatility of the test computer-implemented process.

2. The method of claim 1 , wherein the non-functional requirement score is a score related to one or more non-functional requirements of: cost optimization, operational excellence, process stability, process security, threat indicator, process fragility, process usability, process performance efficiency, process response time, or reliability resilience.

3. The method of claim 1 , wherein generating the pre-breakage snapshot comprises:
receiving, from the monitoring component coupled to the computer-implemented process, a list of break event flags for the computer-implemented process;
identifying respective break event symptoms for each break event flag in the list of break event flags;
generating, for each identified respective break event symptom, a computing environment indicator, a code environment indicator, and a response strategy corresponding to the respective break event symptom;
generating, by a rules engine, a non-functional requirement score for the computer-implemented process, wherein the generated non-functional requirement score for the computer-implemented process is based on the identified respective break event symptom corresponding to the computer-implemented process and the response strategy corresponding to the respective break event symptom of the computer-implemented process;
generating, by the rules engine, a risk score for the computer-implemented process based on the identified respective break event symptom of the computer-implemented process, and the response strategy corresponding to the identified break event symptom; and
storing the generated non-functional requirement and risk scores of the computer-implemented process with a timestamp of when the pre-breakage snapshot was taken in a data structure.

4. The method of claim 1 , wherein generating the simulation result snapshot after application of final response comprises:
in response to application of the process volatility indicated by the generated simulation break event flag to the simulation instance of the network environment, generating based on inputs received from the monitoring component a list of break event flags for the computer-implemented process;
identifying respective break event symptoms for the break event flags in the list of break event flags;
determining, for each identified respective break event symptom, a computing environment indicator corresponding to the identified respective break event symptom, a code environment indicator corresponding to the identified respective break event symptom, and a final response strategy corresponding to the identified respective break event symptom;
storing, for each identified respective break event symptom, the identified respective break event symptom, the determined computing environment indicator, the determined code environment indicator and determined final response strategy into a data structure;
generating, by the rules engine, the updated non-functional requirement score for the computer-implemented process based on the identified respective break event symptom, the determined computing environment indicator, the determined code environment indicator, and the final response strategy corresponding to the identified respective break event symptom of the computer-implemented process;
generating, by the rules engine, the updated risk score for the computer-implemented process based on the identified break event symptom and the final response strategy corresponding to the break event symptom of the computer-implemented process; and
storing the updated non-functional requirement score and the updated risk score of the computer-implemented process with a timestamp indicating when the simulation result snapshot was taken in the data structure.

5. The method of claim 1 , further comprising:
in response to simulating implementation of the final response in the simulation instance of the network environment, generating a modified non-functional requirement score of the updated non-functional requirement score and a modified risk score of the updated risk score for the computer-implemented process; and
storing the modified non-functional requirement score and the modified risk score in the cure result snapshot.

6. The method of claim 1 , wherein evaluating the pre-breakage snapshot, the simulation result snapshot, and the cure result snapshot with reference to one another; comprises:
identifying score changes of non-functional requirement scores and risk scores between the pre-breakage snapshot and the simulation result snapshot, and changes in non-functional requirement scores and risk scores between the simulation result snapshot and the cure result snapshot for the computer-implemented process;
recognizing, by evaluating the identified score changes by the rules engine, interdependencies between the computer-implemented process and other computer processes in a plurality of computer-implemented processes; and
in response to the recognized interdependencies, identifying an operating state of each of the other respective computer-implemented processes in the plurality of computer-implemented processes that provides a below threshold risk score for the computer-implemented process and an above threshold-non-functional requirement score for each of the other respective computer-implemented processes.

7. The method of claim 1 , wherein:
the simulation break event flag is generated by the simulation component based on a risk assessment value assigned to the process volatility, wherein the risk assessment value has a range from a value indicating the process volatility has a high likelihood of causing a process break of the simulated computer-implemented process to a value indicating the process volatility has a low likelihood of causing a process break of the

Assignees

• Capital One Services Llc

Inventors

• Gudka Bhavik
• Barnum Eric

Classifications

• H04L41/145 Primary

  involving simulating, designing, planning or modelling of a network · CPC title

• G06F2201/805

  Real-time · CPC title

• H04L41/0631

  using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis · CPC title

• G06F11/0793

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title

• G06F11/261 Primary

  by simulating additional hardware, e.g. fault simulation · CPC title