Frame Counter Synchronization via Wake-Up Markers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for synchronizing frame counters in data transmission, such as time-synchronization and random numbers, are complex and inefficient, particularly in low-power wireless networks like LoRaWAN, and are susceptible to replay attacks.

Innovation Solution

A method where a second end-device sends a wake-up data frame with a marker to a first end-device, which responds with a data frame containing the synchronized frame counter and marker in the payload, allowing for secure synchronization without constant communication and reducing the need for precise time stamps or random number generation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If time-synchronization with time stamps is used for frame counter synchronization, then synchronization can be achieved, but the complexity increases and performance cannot be guaranteed for rapid data transfer with short send and receive windows

Engineering Contradiction:
Improveframe counter synchronization reliabilityVSAvoidsynchronization process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the synchronization marker from the time-stamp mechanism, using a simple numerical marker value instead of complex time-synchronization protocols. This reduces the synchronization process to exchanging and comparing simple numerical values rather than managing precise time-stamps and synchronization protocols.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the synchronization parameter from time-based (time-stamps requiring precise timing) to counter-based (simple numerical marker values). This parameter change simplifies the synchronization process while maintaining reliability for frame counter synchronization.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If random numbers or nonces are used for authentication, then security can be improved, but the complexity increases due to entropy requirements and buffer memory for storing generated random numbers

Engineering Contradiction:
Improvetransmission securityVSAvoiddata transmission process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses simple, disposable marker values that do not require complex generation mechanisms like random number generators. These marker values are short-lived, used once for synchronization, and then discarded, eliminating the need for entropy management and buffer storage of random numbers.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Solution Approach 2:

The patent changes the authentication parameter from complex random numbers requiring entropy management to simple sequential or predetermined marker values. This simplifies the authentication process while maintaining security through the use of these markers in the synchronization protocol.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If precise time stamps are used for synchronization, then synchronization accuracy can be improved, but energy consumption increases and the system becomes unsuitable for low-power devices with imprecise timers

Engineering Contradiction:
Improvesynchronization precisionVSAvoidenergy consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent replaces the mechanical time-keeping system (precise timers and clocks) with a logical marker-based synchronization system. Instead of relying on hardware timer precision, the system uses exchanged marker values to achieve synchronization, making it suitable for low-power devices with imprecise timers.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent changes the synchronization parameter from time-based (requiring precise timers) to counter-based (using simple marker values). This parameter change eliminates the dependency on precise hardware timers, reducing energy consumption while maintaining synchronization effectiveness.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If constant communication is maintained for frame counter synchronization, then synchronization accuracy can be improved, but energy consumption increases for battery-powered devices

Engineering Contradiction:
Improveframe counter synchronizationVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic synchronization action where marker values are exchanged only when needed (e.g., at the beginning of data transfer or after idle periods) rather than continuously. This periodic approach maintains synchronization reliability while significantly reducing energy consumption for battery-powered devices.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent performs frame counter synchronization in advance (preliminary action) before actual data transfer begins. The marker value is exchanged and synchronized at the start, allowing subsequent data transfers to proceed without continuous synchronization communication, thus reducing energy consumption.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11797693B2Method for synchronizing frame counters and arrangement
Publication Date: 2023.10.24 DIEHL METERING SYSTEMS GMBH
  • US11797693B2 patent drawing
  • US11797693B2 patent drawing
  • US11797693B2 patent drawing

AI summary

A method synchronizes frame counters for protecting data transmissions between a first end-device and a second end-device. The data, in particular data frames, are transferred between the first end-device and the second end-device. The data frames are provided with frame counters to protect the data transfer between the first end-device and the second end-device. The second end-device sends a first data frame to the first end-device. The first data frame contains a marker in its payload data. The first end-device sends back a second data frame as an answer to the second end-device. The second data frame contains a frame counter in the header data, and the second data frame contains the frame counter and the marker in its payload data.