JP2006092167A - Service provision device, semantic relation service provision device, service provision program, semantic relation service provision program, recording medium, service provision method and semantic relation service provision method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily and promptly call service on a calling side even if the service on the calling side is changed or updated. <P>SOLUTION: This service provision device has a service provision means 20 providing the service. The service provision means 20 has: a connector generation means 53 generating a connector of two different interfaces related to the service from semantic relation data wherein semantic relation between the two different interfaces related to the service is defined; a stub generation means 56 generating a stub related to the service to be called, from data described with information related to the service called by the service provision means; and a service calling means 51 calling the service to be called. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a service providing apparatus, a semantic relation service providing apparatus, a service provision program, a semantic relation service provision program, a recording medium, a service provision method, and a semantic relation service provision method.

  An example of conventional problems is shown in FIG. FIG. 1 is a diagram (part 1) illustrating a conventional problem.

  In FIG. 1, an existing system exists, an application included in the system uses an external service, and the external service uses a base service (authentication service in FIG. 1) corresponding to the application. For example, an example required for an application is shown. That is, when the application B uses the service 1 that is an external service, the service 1 is required to perform authentication using the authentication service B.

  In the configuration shown in FIG. 1, when there is a replacement of a base service or a version update of the base service, for example, without changing the creation or setting of each external service, There has been a problem that, for example, messages cannot be transmitted / received because the updated base service is connected as before. In addition to the authentication service, the base service includes a log service for collecting logs, a management service for managing data, and a directory service for providing a directory.

  A conventional solution for solving the above-described problem is shown in FIG. FIG. 2 is a diagram showing a conventional solution.

  As shown in FIG. 2, a dispatcher is provided, and for example, the dispatcher calls (distributes) a new base service (authentication service in the example of FIG. 2) corresponding to the change or change in response to a call from an external service. Alternatively, for example, a message for the old base service before replacement or change may be changed to a message for the new base service after replacement or change by a dispatcher. By adopting the configuration as shown in FIG. 2 and the method as described above, there is no need to change the creation and setting of each external service.

  However, even in the configuration and method shown in FIG. 2, there is a problem that the creation and setting of the dispatcher must be changed depending on the replacement of the base service or the update of the version of the base service. There is also a problem that a dispatcher that executes the processing as described above must be created and installed. For example, it is often troublesome to create and set up to decrypt and sort a message that has been signed or encrypted, or to change it to a new message. In addition, since processing is performed via a single service called a dispatcher, there is a problem that performance such as processing speed falls.

  Hereinafter, another example of conventional problems is shown in FIG. FIG. 3 is a diagram (part 2) illustrating a conventional problem.

  As shown in FIG. 3, when there is an orchestration service that provides a plurality of services together, for example, to a client, etc., for example, when the contents of a plurality of services are changed or a combination of a plurality of services is changed There was a problem that the connection between services was not guaranteed. For example, in the conventional technique, if the service 3 is changed to the service 4, the service 4 is called up without changing the creation and setting of the service 1 and the service 2. There was a problem that could not be called.

  The present invention has been made in view of the above points, and an object of the present invention is to call a caller's service easily and quickly even if the caller's service is changed or updated.

  In order to solve the above problems, the present invention provides a service providing apparatus having a service providing means for providing a service, wherein the service providing means defines a semantic relationship between two different interfaces related to a service. A stub for generating a stub for the service to be called from data in which information on the service to be called by the service providing means and a connector generation unit for generating a connector of two different interfaces related to the service is described from the semantic relation data. It has a generation means and a service call means for calling the service to be called.

  According to the present invention, there is provided a service providing apparatus having service providing means for providing a service, wherein the service providing means uses the semantic relation data defining a semantic relation between two different interfaces related to the service. Connector generating means for generating connectors of two different interfaces according to the above, stub generating means for generating a stub related to the service to be called from data describing information related to the service to be called by the service providing means, and the service to be called And the service calling means for calling, even if the calling service is changed or updated, the calling service can be called easily and quickly.

  Further, as means for solving the above problems, a semantic relation service providing apparatus, a service provision program, a semantic relation service provision program, a recording medium, a service provision method, and a semantic relation service provision method may be used.

  The service providing means described in the claims corresponds to, for example, a service (external service) 20 or a dispatcher 110 described later. Moreover, the connector production | generation means as described in a claim respond | corresponds to the connector production | generation part 53 mentioned later, for example. The stub generation means described in the claims corresponds to, for example, a Web service stub generation unit 56 described later. Further, the service calling means described in the claims corresponds to, for example, a Web service calling unit 51 described later. The semantic relationship data described in the claims corresponds to, for example, a semantic relationship file 90 described later. Further, data in which information related to the service to be called described in the claims is described corresponds to, for example, the WSDL 100 of the Web service 30 described later. Further, data relating to the meaning of the interface related to the service described in the claims corresponds to, for example, a semantic file 85 described later.

  The connector registration means described in the claims corresponds to, for example, a connector registration unit 54 described later. The connector storage means described in the claims corresponds to, for example, a connector storage unit 55 described later. The stub registration means described in the claims corresponds to, for example, a Web service stub registration unit 57 described later. The stub storage means described in the claims corresponds to, for example, a Web service stub storage unit 58 described later. The connector described in the claims corresponds to, for example, a connector 21 described later. Further, the stub described in the claims corresponds to, for example, a Web service stub 22 described later.

  The semantic relation service providing means described in the claims corresponds to, for example, a semantic service 32 described later. Moreover, the meaning analysis means described in the claims corresponds to, for example, a semantic analysis unit 72 described later. The message processing means described in the claims corresponds to, for example, a message processing unit 74 described later. The semantic relation data storage means described in the claims corresponds to, for example, a semantic relation file storage unit 73 described later. Moreover, the meaning data storage means described in the claims corresponds to, for example, a meaning file storage unit 71 described later.

  According to the present invention, even if the caller service is changed or updated, the caller service can be called easily and quickly.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 4 shows an example of the hardware configuration of the service device 1 in which at least one or more services (external services) 20 according to the present invention to be described later are mounted. FIG. 4 is a hardware configuration diagram of an example of the service device.

  As shown in FIG. 4, the service device 1 includes a drive device 13, a ROM 15, a RAM 16, a CPU 17, an interface device 18, and an HDD 19.

  The interface device 18 is an interface that connects the service device 1 to a network or the like.

  A program corresponding to the service (external service) 20 (hereinafter referred to as a service program) or the like is provided to the service device 1 by a recording medium 14 such as a CD-ROM or downloaded through a network. The recording medium 14 is set in the drive device 13, and the service program is installed from the recording medium 14 to the HDD 19 via the drive device 13.

  The ROM 15 stores data and the like. The RAM 16 reads and stores a service program and the like from the HDD 19 when the service device 1 is activated. The CPU 17 executes processing according to a service program read and stored in the RAM 16.

  The HDD 19 stores a service program, a connector 21, a web service stub 22, data, and the like which will be described later. The connector 21 and the web service stub 22 may be stored in the RAM 16 instead of the HDD 19.

  FIG. 5 shows an example of the hardware configuration of the semantic relation service device 2 in which a semantic service (semantic analysis service) 32 according to the present invention to be described later is mounted. FIG. 5 is a hardware configuration diagram of an example of the semantic relationship service apparatus.

  As shown in FIG. 5, the semantic relationship service device 2 includes a drive device 113, a ROM 115, a RAM 116, a CPU 117, an interface device 118, and an HDD 119.

  The interface device 118 is an interface that connects the semantic service device 2 to a network or the like.

  A program corresponding to the semantic service (semantic analysis service) 32 (hereinafter referred to as a semantic analysis service program) or the like is provided to the semantic service device 2 by a recording medium 114 such as a CD-ROM, or downloaded through a network. . The recording medium 114 is set in the drive device 113, and the semantic analysis service program is installed from the recording medium 114 to the HDD 119 via the drive device 113.

  The ROM 115 stores data and the like. The RAM 116 reads a semantic analysis service program or the like from the HDD 119 and stores it when the semantic relation service device 2 is activated. The CPU 117 executes processing in accordance with the semantic analysis service program read and stored in the RAM 116.

  The HDD 119 stores a semantic analysis service program, a semantic file 51 described later, a semantic relation file 63, data, and the like. The semantic file 51 and the semantic relation file 63 may be stored in the RAM 116 instead of the HDD 199.

  4 and 5 show examples in which the service 20 and the semantic service 32 are implemented in the service device 1 and the semantic relationship service device 2, respectively. However, the service 20 and the semantic service 32 are , May be included in the same device (service device 1 or semantic relationship service device 2). However, for the sake of simplification of description, the service 20 is implemented in the service device 1 and the semantic service 32 is implemented in the semantic relationship service device 2 unless otherwise specified.

  An example of the service 20 that solves the conventional problems is shown in FIG. FIG. 6 is a diagram (part 1) illustrating the service 20. In the following description, it is assumed that the system configuration shown in the first embodiment is the system configuration shown in FIG. 1 or FIG.

  As shown in FIG. 6, the service (external service) 20 includes a client implementation 23, a primitive I / F 24, a connector 21, and a web service stub 22.

  Here, the connector 21 connects the Primitive I / F 24 and the Web service I / F 35, and means that the semantic relationship between the Primitive I / F 24 and the Web service I / F 35 is described. It is automatically generated from the relation file 90. The semantic relation file 90 includes a semantic file 85 describing the meaning of the Primitive I / F 24 (or Client Implementation 23) and a semantic file 85 describing the meaning of the Web service I / F 35 (or the Web service 30). Based on.

  A Web service stub 22 that is an intermediary when the service 20 calls the Web service 30 is automatically generated from a WSDL (Web Services Description Language) file (hereinafter simply referred to as WSDL) 100 of the Web service 30 to be called. .

  The client implementation 23 is a service providing function implementation unit that implements a service providing function as the service 20.

  Primitive I / F 24 is an I / F provided by Client Implementation 23.

  The web service I / F 35 is an I / F of the web service 30.

  As shown in FIG. 6, the connector 21 is generated from the semantic relationship file 90 between the Primitive I / F 24 and the Web service I / F 35, and the Web service stub 22 is generated from the WSDL 100 of the Web service 30 to be called. As a result, even if the call destination Web service 30 (or Web service I / F 35) is changed or updated, the service 20 can easily and quickly perform the Web without re-creating the service 20, for example, recompiling. Service 30 can be invoked.

  FIG. 7 shows another example of the service 20 that solves the conventional problems. FIG. 7 is a diagram (part 2) illustrating a service.

  The service 20 shown in FIG. 7 includes a plurality of connectors 21 and Web service stubs 22 as compared to the service 20 shown in FIG. By adopting the configuration as shown in FIG. 7, even if a plurality of Web service 30 (or Web service I / F 35) as a call destination is changed or updated from one implementation (Client Implementation 23), the service 20 is changed. A plurality of Web services 30 can be called easily and quickly without re-creating, for example, recompiling.

  An example of the functional configuration of the service 20 is shown in FIG. FIG. 8 is a diagram illustrating an example of a functional configuration of a service.

  As shown in FIG. 8, the service 20 includes a web service I / F 52, a client implementation 23, a primitive I / F 24, a connector generation unit 53, a connector registration unit 54, a connector storage unit 55, a web service stub. A generation unit 56, a web service stub registration unit 57, a web service stub storage unit 58, and a web service call unit 51 are included.

  The web service I / F 52 is an I / F of the service 20.

  The connector generation unit 53 generates the connector 21 from the semantic relationship file 90. The connector registration unit 53 stores the connector 21 generated by the connector generation unit 53 in the connector storage unit 55. The connector storage unit 55 stores at least one or more connectors 21.

  The Web service stub generation unit 56 generates the Web service stub 22 from the WSDL 100 of the call destination (Web service 30). The Web service stub registration unit 57 stores the Web service stub 22 generated by the Web service stub generation unit 56 in the Web service stub storage unit 58. The web service stub storage unit 58 stores at least one web service stub 22.

  The web service calling unit 51 is called from the web service stub 22 and calls the web service 30 or the like.

  An example in which the connector 21 is automatically generated is shown in FIG. FIG. 9 is a conceptual diagram illustrating an example in which a connector is automatically generated.

  As illustrated in FIG. 9, the connector generation unit 53 automatically generates the connector 21 based on a semantic relationship file 90 that defines a semantic relationship between, for example, the Web service I / F 35 and the Primitive I / F 24. To do. As shown in FIG. 9, the connector 21 bridges two I / Fs.

  Hereinafter, an example of generation of the connector 21 and the Web service stub 22 is shown in FIG. FIG. 10 is a diagram (part 1) illustrating generation of a connector and a web service stub. In the example shown below, the application or orchestration service 40 or the like creates the semantic relation file 90, and the external service (service) 20 is based on the semantic relation file 90 created by the application or orchestration service 40 or the like. This is an example of generating the connector 21 and the like.

  First, the application or orchestration service 40 (hereinafter also simply referred to as the application 40) acquires the Primitive I / F 24 of the external service (service) 20 ((1) in FIG. 10). Actually, it is only necessary to acquire I / F information (information related to the I / F) instead of the I / F. However, in the following, for simplification of description, it is described that the I / F is acquired.

  Next, the application 40 acquires an I / F (Web service I / F 35) of a Web service (the authentication service 31 in the example of FIG. 10) that the external service (service) 20 may call directly (FIG. 10). 10 (2)).

  Subsequently, the application 40 determines the semantic relationship between the I / Fs based on the Primitive I / F 24 of the external service (service) 20 acquired in (1) and the Web service I / F 35 acquired in (2). A file 90 is created ((3) in FIG. 10).

  Next, the application 40 transmits the created semantic relationship file 90 to the external service (service) 20 ((4) in FIG. 10).

  The connector generation unit 53 of the external service (service) 20 generates the connector 21 from the acquired semantic relationship file 90, and the Web service stub generation unit 56 selects the Web service to be called (the authentication service 31 in the example of FIG. 10). A Web service stub 22 is generated from the WSDL 100 ((5) in FIG. 10).

  Hereinafter, another example of the generation of the connector 21 and the Web service stub 22 is shown in FIG. FIG. 11 is a diagram (part 2) illustrating the generation of the connector and the web service stub. In the example shown below, the semantic service 32 creates the semantic relation file 90, and the external service (service) 20 creates the connector 21 and the like based on the semantic relation file 90 created by the semantic service 32. It is.

  First, when the external service (service) 20 is introduced, the introducer of the external service (service) 20 creates the semantic file 85 of the external service (service) 20 (I / F of the external service (service) 20) and the semantics service 32. ((1) in FIG. 11). It is to be noted that the external service (service) 20 itself, not the external service (service) 20 introducer, sets the semantic file 85 of its own (its own I / F) to the semantics service 32 at the time of introduction (or at the time of start-up). You may make it register.

  Further, when the application 40 is installed, the introducer of the application 40 registers the semantic file 85 of the authentication service 31 (I / F of the authentication service 31) in the semantic service 32 ((2) in FIG. 11). Note that the semantic file 85 of the authentication service 31 (I / F of the authentication service 31) used by the application 40 itself, not the introduction of the application 40, at the time of introduction (or at the time of activation) is stored in the semantics service 32. You may make it register.

  Next, the application 40 is a system that the application 40 wants to use or the external service (service) 20 uses when the application 40 is introduced (or activated). For example, the WSDL of the authentication service 31 and the WSDL of the semantic service 32 are passed ((3) in FIG. 11).

  The external service (service) 20 that has received the information from the application 40 sends the semantic service 32 the Web service I / F 35 of the service to be used (the authentication service 31 in the example of FIG. 11), the Primitive I / F 24 of the service, Is inquired about the meaning relation file 90 ((4) of FIG. 11).

  Upon receiving an inquiry from the external service (service) 20, the semantics service 32 returns the semantic relation file 90 to the requesting external service (service) 20 ((5) in FIG. 11). When the semantic service 32 receives the inquiry in (4), the semantic service file 90 is based on the semantic file registered in (1) and the semantic file registered in (2). Alternatively, when the meaning file is registered in (1) and (2), the semantic relationship file 90 may be created based on the meaning file.

  The connector generation unit 53 of the external service (service) 20 generates the connector 21 from the acquired semantic relationship file 90, and the Web service stub generation unit 56 selects the Web service to be called (the authentication service 31 in the example of FIG. 11). A Web service stub 22 is generated from the WSDL 100 ((6) in FIG. 11).

  The semantic service 32 is configured as shown in FIG. 12 to be described later, and by executing the processing shown in FIG. 11 described above, the service 20 acquires the semantic relation file 90 and automatically generates the connector 21. can do. In addition, the service 20 automatically generates the Web service stub 22 from the WSDL 100 of the Web service to be called, so that even if the service (or service I / F) on the call side is changed or updated, the service (Web service) to be called is called. Can be called easily and quickly.

  An example of the functional configuration of the semantic service 32 is shown in FIG. FIG. 12 is a diagram illustrating an example of a functional configuration of the semantic service.

  As shown in FIG. 12, the semantic service 32 includes a Web service I / F 70, a semantic file storage unit 71, a semantic analysis unit 72, a semantic relation file storage unit 73, and a message processing unit 74.

  The web service I / F 70 is an I / F of the semantic service 32. The meaning file storage unit 71 stores a plurality of meaning files 85. The semantic analysis unit 72 performs semantic analysis based on the plurality of semantic files 85 stored in the semantic file storage unit 71 and creates a semantic relation file 90. The semantic relationship file storage unit 73 stores at least one semantic relationship file 90. The message processing unit 74 is a processing unit that performs processing in response to a message from the service 20, for example.

  For example, the message processing unit 74 stores or deletes the semantic file 85 in the semantic file storage unit 71, and stores or deletes the semantic relationship file 90 in the semantic relationship file storage unit 73. Further, the message processing unit 74 inquires of the semantic relationship file 90 to the semantic relationship file storage unit 73 in response to the message, and if there is no semantic relationship file 90 corresponding to the message, the semantic file storage unit 71 performs the meaning. The file 85 is acquired and passed to the semantic analysis unit 72 to request creation of the semantic relationship file 90, and the created semantic relationship file 90 is stored in the semantic relationship file storage unit 73. In addition, when the semantic analysis unit 72 cannot create the semantic relation file 90, the message processing unit 74 creates an error message and returns it to the service 20 or the like. Further, when the semantic file 85 is updated, the message processing unit 74 updates the related semantic relationship file 90.

  An example of a message in the Web service I / F 35 is shown in FIG. FIG. 13 is a diagram illustrating an example of a message in the Web service I / F.

  The example shown in FIG. 13 is an example of a message in the I / F of the authentication service 31, and a user ID, a password, and the like are stored in predetermined tags, respectively.

  An example of the semantic file 85 of the Web service I / F 35 is shown in FIG. FIG. 14 is a diagram illustrating an example of a semantic file of the Web service I / F.

  As shown in FIG. 14, the meaning file 85 describes the meaning of the Web service I / F 35 (or a message in the Web service I / F 35).

  An example of generation of the semantic relationship file 90 is shown in FIG. FIG. 15 is a conceptual diagram of generation of a semantic relationship file.

  As shown in FIG. 15, the semantic analysis unit 72 extracts a common concept (common configuration or information) from a plurality of semantic files 85, performs semantic analysis of the common concept, and generates a semantic relation file 90. .

  Hereinafter, an operation example of the service 20 in the case of synchronization is shown in FIG. FIG. 16 is a flow (part 1) illustrating an example of service operation.

  In step S10, the service 20 receives a request message from the application 40 or the like via the Web service I / F 52.

  In step S11 following step S10, it is necessary to call, for example, another service (another web service) in the client implementation 23 of the service 20.

  Progressing to step S12 following step S11, the web service stub registration unit 57 selects the web service stub 22 to be called from the web service stub storage unit 58 based on the message received from the client implementation 23 via the primitive I / F 24. To do.

  Progressing to step S13 following step S12, the parameter set (included) in the message is passed from the primitive I / F 24 to the web service stub 22 selected in the web service stub registration unit 57.

  Progressing to step S14 following step S13, the message (request message) created by the web service stub 22 including the parameters is transmitted to another service (other web service) via the web service calling unit 51. .

  In step S15 following step S14, the service 20 is generated by the web service stub 22 of the other service (other web service) from the other service (other web service) via the web service calling unit 51. Receive a message (response message).

  In step S16 following step S15, the web service stub registration unit 57 passes the received message to the corresponding web service stub 22.

  Progressing to step S17 following step S16, the web service stub 22 converts the message passed from the web service stub registration unit 57 into a parameter and passes it to the primitive I / F 24.

  Proceeding to step S18 following step S17, the client implementation 23 executes parameter reception processing via the primitive I / F 24.

  Following step S18, based on step S19, the client implementation 23 executes the service providing function of the service 20 based on the received parameters, and sends a response message including the execution result via the web service I / F 52. To the application 40 or the like.

  Hereinafter, an operation example of the service 20 in an asynchronous case is shown in FIG. FIG. 17 is a flowchart (part 2) illustrating an operation example of the service.

  In step S30, the service 20 receives a request message from the application 40 or the like via the Web service I / F 52.

  In step S31 following step S30, the client implementation 23 of the service 20 needs to call, for example, another service (other web service).

  Progressing to step S32 following step S31, the web service stub registration unit 57 selects the web service stub 22 to be called from the web service stub storage unit 58 based on the message received from the client implementation 23 via the Primitive I / F 24. To do.

  Progressing to step S33 following step S32, the parameter set (included) in the message is passed from the primitive I / F 24 to the web service stub 22 selected in the web service stub registration unit 57.

  Progressing to step S34 following step S33, the message (request message) created by the web service stub 22 including the parameters is transmitted to another service (other web service) via the web service calling unit 51. .

  In step S40, the service 20 sends a message (from the other service (other web service) to the other service (other web service) by the web service stub 22 via the web service calling unit 51. Response message). The message is a message (response message) corresponding to the message (request message) transmitted in step S34.

  In step S41 following step S40, the web service stub registration unit 57 selects the web service stub 22 to be called from the web service stub storage unit 58 from the received message.

  Proceeding to step S42 following step S41, the web service stub registration unit 57 passes the received message to the corresponding web service stub 22.

  Proceeding to step S43 following step S42, the web service stub 22 converts the message passed from the web service stub registration unit 57 into a parameter, and passes it to the Primitive I / F 24.

  Proceeding to step S44 following step S43, the client implementation 23 performs parameter reception processing via the primitive I / F 24.

  Following step S45, based on step S46, the client implementation 23 executes the service providing function of the service 20 based on the received parameter, and sends a response message including the execution result via the web service I / F 52. To the application 40 or the like.

  Hereinafter, an example in which the connector 21 and the like are separated from each service 20 shown in the first embodiment to form the dispatcher 110 will be described in the second embodiment. FIG. 18 is a system configuration diagram according to the second embodiment.

  The dispatcher 110 shown in FIG. 18 is obtained by separating the connector 21 of the service 20, the web service stub 22 and the like from the service 20 as shown in FIG. Dispatch between a plurality of authentication services 31.

  An example of the dispatcher 110 is shown in FIG. FIG. 19 is an example of a dispatcher.

  As shown in FIG. 19, the dispatcher 110 includes a Primitive I / F 24, a connector 21, a Web service stub 22, and a Primitive I / F proxy 26.

