M2M Gateway Traffic Smoothing for Burst Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Machine-to-machine (M2M) communication networks face challenges due to unpredictable and variable traffic patterns, leading to inefficient network dimensioning and resource utilization, as M2M traffic is often characterized by infrequent bursts from a large number of devices, resulting in over- or under-dimensioning of networks.

Innovation Solution

Implementing a system where an M2M gateway determines a holding time and outgoing traffic rate for M2M traffic, allowing it to be released in a steady and predictable manner, thereby managing network resources efficiently by holding traffic for a calculated period before releasing it at a controlled rate to the relay network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If M2M traffic is handled in real-time without buffering, then traffic latency is reduced, but network resources are inefficiently utilized due to unpredictable burst patterns

Engineering Contradiction:
Improvetraffic latencyVSAvoidnetwork resource utilization efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The M2M gateway performs preliminary actions by calculating the holding time parameter before traffic arrives, based on historical traffic patterns and network capacity. This pre-calculated holding time is then applied to buffer traffic for the appropriate duration, achieving both low latency (by using pre-determined optimal values) and efficient resource utilization (by smoothing traffic bursts)

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the temporal parameter of traffic flow by introducing a holding time parameter that transforms unpredictable burst traffic into a smoothed, predictable flow. The holding time parameter is dynamically adjusted based on traffic characteristics and network conditions, enabling the system to optimize both latency and resource utilization through parameter transformation

Inventive Principle:
Principle #35Parameter changes

2Reliability

If network capacity is increased to handle peak M2M traffic bursts, then traffic reliability is improved, but network cost and complexity increase due to over-dimensioning

Engineering Contradiction:
Improvetraffic delivery reliabilityVSAvoidnetwork dimensioning complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The M2M gateway acts as an intermediary between M2M devices and the relay network, introducing a holding time mechanism that smooths traffic before it reaches the network. This intermediary function allows the network to be dimensioned for average load rather than peak load, improving reliability without requiring over-dimensioning or increased complexity in the network infrastructure

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If M2M traffic is buffered for longer periods to smooth bursts, then network resource efficiency is improved, but traffic latency increases

Engineering Contradiction:
Improvenetwork resource utilization efficiencyVSAvoidtraffic latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The holding time parameter is made dynamic rather than static, allowing the system to adapt the buffering duration based on real-time traffic characteristics and network conditions. This dynamic adjustment enables the system to minimize latency while still achieving traffic smoothing, as the holding time is optimized for each specific traffic flow rather than applying a fixed conservative buffer

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9559965B2Real-time traffic management for machine to machine communications
Publication Date: 2017.01.31 VERIZON PATENT & LICENSING INC
  • US9559965B2 patent drawing
  • US9559965B2 patent drawing
  • US9559965B2 patent drawing

AI summary

A device may receive machine-to-machine (M2M) traffic associated with an M2M application. The device may determine parameters associated with managing the M2M traffic. The parameters may include information identifying a time window. The device may determine a weighted average traffic rate associated with the M2M traffic based on the parameters. The device may determine a holding time to be applied to the M2M traffic based on the weighted average traffic rate and the parameters. The device may determine an outgoing traffic rate to be applied to the M2M traffic based on the weighted average traffic rate and the parameters. The device may manage the M2M traffic based on the holding time and the outgoing traffic rate.