Bridge Application for Secure Inter-Enterprise Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing inter-enterprise data communication systems face challenges in securely sharing data between different enterprise applications while preventing access by malicious applications, leading to inconvenience in legitimate data sharing.

Innovation Solution

A bridge application managed by a second Enterprise Mobility Management (EMM) server is used to facilitate inter-enterprise data communications by generating and validating tokens, enabling secure data exchange between enterprise applications through encryption and validation processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If strict security measures are implemented to prevent malicious applications from accessing enterprise data, then security is improved, but legitimate data sharing between enterprises becomes inconvenient

Engineering Contradiction:
ImprovesecurityVSAvoiddata sharing convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

A bridge application is introduced as an intermediary component that mediates between enterprise applications from different enterprises. The bridge application validates tokens, establishes secure channels, and facilitates data exchange while maintaining security policies, thus enabling legitimate inter-enterprise data sharing without compromising security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically changes security parameters such as token validation rules and channel encryption settings based on the specific interaction context. By adjusting these parameters, the system can allow legitimate data sharing while maintaining appropriate security controls, resolving the contradiction between strict security and sharing convenience.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If container separation is used to isolate enterprise applications, then security is improved, but inter-enterprise data communication becomes complex

Engineering Contradiction:
ImprovesecurityVSAvoidcommunication architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The bridge application serves as a mediator that operates within the container architecture to facilitate communication between isolated enterprise applications. It handles token validation, secure channel establishment, and data routing, thereby enabling inter-enterprise communication without requiring changes to the container isolation model.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The bridge application is designed as a universal component that can facilitate communication between any enterprise applications from different enterprises. It provides multi-functional capabilities including token validation, secure channel management, and data exchange, reducing the need for application-specific communication logic and simplifying the overall architecture.

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

Data Source

PatentUS10797890B2Providing inter-enterprise data communications between enterprise applications on an electronic device
Publication Date: 2020.10.06 MALIKIE INNOVATIONS LTD
  • US10797890B2 patent drawing
  • US10797890B2 patent drawing
  • US10797890B2 patent drawing

AI summary

Systems, methods, and software can be used to provide inter-enterprise data communications between enterprise applications on an electronic device. In some aspects, a method comprises: receiving, by a bridge application executing on an electronic device, an interoperation request for a first enterprise, wherein the interoperation request includes a first token and a second token; sending, from the bridge application to an application of the first enterprise, the first token, wherein the application of the first enterprise executes on the electronic device; receiving, by the bridge application from the application of the first enterprise, a certificate in response to the first token, wherein the certificate is encrypted by the second token; decrypting, by the bridge application, the certificate by using the second token; and validating, by the bridge application, the application of the first enterprise based on the decrypted certificate.