Software Token Authentication for HVAC Component Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current authentication methods for products, such as those in HVAC systems, face challenges in providing reliable and secure authentication due to vulnerabilities in hardware security modules, limited flexibility, and compatibility issues with new models, as well as poor wireless communication networks.

Innovation Solution

Implementing software tokens that can be updated and redeemed, using redundant token dispensers, and error detection and failure management systems to ensure secure and efficient authentication, even in poor wireless communication conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardware security modules are used for product authentication, then authentication capability is provided, but vulnerability to hacking and lack of replaceability increases

Engineering Contradiction:
Improveauthentication capabilityVSAvoidvulnerability to hacking
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the security token functionality from hardware security modules and implements it as software-based tokens that can be stored in conventional memory. This allows the authentication capability to be maintained while eliminating the vulnerabilities associated with hardware security modules, including their susceptibility to hacking and inability to be replaced or updated.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If hardware security modules are used for product authentication, then authentication capability is provided, but flexibility and adaptability to new models decreases

Engineering Contradiction:
Improveauthentication capabilityVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic tokens that can be updated, renewed, and replaced through software mechanisms. Unlike static hardware security modules, these software-based tokens can adapt to new product models and authentication requirements, providing both reliability and flexibility simultaneously.

Inventive Principle:
Principle #15Dynamics

3Productivity

If tokens are transmitted over wireless networks to production line servers, then token delivery is achieved, but communication reliability decreases in poor network conditions

Engineering Contradiction:
Improvetoken deliveryVSAvoidcommunication reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements error detection and failure management systems that prepare compensatory measures in advance for potential communication failures. When network conditions are poor or failures occur, the system has pre-established mechanisms to handle the failure and ensure token delivery, thus maintaining both productivity and communication reliability.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If error detection and failure management systems are implemented, then communication reliability is improved, but system complexity increases

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the system continuously monitors communication status and automatically adjusts its behavior based on detected errors or failures. This feedback-driven approach improves communication reliability through intelligent error handling while managing system complexity by using automated responses rather than complex manual intervention systems.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12166887B2System and method for programming products with software tokens
Publication Date: 2024.12.10 LENNOX IND INC
  • US12166887B2 patent drawing
  • US12166887B2 patent drawing
  • US12166887B2 patent drawing

AI summary

A system for authenticating components using software security tokens receives, from a remote server, a security token that is a software security artifact that is used to uniquely identify a component. The system programs the security token into the component, where programming the security token into the component comprises encoding the component with the security token such that the security token in retrievable upon request for authenticating the component. The system generates a report file comprising the programmed security token. The programmed security token is used to authenticate the component. The system transmits the report file to the remote server.