Event Metadata Structuring for Contextual Sharing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing email and calendaring systems face difficulties in sharing event metadata effectively between users, as the relevance of metadata can vary for new recipients, leading to inefficiencies in automatic parsing and provisioning.

Innovation Solution

The system parses incoming emails to identify event metadata, allows users to select and integrate relevant metadata for new recipients, and provides options for automatic calendar event creation upon receipt, ensuring metadata is contextually relevant and efficiently shared.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If event metadata is automatically parsed and shared with new recipients, then the ease of operation is improved, but the loss of information increases due to irrelevant metadata being included

Engineering Contradiction:

Improveease of sharing eventsVSAvoidrelevance of metadata

Core Design Contradiction:

Ease of operationVSLoss of information

Solution Approach 1:

The system applies local quality by customizing metadata inclusion based on recipient-specific contexts. Different recipients receive different subsets of event metadata tailored to their roles and relationships with the event, rather than a uniform set of all metadata. This ensures each recipient gets precisely the information relevant to them.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The event metadata is segmented into multiple categories and subsets. The system divides the complete event information into different metadata groups that can be selectively included or excluded based on recipient characteristics, allowing precise control over what information is shared with each recipient.

Inventive Principle:

Principle #1Segmentation

2Reliability

If all event metadata is transmitted to new recipients, then the reliability of information is improved, but the bandwidth usage increases

Engineering Contradiction:

Improvefidelity of event informationVSAvoidbandwidth usage

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system extracts only the necessary subset of event metadata required for each specific recipient rather than transmitting the complete event information. By identifying and removing irrelevant metadata fields based on recipient context, the system maintains information reliability for what is transmitted while significantly reducing overall bandwidth consumption.

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If event metadata is customized for each recipient, then the adaptability is improved, but the device complexity increases

Engineering Contradiction:

Improvecontextual relevance of metadataVSAvoidcomplexity of metadata integration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-defining metadata templates and recipient role profiles before actual event sharing occurs. Common metadata structures, recipient types, and relevance rules are established in advance, which simplifies the runtime complexity of customizing metadata for each recipient while maintaining high adaptability.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11783299B2Sharing events with structured metadata

Publication Date: 2023.10.10 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

When sharing events between users, the sharing users and the recipient users often have different relationships with details of the events. An event structurer enables sharing users to share events via a single user interface with recipients and tailor what aspects of the events are shared, thus ensuring the relevant portions of the events are properly presented to new recipients based on their new relationship with the event's details.