KR20180082271A - Cached wadl execution engine and method for calling web services using the theory - Google Patents

Abstract

The present invention relates to a method for calling a web service using a cached WADL execution engine. The method for calling a web service using a cached WADL execution engine comprises: a step (a) of obtaining a service corresponding to a request obtained from a semantic web database as an execute service; and a step (b) of calling a WADL request cached through a web ontology language for service (OWL-S) execution engine and responding to the call to interpret and execute a WADL resource corresponding to the execution service. Communication between web services is able to be executed in the step (b), and accordingly, a web service corresponding to the service is able to be called from the web services. According to the present invention, when a duplicate service is called in an SOA based web service, it is possible to provide a cached WADL execution engine based SOA infrastructure, which is able to enhance processing speed and network performance.

Description

[0001] CACHED WADL EXECUTION ENGINE AND METHOD FOR CALLING WEB SERVICES USING THE THEORY [0002]

The present invention relates to a cached WADL execution engine for a RESTful web service that improves network performance and a web service invocation method using the same.

With the development of the Internet, the structure of the web service system based on the web-based client-server distributed architecture is gradually spreading. In recent years, mobile applications such as smart phones using smart phones have become popular, Trend.

Web-based companies (for example, Google, Twitter, Microsoft, etc.) design many HTTP-based APIs to create enterprise-class data APIs that can be used in other applications, Service-oriented service-oriented architecture (SOA) is applied.

SOA is a method and architecture for building large-scale Web services. In order to easily build SOA-based Web services, SOA infrastructure is required.

This SOA-based Web service combines several services to process business logic. Therefore, if an Atomic service is defined, it is possible to perform complex processing by combining them, and it is possible to eliminate redundant logic through a combined service. However, when a large number of services are combined in a complicated manner, the same service is repeatedly called and the processing speed and network performance are degraded.

The background technology of the present application is disclosed in Korean Patent Registration No. 10-1324393 (Registered on Feb. 20, 2013).

It is an object of the present invention to solve the above-mentioned problems of the prior art, and it is an object of the present invention to provide a SOA-based web service, which is capable of solving the problem of degraded processing speed and network performance, An execution engine and a web service invocation method using the same.

It is to be understood, however, that the technical scope of the embodiments of the present invention is not limited to the above-described technical problems, and other technical problems may exist.

According to an aspect of the present invention, there is provided a web service invocation method using a cached WADL execution engine, the method comprising: (a) providing a service corresponding to a request acquired from a semantic web database to an execution service (b) invoking a cached WADL request via the Web Ontology Language for Service (OWL-S) execution engine and, in response to the call, interpreting a WADL resource corresponding to the execution service interpreting the web service, and executing the web service corresponding to the service from the web services as the communication between the web services is performed according to the step (b).

In the step (b), the cached WADL request may be called through the WADL grounding provider of the OWL-S execution engine.

In the step (b), when the WADL resource is executed, whether or not the WADL resource is changed while the WADL resource is being cached can be checked using the cache manager.

In addition, in the step (b), it is possible to confirm whether the WADL resource is changed by obtaining the value of the cache entry corresponding to the URI through the cache manager with the URI included in the WADL resource as a key .

In the step (b), conditional requests of HTTP 1.1 may be performed based on the tag value included in the value of the cache entry.

In the step (b), it is possible to confirm whether the WADL resource is changed based on a write-through caching algorithm using the conditional request.

In the step (b), a result of calling the RESTful web application by calling the cached WADL request may be stored in the cache entry.

In addition, the cache manager may store resources based on the LRU algorithm.

