KR20100045656A - A method of interoperability between dpws and web services - Google Patents

Abstract

The present invention relates to a device for interworking between a Jini service and a web service in a ubiquitous environment, and a method for interworking between a Jini service and a web service using the device. More specifically, a lookup service, an adapter, a registration agent, a query agent, and a device / An apparatus for interworking between a Jini service and a web service including a service registry, a context registry, and UDDI, and an interworking method using the device.

According to the present invention, the web service user can discover and use the Genie service, and the user of the Genie system can also find and use the Web service, so that all users can discover and use all the services of the ubiquitous environment.

Description

Apparatus and method for interworking between Web services and web services {A Method of Interoperability between DPS and Web Services}

The present invention relates to a device for interworking between a Jini service and a web service in a ubiquitous environment, and a method for interworking between a Jini service and a web service using the device.

Advances in computing and networks are diversifying and facilitating intelligence in information appliances. The development of information appliances is increasing interest in ubiquitous. Ubiquitous is an environment that supports any service of any device on any network anytime, anywhere (M. Satyanarayanan.Pervasive Computing: Vision and Challenges. IEEE Personal Communications, pp.10-17, 2001). Various service discovery middleware (Jini (Sun Microsystems. Jini Architecture Specification. Http://www.sun.com/jini/), DPWS (Hendrik Bohn, "SIRENA-) which provides service dynamic discovery and binding to realize ubiquitous environment. Service Infrastructure for Real-time Embedded Networked Devices: A service oriented framework for different domains ", 2006), and Havi (The Havi Organization, Havi Version 1.1 Specific ation. Http://www.havi.org). In this document, the service discovery middleware is called a subnetwork. However, these subnetworks have a difference in service description method, communication method, and system description language as shown in Table 1 below. Each subnetwork describes a service using Java classes, WSDL, and structures, each of which contains the information needed to use the service. In addition, Java communication method uses RMI, HTTP based SOAP message, and wireless communication based IEEE1394. Jini and Havi are implemented using Java, and DPWS is implemented using C ++ and Java. This is possible.

By solving the interoperability between these various subnetworks, it becomes possible to achieve true ubiquitous.

Methods for interoperation of subnetworks include individual bridges between subnetworks and an integrated middleware architecture-based approach.

The bridge interworking method between subnetworks is a method for solving interoperability by using a 1: 1 bridge between subnetworks for interworking heterogeneous subnetworks. In Genie systems, you must create bridges for interoperation with heterogeneous subnetworks. While this method facilitates interworking between two subnetworks, it does not solve the interworking between various subnetworks. When a new subnetwork appears, it is necessary to create n (n-1) bridges for the existing subnetwork. n represents the number of currently existing subnetwork. The emergence of new sub-networks not only increases the number of bridges, but also introduces complexity in connection, and does not provide a consistent method for connecting between sub-networks, and also has scalability problems.

Integrated middleware has a structure that connects each subnetwork through an abstracted common layer. This architecture can be easily integrated with other sub-networks even if new middleware emerges, as long as the adapter is implemented.

The Genie system is a technology in which intelligent devices or software that are connected to a network in various ways based on Java can dynamically interact, and have a structure as shown in FIG. 1.

The Genie service registers a lookup service with information to search and use the service on the proxy. Lookup service acts as broker between service and user. The Genie system communicates with each other using RMI.

The Genie system provides the proxy with ServiceID, Service Interface Object, and AttributeSets information. The attribute set contains additional information about the service, including information about the address, location, service description, and service status information. In addition, the Genie system uses group information as a way to limit the use of services. Services available to all users belong to 'Publish' group, and group information can be registered, deleted and changed by administrator. A group registered by an administrator can only be used by clients belonging to the group.

The Genie system stores the event information in the ServiceRegistrar of the lookup service. Stored event information is divided into three categories as shown in Table 2 below.

The Genie client can process events related to the Genie service using the above three categories of events stored in the service register.

The Genie system uses Java classes to describe services and discovers and uses them through RMI. Web services, on the other hand, use WSDL to describe services and to discover and use services based on SOAP messages. Therefore, due to the difference between the Genie system and the web service, you cannot use each other's services.

Techniques such as GOAL (General brOkering Architecture Layer) have been devised for Genie and Web service users to discover and use services.

GOAL converts a web service into a Genie service and registers it with a lookup service. GOAL converts a Web service into a Web service and registers it with UDDI. GOAL registers a web service with UDDI, converts it to a Genie service, and registers it with the lookup service. The Genie service is not only registered with the lookup service but also converted into a web service and registered with UDDI. For each registered service, the web service client searches the UDDI to use the web service and the genie service, and the genie client can search and use the web service and the genie service through the lookup service.

However, since GOAL cannot use event information, it is not possible to determine whether the Genie service is currently available when the Web service client uses the Genie service, and it does not consider the current location of the service. Search is not possible. Even when the Genie client uses the web service, it is impossible to search for the newly emerged service.

In addition, GOAL needs a large-scale lookup service to store Genie services by converting all web services into Genie services one-to-one. In addition, when the lookup service is rebooted, all registered information disappears, thus re-registering the Genie service and converting and registering the Genie service again for the Web service.

An object of the present invention is to provide a device and an interworking method using the same Jini-based services and web services in the ubiquitous environment.

The present invention for solving the above problems, an apparatus and method for reflecting the service dynamic state of the sub-network in the ubiquitous environment.

(1) Device for interworking between Jini service and web service

The present invention includes a lookup service, an adapter, a registration agent, a query agent, a device / service registry, a context registry, and a UDDI, wherein (A) the lookup service searches for Jini devices and services existing in a network, Stores metadata information and event information of the; (B) The adapter, ① requests the source file associated with the Genie service to the lookup service, receives and delivers it to the registration agent, ② generates a web service for the Genie service, and registers the service information of the generated web service as a registration agent. To; (C) the registration agent registers specification information and dynamic state information of the Genie service among the source files received from the adapter in the UDDI, device / service registry, and context registry, respectively; (E) The query agent determines whether the service stored by the lookup service is already registered in the device / service registry and the context registry, and transmits the information to the adapter (the service of the already registered service). Prevent duplicate registration); A device for interworking between a Jini service and a web service.

(2) Method for reflecting service dynamic status

In addition, the present invention uses the above device, the hook-up process, genie service appearance process, service state information change process, service technology information change process, service group information registration process, service group information deletion process, lookup each consisting of It relates to the interworking method between Jini service and web service including service exit process and Genie service exit process.

(A) Hook-up process: ⓐ the lookup service searches for Jini devices and services existing in the network and stores their metadata information and event information ⓑ The adapter searches for a lookup service Acquiring information about the Jini device or service registered in the lookup service. The adapter converts the retrieved Jini services into a web service, and registers the generated web service information and the meta information of the retrieved Jini device or service. Step of sending to the agent, the registration agent registers the meta information in the UDDI, device / service registry and context registry, respectively.

(B) Genie service appearance process: ⓐ the lookup service to search for Jini devices and services existing in the network and to store their metadata information and event information ⓑ When a new service appears and the event occurs, the lookup The service transmits the event information to the adapter. The adapter checks whether the service in which the event occurs is already registered through the query agent. Step of transitioning the stand to the "available" state In the case of a new service, the adapter, requesting and obtaining information about the service from the lookup service ⓕ create a virtual web service for the service, the generated web Agencies to register service information and related meta information of services Step ⓖ the registration step in which the agent registers the meta information on each device / service registry and the registry context to be transmitted to.

(C) Service state information change process: ⓐ the lookup service searches for Jini devices and services existing in the network and stores the information of the device or service in which the state information change event occurred ⓑ the lookup service recalls the event information Transmitting the event information to the registration agent to the adapter, the registration agent to change the status information for the service in which the event occurred stored in the device / service registry.

(D) Service technology information change process: ⓐ the lookup service to search for the Jini device and service existing in the network and to store the information of the technology information change event occurs ⓑ the lookup service to deliver the event information to the adapter Step © The adapter transmits the event information to the registration agent, to change the registration information of the service that the event occurred stored in the device / service registry and the context registry.

(E) Service group information registration process: ⓐ the lookup service receives a new Genie service group ⓑ the lookup service delivers event information to the adapter © the query agent, the service where the event has already occurred Step of confirming whether the service is already registered. Ⓓ If the service is already registered, transitioning the service to the "available" state for the service in the context registry. After requesting and acquiring the information, generating a virtual web service for the service and transmitting the generated service information and related meta information to the registration agent. The registration agent transmits the meta information to the UDDI, device / Registering in the service registry and context registry .

(F) process of deleting service group information: ⓐ step of receiving, by the lookup service, information for deleting the genie service group ⓑ the step of delivering the event information to the adapter ⓒ when the lookup service transmits event information to the registration agent, And registering, by the registration agent, state information on a service group in which the event occurred, stored in the device / service registry.

(G) Step of exiting lookup service: ⓐ the lookup service stops the lookup service function for all Genie devices registered in the lookup service ⓑ the lookup service delivers event information to the adapter © registers event information Transmitting, by the registration agent, the status information of all Genie devices in which the event is stored in the device / service registry.

(G) Genie service exit process: ⓐ the look-up service, inquiries Jini devices whether the service availability at a predetermined time interval ⓑ The response to the service availability query is not returned for a predetermined time, or the connection is terminated (Bye) for the device having the message, the lookup service delivers event information to the adapter. When the adapter delivers the event information to a registration agent, the registration agent is registered in the device / service registry. Changing and registering the status information for the "unavailable" status.

According to the present invention, interoperability between Jini and web services is possible by using a Genie adapter based on Web Services on Universal Networks (WSUN) as an integrated middleware method. Therefore, Web service users can discover and use Gini services, and Gini system users can discover and use Web services, so that all users can discover and use all services in the ubiquitous environment.

More specifically, according to the present invention, a method for a web service client to search for and use a service and a Genie client to discover and use a web service have the following advantages.

(1) In Genie service search and use of web service clients, web service clients can use the service status information to receive a list of currently available services, and by providing the location of services, the service is close in terms of service usage. Can be used.

(2) In the search and use of web services of Genie clients, it is unnecessary to convert web services to Genie services by utilizing Generic web services, and the device of lookup service can be reduced in size, and further newly appeared web by directly searching UDDI. It is possible to search for and use the service.

Hereinafter, with reference to the accompanying drawings will be described in more detail the structure and operation of the components in the present invention, device / service search and use method in the ubiquitous environment utilizing the device / method according to the present invention. However, this attempt is only an example for easily explaining the content and scope of the technical idea of the present invention, and thus the technical scope of the present invention is not limited or changed. It will be apparent to those skilled in the art that various changes and modifications can be made within the scope of the technical idea of the present invention based on these examples.

Hereinafter, the adapter is referred to as ' adapter ' or ' genie adapter '.

The present invention relates to an apparatus and a method for interworking a Jini service and a web service using a lookup service, an adapter, a registration agent, a query agent, a device / service registry, a context registry, and a UDDI.

In the description of the present invention, 'metadata' refers to information regarding a location or a service type of a device, and 'event information' refers to information regarding the appearance or exit of a service.

In the present invention, the Genie adapter extends the Genie client, the lookup service, and the web service client to perform event processing, service search, web service generation, web service search, and message conversion functions.

According to the apparatus of the present invention, the Genie service is searched and processed by the Genie client, and the lookup service is extended to search for a web service. And to use web service, we use web service client function. In addition, it has a message conversion function to solve the difference between the message and the protocol (see Fig. 3).

A block diagram (A) showing an exemplary structure of a device according to the invention and the interrelationships between the adapter and lookup service, UDDI, web service and genie service in the device and method according to the invention are illustrated in FIG. As shown.

According to the present invention, a web service is used as an intermediary for interaction between a Genie service and another kind of service. Therefore, the Genie service is converted into a virtual web service, the converted and generated web service is stored, and the service information such as service name and service address value of the generated web service is registered in UDDI. The Genie client uses the Genie service by searching for the web service registered in UDDI through the Genie adapter. The Genie client then retrieves and uses the web service through the Genie adapter. In summary, the Genie service is transformed into a virtual web service, and the service itself is stored in WSUN's web service storage space. In UDDI, information such as the name of a created service or a service address value (location) is stored. This information makes other services available to Genie. For reference, it is referred to as "Virture Service" in FIG. 5, which means that only the information about the service is delivered, not the actual service.

According to the present invention, according to the Genie adapter architecture, it can be divided into (I) Web service client discovering and using Genie service and (II) Genie client discovering and using Web service.

(I) Discover and use the Genie service of a web service client

In order for the web service client to discover and use the Genie service, the Genie service needs to be registered in the UDDI and the device / service registry, and the Genie service is converted into a Web service.

The Genie adapter retrieves all services present in the Genie system and informs the registration agent. The registration agent registers these services in the device / service registry and context registry, which are the storage of WSUN. In addition, the information about the web service converted from the Gini service is registered in UDDI.

The following describes the process of converting a Genie service into a web service, the process of processing a Genie event, and the process of discovering and using a Genie service by a web service client.

1 <Create Web Service>

In order to discover and use Genie services, heterogeneous network clients are converted to Web services. To create a web service, four steps are required:

(1) Request a source file related to the Genie service from the Genie adapter.

② Download source file related to Genie service from Genie adapter.

③ Create a web service using Axis.

4. Save the WSDL address in the registry.

In order to register the web service created through the above process to UDDI, WSUN is registered in the business entity and Genie service name is registered in the business service.

2 <Genie event processing>

The Genie system provides status information about the service. Using this information, we provide the currently available Genie service to the web service client. In the environment where the Genie system and the heterogeneous system are operated, the event when the Universal Service Broker appears and the hook-up process, the Genie service appearance process, the service status information change process, the service technical information change process, and the service that occur in the Genie system A predetermined action is performed on events such as group information registration process, service group information deletion process, lookup service exit process, and genie service exit process.

(A) Hook-Up

Hook-Up is an event that occurs when the Genie adapter starts running in the environment where the Genie system and the heterogeneous system are operated at design time. The Genie adapter first registers all services registered with each lookup service in the lookup services in the Genie system. At this time, the service is registered using the event information stored in the lookup service, and the process as shown in FIG. 5 is performed.

In order to find the existing Genie services by using the Genie adapter, the Genie client module is used to find the lookup service in the current system using the multicast message (1-2). After looking up the lookup services, information about the services registered in each lookup service is obtained by using a uticast message to each lookup service (3-4). It then sends a unicast message and receives a response to get service interface information for using the service (5-6). Since one Genie service can be registered to several lookup services, the service ID is determined for the service in (7) to determine whether the service has been registered before. In order to use the Genie service in other types of services, the process of creating the Genie service as a web service (8) is passed to the registration agent to store the extracted service information for storage in each registry. 9). The registration agent stores information about the generated web service in UDDI (10-11), and stores metadata and location information about the genie service in the device / service registry and the context registry (12-16).

