Dual-Mode Gateway for Legacy Peripheral Protocol Reverse Engineering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in configuring cloud-based enterprise applications to communicate with legacy peripheral devices, due to lack of documentation and varying communication protocols, leading to potential errors and downtime during migration.

Innovation Solution

A dual-mode local gateway is introduced, capable of operating in inspection and relay modes. In inspection mode, the gateway establishes connections with both the local enterprise application and peripheral devices, logs and forwards data, facilitating reverse-engineering of communication protocols. In relay mode, it relays data between peripheral devices and a cloud-based server, enabling seamless migration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If cloud-based enterprise application is used to control peripheral devices, then facility management is relieved of configuration and management responsibilities, but configuration settings become difficult to generate due to unavailable or incomplete documentation

Engineering Contradiction:
Improvefacility management responsibilityVSAvoidconfiguration generation difficulty
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

A gateway device is introduced as an intermediary between the cloud-based enterprise application and peripheral devices. The gateway captures communication data between local applications and peripheral devices, logs the interaction patterns, and provides this information to the cloud application to enable proper configuration without requiring facility management to manually research communication protocols

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary data capture and logging of communication interactions between local applications and peripheral devices before cloud migration. This preliminary action records the communication patterns, protocols, and data formats used, which are then used to pre-configure the cloud application, eliminating the need for complex configuration work after deployment

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If cloud-based enterprise application is deployed, then remote hosting is achieved, but configuration errors may cause downtime during migration

Engineering Contradiction:
Improveremote hosting capabilityVSAvoiddowntime during migration
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The gateway captures and logs communication data in advance before cloud deployment, storing the interaction patterns, protocols, and data formats. This preliminary documentation allows the cloud application to be pre-configured with accurate settings, reducing the risk of configuration errors and subsequent downtime during migration

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the gateway continuously monitors and logs communication data between local applications and peripheral devices. This feedback information is used to verify and refine the cloud application configuration, ensuring reliability and minimizing downtime during the transition to remote hosting

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12282437B2Dual-mode local gateway for legacy peripheral devices
Publication Date: 2025.04.22 AMADEUS SAS
  • US12282437B2 patent drawing
  • US12282437B2 patent drawing
  • US12282437B2 patent drawing

AI summary

A method includes: obtaining, at a gateway, configuration data defining communication parameters for a peripheral device; receiving, at the gateway, a command to activate an inspection operating mode and deactivate a relay operating mode; in response to activating the inspection operating mode: establishing, with a local enterprise application, a first connection according to the communication parameters for the peripheral device; establishing a second connection with the peripheral device according to the communication parameters; for data received via each one of the first and second connections, (i) logging the data, and (ii) transmitting the data over the other of the first and second connections.