KR100963785B1 - DYNAMIC WEB SERVICE PROXY METHOD FOR OSGi SERVICE PLATFORM - Google Patents

Abstract

Discuss dynamic interworking method with web service in OSGi service platform. In the OSGi service platform, a dynamic interworking method with a web service may include: generating a service assembly description according to a request in an OSGi application service; Analyzing the service assembly description in a plumbing service; Calling a web gateway service from the plumbing service if it is necessary to interconnect with a web service as a result of the analysis; Generating, by the web gateway service, a proxy for the web service, which is requested to interwork with the plumbing service, and registering the proxy in the service registry; And assembling a service from the plumbing service and interworking with the web service.

OSGi, Web Services, Interoperability, Proxy

Description

Dynamic Interworking Method with Web Services in OSSi Service Platform {DYNAMIC WEB SERVICE PROXY METHOD FOR OSGi SERVICE PLATFORM}

The present invention relates to a dynamic interworking method with a web service in an open service gateway initiative (OSGi) service platform. In particular, when a request for a web service is made when a service is executed in an OSGi service platform, a proxy is generated. Through this, it is a way to dynamically interact with web services.

With the development of electronic technology, as electronic devices become more intelligent and the spread of the Internet spreads, new ubiquitous technologies are actively being researched to provide more convenient services by integrating various technologies.

In particular, Smart-Home technology is one of such ubiquitous technologies, and refers to the concept of a home network, which means that digital information devices having various functions are connected to a network for function sharing, data sharing, and remote control. Beyond that, it is an important technology that includes the creation of better services through the intelligence of services and the integration between services.

In this smart home technology, a service platform is required for a technology that can manage and connect various services. A representative service platform is an OSGi service platform proposed by the Open Service Gateway initiative (OSGi).

OSGi service platform operates inside Home Gateway that manages connection between internal and external environment in smart home environment, manages internal equipment and services, and connects various external services based on this. do.

In addition, the OSGi Core standard defines a service framework that registers (connects), manages, and executes services and devices within the framework, defines some basic services, and defines the contents of user program creation. Doing. The framework in the OSGi service platform installs and registers the necessary services and stores the information. When the user requests the required services, the framework searches for and provides them.

On the other hand, stubs of web services, the existing technology for using web services, cannot be used in OSGi environment. This is because it must be in the form of a bundle conforming to the standard specified in the OSGi service platform specification.

Conventionally, a technology for interworking OSGi services and web services is to generate a Java class from the WSDL of the web service, generate a bundled activator class from the Java class, and compress the web service into a jar file according to the OSGi service platform specification. There is a way to interlock. However, this is difficult to see as the dynamic web service in the execution stage when the services are interworked by creating a separate jar file. Also, since the stub of the web service is generated before the service is executed, it cannot be properly reflected when there is a change according to the update of the web service. And unnecessary stubs are generated in advance, which wastes memory. In addition, the reuse of services that allow other services to use dynamically generated services using stubs from Web services is not supported.

In other words, the prior art has a purpose to automatically generate a step for using a web service rather than a focus for interoperability between the OSGi service and the web service. As with the client and development of the web service, the service function must be implemented through the WSDL file and interface, and the service, which is an interoperable OSGi client, must be implemented. However, this produced client service cannot be used for interworking with other web services with similar functions because it is based on port type and partner type of a specific web service. This results in the production of client services of unnecessary services in terms of service assembly.

The present invention provides a dynamic interworking method with a web service in the OSGi service platform.

The present invention provides a method for dynamically interacting with a web service by creating a proxy when a request for a web service is made when the service is executed in the OSGi service platform.

In the OSGi service platform according to an embodiment of the present invention, a dynamic interworking method with a web service may include generating a service assembly description according to a request from an OSGi application service; Analyzing the service assembly description in a plumbing service; Calling a web gateway service from the plumbing service if it is necessary to interconnect with a web service as a result of the analysis; Generating, by the web gateway service, a proxy for the web service, which is requested to interwork with the plumbing service, and registering the proxy in the service registry; And assembling a service from the plumbing service and interworking with the web service.

An embodiment of the present invention comprises the steps of generating a service assembly description according to the request in the OSGi Application Service (OSGi Application Service); Analyzing the service assembly description in a plumbing service; Calling a web gateway service from the plumbing service if it is necessary to interconnect with a web service as a result of the analysis; Generating, by the web gateway service, a proxy for the web service, which is requested to interwork with the plumbing service, and registering the proxy in the service registry; And a method of dynamically interoperating with a web service in an OSGi service platform including assembling a service in the plumbing service and interworking with a web service. It can provide the function to create the delegate of the web service, and it can remove the dependency of the OSGi services on the specific web service and increase the service reusability through the service interworking of the OSGi services.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. If it is determined that the gist of the present invention may be unnecessarily obscured, the detailed description thereof will be omitted.

