KR101482150B1 - Web application executable device and web application management method therof - Google Patents

Abstract

The present invention relates to a web application execution apparatus and a web application management method thereof, and it is an object of the present invention to provide an environment in which a web application can be executed using resources and functions of a terminal regardless of the type of an operating system installed in the terminal, To install, run, and update the included web application on a per-application basis rather than on a page-by-page basis. According to the present invention, upon receipt of an execution request for a web application including web application identification information in the form of a URL (Uniform Resource Location), it is checked whether a web application identified by URL-type web application identification information exists in the local storage , And if the web application exists in the local storage, executes the web application stored in the local storage.

Description

[0001] DESCRIPTION [0002] WEB APPLICATION EXECUTION DEVICE AND WEB APPLICATION MANAGEMENT METHOD [

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a web application management method and apparatus for executing a web application in a terminal, and more particularly, to a web application management method and apparatus for managing a web application including a plurality of pages, And a method for managing the web application.

Recently, an open application and a platform environment have been required for differentiating services while providing an open environment for a mobile communication terminal.

More specifically, a smartphone capable of freely selecting and installing a desired mobile application is rapidly growing, and an OMP (Open Market Place) capable of freely trading such a mobile application is being activated.

However, since various types of operating systems are currently used in smartphones, application developers must develop mobile applications in consideration of various types of operating system environments.

More specifically, an operating system manages resources and functions of a terminal that is itself ported, and when an application (application) implanted in the terminal requests the resources and functions of the terminal, May access some or all of the application. This is accomplished by the operating system providing an application programming interface (API). In other words, the application refers to the API provided by the operating system to access the resources and functions of the device. Therefore, in order to develop an application of a device to which a specific operating system is implanted, developers must develop it in accordance with the format of the API provided by the operating system. In a situation where various operating systems are used, .

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 web application platform supporting a standard web technology is implemented in a mobile communication terminal, it is possible to develop a web application more easily by using the existing rich web developer base and a web development tool, and in addition, It can be developed and provided easily and quickly.

The present invention provides an environment in which a web application can be executed using resources and functions of a terminal irrespective of the type of an operating system installed in the terminal, and a web application including a plurality of pages is installed, And a method for managing the web application.

The present invention provides, as means for solving the problems, a web application execution apparatus including an implantation layer unit, a browser engine layer unit, and a web application runtime layer unit. The transplantation layer supports a single type of transfer layer API (Application Programming Interface) capable of handling a request for function execution supervised by the operating system regardless of the type of the operating system. When a specific transfer layer API is called, API is called to return the response. The browser engine layer part interprets and executes each page of the web application in conjunction with the port layer. The web application runtime layer receives a web application execution request including web application identification information in the form of a URL (Uniform Resource Location), confirms whether the web application exists in the local storage, and if a web application exists in the local storage , It transmits an execution command of the web application to the browser engine layer unit and provides the network and the UI necessary for executing the page in the browser engine layer unit.

In the web application execution apparatus according to the present invention, the URL-type web application identification information includes a protocol schema defined to fetch and execute the web application stored in the local storage, a domain name of the web application manufacturer providing the web application, , And the file name of the web application.

In the web application executing apparatus according to the present invention, the web application may include web content composed of a source file constituting a plurality of pages included in the web application and a resource file including an image inserted into the page, A list of resources included in the web application, configuration information including information on the disclosure of each data, integrity information on the data such as a hash code, execution environment information of the web application, and a range of terminal resources that the web application can access And the like.

In the web application execution device according to the present invention, when the web application does not exist in the local storage, the web application runtime layer checks whether or not the web application is downloaded from the user, and when the user selects download, And downloading and installing the web application.

The web application execution apparatus according to the present invention includes a browser engine layer unit, an application layer unit, and a web application runtime layer unit. The web application execution unit executes a web application runtime layer or a browser engine layer And a layer unit.

The web application execution apparatus according to the present invention verifies a certificate before installation, execution, or loading of a plug-in that invokes resources of the terminal and functions of the operating system other than the web standard in the web application and the browser engine layer, And a security layer for controlling access to the transplantation layer during execution of the web application.

In the web application execution apparatus according to the present invention, the browser engine layer unit may include a browser engine module for interpreting and executing each page of the web application written in the web standard language; A plug-in management module for downloading and installing at least one plug-in, managing a list of installed plug-ins, updating, and processing a call request of the plug-in; And one or more plug-ins installed by the plug-in management module and operating through the plug-in management module, each of the plug-ins calling the functions of the resources and the operating system of the terminal other than the web standard through the porting layer and returning a response thereto .

In the web application execution apparatus according to the present invention, the porting layer unit may include an HTTP module providing an HTML related function and API, an XML module providing an API for an XML parsing function, a thread function provided in an API form, A Thread module that bi-passes the provided functions, a UI backend module that provides the native window system functions necessary for UI (UI) implementation in an API form, and a security storage function in the form of an API Security storage module, a resource module that provides an access interface to the terminal resource in the form of an API, an OS API module that provides an OS API provided by the terminal in addition to the terminal resource, and an API function in an API form Collaboration module, interworking interface with synchronization application existing in external device, API type Providing a synchronization (Sync) module, a local storage, which may include one or more of the local storage (Local Storage) module for providing the API form.

In the web application execution device according to the present invention, the web application runtime layer may include a web application runtime module for performing context management and event handling of the web application instance and command processing from the execution layer; A registry module for managing installation information of the web application and the plug-in and structure information of the web application execution device; A UI engine for processing UI (User Interface) and user input for a screen area other than the area rendered in the browser engine layer; A network selector for setting and managing a network to be used in the web application execution device; And a dynamic synchronization module that stores data while the network connection is disconnected in the local storage while the web application is running and synchronizes data stored in the local storage and external data when the network is connected.

In the web application execution apparatus according to the present invention, the execution layer includes: a container agent that operates the dummy execution module according to a request for execution of a web application through a shortcut icon or a native menu of the terminal; A dummy execution module, which is operated by the container agent and forwards the web application execution command to the web application runtime execution layer after loading the web application runtime execution layer, the browser engine layer, and the porting layer; And a standby mode agent that is loaded by the native standby screen manager and forwards the web application execution command on the standby screen to the web application runtime layer.

In the web application execution device according to the present invention, the security layer may include an authentication module for verifying the certificate of the web application and the plug-in when the web application and the plug-in are installed or executed; And a policy module that controls access to the port layer during execution of the web application according to an access control rule.

In the web application execution apparatus according to the present invention, one or more plug-ins may include a resource plug-in for transferring a function call related to the terminal resource to the transplantation layer unit, a terminal OS API calling function of the web application to the transplantation layer, A system API plug-in for providing an access interface to the function of the application runtime layer, a collaboration plug-in for transferring a function call for interworking between the web application to the transplantation layer, And a Sync plug-in for transferring the synchronization message to the layer unit.

In the web application execution apparatus according to the present invention, the web application runtime module may include a command handler for receiving a command related to the execution of the web application from the execution layer and interpreting the command, and instructing the command to be executed; A context manager for controlling creation and destruction of a native window and a renderer for each web application according to an instruction of a command handler or a browser engine layer; An event handler for processing a system-related event of a native window and a web application execution device generated by the context manager, and transmitting the event to the UI engine so as to give a UI effect when an event related to a predefined situation occurs for the window; And a lifecycle manager for managing a web application including a plurality of pages and a life cycle for each page of the web application.

In the web application execution apparatus according to the present invention, the registry module includes a web application URL, which is web application identification information in the form of a URL, and a content URL, which indicates the location of the local storage in which the web application actually identified by the web application URL is stored And a web application installation information management table including a hash code for verifying the integrity of the web application and policy information for access control of the web application.

In addition, as another means for solving the problem, the present invention provides a terminal equipped with the web application execution apparatus described above.

According to another aspect of the present invention, there is provided a web application receiving method comprising: receiving an execution request of a web application including URL-type web application identification information; Confirming whether a web application identified by URL-type web application identification information exists in the local storage; And executing the web application stored in the local storage when the web application exists in the local storage.

According to another aspect of the present invention, there is provided a method of managing a web application, the method comprising: outputting an error message indicating that a web application requested to be executed does not exist to a user and confirming whether the web application is to be downloaded; If the user selects to download, converting the web application identification information in the form of URL into a URL accessible via the network; And a step of accessing a web server on the network using the converted URL, downloading the web application, and installing the web application on the local storage of the terminal.

In the web application management method according to the present invention, the URL-type web application identification information includes a protocol schema defined to fetch and execute the web application stored in the local storage, a domain name of the web application manufacturer providing the web application, , And the file name of the web application.

In the web application management method according to the present invention, the web application may include a source file constituting a plurality of pages included in the web application in accordance with a web standard, web content composed of a resource file including an image inserted into the page, A list of resources included in the web application, configuration information including information on the disclosure of each data, integrity information on the data such as a hash code, execution environment information of the web application, and a range of terminal resources that the web application can access And the like.

In the web application execution apparatus according to the present invention, the step of executing the web application may include: generating a native window and a renderer instance for the web application in accordance with a browser engine layer of the browser engine container core requesting execution of the web application; Parsing, laying out and rendering a designated page among the pages included in the web application and outputting the page to the generated native window; Extracting one or more other pages included in the web application other than the output page; Performing parsing and layout assignments for one or more other pages; Serializing data of other pages processed until the layout is specified and storing the serialized data as a binary file; Confirming occurrence of an event for another page; And when the event occurs, rendering the stored binary file and outputting the rendered binary file to the native window.

In the web application management method according to the present invention, when receiving an execution request of the web application, the execution layer receives whether or not the browser engine container core is executed Checking; Loading the browser engine container core if the browser engine container core is not running; And if the browser engine container core is running, transmitting an execution command for the web application to the web application runtime layer of the browser engine container core.

In the method of managing a web application according to the present invention, receiving an execution request of a web application may include: calling an execution API through a web application manager managing the web application; Loading a system API plug-in in which a browser engine container core provides an access interface to a core function; And loading the loaded system API plug-in with an execution command for the web application to the context manager of the web application runtime layer.

In the web application management method according to the present invention, the step of receiving an execution request of the web application may include the steps of: receiving a web application execution request of the user from the native standby screen manager and loading a standby mode agent of the execution layer; And a standby mode agent loading the browser engine container core, calling the idle screen mode execution API, and delivering an execution command for the web application to the context manager of the web application runtime layer.

In the web application management method according to the present invention, the step of downloading the web application and installing the web application on the local storage of the terminal includes: downloading the web application by accessing the web server; Calling a registry method into the browser engine layer; Calling a system API plug-in to call the registry module of the web application runtime layer in the browser engine layer; Invoking a system API plug-in to invoke a registry module of the web application runtime layer; And the called registry module extracts installation information from the downloaded file and stores it in the secure storage, and storing the web contents in the local storage.

The web application management method according to the present invention checks the certificate of the web application before installation or execution of the web application and allows the installation or execution of the web application to continue when the certificate verification succeeds. If the certificate verification is not successful , And allowing the user to confirm whether to continue installation or execution.

In the web application management method according to the present invention, in the step of executing the web application, when access to the port layer is required, the access control rule set for each web application is referred to, The method comprising the steps of:

In addition, as another means for solving the problem, the present invention provides a computer-readable recording medium on which a program for executing the above-described web application management method is recorded.

According to the present invention, an interface for executing a function having a different format according to an operating system is provided in a single format regardless of the type of an operating system, so that a web application executes a function of a terminal managed by the operating system in the same manner, The web application can be used in the same manner as the standalone application by managing the web application composed of a plurality of pages to be installed, executed and updated in increments of applications, not page units.

In addition, by applying this to a mobile communication terminal, application developers for a mobile communication terminal can more easily develop an application of the mobile communication terminal by using the existing rich web developer base and the web development tool.

1 is a block diagram showing the overall structure of a web application execution apparatus according to the present invention.
2 is a block diagram showing a package structure of a web application according to the present invention.
3 is a view showing metadata information of a web application managed by the web application execution apparatus according to the present invention.
4 is a flowchart illustrating a method of managing a web application according to the present invention.
5 is a message flow diagram illustrating a process of downloading and updating a web application in the web application management method according to the present invention.
FIG. 6 is a flowchart illustrating a process of executing / installing / loading a security-applied web application in the web application management method according to the present invention.
7 to 9 are flowcharts illustrating various embodiments of a web application execution process in a web application management method according to the present invention.
10 is a flowchart illustrating a process for improving the execution speed of the web application in the web application management method according to 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.

In addition, terms and words used in the present specification and claims should not be construed to be limited to ordinary or dictionary meanings, and the inventor should properly define the terms of a term in order to describe its own invention in the best way possible. It should be construed as meaning and concept consistent with the technical idea of the present invention. Therefore, the embodiments described in the present specification and the configurations shown in the drawings are merely the most preferred embodiments of the present invention, and not all of the technical ideas of the present invention are described. Therefore, It is to be understood that equivalents and modifications are possible.

First, a web application execution apparatus according to the present invention will be described. The web application execution apparatus according to the present invention operates on the operating system of the terminal and processes downloading, installation, and execution of the web application. Such a web application execution device may be implemented by software, hardware, a combination of software and hardware.

1 is a diagram illustrating an overall structure of a web application execution apparatus according to an embodiment of the present invention.

1, the web application execution apparatus includes a porting layer 200, a security layer 300, a web application runtime layer 400, A browser engine layer 500, an executable layer 600, and one or more system web applications 700. The browser engine layer 500 includes a plurality of application programs.

Here, the security layer unit 300, the web application runtime layer unit 400, and the browser engine layer unit 500 are implemented as a browser engine container common module. Here, the web application runtime layer 400 mainly manages the web application, and the browser engine layer 500 interprets each page of the web application and outputs it to the screen. The browser engine container common is independent of the operating system 100 and has dependency only on the portability layer 200.

The browser engine container common includes the browser engine container common and the porting layer 200, and is implemented as a browser engine container core.

The browser engine container core is a multi-tasking container that supports simultaneous execution of multiple web applications and multi-instance for a single web application. The browser engine container core can execute a plurality of containers in one system, .

That is, the browser engine container core creates a window each time a web application is executed, creates a renderer instance, and executes a default page or a request page of the web application.

At this time, the execution layer 600 operates as an entry point of the browser engine container core. The browser engine container core is executed by the execution layer 600 to execute the system web application 700 and other web applications.

Referring to FIG. 2, a web application executed by the present invention includes a plurality of pages, which are bundled and operated together. The web application includes html, xhtml, css, and java script files constituting each page constituting the web application A web content 11 composed of a resource file such as an image to be inserted into the page, a list of data contained in the web application package, integrity information on each piece of data, (Configuration file) 12 including execution environment information of the application (screen size, target CPU, target OS, version of the web application execution device, and the like), and a range of terminal resources that the web application can access And policy information 13 for specifying the policy information. The policy information 13 may include basic access authority information given to the entire web application package and detail access authority information assigned to each page of the web application. The policy information 13 may include resources of the terminal, for example, Address book, terminal functions, and call records. The web application including the web content 11, the configuration information 12, and the policy information 13 is provided in the form of a compressed file, and a certificate proving that the web application is distributed through an authorized organization or a provider As shown in FIG.

The web application execution apparatus according to the present invention identifies such web application through identification information in the form of URL (Uniform Resource Locators).

Typically, a web browser accesses web resources through a protocol scheme such as file: //, http: //, or https: //. Here, file: // means to fetch the web resource of the corresponding URL from the file system, and http: // and https: // to fetch the web resource of the corresponding URL from the network. The web application execution apparatus according to the present invention additionally sets a protocol schema httpa: // for processing the web application. httpa: // means that the web application identified by the URL should be retrieved from local storage and executed.

In addition, in the present invention, the URL of the web application may further include a domain name of a manufacturer of the web application or a content provider providing the web application. The domain name thus included can be used to download the corresponding web application later.

In other words, in the web application execution apparatus according to the present invention, the URL of the web application is composed of a protocol schema, which means execution of the web application, a domain name of the web application manufacturer or the content provider, and a web application name. For example, if the web application name is application1.swa and the domain name of the content provider is www.abc.com, the URL may be expressed as http: //www.abc.com/application1.swa. Here, the extension "swa" is an extension indicating that the web application package is an arbitrarily designated name.

This method of managing the web application differently from other web resources will be described later in more detail.

1, the detailed configuration and functions of each component of the web application execution apparatus according to the present invention will be described.

First, the transplanting layer unit 200 is implemented on the operating system 100 installed in the terminal, and is directly connected to the operating system 100 and is connected to the web application runtime layer unit 400 and the browser engine layer unit 500 Module is independently implemented in the operating system 100, and provides a terminal resource and an OS function to be used.

More specifically, the web application including the system web application 700 may access the operating system 100 through the browser engine container common module and the porting layer 200. When the web application desires to execute the function of the terminal, the browser engine layer unit 500 transmits the request to the transplantation layer unit 200, and the transplantation layer unit 200 transmits the request to the operating system 100 . At this time, the transplantation layer unit 200 converts the request according to the interface of the operating system 100, and transfers the request to the operating system 100. Accordingly, the operating system 100 executes a function requested by the web application or provides resources of the terminal to the web application.

The interface connected to the operating system 100 of the porting layer unit 600 is implemented separately for each operating system 100 and the interface provided to the parent browser engine container common module (hereinafter referred to as the porting layer API) do. Accordingly, the web application can access the functions of the terminal resources or the OS by using the same type of interface regardless of the type of the operating system 100.

The transplantation layer unit 200 includes a plurality of interface modules, and each interface module is implemented in a library form and can be freely added. The interface module included in the porting layer 200 includes an HTTP module for providing functions and APIs related to HTTP and HTTPS, an XML module for providing an API for an XML parsing function, and a thread function in an API form. A thread module that bi-passes the provided functions, a UI backend module that provides the window system functions necessary for the UI implementation in an API form, a secure storage ) Resource module (for example, a phone book, a photograph, a call record, an SMS list, and the like) in API form, an OS API provided by the terminal in addition to the terminal resource , SMS transmission, property setting of the terminal system, etc.) as an API type, a collaboration module for providing interworking functions between web applications in API form, (Sync) module for providing an interface for interworking with a synchronization application existing in a secondary device in an API form, and a local storage module for providing a local storage function existing in an operating system in an API form. have.

