Gateway Device for Multi-Interface Protocol Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The development of communication software for client devices to access different communication interfaces is complex and inefficient, requiring knowledge of various interface protocols and leading to increased development time and reduced efficiency.

Innovation Solution

A device comprising a client managing unit, a remote device managing unit, and an interface protocol processing unit that determines the interface protocol for a given remote device and adds a header to data packets for transmission through the appropriate interface controller, allowing simultaneous connection to multiple interfaces without requiring knowledge of specific protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If communication software is developed according to different communication interfaces, then client devices can access multiple remote devices through different interfaces, but the development process becomes complicated and inefficient

Engineering Contradiction:
Improveability to access multiple communication interfacesVSAvoidcomplexity of communication software development
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a gateway device as an intermediary between client devices and multiple remote devices. The gateway maintains a mapping relationship between service access point identifiers and remote device addresses, translating uniform client requests into interface-specific communication protocols. This mediator approach allows client devices to access multiple interfaces without needing to know the underlying protocol differences, thus maintaining adaptability while reducing development complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway device provides universal access functionality by implementing a unified service access mechanism that works across multiple different communication interfaces. Instead of requiring separate software implementations for each interface, the gateway handles protocol-specific operations centrally, allowing a single universal client application to access various remote devices through different interfaces (such as PLC and Zigbee) using the same service access point identifier.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If client devices package data and addresses into protocol-specific packets for each interface controller, then communication can be established through different interfaces, but development time increases and efficiency decreases

Engineering Contradiction:
Improvecommunication reliability through protocol complianceVSAvoiddevelopment time for communication software
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The gateway device performs preliminary actions by pre-establishing and maintaining a mapping database that associates service access point identifiers with specific remote device addresses and interface protocols. Before actual communication occurs, the gateway has already prepared the protocol-specific packaging and addressing rules. When a client sends a uniform request, the gateway retrieves the pre-configured protocol information and performs the protocol-specific packet formatting in advance, ensuring reliable protocol compliance without requiring the client to spend time on protocol-specific development.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The gateway device provides self-service functionality by automatically determining which interface protocol to use and autonomously packaging data into the appropriate protocol-specific format. The gateway examines the service access point identifier, automatically looks up the corresponding remote device and interface protocol in its mapping database, and handles the protocol conversion without external intervention. This self-service approach ensures protocol compliance while eliminating the need for clients to invest time in learning and implementing multiple protocol specifications.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If multiple interface controllers are used to connect to different remote devices, then communication versatility is improved, but the interface protocol processing complexity increases

Engineering Contradiction:
Improveability to connect to multiple interfacesVSAvoidcomplexity of interface protocol processing
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple interface protocol processing capabilities into a single gateway device. Instead of distributing protocol processing complexity across multiple client devices or controllers, the gateway consolidates all protocol-specific operations in one central location. The gateway maintains a unified mapping database that manages relationships between service access point identifiers and multiple remote devices across different interfaces, combining what would otherwise be separate protocol handling functions into a single integrated system that reduces overall processing complexity.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9385968B2Methods and devices for connecting to multiple interfaces
Publication Date: 2016.07.05 DELTA ELECTRONICS INC(CN)
  • US9385968B2 patent drawing
  • US9385968B2 patent drawing
  • US9385968B2 patent drawing

AI summary

Methods and devices for connecting to multiple interfaces are provided. The method includes: receiving, by a client managing unit, a first data and a connection request transmitted from a first client device, wherein the connection request is used to request to connect to a first remote device; determining, by a remote device managing unit, an interface protocol of an interface controller of the first remote device according to the connection request, and transmitting the first data to an interface protocol processing unit corresponding to the interface protocol; and adding, by the interface protocol processing unit, a header corresponding to the interface controller of the first remote device to the first data and transmitting the first data adding the header to the first remote device through the interface controller.