| commit | 06921da8fde3cd1a3c81116b9ba76f2f3ecb03d1 | [log] [tgz] |
|---|---|---|
| author | manjunath-grl <102359958+manjunath-grl@users.noreply.github.com> | Tue May 16 22:02:34 2023 +0530 |
| committer | GitHub <noreply@github.com> | Tue May 16 12:32:34 2023 -0400 |
| tree | 9f26b767b1094387c0367876833782d729fe46dd | |
| parent | 24de6741c88ab4e4be0e09c65d66324ce66cad22 [diff] |
Modified scripts May 12 (#26537) * Fixes issue 761 TC_ALOGIN_12_1 TC_APPLAUNCHER_3_7_1 TC_APPLAUNCHER_3_8_1 TC_APPLAUNCHER_3_9_1 TC_CONTENTLAUNCHER_10_3 TC_CONTENTLAUNCHER_10_6 TC_CONTENTLAUNCHER_10_7 TC_MEDIAPLAYBACK_6_3 Fixes issue 763 TC_BRBINFO_2_1 Fixes issue 764 TC_BDX_2_1 TC_SC_6_1 TC_SU_2_8 TC_SU_3_3 * Modified tests TC_ACE_1_2 TC_ACL_2_5 TC_ACT_2_1 TC_ACT_3_1 TC_ACT_3_2 TC_APPLAUNCHER_3_7_1 TC_APPLAUNCHER_3_8_1 TC_APPLAUNCHER_3_9_1 TC_AUDIOOUTPUT_7_4 TC_BIND_2_1 TC_BIND_2_2 TC_BOOL_3_1 TC_BRBINFO_2_1 TC_BRBINFO_2_2 TC_BR_2 TC_CADMIN_1_16 TC_CC_4_5 TC_CC_6_4 TC_CC_7_5 TC_CC_9_4 TC_CGEN_2_2 TC_CHANNEL_5_4 TC_CNET_4_11 TC_CNET_4_5 TC_CNET_4_6 TC_CNET_4_9 TC_CONTENTLAUNCHER_10_4 TC_CONTENTLAUNCHER_10_7 TC_DA_1_1 TC_DA_1_5 TC_DA_1_6 TC_DESC_2_1 TC_DGGEN_3_1 TC_DGTHREAD_3_1 TC_DRLK_2_10 TC_DRLK_3_3 TC_G_3_2 TC_IDM_1_2 TC_IDM_2_1 TC_IDM_2_2 TC_IDM_3_1 TC_IDM_3_2 TC_IDM_4_1 TC_IDM_4_3 TC_IDM_6_1 TC_IDM_6_2 TC_IDM_6_4 TC_IDM_7_1 TC_ILL_3_1 TC_I_3_2 TC_LCFG_2_1 TC_LTIME_2_1 TC_LTIME_3_1 TC_LVL_2_3 TC_MEDIAINPUT_3_17 TC_MOD_1_3 TC_MOD_2_2 TC_MOD_3_2 TC_MOD_3_3 TC_MOD_3_4 TC_OO_3_1 TC_OPCREDS_3_1 TC_OPCREDS_3_2 TC_OPCREDS_3_3 TC_OPCREDS_3_4 TC_OPCREDS_3_5 TC_OPCREDS_3_6 TC_PCC_3_1 TC_PSCFG_2_2 TC_SC_4_1 TC_SC_4_2 TC_SC_4_9 TC_SC_5_3 TC_SU_4_1 TC_SU_4_2 TC_SWTCH_2_2 TC_SWTCH_3_1 TC_SWTCH_3_2 TC_TMP_3_1 TC_TSTAT_2_2 TC_TSTAT_3_1 TC_TSUIC_3_1 TC_WAKEONLAN_4_1 TC_WNCV_7_1 * Modified tests TC-SC-4.8 TC-IDM-4.1 TC-IDM-4.4 TC-MOD-2.2 TC-IDM-8.1 Automated test: TC-DRLK-2.3 TC-DGTHREAD-2.3 * Modified MOD-3.3 * Fixes issue 516 TC-SC-6.1 Fixes issue 517 TC-ACL-2.9 Fixes issue 518 TC-DGTHREAD-3.5 Fixes issue 519 TC-DGTHREAD-2.2 TC-DGTHREAD-2.3 Fixes issue 520 TC-DGTHREAD-2.1 Fixes issue 521 TC-ACL-2.9 TC-BR-4 Fixes issue 522 TC-BR-1 TC-BR-2 Fixes issue 523 TC-IDM-7.1 Fixes issue 524 TC-CNET-4.2 TC-CNET-4.16 TC-CNET-4.5 Fixes issue 525 TC-IDM-4.2 Fixes issue 451 TC-TGTNAV-8.2 * Auto generated files * Rolled back script TC-ACT-3.1 TC-BOOL-3.1 TC-ALOGIN-12.1 TC-BRBINFO-1.1 TC-BRBINFO-2.1 TC-FLW-3.1 TC-I-3.1 TC-PRS-3.1 TC-PSCFG-3.1 TC-PS-3.1 TC-SWTCH-3.1 TC-WAKEONLAN-4.1 Placholder - CiTests.json Suites - ciTests.json suites - manualTests.json * Auto generated files * Modified scripts TC-ACE-1.5 TC-BRBINFO-1.1 TC-SC-6.1 * Restyled by whitespace --------- Co-authored-by: Restyled.io <commits@restyled.io>
Examples: 
Platforms: 
Tests: 
Tools: 
Documentation: 
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. Visit the Matter SDK documentation page to read it. |
| 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.