| commit | 47254d56f2824717f8431213441a40ab37266608 | [log] [tgz] |
|---|---|---|
| author | Pradip De <pradipd@google.com> | Mon Mar 17 05:34:19 2025 +0000 |
| committer | GitHub <noreply@github.com> | Mon Mar 17 05:34:19 2025 +0000 |
| tree | fc8db39d8cbc395cb478ef9818bf91b868b8ba13 | |
| parent | 89954f9a6414585f785d756c5d0a4f793bea5d57 [diff] |
Camera AV Stream Management Server Impl (#36204)
* Camera AV Stream Management Server Impl
* Delegate definition
- Support for list entries per index
- Support for Command handlers
* Server Impl
- Attributes and Commands support
-- Setters for Application to update values
* Add attributes to json files
* Autogen code changes to zzz_generated/
* Add Optional Attributes support
* Add support logic for writable attributes.
Modify feature checks for the attributes depending on their optionality
and feature categories.
* Remove some attributes to simplify AVStreamMgmt cluster slightly.
Attributes related to White balance, ShutterSPeed, ISO and Depth sensor
were removed based on feedback at the Nov member meeting.
Also, adjustments for read/write mode changes for certain attributes.
* Remove redundant CurrentSnapshotConfig and CurrentVideoCodecs attributes
Fix name of MaxFramRate in Snapshot Allocation functions.
* Add write support for ImageRotation, ImageFlipHorizontal and ImageFlipVertical attributes.
* Add handler for the SetStreamPriorities command.
* Retrieve persistent attributes from storage during initialization.
* Miscellaneous syntactic fixes to CameraAVStreamMgmt.
* Add persistence for Viewport struct attribute
* Make CameraAVStreamMgmt handle list attributes inside cluster server implementation.
Add Getter functions for cluster attributes.
* Add Delegate functions for loading pre-allocated streams.
Add persistence support for the ranked video stream priorities
attribute.
* Doc updates and adjustments based on latest Spec changes.
* Address review comments.
* Make watermark and OSD optional args.
* Fix
* Add feature and optional flags check in Init
* Modify SetStreamPriorities
* Add error handling for command params.
* Add CameraAvStreamMgmt cluster partially inside all-clusters-app.zap config
Make the snapshot attributes and commands of the CameraStreamMgmt
cluster be part of the all-clusters-app(in a minimalistic way) to
exercise the cluster.
* Add more constraint checking for command params.
Add a delegate notification callback for attribute changes.
Address other review comments.
* Apply suggestions from code review
Co-authored-by: Boris Zbarsky <bzbarsky@apple.com>
* Restyle fixes.
* Add CameraAVStreamMgmt cluster to EP1 of camera-app.zap.
* Remove Enum validation functions.
* Address review comments
- Add endpoint id to logs.
- Add missing constraint checks.
* Various Fixes
- Remove usage of DefaultStorageAllocator for the TLV encoded stored
attributes, and replace them with SafeWriteValue()/SafeReadValue()
APIs from GetSafeAttributePersistenceProvider.
- Make the RankedStreamPriorities a vector and handle the TLV encoding
of the list of enums.
- Populate the CaptureSnapshot response properly with image data
received from delegate.
* Add parameters struct for housing the set of stream allocation parameters for the delegate.
* Add initial delegate implementation in all-clusters-app.
* Update Camera AVStreamMgmt Server SDK based on Spec changes from Spec PR#11309.
* Update all-clusters-app and camera-app with attribute changes.
* Updates to CameraAVStreamMgmt delegate.
* Fix Command de-allocation comments.
* Fix Command code numbering in zap file.
* Add SnapshotStreamModify command support.
* Fix persisted storage handling for Viewport and STream Priorities.
* Address review comments.
* Resolve conflicts in all-clusters-app.matter and camera-app.matter.
* Update src/app/clusters/camera-av-stream-management-server/camera-av-stream-management-server.h
Co-authored-by: Boris Zbarsky <bzbarsky@apple.com>
* Address review comments.
---------
Co-authored-by: Boris Zbarsky <bzbarsky@apple.com>
Builds
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.
