KR101482149B1 - Apparatus for executing application, method thereof and computer recordable medium storing the method - Google Patents

Abstract

The present invention relates to an application execution device, a method thereof, and a computer-readable recording medium on which the method is recorded. Even if an operating system does not support multiple execution or multiple instances of an object regardless of an operating system, The object receiving the request and the object executing the request may be separately provided so that the object receiving the request is executed only at the time of receiving the request and then forwarding to the executing object and terminating the request so that the operating system A plurality of applications can be executed.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to an apparatus for executing an application, a method thereof, and a computer-readable recording medium on which the method is recorded.

The present invention relates to an application execution technology of a terminal, and more particularly, to an application execution apparatus that provides an execution environment capable of simultaneously executing a plurality of applications regardless of the type of an operating system implanted in the terminal, The present invention relates to a computer-readable recording medium on which a method is recorded.

An operating system manages resources and functions of a terminal that is itself ported and when an application implanted in the terminal requests an application, a part of resources and functions of the terminal, All access can be granted to 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. Developers must therefore develop their applications in accordance with the format of the API provided by the operating system in order to develop applications for the device on which the particular operating system is being ported.

Various functions have been recently implemented in the terminal, and various types of peripheral devices providing additional implemented functions are added to the terminal. The functions of these peripheral devices are managed by the operating system. Therefore, APIs are required to access functions of peripheral devices managed by the operating system in order to develop an application in which developers can utilize such peripheral devices. Moreover, various types of operating systems are being ported in recent terminals. Since the application is not executed in the terminal having the different operating system, the application developer of the terminal has to issue the same application separately according to the API of each operating system.

In particular, only one instance (instance) is allowed for an object due to problems such as the performance of the operating system itself or the performance of the device to which the operating system is implanted. In this case, since a plurality of executions of the same object can not be performed, the development of the application is inconvenient for a developer developing the application. In order to use another application while executing one application, It is troublesome to terminate the application.

Therefore, an object of the present invention is to provide an application execution device capable of executing a plurality of applications regardless of an operating system, that is, even if the operating system supports only one execution for one object, And a computer readable recording medium.

According to an aspect of the present invention, there is provided an application execution apparatus including: a run-time manager having a command handler for receiving an execution command for executing an application; And a runtime manager for executing the runtime manager if the runtime manager is not running, and for executing an execution parameter, which is information for executing the application, in the command handler And a dummy container execution unit that transmits the execution command including the execution command and terminates the execution of itself.

In the application execution apparatus of the present invention, when receiving the application execution request, the dummy container execution unit checks whether the run time manager is executing, and when the run time manager is already executing, And transmits the execution command including the argument, and terminates execution of itself.

In the application execution apparatus of the present invention, the run-time manager may further include a context manager for executing an application, and the command handler transmits the execution command including the execution parameter to the context manager.

In the application execution device of the present invention, the application execution device may further include a browser engine rendering the application.

In the application execution apparatus of the present invention, the context manager executes the application according to the execution command, and calls the browser engine to render the executed application.

In the application execution apparatus of the present invention, the context manager creates a window of the application, and the browser engine displays the rendered result of the application on the window.

In the application execution device of the present invention, the browser engine includes an engine core for rendering a markup language and a style sheet of the application, and a script engine as an interpreter for processing the script language of the application.

The application execution apparatus of the present invention is characterized by comprising: a browser engine for receiving a request for executing a function supervised by the operating system from an executed application, regardless of the type of the operating system, A layer portion; And an implantation layer unit for instructing execution of a function corresponding to the function execution request by changing the function execution request according to the type of the operating system.

In the application execution apparatus of the present invention, the transplantation layer unit includes at least one interface module, and each of the interface modules has an interface according to the type of the function execution.

In the application execution device of the present invention, the interface is implemented in accordance with the type of the operating system for instructing execution of the corresponding function, and simultaneously with the container common module to receive a request from the container common module .

In the application execution device of the present invention, the interface module may include: an HTTP module for providing functions related to HTTP and HTTPS; An XML module providing an XML parser function and an XSLT transformation function; A thread module providing a thread function; A UI backend module that provides the operating system's own window system functionality needed to port the user interface; A secure storage module that provides access to secure storage; A local storage module that provides access to storage; A resource manager for providing functions related to resources of the terminal; An OS API manager that provides functions related to the OS API; A common task manager for providing a function for interworking with other applications; And a sink manager that provides functions related to data synchronization with other devices and interworking with other devices.

In the application execution apparatus of the present invention, the browser engine layer unit may include at least one plug-in for delivering the request to the transplantation layer unit corresponding to the type of the function execution; A plug-in manager that calls the plug-in corresponding to the type of the function execution; And a browser engine for instructing the plug-in to transmit a request for executing the function when the plug-in is called.

In the application execution apparatus of the present invention, the plug-in may include: a resource plug-in which transmits an execution request of a function related to terminal resources to the transplantation layer; A system API plug-in for transferring an execution request of an OS API-related function to the above-mentioned porting layer; A common task plug-in for transmitting an execution request of a function for interworking with another application to the transplantation layer; A sink plug for transmitting an execution request of a function related to data synchronization with another device and data synchronization with another device to the transplantation layer; Or the like.

In the application execution apparatus of the present invention, the application execution apparatus may further include a security layer unit, wherein the security layer unit includes: an authentication manager for performing authentication upon installation and execution of the application and the plug-in; And a policy manager for managing access ranges and access rights to the port layer of the browser engine layer unit.

The application execution device of the present invention further includes at least one peripheral device managed by the execution of the function of the operating system.

In the application execution apparatus of the present invention, the execution of the functions may include executing the functions of the operating system itself, using the resources in accordance with execution of the operating system's own functions, executing individual functions of the peripheral devices, And / or the use of resources according to < / RTI >

In the application execution device of the present invention, the peripheral device may include: a wireless communication unit for performing wireless communication; A GPS unit for receiving GPS signals from GPS (Global Positioning System) satellites; An input unit for receiving a user input; A display unit for displaying screen data generated according to use of the terminal; An audio processor having a microphone and a speaker for receiving and outputting a voice signal; A camera unit for performing a camera function; Or the like.

According to another aspect of the present invention, there is provided a method for executing an application, the method comprising: starting execution of the application in response to an application execution request from an operating system; Checking whether a runtime manager including a command handler for receiving an execution command for executing the application is executed; Executing the runtime manager if the runtime manager is not running; Transmitting an execution command including an execution parameter, which is information for executing an application, to the command handler; And a termination step of the dummy-container execution unit terminating its execution.

In the method of executing an application of the present invention, when the execution manager is already executing the execution of the command, transmitting an execution command including an execution parameter, which is information for executing the application, to the command handler, And the dummy container execution unit terminating execution of itself.

In the method of executing an application of the present invention, after the step of transferring, the command handler transfers the execution command having the execution parameter to the context manager; And causing the context manager to execute the application according to the execution command.

