Data Control Ledger Error Correction for User Account Status

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network devices in data communication environments face challenges in controlling data leakage and unauthorized access, as compromised devices can exploit connections to exfiltrate data or upload malicious content, posing security risks due to direct interactions with provisioning service devices.

Innovation Solution

Implementing a data control ledger system that tracks and manages service requests, creating an immutable log to monitor changes in user accounts, and using an integrated architecture to compartmentalize data control ledgers across multiple groups, ensuring end-to-end tracking and error correction, thereby preventing direct modification or exfiltration by compromised network devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If network devices interact directly with provisioning service devices, then service requests can be processed efficiently, but network security is compromised and data leakage risks increase

Engineering Contradiction:
Improveservice request processing efficiencyVSAvoidnetwork security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces data control ledgers as intermediary components between network devices and provisioning service devices. These ledgers store and manage service request information, allowing network devices to submit requests to the ledger rather than directly to provisioning service devices. This intermediary layer maintains security by preventing direct access to sensitive provisioning services while enabling efficient request processing through the decentralized ledger system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If centralized data control is implemented, then security is improved, but system complexity increases

Engineering Contradiction:
Improvenetwork securityVSAvoiddata control system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data control system into multiple distributed ledgers, each managed by different entities or groups. Rather than implementing a single centralized control system, the solution divides the ledger infrastructure into separate, manageable units that can operate independently. This segmentation reduces the complexity burden on any single component while maintaining overall system security through the collective ledger network.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If data control ledgers track all service requests, then accountability is improved, but information storage requirements increase

Engineering Contradiction:
Improveaccountability trackingVSAvoiddata storage volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent implements a distributed ledger system where multiple nodes maintain copies of the service request data. Rather than centralizing all tracking information in a single repository, each participant in the network holds a copy of the relevant ledger data. This copying approach enables comprehensive accountability tracking across the network while distributing storage requirements, preventing any single system from becoming a storage bottleneck.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11593351B2Error correction for data control ledgers
Publication Date: 2023.02.28 BANK OF AMERICA CORP
  • US11593351B2 patent drawing
  • US11593351B2 patent drawing
  • US11593351B2 patent drawing

AI summary

A device configured to receive a first current status for a user account from a provisioning service device. The device is further configured to query a status log using to determine a second current status of the user account. The device is further configured to compare the first current status for the user account from the provisioning service device to the second current status of the user account in the status log, to determine the first current status for the user account does not match the second current status of the user account, and to update one of the status log and the provisioning service device in response to determining that the first current status for the user account does not match the second current status of the user account.