# US 2013/0254832 A1 · Security Protection Domain-Based Testing Framework

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254832 A1
- Document ID: US20130254832A1
- Status: Published application
- Kind: A1
- Application number: 13/532,586
- Filed: 2012-06-25
- Published: 2013-09-26
- Earliest claimed: 2012-03-20
- Assignees: Oracle International Corporation
- Inventors: Boris Kvartskhava; Vasily Isaenko; Alexander Alexeev
- Web page: https://patentgrep.com/patent/US20130254832A1

## CPC

- G06F 11/36: Prevention of errors by analysis, debugging or testing of software
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A method for testing platform implementations, comprising:
performing, by a testing device, for a platform implementation under test:
obtaining a set of permissions according to a particular profile specification, wherein the particular profile specification defines a particular profile, wherein a profile provides APIs for supporting a category of devices and is included in a platform stack that provides a platform runtime environment for the category of devices;
mapping the permissions according to the particular profile specification to another profile specification, wherein said mapping is performed according to a set of permission mapping rules;
adding results of said mapping to the set of permissions, wherein said results are permissions according to the other profile specification;
editing and validating a plurality of protection domain descriptions according to the set of permissions, wherein each protection domain description corresponds to one of a plurality of protection domains supported by the profile specifications; and
for each of the plurality of protection domains that is implemented by the platform implementation under test, determining, from a suite of tests, one or more tests that are to be executed on the platform implementation under test and queuing the one or more tests for execution on the platform implementation under test under the respective protection domain.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein said editing and validating a plurality of protection domain descriptions according to the set of permissions comprises, for each of the plurality of protection domains that is implemented by the platform implementation under test:
editing the respective protection domain description, wherein said editing comprises, for each permission in the set of permission, marking the respective permission as Allowed, User, or Not Permitted in the respective protection domain description; and
validating the respective protection domain description according to one or more validation criteria.

### Claim 3 (depends on 1)

The method as recited in claim 1, wherein said determining, from a suite of tests, one or more tests that are to be executed on the platform implementation under test comprises, for each test in the suite of tests:
determining if the test is applicable to the platform implementation under test; and
determining if permissions specified in a respective test description for the test match permissions specified in the protection domain description of the current protection domain;
wherein the test is not queued for execution if the test not applicable to the platform implementation under test or if the permissions specified for the test do not match the permissions specified for the current protection domain.

### Claim 4 (depends on 3)

The method as recited in claim 3, wherein said editing the respective protection domain description is performed via input to a user interface.

### Claim 5 (depends on 3)

The method as recited in claim 3, wherein the platform implementation under test is a Java Platform, Micro Edition (Java ME®) platform implementation.

### Claim 6 (depends on 1)

The method as recited in claim 1, wherein the particular profile specification is a Mobile Information Device Profile (MIDP) specification, and wherein the other profile specification is a different version of the MIDP specification.

### Claim 7 (depends on 1)

The method as recited in claim 1, wherein the platform stack further includes a configuration that is below the profile in the platform stack and that provides a basic set of libraries and APIs for the platform implementation.

### Claim 8 (depends on 7)

The method as recited in claim 7, wherein the configuration is one of Connected Device Configuration (CDC) or Connected Limited Device Configuration (CLDC).

### Claim 9

A system comprising:
at least one processor; and
a memory storing program instructions, wherein the program instructions are executable by the at least one processor to:
obtain a set of permissions according to a particular profile specification, wherein the particular profile specification defines a particular profile, wherein a profile provides APIs for supporting a category of devices and is included in a platform stack that provides a platform runtime environment for the category of devices;
map the permissions according to the particular profile specification to another profile specification, wherein said mapping is performed according to a set of permission mapping rules;
add results of said mapping to the set of permissions, wherein said results are permissions according to the other profile specification;
edit and validate a plurality of protection domain descriptions according to the set of permissions, wherein each protection domain description corresponds to one of a plurality of protection domains supported by the profile specifications; and
for each of the plurality of protection domains that is implemented by the platform implementation under test, determine, from a suite of tests, one or more tests that are to be executed on the platform implementation under test and queue the one or more tests for execution on the platform implementation under test under the respective protection domain.

### Claim 10 (depends on 9)

