Network Flow Tracking via Payload Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network test systems using connectionless protocols face difficulties in tracking network flows due to alterations in message variables, such as IP addresses, caused by network address translation (NAT) devices, which hinder the identification of originating flows.
Innovation Solution
The method involves transmitting a first message with a connectionless protocol and storing a record based on its payload, using a flow identifier, and receiving a second message to determine its belonging to the flow by matching the payload-based identifier, employing hashing or embedding unique cookies to track network flows despite alterations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If connectionless protocols are used for network testing, then testing speed and efficiency are improved, but the ability to track network flows is lost due to IP address translations by NAT devices
Solution Approach 1:
The patent introduces flow identifiers as intermediary elements that mediate between the source and destination endpoints. These flow identifiers are embedded in test messages and serve as reliable tracking mechanisms that survive NAT transformations, allowing the test system to associate returned messages with their corresponding sent messages without relying on IP address tracking.
Solution Approach 2:
The patent changes the tracking parameter from IP address-based identification to payload-based flow identifier identification. By extracting flow identifiers from the message payload rather than relying on header information that may be altered by NAT, the system maintains accurate flow tracking capability while using connectionless protocols for efficient testing.
2Measurement precision
If IP address tracking is used for flow identification, then flow tracking accuracy is improved, but reliability is reduced when NAT devices translate IP addresses
Solution Approach 1:
The patent employs flow identifiers as intermediary tracking elements that are embedded within message payloads. These identifiers act as reliable mediators that maintain consistency across NAT boundaries, allowing accurate and reliable flow identification without depending on IP address information that may be translated or modified by intermediate devices.
Solution Approach 2:
The patent creates copies of flow identification information within the message payload itself. By embedding flow identifiers in the payload, the system creates redundant identification copies that survive NAT transformations, ensuring both accurate and reliable flow tracking even when IP addresses are translated.
3Ease of operation
If connection-oriented protocols are used, then flow tracking is simplified, but testing efficiency and network performance measurement capability are reduced
Solution Approach 1:
The patent introduces flow identifiers as intermediary elements that enable connectionless protocols to achieve connection-oriented-like flow tracking capability. These identifiers embedded in payloads allow the system to track flows without establishing persistent connections, thus maintaining testing efficiency while achieving reliable flow identification.
Solution Approach 2:
The patent changes the approach from connection-state-based tracking to payload-based flow identifier tracking. This parameter change allows connectionless protocols to provide flow tracking functionality that was previously only available through connection-oriented protocols, thereby improving testing efficiency without sacrificing flow tracking capability.
Data Source
AI summary
The subject matter described herein relates to methods, systems, and computer readable media for testing network equipment devices using connectionless protocols. In some examples, a method for testing a network equipment device under test (DUT) includes transmitting a first message using a connectionless protocol for a network flow to the network equipment DUT according to a test script. The method includes storing a record for the network flow including a first flow identifier for the flow based on a first payload of the first message. The method includes receiving a second message from the network equipment DUT and determining that the second message belongs to the network flow by determining a second flow identifier based on a second payload of the second message and matching the second flow identifier to the first flow identifier.