BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 [PRIOR ART] shows in flow diagram form the distribution path of a mobile application from the application publisher to the end user mobile device.
FIG. 2 shows one example of an arrangement of a mobile application distribution path in accordance with the system of this invention for the purpose of distributing advertising content.
FIG. 3 is a UML sequence diagram which illustrates the rewriting process in accordance with the present invention as used in the mobile application distribution prior to a request for distribution of the application to a mobile device.
FIG. 4 is a UML sequence diagram which illustrates the rewriting process in accordance with the present invention as used in the mobile application distribution subsequent to a request for distribution of the application to a mobile device.
FIG. 5 is a flow diagram showing the steps of code rewriting according to the present invention.
FIG. 6 is a system block diagram of the instrumentation server showing the analysis and rewriting modules and their interaction with a configuration database and optional external systems.
FIG. 7 is a UML sequence diagram which illustrates one example of how certain of the components of FIG. 6 can interact.
FIG. 8 shows in block diagram form the components of a mobile application developed in Java.
FIG. 9 is a diagram showing the results of applying the code rewriting process of FIG. 5 to the mobile application of FIG. 8.
FIG. 10 is a diagram showing a more detailed view of the classfile components of FIG. 8.
FIG. 11 is a diagram showing how the mobile application of FIG. 8 can be divided into two applications for the purpose of reducing the size of individual applications.
FIG. 12 is a diagram showing how the distribution package file size of the mobile application of FIG. 8 can be reduced by removing resource files and retrieving them instead at runtime.
FIG. 13 is a UML sequence diagram showing the runtime behavior of a mobile application instrumented according to the present invention.
FIG. 14 is a UML sequence diagram showing the runtime behavior of a mobile application instrumented according to the present invention, in cooperation with a portal application.
FIG. 15 is a UML sequence diagram showing the runtime behavior of one or more cooperating mobile applications instrumented according to the present invention.
FIG. 16 is a UML sequence diagram showing the interaction of the inventory emulator of one embodiment with ad content servers to provide targeted ads.
FIG. 17 illustrates an example of an instrumented application as displayed to the user, with presplash and postsplash screens.
FIG. 18 is a diagram showing an example flow of applications, advertisements, statistics, and payments in a commercial application of this invention.
FIG. 19 is a diagram showing an example arrangement of the conventional mobile application distribution path which has been augmented with the system of this invention for the purpose of application billing and subscription management.
FIG. 20 is a diagram showing an example arrangement of the conventional mobile application distribution path which has been augmented with the system of this invention for the purpose of gathering market research data.
FIG. 21 is a diagram showing an example arrangement of the conventional mobile application distribution path which has been augmented with the system of this invention for the purpose of personalizing application content.
FIG. 22 is a diagram showing an example arrangement of the conventional mobile application distribution path which has been augmented with the system of this invention for the purpose of communicating game scores to a networked score server.