Client Device Compression Necessity Determiner
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client devices with low-performance CPUs experience delays in main processing due to increased processing loads when handling large data exchanges, even with compressed data communication.
Innovation Solution
A client device system that determines the necessity of data compression based on size and processing times, using a compression presence-absence time table to decide whether to compress data before transmission, thereby reducing processing load and preventing delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data compression is performed to reduce communication data size, then transmission efficiency is improved, but CPU processing load increases causing delays in main processing
Solution Approach 1:
The patent applies parameter changes by dynamically adjusting the compression ratio based on the CPU's current processing state. When the CPU is under heavy load, the system reduces or disables compression to minimize processing delays. When the CPU is idle, the system increases compression ratio to maximize transmission efficiency. This adaptive parameter adjustment resolves the contradiction between transmission efficiency and processing delay.
Solution Approach 2:
The system implements dynamics by making the compression processing adaptive and variable rather than static. The compression ratio and processing intensity are dynamically adjusted based on real-time CPU load monitoring and main processing requirements. This allows the system to optimize the balance between compression benefits and processing overhead according to current operational conditions.
2Ease of manufacture
If a low-performance CPU is used to reduce device cost, then device cost is reduced, but processing capability decreases leading to delays in data communication
Solution Approach 1:
The system applies preliminary action by pre-assessing the CPU's processing capability and the characteristics of data to be transmitted before initiating compression. The system determines in advance whether compression is necessary and what compression ratio to use, based on predicted CPU load and data properties. This prevents unnecessary compression from being applied, thereby avoiding avoidable processing delays while maintaining cost-effectiveness.
Solution Approach 2:
The patent uses parameter changes by adjusting compression intensity based on the specific characteristics of the data being transmitted and the CPU's current state. For certain data types or under specific conditions, the system may reduce or skip compression entirely, even with a low-performance CPU, thereby maintaining communication speed while keeping device costs low.
3Quantity of substance
If compression processing is applied to all data transmissions, then data transmission size is reduced, but main processing delays occur due to increased CPU load
Solution Approach 1:
The system applies partial action by selectively applying compression only to data transmissions where it is most beneficial. Rather than compressing all data uniformly, the system identifies specific data types, transmission conditions, or size thresholds where compression provides the greatest benefit relative to CPU cost. This selective approach reduces overall processing delays while still achieving significant data size reduction where needed.
Solution Approach 2:
The patent implements parameter changes by dynamically adjusting the compression ratio based on data characteristics and system state. For certain data types or under specific conditions, the system may use lower compression ratios or skip compression entirely, thereby reducing CPU processing time while still achieving adequate data size reduction. This adaptive parameter adjustment resolves the contradiction between minimizing transmission size and avoiding processing delays.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
A compression necessity determiner (131) is configured to determine a necessity of compression of to-be-uploaded data to a server. A data compressor (132) is configured to compress, when the compression necessity determiner (131) determines that the compression of the to-be-uploaded data is necessary, the to-be-uploaded data in a predetermined scheme. When the compression necessity determiner (131) determines that the compression of the to-be-uploaded data is unnecessary, a data sender (133) sends data, in which a header is added to the to-be-uploaded data to the communication interface, and when the compression necessity determiner (131) determines that the compression of the to-be-uploaded data is necessary, the data sender (133) sends to the communication interface data in which a header, containing information indicating that the to-be-uploaded data is compressed data, is added to the to-be-uploaded data compressed by the data compressor (132).