Data Storage System Status Update via Merge Logic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for updating system status in data storage systems are inefficient, leading to performance issues and scalability problems due to the need to rebuild entire new subsystems after each poll, even when only a few objects have changed, which consumes resources and renders management systems unusable as the number of objects increases.

Innovation Solution

A method that updates system status by applying merge logic to create new software objects only for changed components, reusing existing update mechanisms to maintain array status efficiently and scalably, thus reducing resource consumption and improving performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional methods rebuild entire new subsystems after each poll, then system status is updated completely, but resource consumption increases and scalability deteriorates

Engineering Contradiction:
Improvesystem status accuracyVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the subsystem update process by identifying and updating only the specific software objects that have changed (newly inserted, modified, or deleted objects) rather than rebuilding the entire subsystem. This is achieved through comparing object identifiers and paths between the old and new full models, isolating changed components for targeted updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by performing only the necessary update operations on changed software objects rather than executing a complete subsystem rebuild. The merge logic selectively applies updates based on change detection, performing minimal necessary actions to maintain system status accuracy while conserving resources.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If conventional methods rebuild entire new subsystems after each poll, then system status is maintained, but the management system becomes unusable as the number of objects increases

Engineering Contradiction:
Improvesystem status maintenanceVSAvoidscalability
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the large-scale subsystem update task into smaller, manageable segments by processing only changed software objects. This segmentation approach prevents the management system from being overwhelmed by the complexity of rebuilding entire subsystems, enabling scalable operation even with large numbers of objects.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

By performing partial updates only on changed objects rather than complete subsystem rebuilds, the patent reduces the operational complexity and computational burden on the management system. This partial action approach maintains system status reliability while preventing the system from becoming unusable as object counts increase.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If merge logic updates only changed components, then resource consumption is reduced, but the update mechanism becomes more complex

Engineering Contradiction:
Improveresource efficiencyVSAvoidupdate mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent prepares for efficient selective updates by pre-establishing the full model structure and object identifier system before updates occur. This preliminary setup enables the merge logic to quickly identify changed components through comparison without requiring complex real-time analysis during the update process itself.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying of the full model structure as a template for updates. By maintaining a complete reference model and comparing against it, the system can identify changes and apply updates to specific copied objects without reconstructing the entire system, simplifying the update mechanism while improving resource efficiency.

Inventive Principle:
Principle #26Copying

4Stability of the object's composition

If entire subsystems are rebuilt, then consistency is ensured, but performance deteriorates due to resource consumption

Engineering Contradiction:
Improvesystem consistencyVSAvoidupdate performance
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent segments the consistency verification process to apply only to changed software objects rather than the entire subsystem. This targeted approach maintains system consistency where changes occur while avoiding the performance penalty of verifying unchanged components, thus improving update performance while preserving consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial verification and update actions only to changed objects, performing the minimum necessary operations to maintain consistency. This partial action approach ensures system consistency is preserved in affected areas while avoiding the performance deterioration associated with complete subsystem rebuilds.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8732688B1Updating system status
Publication Date: 2014.05.20 EMC IP HLDG CO LLC
  • US8732688B1 patent drawing
  • US8732688B1 patent drawing
  • US8732688B1 patent drawing

AI summary

A method is used in updating system status. Updated information is received for a managed object in a data storage system. From the updated information and an existing software object having other information about the managed object, a new software object is derived representing the managed object. Merge logic is applied to update the existing software object based on the new software object. The merge logic being capable of updating an existing full model of the data storage system from a new full model of the data storage system.