Semantic Matching of Federation Intents and Services Capabilities in a Planning System for Automatic Service Federation

• US 20110238795A1
• Filed: 03/26/2010
• Published: 09/29/2011
• Est. Priority Date: 03/26/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bauer, Daniel, Yang, Hao, Dragicevic, Kristijan, Garces-Erice, Luis, Kim, Minkyong, Lei, Hui
• Granted Patent: US 8,250,185 B2
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers

Abstract

A method, device, and computer program product are provided for automatically generating connectivity configuration between domains by a device. A rule is received by the device. The rule is read by the device to determine a first domain invoking a service, a second domain having the service, and connectivity requirements for the first and second domains. A first proxy and a second proxy are automatically determined to fulfill the rule by the device. The first proxy is automatically assigned to the first domain and the second proxy is automatically assigned to the second domain.

Claims

1. A method for automatically generating connectivity configuration between domains by a device, comprising:

receiving a rule by the device;

reading the rule to determine a first domain invoking a service, a second domain having the service, and connectivity requirements for the first and second domains by the device;

automatically determining a first proxy and a second proxy to fulfill the rule by the device; and

automatically assigning the first proxy to the first domain and the second proxy to the second domain.

2. The method of claim 1, wherein automatically determining the first proxy and the second proxy to fulfill the rule by the device comprises:

matching a first proxy pattern of the first proxy to the rule; and

matching a second proxy pattern of the second proxy to the rule.

3. The method of claim 1, further comprising deploying the first proxy in the first domain and deploying the second proxy in the second domain;

wherein the first proxy and the second proxy are configured to fulfill connectivity requirements specified in the rule.

4. The method of claim 1, further comprising performing a semantic compatibility check.

5. The method of claim 4, wherein the semantic compatibility check comprises comparing the first proxy pattern to the second proxy pattern to determine if the first and second proxy patterns are semantically incompatible.

6. The method of claim 5, wherein in response to determining that the first and second proxy patterns are semantically incompatible, the device discontinues a configuration for the first and second domains.

7. The method of claim 4, wherein the semantic compatibility check comprises comparing both the first proxy pattern and the second proxy pattern to the service to determine if at least one of the first and second proxy patterns are semantically incompatible to the service.

8. The method of claim 7, wherein in response to determining that the at least one of the first and second proxy patterns are semantically incompatible to the service, the device discontinues a configuration for the first and second domains.

9. The method of claim 4, wherein a knowledge base stores semantic information for the semantic compatibility check.

10. The method of claim 2, further comprising determining if a functionally of any proxy pattern is redundant to the first proxy pattern;

and

in response to functionally of the proxy pattern being redundant to the first proxy pattern, discarding the proxy pattern.

11. The method of claim 2, further comprising determining if a functionally of any proxy pattern is redundant to the second proxy pattern;

and

in response to functionally of the proxy pattern being redundant to the second proxy pattern discarding the proxy pattern.

12. The method of claim 2, further comprising determining if the service is redundant to the first and second proxy patterns.

13. The method of claim 12, further comprising in response to the service being redundant to the first and second proxy patterns, discarding the first and second proxy patterns.

14. The method of claim 1, wherein the first and second domains represent a plurality of domains;

and

wherein the first and second proxies represent a plurality of proxies.

15. A computing device configured to automatically generate connectivity configuration between domains, comprising:

memory for storing a program; and

a processor, functionally coupled to the memory, the processor being responsive to computer-executable instructions contained in the program and operative for;

receiving a rule;

reading the rule to determine a first domain invoking a service, a second domain having the service, and connectivity requirements for the first and second domains;

automatically determining a first proxy and a second proxy to fulfill the rule; and

automatically assigning the first proxy to the first domain and the second proxy to the second domain.

16. The device of claim 15, wherein automatically determining the first proxy and the second proxy to fulfill the rule by the device comprises:

matching a first proxy pattern of the first proxy to the rule; and

matching a second proxy pattern of the second proxy to the rule.

17. The device of claim 15, further comprising deploying the first proxy in the first domain and deploying the second proxy in the second domain;

wherein the first proxy and the second proxy are configured to fulfill connectivity requirements specified in the rule.

18. The device of claim 15, further comprising performing a semantic compatibility check.

19. The device of claim 18, wherein the semantic compatibility check comprises comparing the first proxy pattern to the second proxy pattern to determine if the first and second proxy patterns are semantically incompatible.

20. A computer program product, tangibly embodied on a computer readable medium, the computer program product including instructions for causing a computer to execute a method for automatically generating connectivity configuration between domains by a device, comprising:

receiving a rule;

reading the rule to determine a first domain invoking a service, a second domain having the service, and connectivity requirements for the first and second domains;

automatically determining a first proxy and a second proxy to fulfill the rule; and

automatically assigning the first proxy to the first domain and the second proxy to the second domain.