BAS Microservice Architecture for Multi-Node Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Building automation systems (BAS) face scalability and fault-tolerance issues due to the reliance on single server applications, which can lead to costly hardware upgrades and increased risk of system failures when handling high demands.

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, allowing for independent deployment and fault monitoring across multiple nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

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

Engineering Contradiction:
Improvesystem operation simplicityVSAvoidsystem scalability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent divides the single server application into multiple independent microservice nodes that can operate separately. Each node handles specific BAS functions, allowing the system to scale by adding more nodes without complicating the overall operation. The segmentation enables independent deployment and management of different service components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The microservice architecture creates universal service components that can perform multiple functions across different BAS operations. Each microservice node is designed to be multi-functional, handling various monitoring and control tasks, which improves scalability while maintaining ease of operation through standardized interfaces.

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

2Device complexity

If a single server application is used for BAS monitoring and control, then device complexity is low, but reliability deteriorates due to decreased fault tolerance

Engineering Contradiction:
Improvesystem structure complexityVSAvoidsystem fault tolerance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

By segmenting the single server into multiple microservice nodes, the patent distributes system functions across independent units. This segmentation improves reliability through fault isolation - if one node fails, others continue operating - while keeping individual node complexity low and managing overall system complexity through standardized communication protocols.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the structural parameter from a monolithic server to a distributed multi-node architecture. This parameter change transforms the system from single-point-failure to multi-point-redundancy, significantly improving fault tolerance while maintaining manageable complexity through consistent service interfaces and containerization standards.

Inventive Principle:
Principle #35Parameter changes

3Ease of manufacture

If server functionality is consolidated in a single application, then ease of manufacture and deployment is high, but adaptability deteriorates when accommodating more users and field controllers

Engineering Contradiction:
Improvesystem deployment easeVSAvoidsystem capacity for users and controllers
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments server functionality into independent microservices that can be manufactured and deployed separately using containerization technology. This approach maintains ease of deployment through automated container orchestration while dramatically improving adaptability - new microservices can be added to accommodate additional users and field controllers without redeploying the entire system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The microservice architecture introduces dynamic scalability to the system. New service nodes can be dynamically added or removed based on user and controller requirements. The container orchestration platform automatically manages resource allocation and service registration, maintaining ease of deployment while providing flexible adaptability to changing system capacity needs.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20240302808A1Building automation system with microservice architecture to support multi-node on-premise BAS server
Publication Date: 2024.09.12 TYCO FIRE & SECURITY GMBH
  • US20240302808A1 patent drawing
  • US20240302808A1 patent drawing
  • US20240302808A1 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.