Content File Matching via Metadata Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing techniques for managing and identifying content files, especially when shared via social networking services, result in high processing loads due to the need to match entity data between original and shared files, making it impractical to determine if shared content files are the same as their original counterparts.
Innovation Solution
A content control method that narrows down the range of target content files for matching by using attribute information items (meta data) before matching entity information items, allowing for efficient and accurate identification of identical content files by consolidating pre-shared and shared content files based on specified conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If entity data of content files are matched to identify whether shared content files and original content files are the same, then identification accuracy is improved, but processing load increases
Solution Approach 1:
The patent segments the identification process into two stages: first comparing attribute information (metadata such as file size, format, creation date) to filter content files, then comparing entity data only for the filtered subset. This segmentation reduces the number of full entity data comparisons needed while maintaining identification accuracy.
Solution Approach 2:
The patent performs preliminary comparison of attribute information before conducting entity data matching. By pre-filtering content files based on attribute compatibility, the system prepares a reduced set of candidates for the more computationally intensive entity data comparison, thereby reducing overall processing load.
2Reliability
If entity data matching is performed on all content files to ensure accurate identification, then identification reliability is improved, but processing time increases
Solution Approach 1:
The identification process is divided into attribute comparison and entity data comparison stages. The attribute comparison stage quickly filters out incompatible files, ensuring that entity data comparison is only performed on relevant candidates, thus maintaining reliability while reducing time loss.
Solution Approach 2:
Attribute information comparison is performed as a preliminary step before entity data matching. This preliminary filtering ensures that only content files with compatible attributes undergo the time-consuming entity data comparison, preserving identification reliability while minimizing processing time.
3Productivity
If attribute information comparison is used to narrow down matching targets, then processing efficiency is improved, but identification precision may be reduced
Solution Approach 1:
The patent uses attribute information comparison as a first-stage filter to improve processing efficiency, then applies entity data comparison as a second-stage verification to ensure identification precision. This two-stage segmentation allows the system to benefit from both efficiency and precision.
Solution Approach 2:
Attribute comparison serves as a preliminary filtering step that narrows down the candidate set without finalizing identification. The subsequent entity data comparison acts as a precision-ensuring step, confirming that the filtered results maintain high identification accuracy.
Data Source
AI summary
A content control method according to the present disclosure includes: obtaining first content file information including attribute information items each on one of first content files which belong to a first content file group; obtaining second content file information including attribute information items each on one of second content files which belong to a second content file group; narrowing down the first content files, the narrowed-down first content files each having an attribute information item satisfying a condition which is set based on the first content file information and the second content file information; and identifying a first content file and a second content file which are partially or entirely same by matching entity information items each on one of the second content files and entity information items each on one or more of the narrowed-down first content files as matching targets.