Android container application display method based on cross-system zero-copy rendering link

By building a cross-system zero-copy rendering link in the HarmonyOS system, the performance bottleneck of Android application rendering result transmission in OpenHarmony is solved, achieving efficient and stable cross-system display and improving compatibility and frame rate.

CN122064512AActive Publication Date: 2026-05-19北京麟卓信息科技有限公司
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202610516500.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-04-20
Publication Date
2026-05-19
Estimated Expiration
2046-04-20

AI Technical Summary

Technical Problem

When running Android applications as containers in OpenHarmony, there are performance bottlenecks in the cross-system transfer of rendering results, including poor compatibility, multiple data copying times, large synchronization delays, difficulty in resolution adaptation, and unstable communication, which lead to frame rate fluctuations and screen tearing.

Method used

By adopting a cross-system zero-copy rendering link approach, a two-way encrypted communication channel is established by starting a memory coordination service and a memory proxy daemon process in the HarmonyOS system, and a cross-system unified memory pool and hardware-level synchronization mechanism are built to achieve high-performance display of Android applications on the HarmonyOS host side.

Benefits of technology

It enables efficient and stable cross-system rendering result transfer without EGL Image support, reduces latency and frame rate fluctuations, improves compatibility and display stability, and reduces the number of data copies and synchronization delays.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122064512A_ABST
    Figure CN122064512A_ABST
Patent Text Reader

Abstract

The invention discloses an Android container application display method based on a cross-system zero-copy rendering link, and the method comprises the steps: taking a gap as a host and an Android as a container, building encrypted communication between the two parties through a memory coordination service and an agent daemon process, completing capability negotiation, and generating a cross-system capability matrix; creating a secure shared buffer area pool by the host according to the secure shared buffer area pool, and distributing a unique identifier and a DRM Prime handle for the buffer area; a container side application initiates a buffer area rendering request, a host matches and distributes a buffer area, and a handle is imported into the container side to bind a rendering context; after the application finishes rendering, synchronizing an object mark completion state through the DRM and notifying the host; and the host verifies the data and waits for a synchronization signal, and submits a buffer area handle to a display controller in a zero copy mode at the VSync opportunity to complete on-screen operation.
Need to check novelty before this filing date? Find Prior Art