KR101453743B1 - Pre-caching method for web application and device using the same - Google Patents

Abstract

The present invention relates to a pre-caching method for a web application in which the execution speed of a web application is improved by analyzing a page-to-page call relationship of a web application composed of a plurality of pages and caching a page with a high possibility of calling, and a terminal device A terminal device that stores a web application composed of a plurality of pages analyzes a call relationship between a plurality of pages included in a web application when executing a web application and searches for one or more pages The execution speed at the time of page switching is improved.

Description

[0001] The present invention relates to a pre-caching method for a web application,

The present invention relates to a pre-caching method for a web application and a terminal device using the method. More particularly, the present invention relates to a method and system for analyzing a call relationship between pages constituting a web application, And more particularly, to a pre-caching method for a web application having improved speed and a terminal device using the same.

Recently, with the growth of smart phones, open environment has been required, and an open application and platform environment is required to differentiate services.

More specifically, as a smartphone capable of freely selecting and installing a desired mobile application is rapidly growing, development of a mobile application available in such a smart phone and an open market place (OMP) Is activated.

On the other hand, the web launched to express static and simple contents has been rapidly expanding the user base and service area because it can provide an equal level of user interface wherever the client application of the browser is available. At the same time, web contents are evolving into simple web content that describes a specific content and can provide a desired service in response to user input.

Accordingly, when a service platform supporting standard web technology is implemented for a mobile communication terminal equipped with a GPOS such as a smart phone, a web application can be provided as a mobile application. Therefore, a rich web developer base and a web development tool It is expected that it will be possible to develop a mobile application more easily and also to develop and provide a rich user interface easily and quickly.

However, since the web application is made by linking a plurality of pages, the terminal must read and display the file of each page each time the page is switched. Thus, the screen switching speed is slower than other applications.

SUMMARY OF THE INVENTION The present invention has been proposed in order to solve the problems of the related art, and it is an object of the present invention to provide a web application that improves the execution speed of a web application by analyzing a page- And a terminal device using the method.

According to one aspect of the present invention, there is provided an information processing apparatus comprising: an input unit for outputting a user input signal corresponding to a user input; A storage unit for storing a file of a web application composed of a plurality of interconnected pages; When a web application is requested to be executed through an input unit, a file of the web application is loaded and executed in the storage unit. When the web application is executed, the calling relationship between a plurality of pages included in the web application is analyzed, And a control unit for pre-caching one or more pages which are likely to be called.

In the terminal device according to the present invention, the control unit may include an analysis module for analyzing a call relation between respective pages of the web application composed of a plurality of mutually linked pages; A prediction module for extracting one or more pages that are likely to be called from the current page and generating a page list based on the analysis result of the analysis module; And an execution module for pre-caching one or more pages included in the page list generated in the prediction module.

In the terminal device according to the present invention, the analysis module may further generate a table for storing the inter-page call frequency using the analysis result.

In the terminal device according to the present invention, the prediction module measures the frequency of calling between pages using the page switching result during execution of the web application, and determines the possibility of calling based on the calling frequency.

In the terminal device according to the present invention, when a page switching event occurs, the prediction module deletes the currently generated page list and generates a page list based on the converted page.

In the terminal device according to the present invention, the execution module sets the number of pages to be cached in consideration of the available memory.

In the terminal device according to the present invention, the control unit may analyze and / or structure one or more pages which are likely to be called and convert the binary page data into binary page data for storage.

The terminal device according to the present invention is characterized in that the web application includes a content file describing the content of the web application and an information file describing the information about the web application.

In the terminal device according to the present invention, the content file includes a source file representing each page of the web application and a resource file linked to the source file by a link.

In the terminal device according to the present invention, the source file includes a markup language in which a tag and an attribute of the tag are described, a style sheet describing a tag and a style in which the attribute of the tag is displayed on the page, And a scripting language.

In the terminal device according to the present invention, the resource file may include at least one of a scene description, a video, an audio, an image, a font, text, metadata, and a script file.

