Contextual Message Routing in Distributed Ledger Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing distributed ledger networks lack efficient mechanisms for contextual messaging and information routing based on message context and node capabilities, leading to suboptimal communication and data sharing among participants.

Innovation Solution

A method and system for contextual messaging in a distributed ledger network that involves identifying message context, retrieving node capabilities, and applying routing preferences to determine the receiving entity, using Transmission Control Protocol (TCP)/Remote Procedure Call (RPC) for secure communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If distributed ledger networks use traditional messaging mechanisms, then implementation is simpler, but routing efficiency and contextual relevance deteriorate

Engineering Contradiction:
Improverouting efficiencyVSAvoidmessaging system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-identifying node capabilities and storing routing preferences before messages are sent. The distributed application retrieves and analyzes node capabilities in advance, and routing preferences are established beforehand based on message context, enabling efficient routing decisions without complex real-time analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The distributed application acts as an intermediary between the sending entity and the receiving entity. It receives the message, identifies the context, retrieves node capabilities, applies routing preferences, and determines the appropriate receiving entity. This intermediary layer simplifies the overall system by centralizing the routing logic while maintaining compatibility with traditional messaging mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the system routes messages without considering node capabilities, then routing is faster, but message delivery reliability deteriorates

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidrouting decision time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-identifying node capabilities and storing routing preferences before messages are sent. The distributed application retrieves and analyzes node capabilities in advance, and routing preferences are established beforehand based on message context, enabling efficient routing decisions without complex real-time analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from message contexts and node capabilities to continuously improve routing decisions. The distributed application analyzes the context of each message, retrieves relevant node capabilities, and applies routing preferences that are refined based on previous routing outcomes and node performance feedback.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If the system implements contextual awareness for routing, then message routing accuracy improves, but system complexity increases

Engineering Contradiction:
Improverouting accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-identifying node capabilities and storing routing preferences before messages are sent. The distributed application retrieves and analyzes node capabilities in advance, and routing preferences are established beforehand based on message context, enabling efficient routing decisions without complex real-time analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The distributed application serves itself by autonomously identifying message contexts, retrieving relevant node capabilities, and determining optimal routing paths without requiring external intervention. The system self-manages the complexity of contextual analysis and capability matching, presenting a simplified interface to users.

Inventive Principle:
Principle #25Self-service

4Measurement precision

If the system retrieves and analyzes node capabilities for every message, then routing precision improves, but processing time increases

Engineering Contradiction:
Improverouting precisionVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-identifying node capabilities and storing routing preferences before messages are sent. The distributed application retrieves and analyzes node capabilities in advance, and routing preferences are established beforehand based on message context, enabling efficient routing decisions without complex real-time analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies local quality by retrieving and analyzing only the specific node capabilities relevant to the current message context, rather than analyzing all node capabilities uniformly. The distributed application selectively queries node capabilities based on the message type, subject, and required processing, reducing unnecessary processing time while maintaining routing precision.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12363029B2Systems and methods for contextual messaging and information routing in a distributed ledger network
Publication Date: 2025.07.15 JPMORGAN CHASE BANK NA
  • US12363029B2 patent drawing
  • US12363029B2 patent drawing
  • US12363029B2 patent drawing

AI summary

Systems and methods for contextual messaging and information routing in a distributed ledger network are disclosed. According to one embodiment, a method may include a distributed application executed by a sending entity node in a distributed ledger network: receiving a message or communication from a sending entity; identifying a context for the message or communication; retrieving capabilities of other nodes in the distributed ledger network; identifying potential receiving entities for the message or communication based on the capabilities; retrieving routing preferences for the sending entity; applying the routing preferences for the sending entity to identify a receiving entity from the potential receiving entities; and sending the message or communication to a receiving node for the receiving entity using the routing preferences, wherein the receiving node is configured to route the message or communication to the receiving entity using routing preferences for the receiving entity.