KR101482151B1 - Device and method for executing web application - Google Patents

Abstract

The present invention provides a web application execution system capable of improving execution speed of a web application composed of a plurality of pages while providing an execution environment of a web application capable of accessing terminal resources without depending on an operating system installed in the terminal, And a terminal using the same. According to the present invention, a portable layer API is provided for functions of a plurality of operating systems and terminals through a porting layer. The web application runtime layer provides a network and a UI required to execute a page in a browser engine layer, And analyzing each page of the web application and outputting the same to the screen. In the browser engine layer, one or more other pages belonging to the web application are analyzed and structured in advance, and the structured page is immediately Rendering and outputting to the screen, thereby shortening the page switching time.

Description

[0001] The present invention relates to a device and method for executing a web application,

The present invention relates to a web application execution method and apparatus, and a terminal to which the web application is applied. More specifically, the present invention provides an execution environment capable of accessing terminal resources without depending on an operating system installed in the terminal, And a web application execution device and method capable of improving the execution speed of the web application.

Recently, with the advent of the open environment as a result of the growth of smartphones, an open application and platform environment is required to differentiate services.

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.

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.

Therefore, when a web application platform supporting a standard web technology is implemented for a mobile communication terminal, it is possible to develop a mobile application more easily by using a 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 execution environment of a web application capable of accessing terminal resources without depending on an operating system mounted on the terminal by supporting a web standard and improving the execution speed of a web application composed of a plurality of pages And an apparatus and method for executing the web application.

According to an aspect of the present invention, there is provided a web application execution apparatus including a browser engine layer, an implantation layer, and a web application runtime layer. The browser engine layer part interprets each page of the web application and outputs it to the screen. One or more other pages belonging to the web application are analyzed and structured and stored, and when the event for another page is generated, And outputs it to the screen. The portability layer supports an application layer API (Application Programming Interface) for the functions of a plurality of operating systems and terminals. When the browser engine layer calls a specific port layer API, the port layer calls an API of the corresponding operating system and terminal, And delivers it to the browser engine layer. The web application runtime layer passes the execution command of the web application to the browser engine layer and provides the network and UI necessary for executing the page in the browser engine layer.

The web application execution apparatus according to the present invention further includes an execution layer unit for loading the browser engine layer unit, the porting layer unit, and the web application runtime layer unit and delivering an execution command of the web application according to the request of the user to the web application runtime layer can do.

The web application execution device according to the present invention verifies the plug-in certificate that calls the 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 layer portion.

In the web application execution apparatus according to the present invention, the browser engine layer unit may include: a browser engine module that interprets and executes each page of the web application; 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 and operated by the plug-in management module to respectively call resources of the terminal and functions of the operating system other than the web standard through the porting layer and return a response thereto.

In the web application execution apparatus according to the present invention, the porting layer unit may include an HTTP module for providing HTML related functions and APIs, an XML module for providing an API for an XML parsing function, a thread function in an API form, (UI) backend module that provides the functions of the window system required for UI (UI) implementation in API form, security storage that provides security storage function in API form, A resource module that provides an access interface for modules and terminal resources in the form of an API, an OS API module that provides an OS API provided by the terminal in addition to terminal resources, an API module, and an API function for a page not included in the web application , A collaboration module provided to the external device, and an interface with the synchronization application existing in the external device A Sync module provided in an API format, and a Local Storage module providing an API function of a local storage function existing in an operating system.

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 state 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 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 for storing data while the network connection is disconnected in the local storage while the web application is running and synchronizing 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 operates according to a request to execute a web application through a shortcut icon or a menu of the terminal, and determines whether the web application runtime execution layer, the browser engine layer, And if so, a container agent for delivering a web application execution command to the web application runtime execution layer; A dummy execution module that operates by the container agent and transmits 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 port layer; And a standby mode agent which is loaded by the standby screen manager of the terminal and forwards the web application execution command in 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 a certificate of the web application and the plug-in when installing or executing the web application and the plug-in; And a policy module for controlling access to the port layer in accordance with access control rules during execution of the web application.

