Schema Object Content Ingestion System

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional systems for developing and processing various data types are inefficient, requiring frequent redesigns, code changes, and integration testing for each content type, leading to developer frustration and significant time spent on workflow development.

Innovation Solution

A content ingestion system that uses schema objects to define user interface, API, and workflow behaviors, deploying parsers on processing engines to interpret and implement these behaviors, enabling scalable and centralized management of data types without requiring individual engine modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional systems are used to process each content type, then processing capability is provided, but frequent redesigns, code changes, and integration testing are required for each discrete content type

Engineering Contradiction:

Improvecapability to process different content typesVSAvoidfrequency of redesigns, code changes, and integration testing

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal schema system that can process multiple content types through a single unified framework. The schema system defines behavior data that can be applied across different processing engines (UI engine, API engine, workflow engine) without requiring separate processing logic for each content type. This allows the system to handle diverse content types while maintaining consistent processing patterns and reducing the need for frequent redesigns.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the processing system into distinct processing engines (UI engine, API engine, workflow engine), each responsible for specific aspects of content processing. By dividing the system into modular components that can independently process different aspects of content types, the system achieves versatility without requiring comprehensive redesigns. Each engine can be updated or modified independently based on specific content type requirements.

Inventive Principle:

Principle #1Segmentation

2Productivity

If conventional development tools are used, then processing applications can be developed, but significant time is spent developing workflows for processing different types of data

Engineering Contradiction:

Improvespeed of workflow developmentVSAvoidtime spent on workflow development and integration testing

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining schema objects that contain behavior data for different content types. These schema objects are created in advance and stored in a centralized schema system, allowing processing engines to retrieve and apply appropriate processing logic without developing workflows from scratch. This preliminary preparation significantly reduces development time when new content types need to be processed.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by allowing the schema system to replicate and distribute behavior data across multiple processing engines. Once a schema object is defined with appropriate behavior data, it can be copied and applied to different engines and content types, eliminating the need to recreate processing logic for each scenario. This copying mechanism accelerates workflow development while maintaining consistency across the system.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If discrete content types are added to conventional systems, then content type variety increases, but additional deployments and roll out are required for each content type

Engineering Contradiction:

Improvenumber of content types supportedVSAvoidease of system deployment and updates

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent merges the management of multiple content types into a single centralized schema system. Instead of managing each content type separately across different engines and deployment environments, the schema system consolidates all behavior definitions in one location. This merging allows content type variety to increase while simplifying deployment, as changes to schema objects automatically propagate to all relevant processing engines without requiring separate deployment processes for each content type.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11803523B2Ingesting and processing content types

Publication Date: 2023.10.31 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

The present disclosure generally relates to systems, methods, and computer-readable media for developing and implementing workflows for a variety of data types. For example, systems disclosed herein may receive or otherwise generate a schema object on a schema system including a plurality of schema objects associated with different workflows. The schema object may include user interface behavior data indicating a content type and associated control type. The schema object may further include application programming interface (API) behavior data indicating a binding between a user interface engine and an API engine. The schema object may also include workflow behavior data indicating one or more services for processing the schema object. Moreover, systems described herein may deploy a plurality of parsers on a plurality of processing engines to enable flexibility and dynamic updates to content ingestion lifecycles.