Automated Data Uploader Module for Secure System Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Extracting user and system data from hundreds or thousands of computers in data centers is a difficult, time-consuming, and inefficient process, especially when data needs to be analyzed by service providers or owners across large geographical areas.

Innovation Solution

An automated data uploader module is installed on or accessible by each computing system to read and export user and system data to a destination storage repository, where it can be transformed (e.g., scrubbed of personally identifiable information) and analyzed, with the ability to store and export data to other destinations as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual data extraction is performed from hundreds or thousands of computers, then data can be obtained for analysis, but the process becomes difficult, time-consuming and inefficient

Engineering Contradiction:
Improvedata extraction efficiencyVSAvoidtime required for data extraction
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables computers to automatically upload their own data to centralized storage repositories without requiring manual intervention. Each computer acts as its own data extraction agent, continuously or periodically uploading user data and system data to the designated storage location, thereby eliminating the need for manual data collection from hundreds or thousands of machines.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If data is extracted and stored in centralized repositories, then data analysis capability is improved, but data security and privacy protection become more challenging

Engineering Contradiction:
Improvedata analysis capabilityVSAvoiddata security risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system segments data by creating separate, dedicated storage repositories for different organizations or entities. Each organization has its own isolated storage location where only its designated computers can upload data. This segmentation ensures that while data is centralized for analysis purposes, security and privacy are maintained through strict access controls and organizational boundaries.

Inventive Principle:
Principle #1Segmentation

3Productivity

If automated data upload modules are installed on each computing system, then data transfer efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoidsystem deployment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The data uploader module is designed as a universal, multi-functional component that can be deployed across different operating systems and computer configurations. The module handles multiple tasks including data collection, data formatting, authentication, and upload to various storage repositories, thereby simplifying the overall system architecture despite the distributed nature of the deployment.

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

Data Source

PatentUS11418592B2Uploading user and system data from a source location to a destination location
Publication Date: 2022.08.16 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11418592B2 patent drawing
  • US11418592B2 patent drawing
  • US11418592B2 patent drawing

AI summary

Automated uploading of user and system data from one or more source computing systems to one or more destination storage repositories is provided. A data uploader module is installed on each computing system or is accessible by each computing system from which user and/or system data may need to be exported to a destination repository. Upon command, a data uploader module reads desired user data or system data from the computing system. The read data is transformed, if required, and the data is then exported to a destination storage repository. The exported data may be stored and analyzed at the destination storage repository from which it may be subsequently exported to other destinations, including back to the source computing system from which it was originally extracted.