KR102020045B1 - Method for executing hybirid web application and apparatus therefor - Google Patents

Abstract

An apparatus and method for executing a hybrid web application is disclosed. Hybrid web applications are written in system API calls and standard web languages. The hybrid web application executing apparatus requests the processing corresponding to the system API call to the hybrid web application interface layer, and calls the system API according to the request of the web user interface layer and the web user interface layer to perform the processing corresponding to the standard web language. A hybrid web application that requests a cross-platform system service interface layer for a process corresponding to, and receives a result of a process corresponding to a system API call from the cross-platform system service interface layer either synchronously or asynchronously and delivers the result to a web user interface layer. It includes a cross-platform system service interface layer that performs platform dependent operations corresponding to the system API based on requests of the interface layer and the hybrid web application interface layer. Can be configured together.

Description

Hybrid web application execution method and hybrid web application execution method {Method for executing hybirid web application and apparatus therefor}

The present invention relates to a hybrid web application, and more particularly, to a structure of a hybrid web application that can operate independently of various platforms, a method of executing a hybrid web application, and an operating device of the hybrid web application based on the same. .

With the proliferation of smart devices, the necessity of rapidly developing and providing various applications is increasing.

The traditional way of developing mobile applications is native application development. This method of developing an application based on a library provided by a specific platform has excellent accessibility to terminal resources, and is suitable for showing good performance such as colorful effects or fast screen switching.

However, the emergence of various mobile platforms (e.g., Apple's iOS, Google's Andriod, etc.) has raised the issue of platform dependency on applications, and as an alternative, a web browser development method based on a mobile browser. This will be noticed.

Web applications have various advantages, such as no need for separate installation for use and the ability to always use upgraded functions without periodic updates, but due to the nature of the web, it is impossible to directly control or utilize terminal functions. At the same time, it has the disadvantage that the performance of the application depends on the characteristics of the browser.

SUMMARY OF THE INVENTION An object of the present invention for solving the above problems is to provide a concept of a hybrid web application having a combination of advantages of a native application and advantages of a web application, and a software architecture for executing the hybrid web application. And to provide a hybrid web application running apparatus having the same.

Another object of the present invention for solving the above problems is to provide a software architecture for executing a hybrid web application and a hybrid web application execution method based thereon.

According to an aspect of the present invention, there is provided an apparatus for executing a hybrid web application written in a system API call and a standard web language, and requesting a process corresponding to the system API call to the hybrid web application interface layer. A web user interface layer performing processing corresponding to the standard web language; Requesting the cross platform system service interface layer a process corresponding to the system API call according to the request of the web user interface layer, and synchronizing or asynchronously from the cross platform system service interface layer a result of the process corresponding to the system API call A hybrid web application interface layer that receives and forwards to the web user interface layer; And a cross platform system service interface layer configured to perform platform dependent operations corresponding to the system API based on the request of the hybrid web application interface layer.

Here, the system API may be an API for controlling hardware or an API for accessing information managed by an operating system.

Herein, the standard web language may include at least one of Java Script, HyperText Markup Language (HTML), and Cascading Style Sheet (CSS).

Herein, the web user interface layer may be configured to separate at least one web engine for performing processing according to the web standard language and the system API call included in the hybrid web application, according to the system API call. And a script engine for requesting processing to the hybrid web application interface layer.

Here, the hybrid web application interface layer, the system API processing unit for processing the system API in response to a request of the web user interface layer, and generates the system API execution request in response to the request of the system API processing unit to interface service requests An interface service request generation unit for transmitting to the cross platform, an interface service request mediation unit for relaying the system API execution request received from the interface service request generation unit to the cross platform system service interface layer, and the interface service request mediation unit; It may include an interface service synchronization management unit for managing the reception of the processing result of the system API execution request delivered to the system service interface layer.

In this case, the system API execution request of the interface service request broker is one of synchronous or asynchronous, and the interface service synchronization management unit mediates the interface service request in one of synchronous or asynchronous manners. It may be configured to manage the interface service request intermediary to receive additional.

Here, the cross platform service interface layer may include a web server for transmitting and receiving a processing request and a processing result of the system API using the hybrid web application interface layer and a HyperText Transfer Protocol (HTTP) protocol. have.

In this case, the web server may be configured to transmit and receive a processing request and a processing result of a system API using a hybrid web application interface layer and HTTP protocol installed in another terminal.

