# US 2023/0267017 A1 · Systems and methods for routing data payloads through a plurality of microservices using machine learning

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

- Number: US 2023/0267017 A1
- Document ID: US20230267017A1
- Status: Published application
- Kind: A1
- Application number: 17/651,729
- Filed: 2022-02-18
- Published: 2023-08-24
- Earliest claimed: 2022-02-18
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Elijah MOREAU-ARNOTT; Jonathan LEE; Garrett RANDALL
- Web page: https://patentgrep.com/patent/US20230267017A1

## CPC

- 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)}
- G06F 9/54: Interprogram communication
- G06N 3/0442: characterised by memory or gating, e.g. long short-term memory [LSTM] or gated recurrent units [GRU]
- G06N 3/084: Backpropagation, e.g. using gradient descent
- G06N 5/01: Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound
- G06N 20/20: Ensemble learning
- H04L 9/0838: {Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these (network architectures or network communication protocols for key exchange in a packet data network H04L63/061)}
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- 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

Methods and systems for routing data payloads through a plurality of microservices are disclosed. The method may comprise: receiving a data payload and first data; predicting, by a trained machine learning model based on the first data, a path through a plurality of microservices associated with the data payload; generating a modified data payload by modifying, via the orchestrator service, the data payload to include: a first header, wherein the first header comprises a first microservice destination address associated with a first microservice of the plurality of microservices and a second header nested within the first header, wherein the second header comprises a second microservice destination address associated with a second microservice of the plurality of microservices; forwarding the modified data payload to the first microservice based on the first header for processing; and forwarding the modified data payload to the second microservice based on the second header for processing.

## Claims

### Claim 1

A computer-implemented method for routing data payloads through a plurality of microservices, the method comprising:
receiving, by one or more processors via an orchestrator service, a data payload and first data that includes information regarding the data payload;
determining, by one or more processors via the orchestrator service, that one or more microservices of a plurality of microservices are associated with the data payload based on the information regarding the data payload and one or more tasks associated with the data payload that are performed by the one or more microservices of the plurality of microservices;
predicting, by a trained machine learning model executed by the one or more processors and based on the first data, a path through the one or more microservices associated with the data payload, wherein the trained machine learning model is trained based on: (i) second data that includes one or more prior data payloads and prior feedback data as test data, and (ii) third data that includes one or more prior microservices corresponding to the one or more prior data payloads, to learn associations between the test data and the corresponding prior feedback data for each of the one or more prior data payloads, such that the trained machine learning model is configured to determine a path through the one or more microservices associated with the data payload in response to input of the first data and the data payload;
generating a modified data payload by modifying, by the one or more processors via the orchestrator service, the data payload to include:
a first header, wherein the first header comprises a first microservice destination address associated with a first microservice of the one or more microservices; and
a second header nested within the first header, wherein the second header comprises a second microservice destination address associated with a second microservice of the one or more microservices;
forwarding, by the one or more processors via the orchestrator service, the modified data payload to the first microservice based on the first header, such that the modified data payload is processed by the first microservice; and
forwarding, by the one or more processors via the first microservice, the modified data payload output by the first microservice to the second microservice based on the second header, such that the modified data payload is processed by the second microservice.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
forwarding, by the one or more processors, the second processed modified data payload output by the second microservice to one of:
a database;
an output stream; or
an outbound API.

### Claim 3 (depends on 1)

The method of claim 1, wherein the processing by the first microservice comprises one or more of:
filtering data in the modified data payload;
inserting additional data into the modified data payload; or
generating a message associated with the modified data payload.

### Claim 4 (depends on 1)

The method of claim 1, wherein the modified data payload is encrypted.

### Claim 5 (depends on 4)

The method of claim 4, wherein the modified data payload is encrypted using one or more of: DES; Triple DES; AES; RSA; Twofish; Blowfish; Threefish; ElGamal; IDEA; RC6; Elliptic Curve Cryptography; or Diffie-Hellman.

### Claim 6 (depends on 1)

The method of claim 1, wherein the prior feedback data comprises one or more feedback scores for each of the one or more prior data payloads.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving, by the one or more processors, a second data payload; and
generating a second modified data payload by modifying, by the one or more processors via the orchestrator service, the second data payload to include:
a second data payload header, wherein the second data payload header comprises the first microservice destination address associated with the first microservice of the plurality of microservices; and
an additional data payload header nested within the second data payload header, wherein the additional data payload header comprises a third microservice destination address associated with a third microservice.

### Claim 8 (depends on 1)

The method of claim 1, wherein the orchestrator service is one of a plurality of orchestrator services, the method further including:
selecting the orchestrator service of the plurality of orchestrator services based on the data payload.

### Claim 9 (depends on 1)

The method of claim 1, wherein the modified data payload further includes a third header nested within the second header, wherein the third header comprises a third microservice destination address associated with a third microservice.

### Claim 10 (depends on 9)

The method of claim 9, further comprising forwarding, by the one or more processors, the modified data payload to the third microservice based on the third header for processing by the third microservice.

### Claim 11

