# US 2014/0236670 A1 · Data Communication and Analytics Platform

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

- Number: US 2014/0236670 A1
- Document ID: US20140236670A1
- Status: Published application
- Kind: A1
- Application number: 13/886,182
- Filed: 2013-05-02
- Published: 2014-08-21
- Earliest claimed: 2013-02-21
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: John A. Tsefrikas; S. Michelle Ybarra; Jeffrey R. Walls; James A. Greco; Richard McKinnon; Paul Schneider
- Web page: https://patentgrep.com/patent/US20140236670A1

## CPC

- G06F 16/21: Design, administration or maintenance of databases
- G06F 16/211: {Schema design and management}
- G06F 16/24: Querying
- G06Q 10/0637: Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
- G06Q 10/10: Office automation; Time management
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- 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

A processor in an attribute retrieval module determines retrievable customer attributes from a plurality of data locations, wherein at least one of the retrievable customer attributes is retrieved from a data location external to the enterprise. The interface receives a customer attribute request from a first computer, the request includes at least one customer identifier and requested customer attributes. The requested customer attributes is a subset of the retrievable customer attributes. The processor determines the data location of each requested customer attribute and generates an information call for each data location. The interface communicates the information call to each data location. The interface receives a data report in response to the information call from each data location. The processor generates a complete data report based on the data report received from each data location, and the interface communicates the complete data report to the first computer.

## Claims

### Claim 1

A system, comprising:
a processor operable to determine retrievable customer attributes from a plurality of data locations, wherein at least one retrievable customer attributes is retrieved from a data location external to an enterprise;
an interface communicatively coupled to the processor and operable to receive a customer attribute request from a first computer, the customer attribute request including at least one customer identifier and requested customer attributes and, the requested customer attributes being a subset of retrievable customer attributes;
the processor is further operable to:
determine the data location of each requested customer attribute; and
generate an information call for each data location, the information call comprising at least the customer identifier and one requested customer attribute;
the interface is further operable to:
communicate the information call to each data location; and
receive a data report in response to the information call from each data location containing the customer attribute information associated with the customer identifier;
the processor is further operable to generate a complete data report based on the data report received from each data location; and
the interface is further operable to communicate the complete data report to the first computer.

### Claim 2 (depends on 1)

The system of claim 1, wherein the processor is further operable to:
determine whether the information call is the same as a prior information call; and
if the information call is the same as the prior information call, access a received data report associated with the prior information call.

### Claim 3 (depends on 1)

The system of claim 1, wherein at least one requested customer attribute is stored in a data location internal to the enterprise and at least one requested customer attribute is stored in a data location external to the enterprise.

### Claim 4 (depends on 1)

The system of claim 1, wherein the customer attribute request includes a priority of the customer attribute request;
the processor is further operable to determine whether the priority of the customer attribute request exceeds the priority of an incomplete information call; and
the interface is further operable to communicate the information call associated with the requested customer attribute request before communicating the incomplete information call if the priority of the customer attribute request exceeds the priority of an incomplete information call.

### Claim 5 (depends on 1)

The system of claim 1, wherein the interface is further operable to:
receive a status update from the data location, the status update indicating the progress of completing the information call; and
communicate the status update to the first computer.

### Claim 6 (depends on 1)

The system of claim 1, wherein:
the processor is further operable to generate a partial data report based on the data reports received from at least one data locations; and
the interface is further operable to communicate the partial data report to the first computer.

### Claim 7

A method, comprising:
determining, by a processor, retrievable customer attributes from a plurality of data locations, wherein at least one retrievable customer attributes is retrieved from a data location external to an enterprise;
receiving, by an interface, a customer attribute request from a first computer, the customer attribute request including at least one customer identifier and requested customer attributes and, the requested customer attributes being a subset of retrievable customer attributes;
determining, by the processor, the data location of each requested customer attribute;
generating, by the processor, an information call for each data location, the information call comprising at least the customer identifier and one requested. customer attribute;
communicating, by the interface, the information call to each data location;
receiving, by the interface, a data report in response to the information call from each data location containing the customer attribute information associated with the customer identifier;
generating, by the processor, a complete data report based on the data report received from each data location;
communicating, by the interface, the complete data report to the first computer.

### Claim 8 (depends on 7)

method of claim 7, further comprising:
determining, by the processor, whether the information call is the same as a prior information call; and
if the information call is the same as the prior information call, accessing a received data report associated with the prior information call.

### Claim 9 (depends on 7)

The method of claim 7, wherein at least one requested customer attribute is stored in a data location internal to the enterprise and at least one requested customer attribute is stored in a data location external to the enterprise.

### Claim 10 (depends on 7)

The method of claim 7, Wherein the customer attribute request includes a priority of the customer attribute request;
and further comprising:
determining, by the processor, whether the priority of the customer attribute request exceeds the priority of an incomplete information call;
if the priority of the customer attribute request exceeds the priority of an incomplete information call, communicating the information call associated with the requested customer attribute request before communicating the incomplete information call.

### Claim 11 (depends on 7)

method of claim 7, further comprising:
receiving a status update from the data location, the status update indicating the progress of completing the information call; and
communicating the status update to the first computer.

### Claim 12 (depends on 7)

The method of claim 7, further comprising:
generating, by the processor, a partial data report based on the data reports received from at least one data locations; and
communicating, by the interface, the partial data report to the first computer.

### Claim 13

Non-transitory computer readable medium comprising logic, the logic, when executed by a processor, operable to:
determine retrievable customer attributes from a plurality of data locations, Wherein at least one retrievable customer attributes is retrieved from a data location external to an enterprise;
receive a customer attribute request from a first computer, the customer attribute request including at least one customer identifier and requested customer attributes and, the requested customer attributes being a subset of retrievable customer attributes;
determine the data location of each requested customer attribute;
generate an information call for each data location, the information call comprising at least the customer identifier and one requested customer attribute;
communicate the information call to each data location;
receive a data report in response to the information call from each data location containing the customer attribute information associated with the customer identifier;
generate a complete data report based on the data report received from each data location;
communicate the complete data report to the first computer.

### Claim 14 (depends on 13)

The computer readable medium of claim 13, wherein the logic is further operable to:
determine whether the information call is the same as a prior information call; and
if the information call is the same as the prior information call, access a received data report associated with the prior information call.

### Claim 15 (depends on 13)

The computer readable medium of claim 13, wherein at least one requested customer attribute is stored in a data location internal to the enterprise and at least one requested customer attribute is stored in a data location external to the enterprise.

### Claim 16 (depends on 13)

The computer readable medium of claim 13, wherein the customer attribute request includes a priority of the customer attribute request; and
wherein the logic is further operable to:
determine whether the priority of the customer attribute request exceeds the priority of an incomplete information call;
if the priority of the customer attribute request exceeds the priority of an incomplete information call, communicate the information call associated with the requested customer attribute request before communicating the incomplete information call.

### Claim 17 (depends on 13)

The computer readable medium of claim 13, wherein the logic is further operable to:
receive a status update from the data location, the status update indicating the progress of completing the information call; and
communicate the status update to the first computer.

### Claim 18 (depends on 13)

computer readable medium of claim 13, wherein the logic is further operable to:
generate a partial data report based on the data reports received from at least one data locations; and
communicate the partial data report to the first computer.
