Dynamic Key Update Timing for Secure Multicast Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face inefficiencies in managing key updates in secure multicast groups, leading to uneven server load distribution and potential security risks due to frequent key changes, which can cause communication bottlenecks and security vulnerabilities.

Innovation Solution

A method and system for determining a time delay in sending key update requests, where a computing device sends initial and subsequent requests after random and maximum update parameters, adjusting based on load data comparisons to distribute the load evenly and prevent unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If key updates are performed frequently to maintain security, then security is improved, but server load increases and communication traffic increases

Engineering Contradiction:
ImprovesecurityVSAvoidserver load
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic adjustment of key update intervals based on real-time server load conditions. The system transitions from static fixed intervals to dynamic adaptive intervals, where the update frequency is continuously adjusted according to observed server load patterns, allowing the system to optimize between security and server load considerations

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the temporal parameter of key updates from fixed intervals to variable intervals based on load data. By modifying the time parameter dynamically according to server load conditions, the system can reduce unnecessary updates during low-load periods while maintaining security during high-load periods

Inventive Principle:
Principle #35Parameter changes

2Reliability

If key updates are performed frequently to maintain security, then security is improved, but communication traffic increases causing bottlenecks

Engineering Contradiction:
ImprovesecurityVSAvoidcommunication traffic
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system dynamically adjusts the key update frequency based on real-time communication traffic conditions and server load, reducing the number of update requests during periods of high traffic to prevent communication bottlenecks while maintaining adequate security

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements a feedback mechanism where the system monitors server load and communication traffic patterns, using this information to adjust future key update timing. This closed-loop approach allows the system to learn from past behavior and optimize update intervals to minimize communication overhead

Inventive Principle:
Principle #23Feedback

3Device complexity

If fixed time delay is used for key update requests, then implementation is simple, but server load distribution is uneven

Engineering Contradiction:
ImproveimplementationVSAvoidserver load distribution
Core Design Contradiction:
Device complexityVSStability of the object's composition

Solution Approach 1:

The patent transforms the static fixed time delay into a dynamic adaptive delay mechanism that responds to real-time server load conditions, achieving more uniform load distribution across the server while remaining practically implementable through automated load monitoring and adjustment

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8588420B2Systems and methods for determining a time delay for sending a key update request
Publication Date: 2013.11.19 PANASONIC HOLDINGS CORP
  • US8588420B2 patent drawing
  • US8588420B2 patent drawing
  • US8588420B2 patent drawing

AI summary

A method for determining a time delay for sending an update request by a computing device is described. A first update request is sent by a computing device at the termination of a first random delay. A first load data is received. A second update request is sent by the computing device at the termination of a maximum update parameter. A second load data is received. The first load data is compared with the second load data. A next update time is adjusted if the first load data differs from the second load data.