QUIC Traffic Detection via UPF Identifier Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network operators face challenges in differentiating and classifying QUIC traffic in multi-access network scenarios, which affects use cases such as Sponsored Data, QoS, and Traffic Optimization.

Innovation Solution

A method is introduced where a User Plane Function (UPF) in a telecommunication network receives a list of QUIC connection identifiers from a Content Provider, allowing the network to detect and classify QUIC traffic by matching these identifiers with incoming packets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Difficulty of detecting and measuring

If QUIC connection identifiers are used for traffic detection, then traffic differentiation capability is improved, but device complexity increases due to maintaining identifier lists and matching logic

Engineering Contradiction:
Improvetraffic differentiation capabilityVSAvoidcomplexity of UPF
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The Content Provider pre-generates and provides a list of all possible QUIC connection identifiers to the UPF before traffic detection begins. This preliminary action enables the UPF to perform simple list-matching operations rather than complex real-time analysis, resolving the contradiction by preparing detection data in advance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The UPF maintains a copy of the connection identifier list provided by the Content Provider. Instead of implementing complex detection algorithms, the UPF simply compares incoming packet identifiers against this copied list, significantly reducing device complexity while maintaining detection capability.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If multiple QUIC connection identifiers are supported for connection migration, then adaptability is improved, but difficulty of detecting and measuring traffic increases due to identifier changes

Engineering Contradiction:
Improveconnection migration supportVSAvoidtraffic detection difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

All possible connection identifiers that may be used during connection migration are pre-generated and provided to the UPF before migration occurs. This allows the UPF to detect traffic regardless of which identifier is currently active, resolving the contradiction by preparing for all future identifier changes in advance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The UPF's detection mechanism is designed to handle multiple connection identifiers universally. By maintaining a list of all valid identifiers and checking against this list, the UPF can detect traffic for any identifier used during connection migration, making the detection system multi-functional and adaptable to identifier changes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3844922B1Detecting quick user datagram protocol internet connections, QUIC, traffic in a telecommunication network between a user equipment, UE, and a content provider, cp
Publication Date: 2025.04.23 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3844922B1 patent drawingFigure 1
  • EP3844922B1 patent drawingFigure 2
  • EP3844922B1 patent drawingFigure 3~4

AI summary

A method of detecting Quick User Datagram Protocol Internet Connections, QUIC, traffic in a telecommunication network between a User Equipment, UE, and a Content Provider, CP, wherein said UE has an established application session with said CP, for a particular application, using QUIC as transport protocol, wherein said method comprises the steps of receiving, by a User Plane Function, UPF, comprised by said telecommunication network, from said CP, a list of connection identifiers that identify said established application session between said UE and said CP, receiving, by said UPF, a QUIC packet comprising a connection identifier, detecting, by said UPF, said QUIC traffic by determining that said connection identifier of said received QUIC packet is comprised by said list of connection identifiers.