Card engine integration with backend systems

Patent metadata

Field	Value
Publication number	US-11405480-B1
Application number	US-202117163166-A
Country	US
Kind code	B1
Filing date	Jan 29, 2021
Priority date	Jan 29, 2021
Publication date	Aug 2, 2022
Grant date	Aug 2, 2022

Abstract

A client application can be configured to render user interface cards, based on card data provided by a remote card engine. An API Response as Card (ARC) engine can intercept a communication between the client application and the card engine, and determine that the communication is associated with another backend system. The ARC engine can request that the backend system perform an account action associated with a user account. The ARC engine can provide information derived from a response from the backend system, reflecting a result of the account action, to the card engine. The card action can generate card data associated with the result of the account action performed by the backend system, and the client application can use the card data to render and display a corresponding card, even if neither the client application nor the card engine are natively configured to interface with the backend system.

First claim

What is claimed is:

1. A method, comprising:
intercepting, by an application programming interface (API) response as card (ARC) engine, a network communication from a client application addressed to a card engine;
determining, by the ARC engine, that the network communication is an action request;
identifying, by the ARC engine, a backend system associated with the action request;
sending, by the ARC engine and based on the action request, an ARC action request to the backend system, wherein the ARC action request identifies a requested account action associated with a user account;
receiving, by the ARC engine from the backend system, an action response indicating an account action result;
sending, by the ARC engine to the card engine, action data indicating the account action result;
receiving, by the ARC engine from the card engine, card data comprising card content associated with the account action result; and
sending, by the ARC engine, the card data to the client application.

2. The method of claim 1 , wherein determining that the network communication is the action request comprises identifying, by the ARC engine, a header in the network communication that is associated with the backend system.

3. The method of claim 2 , wherein identifying the backend system comprises selecting, among a set of backend systems, a particular backend system that corresponds to the header.

4. The method of claim 3 , wherein the set of backend systems comprises one or more of a billing system, an account management system, or a retail system.

5. The method of claim 1 , further comprising identifying, by the ARC engine, the user account based on user credentials in the network communication.

6. The method of claim 1 , wherein the action request is associated with a user selection of a call-to-action, displayed on a card via the client application, associated with the backend system.

7. The method of claim 6 , wherein the client application is a chat application configured to display the card based on a selection of the card at a remote agent device.

8. The method of claim 1 , wherein the ARC engine uses an API associated with the backend system to at least one of:
generate the ARC action request, or
interpret the action response.

9. The method of claim 1 , wherein the card data includes a mapping identifier corresponding to a local card template stored at the client application.

10. The method of claim 1 , wherein the card data identifies formatting information for the card content based on a server-side card template stored at the card engine.

11. The method of claim 1 , wherein the action data is formatted as fact data that the card engine is configured to interpret.

12. A network element, comprising:
one or more processors;
memory storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
intercepting a network communication from a client application addressed to a card engine;
determining that the network communication is an action request;
identifying a backend system associated with the action request;
sending, based on the action request, an application programming interface (API) response as card (ARC) action request to the backend system, wherein the ARC action request identifies a requested account action associated with a user account;
receiving, from the backend system, an action response indicating an account action result;
sending, to the card engine, action data indicating the account action result;
receiving, from the card engine, card data comprising card content associated with the account action result; and
sending the card data to the client application.

13. The network element of claim 12 , wherein determining that the network communication is the action request comprises identifying a header, associated with the backend system, in the network communication.

14. The network element of claim 13 , wherein the operations further comprise identifying the user account based on user credentials in the network communication.

15. The network element of claim 12 , wherein identifying the backend system comprises selecting, among a set of backend systems, a particular backend system that corresponds to the header.

16. The network element of claim 12 , wherein the operations further comprise using an API associated with the backend system to at least one of:
generate the ARC action request, or
interpret the action response.

17. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors of a network element, cause the one or more processors to perform operations comprising:
intercepting a network communication from a client application addressed to a card engine;
determining that the network communication is an action request;
identifying a backend system associated with the action request;
sending, based on the action request, an application programming interface (API) response as card (ARC) action request to the backend system, wherein the ARC action request identifies a requested account action associated with a user account;
receiving, from the backend system, an action response indicating an account action result;
sending, to the card engine, action data indicating the account action result;
receiving, from the card engine, card data comprising card content associated with the account action result; and
sending the card data to the client application.

18. The one or more non-transitory computer-readable media of claim 17 , wherein determining that the network communication is the action request comprises identifying a header, associated with the backend system, in the network communication.

19. The one or more non-transitory computer-readable media of claim 18 , wherein identifying the backend system comprises selecting, among a set of backend systems, a particular backend system that corresponds to the header.

20. The one or more non-transitory computer-readable media of claim 17 , wherein the operations further comprise using an API associated with the backend system to at least one of:
generate the ARC action request, or
interpret the action response.

Assignees

• T Mobile Usa Inc

Inventors

• Kaushal Sarvesh
• Iyer Rohit
• Kosanam Bala Subrahmanya Vivek
• Lambert Alexander Clinton
• Moffett David Bryant

Classifications

• H04L69/26

  Special purpose or proprietary protocols or architectures (network applications for proprietary or special purpose networking environments H04L67/12) · CPC title

• H04L67/63

  Routing a service request depending on the request content or context · CPC title

• G06Q20/34

  using cards, e.g. integrated circuit [IC] cards or magnetic cards · CPC title

• G06Q20/3267

  In-app payments · CPC title

• G06Q20/3223

  Realising banking transactions through M-devices · CPC title