Meanwhile, the cached WADL execution engine according to an embodiment of the present invention includes an acquisition unit that acquires a service corresponding to a request acquired from a semantic web database as an execute service, and an OWL-S (Web Ontology Language for Service And an execution unit for interpreting and executing a WADL resource corresponding to the execution service in response to the call, wherein the execution unit executes communication between the web services by the execution unit, The web service corresponding to the service can be invoked from the web services.

The above-described task solution is merely exemplary and should not be construed as limiting the present disclosure. In addition to the exemplary embodiments described above, there may be additional embodiments in the drawings and the detailed description of the invention.

According to the present invention, when a duplicated service is invoked in a WADL (Web Application Description Language) in an OAW-S based SOA infrastructure through a cached WADL execution engine and a web service invocation method using the cached WADL execution engine, Or cache technique to improve performance.

According to the present invention, it is possible to provide an SOA infrastructure based on a cached WADL execution engine that can improve the processing speed and network performance at the time of calling a duplicated service in an SOA-based web service .

According to the above-mentioned task resolution means, there is an effect that performance improvement in interoperability in a service-based architecture and an infrastructure can be provided by HTTP communication using a caching technique.

However, the effects obtainable here are not limited to the effects as described above, and other effects may exist.

1 is a conceptual diagram of a RESTful SWS applied to a cached WADL execution engine and a web service invocation method using the cached WADL execution engine according to an embodiment of the present invention.
2 is a schematic diagram illustrating a RESTful grounding ontology applied to a cached WADL execution engine and a web service invocation method using the cached WADL execution engine according to an embodiment of the present invention;
Figure 3 is a schematic diagram illustrating the architecture of an SOA infrastructure including a cached WADL execution engine (SHIN) in accordance with one embodiment of the present disclosure.
4 is a diagram illustrating the architecture of a cached WADL execution engine (SHIN) in accordance with one embodiment of the present disclosure.
FIG. 5 is a schematic flowchart illustrating a method of calling a Web service using a cached WADL execution engine according to an exemplary embodiment of the present invention. Referring to FIG.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. It should be understood, however, that the present invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In the drawings, the same reference numbers are used throughout the specification to refer to the same or like parts.

Throughout this specification, when an element is referred to as being "connected" to another element, it is intended to be understood that it is not only "directly connected" but also "electrically connected" or "indirectly connected" "Is included.

It will be appreciated that throughout the specification it will be understood that when a member is located on another member "top", "top", "under", "bottom" But also the case where there is another member between the two members as well as the case where they are in contact with each other.

Throughout this specification, when an element is referred to as "including " an element, it is understood that the element may include other elements as well, without departing from the other elements unless specifically stated otherwise.

In this paper, we propose a cached WADL implementation that can improve performance through cache when calling duplicate services in WADL (Web Application Description Language) in SOA Infrastructure based on OWL-S (Web Ontology Language for Service) Engine and a web service invocation method using the same. Prior to the full-scale explanation, the technology underlying the present invention will be described as follows.

1.1. SOA Infrastructure and SWS using OWL-S.

The main function of the SOA infrastructure is to enable discovery, invocation, composition, and interoperation of Web services. SOA-based infrastructure enables OWL-S ≪ / RTI >

OWL-S refers to a service ontology framework that defines a software agent to automatically perform functions such as search, invoke, composition, interoperability and execution monitoring of Web services. In OWL-S, a service can be represented by three types of ontologies such as a service profile, a service model, and a service grounding. A service profile is an ontology representing a service (that is, a service requested by a user), which is used for automatic search of a service. The service model is an ontology that deals with how to provide services, and is used for automatic composition and interoperability of services. Service grounding is an ontology that defines how services are to be accessed and is used for automatic execution of services.

In addition, the service grounding provides Web Services Description Language (WSDL) as a basic grounding, which can be changed by other service grounding methods such as UPnPGrounding and JavaGrounding. The service model is also used to define the model of the service using process.owl in OWL-S. The process ontology used in the service model can be composed of subclasses and attributes such as an atomic process, a simple process, and a composite process. The process class includes an IOPE (Input, Output, Precondition, Effect) model for automatic interoperability . ≪ / RTI > In other words, the service model of OWL-S basically has IOPE (Input, Output, Precondition, Effect) as an attribute.

In OWL-S, Control Construct classes such as Sequence, Choice, If-Then-Else, Split, Split-Join and Iterate can be used for automatic service composition as a control method for service operation. In other words, in OWL-S, you can combine multiple services using the Composite Process class. Accordingly, in the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention to be described later, an extended process ontology can be used together with a subclass of additional Control Construct such as For-Each.

Service grounding is supported in WSDL, which can be defined by OWL-S. Service grounding can then be optimized by representing WSDL-based business logic in SOA and SWS (Semantic Web Service). However, recently developed Open-API based on Resource-oriented Architecture (ROA) is not consistent with SOA, ROA is generally RESTful style, and this resource is represented by URI which is unique identifier.

The cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention can provide a RESTful web service using RESTfulGrounding and the grounding can support WADL to extend the ServiceGrounding ontology, , The grounding can provide a vocabulary that defines operations for directly controlling RESTful Web resources of one or more single processes (Atomic Processes).

1.2. WSDL and WADL.

WSDL is an XML-based language that is used to describe services provided by a particular business and to provide a way for individuals or other companies to electronically access such services. The proposed WSDL in 2001 consists of an XML specification that uses the HTTP GET and POST methods. It is based on the Simple Object Access Protocol (SOAP), which is designed to invoke endpoints of a Web service, Lt; / RTI > In general, SOA based on OWL-S is based on WSDL and SOAP. This WSDL differs from WADL.

WADL is defined to represent HTTP-based Web applications and RESTful Web resources. The HTTP-based Web API is used to represent data using JSON or XML format. The behavior of RESTful web resources can be described using HTTP methods such as GET, POST, PUT, and DELETE.

On the other hand, web-based companies (eg, Google, Yahoo, Amazon, Flickr, etc.) increasingly do not define open APIs using WSDL. Therefore, these services are designed using RESTful style resource-based architecture in conjunction with open API and WADL.

WADL and WSDL generally use HTTP-based operations. However, WADL is designed for Web applications and resources, and WSDL is designed for Web services and business logic. In the definition of service endpoints, these two languages are used differently to design existing Web services and modern Web applications. In the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention to be described later, WADL is used in a service invocation.

1.3. How to cache client-side resources for RESTful Web applications.

The large-scale Web services standard has a protocol that supports client-side caching of resources, and a typical protocol used in one embodiment of the present invention is 'HTTP 1.1: Conditional Requests'.

This method can be performed to process conditional requests through the value tuples and additional keys in the header when sent over HTTP.

The HTTP client sends a request through the If-None-Match and If-Modified-Since headers. The client can then receive a response from the server, which does not have a body and 304 code, when the applicable resources have not changed (meaning 'cache'). This process reduces the latency of the network So that the network performance of the server can be improved.

The large, open APIs of web-based companies such as GitHub and Google provide web services with conditional requests for possible network performance. On the other hand, if a conditional request is used as a client-side caching method for a REST web application, it can easily be applied to checking the 'modified' caching state and the 'invalid' caching state of the resource and the cached entry.

Accordingly, in the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention to be described later, the conditional request can be used as a client side caching method for RESTful web applications other than REST. In addition, the RESTful web application that is applied to the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention not only supports a response to a resource corresponding to its own URI pattern, (Update), DELETE (remove), and GET (retrieve), which can be implemented as a write-through caching method. The support or activation of four operations including POST (creation), PUT (update), DELETE (removal) and GET (retrieval) is in accordance with known processes. In addition, through an HTTP GET of a conditional request, the application can check the HTTP client for missing hits or cache entries and update the data in the cache line where the data is in the 'modified' state or the 'invalid' state can do. In addition, when the server receives a request for an operation method such as POST, DELETE, or PUT, the status may change from 'unmodified' to 'modified'. In addition, RESTful web services can improve network performance by caching methods because they access one or more resources based on their unique URI.

1.4. Another execution engine for OWL-S.

The SWS execution engine based on OWL-S is OWL-S virtual machine (OSVM) and OWL-S Java API. OSVM is an execution engine supporting DAML-S and OWL-S.

Execution rules for invoking a Web service can be interpreted to apply a Constrol Construct to each Composite Process executed to match the WSDL behavior of the Atomic Process.

In the cached WADL execution engine and the web service invocation method using the same, an OWL-S Java API can be used as an SWS execution engine used together with RESTfulGrounding.

The OWL-S Java API library includes Apache-Jena based OWL-S execution engine, which supports DAML-S 0.7 to OWL-S 1.2, and RDF / OWL- Supports WSDL or UPnP execution for the model. The OWL-S Java API can be easily extended to other grounding methods using the OWL-S grounding provider interface.

The two engines (OWL-S Java API, OSVM) basically support WSDL operations, are based on RDF, and the results of a call from a Web service through both engines can be converted to the RDF format. Accordingly, in the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention described below, XSLT can be supported for transforming JSON, which is data serialized to RDF in the internetwork. Also, in the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention, RESTfulGrounding based on OWL-S Java API is used and OWL-S grounding provider interface is extended to provide a WADL Grounding Provider To create a RESTful SWS execution engine.

Hereinafter, a process of applying a caching layer for a WADL-based SWS call in RESTful grounding in a cached WADL execution engine and a web service calling method using the cached WADL execution engine according to an embodiment of the present invention will be described in detail.

In the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention, the performance of the RESTful SWS invocation process is improved by adding a write-through caching mechanism as a caching layer using conditional requests .

SWS's large-scale design process requires redundant requests for resources, resulting in extremely high network latencies in the Web server. In order to solve this problem, the cached WADL execution engine (hereinafter referred to as 'SHIN') according to an embodiment of the present invention can remove redundant network resources by using a caching layer. In this paper, SHIN can be implemented as a SWS execution engine that can improve performance by reducing server resources.

One of the traditionally used caching mechanisms is the MESI protocol. In general, the MESI protocol is used by the CPU to solve the data consistency problem between cache and physical memory. In a computer architecture, physical memory is accessed by all CPUs, and the CPU has a cache line.

The cached WADL execution engine (SHIN) according to one embodiment of the present disclosure may use a caching protocol for client-side caching, such as write-through, rather than the traditional cache algorithm. In the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention, a contiguous write caching algorithm can be implemented using a conditional request of HTTP 1.1.

The caching algorithm applied here can use the HTTP GET method request with Etag and Modified-Since header to check whether the state of the resource has changed.

If another client writes a resource, the server can update the data on the resource and respond with the Etag and Modified-Since values of the resource when the client sends the GET request to the server. Each client can use the server's Modified-Since or Etag to compare data or hash values. Thereafter, if the data is modified, the client may update the data, hash and date values of the cache entry already in the cache line. This mechanism can define and solve the problem of data consistency and resource sharing. As a result, the Web client can check the status of the resource in the cache line from the Web server. Accordingly, the caching mechanism of the cached WADL execution engine according to an exemplary embodiment of the present invention may use a continuous writing method that is not available in the MESI protocol in order to share resources with other web clients. If a client sends data to a duplicate resource, the data can be stored and shared by each client in the respective cache line.

In the client-side caching algorithm implementation herein, cache entries are not duplicated in the cache line. In the MESI protocol, the key of the cache entry can be generated from the hash value of the data. Likewise, the cached WADL execution engine according to one embodiment of the present disclosure may use a RESTful resource URI as the key of the cache entry. In a RESTFul web application, a URI is a unique value for identifying a web resource or collection. HTTP methods such as GET, POST, PUT, and DELETE are also used for operations on resources. Here, the operations each indicate to take, create, update, and remove. Thus, RESTful services can be continuously developed for use as cached processes. If the web client sends a PUT request to change the data on the server, the other client can update the cache line with the changed data known by the request (request) to the server.

The cached WADL execution engine according to one embodiment of the present application (the inventor of the present invention calls this execution engine 'SHIN') can use the RESTfulGrounding ontology presented as the endpoint of the RESTful SWS for cached calls in the SOA infrastructure have.

1 is a conceptual diagram of a RESTful SWS applied to a cached WADL execution engine and a web service invocation method using the cached WADL execution engine according to an embodiment of the present invention. That is, FIG. 1 shows a conceptual diagram of a connection between WADL and OWL-S in RESTfulGrounding.

Referring to FIG. 1, an ontology applied to the present invention is designed as a new service grounding for extending WADL, such as OWL-S grounding description.

RESTful Grounding can link the OWL-S service grounding and Web application resources in WADL documents. RESTfulGrounding Each input / output can be linked to the input and representation of a WADL document. Also, since data serialization in RESTful web applications is primarily recommended for use in the JSON format, output from the representation of WADL can be converted to RDF / XML using XSLT for OWL-S.

2 is a schematic diagram illustrating a RESTful grounding ontology applied to a cached WADL execution engine and a web service invocation method using the cached WADL execution engine according to an embodiment of the present invention; That is, FIG. 2 illustrates a RESTful grounding ontology designed using RESTfulGrounding, an ontology for grounding RESTful web applications.

Referring to FIG. 2, WadlGrounding and WadlAtomicProcessGrounding may be designed to extend from OWL-S Service Grounding ontology to AtomicProcessGrounding, respectively. WadlGrounding can associate the WADL specification with the WadlResourceMethod property to invoke a method on a connected resource. The calling program for the single (atomic) and composite (composite) processes represents the process execution engine of SWS.

In the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention, the result of calling the RESTful web application in the cache entry is stored in the cache entry using the URI and the HTTP method, Can be implemented. At this time, the cache item set may be referred to as a caching layer of SHIN.

With respect to applying a caching layer to the SWS, the grounding should exhibit a behavior consistent with the unique access key for the web resource. RESTful-style resources can be accessed using a unique URI rather than a URL, and can have four methods for each consistent operation. Therefore, RESTful API applied here is more suitable than REST API for caching layer.

In the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an exemplary embodiment of the present invention, a caching layer focusing on an API based on a RESTful web application can be implemented.

The RESTful API can be defined using two main URI patterns for access and four HTTP methods for the operation of Web resources.

Table 1 below shows the relationship between URIs and methods in the RESTful API specification, which defines the main RESTful style API specification, but this specification does not apply. The API defined by this specification is a RESTful API.

[Table 1]

For example, in Table 1, collections can be represented as 'http://api.example.com/resources'. This 'http://api.example.com' URL represents a web service, and '/ resources' represents a namespace as a collection of resources. Also, 'http://api.example.com/resources' indicates accessing the collection using this URI. An example of a URI for accessing an element is "http://api.example.com/resources/17". In this example, 'http://api.example.com/resources' means the same as above, and '/ 17' indicates the ID for accessing the element in the collection. In the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to the embodiment of the present invention, since the specification is related to the RESTful API as shown in Table 1, this difference is focused.

Hereinafter, an exemplary implementation of a cached WADL execution engine (SHIN) and a web service invocation method using the same will be described in detail with reference to the above description.

Figure 3 is a schematic diagram illustrating the architecture of an SOA infrastructure including a cached WADL execution engine (SHIN) in accordance with one embodiment of the present disclosure.

3, the architecture of an SOA infrastructure including a cached WADL execution engine (SHIN) according to one embodiment of the present invention includes a gateway server 10, a semantic web database 20, a cache for OWL-S The WADL execution engine (SHIN) 30, and the web service 40.

The gateway server 10, the semantic web database 20, the cached WADL execution engine (SHIN) 30 for OWL-S, and the web service 40 can communicate with each other via a network. Examples of the network 10 include a 3rd Generation Partnership Project (3GPP) network, a Long Term Evolution (LTE) network, a World Interoperability for Microwave Access (WIMAX) network, the Internet, a LAN (Local Area Network) (Wireless Local Area Network), a WAN (Wide Area Network), a PAN (Personal Area Network), and the like.

First, briefly, the gateway server 10 is a server that provides a service. For example, the gateway server 10 may include a service provider such as Google, Twitter, Microsoft, Naver, Yahoo, Amazon, ), Flickr, and the like, but are not limited thereto. For example, the SHIN 30 according to one embodiment of the present application may be installed in all servers.