Next, the security layer unit 300 will be described.

The security layer unit 300 is for increasing the security level by controlling access to the transplantation layer unit 200 for another module in the web application execution unit and includes an authentication module 310, ) ≪ / RTI >

The authentication module 310 is installed in the web application and the browser engine layer unit 500 so that upon installation or execution or loading of the plug-in processing access to the transplantation layer 200, the web application and plug- Authenticates whether the web application and the plug-in are legitimately distributed, and enables the legitimately distributed web application and the plug-in to be installed and executed in the terminal.

The policy module 320 controls the access of each web application to the transplantation layer 200 according to the access control rules so that only the web application having the access authority can access the terminal resources and the OS functions. For this, the policy module 320 receives the access control rule through the updater 612 of the execution layer 600 and installs the access control rule. For the access request from the browser engine layer unit 500, the stored access control rule is searched for and granted or denied access according to the corresponding access control rule.

Next, the web application runtime layer unit 400 will be described.

The web application runtime layer unit 400 manages the execution environment of the web application and provides the network and the UI necessary for executing the respective pages of the web application in the browser engine layer unit 500 to be described below. More specifically, the web application runtime layer 400 manages instances of the web application, manages installation of the web application, management of configuration information, and management of the user interface. To this end, the web application runtime layer 400 includes a web application runtime module 410, a registry module 420, a UI (User Interface) engine 430, a network selector 440), and a dynamic synchronization module (450).

