Distributed Ledger Load Balancing for Trustless Entity Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for collaborative operations between entities are centralized, allowing one entity to exert control over others, which is undesirable for trustless and decentralized transactions.

Innovation Solution

A distributed ledger system with smart contracts is used to facilitate cross-entity load balancing by identifying target entities and executing transactions without any single entity exerting control, using a distributed cryptographic ledger to ensure equitable distribution of loads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized system is used for collaborative operations, then control and coordination are simplified, but trustless and decentralized transactions cannot be achieved

Engineering Contradiction:
Improvecontrol and coordinationVSAvoidtrustless and decentralized transactions
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a distributed ledger as an intermediary mechanism that enables trustless transactions between entities without requiring centralized control. The ledger acts as a neutral mediator that all entities can verify, allowing decentralized collaborative operations while maintaining operational simplicity through automated smart contracts.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If conventional banking transactions are used for financial operations, then regulatory compliance is ensured, but additional actions and operations are required

Engineering Contradiction:
Improveregulatory complianceVSAvoidadditional actions and operations
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service through smart contracts that automatically execute financial transactions and compliance checks on the distributed ledger. The system performs regulatory compliance verification autonomously through coded rules, eliminating the need for manual banking operations while maintaining reliability through automated enforcement of compliance requirements.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If one entity exerts control over other entities during collaborative operations, then coordination is centralized, but trustless operations cannot be achieved

Engineering Contradiction:
ImprovecoordinationVSAvoidlack of trustless operations
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent segments control authority across multiple independent entities that each operate their own nodes on the distributed ledger. No single entity has centralized control; instead, coordination emerges from the collective verification and consensus mechanisms of the distributed network, enabling trustless operations while maintaining ease of coordination through standardized protocols.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20260039467A1Cross-entity load balancing using a distributed ledger
Publication Date: 2026.02.05 CHANGE HEALTHCARE HOLDINGS LLC
  • US20260039467A1 patent drawing
  • US20260039467A1 patent drawing
  • US20260039467A1 patent drawing

AI summary

Systems and methods for performing cross-entity load balancing operations using a distributed ledger are provided herein. One example method includes invoking, by a first entity, a smart contract stored on a distributed ledger. Invoking the smart contract causes the smart contract to identify a target entity from a plurality of candidate entities of the plurality of entities, and generate a token and data associated with the target entity. The smart contract executes transactions that are associated with invocations between the plurality of entities such that no one entity of the plurality of entities executes control over any other of the entities. The method also includes receiving the token and the data associated with the target entity, initiating an API call to the target entity using the token and the data associated with the target entity, and receiving, from the target entity or smart contract, a response to the API call.