The event handling described below is an event that occurs in the Genie system while the Genie adapter is running at runtime.

(B) Genie service appearance

The Genie service appearance event is when a new service appears in the lookup service of the Genie system while the Genie adapter is running. The related event will use the event registered in the Registrar of the lookup service.

The process of processing an event related to the appearance of the Genie service is shown in FIG. 6. The process (1-5) is the same as the process in which the service is registered with the lookup service in the Genie system. When a service is registered and an event occurs, the Genie adapter receives relevant event information from the lookup service (6-7). When the related information about the registration event is received, it is determined whether the same service is registered in the registry through the query agent using the SerivceID of the service (8-11). If information about the Genie service exists, the service is a Genie service registered as a web service. In the case of such services, the process goes to (13-16). Process (13-16) handles the process of changing the state of the service from the unavailable state to the available state because the current service is registered in the past, but is exited and reappeared.

However, in the case of a service that does not exist, the Genie adapter requests the lookup service for information about the related service and receives the service information (17-18). 19-27 is the same as the procedure for storing a service in the hook-up step.

(C) changing service status information

The service state information change event refers to a case in which the service is currently in use or an error occurs in the service and thus cannot be used (see FIG. 7).

When the status information changes, the Genie service registers information about the event in the lookup service (1). The Genie adapter asks the lookup service whether the event has occurred at regular intervals as a unicast message, and receives new event information from the lookup service when there is a new event (2-3). Genie adapter goes through the process of changing the status information of the service registered in the registry by using the related event (4-7). Although the Gini service processes the status information in various ways, the exemplary description of the present invention divides the status information of the service into usable and unusable. If the service is currently in use or an error occurs, other users will not be able to use the service.