The web application runtime module 410 performs context management, event handling, and command processing from the execution layer 600 of the web application instance. The web application runtime module 410 includes a command handler 411, a context manager 412, an event handler 413, a lifecycle manager 412, (414). The command handler 411 receives a command related to the execution of the web application from the execution layer 600 via the IPC (Interprocess Communication), analyzes the command, and instructs the corresponding module to perform the operation. The command handler 411 is an IPC command processor. The commands processed by the command handler 411 may include execution / termination of the web application, updating of the configuration information related to the web application execution device, execution and termination of the web application execution device, and installation / uninstall / update of the plug-in have. That is, the command handler 411 requests execution and termination of the web application to the context manager 412 according to the analyzed command, and updates the configuration information of the web application execution device through the registry module 420. The command handler 411 may request the plug-in management module 520 of the browser engine layer unit 500 to install, delete, or update the plug-in 530.

The context manager 412 manages the contexts of web application instances, and controls creation and destruction of windows and renderers for each web application. More specifically, according to a command for executing a web application transmitted from the command handler 411 and the browser engine module 510, and a window generation command transmitted from the browser engine module 510, Generates the instance, and receives the rendering result of the page requested to be executed from the browser engine module 510 and outputs the result to the window. In addition, according to the web application end command transmitted from the command handler 411 and the window destruction command transmitted from the event handler 413 and the browser engine module 510, the resources of the renderer and the window are organized, the window is destroyed, When all the windows owned by the web application are destroyed, the corresponding web application is terminated.

The event handler 413 receives an event related to the window generated by the context manager 412 and a system related event extended by the web application execution device. In addition, when an event related to a predefined situation occurs so as to give a UI effect when switching between pages in a window or between windows, the event is transmitted to the UI engine 430. At this time, since the event related to the browser engine module 510 is handled directly by the browser engine module 510, the event handler 413 does not process the event related to the browser engine module 510.

