Service Request Format Registration to Reduce SOAP Overhead

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing protocols for exchanging service requests and responses between client and server systems, such as SOAP based on XML, incur significant processing and data transfer overhead due to the need for parsing and packaging structured representations.

Innovation Solution

A method where the client system sends a service request format indicating a service identifier and parameter identifiers in sequence, receiving a registration identifier, and then sends only the registration identifier and parameter values, eliminating the need for parsing and packaging, and the server system provides the service response format indicating the sequence of data values, reducing processing and transmission overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If structured representation protocols (XML/SOAP) are used to exchange service requests and responses, then service requests and responses can be exchanged between disparate client and server systems, but processing overhead and data transfer overhead increase

Engineering Contradiction:

Improvecompatibility between disparate systemsVSAvoidprocessing overhead

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the service request into two parts: a registered format definition (sent once) and actual parameter values (sent subsequently). This separation allows the system to exchange only essential data without redundant structural information, reducing processing overhead while maintaining compatibility.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary registration of service request formats between client and server systems. By pre-defining and registering the structure, tags, and expected parameters before actual service calls, the system eliminates the need for repeated parsing of structural information, thereby reducing processing overhead in subsequent interactions.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

Engineering Contradiction:

Improvecompatibility between disparate systemsVSAvoiddata transfer overhead

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts and separates the structural definition from the actual data payload. By taking out the format specification and sending it separately during registration, the subsequent service requests contain only the essential parameter values without redundant XML tags and structural information, significantly reducing data transfer overhead.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses the registered service request format as a template or copy that both client and server systems reference. Instead of transmitting the complete structured representation each time, systems refer to the pre-registered format definition and exchange only the varying parameter values, reducing network traffic.

Inventive Principle:

Principle #26Copying

3Reliability

If parsing and packaging operations are performed on service requests according to XML/SOAP conventions, then structured representations can be interpreted, but processing time increases

Engineering Contradiction:

Improvedata interpretation accuracyVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary registration of service request formats, tags, and expected parameter structures before actual service calls. This advance preparation allows both client and server systems to have the parsing rules cached and ready, eliminating the need for time-consuming parsing operations during actual service requests while maintaining accurate data interpretation.

Inventive Principle:

Principle #10Preliminary action

4Loss of information

If additional data tags are included in service requests to specify data attributes, then data meaning and attributes are clearly defined, but data transfer size increases

Engineering Contradiction:

Improvedata attribute informationVSAvoiddata transfer size

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts the tag definition and attribute specification from each individual service request and places it in the pre-registered format definition. This allows data attributes and meanings to be clearly defined once during registration, while subsequent service requests contain only the actual parameter values without repetitive tag information, minimizing data transfer size.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS7818431B2Efficient exchange of service requests and responses

Publication Date: 2010.10.19 ORACLE INT CORP

AI summary

A client system registers (with a server system) a service request format indicating the service identifier and the parameters (along with the sequence), and the server system responds with a registration identifier and a service response format specifying the parameters that will be contained in a corresponding service response. Thereafter, to request the service, the client system merely needs to send the parameter values along with the registration identifier. The server system merely sends the parameter values according to the response format. In an embodiment, the formats are generated as extensions to Simple Object Access Protocol (SOAP).