Software Copy Protection via Non-Image Validation Tokens

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In regulated environments like casino-type gaming, existing software protection methods are limited as they cannot embed unique identification data in software copies due to strict requirements for exact replica integrity, preventing unauthorized copying.

Innovation Solution

A method and medium that apply a validation token to a software element on a carrier medium by combining image data and a unique identifier using a predetermined algorithm, ensuring only authorized copies can execute by verifying this token.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If unique identification data is embedded in each authorized software copy, then software copying can be tracked and unauthorized copies detected, but software image integrity is compromised and regulatory compliance is violated

Engineering Contradiction:
Improvesoftware copy trackingVSAvoidsoftware image integrity
Core Design Contradiction:
ReliabilityVSManufacturing precision

Solution Approach 1:

The patent divides the carrier medium into two distinct areas: an image area containing the software element that must remain identical across all authorized copies, and a non-image data area containing the validation token that can vary between copies. This segmentation allows each area to serve its specific function - the image area maintains regulatory compliance through exact replication, while the non-image area enables copy tracking through unique validation tokens.

Inventive Principle:
Principle #1Segmentation

2Object-affected harmful factors

If software protection methods are applied in regulated environments, then unauthorized copying can be prevented, but the ability to maintain exact replica integrity is limited

Engineering Contradiction:
Improveunauthorized copyingVSAvoidregulatory compliance
Core Design Contradiction:
Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The patent introduces a validation token as an intermediary element that mediates between software protection requirements and regulatory compliance. The validation token is written to the non-image data area and serves as a bridge - it enables copy protection functionality while the separate image area maintains exact replica integrity for regulatory compliance. The validation token acts as a mediator that allows the system to satisfy both competing requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If validation tokens are applied to carrier media, then unauthorized execution can be prevented, but carrier medium complexity increases

Engineering Contradiction:
Improvesoftware execution authorizationVSAvoidcarrier medium structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent adds a new dimension to the carrier medium by introducing a non-image data area that is distinct from the traditional image area. This dimensional separation allows the validation token to be stored in a different space than the software element itself. The carrier medium is thus organized into multiple dimensions or areas, each serving specific functions, which manages complexity by providing clear separation of concerns rather than mixing protection data with software code.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS9892590B2Systems and methods for data protection
Publication Date: 2018.02.13 AINSWORTH GAME TECH
  • US9892590B2 patent drawing
  • US9892590B2 patent drawing
  • US9892590B2 patent drawing

AI summary

A data protection method includes identifying data indicative of a software element parameter of a software element to be protected, which may be a hash of the software element image or carrier media image area. The method includes identifying data indicative of a medium parameter of a medium authorized to carry the software element, which may be a unique identifier embedded in a non-image area of the medium. A validation token is defined based on a predefined protocol and written to a non-image area of the medium, which token is a function of the software element parameter and medium parameter. A device for executing the software element uses the same predefined protocol to verify the token prior to allowing execution of the software element. If the software element is copied to another medium, the validation token is not verifiable for the copied software, thereby restricting execution of the copied software element.