Remote Device Infrastructure for Browser-Based Multi-Platform Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software developers face challenges in testing their products across a multitude of hardware and software platforms without having to acquire and configure multiple devices, due to the vast array of devices, operating systems, and browsers used by consumers, which strains resources and may lead to overlooked market segments.

Innovation Solution

A remote test system (RTS) that allows developers to connect to a centralized server with various devices, mirror the remote device's display on their local machine, and translate user inputs to the remote device, enabling seamless interaction and testing across different platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers acquire and configure multiple physical devices for testing, then testing coverage across different platforms is improved, but resource strain and device management complexity increase

Engineering Contradiction:
Improvetesting coverageVSAvoiddevice management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates virtual copies of physical devices through cloud-based virtualization. Instead of managing multiple physical devices, developers interact with virtual device instances that replicate the behavior and characteristics of target devices. This allows comprehensive testing coverage while eliminating the complexity of physical device acquisition, configuration, and maintenance.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a cloud-based intermediary layer between the developer's local machine and the target devices. This intermediary manages the device fleet, handles device provisioning, and coordinates testing sessions. Developers interact with this intermediary through a web interface, which abstracts away the complexity of direct device management while maintaining full testing capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If developers use multiple physical devices for testing, then platform compatibility is ensured, but resource strain and setup time increase

Engineering Contradiction:
Improveplatform compatibilityVSAvoidsetup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs device setup and configuration in advance through automated provisioning processes. Virtual device instances are pre-configured with necessary software, drivers, and testing environments before developers need them. When a testing session is initiated, the system quickly allocates a ready-to-use virtual device, eliminating the time-consuming setup process that would occur with physical devices.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates virtual replicas of target devices that can be rapidly instantiated and destroyed. These virtual copies maintain full platform compatibility characteristics without requiring physical device presence. Developers can access multiple device types simultaneously through these virtual copies, ensuring comprehensive platform testing without the logistical burden of physical device management.

Inventive Principle:
Principle #26Copying

3Ease of operation

If developers physically handle multiple devices, then direct device interaction is achieved, but resource strain and operational complexity increase

Engineering Contradiction:
Improvedevice interactionVSAvoidinfrastructure management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent replaces the mechanical interaction of physically handling devices with electronic/software-based interaction. Developers control virtual devices through web interfaces and automated scripts rather than manual physical manipulation. This substitution maintains full interaction capabilities (clicking, typing, gesturing) while eliminating the need for physical device presence and the complexity associated with managing physical device fleets.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250220065A1Remote device infrastructure
Publication Date: 2025.07.03 BROWSERSTACK LTD
  • US20250220065A1 patent drawing
  • US20250220065A1 patent drawing
  • US20250220065A1 patent drawing

AI summary

Disclosed are systems and methods for enabling a developer to use a local browser, running on a local machine of the developer in a first location to access real devices (e.g., smart phones) at a second location, such as a data center. The developer can select and control the remote devices, in the second location. The described embodiments can capture developer's inputs from the first location and input them to the remote device in the second location. A video stream of the remote device is transmitted to the browser in the first location and displayed in a replica canvas on the developer's browser. The developer can interact with the canvas on his/her browser, as if the remote device were present in the first location.