Upon receiving the request (step 1), the gateway server 10 can transmit the service name corresponding to the generated request as a query to the semantic web database 20 (step 2).

The semantic web database 20 is a database for storing a designed semantic web service model. The semantic web database 20 searches for services corresponding to service names received from the gateway server 10 among the stored services, And may be transmitted to the SHIN 30 by the gateway server 10 (step 3). At this time, the service stored in the semantic web database 20 may be stored as an XML document as an example. In other words, the gateway server 10 can return the service corresponding to the request to the SHIN 30 in response to the query for the service name through the semantic web database 20, specifically, the XML of the service corresponding to the request The document can be transferred to the SHIN 30.

SHIN 30 is a cached WADL execution engine for OWL-S implemented in accordance with one embodiment of the present application, wherein SHIN 30 can utilize conditional requests to implement cached WADL requests. Further, in the SHIN 30, each resource of the application can be the reference of the cache. At this time, when the resource is stored in the cache, an LRU (Least Recently Used) algorithm may be used, which is a method of discarding old and old items. A more detailed description will be given later.

The SHIN 30 can interpret and execute the document based on the XML document of the service received from the semantic web database 20 by the gateway server 10 (step 4). At this time, the SHIN 30 can perform communication with the web services 40 while interpreting the document, thereby allowing the SHIN 30 to transmit the web service corresponding to the request from the web service 40 (Step 5).