(D) Change of service technical information

Genie services are mobile. The change of the service technical information is a case where information such as the address and location of the Genie service is changed and registered in the lookup service (see FIG. 8).

The Genie service registers the related event in the lookup service (1), and the Genie adapter receives the related event information from the lookup service (2-3). The service information registered in the registry is changed for the related information (4-9).

(E) Genie service group information registration

The Genie system restricts the use of the service by using group information by the administrator. The group information registration event indicates a process in which a service is registered and processed for a group added by an administrator (see FIG. 9).

The administrator adds a new group to the lookup service and registers a service belonging to the group (1-5). The Genie adapter receives the related events from the lookup service (7-8), and the subsequent process (9-28) goes through the same process as the Genie service appearance.

(F) Delete Genie service group information

The deletion of the Genie service group information indicates a process of processing the deletion because the group information is deleted by the administrator and thus an unusable state is generated for the services belonging to the group (see FIG. 10).

In order to delete the group information registered in the lookup service, all genie services registered in the group are notified, and when all the services leave, the group information is deleted from the lookup service (1, 4). These service group exit events carry relevant event information when requested by the Genie adapter (2-3). The Genie adapter goes through a process of changing the status information of the service to the unavailable state for all services included in the group that has been left out through the registration agent (5-8).

(G) Exit of Lookup Service

