Document Verification System Parallel XML Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing document verification systems are inefficient and time-consuming when dealing with large batches of documents, requiring extensive computer resources and human input, and lack versatility in integrating with legacy document generation systems.

Innovation Solution

A document verification system comprising digital data processors with an interface for receiving electronic document runs, a normalization component for converting documents into a mark-up language taxonomy, a verification engine for real-time semantic checking, and a feedback component for error feedback, allowing for parallel processing and dynamic rule management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional document verification systems process large batches of documents, then verification completeness is improved, but processing time and computer resource consumption increase significantly

Engineering Contradiction:
Improveverification completenessVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The verification system segments the batch processing into individual document-level verification tasks. Each document is verified independently through parallel processing threads, allowing the system to maintain comprehensive verification checks while reducing overall processing time by distributing work across multiple concurrent operations rather than sequential processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from traditional sequential verification to a multi-dimensional parallel processing architecture. By implementing verification across multiple processing threads and utilizing XML-based data structures with hierarchical grouping, the system adds dimensional complexity to the processing architecture, enabling simultaneous verification of multiple documents while maintaining comprehensive check coverage.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If traditional verification systems perform comprehensive checks on each document, then verification quality is improved, but computer resource consumption increases

Engineering Contradiction:
Improveverification qualityVSAvoidcomputer resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system segments comprehensive verification checks into hierarchical groups of data items within each document. By organizing verification rules to operate on grouped elements rather than individual data points, the system maintains thorough verification quality while reducing computational overhead through efficient rule application at the group level.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary normalization of documents to XML format with predefined hierarchical structures before verification. This preliminary action organizes data into standardized groups and elements, enabling subsequent verification rules to execute more efficiently by operating on pre-structured data rather than raw document formats, thereby reducing computer resource consumption during the actual verification phase.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the system integrates with legacy document generation systems, then versatility is improved, but system complexity increases

Engineering Contradiction:
Improveintegration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces an XML-based intermediary layer between legacy document generation systems and the verification engine. Documents from various legacy systems are normalized to a common XML structure with standardized hierarchical groups, serving as a mediator that enables versatile integration without requiring complex point-to-point connections to each legacy system, thereby reducing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The verification system implements a universal XML-based processing framework that can handle documents from multiple legacy generation systems through a single standardized interface. The hierarchical group structure and normalization component provide multi-functional capability to process diverse document formats uniformly, enhancing versatility while avoiding the need for separate processing paths for each legacy system.

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

4Productivity

If the system processes documents in parallel streams, then productivity is improved, but coordination complexity increases

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

Solution Approach 1:

The system implements parallel processing by organizing verification rules and data structures into hierarchical XML groups that can be independently processed. This dimensional organization allows multiple processing threads to operate on different document groups simultaneously while maintaining coordinated verification through the standardized hierarchical structure, enabling high productivity without excessive coordination complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10121071B2Document verification system
Publication Date: 2018.11.06 BRITEBILL
  • US10121071B2 patent drawing
  • US10121071B2 patent drawing
  • US10121071B2 patent drawing

AI summary

A verification system (1) receives batches of documents in excess of 500,000 for external document generation systems. It verifies each document without affecting the core document-generation operations of the source document generation systems, and moreover enriches the documents by adding content such as recipient messages. It normalizes each document into an instance in a mark-up language, one instance per document. In the normalized format, the system performs verification checks including semantic checking across data items in groups. The servers (10, 11) are configured as multi-threaded platforms that process the document instances in parallel, typically validating the instance documents, pattern matching for relevant facts or events and implementing business rules and output actions such as generation of a print stream. There are separate but interlinked verification (10, 11) and presentment (20, 21, 25) branches. Meta data and atomic facts are generated in the verification branch and transferred to the presentment branch for use by it in document sending and possible additional personalization.