Building Automation Software Deployment via Central Infrastructure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing building automation systems face complex and time-consuming software update processes due to slow network technologies, which can take hours and require specialized equipment and licenses, posing challenges in maintaining compatibility and security across devices from different manufacturers.

Innovation Solution

A method and system utilizing a central infrastructure device within the building automation system to manage software installation, generating device-model-dependent installation data, and adjusting transmission rates to maintain system operation, allowing for flexible and efficient software deployment across compatible devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional update tools and network technologies are used for software installation, then software updates can be installed on devices, but the process is extremely time-consuming (10-15 minutes per device) and complex

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoidsoftware installation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the software installation process into two distinct phases: a preparation phase where installation data is generated and stored on a USB drive, and an execution phase where the central infrastructure device performs the actual installation. This segmentation allows the time-consuming preparation work to be done offline, while the actual installation leverages the faster local network connection, thereby reducing total installation time while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by generating and preparing all necessary installation data before the actual software update process. The installation data, including device model information and software packages, is pre-configured and stored on a USB drive. This preliminary preparation eliminates the need for real-time data generation during installation, significantly reducing installation time while ensuring data accuracy and reliability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If specialized update tools and licensed ETS software are deployed to maintain security and compatibility, then device security requirements are met, but the system complexity and cost increase

Engineering Contradiction:
Improvedevice security and compatibilityVSAvoidupdate system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent enables the central infrastructure device to perform software installation autonomously using pre-prepared installation data. The device automatically retrieves installation data from the USB drive, identifies target devices based on device model information, and executes the installation process without requiring external update tools or licensed ETS software. This self-service capability eliminates the need for complex external toolchains while maintaining security and compatibility through built-in device intelligence.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a USB drive as an intermediary medium that carries installation data between the preparation environment and the building automation system. This simple intermediary replaces complex licensed software tools by serving as a portable, universal data transfer mechanism that maintains security and compatibility without adding system complexity or licensing requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If slow network technologies are used for software transmission, then existing network infrastructure can be utilized, but the total update time for multiple devices extends to several hours

Engineering Contradiction:
Improvenetwork compatibilityVSAvoidsoftware update speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent changes the dimension of data transmission by moving from network-based transmission to local storage-based distribution. Instead of transmitting software updates over the slow building automation network, the system prepares installation data locally on a USB drive and stores it on the central infrastructure device. This dimensional shift from network transmission to local access eliminates network speed limitations while maintaining compatibility with existing network infrastructure for device communication.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent creates a local copy of all necessary installation data on the central infrastructure device's storage medium. Rather than repeatedly transmitting software packages over the slow network for each device update, the system makes a single copy of the installation data to USB, stores it locally, and then serves multiple devices from this local copy. This copying approach eliminates repeated network transmissions, dramatically improving update speed while maintaining network compatibility for control and monitoring functions.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP4648389A1Method for playing software on at least one device of a building automation system, and system for playing software
Publication Date: 2025.11.12 GIRA GIERSIEPEN GMBH & CO KG
  • EP4648389A1 patent drawingFigure 1
  • EP4648389A1 patent drawingFigure 2
  • EP4648389A1 patent drawingFigure 3

AI summary

The invention relates to a method for installing software onto at least one device (12) of a building automation system (10), for example, a door communication system, wherein the method comprises: receiving device-model-dependent software (20) for installation onto at least one device (12) of a device model compatible with the software, wherein the software (20) preferably comprises updated firmware data; generating installation data, wherein the installation data comprises the received software (20), project data of the building automation system (10), and configuration data (22) of the installation; and installing the software (20) onto at least one device (12) of a device model compatible with the software by means of a central infrastructure device (14) of the building automation system connected to the device, using the installation data, wherein the central infrastructure device (14) preferably is or comprises a central logic unit of the building automation system (10).The invention further relates to a system (50).