A system for routing data through a plurality of microservices, the system comprising:
at least one memory storing instructions; and
at least one processor executing the instructions to perform a process including:
receiving, via an orchestrator service, a data payload;
receiving, via the orchestrator service, first data that includes information regarding the data payload;
determining a path through a plurality of microservices associated with the data payload based on the first data and tasks associated with the first data that are performed by the plurality of microservices;
generating a modified data payload by modifying, via the orchestrator service, the data payload to include:
a first header, wherein the first header comprises a first microservice destination address associated with a first microservice of the plurality of microservices; and
a second header nested within the first header, wherein the second header comprises a second microservice destination address associated with a second microservice of the plurality of microservices, to generate a modified data payload;
forwarding, via the orchestrator service, the modified data payload to the first microservice based on the first header, such that the modified data payload is processed by the first microservice; and
forwarding, via the first microservice, the modified data payload output by the first microservice to the second microservice based on the second header, such that the modified data payload is processed by the second microservice.

### Claim 12 (depends on 11)

The system of claim 11, wherein the process further includes:
forwarding, by the at least one processor, the modified data payload output by the second microservice to one of:
a database;
an output stream; or
an outbound API.

### Claim 13 (depends on 11)

The system of claim 11, wherein the processing by the first microservice comprises one or more of:
filtering data in the modified data payload;
inserting additional data into the modified data payload; or
generating a message associated with the modified data payload.

### Claim 14 (depends on 11)

The system of claim 11, wherein determining a path through a plurality of microservices associated with the data payload based on the first data further comprises determining, by a trained machine learning model based on the first data, the path through the plurality of microservices associated with the data payload, wherein the trained machine learning model is trained based on:
(i) second data that includes one or more prior data payloads and prior feedback data as test data, and
(ii) third data that includes one or more prior microservices corresponding to the one or more prior data payloads, to learn associations between the test data and the corresponding prior feedback data for each of the one or more prior data payloads, such that the trained machine learning model is configured to determine a path through a plurality of microservices associated with the data payload in response to input of the first data and the data payload.

### Claim 15 (depends on 11)

The system of claim 11, wherein the modified data payload is encrypted using one or more of: DES; Triple DES; AES; RSA; Twofish; Blowfish; Threefish; ElGamal; IDEA; RC6; Elliptic Curve Cryptography; or Diffie-Hellman.

### Claim 16 (depends on 14)

The system of claim 14, wherein the prior feedback data comprises one or more feedback scores for each of the one or more prior data payloads.

### Claim 17 (depends on 11)

The system of claim 11, further comprising:
receiving a second data payload; and
generating a modified data payload by modifying, via the orchestrator service, the second data payload to include:
a second data payload header, wherein the second data payload header comprises the first microservice destination address associated with the first microservice of the plurality of microservices; and
an additional data payload header nested within the second data payload header, wherein the additional data payload header comprises a third microservice destination address associated with a third microservice, to generate a modified second data payload.

### Claim 18 (depends on 11)

The system of claim 11, wherein the orchestrator service is one of a plurality of orchestrator services, the process further including:
selecting the orchestrator service of the plurality of orchestrator services based on the data payload.

### Claim 19 (depends on 11)

The system of claim 11, wherein modifying the data payload further comprises modifying the data payload to include a third header nested within the second header, wherein the third header comprises a third microservice destination address associated with a third microservice, to generate the modified data payload, the process further including:
forwarding the processed modified data payload to the third microservice based on the third header for processing by the third microservice.

### Claim 20

A computer-implemented method for routing data through a plurality of microservices, the method comprising:
receiving, by one or more processors via an orchestrator service, a data payload and first data that includes information regarding the data payload;
determining, by one or more processors via the orchestrator service, that one or more of the plurality of microservices are associated with the data payload based on the information regarding the data payload and one or more tasks associated with the information regarding the data payload that are performed by the one or more microservices of the plurality of microservices;
predicting, by a trained machine learning model executed by the one or more processors and based on the first data, a path through the one or more of microservices associated with the data payload, wherein the trained machine learning model is trained based on: (i) second data that includes one or more prior data payloads and prior feedback data as test data, and (ii) third data that includes one or more prior microservices corresponding to the one or more prior data payloads, to learn associations between the test data and the corresponding prior feedback data for each of the one or more prior data payloads, such that the trained machine learning model is configured to determine a path through the one or more microservices associated with the data payload in response to input of the first data and the data payload;
generating a modified data payload by modifying, by the one or more processors via the orchestrator service, the data payload to include:
a first header, wherein the first header comprises a first microservice destination address associated with a first microservice of the plurality of microservices; and
a second header nested within the first header, wherein the second header comprises a second microservice destination address associated with a second microservice of the plurality of microservices;
forwarding, by the one or more processors via the orchestrator service, the modified data payload to the first microservice based on the first header, such that the modified data payload is processed by the first microservice;
forwarding, by the one or more processors, via the first microservice, the modified data payload output by the first microservice to the second microservice based on the second header, such that the modified data payload is processed by the second microservice;
receiving, by the one or more processors, a second data payload; and
forwarding, by the one or more processors, the second data payload to a second orchestrator service.