If the lookup service exit does not function as a lookup service, the service registered in the lookup service is no longer available. Therefore, it is necessary to handle the event associated with it (see FIG. 11).

If the lookup service no longer functions, it informs all devices and stops the lookup service function when a response is received (1-3). The Genie adapter receives the notification message and changes the state of the service for all services related to the lookup service (4-7).

(H) Genie service exit

Genie service exit refers to the case when the service registered in the lookup service is no longer provided. The exit of the Genie service can be divided into two types. The exiting service can be divided into a case in which the exiting service notifies the lookup service and stops the service function and the case in which the service is stopped due to a problem in the device. In the former case, the relevant event information is registered in the lookup service, but in the latter case, the event is processed using the lease time.

When the Genie service exits normally (see FIG. 12), the exit event is notified to the lookup service (1), and the Genie adapter receives the related event from the lookup service (2-3). The service state information is changed to the unavailable state for the service related to the event (4-7).

If the Genie service is abnormally exited (see FIG. 13), a Lease event that increases the service providing time does not occur in the device. The lookup service knows that there is an exited service at the time of the lease time, and obtains event information from the lookup service to process an event for the exited service (1-2). The Genie adapter then changes the status information for the exited service to unavailable (3-6).

3 <Web service client discovery and use of Genie service>

