Intermediate Object Serialization for Type-Independent Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data serialization techniques face challenges in handling changes to the type of an object during application program development, making it difficult to reuse serialized data effectively.

Innovation Solution

A development program that generates intermediate objects based on type definitions, allowing for independent storage and manipulation of asset data in a format independent of the original object's type, using additional codes for serialization and deserialization processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the type of the object is changed during application program development, then the application program can be improved or updated, but the previously written-out serialized data cannot be used again

Engineering Contradiction:
Improveadaptability to type changesVSAvoidreusability of serialized data
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary conversion module that translates between different object types during serialization and deserialization processes. This intermediary mechanism allows the system to handle type changes while maintaining data reusability, as the conversion module can adapt data from one type to another without losing the ability to reuse previously serialized data.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent employs parameter changes by modifying type identification parameters and type mapping relationships during serialization. By changing how types are identified and mapped rather than the fundamental data structure, the system can accommodate type changes in the application program while preserving the reusability of serialized data through updated type parameter mappings.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If serialization processing is made independent of object type changes, then data reusability is improved, but the complexity of the serialization system increases

Engineering Contradiction:
Improvereusability of serialized dataVSAvoidcomplexity of serialization system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal serialization framework that can handle multiple object types through a common interface and type mapping mechanism. This universal approach allows the same serialization system to work with different types without requiring type-specific serialization logic, thereby achieving data reusability across type changes while managing complexity through standardization.

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

Solution Approach 2:

The patent performs preliminary type registration and mapping setup before actual serialization operations. By pre-configuring type relationships and conversion rules, the system reduces the complexity of handling type changes during runtime, as the framework is already prepared to manage type independence and data reusability through pre-established mappings.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If an intermediate object is introduced for data storage, then flexibility in data manipulation is improved, but the number of processing steps increases

Engineering Contradiction:
Improveflexibility in data manipulationVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts the data storage function into a separate intermediate object structure that is independent of the original object type. This extraction allows the intermediate object to store data in a standardized format that can be manipulated flexibly without being constrained by the original object's type structure, achieving flexibility while the automated conversion process minimizes the time penalty of the additional processing step.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a copied representation of the original object's data in the intermediate object structure during serialization. This copying approach allows flexible manipulation of the copied data without affecting the original object, and since the copying follows a standardized template, the processing overhead is minimized while achieving the desired flexibility in data manipulation.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20240012625A1Non-transitory computer-readable storage medium with executable development program stored thereon, information processing system, information processing apparatus, and information processing method
Publication Date: 2024.01.11 NINTENDO CO LTD
  • US20240012625A1 patent drawing
  • US20240012625A1 patent drawing
  • US20240012625A1 patent drawing

AI summary

A development program for development of an application program with a programming language in which an object is generated based on a type is provided. The development program includes instructions for identifying a type definition in a source code of the application program and instructions for generating a first code that generates an intermediate object for asset data corresponding to each of objects generated based on the identified type definition and adding the generated first code to the source code of the application program. The intermediate object is stored as the asset data.