laitimes

Version 3.0 of the OpenHarmony Product Compatibility Specification Document was officially released

IT House reported on January 14 that the OpenHarmony open source project is an open source project incubated and operated by the Open Atomic Open Source Foundation, and is operated by the OpenHarmony Project Group Working Committee of the Open Atomic Open Source Foundation. OpenHarmony is an open source distributed operating system donated by Huawei to the basic capabilities of the intelligent terminal operating system, which is built by global developers, with the characteristics of all scenarios and distribution, and is an operating system that is "full (all-domain) new (new generation) open (open source) release (open)".

Version 3.0 of the OpenHarmony Product Compatibility Specification Document was officially released

The Product Compatibility Specifications ("PCS") define what is necessary to be compatible with the OpenHarmony system: that is, a product that meets the requirements defined in the Product Compatibility Specification document may be considered compatible with the OpenHarmony system.

Recently, the Compatibility Working Group officially released version 3.0 of the OpenHarmony Product Compatibility Specification Document in the community, and partners can complete the compatibility certification of the OpenHarmony 3.0 LTS version of the product by using the compatibility specification document and the XTS suite.

Visit Gitee to consult the documentation

https://gitee.com/openharmony-sig/compatibility/tree/master/docs

Documentation download link

https://downloads.openharmony.cn/files/OpenHarmony3.0-PCS.pdf

IT House learned that PCS defines the design of ecological devices from the aspects of API compatibility and distributed interface compatibility to ensure the compatibility of OpenHarmony applications on all ecological devices and distributed interoperability. In addition, the product compatibility specification document defines the design of ecological devices from the basic specifications of software and hardware to ensure that users have a consistent experience when using OpenHarmony ecological devices in the same scenarios.

Version 3.0 of the OpenHarmony Product Compatibility Specification Document was officially released

The PCS 3.0 release mainly enriches the following contents:

1. Improved the definition of openHarmony mini system and the description of compatibility specifications

Mini system:

For MCU-like processor-like devices, hardware resources are extremely limited, supporting a minimum memory of 128KiB, providing a variety of lightweight network protocols, lightweight graphics frameworks, and rich IOT bus read and write components. Supporting products such as connection modules, sensor devices, wearable devices, etc. in the field of smart homes.

2. Improved the definition of OpenHarmony small system and the description of compatibility specifications

Small system:

For devices with MMU-enabled application processors, supporting a minimum memory of 4 MiB, providing higher security capabilities, standard graphics frameworks, and multimedia capabilities for video codec. Supportable products such as IP Cameras, electronic cat eyes, routers and dashcams in the smart home field.

3. Improved the definition of the OpenHarmony standard system and the description of the compatibility specification

Standard system:

Devices for application processors that support a minimum memory of 128 MiB can provide enhanced interaction capabilities, GPU and hardware compositing capabilities, more controls and more dynamic graphics capabilities, and a complete application framework. Supportable products such as IOT devices with screens, light smartphones, etc.

4. Improved the definition of optional system capabilities and compatibility specifications

Selectable system capabilities:

OpenHarmony offers a range of optional system components that device developers can configure on demand to support the expansion or custom development of their featured features. The system combines these optional system components into a series of system capabilities described as features or functions for easy understanding and selection by device developers. Supplemented on PCS 3.0.

Read on