Context-Aware Data Backup and Restore Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup and restore systems rely solely on time and date stamps for archiving data, making it inefficient and time-consuming for users to retrieve specific versions of files, as they often struggle to remember when a particular version was backed up.

Innovation Solution

An architecture that employs event-oriented contextual indicia to facilitate the retrieval of desired data file versions by logging contextual event descriptions from sources like social networking services and calendar applications, providing users with memorable events associated with data backups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If backup systems use only time and date stamps for archiving data, then the backup process is simple and automated, but users cannot efficiently retrieve specific file versions without manually reviewing archives

Engineering Contradiction:
Improveease of data retrievalVSAvoidtime to locate specific version
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent introduces contextual event descriptions as an intermediary between the backup system and users. These descriptions, sourced from external applications like calendar apps and social networking services, serve as mediators that connect users to specific backup versions without requiring users to manually review time stamps or archive contents. The contextual events act as a bridge that enables efficient retrieval while maintaining automated backup processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If users must remember the time and date of backups to retrieve specific versions, then the backup system requires minimal additional components, but the user experience becomes difficult and inefficient

Engineering Contradiction:
Improveease of version identificationVSAvoidmemory burden on user
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system performs preliminary action by proactively obtaining and storing contextual event descriptions associated with each backup operation before users need to retrieve data. By pre-fetching relevant contextual information from external sources and linking it to backup versions, the system eliminates the need for users to remember time and date information, as the contextual events are prepared and available in advance for user reference.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If the system integrates multiple external sources for contextual information, then users gain better contextual awareness of backups, but the system complexity and data integration requirements increase

Engineering Contradiction:
Improvecontextual information availabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a multi-functional architecture where a single backup system integrates multiple external data sources (calendar applications, social networking services, and other applications) through a unified interface. The system can obtain contextual event descriptions from various sources using similar processes, making the system versatile and reducing the need for separate integration mechanisms for each source, thereby managing complexity while providing rich contextual information.

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

Data Source

PatentUS8818957B2Employing user-context in connection with backup or restore of data
Publication Date: 2014.08.26 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8818957B2 patent drawing
  • US8818957B2 patent drawing
  • US8818957B2 patent drawing

AI summary

The claimed subject matter relates to architectures for facilitating network-accessible or local backup or restore features in a manner that leverages event-oriented contextual information associated with one or more users of the data to be backed up or restored. In particular, a first restore-based architecture can interface with an associated second backup-based architecture that hosts or maintains a backup data store in order to retrieve a version of the data file that is desired by a user. Additionally, the first architecture can obtain a log of contextual event descriptions that can be aggregated by the second architecture or obtained independently from, e.g., a social networking service or a calendar application associated with the user. Thus, in addition to displaying time and date information associated with the desired version, the first architecture can provide the user with a social context of event from the social services feeds to aid the user in distinguishing between multiple versions of the data file.