In the terminal device according to the present invention, the information file includes configuration information describing configuration information including a list of files included in the web application, a disclosure status and a disclosure range for each file, and a setting value for setting an execution environment of the web application And a policy information file describing policy information for designating a range of access authority for the web application to access the operating system of the terminal.

According to another aspect of the present invention, there is provided a pre-caching method for a web application in a terminal device that executes a web application composed of a plurality of pages, the method comprising the steps of: Analyzing a call relationship between pages constituting an application; Extracting and storing a page list having a high possibility of calling on the basis of the page currently being executed using the analysis result; And pre-caching one or more pages included in the stored page list.

In the pre-caching method for a web application according to the present invention, the step of analyzing a call relation between pages may include generating a table to store a page-to-page call frequency appearing during execution of a web application based on a result of analyzing a call relationship between the pages ; And updating the page-to-page calling frequency based on the page switching event result that occurs during execution of the web application.

The pre-caching method for a web application according to the present invention may further include checking whether a page switching event has occurred and deleting the stored page list when a page switching event occurs.

In the pre-caching method for a web application according to the present invention, the step of caching is characterized by setting the number of pages to be cached in consideration of an available memory.

The method of pre-caching for a web application according to the present invention may further include the step of analyzing and structuring the cached one or more pages into binary page data.

In addition, the present invention provides a computer-readable recording medium on which a program for executing the pre-caching method for the web application described above is recorded.

According to the present invention, in executing a web application composed of a plurality of pages in a terminal device, a page having a high possibility of being called based on the current page is cached in the cache memory in advance, When the page is cached, the data of the corresponding page cached in the cache memory can be directly fetched and output to the screen, so that the page switching speed can be improved. In addition, in executing a web application composed of a plurality of pages, there is an excellent effect that the overall execution performance of the web application can be improved by improving the switching speed between pages. In addition, the present invention can solve the disadvantage of the web application that the screen switching is slow compared to the existing native application by improving the execution performance of the web application, and as a result, it has an excellent effect of improving the user satisfaction with the web application have.

1 is a conceptual diagram for explaining a structure of a web application applied to the present invention.
2 is a block diagram for explaining a file structure of a web application according to the present invention.
3 is a diagram for explaining a process of executing a page of a web application according to the present invention.
4 is a block diagram showing a configuration of a terminal device according to the present invention.
5 is a block diagram showing the configuration of a control unit for processing pre-caching for a web application in a terminal device according to the present invention.
6 is a flowchart illustrating a pre-caching method for a web application according to an embodiment of the present invention.
FIG. 7 is a flowchart illustrating a detailed process of analyzing a page-to-page call relationship in a pre-caching method for a web application according to an exemplary embodiment of the present invention.
FIG. 8 is a diagram illustrating a table for managing call frequency between pages in a pre-caching method for a web application according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description and the accompanying drawings, detailed description of well-known functions or constructions that may obscure the subject matter of the present invention will be omitted. It should be noted that the same constituent elements are denoted by the same reference numerals as possible throughout the drawings.

First, a web application to be applied to the present invention will be described. 1 is a diagram for explaining a configuration of a web application according to the present invention.

Referring to FIG. 1, a web application according to an exemplary embodiment of the present invention operates on a page as a basic unit, and is composed of a plurality of pages 10-13. The plurality of pages 10-13 are linked with one or more other pages. In this embodiment, the page 10 is linked to another page 11, 12, and the page 12 is linked to another page 13. When such a web application is executed, when one page 10 is executed as a start page and an event for executing another page 11 or 12 occurs according to execution of the web application, the other page 11 or 12 .

