Hybrid-Cloud File Conversion for Cross-Platform Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing proprietary structured files in a hybrid-cloud environment is challenging due to compatibility issues across different platforms and the need for secure access, as these files can only be operated by specific software or hardware, and downloading them can be time-consuming if the client computer lacks the appropriate platform.

Innovation Solution

A system and methodology that utilize a hybrid-cloud environment with public and private clouds, employing public key/private key encryption and access control lists to securely convert and transmit proprietary structured files between different platforms, ensuring secure access and compatibility by determining the client's platform and converting the files accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary structured files are stored in a hybrid-cloud environment, then secure access and platform compatibility are improved, but file conversion complexity and processing time increase

Engineering Contradiction:
Improveplatform compatibilityVSAvoidfile conversion complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs file format conversion in advance before the user requests the file. When a file is uploaded, the server converts it to multiple platform-specific formats and stores these pre-converted versions. When a user requests the file, the system simply retrieves the already-converted format matching their platform, eliminating conversion delays at access time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary conversion layer between the stored proprietary files and user access. The server acts as a mediator that automatically detects the user's platform and retrieves or converts the appropriate format, shielding users from platform compatibility issues while managing conversion complexity centrally on the server.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If files are converted on-demand to match client platform, then adaptability is improved, but access time increases

Engineering Contradiction:
Improveplatform compatibilityVSAvoidfile access time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system converts files to multiple platform formats in advance during the upload process or during off-peak hours, storing these pre-converted versions alongside the original file. This preliminary conversion action ensures that when users request files, the appropriate format is already prepared and can be delivered immediately without on-demand conversion delays.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If encryption is applied to proprietary files, then security is improved, but access complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidaccess complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The encryption and decryption process is automated through the web interface. Users simply upload their encrypted proprietary files through the web form, and the server automatically handles the decryption, platform detection, format conversion, and file delivery without requiring users to manually manage encryption keys or conversion parameters. The system serves itself by managing the cryptographic operations transparently.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11445009B1Managing proprietary structured objects
Publication Date: 2022.09.13 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11445009B1 patent drawing
  • US11445009B1 patent drawing
  • US11445009B1 patent drawing

AI summary

Aspects of the invention include receiving, from a first client, a first object, determining a first file format for the first object, wherein the first file format is operable to run on a first platform, generating a catalog for the first object, wherein the catalog comprises data associated with the first object, and wherein the catalog for the first object is stored on a first server, receiving, from a second client, a request to access the data associated with the first object, determining a second platform operated by the second client, converting, on a second server, the first file format for the first object to a second file format, the second file format operable to run on the second platform, and transmitting the first object in the second file format to the second client.