CN102769671A - Competition and cooperation-based Web service relation network system - Google Patents
Competition and cooperation-based Web service relation network system Download PDFInfo
- Publication number
- CN102769671A CN102769671A CN2012102472436A CN201210247243A CN102769671A CN 102769671 A CN102769671 A CN 102769671A CN 2012102472436 A CN2012102472436 A CN 2012102472436A CN 201210247243 A CN201210247243 A CN 201210247243A CN 102769671 A CN102769671 A CN 102769671A
- Authority
- CN
- China
- Prior art keywords
- service
- relation
- web service
- type
- web
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to an Internet-based service description and service discovery network system, and aims to realize dynamic, autonomous and competition and cooperation-based service discovery and automatic and semiautomatic service combination. The technical scheme is that: a competition and cooperation-based Web service relation network system comprises a service submission module, a service acquisition module, a service relation mining algorithm module and a service query/display module, wherein the service submission module performs service submission/service information extraction; the service acquisition module transmits a description file of service with semantic information to the Web through the service query/display module; the service relation mining algorithm module is used for mining a relation between service submission and service acquisition to obtain a service relation which is transmitted to the Web through the service query/display module; and a service query function is realized through the service query/display module. The competition and cooperation-based Web service relation network system is mainly applied to the construction of a network service system.
Description
Technical field
The present invention relates to the network system based on the service describing and the service discovery of internet, the information on services organizational form of particularly using based on Web is like registration, management and access mechanism.Specifically, relate to based on the Web service relational network system that competes and cooperate.
Background technology
At present; Web service registration center is type of employing UDDI (Universal Description often; Discovery and Integration) standard; The Web service of using XML (Extensible Markup Language) document to describe enterprise and provide, and the global directory of maintaining webs service.This Web service based on UDDI or its variant is registered model because of lacking the semantic description to concerning between the Web service, has following drawback:
1. only deposit the essential information such as title, field of Web service in the registration table, discovery, the coupling that can only serve based on keyword cause the recall ratio of Web service and precision ratio not high;
2. lack descriptor, cause in the integrated application of service-oriented flow process the Web service semantic attribute, can't be through the semantic attribute characteristic realization service-seeking of Web service;
3. lack descriptor, the classification of service that has more flexibility and availability mechanism can't be provided concerning between Web service;
4. lay particular emphasis on the service discovery algorithm of functional requirement, can't satisfy the requirement of QoS (Quality of Service);
5. lack further support to the Web service Automatic Combined.
At present; Many researchs are devoted to revise the defective of existing UDDI registration model; Such as utilizing ontology to improve recall ratio, utilize Hash table to improve search efficiency, but all fundamentally do not solve the above-mentioned subject matter that current Web service registry model is faced.
Summary of the invention
The present invention is intended to overcome the deficiency of prior art; Realize dynamically, autonomous, based on the service discovery and automatic, the semi-automatic service combination of competition and cooperation; For achieving the above object; The technical scheme that the present invention takes is based on the Web service relational network system of competition and cooperation, to comprise the submission service module, obtain service module, relation excavation algoritic module, service-seeking/display module; The submission service module comprises the information extraction of the submission/service of serving, and by body semantic support is provided, and the Web service relational network is delivered in the information extraction behind the mark; Obtain service module and then the description document of the service that obtains to have semantic information is delivered to the Web network through service-seeking/display module; Obtaining service module also will be according to the composite services that functional description obtained that comprise semantic information, and these composite services also are to deliver to the Web service relational network through service-seeking/display interface; Service relation mining algorithm module is used for submitting to the excavation of serving and obtaining relationship between services to obtain service relation, and the Web network is delivered to by service-seeking/display module in the back; The inquiry service function is accomplished through service-seeking/display module.
Obtaining service module is specially: when the service of realization arrives; The Web service of promptly being described by OWL-S (Ontology Web Language for Services) or WSDL (Web Service Description Language) utilizes OWL-S2SN resolver or WSDL2SN resolver to decompose the interface of service out; For wsdl document, utilize the WSDL2SN resolver to resolve after, generate Web service relational network node, and then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit; For the OWL-S file, after the dissection process through the OWL-S2SN resolver, generate Web service relational network node, and then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit.
The resolver realization flow of WSDL2SN may further comprise the steps:
At first; Read wsdl document in the definition (definition) step 401 through WSDL4J (WSDL for Java) API (Application Programming Interface): from definition, reading and obtaining type (types) definition is DOM (Document Object Model) type; Step 402: in the types definition, make up attribute informations such as NameSpace; And convert this attribute to JDOM (Java Document Object Model) type; Step 403: obtain accomplishing pattern (schema) definition of the type of conversion, step 404: this schema need use when being defined in and resolving in the face of self-defining parameter type;
For the parameter in the wsdl document is the situation of self-defining complicated type, and the pattern (schema) that obtains above needing to use goes to carry out the parsing of complicated type, until customization type is decomposed, obtains a series of simple types; This part flow process may further comprise the steps:
Step 405: at first service (service) element is resolved, obtain binding information, that is: resolve to < wsdl:service>label, find the binding information of binding (binding) back in each < wsdl:port>label;
Step 406: find corresponding port type (portType) information according to binding information, that is: in < wsdl:binding>label, go for the portType attribute, main interface name that this service provided that Here it is;
Step 407: all operations (operation) to being comprised among the portType is resolved; Obtain the base attribute and the parameter information of each operation; That is: in < wsdl:portType>label, go for each operation; < wsdl:operation>each operation is again respectively to there being the input and output of oneself, and each input and output result is respectively a message (message);
Step 408: find corresponding message definition according to parameter information, that is: go for the basic composition of each message in < wsdl:message >, it possibly be made up of simple types and complicated customization type.If simple types, then resolving stops;
The concrete structure of step 409:Message can obtain from the schema that has built; Until message is decomposed into simple types; If that is: the composition of message is complicated customization type; Then need recursively in type definition, to go for definition, be entirely simple types until structure types to this complicated type;
Step 410: bindtype is judged, further be divided into RPC (Remote Procedure Call) type and code-shaped;
Step 411: when bindtype is the RPC type, make up RPC type complex parameters;
Step 412: judge whether constructed RPC type complex parameters is complicated type;
Step 415: obtain complete information on services;
Step 413:, make up the Doctype complex parameters when bindtype when being code-shaped;
Step 414: judge whether constructed Doctype complex parameters is complicated type;
Step 415: obtain complete information on services.
The realization flow figure of OWL-S2SN resolver specifically may further comprise the steps:
Step 501: at first through the URI (Uniform Resource Identifier) of OWL-S, read the OWL-S file, that is: the URI of the OWL-S file that obtains to be resolved reads this document, and reads other ontology file that it is quoted;
Step 502: import other bodies that OWL-S quotes;
Step 503: whether the body that inspection this document is described effectively reaches compliant, promptly whether has contradiction semantically, and whether meets the OWL-S standard;
Step 504:, then parse and form the needed related content of service node in the service network if the check result of above-mentioned body is effective and compliant;
Step 505: be mapped to the standard that meets the service network definition, that is: the result that will resolve is formatted into the form that meets the service network normalized definition;
Step 506: the result is persisted in the service network, and notifies corresponding maintenance program;
Step 507: with update notification service network maintenance process;
Step 508: if the check result of above-mentioned body be invalid or do not meet standard, then export relevant information, and finish operation this time.
The calculation process of the operation-interface relation of service relation mining algorithm module may further comprise the steps:
At first, two operation-interfaces are carried out preliminary treatment; Whether interface name and the descriptor of judging these two operation-interfaces are antisense, if then algorithm flow finishes; If not, then carry out I/O parameter similarity and calculate, the interface similarity is set up then, obtains relationship type and similarity, and algorithm finishes.
Technical characterstic of the present invention and effect:
Compared with prior art, the discovery of the convenient Web service of the present invention, make up, search coupling, and can realize expanding compatible to multiple service semantics descriptive language, use convenient; Available Web service is organized into the service ecosystem (Service ecosystem), by means of the relation between the service improve service combination, search, operation such as maintenance.
Description of drawings
Fig. 1 is the sketch map that forms based on the Web service relational network of competition and cooperation of the present invention;
Fig. 2 is the Web service relational network system schematic based on competition and cooperation of the present invention;
Fig. 3 serves as reasons and realizes the flow chart of service of service construction function and continuous update functions layer;
Fig. 4 is the flow path switch figure to the different describing modes of various Web service mode converters;
Fig. 5 is the realization flow figure that is applicable to the WSDL2SN resolver of wsdl document;
Fig. 6 is the realization flow figure that is applicable to the OWL-S2SN resolver of OWL-S file;
Fig. 7 is the general frame figure based on the Web service relational network system that competes and cooperate of the present invention;
Fig. 8 is that the operation-interface of service relation mining algorithm of the present invention concerns calculation flow chart;
Fig. 9 is a service relation mining algorithm flow chart of the present invention.
Embodiment
In view of the problem that exists in the prior art; The present invention proposes a kind of Web service relational network system based on competition and cooperation; Through concluding again and put in order, convert thereof into rich semantic body form to the data in the existing Web service register center and to various discrete Web service information; Utilize mining algorithm that the relation between Web service is excavated; Web service registration center is organized into one is node with the Web service, be the network system on limit with the relation between service, thereby realize dynamically, autonomous, based on service discovery and (partly) automatic service combination of competition and cooperation.
The present invention proposes a kind of Web service relational network system based on competition and cooperation; With the node of Web service as this network; Relationship between services is as the limit; Specifically be divided into two-layer again: functional layer and realization layer, comprise the function service respectively and realize service, it is characterized in that; This system comprises in service submission system and service discovery system in Web service relational network, this network, this network and produces service combination system and service-seeking/display interface automatically according to functional description (partly), wherein:
The Web service relational network is used to serve automatic discovery, service (partly) Automatic Combined; This Web service relational network the service that will handle derive from the submission service of this network and the service of obtaining of this network; Wherein, Submit to and serve the information extraction that comprises the submission/service of serving, and by body semantic support is provided, the Web service relational network is delivered in the information extraction behind the mark; The service of obtaining is then delivered to the Web service relational network with the description document of the service that obtains to have semantic information through service-seeking/display interface; And according to the composite services that functional description obtained that comprise semantic information, these composite services also are to deliver to the Web service relational network through service-seeking/display interface; The relation that this Web service relational network is had derives from the excavation of submitting service to and obtaining relationship between services, is obtained by the service relation mining algorithm, and the Web service relational network is delivered to by service-seeking/display interface in the back; The inquiry service function that this Web service relational network provides is accomplished through service-seeking/display interface.
Said realization service comprises the Web service of being described by OWL-S and WSDL, can be divided into three kinds according to granule size: seeervice level, interface level and parametric degree.Correspondingly, relation also is divided into three kinds of granularities.Wherein, the parametric degree semantic relation comes from the semantic relation between the Ontological concept that parameter is marked, and the relation of definition has: whole and part relation, object properties relation, inheritance and equivalence relation.The interface level semantic relation is based upon on the parametric degree semantic relation, is divided into competitive relation and cooperation relation, and wherein, competitive relation comprises: equivalence relation, inheritance, grafting relation; Cooperation relation comprises: complete follow-up relation, the follow-up relation of part, complete forerunner's relation and part forerunner relation.The seeervice level semantic relation is based upon on the interface level semantic relation, is divided into competitive relation and cooperation relation equally, and wherein, competitive relation comprises: equivalence relation, inheritance, grafting relation; Cooperation relation comprises: complete follow-up relation, the follow-up relation of part, complete forerunner's relation and part forerunner relation.
Said function service derives from the difference in functionality of the service of realization; Promptly merge the function of the service of realization and extract different functions; Each function service only provides a kind of function; Therefore realize that service can corresponding a plurality of function services for one, function service also can corresponding a plurality of realization services, function service and realize that service is a kind of relation of multi-to-multi.The service of realization is the instance of function service, connects through Instance-of (instance relation) based on the function service in the Web service relational network of semanteme with between realizing serving.
The subclass commonly used of Web service attribute description part defines in OWL-S file that the structure of said each node is chosen according to correspondence and the wsdl document, and each corresponding nodes provides the URI properties point original OWL-S file or wsdl document simultaneously.
Said wsdl document has two kinds of sources: submit service to and obtain service.Submit to service initiatively to register the Web service of being described by WSDL by the ISP, the service of obtaining is under in the Internet, seeking the available Web service of being described by WSDL and obtain through crawlers.After utilizing the WSDL2SN resolver that wsdl document is resolved; Generate Web service relational network node; And then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit, the resolver realization flow of said WSDL2SN may further comprise the steps:
At first, read wsdl document among the definition through WSDL4JAPI;
From definition, read and obtain type types definition;
In the types definition, make up attribute informations such as NameSpace, and convert this attribute to the JDOM type;
Obtain accomplishing the schema definition of the type of conversion.
For the parameter in the wsdl document is the situation of self-defining complicated type; The schema that obtains above needing to use goes to carry out the parsing of complicated type, until customization type is decomposed, obtains a series of simple types; Therefore, after above-mentioned flow process, also further may further comprise the steps:
At first the service element is resolved, obtain binding information;
Find corresponding portType information according to binding information;
All operations (operation) to being comprised among the portType is resolved, and obtains the base attribute and the parameter information of each operation, and each input and output result is respectively a message;
Find corresponding message definition according to parameter information;
The concrete structure of message obtains from the schema that has built, until message is decomposed into simple types;
Bindtype is judged, further be divided into RPC type and code-shaped;
When bindtype is RPC, make up RPC type complex parameters;
Judge whether constructed RPC type complex parameters is complicated type;
Obtain complete information on services;
When bindtype when being code-shaped, make up the Doctype complex parameters;
Judge whether constructed Doctype complex parameters is complicated type;
Obtain complete information on services.
Said OWL-S file has two kinds of sources equally: submit service to and obtain service.Submit to service initiatively to register the Web service of being described by OWL-S by the ISP, the service of obtaining is under in the Internet, seeking the available Web service of being described by OWL-S and obtain through crawlers.Utilize the OWL-S resolver that the OWL-S file is resolved; Generate Web service relational network node; And then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit, the resolver of said OWL-S2SN specifically may further comprise the steps:
At first, read the OWL-S file through the URI of OWL-S;
Import other bodies that OWL-S quotes;
Whether the body that inspection this document is described effectively reaches compliant;
If the check result of above-mentioned body is effective and compliant, then parses and form the needed related content of service node in the service network;
Be mapped to the standard that meets the service network definition;
The result is persisted in the service network, and notifies corresponding maintenance program;
With update notification service network maintenance process;
If the check result of above-mentioned body is invalid or does not meet standard, then export relevant information, and this EO.
To the corresponding service relation mining algorithm that the service relation in the said Web service relational network adopts, concrete steps are following:
At first, preliminary treatment is carried out in two services, extracted the functional description label (tag) of service and the operation-interface of service; Calculate the relation of two groups of tag and two groups of service operations interfaces then respectively; Obtain service relation according to certain weights weighting again; According to service relation update service network, algorithm finishes.
Wherein this algorithm further comprises the calculation process of service operations interface relationship, and concrete steps are following:
At first, two operation-interfaces are carried out preliminary treatment; Whether interface name and the descriptor of judging these two operation-interfaces are antisense, if then algorithm flow finishes; If not, then carry out the calculating of I/O parameters relationship; Obtain the relationship type and the similarity of operation-interface then, algorithm finishes.
Said system also comprises the manual operation interface.
Below in conjunction with accompanying drawing and specific embodiment further explain the present invention.
Be illustrated in figure 1 as the sketch map that forms based on the Web service relational network of competition and cooperation of the present invention.Service network system is at first obtained many independently Web services from the semantic Web service registration center of traditional nothing; Through analysis, and provide semantic by body and support, semantic description is added in each service service structure; And excavate the various relations that exist between each service; With these independently Web service be node, be that the service network layer form is realized on the limit with the various relations between these services, also carry out extensive simultaneously with regard to the function of each Web service; Take out general character; With the function that takes out is that the function service is a node, thereby forms function service network layer with the relation between the function service as the limit, and the integral body that constitutes thus is exactly the Web service relational network based on competition and cooperation of the present invention.
Be illustrated in figure 2 as the Web service relational network system schematic based on competition and cooperation of the present invention.This service relation network system will be served the node as this network, and semantic relation specifically is divided into two-layer again as the limit between the service: functional layer and realization layer comprise the function service respectively and realize service.
Said realization service comprises the Web service of being described by OWL-S and WSDL, can be divided into three kinds according to granule size: seeervice level, interface level and parametric degree.Correspondingly, relation also is divided into three kinds of granularities.Wherein, the parametric degree semantic relation comes from the semantic relation between the Ontological concept that parameter is marked, and the relation of definition has:
1.Part-of promptly the whole and part relation is represented the association between the whole and part between the parameter.The Part-of relation is irreflexive, and is antisymmetric, transmission.
2.Attribute-of promptly the object properties relation is represented the attribute that parameter is another parameter.The Attribute-of relation is irreflexive, and is antisymmetric, and do not have transitivity.
3.Kind-of promptly inheritance is represented the general and special relation between the parameter.Kind-of is irreflexive, and is antisymmetric, transmission.
4.Equivalent-of i.e. equivalence relation is identical semantically between the expression parameter.Equivalent-of is reflexive, symmetry, transmission.
The interface level semantic relation is based upon on the parametric degree semantic relation, is divided into competitive relation and cooperation relation, and wherein, competitive relation comprises:
5.Exacto promptly equivalence relation is represented interface I
1Input and output semantically with interface I
2Input and output identical, the relation between two interfaces that function equates fully on the semantic hierarchies is described.
6.Subsumeo promptly inheritance is represented interface I
1Input and output comprise interface I respectively
2Input and output, describe previous interface and on semantic hierarchies, comprise a back interface.
7.Plug-ino, the relation of promptly pegging graft, expression interface I
2Input and output comprise interface I respectively
1Input and output, describe a back interface and on semantic hierarchies, comprise previous interface, be the reverse-power of Subsumeo.
Cooperation relation comprises:
8.Sequential-totalo, promptly complete follow-up relation, expression interface I
1Output comprise interface I
2Input.
9.Sequential-parto promptly the follow-up relation of part is represented interface I
1Output comprise interface I
2Input.
10.Precedence-totalo promptly the forerunner concerns fully, expression interface I
2Output comprise interface I
1Input.
11.Precedence-parto promptly part forerunner relation is represented interface I
2Output comprise interface I
1Input.
Because interface is the functional unit of Web service, so the seeervice level semantic relation is based upon on the interface level semantic relation, is divided into competitive relation and cooperation relation equally, and wherein, competitive relation comprises:
12.Exacts promptly equivalence relation is supposed I
11Be service S
1In an interface, I
21Be service S
2In an interface, if I
11And I
21Be Exacto relation, then S
1And S
2It is the Exacts relation.
13.Subsumes if i.e. inheritance is I
11And I
21Be Subsumeo relation, then S
1And S
2It is the Subsumes relation.
14.Plug-ins if the relation of promptly pegging graft is I
11And I
21Be Plug-ino relation, then S
1And S
2It is the Plug-ins relation.
Cooperation relation comprises:
15.Sequential-totals if promptly complete follow-up relation is I
11And I
21Be Sequential-totalo relation, then S
1And S
2It is the Sequential-totals relation.
16.Sequential-parts if the i.e. follow-up relation of part is I
11And I
21Be Sequential-parto relation, then S
1And S
2It is the Sequential-parts relation.
17.Precedence-totals promptly the forerunner concerns fully, if I
11And I
21Be Precedence-totalo relation, then S
1And S
2It is the Precedence-totals relation.
18.Precedence-parts promptly the part forerunner concerns, if I
11And I
21Be Precedence-parto relation, then S
1And S
2It is the Precedence-parts relation.
Function service in this service relation network system derives from the difference in functionality of the service of realization; Promptly merge the function of the service of realization and extract different functions; Each function service only provides a kind of function; Therefore realize that service can corresponding a plurality of function services for one, function service also can corresponding a plurality of realization services, function service and realize that service is a kind of relation of multi-to-multi.The service of realization is the instance of function service; Between connect through Instance-of; The service semantics relation of functional layer is based upon and realizes on the service interface semantic relation basis; And do not have the semantic equivalence relation, therefore all the other six kinds except that the Exact relation realize that the service interface semantic relation can directly be mapped as the semantic relation between the function service.Flow process by realizing service of service construction function and continuous update functions layer is as shown in Figure 3, mainly may further comprise the steps:
The service relation network is empty in the time of at first, initially;
When the service of realization arrived, the Web service of promptly being described by OWL-S (or WSDL) utilized OWL-S2SN resolver (or WSDL2SN resolver) to decompose the interface of service out;
If the service relation network is empty, then this interface is first interface in the service relation network;
This interface is pressed the direct systematic function service of definition that function is served, and it is joined in the function service;
Between the realization service at this interface place and function service, set up mapping relations and update functions service implementing service relation storehouse;
Parameter that this interface is contained and function service generate mapping relations, and are updated to the ideational function map of services and concern the storehouse;
Second and later interface are taked following same action:
Take out an output parameter in the interface;
In the parameter of functional layer, find this parameter;
Concern that through the ideational function map of services storehouse obtains all functions service that parameter therewith has mapping relations, and all functions service that joins of parameter correlation relating to parameters therewith, these services are owing to contain identical or related output parameter, so interface is correlated with therewith;
This interface is carried out the comparison of equivalence relation with relevant all functions service;
If the service of this interface and certain function is of equal value, then this interface is classified as this function service, and function is served interface place therewith realize that map updating between service is in function service implementing service relation storehouse;
Like non-equivalence, then with the direct systematic function service of this interface, and update functions service, function service implementing service relation storehouse and ideational function map of services concern the storehouse.
Wherein, the property parameters of service node comprises:
19. interface attributes: IOPE, i.e. Input (input), Output (output), Precondition (precondition), Effect (object information).
20. functional description (being label or classification): the function that employing keyword form description service is accomplished and the characteristics of service, and, have the service of same keyword to become one type with this classification foundation as service.
21. service providers information: such as, name, and contact method (phone, E-mail).When the user can only use this service, and this service is unavailable, and the supplier that the user can contact service so makes service available through consultation.
22.URI: the address of service.
23.D-URI (Description-URI): the URI at description document place.
24. composite services attribute: do property value as then use " atomic " for atomic service, if composite services are then used " cmp " as property value.
25. authority information: username/password.For paid service, may need.
26. service-creation information: (each modification time).
27. service quality: comprise stability, reliability, cost of serving and credit worthiness.Stability (Stability) is used to describe same Web service in the different difference of calling the constantly required response time; Response time (Response Time) refers to that service sends the request carried out from the requestor and begin to receiving response message institute elapsed time; Reliability (Reliability) expression can maintenance service and the degree of service quality; Cost of serving (Service Cost) is described service consumer need be the expense of using service to pay; Credit worthiness (Grade) is used to describe the evaluation of service user to the Web service that they called.
In the Web service relational network system based on competition and cooperation of the present invention; The subclass commonly used of Web service attribute description part defines in OWL-S file that the structure of each node is chosen according to correspondence and the wsdl document, and each corresponding nodes provides the URI properties point original OWL-S file or wsdl document simultaneously.Adopt this way both can guarantee the succinct, clear of Web service structure, also guaranteed information integrity simultaneously, realize easily.
The present invention mainly adopts the ontology describing to service, representes the Web service relational network.
Because the various Web service describing modes of service relation network of the present invention and prior art are inconsistent; Therefore defined a kind of node structure of the information of comparatively simply not losing former description document again and being comprised, to guarantee the compatibility of this service relation network system to various different Web service describing modes of the prior art.This processing needs at first different describing modes to be resolved, and process of analysis is as shown in Figure 4.This process of analysis may further comprise the steps:
For wsdl document, utilize the WSDL2SN resolver to resolve after, generate Web service relational network node, and then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit; For the OWL-S file, after the dissection process through the OWL-S2SN resolver, generate Web service relational network node, and then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit.
The resolver realization flow of WSDL2SN, this flow process step 401 as shown in Figure 5～step 404, this flow process may further comprise the steps:
At first, read wsdl document among the definition step 401 through WSDL4J API; From definition, read and obtain type types definition (DOM type), step 402; In the types definition, make up attribute informations such as NameSpace, and convert this attribute to JDOM type, step 403; Obtain accomplishing the schema definition of the type of conversion, step 404; This schema is defined in and faces when self-defining parameter type is resolved and need use.
For the parameter in the wsdl document is the situation of self-defining complicated type, and the schema that obtains above needing to use goes to carry out the parsing of complicated type, until customization type is decomposed, obtains a series of simple types.This part flow process step 405 as shown in Figure 4～step 415, this flow process may further comprise the steps:
Step 405: at first the service element is resolved, obtain binding information, that is: resolve to < wsdl:service>label, find the binding information of the binding back in each < wsdl:port>label;
Step 406: find corresponding portType information according to binding information, that is: in < wsdl:binding>label, go for the portType attribute, main interface name that this service provided that Here it is;
Step 407: all operations (operation) to being comprised among the portType is resolved; Obtain the base attribute and the parameter information of each operation; That is: in < wsdl:portType>label, go for each operation; < wsdl:operation>each operation is again respectively to there being the input and output of oneself, and each input and output result is respectively a message;
Step 408: find corresponding message definition according to parameter information, that is: go for the basic composition of each message in < wsdl:message >, it possibly be made up of simple types and complicated customization type.If simple types, then resolving stops;
The concrete structure of step 409:Message can obtain from the schema that has built; Until message is decomposed into simple types; If that is: the composition of message is complicated customization type; Then need recursively in type definition, to go for definition, be entirely simple types until structure types to this complicated type;
Step 410: bindtype is judged, further be divided into RPC type and code-shaped;
Step 411: when bindtype is the RPC type, make up RPC type complex parameters;
Step 412: judge whether constructed RPC type complex parameters is complicated type;
Step 415: obtain complete information on services;
Step 413:, make up the Doctype complex parameters when bindtype when being code-shaped;
Step 414: judge whether constructed Doctype complex parameters is complicated type;
Step 415: obtain complete information on services.
Be illustrated in figure 6 as the realization flow figure of OWL-S2SN resolver, specifically may further comprise the steps:
Step 501: at first through the URI of OWL-S, read the OWL-S file, that is: the URI of the OWL-S file that obtains to be resolved reads this document, and reads other ontology file that it is quoted;
Step 502: import other bodies that OWL-S quotes;
Step 503: whether the body that inspection this document is described effectively reaches compliant, promptly whether has contradiction semantically, and whether meets the OWL-S standard;
Step 504:, then parse and form the needed related content of service node in the service network if the check result of above-mentioned body is effective and compliant;
Step 505: be mapped to the standard that meets the service network definition, that is: the result that will resolve is formatted into the form that meets the service network normalized definition;
Step 506: the result is persisted in the service network, and notifies corresponding maintenance program;
Step 507: with update notification service network maintenance process;
Step 508: if the check result of above-mentioned body be invalid or do not meet standard, then export relevant information, and finish operation this time.
Be illustrated in figure 7 as the general frame figure based on the Web service relational network system that competes and cooperate of the present invention; Wherein the Web service relational network is used to serve automatic discovery, service (partly) Automatic Combined, this Web service relational network the service that will handle derive from the service that the user submits to; The composite services that the Web service network produces automatically; Web service relational network system is searched for from Internet through the robot program automatically, extracts disclosed service.Wherein, submit to service to comprise the information extraction of the submission/service of serving, the Web service relational network is delivered in this information extraction; The Web service network will produce new composite services automatically according to user's demand (partly), and produce the description document of this Web service, when the user is submitted in this service, also leave in the Web service network as a case; The service of obtaining is then added interface with the description document that obtains service through service and is delivered to the Web service relational network; The relation that this Web service relational network is had derives from the excavation of submitting service to and obtaining relationship between services, is obtained by the service relation mining algorithm, and the Web service relational network is delivered to by service-seeking/display interface in the back; The service-seeking function that this Web service relational network provides is accomplished through service-seeking/display interface.
This Web service relational network also comprises the manual operation interface, is used for the inquiry service that the Web service relational network is provided, the manual operation of obtaining service and composite services and Web service relational network.The manual operation of inquiry service is meant to be enumerated out with all Web services in the Web service relational network, and the user is according to the demand active inquiry Web service of oneself then; The manual operation of obtaining service refers to deliver to the Web service relational network through the mode of craft from the description document information extraction of service and through service interpolation interface; The similar inquiry service of the manual operation of composite services is that all Web services in the Web service relational network are enumerated out equally, and the user initiatively makes up Web service according to the demand of oneself then; The manual operation of Web service relational network is meant that the user can make amendment to the annotation results of the Web service of process mark in the Web service relational network.
In order to realize the object of the invention, the present invention will adopt semantic network technology to make up the Web service body and design corresponding relation excavation algorithm.Excavate for service relation; What do is in the general logical relation of serving calculation services in the world; Need detailed numerical to measure degree similar between the service, and the relation between the service depend on the relation between the service operations interface to a great extent.
Be illustrated in figure 8 as the calculation process of the operation-interface relation of service relation mining algorithm, this flow process may further comprise the steps:
At first, two operation-interfaces are carried out preliminary treatment; Whether interface name and the descriptor of judging these two operation-interfaces are antisense, if then algorithm flow finishes; If not, then carry out I/O parameter similarity and calculate, the interface similarity is set up then, obtains relationship type and similarity, and algorithm finishes.
Following mask body is introduced the concrete implication of some treatment steps in this algorithm:
" preliminary treatment " module is some preliminary treatment work that operation-interface is carried out, and comprises participle and analysis to the operation-interface name, to the extraction of keyword in the descriptor, and to the extraction of input tabulation.
The descriptive information of operation-interface name and operation-interface only plays reference role, can no longer consider if not the opposite meaning.
" calculating of parameter similarity " module is used to calculate the similarity degree of two groups of parameters.The input parameter tabulation is the same with the similarity calculating method of output parameter tabulation, and back literary composition is referred to as the parameter list similarity and calculates, and just in final calculating operation interface relationship, the shared proportion of input and output is different.Generally, people more are concerned about the match condition of output, and therefore exporting shared proportion is greater than input.
Generally speaking, the parameter list of service is not simple data type, but has the notion of semantic information, and in this article, the parameter list calculation of similarity degree promptly can be regarded the similarity calculating of two groups of notions as.
Calculation of similarity degree method between two independent once notions at first will be described.Concept similarity is meant in the body tolerance of similarity degree between two notions.Need to prove to have only two notions in the same body that similarity is just arranged, the notion in the different bodies thinks that similarity is zero (can consider the concept similarity in the different bodies future).The similarity degree of notion is relevant with the semantic distance between the notion in the body, can obtain the similarity between single notion through relevant similarity function.
The similarity of two groups of notions can solve through the Optimum Matching method of weighting bigraph (bipartite graph).Regard two groups of notions as two groups of summits, the similarity of operation room is the weights on limit (for simplicity, for similarity is provided with a threshold value, is lower than this threshold value and then thinks zero, promptly do not have this edge).The present invention confirms the coupling between the parameter list with reference to the kuhn-munkres algorithm of classics.
In " service relation foundation " module, according to the similarity value and the next final similarity relation of confirming between the operation-interface of like attribute of input, output list of concepts.
Be illustrated in figure 9 as operate services of the present invention and concern calculation process.This flow process specifically may further comprise the steps:
At first, preliminary treatment is carried out in two services, extracted the functional description label (tag) of service and the operation-interface of service; Calculate the relation of two groups of tag and two groups of service operations interfaces then respectively; Obtain service relation according to certain weights weighting again; According to the service relation update service network of gained, algorithm finishes.
Following mask body is introduced the concrete implication of some treatment steps in this algorithm:
" preliminary treatment " module is some preliminary treatment work that the service operations interface is carried out, and extracts the functional description label (tag) of service and the operation-interface of service.
In " interface relationship calculating " module; As input, pairing is in twos used algorithm shown in Figure 7 and is calculated then with two groups of operation-interfaces; Obtain in two groups of operation-interfaces the similarity value and the relationship type of pairing in twos, again through seeking the optimum Match of bigraph (bipartite graph).Regard two groups of operations as two groups of summits, the similarity of operation room is the weights (for simplicity, for similarity is provided with a threshold value, is lower than this threshold value and then thinks zero, promptly do not have this edge) on limit, thereby confirms the similarity and the relationship type of two groups of operations.Here still confirm the coupling between operation-interface with reference to the kuhn-munkres algorithm.
In " the phrase relation is calculated " module; As input, pairing in twos then is based on the similarity and the relationship type of WordNet semantic dictionary calculating vocabulary with two groups of tag; Obtain among two groups of tag the similarity value and the relationship type of pairing in twos, again through seeking the optimum Match of bigraph (bipartite graph).Regard two groups of tag operations as two groups of summits, the similarity between vocabulary is the weights (for simplicity, for similarity is provided with a threshold value, is lower than this threshold value and then thinks zero, promptly do not have this edge) on limit, thereby confirms the similarity and the relationship type of two groups of operations.
" service relation foundation " module is confirmed service relation through operation-interface relation and tag relation according to certain weight, if service relation exists, then comes the update service network through " update service network " module, and algorithm finishes; Otherwise algorithm directly finishes.
Above content is merely embodiments of the invention, and its purpose is not the restriction that is used for system proposed by the invention, and protection scope of the present invention is as the criterion with claim.Under the situation that does not break away from the spirit and scope of the present invention; Those skilled in the art all should drop within protection scope of the present invention its all conspicuous modification or variation about form and details of carrying out under the situation that does not depart from the scope of the invention and spirit.
Claims (5)
1. the Web service relational network system based on competition and cooperation is characterized in that, comprises the submission service module, obtains service module, relation excavation algoritic module, service-seeking/display module; The submission service module comprises the information extraction of the submission/service of serving, and by body semantic support is provided, and the Web service relational network is delivered in the information extraction behind the mark; Obtain service module and then the description document of the service that obtains to have semantic information is delivered to the Web network through service-seeking/display module; Obtaining service module also will be according to the composite services that functional description obtained that comprise semantic information, and these composite services also are to deliver to the Web service relational network through service-seeking/display interface; Service relation mining algorithm module is used for submitting to the excavation of serving and obtaining relationship between services to obtain service relation, and the Web network is delivered to by service-seeking/display module in the back; The inquiry service function is accomplished through service-seeking/display module.
2. the Web service relational network system based on competition and cooperation as claimed in claim 1; It is characterized in that; When the service of realization arrives; The Web service of promptly being described by OWL-S (Ontology Web Language for Services) or WSDL (Web Service Description Language) utilizes OWL-S2SN resolver or WSDL2SN resolver to decompose the interface of service out; For wsdl document, utilize the WSDL2SN resolver to resolve after, generate Web service relational network node, and then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit; For the OWL-S file, after the dissection process through the OWL-S2SN resolver, generate Web service relational network node, and then be node with the Web service, the semantic relation between Web service is the realization layer that Web service relational network system is formed on the limit.
3. the Web service relational network system based on competition and cooperation as claimed in claim 1 is characterized in that the resolver realization flow of WSDL2SN may further comprise the steps:
At first; Read wsdl document in the definition (definition) step 401 through WSDL4J (WSDL for Java) API (Application Programming Interface): from definition, reading and obtaining type (types) definition is DOM (Document Object Model) type; Step 402: in the types definition, make up attribute informations such as NameSpace; And convert this attribute to JDOM (Java Document Object Model) type; Step 403: obtain accomplishing pattern (schema) definition of the type of conversion, step 404: this schema need use when being defined in and resolving in the face of self-defining parameter type;
For the parameter in the wsdl document is the situation of self-defining complicated type, and the pattern (schema) that obtains above needing to use goes to carry out the parsing of complicated type, until customization type is decomposed, obtains a series of simple types; This part flow process may further comprise the steps:
Step 405: at first service (service) element is resolved, obtain binding information, that is: resolve to < wsdl:service>label, find the binding information of binding (binding) back in each < wsdl:port>label;
Step 406: find corresponding port type (portType) information according to binding information, that is: in < wsdl:binding>label, go for the portType attribute, main interface name that this service provided that Here it is;
Step 407: all operations (operation) to being comprised among the portType is resolved; Obtain the base attribute and the parameter information of each operation; That is: in < wsdl:portType>label, go for each operation; < wsdl:operation>each operation is again respectively to there being the input and output of oneself, and each input and output result is respectively a message (message);
Step 408: find corresponding message definition according to parameter information, that is: go for the basic composition of each message in < wsdl:message >, it possibly be made up of simple types and complicated customization type.If simple types, then resolving stops;
The concrete structure of step 409:Message can obtain from the schema that has built; Until message is decomposed into simple types; If that is: the composition of message is complicated customization type; Then need recursively in type definition, to go for definition, be entirely simple types until structure types to this complicated type;
Step 410: bindtype is judged, further be divided into RPC (Remote Procedure Call) type and code-shaped;
Step 411: when bindtype is the RPC type, make up RPC type complex parameters;
Step 412: judge whether constructed RPC type complex parameters is complicated type;
Step 415: obtain complete information on services;
Step 413:, make up the Doctype complex parameters when bindtype when being code-shaped;
Step 414: judge whether constructed Doctype complex parameters is complicated type;
Step 415: obtain complete information on services.
4. the Web service relational network system based on competition and cooperation as claimed in claim 1 is characterized in that the realization flow figure of OWL-S2SN resolver specifically may further comprise the steps:
Step 501: at first through the URI (Uniform Resource Identifier) of OWL-S, read the OWL-S file, that is: the URI of the OWL-S file that obtains to be resolved reads this document, and reads other ontology file that it is quoted;
Step 502: import other bodies that OWL-S quotes;
Step 503: whether the body that inspection this document is described effectively reaches compliant, promptly whether has contradiction semantically, and whether meets the OWL-S standard;
Step 504:, then parse and form the needed related content of service node in the service network if the check result of above-mentioned body is effective and compliant;
Step 505: be mapped to the standard that meets the service network definition, that is: the result that will resolve is formatted into the form that meets the service network normalized definition;
Step 506: the result is persisted in the service network, and notifies corresponding maintenance program;
Step 507: with update notification service network maintenance process;
Step 508: if the check result of above-mentioned body be invalid or do not meet standard, then export relevant information, and finish operation this time.
5. the Web service relational network system based on competition and cooperation as claimed in claim 1 is characterized in that, the calculation process of the operation-interface relation of service relation mining algorithm module may further comprise the steps:
At first, two operation-interfaces are carried out preliminary treatment; Whether interface name and the descriptor of judging these two operation-interfaces are antisense, if then algorithm flow finishes; If not, then carry out I/O parameter similarity and calculate, the interface similarity is set up then, obtains relationship type and similarity, and algorithm finishes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102472436A CN102769671A (en) | 2012-07-17 | 2012-07-17 | Competition and cooperation-based Web service relation network system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102472436A CN102769671A (en) | 2012-07-17 | 2012-07-17 | Competition and cooperation-based Web service relation network system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102769671A true CN102769671A (en) | 2012-11-07 |
Family
ID=47096919
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012102472436A Pending CN102769671A (en) | 2012-07-17 | 2012-07-17 | Competition and cooperation-based Web service relation network system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102769671A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104809147A (en) * | 2015-02-06 | 2015-07-29 | 天津大学 | Service semantics mark reinforcing method based on implementing analysis feedback |
| CN105306542A (en) * | 2015-09-25 | 2016-02-03 | 北京奇艺世纪科技有限公司 | System for integrating Web services |
| CN108182106A (en) * | 2017-12-26 | 2018-06-19 | 湖南全软软件技术有限公司 | The method and apparatus that WEB front and back end data interactions are realized by semantization label |
| CN111400611A (en) * | 2020-02-17 | 2020-07-10 | 华北电力大学 | Service discovery method based on Web complex relationship network |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101605141A (en) * | 2008-08-05 | 2009-12-16 | 天津大学 | Web service relational network system based on semanteme |
| CN101674290A (en) * | 2008-11-26 | 2010-03-17 | 天津大学 | Semantics-based automatic service combination system for web service relation network |
-
2012
- 2012-07-17 CN CN2012102472436A patent/CN102769671A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101605141A (en) * | 2008-08-05 | 2009-12-16 | 天津大学 | Web service relational network system based on semanteme |
| CN101674290A (en) * | 2008-11-26 | 2010-03-17 | 天津大学 | Semantics-based automatic service combination system for web service relation network |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104809147A (en) * | 2015-02-06 | 2015-07-29 | 天津大学 | Service semantics mark reinforcing method based on implementing analysis feedback |
| CN104809147B (en) * | 2015-02-06 | 2017-12-22 | 天津大学 | A kind of service semantics based on empirical evaluation feedback mark Enhancement Method |
| CN105306542A (en) * | 2015-09-25 | 2016-02-03 | 北京奇艺世纪科技有限公司 | System for integrating Web services |
| CN105306542B (en) * | 2015-09-25 | 2018-12-14 | 北京奇艺世纪科技有限公司 | A kind of system for integrating web service |
| CN108182106A (en) * | 2017-12-26 | 2018-06-19 | 湖南全软软件技术有限公司 | The method and apparatus that WEB front and back end data interactions are realized by semantization label |
| CN111400611A (en) * | 2020-02-17 | 2020-07-10 | 华北电力大学 | Service discovery method based on Web complex relationship network |
| CN111400611B (en) * | 2020-02-17 | 2023-10-27 | 华北电力大学 | Service discovery method based on Web complex relation network |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101605141A (en) | Web service relational network system based on semanteme | |
| EP1753195B1 (en) | Server computer, client device and web service implemented data processing method | |
| Laukkanen et al. | Composing workflows of semantic web services | |
| CN101873335B (en) | Distributed type searching method of cross-domain semantic Web service | |
| US20160217013A1 (en) | Method and system for generating a virtual device resource accessible by an application | |
| US9697297B2 (en) | Representation/invocation of actions/functions in a hypermedia-driven environment | |
| CN101291337A (en) | Grid resource management system and method | |
| CN101609415A (en) | Universal service calling system and method based on middleware | |
| Di Martino et al. | Towards an Ontology-Based Intercloud Resource Catalogue--The IEEE P2302 Intercloud Approach for a Semantic Resource Exchange | |
| CN102769671A (en) | Competition and cooperation-based Web service relation network system | |
| Li et al. | Graph-based semantic evolution for context information management platforms | |
| CN105373537A (en) | Intelligent component library management method | |
| Feng et al. | A study of semantic web services network | |
| CN101771712A (en) | Method for managing Web service registry | |
| CN101727459A (en) | WEB-based data exchange system and method applicable to distributed database | |
| Kourtesis et al. | Web service discovery in the FUSION semantic registry | |
| Berkovsky | Ubiquitous user modeling in recommender systems | |
| JP2012528367A (en) | Method and associated system for adapting data in a data transmission system | |
| Athanasopoulos et al. | Service substitution revisited | |
| CN102082793A (en) | Method for configuring audio-video services | |
| CN102065133B (en) | Method and system for constructing complex service logic by supporting Portlet cooperation | |
| Zhao et al. | Multi-agent Middleware for the Integration of Mobile Supply Chain. | |
| Fuentes-Fernández et al. | Integration of web services in an agent-oriented methodology | |
| Jeong et al. | A message conversion system, XML-based metadata semantics description language and metadata repository | |
| CN103973799A (en) | Resource and environment data decision support platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20121107 |