# US 2023/0068545 A1 · Service cooperation support apparatus, service cooperation support method and service cooperation support program

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

- Number: US 2023/0068545 A1
- Document ID: US20230068545A1
- Status: Published application
- Kind: A1
- Application number: 17/797,535
- Filed: 2020-02-06
- Published: 2023-03-02
- Earliest claimed: 2020-02-06
- Assignees: Nippon Telegraph and Telephone Corporation
- Applicants: Nippon Telegraph and Telephone Corporation
- Inventors: Ryota KATAYANAGI; Kensuke TAKAHASHI; Satoshi KONDO
- Web page: https://patentgrep.com/patent/US20230068545A1

## CPC

- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/545: {where tasks reside in different layers, e.g. user- and kernel-space}
- G06F 9/44: Arrangements for executing specific programs
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A service linkage assistance device includes a reception unit, which receives definition information of a stateless upper-layer API exposed to an upper-layer device that links a plurality of services and definition information of a plurality of stateful lower-layer APIs exposed by a lower-layer device. The service linkage assistance device includes an interpretation unit, which extracts at least one lower-layer API corresponding to the upper-layer API by using the definition information of the upper-layer API and the definition information of the lower-layer APIs, and generates an API correspondence table in which an execution order of the extracted lower-layer API is set.

## Claims

### Claim 1

A service linkage assistance device comprising:
a reception unit, implemented with one or more processors, configured to receive definition information of a stateless upper-layer Application Programming Interface (API) exposed to an upper-layer device that links a plurality of services and definition information of a plurality of stateful lower-layer APIs exposed by a lower-layer device; and
an interpretation unit, implemented with one or more processors, configured to extract at least one lower-layer API corresponding to the upper-layer API by using the definition information of the upper-layer API and the definition information of the lower-layer APIs, and to generate an API correspondence table in which an execution order of the extracted lower-layer API is set.

### Claim 2 (depends on 1)

The service linkage assistance device according to claim 1,
wherein the interpretation unit extracts a lower-layer API that outputs output information of the upper-layer API and, in a case where input information of the extracted lower-layer API has only input information of the upper-layer API, an execution order of the lower-layer API is given priority over an execution order of another lower-layer API by the interpretation unit.

### Claim 3 (depends on 1)

The service linkage assistance device according to claim 1,
wherein the reception unit receives definition information of an internal state that is provided by notification when the lower-layer API is executed, and the interpretation unit generates the API correspondence table by using the definition information of the internal state.

### Claim 4 (depends on 1)

The service linkage assistance device according to claim 1, further comprising:
an execution unit configured to identify a stateful lower-layer API corresponding to an upper-layer API by using the API correspondence table in response to a request from the upper-layer device, and to execute the identified lower-layer API in an order specified by the API correspondence table; and
a storage unit configured to store an internal state included in a response of the lower-layer API.

### Claim 5

A service linkage assistance method performed by a service linkage assistance device, the service linkage assistance method comprising:
receiving definition information of a stateless upper-layer API exposed to an upper-layer device that links a plurality of services and definition information of a plurality of stateful lower-layer APIs exposed by a lower-layer device; and
extracting at least one lower-layer API corresponding to the upper-layer API by using the definition information of the upper-layer API and the definition information of the lower-layer APIs, and generating an API correspondence table in which an execution order of the extracted lower-layer API is set.

### Claim 6 (depends on 5)

The service linkage assistance method according to claim 5, further comprising:
identifying a stateful lower-layer API corresponding to an upper-layer API by using the API correspondence table in response to a request from the upper-layer device, and executing the identified lower-layer API in an order specified by the API correspondence table; and
storing an internal state included in a response of the lower-layer API.

### Claim 7 (depends on 5)

The service linkage assistance method according to claim 5, wherein definition information of an internal state that is provided by notification when the lower-layer API is executed is received in the receiving definition information of a stateless upper-layer API, and the API correspondence table is generated by using the definition information of the internal state in the extracting at least one lower-layer API corresponding to the upper-layer API.

### Claim 8

(canceled)

### Claim 9

A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving definition information of a stateless upper-layer API exposed to an upper-layer device that links a plurality of services and definition information of a plurality of stateful lower-layer APIs exposed by a lower-layer device; and
extracting at least one lower-layer API corresponding to the upper-layer API by using the definition information of the upper-layer API and the definition information of the lower-layer APIs, and generating an API correspondence table in which an execution order of the extracted lower-layer API is set.
