| commit | 0efd31856a278c7b1fc7f5c375673c086a84de01 | [log] [tgz] |
|---|---|---|
| author | Artur Tynecki <77382963+ATmobica@users.noreply.github.com> | Mon Dec 05 20:18:32 2022 +0100 |
| committer | GitHub <noreply@github.com> | Mon Dec 05 19:18:32 2022 +0000 |
| tree | aae2c5e9831a074605371965b40460f8fd87046f | |
| parent | e5342575e6ff5af61f258088902fbb65e15a4b7a [diff] |
[OIS] Platform and examples implementation (#23382) * [OIS] Open IoT SDK build system integration Add Open IoT SDK build system configuration directory. Create GN project to build CHIP library for Open IoT SDK port. Implement CMake file to build and expose CHIP library. Create python script to build GN arguments file. Provide mbedtls and LwIP default configuration. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Open IoT SDK platform layer implementation Add platform layer adaptation files Open IoT SKD platform layer GN build integration Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Open IoT SDK system layer adaptation Add cmsis-rtos locking option. Implement cmsis-rtos system mutex. Open IoT SDK system layer GN build integration. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Add Open IoT SDK platform to common GN build settings Propagate Open IoT SDK platform settings in build system of Matter components. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Open IoT SDK streamer implementation Add Open IoT SDK shell streamer based on SDK retarget. Use default shell main loop. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Open IoT SDK examples common Add Open IoT SDK example platform target that contains source code shared between examples. Create common Cmake settings - sdk, chip and linker common cmake files. Create custome Corstone 300 GCC linker scripts. Create Corstone 300 FVP configuraiton file. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Open IoT SDK shell example Implement Open IoT SDK shell example. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Open IoT SDK lock-app example Implement Open IoT SDK lock-app example. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Open IoT SDK examples helper tools Add Open IoT SDK example script which allows build and run supported examples. Implement OpenIotSdkBuilder Python class with generating and building examples support. Add Open IoT SDK targets to Python builder. Add Open IoT SDK memory configuration to memory script tool. Add Open IoT SDK VSCode tasks integration - build, run and debug OIS examples tasks. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Add Open IoT SDK examples workflow Github workflow to validate Open IoT SDK examples Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Add integration tests for Open IoT SDK examples Add network setup script to enable/disable the TAP/TUN network environment. Create TAP/TUN device and bridge interface to connect it with the ethernet network interface. Create Pytest implementation of Open IoT SDK examples integration tests. Implement lock-app and shell examples tests cases. Add test command to Open IoT SDK example script. Add integrations tests to CI workflow. Add Open IoT SDK examples testing to Vscode tasks. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Add Open IoT SDK platform documentation Create Open IoT SDK platform overview, commissioning approach description and common examples guide. Add README files to shell and lock-app examples. Signed-off-by: ATmobica <artur.tynecki@arm.com> * [OIS] Add Open IoT SDK unit-tests Adaptation changes: Exclude LwIP initialization for Open IoT SDK platform in unit tests implementation. Skip read/write chunking tests in controller component. Skip CommissionerDUTVectors test in credentials component. Skip ControllerTests - #23747 issue Skip CHIP stack initialization in FailSafeContext test. Add Open IoT SDK platform unit-tests application in src/test_driver/openiotsdk/unit-tests directory. Add unit tests to Open IoT SDK example script, CI workflow and VScode tasks. Add unit-tests application documentation. Signed-off-by: ATmobica <artur.tynecki@arm.com> Signed-off-by: ATmobica <artur.tynecki@arm.com>
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.
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.
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 Alliance officially opened the Matter Working Group on January 17, 2020, and the specification is available for adoption now.
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 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 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.
Pervasive: The protocols are broadly deployable and accessible, by leveraging IP and being implementable on low-capability devices.
Ecosystem-Flexible: The protocol is flexible enough to accommodate deployment in ecosystems with differing policies.
Easy to Use: The protocol provides smooth, cohesive, integrated provisioning and out-of-box experience.
Open: The Project’s design and technical processes are open and transparent to the general public, including non-members wherever possible.
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: 
The architecture is divided into layers to help separate the different responsibilities and introduce a good level of encapsulation among the various pieces of the protocol stack. The vast majority of interactions flow through the stack captured in the following Figure:
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 the message's properties and some routing information.
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.
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 | 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 |
Matter is released under the Apache 2.0 license.