# US 11,122,112 B1 · Systems and methods for distributed micro services using private and external networks

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

- Number: US 11,122,112 B1
- Document ID: US11122112B1
- Status: Granted
- Kind: B1
- Application number: 15/274,130
- Filed: 2016-09-23
- Granted: 2021-09-14
- Earliest claimed: 2016-09-23
- Assignees: JPMorgan Chase Bank, N.A.
- Applicants: JPMorgan Chase Bank, N.A.
- Inventors: Erick A. Gomez; Bret Goldsmith; Gordon Robert Macdonald; Harshavardhan Reddy Mukkera; Hirenkumar Patel
- Web page: https://patentgrep.com/patent/US11122112B1

## CPC

- 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)}
- G06F 16/951: Indexing; Web crawling techniques
- H04L 63/105: {Multiple levels of security}
- H04L 63/107: {wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals}
- H04L 67/52: specially adapted for the location of the user terminal
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/133: Protocols for remote procedure calls [RPC]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for enhanced organizational transparency using a credit chain are disclosed. In one embodiment, a method for accessing a resource may include (1) a cloud foundry comprising at least one computer processor receiving an application request from an interface provided by an end user electronic device; (2) the cloud foundry determining a location of at least one resource associated with the application request, wherein the location is selected from a private cloud and a public cloud; (3) the cloud foundry retrieving at least one of a microservice and an API necessary to access the resource from the location; and (4) the cloud foundry routing the application request to the location using the at least one of the microservice and the API.

## Claims

### Claim 1

A method for accessing a resource, comprising:
a cloud foundry comprising at least one computer processor receiving an application request from an interface provided by an end user electronic device;
the cloud foundry determining a location of a resource associated with the application request based on a prior application request for the resource and the end user's physical proximity to a data center hosting the resource, wherein the location is selected from a private cloud and a public cloud;
the cloud foundry determining whether to access the resource based on a security level associated with the resource at the location;
the cloud foundry retrieving at least one of a micro service and an API necessary to access the resource from the location; and
the cloud foundry routing the application request to the location using the at least one of the micro service and the API.

### Claim 2 (depends on 1)

The method of claim 1, wherein the cloud foundry determines the location based on a type of the resource.

### Claim 3 (depends on 1)

The method of claim 1, wherein the location of the resource is stored in a database, and the cloud foundry accesses the database to retrieve the location.

### Claim 4 (depends on 1)

The method of claim 1, wherein the at least one of the micro service and the API are stored in a library.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
the cloud foundry verifying an entitlement of a user associated with the electronic device to access the application or the resource.

### Claim 6 (depends on 1)

The method of claim 1, wherein the micro services comprise at least one of a REST API and a SOAP API.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
the cloud foundry routing the resource to the end user electronic device.

### Claim 8 (depends on 1)

The method of claim 1, wherein the resource is one of an application and data.

### Claim 9

A system for accessing a resource, comprising:
an end user electronic device;
a cloud foundry in communication with the end user electronic device;
a micro services API library hosting a plurality of micro services;
at least one public cloud hosting at least one public resource; and
at least one private cloud hosting at least one private resource;
wherein:
the cloud foundry receives an application request from an interface provided by the end user electronic device;
the cloud foundry determines a location of a resource associated with the application request based on a prior application request for the resource and the end user's physical proximity to a data center hosting the resource, wherein the location is selected from the private cloud and the public cloud;
the cloud foundry determining whether to access the resource based on a security level associated with the resource at the location;
the cloud foundry retrieving, from the micro services API library, at least one of a micro service and an API necessary to access the resource from the location; and
the cloud foundry routing the application request to the location using the at least one of the micro service and the API.

### Claim 10 (depends on 9)

The system of claim 9, wherein the cloud foundry determines the location based on a type of the resource.

### Claim 11 (depends on 9)

The system of claim 9, further comprising at least one database that stores the location of the resource, and the cloud foundry accesses the database to retrieve the location.

### Claim 12 (depends on 9)

The system of claim 9, wherein the cloud foundry verifies an entitlement of a user associated with the electronic device to access the application or the resource.

### Claim 13 (depends on 9)

The system of claim 9, wherein the micro services comprise at least one of a REST API and a SOAP API.

### Claim 14 (depends on 9)

The system of claim 9, wherein the cloud foundry routes the resource to the end user electronic device.

### Claim 15 (depends on 9)

The system of claim 9, wherein the end user electronic device executes the resource.

### Claim 16 (depends on 9)

The system of claim 9, wherein the resource is one of an application and data.
