Security Protection Domain Testing Framework for Java ME
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional testing frameworks for Java ME platform implementations do not support testing across different protection domains, profile specification versions, and devices, requiring separate tests for each scenario.
Innovation Solution
A security protection domain-based testing framework that enables the same certification tests to be run across various protection domains and platforms by automatically selecting appropriate tests with correct permissions, supporting configurations like CDC and MIDP, and allowing for mapping of permissions between MIDP versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate tests are developed for each protection domain and platform, then testing coverage is complete, but test development time and cost increase significantly
Solution Approach 1:
The patent creates a universal test suite that can execute across multiple protection domains and Java ME platforms. Tests are designed with permission annotations that allow them to adapt to different security contexts, enabling one test suite to serve multiple functions across Operator, Manufacturer, and Third-Party domains while maintaining comprehensive coverage.
Solution Approach 2:
The patent utilizes parameter changes by modifying permission settings and security attributes dynamically during test execution. Tests can adjust their permission requirements based on the target protection domain, allowing the same test logic to operate under different security parameters without requiring separate test implementations.
2Measurement precision
If separate tests are developed for each protection domain and platform, then testing accuracy is maintained, but device complexity increases
Solution Approach 1:
The patent segments the test suite into modular test cases with distinct permission annotations and configuration parameters. Each test module is independently configurable for different protection domains, allowing precise control over test behavior while maintaining overall suite coherence. This segmentation enables accurate testing without requiring a monolithic complex test system.
3Productivity
If the same test suite is reused across different protection domains, then test development efficiency improves, but testing precision may deteriorate
Solution Approach 1:
The patent applies local quality by allowing different permission configurations and security parameters to be applied to specific test cases based on their target protection domain. Each test can have localized security requirements and expectations tailored to its specific domain (Operator, Manufacturer, or Third-Party), ensuring precision is maintained even though the same test suite is reused across domains.
Data Source
AI summary
Methods and apparatus for security protection domain-based testing. A testing framework enables the same certification tests to be run across different protection domains or operation modes, and on different platforms or devices. The testing framework may, for example, be directed to testing implementations of the Java Platform, Micro Edition (Java ME®) using Connected Device Configuration (CDC) or Connected Limited Device Configuration (CLDC) as the configuration layer and Mobile Information Device Profile (MIDP) as the profile layer. Different Mobile Information Device Profile (MIDP) specifications (e.g., MIDP 2.x and MIDP 3.x specifications) may be supported. The testing framework may be deployed in the context of compatibility testing and technology compatibility kits (TCKs). The testing framework may, for example, be applied in compatibility testing for Java ME® platform technology implementations.