Skip to content

Commit

Permalink
These are the readme file changes for the specification 1.0 launch . …
Browse files Browse the repository at this point in the history 
…All information are taken out of spec. (#23077)

* These are the readme file changes for the launch of Specification 1.0

* Update README.md

Co-authored-by: Robert Szewczyk <szewczyk@google.com>

Co-authored-by: Robert Szewczyk <szewczyk@google.com>
Co-authored-by: Justin Wood <woody@apple.com>
  • Loading branch information
@NicuAhmadi @robszewczyk @woody-apple
3 people authored Nov 3, 2022
1 parent 7b8c574 commit 64fe656
Showing 1 changed file with 71 additions and 102 deletions.
173 changes: 71 additions & 102 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,133 +20,99 @@

[![ZAP Templates](https://github.com/project-chip/connectedhomeip/workflows/ZAP/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/zap_templates.yaml)

# About
Matter (formerly Project CHIP) creates more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance.

# What is Matter?
Matter is a unified, open-source application-layer connectivity standard built to enable developers and device manufacturers to connect and build reliable, and secure ecosystems and increase compatibility among connected home devices. It is built with market-proven technologies using Internet Protocol (IP) and is compatible with Thread and Wi-Fi network transports.
Matter was developed by a Working Group within the Connectivity Standards Alliance (Alliance). This Working Group develops and promotes the adoption of the Matter standard, a royalty-free connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet. The vision that led major industry players to come together to build Matter is that smart connectivity should be simple, reliable, and interoperable.

Matter simplifies development for manufacturers and increases compatibility for consumers.

The standard was built around a shared belief that smart home devices should be secure, reliable, and seamless to use. By building upon Internet Protocol (IP), Matter enables communication across smart home devices, mobile apps, and cloud services and defines a specific set of IP-based networking technologies for device certification.

Matter (formerly Project Connected Home over IP, or Project CHIP) is a new
Working Group within the Connectivity Standards Alliance (CSA, formerly Zigbee
Alliance). This Working Group plans to develop and promote the adoption of a
new, royalty-free connectivity standard to increase compatibility among smart
home products, with security as a fundamental design tenet.
The Matter specification details everything necessary to implement a Matter application and transport layer stack. It is intended to be used by implementers as a complete specification.

The goal of the Matter project is to simplify development for manufacturers and
increase compatibility for consumers. The project is built around a shared
belief that smart home devices should be secure, reliable, and seamless to use.
By building upon Internet Protocol (IP), the project aims to enable
communication across smart home devices, mobile apps, and cloud services and to
define a specific set of IP-based networking technologies for device
certification.
The Alliance officially opened the Matter Working Group on January 17, 2020, and the specification is [available](https://csa-iot.org/developer-resource/specifications-download-request/) for adoption now.

The CSA officially opened the Matter Working Group on January 17, 2020 and is in
the process of drafting the specification.
Visit [buildwithmatter.com](https://buildwithmatter.com) to learn more and read the latest news and updates about the project.

Visit [buildwithmatter.com](https://buildwithmatter.com) to learn more and read
the latest news and updates about the project.

# Project Overview

## Development Goals

Matter is developed with the following goals and principles in mind:

**Unifying:** Matter will produce a new specification, building with and on top
of market-tested, existing technologies.

**Interoperable:** The specification permits communication between any
Matter-certified device, subject to users’ permission.
**Unifying:** Matter is built with and on top of market-tested, existing technologies.


**Interoperable:** The specification permits communication between any Matter-certified device, subject to users’ permission.


**Secure:** The specification leverages modern security practices and protocols.

**User Control:** The end user is in control of authorization for interaction
with devices.
**User Control:** The end user controls authorization for interaction with devices.


**Federated:** No single entity serves as a throttle or a single point of failure for root of trust.

**Robust:** The set of protocols specifies a complete lifecycle of a device — starting with the seamless out-of-box experience, through operational protocols, to device and system management specifications required for proper function in the presence of change.

**Low Overhead:** The protocols are practically implementable on low compute-resource devices, such as MCUs.

**Federated:** No single entity serves as a throttle or a
single-point-of-failure for root of trust.

**Robust:** The set of protocols specify a complete lifecycle of a device —
starting with the seamless out-of-box experience, through operational protocols,
to device and system management specifications required for proper function in
the presence of change.
**Pervasive:** The protocols are broadly deployable and accessible, by leveraging IP and being implementable on low-capability devices.

**Low Overhead:** The protocols are practically implementable on low
compute-resource devices, such as MCUs.

**Pervasive:** The protocols are broadly deployable and accessible, thanks to
leveraging IP and being implementable on low-capability devices.
**Ecosystem-Flexible:** The protocol is flexible enough to accommodate deployment in ecosystems with differing policies.

**Ecosystem-Flexible:** The protocol must be flexible enough to accommodate
deployment in ecosystems with differing policies.

**Easy to Use:** The protocol should aim to provide smooth, cohesive, integrated
provisioning and out-of-box experience.
**Easy to Use:** The protocol provides smooth, cohesive, integrated provisioning and out-of-box experience.

**Open:** The Project’s design and technical processes should be open and
transparent to the general public, including to non-members wherever possible.

**Open:** The Project’s design and technical processes are open and transparent to the general public, including non-members wherever possible.

## Architecture Overview
Matter aims to build a universal IPv6-based communication protocol for smart home devices. The protocol defines the application layer that will be deployed on devices and the different link layers to help maintain interoperability. The following diagram illustrates the normal operational mode of the stack:
![Matter Architecture Overview](docs/images/Matter_Arch_Overview.png)



The architecture is divided into layers to help separate the different responsibilities and introduce a good level of encapsulation amongst the various pieces of the protocol stack. The vast majority of interactions flow through the stack captured in the following Figure:


![Matter Architecture Overview](docs/images/CHIP_IP_pyramid.png)
![Matter Stack Architecture](docs/images/Matter_Layered_Arch.png)

The Project, as illustrated above, defines the application layer that will be
deployed on devices and controllers as well as the supported IPv6-based networks
to help achieve our interoperability architectural goal. Matter will initially
support Wi-Fi and Thread for core, operational communications and Bluetooth Low
Energy (BLE) to simplify device commissioning and setup.
1. **Application:** High-order business logic of a device. For example, an application that is focused on lighting might contain logic to handle turning on/off the bulb as well as its color characteristics.

The Application Layer can be further broken down into seven main components:

![Matter Stack Architecture](docs/images/CHIP_Arch_Pyramid.png)
2. **Data Model:** The data layer corresponds to the data and verb elements that help support the functionality of the application. The Application operates on these data structures when there is an intent to interact with the device.

1. **Application:** High order business logic of a device. For example, an
application that is focused on lighting might contain logic to handle turning
on/off the bulb as well as its color characteristics.

2. **Data Model:** Data primitives that help describe the various
functionalities of the devices. The Application operates on these data
structures when there is intent to interact with the device.
3. **Interaction Model:** The Interaction Model layer defines a set of interactions that can be performed between a client and server device. For example, reading or writing attributes on a server device would correspond to application behavior on the device. These interactions operate on the elements defined at the data model layer.

3. **Interaction Model:** Represents a set of actions that can be performed on
the devices to interact with it. For example, reading or writing attributes
on a device would correspond to interactions with the devices. These actions
operate on the structures defined by the data model.

4. **Action Framing:** Once an action is constructed using the Interaction
Model, it is framed into a prescriptive packed binary format to enable being
well represented on the “wire”.
4. **Action Framing:** Once an action is constructed using the Interaction Model, it is serialized into a prescribed packed binary format to encode for network transmission. Security: An encoded action frame is then processed by the Security Layer: the message is encrypted and appended with a message authentication code. These actions ensure the data remain confidential and authentic between sender and receiver of the message.


5. **Security:** An encoded action frame is then sent down to the Security Layer
to encrypt and sign the payload to ensure that data is secured and
authenticated by both sender and receiver of a packet.

6. **Message Framing & Routing:** With an interaction encrypted and signed, the
Message Layer constructs the payload format with required and optional header
fields; which specify properties of the message as well as some routing
information.
6. **Message Framing & Routing:** With an interaction encrypted and signed, the Message Layer constructs the payload format with required and optional header fields; which specify the message's properties and some routing information.


7. **IP Framing & Transport Management:** After the final payload has been constructed, it is sent to the underlying transport protocol for IP management of the data.

7. **IP Framing & Transport Management:** After the final payload has been
constructed, it is sent to the underlying transport protocol for IP
management of the data.

# Current Status of Matter

Matter’s design and technical processes are intended to be open and transparent
to the general public, including to Work Group non-members wherever possible.
The availability of this GitHub repository and its source code under an Apache
v2 license is an important and demonstrable step to achieving this commitment.

Matter endeavors to bring together the best aspects of market-tested
technologies and to redeploy them as a unified and cohesive whole-system
solution. The overall goal of this approach is to bring the benefits of Matter
to consumers and manufacturers as quickly as possible. As a result, what you
observe in this repository is an implementation-first approach to the technical
specification, vetting integrations in practice.

The Matter repository is growing and evolving to implement the overall
architecture. The repository currently contains the security foundations,
message framing and dispatch, an implementation of the interaction model and
data model. The code examples show simple interactions, and are supported on
multiple transports -- Wi-Fi and Thread -- starting with resource-constrained
(i.e., memory, processing) silicon platforms to help ensure Matter’s
scalability.
Matter’s design and technical processes are intended to be open and transparent to the general public, including to Working Group non-members wherever possible. The availability of this GitHub repository and its source code under an Apache v2 license is an important and demonstrable step to achieving this commitment.
Matter endeavors to bring together the best aspects of market-tested technologies and redeploy them as a unified and cohesive whole-system solution. The overall goal of this approach is to bring the benefits of Matter to consumers and manufacturers as quickly as possible. As a result, what you observe in this repository is an implementation-first approach to the technical specification, vetting integrations in practice.
The Matter repository is growing and evolving to implement the overall architecture. The repository currently contains the security foundations, message framing and dispatch, and an implementation of the interaction model and data model. The code examples show simple interactions, and are supported on multiple transports -- Wi-Fi and Thread -- starting with resource-constrained (i.e., memory, processing) silicon platforms to help ensure Matter’s scalability.


# How to Contribute

Expand All @@ -160,23 +126,26 @@ Instructions about how to build Matter can be found [here](./docs/README.md).
# Directory Structure

The Matter repository is structured as follows:

| File / Folder | Contents |
| -------------------------------------- | ---------------------------------------------------------------------------------- |
| `build/` | Build system support content and build output directories |
| [BUILDING.md](docs/guides/BUILDING.md) | More detailed information on configuring and building Matter for different targets |
| `CODE_OF_CONDUCT.md` | Code of Conduct for Matter, and contributions to it |
| [CONTRIBUTING.md](./CONTRIBUTING.md) | Guidelines for contributing to Matter |
| `docs/` | Documentation, including [guides](./docs/guides) |
| `examples/` | Example firmware applications that demonstrate use of the Matter technology |
| `integrations/` | Third party integrations related to this project |
| `integrations/docker/` | Docker scripts and Dockerfiles |
| `LICENSE` | Matter [License file](./LICENSE) (Apache 2.0) |
| `BUILD.gn` | Top level GN build file |
| `README.md` | This file |
| `src/` | Implementation of Matter |
| `third_party/` | Third-party code used by Matter |
| `scripts/` | Scripts needed to work with the Matter repository |
| File/Folder | Content |
|--------------------|---------------------------------------------------------------------|
| build | Build system support content and built output directories  |
| build_overrides | Build system parameter customization for different platforms |
| config | Project configurations |
| credentials | Development and test credentials |
| docs | Documentation, including guides  |
| examples | Example firmware applications that demonstrate use of Matter  |
| integrations | 3rd Party integrations  |
| scripts | Scripts needed to work with the Matter repository  |
| src | Implementation of Matter  |
| third_party | 3rd party code used by Matter  |
| zzz_generated | zap generated template code - Revolving around cluster information  |
| BUILD.gn | Build file for the gn build system  |
| CODE_OF_CONDUCT.md | Code of conduct for Matter and contribution to it  |
| CONTRIBUTING.md | Guidelines for contributing to Matter |
| LICENSE | Matter license file  |
| REVIEWERS.md | PR reviewers  |
| gn_build.sh | Build script for specific projects such as Android, EFR32, etc.  |
| README.md | This File |

# License

Expand Down

0 comments on commit 64fe656

Please sign in to comment.