Blender Service Standardizes Data Formats for Notification Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional content management systems face bottlenecks in handling multiple data sources and notification services due to the need for manual customization of data schemas and formats, leading to increased complexity and resource requirements.

Innovation Solution

A unified event format and blender system are introduced to standardize data intake from various sources, converting data into a compatible format for notification generation, reducing the need for manual customization and enabling efficient processing across different data formats and services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual customization of data schemas and formats is implemented for each data source, then the system can handle specific data formats accurately, but the device complexity and customization overhead increase significantly

Engineering Contradiction:
Improvedata format accuracyVSAvoidcustomization overhead
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent introduces a standardized event format as an intermediary layer between diverse data sources and the notification system. This mediator translates various data source formats into a unified event structure, eliminating the need for manual customization of each data source while maintaining accurate data representation. The standardized event format acts as the intermediary that resolves format diversity without requiring system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a universal standardized event format that can accommodate multiple data sources with different formats. This single event format serves multiple purposes by accepting data from various sources (news feeds, social media, APIs) and converting them into a common representation. This multi-functionality eliminates the need for separate customization logic for each data source, reducing overall system complexity.

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

2Adaptability or versatility

If multiple notification services with different request formats are supported, then the system can serve diverse notification needs, but the device complexity and resource requirements increase

Engineering Contradiction:
Improvenotification service compatibilityVSAvoidresource requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The standardized event format serves as an intermediary that decouples notification services from data sources. Each notification service can subscribe to this unified event format and transform it into their specific request format as needed. This mediator approach allows multiple notification services to coexist without requiring the system to maintain separate handling logic for each service, reducing resource requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the notification system into independent components: a standardized event format layer and separate notification service layers. Each service can independently transform the standardized events into their required formats. This segmentation allows services to be added or modified without affecting the core event processing logic, reducing overall system complexity and resource requirements.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If customized logic is manually updated for each new data source, then the system can accommodate new data formats, but the productivity and implementation speed decrease

Engineering Contradiction:
Improvedata source integration capabilityVSAvoidimplementation speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The standardized event format acts as a pre-defined intermediary that specifies exactly how data should be structured before processing. When a new data source is added, the system only needs to map the source's format to the standardized event format using the provided schema, rather than manually creating and maintaining customized logic. This intermediary approach dramatically speeds up integration while maintaining adaptability to new data sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses parameter changes in the form of configurable mapping parameters between data source formats and the standardized event format. Instead of manually programming customized logic for each data source, the system allows configuration of format parameters (field names, data types, formats) to automatically transform data. This parameter-based approach enables rapid adaptation to new data sources without manual logic updates, improving implementation speed.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10831569B1Trigger based notification generation system
Publication Date: 2020.11.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10831569B1 patent drawing
  • US10831569B1 patent drawing
  • US10831569B1 patent drawing

AI summary

Technologies for generating notification messages from data provided from different data sources in different data formats are provided. The disclosed techniques include a blender service that receives, from a first source, first data that is in a first data format and generates, based on the first data, a first event that includes content from the first data. The blender service also receives, from a second data source, second data that is in a second data format and generates a second event that includes content from the second data. An event processing system receives the first and second events and causes notifications to be generated based on the first event and the second event. A notification system generates the notification messages and sends the notification messages to the recipient users.