Catalogue-Based Data Processing Workflow Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In telecommunications data processing, existing systems require significant skill and human resources to handle and execute a wide range of data processing requests, making it inefficient to adapt and expand workflows.
Innovation Solution
A catalogue-based data processing management system that uses a generic algorithm to interpret rules underlying different workflows, allowing for metadata changes without additional programming skills, enabling faster development and deployment of services and reducing Total-Cost-of-Ownership (TCO).
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple different data processing workflows are hardcoded to handle various data processing requests, then the system can execute a wide range of workflows, but the skill and human resources required to adapt and expand workflows increase significantly
Solution Approach 1:
The patent introduces a catalogue as an intermediary layer between the hardcoded workflows and the data processing requests. The catalogue stores metadata that describes different workflows, allowing the system to select and execute appropriate workflows without hardcoding multiple specific implementations. This intermediary catalogue reduces system complexity while maintaining workflow versatility.
Solution Approach 2:
The patent creates a universal workflow execution mechanism that can handle multiple different data processing workflows through a single standardized interface. The catalogue-driven architecture allows one system to perform multiple workflow functions by simply changing the metadata configuration, rather than requiring separate hardcoded implementations for each workflow type.
2Adaptability or versatility
If multiple different data processing workflows are hardcoded to handle various data processing requests, then the system can execute a wide range of workflows, but the time and resources required to adapt and expand workflows increase significantly
Solution Approach 1:
The catalogue acts as a mediator that enables rapid workflow adaptation through metadata configuration rather than code modification. This intermediary layer allows business users to adapt workflows by simply adding or modifying catalogue entries, dramatically improving workflow adaptation efficiency while maintaining system versatility.
Solution Approach 2:
The patent pre-structures the workflow adaptation mechanism with a standardized catalogue framework and metadata schemas. This preliminary setup allows workflows to be adapted quickly by simply filling in predefined templates and configurations, rather than requiring time-consuming custom development for each new workflow requirement.
3Loss of time
If a catalogue-driven architecture is implemented to reduce workflow adaptation complexity, then service deployment time is reduced, but the initial system setup and catalogue configuration require significant effort
Solution Approach 1:
The patent implements preliminary action by pre-defining the catalogue structure, metadata schemas, and workflow templates during the initial system setup. This upfront effort creates a reusable framework that dramatically reduces service deployment time for subsequent workflows. The initial configuration work pays dividends through rapid future adaptations.
Solution Approach 2:
The catalogue-driven architecture enables copying of existing workflow configurations and metadata templates. Once a workflow is configured and validated, it can be copied and adapted for similar use cases by simply modifying catalogue entries rather than recreating workflows from scratch, reducing both initial setup and ongoing deployment efforts.
Data Source
Figure 1
Figure 2
Figure 3A~3B
AI summary
The disclosure concerns a data processing management system for automatically adapting a data processing workflow, in particular a telecommunications processing workflow, comprising a reception unit configured to receive data input in relation to a data processing request; a data processing request analysis unit configured to analyse the data input to determine at least one request parameter; a data processing workflow retrieval unit configured to access a predetermined data processing workflow database and to select a data processing workflow based on the at least one request parameter; a data processing workflow parameter unit configured to access a predetermined technical entity database and to select at least one technical entity based on the at least one request parameter; a data processing workflow adapting unit configured to adapt the selected data processing workflow by accessing a pre-defined task database and including at least one pre-defined task from the pre-defined task database into the selected data processing workflow based on the at least one request parameter and the at least one technical entity, and/or adapting at least one task of the selected data processing workflow based on the at least one request parameter and the at least one technical entity; and a data processing workflow execution unit configured to execute at least one task of the adapted data processing workflow.