Service knowledge map

• US 20090187444A1
• Filed: 03/11/2008
• Published: 07/23/2009
• Est. Priority Date: 05/11/2007
• Status: Abandoned Application

• Current Assignee: Yefim Zhuk
• Original Assignee: Yefim Zhuk
• Inventors: Zhuk, Yefim
• Application Number:
  US12/075,290
• Publication Number:
  US 20090187444A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group
• CPC Class Codes: G06Q 10/063112 Skill-based matching of a person or a group to a task
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

The Service Knowledge Map or Service Knowledge Bus will help developers and subject matter experts (SME) describe, find, assemble, and execute software services.

The main difference between this system and similar purpose systems is the target audience and related methods of communications. While similar systems target computer programs that can read and understand XML messages to connect web services, this system operates with natural language, providing mapping between service descriptions and implementations, and allows computerized systems and multiple audiences of SME for conversational flexibility while describing and assembling new services on-the-fly as well as creating sophisticated policy for service usage.

Claims

1. The Service Knowledge Map or Service Knowledge Bus comprising plurality of the Service Exchange Agent (SEA) systems connected via network and enabling collaboration and exchange of services and service scenarios.

2. The Service Exchange Agent system of claim 1 further comprising the Service Exchange Manager that enables conversational communications between Service Exchange Agent systems as well as subject matter experts, while enabling exchange and collaboration of services and service scenarios.

3. The Service Exchange Agent system of claim 1 further comprising the Service and Scenario Registration block, which enables:

registration of services and service scenarios;

conversation via the Service Exchange Manager with a registrar Service Exchange Agent system or a subject matter expert while collecting technical and non-technical artifacts describing a service or a scenario from multiple view points for multiple audiences, like developers, business analysts and other subject matter experts, which might include but is not limited by;

requirements, design patterns, data, process, and architecture model diagrams and descriptions, invocation data, specific service agreement and negotiation terms

creating meta-data, like keywords and key requirements, related to this new service or scenario

sending this meta-data to the network to be stored in the Service and Scenario Registration blocks in each Service Exchange Agent system, providing distributed search resources

4. The Service Exchange Agent system of claim 1 further comprising the Service Knowledge Mapping block, which enables:

semantic association or mapping of multiple types of data to a related service or a scenario

structured navigation across business domains and service descriptions, like business and system requirements provided with human readable language as well as with XML, architecture diagrams and models, design patterns and other technical artifacts

5. The Service Exchange Agent system of claim 1 further comprising the Service and Scenario Composition block, which in collaboration with the Service Exchange Manager enables:

a conversational dialog to;

a requestor to retrieve requirements that might consist of text descriptions, design pattern names, and other technical artifacts

the Service Knowledge Mapping block to interpret and associate requirements and other descriptions or technical artifacts to existing services and business rules

transformation of incoming and associated data into formatted service invocations and business rules, while composing of a new service or a scenario, which consists of service invocations and business rules understood by a targeted service execution engine

saving a composed service or a scenario

registration of newly composed service or a scenario

sending meta-data, like keywords and key requirements, related to this new service or scenario, to the network for all Service Exchange Agent systems

6. The Service Exchange Agent system of claim 1 further comprising the Service Execution Engine, which enables:

in collaboration with the Service Exchange Manager receiving necessary information about a service or scenario for execution

arranging a conversational dialog to a requestor or other Service Exchange Agent systems that might own some services from a scenario for execution and can provide details on scenario fragments

parsing the scenario and in collaboration with the Service Knowledge Mapping block resolving scenario fragments into service calls and business logics, while replacing run-time variables with run-time values

7. The Service Exchange Agent system of claim 1 further comprising the Service Negotiation block, which:

stores service terms, including desired service value ranges, provided by a registrar;

stores a history of service requests and negotiations;

upon each request, re-calculates service values based on service requests, service terms, and history of negotiations;

in collaboration with the Service Exchange Manager converses with the service requestor and service owners while negotiating service terms upon service request;

after pre-defined number of unsuccessful negotiation cycles, notifies subject matter experts with invitation to participate and resolve negotiation issues

8. The Service Exchange Manager of claim 2 further comprising Initiation Ser vices, which enable structured access to services in multiple business domains, service offering, registration, subscription, and execution, consumption, and composition, as well as negotiation of service terms

9. The Initiation Services of claim 8 further comprising but not limited to basic services, like “

List Services”

, “

Search for a Service”

, “

Subscribe to a Service”

, “

Load a Service”

, “

Execute a Service”

, “

Assemble a new service or scenario”

, “

Register a Service”

, etc., which in collaboration with the Service Exchange Manager enable a conversation to a requester and other Service Exchange Agents to retrieve necessary information and satisfy service exchange requests from beginning-to-end;

for example,

the “

List Services”

