Got it

HCIP-Cloud Computing | HDP Overview

88 0 0 0 0

Hello, everyone!

In this post, I want to share the various desktop protocols used. Each one has its own advantages and disadvantages. Different vendors use different desktop protocols. 

Huawei Desktop Protocol Introduction

Huawei Desktop Protocol(HDP) is a new-generation desktop protocol developed by Huawei. Compared with traditional desktop protocols, HDP has the following features:

  • supports a maximum of 64 virtual channels. Different virtual channels carry different upper-layer application protocols.

  • uses different compression algorithms and flexibly uses server rendering or local rendering for different types of applications.

  • supports smoother and clearer video playback.

  • supports lossless compression algorithms.

  • restores audio details.

  • provides various protocol management policies.

Virtual channels ensure communication security and good user experience based on Quality of Service (QoS) priorities (for example, the keyboard and mouse virtual channel can be given the top priority). 

HDP uses chip hardware interfaces to accelerate video decoding and supports playback of 4K video.

HDP adopts lossless compression algorithms for non-natural images and supports no transmission of repeated image data. When HDP is used to display non-natural images, such as texts, icons, and OA desktops, the peak signal to noise ratio (PSNR) of HDP reaches over 50000 dB, and structural similarity (SSIM) reaches 0.999955, providing close-to-lossless video display quality. 

HDP automatically detects voice scenarios, implements denoising when detecting noises, supports transparent voice transmission on TCs, provides more clear sound in real time, and accurately restores sound. Perceptual evaluation of speech quality (PESQ) is over 3.4. 

HDP provides rich protocol management policies. It delivers independent channel policies for different users or user groups to ensure communication security for each user.

Overall Architecture of HDP

Overall Architecture of HDP

Desktop Protocols Introduction

 1. ICA and HDX Introduction

Citrix Independent Computing Architecture (ICA) is one of the most popular virtual desktopvprotocols. In addition to comprehensive functionality, ICA has the following features:

  • ICA supports a wide range of mobile terminals.

  • ICA is independent of network protocols, meaning it can support TCP/IP, NetBIOS, and IPX/SPX.

  • ICA not only supports the Citrix-developed virtualization platform XenServer, but also supports the vSphere and Hyper-V virtualization platforms.

  • ICA features low bandwidth consumption, so it can be used in networks of poor quality (such as networks with high latency).

High Definition Experience (HDX) is an enhanced edition of ICA. HDX improves user experience of video, audio, multimedia, and 3D services. HDX supports H.264.

Let's take a look at the five most commonly used desktop protocols, starting with ICA.

Virtualization technology is the core of Citrix Delivery Center. ICA is critical to virtualization computing. ICA connects the operating environment of application clients running on the platform and remote terminals. ICA redirects the input and output data of the application operating environment that runs on a central server to the input and output devices of the remote terminals through 32 virtual channels (respectively transmitting mouse, keyboard, image, sound, port, print, and other input/output data). From a user's perspective, there is no difference between working with local clients loaded with software and remote terminals receiving data from application clients running on the platform.

2. PCoIP Introduction

PC over IP(PCoIP) was developed by Teradici for high-end graphics design. In 2008, VMware joined Teradici in developing PCoIP to develop its own virtual desktop infrastructure (VDI) solution VMware View.

  • PCoIP works closely with hardware. PCoIP allows data encoding and decoding and graphics processing to be implemented by professional hardware, and therefore CPU resources can be used in other places. Monitors equipped with PCoIP display chips are provided.

  • PCoIP is developed based on User Datagram Protocol (UDP). UDP cannot ensure reliable transmission, but unlike TCP, it does not require three-way handshakes for complex verification and data restoration. Therefore, UDP supports a high transmission rate and applies to multimedia transmission.

  • However, the native PCoIP does not support redirection of peripherals, such as serial ports and parallel ports. Some TC vendors use extra port redirection plug-ins to make up for this disadvantage.

PCoIP compresses and transmits user sessions as images. It transmits only changed parts of user operations, ensuring efficient use at low bandwidth. In addition, PCoIP supports multiple monitors with a resolution of up to 2560 x 1600 or a maximum of four 32-bit color monitors. In addition, the PCoIP supports ClearType fonts.

Unlike TCP-based RDP, ICA, and HDX, PCoIP is based on UDP. What are the disadvantages of TCP? TCP requires three handshakes. As a result, the verification field of a TCP packet is longer than that of a UDP packet. For this reason, TCP may be unsuitable for a WAN environment with a relatively high network delay and packet loss rate. 

PCoIP compresses and transmits user sessions as images. It transmits only changed parts of user operations, ensuring efficient use at low bandwidth. PCoIP is more adaptive in a WAN environment. It can fully utilize network bandwidth rather than merely preempting bandwidth.

PCoIP is a typical server-side rendering protocol with broad compatibility. Image quality displayed using PCoIP varies with line speeds. If the line speed is low, PCoIP transmits a lossless image to a client. As the line speed increases, PCoIP gradually displays high-definition images. PCoIP can work with the VMware software solution. It also supports hardware encoding and decoding on blade PCs and rack workstations equipped with Teradici host cards.

3. SPICE Introduction

Simple Protocol for Independent Computing Environments (SPICE) is a virtual desktop protocol developed by Qumranet. It was subsequently purchased by Red Hat who now provides it as an open protocol. Having undergone years of community development, SPICE can be considered a mature protocol

SPICE is a particularly good option for video services because it allows display information to be compressed by KVM. This prevents guest OSs from consuming too many CPU resources. SPICE uses lossless compression technology to provide HD experience for users. However, SPICE consumes a lot of bandwidth.

SPICE, provided by Red Hat, is a high-performance, dynamic, and adaptive telepresence technology. It delivers an end-user experience comparable to that of a physical desktop. SPICE is a dedicated protocol for remote access to virtual desktops. It is used to connect users to virtual desktops running on Red Hat's Enterprise Virtualization for Desktops.

In contrast to Microsoft RDP and Citrix ICA, SPICE uses a multi-layer architecture and aims to meet the rich multimedia requirements of desktop users. SPICE implements intelligent access to the available system resources on client devices (CPUs, RAMs, etc.) or virtual host servers. Based on the access result, SPICE dynamically determines whether to present desktop application programs on a client device or the host server, so that the best user experience can be provided in any network condition.

SPICE provides a superior customer experience and is favored by many virtualization vendors.

4. RDP and RemoteFX Introduction

Remote Desktop Protocol (RDP) is a Microsoft protocol, originally based on the MultiWin technology developed by Citrix. RDP provides relatively few functions and applies to Windows environments. Rdesktop is available for Mac RDP clients and Linux RDP clients. The latest RDP version supports printer redirection, audio redirection, and clipboard sharing.

RemoteFX, an enhanced edition of RDP, supports vGPUs, multi-touch, media redirection, and USB redirection.

With RDP, Terminal Services allow users to log in to a server using an authorized account from an authorized terminal to use software and hardware resources allocated to this account. After RDP is upgraded, a client can use local resources, including printers, audio playback resources, disk resources, and hardware interfaces. All computing work is performed on the server side. Clients only need to process network connections, receive data, display screens, and output device data.

Comparison between common desktop protocols, see What are the protocols on the cloud desktop?

That's all, thanks!

The post is synchronized to: HCIP - Cloud Computing

  • x
  • convention:


You need to log in to comment to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits


Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Please bind your phone number to obtain invitation bonus.
Information Protection Guide
Thanks for using Huawei Enterprise Support Community! We will help you learn how we collect, use, store and share your personal information and the rights you have in accordance with Privacy Policy and User Agreement.