In this case, the cross platform service interface layer may further include a system interface unit for processing the system API processing request transmitted through the web server. The system interface unit maps a system interface request processing unit for receiving a system API processing request transmitted through the web server and a system API processing request transmitted from the system interface request processing unit to a platform dependent API, and maps the platform dependent API to a mapped platform dependent API. It may include a system interface interworking unit for calling a system API processing request.

In accordance with another aspect of the present invention, there is provided a method for executing a hybrid web application of a platform including a web user interface layer, a hybrid web application interface layer, and a cross-platform system service interface layer. a web user interface for interpreting the system API call) and the hybrid web application written in a standard web language, requesting a process corresponding to the system API call to the hybrid web application interface layer, and performing a process corresponding to the standard web language. step; In the hybrid web application interface layer, request the cross platform system service interface layer to process the system API call based on the request of the web user interface layer, and process the processing result of the system API call to the cross platform system service interface. A hybrid web application interfacing step of receiving from the layer synchronously or asynchronously and delivering to the web user interface layer; And a cross platform system service interfacing step of performing a platform dependent operation corresponding to the system API based on a request of the hybrid web application interface layer in the cross platform system service interface layer. .

Here, the system API may be an API for controlling hardware or an API for accessing information managed by an operating system.

Herein, the standard web language may include at least one of Java Script, HyperText Markup Language (HTML), and Cascading Style Sheet (CSS).

Here, the web user interfacing step may perform a process corresponding to the web standard language using at least one web engine, and request a process corresponding to the system API call to the hybrid web application interface layer. It can be configured to.

Here, the hybrid web application interfacing may include generating a system API execution request based on a processing request corresponding to the system API call from the web user interface layer; Passing the generated system API execution request to the cross platform system service interface layer; And receiving a processing result of the delivered system API execution request from the cross platform system service interface layer.

In this case, the reception of the processing result of the system API execution request for the system API execution request may be configured to use a synchronous or asynchronous interface.

Here, the cross platform service interface layer and the hybrid web application interface layer may be configured to transmit and receive a processing request and a processing result of the system API using an HTTP protocol.

Here, the hybrid web application interface layer may be configured to transmit and receive a processing request and a processing result of a system API using an HTTP protocol and a cross platform service interface layer of another terminal.

In this case, the cross-platform service interfacing may include mapping a system API processing request transmitted from the hybrid web application interface layer to a platform dependent API; And calling the mapped platform dependent API to process a system API processing request.

The hybrid web application execution method and apparatus according to the present invention can utilize a hybrid web application instead of the conventional native application and web application.

Hybrid web applications can have the following advantages:

First, developers can easily develop platform-independent hybrid web applications based on the web standard language and provide them to various terminals and platform environments.Users can provide complex services using various data, open APIs, and cloud on the Internet. It can be provided in the form of a hybrid application.

Second, using the hybrid web application method, an application based on web technology but having the same performance and functions as a native application can be developed. In addition, it can provide easy development and use of mashup applications that link various Internet open APIs.

Third, hybrid web applications are packaged like native applications, and can be sold and installed through an app store.

Fourth, developers can easily learn applications that utilize various terminal resources and system resources by learning only the system APIs defined for standard hybrid web applications while using the web standard language and technology. Can develop.

Fifth, when hybrid web application is generalized, it can solve the problem of complexity due to explosive increase of terminal hardware characteristics and platform differences, and can extend development efficiency and convenience by providing various terminal control functions by abstracting them. have.

Sixth, since the hybrid web application can exchange control information and remote control between different terminals by using the embedded web server, it can be used for applications such as machine to machine (M2M) and device to device (D2D).

1 is a table for comparing the advantages and disadvantages of a hybrid web application and a conventional native / web application according to the present invention.
2 is a conceptual diagram illustrating the interworking of platforms for executing a hybrid web application according to the present invention.
3 is a block diagram illustrating a software hierarchy of a hybrid web application executing apparatus according to the present invention.
4 is a block diagram illustrating a detailed configuration of a web user interface layer for executing a hybrid web application according to the present invention.
5 is a block diagram illustrating a detailed configuration of a hybrid web application interface layer for executing a hybrid web application according to the present invention.
6 is a conceptual diagram illustrating a process of transmitting a processing request and returning a processing result between a hybrid web application interface layer and a cross platform system service interface layer according to the present invention.
7 is a block diagram illustrating a detailed configuration of a cross platform system service interface layer for executing a hybrid web application according to the present invention.
8 is a conceptual diagram illustrating the interworking between a hybrid web application interface layer and a cross platform system interface layer located in different terminals according to the present invention.
9 is a flowchart illustrating a method of executing a hybrid web application according to the present invention.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. In describing the drawings, similar reference numerals are used for similar elements.

