IoT Feature Exposure via Event Topics and Handler Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT devices face challenges in managing structured and unstructured data in real-time scenarios while providing an intuitive and maintainable architecture that allows easy extension of functionality, especially for novice users, and overcoming firewall issues to enable remote control.

Innovation Solution

An IoT device uses a definition file to map subscription event topics and event handlers, allowing it to subscribe to relevant topics via a message bus environment, generate a unique ID for secure communication, and expose features through a GUI, enabling secure and scalable control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a subscribe/publish architecture with multiple event listeners is used for IoT device control, then the device can handle various events flexibly, but the architecture becomes complex and difficult to maintain for novice users

Engineering Contradiction:
Improveevent handling flexibilityVSAvoidarchitecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an event manager as an intermediary component that sits between the event sources and multiple event listeners. This event manager centralizes the subscription logic and event routing, simplifying the architecture by eliminating the need for individual listeners to directly manage subscriptions. Novice users interact with a simplified interface while the event manager handles the complexity of multiple subscriptions and event routing internally.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple event listeners are implemented for real-time data handling, then real-time scenario processing capability is improved, but the difficulty of managing structured and unstructured data increases

Engineering Contradiction:
Improvereal-time processing capabilityVSAvoiddata management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the event handling process into distinct components: event subscription management, event routing, and event processing. Each event listener is assigned specific event types through the event manager, which organizes and structures the data flow. This segmentation allows real-time processing of both structured and unstructured data while reducing management complexity through clear separation of concerns and standardized data handling interfaces.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If a standardized event subscription approach is used, then ease of extension for novice users is improved, but the ability to handle complex event routing scenarios may be limited

Engineering Contradiction:
Improvefunctionality extension easeVSAvoidevent routing capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The event manager is designed as a universal component that provides multiple functions: subscription management, event routing, filtering, and dispatching to multiple listeners. It offers a standardized interface for novice users to subscribe to events while internally handling complex routing scenarios through configurable event types and listener mappings. This multi-functionality allows the same component to serve both simple and complex event handling needs.

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

Data Source

PatentUS12468645B2Methods, systems, and computer readable media for exposing features of an internet of things (IoT) device
Publication Date: 2025.11.11 KEYSIGHT TECHNOLOGIES INC
  • US12468645B2 patent drawing
  • US12468645B2 patent drawing
  • US12468645B2 patent drawing

AI summary

Methods, systems, and computer readable media for exposing features of an internet of things (IoT) device are disclosed. One example method for exposing features of an IoT device occurs at an IoT device. The method comprises: concurrently with or after bootup of the IoT device, accessing a definition file comprising one or more entries, wherein each of the one or more entries indicates a subscription event topic and an event handler for handling events associated with the subscription event topic; subscribing, via a message bus environment, to a first subscription event topic indicated by the definition file: receiving a first event message associated with the first subscription event topic; and processing, using a first event handler associated with the first subscription event topic indicated by the definition file, the first event message.