# US 2025/0094246 A1 · Metadata-Driven Rapid Adapter Building

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

- Number: US 2025/0094246 A1
- Document ID: US20250094246A1
- Status: Published application
- Kind: A1
- Application number: 18/612,994
- Filed: 2024-03-21
- Published: 2025-03-20
- Earliest claimed: 2023-09-15
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Tuck Chang; Ravi Sankaran; Srimant Misra; Ankur Prakash; Zhengming Zhang; Anuj Kaushal; Sagar Shirguppi; Sumit Aneja; Tian Ma; Paul Lan
- Web page: https://patentgrep.com/patent/US20250094246A1

## CPC

- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques for metadata-driven rapid adapter building (RAB) are disclosed, including: receiving, by an RAB framework, a function call from a third-party application; obtaining, by the RAB framework, a metadata document that defines an adapter between a server-side runtime and the third-party application; determining that the metadata document includes one or more metadata fields that map the function call to one or more software development kit (SDK) functions exposed by the server-side runtime; responsive to receiving the function call and based on the one or more metadata fields, executing the one or more SDK functions exposed by the server-side runtime.

## Claims

### Claim 1

One or more non-transitory computer-readable media storing instructions which, when executed by one or more hardware processors, cause performance of operations comprising:
receiving, by a rapid adapter building (RAB) framework, a function call from a third-party application;
obtaining, by the RAB framework, a metadata document that defines an adapter between a server-side runtime and the third-party application;
determining that the metadata document comprises one or more metadata fields that map the function call to one or more software development kit (SDK) functions exposed by the server-side runtime;
responsive to receiving the function call and based on the one or more metadata fields, executing the one or more SDK functions exposed by the server-side runtime.

### Claim 2 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the operations further comprising:
determining that the metadata document defines a set of relationships between metadata fields in the metadata document;
generating a design-time user interface, for configuring the adapter, based at least on the set of relationships defined by the metadata document;
configuring the adapter based at least on user input received via the design-time user interface.

### Claim 3 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the operations further comprising:
based on the one or more metadata fields, transforming data received in the function call from (a) a first format used by the third-party application to (b) a second format used by the server-side runtime.

### Claim 4 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the operations further comprising:
obtaining an output of the one or more SDK functions exposed by the server-side runtime;
returning the output to the third-party application responsive to receiving the function call.

### Claim 5 (depends on 4)

The one or more non-transitory computer-readable media of claim 4, the operations further comprising:
based on the one or more metadata fields, transforming the output of the one or more SDK functions exposed by the server-side runtime from (a) a first format used by the server-side runtime to (b) a second format used by the third-party application.

### Claim 6 (depends on 4)

The one or more non-transitory computer-readable media of claim 4, the operations further comprising:
based on the one or more metadata fields, enriching the output of the one or more SDK functions with additional data not supplied by the one or more SDK functions.

### Claim 7 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, wherein the metadata document is a JavaScript Object Notation (JSON) document.

### Claim 8

A system comprising:
one or more hardware processors;
one or more non-transitory computer-readable media; and
program instructions stored on the one or more non-transitory computer readable media which, when executed by the one or more hardware processors, cause the system to perform operations comprising:
receiving, by a rapid adapter building (RAB) framework, a function call from a third-party application;
obtaining, by the RAB framework, a metadata document that defines an adapter between a server-side runtime and the third-party application;
determining that the metadata document comprises one or more metadata fields that map the function call to one or more software development kit (SDK) functions exposed by the server-side runtime;
responsive to receiving the function call and based on the one or more metadata fields, executing the one or more SDK functions exposed by the server-side runtime.

### Claim 9 (depends on 8)

The system of claim 8, the operations further comprising:
determining that the metadata document defines a set of relationships between metadata fields in the metadata document;
generating a design-time user interface, for configuring the adapter, based at least on the set of relationships defined by the metadata document;
configuring the adapter based at least on user input received via the design-time user interface.

### Claim 10 (depends on 8)

The system of claim 8, the operations further comprising:
based on the one or more metadata fields, transforming data received in the function call from (a) a first format used by the third-party application to (b) a second format used by the server-side runtime.

### Claim 11 (depends on 8)

The system of claim 8, the operations further comprising:
obtaining an output of the one or more SDK functions exposed by the server-side runtime;
returning the output to the third-party application responsive to receiving the function call.

### Claim 12 (depends on 11)

The system of claim 11, the operations further comprising:
based on the one or more metadata fields, transforming the output of the one or more SDK functions exposed by the server-side runtime from (a) a first format used by the server-side runtime to (b) a second format used by the third-party application.

### Claim 13 (depends on 11)

The system of claim 11, the operations further comprising:
based on the one or more metadata fields, enriching the output of the one or more SDK functions with additional data not supplied by the one or more SDK functions.

### Claim 14 (depends on 8)

The system of claim 8, wherein the metadata document is a JavaScript Object Notation (JSON) document.

### Claim 15

A method comprising:
receiving, by a rapid adapter building (RAB) framework, a function call from a third-party application;
obtaining, by the RAB framework, a metadata document that defines an adapter between a server-side runtime and the third-party application;
determining that the metadata document comprises one or more metadata fields that map the function call to one or more software development kit (SDK) functions exposed by the server-side runtime;
responsive to receiving the function call and based on the one or more metadata fields, executing the one or more SDK functions exposed by the server-side runtime;
wherein the method is performed by at least one device including a hardware processor.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
determining that the metadata document defines a set of relationships between metadata fields in the metadata document;
generating a design-time user interface, for configuring the adapter, based at least on the set of relationships defined by the metadata document;
configuring the adapter based at least on user input received via the design-time user interface.

### Claim 17 (depends on 15)

The method of claim 15, further comprising:
based on the one or more metadata fields, transforming data received in the function call from (a) a first format used by the third-party application to (b) a second format used by the server-side runtime.

### Claim 18 (depends on 15)

The method of claim 15, further comprising:
obtaining an output of the one or more SDK functions exposed by the server-side runtime;
returning the output to the third-party application responsive to receiving the function call.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
based on the one or more metadata fields, transforming the output of the one or more SDK functions exposed by the server-side runtime from (a) a first format used by the server-side runtime to (b) a second format used by the third-party application.

### Claim 20 (depends on 18)

The method of claim 18, further comprising:
based on the one or more metadata fields, enriching the output of the one or more SDK functions with additional data not supplied by the one or more SDK functions.
