# US 2025/0097305 A1 · Framework to resolve protocol endpoints in integration platform

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

- Number: US 2025/0097305 A1
- Document ID: US20250097305A1
- Status: Published application
- Kind: A1
- Application number: 18/466,990
- Filed: 2023-09-14
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Bhagyesh HEDE; Shankara Prasad K; Subhankar CHATTOPADHYAY; Ghanshyam Prasad ARVIND
- Web page: https://patentgrep.com/patent/US20250097305A1

## CPC

- H04L 67/147: Signalling methods or messages providing extensions to protocols defined by standardisation
- H04L 47/20: Traffic policing
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 69/22: Parsing or analysis of headers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An ingress component may receive, from a client, an HTTP URL and HTTP header information for an incoming protocol message (e.g., an AS2 message). An endpoint selector may determine the HTTP header information along with an endpoint address associated with the incoming protocol message. Based on the incoming HTTP header information and the endpoint address of the incoming protocol message, the endpoint selector may dynamically resolve an appropriate deployed endpoint and output an indication of the dynamically resolved appropriate deployed endpoint. A runtime component of an integration platform can then execute the incoming protocol message and interface with the appropriate deployed endpoint.

## Claims

### Claim 1

A system, comprising:
an ingress component to receive, from a client, a HyperText Transfer Protocol (“HTTP”) Uniform Resource Locator (“URL”) and HTTP header information for an incoming protocol message;
an endpoint selector, including:
a computer processor, and
a computer memory coupled to the computer processor and storing instructions that, when executed by the computer processor, cause the endpoint selector to:
determine the HTTP header information,
determine an endpoint address associated with the incoming protocol message,
based on the incoming HTTP header information and the endpoint address of the incoming protocol message, dynamically resolve an appropriate deployed endpoint, and
output an indication of the dynamically resolved appropriate deployed endpoint; and
a runtime component of an integration platform, coupled to the ingress component, to execute the incoming protocol message and interface with the appropriate deployed endpoint.

### Claim 2 (depends on 1)

The system of claim 1, wherein the ingress component is an Application Programming Interface (“API”) gateway processor.

### Claim 3 (depends on 2)

The system of claim 2, wherein the ingress component is further to set a traffic rate limit and implement an authentication policy.

### Claim 4 (depends on 1)

The system of claim 1, wherein the incoming protocol message is associated with the Applicability Statement 2 (“AS2”) protocol.

### Claim 5 (depends on 4)

The system of claim 4, wherein the HTTP header information includes: (i) an AS2 “from” address, (ii) an AS2 “to” address, (iii) a subject, and (iv) an AS2 identifier.

### Claim 6 (depends on 1)

The system of claim 1, wherein the incoming protocol message is associated with one of: (i) the Applicability Statement 4 (“AS4”) protocol, and (ii) the Open Data (“OData”) protocol.

### Claim 7 (depends on 1)

The system of claim 1, wherein the HTTP URL and HTTP header information define an endpoint proxy and the appropriate deployed endpoint is associated with a sender channel.

### Claim 8

A method, comprising:
receiving, by an ingress component from a client, a HyperText Transfer Protocol (“HTTP”) Uniform Resource Locator (“URL”) and HTTP header information for an incoming protocol message;
determining, by a computer processor of an endpoint selector, the HTTP header information;
determining, by the computer processor, an endpoint address associated with the incoming protocol message;
based on the incoming HTTP header information and the endpoint address of the incoming protocol message, dynamically resolving, by the computer processor, an appropriate deployed endpoint;
outputting, by the computer processor, an indication of the dynamically resolved appropriate deployed endpoint; and
executing, by a runtime component of an integration platform coupled to the ingress component, the incoming protocol message by interfacing with the appropriate deployed endpoint.

### Claim 9 (depends on 8)

The method of claim 8, wherein the ingress component is an Application Programming Interface (“API”) gateway processor.

### Claim 10 (depends on 9)

The method of claim 9, wherein the ingress component is further to set a traffic rate limit and implement an authentication policy.

### Claim 11 (depends on 8)

The method of claim 8, wherein the incoming protocol message is associated with the Applicability Statement 2 (“AS2”) protocol.

### Claim 12 (depends on 11)

The method of claim 11, wherein the HTTP header information includes: (i) an AS2 “from” address, (ii) an AS2 “to” address, (iii) a subject, and (iv) an AS2 identifier.

### Claim 13 (depends on 8)

The method of claim 8, wherein the incoming protocol message is associated with one of: (i) the Applicability Statement 4 (“AS4”) protocol, and (ii) the Open Data (“OData”) protocol.

### Claim 14 (depends on 8)

The method of claim 8, wherein the HTTP URL and HTTP header information define an endpoint proxy and the appropriate deployed endpoint is associated with a sender channel.

### Claim 15

A non-transitory, machine-readable medium comprising instructions thereon that, when executed by a processor, cause the processor to execute operations to perform a method, the method comprising:
receiving, by an ingress component from a client, a HyperText Transfer Protocol (“HTTP”) Uniform Resource Locator (“URL”) and HTTP header information for an incoming protocol message;
determining, by a computer processor of an endpoint selector, the HTTP header information;
determining, by the computer processor, an endpoint address associated with the incoming protocol message;
based on the incoming HTTP header information and the endpoint address of the incoming protocol message, dynamically resolving, by the computer processor, an appropriate deployed endpoint;
outputting, by the computer processor, an indication of the dynamically resolved appropriate deployed endpoint; and
executing, by a runtime component of an integration platform coupled to the ingress component, the incoming protocol message by interfacing with the appropriate deployed endpoint.

### Claim 16 (depends on 15)

The medium of claim 15, wherein the ingress component is an Application Programming Interface (“API”) gateway processor.

### Claim 17 (depends on 16)

The medium of claim 16, wherein the ingress component is further to set a traffic rate limit and implement an authentication policy.

### Claim 18 (depends on 15)

The medium of claim 15, wherein the incoming protocol message is associated with the Applicability Statement 2 (“AS2”) protocol.

### Claim 19 (depends on 18)

The medium of claim 18, wherein the HTTP header information includes: (i) an AS2 “from” address, (ii) an AS2 “to” address, (iii) a subject, and (iv) an AS2 identifier.

### Claim 20 (depends on 15)

The medium of claim 15, wherein the incoming protocol message is associated with one of: (i) the Applicability Statement 4 (“AS4”) protocol, and (ii) the Open Data (“OData”) protocol.

### Claim 21 (depends on 15)

The medium of claim 15, wherein the HTTP URL and HTTP header information define an endpoint proxy and the appropriate deployed endpoint is associated with a sender channel.
