Reverse Proxy Module for Firmware Resource Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Electronic devices with firmware stored in rewritable non-volatile memory, such as residential gateways and smart meters, face challenges in managing access to resources due to limited resources and the complexity of updating firmware for interface changes across multiple devices, especially when different operators need to customize the management interface.

Innovation Solution

Implementing a selective redirection module (reverse proxy) on the device to redirect resource requests between local and remote servers, allowing static resources to be managed remotely, thus reducing the need for firmware updates and simplifying management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware is stored locally in rewritable non-volatile memory for device control, then device autonomy and reliability are improved, but device complexity and difficulty of interface updates increase

Engineering Contradiction:
Improvedevice autonomyVSAvoidfirmware update complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The management interface is segmented into multiple resources distributed between local firmware and remote servers. The reverse proxy module divides incoming requests and redirects appropriate ones to remote resources, allowing interface updates without firmware changes while maintaining device autonomy for core functions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A reverse proxy module is introduced as an intermediary between the local client and resources. This intermediary transparently redirects requests to remote servers for specific resources, decoupling the device firmware from the management interface and simplifying update procedures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If all management interface resources are stored locally in firmware, then access speed and reliability are improved, but adaptability and ease of customization decrease

Engineering Contradiction:
Improveresource access speedVSAvoidinterface customization
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

Management interface resources are segmented into local static resources (stored in firmware for fast access) and remote dynamic resources (hosted on external servers for easy customization). The reverse proxy module intelligently routes requests based on resource type, combining the advantages of both local and remote storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different qualities are assigned to different parts of the management interface. Static resources requiring frequent access remain local in firmware, while customizable resources are hosted remotely. This local differentiation optimizes both access speed and adaptability.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If firmware is updated to change management interface, then interface functionality is improved, but productivity and ease of operation worsen due to complex deployment

Engineering Contradiction:
Improveinterface functionalityVSAvoidupdate deployment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

Customizable management interface resources are extracted from the firmware and hosted on remote servers. This extraction allows operators to update interface functionality by simply modifying remote resources without deploying new firmware versions, dramatically improving update efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system enables self-service updates for management interface resources. Operators can directly modify remote resources to change interface functionality without requiring firmware updates or complex deployment procedures, making the system self-updating for interface components.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If a heterogeneous interface is implemented for different operators managing the same device model, then adaptability is improved, but device complexity and management difficulty increase

Engineering Contradiction:
Improveoperator-specific customizationVSAvoidinterface heterogeneity management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The reverse proxy module serves as an intermediary that handles operator-specific customization transparently. It redirects requests to operator-specific remote resources based on authentication information, allowing different operators to have customized interfaces without increasing device complexity or requiring multiple firmware versions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The device maintains a universal firmware base that can serve multiple operators with different interface requirements. The reverse proxy module adds multi-functionality by routing to different remote resources based on operator identity, allowing one device model to support heterogeneous interfaces without increasing core device complexity.

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

Data Source

PatentUS10536546B2Method for managing access to a set of resources delivered via an electronic device
Publication Date: 2020.01.14 SAGEMCOM ENERGY & TELECOM SAS
  • US10536546B2 patent drawing
  • US10536546B2 patent drawing

AI summary

The present invention concerns the field of the management of access to resources by an electronic device, in particular in the case where this device is controlled by firmware stored in a rewritable non-volatile memory.The invention aims to solve the aforementioned problems by the use of a reverse proxy module on the device that enables locating some of the resources of the management interface on a remote server. Access to these resources causes a redirection of the request to the remote server, the response from which is then transmitted to the local client by the device as if it came directly from the device.