Isolated Workspace Platform for Cross-System Document Transformation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing software solutions for document exchange and transaction processing are cumbersome, requiring individual customization for each transaction party, are incompatible across systems, and lack flexibility in handling diverse transaction formats and requirements, leading to inefficiencies and disruptions.

Innovation Solution

A platform service that provides isolated workspaces for clients, transforming document formats, managing software packages, and enabling distributed channel communication to facilitate seamless transactions across incompatible systems, with features like adapter development, authentication, and a user-friendly interface for mapping logic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If standardized document exchange software is implemented, then transaction efficiency is improved, but individual customization requirements increase system complexity

Engineering Contradiction:

Improvetransaction efficiencyVSAvoidsystem customization complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system segments transaction processing into standardized protocols and customizable adapters. Core document exchange follows standard formats while party-specific requirements are handled by separate adapter modules, allowing efficiency through standardization without forcing customization into the core system.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

An intermediary platform is introduced between transaction parties and the document exchange system. This platform provides standardized interfaces while accommodating individual party requirements through configuration and adapter layers, reducing the complexity burden on individual implementations.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If software is individually customized for each transaction party, then transaction-specific requirements are met, but compatibility across different systems deteriorates

Engineering Contradiction:

Improvetransaction requirement fulfillmentVSAvoidsystem compatibility

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements a universal standardized protocol layer that handles common document exchange requirements across all transaction parties. This universal layer ensures compatibility while allowing party-specific adapters to handle specialized requirements, maintaining both versatility and reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Different parts of the system have different levels of customization. The core exchange protocol maintains uniform quality for compatibility, while local adapter components provide customized quality for specific party requirements. This local quality approach allows adaptability without compromising overall system compatibility.

Inventive Principle:

Principle #3Local quality

3Adaptability or versatility

If all software versions and packages are prepared for each client, then service coverage is improved, but resource consumption increases

Engineering Contradiction:

Improveservice coverageVSAvoidsoftware resource consumption

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Multiple software versions and packages are merged into a single standardized platform. Instead of maintaining separate software instances for each client, the system combines functionality into unified components that serve multiple clients, improving service coverage while reducing overall resource consumption.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system uses configuration copying and parameter inheritance instead of full software duplication. Client-specific variations are achieved by copying and customizing configuration files and parameters rather than distributing complete software packages, reducing resource consumption while maintaining service coverage.

Inventive Principle:

Principle #26Copying

4Reliability

If the system is designed for high availability, then service continuity is improved, but system complexity increases

Engineering Contradiction:

Improveservice continuityVSAvoidsystem architecture complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Failover mechanisms and backup systems are configured in advance during system setup. Instead of implementing complex real-time complexity management, the system prepares redundancy and failover paths beforehand, achieving high availability through pre-configured simple structures rather than complex dynamic management.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250244961A1Apparatus for providing application service, method of providing application service, and storage medium storing program executable by computer providing application service

Publication Date: 2025.07.31 INSPIEN

AI summary

Provided is a method of providing the application service including receiving a channel request for transmitting and receiving information from a client in a computing system configured to manage a platform for providing the client with workspaces isolated from each other in which application packages are executed, and providing, by the client, a platform service for transforming the application packages in the workspaces.