# US 2026/0154439 A1 · Systems and methods for linking remote file storage

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

- Number: US 2026/0154439 A1
- Document ID: US20260154439A1
- Status: Published application
- Kind: A1
- Application number: 19/459,754
- Filed: 2026-01-26
- Published: 2026-06-04
- Earliest claimed: 2023-02-07
- Assignees: Wells Fargo Bank, N.A.
- Applicants: Wells Fargo Bank, N.A.
- Inventors: David Bendert; Maximilian Fuchs; Matthew Spain
- Web page: https://patentgrep.com/patent/US20260154439A1

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 16/134: {Distributed indices}
- G06F 16/16: File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems, apparatuses, methods, and computer program products are disclosed for linking remote file storage. An example method includes identifying, by discovery agent circuitry, a set of files for storage from a set of candidate files, and classifying, by file metadata circuitry, each file from the set of files for storage into file usage categories. The example method also includes assigning, by file metadata circuitry, permission categories to each file from the set of files for storage based on the file usage categories, and providing, by communications hardware, the set of files for storage and associated metadata to a file storage host, wherein the associated metadata comprises the file usage categories and the permission categories The example method also includes updating, by the discovery agent circuitry, content stored on the file storage host, the content comprising the set of files for storage.

## Claims

### Claim 1

A method comprising:
obtaining, by communications hardware and from a file source, a set of files for storage and associated metadata, wherein the associated metadata comprises file usage categories and permission categories;
receiving, by the communications hardware and from a request source, a request for a file belonging to the set of files for storage;
determining, by file metadata circuitry, an access level permitted for the file based on the file usage categories and the permission categories; and
in an instance in which the access level is met, transmitting, by the communications hardware and to the request source, content reflecting the access level permitted for the file.

### Claim 2 (depends on 1)

The method of claim 1, further comprising obtaining the file by:
identifying, by discovery agent, the set of files for storage from a set of candidate files;
determining, by the discovery agent and from the set of files for storage, (a) a first set of candidate files within the set of candidate files to which third-party access has been granted more than a predefined number of times and (b) a second set of candidate files based on at least a user file access pattern;
classifying, by the file metadata circuitry, each file from the set of files for storage into the file usage categories, the classifying of each file is based on whether the file belongs to the first set of candidate files or the second set of candidate files;
assigning, by file metadata circuitry, the permission categories to each file from the set of files for storage based on the file usage categories;
providing, by the communications hardware, the set of files for storage and the associated metadata to a file storage host, wherein the associated metadata comprises the file usage categories and the permission categories; and
updating, by the discovery agent, content stored on the file storage host, the content comprising the set of files for storage.

### Claim 3 (depends on 2)

The method of claim 2, wherein:
each file usage category indicates a corresponding usage of a file for a third-party entity; and
each permission category is based on the corresponding usage of the file for the third-party entity.

### Claim 4 (depends on 2)

The method of claim 2, further comprising:
determining, by the file metadata circuitry, that the file associated with the request for the file exists on the file storage host.

### Claim 5 (depends on 1)

The method of claim 1, wherein the request source is an enterprise cloud instance, and the file is stored on a private cloud instance.

### Claim 6 (depends on 1)

The method of claim 1, wherein the content reflecting the access level permitted for the file comprises:
a copy of the file;
limited access to the file through a file access client;
a raw data file generated by converting the file;
a digitally signed confirmation of a content of the file;
an access token linked to the file; or
a combination thereof.

### Claim 7 (depends on 6)

The method of claim 6, wherein the digitally signed confirmation is provided by a third party.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
updating, by blockchain circuitry, a record of the file on a distributed ledger.

### Claim 9 (depends on 1)

The method of claim 1:
wherein the file is stored on a file storage host,
wherein the method further comprises:
establishing, by the communications hardware, a persistent link between the request source and the file storage host.

### Claim 10

An apparatus comprising:
communications hardware configured to:
obtain, from a file source, a set of files for storage and associated metadata, wherein the associated metadata comprises file usage categories and permission categories, and
receive, from a request source, a request for a file belonging to the set of files for storage; and
file metadata circuitry configured to:
determine an access level permitted for the file based on the file usage categories and the permission categories,
wherein the communications hardware is further configured to, in an instance in which the access level is met, transmit to the request source, content reflecting the access level permitted for the file.

### Claim 11 (depends on 10)

The apparatus of claim 10, further comprising a discovery agent configured to obtain the file by:
identifying the set of files for storage from a set of candidate files; and
determining, from the set of files for storage, (a) a first set of candidate files within the set of candidate files to which third-party access has been granted more than a predefined number of times and (b) a second set of candidate files based on at least a user file access pattern,
wherein the file metadata circuitry is further configured to:
classify each file from the set of files for storage into the file usage categories, the classifying of each file is based on whether the file belongs to the first set of candidate files or the second set of candidate files; and
assign the permission categories to each file from the set of files for storage based on the file usage categories,
wherein the communications hardware is further configured to:
provide the set of files for storage and the associated metadata to a file storage host, wherein the associated metadata comprises the file usage categories and the permission categories,
wherein the discovery agent is further configured to:
update content stored on the file storage host, the content comprising the set of files for storage.

### Claim 12 (depends on 11)

The apparatus of claim 11, wherein:
each file usage category indicates a corresponding usage of a file for a third-party entity; and
each permission category is based on the corresponding usage of the file for the third-party entity.

### Claim 13 (depends on 11)

The apparatus of claim 11, wherein the file metadata circuitry is further configured to:
determine that the file associated with the request for the file exists on the file storage host.

### Claim 14 (depends on 10)

The apparatus of claim 10, wherein the request source is an enterprise cloud instance, and the file is stored on a private cloud instance.

### Claim 15 (depends on 10)

The apparatus of claim 10, wherein the content reflecting the access level permitted for the file comprises:
a copy of the file;
limited access to the file through a file access client;
a raw data file generated by converting the file;
a digitally signed confirmation of a content of the file;
an access token linked to the file; or
a combination thereof.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the digitally signed confirmation is provided by a third party.

### Claim 17 (depends on 10)

The apparatus of claim 10, further comprising blockchain circuitry configured to:
update a record of the file on a distributed ledger.

### Claim 18 (depends on 10)

The apparatus of claim 10:
wherein the file is stored on a file storage host,
wherein the communications hardware is further configured to:
establish a persistent link between the request source and the file storage host.

### Claim 19

A computer program product comprising software instructions that, when executed by a processor an apparatus, cause the apparatus to:
obtain, from a file source, a set of files for storage and associated metadata, wherein the associated metadata comprises file usage categories and permission categories;
receive, from a request source, a request for a file belonging to the set of files for storage;
determine an access level permitted for the file based on the file usage categories and the permission categories; and
in an instance in which the access level is met, transmit, to the request source, content reflecting the access level permitted for the file.

### Claim 20 (depends on 19)

The computer program product of claim 19 wherein the software instructions, when executed, further cause the apparatus to:
identify the set of files for storage from a set of candidate files;
determine, from the set of files for storage, (a) a first set of candidate files within the set of candidate files to which third-party access has been granted more than a predefined number of times and (b) a second set of candidate files based on at least a user file access pattern;
classify each file from the set of files for storage into the file usage categories, the classifying of each file is based on whether the file belongs to the first set of candidate files or the second set of candidate files;
assign the permission categories to each file from the set of files for storage based on the file usage categories;
provide the set of files for storage and the associated metadata to a file storage host, wherein the associated metadata comprises the file usage categories and the permission categories; and
update content stored on the file storage host, the content comprising the set of files for storage.
