Cross-Application Contextual Message Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current techniques for displaying contextual messages within applications are slow, inefficient, and costly, as each application must implement a rich canvas for message display, manage content retrieval, storage, and rendering, and require software updates for new messages, leading to increased processor load and memory usage.

Innovation Solution

A cross-application service-driven system where a dynamic background application retrieves and stores rules and messages from a server, detecting actions within client applications to dynamically display relevant messages without requiring each application to manage content or update software, allowing for real-time, efficient, and cost-effective message display across multiple applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If each application implements a rich canvas for displaying contextual messages and manages content retrieval, storage, and rendering, then contextual messages can be displayed within each application, but the device complexity and software update requirements increase

Engineering Contradiction:
Improvecontextual message display capabilityVSAvoidapplication structure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the contextual message management functionality from individual applications and places it in a separate dynamic background application. This background application independently handles content retrieval from servers, storage, and rendering, while client applications only need to provide basic display capabilities. This extraction resolves the contradiction by maintaining message display functionality while significantly reducing the complexity burden on each individual application.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The dynamic background application serves as an intermediary layer between the server and client applications. It manages the complex tasks of content retrieval, storage, and rendering, then provides simplified message display services to client applications. This intermediary approach allows client applications to display contextual messages without implementing full content management systems, thus reducing their complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If software updates are required for each application to display new contextual messages, then message content can be updated, but the time and cost efficiency decrease

Engineering Contradiction:
Improvemessage content update capabilityVSAvoidsoftware update time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The dynamic background application performs preliminary actions by pre-fetching and storing contextual message content from servers before it is needed. When client applications need to display messages, the content is already available in the background application's storage, eliminating the need for real-time updates or downloads. This preliminary action enables rapid message content updates without requiring software updates to client applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates and maintains copies of contextual message content in the dynamic background application's storage. Instead of requiring client applications to directly access or update content from servers, the background application maintains local copies that can be quickly retrieved and displayed. This copying mechanism enables fast message updates independent of client application software versions.

Inventive Principle:
Principle #26Copying

3Ease of operation

If each application manages content retrieval, storage, and rendering independently, then contextual messages can be displayed, but the processor load and memory usage increase

Engineering Contradiction:
Improvecontextual message display functionalityVSAvoidprocessor load and memory usage
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent merges the content retrieval, storage, and rendering functions from multiple client applications into a single dynamic background application. Instead of each application independently managing these resource-intensive tasks, they are consolidated into one shared service. This merging eliminates redundant operations and significantly reduces overall processor load and memory usage while maintaining the ability to display contextual messages across all client applications.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10447828B2Cross-application service-driven contextual messages
Publication Date: 2019.10.15 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10447828B2 patent drawing
  • US10447828B2 patent drawing
  • US10447828B2 patent drawing

AI summary

Aspects of the present disclosure relate to cross-application service-driven dynamic contextual messages. In one aspect, content is retrieved from a server computing device. The content may include at least one rule and at least one contextual message. The content retrieved from the server computing device may be stored. A dynamic background application may detect an action associated with a client application. In response to detecting the action associated with the client application, a contextual message may be identified from the at least one contextual message based on a rule from the at least one rule. The dynamic background application may display the identified contextual message within the client application.