Keep-Alive Signaling Dynamic Timeout Determination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for determining keep-alive timer timeout values in network architectures, such as those involving NAT nodes or PDP contexts, are inefficient and often require additional negotiation or deployment of specific protocols, leading to increased battery consumption and unnecessary signaling due to the lack of a global solution for determining exact timeout values.

Innovation Solution

The method involves requesting and provisioning timeout values using existing signaling methods like the 3GPP Non-Access-Stratum (NAS) protocol, Dynamic Host Configuration Protocol (DHCP) versions 4 or 6, or IPv6 Neighbor Discovery protocol, allowing terminal apparatuses to determine exact timeout values for keep-alive timers associated with NAT nodes, firewalls, or PDP contexts, thereby reducing keep-alive data packets and radio network signaling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If periodic dummy keep-alive packets are transmitted to maintain connection through NAT nodes or firewalls, then connection reliability is improved, but battery consumption and radio network signaling increase

Engineering Contradiction:
Improveconnection reliabilityVSAvoidbattery consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent changes the parameter of keep-alive timing from fixed periodic transmission to dynamic timing based on actual data traffic patterns. The network entity monitors the timing of actual uplink data packets and adjusts the keep-alive timer accordingly, transmitting keep-alive packets only when needed to maintain NAT bindings or firewall rules, rather than using fixed periodic dummy packets.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system uses actual application data traffic to serve the dual purpose of both application communication and keep-alive functionality. Instead of separate dummy keep-alive packets, the timing and presence of actual data packets self-service the connection maintenance function, eliminating redundant transmissions.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If fixed periodic keep-alive packets are transmitted, then connection maintenance is simplified, but network traffic and signaling overhead increase

Engineering Contradiction:
Improveconnection maintenanceVSAvoidnetwork traffic
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent transforms the keep-alive mechanism from fixed periodic parameter to dynamic parameter based on actual traffic patterns. The network entity monitors uplink data packet timing and adjusts keep-alive transmission timing dynamically, reducing the quantity of keep-alive packets while maintaining connection reliability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

Instead of continuous periodic keep-alive packets, the system applies partial action by transmitting keep-alive packets only at necessary intervals determined by actual data traffic patterns, reducing overall network traffic while maintaining sufficient connection maintenance.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If terminal apparatus transmits keep-alive packets at frequent intervals, then connection reliability is improved, but battery consumption increases

Engineering Contradiction:
Improveconnection reliabilityVSAvoidenergy loss
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent changes the frequency parameter of keep-alive transmissions from fixed high frequency to variable frequency based on actual data traffic patterns. The network entity provides timing information to the terminal, allowing it to adjust its transmission schedule and avoid unnecessary energy-consuming transmissions while maintaining connection reliability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The network entity provides feedback to the terminal apparatus regarding timing information for keep-alive transmissions. This feedback mechanism allows the terminal to optimize its transmission schedule based on network conditions and actual traffic patterns, reducing energy loss while maintaining connection reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2705724B1Keep-alive signalling
Publication Date: 2021.07.14 NOKIA TECHNOLOGIES OY
  • EP2705724B1 patent drawingFigure 1
  • EP2705724B1 patent drawingFigure 2
  • EP2705724B1 patent drawingFigure 3

AI summary

Various methods for determining network entity timeout values to improve keep-alive signaling are provided. One example method may comprise providing for transmission of a request for a timeout value associated with a keep-alive timer. The method of this example embodiment may further comprise receiving a response to the request, wherein the response comprises an indication of the timeout value of the keep-alive timer. Additionally, the method may further comprise determining an expiration time of the keep-alive timer based at least in part on the timeout value. The example method may further comprise providing for transmission of a keep-alive data packet prior to the determined expiration time. Similar and related example methods, example apparatuses, and example computer program products are also provided.