IP Flow Mobility Gateway for LTE WiFi Bearer Binding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current networking architectures face challenges in managing mobility of user equipment within mobile and WiFi networks, particularly when connected to the same access point name, as they lack efficient mechanisms for IP flow mobility across different radio access technologies.

Innovation Solution

A method and system that determine the availability of preferred radio access technologies for service data flows and configure them accordingly, allowing for seamless movement of data flows between LTE and WiFi networks while maintaining session continuity and optimizing charging and policy rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If user equipment connects simultaneously to both mobile and WiFi networks with the same access point name, then network coverage and service availability are improved, but managing mobility and routing of data flows between different radio access technologies becomes complex and inefficient

Engineering Contradiction:
Improveservice availabilityVSAvoidmobility management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments IP flows into different service data flows that can be independently routed over different radio access technologies. Each service data flow is associated with specific traffic flow templates (TFTs) that enable granular control and identification of flows, allowing the system to manage mobility on a per-flow basis rather than requiring complex end-to-end mobility management for entire connections.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a gateway node as an intermediary between the user equipment and the packet data network. This gateway node performs IP flow mobility functions including receiving service data flows, determining routing based on available radio access technologies, and forwarding flows to appropriate networks. The gateway acts as a mediator that simplifies mobility management by centralizing routing decisions and maintaining session continuity across different access technologies.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If IP flow mobility is implemented across different radio access technologies, then resource utilization and network efficiency are improved, but determining availability and configuring service data flows dynamically increases system complexity

Engineering Contradiction:
Improvenetwork efficiencyVSAvoidconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamic configuration of service data flows based on real-time availability of radio access technologies. The gateway node continuously monitors the availability of different RATs (mobile network, WiFi network) and dynamically routes service data flows accordingly. When a RAT becomes unavailable, the system automatically reconfigures routing to alternative networks, enabling adaptive resource utilization without manual intervention.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent employs feedback mechanisms where the gateway node receives information about the availability status of different radio access technologies and uses this feedback to make routing decisions. The system monitors network conditions, detects changes in RAT availability, and adjusts service data flow routing in response to this feedback, optimizing network efficiency while maintaining simple configuration through automated decision-making.

Inventive Principle:
Principle #23Feedback

3Reliability

If seamless movement of data flows between LTE and WiFi networks is enabled, then user experience and service continuity are improved, but monitoring and detecting RAT changes and managing bearer binding requires additional system complexity

Engineering Contradiction:
Improvesession continuityVSAvoidmonitoring complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent establishes bearer bindings in advance between service data flows and specific radio access technologies. The gateway node pre-configures binding relationships that associate service data flows with preferred RATs. When RAT changes occur, the system leverages these pre-established bindings to maintain session continuity by redirecting flows along pre-planned paths, avoiding the need for complex real-time renegotiation and simplifying the monitoring process.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If service data flows are dynamically reconfigured based on available network conditions, then resource optimization and network efficiency are improved, but determining RAT availability and managing policy rules increases operational complexity

Engineering Contradiction:
Improveresource utilizationVSAvoidoperational simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements self-service mechanisms where the gateway node autonomously determines radio access technology availability and automatically reconfigures service data flows based on current network conditions. The system monitors RAT availability, evaluates policy rules, and performs routing decisions without requiring manual operational intervention. This automation optimizes resource utilization while maintaining operational simplicity by eliminating the need for complex manual configuration and management.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3399795B1System and method for providing internet protocol flow mobility in a network environment
Publication Date: 2020.06.10 CISCO TECHNOLOGY INC
  • EP3399795B1 patent drawingFigure 1
  • EP3399795B1 patent drawingFigure 2
  • EP3399795B1 patent drawingFigure 3A

AI summary

A method comprising: receiving a policy related rule for a user equipment, UE (12), wherein the UE (12) is accessing an access point name, APN, using a first radio access technology, RAT, type associated with a first default bearer for the UE (12) and wherein the policy related rule is associated with the UE (12) accessing the APN using a second RAT type; and binding the policy related rule to a second default bearer for the UE (12) to access the APN, wherein the second default bearer for the UE (12) is associated with the second RAT type.