Single Tunnel QoS Differentiation in Cellular Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 3GPP EPS/LTE networks face inefficiencies in bearer setup and QoS differentiation due to the need for multiple tunnels and over-dimensioning of transport networks, leading to increased latency and signaling load, especially during handovers, as each QoS flow requires a unique TEID and lacks effective traffic prioritization.

Innovation Solution

Implementing a single tunnel with a unique identifier for multiple bearers, where each bearer has a common tunnel identifier and a unique identification component for QoS differentiation, using the DiffServ Service Classes to prioritize data within the tunnel, and modifying the GTP TEID to include a common part for the tunnel and a separate part for QoS flow identification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a unique TEID is assigned to each QoS flow (bearer), then QoS differentiation is enabled, but tunnel complexity and signaling load increase

Engineering Contradiction:
ImproveQoS differentiationVSAvoidtunnel complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The TEID is segmented into two distinct components: a common TEID shared by all bearers and a bearer identifier specific to each QoS flow. This segmentation allows the system to maintain QoS differentiation through the bearer identifier while using the common TEID for tunnel management, thereby reducing signaling load and tunnel complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The common TEID serves multiple functions by being shared across all bearers within a tunnel. It enables unified tunnel establishment, maintenance, and teardown operations, eliminating the need for separate tunnel management for each QoS flow while still allowing individual bearer identification through the bearer identifier component.

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

2Reliability

If multiple tunnels are established for different QoS flows, then QoS differentiation is achieved, but bearer setup delay increases

Engineering Contradiction:
ImproveQoS differentiationVSAvoidbearer setup delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Multiple bearers with different QoS requirements are merged into a single tunnel by sharing the common TEID. This consolidation reduces the number of tunnel establishment operations from multiple (one per bearer) to a single operation, significantly reducing bearer setup delay while maintaining QoS differentiation through the bearer identifier component.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If transport networks are over-dimensioned to handle peak loads, then service reliability is improved, but network cost increases

Engineering Contradiction:
Improveservice reliabilityVSAvoidnetwork capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

QoS differentiation is implemented at the packet level within the tunnel using the bearer identifier component. This allows the transport network to handle traffic more efficiently by applying appropriate quality of service treatments to specific bearers based on their requirements, rather than over-provisioning the entire network for peak loads of all bearers simultaneously.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP1976196B1Data transmission
Publication Date: 2013.05.15 VODAFONE GRP PLC
  • EP1976196B1 patent drawingFigure 1
  • EP1976196B1 patent drawingFigure 2~4

AI summary

In a mobile or cellular telecommunications network a single tunnel between nodes 7,11,15 and 19 of the network is established to transmit data on a plurality of bearers. Each bearer transmits data relating to a particular service. The respective bearers may be identified by identification data. The identification data may indicate the priority of the data in the particular bearer. The identification data may indicate the DiffServ Service Class, DSSC, as defined in RFC 4594.