Natural Language Document Orchestrator for Selective Pipeline Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing natural language generation systems require full processing through a pipeline for text generation, which is inefficient when input data is already partially processed or only requires minor adjustments, leading to unnecessary steps and resource utilization.

Innovation Solution

A document orchestrator that allows developers to write scripts to invoke NLG services at different levels, enabling selective use of pipeline modules based on input requirements, such as document planning, microplanning, or morphology processing, to generate natural language text efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full processing through a pipeline is used for text generation, then text generation reliability is ensured, but processing time and resource usage increase unnecessarily when input data is already partially processed

Engineering Contradiction:
Improvetext generation reliabilityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the NLG pipeline into independent, modular components (document planning module, microplanning module, morphology processing module, etc.) that can be selectively invoked. Each module is a self-contained unit with defined input and output interfaces, allowing the system to process data through only the necessary modules rather than forcing full pipeline execution. This segmentation enables the system to maintain reliability by ensuring each module meets quality standards while reducing processing time by skipping already-processed stages.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic pipeline configuration where the processing path is determined at runtime based on the input data characteristics and processing requirements. The system can adaptively select which pipeline modules to invoke, transitioning from a static full-pipeline approach to a dynamic selective-execution approach. This allows the system to optimize processing efficiency for different input scenarios while maintaining the capability to execute complete processing when needed for reliability.

Inventive Principle:
Principle #15Dynamics

2Reliability

If full processing through a pipeline is used for text generation, then processing completeness is ensured, but resource utilization increases unnecessarily when input data is already partially processed

Engineering Contradiction:
Improveprocessing completenessVSAvoidresource utilization
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

By dividing the NLG system into discrete, independently invokable modules, the patent enables selective execution of only those processing stages required for the given input data. This prevents unnecessary resource consumption on already-processed data while maintaining processing completeness through appropriate module selection. Each segment can be executed independently, ensuring that essential processing steps are completed without wasting resources on redundant operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the operational parameters of the processing system by introducing configurable invocation flags and processing state indicators that determine which pipeline modules are activated. These parameter changes allow the system to adjust resource allocation dynamically based on input data characteristics, ensuring processing completeness is achieved with minimal necessary resource utilization rather than always executing at full capacity.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If selective use of pipeline modules is enabled, then processing efficiency improves, but system complexity increases due to module coordination requirements

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal document orchestrator component that handles the coordination of all pipeline modules through a standardized interface. This orchestrator provides multi-functional capabilities including module selection, parameter passing, result aggregation, and error handling, thereby reducing the complexity that would otherwise be distributed across multiple coordination points. By centralizing these control functions in a single universal component, the system achieves selective module execution while managing complexity through interface standardization.

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

4Adaptability or versatility

If developers can invoke NLG services at different levels, then flexibility and adaptability improve, but ease of operation decreases due to increased control complexity

Engineering Contradiction:
Improvesystem flexibilityVSAvoidease of use
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a document orchestrator as an intermediary layer between the user and the underlying NLG pipeline modules. This orchestrator provides a simplified, high-level interface that abstracts the complexity of individual module invocation while maintaining the ability to selectively execute modules at different processing levels. Users interact with the orchestrator rather than directly managing module calls, which preserves system flexibility and adaptability while improving ease of operation through interface abstraction.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11727222B2Method and apparatus for natural language document orchestrator
Publication Date: 2023.08.15 ARRIA DATA2TEXT
  • US11727222B2 patent drawing
  • US11727222B2 patent drawing
  • US11727222B2 patent drawing

AI summary

Methods, apparatuses, and computer program products are described herein that are configured to be embodied as a natural language document orchestrator. In some example embodiments, a method is provided that comprises generating natural language text. The method of this embodiment may also include executing document orchestration requests from a scripted input language file.