Component-Based Application Framework for Wireless Device Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing software applications for wireless devices is challenging due to device-specific APIs, limited resources, and the need for rewriting code for each device, leading to inefficiencies and increased development time.

Innovation Solution

A method and system for presenting standard device application data entities as built-in data components, using a component-based application model with a runtime environment that hosts applications, allowing access to standard data entities without device-dependent API invocations, and sharing code across devices through a common application framework.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional per-device application development is used to access SDADEs, then device-specific functionality is achieved, but development time and complexity increase significantly

Engineering Contradiction:
Improvedevice-specific functionalityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent creates a universal application framework that can access SDADEs across different device types through a common interface. The framework layer provides device-agnostic access methods, allowing the same application code to run on multiple device types without modification, thus reducing development time while maintaining device-specific functionality through the standardized access layer

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

2Adaptability or versatility

If traditional per-device application development is used to access SDADEs, then device-specific functionality is achieved, but code must be rewritten for each device

Engineering Contradiction:
Improvedevice-specific functionalityVSAvoidcode complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework provides a universal access interface that abstracts away device-specific API differences. Applications interact with a standardized interface rather than device-specific APIs, eliminating the need to rewrite code for each device while maintaining the ability to access device-specific SDADEs through the standardized layer

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

3Ease of operation

If device-specific APIs are used to access SDADEs, then direct access to device data is achieved, but resource consumption increases

Engineering Contradiction:
Improvedirect data accessVSAvoidenergy consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The framework acts as an intermediary layer between applications and device-specific SDADEs. It provides a standardized access interface that manages resource consumption efficiently by pooling and caching data where possible, reducing redundant access operations and optimizing energy usage while maintaining ease of access through the unified interface

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8391845B2System and method of presenting entities of standard applications in wireless devices
Publication Date: 2013.03.05 MALIKIE INNOVATIONS LTD
  • US8391845B2 patent drawing
  • US8391845B2 patent drawing
  • US8391845B2 patent drawing

AI summary

A method of presenting data entities of standard device applications in wireless devices is provided. Component-based applications are hosted on a wireless device providing an application runtime environment for hosting at least one component-based application. Component definitions are hosted for developing the component-based application. A standard data component implements a standard data component definition; the standard data component definition is embedded into the component-based application definition during development. The standard data component providing access to a standard device data entity by invoking device dependent APIs the standard data component presenting the standard device data entity as a user defined data component. The application runtime environment automatically making functionality available of the user defined data components available to standard data component.