Web Services Response Templates for Data Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web services face inefficiencies and challenges in managing information retrieval and changes, leading to 'response conundrums' where either excessive data is returned or multiple requests are needed, due to a lack of control over the information model in program-to-program communication.

Innovation Solution

The introduction of Web Services Response Templates (WSRTs) allows requestors to explicitly specify the information needed, ensuring only relevant data is returned, and enables seamless integration of new information without breaking client software, by using XML-based templates to control the form and quantity of information exchanged.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a web service returns all available information, then completeness of information is improved, but message size and data retrieval overhead increase

Engineering Contradiction:
Improvecompleteness of informationVSAvoidmessage size
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts only the specific information elements requested by the client from the complete data set, rather than returning all available information. This is achieved through response templates that specify exact data paths and formats, eliminating unnecessary data transmission while maintaining information completeness for the requested scope.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the information model into hierarchical elements that can be selectively retrieved. Response templates define specific segments of data to be returned based on client needs, allowing the system to divide the complete information set into manageable, selectively transferable units that reduce overall message size.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If a web service returns very specific information, then message size is reduced, but number of requests increases to retrieve all required information

Engineering Contradiction:
Improvemessage sizeVSAvoidnumber of requests
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The response template mechanism serves multiple functions simultaneously: it specifies data format, defines information selection criteria, and controls response structure. This multi-functionality allows a single request to retrieve comprehensive yet specific information, eliminating the need for multiple sequential requests while maintaining efficient message size.

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

Solution Approach 2:

The patent introduces dynamic response templates that can be customized for different client needs and data types. Templates can be configured to return varying levels of detail in a single response, adapting to specific information requirements without requiring additional requests, thus reducing time loss while maintaining message efficiency.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If a service adds new information to existing requests, then information availability is improved, but interface complexity increases

Engineering Contradiction:
Improveinformation availabilityVSAvoidinterface complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent changes the parameter of information representation by using standardized response templates with defined schemas. New information is incorporated by updating template parameters and schemas rather than modifying the interface structure, allowing information availability to increase while interface complexity remains stable through parameter-based evolution.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent uses template copying and instantiation to handle new information types. Rather than creating new interface structures, the system copies existing template patterns and adapts them to new data types, maintaining interface simplicity while improving information availability through reusable template structures.

Inventive Principle:
Principle #26Copying

4Loss of information

If a service returns all available information, then information availability is improved, but processing overhead increases

Engineering Contradiction:
Improveinformation availabilityVSAvoidprocessing overhead
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system extracts only the specific information elements required by the client response template, avoiding retrieval and processing of unnecessary data. This extraction mechanism reduces processing overhead by focusing computational resources on generating only the requested information while maintaining complete availability of the underlying data model.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary action by pre-defining response templates with specified data paths and formats. This allows the system to prepare and structure information in advance according to known client requirements, reducing processing overhead during actual request fulfillment while ensuring complete information availability according to the template specifications.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7702746B2Web services response templates
Publication Date: 2010.04.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US7702746B2 patent drawing
  • US7702746B2 patent drawing
  • US7702746B2 patent drawing

AI summary

Provided is a Web Services Response Template (WSRT) that addresses the problems of efficiency and robustness to change in Web Services response by allowing a requestor to explicitly specify, in a response template what information is to be returned by the request. A requestor of a web service gets just the information it needs; different requestors of the same operation may get different information; and a responder sends the requestor only what is asked for so there is no problem when new information becomes available. WSRTs are specifically designed to allow the type of control needed in program-to-program (P2P) communication, while being very efficiently and simply processed by a web service. Thus, WSRTs address difficulties that arise in typical distributed, P2P communication without adding much overhead or complexity to either a service requester or a service provider. The efficiency and flexibility afforded by WSRTs is essential to emerging enterprise architectures based on SOA (Service Oriented Architecture).