Conversational Interface Generation from Web Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Converting web-based interfaces into conversational interfaces is a labor-intensive, subjective process that results in inconsistent conversational flows, requiring significant manual effort and time, especially when dealing with numerous web-based applications.

Innovation Solution

Dynamically generating conversational flows from metadata used for web-based interfaces, allowing for the creation of ordered series of queries with dependencies, enabling flexible and rich dialog trees without manual configuration, and enabling automatic generation and modification of conversational interfaces based on application rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual conversion of web-based interfaces to conversational interfaces is performed, then custom conversational flows can be created, but significant labor and time are required

Engineering Contradiction:
Improveconversational flow customizationVSAvoidconversion speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent copies the existing metadata structure from web-based interfaces and reuses it to generate conversational interfaces automatically. Instead of manually creating conversational flows from scratch, the system copies the interface definition metadata and transforms it into the appropriate conversational format, dramatically reducing conversion time while maintaining consistency with the original interface design

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent changes the interpretation parameters of existing metadata to generate different interface types. By modifying how the same metadata is processed and rendered, the system can generate both web-based and conversational interfaces from identical source definitions, enabling rapid adaptation without manual rework

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If manual conversion is used, then conversational interfaces can be created, but consistency across different applications is compromised

Engineering Contradiction:
Improveconversational flow designVSAvoidflow consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent creates a universal metadata schema that serves multiple purposes: defining web-based interfaces, generating conversational interfaces, and ensuring consistency across applications. This single metadata structure can be interpreted differently to produce various interface types while maintaining uniformity in data organization, field definitions, and conversational logic across the entire application suite

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

3Ease of operation

If extensive manual effort is invested in conversion, then conversational interfaces can be developed, but the process is subjective and varies by individual experience

Engineering Contradiction:
Improveinterface functionalityVSAvoidconversion standardization
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The patent enables the system to generate conversational interfaces automatically from metadata without requiring manual intervention. The metadata contains all necessary information about interface structure, data fields, and relationships, allowing the system to self-configure conversational flows, validation rules, and interaction patterns consistently across all applications

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11449535B2Generating conversational interfaces based on metadata
Publication Date: 2022.09.20 SERVICENOW INC
  • US11449535B2 patent drawing
  • US11449535B2 patent drawing
  • US11449535B2 patent drawing

AI summary

An embodiment may involve persistent storage containing an ordered set of queries that are respectively associated with textual prompts, visibility indicators, definitions of answer formats, and zero or more dependencies on other queries in the ordered set of queries. One or more processors may be configured to iterate through the ordered set of queries, and for a query therein: retrieve the query; determine that the query has a dependency on a previous query; modify a textual prompt of the query, a visibility indicator of the query, or a definition of an answer format of the query; determine that the visibility indicator specifies that the query is visible; provide, by way of a conversational interface, the textual prompt; receive, by way of the conversational interface, an input in response to the textual prompt; verify that the input matches the definition of the answer format; and store the input.