Logical Object Metadata Export via Bulk Job Queuing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for migrating logical objects from one storage location to another require numerous API function calls, leading to computing resource overload and reduced migration speed due to the large number of function calls needed to access metadata for each object.

Innovation Solution

A system that simplifies the metadata export process by allowing a single function call to access metadata for multiple logical objects, using an electronic processor to create an export job, store it in a job queue, and execute it when computing resources are available, thereby reducing the load on computing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If numerous API function calls are made to access metadata for each logical object during migration, then complete metadata retrieval is achieved, but computing resource overload occurs and migration speed decreases

Engineering Contradiction:
Improvemetadata retrieval completenessVSAvoidmigration speed
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent merges multiple individual API function calls into a single bulk metadata export operation. Instead of calling an API for each logical object separately, the system performs one consolidated export job that retrieves metadata for multiple logical objects simultaneously, thereby reducing the total number of function calls and preventing computing resource overload while maintaining complete metadata retrieval.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements preliminary action by creating an export job that is queued and executed when computing resources are available. This allows the system to prepare the metadata export operation in advance and schedule it during periods of lower system load, ensuring that metadata is retrieved before migration needs to proceed, while optimizing the timing to avoid resource conflicts.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If numerous API function calls are made to access metadata for each logical object during migration, then complete metadata retrieval is achieved, but computing resource overload occurs

Engineering Contradiction:
Improvemetadata retrieval completenessVSAvoidcomputing resource usage
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent merges multiple individual API function calls into a single bulk metadata export operation. Instead of calling an API for each logical object separately, the system performs one consolidated export job that retrieves metadata for multiple logical objects simultaneously, thereby reducing the total number of function calls and preventing computing resource overload while maintaining complete metadata retrieval.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements a universal metadata export function that can handle multiple logical objects with different metadata types through a single API call. This multi-functional approach allows the system to retrieve various kinds of metadata (files, folders, lists, permissions, etc.) in one operation, reducing the quantity of computing resources consumed compared to making separate calls for each object type.

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

3Productivity

If a single function call is used to access metadata for multiple logical objects, then computing resource usage is reduced, but server-side logic complexity increases

Engineering Contradiction:
Improvemigration speedVSAvoidserver-side logic
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary export job mechanism that acts as a mediator between the simplified single function call and the complex metadata retrieval process. The export job receives the single function call, translates it into appropriate internal operations, manages the bulk metadata export, and returns the results. This intermediary layer handles the server-side logic complexity internally while presenting a simple interface to external users, thereby maintaining high migration speed without exposing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of time

If metadata export is performed immediately, then data migration can proceed, but computing resources may be unavailable causing delays

Engineering Contradiction:
Improvemigration timingVSAvoidresource availability
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent implements preliminary action by creating an export job that is queued and executed when computing resources are available. This allows the system to prepare the metadata export operation in advance and schedule it during periods of lower system load, ensuring that metadata is retrieved before migration needs to proceed, while optimizing the timing to avoid resource conflicts.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent employs periodic action by checking for computing resource availability at regular intervals before executing the export job. Instead of attempting immediate execution, the system periodically monitors resource status and initiates the metadata export only when resources are confirmed to be available, thereby balancing timely migration with reliable resource availability.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11327802B2System and method for exporting logical object metadata
Publication Date: 2022.05.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11327802B2 patent drawing
  • US11327802B2 patent drawing
  • US11327802B2 patent drawing

AI summary

Systems and methods for exporting logical object metadata. In one example, the system includes an electronic processor configured to receive a first input from a user. The first input includes a logical object location and at least one metadata export option. The electronic processor is also configured to create an export job based upon the first input. The electronic processor is also configured to store the export job in a job queue, determine when a computing resource is available to execute the export job, and execute the export job when the computing resource is available. The electronic processor is also configured to store a job manifest in a memory location. In one example, the job manifest includes metadata for each logical object located in the logical object location.