US2016241634A1PendingUtilityA1

Transaction Execution System Interface and Enterprise System Architecture Thereof

Assignee: EBM/IP LLCPriority: Jan 26, 1998Filed: Apr 21, 2016Published: Aug 18, 2016
Est. expiryJan 26, 2018(expired)· nominal 20-yr term from priority
G06Q 20/04H04L 67/02G06Q 20/16H04L 67/06H04L 67/10G06Q 30/04G06Q 20/10G06Q 20/4037G07F 7/08
48
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system for interfacing at least one user interactive device with a trade execution system to execute trading transactions requested by users over a network includes an application in communication with the network for interfacing between the at least one user interactive device and the trade execution system and coordinating interaction of the at least one user interactive device with the trade execution system. The application contains first and second APIs. The first API is structured to deliver a trading transaction request received from the at least one user interactive device to the trade execution system. The second API is structured to deliver real-time information relating to the trading transaction request received from the trade execution system to the at least one user interactive device. The first API includes at least one stub that is called by the application at a predefined step during processing of the trading transaction request. The at least one stub includes code to interface the application with the trade execution system.

Claims

exact text as granted — not AI-modified
1 . A computer implemented method for accessing and processing data from one or more external data sources at one or more wireless client devices across a network, comprising the steps of:
 creating an application on the one or more wireless client devices using RQL programming language;   accessing the external data source via a driver based on native language of the external data source;   processing the data received from the external data source; and   displaying the processed data into one or more formats via at least one output template.   
     
     
         2 . A method as in  claim 1 , wherein the external data source is accessed using syntax similar to opening a flat file. 
     
     
         3 . A method as in  claim 1 , wherein the external data source is accessed without using ODBC drivers. 
     
     
         4 . A method as in  claim 1 , wherein the processing step uses a data iterator which contains components that handle processing of individual records and record groups. 
     
     
         5 . A method as in  claim 1 , further comprising the step of providing an output template to output the result of the processing step. 
     
     
         6 . A method as in  claim 1 , wherein the application created using RQL programming language is platform independent. 
     
     
         7 . A method as in  claim 1 , wherein the one or more formats is selected from a group consisting of HTML, plain text, other markup and type-setting language and combinations thereof.

Join the waitlist — get patent alerts

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

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