In the method of executing an application of the present invention, the execution factor may include at least one of an identifier of an application that can distinguish the application from another application, and an address of a page of an address of a plurality of pages constituting the application.

In the application execution method of the present invention, the execution of the application may include setting the address of the one page to the start page of the application and executing the address when the context manager receives the address of the page as the execution factor .

In the application execution method of the present invention, the execution of the application may be executed when the context manager receives the identifier as the execution argument, using the default page of the application having the corresponding identifier as the start address.

In the method of executing an application of the present invention, the context manager may call a browser engine to render the application after executing the application.

And a computer-readable recording medium on which an application execution method of the present invention is recorded.

According to the present invention as described above, when the dummy container execution unit receives the application execution request, the dummy container execution unit transmits the application execution command to the runtime manager that executes the application, terminates its own execution, Multiple runs of an application can be provided even if the operating system does not support multiple runs or multiple instances. Accordingly, it is possible to provide convenience for users to use the terminal.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a diagram for explaining a configuration of an application execution device according to an embodiment of the present invention; Fig.
2 is a diagram illustrating a structure of a platform in an application execution apparatus according to an embodiment of the present invention;
3 is a diagram for explaining a detailed configuration of a browser engine container execution unit in a platform according to an embodiment of the present invention;
4 illustrates an application runtime layer in a platform according to an embodiment of the present invention;
5 illustrates a browser engine layer in a platform according to an embodiment of the present invention.
6 is a diagram illustrating a detailed configuration of a security layer in a platform according to an embodiment of the present invention;
7 is a diagram for explaining an implantation layer in a platform according to an embodiment of the present invention;
8 illustrates a system application in a platform according to an embodiment of the present invention.
9 is a diagram for explaining a method of executing an application of a dummy container execution unit according to an embodiment of the present invention;
10 is a diagram for explaining a method of executing an application in a state in which no application is executed according to an embodiment of the present invention;
11 is a view for explaining a method of executing another application in a state where an application according to an embodiment of the present invention is executed;

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 is to be noted that the same constituent elements are denoted by the same reference numerals as possible throughout the drawings.

The terms and words used in the present specification and claims should not be construed as limited to ordinary or dictionary meanings and the inventor is not limited to the meaning of the terms in order to describe his invention in the best way. It should be interpreted 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, the configuration of an application execution apparatus according to an embodiment of the present invention will be described. 1 is a diagram for explaining a configuration of an application execution apparatus according to an embodiment of the present invention.

Referring to FIG. 1, an application execution apparatus according to an embodiment of the present invention includes a control unit 11, a storage unit 12, and a peripheral device 13.

The storage unit 12 is an apparatus for storing data, and includes a main storage device and an auxiliary storage device. The storage unit 12 stores the operating system 10, the platform 20, and the application 30, and stores various data generated according to the function of the terminal.

The control unit 11 is a processing device that actually drives the operating system 10, the platform 20, and the application 30. For example, the control unit 11 may be a central processing unit (CPU). When the terminal is powered on, the control unit 11 moves the operating system 10 from the auxiliary storage device to the main storage device, and then performs booting to drive the operating system 10. The control unit 11 executes the platform 20 at the top of the operating system 10 in a hierarchical structure when there is an execution request of the application 30 according to the user's operation and the platform 20 executes the application 20 30). As described above, the control unit 11 loads the platform 20 from the storage unit 12 and executes the platform 20. However, the platform 20 may be configured as one module in the control unit 11. [ Hereinafter, the platform 20 according to the embodiment of the present invention will be described with the configuration of the control unit 11. [

The control unit 11 controls the peripheral device 13 at the request of the operating system 10. That is, the operating system 10 controls the execution of functions of the terminal through the control unit 11. The execution of the functions of the terminal here includes the individual functions of the peripheral device 13 and the use of resources according to the execution of the individual functions and is performed by the operating system 10, Lt; RTI ID = 0.0 > function < / RTI >

Basically, when the operating system 10 requests execution of the terminal functions described above during execution of the application 30, the operating system 10 provides an interface to the application 30, and the application 30 sends the provided interface And requests the operating system 10 to execute the terminal function. Such an interface may be an application programming interface (API). This interface is implemented in the form of a library, and the library is implemented in a unique format for each operating system 10. Therefore, depending on the type of the operating system 10, the operating system 10 has a different type of interface that provides the same function. In this way, when the application 30 is executed by directly referring to the operating system 10, the application 30 must be implemented differently according to the type of the operating system 10.

The platform 20 provides an interface for executing the terminal function provided by the operating system 10 to be used by the application 30 and provides the interface 30 regardless of the type of the operating system 10 do. That is, although the operating system 10 provides the interface for executing the function of the terminal as an interface having a different format according to the type of the operating system 10, the platform 20 can use interfaces having different formats in one format And provides it to the application 30. In other words, when the application 30 requests execution of a terminal function through an interface having a single format, the platform 20 converts the request according to the format of the interface provided by each operating system 10, 10, and the operating system 10 performs this. Accordingly, the application 30 can access and control the resource or function of the terminal through the interface provided by the platform 20 in the same manner regardless of the type of the operating system 10. According to the embodiment of the present invention, the developers can reduce the effort of separately preparing the same application 30 for each operating system 10. In addition, users can use the application 30 with the same user experience in any operating system 10.

Meanwhile, in the embodiment of the present invention, the application 30 describes a web application as an example, and it is an application operating in a browser. These web applications are written in the web standard language. The web standard language can be exemplified by HTML (Hyper Text Markup Language), CSS (Cascading Style Sheet), JavaScript, and the like. However, the embodiment of the present invention is not limited to the web application, and it is natural that any application that can be driven by the terminal can be implemented in the equivalent range of the present invention.

According to the embodiment of the present invention, in order for the platform 20 to execute the application regardless of the type of the operating system 10, the application must be executed under the application hierarchically. However, there is a case in which multiple executions (instances) of the same object (Object) among the operating system 10 are not supported. In this environment, in order for the platform 20 to execute one application 30 and then execute another application 30, the execution thereof must be duplicated. However, since the operating system 10 does not support it, 30) can not be executed. Therefore, according to the embodiment of the present invention, the platform 20 separately includes an object for receiving the request to execute the application 30 and an object for executing the actual application 30. The object receiving the application execution request from the application 30 receives the execution request when there is a request to execute the application 30 from the operating system 10 and transmits the execution request to the object executing the application 30 of the platform 20 After that, it ends its own execution. In this way, the object receiving the execution request terminates its execution, so that whenever an application execution request is received from the operating system 10, the object can be newly executed and receive the request. The object executing the application 30 can execute a plurality of applications 30 regardless of whether the operating system 10 is supported or not by receiving an application execution request from the object receiving the execution request.

