Documents

The purpose of this document is to define the requirements for products participating in the prpl Certification Program. The document does not define specific test cases, but rather referencing how the test requirements MUST be used to achieve certification.
This document also defines other operational aspects of the prpl Certification Program, such as certification of similar products, maintenance of the program test plans, documentation, and how the certification may be used by companies with certified products.

This document provides a common understanding of flash memory layout design and optimization strategies for prpl’s use cases.

The document will describe what a secure boot process is, and which prerequisites need to be considered. It further explains the major principles, how they could be applied to all prpl-compliant products, and to align on the implementation efforts of a prpl compliant bootloader. This documentwill explain how, by starting with a typically hardware SoC-based Root of Trust, a Chain of Trust can be provided (even with an Open-Source bootloader) by leveraging chipset hardware. The resulting boot process launches execution of authenticated and authorized Firmware.

This document standardizes the formats and methods of securing certificates, encryption keys and other sensitive data embedded in CPE devices at the time of manufacture.

This document identifies low-level APIs recommended by prpl to promote harmonization and convergence among SW platforms. The recommended APIs should be supported by BSPs in order to best leverage the efforts from open-source software communities.

The CPE WAN Management Protocol (CWMP/TR-069) offered a standard mechanism for service providers to manage their devices remotely, ranging from basic device identification, firmware management or configuration of individual services, but mostly focused on provisioning and activation.

Customer demand for ever more features has led carriers, manufacturers and retail brands to apply more and more software customization to gateways, access points, and routers.

Unfortunately, keeping all this software customization in sync across different devices and models quickly turns into a technical nightmare. The main reason is the large fragmentation of embedded operating systems and middleware stacks across the different manufacturers and suppliers.

To overcome this, the prpl membership, a diverse group of industry players ranging from carriers to middleware vendors, from manufacturers to test laboratories, has come together to address this issue and finally standardize intra-device communication with a common API and data model.