Robot Component Communication Across Subnets via Gateway Agents
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for data communication between robot components in different IP address bands or subnets are inadequate, leading to the inability to reuse existing robot components and requiring redevelopment in different frameworks, and preventing direct communication between components in separate subnets.
Innovation Solution
A method for configuring communication between robot components in different networks using a gateway agent protocol, which includes gateway-to-gateway connection processes, data forwarding, and data pulling, enabling communication through a gateway agent that converts data between robot protocols and web-based protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If robot components are placed in different subnets to achieve high computing performance through cloud computing, then computing performance and functionality are improved, but direct communication between components using robot protocol becomes impossible
Solution Approach 1:
The patent introduces a gateway agent as an intermediary component that bridges robot components in different subnets. The gateway agent receives robot protocol messages from components in one subnet, converts them to appropriate communication formats, and forwards them to target components in other subnets, thereby enabling communication across network boundaries while maintaining the benefits of distributed cloud computing architecture
Solution Approach 2:
The patent segments the robot system into multiple subnets with specific functions (e.g., control subnet, computing subnet, sensor subnet). Each subnet can be independently configured and managed, allowing high-performance computing components to be placed in cloud environments while keeping control components in the local network. The gateway agent acts as the boundary interface between these segmented subnets
2Loss of time
If existing robot components are reused in cloud computing environment, then development time is reduced, but communication compatibility between components in different subnets is lost
Solution Approach 1:
The gateway agent is designed as a universal communication interface that can handle multiple robot protocols and communication formats simultaneously. It provides multi-functional capabilities including message routing, protocol conversion, and data format transformation, allowing existing robot components to be reused across different subnets without modification while maintaining communication compatibility
3Device complexity
If robot components communicate within the same subnet, then communication is simple and direct, but computing performance is limited by local robot capabilities
Solution Approach 1:
The patent extends the communication dimension from local subnet to wide-area network by introducing gateway agents that operate at the network boundary. This allows the system to maintain simple intra-subnet communication while adding inter-subnet communication capabilities through the gateway layer, effectively adding a new dimension to the communication architecture without complicating existing simple communication paths
Data Source
AI summary
An apparatus and method for configuring communication between robot components in different networks are provided. The method includes receiving, from at least one first robot component in a subnet, gateway configuration information for requesting a configuration for communication with a second robot component in an additional subnet, performing a gateway-to-gateway connection process by interworking with a target gateway agent corresponding to a target gateway agent address included in the gateway configuration information, and performing at least one of a data forwarding process corresponding to distribution configuration information included in the gateway configuration information, or a data pulling process corresponding to subscription configuration information included in the gateway configuration information, or a combination thereof through a gateway-to-gateway connection channel.