# US 11,907,692 B2 · System and method for retrieval and generation of graphical user interface depicting of graphics associated with rules-based data management

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

- Number: US 11,907,692 B2
- Document ID: US11907692B2
- Status: Granted
- Kind: B2
- Application number: 17/872,358
- Filed: 2022-07-25
- Published: 2024-01-25
- Granted: 2024-02-20
- Earliest claimed: 2022-07-25
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Vijaybabu Eswari Rajan Babu; Pratikshaben Patel; Qian Wen
- Web page: https://patentgrep.com/patent/US11907692B2

## CPC

- G06F 8/433: {Dependency analysis; Data or control flow analysis}
- G06F 8/73: Program documentation
- G06F 8/45: {Exploiting coarse grain parallelism in compilation, i.e. parallelism between groups of instructions}
- G06N 5/025: Extracting rules from data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

Systems, computer program products, and methods are described herein for retrieval and generation of graphical user interface depicting of graphics associated with rules-based data management. The present invention is configured to electronically receive a request from a user for a chart of process data, wherein the chart of the process data represents the corresponding process data most recently saved in a storage device, electronically receive the process data from a rule data management system and export the chart of the process data. Each of the modules and dependency data are received as inputs, and thereafter the chart displays each of the modules and corresponding module generic descriptions, rule data and corresponding rule generic descriptions, and an execution order.

## Claims

### Claim 1

A system for retrieval and generation of graphical user interface depicting of graphics associated with rules-based data management, the system comprising:
at least one non-transitory storage device; and
at least one processor coupled to the at least one non-transitory storage device, wherein the at least one processor is configured to:
electronically receive a request from a user for a chart of process data, wherein the chart of the process data represents the corresponding process data most recently saved in the at least one non-transitory storage device, and wherein the process data comprises one or more modules;
electronically receive the process data from a rule data management system; and
export the chart of the process data, wherein the system receives each of the one or more modules and dependency data as inputs, and thereafter the chart displays each of the one or more modules and corresponding module generic descriptions, one or more rule data and corresponding rule generic descriptions, and an execution order,
wherein the rule data management system is configured to:
electronically receive the one or more rule data and the one or more modules;
store the one or more rule data in a rule definition table;
store the one or more modules in a module table, wherein the module table comprises module identifiers each corresponding to the one or more modules, and wherein the module table is configured to communicate with other systems;
define the process data, the process data comprising the one or more modules, wherein the one or more modules comprise the one or more rule data, and wherein a module rule table is configured to match the one or more rule data with the one or more modules; and
define the dependency data in a dependency table, the dependency data comprising interdependencies between the one or more modules.

### Claim 2 (depends on 1)

The system of claim 1, wherein the rule data management system is further configured to:
store in an optionality table a grouping of modules and a sequence of modules for the process data, wherein the optionality table comprises an optionality index; and
store in a module optionality table the optionality index and the module identifiers.

### Claim 3 (depends on 1)

The system of claim 1, wherein the rule data management system is configured to store a plurality of process data.

### Claim 4 (depends on 1)

The system of claim 1, wherein the rule data management system is further configured to:
receive, from the user, the module generic descriptions for the one or more modules; and
store the module generic description in the module table.

### Claim 5 (depends on 1)

The system of claim 1, wherein the rule data management system is further configured to:
receive, from the user, the rule generic descriptions for the one or more rule data; and
store the rule generic description in the rule definition table.

### Claim 6 (depends on 1)

The system of claim 1, wherein the interdependencies are defined as the one or more modules in parallel, series, or neither.

### Claim 7

A computer program product for retrieval and generation of graphical user interface depicting of graphics associated with rules-based data management, the computer program product comprising a non-transitory computer-readable medium comprising code causing an apparatus to:
electronically receive a request from a user for a chart of process data, wherein the chart of the process data represents the corresponding process data most recently saved in at least one non-transitory storage device, and wherein the process data comprises one or more modules;
electronically receive the process data from a rule data management system; and
export the chart of the process data, wherein the computer program product receives each of the one or more modules and dependency data as inputs, and thereafter the chart displays each of the one or more modules and corresponding module generic descriptions, one or more rule data and corresponding rule generic descriptions, and an execution order,
wherein the rule data management system is configured to:
electronically receive the one or more rule data and the one or more modules;
store the one or more rule data in a rule definition table;
store the one or more modules in a module table, wherein the module table comprises module identifiers each corresponding to the one or more modules, and wherein the module table is configured to communicate with other systems;
define the process data, the process data comprising the one or more modules, wherein the one or more modules comprise the one or more rule data, and wherein a module rule table is configured to match the one or more rule data with the one or more modules; and
define the dependency data in a dependency table, the dependency data comprising interdependencies between the one or more modules.

### Claim 8 (depends on 7)

The computer program product of claim 7, wherein the rule data management system is further configured to:
store in an optionality table a grouping of modules and a sequence of modules for the process data, wherein the optionality table comprises an optionality index; and
store in a module optionality table the optionality index and the module identifiers.

### Claim 9 (depends on 7)

The computer program product of claim 7, wherein the rule data management system is configured to store a plurality of process data.

### Claim 10 (depends on 7)

The computer program product of claim 7, wherein the rule data management system is further configured to:
receive, from the user, the module generic descriptions for the one or more modules; and
store the module generic description in the module table.

### Claim 11 (depends on 7)

The computer program product of claim 7, wherein the rule data management system is further configured to:
receive, from the user, the rule generic descriptions for the one or more rule data; and
store the rule generic description in the rule definition table.

### Claim 12 (depends on 7)

The computer program product of claim 7, wherein the interdependencies are defined as the one or more modules in parallel, series, or neither.

### Claim 13

A method for retrieval and generation of graphical user interface depicting of graphics associated with rules-based data management, the method comprising:
electronically receiving a request from a user for a chart of process data, wherein the chart of the process data represents the corresponding process data most recently saved in at least one non-transitory storage device, and wherein the process data comprises one or more modules;
electronically receiving the process data from a rule data management system; and
exporting the chart of the process data, wherein a system receives each of the one or more modules and dependency data as inputs, and thereafter the chart displays each of the one or more modules and corresponding module generic descriptions, one or more rule data and corresponding rule generic descriptions, and an execution order,
wherein the rule data management system is configured to:
electronically receive the one or more rule data and the one or more modules;
store the one or more rule data in a rule definition table;
store the one or more modules in a module table, wherein the module table comprises module identifiers each corresponding to the one or more modules, and wherein the module table is configured to communicate with other systems;
define the process data, the process data comprising the one or more modules, wherein the one or more modules comprise the one or more rule data, and wherein a module rule table is configured to match the one or more rule data with the one or more modules; and
define the dependency data in a dependency table, the dependency data comprising interdependencies between the one or more modules.

### Claim 14 (depends on 13)

The method of claim 13, wherein the rule data management system is further configured to:
store in an optionality table a grouping of modules and a sequence of modules for the process data, wherein the optionality table comprises an optionality index; and
store in a module optionality table the optionality index and the module identifiers.

### Claim 15 (depends on 13)

The method of claim 13, wherein the rule data management system is further configured to:
receive, from the user, the module generic descriptions for the one or more modules; and
store the module generic description in the module table.

### Claim 16 (depends on 13)

The method of claim 13, wherein the rule data management system is further configured to:
receive, from the user, the rule generic descriptions for the one or more rule data; and
store the rule generic description in the rule definition table.

### Claim 17 (depends on 13)

The method of claim 13, wherein the interdependencies are defined as the one or more modules in parallel, series, or neither.
