Multi-System DRM Constraint Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current digital rights management systems cannot effectively impose multi-system constraints for specific permissions, limiting the ability to restrict content export to multiple DRM systems or specify different types of system constraints, such as play or operating system permissions.
Innovation Solution
A method and apparatus for implementing multi-system constraints in digital rights management, where a rights object includes system constraint descriptions for multiple systems of the same or different types, allowing an executing device to parse and compare system information to determine permitted permissions, enabling content to be executed or played only in specified systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single system constraint is used in the prior art, then the DRM system is simple to implement, but it cannot satisfy multi-system constraint requirements for different DRM systems or different types of systems
Solution Approach 1:
The patent segments the system constraint description into multiple independent constraint elements, each representing a specific DRM system or system type. Each constraint element contains separate identification information (such as DRM system version, player type, operating system) that can be independently evaluated. This segmentation allows the rights object to specify multiple distinct system constraints without creating a monolithic complex structure, enabling multi-system support while maintaining manageable complexity through modular constraint definitions.
2Adaptability or versatility
If multiple sub-elements are used to describe a specific system in the prior art, then the system identification is precise, but it cannot support multiple system constraints under a single permission
Solution Approach 1:
The patent divides the constraint description into multiple discrete constraint elements, where each element maintains clear identification information for a specific system. Each element contains structured sub-elements (such as DRM system identification, version, player type, operating system) that preserve precise system identification. The segmentation approach ensures that while multiple systems are supported, each individual constraint remains clearly defined and identifiable, preventing loss of constraint description clarity.
Solution Approach 2:
The patent introduces a new dimensional structure to the rights object by adding a collection dimension that holds multiple constraint elements. This dimensional expansion allows the system to move from a single-flat constraint structure to a multi-dimensional structure where multiple constraint elements coexist under a single permission. Each constraint element maintains its own identification dimension, enabling precise system identification while supporting multiple systems simultaneously without compromising constraint description clarity.
3Reliability
If the DRM system checks multiple system constraints, then the permission control is flexible and reliable, but the checking process requires more computational resources and time
Solution Approach 1:
The patent performs preliminary action by pre-structuring the constraint elements in the rights object with clear identification information and systematic organization. Each constraint element is prepared in advance with defined sub-elements (DRM system ID, version, player type, operating system) that can be quickly matched against the executing device's system information. This preliminary structuring enables efficient comparison operations during runtime, reducing the computational burden and time required for checking multiple system constraints while maintaining high reliability in permission control.
Data Source
AI summary
A method and a terminal device for making multi-system constraint of a specified permission in a digital rights. A rights object related to content object is obtained by an executing device. The specific permission descriptions of the rights object include system constraint descriptions of a plurality of systems of the same type. The executing device obtains a corresponding system information in the device according to the system constraint descriptions and compares the system information in the device with the system information in the system constraint descriptions, so as to judge whether there is any system permitted in system constraint descriptions. If yes, it determines to permit executing the specific permission for the content object; otherwise, it determines not to permit executing said specific permission for the content object.