Endpoint Plugin Rendering Streaming Media Virtual Desktop

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Virtualized desktop environments face challenges in efficiently rendering streaming media due to high network loads, inefficient use of content cache servers, and scalability issues when content is routed through a host device before being sent to client endpoint devices.

Innovation Solution

Directly transporting content data from content servers to client endpoint devices using a content transport session, allowing native encoding and reducing bandwidth consumption, while using a plugin protocol to instantiate endpoint plugins for rendering media on the client device, thereby avoiding transcoding and computational loads on host devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If content data is routed through host device before being sent to client endpoint devices, then centralized control and management is simplified, but network bandwidth consumption increases and scalability deteriorates

Engineering Contradiction:
Improvecentralized control complexityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Device complexityVSLoss of energy

Solution Approach 1:

The system segments the content delivery path by establishing direct content transport sessions from content servers to client endpoint devices, separating the content data flow from the virtual desktop protocol flow. This segmentation allows centralized control to be maintained for desktop management while enabling efficient direct content delivery that reduces network bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The host device acts as an intermediary that coordinates content delivery by establishing plugin protocol sessions between client endpoint devices and content servers, enabling direct content transport while maintaining centralized control. The host device mediates the process by managing plugin sessions without being the bottleneck for content data flow.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If content is routed through host device, then centralized management is easier, but scalability and cache server efficiency deteriorate

Engineering Contradiction:
Improvemanagement complexityVSAvoidscalability
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

By segmenting content delivery into direct transport sessions independent of the virtual desktop protocol, the system enables scalable content distribution where multiple client endpoint devices can receive content directly from content servers and cache servers without overwhelming the host device, thus improving scalability while maintaining manageable centralized control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The host device serves as a coordinating intermediary that manages plugin sessions and content transport establishment without being the bottleneck for content delivery. This intermediary role enables scalable system architecture where the host device maintains control while allowing efficient direct content flow between content servers and multiple client endpoint devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If media is rendered on host device and transmitted to client endpoint device, then integration is simpler, but network bandwidth consumption increases

Engineering Contradiction:
Improverendering integration complexityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Device complexityVSLoss of energy

Solution Approach 1:

The system extracts the media rendering function from the host device and relocates it to client endpoint devices through endpoint plugins. This extraction eliminates the need to transmit rendered media content over the network, as content is delivered directly in its native format to the client device where it is rendered locally, significantly reducing network bandwidth consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The plugin protocol session acts as an intermediary mechanism that enables direct content transport from content servers to client endpoint devices for local rendering. This intermediary protocol allows the system to maintain integration while avoiding the bandwidth consumption associated with transmitting rendered content, as the plugin coordinates direct content delivery for local playback.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of energy

If endpoint plugins are used for native rendering, then network bandwidth consumption is reduced, but device complexity at client endpoint increases

Engineering Contradiction:
Improvenetwork bandwidth consumptionVSAvoidclient endpoint complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The system employs universal plugin architecture where endpoint plugins provide multi-functional capabilities for rendering different media types (video, audio, Flash, etc.) on client endpoint devices. This universality allows a single plugin framework to handle diverse content types, reducing the need for multiple specialized components and thereby managing client endpoint complexity while enabling efficient local rendering that reduces network bandwidth consumption.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP2710463B1Integrated rendering of streaming media in virtualized desktop environment
Publication Date: 2018.06.06 CISCO TECHNOLOGY INC
  • EP2710463B1 patent drawingFigure 1
  • EP2710463B1 patent drawingFigure 2
  • EP2710463B1 patent drawingFigure 3A

AI summary

Techniques are provided for establishing an integrated rendering of a browser window comprising user interface elements such as streaming media on a client endpoint device. A web browser on a hosted virtual desktop (HVD) generates an HVD display image comprising a browser window and communicates it to the client endpoint device for display, via a virtual desktop interface (VDI) protocol. The browser window comprises a host-provided window element and a placeholder where client-provided data associated with a tag may be rendered. A plugin server element on the client endpoint device instantiates an endpoint browser plugin to render a tag in place of the placeholder portion of the HVD display, before displaying the integrated display of the browser window and rendered tag content at the client endpoint device.