View Port Scheme for Multitasking on Limited Mobile Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile devices can only interact with one application at a time, limiting the ability to multitask and requiring separate versions of MIDlets for different functionalities, which is inefficient and restrictive for legacy applications.

Innovation Solution

The implementation of a View Port concept using Java MIDlets, comprising a Viewer, Canvas, and Registrar components, allows multiple applications to be displayed and interacted with simultaneously by allocating screen space dynamically and providing focus awareness, enabling legacy applications to function within the framework with minimal modification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If only one application controls the UI at a time, then the device maintains simple application execution, but the user cannot multitask and must switch between applications

Engineering Contradiction:
Improvemultitasking capabilityVSAvoidapplication execution management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The display screen is segmented into multiple display areas, with each application assigned to a specific area. This allows multiple applications to be displayed simultaneously in separate regions rather than requiring full-screen exclusive mode, enabling multitasking while maintaining manageable application execution through the Display Manager's coordination of each application's display area.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If legacy applications are converted to support multiple display areas, then multitasking is enabled, but the conversion process becomes complex and time-consuming

Engineering Contradiction:
Improvemulti-display area supportVSAvoidapplication conversion process
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The Display Manager acts as an intermediary layer between the operating system and legacy applications. It automatically manages display area allocation and coordinates multiple applications without requiring modifications to the applications themselves. This mediator approach enables legacy applications to function in a multitasking environment while maintaining their original code, thus avoiding complex conversion processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Area of stationary object

If the entire display area is allocated to a single application, then the application has full screen real estate, but other applications cannot be displayed simultaneously

Engineering Contradiction:
Improvedisplay area allocationVSAvoidapplication execution efficiency
Core Design Contradiction:
Area of stationary objectVSProductivity

Solution Approach 1:

The display area allocation is made dynamic rather than static. The Display Manager dynamically assigns and adjusts display areas for multiple applications based on their needs and user requirements. This dynamic allocation allows the entire display area to be utilized efficiently by multiple applications simultaneously, improving productivity while ensuring each application receives appropriate screen real estate.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9146651B1Displaying multiple applications on limited capability devices
Publication Date: 2015.09.29 T MOBILE INNOVATIONS LLC
  • US9146651B1 patent drawing
  • US9146651B1 patent drawing
  • US9146651B1 patent drawing

AI summary

A method, system, and media are provided for a combination of Java MIDlets, or applications, implementing a “View Port” concept, which allows the user interface of a mobile device to be leveraged for multiple tasks. The View Port provides access to multiple applications when previously interaction with only one application could be carried out at any one time. A View Port scheme also removes the need for two versions of a MIDlet, as a streamlined version of the application is no longer needed. This implementation allows legacy applications to function within the framework as well.