Industrial IoT device discovery is often treated as a preliminary step: find the equipment, install its app, connect, and then begin work. In practice, those steps can create friction for engineers, system integrators, and operators—especially when devices are new, used only occasionally, or not connected to the internet. A Web of Things approach offers a different model: let a device advertise a link to its interface, then use a browser-based application to discover and interact with it over a local wireless connection.
The approach is not a replacement for every industrial application or security architecture. It is a way to rethink how people reach device interfaces, particularly for nearby equipment that needs an immediate, context-specific user experience without requiring a separate native app for every device.
Why industrial IoT device discovery can be cumbersome
Many connected devices rely on mobile apps to provide controls and displays that are impractical to place on the device itself. That shifts interaction to a phone or tablet, but can also require users to identify the correct app, install it, locate the device, pair with it, and configure a connection. Device makers, in turn, may need to develop and maintain native software for multiple mobile platforms.
These steps can be inconvenient for a device used briefly during commissioning or troubleshooting. They can also complicate routine interaction with equipment used across a facility. The challenge is not simply opening an interface: the user needs to know which device the interface belongs to and whether it can connect to that device.
Internet access can add another constraint. Some IoT systems expect both the device and the mobile phone to be online, even when the user needs to communicate only with nearby equipment. A local connection can be more suitable for devices with limited power or network resources, or for situations where an internet connection is unavailable.
A Web of Things model for local device interaction
The proposed model associates web content with a connected device. A device broadcasts a URL that points to its user interface, and a phone or other compatible client detects that advertisement. The browser can then present the link along with information about the corresponding device. When a user opens it, a web app can load in a browser-controlled environment and communicate directly with the device over a local protocol such as Bluetooth Low Energy (BLE).
This separates the source of the interface from the path used to communicate with the device. The web app can be hosted online, while its interaction with the equipment takes place locally. The device therefore does not necessarily need its own internet connection for the user to access the interface and communicate with it.
In a prototype implementation described by the authors, the mobile browser discovered devices broadcasting URLs, retrieved details about the corresponding interfaces, and opened web apps that could use browser-provided APIs to communicate with devices. The implementation also supported Wi-Fi device discovery through multicast DNS (mDNS). These examples demonstrate an architecture and prototype, not a universal capability already available in every browser or industrial device.
Discovery, connection, and trust must work together
Finding a URL is only useful if the user can tell what it represents. A discovery interface should show relevant device information alongside the web app link. Otherwise, operators may still have to guess which nearby device is associated with a page—particularly in a dense installation where several devices are within radio range.
The design also addresses how a web page is authorized to access a device. In a conventional browser pairing flow, a user may be asked to select a device from a list. That can make the user responsible for matching the right device to the right interface. The proposed alternative treats the device as a resource of the website it advertises: the URL acts as a declaration of association, and the browser can limit access to devices that have declared that relationship or have explicitly permitted cross-origin access.
This is an architectural security idea, not a substitute for an organization’s authentication, authorization, or operational controls. Developers can still implement additional authentication in the interface. For industrial deployment, teams would need to evaluate the trust model, user permissions, device identity, and the consequences of granting local access in their specific environment.
What the approach could enable
Short-term access without a dedicated app
A browser-based interface can reduce the need to install a separate native app for a brief interaction. This may be useful for occasional device access, such as viewing local sensor information or using a device-specific control page, provided the relevant browser APIs and device protocol are supported.
Persistent interfaces and offline access
Web app resources can be cached on a phone for quicker repeat access and use when an internet connection is unavailable. In the prototype, the browser cached interface details and resources. Caching can reduce repeated downloads, but teams must consider how updates are managed and how local stored information is protected.
Working with groups of devices
When several devices advertise the same interface URL, a browser can group them under one listing. A single interface could then present multiple related devices, rather than requiring a separate page for each one. The broader design also considers interfaces that can coordinate different device types, although orchestration depends on the required services and permissions.
Practical considerations for automation teams
For engineers and system integrators assessing this model, the key questions are operational as well as technical:
- Discovery: What broadcast protocol and device information are available, and how will users distinguish nearby equipment?
- Connectivity: Can the interface communicate over a supported local protocol without depending on an internet connection?
- Security: How are device-to-interface associations established, and what additional authentication or permissions are required?
- Persistence: Should interfaces be cached for repeat use, and how will cached content remain current?
- Platform support: Are the required browser APIs available on the mobile devices used by operators and technicians?
Radio discovery also has practical limits. The prototype evaluation found that detection depends on factors including advertisement interval, proximity, and signal strength. Signal strength can vary over time, so presenting devices in a continually changing order may make selection harder. A stable, understandable device list matters as much as the underlying connection mechanism.
Conclusion
A browser-based Web of Things architecture reframes industrial IoT device discovery as a connected flow: discover a nearby device, identify its interface, and interact locally through a web app. URL broadcasts, device-aware listings, browser APIs, and caching could reduce dependence on per-device native apps and support access when internet connectivity is limited. Before adopting the approach, automation teams should validate platform compatibility, device identification, security, and lifecycle management. Its practical value depends on making discovery and access simpler without weakening the controls required for industrial operations.