Integration Bot Architecture for Multi-Service Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The development of multiple bot applications is cumbersome and expensive due to the need for separate conversational components, and users face frustration when accessing multiple chat applications to communicate with various bot applications, leading to a barrier in creating a healthy ecosystem of bot applications and discouragement in using bot application functionality.
Innovation Solution
An integration bot is introduced to communicate with multiple domain bots, allowing users to access various data and services without needing to interface directly with each bot application, using a conversational interface or command sequences, and offloading context determination and chat text analysis, thus simplifying the development of new domain bots and providing secure communication based on security levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate conversational components are used for each bot application, then each bot can be developed independently, but the development cost and time increase significantly
Solution Approach 1:
The patent implements a universal conversational component that can serve multiple bot applications simultaneously. This shared component handles common conversational tasks such as natural language processing, intent recognition, and dialogue state tracking, allowing different bot applications to reuse the same infrastructure rather than each requiring separate components.
Solution Approach 2:
The patent merges multiple bot applications into a unified system architecture where they share common conversational processing capabilities. By combining the conversational components into a shared service, the system reduces redundancy and enables efficient resource utilization across multiple bot applications.
2Adaptability or versatility
If users access multiple chat applications to communicate with different bot applications, then each bot application can be accessed, but user frustration increases and usability decreases
Solution Approach 1:
The patent merges multiple bot applications into a single unified chat application interface. Users can access and interact with multiple bot applications through one consolidated interface rather than switching between separate chat applications, thereby improving ease of operation while maintaining access to all bot functionalities.
Solution Approach 2:
The unified chat application provides universal access to multiple bot applications through a single interface. This multi-functional platform allows users to interact with different bot applications without needing separate chat applications, enhancing user convenience and accessibility.
3Ease of operation
If a unified interface is used to access multiple bot applications, then user accessibility improves, but the system complexity increases
Solution Approach 1:
The patent segments the system into distinct modular components: a unified user interface layer, a conversational processing layer, and individual bot application layers. This segmentation allows the complex system to be organized into manageable, independent modules that can be developed, maintained, and scaled separately, reducing overall system complexity despite the unified interface.
Solution Approach 2:
The patent introduces an intermediary conversational component that mediates between the unified user interface and multiple bot applications. This intermediary layer handles the complexity of routing user interactions to appropriate bots, managing dialogue state, and coordinating responses, thereby shielding the user from underlying system complexity while enabling unified access.
Data Source
AI summary
A method for using multi-level bots is discussed. The method includes accessing, via an integration bot, a chat text, provided by a chat application instance, that indicates a user query. The method includes accessing a user state associated with a user of the chat application instance, the user state indicating previous chat texts associated with the chat application instance and corresponding knowledge queries. The method includes generating, based on the user state and analysis of the chat text, a knowledge query for data access using one or more domain bots. The method includes determining, based on the knowledge query, a domain bot and associated communication protocol. The method includes communicating the knowledge query using the communication protocol to the domain bot to obtain a reply. The method includes communicating a response text to the chat application instance, the response text generated based on the reply and the user state.