| commit | c1eef5280c9681a63912b92efd7645f1dd78e6ed | [log] [tgz] |
|---|---|---|
| author | Alexandr Kolosov <rikorsev@gmail.com> | Mon Mar 28 18:57:00 2022 +0300 |
| committer | GitHub <noreply@github.com> | Mon Mar 28 11:57:00 2022 -0400 |
| tree | a314c0e5b84dee38b0f57760e89448406912a804 | |
| parent | 125e73c1148979432b19ff692e5d0f83c6778586 [diff] |
[Telink]: BLE commissioning (source part) (#15723) * [Telink]: Add basic skeleton to integrate Telink SDK * [Telink]: Rework Telink SDK integration skeleton * [Telink]: Prepare BLEManagerImpl sceleton for implementation * [Telink]: BLE advertisement is scanable by chip-device-ctrl tool * [Telink]: Fix mDNS error occurs on commissioning window opening * [Telink]: Implement Matter BLE connection * [Telink]: Remove my_ prefix for GATT variables * [Telink]: Implement Matter GATT Services * [Telink]: Fix issue with improper structure alignment * [Telink]: Implement Rx characteristic write handling * [Telink]: Implement Matter BLE secure connection * [Telink]: Move Shutdown implementation to .cpp part * [Telink]: Add data->is_ready flag to manipulate radio driver state * [Telink]: Adapt solution for Thread 1.2 * [Telink]: Increase size of CHIP thread stack due to stack overflow issue * [Telink]: Add board name to CMakeLists.txt * [Telink]: Add HandleThreadStateChange method to automatic BLE disconnection on Thread provisioning * [Telink]: Refactoring of SwitchToIeee802154 and other cleanups and improvements The commit itself is not really stable. It should be definitely cleaned in a future WARNING: for debug purposes, timeouts in src/platform/DeviceControlServer.cpp and src/platform/DeviceControlServer.cpp has been hard-coded with bigger value. The timeouts shall be changed back in the future. * [Telink]: Fix issue with interrupts disabling after commissioning completion * [Telink]: Fix issue with memory corruption in _InitStack() method * [Telink]: Remove debug LED initialization form BLEManagerImpl * [Telink]: Restore default timeouts * [Telink]: Add tlsr9518adk80d overlay to setup clock frequency to 96MHz * [Telink]: Fix issue when Matter GATT characteristics are not discoverable after connection * [Telink]: Modify default CHIP library timeouts to meet Telink IC timings WARNING: This commit shall be reverted before pull request to upstream * [Telink]: Adapt solution for latest Zephyr commit * [Telink]: Change log level * [Telink]: Remove unnecessary SwitchToIeee802154 * [Telink]: Fix issue with non-logging of Detail log level * [Telink]: Fix fail at the end of commissioning * [Telink]: Cleanups * [Telink]: Restyled fix * [Telink]: Update lighting example Readme.md * [Telink]: Remove unnecessary reboot.h include * [Telink]: Fix spelling mistakes * [Telink]: Remove restriction for progress logging * [Telink]: Add HW cryptography support. * [Telink]: Update docker image version to 0.5.59 Co-authored-by: Alex Tsitsiura <alex.tsitsiura@telink-semi.com> Co-authored-by: Andrii Bilynskyi <andriy.bilynskyy@gmail.com>
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 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 CSA officially opened the Matter Working Group on January 17, 2020 and is in the process of drafting the specification.
Visit buildwithmatter.com to learn more and read the latest news and updates about the project.
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.
Secure: The specification leverages modern security practices and protocols.
User Control: The end user is in control of 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 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.
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 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.
Open: The Project’s design and technical processes should be open and transparent to the general public, including to non-members wherever possible.
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.
The Application Layer can be further broken down into seven main components:
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.
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.
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.
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”.
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.
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.
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.
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.
We welcome your contributions to Matter. Read our contribution guidelines here.
Instructions about how to build Matter can be found here.
The Matter repository is structured as follows:
| File / Folder | Contents |
|---|---|
build/ | Build system support content and build output directories |
| 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 | Guidelines for contributing to Matter |
docs/ | Documentation, including 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 (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 |
Matter is released under the Apache 2.0 license.