Distributed GTK State Management for LLN Security

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Centralized link-layer key management in large-scale networks, particularly in Low Power and Lossy Networks (LLNs), faces challenges such as inconsistent GTK state synchronization, high communication overhead, and complexity due to dynamic link technologies and environmental changes, making it difficult to maintain consistent GTK states across devices.

Innovation Solution

A distributed GTK synchronization mechanism where each supplicant determines its GTK state and exchanges it with neighbors, allowing them to identify inconsistencies and perform local synchronization with the authenticator, eliminating the need for the authenticator to store per-supplicant GTK state and reducing communication overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If centralized link-layer key management is used where the authenticator maintains per-supplicant GTK state, then security management is simplified, but communication overhead increases and scalability deteriorates in large-scale networks

Engineering Contradiction:

Improveauthenticator complexityVSAvoidcommunication overhead

Core Design Contradiction:

Device complexityVSQuantity of substance

Solution Approach 1:

The patent extracts the GTK state management responsibility from the authenticator and relocates it to individual supplicants. Each supplicant now maintains its own GTK state locally and performs self-synchronization by comparing its state with neighbors and requesting updates only when inconsistencies are detected, eliminating the need for the authenticator to store per-supplicant state information.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Supplicants autonomously manage their own GTK state by performing local consistency checks with neighbor supplicants and initiating synchronization requests with the authenticator only when needed. This self-service approach eliminates continuous authenticator involvement and reduces communication overhead while maintaining security consistency.

Inventive Principle:

Principle #25Self-service

2Ease of operation

If centralized GTK state management is implemented, then key distribution is simplified, but latency increases and timeliness of GTK updates deteriorates

Engineering Contradiction:

Improvekey distribution simplicityVSAvoidGTK update latency

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

Supplicants continuously monitor and compare their GTK state with neighbor supplicants in advance, detecting inconsistencies before they affect security operations. This preliminary detection enables immediate local synchronization without waiting for periodic authenticator-initiated updates, reducing GTK update latency while maintaining distribution simplicity.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If the authenticator maintains central view of all supplicant state, then security consistency is improved, but device complexity and memory requirements increase

Engineering Contradiction:

Improvesecurity consistencyVSAvoidauthenticator memory requirements

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized GTK state management into distributed local state maintenance at each supplicant. Instead of one authenticator holding all supplicant states, each supplicant holds and manages its own GTK state independently, achieving security consistency through distributed peer comparison rather than centralized tracking.

Inventive Principle:

Principle #1Segmentation

4Productivity

If distributed GTK state management is implemented, then scalability improves and communication overhead reduces, but detection precision of GTK inconsistencies becomes more difficult

Engineering Contradiction:

Improvenetwork scalabilityVSAvoidGTK state inconsistency detection

Core Design Contradiction:

ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

Supplicants implement continuous feedback mechanisms by comparing their GTK state with neighbor supplicants and authenticator beacon information. This distributed feedback loop enables automatic detection of inconsistencies through local observations, maintaining detection precision while achieving scalability without requiring centralized state monitoring.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8800010B2Distributed group temporal key (GTK) state management

Publication Date: 2014.08.05 CISCO TECHNOLOGY INC

AI summary

In one embodiment, each security protocol supplicant in a computer network determines its group temporal key (GTK) state, and exchanges the GTK state with one or more neighbor supplicants in the computer network. Based on the exchange, a supplicant may determine whether any inconsistencies exist in its GTK state, and in response to any inconsistencies in the GTK state, may perform a GTK state synchronization with a security protocol authenticator by indicating to the authenticator what is needed to resolve the inconsistent GTK state at the particular supplicant. In another embodiment, the authenticator, which is configured to not store per-supplicant GTK state, may transmit beacons containing GTK identifiers (IDs) of GTKs currently enabled on the authenticator, and also responds to supplicants having inconsistent GTK states with one or more needed GTKs as indicated by the supplicants.