US2014006576A1PendingUtilityA1

Managing service specifications and the discovery of associated services

Individually held — no corporate assignee on recordPriority: Jun 28, 2012Filed: Jun 28, 2012Published: Jan 2, 2014

Est. expiryJun 28, 2032(~5.9 yrs left)· nominal 20-yr term from priority

Inventors:Rahul P. Akolkar Arun Kwangil Iyengar Isabelle M. Rouvellou Ignacio Silva-Lepe Revathi Subramanian

G06Q 10/103

PatentIndex Score

Cited by

References

Claims

Abstract

Various embodiments manage service labels for association with service specifications in a service-oriented environment. In one embodiment at least one candidate service label is received from a user associated with a service domain of a distributed federated service-oriented environment. The candidate service label includes at least one of a service type and a set of terms characterizing a service. The candidate service label is sent to a community of users associated with one or more service domains in the distributed federated service-oriented environment. One of a vote for accepting the candidate service label and a vote for rejecting the candidate service label is received from each of a plurality of users in the community of users. The candidate service label is stored as an accepted service label in the service domain based on a number of votes for accepting the candidate service label being above a given threshold.

Claims

exact text as granted — not AI-modified

What is claimed is: 
     
         1 . A method for managing service labels for association with service specifications in a service-oriented environment, the method comprising:
 receiving at least one candidate service label from a user, wherein the candidate service label comprises at least one of a service type and a set of terms characterizing a service;   sending the candidate service label to a community of users;   receiving, based on the sending, one of a vote for accepting the candidate service label and a vote for rejecting the candidate service label from each of a plurality of users in the community of users; and   based on a number of votes being above a given threshold, one of
 storing the candidate service label as an accepted service label associated with the community of users; and 
 rejecting the candidate service label. 
   
     
     
         2 . The method of  claim 1 , wherein the service type comprises a service type name and a description of a functionality provided by a service matching the service type. 
     
     
         3 . The method of  claim 1 , wherein the service type further comprises one or more input and output parameters associated with the service type. 
     
     
         4 . The method of  claim 1 , wherein each of the set of terms comprises an identifier and a definition associated with the term. 
     
     
         5 . The method of  claim 1 , wherein the candidate service label is sent to the community of users via a distributed consensus protocol. 
     
     
         6 . The method of  claim 1 , further comprising:
 replicating the accepted service label in at least one information processing system that is different from an information process system on which the candidate service label has been stored.   
     
     
         7 . The method of  claim 1 , further comprising:
 receiving, from a user, a first service specification of a requested service comprising the accepted service label;   identifying, from a registry, at least a second service specification associated with an available service, wherein the second service specification comprises an accepted service label;   comparing the accepted service label of the first service specification with the accepted service label of the second service specification;   determining, based on the comparing, that the accepted service label of the first service specification matches the accepted service label of the second service specification; and   based on the determining notifying, the user, from which the first service specification was received, of the available service.   
     
     
         8 . A method for matching service specifications in a service-oriented environment, the method comprising:
 analyzing a registry of service specifications;   identifying, based on the analyzing, a first set of service specifications associated with requested services and a second set of service specifications associated with available services,   wherein each service specification in the first and second sets of service specifications comprises a service label, wherein information within each of the service labels has been previously agreed upon by two or more users in a community of users, and wherein each service label comprises at least one of a service type and a set of terms characterizing a service;   comparing the service labels of the first set of service specifications with the service labels of the second set of service specifications; and   identifying at least one service specification in the first set of service specifications that matches at least one service specification in the second set of service specifications based on comparing the services labels thereof.   
     
     
         9 . The method of  claim 8 , wherein the service type comprises a service type name and a description of a functionality provided by a service matching the service type. 
     
     
         10 . The method of  claim 8 , wherein the service type further comprises one or more input and output parameters associated with the service type. 
     
     
         11 . The method of claim of  claim 8 , wherein identifying at least one service specification in the first set of service specifications that matches at least one service specification in the second set of service specifications further comprises:
 determining, based on the comparing, that at least one of structural characteristics and syntactic characteristics of at least one of a service type name, a description, one or more input parameters in the service label of the at least one service specification in the first set of service specifications matches at least one of structural characteristics and syntactic characteristics of at least one of a service type name, a description, and one or more input parameters, respectively, in the service label of the at least one service specification in the second set of service specifications.   
     
     
         12 . The method of  claim 8 , wherein the information within each of the service labels has been previously agreed upon by two or more users in a community of users using a distributed consensus protocol. 
     
     
         13 . The method of  claim 8 , wherein each of the set of terms comprises an identifier and a definition associated with the term. 
     
     
         14 . The method of  claim 13 , wherein the identifier is a text string. 
     
     
         15 . The method of claim of  claim 13 , wherein identifying at least one service specification in the first set of service specifications that matches at least one service specification in the second set of service specifications further comprises:
 determining, based on the comparing, that at least one of the identifier and the definition in the service label of the at least one service specification in the first set of service specifications matches at least one of the identifier and the definition, respectively, in the service label of the at least one service specification in the second set of service specifications.   
     
     
         16 . A method for discovering services in a service-oriented environment, the method comprising:
 receiving, from a user in a community of users, a request for a service, wherein the request comprises a first service specification;   identifying, from a registry of service specifications, at least a second service specification, wherein the second service specification is associated with at least one available service,   wherein the first service specification comprises a first service label and the second service specification comprises a second service label, wherein information within each of the first and second service labels has been previously agreed upon by two or more users in the community of users, and wherein each of the first and second service labels comprises at least one of a service type and a set of terms characterizing a service;   comparing the first service label with the second service label;   determining, based on the comparing, that the first service label matches the second service label; and   satisfying, based on the determining, the request with the available service associated with the second service specification.   
     
     
         17 . The method of  claim 16 , wherein the service type comprises a service type name and a description of a functionality provided by a service matching the service type. 
     
     
         18 . The method of  claim 16 , wherein the service type further comprises one or more input and output parameters associated with the service type. 
     
     
         19 . The method of claim of  claim 16 , wherein determining that the first service label matches the second service label further comprises:
 determining, based on the comparing, that at least one of structural characteristics and syntactic characteristics of at least one of a service type name, a description, and one or more input parameters in the first service label matches at least one of structural characteristics and syntactic characteristics of at least one of a service type name, a description, and one or more input parameters, respectively, in the second service label.   
     
     
         20 . The method of claim of  claim 16 , wherein determining that the first service label matches the second service label further comprises:
 determining, based on the comparing, that at least one of the identifier and the definition in the first service label matches at least one of the identifier and the definition, respectively, in the second service label.   
     
     
         21 . The method of  claim 16 , wherein the information within each of the service labels has been previously agreed upon by two or more users in a community of users using a distributed consensus protocol. 
     
     
         22 . The method of  claim 16 , wherein each of the set of terms comprises an identifier and a definition associated with the term. 
     
     
         23 . The method of  claim 22 , wherein the identifier is a text string.

Join the waitlist — get patent alerts

Track US2014006576A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.