Terms such as first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

The following description relates to a method and apparatus for providing a platform-independent hybrid web application in a variety of terminal environments, including smart phones, mobile devices, desktops, and small devices.

In the following description, a "platform" is a concept encompassing a processor and hardware devices that are the basis of a system and an operating system for driving the system, and the terminal device refers to a device actually implemented based on a specific platform. In the following description, the platform and the terminal may be used interchangeably, but the terminal is used as a meaning for emphasizing the hardware characteristics on which the platform is based, and the platform is used as a more comprehensive term.

According to the invention hybrid  Web Of application  Concept and action concept

The present invention relates to a method and apparatus for providing a hybrid web application independent of the characteristics of various platforms and terminal devices.

The hybrid web application method enables platform independent application development, develops applications with the same functions as native applications based on web technology, and easily supports mashup applications that connect various Internet open APIs. Can be provided for development and use.

The hybrid web application proposed in the present invention may be written in a web standard language including a system API (Application Programming Interface) call. Therefore, in the hybrid web application, the platform-independent portion may be written as a web standard language, and the platform-dependent portion may be written to call a system API, as in the conventional web application. Can be. For example, the web standard language may include HyperText Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript, or the like. System APIs are APIs defined to enable control and access to the resources of the platform or other platform on which the hybrid web application runs. Here, the resources of the platform may be, for example, hardware (eg, cameras, acceleration sensors, GPS sensors, etc.) and information managed by the platform's operating system (eg, when the terminal is a smartphone, contacts information, calendar, etc.). ) Information, etc.).

1 is a table for comparing the advantages and disadvantages of a hybrid web application and a conventional native / web application according to the present invention.

Referring to FIG. 1, since a native application is developed based on a library provided by a specific platform, access to platform resources is excellent, and thus it is suitable for exerting good performances such as colorful effects or fast screen switching. In addition, since a native application can be distributed in the form of a binary file, it is easy to sell online or offline through an app store. On the other hand, by taking a platform-dependent development approach, software upgrades are not easy, and code reusability is low.

On the other hand, a web application may have advantages and disadvantages opposite to those of the above-described native application. Representatively, web applications have various advantages, such as no need for separate installation for use and the ability to always use upgraded functions without periodic updates, but due to the web-based characteristics, the web application can directly control or utilize terminal functions. It is impossible to do this, and at the same time, the performance of the application depends on the characteristics of the web browser.

Hybrid web applications attempt to take advantage of the two application methods. In hybrid web application method that combines native app and web application, programming using web standard technology (HTML, CSS, Javascript) is packaged like a native application and can be sold through app store. Becomes

In addition, the hybrid web application according to the present invention can be programmed through a web standard language, thereby reducing the time and cost required for development. In addition, since the hybrid web application according to the present invention uses a system API call for platform-dependent hardware control or access to operating system management information, the hybrid web application may have a performance similar to that of a native app.

In particular, the hybrid web application according to the present invention may take a structure that can control the hardware and operating system of a platform other than the platform on which the hybrid web application is currently running.

2 is a conceptual diagram illustrating the interworking of platforms for executing a hybrid web application according to the present invention.

Referring to FIG. 2, the hybrid web application according to the present invention may be configured to access hardware resources and operating system resources of different platforms between platforms on which the hybrid web application is executed.

For example, the hybrid web application according to the present invention is applied to various terminals 200 and is driven, and the cross-platform service interface layer described below provided by various terminals 201 and 202 connected through a wired / wireless network is Hypertext Transfer Protocol (HTTP) protocol. You can call each other using.

Accordingly, the terminals, which are the hybrid web application execution apparatuses according to the present invention, share a resource with each other to form a virtual hybrid application cloud 270 and control and utilize unique resources and services of the terminal.

hybrid  Web application  Running device

3 is a block diagram illustrating software layers mounted in a hybrid web application executing apparatus according to the present invention.

Referring to FIG. 3, the hybrid web application 10 is executed using the web user interface layer 100, the hybrid web application interface layer 200, and the cross platform system service interface layer 300.