The at least one plug-in may include a resource plug-in for transferring a function call related to the terminal resource to the transplantation layer, a terminal OS API calling function of the web application to the transplantation layer, A system API plugin for providing an access interface to the function of the runtime layer, a collaboration plug-in for transferring a function call for linking a page not included in the web application to the porting 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 windows and renderers for each web application according to instructions of a command handler or a browser engine layer; An event handler for processing a window event generated by the context manager and a system related event of the web application execution device, and transmitting the event to the UI engine when an event related to a predefined situation occurs in 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 addition, as another means for solving the problem, the present invention provides a terminal equipped with the web application execution apparatus described above.

In addition, according to another aspect of the present invention, there is provided a Web application execution method comprising the steps of: creating a window and a renderer instance for a web application when a browser engine layer of the browser engine container core requests a web application execution; Analyzing and structuring a designated page among the pages included in the web application, and rendering the rendered page and outputting the rendered page to a window; Extracting one or more other pages included in the web application other than the output page; Analyzing and structuring one or more other pages; Storing structured data of another page; Confirming occurrence of an event for another page; And rendering the stored structured data when the event occurs, and outputting the rendered structured data to a window.

A method of executing a web application according to the present invention includes the steps of: confirming whether a browser engine container core is executed in an execution layer when an execution request using a shortcut icon of a web application is input before a step of creating a window and a renderer instance; Loading the browser engine container core if the browser engine container core is not running; As a result of checking, if the browser engine container core is running, it may further include transmitting a web application execution command to the web application runtime layer of the browser engine container core.

A method for executing a web application according to the present invention includes the steps of: calling an execution API in response to a request for execution of a web application of a user in a web application manager managing an installed web application, prior to a step of creating a window and a renderer instance; Loading a system API plug-in, wherein the browser engine container core provides an access interface to the core function, and calling an execution API; The loaded system API plug-in may further include transmitting an execution command of the web application to the context manager of the web application runtime layer.

A method of executing a web application according to the present invention includes the steps of: a step of loading a standby mode agent of an execution layer unit by a native idle screen manager receiving a request for executing a web application of a user, prior to a step of creating a window and a renderer instance; The standby mode agent may load the browser engine container core, call the idle screen mode execution API, and forward the execution request of the web application to the context manager of the web application runtime layer.

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 web application execution method described above is recorded.

According to the present invention, a terminal including a terminal supports execution of a web application that conforms to a web standard and uses resources of the terminal irrespective of the type of an operating system, and at the time of initial execution of the web application, Analyzing and structuring the data and storing the data, and if the page conversion is requested, the stored data is fetched and immediately rendered, thereby shortening the switching time between pages, thereby improving the execution speed of the web application.

1 is a block diagram showing the overall structure of a web application execution apparatus according to the present invention.
2 is a flowchart illustrating a method of executing a web application according to the present invention.
3 to 5 are flowcharts illustrating various embodiments of a web application execution method according to an exemplary embodiment of the present invention.
FIG. 6 is a diagram illustrating a process of a page in a web application execution method according to the present invention.
7 is a block diagram illustrating a package structure of a web application 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.

1 is a diagram illustrating an overall structure of a web application execution apparatus according to 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 a system web application 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. Here, the web application runtime layer 400 mainly manages the web application, and the browser engine layer 500 interprets and executes each page of each web application. The browser engine container common is independent of the operating system 100 and has dependency only on the porting layer 200 by accessing the operating system 100 through the porting 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.

A browser engine container core is a multi-tasking container that supports simultaneous execution of multiple web applications and multiple instances of a single web application. It can execute multiple containers within a system, and the container itself operates as a single instance do.

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

At this time, the execution layer 600 is used as an entry point of the browser engine container core. That is, 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. 7, the web application 800 includes a plurality of pages, such as html, xhtml, css, and java, which constitute each page of the web application. a script file and the like, and a resource file such as an image to be inserted into each page, a list of data included in the web application package, whether the data is disclosed by data, integrity of data such as a hash code (Configuration file) 820 including information about the execution environment of the web application (screen size, target CPU, target operating system, version of the web application execution device, and the like), and terminal information And policy information 830 for specifying a range of the policy information 830.

