Local License Validation via Embedded Hash for JavaScript Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional license validation methods require pre-defined license keys, external server connections, or hardware installations, which are not suitable for developers creating client-side JavaScript applications who need to restrict access to licensed software without these dependencies.

Innovation Solution

A method using a processor on a user device to generate and store a hash based on license parameters, integrating software access through a web crypto API, allowing license validation without external dependencies, by scanning and interpreting the hash upon element rendering on a web page.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional license validation methods are used (requiring pre-defined license keys, external server connections, or hardware installations), then license security and control are improved, but system complexity and ease of operation deteriorate

Engineering Contradiction:
Improvelicense securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the license validation logic from external dependencies (servers, hardware devices) and embeds it directly into the software application. The license key is integrated into the software code itself, allowing validation to occur locally without requiring external infrastructure, thus reducing system complexity while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The software application performs license validation independently using its own embedded license key and validation logic. The application serves itself by checking the license status locally without requiring external verification services, eliminating the need for additional hardware or network connections while maintaining reliable license control.

Inventive Principle:
Principle #25Self-service

2Reliability

If conventional license validation methods are used (requiring pre-defined license keys, external server connections, or hardware installations), then license control is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvelicense controlVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent combines the license validation functionality with the main software application into a single integrated system. The license key is merged into the software code, and validation occurs automatically as part of the normal application execution flow, eliminating the need for separate validation steps or external interactions and thereby improving ease of operation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The software application autonomously validates its own license status using embedded credentials and logic. This self-service approach eliminates the need for users to manually connect to external servers or install additional hardware, making the licensing process transparent and effortless while maintaining strict license control.

Inventive Principle:
Principle #25Self-service

3Reliability

If online license validation is used (requiring connection to external network), then centralized license management is improved, but productivity and speed deteriorate

Engineering Contradiction:
Improvecentralized license managementVSAvoidvalidation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the license management functionality by distributing the validation logic and credentials to individual software copies. Each application instance contains its own embedded license key and validation capability, allowing independent local validation without requiring centralized server communication, thus dramatically improving validation speed while maintaining license management integrity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11698948B2Systems and methods for validating licenses
Publication Date: 2023.07.11 FUSIONCHARTS INC
  • US11698948B2 patent drawing
  • US11698948B2 patent drawing
  • US11698948B2 patent drawing

AI summary

A method for license validation is disclosed herein, including receiving one or more strings of one or more parameters defining a license authorizing access to at least one or more portions of software, generating a first hash based on the one or more parameters defining the license and a key, storing parameters defining the generated first hash, storing the generated first hash, responsive to an element rendering on a web page, determining a version of an application program interface used to generate the first hash and the key used to generate the hash, by interpreting the hash, and integrating the one or more portions of software for use by a user. The one or more portions of software are integrated based on the one or more parameters defining the license embedded in the first hash.