Browser Native App Connection via Background Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing browser extensions and plug-ins are limited in their ability to provide automated access to resources associated with events detected on local applications, requiring users to navigate multiple applications and databases, which is time-consuming and inefficient for enterprise applications.

Innovation Solution

A system that includes a web browser with a native application and a background service component, allowing executable code to establish a connection between the browser and native applications, enabling automated access to computing device resources and synchronization of events between browser and native applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If browser extensions are used to extend browser functionality, then the browser can access local application resources, but the system complexity increases and multiple versions must be maintained for different browser types

Engineering Contradiction:
Improvebrowser functionality extensionVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a background service as an intermediary component that mediates between the browser and local applications. This service handles the complexity of resource access and event synchronization, allowing the browser to extend functionality without directly managing the complexity of local application integration. The background service acts as a universal mediator that works across different browser types, reducing the need for multiple specialized extensions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The background service provides universal functionality that can operate with different types of browsers and local applications. Instead of creating separate extensions for each browser type, the system uses a single background service that can communicate with various browsers through standardized interfaces, reducing maintenance burden while maintaining versatility.

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

2Reliability

If users manually navigate between applications to retrieve resources, then existing applications can function independently, but the time required increases significantly

Engineering Contradiction:
Improveapplication independenceVSAvoidresource retrieval time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements event-driven feedback mechanisms where local applications automatically notify the background service when events occur. The browser then receives these events and can automatically retrieve relevant resources without requiring manual user intervention. This feedback loop eliminates the need for users to manually navigate between applications while maintaining application independence.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The background service pre-establishes connections and indexing mechanisms with local applications, enabling rapid resource retrieval when events occur. By preparing the infrastructure in advance, the system can quickly synchronize resources between browser and local applications without requiring manual navigation during operation.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If plug-ins are used for page-specific operations, then user permission is required for each operation, but the ease of automated access decreases

Engineering Contradiction:
Improveuser permission requirementVSAvoidautomated access capability
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The patent segments the automation permission model into two phases: initial permission grant during background service installation, and automated execution during operation. Users provide permission once during service installation, after which the system can automatically access resources without requiring permission for each individual operation, thus enabling automation while maintaining security.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10949487B2Systems and methods for accessing computing device resources
Publication Date: 2021.03.16 HYLAND SWITZERLAND SARL
  • US10949487B2 patent drawing
  • US10949487B2 patent drawing
  • US10949487B2 patent drawing

AI summary

A method of accessing a computing device resource includes loading a web application into a web browser running on a computing device; determining, by the web application, whether a native application is active on the computing device; and if the native application is active, establishing a connection between the web application and a native application; and receiving information about the computing device resource through the native application.