Voice Assistant Runtime Component for Cross-Platform Web Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Voice assistants are limited by their reliance on specific platforms, operating systems, and hardware devices, making them cumbersome to use across different environments and lacking seamless functionality with web applications and web pages.

Innovation Solution

Implementing a voice assistant runtime component within client applications like web browsers, which compiles or interprets voice assistant functionality using universal application interfaces like WebAssembly, allowing voice commands to be executed without requiring specific platforms or locally installed applications, and enabling key word detection for hands-free operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If voice assistants are implemented on specific platforms or hardware devices, then voice assistant functionality is provided, but portability and accessibility across different devices are reduced

Engineering Contradiction:
Improveplatform compatibilityVSAvoidplatform-specific implementation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal voice assistant runtime that can execute on multiple platforms including web browsers, mobile devices, and desktop computers. The runtime component is designed to be platform-agnostic, allowing the same voice assistant functionality to operate across different operating systems and hardware architectures without requiring platform-specific implementations.

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

Solution Approach 2:

The patent introduces a runtime component as an intermediary layer between the voice assistant logic and the underlying platform. This runtime acts as a mediator that handles platform-specific variations, allowing the voice assistant to function universally while adapting to different environments through the runtime's abstraction layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If dedicated local applications are required for voice assistant functionality, then voice assistant capabilities are provided, but ease of access and convenience are reduced

Engineering Contradiction:
Improveaccess convenienceVSAvoidapplication installation requirement
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the voice assistant functionality from dedicated local applications and implements it within existing web browsers and client applications. By taking out the voice assistant core functionality and embedding it in universally available platforms like web browsers, users gain access to voice assistant capabilities without needing to install separate applications.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The voice assistant runtime is designed to function within multiple existing application types including web browsers, communication applications, and enterprise software. This multi-functional approach allows a single runtime implementation to provide voice assistant access across diverse applications without requiring separate dedicated applications for each use case.

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

3Productivity

If voice assistants are implemented client-side, then responsiveness and functionality are improved, but platform dependency and lack of cross-platform functionality increase

Engineering Contradiction:
Improvecommand execution capabilityVSAvoidcross-platform functionality
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The runtime component serves as an intermediary that enables client-side voice assistant processing while maintaining cross-platform compatibility. It mediates between the client-side execution environment and the voice assistant functionality, allowing responsive local processing to occur while the runtime handles platform-specific adaptations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements parameter changes by adapting the runtime's configuration and behavior based on the detected platform environment. The runtime can modify its operational parameters, supported features, and resource allocation based on whether it's running in a web browser, mobile application, or desktop environment, thereby maintaining optimal performance across different platforms.

Inventive Principle:
Principle #35Parameter changes

4Ease of manufacture

If web technologies are used for voice assistant implementation, then accessibility and ease of deployment are improved, but bandwidth consumption and functionality limitations increase

Engineering Contradiction:
Improvedeployment simplicityVSAvoidbandwidth usage
Core Design Contradiction:
Ease of manufactureVSQuantity of substance

Solution Approach 1:

The patent implements preliminary action by pre-compiling and caching voice assistant resources, models, and dependencies locally in the browser or application. This allows the system to minimize bandwidth consumption during actual voice assistant operations by having essential resources already available locally, reducing the need for repeated downloads or cloud dependencies.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11749276B2Voice assistant-enabled web application or web page
Publication Date: 2023.09.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11749276B2 patent drawing
  • US11749276B2 patent drawing
  • US11749276B2 patent drawing

AI summary

Various embodiments discussed herein enable applications to seamlessly contribute to executing voice commands of users via voice assistant functionality. In response to receiving a user request to open an application or web page, the application can request and responsively receive a voice assistant runtime component along with the application or web page. The application, using a particular universal application interface component can compile or interpret the voice assistant runtime component from a source code format to an intermediate code format. In response to the application or web page being rendered and the detection of a key word or phrase, the application can activate voice assistant command execution functionality. The user can issue a voice command after which the application along with specific services can help execute the voice command.