Bridge Node Bus Interface for Open System Data Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In open system architectures, sub-system providers face challenges such as sharing proprietary intellectual property, difficulty in characterizing standard implementations, and lack of control over integration controls, as they must adhere to a common open standard interface that may not be compatible with all sub-systems.
Innovation Solution
A method and system that utilize a common bus as a shared transport medium, with bridge nodes that communicate through the bus, allowing sub-systems to interface using standard messages or signals while maintaining control over proprietary data and allowing the system owner to enforce integration controls, thereby protecting proprietary data and facilitating integration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sub-system providers share proprietary implementation instructions to comply with open standard interface requirements, then system integration and compliance checking are improved, but proprietary intellectual property is exposed and security is compromised
Solution Approach 1:
The patent introduces a bus interface as an intermediary component that mediates between sub-systems. The bus interface receives data sharing requests, applies filtering based on implementation instructions, and selectively transmits data. This allows compliance checking without direct exposure of proprietary implementation details, as the bus interface acts as a controlled intermediary that enforces access rules.
2Adaptability or versatility
If all sub-systems use the same Open SI implementation and underlying transport, then integration compatibility is improved, but device complexity increases and provider flexibility is reduced
Solution Approach 1:
The patent segments the system into distinct functional layers: sub-systems with their own proprietary implementations, a standardized bus interface layer for communication, and filtering logic for access control. This segmentation allows each sub-system to maintain its own implementation complexity independently while achieving overall compatibility through the standardized interface layer.
Solution Approach 2:
The patent applies local quality by allowing different sub-systems to have different implementation characteristics locally, while the bus interface provides a consistent standardized interface. Each sub-system can optimize its local implementation for its specific function without requiring all sub-systems to use identical implementations, thus reducing overall device complexity while maintaining compatibility.
3Adaptability or versatility
If sub-system providers develop their own Open SI implementations, then provider independence and innovation are improved, but system integration control and standardization are compromised
Solution Approach 1:
The bus interface serves as a mediator that enables provider independence while maintaining integration control. Providers can develop their own implementations that communicate through the standardized bus interface, which enforces integration rules and filtering criteria. This intermediary approach allows innovation at the sub-system level while maintaining standardized control at the interface level.
Data Source
AI summary
Protection and integration of proprietary data in an open system architecture, which includes at least one sub-system, and which must comply with an open standard interface mandated by the system owner. The open standard interface defines the set of messages or signals which may be exchanged by sub-system components. The sub-system provider computer is granted a bridge node to instantiate within their controlled sub-system boundary. The bridge node communicates with the sub-system components via the interchangeable open standard interface and relays messages or signals to other sub-system bridge nodes through a shared common bus. The sub-system provider may protect their proprietary data in their standard interface implementation from the system owner and/or other sub-system providers in the overall system. This is achieved by removing the need for sub-system providers to share their open standard interface implementations with each other in order to integrate together into the overall system.