Develop Future-Ready Gateways with Matter

Agenda

1. Why gateways
2. Matter intro
3. Matter architecture
4. General challenges with gateway development
5. Migration into Matter
6. Unify Framework

Why Gateways?

Introduction and Context

Gateways are essential for the Internet of Things (IoT). However, supporting multiple protocols leads to increased complexity, which acts as a barrier to adoption. Matter represents a significant shift in the prevailing trends. The key question is: How can one adopt Matter?

Image Description: A white IoT gateway device with two antennas, status indicator lights, and ports.

Matter Intro

Paths to Matter End Products

The document outlines three primary paths for developing Matter end products:

• CSA Matter GitHub: This path has numerous gaps to reaching production.
• Silicon Labs Matter GitHub: This path offers improved stability and a more straightforward approach, though some challenges may remain.
• Studio, Tools, and GSDK: This path is presented as the optimal route for mass market adoption, leveraging tools like Simplicity Studio and VS Code.

Each path progresses through stages such as building sample applications, testing on hardware platforms, verified compliance, and integration.

Silicon Labs Matter Solution

HARDWARE

Field Proven SoCs and Modules, supporting Thread, Bluetooth, and Wi-Fi. Includes Certified Thread PHYs.

SOFTWARE

A comprehensive, one-stop-shop for all software needs, featuring a full Matter solution built on top of IP stacks.

TOOLS

Offers Reference Applications, Command Line Interface support, LCD display for QR codes, and Studio support targeted for Q4 2022.

CERTIFICATION

Supports over 50,000 Wi-Fi and 802.15.4 end products deployed. Provides support for end-product certification, with Matter certification expected in Fall of 2022.

Matter Architecture

Matter Protocol Stack

Goal: Matter aims to create a universal IPv6-based communication protocol for smart home devices, defining the application layer and link layers to ensure interoperability.

Key Pillars:

• Application
• Networking

Protocol Stack Layers:

• Application Layer: Defines the application logic.
• Transport Layer: Uses TCP and UDP.
• Network Layer: Utilizes IPv6.
• Link/Media Layer: Supports Ethernet, Wi-Fi, Thread, and 802.15.4.

Matter Application Layer

The Matter application layer focuses on unifying the smart home experience and providing interoperability through:

• Security
• Data model
• Device interactions
• Device types
• Commissioning

The application layer is structured into several components, including the Application layer, Data model, Interaction model, Action framing, Security, Message framing & routing, and IP Framing & transport management.

Matter Networking

Matter networking is largely connectivity technology agnostic, supporting any IPv6-bearing network that adheres to core IPv6 standards. This enables trivial interoperability across many technologies. The presence of non-IPv6 devices presents unique considerations.

Diagram Description: A network diagram illustrating Matter connectivity. It shows devices like a Matter Device, Thread Border Router, Matter Bridge, and Non-IP Devices connected via various networks (Ethernet, Wi-Fi, Thread) to the Internet. It also depicts Matter Controllers and the potential for integration with other ecosystems.

General Challenges

Typical Requirements of an IoT Gateway

• Operating System: Networking, Standard libraries, Development environment, BSP, Shells, etc.
• Remote Monitoring
• Local Access Control
• Security Monitoring
• Platform (OS) Updates
• Application Management: Updates, Monitoring, Control (Start/Stop).
• Connectivity Management: Multiple uplinks, Security.
• Connectivity Monitoring
• Intrusion Monitoring/Alerts
• Alert System: Email/SMS/etc.
• Logging: Syslog may not be sufficient.
• Cloud Integration: Clients, Credential management, Key rotation.
• System Management: Disk space, Configuration.

...'But Wait, There's More!'

• Deployment: Key provisioning, Configuration.
• Connectivity: Infrastructure, Contracts.
• Backend: Management of GW devices (all aspects), Build systems for software, Monitoring (all aspects), Dashboards, Recovery, and more.
• Key Management

Image Description: An IoT gateway device is depicted surrounded by various icons representing key management, configuration (gear), connectivity (Wi-Fi), cloud services, and smart home devices (house).

Questions to Answer

• Bridge vs. Access Point vs. Gateway?
• RTOS vs. Full-fledged OS?
• Line-powered vs. Battery powered? (Is battery backup required?)
• What wireless technology to use?
• Uplink connectivity technology
• Off-the-shelf GW platform or custom development?
• Service architecture – what needs to be local?
• Where to do major development?
• What is the most common transaction?
• Is all/some/none of communication time-critical?
• Who will monitor the system?

The Recipe for a Perfect Matter Gateway?

The core idea is that a Matter Gateway functions much like an Access Point.

Actually Critical Design Requirements:

• Flexible architecture ?
• Extendibility ➕
• Maintainability ⚙️

Migration into Matter

Barriers for Adoption

While Matter offers many promises, several barriers exist for its adoption:

• A large installed base of 'legacy' products.
• Lack of interoperability with existing deployments.
• Difficulty of migration.
• The continuous evolution of technology.

Unify Framework

What is it?

The Unify Framework is a network and application data model abstraction framework designed for system integrators, device vendors, and IoT cloud/platform providers.

What can you do with it?

• Develop a single gateway software base.
• Delegate protocol-specific translations to Unify.
• Maintain a single codebase for business logic across various devices and wireless protocols.
• Seamlessly integrate Matter, Z-Wave, and Zigbee devices, with support for more protocols planned.
• Simplify host processor designs.

How does it work?

It utilizes a common, well-defined data model, API, and status definitions for IoT services like device addition, updating, and removal. Protocol controllers translate these common IoT services into protocol-specific formats.

Diagram Description: The Unify Framework architecture illustrates integration between different ecosystems (ABC and Matter) via bridges and a central Unify Core. It shows various protocol controllers (Z-Wave, BLE, Zigbee, Matter) interacting with their respective stacks, enabling unified device management.

Unify Framework – Matter Integration Components

The Unify Framework integrates Matter by using the Unify SDK-Matter Bridge Application, which communicates with the Unify Core. Protocol controllers translate ZCL commands on the Matter protocol interface into the Unify Controller Language data model and publish them via MQTT. This allows Z-Wave and Zigbee devices to be seen as bridged devices on the Matter fabric. The Unify-Matter bridge application is built upon software from the CSA Alliance.

Getting Started with Unify

To begin using Unify, download the software from GitHub: https://github.com/SiliconLabs/UnifySDK. A GitHub account is required to access the repository.

Diagram Description: The setup involves a Raspberry Pi 4 or Linux Host connected to a Computer Terminal running a Graphical App Dev Tool. It also shows development kits for Zigbee (xG21 Dev Kit) and Z-Wave (700 Long Range Dev Kit), along with a Virtual Remote Terminal.

Thank You