Microservices Robot Control via API Gateway and WebRTC

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional robot control systems based on monolithic architecture face inefficiencies in scalability and real-time control due to their communication methods, particularly when using HTTP, which hinders effective monitoring and control of robots.

Innovation Solution

Implementing a microservices architecture (MSA) that combines HTTP communication for user terminals with WebRTC for real-time control and monitoring, enabling an API gateway to connect authentication, management, and operation servers, and allowing robots to communicate with administrator terminals through WebRTC for enhanced scalability and real-time data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If HTTP communication is used for robot control, then ease of implementation is improved, but real-time control capability deteriorates

Engineering Contradiction:
Improveease of implementationVSAvoidreal-time control capability
Core Design Contradiction:
Ease of manufactureVSSpeed

Solution Approach 1:

The communication system is segmented into two distinct protocols: HTTP for non-real-time operations (authentication, management) and WebRTC for real-time control and monitoring. This segmentation allows each protocol to be optimized for its specific purpose, resolving the contradiction between ease of implementation and real-time capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The API gateway serves as an intermediary that routes different types of communication traffic to appropriate handlers. It mediates between the simplicity of HTTP and the real-time requirements of WebRTC by directing authentication and management requests through HTTP while routing control and monitoring requests through WebRTC.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If monolithic architecture is used, then system simplicity is improved, but scalability and error isolation deteriorate

Engineering Contradiction:
Improvesystem simplicityVSAvoidscalability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system architecture is divided into independent microservices (authentication service, management service, operation service) that can be developed, deployed, and scaled independently. This segmentation improves scalability and error isolation while maintaining system simplicity through standardized communication interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The API gateway provides universal functionality by handling multiple types of requests (authentication, management, control, monitoring) through a single entry point. This multi-functionality maintains system simplicity while enabling specialized services to operate independently.

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

3Device complexity

If monolithic architecture is used, then system simplicity is improved, but error isolation and service independence deteriorate

Engineering Contradiction:
Improvesystem simplicityVSAvoiderror isolation
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system is segmented into independent services where errors in one service (e.g., authentication) do not propagate to others (e.g., control or monitoring). Each service operates independently with its own error handling, improving reliability while maintaining simplicity through the API gateway's unified interface.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11979453B2Microservices architecture based robot control system and method thereof
Publication Date: 2024.05.07 HYUNDAI MOTOR CO LTD
  • US11979453B2 patent drawing
  • US11979453B2 patent drawing
  • US11979453B2 patent drawing

AI summary

A robot control system and a method may be operated in a microservices architecture (MSA)-based control environment. The robot control system includes an application programming interface (API) gateway that connects an authentication server for authenticating a robot, a management server for managing the robot, and an operation server for operating the robot in a Hyper Text Transfer Protocol (HTTP) communication method and an administrator terminal that communicates with the robot through WebRTC (Web Real-Time Communication).