Graphical Workflow Construction With Function Blocks and Behavior Trees
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workflow systems rely on text descriptions, requiring users to navigate multiple engineering tools with different user interfaces, leading to increased costs, reduced efficiency, and limited flexibility due to long development cycles.
Innovation Solution
A workflow construction method and system that uses a graphical user interface (GUI) to receive function block node addition and connection operations, allowing users to construct behavior trees by dragging and connecting function block nodes, which represent service operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If text descriptions are used for workflows, then implementation flexibility is maintained, but user operation complexity increases and efficiency decreases
Solution Approach 1:
The patent uses graphical function block nodes as visual copies of service operations, allowing users to drag and connect pre-defined functional blocks to create workflows. This visual copying approach eliminates the need to write text descriptions from scratch, improving both ease of operation and creation efficiency.
Solution Approach 2:
The patent segments workflows into discrete function block nodes, each representing a specific service operation. Users can independently select, drag, and connect these segmented functional blocks, making workflow creation more manageable and efficient compared to writing entire text descriptions.
2Adaptability or versatility
If multiple engineering tools are used for workflow execution, then specific service functions are achieved, but system complexity increases and development cycle lengthens
Solution Approach 1:
The patent creates a universal graphical interface platform that can execute multiple types of service operations through a single unified system. The function block nodes represent different service functions (data collection, annotation, training, deployment), all accessible through one platform, eliminating the need for multiple separate engineering tools.
Solution Approach 2:
The patent merges multiple engineering tools into a single integrated graphical interface system. By combining data collection, annotation, model training, and deployment capabilities into one unified platform with consistent graphical operations, it reduces the number of separate tools users must navigate.
3Adaptability or versatility
If multiple engineering tools with different interfaces are used, then specific service operations can be performed, but user operation consistency deteriorates
Solution Approach 1:
The patent implements a universal graphical interface that provides consistent drag-and-drop operations for all service types. The same interaction paradigm (dragging function blocks, connecting ports) works across data collection, annotation, training, and deployment operations, ensuring interface consistency while maintaining versatility.
4Adaptability or versatility
If text-based workflow descriptions are used, then implementation flexibility is maintained, but development cycle time increases
Solution Approach 1:
The patent prepares function block nodes with pre-defined service operations and parameters before users need them. These pre-configured graphical blocks can be directly dragged into workflows without requiring users to write or configure text descriptions, significantly reducing development cycle time while maintaining flexibility through selectable block types.
Data Source
AI summary
Various embodiments of the teachings herein include a workflow construction method. An example includes: receiving function block node addition and connection operations from a GUI on the basis of function block type graphs, wherein each function block node implements a service operation; and constructing a behavior tree corresponding to one workflow in response to the function block node addition and connection operations. Each function block type graph comprises: a function block name, a function block header, a link input port and a link output port, an input data chunk and an output data chunk, a data input port and a data output port, and a function block body. The function block node addition operation comprises a dragging operation.