Token Validation Server Using Two-Step Code Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of managing product discounts across numerous retail outlets and the risk of fraudulent use necessitate a system that efficiently monitors discounted products at the individual retailer and consumer level while maintaining high security and control.

Innovation Solution

A communications server and user device system requiring two unique codes for token validation, with a two-step verification process, including a reservation and validation phase, to enhance security and control token usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single unique code is used for token validation at retail locations, then the ease of operation is improved, but the security against fraudulent use deteriorates

Engineering Contradiction:
Improvetoken validation processVSAvoidsecurity against fraud
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The single unique code is segmented into two separate codes: a first unique code displayed at the retail location and a second unique code provided to the user. This segmentation allows the validation process to be divided into two distinct steps, enhancing security while maintaining operational simplicity. The first code identifies the location, and the second code completes the validation, ensuring that both the location and the user are verified.

Inventive Principle:
Principle #1Segmentation

2Reliability

If token usage limits are enforced at the retailer level, then the control over discount abuse is improved, but the device complexity deteriorates

Engineering Contradiction:
Improvecontrol over discount abuseVSAvoidretailer system integration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A central server acts as an intermediary between the user device and the retailer system. The server stores and manages the token usage limits for each retail location, receiving the second unique code from the user device and comparing it against the stored limits. This eliminates the need for complex integration between the retailer's point-of-sale system and the discount management system, as all validation logic resides on the server.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If a two-step verification process is implemented, then the security against fraudulent use is improved, but the loss of time in the validation process deteriorates

Engineering Contradiction:
Improvesecurity against fraudVSAvoidtoken validation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The first unique code is validated in advance to generate a token and reserve the discount for the user. This preliminary action ensures that the discount is allocated to the user before they arrive at the retail location. When the user presents the token along with the second unique code at the location, the validation is completed quickly by simply verifying the second code against the reserved token, minimizing the time required at the point of sale.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3935802B1A communications server and user device for validating a token
Publication Date: 2026.02.18 SANOFI SA(FR)
  • EP3935802B1 patent drawingFigure 1~2
  • EP3935802B1 patent drawingFigure 3~4
  • EP3935802B1 patent drawingFigure 5

AI summary

A Communications Server and User Device for Validating a Token A communications server for validating a token on a user device, the communications server comprising a memory storing: a list of locations; a first unique code associated with each location; a second unique code associated with each location; a user device product threshold; and a number of previously validated tokens for the user device, wherein the communications server is configured to: receive a first communication from the user device specifying the first unique code associated with a particular location; compare the number of previously validated tokens for the user device against the user device product threshold; when the number of previously validated tokens for the user device does not exceed the user device product threshold, send a reservation message to the user device, the reservation message causing the token on the user device to be reserved for use at the particular location; receive a second communication from the user device, the second communication specifying the second unique code associated with the particular location; and in response to receiving the second unique code associated with the particular location, send a validation message to the user device, the validation message causing the token on the user device to be validated.