Matter certification
Matter offers full certification, including test specification, certification program, and certification framework.
Read the following sections for an overview of the Matter certification process. For detailed information, see the official Certification Policy documentation from Connectivity Standards Alliance (CSA). This and other documents related to certification are available in the Matter Resource Kit to Matter members.
The public listing of certified Matter products is available at the CSA Certified Products Database page.
Certification types
You can apply for certification of the following types:
- Certified Product
An end product that has obtained certification. The Certified Product label confirms that the product is fully compliant to the Matter standard and allows the product to use the Certified Product logo.
- Certified Software Component
A software feature of a Supported Operating Environment (SOE).
This page offers general introduction to the Matter certification process, and so it makes no distinction between these types. It uses the term Matter component to refer to both of them.
Certification process overview
Each certification is preceded by a testing phase. The testing confirms that the Matter component is following the Matter standard, as described in the Matter specification. The certification is the official recognition of the conformity to the standard.
The following figure provides an overview of the Matter certification process steps.
Initial requirements: Membership at CSA
Before you start applying for the Matter certification, you must join CSA, as detailed in the following table.
Technology certification |
Stage for certification |
SDO to join |
Minimum SDO membership level required |
---|---|---|---|
Matter Certification |
Production |
Adopter |
Joining CSA allows you to meet the following requirements:
Familiarity with the Matter Core Specification, which is the standard for the certification. You can download it from the CSA Specifications Download Request page.
Assignment of Vendor ID (VID), which is required when applying for certification. You can apply to CSA’s Certification Team to obtain VID. The VID codes are valid immediately upon assignment.
Testing
The Matter certification process requires testing before any application for certification is sent. The testing can be performed at an Authorized Test Laboratory (ATL), using a test plan developed by CSA. Each ATL has its own submission process, but all require a Declaration of Conformity and a Protocol Implementation Conformance Statement (PICS). Both documents confirm that the Matter component you are going to certify is meeting the protocol requirements.
The ATL can contact you if your Matter component is failing any of the test cases.
You can find the list of available ATLs on the CSA’s Testing Providers page.
Reporting
After the Matter component successfully passes all required test cases, the ATL sends a test report to both you and CSA. The test report summarizes the testing process and includes a variety of information, including details about the device, Certification types, test plans, and Test Harness.
Application
Once you have obtained the test report for your Matter component, you can apply for the certification to CSA. You can do this online from the CSA Member Resources page using the different Certification and Testing tools to submit the required documentation.
Application requirements
The final application for certification requires you to send the following documents to CSA:
Declaration of Conformity
Description of the Matter component to be certified (and photos of the end product, for the product certification)
PICS
You can generate the PICS in the XML format using CSA’s PICS Tool, available from CSA Member Resources page.
Dependent Transport Attestation
When applying for Matter certification, you must present a self-attestation that confirms you have applied for and obtained the certification for the transport platform you are using for your Matter component. The processes for obtaining such certification are governed by different Standard Development Organizations (SDOs). See the Dependent certification requirements for more information about the processes compatible with the Matter platform in the nRF Connect SDK.
CSA provides attestation forms to its members on the Matter Attestation Form directory page.
Matter Attestation of Security
For a Matter component to be certified, CSA’s policies require an Attestation of Security that provides detailed information about the security level of the Matter component. The attestation document lists robustness security requirements based on the Matter Core Specification. The product developer must indicate the level of compliance and briefly justify the choice.
The attestation must be filled by the person responsible for end product certification who meets the following requirements:
The person’s organization is a member of the Matter community.
The person has an account on the Connectivity Standards Alliance Certification Web Tool.
Once both these requirements are met, the responsible person can download the Matter Attestation of Security template, fill it in, and submit it in the certification web tool when applying for the certification.
Processing
During this stage of the certification process, CSA verifies the submission for relevant criteria, including relevant documentation, membership in CSA, completion of testing, and payment of applicable fees. The duration of this step depends on the complexity of your application and the length of the review queue.
Certification
At the end of a successful processing, the Matter component is granted the certification.
CSA will ensure that the following certification actions are completed when the certification is granted:
Certificate of compliance is sent to the certification requester.
The newly certified Matter component is listed on the CSA Certified Products Database page.
Matter certified logos are available from the Certification Web Tool dashboard.
Certification Declaration file is available for download.
Certification record is entered into Matter Distributed Compliance Ledger.
Matter certification process variants
The standard Matter certification process has several variants that you can use if you want to certify several products of the same family or you have already obtained the certification.
Product Family certification
The Product Family certification lets you certify several variants of the same product. In this certification path, the first product must be tested according to the original certification process at an ATL. Then, you can apply for certification of the first product and a number of other products from the same family.
To be considered of the same family, the other products must meet the following criteria:
All products must share the same device type as the first product.
All products must be variants of the first product, which should also be the most feature complete.
All products must conform with the Matter specifications, regardless of differences.
Certification by Similarity
Certification by Similarity lets you certify products that derive from a previously certified product. This variant is meant for Matter components that use Matter software that was already certified as part of either the standard procedure or the Product Family certification.
Rapid Recertification program
Note
The Rapid Recertification program is currently experimental. You can read more about it in a dedicated document in the Matter Resource Kit.
The Rapid Recertification program lets you perform the product testing using the services of a qualified CSA Member, even your own organization, instead of an ATL. This allows for a potentially more streamlined recertification process when you want to certify The first certification must still be done at an ATL.
Dependent certification requirements
Because Matter is an application layer, it relies on proven technologies for network connectivity. These technologies come with their own certification processes governed by different Standard Development Organizations (SDOs).
Matter over Thread certification requirements
The following table lists Matter over Thread certification requirements for when a product moves to production.
Technology certification |
Stage for certification |
SDO to join |
Minimum SDO membership level required |
---|---|---|---|
Bluetooth QDID |
Production |
Adopter |
|
Thread Group Certification |
Production |
Implementer |
Bluetooth and Thread certifications can be inherited from Nordic Semiconductor (see the following section).
Matter dependent certification inheritance
If your product uses qualified Bluetooth stack and certified Thread libraries provided as part of the nRF Connect SDK, you can inherit certification from Nordic Semiconductor, provided that you do not introduce any changes to these stacks. In practice, this means reusing Nordic Semiconductor’s certification identifiers, which were obtained as a result of the official certification procedures.
Note
The inheritance is granted by the related SDO after you join the organization and apply for certification by inheritance. The procedure differs from SDO to SDO and has different names. For details, contact the appropriate certification body in the SDO.
Certification identifiers
Nordic Semiconductor provides the following certification identifiers:
Bluetooth Qualified Design IDs (Bluetooth QDIDs) - Obtained in accordance with Bluetooth SIG’s Qualification Process.
Thread Certification IDs (Thread CIDs) - Obtained in accordance with Thread Group’s certification information.
You can visit the following pages on Nordic Semiconductor Infocenter to check the Bluetooth QDIDs and Thread CIDs valid for SoCs that support Matter applications:
Certification document templates
Some of the certification documents require providing information about Nordic Semiconductor’s SoCs or the nRF Connect SDK. To help you with filling in these documents, Nordic Semiconductor can provide you with appropriate templates.
To request and obtain such documents, open a private ticket on DevZone after you join the related SDO.
Note
Nordic Semiconductor provides just an example answers based on the reference SDK applications, which may guide you on how to answer to certain platform-related questions. You are still solely responsibility for filling original documents according to a product specifiction. The final approval depends on the Director of Certification in the given Standards Developing Organization (SDO).