Memory-Loaded Software Watermarking for Piracy Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for preventing software piracy are inadequate as they either rely on network-dependent models that frustrate users with speed and reliability issues or require hardware changes that are not easily implementable in conventional desktops, and lack effective tracking of piracy sources.

Innovation Solution

A method that spawns applications without using files on the computer's file system by retrieving protected application data from a remote or local server, encrypting it, and mapping it to inaccessible memory, while watermarking the data with unique identifiers to track piracy sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If software is distributed as files on the file system, then ease of installation and operation is improved, but vulnerability to piracy increases

Engineering Contradiction:
Improveease of installationVSAvoidvulnerability to piracy
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the application code from the file system and loads it directly into memory during execution. This removes the file from being a copyable object, eliminating the piracy vulnerability while maintaining ease of installation through standard file download and execution processes.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces memory as an intermediary between the distributed software and the file system. The application is distributed as a file but mediated through memory loading, preventing direct file copying while maintaining the distribution model.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If software is loaded directly from memory without file system usage, then piracy prevention is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvepiracy preventionVSAvoidease of installation
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent makes the memory loading process transparent and automatic. The system itself handles the conversion from file to memory loading without requiring user intervention or special installation procedures, maintaining ease of operation while achieving piracy prevention.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If software is distributed as executable files, then ease of distribution is improved, but ability to track piracy sources deteriorates

Engineering Contradiction:
Improveease of distributionVSAvoidtracking piracy sources
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent embeds unique watermarks in different locations within the memory-loaded application code for different licensed users. This allows local differentiation of copies while maintaining the same distribution format, enabling piracy source tracking without compromising distribution ease.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent uses watermarking techniques that embed invisible identifiers within the application code, analogous to color changes that are imperceptible to users but detectable for tracking purposes. This enables piracy tracking while maintaining identical distribution files.

Inventive Principle:
Principle #32Color changes

4Object-affected harmful factors

If authorization keys and registration are required, then piracy prevention is improved, but device complexity increases

Engineering Contradiction:
Improvepiracy preventionVSAvoidsystem complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent merges the authorization verification into the memory loading process itself. The licensed user identifier is embedded in the memory structure, combining authentication and execution into a single operation, thereby preventing piracy without adding separate complex authorization systems.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20240045933A1Method and apparatus for preventing and investigating software piracy
Publication Date: 2024.02.08 KOREN PATRICK ROBERT
  • US20240045933A1 patent drawing
  • US20240045933A1 patent drawing
  • US20240045933A1 patent drawing

AI summary

An apparatus, method, and system for curtailing and investigating software piracy is provided. The method includes spawning user applications on a computer without use of a file on the file system. A protected application data source is retrieved by an operating system of the computer from a server and placed into a portion of memory not accessible by at least one application. The operating system also prevents the protected application data source from being written to the file system. In this manner there is no file subject to unauthorized distribution. The protected application data may also be watermarked by ordering at least one of executable functions, function call parameters, and program data according to a license identifier so that any two versions execute the same, but carry an identifier which can be used to trace piracy to the source.