Web-Based IoT Debugging via Browser Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional debugging methods for IoT devices require a debugging application to be downloaded and installed on a host device, limiting it to high-performance laptops or desktops and being undesirable for users, especially when debugging smaller IoT devices like temperature sensors or electronic door locks.

Innovation Solution

Enabling web-based interaction with a debug interface by communicatively coupling a host device to a node device using various connection mechanisms, allowing access to a debugger via a web browser, which can be accessed remotely or executed within the browser, eliminating the need for local installation of debugging software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a debugging application is downloaded and installed onto a host device, then debug functionality is provided, but the host device is limited to high-performance laptops or desktops and the installation process is undesirable for users

Engineering Contradiction:
Improveease of debugging accessVSAvoiddevice compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

A web server acts as an intermediary between the host device and the debugger. The debugger is hosted on the web server and accessed through a web browser on the host device, eliminating the need to install debugging software locally while maintaining full debug functionality across diverse device types

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the traditional mechanical installation process (downloading and installing debugging applications) with a web-based access model. Instead of installing software on the host device, users access the debugger through a web browser via network communication, substituting physical installation with digital access

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

2Adaptability or versatility

If a debugging application is downloaded and installed onto a host device, then debug functionality is provided, but the host device is limited to high-performance laptops or desktops

Engineering Contradiction:
Improvedevice compatibilityVSAvoidsystem requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The web server serves as an intermediary that handles the complex debugging operations remotely. This allows resource-constrained devices like smartphones and tablets to access full debugging functionality without needing to meet high-performance system requirements, as the computational burden is shifted to the server

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The web-based debugging interface provides universal access across multiple device types and operating systems. A single web browser implementation enables debugging functionality on diverse devices including smartphones, tablets, laptops, and desktops, eliminating the need for device-specific debugging applications

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

Data Source

PatentUS11321222B2Method and apparatus for debugging devices
Publication Date: 2022.05.03 ARM IP
  • US11321222B2 patent drawing
  • US11321222B2 patent drawing
  • US11321222B2 patent drawing

AI summary

Techniques are described for debugging node devices. A node device may be connected to a host device for debugging purposes. A debugger, providing debug functionality, such as a debugging web application, may run on a remote server and be accessed via a web browser running at the host device, to debug the node device. Alternatively, the debugging web application may execute in the web browser running at the host device to debug the node device. In another alternative, the debugging web application may execute at a gateway device provided between the node device and the host device. In all cases the debugging web application is controlled via a debug user interface running at the web browser. Consequently, a user of the host device is not required to install a debugger at the host device in order to debug a node device.