Embedded Designer Framework Memory Cache Sharing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current designer implementations face challenges in reducing memory usage and bandwidth consumption, as each designer renders its own set of components, leading to increased memory utilization and bandwidth usage when launched independently.

Innovation Solution

The embedded designer implementation framework allows designers to be embedded within each other and launched inline, sharing a common memory cache for configurable components, reducing memory usage and bandwidth consumption by minimizing remote memory access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each designer renders its own set of components independently, then each designer maintains independent graphical design functionality, but memory usage and bandwidth consumption increase

Engineering Contradiction:
Improveindependent graphical design functionalityVSAvoidmemory usage
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Multiple designers share a common memory cache for configurable components, merging the previously separate memory resources into a unified pool that serves all designers, thereby reducing total memory usage while maintaining independent design functionality

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The common memory cache serves multiple designers simultaneously, making it a universal resource that can be accessed by any designer that needs configurable components, eliminating the need for duplicate component storage across different designers

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

2Adaptability or versatility

If each designer renders its own set of components independently, then each designer maintains independent graphical design functionality, but bandwidth consumption increases due to remote memory access

Engineering Contradiction:
Improveindependent graphical design functionalityVSAvoidbandwidth consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

Multiple designers share a common memory cache for configurable components, merging the previously separate memory resources into a unified pool that serves all designers, thereby reducing total memory usage while maintaining independent design functionality

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The common memory cache acts as an intermediary between designers and the remote memory system, allowing designers to access configurable components locally without requiring repeated remote memory access, thereby reducing bandwidth consumption

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10691421B2Embedded designer framework and embedded designer implementation
Publication Date: 2020.06.23 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10691421B2 patent drawing
  • US10691421B2 patent drawing
  • US10691421B2 patent drawing

AI summary

In some examples, embedded designer implementation may include, upon receiving an indication of actuation of a second designer launch element that is included in a first designer, launching a second designer inline from the first designer. Further, embedded designer implementation may include, upon receiving an indication of actuation of a first designer return element that is included in the second designer, returning to the first designer inline from the second designer. The first designer and the second designer may include a configurable component. Further, embedded designer implementation may include utilizing a common portion of the memory for the configurable component.