Token-Based Message Capture for Network Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current message capture solutions for high-bandwidth network traffic are resource-intensive and costly, making them impractical for network traffic testing purposes.
Innovation Solution
A token-based message capture method that generates test messages with a token and data integrity check value (DICV), which are sent to a system under test, and the received messages are stored using the token and DICV, allowing for efficient storage and compression of message data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional message capture solutions are used for high-bandwidth network traffic, then complete message data can be captured, but resource consumption and costs increase significantly
Solution Approach 1:
The message capture system is segmented into two parts: (1) a message generation module that creates test messages with embedded tokens and DICVs, and (2) a message capture module that stores only tokens and delta information. This segmentation allows the system to maintain complete message capture capability while significantly reducing storage requirements by storing only the essential identification and integrity data rather than full message copies.
Solution Approach 2:
Instead of storing complete message data, the system creates a simplified copy consisting of tokens and delta information. The token serves as a compact representation of the original message, and the delta information captures only the necessary modifications. This copying approach maintains the ability to reconstruct and verify messages while dramatically reducing storage resource consumption.
2Loss of information
If traditional message capture solutions are used for high-bandwidth network traffic, then all message data can be stored, but the cost becomes prohibitive for testing purposes
Solution Approach 1:
The system performs preliminary actions by embedding tokens and DICVs into test messages before they are sent through the network. This pre-preparation ensures that when messages are captured, the essential integrity verification data is already in place, eliminating the need to store and process complete message data while maintaining the ability to verify message integrity and detect modifications.
Solution Approach 2:
The system changes the parameters of message storage by transitioning from storing complete message data to storing only tokens and delta information. This parameter change fundamentally reduces the storage footprint and associated costs while maintaining the critical functionality of message integrity verification through the preserved DICV mechanism.
3Quantity of substance
If tokens and delta information are used to store message representations, then storage requirements are reduced, but the complexity of message verification increases
Solution Approach 1:
The verification process is made self-service through the use of self-contained tokens that include embedded DICVs. When a message is captured and stored with its token, the token itself carries the necessary integrity verification data. This eliminates the need for complex external verification systems, as the token structure enables automatic verification through simple DICV comparison operations.
Data Source
AI summary
Methods, systems, and computer readable media for token based message capture are disclosed. One method includes generating a test message including a token indicative of message data and a data integrity check value (DICV) computed based on at least a portion of the message data. The method also includes sending the test message to a system under test (SUT). The method further includes receiving, from the SUT, a version of the test message, wherein the version of the test message includes the token and the DICV. The method also includes storing a representation of the version of the test message using the token and the DICV.