# US 2019/0317845 A1 · Device based automated tool integration for lifecycle management platform

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

- Number: US 2019/0317845 A1
- Document ID: US20190317845A1
- Status: Published application
- Kind: A1
- Application number: 16/456,501
- Filed: 2019-06-28
- Published: 2019-10-17
- Earliest claimed: 2016-04-12
- Assignees: Accenture Global Solutions Limited
- Applicants: Accenture Global Solutions Limited
- Inventors: Krupa Srivastava; Vijayaraghavan Koushik; Chandrashekhar Deshpande; Mark Lazarus; Le G. Dang; Madhusudhana Desai; Sumit Kute; Arpan Shukla; Tiarenla Jamir; Prashant Sawant; Rohan Sharma; Bhaskar Ghosh; Mohan Sekhar; Rajendra T. Prasad
- Web page: https://patentgrep.com/patent/US20190317845A1

## CPC

- G06F 9/545: {where tasks reside in different layers, e.g. user- and kernel-space}
- G06F 8/70: Software maintenance or management
- G06F 9/451: Execution arrangements for user interfaces
- G06F 9/45504: {Abstract machines for program code execution, e.g. Java virtual machine [JVM], interpreters or emulators}
- G06F 9/45533: {Hypervisors; Virtual machine monitors}
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 8/36: Software reuse
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A device may identify a tool operating on a first device for integration into a lifecycle management platform operating on a second device. The tool may be associated with providing a functionality not included in the lifecycle management platform. The first device may be external to the second device. The device may determine a set of tool attributes for data events associated with the tool. The data events may include a data input, a data output, a new message, an updated message, a deleted message, or the like. The device may select a message format based on the set of tool attributes. The device may configure adaptation for a tool application programming interface (API) of the tool and a platform API of the lifecycle management platform based on the message format. The device may provide information associated with configuring adaptation for the tool API and the platform API.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method comprising:
receiving, by a first device, a message from a second device;
identifying, by the first device, a first adapter for the message;
using, by the first device, the first adapter to convert the message to a first particular format;
outputting, by the first device, an adapted message to a third device,
the adapted message being the message converted to the first particular format;
receiving, by the first device, from the third device, and based on outputting the adapted message, a response message;
identifying, by the first device, a second adapter for the response message;
using, by the first device, the second adapter to convert the response message to a second particular format; and
outputting, by the first device via an application programming interface (API) of the second device, an adapted response message to the second device,
the adapted response message being the response message converted to the second particular format.

### Claim 22 (depends on 21)

The method of claim 21, further comprising:
exposing an interface of the first device; and
wherein receiving the message from the second device comprises:
receiving, based on exposing the interface, the message from the second device.

### Claim 23 (depends on 21)

The method of claim 21, further comprising:
performing a verification of the message based on receiving the message from the second device; and
wherein using the first adapter to convert the message comprises:
using, based on performing the verification of the message, the first adapter to convert the message.

### Claim 24 (depends on 23)

The method of claim 23, wherein performing the verification of the message comprises:
performing the verification of the message based on at least one of:
a source of the message,
a type of the message,
a security token included in the message,
project details associated with the message, or
an identifier of the message.

### Claim 25 (depends on 21)

The method of claim 21, wherein the message is a defect message; and
wherein the method further comprises:
verifying that the defect message is from an authorized source to publish a defect; and
wherein using the first adapter to convert the message comprises:
using, based on verifying that the defect message is from the authorized source, the first adapter to convert the defect message.

### Claim 26 (depends on 25)

The method of claim 25, wherein verifying that the defect message is from the authorized source comprises:
verifying at least one of:
an Internet Protocol (IP) address corresponding to the authorized source,
a network identifier corresponding to the authorized source,
a user name corresponding to the authorized source, or
a password corresponding to the authorized source.

### Claim 27 (depends on 21)

The method of claim 21, wherein the message comprises data encapsulated by the API.

### Claim 28

