Filesystem Communications Interface for Cross-Platform Data Exchange

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in enabling interoperability between computer applications operating on incompatible platforms, requiring substantial coding and resources, and often necessitate specialized knowledge, leading to delays and inefficiencies in data exchange.

Innovation Solution

A filesystem communications interface (FCI) device mounts filesystems on multiple computers, installs communications interface drivers, and converts data transfer commands between filesystem-based and network-based protocols, allowing seamless data transfer between applications without requiring programmers to understand specific protocols or APIs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If computer applications use different operating systems and proprietary communication methods to achieve interoperability, then data exchange between incompatible platforms is enabled, but device complexity and development resources increase significantly

Engineering Contradiction:

Improveinteroperability between incompatible platformsVSAvoidcoding requirements and development resources

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a filesystem communications interface (FCI) as an intermediary layer between applications on different platforms. The FCI translates filesystem-based communication calls into network-based protocols, enabling incompatible applications to exchange data without requiring custom integration code. This mediator handles protocol conversion, eliminating the need for developers to implement proprietary communication methods for each platform combination.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The FCI provides a universal communication interface that works across multiple operating systems and device types. By standardizing on filesystem-based APIs as the common interface and handling platform-specific translations internally, the system enables a single application design to communicate with diverse platforms without modification, reducing development complexity while maintaining broad adaptability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If custom communication interfaces are developed for each device type to ensure protocol compliance, then data exchange accuracy is maintained, but development time and production delays increase

Engineering Contradiction:

Improveprotocol adherence and data exchange accuracyVSAvoiddevelopment time and production delays

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The FCI performs protocol conversion and communication protocol handling in advance, before data exchange occurs. By pre-configuring translation rules and conversion logic within the FCI layer, the system ensures protocol compliance is automatically maintained without requiring real-time custom processing. This preliminary setup eliminates the need for time-consuming custom interface development for each device type while ensuring reliable data exchange.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If intermediary platforms are used to facilitate interoperability, then communication between incompatible applications is enabled, but programming complexity and specialized knowledge requirements increase

Engineering Contradiction:

Improveinteroperability capabilityVSAvoidprogramming complexity and knowledge requirements

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The FCI implements self-service by automatically handling protocol translation and communication protocol selection based on the target device type. Instead of requiring programmers to manually configure communication interfaces or learn multiple protocols, the FCI autonomously determines the appropriate translation strategy and executes it. This automation maintains interoperability capability while significantly reducing programming complexity and eliminating the need for specialized communication protocol knowledge.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS11625289B2Systems and methods for filesystem-based computer application communication

Publication Date: 2023.04.11 MASTERCARD INT INC

AI summary

A method of filesystem-based communication of computer applications is provided. The method implemented using a filesystem communications interface (FCI) computer device coupled to a first computer and a second computer on which computer applications are installed. The method includes mounting file systems on the first computer and second computer by installing communications interface drivers, receiving a data transfer command that includes a data unit from the first computer, identifying that the data transfer command corresponds to a filesystem-based data transfer protocol, generating another data transfer command by converting the first data transfer command into a first network-based data transfer protocol, receiving the data unit from the first computer, and transmitting, using the second communications interface driver, the data unit to the second computer application by the using a third data transfer command.