Web Storage Format Conversion for Third-Party Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web-based storage systems often restrict access to native files, making it difficult for third-party applications to access and utilize file content due to format incompatibility and proprietary concerns, as raw content is not directly exposed.

Innovation Solution

A system and method that convert native files into exportable formats compatible with third-party applications, allowing read-only access while maintaining proprietary integrity, by cross-referencing lists of exportable and importable formats and user input for format selection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If native files are restricted to maintain proprietary integrity, then data security is improved, but third-party application accessibility deteriorates

Engineering Contradiction:
Improveproprietary data integrityVSAvoidthird-party application compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments the file access process into two distinct parts: the original native file remains protected and unchanged, while a separate converted representation is generated for third-party applications. This segmentation allows the proprietary file to maintain its integrity while providing accessible copies to external applications.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates a converted copy of the native file in a format compatible with third-party applications. This copy contains the necessary content representation while the original proprietary file remains intact and protected. The copying mechanism enables accessibility without compromising the source data.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If format conversion is implemented to enable third-party access, then application compatibility is improved, but system complexity deteriorates

Engineering Contradiction:
Improveapplication compatibilityVSAvoidconversion system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a universal conversion mechanism that can handle multiple file formats through a single integrated process. The conversion system is designed to work with various native formats and produce universally compatible output formats, reducing the need for multiple specialized conversion tools and simplifying the overall system architecture.

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

3Ease of operation

If direct access to native files is provided, then application functionality is improved, but data security deteriorates

Engineering Contradiction:
Improvefile access convenienceVSAvoidproprietary data exposure
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system introduces a conversion process as an intermediary between the native file and third-party applications. This intermediary layer transforms the proprietary format into a compatible format without exposing the original file, thereby maintaining security while enabling convenient access through the converted representation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2864900B1System and method for end-to-end exposure of exported representations of native data types to third-party applications
Publication Date: 2020.12.09 GOOGLE LLC
  • EP2864900B1 patent drawingFigure 1
  • EP2864900B1 patent drawingFigure 2
  • EP2864900B1 patent drawingFigure 3

AI summary

Systems and methods are disclosed herein for exporting a file to an application. A processor receives a request from a user for access to a file stored on a web-based storage system. The request includes a designation of an application to open the file, and the file is associated with a native format. The processor determines that the application is not configured to import the file in the native format and determines whether the file can be converted to an importable format that can be imported by the application. The processor converts the file from the native format to the importable format and exports the converted file in the importable format to the application, which opens the converted file.