Epoch-Based MUD Logging for Network Virtualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In network-based virtualization systems, standard MUD logging processes are ineffective due to the inability of intelligent ports or network devices to coordinate and maintain a consistent log across multiple network devices, leading to difficulties in managing and maintaining data integrity and redundancy, especially during mirroring and recovery processes.

Innovation Solution

Implementing a master MUD logger and secondary MUD loggers that communicate to update and synchronize MUD logs across multiple network devices or ports, using epoch-based logging to track modifications and facilitate efficient data recovery without unnecessary data restoration, thereby addressing the coordination and redundancy challenges.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If standard MUD logging is implemented in network-based virtualization systems, then each network device maintains its own log independently, but coordination and data consistency across multiple devices cannot be ensured

Engineering Contradiction:
Improveindependent log maintenanceVSAvoidlog consistency
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

A master MUD logger is introduced as an intermediary component that receives MUD log information from multiple secondary MUD loggers across different network devices. The master logger consolidates and manages the unified MUD log, ensuring consistency and coordination while allowing secondary loggers to maintain their independent logging operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive data mirroring is performed for redundancy, then data integrity is improved, but recovery time and data replication overhead increase

Engineering Contradiction:
Improvedata integrityVSAvoidrecovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and logs only the modified portions of data (MUD log information) rather than replicating entire data sets. By identifying and tracking only the changed segments through MUD logging, the system maintains data integrity for recovery while minimizing unnecessary data replication and reducing recovery time.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing complete data mirroring for all data, the system applies partial action by logging and replicating only the modified portions identified through MUD logging. This reduces the volume of data that needs to be replicated and recovered while still ensuring data integrity for the changed segments.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If MUD log information is maintained across multiple network devices, then data recovery capability is improved, but coordination complexity and system overhead increase

Engineering Contradiction:
Improverecovery capabilityVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a hierarchical dimension to MUD logging by organizing multiple secondary MUD loggers under a single master MUD logger. This hierarchical structure adds a management layer that simplifies coordination across network devices while maintaining distributed logging capability, reducing the complexity of peer-to-peer coordination.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS7953943B2Epoch-based MUD logging
Publication Date: 2011.05.31 CISCO TECHNOLOGY INC
  • US7953943B2 patent drawing
  • US7953943B2 patent drawing
  • US7953943B2 patent drawing

AI summary

In one embodiment, a MUD logger receives a notification from another MUD logger maintaining another MUD log for a volume, the notification indicating one or more modifications to be made to a MUD log maintained by the MUD logger receiving the notification, wherein the MUD log includes information for one or more epochs, wherein the information for each of the epochs indicates a set of one or more regions of the volume that have been modified during the corresponding epoch. The MUD logger updates the MUD log associated with the volume, wherein updating the MUD log is performed in response to the notification.