The hybrid web application 10 may be written in the web standard language 11 and may include at least one system API call 12. Web standard languages for building hybrid web applications include JavaScript, HyperText Markup Language (HTML), and Cascading Style Sheets (CSS). It also includes standard languages. As already mentioned above, the system APIs control and access (e.g., hardware (e.g., cameras, acceleration sensors, GPS sensors, etc.) hardware and platform information on the platform or other platform on which the hybrid web application is running (e.g., In the case where the platform is a smart phone, it is defined for the hybrid web application according to the present invention to enable access to contact information, calendar information, etc.).

In addition, the above-described web user interface layer 100, hybrid web application interface layer 200 and cross-platform system service interface layer 300 is named by the representative functions of each layer, by the name Each layer is not limited. The hybrid web application 10 and the layers 100, 200, and 300 may be stored in a memory of a terminal and executed by a processor. In this case, each layer may be strictly separated and exist as each module, and some layers may exist as a single module while maintaining each function.

In terms of distribution of the application, the hybrid web application 10 described above may take the form of a binary file. In addition, the hybrid web application 10 may include one application package together with all or some of the web user interface layer 100, the hybrid web application interface layer 200, and the cross platform system service interface layer 300. It can be distributed online or offline through the App Store. In another distribution method, the above-described layers 100, 200, and 300 and the hybrid web application 10 may be separated and distributed. That is, when the above-described layers (100, 200, 300) are first installed on the platform, it is also possible to distribute only the hybrid web application online or offline. Of course, the above-described layers 100, 200, and 300 may also be distributed online or offline separately from the hybrid application.

Hereinafter, the role and detailed configuration of each of the layers described above will be described.

1) Web user interface layer

The web user interface layer 100 interprets the hybrid web application 10 and requests a process corresponding to the system API call 12 included in the hybrid web application to the hybrid web application interface layer 200 which will be described later. The processing corresponding to the general standard web language part except API call is a layer to perform directly.

4 is a block diagram illustrating a detailed configuration of a web user interface layer for executing a hybrid web application according to the present invention.

Referring to FIG. 4, the web user interface layer is used to separate at least one web engine 120 for executing a general standard web language part and a system API call part for a general standard web language part in a hybrid web application. It may be configured to include a script engine 110.

The web engine includes an HTML rendering engine or a CSS rendering engine, and executes general standard web languages provided separately by a script engine to provide a browsing screen in a manner similar to that of a typical web application.

The script engine 110 interprets the hybrid web application, providing the general standard web language portion 11 to the web engine, and for the system API calls 12 to the system API calls with the hybrid web application interface layer 200. It will request the corresponding processing.

In this case, an embodiment in which the web engine and the script engine are not clearly distinguished from each other is possible. That is, the web engine may typically be configured to include a script engine (eg, a JavaScript interpreter), in which case the script engine included in the web engine separates the standard web language parts and system API call parts that are common in a hybrid web application. The function will have to be implemented.

Hybrid Web Application Interface Layer

The hybrid web application interface layer 200 requests the cross-platform system service interface layer 300 for a process corresponding to a system API call according to the request of the web user interface layer 100, and a process corresponding to the system API call. A result is a layer that returns a result synchronously or asynchronously from the cross platform system service interface layer 300 to the web user interface layer.

5 is a block diagram illustrating a detailed configuration of a hybrid web application interface layer for executing a hybrid web application according to the present invention.

Referring to FIG. 5, the hybrid web application interface layer 200 according to the present invention includes a web interface provider 210, an interface service request generator 220, an interface service request broker 230, and an interface service synchronization manager ( 240).

First, the web interface providing unit 210 is a component that receives a request corresponding to a system API call from the web user interface layer 100 described above, and provides the processing result to the web user interface layer 100.

Next, the interface service request generation unit 220 is a component for generating a device control and system function control API request requested through the web interface providing unit 210 according to a predefined request specification.

Next, the interface service request broker 230 transmits the request generated through the interface service request generator to the cross platform system service interface layer 300 according to a synchronous / asynchronous interface processing scheme. Component.

Finally, the interface service synchronization manager 240 is a component that manages a synchronous / asynchronous interface processing process.

The interface service request broker 230 transmits the request generated through the interface service request generator 220 to the cross platform system service interface layer 300 and transmits the result synchronously or asynchronously to the cross platform system service interface layer. In operation 300, the interface service synchronization manager 240 performs a process related to receiving such a result synchronously or asynchronously. Meanwhile, the interface processing method of the corresponding system API is determined according to the characteristics of the system API.

