Data Managing Method for Restricting Invalid Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data management methods cannot restrict data copying based on individual user permissions, leading to invalid data distribution, as they either prohibit copying entirely or allow it uniformly, without considering the order of users in document circulation.
Innovation Solution
A data managing method that inputs data identification information, user identification information, and process identification information, determining if the user is permitted to execute processes by referencing permission data, and forbidding output processes if not permitted, ensuring valid data distribution by specifying user order.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If copying is prohibited uniformly for all users, then data security is improved, but data circulation efficiency deteriorates
Solution Approach 1:
The patent applies local quality by differentiating permission settings for different users rather than applying a uniform prohibition. Each user is assigned specific permission levels (e.g., view-only, copy-allowed, edit-permitted) based on their role and authorization, allowing data security to be maintained while enabling appropriate circulation among authorized users.
Solution Approach 2:
The patent implements dynamic permission management where user access rights can be changed over time. Permission data is updated to reflect changing authorization states, such as when a user's role changes or when data circulation requirements evolve, allowing the system to adapt security and circulation needs dynamically.
2Productivity
If copying is allowed uniformly for all users, then data circulation efficiency is improved, but data security deteriorates
Solution Approach 1:
The patent applies local quality by differentiating permission settings for different users rather than applying a uniform prohibition. Each user is assigned specific permission levels (e.g., view-only, copy-allowed, edit-permitted) based on their role and authorization, allowing data security to be maintained while enabling appropriate circulation among authorized users.
3Reliability
If permission checking is performed for each user, then data security is improved, but system complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-establishing permission data that associates user identification information with process identification information before actual data operations occur. This permission framework is set up in advance, allowing rapid authorization checks during data circulation without adding significant complexity to real-time operations.
Solution Approach 2:
The patent introduces permission data as an intermediary layer between users and data resources. This permission data structure acts as a mediator that simplifies the authorization process by providing a standardized format for storing and checking user permissions, reducing the complexity of direct user-data authorization management.
4Reliability
If uniform copying prohibition is applied, then data security is improved, but adaptability to different user needs deteriorates
Solution Approach 1:
The patent applies local quality by differentiating permission settings for different users rather than applying a uniform prohibition. Each user is assigned specific permission levels (e.g., view-only, copy-allowed, edit-permitted) based on their role and authorization, allowing data security to be maintained while enabling appropriate circulation among authorized users.
Solution Approach 2:
The patent implements universality through a comprehensive permission data structure that can accommodate multiple user roles, data types, and permission levels within a single unified system. This multi-functional permission framework can adapt to various user needs and data circulation scenarios while maintaining consistent security management.
Data Source
AI summary
In order to prevent invalid distribution of data, a data managing method includes the steps of inputting a document, extracting, from the input document, a document No. for identifying the document, receiving the input of a user ID for identifying a user, determining whether or not a process for the input document is permitted for the user identified by the acquired user ID by referring to permission data, and forbidding the execution of output processes for the input data in the case where it has been determined in the determining step that the process is not permitted. The permission data is data which associates, for each document No., user IDs with the process names for identifying processes permitted for the document.