Mesh Network Provisioning for HVAC Device Key Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

HVAC systems lack efficient methods for provisioning and servicing mesh networks, which are essential for effective communication and operation of networked devices within heating, ventilation, and air conditioning systems.

Innovation Solution

A method and system for provisioning and servicing mesh networks in HVAC systems, involving the use of computers configured with software or firmware to receive user instructions, provision devices with keys, and transfer provisioning data for storage, allowing for the establishment and maintenance of mesh networks using different communication protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If mesh networks are implemented in HVAC systems for device communication, then network connectivity and device coordination are improved, but system complexity and provisioning difficulty increase

Engineering Contradiction:
Improvenetwork connectivityVSAvoidprovisioning difficulty
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary provisioning actions by pre-generating provisioning data containing cryptographic keys and network configuration information before devices join the mesh network. This advance preparation simplifies the actual network joining process and reduces provisioning complexity during deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A central server acts as an intermediary to manage mesh network provisioning. The server generates provisioning data, stores it securely, and distributes it to devices as needed, mediating between the complex network configuration requirements and the simpler device joining process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple communication protocols are used in the mesh network, then device compatibility and communication flexibility are improved, but system complexity and protocol management difficulty increase

Engineering Contradiction:
Improvedevice compatibilityVSAvoidprotocol management difficulty
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The provisioning data structure is designed to be universal and protocol-agnostic, containing essential network joining information that works across different communication protocols. This allows the same provisioning mechanism to support multiple protocols without increasing management complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system manages protocol diversity by changing parameters in the provisioning data rather than creating separate provisioning systems for each protocol. By dynamically adjusting protocol-specific parameters within a unified provisioning framework, the system maintains compatibility while avoiding excessive complexity.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If provisioning data is stored locally on devices, then network autonomy and security are improved, but data management and updating complexity increase

Engineering Contradiction:
Improvenetwork autonomyVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Provisioning data is prepared and validated in advance before being stored locally on devices. This preliminary action ensures data integrity and security while simplifying local storage management, as the data is ready-to-use and requires minimal subsequent management.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The central server acts as an intermediary for provisioning data management, handling generation, storage, and distribution. This mediates between the need for local autonomous storage and the complexity of data management, allowing devices to store data locally while the server manages updates and security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12156034B2Provisioning and servicing mesh networks
Publication Date: 2024.11.26 LENNOX IND INC
  • US12156034B2 patent drawing
  • US12156034B2 patent drawing
  • US12156034B2 patent drawing

AI summary

In an embodiment, a method includes receiving a user instruction to initiate meshnet provisioning. The method also includes provisioning a first device to a meshnet, where the provisioning the first device yields first provisioning data that includes one or more keys. The method also includes provisioning a second device to the meshnet, where the provisioning the second device yields second provisioning data that includes include one or more keys. The method also includes transferring provisioning data that includes the first provisioning data and the second provisioning data to storage on the first device. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the method.