6 is a conceptual diagram illustrating a process of transmitting a processing request and returning a processing result between a hybrid web application interface layer and a cross platform system service interface layer according to the present invention.

Referring to FIG. 6, the hybrid web application interface layer 200 may request synchronous processing for a processing request corresponding to a predetermined system API with respect to the cross platform system service interface layer 300 (511). In this case, the interface service request broker 230 stops the execution of the application until the point at which the result of the request is returned with the help of the interface service synchronization manager 240, and then the result from the cross platform system service interface layer 300. 512 is returned.

 Meanwhile, the hybrid web application interface layer 200 may request asynchronous processing for a processing request corresponding to a predetermined system API to the cross platform system service interface layer 300 (531). In this case, the interface service request intermediary 230 transmits the processing request to the cross-platform system service interface layer 300, and then, with the help of the interface service synchronization management unit 240, the time point at which the result of the request is returned is returned. If the result is returned from the cross platform system service interface layer 300 (532).

In addition, there may be asynchronous processing in the form of notification as another interface method. The notification means informing the counterpart when a pre-registered triggering condition is met or a triggering event occurs. The notification is different from the conventional asynchronous processing described above in that the notification is not only a one-time processing result return but a continuous notification of the condition or event occurrence whenever the triggering condition registered by the counterpart is satisfied or an event occurs. The hybrid web application interface layer 200 may request the cross platform system service interface layer 300 to register a notification for a processing request corresponding to a predetermined system API (521). In this case, the interface service request broker 230 transmits the processing request to the cross-platform system service interface layer 300, and then performs other tasks without waiting for a response to be returned. Subsequently, when an event that needs to be notified about a registered notification is generated, the interface service request broker 230 may receive a notification from the cross platform system service interface layer 300 with the help of the interface service synchronization manager 240. 522.

3) cross platform system service interface layer

The cross platform system service interface layer 300 is a layer that performs platform dependent operations corresponding to the system API according to a request of the hybrid web application interface layer.

7 is a block diagram illustrating a detailed configuration of a cross platform system service interface layer for executing a hybrid web application according to the present invention.

Referring to FIG. 7, the cross platform system service interface layer 300 may include a web server 310 and a system interface 320. More specifically, the system interface unit 320 may include a system request processing unit 321 and a system interface interworking unit 322.

First, the web server 310 is an embedded web server embedded in the cross platform system service interface layer 300. The web server 310 processes a system API using a hybrid web application interface layer and a HyperText Transfer Protocol (HTTP) protocol. A component that exchanges request and processing results.

The cross platform system service interface layer 300 and the hybrid web application interface layer 200 are configured to exchange processing requests and processing results of the system API with the HTTP protocol so that the cross platform system service interface layer 300 and the hybrid web application interface are configured. The layer 200 may be located in different terminals. That is, the cross platform system interface layer 300 and the hybrid web application layer 200 existing in different terminals may be configured to exchange processing requests and processing results of system APIs using the HTTP protocol. Through this, the hybrid web application can call the cross-platform service interface layer provided by various terminals connected through the wired / wireless network using the HTTP protocol.

8 is a conceptual diagram illustrating the interworking between a hybrid web application interface layer and a cross platform system interface layer located in different terminals according to the present invention.

Referring to FIG. 8, for example, a hybrid web application 811 mounted on one's own smartphone (first terminal; 810) controls a camera 825 mounted on another's smartphone (second terminal; 820). If desired, the hybrid web application interface layer 813 installed in the first terminal may transmit a processing request of the camera control system API to the cross platform system interface layer 824 installed in the second terminal using the HTTP protocol. This corresponds to the concept described above with reference to FIG. 2.

Next, the system interface unit 820 is a component that processes the system API processing request transmitted through the web server.

As a detailed configuration, the system interface unit 820 may convert the system API request request from the system interface request processor 821 and the system interface request processor received from the system interface request processor to the platform-dependent API. It may be configured to include a system interface interworking unit 822 for mapping and calling a mapped platform-dependent API to process a system API processing request.

As an additional component, the system interface unit 820 may further include a system interface manager 823 for managing the system interface and managing the embedded web server.

hybrid  Web application  How to run

9 is a flowchart illustrating a method of executing a hybrid web application according to the present invention.

