Plug-in Assembler for Heterogeneous Backend Server Communication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Developing software applications for wireless devices is challenging due to the diversity of devices, resource constraints, and complexity in communicating with various backend servers, particularly because existing solutions require extensive knowledge of communication protocols and result in inefficient and costly bandwidth usage.

Innovation Solution

A plug-in system for application development environments that facilitates communication with backend servers through a connector, using a schema-based description document to ensure interoperability, allowing developers to create applications that can interact with multiple backend servers without needing intimate knowledge of each server's specifics, and enabling extensibility to different backend servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If native applications are developed for specific wireless device platforms, then application performance and data persistence are improved, but device compatibility and development complexity increase

Engineering Contradiction:

Improvedata persistenceVSAvoiddevice compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments the application into platform-independent logic and platform-specific presentation layers. The authoring application creates standardized data models that are separated from device-specific rendering, allowing the same application logic to persist data reliably across different platforms while adapting presentation to each device type.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the authoring application and standardized data models) between the application logic and device-specific platforms. This intermediary translates platform-independent application requirements into platform-specific implementations, enabling data persistence without requiring separate native applications for each device type.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If multiple versions of the same application are developed for different platforms, then platform optimization is improved, but development time and maintenance complexity increase

Engineering Contradiction:

Improveplatform optimizationVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system creates a universal authoring application that can generate applications for multiple wireless device platforms simultaneously. The standardized data models and schema-based descriptions enable a single application development effort to produce optimized applications for different platforms, eliminating the need to develop and maintain separate application versions for each platform.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If SOAP protocol is used to interface with backend servers, then communication standardization is improved, but system complexity and bandwidth usage increase

Engineering Contradiction:

Improvecommunication standardizationVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the communication protocol complexity from the application layer and places it in the connector layer. The schema-based description documents define communication requirements at a high level, while the connector handles the detailed SOAP protocol implementation, separating concerns and reducing application complexity.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The connector acts as an intermediary between the application and backend servers, handling SOAP protocol communication. This intermediary translates standardized application requests into SOAP messages, shielding the application from protocol complexity while maintaining standardized communication with diverse backend servers.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Adaptability or versatility

If Web Service layer is added to interface with backend servers, then server accessibility is improved, but system complexity and functionality limitations increase

Engineering Contradiction:

Improveserver accessibilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the Web Service interface requirement from the core application logic and implements it through connectors that work directly with the authoring application. The schema-based description documents enable the application to access backend servers without requiring a separate Web Service layer, reducing system complexity while maintaining server accessibility.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS7624370B2System and method for facilitating development of an application and supporting access to a plurality of heterogeneous backend servers

Publication Date: 2009.11.24 MALIKIE INNOVATIONS LTD

AI summary

A plug-in is provided for use with an authoring application. The plug-in facilitates development of a wireless application in communication with a backend server via a corresponding connector. The plug-in comprises an interface and an assembler. The interface interfaces with the authoring application and receiving a desired inquiry from the authoring application to be posted to the backend server. The assembler creates a schema-based description document describing the inquiry in accordance with a set of predefined criteria for ensuring that the connector is able to interpret the description document.