enables a conversation with a requestor to narrow down the area of requestor interests, starting from business domain names and reveals the main requestor'"'"'s interest factors that might include service requirements, design patterns, or other business or technical considerations captured in the Service Knowledge Mapping block;

the “

Subscribe to a Service”

enables the conversation, which will retrieve the Customer Data, including, for example, but not limited to desired service execution location, specific service data, and scheduling information;

10. The Service Exchange Manager of claim 2 further comprising the Collaborative Work Controller, which enables collaborative work within the Service Exchange Agent system and with other Service Exchange Agents and subject matter experts, for example, when not all components of a requested service or a scenario can be found within a single Service Exchange Agent system

11. The Collaborative Work Controller of claim 10 further comprising Collaborative Work Coordinator criteria, which enable assigning one of the systems a system coordinator, based on criteria, for example, based on relevance to a business domain of a requested service scenario or based on a current system load, where the coordinator system is responsible for initiation and support of conversations and negotiations while in collaborative work with other Service Exchange Agent systems

12. The Service and Scenario Registration block of claim 3 further comprising the Service and Scenario Register Manager and collection blocks, which include for example, but not limited to:

Collector of Technical Artifacts that Reflect Multiple Views, like Design Patterns and Models, Business, Process, and Services diagrams, etc.,

Business Rules Collector,

Invocation Data Collector, Descriptions Collector, etc.,

where each collector block in collaboration with the Service and Scenario Register Manager enables;

data collection in a conversational mode;

interactions with the Service Knowledge Mapping block for data interpretation, translation into proper formats, for example, into formatted business rules, and association or mapping data to a registered service;

checking collected data against collector block'"'"'s rules and criteria;

reporting inconsistency or rule violation to the Service Exchange Manager, which generates and sends to the registrar party a more precise information request that focuses on problematic data

13. The Service Knowledge Mapping block of claim 4 further comprising:

the Service Knowledge Mapping Controller,

the Service and Scenario Knowledgebase,

the Business Domain Maps,

the Integrity Checker,

i. where the Service Knowledge Mapping Controller enables interactions between the Service and Scenario Knowledgebase, the Business Domain Maps, the Integrity Checker, and major Service Exchange Agent system blocks,

ii. the Service and Scenario Knowledgebase enables storage of service descriptions and multiple other artifacts, and provides their mapping with natural language based associative rules;

iii. the Service and Scenario Knowledgebase in collaboration with the Service Knowledge Mapping Controller and the Service Exchange Manager enables conversational dialog with natural language elements between the Service Exchange Agent system blocks and subject matter experts or other Service Exchange Agent systems;

iv. the Business Domain Maps block defines business domains of registered services, for example, in the Topic Maps format, and enables conversational structured access to services by providing to distributed Service Exchange Agent systems meta-data about business domain and brief descriptions of related services;

v. the Integrity Checker enables checking of data association consistency and it is triggered each time when a new rule or association is stored;

vi. if one association or a rule is in conflict with another association or a rule, the Integrity Checker reports to the Service Knowledge Mapping Controller and back to the Service Exchange Manager, which communicates to another party a message that will focus on a problem area to retrieve more data to resolve a conflict

14. The Scenario and Service Composition block of claim 5 further comprising:

the Assembly Manager,

the Requirements Collector,

the Composite Service Assembler,

the Business Rules Assembler;

where;

the Assembly Manager enables interactions between the Requirements Collector, the Composite Service Assembler, the Business Rules Assembler, and other blocks of the Service Exchange Agent system, like the Service Exchange Manager, and the Services Knowledge Mapping block;

the Requirements Collector, in collaboration with the Assembly Manager, enables collection of requirements and separation of description information from invocation data and business rules;

the Composite Service Assembler, enables transformation of invocation data into properly formatted composite service scenario that can include business rules or references to business rules and can be executed by the targeted service execution engine;

the Business Rules Assembler, enables transformation of business logics descriptions into properly formatted business rules

15. The Business Rules Assembler of claim 14 enables association or integration of new rules with the existing set of rules in the Service and Scenario Knowledgebase and in collaboration with the Integrity Checker of claim 13 enables checking of data association consistency

16. The Service Exchange Agent system of claim 1 further comprising the Service Execution Engine, which enables parsing the composite service scenario and in collaboration with the Service Knowledge Mapping block resolving scenario fragments into service calls and business logics, while replacing run-time variables with run-time values and executing services and service scenarios

17. The Service Exchange Agent system of claim 1 further comprising the Service Negotiation block, which enables:

saving service terms, including desired service value range;

tracking service requests and calculation of service values based on demand, service terms, and previous negotiations;

negotiations of service terms and values, where it starts with rule-based computerized negotiations between Service Exchange Agents, and after pre-defined number of negotiation cycles, the Service Exchange Agent coordinator system will send a request to subject matter experts to participate and resolve the issues