The Genie adapter will reflect all events in the registry. The web service client discovers and uses a service in the flow shown in FIG. 14.

The web service client discovers the service through a query agent to discover the service (1-4). In the case of web services, the service is used immediately. However, for the services provided by the Genie system, the service status information is retrieved from the device / service registry (7-10). The web service client uses the service by calling a virtual web service to use the service by reflecting the status information (11-12).

(II) Genie Clients Discover and Use Web Services

The Genie system uses a multicast message to find a lookup service. The Gini client finds the service by calling the Lookup () method from the found lookup service using the ServiceRegistrar object. In order to find a service, a service template (ServiceTemplate) is used. The service template includes a ServiceID, a ServiceType, and an AttributeSetTemplate, and a service is searched using a ServiceType.

Table 3 shows the mapping relationship between each other to search web services using messages for discovering and using Genie services in the Genie system.

The Genie system uses the ServiceID, ServiceType, and AttributeSetTemplate to find a service in the lookup service. Among these informations, a service is searched using ServiceType. In the present invention, a web service is searched using a ServiceType to search for a web service. This makes it possible to discover web services without converting them to Genie services.

The Genie client receives the ServiceID, ServiceName, Endpoint, and Service Interface from the lookup service. The web service information mapped to this is shown in Table 4.

The Genie adapter receives the Genie client's interface to call the web service's UUID, business service name, adapter address, and generic web service within the routing proxy. Genie client calls Generic Web Service through interface and binds with Web service.