As shown in FIG. 19, semantic relations file 90 includes, for example, a mean file 80 ₁ Client Implementation20 (Primitive I / F24) , and means file ₈₀₂ for the Web Service 30 (Web Service I / F 35) from the product The connector 21 is automatically generated from the semantic relationship file 90.

Also, Web service stub 22 is automatically generated from WSDL100 ₂ Web services 30 to which the dispatcher 110 calls, Primitive I / F26 Client Implementation20 is intermediary for calling a dispatcher 110, Client Implementation20 calling the dispatcher 110 automatically generated from the WSDL100 _1.

As shown in FIG. 19, the connector 21 is generated from the semantic relationship file 90 between the Primitive I / F 24 and the Web service I / F 35, and the Web service 30 is called from the WSDL 100 _{2 of the} Web service 30 called by the dispatcher 110. generates stub 22, from WSDL100 ₁ of Client Implementation20 calling the dispatcher 110, by generating a Primitive I / F proxy 26, the dispatcher 110, the callee Web service 30 (or Web service I / F 35), Even if it is changed or updated, the web service 30 can be called easily and quickly without re-creating the dispatcher 110 or the service 20, for example, recompiling. It can be.

  Hereinafter, an example of functional configurations of the service 20 and the dispatcher 110 is shown in FIG. FIG. 20 is a diagram illustrating an example of a functional configuration of a service and a dispatcher.

  As illustrated in FIG. 20, the service 20 includes a Web service I / F 52, a Client Implementation 23, and a Primitive I / F 24.

  Also, as shown in FIG. 20, the dispatcher 110 includes a Primitive I / F 24, a Web service calling unit 51, a connector generation unit 53, a connector registration unit 54, a connector storage unit 55, and a Web service stub generation unit. 56, a Web service stub registration unit 57, a Web service stub storage unit 58, a Primitive I / F proxy generation unit 59, a Primitive I / F proxy registration unit 60, and a Primitive I / F proxy storage unit 61. Including.

  The Primitive I / F proxy generation unit 59 generates the Primitive I / F proxy 26 from the WSDL 100 of the caller (Client Implementation 20). The Primitive I / F proxy registration unit 60 stores the Primitive I / F proxy 26 generated by the Primitive I / F proxy generation unit 59 in the Primitive I / F proxy storage unit 61. The Primitive I / F proxy storage unit 61 stores the Primitive I / F proxy 26.

  The dispatcher 110 shown in the second embodiment is mounted on a device having the same hardware configuration as the service device 1 shown in the first embodiment, for example, and the CPU of the device performs processing according to a program corresponding to the dispatcher 110. Execute.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