A first device, comprising:
one or more memories; and
one or more processors communicatively coupled to the one or more memories, configured to:
receive a message from a second device;
identify a first adapter for the message;
use the first adapter to convert the message to a first particular format;
output an adapted message to a third device,
the adapted message being the message converted to the first particular format;
receive, from the third device and based on outputting the adapted message, a response message;
identify a second adapter for the response message;
use the second adapter to convert the response message to a second particular format; and
output an adapted response message to the second device,
the adapted response message being the response message converted to the second particular format, and
the adapted response message being received, by the second device, via an application programming interface (API) of the second device.

### Claim 29 (depends on 28)

The first device of claim 28, wherein the one or more processors are further configured to:
expose an interface of the first device; and
wherein the one or more processors, when receiving the message from the second device, are configured to:
receive, based on exposing the interface, the message from the second device.

### Claim 30 (depends on 28)

The first device of claim 28, wherein the one or more processors are further configured to:
perform a verification of the message based on receiving the message from the second device; and
wherein the one or more processors, when using the first adapter to convert the message, are configured to:
use, based on performing the verification of the message, the first adapter to convert the message.

### Claim 31 (depends on 30)

The first device of claim 30, wherein the one or more processors, when performing the verification of the message, are configured to:
perform the verification of the message based on at least one of:
a source of the message,
a type of the message,
a security token included in the message,
project details associated with the message, or
an identifier of the message.

### Claim 32 (depends on 28)

The first device of claim 28, wherein the message is a defect message; and
wherein the one or more processors further configured to:
verify that the defect message is from an authorized source to publish a defect; and
wherein the one or more processors, when using the first adapter to convert the message, are configured to:
use, based on verifying that the defect message is from the authorized source, the first adapter to convert the defect message.

### Claim 33 (depends on 32)

The first device of claim 32, wherein the one or more processors, when verifying that the defect message is from the authorized source, are configured to:
verify at least one of:
an Internet Protocol (IP) address corresponding to the authorized source,
a network identifier corresponding to the authorized source,
a user name corresponding to the authorized source, or
a password corresponding to the authorized source.

### Claim 34 (depends on 28)

The first device of claim 28, wherein the message comprises on data encapsulated by the API.

### Claim 35

A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors of a first device, cause the one or more processors to:
receive a message from a second device;
identify a first adapter for the message;
use the first adapter to convert the message to a first particular format;
output an adapted message to a third device,
the adapted message being the message converted to the first particular format;
receive, from the third device, and based on outputting the adapted message, a response message;
identify a second adapter for the response message;
use the second adapter to convert the response message to a second particular format; and
output an adapted response message to the second device,
the adapted response message being the response message converted to the second particular format, and
the adapted response message being received, by the second device, via an application programming interface (API) of the second device.

### Claim 36 (depends on 35)

The non-transitory computer-readable medium of claim 35, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
expose an interface of the first device; and
wherein the one or more instructions, that cause the one or more processors to receive the message from the second device, cause the one or more processors to:
receive, based on exposing the interface, the message from the second device.

### Claim 37 (depends on 35)

The non-transitory computer-readable medium of claim 35, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
perform a verification of the message based on receiving the message from the second device; and
wherein the one or more instructions, that cause the one or more processors to use the first adapter to convert the message, cause the one or more processors to:
use, based on performing the verification of the message, the first adapter to convert the message.

### Claim 38 (depends on 37)

The non-transitory computer-readable medium of claim 37, wherein the one or more instructions, that cause the one or more processors to perform the verification of the message, cause the one or more processors to:
perform the verification of the message based on at least one of:
a source of the message,
a type of the message,
a security token included in the message,
project details associated with the message, or
an identifier of the message.

### Claim 39 (depends on 35)

The non-transitory computer-readable medium of claim 35, wherein the message is a defect message; and
wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to:
verify that the defect message is from an authorized source to publish a defect; and
wherein the one or more instructions, that cause the one or more processors to use the first adapter to convert the message, cause the one or more processors to:
use, based on verifying that the defect message is from the authorized source, the first adapter to convert the defect message.

### Claim 40 (depends on 39)

The non-transitory computer-readable medium of claim 39, wherein the one or more instructions, that cause the one or more processors to verify that the defect message is from the authorized source, cause the one or more processors to:
verify at least one of:
an Internet Protocol (IP) address corresponding to the authorized source,
a network identifier corresponding to the authorized source,
a user name corresponding to the authorized source, or
a password corresponding to the authorized source.