9 is referred to in parallel with the software hierarchy of FIG. 3 described above. A method of executing a hybrid web application according to the present invention is a method of executing a hybrid web application in a device including a web user interface layer 100, a hybrid web application interface layer 200, and a cross platform system service interface layer 300.

9, a method of executing a hybrid web application according to the present invention may include a web user interfacing step S910, a hybrid web application interfacing step S920, and a cross platform system service interfacing step S930. . The steps S910, S920, and S930 are executed after receiving the execution command of the hybrid web application (S901), and programming the processing for the system web page and the processing for the standard web language constituting the hybrid web application. It proceeds in the order in which it was made, so it repeats continuously.

First, the web user interfacing step (S910) is an operation performed in the web user interface layer 100, and analyzes a hybrid web application written in a standard web language including a system API call to analyze the system API. The processing corresponding to the call is requested to the hybrid web application interface layer 200, and the processing corresponding to the part excluding the system API call in the standard web language is performed.

In order to perform the web user interfacing step (S910), as mentioned above, the web user interface layer 100 may be used in a hybrid web application and at least one web engine 120 for executing a general standard web language portion. It may be configured to include a script engine 100 for separating the general standard web language portion and the system API call portion.

Next, the hybrid web application interfacing step (S920) is an operation performed in the hybrid web application interface layer 200, and cross-platforms the processing of the system API call based on the request of the web user interface layer 100. Requesting the system service interface layer 300, receiving the processing result of the system API call from the cross-platform system service interface layer 300 synchronously or asynchronously, and delivering the result to the web user interface layer 100. to be.

That is, in the hybrid web application interfacing step (S920), a process corresponding to a system API call is requested from the web user interface layer 100, and the requested device control and system function control API requests are generated according to a predefined request specification. . Thereafter, the generated request is forwarded to the cross platform service interface layer 300 according to the synchronous / asynchronous interface processing scheme.

According to the interface processing scheme adopted by the request, the hybrid web application interface layer 200 may receive the processing result of the request synchronously or asynchronously from the cross platform service interface layer 300.

Since a process request transmission and a process result return process between the hybrid web application interface layer 200 and the cross platform system service interface layer 300 have been described with reference to FIG. 6, a description thereof will be omitted.

Lastly, the cross platform system service interfacing step (S930) is an operation performed in the cross platform system service interface layer 300, and corresponds to the system API based on a request of the hybrid web application interface layer 200. This step performs platform dependent operations.

In this case, the cross platform system service interface layer 300 and the hybrid web application interface layer 200 may be configured to exchange a processing request and a processing result of the system API using the HTTP protocol. Through this, the cross platform system interface layer 300 and the hybrid web application layer 200 existing on different platforms may be configured to exchange processing requests and processing results of system APIs using the HTTP protocol. That is, the hybrid web application may call the cross platform service interface layer 300 provided by various terminals connected through the wired or wireless network using the HTTP protocol. The interworking concept between the hybrid web application interface layer 200 and the cross platform system interface layer 300 located in different terminals has been described with reference to FIG. 8.

In the cross platform system service interfacing step (S930), the cross platform system service interface layer 300 receives a system API processing request transmitted from the hybrid web application interface layer 200, and receives the received system API processing request from the platform dependent API. The system API processing request is handled by calling the mapped platform-dependent API.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art will be variously modified and changed within the scope of the invention without departing from the spirit and scope of the invention described in the claims below I can understand that you can.

10: Hybrid web application
11: Standard Web Language Part 12: System API Calls
100: Web user interface layer
110: script engine 120: web engine
200: hybrid web application interface layer
210: web interface provider 220: interface service request generation unit
230: interface service request broker
240: interface service synchronization management unit
300: cross platform system service interface layer
310: embedded web server 320: system interface unit
321: system interface request processing unit
322: system interface linkage
323: system interface management unit

Claims (19)

