Connection Profile Broker for Context-Aware IoT Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge in the IoT arena is the need for IoT systems to be aware of and utilize information from other IoT systems within a specific context, exacerbated by the dynamic nature of IoT devices and systems over their lifetime, and the lack of a single entity managing all devices and systems involved.
Innovation Solution
A system where compliant IoT systems and services are automatically connected by a broker using connection profiles and metadata, allowing the profile broker to discover compatible client and server applications within a context, creating a connection instance that compiles metadata for communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IoT systems use customized integration for each device and system, then compatibility and information exchange capability are improved, but device complexity and integration effort increase significantly
Solution Approach 1:
The patent implements a universal connection profile framework that defines standardized metadata schemas and connection templates applicable across diverse IoT devices and systems. Instead of creating customized integration logic for each device pair, the system uses universal connection profiles that can be instantiated for different device combinations, reducing integration effort while maintaining compatibility.
Solution Approach 2:
The patent introduces a broker as an intermediary component that manages connection profiles and facilitates automatic connection establishment between IoT devices. The broker mediates the interaction between devices by matching connection requests with appropriate profiles, eliminating the need for direct customized integration between each device pair and significantly reducing overall system complexity.
2Ease of operation
If a centralized entity manages all IoT devices and systems, then connection management and information exchange are simplified, but system architecture complexity and deployment difficulty increase
Solution Approach 1:
The patent enables IoT devices to self-register and self-configure by automatically generating metadata and connection instances based on predefined connection profiles. Devices autonomously declare their capabilities and requirements, and the broker automatically matches them with appropriate connection profiles, eliminating the need for manual centralized configuration while maintaining simplified connection management.
Solution Approach 2:
The patent pre-defines connection profiles with metadata schemas and connection templates before devices are deployed. These preliminary configurations include standardized data models, communication protocols, and connection parameters that are prepared in advance, allowing devices to be quickly integrated without requiring complex real-time configuration management.
3Adaptability or versatility
If connection profiles are dynamically created for each device interaction, then connection flexibility and adaptability are improved, but processing time and computational resources increase
Solution Approach 1:
The patent pre-defines connection profiles with metadata schemas, data models, and connection templates before runtime. These profiles are prepared in advance and stored in a repository, allowing the broker to quickly instantiate connections by simply binding device-specific parameters to the pre-configured templates, dramatically reducing processing time while maintaining flexibility.
Solution Approach 2:
The patent creates connection instances by copying and instantiating predefined connection profile templates rather than creating entirely new connection configurations from scratch. The broker replicates the structured metadata and connection parameters from master profiles, adjusting only device-specific identifiers and values, which significantly accelerates the connection establishment process.
4Measurement precision
If metadata schemas are highly specific to each device type, then information exchange precision is improved, but system-wide interoperability and ease of integration decrease
Solution Approach 1:
The patent segments metadata schemas into hierarchical layers: device-type-specific schemas for precise data representation and a universal base schema for common IoT data structures. This segmentation allows each device type to have precise metadata definitions while maintaining compatibility with the universal framework, enabling both precision and interoperability.
Solution Approach 2:
The patent implements a universal base metadata schema that defines common data structures, data types, and communication patterns applicable to all IoT devices. Device-specific metadata extends this universal schema with type-specific properties, creating a multi-functional metadata framework that ensures both precise information exchange for specific devices and broad system-wide interoperability.
Data Source
AI summary
A method of connecting applications over a network can be provided by a connection profile broker that can determine that server metadata included in a server application instance and the client metadata included in a client application instance describe complementary functions and therefore may be appropriate for connection via the connection profile. To further determine this, the connection profile broker can determine whether the client application instance is related to the server application instance by at least one type of relationship that is included in the client scope metadata and further determines whether the server application instance is related to the client application instance by at least one type of relationship that is included in the server scope metadata. The connection profile broker can also be operatively coupled to a firewall, which can request information from the broker to determine whether the connection should be allowed.