Information Processing Apparatus Data Integration Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing information processing systems face challenges in keeping shared save data among multiple applications up-to-date without complex operations, often leading to user errors due to outdated or conflicting data.

Innovation Solution

An information processing program and apparatus that store and manage data as both 'first' and 'second' data, allowing for integration and updating of these data sets to ensure they remain current, with features like automatic saving and error handling to prevent data corruption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If save data is shared among multiple applications without integration mechanisms, then data consistency is maintained, but user errors occur due to outdated or conflicting data

Engineering Contradiction:
Improvedata consistencyVSAvoiduser error rate
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an integration management unit as an intermediary that mediates between multiple applications and the shared storage medium. This unit integrates save data from different applications before writing to storage, ensuring data consistency while preventing user errors through centralized control. The intermediary resolves conflicts between applications by coordinating data integration timing and content.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where the integration management unit monitors data integration status and provides updates to applications. This feedback loop ensures that applications are aware of the current state of shared data, allowing them to adjust their operations accordingly and preventing conflicts that would lead to user errors.

Inventive Principle:
Principle #23Feedback

2Loss of information

If save data is updated frequently to maintain current information, then data currency is improved, but system complexity increases due to coordination requirements

Engineering Contradiction:
Improvedata currencyVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The integration management unit serves as a mediator that handles all update operations centrally. Applications communicate their data update needs to this intermediary, which then coordinates the integration and writing processes. This approach maintains data currency through frequent updates while managing system complexity by consolidating coordination logic in a single management unit rather than requiring complex peer-to-peer coordination between applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service mechanisms where the integration management unit automatically detects when data updates are needed and initiates integration processes without requiring manual intervention. The unit monitors data changes, determines integration timing, and executes updates autonomously, reducing the complexity burden on the overall system while maintaining current data.

Inventive Principle:
Principle #25Self-service

3Reliability

If data integration is performed manually to ensure accuracy, then data integrity is maintained, but operation time increases due to confirmation processes

Engineering Contradiction:
Improvedata integrityVSAvoidoperation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The integration management unit performs self-service data integration by automatically detecting when save data needs to be integrated, retrieving the data from applications, and writing it to the storage medium without manual intervention. This automated process maintains data integrity through systematic integration while eliminating the time-consuming confirmation processes that would be required if manual operations were used.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-establishing integration rules and data structures before actual data integration occurs. The integration management unit is pre-configured with knowledge of which applications use which data formats, allowing it to perform rapid, accurate integration without requiring time-consuming verification steps during the actual update process.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If save data structures are simplified for easy management, then ease of operation is improved, but adaptability to different applications decreases

Engineering Contradiction:
Improvedata management easeVSAvoidapplication compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the data management system into distinct functional components: application-specific data structures maintained by individual applications, and a standardized integration format managed by the integration management unit. Each application can use its own optimized data structure for ease of operation, while the integration management unit translates between these different structures and a standardized storage format, thereby maintaining adaptability across different applications without compromising operational simplicity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9072964B2Information processing program and information processing apparatus
Publication Date: 2015.07.07 NINTENDO CO LTD
  • US9072964B2 patent drawing
  • US9072964B2 patent drawing
  • US9072964B2 patent drawing

AI summary

In an information processing apparatus stores, save data shared among first-third applications is stored in a memory for saved data by bringing it into correspondence with the first-third applications as first-third data. A computer integrates the first-third data stored in the memory for saved data within a main memory when the first application is activated, for example, and updates the integration data in accordance with execution of the first application and overwrites the first data and second data stored in the memory for saved data with the updated integration data in response to an automatic saving instruction or a saving instruction by a user at the same time.