# US 12,223,314 B2 · Software change analysis and automated remediation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,223,314 B2 - Document ID: US12223314B2 - Status: Granted - Kind: B2 - Application number: 18/146,031 - Filed: 2022-12-23 - Published: 2023-06-29 - Granted: 2025-02-11 - Earliest claimed: 2021-01-14 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Krystan R. Franzen; Mohamed Seck - Web page: https://patentgrep.com/patent/US12223314B2 ## CPC - G06F 8/70: Software maintenance or management - G06F 3/04847: Interaction techniques to control parameter settings, e.g. interaction with sliders or dials - G06F 8/65: Updates (security arrangements therefor G06F21/57) - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F 9/541: {via adapters, e.g. between incompatible applications} - G06F 11/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)} - G06N 5/04: Inference or reasoning models - G06N 20/00: Machine learning - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract In some implementations, a system may receive dependency indicators associated with a plurality of cloud-based applications and receive change indicators associated with changes to one or more first applications of the plurality of cloud-based applications. The system may receive an indicator associated with an incident ticket based on a problem with a second application of the plurality of cloud-based applications. The device may determine at least one of the change indicators associated with the incident ticket based on dependencies between the one or more first applications and the second application and based on a difference between a time associated with the incident ticket and a time associated with the at least one of the change indicators. The system may, based on determining the at least one of the change indicators, transmit a command to rollback at least one of the changes or to rollforward at least one change. ## Claims ### Claim 1 A system comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: obtain an indicator associated with an incident ticket based on a problem with a first application of a plurality of applications; determine, based on one or more dependency indicators associated with the plurality of applications, at least one of a plurality of change indicators, associated with changes to one or more second applications of the plurality of applications, is associated with the incident ticket, wherein the determination that the at least one of the plurality of change indicators is associated with the incident ticket is based on differences in a time associated with the incident ticket and times associated with the plurality of change indicators; and transmit a command to rollback at least one of the changes associated with the at least one of the plurality of change indicators or to rollforward at least one change related to the first application or the one or more second applications, based on determining that the at least one of the plurality of change indicators is associated with the incident ticket. ### Claim 2 (depends on 1) The system of claim 1, wherein the determination that the at least one of the plurality of change indicators is associated with the incident ticket is additionally based on: dependencies between the first application and the one or more second applications. ### Claim 3 (depends on 1) The system of claim 1, wherein the indicator associated with the incident ticket comprises a data structure that indicates information about the problem. ### Claim 4 (depends on 1) The system of claim 1, wherein an identifier of the first application comprises one or more of: a process identifier, a thread identifier, or an alphanumeric name of the first application. ### Claim 5 (depends on 1) The system of claim 1, wherein the indicator associated with the incident ticket is obtained from a server that accepts reports from one or more users of a cloud-based environment associated with the plurality of applications. ### Claim 6 (depends on 1) The system of claim 1, wherein the one or more processors, to determine the at least one of the plurality of change indicators, are configured to: determine the at least one of the plurality of change indicators based on layers of dependency between the first application and the one or more second applications. ### Claim 7 (depends on 1) The system of claim 1, wherein the one or more processors, to determine the at least one of the plurality of change indicators, are configured to: score each of the plurality of change indicators, and determine the at least one of the plurality of change indicators based on the scoring. ### Claim 8 A method, comprising: obtaining, by a system, an indicator associated with an incident ticket based on a problem with a first application of a plurality of applications; determining, based on one or more dependency indicators associated with the plurality of applications, at least one of a plurality of change indicators, associated with changes to one or more second applications of the plurality of applications, is associated with the incident ticket, wherein the determination that the at least one of the plurality of change indicators is associated with the incident ticket is based on differences in a time associated with the incident ticket and times associated with the plurality of change indicators; and transmitting, by the system, a command to rollback at least one of the changes associated with the at least one of the plurality of change indicators or to rollforward at least one change related to the first application or the one or more second applications, based on determining the at least one of the plurality of change indicators is associated with the incident ticket. ### Claim 9 (depends on 8) The method of claim 8, wherein the determination that the at least one of the plurality of change indicators is associated with the incident ticket is additionally based on: dependencies between the first application and the one or more second applications. ### Claim 10 (depends on 8) The method of claim 8, wherein the indicator associated with the incident ticket comprises a data structure that indicates information about the problem. ### Claim 11 (depends on 8) The method of claim 8, wherein an identifier of the first application comprises one or more of: a process identifier, a thread identifier, or an alphanumeric name of the first application. ### Claim 12 (depends on 8) The method of claim 8, wherein the indicator associated with the incident ticket is obtained from a server that accepts reports from one or more users of a cloud-based environment associated with the plurality of applications. ### Claim 13 (depends on 8) The method of claim 8, wherein determining the at least one of the plurality of change indicators comprises: determining the at least one of the plurality of change indicators based on layers of dependency between the first application and the one or more second applications. ### Claim 14 (depends on 8) The method of claim 8, wherein determining the at least one of the plurality of change indicators comprises: scoring each of the plurality of change indicators, and determining the at least one of the plurality of change indicators based on the scoring. ### Claim 15 A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a system, cause the system to: obtain an indicator associated with an incident ticket based on a problem with a first application of a plurality of applications; determine, based on one or more dependency indicators associated with the plurality of applications, at least one of a plurality of change indicators, associated with changes to one or more second applications of the plurality of applications, is associated with the incident ticket, wherein the determination that the at least one of the plurality of change indicators is associated with the incident ticket is based on differences in a time associated with the incident ticket and times associated with the plurality of change indicators; and transmit a command to rollback at least one of the changes associated with the at least one of the plurality of change indicators or to rollforward at least one change related to the first application or the one or more second applications, based on determining the at least one of the plurality of change indicators is associated with the incident ticket. ### Claim 16 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the determination that the at least one of the plurality of change indicators is associated with the incident ticket is additionally based on: dependencies between the first application and the one or more second applications. ### Claim 17 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the indicator associated with the incident ticket comprises a data structure that indicates information about the problem. ### Claim 18 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein an identifier of the first application comprises one or more of: a process identifier, a thread identifier, or an alphanumeric name of the first application. ### Claim 19 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the indicator associated with the incident ticket is obtained from a server that accepts reports from one or more users of a cloud-based environment associated with the plurality of applications. ### Claim 20 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the system to determine the at least one of the plurality of change indicators, cause the system to: determine the at least one of the plurality of change indicators based on layers of dependency between the first application and the one or more second applications.