A device that runs a system API call and a hybrid web application written in a standard web language.
A web user interface layer requesting a process corresponding to the system API call to a hybrid web application interface layer and performing a process corresponding to the standard web language;
Requesting the cross platform system service interface layer a process corresponding to the system API call according to the request of the web user interface layer, and synchronizing or asynchronously from the cross platform system service interface layer a result of the process corresponding to the system API call A hybrid web application interface layer that receives and forwards to the web user interface layer; And
A cross platform system service interface layer configured to perform platform dependent operations corresponding to the system API based on the request of the hybrid web application interface layer;
And the web user interface layer, the hybrid web application interface layer and the cross platform system service interface layer are separate layers. The method according to claim 1,
The system API is an API for controlling hardware or an API for accessing information managed by the operating system. The method according to claim 1,
The standard web language may include at least one of Java Script, HyperText Markup Language (HTML), and Cascading Style Sheet (CSS). The method according to claim 1,
The web user interface layer is,
At least one web engine for performing a process according to the standard web language; And
And a script engine for separating the system API call included in the hybrid web application and requesting a process according to the system API call to the hybrid web application interface layer. The method according to claim 1,
The hybrid web application interface layer,
A system API processor configured to process the system API according to a request of the web user interface layer;
An interface service request generation unit generating a system API execution request according to a request of the system API processing unit and transferring the generated system API request to an interface service request broker;
An interface service request broker for relaying the system API execution request received from the interface service request generator to the cross platform system service interface layer; And
And an interface service synchronization manager configured to manage reception of a processing result of the system API execution request transmitted to the cross platform system service interface layer through the interface service request broker. The method according to claim 5,
The system API execution request of the interface service request broker is either synchronous or asynchronous,
The interface service synchronization management unit manages the interface service request broker so that the interface service request broker can receive the processing result of the system API execution request in one of synchronous or asynchronous manners. Running device. The method according to claim 1,
The cross platform system service interface layer,
And a web server configured to transmit and receive a processing request and a processing result of the system API using the hybrid web application interface layer and a HyperText Transfer Protocol (HTTP) protocol. The method according to claim 7,
And the web server transmits and receives a processing request and a processing result of a system API using a hybrid web application interface layer and an HTTP protocol installed in another terminal. The method according to claim 8,
The cross platform system service interface layer,
And a system interface unit configured to process a processing request of the system API transmitted through the web server. The method according to claim 9,
The system interface unit
A system interface request processing unit which receives a processing request of the system API transmitted through the web server; And
And a system interface interworking unit configured to map a processing request of the system API transmitted from the system interface request processing unit to a platform dependent API and call the mapped platform dependent API to process a processing request of the system API. Execution device of the web application. A method of running a hybrid web application of a platform including a web user interface layer, a hybrid web application interface layer, and a cross platform system service interface layer.
In the web user interface layer, a system API call and the hybrid web application written in a standard web language are interpreted to request a process corresponding to the system API call to the hybrid web application interface layer, and the standard web Web user interfacing to perform a process corresponding to a language;
In the hybrid web application interface layer, request the cross platform system service interface layer to process the system API call based on the request of the web user interface layer, and process the processing result of the system API call to the cross platform system service interface. A hybrid web application interfacing step of receiving from the layer synchronously or asynchronously and delivering to the web user interface layer; And
At the cross platform system service interface layer, performing a platform dependent operation corresponding to the system API based on a request of the hybrid web application interface layer;
The hybrid web application operates independently of various types of platforms, and wherein the web user interface layer, the hybrid web application interface layer and the cross platform system service interface layer are separate layers. The method according to claim 11,
The system API is an API for controlling hardware or an API for accessing information managed by the operating system. The method according to claim 11,
The standard web language includes at least one of Java Script, HyperText Markup Language (HTML), and Cascading Style Sheet (CSS). The method according to claim 11,
The web user interfacing may include performing a process corresponding to the standard web language using at least one web engine and requesting a process corresponding to the system API call to the hybrid web application interface layer. To run a hybrid web application. The method according to claim 11,
The hybrid web application interfacing step,
Generating a system API execution request based on a processing request corresponding to the system API call from the web user interface layer;
Passing the generated system API execution request to the cross platform system service interface layer; And
And receiving a processing result of the delivered system API execution request from the cross platform system service interface layer. The method according to claim 15,
And receiving a processing result of the system API execution request with respect to the system API execution request using a synchronous or asynchronous interface method. The method according to claim 11,
And the cross platform system service interface layer and the hybrid web application interface layer transmit and receive a processing request and a processing result of the system API using an HTTP protocol. The method according to claim 11,
The hybrid web application interface layer is a method of executing a hybrid web application, characterized in that for transmitting and receiving the processing request and the processing result of the system API using a cross platform system service interface layer and HTTP protocol of the other terminal. The method according to claim 18,
The cross platform system service interfacing step
Mapping a system API processing request delivered from the hybrid web application interface layer to a platform dependent API; And
And executing a system API processing request by calling the mapped platform dependent API.

Images