# US 2022/0019465 A1 · Systems and methods for batch job execution in clustered environments

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0019465 A1
- Document ID: US20220019465A1
- Status: Published application
- Kind: A1
- Application number: 17/449,276
- Filed: 2021-09-29
- Published: 2022-01-20
- Earliest claimed: 2019-05-15
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Kirankumar POKKULURI
- Web page: https://patentgrep.com/patent/US20220019465A1

## CPC

- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/5038: {considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups)}
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 20/401: {Transaction verification}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Systems and methods are disclosed for batch job execution. In some embodiments, a method may include: executing a plurality of service instances, each service instance being configured to execute jobs stored in a database; and by a first service instance of the plurality of service instances, identifying a job stored in the database, determining that no service instance of the plurality of service instances other than the first service instance has initiated execution of the job, generating an execution timestamp having a granularity of one second or longer, recording the generated execution timestamp in the database such that the execution timestamp is associated with the job, and executing the job. The service instances other than the first service instance may be configured to avoid execution of the job upon determining that a respective system time matches the execution timestamp to the granularity of the execution timestamp.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A computer-implemented method for batch job execution, the method comprising:
executing a plurality of service instances, each service instance being configured to execute jobs stored in a database;
identifying a job stored in the database;
identifying a first service instance;
determining that no service instance of the plurality of service instances other than the first service instance has initiated execution of the job;
generating an execution timestamp having a granularity of at least one of 2 seconds, 3 seconds, or 5 seconds;
recording the generated execution timestamp in the database such that the execution timestamp is associated with the job;
instructing the first service instance to execute the job;
identifying a second service instance;
determining whether a system time of the second service instance matches the first execution timestamp to the granularity of the execution timestamp associated with the job; and
upon determining that the system time of the second service instance matches the first execution timestamp to the granularity of the first execution timestamp, instructing the second instance to refrain from executing the job.

### Claim 22 (depends on 21)

The method of claim 21, wherein the first execution timestamp has a time value of a system time of the first service instance prior to the executing the first job.

### Claim 23 (depends on 21)

The method of claim 21, wherein the job includes generation of a file representing a financial transaction.

### Claim 24 (depends on 23)

The method of claim 23, wherein the financial transaction comprises an automated clearing house file representing a person-to-person transaction of transferring funds from an account maintained by a bank to an account maintained by a receiving bank.

### Claim 25 (depends on 21)

The method of claim 21, further comprising:
upon determining that the system time of the second service instance does not match the first execution timestamp to the granularity of the first execution timestamp, instructing the second instance to execute the job.

### Claim 26 (depends on 21)

The method of claim 21, wherein the first service instance is executed on a first computer system and the second service instance is executed on a second computer system located at a geographical region that is different from a geographic location of the first computer system.

### Claim 27 (depends on 21)

The method of claim 21, wherein the jobs stored in the database are stored in a single queue of the database.

### Claim 28 (depends on 27)

The method of claim 27 further comprising, by the second service instance:
upon determining that the system time of the second service instance matches the first execution timestamp to the granularity of the first execution timestamp, querying the single queue to identify another job to be executed.

### Claim 29 (depends on 26)

The method of claim 26, wherein the first computer system and the second computer system are cloud computing systems.

### Claim 30 (depends on 21)

The method of claim 21, further comprising:
upon instructing the second instance to refrain from executing the job, removing the job from the database.

### Claim 31

A computer-implemented method for batch job execution, the method comprising:
executing a plurality of service instances, each service instance being configured to execute jobs stored in a database;
identifying a job stored in the database;
identifying a first service instance;
determining that no service instance of the plurality of service instances other than the first service instance has initiated execution of the job;
generating an execution timestamp having a granularity at least one of 15 seconds, 20 seconds, 30 seconds, or 59 seconds;
recording the generated execution timestamp in the database such that the execution timestamp is associated with the job;
instructing the first service instance to execute the job;
identifying a second service instance;
determining whether a system time of the second service instance matches the first execution timestamp to the granularity of the execution timestamp associated with the job; and
upon determining that the system time of the second service instance matches the first execution timestamp to the granularity of the first execution timestamp, instructing the second instance to refrain from executing the job.

### Claim 32 (depends on 31)

The method of claim 31, wherein the first execution timestamp has a time value of a system time of the first service instance prior to the executing the first job.

### Claim 33 (depends on 31)

The method of claim 31, wherein the job includes generation of a file representing a financial transaction.

### Claim 34 (depends on 33)

The method of claim 33, wherein the financial transaction comprises an automated clearing house file representing a person-to-person transaction of transferring funds from an account maintained by a bank to an account maintained by a receiving bank

### Claim 35 (depends on 31)

The method of claim 31, further comprising:
upon determining that the system time of the second service instance does not match the first execution timestamp to the granularity of the first execution timestamp, instructing the second instance to execute the job.

### Claim 36 (depends on 31)

The method of claim 31, wherein the first service instance is executed on a first computer system and the second service instance is executed on a second computer system located at a geographical region that is different from a geographic location of the first computer system.

### Claim 37 (depends on 31)

The method of claim 31, wherein the jobs stored in the database are stored in a single queue of the database.

### Claim 38 (depends on 37)

The method of claim 37, further comprising, by the second service instance:
upon determining that the system time of the second service instance matches the first execution timestamp to the granularity of the first execution timestamp, querying the single queue to identify another job to be executed.

### Claim 39 (depends on 31)

The method of claim 31, further comprising:
upon instructing the second instance to refrain from executing the job, removing the job from the database.

### Claim 40

A system for payment transfer, the system comprising:
a first computer system comprising one or more processors configured to execute a first service instance; and
a second computer system comprising one or more processors configured to execute a second service instance, wherein
the first service instance and the second service instance are each configured to:
retrieve a job from a plurality of jobs stored in a database;
determine whether the job is associated with an execution timestamp;
upon determining that the job is not associated with an execution timestamp, generating an execution timestamp having a granularity of at least one of 2 seconds, 3 seconds, or 5 seconds;
recording the generated execution timestamp in the database such that the execution timestamp is associated with the job; and
executing the job.