These web applications package and manage the files constituting the plurality of pages 10 to 13. [

2 is a diagram for explaining a file structure of a web application. Referring to FIG. 2, the web application includes a content file 100 describing contents of a plurality of pages and an information file 200 describing information about the web application. . Here, the content file 100 includes a source file 110 and a resource file 120. The information file 200 includes a configuration information file 210 and a policy information file 220.

The source file 110 is a file written in a markup language, a style sheet, and a scripting language. The double style sheet and the script language can be optionally omitted. Each page 10-13 of the web application is represented by the source file 110 written in the above-described languages. Here, the markup language can be exemplified by Hypertext Markup Language (HTML), Extensible Hypertext Markup Language (XHTML), and Extensible Markup Language (XML). The markup language includes a plurality of tags, Attribute and general text. A style sheet describes a style, such as font, size, color, layout, etc., of pages 10 to 13 shown by tags, attributes, and text as a design attribute defined by a user, i.e., a style. A page using such a style sheet is displayed in the same manner as described in the style sheet in a display apparatus having a different screen resolution and in a browser of a different kind. This style sheet can exemplarily represent CSS (Cascading Style Sheets). A scripting language is a programming language, a language for dynamically controlling web applications. Typically, JavaScript (Java Script) can be exemplified.

The resource file 120 refers to various files other than the source file 110 inserted in each page 10-13 of the web application. This resource file 120 may be inserted into the pages 10-13 using a link tag through a programming language describing the source file 110. [ In addition, the resource file 120 may be stored in a device on the Web or a local device in which the web application is executed. An address (URL) that can be downloaded and accessed to the resource file 120 is a mark Up language. ≪ / RTI > The resource file 120 may include a scene description, a video, an audio, an image, a font, a text, a meta-data, and a script ) File can be exemplified. The resource file 120 may exist in various types other than those listed above, and may be a file of various formats.

The configuration information is the contents described in the configuration information file 210. The configuration information includes a list of files included in the corresponding web application, a disclosure status and a disclosure range for each file, and a setting value for setting an execution environment of the web application . Here, the execution environment describes specifications and settings required for a web application to be executed, and includes a screen size, a CPU, a clock speed of the CPU, an operating system, a buffer type and size for input and output .

The policy information is information described in the policy information file 220 and is information for designating a range of access authority for the corresponding web application to access the operating system of the terminal, for example, a hash code. The hash code is used to verify the integrity of the web application. The hash code can be used to confirm whether or not the corresponding web application is authorized to access the operating system of the terminal.

In addition, we will explain how each page of the web application is processed and executed. In general, a programming language can be classified into an imperative description language and a declarative description language. An imperative description language is a language that is described by emphasizing 'how' the solution is to be sought. It specifies the algorithm to be executed and does not specify the goal. Typically, traditional Fortran, C, Java, etc. correspond to the imperative description language. Conversely, a declarative description language is a language that is described with an emphasis on explaining what the 'solution' is, and it does not specify the algorithm and the goal. A source file 110 according to an embodiment of the present invention is written in a declarative description language. For example, if the source file 110 is written in HTML of a markup language, the tag and tag attributes of the HTML declare what to show in the HTML viewer, i.e., the browser. Accordingly, the procedural algorithm of the browser engine interprets the attributes of tags and tags and converts them into points to be displayed on the screen. To do this, the constituent elements (tags and attributes) of the source file 110 written in the declarative description language are parsed into meaningful tokens to analyze the hierarchical relationship between them, and then the sentence structure Constitute a previously determined parse tree. Each node in the parse tree can contain tags, attributes, and plain text, which declares what to show. Then, the declaration of each node is expressed according to the hierarchical relation of the tree structure. This will be described in more detail with reference to FIG.

Referring to FIG. 3, as described above, the source file 110 includes a markup language 111 and a style sheet 113. In addition, a script language may be included, but a description of a part for processing the script language will be omitted here.

In step S301, the markup language 111 and the style sheet 113 decompose the constituent components into meaningful tokens according to the interpretation method of the declarative description language, analyze the hierarchical relationship between them, Construct a parse tree. Here, the parse tree includes a Document Object Model (DOM) tree 310 and a style tree 320. That is, the markup language 111 is composed of a tag, an attribute of the tag, and a plain text. After the markup language 111 is decomposed, the DOM tree 310 is configured according to each hierarchical relationship. The style sheet 113 has a style that specifies the characters, margins, layout, and the like of the page 10 represented by the markup language 111, and the style sheet 113 is decomposed into a hierarchical relationship Thereby constructing a style tree 320 arranged in a tree structure.

Then, in step S303, the DOM tree 310 and the style tree 320 are combined to form a renderer tree 330. [ Then, in step S305, a layout suitable for the style is set through the analysis of the renderer tree 330, and the values of the respective attributes are arranged in the layout to generate the page data 340. [ This page data 340 is data before being rendered and displayed as page 10 on the screen.

Next, in step S307, the structure of the page data 340 is serialized and stored in a binary form. The page data stored in binary form is referred to as binary page data 350 in this manner. If the user requests to execute the page 10 in this state, the binary page data 350 is rendered and output in step S309. If necessary, step S307 of changing the data structure may be omitted. That is, the page data 340 can be directly rendered and output to the page 10.

Next, in executing the above-described web application, a terminal device that performs dictionary caching according to the present invention and a pre-caching method for the web application thereof will be described.

4 is a block diagram illustrating a configuration of a terminal device for performing pre-caching for a web application according to the present invention.

4, a terminal device according to the present invention includes a control unit 410, a storage unit 420, an input unit 430, a display unit 440, a communication unit 450, and an audio processing unit 460 .

In the present invention, the control unit 410 loads and executes a file of the web application stored in the storage unit 420 in response to a request for execution of the web application by the user, One or more pages having a high possibility of being cached are cached in the memory based on the page displayed on the current screen by analyzing the call relation between the plurality of pages included in the web application. More specifically, the control unit 410 includes a cache memory 411 to reduce memory access time. The cache memory 411 is a memory having a higher speed than a main memory having data of the most frequently used position in the main memory such as a RAM and copies frequently used data to the cache memory 411, The average memory access time can be reduced, thereby improving the execution speed. In this case, when the control unit 410 reads or writes data in the storage unit 420, the control unit 410 checks whether the corresponding data exists in the cache memory 411. If the data exists in the cache memory 411, And reads the data directly from the memory 411. Otherwise, it accesses the storage unit 420 and reads the data. In addition, in the present invention, while the web application is being executed, the control unit 410 analyzes a call relationship between a plurality of pages included in the web application, copies a page with a high possibility of being called into the cache memory 411 in advance, If a conversion event occurs, the cache memory 411 checks whether the corresponding page exists. If the page exists, the page data is fetched and displayed on the screen. If the cache memory 411 does not exist, The data of the page is fetched and displayed on the screen.

The storage unit 420 stores the data of the web application, that is, the web application package having the structure as shown in Fig. 2, as means for temporarily or permanently storing data in the terminal device. In the present invention, the storage unit 420 includes a main memory such as a RAM (Read Access Memory) and a storage such as a hard disk drive (HDD) or a flash memory. Here, the RAM takes time to access data stored at any position, and programs or data that is being executed in the terminal are loaded, and an auxiliary memory device such as a hard disk or a flash memory is accessed at a time There is a difference, the speed is slower than the memory, but the capacity is large, so data and programs are kept. In the present invention, the storage unit 420 stores a file of the web application. The file of the web application is substantially stored in the HDD or the flash memory, and is loaded into the memory at the execution request under the control of the control unit 410 .

The input unit 430 is a means for generating a user input signal corresponding to a user input. The input unit 430 includes a plurality of input keys and function keys for receiving numeric or character information and setting various functions. A user input signal is generated from the corresponding input key or function key and transmitted to the control unit 410. [ The input unit 430 may include at least one of a universal input device such as a keyboard, a mouse, and a touch pad. In addition, various input devices that are under development or are expected to be developed in the future may be included in the input unit 430 . In the present invention, the input unit 430 is used by the user to input an execution request of the web application.

The display unit 440 displays the execution result of the web application on the screen under the control of the control unit 410. [ In other words, a visual representation (e.g., a background, a menu, a photograph, a moving picture, a text, an icon, etc.) of the execution result of the web application is displayed. The display unit 440 may be implemented by an LCD (Liquid Crystal Display) or a touch screen. When the display unit 440 is implemented by a touch screen, the display unit 440 may perform some or all of the functions of the input unit 430.

The communication unit 450 is a means for performing communication by connecting to a network. Like a general web page, a web application can be executed in conjunction with a server via a network. Therefore, when the interworking with the server is requested according to the control of the controller 410, the communication unit 450 connects to the network and communicates with the server.

The audio processor 460 outputs an audio signal through the speaker SPK under the control of the controller 410 or converts an audible sound into an electrical audio signal through a microphone MIC and transmits the electrical audio signal to the controller 410 . Particularly, in the present invention, the audio processing unit 460 outputs audible parts (effect sound, background sound, etc.) in the execution result of the web application.

When a user input signal requesting execution of a web application is transmitted from the input unit 430 to the control unit 410 according to an input of a user, the control unit 410 controls the storage unit 420 And outputs the downloaded file through the display unit 440 and the audio processing unit 460. [ In addition, while the web application is being executed, the control unit 410 analyzes the calling relationship of each page constituting the web application, and displays one or more pages, which are likely to be called, on the page displayed on the current screen in advance in the cache memory 411 By copying, it is possible to improve the speed of page switching. In addition, the control unit 410 performs analysis and layout setting on one or more pages that are likely to be called, and stores the same in the form of the binary page data 350 shown in FIG. In this case, when the page switching event occurs, the binary page data 350 can be directly rendered and displayed on the screen, thereby further improving the execution speed.

FIG. 5 is a functional block diagram showing a configuration for performing pre-caching for a web application in the control unit 410 in the terminal device according to the present invention.

Referring to FIG. 5, the control unit 410 includes an analysis module 510, a prediction module 520, and an execution module 530.

The analysis module 510 analyzes the call relation between each page of the web application composed of a plurality of mutually linked pages. More specifically, the analysis module 510 analyzes the call relationship between the pages constituting the web application that is requested to be executed or executed, and stores the page-to-page call frequency appearing during execution of the corresponding web application . 8 shows an example of a table for storing the inter-page call frequency generated by the analysis module 510. The table includes a current page field indicating a page currently being executed, a switch indicating a page to be switched in the current page, Page field, and a count field for describing the frequency at which the conversion page is called in the current page. In this embodiment, the web application includes pages 1 to 5, wherein page 1 is linked to pages 2, 3, and 4, and page 2 is linked to pages 1, 5, A table such as 8 is created to represent this calling relationship. In the above, the calling frequency recorded in the number field is updated each time a page switching event is generated during execution of the web application. The analysis module 510 updates the calling frequency of the table as shown in FIG. 8 based on the page switching result when the page switching event occurs during execution of the web application. That is, the current page where the page switching event occurs and the called conversion page are extracted, and the calling frequency is increased in the number of times of the corresponding index in the table. Here, only the call frequency occurring during one execution of the web application may be measured, or the call frequency generated at the execution of the web application may be accumulated. In the latter case, the analysis module 510 generates a table by analyzing the page-to-page call relationship only once at the initial execution of each web application.

Then, the prediction module 520 extracts one or more pages which are likely to be called from the current page, based on the analysis result of the analysis module 510, and generates a page list. In this regard, in one embodiment of the present invention, the prediction module 520 determines the callability based on the frequency of calls between each page. That is, the prediction module 520 generates a page list by extracting a page having a high possibility of being called from the current page, based on the calling frequency recorded in the table configured in the analysis module 510. The page list can be arranged by arranging the pages in order of great possibility of calling. In the embodiment shown in Fig. 8, if the current page is page 1, page 3 is extracted as the page with the greatest callability, and then page 2, page 4 can be extracted in that order. In addition, if the page switching event occurs during execution of the web application, the prediction module 520 deletes the currently generated page list and generates a page list based on the converted page. That is, the page list is newly generated based on the current page every time the page is switched.

Lastly, the execution module 530 caches one or more pages included in the page list generated by the prediction module 520 in the cache memory 411. The caching is performed before the actual page call is made. Accordingly, when an actual page change event occurs, the control unit 410 accesses the cache memory 411 to check whether the called page exists, and if there is a page to be called, the control unit 410 reads the data of the corresponding page of the cache memory 411 So that it is possible to shorten the time required for accessing the storage unit 420. Particularly, when the page is stored as binary page data in the dictionary caching, the process of interpreting and layout setting process for the page can be omitted, and the screen switching speed can be further increased.

In addition, the execution module 530 can determine the number of pages to be cached in consideration of the amount of available memory in the cache memory 411 in caching a page with a high possibility of being called. That is, in the page list, caching is performed in an available memory range of the cache memory 411 in order of great possibility of calling.

Next, with reference to FIG. 6 and FIG. 7, a pre-caching method for a web application according to the present invention will be described according to an operation sequence.

6, when a user requests execution of a web application in a terminal device having a web application composed of a plurality of pages, the terminal device loads the corresponding web application file into a memory and executes the file (S610) The calling relationship between the pages constituting the web application is analyzed (S620). This can be done by analyzing the source file 110 of the web application and also by measuring the page calling frequency that appears during the execution of the web application. FIG. 7 is a flowchart illustrating the detailed procedure of step S620. Referring to FIG. 7, in operation S620, the terminal generates a table (see FIG. 8) for storing the inter-page call frequency using the call relationship between analyzed pages in the source file of the web application during execution (S710). That is, a callable conversion page is extracted for each page constituting the web application, and a table is formed by mapping as shown in FIG. When the table is initially created, all values of the calling frequency field are initialized.

Then, the terminal device confirms whether a page switching event occurs during execution of the web application (S720). As a result of the confirmation, when the page switching event occurs, the terminal extracts the information of the current page and the conversion page, and updates the calling frequency of the portion corresponding to the table (S730). The step S730 is repeatedly performed every time the page switching event occurs until the execution of the web application is terminated (S740), and the page calling frequency displayed during execution of the corresponding web application is measured.

6, after performing step S620 or performing step S620, the terminal extracts and stores a page list having a high possibility of calling based on the page currently being executed (step S630).

Then, the terminal apparatus caches one or more pages included in the stored page list (S640). That is, the data of the corresponding page in the storage unit 420 is copied to the cache memory 411 of the control unit 410 (S640). When the page copied to the cache memory 411 is called by the user, the page can be directly read and displayed by the control unit 410 of the terminal device. In addition, in step S640, caching is performed in consideration of a usable memory amount of the cache memory 411. [ That is, consider callability and available memory. In addition, in step S640, when the one or more pages are cached, the terminal device may analyze and structure the one or more pages in advance, change the binary page data to binary page data, and store the binary page data in the cache memory 411. According to this, when the corresponding page is actually called, rendering can be performed directly without analyzing and structuring the page, so that the screen switching speed can be further improved.

In addition, the terminal device further checks whether a page switching event occurs during the execution of the web application (S650). If the page switching event occurs as a result of the confirmation, the terminal device generates a page list corresponding to the converted page The page list is deleted (S660).

The above-described steps S630 to S660 are repeated until execution of the corresponding web application is terminated (S670).

The pre-caching method for a web application according to the present invention may be implemented in a form of software readable by various computer means and recorded in a computer-readable recording medium. Here, the recording medium may include program commands, data files, data structures, and the like, alone or in combination. Program instructions to be recorded on a recording medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. For example, the recording medium may be an optical recording medium such as a magnetic medium such as a hard disk, a floppy disk and a magnetic tape, a compact disk read only memory (CD-ROM), a digital video disk (DVD) Includes a hardware device that is specially configured to store and execute program instructions such as a magneto-optical medium such as a floppy disk and a ROM, a random access memory (RAM), a flash memory, do. Examples of program instructions may include machine language code such as those generated by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like. Such a hardware device may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, It will be apparent to those skilled in the art. Furthermore, although specific terms are used in this specification and the drawings, they are used in a generic sense only to facilitate the description of the invention and to facilitate understanding of the invention, and are not intended to limit the scope of the invention.

The present invention can be applied to web application execution in a terminal device. In executing the web application in which the terminal device is constituted by a plurality of pages, the terminal device caches a page having a high possibility of calling based on the current page, By storing, when the next page is called during the execution of the web application, it becomes unnecessary to access the local storage such as the hard disk or the flash memory, so that the actual page conversion can be performed more quickly. In addition, By improving the page-to-page switching speed, overall execution performance of the web application can be improved. In addition, by improving the execution performance of the web application, it is possible to improve the disadvantage of the web application that the screen switching is slower than the existing native application, and it is possible to improve user satisfaction through the improvement.

410:
420:
430:
440:
450:
460: Audio processor
510: Analysis module
520: prediction module
530: Execution module

Claims (18)

An input unit for outputting a user input signal corresponding to a user input;
A storage unit for storing a file of a web application composed of a plurality of interconnected pages; And
Wherein when a web application is requested to be executed through the input unit, the storage unit loads and executes a file of the web application, analyzes a call relationship between a plurality of pages included in the web application when the web application is executed, And a control unit for pre-caching one or more pages which are likely to be called based on the reference. The apparatus of claim 1, wherein the control unit
An analysis module for analyzing a call relation between respective pages of a web application composed of a plurality of mutually linked pages;
A prediction module for extracting one or more pages that are likely to be called from the current page and generating a page list based on the analysis result of the analysis module; And
And an execution module for previously caching one or more pages included in the page list generated by the prediction module. 3. The system of claim 2, wherein the analysis module
And generates a table for storing the frequency of inter-page calls using the analysis result. 3. The apparatus of claim 2, wherein the prediction module
Wherein the calling frequency of each page is measured using the page switching result during execution of the web application and the calling possibility is determined based on the calling frequency. 3. The apparatus of claim 2, wherein the prediction module
Deletes the currently generated page list when a page change event occurs, and generates a page list again based on the converted page. 3. The system of claim 2, wherein the execution module
And determines the number of pages to be cached in consideration of the available memory. The apparatus of claim 1, wherein the control unit
Wherein the one or more pages having a high possibility of calling are analyzed and structured to be converted into binary page data and stored. The method of claim 1, wherein the web application
A content file describing the content of the web application, and an information file describing information about the web application. 9. The method of claim 8,
A source file representing each page of the web application, and a resource file linked to the source file by a link. 10. The method of claim 9,
And a script language for dynamically controlling the web application. The method of claim 1, wherein the attribute of the tag is an attribute of the tag, Terminal device. The method of claim 9, wherein the resource file
A scene description, a video, an audio, an image, a font, a text, a metadata, and a script file. The information processing apparatus according to claim 8,
A configuration information file describing configuration information including a list of files included in the web application, a disclosure status and a disclosure range for each file, and a setting value for setting an execution environment of the web application,
Wherein the web application includes a policy information file describing policy information for designating a range of access rights to access the operating system of the terminal. A pre-caching method for a web application in a terminal device that executes a web application composed of a plurality of pages,
Analyzing a call relationship between pages constituting a web application when the terminal device executes the web application;
Extracting and storing a page list having a high possibility of calling based on a page currently being executed using the analysis result; And
And pre-caching one or more pages included in the stored page list. 14. The method of claim 13, wherein analyzing the call relationship between the pages comprises:
Generating a table to store a page-to-page call frequency appearing during execution of the web application, based on an analysis result of the call relationship between the pages;
Updating the page-to-page calling frequency of the table based on page switching event results that occur during execution of the web application. 14. The method of claim 13,
Further comprising checking whether a page change event has occurred and deleting the stored page list when a page change event occurs. 14. The method of claim 13, wherein the caching comprises:
And the number of pages to be cached is set in consideration of the available memory. 14. The method of claim 13,
Analyzing and structuring the cached one or more pages into binary page data. ≪ Desc / Clms Page number 21 > A computer-readable recording medium recording a program for executing a pre-caching method for a web application according to any one of claims 13 to 17.

Images