Digital Rights Management via Flow Code Injection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital rights management methods require different encryption/decryption tools for various file types, causing inconvenience for both users and end-users due to the need for multiple tool installations and usage.
Innovation Solution
A method that encrypts files with flow codes, unique identifiers, authorization locations, and verification information, allowing users to define encryption intensity without changing the encryption/decryption tool, using symmetric cryptography algorithms like RC4 and AES, and generating an authorization document based on file type for decryption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different encryption/decryption tools are used for different file types, then the verification process can be customized for each file type, but the complexity of the system increases and users need to install and manage multiple tools
Solution Approach 1:
The patent applies universality by designing a single encryption/decryption tool that can handle multiple file types through the flow code mechanism. The flow code embedded in the encrypted file header identifies the file type and triggers the appropriate verification process within the same tool, eliminating the need for multiple specialized tools while maintaining customized verification for each file type.
Solution Approach 2:
The patent uses the flow code as an intermediary element that mediates between the encrypted file and the decryption tool. The flow code carries information about the file type and verification requirements, allowing the single decryption tool to automatically adapt its behavior based on the flow code content without requiring multiple specialized tools.
2Adaptability or versatility
If multiple encryption/decryption tools are installed for different file types, then each file type can be processed with appropriate verification, but the ease of operation decreases due to installation and usage complexity
Solution Approach 1:
The patent makes the decryption tool universal by enabling it to process multiple file types through a single interface. The tool automatically reads the flow code in the encrypted file header to determine the file type and applies the corresponding verification process, providing multi-functionality without requiring users to install or switch between multiple specialized tools.
Solution Approach 2:
The decryption tool performs self-service by automatically identifying the file type through the flow code and selecting the appropriate verification process without user intervention. This eliminates the need for users to manually configure or switch between different tools for different file types, significantly improving ease of operation.
3Ease of operation
If a single encryption tool is used for all file types, then the ease of operation improves, but the ability to implement different verification processes for different file types is limited
Solution Approach 1:
The patent applies segmentation by dividing the verification process into multiple discrete verification items that can be selectively applied. Each file type has its own verification requirements encoded in the flow code, and the single decryption tool segments the overall verification task into specific sub-tasks based on the flow code information, enabling differentiated verification without requiring multiple tools.
Solution Approach 2:
The patent makes the verification process dynamic by allowing it to adapt based on the flow code content. The decryption tool dynamically selects and executes different verification processes depending on the file type identified in the flow code, providing versatility and adaptability within a single static tool through dynamic behavior adjustment.
Data Source
AI summary
The present invention discloses a kind of management method for digital rights, wherein, it comprises the following steps: Step S1: the original electronic file is encrypted on the server-side, and in the meantime, the flow code, the file unique identifier, the authorization locations and verification information is injected; Step S2: obtaining flow codes, file identifier, authorization locations and verification information from the encrypted file, and then conducting integrality verification thereon; step S3: After it is verified that there is no error, the related information is sent to the authorization server; S4: after receiving the injection information about the encrypted file, the authorization server conducting integrality verification firstly, then judging the type of encryption file according to the flow code, and generating an authorization file and sending the same according to the type; Step S5: a decryption tool obtaining the authorization file to conducting integrality verification on the authorization information, and then decrypting, parsing, using same under the right control. By means of the above method of the present invention, a user can self-define the file encryption intensity under the condition of no changing or very little changing of an encryption/decryption tool.