URI Broker Mediates Custom Scheme Invocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies lack the capability to natively handle URI invocation actions in various applications, limiting their functionality and user experience.

Innovation Solution

A system and method that allows developers to embed URIs in HTML, applications, or documents to invoke specific applications or functionalities, using a URI Broker that redirects the URI selection to the appropriate app based on predefined mappings, enabling actions like telephony, messaging, and presence updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard URI handling is used in applications, then compatibility with common protocols is maintained, but functionality for custom actions and non-standard applications is limited

Engineering Contradiction:
ImproveURI invocation capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a URI Broker as an intermediary component that sits between the URI invocation system and target applications. The broker receives URI invocations, interprets custom URI schemes, resolves them to appropriate applications or actions, and manages the invocation process. This mediator enables custom URI handling without requiring changes to the core operating system or application framework, thus maintaining system simplicity while extending functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If custom URI schemes are implemented without a broker, then direct application invocation is achieved, but reliability and proper routing of URI actions are compromised

Engineering Contradiction:
ImproveURI action executionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The URI Broker is designed as a universal component that can handle multiple types of URI schemes and invoke various applications through a single unified interface. It provides multi-functional capabilities including URI parsing, application resolution, action routing, and fallback management. This universal approach ensures reliable URI action execution across different scenarios without requiring separate custom implementations for each application or URI type.

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

3Adaptability or versatility

If URI handling is built into each application natively, then each app can independently process URIs, but the overall system lacks unified management and consistency

Engineering Contradiction:
Improveapplication-specific URI handlingVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The URI Broker serves as a centralized intermediary that manages URI handling across the entire system. Rather than requiring each application to implement its own native URI parsing and routing logic, applications can rely on the broker to interpret custom URI schemes and route invocations appropriately. This maintains adaptability for application-specific needs while providing unified management and consistency through the central broker.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10447797B2Method and system for a uniform resource identifier (URI) broker
Publication Date: 2019.10.15 AVAYA INC
  • US10447797B2 patent drawing
  • US10447797B2 patent drawing
  • US10447797B2 patent drawing

AI summary

A system provides the ability for developers to create and embed a URI in HTML, a document, or an application to invoke another application or functionality according to a URI scheme name. The invoked application does not natively react to URI selections. Rather, a URI Broker can redirect the URI selection to the desired application and conduct any pre-processing to allow the URI to invoke any application, even those that do not include URI capability.