Unified Application Interface for Multi-App Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile device setup processes are inefficient due to the need for multiple disjointed applications for configuration, lack of adaptability to changes, and a disjointed user experience, as well as the inability to communicate user actions effectively between applications.

Innovation Solution

A method where a primary application generates a unified graphical user interface (GUI) that incorporates user interface information from secondary applications using JSON or HTTP schema, allowing user input to be processed and communicated back to the respective applications, providing a unified and adaptable configuration experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single setup application is developed to integrate multiple applications' functionalities, then configuration efficiency is improved, but adaptability to changes and updates deteriorates

Engineering Contradiction:
Improveconfiguration efficiencyVSAvoidadaptability to changes
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the setup system into a container application and multiple independent embedded applications. Each embedded application maintains its own codebase and can be independently updated, while the container provides unified configuration capabilities. This segmentation allows both high-level integration benefits and individual adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The container application serves as a universal setup environment that can host and manage multiple different embedded applications through a standardized interface. This multi-functionality allows the system to maintain a single unified configuration process while supporting diverse application types and future updates.

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

2Ease of operation

If a single setup application integrates multiple applications, then user experience is improved, but visual consistency deteriorates due to disjointed appearance

Engineering Contradiction:
Improveuser experienceVSAvoidvisual consistency
Core Design Contradiction:
Ease of operationVSShape

Solution Approach 1:

The patent applies local quality by allowing each embedded application's user interface components to maintain their own visual characteristics and design patterns while being embedded within the unified container. This enables visual differentiation for each application's specific needs while preserving the overall unified structure.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The container application merges multiple embedded applications into a single unified interface framework. The merging process combines the individual application components with the container's unified navigation and control mechanisms, creating a cohesive user experience that maintains both individuality and unity.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If multiple disjoint applications are sequentially launched for configuration, then adaptability is improved, but user experience deteriorates due to disjointed appearance

Engineering Contradiction:
ImproveadaptabilityVSAvoiduser experience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The container application acts as an intermediary that mediates between the user and multiple embedded applications. It provides a unified interface layer that translates user actions into appropriate embedded application calls, maintaining a consistent user experience while enabling access to multiple specialized applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a nested structure where multiple independent embedded applications are contained within a single container application. This nesting allows each inner application to maintain its independence and adaptability while being presented through the outer container's unified interface, creating a hierarchical organization that resolves the contradiction.

Inventive Principle:
Principle #7Nested doll (Nesting)

4Device complexity

If a single setup application is used, then configuration process is simplified, but communication of user actions between applications deteriorates

Engineering Contradiction:
Improveconfiguration processVSAvoidcommunication of user actions
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent implements feedback mechanisms where the container application monitors and tracks user interactions with embedded applications. This feedback system captures user actions, transmits them appropriately between applications, and ensures that configuration information is preserved and communicated throughout the system, preventing information loss.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The container application creates and manages copies of configuration data and user action information as it passes between embedded applications. This copying mechanism ensures that user actions are preserved and accurately transmitted across application boundaries, maintaining information integrity while simplifying the overall configuration process.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9875116B2Sharing of a user input interface of an application session of one application between two or more applications
Publication Date: 2018.01.23 CELLCO PARTNERSHIP INC
  • US9875116B2 patent drawing
  • US9875116B2 patent drawing
  • US9875116B2 patent drawing

AI summary

A primary application and a secondary application installed on a mobile communication device are both configured to obtain input from a user of the device through an application session of the primary application. The primary application transmits a notification to cause the secondary application to begin execution in the background. The primary application further transmits a request for user interface (UI) information to the secondary application. Based on UI information received from the secondary application, the primary application generates a graphical user interface (GUI) including an interface for receiving user input relating to the secondary application. The generated GUI is displayed on the device in the application session of the primary application, and user input relating to the secondary application is received in the application session of the primary application. The primary application then transmits to the secondary application user input identified as relating to the secondary application.