Network Node Outage Traffic Load Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless packet data networks, outages at network nodes lead to a surge in data connection requests from mobile nodes with 'always on' applications, causing heavy network loading due to simultaneous reconnect attempts.

Innovation Solution

The network node generates session termination messages and releases data connections, prompting mobile nodes to delay reconnect requests based on randomization, reducing the bursty network traffic typically seen during outages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the network node releases data connections and generates session termination messages upon outage, then the network node can recover from the outage condition, but a large number of mobile nodes simultaneously attempt to reconnect causing heavy network loading

Engineering Contradiction:
Improvenetwork node recoveryVSAvoidnetwork traffic surge
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent applies periodic action by implementing exponential backoff algorithms that create time-based periodic reconnection attempts. Mobile nodes delay their reconnect requests using exponentially increasing time intervals (e.g., 1 second, 2 seconds, 4 seconds, 8 seconds) with randomization factors. This transforms the simultaneous reconnection surge into a distributed, periodic pattern that prevents network overload while ensuring eventual reconnection.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent changes the time parameter of reconnection attempts dynamically. Instead of fixed immediate reconnection, the system modifies the time interval parameter exponentially (backoff mechanism) and adds randomization parameters. This transforms the reconnection behavior from a synchronized burst into a distributed temporal pattern, reducing peak network load while maintaining service restoration.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If mobile nodes immediately attempt to reconnect after receiving session termination messages, then service restoration is achieved quickly, but network infrastructure experiences heavy loading due to simultaneous connection requests

Engineering Contradiction:
Improveservice restoration speedVSAvoidnetwork infrastructure load
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The exponential backoff mechanism creates a periodic reconnection pattern where mobile nodes attempt reconnection at exponentially spaced intervals rather than simultaneously. This periodic action with increasing intervals (1s, 2s, 4s, 8s, 16s, 32s, 64s, 128s, 256s, 512s, 1024s) distributes the reconnection load over time, reducing peak network infrastructure load while ensuring service restoration through eventual successful connections.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent implements preliminary action by having mobile nodes pre-calculate and implement delay timers before attempting reconnection. The exponential backoff algorithm pre-determines the reconnection schedule based on the number of previous failure attempts, allowing nodes to wait appropriately before retrying. This preliminary timing action prevents immediate simultaneous reconnection bursts while maintaining a structured approach to service restoration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8619557B2System and method for managing network traffic load upon outage of a network node
Publication Date: 2013.12.31 MALIKIE INNOVATIONS LTD
  • US8619557B2 patent drawing
  • US8619557B2 patent drawing
  • US8619557B2 patent drawing

AI summary

In one embodiment, a scheme is disclosed for managing network traffic load upon outage of a network node disposed in a wireless packet data network, wherein the network node is adapted to serve a substantially large number of mobile nodes using respective data connections. Upon encountering an outage-causing condition, the network node releases the data connections and generates session termination messages for transmission to the mobile nodes. Responsive to receiving the session termination messages, the mobile nodes variably delay their data session reconnect requests based on randomization.