Packet Header Extension for Scalable Protection Protocol Signaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network protocols have limited scalability and support for a small number of protection protocols, making it difficult to efficiently manage and process data protected by multiple security protocols.
Innovation Solution
A packet sending and receiving method that utilizes a first packet header with an indication field and a second packet header containing a type field, offset field, length field, and flag field to indicate and locate protected data, allowing for the support of multiple protection protocols and efficient data processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a special field in packet header is used to indicate protection protocol, then data security is achieved, but scalability is limited and support for multiple protection protocols is poor
Solution Approach 1:
The patent implements a nested packet header structure where a first packet header contains an indication field pointing to a second packet header. The second packet header contains the type field that indicates the protection protocol. This nesting allows the indication field in the first header to use a reserved value (e.g., 0xFE) to signal the presence of the second header, while the second header's type field provides the actual protocol identification. This resolves the contradiction by enabling extended protocol support without requiring the first header to accommodate all possible protocol values directly.
Solution Approach 2:
The packet header is segmented into two distinct parts: a first packet header with an indication field for presence signaling, and a second packet header with a type field for protocol specification. This segmentation allows the indication field to maintain a simple reserved value structure while the type field in the second header provides comprehensive protocol support. The segmentation effectively divides the functionality between presence indication and protocol identification, resolving the scalability limitation.
2Adaptability or versatility
If existing packet header fields are used to indicate protection protocol, then simplicity is maintained, but the quantity of supported protection protocols is small
Solution Approach 1:
The patent adds a dimensional layer to the packet header structure by introducing a second packet header that is conditionally present. The first packet header's indication field serves as a gateway that, when set to a reserved value, triggers the inclusion of the second header dimension. This dimensional expansion allows the system to support a larger quantity of protection protocols without modifying the original first header structure, effectively adding capacity in a new structural dimension.
Solution Approach 2:
The first packet header performs a preliminary action by setting its indication field to a reserved value (e.g., 0xFE) to pre-signal the presence of the second packet header. This preliminary indication allows receiving devices to prepare for and efficiently process the extended header structure before actually encountering the type field information. This preliminary signaling mechanism enables scalable protocol support while maintaining processing efficiency.
Data Source
Figure 1
Figure 2~4
Figure 5~6
AI summary
A packet sending method is provided. The method includes: generating, by a network device, a first packet, and sending the first packet. The first packet includes a first packet header, a second packet header, and protected data. The first packet header includes an indication field. The indication field is used to indicate that the first packet includes the second packet header. The second packet header includes a type field. The type field is used to indicate a first protection protocol. The protected data is data protected by using the first protection protocol. In the foregoing technical solution, the second packet header is a packet header defined in this application. Because a value of the type field in the second packet header is not defined in an existing protocol, the type field may indicate more protection protocols. Therefore, the foregoing solution has good scalability and can support more protection protocols.