1 <Generic Web Service>

Generic web services reside in routing proxies. Generic web service is a service that can use all web services. As shown in FIG. 15, the Genie client uses the web service through an interface capable of calling a Generic web service from the Genie adapter.

2 <The process by which Genie client discovers and uses web services>

In the present invention, the lookup service is extended to utilize a wsLookup () method to call a query agent to retrieve a service registered in UDDI.

When a Genie client discovers and uses a web service, the process is performed as shown in FIG. 16.

When the Genie client requests the service to the lookup service, the Genie client searches the UDDI and the device / service registry using the ServiceType (3-8). The Genie client calls the Web service to the Genie adapter to use the web service and uses the web service through the Generic web service in the Routing Proxy (11-14).

Comparing the present invention with the prior art is as follows.

In the present invention, the adapter processes the events occurring in the Genie system and utilizes them in the search. Through this, in discovering and using the Genie service in the web service client, service information may be provided by using service state information and location information.

In discovering and using web services in Genie clients, the lookup service is extended to search UDDI to discover web services. In using web services, web services are used using generic web services.

When comparing GOAL and Genie adapters, the following points can be compared.

(1) Comparison of Genie Service Search and Usage of Web Service Clients

When the GOAL and Genie adapters are used by the web service client to discover and use the Genie service, the service search, event information, and web service creation time are compared with each other.

Both systems can search for the same service, but the Genie adapter can use the event information to receive the service. This enables the retrieval of currently available information. In addition, new Web Genie service can be searched by creating web service at Run Time.

(2) Web service search and use comparison of Genie client

Table 6 shows the comparison between the service search, the search target, the service conversion, and the newly discovered web service search between the client and the GOAL and the Genie adapter.

Both systems can search the web service in the same way, but GOAL is the lookup service while the search target is the other, while Genie adapter uses UDDI. Genie adapters make it possible to search for emerging Web services. Also, according to the difference of search targets, GOAL has to create 1: 1 as a service having all web services. However, Genie adapter can use service without service conversion by utilizing Generic web service.

1 is a block diagram illustrating an exemplary structure of a Genie system.

Figure 2 is a conceptual diagram showing the components and the interrelationship of the GOAL system known in the prior art.

3 is a block diagram illustrating an example of a function performed by an apparatus of the present invention.

4 is a block diagram (A) showing an exemplary structure of an apparatus according to the present invention, and an example of the interrelationship between an adapter and a lookup service, a UDDI, a web service and a genie service in the apparatus and method according to the present invention. (B).

5 is a flowchart illustrating a hook-up process of a service in an apparatus and method according to the present invention.

6 is a flow chart showing a Genie service appearance process in the apparatus and method according to the present invention.

7 is a flowchart illustrating a process of changing service state information in an apparatus and method according to the present invention.

8 is a flowchart illustrating a process of changing service description information in an apparatus and method according to the present invention.

9 is a flowchart illustrating a process of registering genie service group information in an apparatus and method according to the present invention.

10 is a flowchart illustrating a process of deleting genie service group information in an apparatus and method according to the present invention.

11 is a flowchart illustrating an exit process of a lookup service in an apparatus and a method according to the present invention.

12 is a flowchart illustrating a normal exit process of the Genie service in the apparatus and method according to the present invention.

13 is a flow chart showing an abnormal exit process of the Genie service in the apparatus and method according to the present invention.

14 is a flowchart illustrating a process of a web service client discovering and using a Genie service in an apparatus and method according to the present invention.

15 is a block diagram showing the operation of a generic web service in the device and method according to the present invention.

16 is a flowchart illustrating a process of a Genie client discovering and using a web service in the apparatus and method according to the present invention.

Claims (2)

