Defining 'apartment' and 'shared infrastructure' in the Matter context
In the context of Multi-Dwelling Units (MDUs), distinguishing between 'apartment' and 'shared infrastructure' is crucial for the successful implementation of the Matter standard. Matter operates with the concept of a 'fabric' – a virtual network where all devices are connected, share a common trusted root, and their security and privileges are managed by an administrator.
For individual apartments, a separate Matter fabric is typically created, with the resident or their hub (Matter controller) acting as the administrator. This aligns with the traditional 'walls in' ownership model, where the resident is responsible for everything within their living space, including finishes, plumbing, and internal electrical systems.
Conversely, shared building infrastructure encompasses elements such as roofs, exterior walls, stairwells, elevators, main engineering systems (e.g., HVAC in common areas), access control systems, and video surveillance in entrances and surrounding areas. These elements are common property, and responsibility for their maintenance lies with the building management (e.g., homeowners' association, management company).
Matter supports Multi-Admin functionality, allowing a device to be part of multiple fabrics simultaneously. This enables, for example, a smart thermostat in an apartment to be managed by both the resident and a centralized Building Management System (BMS) for energy optimization. Matter 1.6 introduced the concept of 'Joint Fabric,' which allows multiple authorized controllers to manage a single shared Matter fabric. This simplifies scenarios for transferring rights in new constructions or professionally managed properties, where different parties (manager, tenants, service providers) require coordinated access to the same devices.
Ownership of Matter devices and data: Individual vs. collective
The question of Matter device and data ownership is key to avoiding conflicts and ensuring security. The device owner is typically the administrator of its Matter fabric.
- Individual ownership: Devices installed by residents in their apartments (smart lighting, outlets, air quality sensors) are their private property. Residents are administrators of their respective Matter fabrics and are responsible for their commissioning, configuration, and data management.
- Collective ownership: Devices that are part of the shared infrastructure (e.g., leak sensors in the basement, access control systems at the entrance, building-wide meters) belong to the building management. In this case, the Matter fabric administrator is the management company or homeowners' association, which is responsible for centralized management, monitoring, and data security.
Clear definition of ownership boundaries should be documented in contracts or residency rules to avoid disputes regarding responsibility for maintenance, repair, and data access. Matter ensures a high level of security through unique device identification, encryption of all communications, and mandatory device authentication before joining the network. This ensures data confidentiality, even if devices from different owners operate on a shared physical network.
Commissioning Matter devices: Challenges in a multi-user environment
Commissioning in Matter is the process of adding a new device to an existing Matter fabric. In a multi-dwelling unit, this process has its own specifics and challenges:
- Multiple administrators: Each apartment may have its own Matter administrator (resident) who adds their devices to their fabric. This requires Matter devices to support Multi-Admin functionality, allowing them to be managed by multiple controllers.
- Security and isolation: It is crucial to ensure that one resident's devices cannot unauthorizedly interact with another's devices or with the shared infrastructure. The Matter commissioning process includes Device Attestation and the use of certificates to establish a trusted connection, enhancing security.
- Convenience for scalability: For large properties, traditional commissioning methods (e.g., via Bluetooth LE with a QR code) may be inconvenient. Matter 1.4.2 introduced Wi-Fi-only commissioning, eliminating the need for an additional Bluetooth radio for some devices and simplifying large-scale deployment. Matter 1.6 went further by introducing NFC-Based Commissioning, which allows devices to be commissioned even before full power-up, ideal for hidden devices like built-in switches or ceiling lights.
For shared infrastructure, commissioning should be centralized, managed by a Building Management System (BMS) or a specialized operator, ensuring uniform security and configuration standards.
Managing shared Matter infrastructure: Networks and controllers
Shared Matter infrastructure in an MDU is based on IP networks, using Wi-Fi, Thread, or Ethernet as transport protocols.
- Network topology: For devices requiring high bandwidth (cameras, smart displays), existing Wi-Fi infrastructure is used. For low-power devices (sensors, switches), a Thread network is ideal, creating a self-healing mesh network with low power consumption. Thread devices require border routers to connect to the main IP network.
- Centralized controllers (hubs): Central controllers are needed to manage a shared Matter fabric. These can be specialized gateways or software solutions integrated into a BMS. These controllers act as fabric administrators, managing access, collecting telemetry, and executing automation scenarios.
- Network security: Matter is designed with a focus on security. All messages are encrypted, and devices are authenticated. This provides protection against unauthorized access and data manipulation. For shared infrastructure, it is critical to implement network segmentation and strict access control policies to isolate traffic from different services and residents.
Lifecycle boundary of Matter devices: From installation to decommissioning
Managing the lifecycle of Matter devices in an MDU covers all stages: from initial installation and setup to firmware updates, maintenance, replacement, and decommissioning. This process must be clearly divided between residents and building management.
- Installation and setup: For devices in apartments, responsibility lies with residents. For shared infrastructure, it falls to building management or contractors. Matter 1.6 with NFC-Based Commissioning simplifies this stage, allowing pre-configuration of devices.
- Firmware Over-the-Air (FOTA) updates: Matter includes mechanisms for secure Over-the-Air (OTA) firmware updates. For shared infrastructure devices, these updates must be centrally controlled and executed by building management to ensure system stability and security. For devices in apartments, residents are responsible for updates, but the management company can provide recommendations or even centralized update management services for compatible devices.
- Maintenance and replacement: Regular maintenance and planned replacement of shared infrastructure devices are the responsibility of building management. For devices in apartments, this is the residents' responsibility. Clear rules and maintenance schedules help extend equipment lifespan and prevent failures. The concept of Building Lifecycle Management (BLM) offers a strategic approach to managing buildings from design to demolition, ensuring optimal performance and efficiency at every stage, including IoT devices.
- Decommissioning: When residents change or the system is upgraded, it is important to correctly decommission devices, removing them from Matter fabrics and ensuring the deletion of confidential data.
Practical checklist for developers and operators
| Criterion | Yes/No | Comments for Developer/Operator |
|---|---|---|
| Are ownership boundaries clearly defined for each Matter device? | Differentiate between resident devices and shared infrastructure. | |
| Which commissioning mechanism is chosen for in-apartment devices and shared infrastructure? | Consider Wi-Fi-only or NFC-Based Commissioning for scalability. | |
| Who is responsible for the maintenance and security of the shared Matter network (Thread/Wi-Fi)? | Define who is responsible for network infrastructure and border routers. | |
| How is data isolation ensured between different apartment owners? | Use Matter fabrics and security mechanisms to separate access. | |
| Is there a plan for firmware updates for all Matter devices? | Develop an FOTA strategy for centralized and individual devices. | |
| Who is responsible for maintaining and replacing shared infrastructure devices? | Identify responsible parties and budget for equipment lifecycle. | |
| Is there a mechanism for transferring ownership/management rights when residents change? | Consider scenarios for changes in apartment owners or tenants. | |
| What security protocols are applied to protect the Matter network and data? | Verify the use of encryption, authentication, and certificates. | |
| Does the Matter system integrate with the shared Building Management System (BMS)? | Ensure interoperability for centralized monitoring and automation. |
Developing and integrating Matter solutions in multi-dwelling units opens new opportunities for the AZIOT platform in terms of centralized management of shared infrastructure and providing tools for building operators. This enables them to effectively manage device lifecycles and data while ensuring flexibility for individual users. AZIOT, by integrating protocols such as MQTT, Modbus, BACnet, KNX, Zigbee, Z-Wave, LoRaWAN, Matter, SCADA, BMS, and ERP, can act as a single point of control for diverse IoT systems. The use of edge processing, Unity Base, rules/scenarios, dashboards, auditing, and access control allows AZIOT to provide the necessary data isolation, flexible rights management, and process automation, which are critical for multi-user environments. Intecracy solutions and inbase.com.ua solutions provide comprehensive tools for enterprise system and automation architects.
Successful Matter implementation in multi-dwelling units depends on meticulous planning and clear definition of responsibilities. Developers and operators must consider the specifics of ownership, commissioning, shared infrastructure management, and device lifecycles to create secure, scalable, and user-friendly IoT systems. Such an approach not only minimizes technical and legal risks but also maximizes the value of smart technologies for all residents and building management.