Remote Software Usage Tracking via Intermediary Token Relay
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software licensing techniques require network connectivity and a reliable time reference to activate and deactivate software applications on remote devices, which is not feasible for devices without internet access or reliable time references, such as sensors in isolated environments.
Innovation Solution
A system that uses activation and deactivation tokens to track software usage on remote devices without network connectivity, where a computing device relays tokens to enable or disable software features, allowing the system to manage usage without relying on external connectivity or time references.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional software licensing techniques are used to activate and deactivate software applications on remote devices, then software usage can be tracked and managed, but network connectivity and reliable time reference are required which are not available in isolated environments
Solution Approach 1:
The patent introduces a computing device as an intermediary between the software provider system and the remote device. The computing device receives activation tokens from the system and relays them to the remote device, enabling software activation without requiring the remote device to have direct network connectivity. This mediator resolves the contradiction by allowing reliable software management while adapting to isolated environments.
Solution Approach 2:
The patent extracts the network connectivity requirement from the remote device by performing activation and deactivation operations through a local computing device instead. The remote device itself does not need network access; only the intermediary computing device requires connectivity to communicate with the software provider system, thereby enabling isolated environment operation.
2Measurement precision
If network connectivity is required for software activation and deactivation, then accurate usage tracking is possible, but devices in isolated environments cannot receive software updates or activation
Solution Approach 1:
The computing device serves as a mediator that bridges the gap between the networked software provider system and the isolated remote device. It receives precise activation tokens and usage information from the system and delivers them locally, maintaining measurement precision while enabling ease of operation in isolated environments without direct network access.
Solution Approach 2:
The system performs preliminary actions by generating and transmitting activation tokens to the computing device before the remote device needs to use the software. This advance preparation allows the remote device to be activated immediately when needed, without requiring real-time network connectivity during the actual software operation.
3Reliability
If a reliable time reference is required for software licensing, then subscription periods can be accurately managed, but devices without time synchronization cannot enforce licensing terms
Solution Approach 1:
The computing device acts as an intermediary that handles time reference requirements. Instead of requiring the remote device to have its own reliable time reference, the system manages subscription periods through the computing device which can maintain accurate time for licensing operations, thereby enabling subscription management on devices without time synchronization capability.
Solution Approach 2:
The system performs self-service by maintaining its own time reference and subscription management independently of the remote device's timekeeping capability. The software provider system tracks subscription periods and generates appropriately timed activation and deactivation tokens without relying on the remote device to provide or verify time information.
4Ease of operation
If direct network connectivity is implemented on remote devices, then software activation can be performed, but device complexity and power consumption increase
Solution Approach 1:
The computing device serves as an intermediary that consolidates network connectivity requirements. Instead of each remote device needing its own network interface and connectivity capability, a single computing device handles all communication with the software provider system, thereby reducing device complexity while maintaining ease of software activation.
Solution Approach 2:
The computing device performs multiple functions: it acts as a network interface for the remote device, stores activation tokens, manages local software activation, and communicates with the software provider system. This multi-functionality eliminates the need for the remote device to have dedicated network hardware, reducing its complexity while preserving activation capability.
Data Source
AI summary
Described herein are techniques for a system to track usage of a software application on a remote device, without having connectivity to the remote device. The system transmits an activation token to a computing device different from the remote device to activate the software application, and receives a deactivation token generated by the remote device from the computing device when the software application is deactivated. The system uses transmission of an activation token and receipt of a deactivation token as indicators of start and end times of use of the software application. For example, the system uses the indicated start and end times to determine a billing period for use of the software application.