SOA HTTP Request Parameter Segmentation for Network Overhead Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Service-Oriented Architecture (SOA) systems, the lack of data length restrictions in HTTP POST requests leads to excessive network overhead due to large data transmissions, causing network congestion and decreased processing efficiency.

Innovation Solution

A method and apparatus that assign intermediate parameters to replace target parameters with longer data lengths in HTTP requests exceeding a preset threshold, reducing the data length of the converted HTTP request and minimizing data transmission across the SOA system, thereby decreasing network overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If HTTP POST requests are used without data length restrictions in SOA systems, then components can transmit complete and accurate data, but network overhead increases excessively due to large data transmission volumes

Engineering Contradiction:
Improvedata completenessVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the original HTTP request into two parts: a converted HTTP request with intermediate parameters for transmission, and the original request with target parameters stored locally. This segmentation allows components to transmit only lightweight intermediate parameters rather than complete large datasets, reducing network overhead while maintaining data accessibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediate parameters as mediators between components. These intermediate parameters serve as references or pointers to the actual target parameters stored in local databases. Instead of transmitting large target parameters across the network, components exchange small intermediate parameters that locally resolve to the full data, thus reducing network overhead while preserving data completeness.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If large amounts of data are transmitted across components in the SOA system, then complete information is available for processing, but network congestion occurs and processing efficiency decreases

Engineering Contradiction:
Improveinformation completenessVSAvoidprocessing efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent divides information storage and transmission into two segments: lightweight intermediate parameters are transmitted across the network for information access, while complete target parameters are stored locally in component databases. This segmentation enables components to obtain complete information locally without transmitting large datasets across the network, thus maintaining information completeness while improving processing efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates intermediate parameters as simplified copies or references of the original target parameters. These intermediate parameter copies contain sufficient information for component identification and data retrieval, allowing components to access complete information through local database queries rather than receiving full data transmissions, thereby improving processing efficiency.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If complete target parameters are transmitted in HTTP requests, then accurate data processing is enabled, but hardware requirements increase due to larger data transmission volumes

Engineering Contradiction:
Improvedata processing accuracyVSAvoiddata transmission volume
Core Design Contradiction:
Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The patent segments data into transmitted intermediate parameters and locally stored target parameters. This segmentation allows components to receive and process only small intermediate parameter datasets across the network, while maintaining access to complete target parameters locally for accurate processing, thus reducing data transmission volume without compromising processing accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses intermediate parameters as intermediary references that enable accurate data processing without requiring transmission of complete target parameters. Components use the intermediate parameters to locally retrieve precise target parameter data from their databases, maintaining manufacturing precision while minimizing the quantity of data transmitted across the network.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10904316B2Data processing method and apparatus in service-oriented architecture system, and the service-oriented architecture system
Publication Date: 2021.01.26 ADVANCED NOVA TECH (SINGAPORE) HLDG PTE LTD
  • US10904316B2 patent drawing
  • US10904316B2 patent drawing
  • US10904316B2 patent drawing

AI summary

Data processing method and apparatus in a Service-Oriented architecture (SOA) system are disclosed. The method replaces a target parameter having a larger data length included in an original HTTP request with an intermediate parameter having a smaller data length. A data length of a HTTP request that is converted from an original HTTP request is reduced as compared to a data length of the original HTTP request, thus reducing an amount of data that is transmitted, i.e., sent or received, by a target component, which accordingly reduces an amount of data transmitted in the SOA system and decreases a network overhead of the SOA system.