An embodiment of the present invention is a method of dynamically interacting with a web service by creating a proxy when a request for a web service is made when the service is executed in an OSGi service platform.

1 is a diagram illustrating a structure of an OSGi framework for an OSGi service platform interoperating with a web service according to an exemplary embodiment of the present invention. Referring to FIG. 1, the OSGi framework 100 includes an OSGi Application Service 110, a Plumbing Service 120, a Web Gateway Service 130, and a Proxy. 140, a service registry 150.

The OSGi Application Service 110 is a type of graphical user interface (GUI) application used by a user. The OSGi Application Service 110 generates an XML description graph according to a user's request and generates the generated service assembly description. To the plumbing service 120 to request the configuration of the service.

The plumbing service 120 is a system service of the OSGi framework that receives a service assembly description in the form of XML and assembles and manages the services described thereon. The plumbing service 120 includes a wire admin service, a declaratvie service, an event admin service, and a service tracker. Here, the Wire Admin service is a service that manages wires connecting the services. The Wire Admin service provides each consumer or producer service to pass values via wires without invoking the service directly. The Declaratvie service is a service that manages the dependency of each service component. Event Admin service is a service that manages events of services, and Service Tracker is a service that tracks the status of the service. Here, the status of the service means the life cycle status of installation, activation, deactivation, and uninstallation. That is, the plumbing service 120 is a service for managing a dynamic pipe connection using a wire admin service, a declaratvie service, an event admin service, and a service tracker.

In addition, the plumbing service 120 is a subject that connects the proxy 140 generated by the web gateway service 130 with another service according to an embodiment of the present invention. That is, the service defined in the XML specification is retrieved from the service registrar 150 and connected to the consumer and the producer service. At this time, Proxy and OSGi services are connected.

After the connection of the services, the plumbing service 120 keeps track of the corresponding services for management of the connected services (the tracking is performed by the above-described Service Tracker service). That is, the plumbing service 120 detects and responds to a state change of internal services of the assembled service (replacement of the service, discontinuance of the assembled service, etc.).

The Web Gateway Service 130 reads a Web Services Description Language (WSDL) file of the web service 160 as a system service inside the OSGi framework and analyzes the web service description language (162) file to analyze the proxy of the web service 160. 140) to create a service. More details of the web gateway service 130 will be described later with reference to FIG. 2.

The proxy 140 is registered as a service in the OSGi framework 100 as a delegate of the web service 160 and directly connects to OSGi services. More details of the proxy 140 will be described later with reference to FIGS. 3 and 4.

The service registry 150 registers and stores OSGi services in service and provides information on services registered with the plumbing service 120. In addition, according to an embodiment of the present invention, the proxy 140 generated by the web gateway service 130 is additionally registered and stored, and the registration event is provided to the plumbing service 120 when the proxy 140 is registered.

2 is a diagram illustrating a structure of a web gateway service in an OSGi framework for interworking with a web service according to an exemplary embodiment of the present invention. 2, the web gateway service 130 may include a WSDL analyst 232, a proxy generator 234, and a proxy manager 236.

The WSDL analyst 232 retrieves a web service provided from the plumbing service 120, requests a WSDL, and analyzes the WSDL of the web service 160 to obtain information necessary for generating a proxy therefrom. Parsing a WSDL here means parsing it because the WSDL is an XML description. That is, the WSDL analyzer 232 generates a proxy by checking information such as a web service name, an interface, a service URL, an encoding type, a method name, input and output variable (parameter) types, etc. for generating a proxy from the parsed XML document. Provided to section 234.

The proxy generator 234 generates the proxy 140 using the information obtained by the WSDL analyzer 232.

The proxy manager 236 is a module that tracks / manages the generated proxy. The proxy manager (236) registers the proxy (140) generated by the proxy generator (234) with the service register (150) and maintains a list of services corresponding to the proxy created by the proxy generator (234). Using this, the status of the web service is periodically checked through the Simple Object Access Protocol (SOAP), and the service is updated or lost. That is, it plays a role of detecting event occurrence of web service. In addition, the proxy manager 236 directly manages the proxy 140 generated by the proxy generator 234 to suppress generation of unnecessary services.

3 is a diagram illustrating interworking between a web service and an OSGi service through a proxy in an OSGi framework for interworking with a web service according to an exemplary embodiment of the present invention.

Referring to FIG. 3, interworking through proxies is performed through Pipe and SOAP. That is, the interworking between the proxy 140 and the OSGi services 302 and 304 connects via a pipe to receive or transmit a value, and the interworking between the proxy 140 and the web service 160 requests using SOAP. Or answer.

4 is a diagram illustrating a configuration of a proxy created for interworking with a web service according to an exemplary embodiment of the present invention. Referring to FIG. 4, the proxy 140 includes a web service processor 442, a message converter 444, and an OSGi processor 446.

The web service processing unit 442 is a module that processes the interaction between the proxy 140 and the web service 160, and uses a JAX-RPC type dynamic call interface client type invocation method provided by AXIS for invoking a web service. do. The web service processor 442 creates a Call object therein and processes a message with the web service through the web object.