An apparatus for interworking between a Jini service and a web service including a lookup service, an adapter, a registration agent, a query agent, a device / service registry, a context registry, and a UDDI, (A) the lookup service retrieves Jini devices and services present in the network and stores their metadata information and event information; (B) The adapter, ① requests the source file associated with the Genie service to the lookup service, receives and delivers it to the registration agent, ② generates a web service for the Genie service, and registers the service information of the generated web service as a registration agent. To; (C) the registration agent registers specification information and dynamic state information of the Genie service among the source files received from the adapter in the UDDI, device / service registry, and context registry, respectively; (E) The query agent determines whether the service stored by the lookup service is already registered in the device / service registry and the context registry, and transmits the information to the adapter (the service of the already registered service). Preventing duplicate registrations; Apparatus for interworking between Jini services and Web services, characterized in that. In the interworking method between the Jini service and the web service using the device according to claim 1, (A) Hook-up process consisting of the following steps Ⓐ the lookup service searches for Jini devices and services existing in the network and stores their metadata information and event information The adapter acquiring information about the Jini device or service registered in the lookup service by searching for the lookup service; Ⓒ generating, by the adapter, a virtual web service in the adapter and transmitting meta information of the retrieved Jini device or service to a registration agent; The registration agent registers the meta information in the device / service registry and context registry, respectively: (B) Genie service appearance process consisting of the following steps Ⓐ the lookup service searches for Jini devices and services existing in the network and stores their metadata information and event information When an event occurs, the lookup service delivers event information to the adapter. Ⓒ checking by the query agent whether the service where the event has occurred is already registered; If a service is already registered, switching the state of the service to the "available" state in the context registry Ⓔ If the service is new, the adapter requests and obtains information about the service from a lookup service. Create a virtual web service for the service and store it in the adapter; When the related meta information is transmitted to a registration agent, the registration agent registering the meta information in a device / service registry and a context registry, respectively: (C) Service status information change process consisting of the following steps Ⓐ the lookup service searches for a Jini device and a service existing in a network and stores information on a state information change event; The lookup service forwarding event information to the adapter; When the event information is transmitted to the registration agent, the registration agent changes and registers state information on the service in which the event occurred in the device / service registry: (D) Service technology information change process consisting of the following steps Ⓐ the lookup service searches for Jini devices and services existing in the network and stores the information on which the technology information change event has occurred; The lookup service forwarding event information to the adapter; When the event information is transmitted to the registration agent, the registration agent changes and registers the technical information on the service in which the event occurred in the device / service registry and the context registry: (E) Service group information registration process consisting of the following steps Ⓐ the lookup service receives a new genie service group The lookup service forwarding event information to the adapter; Ⓒ checking by the query agent whether the service where the event has occurred is already registered; If a service is already registered, switching the state of the service to the "available" state in the context registry Ⓔ If the service is new, the adapter requests and obtains information about the service from a lookup service. Create a virtual web service for the service and store it in the adapter; When the related meta information is transmitted to a registration agent, the registration agent registering the meta information in a device / service registry and a context registry, respectively: (F) Process of deleting service group information consisting of the following steps Ⓐ the step of receiving, by the lookup service, information for deleting a genie service group The lookup service forwarding event information to the adapter; When the event information is transmitted to the registration agent, the registration agent changes and registers state information on the service group in which the event is stored in the device / service registry: (G) the lookup service exit process consisting of the following steps: Ⓐ the lookup service stops the lookup service function for all Genie devices registered in the lookup service The lookup service forwarding event information to the adapter; When the event information is transmitted to the registration agent, the registration agent changes and registers state information on all Genie devices in which the event is stored in the device / service registry: (G) Genie service exit process consisting of the following steps: Ⓐ wherein the lookup service inquires whether Jini devices are available for service at a predetermined time interval; Ⓑ For a device that does not reply to the service availability query for a predetermined time or has a connection termination (Bye) message, If the lookup service delivers event information to the adapter, and the registration agent delivers the event information to a registration agent, Registering, by the registration agent, changing state information of the device registered in the device / service registry to a "unavailable" state: Interworking method between Jini services and web services, characterized in that it comprises a.

Images