System and method of generating applications for mobile devices

• US 20050108692A1
• Filed: 10/29/2004
• Published: 05/19/2005
• Est. Priority Date: 11/17/2003
• Status: Abandoned Application

• Current Assignee: Tira Wireless, Inc.
• Original Assignee: Tira Wireless, Inc.
• Inventors: Yuen, Ivan Yik Fong, Lau, Allen N.L., Tarle, Martin Anthony, Tabay, Oliver Attila
• Application Number:
  US10/975,346
• Publication Number:
  US 20050108692A1
• Time in Patent Office: Days
• US Class Current: 717/136
• CPC Class Codes: G06F 8/52 Binary to binary
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting

Abstract

A method and system of generating target applications from Java reference applications for a particular combination of mobile devices is provided. The method includes the steps of: a) unpacking the reference application into a number of class files; and b) transforming the reference application into the target application by a device plug-in. The device plug-in is capable of transforming different reference applications into corresponding target applications for a particular combination of the reference mobile device and the target mobile device. The system includes a transformation engine and a device plug-in corresponding to the reference/target mobile device combination. The device plug-in includes an XML file and pieces of software code to modify corresponding portions of the reference application not supported by the target mobile device. The XML file directs the transformation engine to identify the unsupported portion of the reference application and to modify the portion with the selected software code.

Claims

1. A method of generating a target application configured for a target mobile device from a Java reference application configured to execute on a reference mobile device, the method comprising:

a) unpacking the reference application into a plurality of class files;

b) transforming the reference application into the target application by a device plug-in, wherein the device plug-in is adapted to transform a plurality of different reference applications into a corresponding plurality of target applications for a predetermined combination of the reference mobile device and the target mobile device.

2. The method of claim 1, wherein the reference application is in bytecode during the transformation step.

3. The method of claim 2, wherein the device plug-in comprises an instruction file and at least one library, wherein the transformation step comprises the instruction file instructing a transformation engine to modify a portion of the reference application with a selected software code stored in the library, wherein the portion of the reference application is not supported by the target mobile device.

4. The method of claim 3, wherein the transforming step comprises modifying at least one of a plurality of class files in the reference application.

5. The method of claim 4, wherein the transformation step comprises adding a new class file to the reference application.

6. The method of claim 4, wherein the modifying step comprises at least one action selected from the group of:

adding a new method, renaming an existing method, replacing a first object method call with a second object method call, replacing the first object method call with a static method call, renaming a constant pool entry, and inserting a new inner class to an existing class.

7. The method of claim 6, further comprising saving the target application to a computer readable medium.

8. The method of claim 7, further comprising repeating step (a) and step (b) to transform the plurality of different reference applications into the plurality of corresponding target applications.

9. The method of claim 1, further comprising selecting a predetermined device plug-in from a plurality of the device plug-ins, the predetermined device plug-in corresponding to the predetermined combination of the reference mobile device and the target mobile device, each of the plurality of the device plug-ins corresponding to a different combination of the reference mobile device and the target mobile device.

10. The method of claim 3, further comprising repackaging the target application into executable code.

11. The method of claim 10, wherein the repackaging step further comprises obfuscating the class files of the target application.

12. The method of claim 10, wherein the repackaging step further comprises pre-verifying the class files of the target application.

13. The method of claim 3, wherein the target application is a non-Java application.

14. The method of claim 6, wherein the unpacking step comprises unpacking a JAR file of the reference application.

15. The method of claim 14, wherein the method further comprises breaking an immutable image from the reference application into a plurality of smaller images.

16. The method of claim 2, wherein the transformation step comprises inserting an interception module into the reference application, wherein the interception module is adapted to intercept key events.

17. The method of claim 16, wherein the transformation step comprises inserting a conversion table into the interception module, wherein the conversion table defines key-mapping from the reference mobile device to the target mobile device.

18. A method of generating a target application configured to execute on a target mobile device from a Java reference application configured to execute on a reference mobile device, the method comprising:

a) unpacking the reference application into a plurality of class files; and

