# US 2013/0254335 A1 · Inter-domain replication of service information

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254335 A1
- Document ID: US20130254335A1
- Status: Published application
- Kind: A1
- Application number: 13/890,820
- Filed: 2013-05-09
- Published: 2013-09-26
- Earliest claimed: 2012-03-20
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Shigemitsu Inoue; Yohsuke Ishii; Koichi Nakamura
- Web page: https://patentgrep.com/patent/US20130254335A1

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06F 16/258: {Data format conversion from or to a database}
- H04L 41/0246: Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L 41/50: Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L 63/02: {for separating internal from external traffic, e.g. firewalls}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An automated conversion of service information between independent information technology (IT) management domains is performed using a federated gateway within each of the independent IT management domains that bridges the independent IT management domains. The automated conversion of service information allows at least one service consumer application executing within a first independent IT management domain to use a local service definition format to access at least one remote service provider application with a remote service interface defined using a different remote service definition format for execution in a second independent IT management domain. At least one service request is dynamically processed for the at least one remote service provider application via service provider application endpoint translation using the federated gateway within each of the independent IT management domains that bridges the independent IT management domains.

## Claims

### Claim 1

A method, comprising:
performing an automated conversion of service information between independent information technology (IT) management domains using a federated gateway within each of the independent IT management domains that bridges the independent IT management domains, where the automated conversion of service information allows at least one service consumer application executing within a first independent IT management domain to use a local service definition format to access at least one remote service provider application with a remote service interface defined using a different remote service definition format for execution in a second independent IT management domain; and
dynamically processing at least one service request for the at least one remote service provider application via service provider application endpoint translation using the federated gateway within each of the independent IT management domains that bridges the independent IT management domains.

### Claim 2 (depends on 1)

The method of claim 1, where performing an automated conversion of service information between independent IT management domains using a federated gateway within each of the independent IT management domains that bridges the independent IT management domains comprises:
identifying, via a local governance service registry within the first independent IT management domain, a definition of the at least one remote service provider application within a remote governance service registry within the second independent IT management domain, where the local governance service registry and the remote governance service registry form a federated service registry gateway as part of the federated gateway within each of the independent IT management domains that bridges service registration between the independent IT management domains;
converting the remote service interface to a local service interface defined with the local service definition format; and
registering the local service interface that represents the converted remote service interface within a local runtime service registry accessible by the at least one service consumer application executing within the first independent IT management domain.

### Claim 3 (depends on 2)

The method of claim 2, where converting the remote service interface to a local service interface defined with the local service definition format comprises:
replacing an endpoint address of the at least one remote service provider application within the second independent IT management domain with an endpoint address of the remote governance service registry of the federated gateway; and
re-writing the remote service interface definition to convert from a remote protocol to a local protocol used by the local service interface.

### Claim 4 (depends on 3)

The method of claim 3, where converting the remote service interface to a local service interface defined with the local service definition format further comprises:
replacing remote security policy information used for originating the at least one service request with local security policy information mapped to the remote security policy information via a local access/identity manager and a remote access/identity manager that form a federated security gateway as part of the federated gateway within each of the independent IT management domains that bridges security policy information between the independent IT management domains.

### Claim 5 (depends on 1)

The method of claim 1, where dynamically processing at least one service request for the at least one remote service provider application via service provider application endpoint translation using the federated gateway within each of the independent IT management domains that bridges the independent IT management domains comprises:
routing the at least one service request via a federated enterprise service bus (ESB) comprising a local ESB within the first and a remote ESB within the second independent IT management domains, where the local ESB within the first and the remote ESB within the second independent IT management domains form a federated ESB gateway as part of the federated gateway within each of the independent IT management domains that bridges routing between the independent IT management domains; and
providing connectivity mediation between the independent IT management domains via the federated ESB.

### Claim 6 (depends on 5)

The method of claim 5, where providing connectivity mediation between the independent IT management domains via the federated ESB comprises:
performing token exchange between a security gateway within the federated ESB and a local access/identity manager that forms a portion of a federated security gateway as part of the federated gateway within each of the independent IT management domains that bridges the security policy information between the independent IT management domains.

### Claim 7 (depends on 6)

The method of claim 6, where providing connectivity mediation between the independent IT management domains via the federated ESB further comprises:
performing token exchange between the local access/identity manager and a remote access/identity manager within the second independent IT management domain that forms another portion of the federated security gateway within the federated gateway within each of the independent IT management domains that bridges the security policy information between the independent IT management domains.
