Secure Software Deployment via Readable Restricted-Use Tokens

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data extraction systems are time-consuming to deploy and expand, as they require custom scripting and intermingle business logic with data extraction logic, leading to errors, security issues, and reduced integrity of data records. Additionally, deploying software packages onto customer-controlled computing devices is challenging due to security protocols and the difficulty in typing and communicating complex, randomized URLs.

Innovation Solution

A data extraction system that uses programmatically implemented extraction job specifications to perform data extraction without custom scripting, separating business logic from data extraction to enhance security and integrity. Additionally, a software deployment system generates a unique URL with a readable restricted use token for easy typing and secure deployment of software packages onto customer-controlled computing devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom scripting is used for data extraction, then flexibility and adaptability are improved, but reliability and security deteriorate due to errors and bugs

Engineering Contradiction:
ImproveflexibilityVSAvoidreliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the data extraction functionality into standardized, pre-built components that can be configured through parameters rather than custom code. This allows flexibility through configuration while maintaining reliability through standardized implementation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses parameter changes to achieve adaptability. Instead of modifying code through custom scripting, users adjust parameters and configurations to adapt the extraction process to different data sources and requirements, thereby maintaining reliability while achieving flexibility.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If business logic is intermingled with data extraction logic, then functionality is improved, but security and data integrity deteriorate

Engineering Contradiction:
ImprovefunctionalityVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system segments business logic from data extraction logic into separate components. Data extraction is handled by standardized, secure processes, while business logic is applied separately through configured transformations, thereby maintaining functionality while improving security and data integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer that separates data extraction from business logic application. This intermediary handles the extraction securely and passes data to business logic components, preventing direct intermingling and the associated security risks while preserving full functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If complex randomized URLs are used for software deployment, then security is improved, but ease of operation deteriorates due to typing difficulty

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system uses a QR code (visual copy) instead of a complex text URL. The QR code encodes the same deployment information in a visually readable format that can be easily captured and processed, eliminating typing errors while maintaining security through the encoded token.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system replaces the mechanical process of manual URL typing with automated QR code scanning. This substitution eliminates human error in transcribing complex URLs while maintaining the security of the randomized token through the same underlying mechanism.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Ease of operation

If physical storage devices are used for software installation, then ease of operation is improved, but security protocols are violated

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system replaces physical storage device installation with a network-based download process. Software is downloaded securely through the generated URL or QR code, eliminating the need for physical media while maintaining ease of operation through automated download and installation processes that comply with security protocols.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12277201B2Secure deployment of a software package
Publication Date: 2025.04.15 PALANTIR TECHNOLOGIES INC
  • US12277201B2 patent drawing
  • US12277201B2 patent drawing
  • US12277201B2 patent drawing

AI summary

A method of securely deploying a software package comprises storing validity data describing restricted use of a restricted use token; receiving a command including a URL to deploy a software package; testing validity of the URL based on the validity data; and downloading, when the testing is successful, the software package via a secure channel, wherein the method is performed using one or more processors.