Private Ecosystem Controller for Secure App Data Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile communication systems face challenges in securely sharing proprietary or confidential applications, content, and data within private networks, as they often rely on central servers that limit third-party vendors' control over distribution and updates, and fragment memory resources into separate sandboxes, leading to inefficient resource usage and difficulty in data sharing between apps.

Innovation Solution

A private mobile communications ecosystem is implemented, allowing for a restricted network to distribute proprietary applications and data, integrating related apps into a centralized suite on the user device, and using an authorization mechanism to control access, thereby reducing redundant data storage and enhancing resource efficiency and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If central servers are used to distribute applications and data, then distribution control is simplified, but third-party vendors lose control over distribution and updates

Engineering Contradiction:
Improvedistribution controlVSAvoidvendor control
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system segments distribution control into two parts: central servers handle general distribution logistics, while ecosystem controllers at vendor devices manage vendor-specific control over their applications. This segmentation allows both centralized efficiency and decentralized vendor autonomy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Ecosystem controllers act as intermediaries between central servers and vendor applications. These controllers enable vendors to maintain control over their app distribution and updates while still utilizing central server infrastructure for broad distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If memory resources are fragmented into separate sandboxes for each app, then security is improved, but data sharing between apps becomes difficult and resource efficiency decreases

Engineering Contradiction:
ImprovesecurityVSAvoiddata sharing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system merges sandbox isolation with ecosystem-level data sharing by allowing applications within the same ecosystem to access shared data stores. This combines the security benefits of sandboxing with the efficiency of centralized data access for related applications.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Different data access policies are applied to different applications based on their ecosystem relationships. Applications within the same ecosystem gain enhanced data sharing capabilities while maintaining sandbox security boundaries, creating local quality variations in access permissions.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If each application is distributed separately through central servers, then distribution flexibility is improved, but users must search for and locate specific applications one-by-one

Engineering Contradiction:
Improvedistribution flexibilityVSAvoidapplication location time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Applications within an ecosystem are merged into a coordinated group that can be distributed and managed together. This allows users to access multiple related applications through a single ecosystem interface rather than searching for each application separately.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The ecosystem controller provides universal access points for multiple applications within the ecosystem. Users can locate and access any application in the ecosystem through the controller's unified interface, eliminating the need to search for each application individually.

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

4Device complexity

If central servers control application distribution, then distribution management is simplified, but vendors have little or no control over how their applications are distributed

Engineering Contradiction:
Improvedistribution managementVSAvoidvendor control
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

Distribution management is segmented between central servers handling logistics and ecosystem controllers handling vendor control. This segmentation resolves the contradiction by assigning different control aspects to different system components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamics allow flexible control allocation where ecosystem controllers can adapt vendor control mechanisms based on specific vendor needs while maintaining overall system coordination through central servers.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10630722B2System and method for sharing information in a private ecosystem
Publication Date: 2020.04.21 JPMORGAN CHASE BANK NA
  • US10630722B2 patent drawing
  • US10630722B2 patent drawing
  • US10630722B2 patent drawing

AI summary

A system and method are disclosed for controlling a restricted ecosystem of software applications. The method may include originating software applications from a vendor, associating a collection of the software applications with a user, controlling the distribution of the collection of software applications to the user, controlling access to the collection of software applications based on user credentials, and controlling the installing and updating of the collection of software applications. The method may additionally include executing a first software application from the collection of software applications, executing a second software application, and transferring data from the first software application to the second software application. The method may additionally include transferring data from the first software application to a web service.