The system as recited in claim 9, wherein, to edit and validate a plurality of protection domain descriptions according to the set of permissions, the program instructions are executable by the at least one processor to, for each of the plurality of protection domains that is implemented by the platform implementation under test:
obtain input editing the respective protection domain description, where said input specifies, for each permission in the set of permission, a respective permission of Allowed, User, or Not Permitted in the respective protection domain description; and
validate the respective protection domain description according to one or more validation criteria.

### Claim 11 (depends on 9)

The system as recited in claim 9, wherein, to determine, from a suite of tests, one or more tests that are to be executed on the platform implementation under test, the program instructions are executable by the at least one processor to, for each test in the suite of tests:
determine if the test is applicable to the platform implementation under test; and
determine if permissions specified in a respective test description for the test match permissions specified in the protection domain description of the current protection domain;
wherein the test is not queued for execution if the test not applicable to the platform implementation under test or if the permissions specified for the test do not match the permissions specified for the current protection domain.

### Claim 12 (depends on 11)

The system as recited in claim 11, wherein the platform implementation under test is a Java Platform, Micro Edition (Java ME®) platform implementation.

### Claim 13 (depends on 9)

The system as recited in claim 9, wherein the particular profile specification is a Mobile Information Device Profile (MIDP) specification, and wherein the other profile specification is a different version of the MIDP specification.

### Claim 14 (depends on 9)

The system as recited in claim 9, wherein the platform stack further includes a configuration that is below the profile in the platform stack and that provides a basic set of libraries and APIs for the platform implementation, wherein the configuration is one of Connected Device Configuration (CDC) or Connected Limited Device Configuration (CLDC).

### Claim 15

A non-transitory computer-readable storage medium storing program instructions, wherein the program instructions are computer-executable to implement:
obtaining a set of permissions according to a particular profile specification, wherein the particular profile specification defines a particular profile, wherein a profile provides APIs for supporting a category of devices and is included in a platform stack that provides a platform runtime environment for the category of devices;
mapping the permissions according to the particular profile specification to another profile specification, wherein said mapping is performed according to a set of permission mapping rules;
adding results of said mapping to the set of permissions, wherein said results are permissions according to the other profile specification;
editing and validating a plurality of protection domain descriptions according to the set of permissions, wherein each protection domain description corresponds to one of a plurality of protection domains supported by the profile specifications; and
for each of the plurality of protection domains that is implemented by the platform implementation under test, determining, from a suite of tests, one or more tests that are to be executed on the platform implementation under test and queuing the one or more tests for execution on the platform implementation under test under the respective protection domain.

### Claim 16 (depends on 15)

The non-transitory computer-readable storage medium as recited in claim 15, wherein, in said editing and validating a plurality of protection domain descriptions according to the set of permissions, the program instructions are computer-executable to implement, for each of the plurality of protection domains that is implemented by the platform implementation under test:
editing the respective protection domain description, wherein said editing comprises, for each permission in the set of permission, marking the respective permission as Allowed, User, or Not Permitted in the respective protection domain description; and
validating the respective protection domain description according to one or more validation criteria.

### Claim 17 (depends on 15)

The non-transitory computer-readable storage medium as recited in claim 15, wherein, in said determining, from a suite of tests, one or more tests that are to be executed on the platform implementation under test, the program instructions are computer-executable to implement, for each test in the suite of tests:
determining if the test is applicable to the platform implementation under test; and
determining if permissions specified in a respective test description for the test match permissions specified in the protection domain description of the current protection domain;
wherein the test is not queued for execution if the test not applicable to the platform implementation under test or if the permissions specified for the test do not match the permissions specified for the current protection domain.

### Claim 18 (depends on 17)

The non-transitory computer-readable storage medium as recited in claim 17, wherein the platform implementation under test is a Java Platform, Micro Edition (Java ME®) platform implementation.

### Claim 19 (depends on 15)

The non-transitory computer-readable storage medium as recited in claim 15, wherein the particular profile specification is a Mobile Information Device Profile (MIDP) specification, and wherein the other profile specification is a different version of the MIDP specification.

### Claim 20 (depends on 15)

The non-transitory computer-readable storage medium as recited in claim 15, wherein the platform stack further includes a configuration that is below the profile in the platform stack and that provides a basic set of libraries and APIs for the platform implementation, wherein the configuration is one of Connected Device Configuration (CDC) or Connected Limited Device Configuration (CLDC).
