Applying OMA DRM Permission Model to Java MIDP Applications
Solution Overview
Problem
Current OMA DRM technology is not used for protecting Java MIDP applications, lacking a system and method to apply the OMA DRM permission model, which is essential for selecting and enforcing permissions for MIDlet applications.
Innovation Solution
Implementing the OMA DRM permission model by applying the 'execute' permission to MIDlets and using constraints to enforce permission enforcement, ensuring that MIDlets are not launched if execution rights are invalid and are closed if they expire while running, with user notification and the option to request new rights.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If OMA DRM permission model is applied to MIDlets, then security and control of digital rights is improved, but system complexity increases due to permission checking and enforcement mechanisms
Solution Approach 1:
The system performs permission checking before MIDlet execution by validating rights objects and constraints in advance. The permission manager checks whether execution rights are valid before allowing the MIDlet to launch, preventing unauthorized execution rather than dealing with security issues during runtime.
Solution Approach 2:
A permission manager component acts as an intermediary between the DRM system and MIDlet execution. This mediator handles permission checking, rights validation, and constraint enforcement, separating security functionality from the core execution mechanism and managing complexity through a dedicated intermediary layer.
2Reliability
If permission checking is performed at launch time, then unauthorized execution is prevented, but user experience deteriorates due to potential launch failures and execution interruptions
Solution Approach 1:
The system provides feedback to users when execution rights expire or become invalid. Users are notified of rights expiration and can request renewal through the permission manager, which communicates with the rights issuing service. This feedback mechanism maintains execution control while giving users control over the situation.
Solution Approach 2:
The permission system dynamically adjusts execution status based on rights validity. When rights expire during execution, the system transitions the MIDlet to a paused state rather than immediate termination, allowing dynamic recovery through rights renewal. This dynamic approach balances security with user experience by providing opportunities for recovery.
3Reliability
If execution rights are enforced strictly, then digital rights protection is improved, but application functionality is reduced due to inability to continue running after rights expiration
Solution Approach 1:
The system implements dynamic execution control where MIDlets can transition between running, paused, and terminated states based on rights validity. When rights expire, the MIDlet is paused rather than immediately terminated, allowing dynamic recovery through rights renewal requests. This dynamic approach maintains strict rights protection while preserving application continuity opportunities.
Solution Approach 2:
The system checks rights validity before allowing MIDlet execution and continuously monitors during runtime. By performing preliminary validation and ongoing checks, the system ensures rights protection is maintained while providing clear feedback to users about the status of their execution rights, enabling informed decisions about renewal.
Data Source
AI summary
A system and method of applying a permission model to an application operating on a mobile electronic device. When an application is launched on the mobile electronic device, it is determined whether the mobile electronic device possesses execution rights for the application. If the mobile electronic device does not possess valid execution rights for the application, the application is closed. If valid execution rights for the application expire after the application has been launched, a system is provided to inform the user that the rights have expired. The application with expired rights is then closed, unless the user obtains a new and valid rights object for the application.