The lifecycle module 414 manages the life cycle of the web application. As described above, a web application is composed of a plurality of pages, in which each page of the web application is initiated by a visit and is terminated each time it is switched to another page. The web application is started by creating one window for each web application in response to the execution request of the execution layer 600 or another web application or native application. When the user closes all windows related to the web application, When a close request occurs and all windows are closed, it is terminated. In addition, even if another web application or an external page is loaded while only one window is created by the instance of the web application, the process is terminated. The lifecycle module 414 manages the life cycle for each page of the web application.

Next, in the web application runtime layer 400, the registry module 420 manages the installation information of the web application and the configuration information of the web application execution device. Here, the installation information and the configuration information are stored in the secure storage area of the terminal through the transport layer unit 200. In addition, the installation information of the web application can be registered at installation of the web application or registered at the terminal binary packaging.

3 is a diagram illustrating a configuration of an installation information management table of a web application managed by the registry module 420. As shown in FIG. Referring to FIG. 3, the installation information of the web application includes a web application URL, which is unique information for identifying a web application, a content URL, which is a path of a local storage where a web application actually divided by the URL is stored, A hash code for integrity verification of the web application, and access right information for access control of the web application. This information is extracted by the registry module 420 at the time of downloading the web application and stored in the secure storage area of the terminal.

In addition, the registry module 420 manages web application contents such as installation, deletion and update of a web application, setting of the attributes of the web application, extraction and provision of authentication information of the web application, Module management including inter-dependency management, attribute setting function of a web application execution device, and management function of installation information of a plug-in. The registry module 420 provides an API for installing, deleting, and updating web application execution devices.

Next, the UI engine 430 processes UI and user input to an area other than the area rendered by the browser engine module 510. [ Specifically, it handles processing for the remaining area other than the area where the page of the web application is outputted, from among the entire screen of the terminal, and may include a status bar for displaying the execution status and a soft button area for user input . At this time, since the annunicator area for indicating the signal reception strength, the availability of the communication, the battery remaining amount, etc. of the antenna in the mobile communication terminal may not allow customization according to the type of the operating system 100, . In addition, the UI engine 430 executes a plurality of web applications at the same time, and when a separate window is created and allocated for each web application, the switching between the windows is performed through the window module of the terminal. That is, the UI engine 430 processes functions related to the UX (user experience) through the organic operation between the context manager 412 and the UI backend module provided by the transplantation layer 200. In addition, the UI engine 430 provides a dynamic effect when switching between screens and screens during execution of a web application. These transition effects can be implemented using Web standards technologies (eg HTML, CSS, JavaScript). In addition, in order to vividly provide a complex and colorful screen transition effect to the user, the UI engine 430 can provide a screen transition effect executed in the native code level in a plug-in form.

Next, the network selector 440 sets and manages a network to be used in the web application execution apparatus. For this purpose, the network selector 440 receives a selection method and priority for a network (e.g., modem, Wi-Fi, Bluetooth, etc.) Here, the selection method can provide three options of automatic, manual, and semi-automatic, and automatic attempts to connect to a possible network according to the set priority, and manual attempts to access only the network selected by the user , Semi-Automatic will pop up a pop-up every time a network switch is required and let the user select it.

The dynamic synchronization module 450 is a means for ensuring execution of a seamless web application regardless of whether the terminal is on-line or off-line. More specifically, the dynamic synchronization module 450 allows a web application that accesses external data to run through a cache mechanism when the network connection is disconnected, and when connected to the network, And automatically synchronizes the data with the external data in the background while the user does not recognize it.

Next, the browser engine layer unit 500 will be described.

The browser engine layer unit 500 is a layer for executing parsing / rendering and JavaScript interpreting for each page of the web application and includes a browser engine module 510, a plug-in module 520, , And one or more plug-ins (530). Among them, the browser engine module 510 interprets and executes a web application written in a web standard language such as HTML, CSS, and JavaScript. The browser engine module 510 includes a web core 511 for processing a web standard language and a script core (ScriptCore) 512 for processing a script language. As described above, by configuring the web core 511 and the script core 512 as modules, updating and replacement for each module becomes easy. The script core 512 is preferably configured to prohibit cross references between web applications in order to prevent hacking and the like. Such a browser engine module 510 can be implemented with Webkit, an open source-based browser engine. In this case, it is desirable to optimize the Webkit code according to the environment of the terminal, which is different from the PC environment and has a limitation on the processing capability of the processor and the network bandwidth.

In addition, the browser engine module 510 accesses the operating system 100 and the terminal resources through the porting layer 200 when the terminal resource is used while executing the web application. More specifically, the browser engine module 510 may include a protocol processor, an XML processor, a window processor, a Font processor, an Image Decoder processor, an Internationalization processor, and a System processor . The protocol handler provides HTTP and HTTPS protocol functions and provides management functions such as uploads, proxies, and cookies required for HTTP function operations. The XML processor provides an XML parser function and an XSLT XML transformation function. The window processor provides a window system to be used by the browser engine module 510 and provides a UI widget such as a button, a list box, a combo box, and a text editor to be used by the web core 511. The font processor provides a font system for use by the web core 511. The image decoder processor provides an image decoder function to be used by the web core 511. The internationalization processor provides the string conversion function necessary for multilingual processing. The system handler provides system functions such as a timer. In addition, the browser engine module 510 performs basic functions necessary for the functions of the protocol processor, the XML processor, the window processor, the font processor, the image decoder processor, the internationalization processor, and the system processor, And is obtained from the operating system 100.

In addition, web applications should be able to use terminal resources such as address book or terminal applications in addition to web standard functions. To this end, the browser engine layer 500 further includes a plug-in module 520 and one or more plug-ins 530 to invoke terminal-dependent functions. Accordingly, when implementing the browser engine module 510, processing of the terminal dependent functions is performed through the plug-in module 520 and the one or more plug-ins 530, so that in the implementation of the browser engine module 510, Can be applied to a web application execution device without a large modification. In addition, future enhancements can be made easier by adding new functions that can be provided in the future as plug-ins.

The plug-in module 520 downloads and installs a plurality of plug-ins 530, manages the list of installed plug-ins, updates, and responds to plug-in call requests of web applications. Here, the download request and the update request of the new plug-in are generated by the updater 612 included in the execution layer 600, and the request is transmitted to the plug-in module 520 through the web application runtime layer 400 do. The plug-in module 520 receiving the download request downloads the plug-in package according to the OMA download standard and stores the plug-in installation information in the secure storage area of the terminal through the registry module 420. The plug-in module 520 includes a browser-side API that the browser must provide to the plug-in and a plug-in API that the plug-in must provide to the browser, and the plurality of plug-ins 530 call the browser- And the browser engine module 510 calls the plug-in API to perform the operation.

The one or more plug-ins 530 call resources and operating system functions of the terminals other than the web standard required by the web application and transmit a response thereto to the browser engine module 510. One or more plug-ins 530 may include a resource plug-in for transferring a function call related to the terminal resource of the web application to the resource module of the transplantable layer 200, and a terminal OS API calling function of the web application to the transplantation layer 200 OS API module and provides a system API plug-in that provides an access interface for functions of the web application runtime layer 400, and a call and response function for a function for interworking between a web application and a native application installed in the terminal And a synchronization plug-in for handling calls and responses of functions related to synchronization of the web application. In addition, plug-ins for various other functions can be added as needed.

In the web application execution apparatus according to the present invention, the terminal resources that can be accessed through the plug-in module 520 and the one or more plug-ins 530 include, for example, a photograph, an address book, You can include methods and properties related to log retrieval.

Next, the execution layer 600 will be described.

The execution layer 600 serves as an entry point of the browser engine container core and operates in the form of a single instance. The execution layer 600 may be implemented as an executable file of a native OS or as a DLL. At this time, in order to increase the portability, the execution layer 600 accesses the operating system 100 using the porting layer 200 as much as possible even in a native OS application. According to this, it is possible to have source level portability in any operating system.

The execution layer unit 600 loads and executes a browser engine container core including the above-described porting layer unit 200, the security layer unit 300, the web application runtime layer unit 400 and the browser engine layer unit 500 Sends a web application execution command according to a user's request to the web application runtime layer 400 or the browser engine layer 500 and confirms module-specific update of the web application execution device by SMS push or self check Pass the relevant download request to the appropriate module. In particular, an update to the plug-in 530 included in the browser engine layer unit 500 is checked, and the download request is transmitted to the plug-in module 520. The execution layer 600 includes a container agent 610, a dummy execution module 620, and a idle agent 630.

The container agent 610 is implemented as a native application of the terminal and transmits a command for executing the web application through the shortcut menu or the native menu of the terminal to the web application runtime layer 400 through the dummy execution module 620 . More specifically, when the execution of the web application is requested while the web application execution apparatus is running, the execution command of the web application is immediately transmitted to the command handler 411 of the web application runtime module 410, If the execution device is not running, the browser engine container core is loaded and executed, and then the execution command of the web application is transmitted to the command handler 411. For this, a web application Launcher 611 is included. In addition, the container agent 610 performs module-specific update of the web application execution device through SMS push or self check. To this end, the container agent 610 includes a updater 612. The updater 612 manages the update of the plug-in 530 installed on the web application execution device and the download and installation / deletion of the newly extended plug-in, and updates the access control rule for the access control rule for the security layer 300 (For example, a policy server), and requests download to the policy module 320 when necessary. It is preferable that the container agent 610 is implemented not in the form of a daemon but in a form in which the corresponding function is performed and terminated immediately. The container agent 610 is not driven for a long time, Module 620 and immediately terminates.

The dummy execution module 620 is driven by the container agent 610 and is used by the portability layer unit 200, the security layer unit 300, the web application runtime layer unit 400, and the browser engine layer unit 500 ), And more specifically, it loads only the browser engine container core and transmits the execution command of the web application.

