BAS Microservice Architecture for Scalable Multi-Node Servers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Building automation systems (BAS) face scalability and fault-tolerance issues due to reliance on single server applications, which can lead to costly hardware upgrades and system downtime when demand increases.

Innovation Solution

Implementing a microservices architecture with a server platform that decomposes server functionality into separate services, using containerization technology, orchestration networks, and a common data model to manage communication and data storage across multiple nodes, both on-premise and in the cloud.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single server application is used to control and monitor BAS devices, then the system structure is simple and ease of operation is maintained, but scalability deteriorates and fault tolerance decreases when usage increases

Engineering Contradiction:
Improveease of operationVSAvoidscalability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent divides the single server application into multiple independent microservice nodes (first node, second node, third node, etc.), each capable of handling specific BAS operations. This segmentation allows the system to scale horizontally by adding more nodes without increasing complexity of individual components, resolving the contradiction between operational simplicity and scalability.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If a single server application is used, then device complexity is low, but reliability deteriorates due to lack of fault tolerance

Engineering Contradiction:
Improvedevice complexityVSAvoidfault tolerance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent merges multiple identical microservice nodes into a distributed system where each node provides the same functionality. This combination creates redundancy, ensuring that if one node fails, others can continue operating, thereby improving reliability without significantly increasing overall system complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system changes the parameter of node quantity from single to multiple, and introduces orchestration mechanisms to manage these nodes. This parameter change enables fault tolerance while keeping individual node complexity low, as each node remains a simple, standardized unit.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If server functionality is decomposed into separate microservices, then scalability and fault tolerance are enhanced, but device complexity increases

Engineering Contradiction:
Improvefault toleranceVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates universal microservice nodes that can perform multiple BAS operations (monitoring, control, data collection) through standardized interfaces. This multi-functionality reduces the need for specialized components, managing complexity while maintaining the benefits of service decomposition for reliability and scalability.

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

Solution Approach 2:

The patent introduces an orchestration layer as an intermediary that manages communication and coordination between microservice nodes. This mediator handles the complexity of inter-node interactions, allowing individual nodes to remain simple while the overall system achieves high reliability through coordinated operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If microservice architecture with multiple nodes is implemented, then scalability improves allowing more users and field controllers, but system complexity increases

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent transitions from a vertical scaling model (adding power to a single server) to a horizontal scaling model (adding more nodes in a distributed network). This dimensional change in architecture allows scalability without proportionally increasing system complexity, as each added node operates independently with standardized protocols.

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

Data Source

PatentUS10962946B2Building automation system with microservice architecture to support multi-node on-premise bas server
Publication Date: 2021.03.30 TYCO FIRE & SECURITY GMBH
  • US10962946B2 patent drawing
  • US10962946B2 patent drawing
  • US10962946B2 patent drawing

AI summary

A building automation system (BAS) with microservice architecture. The system includes a server platform configured to perform various operations within the building automation system. The server platform includes a microservices platform configured to execute various processes within the BAS. The microservices platform includes a plurality of nodes where each node is configured to run one or more services as separate processes. The microservices platform further includes a message bus configured to control communication between processes and an orchestration network configured to control communication between the plurality of nodes. The server platform further includes a common data model (CDM) shared between the plurality of nodes where the CDM consists of metadata of the BAS. The server platform further includes a container orchestration platform configured to manage and control the plurality of nodes.