Storage Resource Identifier Promotion in Job Management GUI

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In data storage system management, long-running jobs that affect multiple storage resources can be difficult to monitor and manage due to the lack of immediate resource identification within the user interface, leading to inefficiencies when issues arise, as administrators must navigate through multiple layers to find affected resources.

Innovation Solution

The solution involves associating storage resources with jobs and batch jobs at higher levels, allowing resource identifiers to be copied from lower-level tasks to job and batch job data objects, enabling their display in user interfaces, such as GUI screens, to facilitate direct navigation and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If administrators use automated tasks and jobs for complex system management operations, then automation and monitoring capabilities are improved, but the ability to quickly identify affected storage resources deteriorates due to the hierarchical abstraction

Engineering Contradiction:
Improveautomation of system management operationsVSAvoidease of identifying affected storage resources
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The patent introduces an intermediary mechanism that bridges the hierarchical abstraction layers. The job-level user interface acts as an intermediary that retrieves and displays storage resource identifiers from task-level data objects, allowing administrators to access detailed resource information without drilling down through multiple hierarchical layers. This intermediary function resolves the contradiction by maintaining automation at lower levels while providing ease of access at higher levels.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new dimension to the hierarchical structure by implementing cross-level information access. Instead of strictly moving from high-level jobs down to low-level tasks to access resource identifiers, the system creates a vertical information channel that allows job-level interfaces to directly access and display task-level storage resource identifiers. This dimensional change enables administrators to view resource details at the job level without navigating through intermediate hierarchical layers.

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

2Reliability

If administrators must drill down through multiple interface layers to find storage resource identifiers, then system security and abstraction are maintained, but time efficiency and productivity deteriorate

Engineering Contradiction:
Improvesystem security and abstraction integrityVSAvoidtime efficiency in locating storage resources
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The job-level user interface serves as an intermediary that safely retrieves storage resource identifiers from task data objects through defined interfaces. This intermediary mechanism maintains system security and abstraction integrity by using controlled access methods while simultaneously improving productivity by presenting resource information at the job level without requiring administrators to navigate through multiple hierarchical layers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback by having the job-level interface query and display storage resource identifiers from task-level data objects. This feedback mechanism provides immediate information about affected resources at the job level, eliminating the need for administrators to drill down through multiple layers, thus improving time efficiency while maintaining system architecture integrity.

Inventive Principle:
Principle #23Feedback

3Device complexity

If storage resource identifiers are kept only at task level, then data structure simplicity is maintained, but user interface efficiency and accessibility deteriorate

Engineering Contradiction:
Improvedata structure simplicityVSAvoiduser interface efficiency
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The job-level user interface acts as an intermediary that retrieves and displays storage resource identifiers from task data objects without modifying the underlying data structure. This approach maintains data structure simplicity at the task level while improving user interface efficiency by providing direct access to resource identifiers at the job level through the intermediary querying mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new dimension to information access by enabling job-level interfaces to query and display task-level storage resource identifiers. This dimensional change allows the system to maintain simple task-level data structures while providing enhanced user interface efficiency through cross-level information retrieval and display capabilities.

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

Data Source

PatentUS10437633B1Data storage system management with promotion of task-level resource identifiers to higher objects
Publication Date: 2019.10.08 EMC IP HLDG CO LLC
  • US10437633B1 patent drawing
  • US10437633B1 patent drawing
  • US10437633B1 patent drawing

AI summary

A data storage system executes a system management component initiating and monitoring a multi-task job affecting a storage resource such as a storage device. Execution includes maintaining a job data object and a set of task data objects for the multi-task job. A task operates upon the storage resource has a respective task data object containing an identifier of the storage resource as a task-affected storage resource. The job data object is used by a job-level function (e.g., job level of a management GUI) and initially lacks the identifier of the storage resource. During execution, the identifier of the storage resource is copied from the task data object to the job data object as an identifier of a job-affected storage resource, which is then used in subsequent performance of the job-level function (e.g., displaying a hyperlink for the storage resource in a job-level screen of the management GUI).