System and method for coalescing market data at a client device

• US 10,055,790 B2
• Filed: 05/01/2014
• Issued: 08/21/2018
• Est. Priority Date: 06/26/2002
• Status: Active Grant

• Current Assignee: Trading Technologies International, Inc.
• Original Assignee: Trading Technologies International, Inc.
• Inventors: Singer, Scott F.
• Primary Examiner(s): Ebersman, Bruce I
• Assistant Examiner(s): Gaw, Mark H
• Application Number:
  US14/266,962
• Publication Number:
  US 20140316966A1
• Time in Patent Office: 1,573 Days
• CPC Class Codes: G06Q 20/042 characterized in that the payment protocol involves at least one cheque
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis

Abstract

A client device coalesces data received from an exchange, and provides a client application such as a graphical user interface with the opportunity to process fewer, but up-to-date, data updates from an exchange when a large volume of prices becomes available. Accordingly, the trader can be assured of receiving updated information that are fed to the client applications at a rate that is cohesive with that client device'"'"'s processing speed.

Claims

1. A non-transitory computer readable medium having stored therein instructions executable by a processor of a client device, wherein the instructions are executable to:

receive by an API running in an API thread of the client device a first market data update for a tradeable object from an electronic exchange;

store by the API running in the API thread the first market data update in a shared data structure in a memory of the client device, wherein the shared data structure is accessible by at least the API thread and a graphical user interface thread, wherein the graphical user interface thread is running a graphical user interface for the client device;

provide by the API running in the API thread a notification to the graphical user interface running in the graphical user interface thread that the shared data structure includes an update, wherein the notification to the graphical user interface running in the graphical user interface thread includes at least one of the group consisting of;

(i) setting a flag and (ii) placing a message in a message queue for the graphical user interface;

receive by the API running in the API thread at least one subsequent market data update for the tradeable object from the electronic exchange, wherein the subsequent market data update is received subsequent to providing the notification and prior to the graphical user interface running in the graphical user interface thread accessing the shared data structure responsive to the notification; and

overwrite by the API running in the API thread the first market data update in the shared data structure with the at least one subsequent market data update before the first market update is accessed by the graphical user interface running in the graphical user interface thread to create a coalesced market data update until the graphical user interface indicates to the API running in the API thread that the graphical user interface has retrieved the coalesced market data update responsive to the notification.

2. The computer readable medium of claim 1, wherein the instructions are further executable to clear the shared data structure after the graphical user interface running in the graphical user interface thread has retrieved the coalesced market data update.

3. The computer readable medium of claim 1, wherein the instructions are further executable to:

receive by the API running in the API thread a second market data update after the graphical user interface running in the graphical user interface thread has retrieved the coalesced market data update;

store by the API running in the API thread the second market data update in the shared data structure; and

provide by the API running in the API thread a second notification to the graphical user interface running in the graphical user interface thread that the shared data structure includes a second update.

4. The computer readable medium of claim 1, wherein the shared data structure includes a plurality of fields, wherein the first market data update and the at least one subsequent market data update are associated with one of the plurality of fields.

5. The computer readable medium of claim 1, wherein a second notification is not sent to the graphical user interface running in the graphical user interface thread if a pending notification is in the message queue for the graphical user interface.

6. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for a price of the tradeable object.

7. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for an order of the tradeable object.

8. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for a fill of the tradeable object.

9. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for a last traded price of the tradeable object.

10. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for a last traded quantity of the tradeable object.

11. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for an inside market of the tradeable object.

12. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for a settlement price of the tradeable object.

13. The computer readable medium of claim 1, wherein the first market data update and the at least one subsequent market data update are for a quantity of the tradeable object.