Dual Memory Region Rollback for Pluggable Interface Modules

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Network communication devices face challenges in managing software updates for pluggable interface modules, particularly in ensuring fault tolerance and preventing service disruptions during the upgrade process, as existing methods lack robust rollback mechanisms and comprehensive validation procedures.

Innovation Solution

Implementing a dual memory region configuration in network communication devices, where one region stores an active software image and the other a committed version, allowing for a two-phase upgrade process that validates and activates new software images while ensuring rollback to a previous version if the new image fails, thereby maintaining network stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single memory region is used to store software images, then device complexity is reduced, but reliability deteriorates due to inability to rollback on failure

Engineering Contradiction:

Improvefault toleranceVSAvoidmemory region configuration

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The memory is segmented into multiple dedicated regions (first memory region for first software image, second memory region for second software image) allowing independent storage and selection of software versions. This segmentation enables the system to maintain multiple images simultaneously while providing clear separation of concerns for each image, resolving the contradiction between having multiple images for reliability and keeping the structure simple.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary validation of the new software image before activating it. The validation process checks the new image for errors or incompatibilities beforehand, and only if validation passes does the system switch to using the new image. This preliminary action prevents failures from affecting network operations while maintaining the ability to rollback if validation reveals issues.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If software images are updated without validation, then update speed increases, but reliability deteriorates due to potential image failures

Engineering Contradiction:

Improvesoftware image validityVSAvoidupdate validation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system maintains copies of both the old and new software images in separate memory regions simultaneously. This copying approach allows the validation process to work on the new image without affecting the running old image, enabling parallel operations where validation occurs in the background while the system continues operating with the validated image ready for activation.

Inventive Principle:

Principle #26Copying

3Reliability

If the system switches to new software image immediately upon upload, then productivity increases, but reliability deteriorates due to lack of verification

Engineering Contradiction:

Improveoperation verificationVSAvoidsoftware update speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the validation result determines the activation decision. If validation succeeds, the system feedbacks by switching to the new image; if validation fails, the system feedbacks by maintaining the old image and initiating rollback procedures. This feedback loop ensures reliability without unnecessarily delaying productive updates.

Inventive Principle:

Principle #23Feedback

4Reliability

If rollback mechanism is implemented, then reliability improves, but device complexity increases due to additional memory regions and validation logic

Engineering Contradiction:

Improverollback capabilityVSAvoidsoftware image management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system uses parameter changes (switching between different memory regions) to implement rollback functionality. By changing the active memory region pointer or selection parameter from the first region to the second region, the system can quickly rollback between software images without complex reconfiguration procedures, simplifying the overall management despite having multiple images available.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS20240333589A1Software image updating for pluggable device

Publication Date: 2024.10.03 VERIZON PATENT & LICENSING INC

AI summary

An example method includes storing a first software image for a pluggable interface module connected to a network communication device in a first memory region of the network communication device, storing a second software image for the pluggable interface module in a second memory region of the network communication device, programming the pluggable interface module with the first software image from the first memory region of the network communication device responsive to determining the pluggable interface module requires updating, setting a first active indicator for the first software image responsive to validating the programming of the pluggable interface module with the first software image, verifying an operation of the first software image by the pluggable interface module, and responsive to a failure of the verifying the operation of the first software image, programming the pluggable interface module with the second software image from the second memory region.