It is FIG. (1) which shows a conventional problem. It is a figure which shows the conventional solution. It is FIG. (2) which shows a conventional problem. It is a hardware block diagram of an example of a service apparatus. It is a hardware block diagram of an example of a semantic relationship service apparatus. It is FIG. (1) which shows a service. It is a figure (the 2) which shows a service. It is a figure which shows an example of the function structure of a service. It is a conceptual diagram which shows the example in which a connector is produced | generated automatically. FIG. 6 is a diagram (part 1) illustrating generation of a connector and a web service stub. FIG. 10 is a diagram (part 2) illustrating generation of a connector and a web service stub. It is a figure which shows an example of a function structure of a semantic service. It is a figure which shows an example of the message in Web service I / F. It is a figure which shows an example of the semantic file of Web service I / F. It is a conceptual diagram of generation of a semantic relationship file. It is a flow (the 1) which shows the operation example of a service. It is a flow (the 2) which shows the operation example of a service. FIG. 10 is a system configuration diagram according to the second embodiment. It is an example of a dispatcher. It is a figure which shows an example of a function structure of a service and a dispatcher.

Explanation of symbols

1 Service device 2 Semantic service device 20 Service (external service)
21 Connector 22 Web Service Stub 23 Client Implementation
24 Primitive I / F
26 Primitive I / F Proxy 30 Web Service 31 Authentication Service 32 Semantics Service 35 Web Service I / F
40 applications (or orchestration services)
52 Web Service I / F
53 Connector generation unit 54 Connector registration unit 55 Connector storage unit 56 Web service stub generation unit 57 Web service stub registration unit 58 Web service stub storage unit 59 Primitive I / F proxy generation unit 60 Primitive I / F proxy registration unit 61 Primitive I / F proxy storage unit 70 Web service I / F
71 Semantic file storage unit 72 Semantic analysis unit 73 Semantic relationship file storage unit 74 Message processing unit 85 Semantic file 90 Semantic relationship file 100 WSDL
110 Dispatcher

