Java Application Manager for State Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional JAVA applications executed on user devices, such as digital televisions and mobile communication terminals, operate independently, making it difficult to ensure continuity and information sharing between applications, limiting their expandability.

Innovation Solution

A method for managing JAVA applications that allows for state changes and information sharing between applications by issuing execution requests with specific execution type information, enabling seamless transitions between applications, such as pausing, killing, and restarting, using APIs like X2let, method invocation, resource support, and application manager APIs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If JAVA applications are executed independently on user devices, then each application can run autonomously, but continuity and information sharing between applications cannot be guaranteed

Engineering Contradiction:
Improveapplication independenceVSAvoidinformation sharing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an application manager as an intermediary component that mediates between independent JAVA applications and the operating system. This manager enables information sharing and continuity by controlling application lifecycle events (suspend, resume, destroy) and managing application states, while preserving the independence of individual applications through standardized API interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If conventional application models are used, then applications can be executed on embedded devices, but expandability and continuity between applications are limited

Engineering Contradiction:
Improveapplication execution capabilityVSAvoidapplication expandability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic application state management where applications can transition between different states (running, suspended, destroyed) based on execution type information. This dynamic approach allows applications to be paused and resumed, enabling continuity and expandability while maintaining ease of execution on embedded devices through the standardized application manager interface.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If one JAVA application is executed on a single screen, then the application can display content, but seamless transitions and information sharing between applications are difficult

Engineering Contradiction:
Improveapplication display capabilityVSAvoidapplication transition time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements preliminary suspension of the first application before executing the second application. By suspending rather than fully terminating the first application, the system preserves its state and enables rapid resumption, reducing transition time and allowing seamless switches between applications while maintaining display capabilities.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8347314B2Method for managing java applications
Publication Date: 2013.01.01 HERMES IP MANAGEMENT LLC
  • US8347314B2 patent drawing
  • US8347314B2 patent drawing
  • US8347314B2 patent drawing

AI summary

A method for managing JAVA applications executable in a user device provides an expandability for and a continuity between JAVA applications by changing states of the JAVA applications in execution and sharing information between the JAVA applications.