Herein, the policy information 830 may include basic access authority information given to the whole web application package and detail access authority information assigned to each page of the web application, , For example, access control for photos, address book, terminal functions, call records. Such a web application may be provided in the form of a compressed file and may further include a certificate attesting that the web application is to be distributed through an authorized institution or provider.

Hereinafter, functions and detailed configurations of the respective components will be described.

Each of modules of the web application runtime layer unit 400 and the browser engine layer unit 500 is installed on the operating system 100 installed in the terminal, (Hereinafter referred to as an " application layer API ") for various OS functions of the operating system 100 and resources of the terminal in order to be independently implemented and operated. That is, the transplantation layer 200 provides the transplantation layer APIs for the functions of the terminal resources and the operating system to the upper web application runtime layer 400 and the browser engine layer 500, When API calls are made, the APIs of the corresponding terminal resources and operating system are called. The portable layer API that can be provided in the portable layer 200 includes an HTTP module that provides functions and APIs related to HTTP and HTTPS, an XML module that provides an API for an XML parsing function, A thread module that bi-passes a function provided by the UI module 100, a UI backend module that provides a window system function necessary for UI implementation in an API form, and a security storage function in an API form A resource module that provides an access interface for a Secure Storage module and terminal resources (for example, a telephone directory, a photograph, a call log, an SMS list, and the like) in the form of an API, an OS API OS API module that provides APIs in the form of call connection, SMS transmission, property setting of the terminal system, etc.), API function to interoperate with pages not included in web application, API type 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 existing in the operating system as an API type It may contain more than one, and other transport layer APIs may be added as needed. Each module of the transplantation layer 200 is implemented as a DLL in order to facilitate future updating.

Since the transfer layer unit 200 is dependent on the operating system, it is preferable that the transfer layer unit 200 is implemented so as to be applicable to various types of operating systems 100 mounted on the terminal.

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 provided in the web application and the browser engine layer unit 500 and authenticates the web application and the plug-in upon installation and execution of the plug-in 530 that relays access to the portable layer unit 200 . That is, the web application execution apparatus according to the present invention installs or executes the web application and the plug-in according to whether or not the authentication module 310 is authenticated.

The policy module 320 controls access to the porting layer 200 of each web application according to an access control rule. More specifically, the access control rule set for each web application is downloaded and stored, and when the access request of the porting layer 200 is requested, access is permitted or denied by referring to the access control rule of the web application.

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

The web application runtime layer 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 later. More specifically, the web application runtime layer unit 400 manages instances of the web application, performs registry management and user interface management for installing the web application and setting information. 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), interprets the command, and instructs the corresponding module to perform the operation. The command handler 411 is an IPC command processor. Commands that can be processed by the command handler 411 include execution / termination of the web application, updating of the setting information related to the web application execution device, execution and termination of the web application execution device, and installation / uninstall / have.

The context manager 412 manages the contexts of web application instances, and controls creation and destruction of windows and renderers for each web application. In other words, a window is generated in accordance with a command for executing a web application delivered from the command handler 411 and the browser engine module 510, and a window generation command transmitted from the browser engine module 510, and an instance of a renderer And outputs the rendered result of the page requested by the browser engine module 510 to the corresponding 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.

The lifecycle manager 414 manages the life cycle of the web application. One web application consists of a number of pages, each page of the web application initiated by a visit and terminated each time it switches to another page. The web application is started by creating one window for each web application by execution request of the execution layer 600 or another web application or a 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 manager 414 manages the start and end of the web application.

