Method and apparatus for securely enabling native code execution on a JAVA enabled subscriber device

• US 20040172620A1
• Filed: 02/28/2003
• Published: 09/02/2004
• Est. Priority Date: 02/28/2003
• Status: Abandoned Application

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Perez, Ricardo Martinez
• Application Number:
  US10/376,667
• Publication Number:
  US 20040172620A1
• Time in Patent Office: Days
• US Class Current: 717/118
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators

Abstract

A J2ME application (18) stored in memory (14) of a subscriber device (10) includes a Java Native Framework application program interface (24) for providing execution of Framework native code (21) and subscriber device native code (20). An instantiation process (300) determines if the J2ME application (18) has a primary key and accordingly initializing a registration database (48). A registration process (400) registers the Framework native code (21) in the registration database according to an assigned entry identification and dynamically links the Framework native code (21) with subscriber device native code (20), if needed. An execution process (500) executes the Framework native code (21) when the Java Native Framework application program interface is run by the J2ME application (18).

Claims

1. A method for providing native code execution for a Java application, the method comprising:

registering a Framework native function into a registration database according to an entry identification assigned to the Framework native function; and

jumping to Framework native code corresponding to the Framework native function when the Framework native function is called during execution of the Java application by referring to the entry identification assigned to the Framework native function.

2. The method of claim 1, wherein the registering of the Framework native function into the registration database further comprises linking the Framework native code with one or more native application program interfaces.

3. The method of claim 1, wherein the registering of the Framework native function into the registration database further comprises storing the Framework native code in memory associated with one or more native application program interfaces to thereby install the Framework native code.

4. The method of claim 1, further comprising:

determining when the Java application has a valid primary key prior to the registering of the Framework native function into the registration database; and

performing the registering of the Framework native function into the registration database and the jumping to the Framework native code only when the the Java application has the valid primary key.

5. The method of claim 1, further comprising:

determining when the Java application has a valid application program interface key; and

determining a license level associated with the valid application program interface key when the Java application is determined to have the valid application program interface key.

6. The method of claim 5, wherein the registering of the Framework native function into the registration database further comprises linking native code of an application program interface associated with the license level with the Framework native code.

7. The method of claim 5, wherein the registering of the Framework native function into the registration database further comprises cross linking the Framework native function with one or more Framework native functions previously registered in the registration database.

8. The method of claim 5, wherein the determining of when the Java application has the valid application program interface key is performed when the Java application instantiates a Native Framework.

9. The method of claim 1, wherein the registering of the Framework native function into the registration database further comprises decoding the Framework native code.

10. The method of claim 1, wherein the registering of the Framework native function into the registration database further comprises determining if an executable and linking format of the Framework native code is compatible with a target architecture.

11. A Java Native Framework application program interface arranged to provide native code execution by a Java application, the Java Native Framework application program interface when executed by a Java application resulting in the Java application:

registering a Framework native function into a registration database according to an entry identification assigned to the Framework native function; and

jumping to Framework native code corresponding to the Framework native function when the Framework native function is called by the Java application by referring to the entry identification assigned to the Framework native function.

12. The Java Native Framework application program interface of claim 11, further comprising linking the Framework native code with one or more application program interfaces.

13. The Java native framework application program interface of claim 11, further comprising:

determining when the Java application has a valid primary key prior to the registering of the Framework native function into the registration database; and

performing the registering of the Framework native function into the registration database and the jumping to the Framework native code only when the Java application is determined to have the valid primary key.

14. The Java Native Framework application program interface of claim 13, wherein the determining when the Java application has a valid primary key is performed when the Java application instantiates a Native Framework variable.

15. The Java Native Framework application program interface of claim 13, wherein the determining when the Java application has a valid primary key further comprises decrypting a secure key embedded with the Java application at a download time.

16. The Java Native Framework application program interface of claim 11, further comprising:

determining when the Java application has a valid application program interface key; and

determining a license level associated with the valid application program interface key.

17. The Java Native Framework application program interface of claim 16, wherein the registering of the Framework native function further comprises linking the Framework native code with one or more application program interfaces associated with the license level.

18. The Java Native Framework application program interface of claim 16, wherein the registering of the Framework native function into the registration database further comprises cross linking the Framework native code with one of previously registered Framework native code and JAVA classes.

19. The Java Native Framework application program interface of claim 16, wherein the registering of the Framework native function into the registration database further comprises determining if an executable and linking format of the Framework native code is compatible with a target architecture.

20. The Java Native Framework application program interface of claim 11, wherein the registering of the Framework native function into the registration database further comprises storing the Framework native code in memory associated with one or more native application program interfaces to thereby install the Framework native function.

21. A Java Native Framework application program interface comprising a registration database including one or more entry identifications, wherein each of the one or more entry identifications refers to Framework native code stored in memory, the Framework native code including one of dynamically linked native code and cross linked Framework native code for execution by a Java application.

22. The Java Native framework of claim 21, wherein the Framework native code is stored in heap memory.

23. The Java Native framework of claim 21, wherein the Framework native code further includes dynamically linked additional Framework native code.

24. The Java Native framework of claim 21, wherein the dynamically linked native code is native code corresponding to a predetermined license level.

25. The Java Native framework of claim 21, wherein one of the Framework native code and a corresponding Java Class is suitable for execution by any one of a plurality of Java applications.