Lossy LAN Packet Compression for Diagnostic Data Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network diagnostics systems face high storage, bandwidth, and processing requirements due to the large number and size of packet captures, especially in IEEE 802.11 WiFi systems where repetitive beacon packets are transmitted, limiting the effectiveness of existing compression algorithms like GZIP which are lossless and do not reduce the number of packets.
Innovation Solution
Implementing a lossy compression technique that identifies and replaces similar packets with custom packets containing references to the original packets, allowing for high compression ratios while ensuring diagnostic integrity by retaining the ability to regenerate original packets, thus reducing storage, bandwidth, and processing needs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If lossless compression algorithms like GZIP are used to compress packet captures, then the original packets can be perfectly recreated when decompressed, but the maximum compression ratio is limited and the number of packets is not reduced
Solution Approach 1:
The patent changes the fundamental parameter of compression from lossless to lossy, allowing some information to be discarded in exchange for significantly higher compression ratios. This is achieved by identifying and removing redundant packet data while retaining only essential diagnostic information, thereby resolving the contradiction between reconstruction accuracy and compression efficiency.
Solution Approach 2:
The patent extracts and removes redundant information from packet captures, specifically identifying and eliminating duplicate beacon packets and other repetitive data. By taking out only the necessary diagnostic elements and discarding redundant copies, the system achieves high compression ratios while maintaining diagnostic integrity.
2Loss of information
If all packets including repetitive beacon packets are captured and processed, then complete network diagnostic data is obtained, but storage, bandwidth, and CPU processing requirements increase significantly
Solution Approach 1:
The patent applies the principle of discarding redundant packet information that can be recovered or reconstructed later. By identifying repetitive packets (such as beacon packets with identical content) and discarding them in the compressed format, the system reduces packet quantity while maintaining diagnostic completeness through selective retention of unique diagnostic data.
Solution Approach 2:
Instead of processing all packets equally, the patent applies partial action by selectively processing only those packets that contain unique diagnostic information. Repetitive packets are identified and excluded from full processing, reducing the quantity of packets requiring CPU analysis while maintaining sufficient diagnostic data through targeted selection.
3Productivity
If compression is applied across a block of multiple packets to achieve higher compression ratios, then the compressed file size is reduced, but the processing delay increases
Solution Approach 1:
The patent applies preliminary action by pre-identifying and marking redundant packets (such as duplicate beacons) before the actual compression process. This preliminary classification allows the compression algorithm to efficiently handle blocks of packets with known redundancy patterns, achieving high compression ratios without excessive processing delays since the redundant nature of packets is already determined.
Data Source
AI summary
Methods and apparatus are disclosed for processing local area network diagnostic data obtained in respect of a local area network. The method includes calculating a value for each of a plurality of data units according to a predetermined function of one or more field-values stored in the data unit; identifying a first and second data unit as being similar in dependence on a comparison of their respective values, the second data unit having at least one field-value which differs from a corresponding field-value of the first data unit; in response to such an identification, creating a third data unit containing a field-value indicative of the first data unit and an indication of the at least one field-value which differs from the corresponding field-value in the first data unit; and sending the first and third data units for performance analysis at a remote network diagnostic device outside the LAN.