QUIC Migration Flow Service Typing Without SNI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing deep packet inspection (DPI) systems struggle to accurately determine the service type of QUIC migration flows after connection migration, as they cannot acquire Server Name Indication (SNI) from the QUIC migration flow, rendering it impossible to identify the migration service type.
Innovation Solution
The method involves determining a first identification feature in the QUIC migration flow, matching it with a metadata object generated based on a second identification feature from the QUIC negotiation flow, and configuring the negotiation service type as the migration service type.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the DPI system uses SNI in the ClientHello message to determine the negotiation service type, then the negotiation service type can be accurately identified, but the migration service type cannot be determined after connection migration since SNI is not available in the QUIC migration flow
Solution Approach 1:
The patent extracts and stores the SNI information and service type during the QUIC negotiation phase before connection migration occurs. This preliminary extraction and storage of identification information enables the system to later match and determine the migration service type even though SNI is not present in the migration flow, thus resolving the information loss problem after migration
Solution Approach 2:
The patent introduces an intermediary mapping relationship between the QUIC negotiation flow and QUIC migration flow through common identifying features (such as source/destination IP addresses, ports, and connection identifiers). This intermediary mapping enables the system to associate migration flow information with previously stored negotiation flow service types, allowing accurate service type determination without direct SNI information in the migration flow
2Reliability
If the DPI system relies on SNI from the QUIC negotiation flow to identify service types, then negotiation service type determination is accurate, but migration service type determination becomes impossible without SNI in the migration flow
Solution Approach 1:
The system performs preliminary extraction of SNI and service type information during the negotiation phase and stores it in a mapping table before migration occurs. This advance preparation ensures reliable service type identification for migration flows without requiring complex real-time analysis during migration, thus maintaining reliability while managing complexity
Solution Approach 2:
The patent introduces an intermediary mapping table that stores the relationship between QUIC negotiation flows and service types. This intermediary structure simplifies the determination process for migration flows by providing a direct lookup mechanism based on matching identification features, reducing the complexity of real-time service type determination while maintaining high reliability
3Productivity
If the DPI system extracts SNI during the QUIC negotiation phase, then the negotiation service type can be determined, but the migration service type remains undetermined without further SNI extraction from the migration flow
Solution Approach 1:
The patent extracts and stores service type information during the QUIC negotiation phase before migration occurs. This preliminary extraction eliminates the need to perform SNI extraction during the migration phase, improving processing efficiency while preventing information loss about the migration service type through the stored mapping relationship
Solution Approach 2:
The system creates a copy of the service type information obtained from the negotiation phase and stores it in a mapping table. This copied information is then used to determine the migration service type without needing to re-extract SNI from the migration flow, thus improving efficiency while preventing information loss
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
The present application provides a method for determining a service type of network traffic, an electronic device, and a readable storage medium. The method includes following steps: acquiring the QUIC migration flow, and determining a first identification feature corresponding to the QUIC migration flow; matching and acquiring a negotiation service type corresponding to the first identification feature from a metadata object, the metadata object being generated based on a second identification feature and the negotiation service type matching the QUIC negotiation flow corresponding to the QUIC migration flow; and configuring the negotiation service type as a migration service type corresponding to the QUIC migration flow.