System Architecture
The Kunpeng BoostKit for
This document does not describe a specific component. Instead, it introduces the TrustZone Kit as a solution. By describing involved components, this document aims to help industry developers learn about the software and hardware entities so that they can quickly deploy and use their own development environment.

With this kit, Huawei aims to provide a secure platform for developers to deploy their own applications, including client applications (CAs) and trusted applications (TAs). The involved parties include Huawei and the customers. Table 1 describes the components and functions involved in the kit from the perspectives of Huawei and customers respectively.
Category |
Subcategory |
Description |
|---|---|---|
Industrial customers |
Service applications |
According to the TrustZone software development model, a specific service application is divided into a TA and a CA.
|
Linux OS |
Linux OS selected and deployed by you. The TEE is not coupled with the guest OS. However, the communication between the CA and TA depends on the communication framework in the REE. Huawei provides the communication framework as an REE patch. To ensure compatibility with the OS, Huawei has open-sourced the REE patch in the openEuler community. You can compile the REE patch on the selected OS on demand. |
|
Huawei deliverables |
Secure OS |
Huawei-developed TEE OS, which provides an application execution environment in the TEE. It adapts to the multi-CPU and multi-core Kunpeng platform and Kunpeng hardware. Generally, a Kunpeng server that supports the TrustZone function is equipped with the |
Hardware firmware |
To support the TrustZone feature, the hardware firmware is adapted as follows:
|
|
REE patch |
To enable your service CA to communicate with the TA deployed in the TEE, a patch needs to be deployed in the guest OS. The patch includes the user-mode API library, daemon process, and kernel driver. To meet the requirements for different OSs, Huawei has open-sourced the patch. |
|
SDK |
API description, application packaging tools, header files, and demo code are included. Currently, the SDK has been open-sourced. |