Smart Building Data Connector With Buffering for Cloud Readiness

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing building management systems have complex, device-specific data connectors that make it difficult to establish flexible connectivity between local and remote cloud devices, limiting data management efficiency and user control over building data.

Innovation Solution

A Smart Building Data Connector (SBDC) with a flexible user interface and intelligent processing that configures, selects, and maps facility data to cloud devices, generating processed data and buffer data to ensure seamless transmission and analytics, even when the remote cloud device is not ready, enabling real-time data analytics and actionable outcomes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If device-specific data connectors with rigid requirements are used, then data transmission reliability is improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidconnector complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal data connector that can connect multiple different local data devices to a single remote cloud device. The connector uses a standardized interface that accepts data from various device types (HVAC, lighting, security systems) and processes them uniformly, eliminating the need for multiple device-specific connectors while maintaining reliable data transmission through standardized protocols and error handling mechanisms.

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

Solution Approach 2:

The connector dynamically adjusts transmission parameters such as data sampling rates, buffer sizes, and communication protocols based on the specific device being connected and the current system state. This allows the universal connector to adapt to different device requirements while maintaining optimal performance and reliability, rather than requiring rigid fixed parameters for each device type.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If device-specific data connectors with rigid requirements are used, then data transmission reliability is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidconnector operation ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The universal data connector automatically performs device detection, configuration, and data mapping without requiring manual setup for each device type. The system self-configures communication parameters, automatically maps data points between different device protocols and the standardized interface, and handles error recovery, significantly reducing operational complexity while maintaining reliable transmission.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary layer between diverse local devices and the cloud that handles protocol translation and data normalization. This intermediary connector absorbs the complexity of dealing with multiple device-specific protocols, presenting a simplified uniform interface to users while ensuring reliable data transmission through professional-grade error handling and data validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If real-time data transmission is implemented, then productivity is improved, but reliability deteriorates when remote device is not ready

Engineering Contradiction:
Improvedata management efficiencyVSAvoiddata transmission reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-configuring buffer zones and establishing communication protocols before actual data transmission begins. The connector prepares receive buffers, validates data formats, and confirms remote device readiness in advance, allowing real-time transmission to proceed smoothly without data loss when devices are temporarily unavailable.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements buffering mechanisms that cushion against transmission failures by storing data temporarily when the remote cloud device is not ready to receive it. The local connector maintains a buffer zone that absorbs data flow variations, ensuring that real-time productivity is maintained locally while reliability is preserved by preventing data loss during remote device unavailability.

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

Data Source

PatentUS20240231292A9Smart building data connector
Publication Date: 2024.07.11 SIEMENS INDUSTRY INC
  • US20240231292A9 patent drawing
  • US20240231292A9 patent drawing
  • US20240231292A9 patent drawing

AI summary

There is described a smart building data connector, and method thereof, of a building management system. The connector receives change of value data from a local data device and generates processed data based on the change of value data and mapping data correlating the local data device to a remote cloud device. The connector attempts to transmit the processed data to the remote cloud device. The connector generates buffer data in response to determining that the remote cloud device is not ready to receive the processed data or the processed data has not been transmitted properly to the remote cloud device. Data analytics are determined based on the change of value data, the processed data, and the buffer data, and an action is performed at the remote cloud device based on the results of the data analytics.