Network Interface Protocol Fragmentation Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In heterogeneous computing environments with different IP topologies, existing communication systems face challenges in maintaining data packet fragmentation compatibility across incompatible network interfaces, such as IPv4 and IPv6, leading to difficulties in re-assembling packets when fragments are received from different interfaces.
Innovation Solution
The method involves identifying the network interface protocol and deriving fragmentation data according to the desired protocol, storing this data in an application layer header, which allows for the re-assembly of logical packets even when transmitted over incompatible interfaces by including specific fragmentation information, ensuring compatibility and enabling re-assembly regardless of the interface used.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data packet fragmentation is performed according to different IP topology versions for different network interfaces, then communication compatibility across heterogeneous interfaces is improved, but device complexity and difficulty of processing fragmentation logic increase
Solution Approach 1:
The patent segments the fragmentation logic into two distinct parts: (1) fragmentation operation performed by the originating node according to its local IP topology version, and (2) re-assembly operation performed by the destination node by matching fragmentation characteristics against multiple stored IP topology versions. This segmentation allows each node to handle only its own fragmentation logic while the destination node performs the adaptation work by selecting the appropriate topology version for re-assembly.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of stored IP topology version data at the destination node. This intermediary enables the destination node to act as a translator, converting fragmented packets from one IP topology version into the appropriate format for re-assembly, without requiring the originating node to be aware of or adapt to multiple topology versions.
2Adaptability or versatility
If multiple IP topology versions are stored and processed at each node, then re-assembly of packets from different interfaces is enabled, but memory requirements and processing overhead increase
Solution Approach 1:
The patent applies local quality by having each node store and process only the IP topology version that is locally applicable to its own network interface configuration. The destination node stores multiple topology versions but only actively uses the one matching its local configuration, while the originating node uses only its own local topology version. This avoids the need for every node to maintain all possible topology versions in memory.
3Device complexity
If a single fragmentation technique is applied across multiple protocols, then device complexity is reduced and communication is simplified, but compatibility with incompatible network interfaces deteriorates
Solution Approach 1:
The patent implements universality by designing the destination node to perform multiple functions: it receives fragmented packets, identifies the source IP topology version, selects the appropriate stored topology version for comparison, and performs re-assembly. This multi-functional destination node enables a single fragmentation technique to work across multiple protocol interfaces without requiring each interface to implement its own fragmentation logic.
Data Source
AI summary
A method and technique for communications over multiple protocol interfaces in a computing environment includes identifying a first communications protocol of a network interface for ingress data packet communications. Responsive to the identified first communications protocol of the network interface differing from a second communications protocol used for the data packet communications, fragmentation data according to a data packet fragmentation protocol corresponding to the second communications protocol is derived from an application layer header of the data packet communications. A logical packet is re-assembled from the data packet communications using the data packet fragmentation protocol and the fragmentation data.