WO2003107186A1 - プログラム実行処理端末装置、プログラム実行処理方法及びプログラム - Google Patents
プログラム実行処理端末装置、プログラム実行処理方法及びプログラム Download PDFInfo
- Publication number
- WO2003107186A1 WO2003107186A1 PCT/JP2003/006980 JP0306980W WO03107186A1 WO 2003107186 A1 WO2003107186 A1 WO 2003107186A1 JP 0306980 W JP0306980 W JP 0306980W WO 03107186 A1 WO03107186 A1 WO 03107186A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- program
- format
- temporary
- runtime
- execution
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
Definitions
- the present invention relates to an information terminal device for interpreting and executing a received program, a program execution processing method and a program, and in particular, an information terminal device for realizing a high-speed program start-up,
- the present invention relates to a program execution processing method and a program.
- a typical example is a service for distributing content such as images and ringtones.
- a program not just data, and execute it as an application on a portable information terminal.
- a program not only the functions (applications) provided to the mobile information terminal from the beginning, but also new ones later.
- Various functions can be added and used.
- PIM Patenta 1 Information Manager
- applications such as electronic telephone books and electronic schedule books, and game application applications And other services.
- the user is free to choose the application that has the features he or she wants to use, or the user interface that is easy to use, the screen configuration that he or she likes, and so on. By downloading the program, you can use the selected application.
- JaVa (TM) is a promising software architecture to realize the program distribution mechanism.
- Java is equipped with a virtual machine mechanism, and can run programs without depending on the hardware and the hardware of the device. It is considered an effective architecture not only in the field of convenience such as Narco View (hereinafter abbreviated as PC) but also for home appliances. .
- the start-up time here refers to the user or personal digital assistant.
- Other installed applications can use a specific application for the virtual machine inside the mobile information terminal. It indicates the elapsed time from when an instruction to start execution of interpretation of an application is given to when the initial screen of the application whose start is instructed is output on the display screen of the portable information terminal.
- the startup time is the time it takes for the application to become available, and for the user, the extra time that the application is not actually being used. Because of the time, the longer the startup time, the lower the application execution efficiency.
- TM JaVa
- TM general JaVa
- TM Java
- TM Java
- a program consists of one or more files called class files.
- class files When a program is downloaded, there is usually one class file. It is provided in a packaged format in a file, but after downloading, it is expanded as one or more class files and It is saved as a file.
- the initialization process is an initial operation necessary to enable execution of a Java (TM) virtual machine. More specifically, processing to secure a memory area (such as Java heap area) used by the virtual machine, initialization of garbage collection processing, initialization of class loader, Performs the initialization of the red management, etc.
- TM Java
- the class verification process is a process performed to guarantee the safety of the program to be executed. Specifically, the inspection of the class file format and the byte code included in the class file conform to the specification of JaVa (TM). Inspect this.
- the class file is defined as a recording format that can be executed by a Java TM virtual machine (hereinafter referred to as a run-time execution format). This is the process of expanding on the memory area used by the virtual machine.
- the target class file is a class file with a main method that is the first execution method of the program to be executed, and a class file with the main method. All class files that can be referenced from the file.
- the class loading process is defined as “the class loading process that is necessary only when the application is started for the first time” and the “application Class loading required for the second and subsequent startups of the application ", and the results of the" first class opening-loading process "are stored in a class file.
- the temporary runtime format By storing it as a recording format different from the format (hereinafter referred to as the temporary runtime format), when the program is started, the " The purpose is to reduce the time required to start the program by only having to perform "class load processing". Disclosure of the invention
- a program execution processing terminal device of the present invention is a program for converting a Java (TM) class file into a runtime execution form, for example, from a Java (TM) class file. And a temporary lantern generated based on a program stored in the program storage unit or a runtime execution format converted by the loader unit.
- Temporary run time storage unit for storing the time execution format, and temporary run time stored in the temporary run time execution format storage unit
- a post loader unit for performing a boss loading process for converting an executable format into a runtime executable format, and the temporary run mode is specified when a program is instructed to start.
- Temporary run time in the memory It is determined whether or not the executable form exists.
- the loader unit is requested to convert to the runtime executable form. Requests the loader to convert to runtime execution format. It should be noted that even if the runtime execution format converted by the loader unit is converted to a temporary runtime execution format, the temporary runtime execution format can be obtained. Good. In this way, when the program is started up for the first time, it performs normal load processing, performs run-time saving processing after load processing, and executes tempo processing. By generating a run-time runtime format, the program will be able to generate a run-time format from the temporary run-time format on the second and subsequent launches. Load processing can be replaced with normal load processing, and the processing time required for starting the second and subsequent programs can be shortened.
- a temporary run time execution format is obtained. You may. In this way, the program is preloaded and the temporary run-time executable is generated. From the first time on, the normal load processing can be replaced by the post load processing, and the processing time required for starting the program can be reduced.
- a temporary run time storage format storage step to store the temporary run time execution format storage portion when the program is instructed to start.
- a program of the present invention is for causing a computer to execute the above-described program execution processing method.
- This program may be supplied to a computer such as an information terminal device in a state stored in a computer-readable recording medium, or may be supplied to a computer such as an information terminal device via a communication line. It may be supplied at a convenience store overnight.
- FIG. 1 is a hardware configuration diagram of a portable information terminal according to an embodiment of the present invention.
- FIG. 2 is a block diagram showing a configuration of a program execution processing terminal device according to the embodiment of the present invention.
- FIG. 3 is a diagram showing a relationship between data conversion and data conversion in the class loading process according to the embodiment of the present invention.
- FIG. 4 is a diagram showing an example of a program structure according to the embodiment of the present invention.
- FIG. 5 is a diagram showing an example of the structure of the runtime execution format according to the embodiment of the present invention.
- FIG. 6 is a diagram showing an example of the structure of the runtime execution format according to the embodiment of the present invention.
- FIG. 7 is a diagram showing an example of a structure of a temporary runtime execution form in the embodiment of the present invention.
- FIG. 8 is a diagram showing an example of a structure of a temporary run time execution format according to the embodiment of the present invention.
- FIG. 9 is a flowchart illustrating an example of an operation procedure of the loader unit according to the embodiment of the present invention.
- FIG. 10 is a flowchart showing an example of the operation procedure of the runtime saving unit in the embodiment of the present invention.
- FIG. 11 is a flowchart illustrating an example of an operation procedure of the preloader unit according to the embodiment of the present invention.
- FIG. 12 is a flowchart illustrating an example of an operation procedure of the postloader unit according to the embodiment of the present invention.
- FIG. 13 is a diagram showing an example of a screen display at the time of the run-time-severing process according to the embodiment of the present invention.
- FIG. 14 is a diagram showing an example of a screen display at the time of preload processing in the embodiment of the present invention.
- FIG. 15 is a block diagram showing a configuration of a program execution processing terminal device according to the embodiment of the present invention.
- FIG. 16 is a diagram illustrating an example of an input screen for setting information according to the embodiment of the present invention.
- FIG. 7 is a diagram showing an example of the history information of the insert according to the embodiment of the present invention.
- FIG. 18 is a block diagram illustrating a configuration of a program execution processing terminal device according to an embodiment of the present invention.
- FIG. 19 is a flowchart illustrating an example of an operation procedure of the preload control unit according to the embodiment of the present invention.
- FIG. 20 is a diagram showing an example of a reference time input screen according to the embodiment of the present invention.
- FIG. 21 is a diagram showing an example of a reference time input screen according to the embodiment of the present invention.
- FIG. 22 is a diagram showing an example of the internal state transition in the embodiment of the present invention.
- FIG. 23 is a diagram showing an example of a table corresponding to the pre-reading process in the embodiment of the present invention.
- FIG. 24 is a block diagram showing the configuration of the program execution processing terminal device according to the embodiment of the present invention.
- FIG. 25 is a diagram illustrating an example of a processing outline of the separate application instruction notification unit according to the embodiment of the present invention.
- FIG. 1 is a diagram showing a hardware configuration of a portable information terminal according to Embodiment 1 of the present invention.
- Central Processing Unit (CPU) 1 and BLJ The apparatus includes a device 2, an input device 3, an output device 4, and a transmission / reception device 5, which are connected to each other via a system path 6.
- the storage device 2 includes a ROM, an RA memory, and a hard disk drive, and is used when the CPU 1 performs processing.
- the BLiH area is used as an area for using the program itself.
- the output device 4 is composed of a display device such as a display, a speed display, and the like, and performs processing such as a screen display of the output from the CPU 1 and reproduction of audio data. .
- the transmission / reception device 5 performs data communication via a wireless or wired path, and the CPU 1 transmits data from an external device (not shown) via the transmission / reception device 5 to a program or the like. Data can be downloaded.
- FIG. 2 is a block diagram showing the configuration of the program execution processing terminal device of the present embodiment.
- the program execution processing terminal device includes a program download unit 101, a mouth unit 102, a runtime saving unit 103, and a prelog unit 1 04, a postloader section 105, an interpreter section 106, a control section 107, a program storage section 301, and a temporary run tie. It has a runtime execution format storage unit 302 and a runtime execution format storage unit 303.
- the program download section 101 receives a program from the program distribution destination and stores the received program in the program storage section 301 via the control section 107. Store.
- the program download section 101 can be realized by using a program download mechanism of a conventional portable information terminal.
- the loader section 102 converts the program stored in the program storage section 301 into a run-time executable form in accordance with a request from the control section 107 '
- the processing for storing in the image execution format storage unit 303 is performed. Also, it notifies the interpreter section 106 of the start of program execution. Further, the converted runtime execution format is notified to the runtime saving unit 103, and the runtime saving process is requested.
- the run-time saving unit 103 temperates the run-time execution format stored in the run-time execution format storage unit 303.
- the conversion into the runtime format is performed, and the process is stored in the temporary runtime format storage unit 302.
- the preloader section 104 converts the program stored in the program storage section 301 into a temporary runtime format in accordance with a request from the control section 107. Then, a process for storing in the temporary runtime execution format storage unit 302 is performed.
- the postloader section 105 executes the temporary run-time execution form stored in the temporary run-time execution form storage section 302 in a run-time manner.
- the data is converted into a format and stored in the runtime execution format storage unit 303. It also notifies the interpreter section 106 of the start of program execution.
- the pre-install part 106 is stored in the runtime execution form storage part 303. Interpret and execute the stored runtime execution format.
- this interpreter section 106 can be realized using a conventional Java (TM) virtual machine.
- the control unit 107 stores the temporary run time of the program to be started in the temporary run time execution format storage unit 302 when the start of the program is instructed. Judge whether or not the executable form exists.If not, request the loader unit 102 to convert it to the runtime executable form.If it does, request the loader unit 105 to convert it to the runtime loader unit. Requests conversion to runtime executable. To convert a temporary runtime into a runtime, copy most of the data and address the indirect representation, as described below. Since it is only necessary to convert the data to the actual address, the processing time is shorter than when the program is converted to the runtime execution format.
- the program storage unit 301 that can reduce the startup time is stored in the program download roW.
- C 101 stores the program received from the program distribution destination.
- a non-volatile memory typified by flash memory or the like, that is, a device that keeps recording even when the power of the portable information terminal is turned off.
- a specific program may be stored in advance. Further, the program stored in advance may be fixed using non-erasable memory such as a ROM.
- the runtime execution format storage unit 303 stores the runtime execution format converted by the sender unit 102 or the postloader unit 105.
- the run-time execution format is a storage area that can be interpreted and executed directly from the interpreter unit 106, so that it can be accessed at high speed. I hope it was realized by For example, volatile RAM is used for this.
- the temporary runtime execution format storage unit 302 stores the temporary runtime execution format converted by the runtime sampling unit 103.
- the temporary runtime execution format storage unit 302 is not particularly limited to volatile or non-volatile. In order to shorten the program startup time, the access speed of the program is faster than that used for the program storage unit 301. It is hoped that a suitable storage device will be used.
- the temporary runtime storage unit 302 is a non-volatile memory such as a flash memory, for example. If you use the temporary run time format stored in the temporary run time format storage unit 302 just before turning off the power of the portable information terminal, the power This is preferable because it can be used the next time the power is turned on.
- both the runtime saving section 103 and the prelog section 104 are provided, but the present invention is not limited to this. That is, only one of them may be provided. Also in this case, similarly to the present embodiment, the startup time of the program can be reduced.
- FIG. 3 shows processing performed by the loader section 102, the runtime saving section 103, the preloader section 104, and the postloader section 105.
- FIG. 4 is a diagram showing an example of a data flow. This figure shows the flow of data conversion from the time when the program 201 is downloaded from the program distribution destination to the time when the runtime execution format 203 is interpreted and executed. .
- the program download section 101 receives the program 201 transmitted from the program distribution destination and stores it in the program storage section 301. .
- the loader 102 executes the program 201 in the run-time execution form 200 according to the instruction from the control unit 107. 3 and the interpreter section 106 interprets and executes the runtime executable form 203.
- the runtime saving unit 103 converts the runtime execution format 203 into the temporary runtime execution format 202, and the temporary runtime execution format. It is stored in the storage unit 302.
- the postloader unit 105 converts the temporary run-time execution format 202 into the runtime execution format.
- the data is converted to 203, and the printer unit 106 interprets and executes the runtime execution format 203.
- the preloader unit 104 converts the program 201 into a temporary runtime execution format 202 and stores it in the temporary runtime execution format storage unit 302.
- the post loader unit 105 executes the temporary run time execution format 202 in accordance with the instruction from the control unit 107.
- the interpreter section 106 interprets the runtime execution format 203 and executes it.
- FIG. 4 to 8 show an example of the structure of the program 201, the runtime execution form 203, and the temporary run time execution form 202 described in FIG. Indicated. Hereinafter, description will be made in order.
- the program 201 can be obtained as an evening with a format that can be interpreted and executed with T ⁇ nS V ⁇ .
- Figure 4 shows an example of the structure of the opening program 201.
- Fig. 4 shows the structure of the content recorded in the program 201, which is similar to the C language.
- the u1, u2, and u4 types represent the unsigned 1-byte, 2-note, and 4-byte data amounts, respectively.
- JaVa (TM) program 2 0 1 usually consists of one or more class files,
- Fig. 4 shows only the top-level structures.
- Figs. 5 and 6 show examples of the structure of the runtime execution format 203.
- the run-time execution format 203 is realized as a continuous memory message stored in the run-time execution format storage unit 303.
- Java TM is used for the run-time format. It is dependent on the implementation of the virtual machine, and is not specified at all.
- the run-time executable form 203 is shown as a class-based memory image.
- the actual Java (TM) program often consists of two or more class files, in which case a similar memory image is created. As many as the number of ras files will be generated.
- the memory image that expresses the class contains a runtime structure of a constant pool structure, which is a lower level structure, and a runtime structure of an interface structure. It includes run-time format for field structure, run-time format for field structure, run-time format for method structure, and run-time format for attribute structure.
- “* Constant — pool” is a pointer that points to the beginning of the runtime format of the constant pool structure, "(constant-poo 1 *) tis-class” and “(constant-poo 1 *) super ⁇ class ”is a pointer to the address of the entry in the instant pool structure, and“ * interfaces ”is the head of the runtime structure of the interface structure.
- the pointer that points to “* fields” is the pointer to the beginning of the field structure runtime format, and the “* methods” is the pointer to the beginning of the method structure runtime format.
- the pointer to point, "* attributes" is the pointer to the beginning of the attribute structure's runtime format.
- pointer value does not necessarily refer to the structure in the memory image of the same class in which the pointer is included, but may refer to other classes. In some cases, it refers to the structure of the memory image.
- the memory image of the runtime execution form 203 contains a pointer, and this pointer value is fixed to a certain value when generating the memory image. Not available (Possible depending on the location of the memory image in the runtime executable storage unit 303) This is because the inter- value fluctuates.)
- the entries in the instant pool structure and the entries in the interface Data in an entry in a field structure, an entry in a field structure, an entry in a method structure, and an entry in an attribute structure.
- the value may include a point value, but it is omitted in this explanation.
- FIGS. 7 and 8 show an example of the structure of the temporary runtime execution format 202.
- FIG. The temporary run time execution form 202 is stored in the temporary run time execution form storage section 302. Either the image may be recorded as a memory image, or the data may be recorded as a file in which bytes are arranged in bytes, but in this case, Fig. 5 It is shown as a memory image in the same way as the expression in Fig. 6. Shown here is an example of the implementation of the temporary run-time execution form 202 corresponding to the embodiment of the run-time execution form 203 shown in FIGS. 5 and 6. is there.
- C 1 ass — id is identification data (class identification number) uniquely given to a memory image in class units. If more than one class of memory image is created, this c 1 ass —id value must not be duplicated.
- “Runtime-one-image-size” is a runtime executable generated from this general-purpose runtime executable. It records the memory size of the formula.
- FIGS. 7 and 8 do not have a pointer value, which is different from FIGS. 5 and 6.
- the data that was represented as a pointer in FIGS. 5 and 6 has all been converted to the following two sets of data (shaded in FIGS. 7 and 8). Part) ⁇
- Ref-c1asss-id specifies the class identification number. This subsequent data is always followed by the entry number.
- the “entrance U number” is defined as the key in the con- trol panel structure / interface structure / field structure / method structure zattribute structure. Indicates the entry number of the evening
- pointer expressions in runtime executables 203 sometimes refer to the structure of the memory message of another class. May be.
- the entry number is always expressed in combination with c 1 a s s-i d to specify which class's memory image follows the memory image.
- Temporal Run Executable Form 203 Since the memory image of Tempora U Run Executable Form 203 does not include Boyne Storm, the Temporal Run Executable Form is stored in memory. Regardless of the location of the memory image in the file, it is determined to be a unique data sequence when the memory image is generated. In other words, the contents of the temporary run-time execution format that expresses a certain class are always thoughtful. I keep it.
- FIG. 9 shows an example of a flow of a data conversion process in the coder 102.
- the memory usage of the runtime execution form 203 generated by the mouth part 102 is calculated (step 601). This inspects the class file included in program 201 and finds consant-poo 1-countsinterfaces-count> fie1ds-count, methods-count :, attributes-COunt. , And a number indicating the number of entries for each structure
- step 602 it is checked whether or not there is a free space in the storage memory area (step 602). If there is no free space (N in step 602), it is determined that continuation of the text-to-text conversion process by the decoder unit 102 is not possible, and the word processing itself is not performed. It cancels, notifies the user that the program cannot be started, and terminates the processing (step 603). On the other hand, if there is an empty space (Y in step 602), a memory area corresponding to the value calculated in step 601 is stored in the runtime execution format storage section 303. Secure (Step 604) Next, the class file is inspected, and the data other than the portion represented as a pointer value in the runtime execution format 203 is copied, whereby the runtime is executed. The data is stored in the program execution format storage section 303 (step 605). This corresponds to the data shown in white boxes in the memory images of FIGS. 5 and 6.
- the data expressed as pointer values in the runtime execution format 203 is calculated from the class file, and the calculated data is stored in the runtime execution format. This is stored in the section 303, and the conversion processing from the program 201 to the runtime execution form 203 is completed (step 606). This corresponds to the data shown in the shaded boxes in the memory images of Figs. 5 and 6.
- FIG. 10 shows an example of the data conversion processing flow in the runtime saving unit 103.
- the memory usage of the temporary runtime execution format 202 generated by the runtime saving unit 103 is calculated (step 701). .
- This is the run-time executable 203, and the entries for each structure are: constant—poo 1—count, interfaces—count, fiel'ds—count, methods—count, attributes—count. It can be calculated from the numerical value indicating the number of entries and the size of each entry of each structure.
- the temporary run time which is the storage location of the temporary run time format 202, is stored. It is checked whether or not there is a free space in the storage memory area in the memory execution form d storage unit 302 (step 720). If there is no free space (N in step 702), the run-time conversion section 103 determines that it is impossible to continue the conversion process, and the run-time save The processing itself is cancelled, and the processing is terminated (step 703). On the other hand, if there is an empty space (Y in step 702), the calculation is performed in step 601, with the temporary run time execution form C0 ⁇
- Temporary run-time execution form as evening 3 ⁇ 4p Store data overnight in custom section 302 (step 705) o
- the runtime execution format 203 which is the source of the runtime processing, is used for recording in the runtime execution format storage unit 303. Calculates the numerical value of the amount of memory used, and stores the temporary runtime format as the runtime-imae_size data of the temporary runtime format. Store in 302 (Step 706)
- the memory image of the runtime execution format 203 is inspected, and the data other than the portion expressed as the pointer value in the runtime execution format 203 is copied to the tempo.
- the data is stored in the temporary run-time execution format storage unit 302 by copying the data as a run-time of the run-time runtime format 202. Step 707). This is equivalent to the data shown in white boxes in the memory images in Fig. 7 and Fig. 8.
- the converted data is stored in: r run time execution format storage section 302, and the run time run format 2 is read from run time run format 203.
- the conversion process to 02 is completed (step 708).
- the data of the point value is converted into the form of “identification number J of the class containing the structure indicated by the point value” and “entry number in the structure”. This is shown in the memory images in Figs. 7 and 8, except for c1ass-id and runt 1me-1mage-size. Equivalent to.
- FIG. 11 shows an example of the processing flow of the overnight conversion in the pre-order unit 104.
- the memory usage of the temporary runtime execution format 202 generated by the preloader 104 is calculated (step 801). This inspects the class file before processing, and enters an entry for each structure such as constant-pool-one count, interfaces-count, fields-count, methods-count; and attributes-count. It can be calculated from the numerical value indicating the number and the size of each entry of each structure.
- the temporary In the temporary runtime execution format storage unit 302 which is the storage location of the runtime execution format 202, it is checked whether or not there is free storage memory area. 8102). If there is no free space (N in step 802), it is determined that the data conversion process by the preloader unit 104 cannot be continued, and the preload process itself is cancelled. Then, the processing is terminated (step 803). On the other hand, if there is free space (Y in step 802), the temporary run-time execution format storage unit 302 stores only the value calculated in step 801. Secure a memory area (step 804).
- identification numbers are given to all classes to be subjected to preload processing, and the c1 ass-id data of the temporary run-time execution form 202 is given.
- the data is stored in the temporary runtime execution format storage unit 302 (step 805).
- the program 210 which is the source of the preload processing, is stored in the temporary runtime execution format storage unit 302. Calculates the amount of memory to be used when converted to run-time executable form 203, and calculates the runtime run-time image size of temporary run-time executable form 202.
- the data is stored in the temporary runtime execution format storage unit 302 as data (step 806).
- the data is copied as data in the runtime execution format 202 (step 807). This is indicated by the white box in the memory image of Figures 7 and 8. Equivalent to one evening.
- the program 201 is inspected, and the data in the portion of the temporary run-time executable form 202 expressed as a reference value to another structure is referred to as “reference data”.
- the data is converted into the data in the form of “identification number of the class including the structure” and “entry number in the structure”. End the conversion process to the executable form 202 (Step 808) 0
- FIG. 12 shows an example of the flow of the process of the overnight conversion in the post mouth unit 105.
- the amount of memory used in the runtime execution form 203 generated by the post mouth part 105 is calculated (step 901). This is a temporary runtime executable.
- the run-time execution format storage section 303 which is the storage location of the run-time execution format 203, has free space in the save memory area.
- Check for existence step 902 If there is no free space (N in step 902), it is determined that the continuation of the processing by the postloader section 105 cannot be performed, and the boss mouth processing itself is not performed. Cancel, notify the user that the program cannot be started, and terminate the process (step 903). On the other hand, if there is (Step 902 is Y), the runtime execution format storage unit 3
- a memory area is secured for the value calculated in step 901 (step 904).
- the temporary run-time executable 202 is inspected, and the portion of the run-time executable 203 other than the portion expressed as a pointer value is copied.
- the data is stored in the runtime execution type PL storage unit 303 (step 905). This corresponds to the white box in the memory image of Figures 5 and 6.
- the expression represented as a pointer value in the runtime execution format 203 is calculated, and the calculated values are stored in the runtime execution format storage unit 303, and the tempora
- the conversion process from the re-execution form 202 to the re-execution form 203 ends (step 906).
- This calculation is based on the reference values in the temporary runtime execution format 202, that is, the “identification number of the class including the referenced structure” and the “entry number in the structure”. This can be realized by converting the shape of the night sky into a point night sky. This crest-evening corresponds to the hatched box in the memory images of Figures 5 and 6.
- the program can be started and executed only by the postload process. Become .
- the run-time executable form 203 can be easily obtained by copying the memory image. The two major effects are that the amount of processing for image generation can be significantly reduced, and the startup time of the program can be shortened.
- FIG. 13 is a diagram for explaining a screen display during the runtime saving process.
- the runtime-separating unit 103 generates a temporary run-time execution format at the end of the load process by the loader unit 102. It is only necessary to check whether or not there is free memory area to be stored, and to perform run-time-severing processing immediately when it is determined that there is free memory area.
- the loader section 102 outputs the display screen of the mobile information terminal during the process of converting the program 201 into the runtime execution form 203
- the time saving section 103 converts the display output of the portable information terminal during the process of converting the runtime execution format 203 into the temporary runtime execution format 202.
- An example is shown in which a change is made and the processing status is notified to the user. In this case, the user may consider runtime save processing as extra processing, and may feel extra stress in the waiting time until the program starts executing.
- Fig. 13 (b) shows an example in which the display screen outputs of these two processes are made the same without any change, and the user is not notified of the boundaries of these processes. This makes it possible to hide the processing time of the runtime saving processing in the loading processing, so that unnecessary stress is not given to the user.
- FIG. 14 is a diagram for explaining a screen display at the time of preload processing.
- the preloader unit 104 determines whether or not there is a free memory area for generating and storing a temporary runtime format after the download process is completed. Should be checked, and if it is determined that there is free space, the pre-reading process can be performed immediately.
- Fig. 14 (a) the display screen output of the portable information terminal during the process of downloading the program 201 by the program download interface 101 and the pre-
- the header section 104 changes the output of the display screen of the portable information terminal during the process of converting the program 201 into the temporary runtime execution form 202, and processes it for the user.
- An example of the status notification is shown. In this case, the user may regard the preload processing as extra processing, and may feel extra stress in the waiting time until the program starts executing.
- Fig. 14 (b) the display screen output of these two processes is made the same without intentionally changing, and the user is deemed to have the boundary between these processes.
- An example in which the notification is not given is shown.
- the processing time of the preload processing can be hidden in the download processing, so that unnecessary stress is not given to the user.
- the run-time saving section 103 or the pre-loader section 104 can hold the temporary run-time execution format in advance. Since the program can be interpreted and executed only by the postload processing, the startup time can be reduced.
- the run-time-severing processing by the run-time-severing unit is performed after the program has been loaded and the program that has been subsequently successive- sively loaded. It was done for Gram. However, it is possible to select and determine a program to be subjected to the run-time-save processing based on other criteria. The details will be described below with reference to the drawings.
- FIG. 15 is a block diagram showing a configuration of a program execution processing terminal device according to Embodiment 2 of the present invention.
- the unit 107, the program storage unit 301, the temporary runtime execution format storage unit 302, and the runtime execution format storage unit 303 are the same as those described in FIG. It is the same as Here, the newly added runtime saving section 110, setting information storage section 304, and interrupt history storage section 304 will be described.
- the run-time saving unit 110 performs run-time saving based on the setting information or history information stored in the setting information storage unit 304 or the history history storage unit 304.
- the setting information storage section 304 for selecting and determining the start timing of the binning process and the target program stores the setting information for identifying the target program for which the run-time processing is performed. This one report is referred to from the run-time saving section 110, and the program that is specified as the target of the run-time saving process (a program that specifies high-speed startup). ), The run-time-severing process is executed.
- the setting information stored in the network information storage unit 304 is determined based on, for example, one-sided input designation.
- Figure 16 shows an example of the input screen. From the program list displayed on the display screen of the portable information terminal, the user can specify ⁇ N or 0FF for each program to be started immediately.
- the programs “Schedule 1 e” and “MemoPad” are specified as fast startup ON. High-speed startup ⁇ The program specified as N was loaded 1 ⁇ 2; When the program is loaded, no run-time-save processing is performed.
- FIG. 17 shows an example of the history information stored in the print history storage unit 305.
- information on how many times it has been started and the last time it was started are shown. , Is stored as a table. It should be noted that other information such as the average startup time and the startup interval may be included, or only one piece of information such as, for example, only the number of startups may be used.
- the following criteria can be applied. You could think so . It should be noted that it may be another criterion using the history information in the evening history storage unit 305.
- the first criterion is that if a program that has been started more than three times is loaded, the program is considered to be used frequently and run-time saving Perform processing.
- the number of selection criteria is not limited to three, but may be any number.
- the second criterion is that, among all programs, the top two programs that have been started so far are the most frequently used programs. No, perform runtime semantic processing.
- the numerical value of the selection criterion is not limited to the upper two, but may be an arbitrary number.
- the storage area of the temporary runtime execution format storage unit 302 is provided by the temporary runtime execution format of a program that does not require high-speed startup or a program that is not frequently used. Can be prevented from being occupied. In other words, run-time saving of programs that require high-speed startup or frequently used programs due to insufficient free storage space in the temporary runtime execution format storage unit 302 Processing can be prevented from failing, and efficient run-time-save processing can be performed.
- the preload processing by the preloader unit is performed when the program is downloaded and the downloaded program is successively downloaded. It was decided to do so.
- the start timing of the preloading process and the target program can be selectively determined based on other criteria.
- FIG. 18 is a block diagram illustrating a configuration of a program execution processing terminal device according to Embodiment 3 of the present invention.
- Time saving section 110 preloader section 11, blade control section 112, program gd storage section 30, and runtime format It comprises a storage section 302, a run-time execution format storage section 303, a setting information storage section 304, and a print split history storage section 105.
- a setting report section 304, and an ink split history storage section 305 are the same as those described with reference to FIG. 1, and a new preloader 1 is added.
- Pre-control unit 1 1 2 Pre-control unit 1 2
- Each of the pre-programs 1 receives the notification from the pre-load control unit 112, and thereby stores the program recorded in the program storage unit 301 in the temporar. It converts the data into the runtime format and stores it in the runtime format storage section 302. In particular, when a child that specifies a specific program is notified, the program that has been notified is selected for preload processing. By receiving the instruction to start the port from the control unit 107, when the program is downloaded, the loading process is executed continuously.
- the setting information storage section 304 Alternatively, a program to be preloaded is selected and determined based on the setting information or the history information stored in the print history storage unit 3005.
- the pre-D control unit 112 determines the start of pre-loading based on the device status of the portable information terminal, and notifies the pre-load unit 111 of the start of processing. .
- the program to be preloaded may be determined by the preload control unit 112, and the determined program may be notified to the preloader unit 111. Even if the start time is notified only without specifying the program to be preloaded and the pre-loader section selects the program to be processed, Good.
- the device state for example, it is conceivable to apply the following criteria.
- the first criterion is that if the mobile information terminal has been in a state of not accepting any user input operation (standby) for a certain period of time or more, pre-processing is performed.
- the preload control unit 112 holds the time length data (reference time) set by the user, and performs the input operation of the user with respect to the non-mobile information.
- the start time is determined by measuring the continuous time of the state where no delay is added (standby) and comparing it with the reference time
- FIG. 19 shows an example of a processing flow in the preload control section 112.
- the device status of the Wm report terminal has entered a state where no user input has been received (standby) for a certain period of time or longer. Is detected (step 1502). If it is not in the standby state (step 1502 is N), the processing transits to step 1501 and repeats the processing. On the other hand, if it is in the standby state (step 1502 is Y), the continuous time of the standby state is updated (step 1503), and the length of the continuous time and the standard are updated. Compare with time (step 1504).
- Step 1504 Until the continuous time of the standby state exceeds the reference time (N in Step 1504), repeat Step 1504 from Step 1502.
- step 15054 is Y
- the start timing of the preload processing is determined, and the preloader section 1 1 1 Notify the start of processing.
- the reference time may be a value unique to the portable information terminal, such as being converted to a ROM, or may be a value that can be changed by a user input.
- Fig. 20 shows an example of the display screen at the time of setting by the user. In this case, 15 minutes is set as the reference time, and the preload processing is started at a timing when the continuous time of the standby state exceeds 15 minutes.
- the pre-load process is executed while the user is not operating the portable information terminal, so that the pre-load process is hidden from the user. Therefore, there is an advantage that no stress is given to the user by executing the preload processing.
- the second criterion is to perform preload processing when the portable information terminal comes out of the standby state.
- the preload control unit 112 changes the user from the mobile information terminal in the standby state.
- the start timing is determined by detecting that the mobile terminal has entered the non-standby state by inputting a user operation, for example, and that the standby state has ended.
- the third criterion is that a preload process is performed when the internal time of the portable information terminal becomes constant.
- the preload control unit 112 holds the time data (reference time) set in advance, compares the actual current time with the reference time, and finds a match.
- the start time is determined by detecting the start time. .
- the reference time may be a value unique to the portable information terminal, such as being converted to a ROM, or the numerical value may be changed by a user input.
- Figure 21 shows an example of the display screen when setting by the user.
- 13:15 is set as the reference time
- the preload processing starts at the time when the actual current time is 13:15.
- a fourth criterion is to perform a preload process when the power of the portable information terminal is turned on.
- the preload control unit 112 determines the start timing based on the power being input.
- the mechanism for detecting the power input of the portable information terminal itself can be realized by using a mechanism such as an event notification from a device used in the conventional portable information terminal. .
- the fifth criterion is that the portable information terminal is a foldable terminal (for example, a foldable mobile phone), and that the user can open or close the foldable portable information terminal. Perform preload processing at that time.
- the preload controller 1 1 2 Is to detect that the portable information terminal has transitioned from a closed state to an open state, or that the portable information terminal has transitioned from an open state to a closed state. To determine the start timing.
- the mechanism for detecting the folding / unfolding of a portable information terminal itself can be realized by using a mechanism such as an event notification from a device used in a conventional portable information terminal. It is possible.
- the sixth criterion is to perform a loading process when communication occurs between the portable information terminal and another electronic device.
- the prod control unit 112 detects the occurrence of data communication between the portable information terminal and another electronic device, so that the start timing is determined. Determine.
- the mechanism itself for detecting the occurrence of communication can be realized using a mechanism such as an event notification from a device used in a conventional mobile phone. .
- the communication here includes an incoming voice call, data communication using HTTP, data communication using FTP, data communication using SSL, and data communication using IrDA. , Etc. are conceivable. Of course, other types of communication supported by the portable information terminal may be used.
- a program to be subjected to preload processing that is started based on the occurrence of communication, a program associated with the type of communication that has occurred may be selected. The selection of this program will be described later. (The seventh criterion in Fig. 23 is that the preload process is performed when the portable information terminal comes and goes with another electronic device.
- the load control unit 112 may be used to attach (attach) another electronic device to the portable information terminal or to remove another electronic device attached (attached) to the portable information terminal.
- the start timing is determined by detecting this.
- the mechanism for detecting the occurrence of attachment / detachment of an external device should be realized by using a mechanism such as an event notification from an external device used in a conventional portable information terminal. Is possible.
- the external device here is, specifically, an external storage device such as an SD card, a function expansion unit such as a B1uetooth, a USB connector, an earphone, a microphone, and a power supply.
- a connector, charger, keypad, etc. can be considered.
- other types of external devices supported by the portable information terminal may be used.
- a program to be preloaded which is started based on attachment / detachment of an external device, a program associated with the type of the external device may be selected. The selection of this program will be described later (Fig. 23).
- the eighth criterion is that a preload process is performed when the execution of another application implemented in the portable information terminal starts or ends.
- the preload control unit 112 may start executing another application implemented in the portable information terminal, or may execute another application.
- the start time is determined by detecting that the execution of the case has ended.
- the mechanism for detecting the start or end of the execution of another application itself is the same as that used in conventional mobile information terminals for software-to-software communication. It can be realized using a mechanism.
- the other application is, specifically, an application mounted on a portable information terminal, such as a browser, a camera, a schedule book, a media player, and the like. Anything is fine.
- this other application may be described in a machine language (native), or may be described by a mechanism using another execution system such as Java (TM). May be described. Also, a program that is preloaded when another application starts or ends is linked and started from the application whose execution has started. Something associated with this other application type, such as possible, may be selected. The selection of this program will be described later (Fig. 23).
- the ninth criterion is to perform pre-slip processing when a certain screen transition is performed in accordance with the input operation of the user of the portable information terminal.
- the preload control unit 112 detects the occurrence of a transition of the internal state of the portable information terminal based on the input operation to the user, thereby starting the timing. Decide what you want.
- a combination of instructions that can be input by the user is set for each internal state, and the next processing operation when a specific input operation is performed is determined.
- the internal state changes sequentially according to the input operation of the user or the communication status with the outside, and the display screen changes with the transition of the internal state.
- the preload control unit 112 detects when a predetermined specific transition has occurred in the transition of the internal state. Detection of internal state transitions is used by conventional portable information terminals It can be realized using the mechanism of communication between software
- Figure 22 shows an example of the transition of the internal state.
- This example shows three internal states: (1) menu selection state, (2) application selection state, and (3) Java application selection state.
- the preload control unit 112 detects this, and the pre-opening unit 1 11. Notify 1 of the start of processing.
- the preloader section 111 starts program preload processing.
- a program associated with the type of the internal state transition may be selected. The selection of this program will be described later (Fig. 23).
- Preload processing can be performed.
- the first selection criterion is to select appropriately (randomly) from the programs downloaded to the mobile information terminal.
- the second selection criterion is that, based on the setting information stored in the setting information storage section 304, a high-speed start designation is made from among the programs downloaded to the portable information terminal. Select a program that has been set as the program of the above, and perform preload processing. Other programs are not subject to preload processing.
- the setting information storage unit 304 has already been described in the second embodiment.
- the third selection criterion is to select a program that is determined to be frequently used based on the history information stored in the print history storage unit 305, and perform preload processing. Go. For example, select the program that has been started the most number of times, or select the program that was started most recently; . It should be noted that the print history storage unit 305 has already been described in the second embodiment.
- the preload control unit 112 selects a program to be processed according to a condition for starting the preload processing.
- the preload control unit 112 holds a preload processing correspondence table, which is a correspondence table between a preload processing start condition and a program to be processed. The program to be processed is selected and determined based on the corresponding table.
- Fig. 23 shows an example of a table for preload processing.
- each condition is identified by assigning a unique ID number called a condition number to the condition for starting the preload processing.
- a condition number a unique ID number
- Ma the start condition is described in sentences, but it is only necessary that the correspondence between the condition number and the meaning be such that the number is not duplicated.
- the identifier of the program to be preloaded is represented by a character string, but may be represented in another way. Programs that are highly relevant to each preload processing start condition, that is, likely to be executed next, should be recorded in advance in the preload processing correspondence table. And pre
- the start timing of the preload process and the target program can be selected, and a program that requires high-speed startup or a program that is frequently used can be selected. As a result, efficient preload processing can be performed.
- FIG. 24 is a block diagram showing a configuration of a program execution processing terminal device according to Embodiment 4 of the present invention.
- Producer download section 101 loader section 102, run time saving section 110, post loader section 105, and printer setup Section 106, control section 107, preloader section 113, separate application instruction notification section 114, and program storage section 3.
- 0 Temporary run-time execution format storage unit 302, Run-time execution format storage unit 303, and setting information storage unit 30
- the section 303, the setting information storage section 304, and the ink split history storage section 304 are the same as those described in FIG.
- the loader unit 113 and the separate application instruction notifying unit 114 will be described.
- the preloader section 113 receives the notification from the separate application instruction notifying section 114, and stores the program recorded in the program storage section 301 as a text.
- the preload processing is performed to convert the data into a runtime format and store it in the temporary runtime storage unit 302. In particular, when an identifier designating a specific program is notified, the notified program is selected as a target for preload processing.
- the preload processing can be continuously performed. It is also possible.
- the separate application instruction notifying section 114 reports the preload start instruction from another application implemented in the portable information terminal. Notify the data section 1 1 3.
- Figure 25 shows a preload start from another application. An example of the processing outline when instructed is illustrated.
- the mechanism for receiving an instruction to start loading from another application is, for example, an API that can be called from within the source code of another application. However, this can be realized by providing it in a portable information terminal.
- the separate application instruction notifying section 114 performs the processing, and instructs the preloader section 113 to start the pre-read processing.
- the API indicated as preloading—start is called from another application to notify the preloader unit 113 of the start of preload processing. An example of working is shown.
- the program to be pre-processed can be specified together with the API call.
- Figure 25 shows an example of specifying a program as an argument of API.
- the argument program_id represents the identifier of the program stored in the program storage unit 301, and the preloader unit 1 1 3 in the processing of pre1 oading_start
- the notice given to the public shall include the information of the program-id.
- the preloader section 113 receives the information of this program—id, and selects a program to be preloaded. It is also possible for the preloader unit 113 to select and execute the next program to be preloaded without specifying a program.
- the trigger for the occurrence of the preload process can be freely specified in the running application, instead of being determined based on the device state. Become . That is, a specific By creating an application that invokes the program's preloading process, the next time the portable information terminal that executes the application will execute By performing preload processing for a specific program such as a program, the startup time of a specific program can be reduced.
- a program such as JaVa (TM) downloaded to a portable information terminal using a program distribution service
- a program is executed.
- Mode processing ⁇ By performing run-time-severing processing, the length of program startup time can be reduced.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP03733256A EP1515232A4 (en) | 2002-06-18 | 2003-06-03 | PROGRAM EXECUTION TERMINAL DEVICE, PROGRAM EXECUTION METHOD, AND PROGRAM |
US10/496,968 US7506323B2 (en) | 2002-06-18 | 2003-06-03 | Program execution processing terminal device, program execution processing method, and program |
AU2003241885A AU2003241885A1 (en) | 2002-06-18 | 2003-06-03 | Program execution terminal device, program execution method, and program |
JP2004513936A JP4376181B2 (ja) | 2002-06-18 | 2003-06-03 | プログラム実行処理端末装置 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002-176855 | 2002-06-18 | ||
JP2002176855 | 2002-06-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003107186A1 true WO2003107186A1 (ja) | 2003-12-24 |
Family
ID=29728124
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/006980 WO2003107186A1 (ja) | 2002-06-18 | 2003-06-03 | プログラム実行処理端末装置、プログラム実行処理方法及びプログラム |
Country Status (6)
Country | Link |
---|---|
US (1) | US7506323B2 (ja) |
EP (1) | EP1515232A4 (ja) |
JP (1) | JP4376181B2 (ja) |
CN (1) | CN1310148C (ja) |
AU (1) | AU2003241885A1 (ja) |
WO (1) | WO2003107186A1 (ja) |
Families Citing this family (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100697416B1 (ko) * | 2003-09-30 | 2007-03-20 | 교세라 가부시키가이샤 | 모바일 통신 단말기, 정보 제공 시스템 및 프로그램을기록한 컴퓨터 판독가능한 기록 매체 |
US7539975B2 (en) * | 2004-06-30 | 2009-05-26 | International Business Machines Corporation | Method, system and product for determining standard Java objects |
US7647581B2 (en) * | 2004-06-30 | 2010-01-12 | International Business Machines Corporation | Evaluating java objects across different virtual machine vendors |
US7493596B2 (en) * | 2004-06-30 | 2009-02-17 | International Business Machines Corporation | Method, system and program product for determining java software code plagiarism and infringement |
US7739267B2 (en) * | 2006-03-10 | 2010-06-15 | International Business Machines Corporation | Classification and sequencing of mixed data flows |
US9361137B2 (en) | 2006-03-10 | 2016-06-07 | International Business Machines Corporation | Managing application parameters based on parameter types |
US8160999B2 (en) * | 2006-12-13 | 2012-04-17 | International Business Machines Corporation | Method and apparatus for using set based structured query language (SQL) to implement extract, transform, and load (ETL) splitter operation |
US8219518B2 (en) | 2007-01-09 | 2012-07-10 | International Business Machines Corporation | Method and apparatus for modelling data exchange in a data flow of an extract, transform, and load (ETL) process |
US9298721B2 (en) * | 2007-02-28 | 2016-03-29 | Qualcomm Incorporated | Prioritized search results based on monitored data |
US8745507B2 (en) * | 2007-11-30 | 2014-06-03 | At&T Intellectual Property I, L.P. | Preloader employing enhanced messages |
CN101520733B (zh) * | 2008-02-27 | 2014-04-16 | 国际商业机器公司 | 装载类的方法和装置及重组类存档文件方法 |
US20100011357A1 (en) * | 2008-07-13 | 2010-01-14 | International Business Machines Corporation | System and method for garbage collection in a virtual machine |
US8875115B2 (en) * | 2008-11-29 | 2014-10-28 | International Business Machines Corporation | Type merging technique to reduce class loading during Java verification |
US8458676B2 (en) * | 2009-06-30 | 2013-06-04 | International Business Machines Corporation | Executing platform-independent code on multi-core heterogeneous processors |
US9069543B2 (en) | 2011-12-22 | 2015-06-30 | International Business Machines Corporation | Predictive operator graph element processing |
WO2014094107A1 (en) * | 2012-12-17 | 2014-06-26 | Blackberry Limited | System and methods for launching an application on an electronic device |
US11483415B2 (en) | 2014-07-16 | 2022-10-25 | Tensera Networks Ltd. | Background pre-rendering of user applications |
US11489941B2 (en) * | 2014-07-16 | 2022-11-01 | Tensera Networks Ltd. | Pre-loading of user applications including skipping of selected launch actions |
US11095743B2 (en) * | 2014-07-16 | 2021-08-17 | Tensera Networks Ltd. | Optimized content-delivery network (CDN) for the wireless last mile |
KR102401772B1 (ko) * | 2015-10-02 | 2022-05-25 | 삼성전자주식회사 | 전자 장치에서 어플리케이션 실행 장치 및 방법 |
US12099856B2 (en) | 2018-03-05 | 2024-09-24 | Tensera Networks Ltd. | Robust application preloading with accurate user experience |
WO2019171237A1 (en) | 2018-03-05 | 2019-09-12 | Tensera Networks Ltd. | Application preloading in the presence of user actions |
US11922187B2 (en) | 2018-03-05 | 2024-03-05 | Tensera Networks Ltd. | Robust application preloading with accurate user experience |
CN114144777A (zh) | 2019-07-30 | 2022-03-04 | 腾赛拉网络有限公司 | 用户设备中应用用户界面的预渲染 |
WO2022118131A1 (en) | 2020-12-03 | 2022-06-09 | Tensera Networks | Preloading of applications having an existing task |
WO2022130156A1 (en) | 2020-12-20 | 2022-06-23 | Tensera Networks Ltd. | Preloading of applications transparently to user |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07191853A (ja) * | 1993-12-27 | 1995-07-28 | Nec Corp | メモリファイル化処理システム |
JPH07271603A (ja) * | 1994-03-31 | 1995-10-20 | Mitsubishi Electric Corp | オーバレイプログラムロード方式 |
JPH10506743A (ja) * | 1996-02-21 | 1998-06-30 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | コンピュータ・システムのユーザ要求に対する応答時間を改善する方法およびコンピュータ・システム |
JPH11212893A (ja) * | 1997-10-08 | 1999-08-06 | Sony Corp | 電子機器におけるプログラム起動装置、プログラム起動方法、媒体および電子機器 |
JPH11232115A (ja) * | 1997-11-19 | 1999-08-27 | Internatl Business Mach Corp <Ibm> | ソフトウェア・モジュール転送方法、データ処理ネットワークおよびシステム |
JP2001273151A (ja) * | 2000-01-21 | 2001-10-05 | Fujitsu Ltd | プログラム実行装置、プログラム実行方法、記録媒体、及び制御プログラム |
JP2002508560A (ja) * | 1997-12-16 | 2002-03-19 | マイクロソフト コーポレイション | マルチプル・クラスファイルのランタイムイメージへの結合 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3727677B2 (ja) * | 1994-09-20 | 2005-12-14 | 石塚硝子株式会社 | ガラス製品のプレス成形装置 |
JP3586943B2 (ja) | 1995-10-20 | 2004-11-10 | 富士通株式会社 | プログラムロード装置と方法 |
US5966702A (en) | 1997-10-31 | 1999-10-12 | Sun Microsystems, Inc. | Method and apparatus for pre-processing and packaging class files |
US6513155B1 (en) * | 1997-12-12 | 2003-01-28 | International Business Machines Corporation | Method and system for merging event-based data and sampled data into postprocessed trace output |
EP0950947B1 (en) | 1998-03-24 | 2003-09-10 | Sun Microsystems, Inc. | Static binding of dynamically dispatched calls in the presence of dynamic linking and loading |
GB9825102D0 (en) * | 1998-11-16 | 1999-01-13 | Insignia Solutions Plc | Computer system |
CA2255042C (en) * | 1998-11-30 | 2004-04-13 | Leonard W. Theivendra | Class loader |
GB0013132D0 (en) * | 2000-05-31 | 2000-07-19 | Ibm | Virtual machine with reiitialisation |
-
2003
- 2003-06-03 WO PCT/JP2003/006980 patent/WO2003107186A1/ja active Application Filing
- 2003-06-03 CN CNB038019493A patent/CN1310148C/zh not_active Expired - Fee Related
- 2003-06-03 JP JP2004513936A patent/JP4376181B2/ja not_active Expired - Fee Related
- 2003-06-03 EP EP03733256A patent/EP1515232A4/en not_active Withdrawn
- 2003-06-03 US US10/496,968 patent/US7506323B2/en not_active Expired - Fee Related
- 2003-06-03 AU AU2003241885A patent/AU2003241885A1/en not_active Abandoned
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07191853A (ja) * | 1993-12-27 | 1995-07-28 | Nec Corp | メモリファイル化処理システム |
JPH07271603A (ja) * | 1994-03-31 | 1995-10-20 | Mitsubishi Electric Corp | オーバレイプログラムロード方式 |
JPH10506743A (ja) * | 1996-02-21 | 1998-06-30 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | コンピュータ・システムのユーザ要求に対する応答時間を改善する方法およびコンピュータ・システム |
JPH11212893A (ja) * | 1997-10-08 | 1999-08-06 | Sony Corp | 電子機器におけるプログラム起動装置、プログラム起動方法、媒体および電子機器 |
JPH11232115A (ja) * | 1997-11-19 | 1999-08-27 | Internatl Business Mach Corp <Ibm> | ソフトウェア・モジュール転送方法、データ処理ネットワークおよびシステム |
JP2002508560A (ja) * | 1997-12-16 | 2002-03-19 | マイクロソフト コーポレイション | マルチプル・クラスファイルのランタイムイメージへの結合 |
JP2001273151A (ja) * | 2000-01-21 | 2001-10-05 | Fujitsu Ltd | プログラム実行装置、プログラム実行方法、記録媒体、及び制御プログラム |
Non-Patent Citations (1)
Title |
---|
See also references of EP1515232A4 * |
Also Published As
Publication number | Publication date |
---|---|
JPWO2003107186A1 (ja) | 2005-10-20 |
US20050066283A1 (en) | 2005-03-24 |
US7506323B2 (en) | 2009-03-17 |
JP4376181B2 (ja) | 2009-12-02 |
EP1515232A4 (en) | 2007-09-05 |
EP1515232A1 (en) | 2005-03-16 |
CN1310148C (zh) | 2007-04-11 |
CN1613061A (zh) | 2005-05-04 |
AU2003241885A1 (en) | 2003-12-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2003107186A1 (ja) | プログラム実行処理端末装置、プログラム実行処理方法及びプログラム | |
US6980979B2 (en) | Method and apparatus for customizing Java API implementations | |
US7035806B2 (en) | Communication apparatus, communication method and program storage medium | |
US6564229B1 (en) | System and method for pausing and resuming move/copy operations | |
US7730047B2 (en) | Analysis of media content via extensible object | |
JPH11259304A (ja) | プラグインメディアデコ―ダ供給方法及び装置 | |
WO2017193885A1 (zh) | 一种应用启动方法及装置 | |
TW201440037A (zh) | 語音操控方法、行動終端裝置及語音操控系統 | |
EP1118931A3 (en) | Method of controlling portable personal device having facilities of storing and playing digital contents by computer and portable personal device operation method therefor | |
US20070266231A1 (en) | Portable Electronic Device and Method for Loading Resource Data of the Portable Electronic Device | |
KR100452343B1 (ko) | 기계어 코드 실행영역을 포함하는 이동통신 단말기용 파일을 기록하는 저장매체 및 그를 이용한 파일 실행방법 | |
KR101015149B1 (ko) | 말하는 전자책 | |
US7162425B2 (en) | Speech-related event notification system | |
US20070239780A1 (en) | Simultaneous capture and analysis of media content | |
US20080175564A1 (en) | System and method for presenting supplementary program data utilizing pre-processing scheme | |
US6876969B2 (en) | Document read-out apparatus and method and storage medium | |
JP2009211187A (ja) | 情報処理装置 | |
JP2002351652A (ja) | 音声認識操作支援システム、音声認識操作支援方法、および、音声認識操作支援プログラム | |
JP2011505623A (ja) | メモリ使用量を改善する方法、装置、およびコンピュータプログラム | |
JP2003330736A (ja) | 不正リソース利用防止システム及びその方法並びにプログラム | |
WO2011010442A1 (ja) | 情報処理端末 | |
JP2001216131A (ja) | 情報処理装置および方法、並びにプログラム格納媒体 | |
JP2003271406A (ja) | データ処理装置およびデータ処理方法ならびにそのプログラム | |
US7970839B2 (en) | Automatic download of images from online storage | |
JP2008052698A (ja) | 言語フォーマット認識方法および装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004513936 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003733256 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10496968 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038019493 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2003733256 Country of ref document: EP |