The standby mode agent 630 supports the web application to operate on the idle screen of the terminal. The standby mode agent 630 is implemented according to the specification of the native OS, and a separate executable file such as IDLE Manager can be loaded by executing a component such as a plug-in or a widget. More specifically, the standby mode agent 630 is loaded by a native idle screen manager, and when a request for executing a specific web application is received from the idle screen, the standby mode agent 630 transmits the request to the web application runtime layer 400 do.

Next, the one or more system web applications 700 is a web application provided together with the installation of the web application execution apparatus, and includes a web application manager 710 for managing other web applications installed by the user, And a web application downloader 720 that manages downloading of applications.

The web application manager 710 operates on the web application runtime layer 400 and accesses the registry module 420 of the web application runtime layer 400 to obtain information on web applications installed on the terminal, And transmits the request to the web application runtime layer 400 if the user wants to start a specific web application.

The web application downloader 720 is a web application for connecting to an external server and downloading the web application.

The web application execution apparatus thus constructed is installed in a terminal equipped with the operating system 100 and operates on the operating system 100 to provide the same execution environment for the web application regardless of the type of the operating system.

The web application execution device according to the present invention supports simultaneous execution of multiple web applications and multi-instance for a single web application. That is, a plurality of containers can be executed in one system, and the container itself operates as a single instance.

The web application execution apparatus according to the present invention is basically a multi-tasking container that supports simultaneous execution of a plurality of web applications. The multi-tasking container is a multi-tasking container for grouping web applications according to the nature or kind of the web application, The execution apparatus can be driven. For example, the general web application and the web application that performs the widget service on the idle screen can be grouped and executed, respectively. At this time, each container itself is operated as a single instance, in which a plurality of web applications are simultaneously operated. At this time, all the modules of the web application execution apparatus are implemented to be thread safe in order to operate the web applications by multi-tasking.

By implementing the single-instance for each container in this manner, the web application execution apparatus of the present invention can be ported regardless of the characteristics of the native system even in an operating system that does not support multi-instance.

 The web application execution apparatus of the present invention conforms to a web standard, and creates a window of a native system each time a web application is executed, and creates a renderer instance so that a default or request page of the web application can be executed. Also, it is possible for one web application to create several windows, where renderer instances are created and allocated per window. In addition, multiple web applications can be run simultaneously, and multiple instances of a single web application are possible. All instances of the web application are managed by the context manager 412 and all events generated by the user interaction or system are delivered to the appropriate web application instance by the event handler 413.

In the web application execution device according to the present invention, in order to install and execute the web application securely, security between the web application and the terminal resource and security between the web application should be solved.

Security between web applications can be implemented by forbidding cross-references to web applications. That is, when a plurality of web applications are run on a single processor loaded by the dummy execution module 620, each web application is run on the browser engine layer portion 500 loaded on a separate thread. At this time, each web application owns one window. According to the web standard, when knowing the name of the corresponding window, another web application can refer to another web application without limitation. In the present invention, Restricts different web applications from accessing each other's web document objects. This can be implemented by modifying the JavaScript core 512 of the browser engine module 510.

The security between the web application and the terminal resources is implemented through the security layer unit 300.

Hereinafter, a web application management method according to the present invention will be described.

4 is a flowchart illustrating a web application management method by the web application execution apparatus of the present invention.

