Metadata Transfer Between Independent Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software applications on user devices are limited in their ability to communicate and share metadata with other applications in response to external trigger events, restricting their functionality and interaction capabilities.

Innovation Solution

A method and device that detect non-specific trigger events on user devices, allowing metadata transfer between independent software applications to invoke actions in separate applications, enabling seamless interaction and collaboration between applications without being part of the operating system processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications are kept separate and independent (not operating system processes), then application independence and modularity are improved, but application-to-application communication and metadata sharing capabilities deteriorate

Engineering Contradiction:
Improveapplication independenceVSAvoidmetadata sharing capability
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary mechanism that enables metadata transfer between independent applications without requiring them to be integrated or share processes. This intermediary allows Application A to send metadata to Application B while both remain separate and independent, resolving the contradiction between application independence and metadata sharing capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If applications use traditional command inputs within their own interfaces, then application simplicity and ease of operation are improved, but application interaction and collaboration capabilities deteriorate

Engineering Contradiction:
Improveapplication simplicityVSAvoidapplication interaction capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal metadata transfer mechanism that enables applications to perform multiple functions including receiving commands, sharing data, and triggering actions across application boundaries. This allows applications to maintain simple interfaces while gaining enhanced interaction capabilities through the shared metadata infrastructure.

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

3Reliability

If applications are integrated as operating system processes, then system-level control and coordination are improved, but application independence and flexibility deteriorate

Engineering Contradiction:
Improvesystem coordinationVSAvoidapplication independence
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the system into independent application processes that communicate through standardized metadata transfer mechanisms. This segmentation allows each application to maintain independence and flexibility while the standardized interface ensures reliable system-level coordination, resolving the contradiction between integration benefits and independence requirements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8978047B2Method and system for invoking an application in response to a trigger event
Publication Date: 2015.03.10 SONY GROUP CORP
  • US8978047B2 patent drawing
  • US8978047B2 patent drawing
  • US8978047B2 patent drawing

AI summary

A method for invoking a software application comprising: executing a first application on a user device; detecting a trigger event on the user device, the trigger event is non-specific and external to the first application and a second application; invoking the second application in response to the trigger event; sending metadata from the first application to the second application; and performing an action in the second application based at least partially on the metadata received from the first application, wherein, the first application and the second application are not operating system processes, and the second application is separate and independent from the first application.