Radio Traffic Management via Data Plane Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network traffic management systems, particularly for mobile and wireless devices, fail to optimize radio traffic effectively, leading to unnecessary battery drain due to frequent wake-ups from idle state caused by TCP protocol operations like TCP FIN packets and zero window probes, which are not optimized for mobile devices.

Innovation Solution

A system and method for radio traffic management that determines the status of mobile devices and manages packet flow by queuing, closing, or responding to packets based on device activity, using Deep Packet Inspection to differentiate between time-critical and non-time-critical packets, and employing a data plane device to reduce unwanted traffic and minimize radio wake-ups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TCP protocol is used for internet access on mobile devices, then network connectivity is established, but battery life is drained due to frequent radio wake-ups from idle state

Engineering Contradiction:
Improvenetwork connectivityVSAvoidbattery life
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

A data plane device is introduced as an intermediary between the mobile device and the network server. This device inspects packets, determines UE status (active/idle), and selectively forwards packets or queues them, preventing unnecessary radio wake-ups while maintaining network connectivity when needed.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary status determination of the UE before processing packets. By checking whether the UE is in idle or active state beforehand, the system can pre-queue packets during idle periods and only forward them when the UE becomes active, avoiding wake-ups.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If radio interface remains in active state to handle packet flow, then packet transmission is reliable, but power consumption increases

Engineering Contradiction:
Improvepacket transmissionVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by stationary object

Solution Approach 1:

The system dynamically adjusts radio state based on packet characteristics and UE status. Time-sensitive packets trigger active state transitions, while non-time-sensitive packets are queued during idle state. This dynamic approach ensures reliable transmission when needed while minimizing power consumption during idle periods.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Packets are segmented into time-critical and non-time-critical categories. Different handling strategies are applied to each segment: time-critical packets receive immediate forwarding, while non-time-critical packets are queued. This segmentation allows the radio to remain idle longer without compromising essential communication.

Inventive Principle:
Principle #1Segmentation

3Productivity

If all packets are forwarded immediately, then network responsiveness is high, but redundant traffic increases causing battery drain

Engineering Contradiction:
Improvenetwork responsivenessVSAvoidbattery drain
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

Instead of forwarding all packets immediately (excessive action), the system applies partial action by selectively forwarding only time-critical packets and queuing non-time-critical ones during idle periods. This partial forwarding approach reduces redundant traffic and battery drain while maintaining necessary responsiveness.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system changes the forwarding parameter based on packet type and UE status. For time-critical packets, forwarding is immediate; for non-time-critical packets, forwarding is delayed or queued. This parameter change enables the system to balance responsiveness with energy efficiency.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If Deep Packet Inspection is performed on all packets, then traffic optimization is achieved, but processing complexity increases

Engineering Contradiction:
Improvetraffic optimizationVSAvoidprocessing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The complex packet inspection and status determination logic is extracted from the mobile device and placed in the data plane device. This separates the complexity from the UE, allowing the mobile device to simply forward packets while the network-side device handles the optimization logic.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The data plane device serves multiple functions: packet inspection, UE status determination, packet queuing, and selective forwarding. By consolidating these functions in a single network component, the system achieves traffic optimization without increasing UE complexity.

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

Data Source

PatentUS20230033139A1System and method for managing radio traffic for mobile and wireless devices
Publication Date: 2023.02.02 SANDVINE CORP
  • US20230033139A1 patent drawing
  • US20230033139A1 patent drawing
  • US20230033139A1 patent drawing

AI summary

A system and method for radio traffic management in a computer network. The method includes: determining user equipment (UE) status associated with a traffic flow session; determining traffic flow parameters associated with the traffic flow associated with the UE; determining a change in the UE status; and determining a traffic action for at least one packet associated with the traffic flow based on the UE status. The system includes: a UE state module configured to determine UE status associated with a traffic flow session; a packet inspection module configured to determine traffic flow parameters associated with the traffic flow associated with the UE; a forwarding module configured to determine a traffic action for at least one packet associated with the traffic flow based on the UE status.