Referring to FIG. 4, the web application execution apparatus according to the present invention receives an execution request of a specific web application (S401). The execution request of the web application is configured to receive a URL for the web application set to identify the web application. Here, as described above, the URL for the web application includes a protocol skimmer (http: //) defined as accessing the local storage to execute the web application, a name of the web application file, Or a domain name of a content provider providing a web application. In addition, the input web application URL may further include a file name to be initially executed in the web application. This can be specified by the user.

As described above, when a URL of a specific web application is input, the web application execution apparatus confirms whether a web application identified by the URL exists in the local storage of the terminal (S402). This can be done by retrieving the installation information of the installed web application managed as shown in FIG. 3 through the registry module 420 of the web application runtime layer 400. That is, the install module 420 searches the install information management table of the web application shown in FIG. 3 through the registry module 420 to check whether the web application identified by the input URL is installed.

If it is determined that the web application identified by the input URL exists in the local storage, the web application execution apparatus executes the web application (S408). More specifically, the web application execution device checks the file path (content URL) in the local storage where the corresponding web application is actually located from the installation information management table of the web application through the registry module 420, The browser engine layer unit 500 executes the request page of the web application. Here, if the input URL describes only the package file name of the web application, the default page set in advance is executed for the first time. If the input URL contains a specific file name in the package of the web application, The request page corresponding to the first time is executed. The execution method of the web application executed in step S408 will be described in more detail later.

On the other hand, if it is determined that the web application identified by the input URL does not exist in the local storage, the web application execution apparatus outputs an error message indicating that the web application requested to be executed does not exist to the user, (S403).

When the user selects not to download (S404), the web application execution device selects the download (S404), and the input web application URL is converted into a network URL for downloading the corresponding web application do. For example, the web application URL contains the name of the publisher's domain and the filename of the web application, so you only need to convert the protocol schema http: // to http: // or https: //.

Then, the web application execution apparatus accesses the corresponding web server on the network using the converted network URL (S406). Here, the web server may be a web server of a manufacturer that produced the web application, or a web server of a content provider that provides the web application, identified by a domain name included in the URL.

The web application execution device downloads the requested web application from the connected web server and installs it in the local storage of the terminal (S407). Here, the downloading process can be performed according to the OMA standard. In step S407, the web application package 100 shown in FIG. 2 is downloaded as a compressed file from the web server. In the installation process, the web content 11 is stored in the local storage of the terminal, The policy information 13 is stored in the security storage of the terminal through the registry module 420. [ In addition, the installation information of the web application is registered in the web application installation information management table of the secure storage through the registry module 420. As shown in FIG. 3, the installation information registered here includes a URL of the web application, a content URL indicating the file path of the local storage in which the web content 11 is stored, and a URL included in the downloaded structure information 12 A hash code, and policy information 13 are included.

In this manner, when the installation of the web application is completed, the web application execution device fetches the web content of the web application in step S408, and executes the default page or the request page.

Next, with reference to FIG. 5 to FIG. 10, the important steps in the management method of the web application will be described in more detail.

FIG. 5 is a flowchart illustrating a detailed process of downloading and installing a web application in the web application management method according to the present invention.

The updating and downloading of the web application can be performed by pushing SMS from the update server or self-checking by the updater 612 included in the execution layer 600. In this case, an update request (S501) by SMS push is received from the update server 51, or the self-check causes the updater 612 to transmit the download request to the web application downloader 720. 2, if a web application requested to be executed does not exist in the local storage, a download request is transmitted from the web application execution device to the web application downloader 720 .

When the download request is transmitted to the web application downloader 720, the web application downloader 720 accesses the download server 52 and requests a specific web application to download (S503). In the case of step S406 of FIG. 2, the download server 52 becomes a web server identified by the domain name of the manufacturer or content provider included in the web application URL.

In response to the download request, the download server 52 downloads the web application requested in accordance with the OMA standard (S504). At this time, the download server 52 delivers a download descriptor (DD) to the web application downloader 720 and a web application package (SMF) having the structure shown in FIG. 2 (S505).

As described above, the web application downloader 720 that has downloaded the web application package performs the installation process of the web application. To do so, the web application downloader 720 calls the registry method to the browser engine module 510 (S506). Then, the browser engine module 510 calls the system API plug-in 531 to call the registry module 420 (S507). The system API plug-in 531 operates to call the registry module 420 of the web application runtime layer 400 (S508).

The registry module 420 thus called extracts the installation information from the downloaded file by the web application downloader 720 and stores it in the secure storage 53 in step S509 and stores the web content in the local storage 54 (S510).

At this time, the installation information including the hash code and the policy information for the integrity verification is stored separately in the secure storage 53, so that inappropriate information about the important information for managing the web application Access can be blocked.

Next, FIG. 6 is a flowchart illustrating a security providing process for executing the web application in the web application managing method according to the present invention. In the web application management method shown in Fig. 2, the integrity of the web application to be installed or executed is applied before installation of the web application in step S407 or before execution of the web application in step S408, It is possible to prevent a web application having one intention or an inappropriate web application from being installed or executed in the terminal.

To this end, the web application used in the present invention is code-signed, and at the time of downloading, the certificate information is downloaded together and stored in the secure storage 52.

Referring to FIG. 6, the web application execution apparatus includes a web application or a web application installed in the browser engine layer unit 500, and receives a request for installation of a plug-in 530 for processing a call and a response to the portable layer unit 200 (S601). If it is determined that the web application and the plug are installed, the code signature of the corresponding web application and plug-in is verified (S602). More specifically, before the web application downloader 720 and the plug-in management module 520 start installing the web application and the plug-in, authentication of the web application and plug-in is requested to the authentication module 310, The module 310 receives the certificate of the web application and the plug-in and the encrypted hash value from the registry module 420, and performs the certificate verification through the hash operation. The certificate verification may be performed in a generally known authentication standard, for example, X509, and such authentication method and verification method are well known, and a detailed description thereof will be omitted here.

If the verification of the plug-in and the web application is successfully performed through the authentication module 310, the web application execution device executes installation of the web application and the plug-in (S603 and S604).

On the other hand, if the verification of the plug-in and the certificate of the web application is unsuccessful, the web application manager 710 and the plug-in management module 520 send an error message indicating that the corresponding web application and the plug- To the user (S605).

Then, if the user selects to install, the step S604 is performed to install the corresponding plug-in and the web application, and if the user selects to stop the installation, the process is terminated (S606 ).

In addition, the present invention verifies the code sign of the web application and the plug-in at every execution and loading of the web application and the plug-in.

That is, the web application execution device confirms an execution request or a loading request for the web application and the plug-in (S607).

If it is determined that there is an execution request or a loading request of the plug-in and the web application, the authentication module 310 of the web application execution device fetches the encrypted hash value and the certificate of the corresponding web application and the plug-in from the registry module 420, (S608).

If the code signature verification is successful, the web application execution device executes execution or loading of the requested web application and plug-in (S609, S610), and conversely if the verification is not successful, the requested web application and plug- And provides an error message to the user that the certificate is not included (S611).

Then, if the user selects execution or loading, the user performs step S610 to execute or load the corresponding plug-in and web application. If the user selects to interrupt the execution, (S612).

In this manner, by performing the verification process of the code sign every time the web application and the plug-in are installed, executed or loaded, the web application and the plug-in by the third developer or the malicious hacker are misused, It can filter out the application is running, and can provide the user with reliability in executing the web application.

In addition, the web application execution apparatus according to the present invention can access the web application through the policy module 320 of the security layer unit 300 at the time of requesting access to the transplantation layer unit 200 during execution of the web application. Check permissions, grant or deny access. Accordingly, it is possible to prevent a web application from improperly hacking or accessing resources or OS functions of the terminal.

Next, FIGS. 7 to 9 are flowcharts illustrating various embodiments of a process for processing an execution request of a web application in a web application management method according to the present invention. This can be applied to steps S401, S402, and S408 of FIG.

Referring to FIG. 7, in the web application execution apparatus according to the present invention, a web application execution request can be made through a shortcut icon.

When the execution request of the web application using the shortening icon occurs (S701), the web application execution apparatus operates the container agent 610 of the execution layer 600 to execute the web application runtime layer 400 and the browser engine layer It is confirmed whether the browser engine container core including the unit 500 is running (S702).

If the browser engine container core is not running (S703), the browser engine container core, that is, the porting layer unit 200, the security layer unit 300, the web application runtime layer unit 400, The engine layer unit 500 is loaded (S704).

In step S704, if the browser engine container core is already running, the web application execution command is transmitted to the command handler 411 of the web application runtime module 410 in step S705. This is accompanied by a web application URL for identification of the web application, as described above.

The command handler 411 transfers the execution request of the web application to the context manager 412 (S706).

The context manager 412 creates a window and a renderer instance for the web application, and executes a default page or a requested page (S707)

Next, referring to FIG. 8, in the web application execution apparatus according to the present invention, a web application execution request can be made through the web application manager 710 (S801).

The web application manager 710 refers to the installation information of the web application stored in the registry module 420 and directs the user to the list of currently installed web applications. Here, if the user requests execution of a specific web application, the web application manager 710 calls the execution API provided by the web application execution apparatus according to the present invention (S802).

The browser engine module 510 loads the system API plug-in 532 among the one or more plug-ins 530 and calls the execution API (S803).

The system API plug-in 532 provides an access interface for the core function of the web application execution device, in particular, the functions of the web application runtime layer 400, The execution request of the web application is transmitted to the context manager 412 of the runtime layer 400 (S804).

Then, the context manager 412 creates a window and a renderer instance for the web application, and executes a default page or a request page (S805).

Finally, referring to FIG. 9, the web application execution apparatus according to the present invention can be requested to execute a web application on the idle screen of the terminal (S901). At this time, the web application execution apparatus is in a disabled state.

Accordingly, the native idle screen manager installed in the terminal receives the user's web application execution request, loads the idle mode agent 630 of the execution layer 600, and delivers the web application execution command (S902).

The standby mode agent 630 loads a browser engine container core composed of the portable unit layer 200, the security layer unit 300, the web application runtime layer unit 400 and the browser engine layer unit 500 , And then calls the idle screen mode execution API (S903).

In step S904, the context manager 412 receives the execution command of the web application through the idle screen mode execution API call, creates a window and a renderer instance for the web application, and executes a default page or a request page.

In addition, the web application execution apparatus according to the present invention may further execute the web application execution method as shown in Fig. 10 in order to improve the initial execution speed and the page-to-page switching speed when the web application is executed. This can be applied to the management method of the web application shown in FIG. 4 at the time of page execution at step S408.

Referring to FIG. 10, when executing a web application, the web application execution apparatus according to the present invention outputs a default page or a requested page through a window created by parsing, layout, and rendering processing (S1001) One or more other pages included in the page are extracted (S1002). The one or more other pages may be pages that are linked in the currently outputted page, or may be the remaining pages included in the web application. That is, it is possible to extract other related pages at the time of execution of each page, or extract all the remaining pages at the time of execution of the initial page.

The browser engine module 510 of the web application execution apparatus parses the extracted one or more other pages to generate a DOM tree and a style tree, connects the related nodes of the DOM tree and the style tree, (S1003). That is, the Web content 11 is parsed to construct a DOM (Document Object Model) tree and a renderer style tree. Then, the DOM tree and the related nodes of the renderer style tree are concatenated to create a renderer object. Specifies the layout of each page. The data processed up to the layout can be output to the screen through rendering.

Then, the browser engine module 510 serializes the data of the other pages processed until the layout is designated, and outputs the serialized data as a binary file (S1004). The binary file of the other page is temporarily stored while the corresponding web application is executed, and may be deleted at the end of the corresponding web application.

Then, the browser engine module 510 checks whether an event for another page, more specifically, a request to switch to another page occurs (S1005).

When an event for another page is generated, a binary file of another page stored in step S1004 is fetched and rendered and output through a corresponding window (S1006).

The steps (S1002 to S1006) are repeated until the web application is terminated (S1007).

In this case, when a web application composed of a plurality of pages is executed, data of each page of the web application stored in the terminal is fetched, and the data of the page is pre-parsed and designated in advance, You can import and render the data. Therefore, the web application execution method according to the present invention can improve the execution speed of the web application by shortening the initial execution time of the web application or the page-to-page conversion time.

The web application execution device and its web application management method according to the present invention can be implemented in software form 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 a magnetic medium such as a hard disk, a floppy disk and a magnetic tape, an optical medium such as a CD-ROM or a DVD, a magneto-optical medium such as a floppy disk magneto-optical media, and hardware devices that are specially configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. 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.

In addition, while the present invention has been described in connection with what is presently considered to be preferred embodiments thereof, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, It is self-evident to those who have knowledge. 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.

According to the present invention, an interface for executing a function having a different format according to an operating system is provided in a single format regardless of the type of an operating system, so that a web application executes a function of a terminal managed by the operating system in the same manner, The web application can be used in the same manner as the standalone application by managing the web application composed of a plurality of pages to be installed, executed and updated in increments of applications, not page units.

In addition, by applying this to a mobile communication terminal, mobile communication terminal application developers can more easily develop a web application by using existing rich web developer base and web development tool.

100: Operating system (General Purpose OS)
200: Porting layer
300: Security layer
400: Web Application Runtime layer
500: Browser Engine layer
600: Executable layer
700: System Web Application
310: Authentication module
320: Policy module
410: Web Application Runtime Module
420: Registry Modules
430: UI engine
440: Network Selector
450: Dynamic Synchronization Module
510: Browser engine module
520: Plug-in management module
530: Plugin
610: Container agent
620: Dummy execution module
630: Standby mode agent

Claims (27)

A single-type portable layer API (Application Programming Interface) for handling requests for executing functions managed by the operating system regardless of the type of operating system is provided. When a specific portable layer API is called, APIs of corresponding operating systems are called An importing layer unit for returning the data;
A browser engine layer unit for interpreting and executing each page of the web application in cooperation with the transplantation layer unit; And
Receives a web application execution request including web application identification information in the form of a URL (Uniform Resource Location), confirms whether the web application exists in the local storage, and if a web application exists in the local storage, And a web application runtime layer unit for delivering an execution command of the application to the browser engine layer unit and providing a network and a UI required for executing the page in the browser engine layer unit. The method of claim 1, wherein the web application identification information in the form of URL is
A protocol schema defined to import and execute web applications stored on local storage,
A domain name of a web application manufacturer or a content provider providing the web application,
And a file name of the web application. The method of claim 1, wherein the web application
A web content including a source file constituting a plurality of pages included in a web application according to a web standard, a resource file including an image inserted into the page,
A configuration information including a list of data included in the web application, information on whether the data is disclosed according to the data, integrity information on each data such as a hash code, execution environment information of the web application,
And policy information for specifying a range of terminal resources accessible to the web application. The method of claim 1, wherein the web application runtime layer
If the web application does not exist in the local storage, confirms whether or not the web application is downloaded, and when the user selects download, the web application is connected to the server through the network to download and install the web application. Execution device. The method according to claim 1,
And an execution layer unit for loading the browser engine layer unit, the porting layer unit, and the web application runtime layer unit and transmitting a request for execution of the web application according to the request of the user to the web application runtime layer or the browser engine layer unit. A web application execution unit. The method according to claim 1,
Wherein the web application and the browser engine layer verify the certificate before installation, execution, or loading of a plug-in that invokes resources related to the terminal and functions related to the operating system other than the web standard and executes the web application in accordance with the access control rule Further comprising a security layer for controlling access to the transport layer. The browser engine of claim 1, wherein the browser engine layer
A browser engine module for interpreting and executing each page of the web application written in the web standard language;
A plug-in management module for downloading and installing one or more plug-ins, managing a list of installed plug-ins, updating, and processing a call request of plug-ins; And
One or more plug-ins installed by the plug-in management module and operating through the plug-in management module, each of the plug-ins calling a resource of the terminal other than the web standard and a function of the operating system through the porting layer and returning a response thereto The web application executing apparatus comprising: 2. The apparatus of claim 1, wherein the implantation layer
An HTTP module that provides functions and APIs related to HTML,
XML module that provides API for XML parsing function,
A thread module that provides the thread function as an API type and bypasses the functions provided by the operating system,
A UI backend module that provides API functions of the native window system necessary for UI (User Interface)
Secure storage module that provides secure storage function in API form,
A resource module that provides an access interface for terminal resources in an API form,
An OS API module that provides OS APIs provided by terminals in API form in addition to terminal resources,
Collaboration module that provides interoperability between web applications in API form,
A synchronization module for providing an API interface for interworking with a synchronization application existing in an external device,
And a local storage module for providing a local storage function in an API form. 6. The method of claim 5, wherein the web application runtime layer
A web application runtime module for performing context management and event handling of the web application instance, and command processing from the execution layer;
A registry module for managing installation information of the web application and the plug-in and structure information of the web application execution device;
A UI engine for processing UI (User Interface) and user input for a screen area other than the area rendered by the browser engine layer unit;
A network selector for setting and managing a network to be used in the web application execution device; And
And a dynamic synchronization module for storing data while the web application is disconnected in the local storage when the network connection is disconnected and for synchronizing data stored in the local storage and external data when the network is connected, Application execution device. 6. The apparatus of claim 5, wherein the execution layer
The web application execution execution layer, the browser engine layer, and the porting layer in response to a request to execute the web application through the shortcut menu or the native menu of the terminal, A container agent for delivering to a web application runtime execution layer;
A dummy execution module which is operated by the container agent and loads the web application runtime execution layer, the browser engine layer and the porting layer, and then transmits a web application execution command to the web application runtime execution layer; And
And a standby mode agent which is loaded by the native standby screen manager and forwards the web application execution command in the standby screen to the web application runtime layer. 7. The apparatus of claim 6, wherein the security layer
An authentication module for verifying a certificate of the web application and the plug-in when the web application and the plug-in are installed or executed; And
And a policy module that controls access to the port layer in accordance with an access control rule during execution of the web application. 8. The method of claim 7, wherein the one or more plug-
A resource plug-in for transferring a function call related to the terminal resource to the portable layer,
A system API plugin for delivering a terminal OS API calling function of the web application to the porting layer and providing an access interface for the function of the web application runtime layer,
A collaboration plug-in for transferring a function call for interworking between the web application and the native application to the porting layer,
And a synchronization plug for transmitting a function call related to the synchronization agent of the web application to the porting layer. 10. The method of claim 9, wherein the web application runtime module
A command handler for receiving a command related to the execution of the web application from the execution layer and interpreting the command and instructing the command;
A context manager for controlling generation and destruction of a native window and a renderer for each web application in accordance with instructions of the command handler or the browser engine layer;
An event handler for processing a system-related event of the native window and the web application execution device generated by the context manager, and transmitting the event to the UI engine so as to give a UI effect when an event related to a predefined situation occurs for the window; And
And a lifecycle manager for managing a web application including a plurality of pages and a life cycle of each page of the web application. 10. The system of claim 9, wherein the registry module
A web application URL that is web application identification information in the form of a URL, a content URL indicating a location of a local storage where a web application identified by the web application URL is actually stored, a hash code for verifying the integrity of the web application, And a web application installation information management table including policy information for access control of the web application is configured and managed. A terminal equipped with the web application execution device according to any one of claims 1 to 14. A browser engine layer for interpreting and executing each page of the web application; a browser engine layer for providing a network and a UI required to execute a page; A web application management method according to a web application execution device including a browser engine container core including a web application runtime layer and an execution layer as an entry point of the browser engine container core,
Receiving an execution request of a web application including web application identification information in the form of a URL (Uniform Resource Location);
Confirming whether a web application identified by the URL-type web application identification information exists in the local storage; And
And if the web application exists in the local storage, executing the web application stored in the local storage. 17. The method of claim 16,
If the web application does not exist in the local storage, outputting an error message to the user that the web application requested to be executed does not exist and confirming whether to download the web application;
If the user selects to download, converting the web application identification information in the form of URL into a URL accessible via the network; And
Accessing a web server on the network using the converted URL, downloading the web application, and installing the web application on a local storage of the terminal. 17. The method of claim 16, wherein the web application identification information in URL form
A protocol schema defined to import and execute web applications stored on local storage,
A domain name of a web application manufacturer or a content provider providing the web application,
And a file name of the web application. 17. The system of claim 16, wherein the web application
A web content including a source file constituting a plurality of pages included in a web application according to a web standard, a resource file including an image inserted into the page,
A configuration information including a list of data included in the web application, information on whether the data is disclosed according to the data, integrity information on each data such as a hash code, execution environment information of the web application,
And policy information for specifying a range of terminal resources accessible to the web application. 17. The method of claim 16, wherein executing the web application further comprises:
Generating a native window and a renderer instance for the web application in response to a browser engine layer of the browser engine container core requesting execution of the web application;
Parsing, laying out and rendering a designated page among the pages included in the web application and outputting the page to the generated native window;
Extracting one or more other pages included in the web application other than the output page;
Performing parsing and layout assignments for the one or more other pages;
Serializing data of other pages processed until the layout is designated and storing the serialized data as a binary file;
Confirming occurrence of an event for the other page;
And when the event occurs, rendering the stored binary file and outputting the rendered binary file to the native window. 17. The method of claim 16, wherein the step of receiving an execution request of the web application
Checking whether execution of the browser engine container core is performed by the execution layer when a request for execution of the web application of the user using the shortcut icon is input;
Loading the browser engine container core if the browser engine container core is not running;
And delivering an execution command for the web application to the web application runtime layer of the browser engine container core if the browser engine container core is running. 17. The method of claim 16, wherein the step of receiving an execution request of the web application
A step in which an execution API is invoked through a web application manager managing a web application;
Loading the system API plug-in wherein the browser engine container core provides an access interface to the core functionality; And
Wherein the loaded system API plug-in transfers an execution command for the web application to a context manager of the web application runtime layer. 17. The method of claim 16, wherein the step of receiving an execution request of the web application
The native idle screen manager receiving a request for executing a web application of the user and loading the idle mode agent of the execution hierarchy; And
The waiting mode agent loading the browser engine container core and calling an idle screen mode execution API to deliver an execution command for the web application to the context manager of the web application runtime layer How to manage web applications. The method as claimed in claim 17, wherein the step of downloading the web application and installing the web application in a local storage of the terminal comprises:
Accessing the web server to download a web application;
Invoking a registry method into the browser engine layer;
Calling the system API plug-in to call the registry module of the web application runtime layer in the browser engine layer;
Invoking the system API plug-in by the call to call the registry module of the web application runtime layer; And
Wherein the called registry module extracts installation information from the downloaded file and stores the retrieved installation information in the secure storage, and storing the web content in a local storage. 17. The method of claim 16,
The web application can be installed or executed before the installation or execution of the web application. If the certificate verification is successful, the web application is allowed to continue to be installed or executed. If the certificate verification is unsuccessful, The web application management method comprising the steps of: 17. The method of claim 16, wherein executing the web application further comprises:
Further comprising the step of granting or denying access to the transplantation layer by referring to access control rules set for each web application when access to the transplantation layer is required. 26. A computer-readable recording medium on which a program for executing the web application management method according to any one of claims 16 to 26 is recorded.

Images