# US 2025/0168253 A1 · Open resource discovery of entity types

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

- Number: US 2025/0168253 A1
- Document ID: US20250168253A1
- Status: Published application
- Kind: A1
- Application number: 18/511,338
- Filed: 2023-11-16
- Published: 2025-05-22
- Earliest claimed: 2023-11-16
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Simon Heimler; Sebastian Wennemers
- Web page: https://patentgrep.com/patent/US20250168253A1

## CPC

- H04L 67/561: Adding application-functional data or data for application control, e.g. adding metadata
- G06F 16/252: {between a Database Management System and a front-end application}
- 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

The disclosure generally describes methods, software, and systems for open resource discovery protocol describing entity types. An identifier of a first entity type is received. The first entity type defines a relation between an application programming interface (API) and event information. A reference for the first entity type is generated based on the identifier of the first entity type. The reference links the first entity type to the API. A description of the first entity type is provided for storage using the reference for the first entity type. the description includes a structure of an underlying data model. A request to provide the first entity type based on the description of the first entity type is received. The first entity type is provided using an exposed API and the reference for the first entity type.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving, by one or more processors, an identifier of a first entity type, the first entity type defining a relation between an application programming interface (API) and event information;
generating, by the one or more processors, based on the identifier of the first entity type, a reference for the first entity type, the reference linking the first entity type to the API;
providing, by the one or more processors, a description of the first entity type for storage using the reference for the first entity type, the description comprising a structure of an underlying data model;
receiving, by the one or more processors, a request to provide the first entity type based on the description of the first entity type; and
in response to the received request, providing, by the one or more processors, the first entity type using an exposed API and the reference for the first entity type.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising:
generating, by the one or more processors, a mapping of the first entity type to a second entity type.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, wherein the mapping comprises information indicative of local data models that are supported by the first entity type and the second entity type.

### Claim 4 (depends on 2)

The computer-implemented method of claim 2, further comprising:
deriving, by the one or more processors, a data flow based on the mapping of the first entity type to the second entity type.

### Claim 5 (depends on 2)

The computer-implemented method of claim 2, wherein the first entity type comprises a root entity and the second entity type comprises a sub-entity.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the underlying data model is stored as metadata information.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the reference comprises external files or locations.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the description comprises properties of the first entity type and data types the first entity type.

### Claim 9

A computer-implemented system comprising:
a memory storing application programming interface (API) information; and
a server performing operations comprising:
receiving an identifier of a first entity type, the first entity type defining a relation between an application programming interface (API) and event information;
generating based on the identifier of the first entity type, a reference for the first entity type, the reference linking the first entity type to the API;
providing a description of the first entity type for storage using the reference for the first entity type, the description comprising a structure of an underlying data model;
receiving a request to provide the first entity type based on the description of the first entity type; and
in response to the received request, providing the first entity type using an exposed API and the reference for the first entity type.

### Claim 10 (depends on 9)

The computer-implemented system of claim 9, wherein the operations further comprise:
generating a mapping of the first entity type to a second entity type.

### Claim 11 (depends on 10)

The computer-implemented system of claim 10, wherein the mapping comprises information indicative of local data models that are supported by the first entity type and the second entity type.

### Claim 12 (depends on 10)

The computer-implemented system of claim 10, wherein the operations further comprise:
deriving a data flow based on the mapping of the first entity type to the second entity type.

### Claim 13 (depends on 10)

The computer-implemented system of claim 10, wherein the first entity type comprises a root entity and the second entity type comprises a sub-entity.

### Claim 14 (depends on 9)

The computer-implemented system of claim 9, wherein the underlying data model is stored as metadata information.

### Claim 15 (depends on 9)

The computer-implemented system of claim 9, wherein the reference comprises external files or locations.

### Claim 16 (depends on 9)

The computer-implemented system of claim 9, wherein the description comprises properties of the first entity type and data types the first entity type.

### Claim 17

A non-transitory computer-readable media encoded with a computer program, the computer program comprising instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:
receiving an identifier of a first entity type, the first entity type defining a relation between an application programming interface (API) and event information;
generating based on the identifier of the first entity type, a reference for the first entity type, the reference linking the first entity type to the API;
providing a description of the first entity type for storage using the reference for the first entity type, the description comprising a structure of an underlying data model;
receiving a request to provide the first entity type based on the description of the first entity type; and
in response to the received request, providing the first entity type using an exposed API and the reference for the first entity type.

### Claim 18 (depends on 17)

The non-transitory computer-readable media of claim 17, wherein the operations further comprise:
generating a mapping of the first entity type to a second entity type, wherein the mapping comprises information indicative of local data models that are supported by the first entity type and the second entity type.

### Claim 19 (depends on 17)

The non-transitory computer-readable media of claim 17, wherein the underlying data model is stored as metadata information.

### Claim 20 (depends on 17)

The non-transitory computer-readable media of claim 17, wherein the description comprises properties of the first entity type and data types the first entity type.
