Smart Beacon Dynamic ID Generation for Spoofing Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current beacon-based systems are susceptible to hacking and spoofing, allowing hackers to mimic beacon signals and access unauthorized rewards or private user data, and lack verification of a mobile device's presence near a beacon.

Innovation Solution

Implementing smart beacons that dynamically generate unique beacon IDs, which can be validated by application servers, and incorporating additional logic and storage in beacon hardware to execute functions for generating dynamic IDs, ensuring that only authentic devices receive location-based services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If static beacon IDs are used for simple location identification, then ease of operation is improved, but security against spoofing deteriorates

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies dynamics by transitioning from static beacon IDs to dynamic beacon IDs that change over time. The beacon ID is generated based on a seed value and a time counter, ensuring that the ID is different at each interval. This resolves the security issue while maintaining operational simplicity through automated generation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces an intermediary verification mechanism where the server validates beacon IDs by regenerating them using the same algorithm. The server acts as a mediator that confirms the authenticity of the beacon ID without requiring complex cryptographic protocols, thus maintaining ease of operation while improving security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If dynamic beacon IDs are generated and validated by application servers, then security against spoofing is improved, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the security function into two parts: the beacon device generates dynamic IDs using a simple algorithm with a seed value and time counter, while the server handles the verification logic. This segmentation allows the beacon hardware to remain simple while achieving strong security through the server's validation capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The server creates a copy of the beacon ID generation algorithm to verify the authenticity of received beacon IDs. Instead of requiring complex verification protocols, the server simply regenerates the expected ID using the same seed and time parameters and compares it with the received ID, thus reducing device complexity while maintaining security.

Inventive Principle:
Principle #26Copying

3Reliability

If beacon IDs are varied at intervals, then prevention of spoofing is improved, but loss of time for ID regeneration occurs

Engineering Contradiction:
Improveprevention of spoofingVSAvoidtime for ID regeneration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-generating beacon IDs at regular intervals based on the time counter. The beacon device continuously updates its ID according to the elapsed time, so when verification is needed, the correct ID is already generated and ready, minimizing any time loss while maintaining strong spoofing prevention.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3029972B1Smart beacon data security
Publication Date: 2019.09.25 ACCENTURE GLOBAL SERVICES LTD
  • EP3029972B1 patent drawingFigure 1
  • EP3029972B1 patent drawingFigure 2
  • EP3029972B1 patent drawingFigure 3

AI summary

A secure beacon-based system includes beacons that may generate dynamic beacon identifiers. A mobile device application may send a request to an application server, including a dynamic beacon identifier. The application server can locally compute the dynamic beacon identifier and compare it to the received beacon identifier to validate the request and determine whether to respond to the request.