PMIPv6 Tunnel Service Flow Differentiation via GRE Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing PMIPv6-based data transmission solutions, data packets from a Mobile Node (MN) cannot be distinguished and controlled based on service flows, leading to inefficiencies in network management and charging control.
Innovation Solution
A PMIPv6-based data transmission method and system that establishes a bidirectional tunnel between a Mobile Access Gateway (MAG) and a Local Mobility Anchor (LMA) using service flow identifiers and Generic Routing Encapsulation (GRE) keys, allowing for the differentiation and management of data packets based on service flows by adding a service flow identification option to Proxy Binding Update (PBU) and Proxy Binding Ack (PBA) messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a bidirectional tunnel is established between MAG and LMA for PMIPv6 data transmission, then mobility support is achieved, but data packets cannot be distinguished and controlled based on service flows
Solution Approach 1:
The patent segments the data transmission process by introducing service flow identification options (SFID, transport level description, application level description) into the PBU/PBA signaling messages. This allows the bidirectional tunnel to be segmented into multiple service flow-specific sub-tunnels, enabling differentiation of data packets based on service flows while maintaining the overall tunnel structure for mobility support.
Solution Approach 2:
The patent adds new dimensions to the existing bidirectional tunnel by incorporating service flow identification fields into the signaling messages and tunnel parameters. This dimensional expansion allows the tunnel to carry additional metadata (SFID, transport level description, application level description) that enables service flow-based packet differentiation without fundamentally restructuring the mobility management mechanism.
2Measurement precision
If service flow identification options are added to PBU and PBA messages, then data packet distinction based on service flow is enabled, but message structure complexity increases
Solution Approach 1:
The patent implements nested structure by placing service flow identification options within the existing PBU and PBA message frameworks. The service flow identification fields (SFID, transport level description, application level description) are nested inside the mobility options section of the signaling messages, allowing precise service flow identification while minimizing the increase in message structure complexity by utilizing existing message containers.
Solution Approach 2:
The patent performs preliminary action by pre-defining the service flow identification options and their formats in the signaling messages before data transmission begins. The SFID and description fields are established during the binding update/acknowledgment phase, so that when data packets arrive, the service flow identification information is already in place, eliminating the need for complex real-time analysis and reducing processing complexity.
3Productivity
If multiple service flows are supported with unique identifiers, then charging control based on service flow is enabled, but tunnel management complexity increases
Solution Approach 1:
The patent implements feedback mechanisms where the MAG and LMA exchange service flow identification information in the PBU/PBA signaling messages. The LMA receives SFID and transport level description from the MAG, validates them, and returns acknowledgment with uplink GRE key. This feedback loop ensures that service flow identification is consistently maintained across both ends, enabling efficient charging control while simplifying tunnel management through automated verification and error correction.
Solution Approach 2:
The patent achieves universality by designing the service flow identification options to serve multiple functions: (1) identifying service flows for charging control, (2) enabling QoS differentiation, (3) supporting mobility management, and (4) providing tunnel establishment parameters. The same SFID and description fields used for charging control also serve as tunnel identification parameters, reducing the need for separate management mechanisms and lowering overall system complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A data transferring method, a system and a related network device based on proxy mobile (PM) IPv6, which are used for solving the problem that the existing data transferring scheme based on proxy mobile (PM) IPv6 can't distinguishes and controls the mobile node (MN) data packages according to service flow. The data transferring method includes: after the mobile node (MN) initiates the service flow, a mobile access gateway (MAG) and local mobility anchor (LMA) establishes a bidirectional tunnel by information interaction based on service flow binding; in which, in the process of the bidirectional tunnel establishing, the service is distributed the downlink GRE Key and uplink GRE Key, and the local mobility anchor (LMA) adds service flow identifier of the service flow and the binding relationship of the address information of the mobile node (MN); the mobile access gateway (MAG) and local mobility anchor (LMA) transfers the data packages of the service flow initiated by the mobile node (MN) on the bidirectional tunnel between the mobile access gateway (MAG) and local mobility anchor (LMA) according to the service flow identifier and the binding relationship and the uplink, downlink GRE Key.