Integration Engine for Web File Management API Agnostic Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for integrating web-based file management systems with web-based applications require significant resources and time, as they often necessitate modifications to the application programming interface (API) of the service, making it cumbersome for developers to enable communication and data exchange between systems.

Innovation Solution

An API-agnostic integration method and system that uses an integration engine to facilitate communication between web-based file management systems and applications, allowing developers to configure services without altering the API of the web-based application, enabling seamless file management and service integration through a configuration interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the API of the web-based application is modified to enable integration with the file management system, then integration capability is improved, but development time and resources increase

Engineering Contradiction:
Improveintegration capabilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an integration engine as an intermediary component that sits between the web-based application and the file management system. This integration engine handles all communication and data exchange, allowing the application to interact with file management services without requiring modifications to the application's existing API. The integration engine translates and mediates between different protocols and interfaces, thus improving adaptability while avoiding the time-consuming process of modifying the core application code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the API of the web-based application is modified to enable integration with the file management system, then integration capability is improved, but resource consumption increases

Engineering Contradiction:
Improveintegration capabilityVSAvoiddevelopment resources
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The integration engine serves as a reusable intermediary component that eliminates the need for developers to invest significant resources in modifying application code for each integration scenario. By providing a standardized interface and handling integration logic centrally, it reduces the overall development resources required while maintaining high integration capability across multiple applications and services.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration engine is designed to be universal and multi-functional, capable of integrating various web-based applications with the file management system through a common interface. This universality means that once the integration engine is developed, it can be reused across multiple integration scenarios without requiring additional resource investment for each new integration, thus improving adaptability while conserving development resources.

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

3Loss of time

If an integration engine is introduced to facilitate communication without API modifications, then development time is reduced, but system complexity increases

Engineering Contradiction:
Improvedevelopment timeVSAvoidsystem architecture
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

While the integration engine does add a component to the system architecture, it provides significant benefits by eliminating the need for complex API modifications across multiple applications. The integration engine centralizes the complexity of integration logic in a single, manageable component with well-defined interfaces, making the overall system easier to maintain and extend compared to having scattered API modifications throughout multiple applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9519526B2File management system and collaboration service and integration capabilities with third party applications
Publication Date: 2016.12.13 BOX INC
  • US9519526B2 patent drawing
  • US9519526B2 patent drawing
  • US9519526B2 patent drawing

AI summary

A system and method for providing a file management service for collaboration is disclosed. The method for providing a file management service for collaboration, which may be implemented on a system, includes, for example, providing a client through which a user accesses a file through the file management service, further providing, by the file management service via the client, the user with collaboration capability of the file with other users, and/or controlling editing of the file by other users based on whether it is specified as being shared by the user. In one embodiment, the file management service further enables integration of a third-party service with the file management service and the third-party service is accessible for use with the file via the file management service.