Universal Interface Adapter for Cloud Migration via JSON Stitching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized systems and services face challenges in integrating with disparate devices that have non-standardized communications protocols and message specifications, leading to complex and costly serialized communications that hinder migration to cloud-based systems.
Innovation Solution
A system and method that utilize JavaScript Object Notation (JSON) files to standardize interface specifications, creating combinations through stitching to establish cloud-based communications between centralized systems and disparate devices, regardless of their technical specifics, using a universal interface adaptor that consolidates and standardizes GSS interface specifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If serialized hardware connections are used to integrate disparate devices with centralized systems, then device compatibility is achieved, but system complexity and migration costs increase
Solution Approach 1:
The patent introduces an intermediary layer (application server with protocol translation capabilities) that mediates between disparate devices using serial hardware connections and centralized systems. This intermediary translates non-standardized device protocols into standardized communication protocols, enabling compatibility without directly connecting diverse devices to the centralized system, thereby reducing overall system complexity.
Solution Approach 2:
The integration architecture is segmented into distinct layers: device layer, protocol translation layer (application server), and centralized system layer. This segmentation allows each layer to handle specific functions independently, making the system more manageable and reducing the complexity of direct device-to-centralized-system integration.
2Reliability
If serialized hardware connections are used for device integration, then communication reliability is maintained, but cloud migration capability is hindered
Solution Approach 1:
The application server acts as a mediator that decouples the reliability requirements of serial hardware connections from the cloud migration needs. It maintains reliable communication with devices through standardized protocols while simultaneously enabling cloud connectivity through web services and REST APIs, thus supporting both communication reliability and cloud migration capability.
Solution Approach 2:
The patent replaces direct mechanical/physical serial hardware connections with software-based protocol translation and communication abstraction. This substitution allows the system to maintain communication reliability through software protocols while gaining the flexibility needed for cloud migration, eliminating the constraint of physical connection requirements.
3Adaptability or versatility
If vendor-specific interface specifications are supported, then device interoperability is achieved, but integration cost and time increase
Solution Approach 1:
The application server implements universal protocol translation capabilities that can handle multiple vendor-specific interface specifications through a single platform. Instead of requiring separate integration solutions for each vendor, the universal server translates various proprietary protocols into standardized formats, significantly reducing integration time and effort while maintaining broad device interoperability.
Solution Approach 2:
The system changes the parameter of interface specification handling from vendor-specific custom implementations to a standardized protocol translation approach. By parameterizing the translation rules and protocols within the application server, it can adapt to different vendors through configuration rather than custom development, reducing integration time while maintaining interoperability.
Data Source
AI summary
A system, computer program product, and method are presented for integrating centralized systems with disparate devices and non-standardized communications protocols and message specifications. The method includes identifying one or more interface systems for one or more facilities. Each facility includes a centralized computing system. The method also includes capturing one or more interface specifications for the respective interface systems. The method further includes creating one or more JavaScript Object Notation (JSON) files from the interface specifications. Each JSON file includes one or more logical properties associated with the respective interface systems. The method also includes creating one or more JSON file combinations through stitching at least a portion of the one or more JSON files. The method further includes establishing cloud-based communications between the interface systems and the respective centralized system of the facilities through the JSON file combinations.