Microservice Framework for Embedded Service Configuration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Optical communication systems face challenges in configuring services in resource-constrained environments, requiring recompilation of firmware or software for each configuration change, which is resource-intensive and time-consuming.

Innovation Solution

A network element comprising an embedded device with a microservice framework, including a core framework microservice, device microservice, and hardware entity microservice, allowing for loosely coupled service management and configuration without the need for extensive recompilation, using a system with processors and non-transitory computer-readable media to execute instructions for managing distributed microservices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If traditional firmware recompilation methods are used for configuration changes, then configuration accuracy is achieved, but productivity deteriorates due to resource-intensive and time-consuming processes

Engineering Contradiction:

Improveconfiguration accuracyVSAvoidconfiguration speed

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The system segments the configuration process into independent microservices that can be individually deployed and managed. Each microservice represents a discrete functional unit that can be configured, updated, and scaled independently, eliminating the need to recompile entire firmware images for minor configuration changes.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The configuration system transitions from static firmware compilation to dynamic service deployment. Configuration changes are applied at runtime through service instantiation and parameter adjustment rather than requiring pre-compilation, enabling flexible and rapid configuration updates without resource-intensive build processes.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If firmware recompilation is performed for each configuration change, then service configuration is achieved, but loss of time increases due to lengthy execution processes

Engineering Contradiction:

Improveservice configuration capabilityVSAvoidconfiguration execution time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary configuration setup through service templates and predefined parameters. Common configuration patterns are pre-configured in the microservice framework, allowing rapid instantiation and deployment without time-consuming compilation processes while maintaining adaptability for custom requirements.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Configuration changes are implemented through parameter modification of existing microservices rather than structural firmware changes. The system allows dynamic adjustment of service parameters, environment variables, and configuration files at runtime, enabling flexible service configuration without time-intensive recompilation cycles.

Inventive Principle:

Principle #35Parameter changes

3Manufacturing precision

If extensive recompilation is required for configuration changes, then configuration completeness is achieved, but use of energy increases due to resource-intensive processes

Engineering Contradiction:

Improveconfiguration completenessVSAvoidcomputational resource consumption

Core Design Contradiction:

Manufacturing precisionVSUse of energy by moving object

Solution Approach 1:

The system uses service configuration copies and templates to replicate proven configurations across multiple instances. Instead of recompiling firmware for each new service, the framework allows rapid cloning and customization of existing service configurations, maintaining configuration completeness while minimizing computational resource consumption.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The microservice framework provides universal configuration capabilities that can be applied across different service types and contexts. A single configurable framework handles diverse service requirements through parameterization and composition, eliminating the need for separate compilation processes for each service while ensuring configuration completeness.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11683227B2Streaming and config for event driven microservice architecture for embedded services

Publication Date: 2023.06.20 INFINERA CORP

AI summary

A network element is herein disclosed. The network element comprises an embedded device having one or more property affecting a function of the embedded device and one or more status; a first computing system having a first processor and a first memory, the first memory being a first non-transitory computer-readable medium storing a device microservice and a hardware entity microservice, the hardware entity microservice in communication with the embedded device; a second computing system having a second processor and a second memory, the second memory being a second non-transitory computer-readable medium storing a core framework microservice; and a communication device in communication with the first computing system and the second computing system.