Web Service Aggregation via Automatic Interface Generation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for aggregating web services require programmers to write customized code and distribute client applications to each endpoint, which is time-consuming and platform-specific, limiting the flexibility in developing complex applications.

Innovation Solution

A method that automatically generates a user interface for aggregating web services by processing web service descriptions to identify inputs and outputs, allowing for automatic invocation of web services without the need for customized code, using predetermined naming conventions and user interactions to infer relationships between services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If customized client applications are written to aggregate web services, then web service aggregation functionality is achieved, but development time and programming skill requirements increase

Engineering Contradiction:

Improveweb service aggregation capabilityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables automatic generation of client applications that aggregate web services without requiring programmers to write customized code. The framework automatically discovers web service relationships, generates appropriate aggregation logic, and creates deployable client applications, allowing the system to serve itself in the application generation process.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The framework performs preliminary analysis of web service descriptions to identify input-output relationships and aggregation opportunities before client application generation. By pre-processing web service metadata and establishing service composition models in advance, the system reduces the time required for actual application development and deployment.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If customized client applications are distributed to each endpoint, then web service aggregation is implemented, but deployment complexity and platform-specific customization increase

Engineering Contradiction:

Improveweb service aggregation functionalityVSAvoiddeployment complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework generates universal client applications that can be deployed across multiple platforms and endpoints without requiring platform-specific customization. The generated applications use standardized interfaces and abstraction layers that work across different operating systems and devices, reducing deployment complexity while maintaining broad adaptability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If manual code writing is required for web service aggregation, then aggregation logic can be customized, but programming skill requirements and maintenance burden increase

Engineering Contradiction:

Improveaggregation logic flexibilityVSAvoidease of development

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The framework acts as an intermediary between web service descriptions and client application code. It automatically translates web service metadata and aggregation requirements into executable client applications, eliminating the need for programmers to manually write aggregation logic while preserving the ability to customize aggregation behavior through configuration rather than code.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Adaptability or versatility

If platform-specific client applications are created, then web services can be aggregated for specific platforms, but development time and skill requirements increase

Engineering Contradiction:

Improveplatform-specific aggregation capabilityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The framework generates platform-agnostic client applications that can operate across multiple platforms without requiring separate development efforts. The universal application structure adapts to different platforms through configuration rather than code modification, reducing development time while maintaining platform-specific aggregation capabilities.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7552170B2Apparatus and method for aggregating web services

Publication Date: 2009.06.23 MALIKIE INNOVATIONS LTD

AI summary

An apparatus and method for aggregating web services in generating a user interface for a computing device. Web service descriptions are received that define a web service interface to each of a plurality of web services. The web service descriptions are processed to identify inputs to first web services obtainable by invoking one or more second web services. A user interface is generated for the computing device that aggregates these first and second web services. By identifying instances in which the input to one web service may be obtained by invoking another web service, a user interface which aggregates these web services may be automatically generated.