Code-Independent Graph Execution Through Data-Driven Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional computing systems require continuous code changes and recompiling, lack modularity, and are not easily portable across different environments due to reliance on external code bases, making them inefficient for continuous function and modular code changes.

Innovation Solution

A computing environment where graph structures are driven by data flow through interconnected nodes, independent of an external code base, with minimal code in each node to interface with the operating system, allowing for modular, asynchronous, and context-dependent operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional code-based graph structures are used, then the system can perform complex operations, but the system requires external code bases and recompiling for any changes

Engineering Contradiction:
Improvecontinuous function capabilityVSAvoidrun-stop and recompiling time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent extracts the execution control from external code bases and relocates it to the graph structure itself. The graph becomes self-executing through data flow, eliminating the need for external code interpretation and recompiling. This allows continuous operation without time loss to compilation cycles.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements dynamic execution where the graph structure can adapt and reconfigure itself based on data flow requirements. The system transitions from static code-based execution to dynamic data-driven execution, enabling continuous modification without recompiling by allowing the graph topology and data flows to change at runtime.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If traditional code-based graph structures are used, then the system can execute operations, but the code is not modular and changes require recompiling

Engineering Contradiction:
Improvemodular code changesVSAvoidcode modularity
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the system into independent nodes and data flows within the graph structure. Each node represents a discrete functional unit that can be modified independently without affecting the entire system. This segmentation enables modular changes where individual nodes can be added, removed, or modified without requiring recompilation of the entire code base.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a dynamic graph structure where connections and data flows can be reconfigured at runtime. This dynamic topology allows modular adaptation of system functionality without code recompiling, as the graph can dynamically rewire connections between nodes to implement new functions or modify existing ones.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If traditional graph structures with external code bases are used, then the system can perform operations, but the system is not portable across platforms

Engineering Contradiction:
Improveplatform independenceVSAvoidcode portability
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent extracts platform-specific code dependencies from the graph structure by implementing a platform-independent core that uses standard data flow mechanisms. The graph structure itself becomes the universal interface, allowing the same graph to execute on different platforms without code modification, as the data flow model translates to platform-specific implementations automatically.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a universal graph execution model that can operate across multiple platforms through a common data flow interface. The graph structure serves as a universal representation that can be instantiated on different operating systems and hardware architectures, providing platform independence while maintaining full functionality through the standardized data-driven execution model.

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

4Adaptability or versatility

If traditional code-based systems are used, then the system can execute functions, but extensive code rewriting is required for portability

Engineering Contradiction:
Improvecross-environment operationVSAvoidcode rewriting effort
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the execution logic from platform-specific code and relocates it to the graph structure's data flow mechanisms. This extraction eliminates the need for extensive code rewriting when porting, as the graph structure itself becomes the portable artifact that carries the execution logic independently of any single platform's code base.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements a universal graph execution model that serves as a single portable implementation across all target environments. Rather than requiring separate code bases for different platforms, the same graph structure can be deployed universally, with platform-specific details handled by the execution engine's translation layer, thereby eliminating extensive code rewriting efforts.

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

Data Source

PatentUS20250217124A1Code-independent graph technology
Publication Date: 2025.07.03 CONTRAST INC
  • US20250217124A1 patent drawing

AI summary

A computing environment of the invention comprises a graph structure, or multiple interconnected graph structures, the behavior of which is driven by data flow through interconnected nodes, independent of an external code base. The computer system may include a plurality of interconnected nodes in which data flow between the nodes drives execution of one or more functions and wherein code within the system is restricted to said nodes, each of which performs a dedicated function and an engine to drive communication between said system and operating hardware. Data are injected into a node and the node responds by outputting a value (data) to one or more subsequent nodes. Those nodes, in turn, output a behavior that is dependent upon the value (data) they received from one or more other nodes. Thus, it is the data that drives operation of the graph and not a traditional code stack.