Mobile Content Management Apparatus with Segmented Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The lack of standardized metadata standards for mobile content services leads to compatibility issues and poor service quality, as each provider defines their own metadata standards, making it difficult to share information and provide user-specific services.
Innovation Solution
A mobile content management apparatus that stores first meta information for general attributes, second meta information for unique attributes, and third meta information for statistics and linkage relationships, using standardized metadata formats like Dublin Core, MPV, and RSS to manage and provide mobile content effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each mobile content service provider defines their own metadata standards, then they can secure various types of metadata for their specific services, but compatibility issues arise and information sharing becomes difficult
Solution Approach 1:
The metadata is divided into three distinct segments: first metadata for general attributes (Dublin Core), second metadata for unique attributes of each content type (MPV standards), and third metadata for statistics and linkage relationships. This segmentation allows each segment to serve its specific purpose while maintaining overall system compatibility.
Solution Approach 2:
The first metadata using Dublin Core standards provides a universal foundation that can be applied across all mobile content types and service providers, ensuring baseline compatibility while allowing second and third metadata to provide type-specific and service-specific functionality.
2Reliability
If comprehensive metadata standards are established to manage various mobile content attributes, then service quality can be improved, but the complexity of metadata management increases
Solution Approach 1:
By segmenting metadata into three distinct categories with different standards, the system manages complexity through organization. Each segment has a specific purpose and standard, making the overall complex system more manageable and maintainable.
Solution Approach 2:
Different metadata segments use different standards appropriate to their specific needs: Dublin Core for general attributes, MPV for media-specific attributes, and custom standards for statistics and linkages. This local quality approach optimizes each segment for its specific function.
3Reliability
If standardized metadata formats are adopted for mobile content, then compatibility and information sharing improve, but the ability to provide user-specific services and content linkage may be limited
Solution Approach 1:
The three-segment metadata structure allows first metadata to ensure compatibility through standardized Dublin Core, while second and third metadata segments provide the adaptability needed for user-specific services and content linkage through type-specific and relationship-specific attributes.
Solution Approach 2:
The patent merges three different metadata approaches into a unified structure that combines the benefits of standardized formats (compatibility) with customized attributes (adaptability), creating a hybrid solution that achieves both goals simultaneously.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A mobile content management apparatus including: a data storage (120) storing first meta information (MI1) comprising metadata defining general attributes of mobile content, second meta information (MI2) including metadata defining unique attributes of each of the different types of mobile content, and third meta information (MI3) including metadata related to statistics on the mobile content and metadata indicating linkage relationships among the different types of mobile content; and a controller (150) providing a user interface inputting metadata for forming the first through third meta information (MI1,MI2,MI3) so as to register the mobile content and storing the metadata input through the user interface in the data storage (120).