Application Gateway Data Mapping for Wireless Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing software applications for wireless devices is challenging due to the need for multiple platform-specific versions, resource-intensive browser applications, and inefficient data communication between devices and backend servers, particularly in the absence of schema transformation that optimizes data structure at the handheld level.

Innovation Solution

An application gateway system that facilitates message communication between wireless devices and backend servers using a schema-based internal format, with a transformer to translate data between compact and internal formats, enabling efficient data mapping and communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If browser-based applications are used for cross-platform compatibility, then adaptability to different devices is improved, but resource consumption and data transfer bandwidth requirements increase

Engineering Contradiction:
Improvecross-platform compatibilityVSAvoidresource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent introduces an application gateway as an intermediary component between wireless devices and backend servers. This gateway provides a standardized interface that mediates communication, allowing browser-based applications to interact with diverse backend systems without direct device-server connections. The gateway handles protocol translation and data formatting, reducing the resource burden on mobile devices while maintaining cross-platform compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system architecture is segmented into distinct layers: the presentation layer (browser-based application), the mediation layer (application gateway), and the data layer (backend servers). This segmentation allows each component to be optimized independently - the browser layer provides adaptability, the gateway reduces resource consumption through efficient protocol handling, and backend servers manage data processing.

Inventive Principle:
Principle #1Segmentation

2Productivity

If native applications are developed for specific wireless device platforms, then application optimization for the runtime environment is improved, but device complexity and memory resource requirements increase

Engineering Contradiction:
Improveapplication execution efficiencyVSAvoidplatform-specific development complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The application gateway provides a universal interface that works across multiple device platforms and backend server types. Instead of developing separate native applications for each platform, a single standardized application can communicate with the gateway, which then handles platform-specific protocols. This multi-functional approach maintains execution efficiency while reducing development complexity.

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

3Ease of operation

If data is transferred between wireless devices and backend servers without schema transformation, then communication simplicity is maintained, but data structure optimization at the handheld level is lost

Engineering Contradiction:
Improvecommunication simplicityVSAvoiddata communication efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The application gateway acts as a mediating transformation layer between wireless devices and backend servers. It receives data in one schema format from devices, transforms it according to predefined mappings, and outputs it in the appropriate format for backend servers. This intermediary transformation maintains ease of operation for developers while significantly improving data communication efficiency through optimized data structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically changes data parameters (schema formats, data structures, encoding schemes) based on the communication context. The gateway contains transformation rules that modify data parameters to optimize for the target system, whether that's a mobile device with limited resources or a backend server requiring specific data formats. This parameter transformation resolves the contradiction between simplicity and efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7586926B2System and method for generic data mapping between wireless component applications and application data sources
Publication Date: 2009.09.08 MALIKIE INNOVATIONS LTD
  • US7586926B2 patent drawing
  • US7586926B2 patent drawing
  • US7586926B2 patent drawing

AI summary

An application gateway is configured to facilitate message communication between an application executing on a wireless device and a backend server. The application gateway comprises a message interface, a backend connector and a transformer. The message interface facilitates communication between the wireless device and the application gateway in a compact format. The backend connector facilitates communication between the application gateway and the backend server using a schema-based internal format. The transformer translates data between the compact format and the internal format. The transformer further includes a transformer mapping document for correlating elements in the compact format with elements in the internal format.