US 11,888,955 B1
Card engine integration with backend systems
Sarvesh Kaushal, Newcastle, WA (US); Rohit Iyer, Redmond, WA (US); Bala Subrahmanya Vivek Kosanam, Issaquah, WA (US); Alexander Clinton Lambert, Issaquah, WA (US); and David Bryant Moffett, Issaquah, WA (US)
Assigned to T-Mobile USA, Inc., Bellevue, WA (US)
Filed by T-Mobile USA, Inc., Bellevue, WA (US)
Filed on Jan. 29, 2021, as Appl. No. 17/163,185.
Int. Cl. G06F 15/16 (2006.01); H04L 67/567 (2022.01); G06Q 20/32 (2012.01); H04L 67/63 (2022.01); H04L 67/133 (2022.01); G06Q 20/34 (2012.01)
CPC H04L 67/567 (2022.05) [G06Q 20/325 (2013.01); H04L 67/133 (2022.05); H04L 67/63 (2022.05); G06Q 20/352 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
receiving, by a card engine, action data indicating a result of an account action, associated with a user account with a service provider, that was at least attempted by a backend system associated with the service provider, wherein:
the card engine executes on a computing device remotely from a user equipment (UE) executing a client application, the client application being configured to visually display account information associated with the user account via user interface (UI) cards based on card data provided by the card engine,
the card engine and the client application are not compatible with an application programming interface (API) of the backend system that is configured to perform the account action, and
the card engine receives the action data from an API Response as Card (ARC) engine that is remote from the UE, wherein:
the ARC engine intercepts an action request sent by the client application to the card engine over a network,
the ARC engine transmits an ARC action request to the backend system, wherein the ARC action request:
corresponds to the action request and is based on the API of the backend system that the card engine and the client application are not compatible with, and
causes the backend system to at least attempt to perform the account action associated with the user account,
the ARC engine receives an action response, from the backend system based on the API of the backend system, indicating the result of the account action that was at least attempted by the backend system in response to the ARC action request, and
the ARC engine transmits the action data to the card engine, the action data indicating the result, of the account action that was at least attempted by the backend system, in a fact data format interpretable by the card engine, instead of based on the API of the backend system that the card engine is not compatible with;
selecting, by the card engine, a card format from among a plurality of visual card formats for UI cards to be presented via the client application, wherein the card format is selected based on the result, of the account action that was at least attempted by the backend system, indicated by the action data received by the card engine from the ARC engine;
generating, by the card engine, a card data instance based on the card format and the action data, wherein the card data instance includes card content indicative of the result, of the account action that was at least attempted by the backend system, indicated by the action data received by the card engine from the ARC engine; and
sending, by the card engine, the card data instance to the client application over the network,
wherein the card data instance causes the client application to render and display, in a UI of the client application, a corresponding UI card that visually presents the card content, indicative of the result of the account action that was at least attempted by the backend system, based on the card format selected by the card engine.