Database Network Traffic Optimization via Usage-Based Column Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing client-server database management systems face inefficiencies in data transfer between servers and clients, often transmitting unnecessary data due to careless coding and early optimization, leading to wasted bandwidth and hindered performance.

Innovation Solution

Utilizing usage statistics to determine which data is actually or likely to be used by a client, allowing only a subset of data to be transmitted, thereby reducing unnecessary data transfer and optimizing network traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If all requested data is transmitted from server to client, then the client receives complete data sets, but network bandwidth is wasted and latency increases due to transmission of unused data

Engineering Contradiction:
Improvedata transmission efficiencyVSAvoidnetwork bandwidth waste
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary subset of data columns that the client will actually use from the complete data set. The server identifies and transmits only these relevant columns rather than all requested columns, thereby eliminating waste of network bandwidth while ensuring the client receives all needed information.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary analysis of data usage patterns before data transmission occurs. By examining which columns are actually used by the client application, the system can pre-determine the optimal subset of columns to transmit, avoiding the transmission of unnecessary data from the outset.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If complete data blocks are transmitted to client, then all possible data is available, but transmission time and network latency increase

Engineering Contradiction:
Improvedata completenessVSAvoiddata transmission latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and transmits only the essential columns that the client will actually utilize. This selective transmission maintains data reliability for the needed information while dramatically reducing transmission time and network latency by eliminating superfluous data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transmitting only the necessary portion of the requested data rather than the complete data set. This approach provides exactly what the client needs without the excessive transmission of additional columns that would only increase latency.

Inventive Principle:
Principle #16Partial or excessive action

3Ease of manufacture

If early optimization is applied without usage statistics, then data transfer is simplified, but unnecessary data is transmitted leading to wasted bandwidth

Engineering Contradiction:
Improveoptimization implementation simplicityVSAvoidbandwidth waste
Core Design Contradiction:
Ease of manufactureVSLoss of energy

Solution Approach 1:

The patent implements feedback by monitoring and analyzing actual data usage patterns at the client side. This usage information is fed back to the server, enabling the server to adapt its data transmission strategy and send only the columns that are actually used, thereby eliminating bandwidth waste while maintaining implementation simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8639710B2Optimization of database network traffic based upon data-use analysis
Publication Date: 2014.01.28 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8639710B2 patent drawing
  • US8639710B2 patent drawing
  • US8639710B2 patent drawing

AI summary

An apparatus, program product and method utilize one or more usage statistics, which are reflective of what data is actually and/or likely to be used by a client when processing a database query, to reduce or eliminate the transfer of unnecessary data between a client and server in a client-server database management system. Information such as the columns that are or have been used and/or the number of rows that have been accessed, may be utilized to identify certain data that is likely to not be used during processing of the database query. Based upon the data that has been identified, a subset of the data that would otherwise be returned as a result of the database query may be identified and returned to a client, often substantially reducing the amount of data required to be retrieved by a client in connection with a database query.