The web service 40 is a cloud server that provides a web service corresponding to a request, and can provide web services corresponding to each function for a request.

Hereinafter, the architecture of the SWS execution engine and the SOA infrastructure SHIN (30) based on the OWL-S API used to parse and process models in OWL-S will be described in more detail.

The SHIN 30 may include a description of a service for invoking a WADL-based web service and interworking with an HTTP-based web service. In order to provide enhanced performance to the SHIN 30, the caching layer Can be added.

The gateway server 10 can register and search the SWS in the semantic web database 20 by transmitting a request including the query related to the SWS to the semantic web database 20. [ In addition, the gateway server 10 may have a function for configuring an OWL-S service and a process in the semantic web database 20. SWS is based on OWL-S, and SWS may have a separate service class for each document in OWL-S.

The SHIN 30 can process web requests using parameters such as URIs associated with individual OWL-S services. When the SHIN 30 receives a new service URI from the OWL-S, the SHIN 30 may store the service in the semantic web database 20 as RDF triples. The response to the received service URI may have an Etag and Modified-Since header to support the cache. A client sending a request to the server can cache the response.

SPARQL is based on Apache Jena's MySQL and SDB, and SPARQL uses semantics and semantics to query the knowledge base expressed in RDF graphs. Semantic Web database 20 can use SPARQL for queries. , semantics). Therefore, most query methods for RDF graphs can use SPARQL as the default language. Service URIs can be stored in the RDB as RDF triples, and triples can be accessed using Apache Jena's SDB interface. SDB can use the JDBC interface to access the RDB. In the cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to one embodiment of the present invention, the Jena ARQ module can be used as a query engine of Jena supporting SPARQL before the process. Meanwhile, the architecture of the SHIN 30, which is a cached WADL execution engine, may be as shown in FIG.

4 is a diagram illustrating the architecture of a cached WADL execution engine (SHIN) in accordance with one embodiment of the present disclosure.

Referring to FIG. 4, the SHIN 30, which is a cached WADL execution engine according to an embodiment of the present invention, may include an acquisition unit (not shown) and an execution unit (not shown). For example, an acquisition unit (not shown) may include an OWL-S Java API 31 and an execution unit (not shown) may include a cache manager 33 and a RESTful web application server 34, It is not.

The OWL-S Java API 31 can implement WADL as a SWS execution engine used together with RESTfulGrounding, and the OWL-S Java API 31 can extend the Grounding Provider interface to support various grounding. The OWL-S Java API 31 applied to the SHIN 30 of the present application may mean an execution engine extended from the OWL-S grounding provider interface for processing WADL-based RESTfulGrounding by the WADL Grounding Provider 31c .

The OWL-S Java API 31 may include, for example, a WSDL Grounding Provider 31a, a UPnP Provider 31b, and a WADL Grounding Provider 31c as various grounds.

The OWL-S Java API 31 of the SHIN 30 can acquire (receive) a service corresponding to the request from the semantic web database 20 as an execution service (execution service). When the execution service is acquired, You can call the grounding in.

Specifically, when the OWL-S Java API 31 receives a service corresponding to a request as an execution service (Execute Service), the OWL-S Java API 31 can call the WADL request 32 via the WADL Grounding Provider 31c, The WADL request 32 can be executed while interpreting it. In other words, the OWL-S Java API 31 can acquire a WADL resource (i.e., a URI) corresponding to the Atomic process of the execution service in response to the call, and the acquired WADL resource is transmitted to the WADL Grounding Provider 31c Can be interpreted and executed. At this time, when the SHIN 30 calls the WADL request 32, the cache manager 33 can be cached. Thus, the called WADL request 32 may be referred to as a cached WADL request.

The SHIN 30 may invoke the WADL request 32 cached via the WADL grounding provider 31c of the OWL-S Java API 31 which is the OWL-S execution engine, and in response to the call, You can interpret and execute the WADL resource corresponding to the process. At this time, the SHIN 30 can communicate with the RESTful web application server 34 using the WADL when interpreting the WADL resource. Further, the SHIN 30 can communicate with the Web services 40 by analyzing and executing the WADL resources corresponding to the execution services, thereby enabling the SHIN 30 to send execution services (i.e., Service) may be invoked.

Also, when the WADL resource corresponding to the request is executed, the SHIN 30 can confirm whether the WADL resource is changed using the cache manager 33 while the WADL resource is being cached. At this time, the SHIN 30 obtains the value of the cache entry corresponding to the URI through the cache manager 33 with the URI included in the WADL resource as a key, thereby confirming whether or not the WADL resource has been changed have. The SHIN 30 may also perform Conditional Requests of HTTP 1.1 based on the tag value contained in the value of the cache entry. At this time, the SHIN 30 can confirm whether or not the WADL resource is changed based on a write-through caching algorithm using a conditional request.

The SHIN 30 may also store the result of the call of the RESTful web application server 34 by invoking the cached WADL request 32 in the cache entry so that the cached execution engine can be implemented. Here, the RESTful web application server 34 may refer to a server that provides a service for exchanging information resources on the network through the web using URI and HTTP basic functions (GET, POST, PUT, DELETE).

The cache manager 33 is responsible for managing cache entries for the GET method in the execution engine client, which can be otherwise referred to as a cache store.

The cache manager 33 according to one embodiment of the present disclosure can be implemented as a simple dictionary of JVM memory. In addition, the cache manager 33 may be implemented by storing many other key-values. In addition, the cache manager 33 may use the LRU algorithm for spacing the cache entries and may store the resources based on the LRU algorithm.

On the other hand, if the process can perform caching (i.e., there is a previously invoked service or an atomic process) by checking the Etag or Modified-Since header in the server's response, You can return the cached result through a call. Therefore, the SHIN 30 can provide a service orchestration in the form of automatic retrieval, invocation, composition, and interoperability of web services constituting an SOA-based infrastructure.

In this case, a cached WADL execution engine (SHIN) 30 is proposed as a new WADL execution engine for a RESTful web service. When a web service is executed using the SHIN 30, the speed of the SOA process is improved . SHIN 30 can request the WADL specification using the 'HTTP 1.1: Conditional Request' method. The cached WADL execution engine and the web service invocation method using the cached WADL execution engine according to an embodiment of the present invention can improve the performance for a complicated process and reduce the network latency more effectively.

Hereinafter, the operation flow of the present invention will be briefly described based on the details described above.

FIG. 5 is a schematic flowchart illustrating a method of calling a Web service using a cached WADL execution engine according to an exemplary embodiment of the present invention. Referring to FIG.

The web service invocation method using the cached WADL execution engine shown in FIG. 5 can be performed by the cached WADL execution engine described above. Therefore, even if omitted below, the contents described for the cached WADL execution engine can be similarly applied to the description of the web service invocation method using the cached WADL execution engine.

Referring to FIG. 5, in step S51, a service corresponding to the request acquired from the semantic web database can be acquired as an execution service.

Next, in step S52, the cached WADL request is called through the OWL-S Java API which is the OWL-S execution engine, and the WADL resource corresponding to the Atomic process of the execution service is analyzed and executed in response to the call. At this time, as the communication between the web services is performed in step S52, the web service corresponding to the service can be called from the web services.

In step S52, the WADL grounding provider of the OWL-S execution engine can invoke the cached WADL request.

In step S52, when the WADL resource is executed, whether or not the WADL resource has been changed can be confirmed by using the cache manager while the WADL resource is being cached. At this time, the cache manager can store resources based on the LRU algorithm.

In addition, in step S52, it is possible to confirm whether or not the WADL resource is changed by acquiring the value of the cache entry corresponding to the URI through the cache manager with the URI included in the WADL resource as a key.

In addition, in step S52, conditional requests of HTTP 1.1 can be performed based on the tag value included in the value of the cache entry.

In addition, in step S52, it is possible to confirm whether or not the WADL resource is changed based on a write-through caching algorithm using a conditional request.

Further, in step S52, the result of calling the RESTFul web application by calling the cached WADL request may be stored in the cache entry.

In the above description, steps S51 to S52 may be further divided into further steps or combined into fewer steps, according to embodiments of the present disclosure. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

The web service invocation method using the cached WADL execution engine according to an exemplary embodiment of the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the 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. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

It will be understood by those of ordinary skill in the art that the foregoing description of the embodiments is for illustrative purposes and that those skilled in the art can easily modify the invention without departing from the spirit or essential characteristics thereof. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be interpreted as being included in the scope of the present invention.

30: Cached WADL Execution Engine
31: OWL-S Java API
33: cache manager
34: RESTful web application server

Claims (10)

(a) acquiring a service corresponding to a request acquired from the semantic web database as an execute service; And
(b) invoking a cached WADL request through an OWL-S (Web Ontology Language for Service) execution engine, and interpreting and executing a WADL resource corresponding to the execution service in response to the call ,
And the web service corresponding to the service is called from the web services as the communication between the web services is performed according to the step (b). The method according to claim 1,
In the step (b)
And calling the cached WADL request through a WADL grounding provider of the OWL-S execution engine. The method according to claim 1,
In the step (b)
When the WADL resource is executed, checking whether the WADL resource is changed using the cache manager in a state of caching the WADL resource. The method of claim 3,
In the step (b)
Wherein a cache entry corresponding to the URI is obtained from the cache manager by using a URI included in the WADL resource as a key to confirm whether the WADL resource is changed or not by using the cached WADL execution engine How to call a web service. 5. The method of claim 4,
In the step (b)
And performs conditional requests of HTTP 1.1 based on the tag value included in the value of the cache entry. 6. The method of claim 5,
In the step (b)
Wherein a change in the WADL resource is checked based on a write-through caching algorithm using the conditional request. 5. The method of claim 4,
In the step (b)
And storing the result of calling the RESTful web application by invoking the cached WADL request in the cache entry. The method of claim 3,
Wherein the cache manager stores resources based on an LRU algorithm. An acquiring unit acquiring a service corresponding to a request acquired from the semantic web database as an execute service; And
And an execution unit that invokes a cached WADL request through an OWL-S (Web Ontology Language for Service) execution engine, and interpreting and executing a WADL resource corresponding to the execution service in response to the call,
And a web service corresponding to the service is called from the web services as the execution of the communication between the web services by the execution unit. A computer-readable recording medium on which a program for executing the method of any one of claims 1 to 8 is recorded.

Images