The message converting unit 444 is a module for modifying and transmitting the message processing type of the called service in order to overcome the difficulty of interworking caused by the difference between the OSGi service and the service calling method of the web service 160. The function of this proxy 140 supports assembly of loosely coupled services between web services and OSGi services.

The OSGi processing unit 446 is a module that processes the interaction between the proxy 140 and the OSGi service and is connected through a pipe. At this time, Pipe basically interacts with services through update method and pulled method. Where update is a call to pass (response) the value from the child service (eg producer service) to the parent service and pulled requests (requests) the value of the child service from the parent service (eg consumer service). Is the call to

Hereinafter, a method of dynamically interoperating with a web service in the OSGi service platform according to the present invention configured as described above will be described with reference to the accompanying drawings.

5 is a flowchart illustrating a process of interworking with a web service in an OSGi service platform according to an exemplary embodiment of the present invention.

Referring to FIG. 5, if the OSGi service platform detects a service request from a user through an OSGi application service in step 500, the OSGi service platform proceeds to step 502 to generate a service assembly description of the requested services, and proceeds to step 504. The service assembly description is analyzed using a plumbing service, and the process proceeds to step 506 to search for the analyzed service.

After that, the plumbing service of the OSGi service platform proceeds to step 508 to check whether the searched service is a web service. If the check result is a web service, the flow proceeds to step 510 where the plumbing service calls the web gateway service.

After that, the web gateway service of the OSGi service platform proceeds to step 512 to read and analyze the web services description language (WSDL) of the web service that is requested to be interoperated with the plumbing service, and then to step 514. Proceed to create a proxy using the analysis information of the WSDL, and proceeds to step 516 to register the generated proxy in the service registry.

After that, when the plumbing service of the OSGi service platform detects that the proxy is registered in the service registry in step 518, the plumbing service of the OSGi service platform assembles the service and provides the service linked with the web service.

On the other hand, if the web service does not exist in the searched result of step 508 and only the OSGi service exists, the plumbing service (Plumber Service) assembles and connects the OSGi service according to the conventional technology.

Embodiments according to the present invention can be implemented in the form of program instructions that can be executed by various computer means can be recorded on a computer readable medium. The computer readable medium may include program instructions, file data, data structures, etc. alone or in combination. Program instructions recorded on the media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and 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 not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

As described above, although the present invention has been described with reference to the limited embodiments and the drawings, the present invention is not limited to the above embodiments, and those skilled in the art to which the present invention pertains various modifications and variations from such descriptions. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the claims below but also by the equivalents of the claims.

1 is a diagram illustrating a structure of an OSGi framework for an OSGi service platform interoperating with a web service according to an embodiment of the present invention;

2 is a diagram illustrating a structure of a web gateway service in an OSGi framework for interworking with a web service according to an embodiment of the present invention;

3 is a diagram illustrating interworking between a web service and an OSGi service through a proxy in an OSGi framework for interworking with a web service according to an embodiment of the present invention;

4 is a diagram illustrating a configuration of a proxy generated for interworking with a web service according to an embodiment of the present invention;

5 is a flowchart illustrating a process of interworking with a web service in an OSGi service platform according to an exemplary embodiment of the present invention.

Claims (8)

Generating a service assembly description according to a request in an OSGi application service; Analyzing the service assembly description in a plumbing service; Calling a web gateway service from the plumbing service if it is necessary to interconnect with a web service as a result of the analysis; Generating, by the web gateway service, a proxy for the web service, which is requested to interwork with the plumbing service, and registering the proxy in the service registry; And Assembling a service in the plumbing service and interworking with a web service. The web gateway service of claim 1, When the interworking request is received from the plumbing service, the Web service description language (OSDL) of the web service is read and analyzed, and the proxy is generated using the information of the WSDL. Dynamic interworking methods. The method of claim 2, wherein the information of the WSDL used when generating the proxy, A dynamic interworking method with a web service in an OSGi service platform, comprising a web service name, an interface, a service URL, an encoding type, a method name, and input and output variables (parameters). The web gateway service of claim 1, Dynamic interworking method with the web service in the OSGi service platform, characterized in that it periodically checks the status of the web service through the Simple Object Access Protocol (SOAP) to detect the update or loss of the service and respond to it. . The web gateway service of claim 1, And the proxy information is deleted from the service registry when the service of the proxy is terminated. The method of claim 1, wherein the proxy is Dynamic interworking method with the web service in the OSGi service platform, characterized in that the connection via the web service and the Simple Object Access Protocol (SOAP). The method of claim 1, wherein the assembled service includes an OSGi service, The proxy is Dynamic interworking method with web service in OSGi service platform characterized by connecting OSGi service and pipe. A computer-readable recording medium in which a program for executing the method of any one of claims 1 to 7 is recorded.

Images