Metadata-Based Automation Architecture for Cloud Collaboration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current automation architectures for cloud-based collaboration platforms are not scalable and lack customization options for jobs triggered by user actions, making them inefficient in distributed computing environments.

Innovation Solution

A configurable event-based automation architecture that integrates a metadata service with an event-based automation engine, allowing users to specify rules for automating jobs based on metadata events, enabling customizable and scalable job execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current automation architectures are used to trigger jobs at the front-end, then jobs can be executed in response to user actions, but the system is not scalable and lacks customization options in distributed computing environments

Engineering Contradiction:
Improvecustomization options for jobsVSAvoidautomation architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the automation architecture into distinct components: event sources that generate events, a rule engine that processes events against defined rules, and job execution services that perform actions. This segmentation allows each component to be independently configured and scaled, providing customization options without increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The automation architecture implements dynamic rule definitions that allow users to create, modify, and delete automation rules without system reconfiguration. Rules can be dynamically added to match different event types and trigger appropriate jobs, enabling the system to adapt to changing requirements while maintaining a consistent architectural framework.

Inventive Principle:
Principle #15Dynamics

2Productivity

If front-end automation architecture is used, then jobs can be triggered by user actions, but the architecture lacks scalability in distributed computing environments

Engineering Contradiction:
Improvejob execution efficiencyVSAvoidscalability in distributed environments
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system introduces an event-driven intermediary layer that decouples event sources from job execution services. Events are published to a centralized event processing mechanism that routes them to appropriate rule engines and execution services, enabling scalable distribution across multiple servers while maintaining reliable job execution through standardized event handling protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If current automation architectures are used, then basic job triggering is possible, but the system lacks configurability for metadata-based automation

Engineering Contradiction:
Improvemetadata-based automation configurabilityVSAvoidautomation configuration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system implements self-service automation configuration where users can define their own automation rules based on metadata events without requiring system administrator intervention or complex coding. The rule engine provides a user-friendly interface for configuring event sources, defining metadata conditions, and specifying job execution parameters, making metadata-based automation accessible to end users.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11876845B2Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms
Publication Date: 2024.01.16 BOX INC
  • US11876845B2 patent drawing
  • US11876845B2 patent drawing
  • US11876845B2 patent drawing

AI summary

Scalable architectures, systems, and services are provided herein for generating jobs by applying user-specified metadata rules to metadata events. More specifically, the scalable architecture described herein uses metadata to drive automations and/or polices in a cloud-based environment. In one embodiment, the architecture integrates a metadata service with an event-based automation engine to automatically trigger polices and/or automations based on metadata and/or changes in metadata changes. The metadata service can include customizable and/or pre-build metadata templates which can be used to automatically apply a metadata framework (e.g., particular fields) to files based on, for example, the upload or placement of a particular file in a particular folder. The architecture also provides for advanced metadata searching and data classification.