In the web application runtime layer 400, the registry module 420 manages installation information of the web application and configuration information of the web application execution device. Here, the actual installation information and the structure information are stored in the secure storage of the terminal through the transplanting 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. More specifically, the registry module 420 manages web application content such as installation, deletion, and update of a web application, setting the attributes of the web application, extracting and providing authentication information of the web application, , Module management including dependency management between modules, attribute setting function of web application execution device, and management function of installation information of 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. [ More specifically, it handles processing for remaining areas other than the area where the page of the web application is output, from among the entire screen of the terminal, including a status bar for displaying the execution status and a button for user input. At this time, the annuniciator area for displaying the signal reception intensity of the antenna, the availability of the call, and the battery remaining amount may not be customized depending on the type of the operating system 100, have. 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 manager of the terminal. That is, the UI engine 430 processes UX (User experience) related functions 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 at 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 assures the execution of a seamless web application regardless of whether the terminal is on-line or off-line. More specifically, when a web application accessing external data is being executed, if the network connection is lost, data is stored in the local storage through a cache mechanism, and data stored in the local storage when connected to the network The synchronization of external data is automatically performed 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 includes a browser engine module 510, a plug-in management module 520, and one or more plug-ins 530, which interprets and executes each page of the web application. Among them, the browser engine module 510 interprets and executes each page of a web application written in a web standard language such as HTML, CSS, and JavaScript. 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. The browser engine module 510 comprises a Web core 511 for analyzing and rendering a web standard language and a script core 512 for performing JavaScript interpreting. In implementing the browser engine module 510, the web core 511 and the script core 512 are configured as modules, respectively, whereby update and replacement can be performed for each module. In particular, the browser engine module 510 is preferably configured to prohibit cross-references between web applications in order to prevent hacking and the like. The browser engine module 510 uses the functions of the operating system 100 through the porting layer 200 to execute the web application. More specifically, the browser engine module 510 includes a protocol processing function such as HTTP and HTTPS, an XML processing function such as an XML parser and XML conversion, a window processing function, a font processing function, an image decoder processing function, And a timer. In order to provide such functions, necessary basic functions are provided through the transplantation layer unit 200. That is, the HTTP (s) module, the XLM module, the UI backend module, and the OS API module of the transplanting layer unit 200 access the operating system 100 and the terminal resources to execute the respective pages using necessary functions.

In addition, while executing each page of the web application, the browser engine module 510 extracts structured data after extracting, analyzing and structuring other pages except the page output to the current window. When the event for the other page is generated, the structured data is fetched and directly rendered and output to the corresponding window. According to this, the web application execution device according to the present invention can remarkably improve the execution speed by shortening the initial execution time and the page-to-page switching time when executing the web application.

In addition, web applications can use terminal resources such as address books and terminal applications in addition to web standard functions. To this end, the browser engine layer 500 further includes a plug-in management module 520 and one or more plug-ins 530 to invoke terminal-dependent functions. Accordingly, since the processing of the terminal-dependent functions is performed through the plug-in management module 520 and the one or more plug-ins 530, in implementing the browser engine module 510, And can be applied to an execution device. In addition, new functions that can be provided in the future can be added in the form of plugins, which makes extension of functions easier.

The plug-in management module 520 performs a response to a request for downloading and installing a plurality of plug-ins, managing a list of installed plug-ins, updating, and requesting a plug-in of a web application. Here, the download request and 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 management module 520 through the web application runtime layer 400 do. In response to the download request, the plug-in management module 520 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 management module 520 includes a browser-side API that the browser must provide to the plug-in, and a plug-side API that the plug-in must provide to the browser. The plug-in calls the browser-side API to perform an operation, Side API to manage plug-ins related to the creation / operation / destruction of plug-ins.

The one or more plug-ins 530 call a function related to an operating system and resources of a terminal other than the web standard required by the web application and transmit a response to the browser system to the browser engine module 510, A resource plugin for transferring a related function call to the resource module of the transplantation layer 200 and a terminal OS API calling function of the web application to the OS API module of the transplantation layer 200, The system API plug-in providing the access interface for the core function of the mobile terminal 400 and the function call for linking with the page not included in the web application to the collaboration module of the transplantation layer 200 A plug-in, and a function call related to the synchronization agent of the web application, May include one or more of the synchronization (Sync) plug-in for delivering the (Sync module), and in addition you can add a plug-in for various other functions as required.

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

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, the execution layer 600 accesses the operating system 100 using the transplantation layer 200 as much as possible in order to improve the portability. 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 And transmits a web application execution command according to the user's request to the web application runtime layer 400 or the browser engine layer unit 500. In addition, an SMS-push or self-check checks the update of each module of the web application execution device and transfers the related download request to the corresponding module. In particular, an update to the plug-in 530 included in the browser engine layer unit 500 is checked and a download request is transmitted to the plug-in management 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 form of the terminal, and transmits the execution command of the web application through the shortcut menu or the native menu of the terminal by loading 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 directly transmitted to the command handler (not shown) of the web application runtime module 410 through the dummy execution module 620 411). When the web application execution apparatus is not running, the browser engine container core is loaded and executed through the dummy execution module 620, and the execution command of the web application is transmitted to the command handler 411 do. 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 an 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 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 protocol according to the characteristics of the native OS. The standby mode agent 630 is loaded by a native idle screen manager of the terminal. If there is a request for executing a specific web application on the idle screen, To the web application runtime layer (400).

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 unit 400 when 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 device thus constructed is installed in a terminal equipped with various types of operating systems 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 the web standard, and generates a window of a native system each time a web application is executed, and generates a renderer thread to execute a default or request page of the web application. Also, it is possible for a single web application to create multiple windows, in which renderer threads 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.

Here, the security between the web applications can be implemented by forbidding the cross reference of the web application. 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 script core 512 of the browser engine module 510.

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

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

2 is a flowchart illustrating a basic procedure of a web application execution method according to the present invention.

Referring to FIG. 2, when an execution request of a specific web application occurs, the web application execution apparatus according to the present invention creates a window and a renderer instance for the web application (S201, S202). That is, when an execution command of the web application is transferred to the context manager 412 of the web application runtime module 410, the context manager 412 generates a window and a renderer instance for the corresponding web application. Here, the execution command of the web application can be transmitted through various paths such as a shortcut icon, a native menu, a web application manager 710, and a idle screen, which will be described in more detail later.

As described above, when a window and a renderer instance for a web application are generated, the corresponding browser engine module 510 analyzes, structures, and rasterizes a page included in the web application and outputs the generated window to the generated window (S203). Here, the page to be initially executed may be an initial page set as a default in the installation information of the web application, or may be a page arbitrarily designated by the user. In this case, when a web application is requested to be executed, the user can specify the address of the page to be initially executed.

In addition, the browser engine module 510 extracts one or more other pages included in the web application in addition to the executed designated page (S204). The one or more other pages may be pages connected to the currently output page, or may be all pages constituting 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 analyzes the extracted one or more other pages, creates a DOM tree and a style tree, and connects the related nodes of the DOM tree and the style tree to structure the corresponding page (S 205). 6, each page of the web application includes web content 61 written in a web standard language such as HTML and xHTML, format information 62 such as css, ). This execution of the web page is performed by analyzing the web content 61 and the format information 62 of the page and constructing a DOM (Document Object Model) tree 63 and a renderer style tree 64, 63 and an associated node of the renderer style tree 64 to create a renderer object 65. [ A layout 66 is specified by structuring the page through the generated renderer object. The structured data can be output to the screen through rendering.

In step S205, only the analysis and structuring of each page is performed.

Then, the browser engine module 510 serializes the structured data of the other pages without directly rendering the data, and stores the serialized data in a binary file (S206). 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 the other page, more specifically, a request to switch to another page occurs (S207).

When the event for the other page is generated, the binary file of another page stored in step S206 is fetched and rendered and output through the corresponding window (S208).

The above steps S204 to S208 are repeated until the corresponding web application is terminated (S209).

In this case, when a web application composed of a plurality of pages is executed, data for each page of the web application stored in the terminal is fetched, and pre-parsing and layout designation are also processed. Thus, 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.

In the web application execution method according to the present invention, the web application execution request processing may be performed as shown in FIG. 3 to FIG.

3 is a flowchart illustrating a first embodiment of a method for transmitting an execution command of a web application in a web application execution method according to the present invention. Referring to FIG. 3, a user's web application execution request can be made using a shortcut icon. When the execution request of the web application using the shortcut icon is input in step S301, the container agent 610 of the execution layer 600 operates and the web application runtime layer 400 and the browser engine layer 500 It is confirmed whether the browser engine container core is running (S302).

If the browser engine container core is not running (S303), the browser engine container core, i.e., the portability layer unit 200, the security layer unit 300, the web application runtime The layer unit 400 and the browser engine layer unit 500 are loaded (S304).

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 S305.

The command handler 511 analyzes the command transmitted from the execution layer 600, and transmits the execution request of the web application to the context manager 412 if the command is a web application execution command (S306).

The context manager 412 creates a window and a renderer instance for the web application (S307, S308).

The subsequent operations are the same as the steps S202 to S209 shown in Fig.

4 is a flowchart illustrating a second embodiment of a method for transmitting an execution command of a web application in a web application execution method according to the present invention. Referring to FIG. 4, the web application execution request of the user may be made by the web application manager 710.

In this case, the web application manager 710 refers to the installation information of the web application stored in the registry module 420, and guides 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 an execution API provided by the web application executing apparatus according to the present invention (S402).

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

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

Then, the context manager 412 creates a window and a renderer instance for the web application (S405, S406).

The subsequent steps are the same as the steps S202 to S209 shown in Fig.

Lastly, FIG. 5 is a flowchart illustrating a method for transmitting an execution command of a web application in a web application execution method according to a third embodiment of the present invention.

Referring to FIG. 5, the user can request execution of a specific web application on the idle screen of the terminal (S501). In this case, the terminal is in the activated state of the idle screen, and the web application execution apparatus is in the inactive state at this time.

Accordingly, when the native idle screen manager installed in the terminal receives the user's web application execution request, the idle mode agent 630 of the execution hierarchy 600 is loaded and the web application execution command is transmitted (S502).

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 calls the idle screen mode execution API (S503).

The context manager 412 receives the execution command of the web application through the idle screen mode execution API call and creates a window and a renderer instance for the web application at steps S504 and S505.

The subsequent steps are the same as the steps S202 to S209 in Fig.

The apparatus and method for executing a web application according to the present invention may be implemented in the form of software readable by various computer means and recorded on 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.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art. It is self-evident to those who have. Furthermore, although specific terms are used in this specification and the drawings, they are used in a generic sense only to facilitate the description of the invention and to facilitate understanding of the invention, and are not intended to limit the scope of the invention.

The present invention is applied to a terminal equipped with an operating system, and provides an execution environment of a web application that can use terminal resources according to a web standard, while controlling execution and installation of a web application and a plug-in and access to terminal resources The legitimate web application and the plug-in are installed or executed, and the executed web application can access the terminal resource within the granted authority. As a result, the present invention can prevent the web application, which is modulated due to an impure purpose such as hacking, Thereby preventing the terminal resources from being hacked by the web application having the impure intention and providing the user with the security for the installation and use of the web application.

100: Operating system (OS, Operating System)
200: Porting layer
300: Security layer
400: Web Application Runtime layer
500: Browser Engine layer
600: Executable layer
700: System Web Application

Claims (17)

Analyzing and structuring one or more other pages belonging to the web application, storing structured data, and rendering the structured data when rendering an event for the other page, A browser engine layer unit for outputting the image data to a screen;
And provides an integrated transport layer API (Application Programming Interface) for functions and terminal resources of a plurality of operating systems. When the browser engine layer calls the specific transport layer API, the API of the corresponding operating system is called and the response is received An importing layer unit for delivering the URL to the browser engine layer unit; And
And a web application runtime layer for delivering an execution command of the web application to the browser engine layer and providing the network and UI necessary for executing the page in the browser engine layer. The method according to claim 1,
Further comprising an execution layer unit for loading the browser engine layer unit, the porting layer unit, and the web application runtime layer unit and transmitting an execution command of the web application according to a user's request to the web application runtime layer unit. Device. The method according to claim 1,
The web application and the browser engine layer verifies the certificate of the plug-in that calls the resources and operating system functions of the terminal other than the web standard and controls access to the transplantation layer during execution of the web application according to the access control rule Wherein the web application execution unit further comprises a layer unit. 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
And one or more plug-ins installed by the plug-in management module and operating through the plug-in management module to invoke resources and operating system functions of terminals other than the web standard, respectively, and return a response thereto to the browser engine module 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,
An UI backend module that provides functions of the window system necessary for UI (User Interface) implementation in an API form,
Secure storage module that provides secure storage function in API form,
A resource module for providing 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,
A Collaboration module for providing an API function for interworking with a native application installed in the terminal,
A synchronization module for providing an API interface for interworking with a synchronization application existing in an external device,
And a local storage module providing an operating system's local storage function in an API form. 3. The method of claim 2, 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. 3. The apparatus of claim 2, wherein the execution layer
A dummy execution module that loads a web application runtime execution layer, a browser engine layer, and an application layer, and then transmits a web application execution command to the web application runtime execution layer;
A container agent that operates according to a shortening icon or a request for executing a web application through a menu of the terminal, and executes the dummy execution module to deliver a web application execution command to the web application runtime execution layer; And
And a standby mode agent that is loaded by the standby screen manager of the terminal and forwards the web application execution command in the standby screen to the web application runtime layer. 4. The apparatus of claim 3, wherein the security layer
An authentication module for verifying a certificate of the web application and the plug-in before installing or executing the web application and the plug-in; 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. 5. The method of claim 4, wherein the one or more plug-
A resource plugin for transmitting a function call related to the terminal resource to the transplantation layer,
A system API plug-in for delivering a function call to the terminal of the web application and the OS API to the transplantation 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 with a page not included in the web 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. 7. The method of claim 6, 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 windows and renderers for each web application according to the command handler or the browser engine layer unit;
An event handler for processing an event related to the window generated by the context manager and a system related event of the web application execution device, and transmitting the event to the UI engine 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. 11. The method of claim 10, wherein the command processed by the command handler comprises:
Execution and termination of the web application, updating of setting information related to the web application execution device, execution and termination of the web application execution device, installation, uninstallation, and update of the plug-in installed in the browser engine layer portion The web application executing apparatus comprising: A terminal equipped with the web application execution apparatus according to any one of claims 1 to 11. A web application runtime layer for providing a network and a UI required to execute a page in the browser engine layer unit, a web application runtime layer for providing a web page for each page of the web application, A web application execution method according to a web application execution device including a browser engine container core including a browser engine layer that interprets and executes a browser engine container core and an execution layer that is an entry point of the browser engine container core,
Creating a window and a renderer instance for the web application if the web application runtime layer requests a web application execution;
Analyzing, structuring, and rendering a designated page from the pages included in the web application and outputting the rendered page to the browser engine layer;
Extracting one or more other pages included in the web application other than the output page;
Analyzing and structuring the one or more other pages;
Storing data of the structured other page;
Confirming occurrence of an event for the other page;
And rendering the data of the structured other page when the event occurs, and outputting the rendered data to the window. 14. The method of claim 13, wherein prior to creating the window and renderer instance,
Checking whether execution of the browser engine container core is performed by the execution layer when the execution request using the shortcut icon of the user's web application is input;
Loading the browser engine container core if the browser engine container core is not running; And
When the browser engine container core is executed, transmitting a web application execution command to a web application runtime layer of the browser engine container core;
The method of claim 1, further comprising: 14. The method of claim 13, wherein prior to creating the window and renderer instance,
Calling an execution API in response to a request for execution of a web application by a web application manager managing an installed web application;
Loading the system API plug-in wherein the browser engine container core provides an access interface to the core functionality; And
Transmitting the execution command of the web application to the context manager of the web application runtime layer unit;
The method of claim 1, further comprising: 14. The method of claim 13, wherein prior to creating the window and renderer instance,
The idle screen manager of the terminal receives the user's web application execution request and loads the idle mode agent of the execution layer; And
The standby mode agent loading the browser engine container core and invoking the idle screen mode execution API to deliver an execution request of the web application to the context manager of the web application runtime layer. How to do it. A computer-readable recording medium on which a program for executing the web application execution method according to any one of claims 13 to 16 is recorded.

Images