IPv6 Extension Headers for Non-IP Protocol Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Converting applications designed for non-IP protocol stacks to IP protocol stacks is time-consuming and costly, and existing solutions like tunneling reduce over-the-air efficiency by requiring additional processing power and memory.
Innovation Solution
Placing non-IP protocol data in IPv6 extension headers allows applications to operate on an IP protocol stack with minimal modifications, enabling seamless communication between non-IP and IP networks by making the data available in the extension headers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If tunneling is used to allow non-IP nodes to communicate in an IP network, then communication compatibility is improved, but processing overhead and memory requirements increase, reducing over-the-air efficiency
Solution Approach 1:
The patent segments the protocol data by separating IP header information from non-IP protocol data, placing each in appropriate IPv6 extension headers. This allows receiving nodes to selectively process only the segments they need, reducing overall processing overhead while maintaining communication compatibility between IP and non-IP networks
Solution Approach 2:
The patent uses IPv6 extension headers as an intermediary structure that carries both IP and non-IP protocol data in a standardized format. This intermediary enables seamless communication between different protocol stacks without requiring full tunneling encapsulation, thus improving over-the-air efficiency while maintaining adaptability
2Adaptability or versatility
If applications are converted to operate on an IP protocol stack, then IP compliance is improved, but development time and cost increase
Solution Approach 1:
The patent makes the application layer universal by designing it to operate over IPv6 protocol stack while preserving access to non-IP protocol data through extension headers. This multi-functionality allows the same application to work across different protocol stacks without requiring separate versions, significantly reducing development time and cost while maintaining IP compliance
Solution Approach 2:
The patent copies essential non-IP protocol data into IPv6 extension headers, creating a portable representation that can be accessed by applications running on IP stacks. This copying approach allows legacy applications to function on new IP-based infrastructure without complete re-development, reducing both time and cost
3Adaptability or versatility
If non-IP protocol data is placed in IPv6 extension headers, then application reusability is improved, but header complexity increases
Solution Approach 1:
The patent applies dynamics by making extension header usage optional and context-dependent. Nodes only include and process non-IP protocol data in extension headers when their applications require it, rather than always including such headers. This dynamic approach improves application reusability across different nodes while avoiding unnecessary header complexity for nodes that don't need the additional data
Data Source
AI summary
An IP packet may include an IP header and one or more optional IP extension headers. The packet may contain non-IP protocol data in one of the IP extension headers. An application that uses non-IP protocol data may use the non-IP protocol data from the IP extension header. This allows an application designed for a non-IP protocol stack to operate on a device with an IP protocol stack with minimal modification. The non-IP protocol data may alternatively support non-IP routing options within a network or sub-network.