RAN Flow ID Mapping for Packet Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing communication networks face challenges in efficiently handling packet flows, particularly in reducing signaling overhead and accurately identifying data packets within the radio access network, which affects network capacity and performance, especially for small user data packets like voice and control packets.

Innovation Solution

The method involves determining a RAN flow ID for data packets, which includes both PDU session ID and PDU flow ID, using techniques such as concatenation or encoding with a paring function to minimize header overhead, and optionally using local RAN IDs to reduce computational complexity and processing time for encryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If PDU session ID and PDU flow ID are included in the packet header for accurate flow identification, then packet identification accuracy is improved, but header overhead increases

Engineering Contradiction:
Improvepacket identification accuracyVSAvoidheader overhead
Core Design Contradiction:
Measurement precisionVSLoss of substance

Solution Approach 1:

The patent combines PDU session ID and PDU flow ID into a single RAN flow ID field in the packet header. This merging allows both identification functions to be achieved simultaneously while reducing the total header size compared to including both IDs separately.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The RAN flow ID is designed to serve multiple functions: it uniquely identifies the PDU session and the PDU flow within that session. This multi-functionality eliminates the need for separate identification fields, thereby reducing header overhead while maintaining accurate packet identification.

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

2Measurement precision

If explicit signaling is used to indicate flow to data radio bearer mapping, then mapping accuracy is improved, but signaling overhead increases

Engineering Contradiction:
Improveflow mapping accuracyVSAvoidsignaling overhead
Core Design Contradiction:
Measurement precisionVSLoss of substance

Solution Approach 1:

The patent enables the UE to autonomously determine the flow to data radio bearer mapping by examining the RAN flow ID in received packets. This self-service approach eliminates the need for explicit network signaling to convey mapping information, thereby reducing signaling overhead while maintaining accurate mapping.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The network pre-configures the UE with the relationship between RAN flow IDs and data radio bearers during connection setup. This preliminary action allows the UE to perform local mapping decisions without requiring subsequent explicit signaling, reducing overall signaling overhead.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If RAN flow ID is included in every packet header, then flow identification reliability is improved, but processing complexity increases

Engineering Contradiction:
Improveflow identification reliabilityVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes the parameter representation by using a compact RAN flow ID that encodes both PDU session and flow information. This parameter transformation reduces the computational complexity of flow identification while maintaining reliable flow distinction across all packets.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3536016B1UE, network node and methods for handling data packets
Publication Date: 2020.04.08 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3536016B1 patent drawingFigure 1~2
  • EP3536016B1 patent drawingFigure 3~4
  • EP3536016B1 patent drawingFigure 5

AI summary

A method, performed by a RAN node for handling data packets from a Core Network (CN) node to a User Equipment (UE) is provided. The RAN node receives (601) from the CN node, a data packet comprised in a PDU flow. The data packet comprises a PDU session ID and a PDU flow ID for identifying the data packet. The RAN node generates (602) a RAN flow ID based on the PDU session ID and the PDU flow ID. The RAN node further transmits (603) a RAN packet to the UE, wherein the RAN packet comprises the data packet and the generated RAN flow ID for identifying the RAN packet.