Domain Interface Engine With Microbots for Scalable Virtual Assistants

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional virtual assistant applications face challenges due to their monolithic architecture, which hinders scalability, flexibility, and maintenance, necessitating extensive preprocessing and integration of backend domain content, leading to prolonged development cycles, incompatibility with legacy systems, and inaccuracies in AI model performance.

Innovation Solution

Implementing a domain interface engine with modular microbots, each assigned to a specific backend domain, allowing for decoupled architecture, independent updates, and specialized AI models, reducing resource consumption and improving response accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a monolithic architecture is used for VA applications, then development and deployment are simplified, but scalability and flexibility are hindered

Engineering Contradiction:

Improveease of developmentVSAvoidscalability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments the monolithic VA application into multiple independent microservices, each handling specific functions such as NLP, dialogue management, and domain-specific tasks. This segmentation enables independent deployment, scaling, and maintenance of each microservice while maintaining overall system functionality.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (service mesh or API gateway) that facilitates communication between microservices and backend domains. This intermediary enables loose coupling, allowing microservices to be updated and scaled independently while maintaining system-wide coordination.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If a monolithic architecture is used for VA applications, then the system structure is simplified, but maintenance and updates become difficult

Engineering Contradiction:

Improvesystem structureVSAvoidease of maintenance

Core Design Contradiction:

Device complexityVSEase of repair

Solution Approach 1:

The patent divides the monolithic system into modular microservices that can be independently maintained and updated. Each microservice encapsulates specific functionality, making it easier to locate, test, and update without affecting the entire system.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts specific functionalities from the monolithic system into separate microservices. This extraction allows targeted maintenance and updates of only the affected components rather than requiring full system reconfiguration.

Inventive Principle:

Principle #2Taking out (Extraction)

3Measurement precision

If extensive preprocessing and integration of backend domain content is performed, then AI model accuracy is improved, but development cycles are prolonged

Engineering Contradiction:

ImproveAI model accuracyVSAvoiddevelopment cycle

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-processing and organizing backend domain content into structured formats before AI model training. This advance preparation reduces the time required for model development and iteration while maintaining high accuracy.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic content retrieval where microservices fetch relevant domain content on-demand during runtime rather than pre-loading all content. This dynamic approach reduces initial processing time while ensuring accurate responses through contextual content retrieval.

Inventive Principle:

Principle #15Dynamics

4Adaptability or versatility

If a monolithic architecture is used, then all functionalities are bundled together, but isolation and scalability of individual components are hindered

Engineering Contradiction:

Improvefunctional integrationVSAvoidcomponent scalability

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the monolithic architecture into independent microservices that can be scaled individually based on demand. Each microservice maintains its own resource allocation, enabling horizontal scaling of specific components without affecting the entire system.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates universal microservice templates that can be replicated and deployed across multiple domains. These standardized microservices maintain consistent functionality while allowing independent scaling and customization for different backend domains.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12443636B1Domain interface engine(s) for virtual assistant applications

Publication Date: 2025.10.14 ORACLE INT CORP

AI summary

Various embodiments of the present technology generally relate to systems and methods for providing a domain interface engine for virtual assistant applications. In an example, a method includes receiving, by a domain interface engine, a user query from a first client device. The domain interface engine may include multiple microbots, each of which is assigned to a respective backend domain. The domain interface engine may determine a first microbot for handling the user query. The first microbot may be assigned to a first backend domain and may retrieve a domain content from the first backend domain corresponding to the user query. The first microbot may also generate a query response based on the domain content and the domain interface engine may transmit the query response to the first client device.