Global Composition System Single Engine Rendering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional computing devices face inefficiencies in rendering multiple applications due to redundant processing and resource consumption, particularly in 'thin' devices with limited resources, as each application has its own composition engine unaware of others' contributions, leading to unnecessary rendering and resource wastage.

Innovation Solution

A global composition system that uses a single composition engine accessible via APIs by multiple applications, managing rendering through a global composition tree for efficient occlusion detection and mixed content rendering, while prioritizing resource usage and ensuring security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If each application has its own composition engine, then application independence and execution flexibility are improved, but resource consumption and rendering redundancy increase

Engineering Contradiction:
Improveapplication independenceVSAvoidresource consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple composition engines into a single shared composition engine that serves all applications. This single engine maintains awareness of all application elements and their spatial relationships, enabling it to perform global occlusion detection and eliminate redundant rendering operations while preserving application independence through standardized API interfaces.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The composition engine is designed as a universal multi-functional component that can handle rendering tasks for multiple different applications simultaneously. It provides a standardized interface that works across diverse applications while implementing global optimization algorithms that benefit from knowledge of all application states.

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

2Adaptability or versatility

If each application has its own composition engine, then application-specific rendering control is improved, but rendering efficiency and resource utilization deteriorate

Engineering Contradiction:
Improverendering controlVSAvoidrendering efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

Multiple composition engines are merged into a single engine that maintains comprehensive awareness of all application elements. This enables global optimization through occlusion detection and intelligent rendering scheduling, significantly improving rendering efficiency while preserving application-specific control through standardized interfaces.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The single composition engine implements feedback mechanisms by continuously monitoring the states of all application elements and using this information to make intelligent rendering decisions. It detects occlusions and adjusts rendering operations based on real-time knowledge of the entire display composition, improving overall efficiency.

Inventive Principle:
Principle #23Feedback

3Use of energy by moving object

If a single composition engine is used, then resource efficiency and rendering optimization are improved, but system complexity and security management worsen

Engineering Contradiction:
Improveresource efficiencyVSAvoidsystem complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The system is segmented into distinct functional layers: application modules that generate rendering requests, a standardized API interface layer, and the single composition engine that performs global optimization. This segmentation manages complexity by clearly defining boundaries and responsibilities while enabling resource efficiency through centralized control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A standardized API interface acts as an intermediary between applications and the composition engine. This mediator layer simplifies system complexity by providing a uniform interface that abstracts the underlying complexity of global composition management, while enabling secure and efficient communication between applications and the single engine.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of energy

If a single composition engine is used, then redundant rendering is reduced and resource consumption decreases, but the ability to handle diverse application requirements deteriorates

Engineering Contradiction:
Improveresource consumptionVSAvoidapplication support
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The single composition engine is designed as a universal platform capable of handling diverse application requirements through standardized interfaces. It maintains adaptability by supporting multiple application types and rendering scenarios while implementing global optimization algorithms that reduce resource consumption across all applications.

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

Solution Approach 2:

The composition engine adapts to diverse application requirements by dynamically adjusting rendering parameters and optimization strategies based on the specific characteristics of each application and its current state. This enables resource-efficient rendering across varied application scenarios without sacrificing versatility.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2715529B1Global composition system
Publication Date: 2020.02.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2715529B1 patent drawingFigure 1
  • EP2715529B1 patent drawingFigure 2
  • EP2715529B1 patent drawingFigure 3

AI summary

A global composition system is described. In one or more implementations, the global composition system may be configured to perform rendering for a plurality of applications. For example, the global composition system may be configured to expose one or more application programming interfaces (APIs) that are accessible to the applications. The APIs may then be used to cause a single composition engine to perform the rendering for the plurality of applications. The use of a single composition engine may be used to support a variety of different functionality, such as to perform efficient rendering by knowing what elements are provided by each of the applications and how those items relate for rendering to a display device.