Overview

A cloud phone is a cloud server with a native Android operating system and functions as a virtual phone. It extends the functions of a physical phone and can be used in various scenarios such as cloud games and mobile office.

The device-cloud engine consists of the device side and the cloud side. The cloud side runs on a server; the device side is generally a cloud phone APK, which can be installed on your Android mobile phone to interact with the cloud side and operate the Kbox container.

This document describes the integrated development of the device and cloud engines used in the video stream cloud phone.

For details, see Table 1.

**Table 1** Service description
Service Name	Concept
Video stream engine	A binary library based on video stream cloud phones. It consists of the server and the client, integrates the image capture, H.264/H.265 encoding and decoding, and image display functions of a cloud phone, and provides simple external APIs. Developers do not need to focus on the underlying technical implementation details. The server is responsible for obtaining cloud phone images and H.264/H.265 encoding, and the client is responsible for H.264/H.265 decoding and display. The video stream engine supports only the Android platform. The demos provide a series of code samples to demonstrate how to call interface functions to help developers quickly understand service development.
Base engines	The base engines include an audio engine and a touch engine. The audio engine consists of the server and the client. It enables a client-side physical mobile phone to play the audio data generated on a server-side cloud phone. The server installation package is an .so file that integrates the function of redirecting audio data on the server. The client installation package is an .aar file that integrates the function of playing the server-side redirected audio data. Simple external APIs are provided, and developers do not need to focus on the underlying technical details. Currently, the audio engine supports only the Android platform. The development process and encoding instances are provided. The demos provide a series of code samples to demonstrate how to call interface functions to help developers quickly understand service development. The touch engine consists of the server and the client. It enables a server-side cloud phone to identify touch operations on a client-side physical mobile phone. The server installation package is an .so file that integrates the function of injecting touch data generated on the client into a server-side cloud phone. The client installation package is an .aar file that integrates the function of intercepting touch data on the client. Simple external APIs are provided, and developers do not need to focus on the underlying technical details. Currently, the touch engine supports only the Android platform. The development process and encoding instances are provided. The demos provide a series of code samples to demonstrate how to call interface functions to help developers quickly understand service development.

Parent topic: Developer Guide