b) transforming the reference application into the target application by a device plug-in and an application plug-in, wherein the device plug-in is adapted to transform a plurality of different reference applications into a corresponding plurality of target applications for a predetermined combination of the reference mobile device and the target mobile device, wherein the application plug-in is adapted to modify a portion of the reference application, wherein the portion does not execute optimally on the target mobile device after transformation of the reference application by the device plug-in.

19. The method of claim 18, wherein the transformation step further comprises:

i) transforming the reference application into an intermediary application build by the application plug-in; and

ii) transforming the intermediary application build into the target application by the device plug-in.

20. The method of claim 19, wherein step (i) further comprises the application plug-in instructing the transformation engine to modify the portion of the reference application.

21. The method of claim 20, wherein the reference application is in bytecode during the transformation step.

22. The method of claim 21, wherein the application plug-in comprises Java code.

23. A method of generating a target application configured to execute on a target mobile device from a Java reference application configured to execute on a reference mobile device, the method comprising:

a) unpacking the reference application into a pluarality of class files;

b) transforming the reference application into an intermediary application build by a device plug-in;

c) generating an application plug-in adapted to modify a portion of the reference application, wherein the portion does not execute optimally on the target mobile device after transformation of the reference application by the device plug-in;

d) repeating step (a); and

e) transforming the reference application into the target application by the device plug-in and the application plug-in.

24. The method of claim 23, wherein step (e) further comprises:

i) transforming the reference application into the intermediary application build by the application plug-in; and

ii) transforming the intermediary application build into the target application by the device plug-in.

25. A system for transforming Java reference applications adapted to execute on a reference mobile device into corresponding target applications configured for a target mobile device, the system comprising:

a) a transformation engine; and

b) a device plug-in comprising;

i) an instruction file; and

ii) a selected software code adapted to modify a portion of the reference application not supported by the target mobile device;

wherein the transformation engine is adapted to access the instruction file, the instruction file being adapted to direct the transformation engine to identify the portion of the reference application and to modify the portion with the selected software code.

26. The system of claim 25, wherein the instruction file comprises an XML file.

27. The system of claim 26, wherein the device plug-in comprises a library, the library being adapted to store a plurality of the software codes adapted to modify a plurality of the portions.

28. The system of claim 27, wherein the transformation engine is a Java application.

29. The system of claim 26, wherein the selected software code comprises an interception module adapted to intercept key events.

30. The system of claim 29, wherein the interception module comprises a conversion table adapted to define key-mapping from the reference mobile device to the target mobile device.

31. The system of claim 26, wherein the selected software code comprises a new method adapted for insertion into the reference application.

32. The system of claim 26, wherein the selected software code comprises a static method call adapted for insertion into the reference application.

33. The system of claim 26, wherein the selected software code comprises a new method name adapted to replace a method name in the reference application.

34. The system of claim 26, wherein the selected software code comprises a new object method call adapted to replace a method call in the reference application.

35. The system of claim 26, wherein the selected software code comprises a new class file adapted for insertion into the reference application.

36. The system of claim 26, further comprising a plurality of the device plug-ins, each of the plurality of the device plug-ins corresponding to a different combination of reference and target mobile device, wherein the transformation engine is adapted to choose a selected one of the device plug-ins corresponding to the different combination.

37. The system of claim 27, wherein the target applications are Java applications.

38. The system of claim 27, wherein the target applications are non-Java applications.

39. A system for transforming a Java reference application configured to execute on a reference mobile device into a target application configured to execute on a target mobile device, the system comprising:

a) a transformation engine; and

b) a device plug-in adapted to transform the reference application into a target application, the device plug-in comprising;

i) an instruction file; and

ii) a selected software code adapted to modify a portion of the reference application not supported by the target mobile device; and

c) an application plug-in adapted to instruct the transformation engine to modify at least a portion of the reference application;

wherein the portion of the reference application does not execute optimally on the target mobile device after transformation of the reference application by the device plug-in;

wherein the transformation engine is adapted to access the instruction file, the instruction file being adapted to direct the transformation engine to identify the portion of the reference application and to modify the portion with the selected software code.