US2024036834A1PendingUtilityA1

Unified Desktop Computing System

Assignee: BANK OF AMERICAPriority: Aug 1, 2022Filed: Aug 1, 2022Published: Feb 1, 2024
Est. expiryAug 1, 2042(~16 yrs left)· nominal 20-yr term from priority
G06F 8/36H04L 67/133H04L 69/08H04L 67/02G06F 9/541G06F 9/542
43
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Various aspects of the disclosure relate to a unified framework application programming interface (API) to facilitate communicate between applications developed using different technology stacks. The unified framework API integrates communication functionality for each different technology stacks into unified publication and subscription API functions such that each application calls the unified framework API functions to publish information or to subscribe to receive published information. Each application publishes data using its native communication protocol and receives data in its native format, where the unified framework API performs an automatic translation of the information as needed.

Claims

exact text as granted — not AI-modified
1 . A system comprising:
 a computing device hosting a unified API function library;   a workstation, comprising:
 at least one processor; and 
 memory storing computer-readable instructions that, when executed by the at least one processor, cause the workstation to:
 initialize a unified framework API based on the unified API function library; 
 receive, from a first application, a publication event in a first protocol format; 
 translate, by a unified framework, the publication event to at least a second protocol format; and 
 publish, by the unified framework, the publication event in the second protocol format. 
 
   
     
     
         2 . The system of  claim 1 , wherein the instructions cause the workstation to publish the publication event in both the first protocol format and the second protocol format. 
     
     
         3 . The system of  claim 1 , wherein the first protocol format comprises a document object model (DOM) format. 
     
     
         4 . The system of  claim 2 , wherein the first protocol format comprises a javascript communications format. 
     
     
         5 . The system of  claim 1 , wherein the first application and a second subscribing application integrates the unified API function calls. 
     
     
         6 . The system of  claim 1 , wherein updates to the unified API function library hosted by the computing device are applied during initialization of the workstation. 
     
     
         7 . An apparatus comprising:
 a communication interface linked to an external computing device hosting a unified API function library;   at least one processor; and   memory storing computer-readable instructions that, when executed by the at least one processor, cause the apparatus to:
 initialize a unified framework API based on the unified API function library; 
 receive, from a first application, a publication event in a first protocol format; 
 translate, by a unified framework, the publication event to at least a second protocol format; and 
 publish, by the unified framework, the publication event in the second protocol format. 
   
     
     
         8 . The apparatus of  claim 7 , wherein the instructions cause the apparatus to publish the publication event in both the first protocol format and the second protocol format. 
     
     
         9 . The apparatus of  claim 7 , wherein the first protocol format comprises a document object model (DOM) format. 
     
     
         10 . The apparatus of  claim 7 , wherein the first protocol format comprises a javascript communications format. 
     
     
         11 . The apparatus of  claim 7 , wherein the first application and a second subscribing application integrates the unified API function calls. 
     
     
         12 . The apparatus of  claim 7 , wherein updates to the unified API function library hosted by the external computing device are applied during initialization of the apparatus. 
     
     
         13 . The apparatus of  claim 7 , wherein support for a third protocol format comprises updating the unified API function library to translate from the first protocol format or the second protocol format to the third protocol format. 
     
     
         14 . Non-transitory memory storing computer-readable instructions that, when executed by at least one processor, cause a computing device to:
 initialize a unified framework API based on a unified API function library;   receive, from a first application, a publication event in a first protocol format;   translate, by a unified framework, the publication event to at least a second protocol format; and   publish, by the unified framework, the publication event in the second protocol format.   
     
     
         15 . The non-transitory memory of  claim 14 , wherein the instructions cause the computing device to publish the publication event in both the first protocol format and the second protocol format. 
     
     
         16 . The non-transitory memory of  claim 14 , wherein the first protocol format comprises a document object model (DOM) format. 
     
     
         17 . The non-transitory memory of  claim 14 , wherein the first protocol format comprises a javascript communications format. 
     
     
         18 . The non-transitory memory of  claim 14 , wherein the first application and a second subscribing application integrates the unified API function calls. 
     
     
         19 . The non-transitory memory of  claim 14 , wherein updates to the unified API function library hosted by an external computing device are applied during initialization of the computing device. 
     
     
         20 . The non-transitory memory of  claim 14 , wherein support for a third protocol format comprises updating the unified API function library to translate from the first protocol format or the second protocol format to the third protocol format.

Join the waitlist — get patent alerts

Track US2024036834A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.