# US 2017/0302754 A1 · Proxy framework, systems and methods for electronic data interchange through information exchange platform

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

- Number: US 2017/0302754 A1
- Document ID: US20170302754A1
- Status: Published application
- Kind: A1
- Application number: 15/487,264
- Filed: 2017-04-13
- Published: 2017-10-19
- Earliest claimed: 2016-04-15
- Assignees: Open Text Gxs Ulc
- Applicants: Open Text GXS ULC
- Inventors: Marcelo Busatta; Bhaskar R. Gudlavenkatasiva; Michael D. McKee
- Web page: https://patentgrep.com/patent/US20170302754A1

## CPC

- H04L 67/303: Terminal profiles
- G06F 16/972: {Access to data in other repository systems, e.g. legacy data or dynamic Web page generation}
- H04L 67/563: Data redirection of data network streams
- H04L 67/564: Enhancement of application control based on intercepted application data
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- 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

A proxy framework communicatively connected to source systems and backend systems can intercept a call from a client device to a legacy backend system, interprets the call, and determines whether an account associated with the client device has migrated to an information exchange platform. If so, the proxy framework can direct the call to a native backend system that is native to the information exchange platform, instead of the legacy backend system. If not, the call is forwarded to the legacy backend system.

## Claims

### Claim 1

A system, comprising:
a proxy framework comprising a proxy server embodied on non-transitory computer memory,
the proxy framework operating on an information exchange platform,
the proxy server communicatively connected to a plurality of source systems and backend systems,
the backend systems including a legacy backend system and a native backend system,
the native backend system native to the information exchange platform,
the proxy server comprising:
a decision engine; and
a database storing account migration information;
the proxy server configured for:
intercepting a call from a client device through a source system to the legacy backend system;
interpreting the call from the client device, the call containing an identifier;
accessing the database using the identifier;
retrieving account migration information associated with the identifier;
determining, by the decision engine based on the account migration information, whether an account associated with the client device has migrated to the information exchange platform;
when the account associated with the client device has migrated to the information exchange platform, directing the call to the native backend system native to the information exchange platform; and
when the account associated with the client device has not migrated to the information exchange platform, forwarding the call to the legacy backend system.

### Claim 2 (depends on 1)

The system of claim 1, wherein the interpreting comprises translating the call from the client device to a language supported by the native backend system.

### Claim 3 (depends on 1)

The system of claim 1, wherein the proxy server further comprises a registration component configured for registration of user accounts on behalf of the legacy backend system, the native backend system, or a combination thereof.

### Claim 4 (depends on 1)

The system of claim 1, wherein the proxy server further comprises a cache and wherein the database resides in the cache.

### Claim 5 (depends on 1)

The system of claim 1, wherein the proxy server further comprises an aggregator configured for aggregating and storing data in the database, the data including user data from client devices through source systems communicatively connected thereto, transaction data from all traffic flowing through the proxy framework, or a combination thereof.

### Claim 6 (depends on 5)

The system of claim 5, wherein the aggregator is further configured for analyzing the data collected at the proxy server, generating account-specific statistics, and storing the account-specific statistics in the database.

### Claim 7 (depends on 6)

The system of claim 6, wherein the proxy server is further configured for utilizing the account-specific statistics to execute a rule-based decision for directing or redirecting the call from the client device.

### Claim 8 (depends on 1)

The system of claim 1, wherein the proxy server is further configured for categorizing user accounts stored in the database into different categories, levels, or tiers.

### Claim 9 (depends on 7)

The system of claim 7, further comprising:
a solution decision maker embodied on non-transitory computer memory, wherein the proxy server is one of a plurality of solutions implemented on the information exchange platform.

### Claim 10 (depends on 9)

The system of claim 9, wherein each solution of the plurality of solutions is assigned to a particular category, level, or tier, wherein the solution decision maker is configured for validating an account, identifying a category, level, or tier associated with the account, and directing transaction flow associated with the account to the solution assigned to the particular category, level, or tier.

### Claim 11

A method, comprising:
intercepting a call from a client device through a source system to a legacy backend system, the intercepting performed by a proxy server embodied on non-transitory computer memory, the proxy server residing in a proxy framework, the proxy framework operating on an information exchange platform, the proxy server communicatively connected to a plurality of source systems and backend systems, the backend systems including the legacy backend system and a native backend system, the native backend system native to the information exchange platform;
interpreting the call from the client device, the call containing an identifier, the interpreting performed by the proxy server;
accessing a database using the identifier, the database storing account migration information, the accessing performed by the proxy server;
retrieving account migration information associated with the identifier, the retrieving performed by the proxy server;
determining whether an account associated with the client device has migrated to the information exchange platform, the determining performed by the proxy server based on the account migration information;
when the account associated with the client device has migrated to the information exchange platform, directing the call to the native backend system native to the information exchange platform, the directing performed by the proxy server; and
when the account associated with the client device has not migrated to the information exchange platform, forwarding the call to the legacy backend system, the forwarding performed by the proxy server.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the interpreting comprises translating the call from the client device to a language supported by the native backend system.

### Claim 13 (depends on 11)

The method according to claim 11, wherein the proxy server further comprises a registration component configured for registration of user accounts on behalf of the legacy backend system, the native backend system, or a combination thereof.

### Claim 14 (depends on 11)

The method according to claim 11, wherein the proxy server further comprises a cache and wherein the database resides in the cache.

### Claim 15 (depends on 11)

The method according to claim 11, wherein the proxy server further comprises an aggregator configured for aggregating and storing data in the database, the data including user data from client devices through source systems communicatively connected thereto, transaction data from all traffic flowing through the proxy framework, or a combination thereof.

### Claim 16 (depends on 15)

The method according to claim 15, wherein the aggregator is further configured for analyzing the data collected at the proxy server, generating account-specific statistics, and storing the account-specific statistics in the database.

### Claim 17 (depends on 16)

The method according to claim 16, wherein the proxy server is further configured for utilizing the account-specific statistics to execute a rule-based decision for directing or redirecting the call from the client device.

### Claim 18 (depends on 11)

The method according to claim 11, wherein the proxy server is further configured for categorizing user accounts stored in the database into different categories, levels, or tiers.

### Claim 19 (depends on 17)

The method according to claim 17, wherein the proxy server is one of a plurality of solutions implemented on the information exchange platform.

### Claim 20 (depends on 19)

The method according to claim 19, wherein each solution of the plurality of solutions is assigned to a particular category, level, or tier, wherein a solution decision maker running on the information exchange platform is configured for validating an account, identifying a category, level, or tier associated with the account, and directing transaction flow associated with the account to the solution assigned to the particular category, level, or tier.
