# US 8,788,396 B2 · Intraday risk management data cloud computing system capable of controlling execution of orders > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,788,396 B2 - Document ID: US8788396B2 - Status: Granted - Kind: B2 - Application number: 12/873,148 - Filed: 2010-08-31 - Published: 2011-07-07 - Granted: 2014-07-22 - Earliest claimed: 2003-10-14 - Assignees: FTEN, Inc. - Applicants: Lee Arthur Cole; Douglas Guy Kittelsen; Malcolm Gary Lafever; Ted Nathan Myerson - Inventors: Lee Arthur Cole; Douglas Guy Kittelsen; Malcolm Gary Lafever; Ted Nathan Myerson - Web page: https://patentgrep.com/patent/US8788396B2 ## CPC - G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange - G06Q 40/06: Asset management; Financial planning or analysis - G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes - G06Q 40/08: Insurance - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract In at least one embodiment, a method and system associated with financial articles of trade may include comparing relevant portions of data pertaining to an attempted transaction, wherein the transaction may pertain to one in which an entity is financially liable but unaware. At least one embodiment includes monitoring market transaction activity data to determine when a trading entity has exceeded an aggregated limit, such as one or more trading sub-limits corresponding to one or more custodial prime brokers facilitating trading for the trading entity. At least one embodiment includes a pre-trade gateway to determine if an order violates a pre-trade risk based on information collected by a front-end analyzer. Possible actions include, but are not limited to, placing a null order, terminating a connection associated with the order, modifying the order so as not to violate a pre-trade risk check, and/or notifications to one or more entities. ## Claims ### Claim 1 A computer-implemented method of managing intraday risk conditions, comprising: collecting, by a processor, transaction specific data from a plurality of liquidity destinations trading at least one financial article of trade, wherein the collected transaction specific data comprises account parameters corresponding to associated liquidity destinations; defining, by the processor, an intraday risk condition of a trading market; associating, by the processor, said defined, intraday risk condition with a trading entity; identifying, by the processor, an event in said trading market from said account parameters of the transaction specific data in which the event matches said defined intraday risk condition; terminating, by the processor, at least one dedicated communication session between said trading entity and a corresponding liquidity destination; and initiating, responsive to the identified event, by the processor, a process at said corresponding liquidity destination that cancels pending transaction messages submitted by said trading entity. ### Claim 2 (depends on 1) The method of claim 1, wherein said terminating the dedicated communication session comprises: physically de-coupling a connection between said trading entity and said corresponding liquidity destination, wherein said connection enables said communication session. ### Claim 3 (depends on 1) The method of claim 1, wherein said terminating the dedicated communication session comprises: logically de-coupling a connection between said trading entity and said corresponding liquidity destination, wherein said connection enables said communication session. ### Claim 4 (depends on 1) The method of claim 1, wherein said terminating the dedicated communication session comprises: invoking a session termination over at least one communication session. ### Claim 5 (depends on 4) The method of claim 4, wherein said session termination comprises a TCP teardown. ### Claim 6 (depends on 1) The method of claim 1, wherein said terminating the dedicated communication session comprises: terminating a plurality of communication sessions between said trading entity and said plurality of liquidity destinations. ### Claim 7 (depends on 6) The method of claim 6, wherein said terminating all communication session comprises: at least one of physically or logically de-coupling a plurality of connections between said trading entity and said plurality of liquidity destinations, wherein said plurality of connections enables said plurality of communication sessions. ### Claim 8 (depends on 7) The method of claim 7, further comprising: determining said plurality of connections between said trading entity and said plurality of liquidity destinations. ### Claim 9 (depends on 6) The method of claim 6, wherein said terminating a plurality of communication sessions comprises: terminating all communication sessions between said trading entity and said plurality of liquidity destinations. ### Claim 10 (depends on 1) The method of claim 1, wherein said terminating at least one communication session further comprises: causing a physical de-coupling of a connection between said trading entity and said corresponding liquidity destination. ### Claim 11 (depends on 1) The method of claim 1, wherein said terminating at least one communication session further comprises: sending an instruction to a third party component to initiate an action altering said communication session. ### Claim 12 (depends on 1) The method of claim 1, wherein said initiating a process comprises: forcing a cancel-on-disconnect process at said corresponding liquidity destination. ### Claim 13 (depends on 1) The method of claim 1, wherein said condition is based on transactions of financial articles of trade related to said trading entity. ### Claim 14 (depends on 1) The method of claim 1, wherein said condition includes transactions of financial articles of trade not related to said trading entity. ### Claim 15 (depends on 6) The method of claim 6, further comprising: determining, by the processor, from the account parameters of said transaction specific data canceled orders related to said trading entity over said plurality of liquidity destinations; determining, by the processor, an open order base of said trading entity based on said transaction specific data; comparing, by the processor, said open order base to said canceled orders; and determining, by the processor, that orders for transactions of financial articles of trade are not submitted through said plurality of communication sessions when said canceled orders do not correspond to said open order base. ### Claim 16 (depends on 1) The method of claim 1, further comprising: restoring, by the processor, said at least one communication session to said corresponding liquidity destination through a pre-trade gateway performing pre-trade risk analysis.