Claims (23)

A service providing apparatus having service providing means for providing a service,
The service providing means includes:
Connector generating means for generating connectors of two different interfaces related to the service from semantic relationship data defining a semantic relationship between two different interfaces related to the service;
Stub generating means for generating a stub related to the service to be called from data describing information related to the service to be called by the service providing means;
Service calling means for calling the calling service;
A service providing apparatus comprising:   2. The service according to claim 1, wherein the connector generation unit receives the semantic relationship data from an application or service that calls the service providing unit, and generates the connector based on the received semantic relationship data. Providing device.   The connector generation unit receives the semantic relationship data from a semantic relationship service providing unit that provides a service related to a semantic relationship between two different interfaces related to the service, and determines the connector based on the received semantic relationship data. The service providing apparatus according to claim 1, wherein the service providing apparatus is generated.   The said service provision means further has a connector registration means which registers the connector produced | generated by the said connector production | generation means in the connector preservation | save means which preserve | saves this connector, The Claim 1 thru | or 3 characterized by the above-mentioned. Service providing device.   5. The service providing apparatus according to claim 4, wherein the service providing means further includes the connector storage means.   6. The stub registration unit according to claim 1, further comprising: a stub registration unit configured to register the stub generated by the stub generation unit in a stub storage unit that stores the stub. Service providing device.   The service providing apparatus according to claim 6, wherein the service providing unit further includes the stub storage unit.   The service providing apparatus according to claim 1, wherein the service providing unit includes a plurality of the connectors and the stubs. A semantic relationship service providing apparatus having a semantic relationship service providing means for providing a service related to a semantic relationship between two different interfaces related to a service,
The semantic relationship service providing means includes:
Semantic analysis means for analyzing data related to the meaning of the interface related to the service;
Message processing means for executing processing related to transmission / reception of messages, and providing semantic relationship data related to the semantic relationship between two different interfaces related to services to a request source in response to a request;
A semantic relationship service providing apparatus characterized by comprising:   The semantic relation service providing apparatus according to claim 9, wherein the semantic analysis means analyzes data related to a meaning of an interface related to the service and creates the semantic relation data.   11. The semantic relation service providing apparatus according to claim 9 or 10, wherein the semantic relation service providing means further comprises semantic relation data storage means for storing the semantic relation data.   12. The semantic relation service providing apparatus according to claim 9, wherein the semantic relation service providing means further comprises semantic data storage means for storing data related to a meaning of an interface related to a service. Computer
A service providing program that operates as a service providing means for providing a service,
The service providing means includes:
Connector generating means for generating connectors of two different interfaces related to the service from semantic relationship data defining a semantic relationship between two different interfaces related to the service;
Stub generating means for generating a stub related to the service to be called from data describing information related to the service to be called by the service providing means;
Service calling means for calling the calling service;
A service providing program characterized by comprising:   14. The service according to claim 13, wherein the connector generation unit receives the semantic relationship data from an application or service that calls the service providing unit, and generates the connector based on the received semantic relationship data. Offer program.   The connector generation unit receives the semantic relationship data from a semantic relationship service providing unit that provides a service related to a semantic relationship between two different interfaces related to the service, and determines the connector based on the received semantic relationship data. 14. The service providing program according to claim 13, wherein the service providing program is generated.   The said service provision means further has a connector registration means which registers the connector produced | generated by the said connector production | generation means in the connector preservation | save means which preserve | saves this connector, The Claim 13 thru | or 15 characterized by the above-mentioned. Service provision program.   17. The stub registration unit according to claim 13, further comprising: a stub registration unit configured to register the stub generated by the stub generation unit in a stub storage unit that stores the stub. Service provision program. Computer
A semantic relationship service providing program that operates as a semantic relationship service providing means for providing a service related to a semantic relationship between two different interfaces related to a service,
The semantic relationship service providing means includes:
Semantic analysis means for analyzing data related to the meaning of the interface related to the service;
Message processing means for executing processing related to transmission / reception of messages, and providing semantic relationship data related to the semantic relationship between two different interfaces related to services to a request source in response to a request;
A semantic relationship service providing program characterized by comprising:   19. The semantic relation service providing program according to claim 18, wherein the semantic analysis means analyzes data related to a meaning of an interface related to the service and creates the semantic relation data.   A computer-readable recording medium on which the service providing program according to claim 13 is recorded.   A computer-readable recording medium in which the semantic service providing program according to claim 18 or 19 is recorded. A service providing method for providing a service,
A connector generation stage for generating connectors of two different interfaces related to the service from semantic relationship data defining a semantic relationship between two different interfaces related to the service;
A stub generation stage for generating a stub related to the service to be called from data describing information related to the service to be called;
A service invocation step of invoking the invoking service;
A service providing method characterized by comprising: A semantic relationship service providing method for providing a service related to a semantic relationship between two different interfaces related to a service,
A semantic analysis stage for analyzing data related to the meaning of the interface related to the service;
A message processing stage that performs processing related to message transmission and reception, and provides, in response to a request, semantic relationship data related to a semantic relationship between two different interfaces related to a service to a request source;
A semantic relation service providing method characterized by comprising:

Images