Semantic Rules Engine for Web Service Interface Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Web services require human intervention for integration and interface modification, making them cumbersome to utilize and adapt, even with standardized protocols like SOAP, WSDL, and UDDI, due to the need for manual analysis and coding to handle message semantics and interface changes.

Innovation Solution

A semantic interpretation specification is used to automatically generate interfaces with distributed computing services by entering rules into a rules engine, such as JESS, allowing dynamic discovery and interaction with Web services without manual programmer intervention, using ontologies to define message structure and vocabulary and semantic interpretation rules to handle message exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual analysis and coding are used to integrate Web service interfaces, then interface integration can be achieved, but the process becomes cumbersome and requires continuous human intervention for modifications

Engineering Contradiction:
Improveinterface integration reliabilityVSAvoidinterface integration ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables self-service by automatically generating interface integration code through semantic interpretation of service descriptions. The generator component creates ready-to-use integration code without requiring manual programming, allowing the system to serve itself in the interface integration process.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A semantic interpretation layer acts as an intermediary between Web service descriptions and integration code. This mediator translates service interfaces into executable integration logic, eliminating the need for direct manual coding while ensuring reliable integration through structured semantic processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If standardized Web service protocols (SOAP, WSDL, UDDI) are used, then distributed data access is enabled, but manual modification is still required when services or interfaces change

Engineering Contradiction:
Improvedistributed data access capabilityVSAvoidtime for manual modification
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system implements dynamic adaptation by continuously monitoring Web service interface changes and automatically regenerating integration code. When services or interfaces change, the semantic interpretation layer detects modifications and updates the integration logic without manual intervention, making the system adaptable to changing conditions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

A feedback mechanism monitors Web service interface changes and triggers automatic code regeneration. The system continuously checks for interface modifications and feeds this information back to the code generator, which then updates the integration code accordingly, eliminating manual modification time.

Inventive Principle:
Principle #23Feedback

3Ease of manufacture

If Web services are implemented as self-contained modular applications, then service reusability is improved, but the effort to analyze and manually integrate interfaces increases

Engineering Contradiction:
Improveservice reusabilityVSAvoidinterface integration complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system replaces manual mechanical coding processes with automated semantic interpretation. Instead of manually analyzing and coding interface integrations, the system uses semantic processing to automatically generate integration code from service descriptions, reducing integration complexity while maintaining service reusability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The semantic interpretation layer provides universal functionality by handling diverse Web service interfaces through a common processing mechanism. This universal approach allows the system to integrate different service types using the same automated process, reducing overall integration complexity while preserving service modularity and reusability.

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

Data Source

PatentUS7607136B2Method and apparatus for interfacing with a distributed computing service
Publication Date: 2009.10.20 VALTRUS INNOVATIONS LTD
  • US7607136B2 patent drawing
  • US7607136B2 patent drawing
  • US7607136B2 patent drawing

AI summary

A method, system, and apparatus is disclosed for interfacing with a distributed computing service. A semantic interpretation specification can be accessed that describes a behavior used to interface with the distributed computing service. The semantic interpretation specification is entered into a rules engine. A set of procedures is obtained from the rules engine for interacting with the distributed service. An interface with the distributed computing service can be formed using the set of procedures.