Airlet Runtime Environment for Asynchronous Mobile Data Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing mobile device communication systems face challenges in providing seamless access to internet information and managing applications efficiently, particularly in environments with poor network connectivity, due to limitations in handling asynchronous data updates and inter-device communication.

Innovation Solution

The implementation of a Client Application Generation Engine (CAGE) and AirML language, which enables airlets to run on mobile devices, providing dynamic access to local data, asynchronous messaging, and abstracting device-specific functionalities, allowing airlets to operate independently of network connectivity and interact with servers through a high-level abstraction layer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If mobile devices use traditional web browsers with WAP and XML protocols for internet access, then devices can access internet information, but devices face limitations in handling asynchronous data updates and inter-device communication, especially in poor network conditions

Engineering Contradiction:

Improveapplication operation reliabilityVSAvoidnetwork environment adaptability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a runtime environment as an intermediary layer between the airlet application and the mobile device operating system. This runtime environment provides abstracted interfaces for file system access, device capabilities, and network communication, allowing airlets to operate independently of specific device implementations and network conditions. The runtime environment mediates between the high-level airlet code and the underlying platform complexities.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the operational parameters of mobile applications by transitioning from synchronous web-based protocols (WAP, XML) to an asynchronous event-driven model. Airlets use asynchronous messaging and can operate in both connected and disconnected modes, fundamentally changing how mobile applications handle data updates and user interactions across varying network conditions.

Inventive Principle:

Principle #35Parameter changes

2Productivity

If applications are designed to require server connectivity for data access, then data can be updated in real-time, but applications cannot operate in poor network conditions and users experience interruptions

Engineering Contradiction:

Improveapplication functionalityVSAvoidnetwork wait time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by enabling airlets to perform data access and processing operations locally on the mobile device without requiring real-time server connectivity. The runtime environment allows airlets to access local files, cache data, and execute operations independently, with server synchronization occurring asynchronously when connectivity is available. This eliminates network wait time for core application functionality.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Airlets are designed to be self-sufficient by implementing local data storage and processing capabilities. The runtime environment provides airlets with direct access to the device's file system and local resources, allowing applications to serve themselves without constant server intervention. Data is updated locally and synchronized with the server asynchronously, enabling continuous operation regardless of network conditions.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If mobile applications abstract device-specific functionalities, then applications become more portable across different devices, but the complexity of the abstraction layer increases

Engineering Contradiction:

Improvedevice compatibilityVSAvoidruntime environment complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The runtime environment implements universality by providing a standardized set of interfaces and APIs that work across different mobile device platforms. Instead of writing separate code for each device type, airlets use the runtime environment's abstracted interfaces for file access, device capabilities, and communication, which handle platform-specific variations internally. This single interface serves multiple device types.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent extracts device-specific complexity from the application logic and places it in the runtime environment layer. The runtime environment handles all platform-specific implementations, device capability variations, and system integrations, while airlets operate at a higher level of abstraction. This extraction isolates complexity in a manageable layer beneath the application code.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS7665094B2Systems and methods for mobile communication

Publication Date: 2010.02.16 ORACLE INT CORP

AI summary

A mobile communication system uses a runtime environment program which can communicate with a server. Applications are used with their own corresponding application data store. The application data store is persistent even when the applications are not running. The runtime environment program can obtain data from the server to update the application data store. The application can use the application data store. Messages can be cached at the mobile device and the server to allow for possible downtimes in the communication in the mobile unit and the server.