Each of the peripheral devices 13 has a unique function and the operating system 10 can control its execution through the control unit 11. [ The peripheral device 13 includes an input unit 14 having various keys for receiving a user's input, a display unit 15 for displaying screen data generated according to the execution of functions of the terminal, a wireless unit An audio processing unit 18 having a communication unit 16, a GPS unit 17 for receiving a GPS signal from a GPS (Global Positioning System) satellite, a microphone and a speaker for inputting and outputting a voice signal, And a camera unit 19 for carrying out the present invention. Although not shown, a peripheral device 13 of a terminal according to an embodiment of the present invention may include a storage medium inserting unit for inserting an external storage medium such as a memory card to store data, And a charging terminal. Although the variations of the portable devices vary greatly depending on the convergence trend of the digital devices, it is not possible to enumerate all of them, but it is also possible that devices equivalent to the above-mentioned peripheral device 13 are added to the terminal according to the embodiment of the present invention It will be understood by those skilled in the art that various changes and modifications may be made without departing from the scope of the present invention.

The operating system 10 manages the above-described function execution of the peripheral device 13 through the control unit 11. [ This is accomplished by the control unit 11 interpreting the execution command of the operating system 10 and the control unit 11 operating the peripheral device 13. [ When the application 30 requests the function execution of the terminal 20 through the interface provided by the platform 20, the application 30 transmits a function execution request of the platform 20 to the operating system 10, The operating system 10 causes the control unit 11 to execute the function of the peripheral device 13. [

Next, the platform 20 in the application execution apparatus according to the embodiment of the present invention will be described in more detail. 2 is a diagram for explaining the structure of a platform in an application execution apparatus according to an embodiment of the present invention.

2, a platform 20 according to an embodiment of the present invention includes a browser engine container core 21 (abbreviated as "container core") and a browser engine container executor ) Unit 200 (abbreviated as "container execution unit" hereinafter). In addition, the platform 20 further includes a system application 40.

The container execution unit 200 and its detailed configurations may be objects receiving an application execution request as described above. Further, the container core 21 and its detailed configurations may be objects that actually execute the application as described above. Therefore, the container executing unit 200 and its detailed configurations have the operating characteristics of executing their functions after they are executed, and ending their own execution immediately. This allows the container core 21 to execute a plurality of applications.

The container core 21 includes an application runtime layer 300, a browser engine layer 400, a security layer 500 and a porting layer 600 . The transplanting layer unit 600, the security layer unit 500, the browser engine layer unit 400, and the application runtime layer unit 300 are sequentially connected. The application runtime layer 300, the browser engine layer 400 and the security layer 500 except for the porting layer 600 in the container core 21 may include a browser engine container common module, 22: hereinafter abbreviated as "container common module").

Referring to the structure of the platform 20 as described above, the implantation layer 600 is directly connected to the operating system 10. The container executing unit 200 and the container common module 22 are connected to the porting layer unit 600 so that the container executing unit 200 and the container common module 22 can communicate with each other through the porting unit 600 10).

In particular, since the application 30 and the system application 40 are executed and are directly connected to the container common module 22, the application 30 and the system application 40 can access the operating system 10 through the container common module 22 and the porting layer 600 . When the application 30 wants to execute the function of the terminal, the application 30 requests the container common module 22 to do so. The container common module 22 then forwards the request to the transplantation layer 600 and the transplantation layer 600 forwards the request back to the operating system 10. At this time, the porting layer unit 600 converts the request according to the interface of the operating system 10 and transfers the converted request to the operating system 10. Accordingly, the operating system 10 executes the function requested by the application 30 through the control unit 11. [

The interface of the transport layer unit 600 is connected to the container common module 22 while being connected to the operating system 10. Thus, the interface of the portability layer 600 is implemented for each operating system 10 so that it can connect with each operating system 10 in connection with the operating system 10. In this way, the interfaces implemented by the respective operating systems 10 can be connected to either the container common module 22 or the implantation layer 600 so that they are mutually connected to each other between the container common module 22 and the implantation layer 600 It is implemented correctly. Accordingly, when the application 30 requests execution of a function governed by the operating system 10 in conformity with the container common module 22 regardless of the operating system 10, the container common module 22 executes the function common to the operating system 10, The application layer 30 can transmit the request of the application 30 to the porting layer unit 600 regardless of the type of the application. The transport layer unit 600 receiving this request can instruct the operating system 10 to execute the function according to the request for each operating system 10. [ Therefore, the application 30 can access the terminal resources or functions through the platform 20 regardless of the type of the operating system 10.

In the platform 20, the container common module 22 receives a request from the application 30, and the porting layer unit 600 instructs the application 10 to execute the function according to the request, do. For this purpose, the container common module 22 and the application 30 are implemented mutually, and the portable layer module 600 is implemented according to the type of each operating system 10. In addition, the container common module 22 must be able to transmit the request of the application 30 to the transplantation layer 600. Accordingly, the container common module 22 and the porting layer unit 600 are implemented mutually. As described above, since the platform 20 is formed between the application 20 and the operating system 10 in two hierarchical structures, that is, the container common module 22 and the porting layer unit 600, the application 30 and the operation Even if any one of the container 10 and the container 10 is changed, the entire platform 20 need not be changed and only the corresponding configuration among the container common module 22 and the transplantation layer 600 can be changed.

Next, the detailed structure of the platform 20 according to the embodiment of the present invention will be described in more detail. FIG. 3 is a view for explaining a detailed configuration of a browser engine container executing unit in a platform according to an embodiment of the present invention, FIG. 4 is a view for explaining an application runtime layer in a platform according to an embodiment of the present invention, Is a diagram for explaining a browser engine layer in a platform according to an embodiment of the present invention. 6 is a view for explaining the detailed configuration of the security layer in the platform according to the embodiment of the present invention, FIG. 7 is a view for explaining the porting layer in the platform according to the embodiment of the present invention, FIG. 4 is a diagram for describing a system application in a platform according to an embodiment of the present invention. FIG.

First, the container executing unit 200 according to the embodiment of the present invention will be described.

3 to 6, the container executing unit 200 plays a role of managing the general execution of the application 30, the execution in the standby mode, the updating of all or a part of the container core 21, and the like. The container execution unit 200 serves as an entry point of the application 30 and can generate the container core 21. [ The container execution unit 200 is not driven in the form of a daemon that continuously executes a process in the background after being executed, and executes the corresponding function after being executed and is immediately terminated. This is for driving a plurality of applications 30 even when the operating system 10 does not support multiple execution or multi-instance. That is, each of the container executing unit 200 and its detailed configuration is an object that receives an application execution request, as described above.

The container execution unit 200 includes a container agent 210, a dummy container execution unit 220, and a standby mode agent 230.

The container agent 210 includes an application launcher 211 and a container update module 213. When the container agent 210 is requested to execute the application 30, the container agent 210 performs a trigger operation to execute the application 30.

Triggering the execution of the application 30 is accomplished by the application launcher 211 delivering the execution factor to the application runtime layer 300 through the dummy container execution unit 220. The application launcher 211 may transmit at least one of an identifier (ID) and an address (URL) of the application 30 as an execution parameter so that the application 30 is executed. At this time, when the address (URL) of the application 30 is transmitted as an argument, the application 30 can be executed with the corresponding address as the start page. When only the name or identifier (ID) of the application 30 is passed as a parameter, a default page extracted from the metadata of the package in which all the source files of the application 30 are stored is set as a start page . Here, the default page is extracted from the metadata of the application 30 when the application 30 is installed and registered through the registry manager 320.

The container agent 210 plays a role of updating part or all of the container core 21. The update can be performed according to the following two methods. First, there is a way for the server for updating to trigger the container agent 210 to perform the update, which may illustrate that the server triggers the container agent 210 via "SMS push" . Second, there is a method in which the container agent 210 periodically checks for update. This is a method of self-checking whether the container agent 210 periodically performs update. The above-described update may be performed by the container update module 213. [ The container update module 213 can update all of the container core 21 or update each configuration of the container core 21. [ That is, since the container core 21 is modularized into a plurality of detailed configurations, the container update module 213 can update each configuration individually. In particular, in the case of the plug-in 430 of the browser engine layer 400, a plug-in 430 for implementing a new function may be additionally provided. In addition, the container update module 213 can update data used by each configuration of the container core 21. For example, the security policies of the security layer 500 may be newly updated.

The dummy container execution unit 220 is requested to execute an application from the operating system 10 or the container agent 210 and executes the runtime manager 310 of the application runtime layer 300 that is in charge of execution of the application . Then, the dummy container execution unit 220 transmits an execution command to the command handler 311 of the runtime manager 310, and then ends its execution. At this time, if the runtime manager 310 is already executing, the execution manager 310 simply passes the execution command to the command handler 311, and then ends its execution. Here, when the dummy container execution unit 220 delivers the execution command, it means that the control authority is handed over to the runtime manager 310 of the container core 21.

In particular, after the dummy container execution unit 220 hands over the control, the execution of the self-execution is terminated when the operating system 10 does not support multiple execution or multiple instances of the same object, . That is, since the execution request of the application from the operating system 10 is a single execution (single instance) and the execution of the application is performed in the runtime manager 310, the operating system 10 The application can be run multiple times at any time.

When the dummy container execution unit 220 transmits an application execution request to the dummy container execution unit 220 through the application launcher 211, The execution of itself is terminated after the execution request. This is the reason why the dummy container execution unit 220 ends its execution after sending the execution command.

When delivering an execution request, the dummy container execution unit 220 transmits an execution parameter, which is information for executing the application 30, together. Here, the execution parameter includes an identifier and an address, and an address may be omitted. Here, the identifier is for distinguishing the application 30 from the other applications 30. Therefore, when the application 30 is executed, the application 30 can be executed separately from the other applications 30 through the identifier of the execution factor. On the other hand, one application 30 is made up of a plurality of pages, and each page is assigned an address. In addition, the application 30 is executed by using any one of a plurality of pages as a start page. Therefore, when an address is included in the execution parameter, the application 30 can be executed with the address as the start page. When the address is not included in the execution parameter, the application 30 can be executed with the default page set as a start address set in advance when the application 30 is installed.

The application module 30 is a module for operating the application on the idle mode screen of the terminal, and is implemented in accordance with each idle mode component protocol (IDLE Component Protocol) for each operating system 10.

Next, the application runtime layer unit 300 according to the embodiment of the present invention will be described.

3 to 6, the application runtime layer 300 provides an application execution environment and functions as a kernel of the entire platform 20. Application runtime layer 300 When the application 30 is created, it manages the generated application 30 and manages registry information and UI (User Interface) for application installation and configuration information setting do.

When the application 30 is executed, the runtime manager 310 manages the context of the application 30, performs event handling, and if there is an instruction from the container execution unit 200 , And processes this command. To this end, the runtime manager 310 includes a command handler 311, a context manager 313, an event handler 315, and a life cycle manager 317.

The command handler 311 is an IPC command processor that receives commands from the container execution unit 200 via an inter-process communication (IPC) method, analyzes the commands, and performs an operation corresponding to each command. The command handler 311 performs the following operations according to the command. The command handler 311 may request the context manager 313 to execute or terminate the application 30. In addition, the command handler 311 can update the configuration information of the platform 20 through the registry manager 320. Then, the command handler 311 can organize resources and terminate the platform 20, which is a process of itself. This is to terminate the running platform 20 process at the time of updating the platform 20 against the operating system 10 which does not provide the other process termination function. In addition, the command handler 311 may request the plug-in manager 420 to install, delete, and update the plug-in 430.

The context manager 313 manages the context of the application 30 and manages the creation and destruction of the browser engine 410 renderer and window. When the execution of the application 30 is requested from the command handler 311, the context manager 313 creates a window according to a window creation command from the browser engine 410. [ Next, the context manager 313 creates a renderer of the browser engine 410. The context manager 313 then renders the requested page through the generated renderer and displays the rendered result in the generated window. The context manager 313 may receive a command from the command handler 311 to terminate the browser or an instruction to instruct the event handler 315 and the browser engine 410 to extinguish the window. In this case, the context manager 313 retrieves the renderer and window resources of the browser engine 410, and then terminates the application 30 or extinguishes the window. In addition, the context manager 313 terminates the corresponding application 30 when all the windows owned by the application 30 are destroyed.

The event handler 315 receives and processes window related events generated by the context manager 313 and system related events extended from the platform 20 itself. On the other hand, since the event related to the browser engine 410 is handled directly by the browser engine 410, the event handler 315 does not process the event related to the browser engine 410. [

The lifecycle manager 317 manages the life cycle of the application and the windows and pages of the application. The application 30 may comprise a plurality of pages. Also, at least one window is created for each application 30, and at least one page is displayed through a window. If you navigate to another page, the previous page may disappear. In addition, if all windows associated with the application 30 are closed, the application 30 is terminated. As described above, there is a life cycle of the application 30, the window and the page of the application 30, and the life cycle manager 317 manages the life cycle.

The registry manager 320 is a module for managing application 30 installation information and configuration information of the platform 20 and actual information can be stored in a secured area through a security manager 625 . The registry manager 320 provides functions related to the application 30, the platform 20, and the plug-in 430. The function provided by the registry manager 320 is as follows according to the subject.

The UI engine 330 is responsible for all UI and user input processing other than the area rendered by the browser engine 410. More specifically, it is responsible for display of all areas except the content area of the application 30, and the status bar area and the soft button area correspond to this. Here, the status bar area is an area for displaying icons representing the status of the terminal, and is mainly disposed at the top of the display part 15. In this area, an icon indicating the received signal strength, an icon indicating the battery remaining amount, An icon indicating whether the mode is displayed or the like may be displayed. The soft button area is an area for displaying a basic key such as a "menu" key, an "OK" key, a cancel key, etc. when the terminal employs a full- As shown in Fig.

The network selector 340 is a module for providing a function of setting and managing a network to be used by the container core 21 and a method for selecting a network (e.g., modem, Wi-Fi, Bluetooth, Allows you to set a ranking. The network selection method offers three options: automatic, manual, and semi-automatic. If it is automatic, it connects through the connectable network according to the set priority. If the number is the same, it tries to connect only to the selected network. If it is semi-automatic, it pops up every time a network connection or switching is requested, .

The application synchronization manager 350 is a module for ensuring seamless execution of the application 30 irrespective of whether the terminal is on line or offline or not. (Caching Mechanism), and when connected to the network, performs auto synchronization in the background while the user does not recognize the data stored in the local storage .

Next, the browser engine layer unit 400 according to the embodiment of the present invention will be described.

5 and 7, the browser engine layer 400 includes a browser engine 410, a plug-in manager 420, and a plurality of plug-ins 430 managed by the plug-in manager 420 ).

The browser engine 410 interprets the application 30, displays it on the screen, and executes it. To this end, the browser engine 410 includes an engine core 411 for processing a markup language and a style sheet, and a script engine 413, which is an interpreter for processing a script language. The browser engine 410 also includes 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 XML parser functionality and XSLT transformation functionality. The window processor provides a window system to be used by the browser engine 410 and provides a UI widget such as a button, a list box, a combo box, and a text editor to be used by the engine core 411. The font processor provides a font system to be used by the engine core 411. The image decoder processor provides an image decoder function to be used by the engine core 411. The internationalization processor provides the string conversion function necessary for multilingual processing. The system handler provides system functions such as a timer. The browser engine 410 includes a protocol processor, an XML processor, a window processor, a font processor, an image decoder processor, an internationalization processor, a system processor, and the like. 10).

Meanwhile, the browser engine layer unit 400 may provide the function through the plug-in 430 when the application 30 requests a function other than the web standard function. Here, the function other than the Web standard function means that the function of the terminal managed by the operating system 10 is executed. For example, this may be a device-dependent function such as an address book or interworking with other applications.

When the application 30 requests execution of a function supervised by the operating system 10, the browser engine 410 calls the plug-in 430 having the corresponding function through the plug-in manager 420, The application layer 430 transmits a request of the application 30 to the interface module 610 providing the corresponding function in the layer 600. [ This delivery method allows the interface module 610 to provide a single type of interface, regardless of the operating system 10, so that the plug-in 430 can always request the function in the same format, regardless of the operating system 10. [ . In response to the request of the plug-in 430, the corresponding interface module 610 executes the function of the terminal requested by the application 30 through the operating system 10. In order to perform such a function, the interface module 610 changes the format of each operating system 10 according to the above-described request and directs the operating system 10 to change the format.

As described above, by designing the browser engine layer unit 400 as a structure that dynamically combines the plug-in 430 with the browser engine 410, the following advantages can be obtained. When the browser engine 410 is updated, the latest browser engine 410 can be quickly applied to the platform 20 without any modification. There is also the advantage that extensions of functions that are not currently understood can be provided consistently in the form of plug-ins 430. For example, if a plug-in capable of playing a specific type of media is required, it can be developed and added to the plug-in 430.

The plug-in manager 420 and the plug-in 430 will now be described in more detail.

The plug-in manager 420 manages the plug-in 430. That is, the plug-in manager 420 manages the list of the installed plug-ins 430, downloads and installs the new plug-ins 430, updates existing plug-ins 430 existing therein, If there is an execution request, the corresponding plug-in 430 is called according to the type of execution of the function.

In the embodiment of the present invention, the plug-in 430 includes a resource plug-in 431, a system API plug-in 433, a common operation plug-in 435, And a Sync Plug-In (437).

The resource plug-in 431 transmits the resource plug-in 431 to the resource manager 621 of the transplantation layer 600 when the application 30 requests the function execution related to the terminal resource. Accordingly, the resource manager 621 executes the corresponding function. That is, the resource manager 621 can provide the terminal resources through the execution of the functions of the operating system 10.

The system API plug-in 433 transmits the OS API manager 623 of the transplantation layer 600 to the application 30 when the application 30 calls the OS API related function. Accordingly, the OS API manager 623 of the porting layer unit 600 executes the corresponding function.

The common job plug-in 435 transmits the request to the common operation manager 625 of the porting layer unit 600 when the application 30 requests interworking with another application. Then, the common task manager 625 executes the corresponding function.

The sink plug-in 437 transfers the synchronization plug-in 437 to the sink manager 627 of the implantation layer 600 when the application 30 calls a function related to interlocking with another device and data synchronization with another device. Then, the sink manager 627 executes the corresponding function.

Next, the security layer 500 according to the embodiment of the present invention will be described.

3 to 7, the security layer 500 performs authentication of accesses of the application layer unit 300 and the browser engine layer unit 400 to the access layer unit 600, Grant some or all of the access in accordance with the policy. The security layer 500 includes an authentication manager 510 and a policy manager 520.

The authentication manager 510 performs authentication for the application 30 and the plug-in 430 during installation and execution. Here, at the time of installation, authentication is a procedure for confirming whether the application 30 and the plug-in 430 are installed by a proper procedure. At the time of execution, authentication is performed by the application 30 and the plug- In order to confirm whether or not it has been installed. For this authentication, the authentication manager 510 has a hashing algorithm and various security libraries, and performs an authentication function accordingly.

The policy manager 520 receives a file describing a policy for access control from the container update module 213, and installs and stores the file. The policy manager 520 searches the pre-stored policies for access requests of the plug-ins 430 and accepts or rejects some or all of the accesses according to the policy. The policy manager 520 may update the policy for that access control in real time.

Next, the transplantation layer unit 600 according to the embodiment of the present invention will be described.

3 to 7, the porting layer unit 600 includes an operating system 10 (FIG. 3) so that the application 30 can be implemented and operated by the container common module 22 regardless of the type of the operating system 10 ) In the form of a single type of interface. To this end, the interface of the transport layer unit 600 may be implemented according to the operating system 10, and may be implemented between the transport layer unit 600 and the container common module 22. In addition, the application 30 requests the function common to the container common module 22 to execute the function.

Accordingly, when the application 30 requests the container common module 22 to execute the function, the container common module 22 can deliver it to the transplantation layer unit 600. The porting layer unit 600 may instruct the operating system 10 to execute the corresponding function through the function execution request received from the container common module 22.

The transplanting layer unit 600 includes a plurality of interface modules 610, and each interface module 610 includes a plurality of interfaces related to each function. Each interface is capable of executing the functions of the terminal according to the type of the operating system 10 and can receive a function execution request according to the container common module 22. Accordingly, An accessible interface can be provided regardless of the operating system 10.

The interfaces within the interface module 610 can be implemented and managed in the form of libraries, respectively. If it is desired to further provide an interface for executing the added functions, it is possible to define a separate interface, implement it in the form of a library, and link it to the corresponding interface module 610. Such an interface may be implemented to execute the corresponding function through the operating system 10 according to the type of the operating system 10 or may be implemented by a request of the container executing section 200, the container common module 22, And may be a stub that converts only the format for each operating system 10 and bypasses the operating system 10 to the operating system 10.

The interface module 610 includes a hypertext transfer protocol (HTTP) module 611, an extensible markup language (XML) module 613, a thread module 615, a UI backend module 617, a secure storage module 619, a resource manager 621, an OS API manager 623, a collaboration manager 625, a sync manager 627, Manager (Local Storage Manager, 629).

The HTTP module 611 basically includes an interface having HTTP and HTTPS related functions. In order for the browser engine 410 to operate, an HTTP protocol processor capable of delivering application contents to the browser engine 410 is required, and the HTTP module 611 includes an interface for providing the HTTP protocol processor function. For example, the HTTP module 611 may include an interface having functions such as socket creation, TCP / IP (/ l) connection, data transmission, data reception, HTTP communication connection, data request, SSL Can be provided. The HTTP module 611 has a separate library, and each library is separately implemented and managed. Each library may be a code that actually implements the requirements according to the level of function support associated with HTTP of the operating system 10 or may simply be a stub that passes the request of the browser engine 410 to the OS There is also.

The XML module 613 includes an interface that provides an XML parser function and an interface that provides an XSLT (Extensible Style Sheet Language Transformation) conversion function. The XML parser function is a function to convert HTML contents into a DOM (Document Object Model) tree format, and the XSLT transformation function is a function to convert an XML document through XSLT. The browser engine 410 needs these XML parser functions and XSLT transform functions to render the application 30. [ Accordingly, the XML module 613 provides a simple link when the XML parser 613 can use the XML parser function and the XSLT transformation function in the operating system 10, and if not, the actual implementation code is provided through the interface do.

The thread module 615 includes an interface having a thread function. Here, the thread function refers to processing the priority or the like when the application 30 processes a plurality of commands. The interface of the thread module 615 is used in the runtime manager 310 and the browser engine 410.

The UI backend module 617 includes an interface that provides the window system functionality of the operating system 10 itself, which is required to port the user interface (UI) of the browser engine 410. In order for the browser engine 410 to display the content provided by the application 30 on the display unit 15, a button, a list box, a combo box, an edit box, You need a widget that provides a variety of UIs. Accordingly, the UI backend module 617 obtains a widget of the UI required by the application 30 from the operating system 10 and delivers it to the browser engine 410. The UI backend module 617 also transfers the font system of the operating system 10 to the browser engine 410. In addition, the interface of the UI backend module 617 allows display and selection of screen telephony effects.

The secure storage module 619 includes an interface for accessing secure storage. Here, the secure storage stores data to which security is to be applied. This interface handles the data to be secured by the authentication manager 510 and the policy manager 520 of the security layer 500 and this data is stored in secure storage through the interface of the secure storage module 619. [ Meanwhile, in the case of a terminal or device without secure storage, the secure storage module 619 may further include an interface that provides a function of encrypting and decrypting data in real time by applying an encryption algorithm in software.

The resource manager 621 provides an interface for accessing terminal resources. Such terminal resources may be data generated according to the execution of the peripheral device 13 of the terminal. For example, the terminal resources include a phone book, a photo, a call history, and a short messaging service (SMS) list. This interface allows access to the terminal resources according to the type of the operating system 10 and receives an access request for the terminal resources from the container common module 22. [ Therefore, the application 30 can be provided with an interface for accessing resources of the terminal irrespective of the operating system 10. The resource manager 621 has a separate library for each resource, and each library is separately implemented and managed. If a separate interface is provided for each resource and an interface for accessing the added resource is to be additionally provided, a separate interface can be defined and implemented in a library form, and then linked to the resource manager 621.

The resource manager 621 can provide the following functions through the interface. The resource manager 621 can provide the reception time, the call time, the sender, etc. with the list of the received and sent SMS messages, the details of each SMS message, and the details of the received and transmitted voice or video calls . The resource manager 621 also provides a list of each individual on the phonebook and detailed information about each personal list, and may provide a list of groups on the phone book and a list of individuals belonging to each group. The resource manager 621 can provide a list of schedule, alarm, memo, and detailed information. In addition, the resource manager 621 can provide detailed information on photographs, videos, music, and the like and a path through which each original data can be accessed.

The OS API manager 623 provides a terminal control function of the operating system 10 itself and includes an interface for providing such a function. OS API manager 623 provides the following terminal functions through the interface. The OS API manager 623 provides terminal functions such as voice call, video call, text message function, landmark information, and location information provision. In addition, the OS API manager 623 can provide a function of registering and releasing an application on the idle screen of each operating system 10. [ The OS API manager 623 provides a terminal function for creating or deleting audio or video data and has functions such as execution, pause, and stop of the generated audio or video data, volume and video output A terminal function for specifying a location can be provided. In addition, the OS API manager 623 can provide functions such as camera preview setting and capturing, and a terminal function for controlling input and output such as serial communication and local communication.

The common task manager 625 includes an interface that provides an interworking function with other applications operating in each operating system 10. These other applications may be related to phone books, cameras, music players, dialers, SMS, and the like. Using the interface provided by the common task manager 625, the application 30 can be interworked with the above-mentioned other applications.

The sink manager 627 includes an interface that provides a function of exchanging data in real time in cooperation with another device. When the terminal attempts to exchange data with the other apparatus in real time, the operating system 10 allows the terminal to interwork with the other apparatus and acquires synchronization with data of the other apparatus. Thus, the interface of the sink manager 627 provides the functionality of the operating system 10 to provide the interworking and synchronization described above.

The local storage module 629 includes an interface for abstraction of a unique storage function existing in each operating system 10 and consistently providing it to an upper layer regardless of its type.

Next, the system application 40 according to the embodiment of the present invention will be described.

4, 5, and 8, the system application 40 provides functions such as downloading and installation of the application 30, and the like. In addition, the system application 40 can provide a list of the installed applications 30 and the installed applications 30. The system application 40 itself is created in the form of an application 30, so it is connected to the container common module 22 and operates in the same manner as the application 30. The system application 40 includes an application manager 41 and an application downloader 43.

The application manager 41 accesses the registry manager 320 of the application runtime layer 300 through the system API plug-in 433 to obtain the information of the installed application 30 and displays it through the UI Role.

The application downloader 43 downloads and installs the application 30 from the server.

Next, an application execution method according to an embodiment of the present invention will be described. The operation of the dummy container execution unit 220 will be described below. FIG. 9 is a diagram for explaining an application execution method of the dummy container execution unit according to the embodiment of the present invention.

Referring to FIG. 9, the dummy container execution unit 220 assumes that its own execution is terminated. In this state, the dummy container execution unit 220 starts execution of itself by receiving a request to execute the application 30 in step S901. Here, the start of execution means to instantiate the object. That is, the dummy container execution unit 220 is an object, and the dummy container execution unit 220 starts execution, which means that the dummy container execution unit 220 is instantiated.

In this manner, the dummy container execution unit 220 that has started executing checks whether the runtime manager 310 is executing in step S903. If the runtime manager 310 is running, it means that at least one other application 30 is already running. If the runtime manager 310 is not running, it means that no application 30 is running. When the runtime manager 310 is running, the command handler 311, the context manager 313, the event handler 315, and the life cycle manager 317, which are internal components of the runtime manager 310, it means.

If it is determined in step S903 that the runtime manager 310 is already executing, the dummy container execution unit 220 sets the execution argument to execute the application 30 in the command handler 311 of the runtime manager 310 in step S907 Send the execute command together. Here, the execution factor includes at least one of an identifier of an application and an address of a page of pages constituting an application. Then, the dummy container execution unit 220 ends its execution in step S909.

On the other hand, if it is determined in step S903 that the runtime manager 310 is not running, the dummy container execution unit 220 executes the runtime manager 310 in step S905. Executing the runtime manager 310 is like executing the command handler 311, the context manager 313, the event handler 315 and the life cycle manager 317, which are internal components of the runtime manager 310. Accordingly, the dummy container execution unit 220 transmits an execution command together with the execution argument to execute the application 30 in the command handler 311 of the runtime manager 310 in step S907. Here, the execution factor includes at least one of an identifier of an application and an address of a page of pages constituting an application. Then, the dummy container execution unit 220 ends its execution in step S909.

The dummy container execution unit 220 that triggers the execution of the application 30 and the runtime manager 310 that actually executes the application 30 are made up of different objects. The multi-execution of the application 30 can be performed even if the application 10 does not allow a plurality of instances.

The runtime manager 310 can actually execute the application 30 and execute a plurality of applications 30 after execution of itself. However, in the case of the operating system 10 that does not support multi-instance, in order to execute a plurality of applications 30, the runtime manager 310 must be executed at least twice, .

Therefore, the present invention is executed every time the dummy container execution unit 220 requests execution of the application 30, and issues an execution command to the runtime manager 310 to execute the application 30 together with the execution factor , And by ending its own execution, it is possible to execute a plurality of applications 30 even in the operating system 10 that does not support multi-instance.

Next, a method of executing the application 30 according to the embodiment of the present invention will be described in more detail. At this time, a method of executing the application 30 in a state in which no application 30 is executed, and a method of executing another application 30 in a state in which at least one application 30 is executed .

10 is a diagram for explaining a method of executing an application in a state in which no application is executed according to the embodiment of the present invention. It is assumed in FIG. 10 that no application 30 is being executed. Also, according to the embodiment of the present invention, the dummy container execution unit 220 is also in a state where the execution is finished.

Referring to FIG. 10, when the user requests to execute a specific application 30 through the input unit 14, the control unit 11 senses the input, and the detection of the input is performed through the operating system 10. Accordingly, the operating system 10 executes the dummy container execution unit 220 in step S1001 and delivers the execution request for the specific application 30 of the user together with the execution parameter of the application 30 to execute.

Since no application 30 is running, the runtime manager 310 is not running. Accordingly, the dummy container execution unit 220 receiving the execution request of the application 30 executes the runtime manager 310, which plays the role of actually executing the application 30 in step S1003. As the runtime manager 310 is executed, the command handler 311 and the context manager 313, which are components of the runtime manager 310, are also executed. Therefore, in step S1005, the dummy container execution unit 220 transmits an execution command together with an execution command to execute the application 30 in the command handler 311. [ Then, the dummy container execution unit 220 ends its execution in step S1007. Here, step S1007 is performed immediately after step S1005 regardless of the order of execution of steps S1009 to S1013 after step S1007. In this manner, the dummy container execution unit 220 transmits the application 30 execution command and immediately terminates the operation so that the operating system 10 that does not support the multi-execution is ready to receive another application 30 execution request .

On the other hand, the command handler 311 that receives the execution command including the execution parameter causes the context manager 313, which is an internal configuration of the runtime manager 310, to execute the application 30 corresponding to the execution parameter Command. Then, the context manager 313 executes the corresponding application 30 in step S1011. At this time, the context manager 313 calls the browser engine 410 of the browser engine layer 400 to execute the application. At this time, the browser engine 410 performs rendering of the application in step S1013.

11 is a diagram for explaining a method for executing another application in a state where an application according to an embodiment of the present invention is executed. In FIG. 11, it is assumed that at least one application 30 is in execution and the dummy container execution unit 220 is in a state of being in execution.

Referring to FIG. 11, when the user requests to execute a specific application 30 through the input unit 14, the control unit 11 senses this, and the detection of such input is performed through the operating system 10. Accordingly, the operating system 10 executes the dummy container execution unit 220 in step S1101 and delivers the execution request for the specific application 30 of the user together with the execution parameter of the application 30 to execute.

The command manager 311 and the context manager 313 which are components of the runtime manager 310 are also executed because the runtime manager 310 is in the running state because any one of the applications 30 is running It is. Therefore, in step S1103, the dummy container execution unit 220 provides the execution command with the execution command to execute the application 30 in the command handler 311. [ Then, the dummy container execution unit 220 ends its execution in step S1105. Here, step S1005 is performed immediately after step S1003 irrespective of the execution order of steps S1107 to S1111 after step S1005. In this manner, the dummy container execution unit 220 transmits the application 30 execution command and immediately terminates the operation so that the operating system 10 that does not support the multi-execution is ready to receive another application 30 execution request .

On the other hand, the command handler 311 receiving the execution command provides the execution command to the context manager 313, which is an internal configuration of the runtime manager 310, so that the application 30 corresponding to the execution parameter is executed in step S1107. Then, the context manager 313 executes the corresponding application 30 in step S1109. At this time, the context manager 313 calls the browser engine 410 of the browser engine layer 400 to execute the application 30, and the browser engine 410 performs rendering of the application in step S1111.

As described above, according to the application 30 execution request, the dummy container execution unit 220 processes the process of triggering the execution of the application 30, and immediately terminates its execution, It is possible to execute a plurality of different applications 30 even when the application does not support multiple execution or multi-instance for one object.

The method for executing the application 30 according to the embodiment of the present invention may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable recording medium. 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.

It should be noted that the embodiments of the present invention disclosed in the present specification and drawings are only illustrative of specific examples for the purpose of understanding and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical idea of the present invention are possible in addition to the embodiments disclosed herein.

The present invention relates to an application execution apparatus applied to various types of user apparatuses such as a mobile communication terminal, a PMP, a PDA, a notebook, and an MP3 player, a method thereof, and a computer readable recording medium on which the method is recorded. An object for receiving a request and an object for executing an application. The object is executed only when an object receiving the application execution request receives the execution request, and the received execution request is transmitted. After the object is terminated, By preparing for another execution request, multiple executions of an application can be performed even when the operating system does not support multiple executions (instances). When using the platform according to the embodiment of the present invention, Multiple executions of an application can be performed, and for this reason, Because of the degree to which the potential not only be sufficient to explicitly carried in reality there is industrial applicability.

10: Operating system 11:
12: storage part 13: peripheral device
14: input unit 15: display unit
16: wireless communication unit 17: GPS unit
18: audio processing unit 19: camera unit
20: Platform 21: Browser Engine Container Core
22: Browser Engine Container Common Module
30: Application 40: System Application
41: Application Manager 43: Application Downloader
200: Browser engine container execution unit 210: Container agent
211: Application Launcher 213: Container Update Module
220: dummy container execution unit 230: standby mode agent
300: Application runtime layer 310: Runtime manager
311: Command Handler 313: Context Manager
315: Event Handler 317: Life Cycle Manager
320: Registry manager 330: UI engine
340: Network Selector 350: Application Sync Manager
400: Browser Engine Layer 410: Browser Engine
411: engine core 413: script engine
420: Plug-in Manager 430: Plug-in
431: Resource plug-in 433: System API plug-in
435: Common operation plug-in 437: Sync plug-in
500: security layer unit 510: authentication manager
520: Policy Manager
600: Portion layer unit 610: Interface module
611: HTTP module 613: XML module
615: Thread module 617: UI backend module
619: Secure Storage Module 621: Resource Manager
623: OS API Manager 625: Common Operations Manager
627: Sync manager 629: Local storage module

Claims (25)

In an application execution device,
A runtime manager having a command handler for receiving an execution command for executing an application, the execution manager receiving the execution command and executing the application; And
The method of claim 1, further comprising: determining whether the runtime manager is running when the application execution request is received from the operating system; executing the runtime manager if the runtime manager is not running; And a dummy container execution unit for sending the execution command to terminate the execution of the application. The apparatus of claim 1, wherein the dummy container execution unit
When the runtime manager is already executing, transmitting the execution command including an execution parameter, which is information for executing an application, to the command handler, And terminates the execution of the application. The method of claim 1, wherein the runtime manager
Further comprising a context manager for executing the application,
And the command handler delivers the execution command including the execution parameter to the context manager. 4. The system according to claim 3, wherein the application execution device
And a browser engine for rendering the application. 5. The application execution device according to claim 4, wherein the context manager calls the browser engine to execute the application according to the execution command and render the executed application. 6. The method of claim 5, wherein the context manager
Wherein the browser engine generates a window of the application, and the browser engine displays the rendered result of the application on the window. 5. The method of claim 4, wherein the browser engine
An engine core for rendering a markup language and a style sheet of the application; And
And a script engine which is an interpreter for processing a script language of the application. The method according to claim 1,
A browser engine layer for receiving a request for executing a function supervised by the operating system and transmitting a request for executing the received function, regardless of the type of the operating system, after executing the application; And
Further comprising: an import layer unit for changing the function execution request according to the type of the operating system and instructing execution of a function corresponding to the function execution request. 9. The apparatus of claim 8, wherein the implantation layer
And at least one interface module, wherein each of the interface modules has an interface according to the type of the execution of the function. 10. The apparatus of claim 9, wherein the interface
Wherein the container common module is implemented in accordance with the type of the operating system to instruct execution of the corresponding function, and is configured to be mutually compatible with the container common module in order to receive a request from the container common module. 10. The apparatus of claim 9,
An HTTP module providing HTTP and HTTPS related functionality;
An XML module providing an XML parser function and an XSLT transformation function;
A thread module providing a thread function;
A UI backend module that provides the operating system's own window system functionality needed to port the user interface;
A secure storage module that provides access to secure storage;
A local storage module that provides access to storage; A resource manager for providing functions related to resources of the terminal;
An OS API manager that provides functions related to the OS API;
A common task manager for providing a function for interworking with other applications; And
And a sink manager for providing functions related to data synchronization with other apparatuses and interlocking with other apparatuses. 9. The apparatus of claim 8, wherein the browser engine layer
At least one plug-in for delivering the request to the grafting layer portion in correspondence with the type of function execution;
A plug-in manager that calls the plug-in corresponding to the type of the function execution; And
And a browser engine for instructing the plug-in to transmit a request for executing the function when the plug-in is called. 13. The plug of claim 12, wherein the plug-
A resource plug-in for transmitting an execution request of a function related to terminal resources to the transplantation layer;
A system API plug-in for transferring an execution request of an OS API-related function to the above-mentioned porting layer;
A common task plug-in for transmitting an execution request of a function for interworking with another application to the transplantation layer; And
A sink plug for transmitting an execution request of a function related to interlocking with another device and data synchronization with another device to the transplanting layer; The application executing apparatus comprising: 13. The apparatus of claim 12, wherein the application execution device further comprises a security layer,
An authentication manager for performing authentication when the application and the plug-in are installed and executed; And
And a policy manager for managing an access range and an access right to the port layer of the browser engine layer unit. 9. The method of claim 8,
And at least one peripheral device managed by the execution of the function of the operating system. 16. The method of claim 15,
And at least one of execution of the operating system's own functions, use of resources in accordance with execution of the operating system's own functions, execution of individual functions of the peripheral devices, and use of resources in execution of individual functions of the peripheral devices To the application execution unit. 16. The system of claim 15,
A wireless communication unit for performing wireless communication;
A GPS unit for receiving GPS signals from GPS (Global Positioning System) satellites;
An input unit for receiving a user input;
A display unit for displaying screen data generated according to use of the terminal;
An audio processor having a microphone and a speaker for receiving and outputting a voice signal; And
A camera unit for performing a camera function; The application executing apparatus comprising: In an application execution method,
The dummy container execution unit initiating execution of itself according to an application execution request from the operating system;
Checking whether a runtime manager including a command handler for receiving an execution command for executing the application is executed;
Executing the runtime manager if the runtime manager is not running;
Transmitting an execution command including an execution parameter, which is information for executing an application, to the command handler; And
And terminating the execution of the dummy-container executing unit itself by the dummy-container executing unit. 19. The method of claim 18,
Transmitting an execution command including an execution parameter, which is information for executing an application, to the command handler if the runtime manager is already executing the command; And
Ending execution of the dummy container execution unit itself;
Lt; RTI ID = 0.0 > 1, < / RTI > 19. The method of claim 18,
The command handler delivering the execution command including the execution parameter to the context manager; And
And executing the application according to the execution command by the context manager. 21. The method of claim 20,
An identifier for distinguishing the application from other applications, and an address of one page among a plurality of page addresses constituting the application. 22. The method of claim 21,
And when the context manager receives the address of the page as the execution parameter, the context manager sets the address of the page as the start page of the application and executes the application. 22. The method of claim 21,
And when the context manager receives the identifier as the execution parameter, executes the application with the default page of the application having the corresponding identifier as the start address. 21. The method of claim 20, further comprising: after executing the application,
And the context manager calls a browser engine to render the application. A computer-readable recording medium on which the method according to any one of claims 18 to 24 is recorded.

Images