Control Server Access Logic for Version-Specific File Permissions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems fail to manage access control considering the time axis for files in a storage system, leading to issues where users cannot view the non-updated version of a file after it has been updated.
Innovation Solution
A control server and data sharing system that utilizes a distributed ledger to manage viewing permissions separately for different versions of a file by using a combination of file and version identifiers, allowing the system to check and enforce permissions based on these identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If a file is updated in a distributed storage system, then the file content is improved/updated, but the user cannot view the non-updated version of the file anymore
Solution Approach 1:
The patent segments the permission information by creating a separate permission record for each file version. The distributed ledger stores permission information that includes both file identifiers and version identifiers, allowing independent permission management for each version. This segmentation enables users to have different permissions for different versions of the same file, resolving the contradiction between maintaining file updates and preserving access to historical versions.
Solution Approach 2:
The patent adds a version dimension to the permission control system. Instead of managing permissions only at the file level, the system now manages permissions at the file-version level by incorporating version identifiers into the permission information stored in the distributed ledger. This dimensional expansion allows the system to track and control access to specific versions while maintaining the ability to update files.
2Reliability
If permission information is managed for each file version, then viewing permission control is improved, but the system complexity increases
Solution Approach 1:
The patent employs the existing distributed ledger system to serve multiple functions: it continues to maintain file permission information while simultaneously managing version-specific permission control. The same ledger infrastructure that tracks user permissions for files is extended to also track permissions for specific versions, eliminating the need for separate complex version control systems and reducing overall system complexity.
Solution Approach 2:
The patent copies the permission information management approach from the distributed ledger system and applies it to version control. By replicating the permission tracking mechanism used for files and adapting it to work with file versions (by including version identifiers), the system achieves reliable version-specific permission control without building an entirely new complex system from scratch.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Upon receiving a usage request that includes a file identifier and a version identifier from a user terminal 20, a control server 10 transmits a file request that is based on the usage request to a file management system, and transmits a permission information request that is based on the usage request to a distributed ledger system. Upon receiving the file request, the file management system acquires the file that corresponds to the combination of the file identifier and the version identifier and transmits the file to the control server 10. Upon receiving the permission information request, the distributed ledger system acquires permission information that corresponds to the combination of the file identifier and the version identifier from a distributed ledger, and transmits the permission information to the control server 10. The control server 10 transmits the file to the user terminal 20 if the user of the user terminal has viewing permission based on the permission information.