Software Patch Conversion for Illegitimate Copy Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods can only hinder the use of illegitimate software copies, but not replace them with legitimate ones, thus failing to fully address copyright infringement and revenue loss for software producers.

Innovation Solution

A method and system that determine metadata differences between illegitimate and legitimate software copies, using a software patch to replace the former with the latter, including a first patch component to overwrite illegitimate components and a second component for authentication and user interface to facilitate legitimate usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing techniques are used to identify and hinder illegitimate copies, then copyright protection is improved, but user conversion to legitimate copies is not achieved

Engineering Contradiction:
Improvecopyright protectionVSAvoiduser conversion to legitimate copies
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent converts the harmful presence of illegitimate copies into a beneficial opportunity by using the illegitimate copy itself as a delivery mechanism for the patch. The patch, disguised as a legitimate update, replaces the illegitimate copy with a legitimate one, turning copyright infringement into a conversion opportunity for legitimate licensing.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Solution Approach 2:

The patent introduces a patch as an intermediary element that mediates between the illegitimate copy and the legitimate software. This patch serves as a bridge, containing both the legitimate software components and the licensing mechanism, enabling smooth transition without direct user action.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If illegitimate copies are allowed to run with restricted features, then user engagement is maintained, but revenue loss from unauthorized usage continues

Engineering Contradiction:
Improveuser engagementVSAvoidrevenue loss
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent performs preliminary action by embedding the licensing mechanism and legitimate software components into the patch before it is applied. The authentication system is pre-configured to detect whether the software is running legitimately, and revenue collection is built into the activation process, ensuring that revenue loss is prevented from the moment of conversion.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If complete blocking of illegitimate copies is implemented, then copyright protection is strengthened, but user experience and potential revenue conversion are lost

Engineering Contradiction:
Improvecopyright protectionVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamics by making the software state changeable. Instead of a static blocked state, the software can dynamically transition from illegitimate to legitimate status through patch application. The system adapts its behavior based on authentication status, enabling full functionality when legitimate and restricted functionality when illegitimate, thus preserving user experience while protecting copyright.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9038057B2Method for replacing an illegitimate copy of a software program with a legitimate copy and corresponding system
Publication Date: 2015.05.19 SONY DADC AUSTRIA
  • US9038057B2 patent drawing
  • US9038057B2 patent drawing
  • US9038057B2 patent drawing

AI summary

A method for replacing an illegitimate copy of a software program with a legitimate copy is provided, the method including: determining metadata of a first software program running on a computer; transmitting a patch from a first server to the computer, if the metadata does not correspond to metadata of a legitimate copy of the software program; generating a second software program by replacing at least a part of the first software program with the patch; displaying a graphical user interface using code components of the patch and asking a user for an authentication token; acquiring the authentication token from a second server; verifying the authentication token; and labeling the second software program as a legitimate copy if the authentication token is verified. A corresponding system is also provided.