Interworking Service for Cross-Protocol IoT Server Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge of integrating and interoperating multiple IoT platforms and devices with different standards, leading to fragmented data systems and complex device configuration processes, hindering seamless communication and coordinated operations in smart city and home automation scenarios.
Innovation Solution
An Interworking Service entity facilitates device and server discovery, registration, and interoperability across various IoT protocols, providing translation and message forwarding services, along with device configuration support, to enable communication between devices and servers using different SL protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple IoT platforms and devices with different standards are integrated, then device functionality and service capability are improved, but system complexity and configuration difficulty increase
Solution Approach 1:
The patent introduces an interworking service entity that acts as an intermediary between devices using different SL protocols. This entity receives requests from devices, translates them into appropriate protocols, and forwards them to the target servers, thereby enabling interoperability without directly increasing device complexity.
Solution Approach 2:
The system segments the complexity by separating protocol translation functionality into a dedicated interworking service entity, distinct from the devices and servers. This allows each component to remain simple while the overall system achieves high adaptability through the specialized intermediary component.
2Adaptability or versatility
If protocol translation and message forwarding services are implemented, then communication compatibility is improved, but processing overhead and service complexity increase
Solution Approach 1:
The interworking service entity is designed to handle multiple SL protocols simultaneously, providing universal protocol translation capabilities. It can translate between different protocols (e.g., CoAP to HTTP, MQTT to REST) using a common internal representation, reducing the need for separate translation mechanisms for each protocol pair.
Solution Approach 2:
The system uses data repositories to store standardized device information and server information in a common format. This copying mechanism allows the interworking entity to work with standardized representations rather than dealing with each protocol's native format directly, simplifying the translation process.
3Adaptability or versatility
If dynamic configuration and device registration services are provided, then system flexibility is improved, but data management complexity and processing time increase
Solution Approach 1:
Devices and servers perform preliminary registration with the interworking service entity, providing their capabilities, supported protocols, and service information in advance. This pre-registration allows the system to quickly match devices with appropriate servers without extensive real-time processing when communication is needed.
Solution Approach 2:
The interworking service entity maintains data repositories that store device information and server information, which are continuously updated based on registration and discovery requests. This feedback mechanism ensures that the system has current information about available services and devices, enabling efficient matching without repeated complex queries.
Data Source
AI summary
An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.