Private Mobile Ecosystem for Secure App Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile communication systems lack a mechanism for third-party vendors to securely and efficiently distribute and manage proprietary applications, content, and data across multiple platforms, leading to fragmented data storage, inefficient resource usage, and limited control over app updates and distribution.

Innovation Solution

A private mobile communications ecosystem that allows vendors to create a restricted network for distributing proprietary applications and data, integrating them into a centralized suite on user devices, enabling secure sharing and updating across platforms while reducing redundant data storage and enhancing user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a central communication server is used to distribute applications and data, then distribution simplicity is improved, but vendor control and restricted network distribution capability deteriorate

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

Solution Approach 1:

The system segments the distribution architecture into two parts: a public central server for general app distribution and a private restricted network for vendor-controlled proprietary app distribution. This allows vendors to maintain control over their proprietary applications while the central server continues to provide simplified distribution for public apps.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a vendor server as an intermediary between the central communication server and user devices. This intermediary enables vendors to control the distribution of proprietary applications within restricted networks while still leveraging the central server's distribution infrastructure for non-proprietary content.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If applications are distributed as discrete items through a central server, then distribution control is improved, but user convenience and resource efficiency deteriorate

Engineering Contradiction:
Improvedistribution controlVSAvoiduser convenience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent merges multiple discrete applications from the same vendor into a unified suite that can be distributed and managed as a single entity. Users can download and update entire suites of related applications simultaneously, improving convenience while maintaining vendor control over the complete application package.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system provides universal suite management functionality that works across different vendors and application types. The suite distribution mechanism is designed to be platform-agnostic, allowing any vendor to package and distribute multiple applications together through a standardized interface.

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

3Reliability

If data is stored locally in each application's sandbox, then data security is improved, but resource consumption and data sharing efficiency deteriorate

Engineering Contradiction:
Improvedata securityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges data storage into a centralized location that is accessible by multiple applications within a suite. Instead of each application maintaining separate local copies of proprietary data, the data is stored once and shared across all applications that need it, reducing redundant storage and improving efficiency while maintaining security through controlled access.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system introduces a suite container as an intermediary storage layer between the device's file system and individual applications. This intermediary manages data storage and retrieval for the entire suite, allowing applications to access shared data without direct file system access, thereby maintaining security while reducing resource consumption.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If applications are updated individually through a central server, then update control is improved, but update efficiency and user experience deteriorate

Engineering Contradiction:
Improveupdate controlVSAvoidupdate efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges the update process for multiple applications into a single suite update operation. When a suite is updated, all applications within that suite are updated simultaneously in one download and installation process, dramatically improving update efficiency while maintaining vendor control over the complete update package.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary packaging of multiple applications into a unified suite update package before distribution. This preliminary action allows the update to be deployed as a single atomic operation, ensuring that all applications in the suite are updated together and preventing partial update states that could leave the system in an inconsistent state.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9430211B2System and method for sharing information in a private ecosystem
Publication Date: 2016.08.30 JPMORGAN CHASE BANK NA
  • US9430211B2 patent drawing
  • US9430211B2 patent drawing
  • US9430211B2 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.