# US 2024/0202350 A1 · Thin network-based resource integration

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

- Number: US 2024/0202350 A1
- Document ID: US20240202350A1
- Status: Published application
- Kind: A1
- Application number: 18/081,145
- Filed: 2022-12-14
- Published: 2024-06-20
- Earliest claimed: 2022-12-14
- Assignees: NCR Voyix Corporation
- Applicants: NCR Voyix Corporation
- Inventors: Robert Michael Dolezal
- Web page: https://patentgrep.com/patent/US20240202350A1

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A legacy resource is virtualized as a virtualized resource defined by features and capabilities set by an individual through a front-end user interface. Access rules are set on the virtualized resource based on the features and capabilities. When an access is requested to the virtualized resource, the corresponding access rules are enforced. Assuming there is no violation in the access rules, virtualized legacy resource services are overlaid on legacy resource services to cause the legacy resource services to perform any needed access operations on the corresponding legacy resource associated with the virtualized resource without changing any workflows processed by the legacy resource services.

## Claims

### Claim 1

A method, comprising:
expanding a first definition for first capabilities of a legacy resource in a second definition for second capabilities of a virtual resource;
assigning access rules to the virtual resource based on the second definition and the second capabilities;
linking the virtual resource to a legacy resource service associated with accessing the legacy resource;
enforcing the access rules during a first access operation on the virtual resource; and
causing the legacy resource service to perform a second access operation on the legacy resource based on performing the first access operation on the virtual resource maintaining the legacy resource in agreement with the first access operation by the legacy resource service performing the second access operation on the legacy resource.

### Claim 2 (depends on 1)

The method of claim 1, wherein expanding further includes receiving a virtual resource type from a user through a user interface, presenting available attributes to the user through the interface based on the virtual resource type, obtaining attribute selections from the available attributes provided by the user through the interface, and generating the second definition based on the virtual resource type and the attribute selections.

### Claim 3 (depends on 2)

The method of claim 2, wherein assigning further includes generating an alias identifier for the second definition and linking the alias identifier to the user and the second definition associated with the virtual resource.

### Claim 4 (depends on 3)

The method of claim 3 further comprising, providing the alias identifier to the user through the user interface.

### Claim 5 (depends on 4)

The method of claim 4, wherein linking further includes receiving a legacy resource identifier for the legacy resource from the user through the user interface and identifying the legacy resource service based on the legacy resource identifier.

### Claim 6 (depends on 1)

The method of claim 1, wherein enforcing further includes receiving an alias identifier for the virtual resource, access details, and the first access operation from a workflow that is associated with a transaction being processed that references the alias identifier for the virtual resource.

### Claim 7 (depends on 6)

The method of claim 6, wherein receiving further includes receiving the alias identifier, the access details, and the first access operation on a communication being monitored for a virtual resource type assigned to the virtual resource.

### Claim 8 (depends on 7)

The method of claim 7, wherein enforcing further includes enforcing additional access rules against the first access operation based on the communication port.

### Claim 9 (depends on 1)

The method of claim 1, wherein causing further includes:
processing an application programming interface (API) to provide a legacy identifier for the legacy resource, access details for the second access operation, and the second access operation to the legacy resource service causing the legacy resource service to perform the second access operation on the legacy resource using the access details.

### Claim 10 (depends on 9)

The method of claim 9, wherein processing further includes:
providing a second legacy resource identifier for a second legacy resource in the access details based on the second access operation.

### Claim 11 (depends on 10)

The method of claim 10 further comprising, providing at least one confirmation that the legacy resource service completed processing the second operation on the legacy resource upon notification received from the legacy resource service through the API.

### Claim 12 (depends on 1)

The method of claim 1, wherein causing further includes updating a ledger maintained for the virtual resource based on the first access operation and the second access operation.

### Claim 13

A method, comprising:
maintaining at least one alias account for at least one legacy account;
identifying a transaction being requested that makes a first reference to the at least one alias account;
enforcing rules and ensuring the transaction does not violate the rules;
performing a first action on the at least one alias account based on transaction details for the transaction;
at least modifying the transaction details to replace the first reference to the at least one alias account with a second reference to the at least one legacy account;
providing the modified transaction details to an existing workflow of a legacy resource service causing the transaction to be processed against the at least one legacy account using the modified transaction details; and
updating a ledger maintained for the at least one alias account based on the transaction.

### Claim 14 (depends on 13)

The method of claim 13, wherein identifying further includes obtaining the transaction as a predefined transaction that is processed when a predefined event is detected.

### Claim 15 (depends on 13)

The method of claim 13, wherein identifying further includes receiving the transaction from a workflow associated with at least two parties to the transaction.

### Claim 16 (depends on 13)

The method of claim 13, wherein enforcing further includes identifying the rules based on an alias account type assigned to the at least one account.

### Claim 17 (depends on 13)

The method of claim 13, wherein performing further includes performing a second action on an additional alias account based on the transaction details.

### Claim 18 (depends on 13)

The method of claim 13, wherein at least modifying further includes providing the modified transaction details as a transfer of funds between the at least one legacy account associated with a first party to the transaction and a second legacy account associated with a second party to the transaction, wherein the legacy resource service is a third-party transaction clearinghouse service.

### Claim 19

A system, comprising:
a server comprising at least one processor and a non-transitory computer-readable storage medium;
the non-transitory computer-readable storage medium comprising server executable instructions;
the server executable instructions, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
providing a front-end interface to define capabilities of at least one virtual resource overlaid on at least one legacy resource;
assigning customized access rules to the at least one virtual resource based on user-defined input provided through the front-end interface;
enforcing the customized access rules during first access operations that reference the at least one virtual resource;
causing a legacy resource service associated with the at least one legacy resource to perform second access operations against the at least one legacy resource based on processing the first access operations against the at least one virtual resource; and
maintaining an updated ledger that balances the first access operations performed on the at least one virtual resource with the second access operations performed on the at least one legacy resource by the legacy resource service.

### Claim 20 (depends on 19)

The system of claim 19, wherein the at least one virtual resource includes a single virtual resource and the at least one legacy resource includes two or more legacy resources.
