Network Data Process Verification with Derived Keys and Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex networked data processing systems, verifying data processes for clients without revealing their identity or execution details is challenging, especially when multiple computing resources handle high volumes of data processes with conflicting motivations and potential information leakage.

Innovation Solution

A system and method for managing data processes using machine-interpretable instructions that generate child requests with derived keys, allowing supervision and encryption to verify and monitor the execution of parent processes across networked resources while maintaining anonymity and confidentiality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data processes are routed through multiple computing resources for execution, then processing capability and system flexibility are improved, but verification difficulty and information security risks increase

Engineering Contradiction:
Improvesystem flexibilityVSAvoidverification difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where supervisors receive execution results from computing resources and send verification requests back to instructors. The system continuously monitors and verifies data processes by routing verification requests through the same multi-resource path, ensuring that each computing resource's actions are tracked and confirmed. This feedback loop resolves the verification difficulty by providing structured return paths for validation without changing the forward routing flexibility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces supervisors as intermediary entities that mediate between instructors and computing resources. Supervisors receive data processes from instructors, route them to appropriate computing resources, and then verify the execution results before returning them to instructors. This intermediary layer simplifies verification by centralizing the monitoring function, allowing instructors to trust the supervisor's validation without needing to directly verify each resource's output.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If client identity and execution details are concealed to maintain security, then information confidentiality is improved, but verification capability deteriorates

Engineering Contradiction:
Improveinformation confidentialityVSAvoidverification capability
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent segments information into different levels of confidentiality. Client identities and sensitive execution details are concealed from public view and even from most system participants. However, verification-critical information such as process identifiers, routing paths, and execution results are segmented and shared selectively with supervisors and authorized parties. This segmentation allows the system to maintain overall confidentiality while providing targeted verification capabilities to those who need them.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing different information visibility to different system participants. Instructors have full visibility of their own data processes, supervisors have visibility of routing and execution details for verification purposes, but computing resources and other participants only see what is necessary for their specific functions. This localized information distribution maintains confidentiality where needed while enabling verification where required.

Inventive Principle:
Principle #3Local quality

3Reliability

If multiple intermediaries are introduced to route and verify data processes, then system security and verification capability are improved, but system complexity increases

Engineering Contradiction:
Improvesystem securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent makes supervisors multi-functional entities that perform multiple roles: routing data processes from instructors to computing resources, monitoring execution in real-time, verifying results, and managing verification requests. By consolidating these functions into a single intermediary type, the system avoids the complexity of multiple specialized intermediaries while maintaining comprehensive security and verification capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent implements preliminary action by having supervisors establish verification protocols and routing paths before data processes are executed. Verification criteria, authorized computing resources, and expected outcome parameters are pre-configured and validated. This preliminary setup reduces runtime complexity by avoiding dynamic decision-making during execution, as the verification framework is already in place when processes begin.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12388766B2Verification of data processes in a network of computing resources
Publication Date: 2025.08.12 ROYAL BANK OF CANADA
  • US12388766B2 patent drawing
  • US12388766B2 patent drawing
  • US12388766B2 patent drawing

AI summary

A method for managing data processes in a network of computing resources includes: receiving at least one child request being routed from an intermediary device to at least one corresponding destination device, the at least one child request requesting execution of at least one corresponding child data process, each of the at least one child data process for executing at least a portion of the at least one parent data process from an instructor device, and each of the at least one child request including a destination key derived at least in part from the at least one instructor key; storing the at least one child request in at least one storage device; modifying the at least one child request upon receiving a child request modification signal; and generating signals for communicating the child requests to one or more requesting devices.