Containerized IoT Edge Gateway for Low-Latency Fleet Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current IoT technologies face challenges with latency and complexity in developing services for specific use cases, particularly in vehicle fleet settings, where edge computing requires low-level code interaction with vehicle systems, leading to barriers for innovative developments and error-prone implementations.

Innovation Solution

An adaptable IoT platform with an edge device hosting container-based applications and a middleware API that allows developers to create and deploy applications using simple functions, eliminating the need for complex code, and utilizing containerization for flexible and customizable execution of discrete applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If edge computing is used to process data at a location closer to the vehicle, then data access speed is improved, but service accessibility and backend process availability deteriorate

Engineering Contradiction:
Improvedata access speedVSAvoidservice accessibility
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The system segments services into edge-based container applications for local data processing and cloud-based backend processes for centralized management. This segmentation allows data to be processed quickly at the edge while maintaining access to comprehensive cloud services, resolving the contradiction between fast local access and broad service availability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer that connects edge computing devices with cloud services, enabling seamless interaction between local data processing and remote backend processes. This intermediary facilitates both rapid local response and comprehensive cloud service access, addressing the accessibility limitation of pure edge computing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If developers write low-level code to communicate with vehicle systems, then system control precision is improved, but development complexity and error rate worsen

Engineering Contradiction:
Improvesystem control precisionVSAvoiddevelopment complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent introduces a middleware layer that acts as an intermediary between high-level application logic and low-level vehicle system communication. This middleware handles complex protocols and device-specific details, allowing developers to write simpler code while maintaining precise system control through the intermediary's standardized interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system uses container-based virtualization to create standardized copies of application environments that encapsulate all necessary device drivers and communication protocols. This copying approach allows applications to run with precise system control without developers needing to write complex low-level code, as the container images contain pre-configured communication templates.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20230419745A1Systems and techniques for providing an adaptable and container-based internet of things platform environment
Publication Date: 2023.12.28 MOREY CORP
  • US20230419745A1 patent drawing
  • US20230419745A1 patent drawing
  • US20230419745A1 patent drawing

AI summary

Systems and techniques are disclosed for providing an adaptable Internet of Things platform. A platform edge gateway device hosts containerized applications, in which each containerized application performs a discrete function. The edge gateway device correlates data output from one or more of the containerized applications, which are then transmitted to additional containerized applications for further processing.