Thin Client Provisioning via WebView Communication Tunnels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network-connectable devices require frequent updates and large file sizes for provisioning data, and there is a risk of third-party access to sensitive information.

Innovation Solution

A method using a thin client with a communication tunnel between a network-connectable device, a mobile terminal, and a remote server, where provisioning data is transmitted through a webview and a library, minimizing data storage and updates on the client side, and ensuring secure data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If thick clients are used for provisioning network-connectable devices, then provisioning functionality is complete, but file size increases and frequent updates are required

Engineering Contradiction:
Improveprovisioning functionalityVSAvoidclient file size
Core Design Contradiction:
Adaptability or versatilityVSWeight of stationary object

Solution Approach 1:

The patent extracts the provisioning data and device management functionality from the client application and relocates it to a remote server. The client becomes a thin interface that communicates with the server, which stores and manages all provisioning data. This separation allows the client to remain lightweight while the server provides comprehensive provisioning capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a communication tunnel as an intermediary layer between the client and the remote server. This tunnel, established through the mobile terminal, enables secure data transmission without requiring the client to directly access or store sensitive provisioning data, thus maintaining functionality while minimizing client footprint.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If thick clients store provisioning data locally, then provisioning can be performed offline, but security risks increase due to third-party access

Engineering Contradiction:
Improveoffline provisioning capabilityVSAvoidthird-party access risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts provisioning data from local client storage and relocates it to secure server-side storage. The client application does not store sensitive data locally, eliminating the security vulnerability to third-party access while maintaining provisioning functionality through server communication.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The communication tunnel acts as a secure intermediary that transmits provisioning data between the client and server without exposing it to local storage vulnerabilities. This intermediary layer protects sensitive information from third-party access on the client device while enabling provisioning operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If provisioning data is stored on the client, then access speed is fast, but client updates are required frequently

Engineering Contradiction:
Improvedata access speedVSAvoidclient update interval
Core Design Contradiction:
SpeedVSDuration of action of stationary object

Solution Approach 1:

The patent extracts provisioning data from client-side storage and relocates it to server-side storage. The client accesses data through the communication tunnel, which provides fast access speeds while eliminating the need for frequent client updates since all data resides on the continuously maintainable server.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4085597B1Thin client for installing a network-connectable device
Publication Date: 2025.10.29 WITHINGS SAS
  • EP4085597B1 patent drawingFigure 1
  • EP4085597B1 patent drawingFigure 2~3

AI summary

The disclosure relates to methods and systems for provisioning a network-connectable device. A communication tunnel is formed for transmitting data between the network-connectable device, a mobile terminal and a remote server. The communication tunnel comprises a first link initiated using a webview embedded in an application on the mobile terminal and a second link initiated using a library attached to the webview. The first link connects the mobile terminal with the remote server. The second link connects the network-connectable device with the remote server through the mobile terminal. A data packet indicating that the network-connectable device is ready to be provisioned is received through the communication tunnel. A request for providing provisioning data is sent through the communication tunnel based on said data packet. Provisioning data are transmitted through the communication tunnel in response to sending the request. The network-connectable device is provisioned using the provisioning data.