Micro-Adapter Architecture for Cloud Native IoT Gateway

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing IoT device gateway architectures struggle to efficiently manage diverse IoT devices with varying functionalities and mobility across different domains, particularly in telematics where IoT devices are mobile and lack collaboration within the same geolocation, requiring effective protocol translation and event analysis for applications like efficient routing.

Innovation Solution

A micro-adapter architecture for a cloud-native device gateway service is introduced, comprising an application layer, device layer, and transport layer, with distributed microservices that provide bounded contexts and support diverse IoT domains through protocol transformation, authentication, and traffic isolation, enabling efficient communication and event processing across different IoT devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a traditional IoT device gateway architecture is used to manage diverse IoT devices, then the system can provide basic protocol translation and device connectivity, but it struggles to efficiently manage devices with varying functionalities and mobility across different domains

Engineering Contradiction:

Improveability to manage diverse IoT devices with varying functionalities and mobilityVSAvoidarchitecture complexity for managing diverse device types and protocols

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The gateway architecture is segmented into distinct layers: a transport layer handling communication protocols and device layer handling device-specific functionalities. This segmentation allows each layer to independently manage its responsibilities, improving adaptability to diverse devices without increasing overall system complexity

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The transport layer is designed as a universal component that handles multiple communication protocols and device types through standardized interfaces. This multi-functionality allows the same transport layer infrastructure to support various device functionalities and mobility patterns across different domains

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If protocol translation is implemented for multiple IoT devices operating in different domains, then communication compatibility is improved, but the complexity of managing different protocols and translation rules increases

Engineering Contradiction:

Improveprotocol translation capability across different IoT domainsVSAvoidcomplexity of protocol translation and event processing

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Protocol translation is segmented into the transport layer, which handles protocol-specific logic and translation rules, while the device layer handles domain-specific event processing. This separation reduces complexity by confining protocol complexity to a dedicated layer with standardized interfaces

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The transport layer acts as an intermediary between diverse IoT devices and the application layer. It provides standardized translation and adaptation mechanisms that mediate between different protocols and the uniform interface expected by upper layers, reducing overall system complexity

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the gateway provides comprehensive device management and protocol translation, then device connectivity and functionality are enhanced, but the system may not efficiently handle mobile devices lacking collaboration within the same geolocation

Engineering Contradiction:

Improvesupport for mobile IoT devices across different geolocationsVSAvoidefficiency of event processing and routing for mobile devices

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

Event processing is segmented into domain-specific handlers in the device layer that can efficiently process events according to domain rules, rather than a monolithic processing system. This allows optimized handling of mobile devices in different domains without compromising overall efficiency

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The architecture allows each domain to have its own event processing logic and collaboration rules tailored to local requirements. Mobile devices in different geolocations can be handled with domain-specific optimizations, improving overall productivity while maintaining adaptability

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS11444810B2Micro-adapter architecture for cloud native gateway device

Publication Date: 2022.09.13 VERIZON PATENT & LICENSING INC

AI summary

A method, a device, and a non-transitory storage medium are described in which a micro-adapter architecture for a device gateway service is provided. The micro-adapter architecture for a device gateway service may be included in a cloud native backend gateway. The cloud native backend gateway may include a set of adapters that are logically grouped in layers for providing device gateway services. The device gateway services may include an application layer, a device layer, and a transport layer. The device gateway services may include bounded contexts based on rules that define the application layer, the device layer, and the transport layer. The device gateway services may be microservices that are distributed within the defined layers.