Distributed File Collection via Dynamic Conductor Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current online content systems face challenges with high latency and downtime due to static system configurations, making it difficult to adapt to changes in data types and consumer needs in distributed networks.

Innovation Solution

A computer-implemented system and method for distributed file collection and processing, comprising a producer system, a collector system, a conductor system, and a consumer system, which dynamically manage file detection, allocation, and distribution based on configuration files and requests, allowing for elastic expansion and contraction with minimal downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static system configuration is used to manage data collection and distribution, then system stability is maintained, but adaptability to new data types and consumers deteriorates

Engineering Contradiction:
Improveadaptability to new data typesVSAvoidsystem configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic configuration where the system automatically detects new file types and registers new consumers without requiring static pre-configuration. The conductor service dynamically updates the registry of available files and consumer capabilities, allowing the system to adapt to changing data types and consumers in real-time without manual intervention or system shutdowns.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system employs self-service mechanisms where the conductor service automatically discovers new file types produced by producer services and autonomously registers them in the registry. Similarly, consumer services automatically register themselves and their data requirements with the conductor, eliminating the need for manual configuration and enabling the system to serve itself as it evolves.

Inventive Principle:
Principle #25Self-service

2Reliability

If static configuration files are used to define data types and consumers, then system reliability is improved, but downtime increases when changes are needed

Engineering Contradiction:
Improvesystem uptimeVSAvoiddowntime for configuration changes
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent ensures continuous operation by implementing a configuration system that allows changes to be made without shutting down the system. Producer services, consumer services, and the conductor service continue to operate and process data throughout the configuration update process, eliminating downtime and ensuring uninterrupted useful action while the system adapts to new requirements.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system performs preliminary registration and detection actions where the conductor service maintains a registry of available files and consumer capabilities in advance. When new file types or consumers are introduced, they are pre-registered and detected before being actively used, allowing the system to prepare for changes without interrupting ongoing operations and minimizing any potential downtime.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If manual configuration updates are performed to add new file types or consumers, then measurement precision of system state is improved, but productivity deteriorates

Engineering Contradiction:
Improvespeed of system adaptationVSAvoidautomatic discovery and registration
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent implements feedback mechanisms where producer services notify the conductor service when new file types are produced, and consumer services notify the conductor of their data requirements. The conductor continuously monitors and updates the registry based on this feedback, enabling automatic detection and registration of new files and consumers without manual intervention, thereby high productivity and extensive automation.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system enables self-service through automatic discovery and registration capabilities. Producer services automatically announce their produced file types to the conductor, and consumer services automatically register their data requirements. The conductor autonomously maintains the registry by processing these self-service announcements, eliminating manual configuration tasks and enabling rapid system adaptation with high automation.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If the system grows to accommodate additional content creators and recipients, then versatility is improved, but data latency increases

Engineering Contradiction:
Improvecapacity for additional participantsVSAvoiddata latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the system into independent, distributed services (producer services, consumer services, and conductor service) that operate autonomously. Each service maintains its own local state and communicates through standardized interfaces. This segmentation allows the system to scale to accommodate additional participants without creating centralized bottlenecks, as each service can process and respond to requests independently, thereby maintaining low latency even as the system grows in versatility.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12339806B2Computerized systems and methods for distributed file collection and processing
Publication Date: 2025.06.24 YAHOO AD TECH LLC
  • US12339806B2 patent drawing
  • US12339806B2 patent drawing
  • US12339806B2 patent drawing

AI summary

Systems and methods are disclosed for distributed file collection and processing. According to certain embodiments, a producer system may detect a producer configuration file that specifies a file type, identify at least one file of the specified file type, and send the at least one identified file to a collector system. A conductor system may receive a request from a consumer system and allocate the at least one identified file to the consumer system based on the request. The collector system may receive the at least one identified file from the producer system. The consumer system may send the request to the conductor system and pull the at least one identified file from the collector system.