Analysis of Matter Protocol Features (2) Multiple Fabric and Authority Control

 Focus: core products, core market, core information

What I’m talking to you today is how the Matter protocol allows a device to belong to multiple different networks. For better understanding, I call it a device clone; and the permission control logic of the same network;

This article has a total of 630 fonts, and the reading time is estimated to be 6 minutes;

01

Multiple Fabric requirements background

I think there are requirements for ecological compatibility and special scenarios. I will explain them separately.

Ecological Compatibility Requirements:

You bought an air conditioner, and then the living room is a Google speaker, and the bedroom is an Amazon speaker;

You hope that after the air conditioner joins Google Audio, it can continue to join Amazon. At this time, the air conditioner needs to have the ability to support multiple networks;

special scene requirements

Here is a common example, that is, neighbor A installed a camera in the corridor, and then neighbor B saw it and hoped to buy one;

At this time, A directly opens the permission of the camera, so that neighbor B can also add this camera;

02

Implementation of Multiple Fabric

Multiple Administrator 

Matter defines the network as a shared resource, so it supports multiple networks of devices; here Matter supports Multiple Administrator; the Admin here can be understood as a network administrator, who can manage the access rights (Access Control List, ACL) of all nodes in the network ;

Commissioning

The Matter protocol defines an Administrator Commissioning Cluster, which allows to control the distribution network of devices;

The Administrator can make the device enter the network configuration mode through the OpenCommissioningWindow command; 

It should be noted here that during the reopening period, the device should ensure the normal operation of the original network;

03

Introduction to Matter ACLs

The Matter protocol defines an Access Control List (ACL) Cluster, which is used to manage the permissions of nodes;

Endpoint0 of all nodes contains an instance of ACL Cluster, which is used to store device information with access rights;

This AclEngries is managed by a node with Administrator authority, and the ACL that is not responsible for the Administrator cannot be modified (thus supporting the device avatar feature)

>> History related articles

Talking about the Matter protocol (formerly CHIP protocol)

Analysis of Matter protocol features (1) Support for non-Matter protocols

Case analysis, immersive mastering of important concepts of Matter

~~ "Make a friend" ~~

Guess you like

Origin blog.csdn.net/iotthings/article/details/122994211