Patent Application
20190362425
Computer processing speeds depend in large part on the amount of data being processed and the complexity of the operations and processing being performed on the data. Some computing systems include many, e.g., hundreds or thousands, of objects of differing types, and attempt to compute values for the objects. Some of the objects may be related or based on other objects, and the system environment may impose rules and restrictions on the objects. For computers handling multiple inter-related objects having different rules and restrictions, it is a challenge to efficiently process and compute final values for the objects. Reducing or minimizing the number of data sets and/or operations performed thereon can increase processing efficiency.
A computer tasked with calculating values and optimizing values based on rules and restrictions may follow a set of procedures, routines, or sub-routines to arrive at the final values. The optimization process may be computationally intensive depending on how many values the computer must consider to arrive at the final values. In many cases, a computer process may run a specified process or routine which results in multiple potential solution values for the objects. The computer process may then have a choice or some flexibility regarding the final object values that are output. Unless the computer is configured to optimize the selected object values, the computer may be forced to select values at random, which may lead to sub-optimal values, or use a brute-force technique to sort through all the combinations which leads to performance degradation and delays. Processing delays may undermine any benefit from selecting proper object values.
A computer calculation process that is constrained by rules or boundaries to optimize values can become much more efficient if the number of data sets being considered can be intelligently reduced.
Accordingly, there is a need for systems and methods that can optimize object values for inter-related objects in an efficient and timely manner, so that the optimized object solutions justify any increase in processing time due to the optimization.
The disclosed embodiments relate generally to selecting optimum values for inter-related objects, e.g., objects influencing and/or dependent upon other system objects, when a computer process computes multiple potential values for each object. Specifically, the disclosed embodiments optimize overall system performance by determining and selecting object values that conform to pre-defined rules and/or relationships between different objects, including identifying and discarding object values that deviate from or otherwise result in a violation of the pre-defined rules and relationships.
Thus, the disclosed embodiments reduce the load on a computer by identifying and eliminating solutions that would result in undesirable object relationships. In other words, the disclosed embodiments rely on desirable object relationships to select object values, so that the selected object values result in the desired object relationships. The desired object relationships may be derived from data input into the system. In one embodiment, the desired object relationships reflect a high level of overall system performance and user satisfaction.
In one embodiment, the disclosed embodiments may be implemented to determine object values so that a maximum number of inter-object transactions can be enabled and do so in an iterative process that conserves computing time and resources. The relationship logic may be pre-configured into a computer, such that the computer optimizes its solutions to conform to as many of the pre-configured logic or criterion as it can. In one embodiment, the object relationships are ranked or are hierarchal in nature, and the computing systems begins with the highest ranked relationship and attempts to meet its rules, then processes the second-highest ranked relationship, and so on. Any object optimization performed during processing of the highest relationship is used during processing of the second relationship. In other words, instead of processing each object relationship separately and independently, the relationship rules are prioritized, and results of processing the highest priority relationship are used during processing of the second highest priority relationship, and the results after processing the second highest priority relationship are used during processing of the third highest priority relationship, and so on until optimum values are determined, or until all of the relationship rules are processed. In one embodiment, if there are multiple solutions for an object value even after all the relationship rules have been processed, the computing system may add additional rules, e.g., based on historical object values, to optimize the final solution.
Objects may be implemented in code, using, among other things, a tangible computer-readable medium comprising computer-executable instructions (e.g., executable software code). Alternatively, objects may be implemented as software code, firmware code, specifically configured hardware or processors, and/or a combination of the aforementioned. An object may be implemented and stored as a set of related data, e.g., a database. Objects may be implemented using a pre-defined data structure. An object may be implemented as an instance of a class that contains data and methods for processing the data. For example, an object may be a self-contained entity that includes data and procedures to manipulate the data. An object may be any item in the computing environment that can be individually manipulated, selected, or processed. Objects may be exposed as shapes, pictures, or words in a display screen or in a user interface.
One exemplary environment where optimizing computer processing of related objects is desirable is in financial markets, and in particular, electronic financial exchanges, such as a futures exchange, such as the Chicago Mercantile Exchange Inc. (CME). In particular, an exchange may offer multiple products and contracts for purchase that may be represented as objects in the computing system. The associated costs and values of objects may be considered to be related data sets. An exchange computer system may also be constrained by the tradable positions of markets, such as for example, bid and ask values for the different contracts, available on the exchange.
A financial instrument trading system, such as a futures exchange, such as the Chicago Mercantile Exchange Inc. (CME), provides a contract market where financial instruments, e.g., futures and options on futures, are traded using electronic systems. “Futures” is a term used to designate all contracts for the purchase or sale of financial instruments or physical commodities for future delivery or cash settlement on a commodity futures exchange. A futures contract is a legally binding agreement to buy or sell a commodity at a specified price at a predetermined future time. An option contract is the right, but not the obligation, to sell or buy the underlying instrument (in this case, a futures contract) at a specified price within a specified time. The commodity to be delivered in fulfillment of the contract, or alternatively the commodity for which the cash market price shall determine the final settlement price of the futures contract, is known as the contract's underlying reference or “underlier.” The terms and conditions of each futures contract are standardized as to the specification of the contract's underlying reference commodity, the quality of such commodity, quantity, delivery date, and means of contract settlement. Cash settlement is a method of settling a futures contract whereby the parties effect final settlement when the contract expires by paying/receiving the loss/gain related to the contract in cash, rather than by effecting physical sale and purchase of the underlying reference commodity at a price determined by the futures contract price. Options and futures may be based on more generalized market indicators, such as stock indices, interest rates, futures contracts, and other derivatives.
An exchange may provide for a centralized “clearing house” through which trades made must be confirmed, matched, and settled each day until offset or delivered. The clearing house may be an adjunct to an exchange, and may be an operating division of an exchange, which is responsible for settling trading accounts, clearing trades, collecting, and maintaining performance bond funds, regulating delivery, and reporting trading data. One of the roles of the clearing house is to mitigate credit risk. Clearing is the procedure through which the clearing house becomes buyer to each seller of a futures contract, and seller to each buyer, also referred to as a novation, and assumes responsibility for protecting buyers and sellers from financial loss due to breach of contract, by assuring performance on each contract. A clearing member is a firm qualified to clear trades through the clearing house.
The clearing house of an exchange clears, settles and guarantees matched transactions in contracts occurring through the facilities of the exchange. In addition, the clearing house establishes and monitors financial requirements for clearing members and conveys certain clearing privileges in conjunction with the relevant exchange markets.
The clearing house establishes clearing level performance bonds (margins) for all products of the exchange and establishes minimum performance bond requirements for customers of such products. A performance bond, also referred to as a margin requirement, corresponds with the funds that must be deposited by a customer with his or her broker, by a broker with a clearing member or by a clearing member with the clearing house, for the purpose of insuring the broker or clearing house against loss on open futures or options contracts. This is not a part payment on a purchase. The performance bond helps to ensure the financial integrity of brokers, clearing members and the exchange as a whole. The performance bond refers to the minimum dollar deposit required by the clearing house from clearing members in accordance with their positions. Maintenance, or maintenance margin, refers to a sum, usually smaller than the initial performance bond, which must remain on deposit in the customer's account for any position at all times. The initial margin is the total amount of margin per contract required by the broker when a futures position is opened. A drop-in funds below this level requires a deposit back to the initial margin levels, i.e., a performance bond call. If a customer's equity in any futures position drops to or under the maintenance level because of adverse price action, the broker must issue a performance bond/margin call to restore the customer's equity. A performance bond call, also referred to as a margin call, is a demand for additional funds to bring the customer's account back up to the initial performance bond level whenever adverse price movements cause the account to go below the maintenance.
The exchange derives its financial stability in large part by removing debt obligations among market participants as they occur. This is accomplished by determining a settlement price at the close of the market each day for each contract and marking all open positions to that price, referred to as “mark to market.” Every contract is debited or credited based on that trading session's gains or losses. As prices move for or against a position, funds flow into and out of the trading account. In the case of the CME, each business day by 6:40 a.m. Chicago time, based on the mark-to-the-market of all open positions to the previous trading day's settlement price, the clearing house pays to or collects cash from each clearing member. This cash flow, known as settlement variation, is performed by CME's settlement banks based on instructions issued by the clearing house. All payments to and collections from clearing members are made in “same-day” funds. In addition to the 6:40 a.m. settlement, a daily intra-day mark-to-the market of all open positions, including trades executed during the overnight GLOBEX®, the CME's electronic trading systems, trading session and the current day's trades matched before 11:15 a.m., is performed using current prices. The resulting cash payments are made intra-day for same day value. In times of extreme price volatility, the clearing house has the authority to perform additional intra-day mark-to-the-market calculations on open positions and to call for immediate payment of settlement variation. CME's mark-to-the-market settlement system differs from the settlement systems implemented by many other financial markets, including the interbank, Treasury securities, over-the-counter foreign exchange and debt, options, and equities markets, where participants regularly assume credit exposure to each other. In those markets, the failure of one participant can have a ripple effect on the solvency of the other participants. Conversely, CME's mark-to-the-market system does not allow losses to accumulate over time or allow a market participant the opportunity to defer losses associated with market positions.
In order to minimize risk to the exchange while minimizing the burden on members, it is desirable to approximate the requisite performance bond or margin requirement as closely as possible to the actual positions of the account at any given time. An exchange may use a settlement method to determine the position of a contract. It may be difficult to quickly and efficiently select the best settlement price when multiple potential settlement prices can be used. For example, when multiple potential settlement prices can be used, differentiating between the multiple potential settlement prices may be a time-consuming task, or the logic for determining the best settlement price may be context or case specific.
With some spread instruments, the market is sufficiently inactive during or at the end of the trading day. Very little, if any, trades may occur during a given day. In such cases, because of low liquidity and trading activity, it may be difficult to determine daily settlement prices for purposes of accurately estimating performance bond requirements. Thus, the exchange may determine a settlement price based on other market conditions. In many cases, the logic used to determine a settlement price for a contract may result in multiple viable or possible settlement prices. When multiple settlement prices all conform to or are valid for the outright market for a contract, the exchange may have a choice or some flexibility regarding the settlement price that is selected for a contract. As used herein, prices may be considered to be valid, for example, for an existing market or contract if the prices are equivalent to the bid or the ask for that contract, or if the prices are the same as one of the ticks between the bid and the ask for that contract.
While the disclosed embodiments may be discussed in relation to futures and/or options on futures trading, it should be appreciated that the disclosed embodiments may be applicable to any equity, fixed income security, currency, commodity, options or futures trading system or market now available or later developed. It should be appreciated that a trading environment, such as a futures exchange as described herein, implements one or more economic markets where rights and obligations may be traded. As such, a trading environment may be characterized by a need to maintain market integrity, transparency, predictability, fair/equitable access, and participant expectations with respect thereto. For example, an exchange must respond to inputs, such as trader orders, cancelations, etc., in a manner as expected by the market participants, such as based on market data, e.g., prices, available counter-orders, etc., to provide an expected level of certainty that transactions will occur in a consistent and predictable manner and without unknown or unascertainable risks. In addition, it should be appreciated that electronic trading systems further impose additional expectations and demands by market participants as to transaction processing speed, latency, capacity, and response time, while creating additional complexities relating thereto. Accordingly, as will be described, the disclosed embodiments may further include functionality to ensure that the expectations of market participants are met, e.g., that transactional integrity and predictable system responses are maintained.
As was discussed above, electronic trading systems ideally attempt to offer an efficient, fair and balanced market where market prices reflect a true consensus of the value of products traded among the market participants, where the intentional or unintentional influence of any one market participant is minimized if not eliminated, and where unfair or inequitable advantages with respect to information access are minimized if not eliminated.
Although described below in connection with examples involving instruments having multiple components, such as calendar and butterfly spread instruments, the methods described herein are well suited for determining final values for any variety of objects conforming to a set of rules or relationships, such as for example, determining settlement prices for a variety of instruments based on a related market.
Generally, the disclosed embodiments may be applicable to any computer processing system that is constrained by a variety of rules and data values. When a computer processor attempts to compute a large number of data sets in an environment including rules constraints and data constraints, the number of possible solutions or combinations of values can become unwieldy.
The disclosed embodiments may be applicable to contracts for any type of underlier commodity, equity, option, or futures trading system or market now available or later developed. The disclosed embodiments are also not limited to intra-market spread instruments, and accordingly may also be used in connection with inter-market spread instruments for contracts associated with different commodities.
While the disclosed embodiments may be described in reference to the CME, it should be appreciated that these embodiments are applicable to any exchange. Such other exchanges may include a clearing house that, like the CME clearing house, clears, settles, and guarantees all matched transactions in contracts of the exchange occurring through its facilities. In addition, such clearing houses establish and monitor financial requirements for clearing members and convey certain clearing privileges in conjunction with the relevant exchange markets.
The disclosed embodiments are also not limited to uses by a clearing house or exchange for purposes of enforcing a performance bond or margin requirement. For example, a market participant may use the disclosed embodiments in a simulation or other analysis of a portfolio. In such cases, the settlement price may be useful as an indication of a value at risk and/or cash flow obligation rather than a performance bond. The disclosed embodiments may also be used by market participants or other entities to forecast or predict the effects of a prospective position on the margin requirement of the market participant.
The methods and systems described herein may be integrated or otherwise combined with various risk management methods and systems, such as the risk management methods and systems described in U.S. Pat. No. 7,769,667 entitled “System and Method for Activity Based Margining” (the '667 Patent”), the entire disclosure of which is incorporated by reference herein and relied upon. For example, the methods and systems described herein may be configured as a component or module of the risk management systems described in the above-referenced patent. Alternatively, or additionally, the disclosed methods may generate data to be provided to the systems described in the above-referenced patent. For example, the settlement prices determined by the disclosed embodiments may be incorporated into margin requirement(s) determined by the risk management method or system.
In one embodiment, the disclosed methods and systems are integrated or otherwise combined with the risk management system implemented by CME called Standard Portfolio Analysis of Risk™ (SPAN®). The SPAN system bases performance bond requirements on the overall risk of the portfolios using parameters as determined by CME's Board of Directors, and thus represents a significant improvement over other performance bond systems, most notably those that are “strategy-based” or “delta-based.” Further details regarding SPAN are set forth in the '667 Patent.
In one embodiment, the disclosed embodiments may be integrated or combined with a margin model, such as a margin model different from SPAN. For example, a margin model may be implemented to generate multiple settlement prices.
The embodiments may be described in terms of a distributed computing system. The particular examples identify a specific set of components useful in a futures and options exchange. However, many of the components and inventive features are readily adapted to other electronic trading environments. The specific examples described herein may teach specific protocols and/or interfaces, although it should be understood that the principles involved may be extended to, or applied in, other protocols and interfaces.
It should be appreciated that the plurality of entities utilizing or involved with the disclosed embodiments, e.g., the market participants, may be referred to by other nomenclature reflecting the role that the particular entity is performing with respect to the disclosed embodiments and that a given entity may perform more than one role depending upon the implementation and the nature of the particular transaction being undertaken, as well as the entity's contractual and/or legal relationship with another market participant and/or the exchange.
An exemplary trading network environment for implementing trading systems and methods is shown in
Herein, the phrase “coupled with” is defined to mean directly connected to or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware and software-based components. Further, to clarify the use in the pending claims and to hereby provide notice to the public, the phrases “at least one of <A>, <B>, . . . and <N>” or “at least one of <A>, <B>, . . . <N>, or combinations thereof” are defined by the Applicant in the broadest sense, superseding any other implied definitions herebefore or hereinafter unless expressly asserted by the Applicant to the contrary, to mean one or more elements selected from the group comprising A, B, . . . and N, that is to say, any combination of one or more of the elements A, B, . . . or N including any one element alone or in combination with one or more of the other elements which may also include, in combination, additional elements not listed.
The exchange computer system 100 may be implemented with one or more mainframe, desktop, or other computers, such as the example computer 200 described below with respect to
A match engine module 106 may be included to match bid and offer prices and may be implemented with software that executes one or more algorithms for matching bids and offers. A trade database 108 may be included to store information identifying trades and descriptions of trades. In particular, a trade database may store information identifying the time that a trade took place and the contract price. An order book module 110 may be included to compute or otherwise determine current bid and offer prices, e.g., in a continuous auction market, or also operate as an order accumulation buffer for a batch auction market. A market data module 112 may be included to collect market data and prepare the data for transmission to users.
A risk management module 134 may be included to compute and determine a user's risk utilization in relation to the user's defined risk thresholds. The risk management module 134 may also be configured to determine risk assessments or exposure levels in connection with positions held by a market participant.
The risk management module 134 may be configured to administer, manage, or maintain one or more margining mechanisms implemented by the exchange computer system 100. Such administration, management or maintenance may include managing a number of database records reflective of margin accounts of the market participants. In some embodiments, the risk management module 134 implements one or more aspects of the disclosed embodiments, including, for instance, principal component analysis (PCA) based margining, in connection with interest rate swap (IRS) portfolios, as described below.
An order processing module 136 may be included to decompose delta-based, spread instrument, bulk, and other types of composite orders for processing by the order book module 110 and/or the match engine module 106. The order processing module 136 may also be used to implement one or more procedures related to clearing an order.
A settlement module 140 (or settlement processor or other payment processor) may be included to provide one or more functions related to settling or otherwise administering transactions cleared by the exchange. Settlement module 140 of the exchange computer system 100 may implement one or more settlement price determination techniques. Settlement-related functions need not be limited to actions or events occurring at the end of a contract term. For instance, in some embodiments, settlement-related functions may include or involve daily or other mark to market settlements for margining purposes. In some cases, the settlement module 140 may be configured to communicate with the trade database 108 (or the memory(ies) on which the trade database 108 is stored) and/or to determine a payment amount based on a spot price, the price of the futures contract or other financial instrument, or other price data, at various times. The determination may be made at one or more points in time during the term of the financial instrument in connection with a margining mechanism. For example, the settlement module 140 may be used to determine a mark to market amount on a daily basis during the term of the financial instrument. Such determinations may also be made on a settlement date for the financial instrument for the purposes of final settlement.
In some embodiments, the settlement module 140 may be integrated to any desired extent with one or more of the other modules or processors of the exchange computer system 100. For example, the settlement module 140 and the risk management module 134 may be integrated to any desired extent. In some cases, one or more margining procedures or other aspects of the margining mechanism(s) may be implemented by the settlement module 140.
An optimization module 142 may be included to select best or optimum values for contracts when multiple values all meet the criterion for other related contracts. When multiple contracts are simultaneously considered for settlement by an exchange system, and when the system determines more than one settlement price solution for a contract, it would be beneficial to the exchange to optimize the selection of the settlement price or prices such that the selected values result in desirable relationships between the contracts (e.g., values that are valid for other dependent contracts). In an environment having multiple contracts, multiple possible prices and multiple relationships, a computer system may not be able to determine an optimum solution without spending a high amount of computing time and resources.
An optimum solution or solutions may be the combination(s) of objects, e.g., contract settlement prices, that conform to a hierarchical prioritization of object relationships. The optimization module 142 may for example be utilized in conjunction with the settlement module 140 which determines a mark to market amount. The optimization module 142 in one embodiment determines which of multiple possible settlement prices, each of which could be selected as the settlement price for a contract, should be selected for a contract. The optimization module 142 in one embodiment also determines the optimum combinations of multiple contracts so that the solutions are valid for the existing markets for the contracts as well as spread relationships between the contracts, such as calendar and butterfly spreads.
It should be appreciated that concurrent processing limits may be defined by or imposed separately or in combination, as was described above, on one or more of the trading system components, including the user database 102, the account data module 104, the match engine module 106, the trade database 108, the order book module 110, the market data module 112, the risk management module 134, the order processing module 136, the settlement module 140, or other component of the exchange computer system 100.
One skilled in the art will appreciate that one or more modules described herein may be implemented using, among other things, a tangible computer-readable medium comprising computer-executable instructions (e.g., executable software code). Alternatively, modules may be implemented as software code, firmware code, specifically configured hardware or processors, and/or a combination of the aforementioned. For example, the modules may be embodied as part of an exchange 100 for financial instruments. It should be appreciated the disclosed embodiments may be implemented as a different or separate module of the exchange computer system 100, or a separate computer system coupled with the exchange computer system 100 so as to have access to margin account record, pricing, and/or other data. As described above, the disclosed embodiments may be implemented as a centrally accessible system or as a distributed system, e.g., where some of the disclosed functions are performed by the computer systems of the market participants.
The trading network environment shown in
An exemplary computer device 114 is shown directly connected to exchange computer system 100, such as via a T1 line, a common local area network (LAN) or other wired and/or wireless medium for connecting computer devices, such as the network 220 shown in
Exemplary computer devices 116 and 118 are coupled with a local area network (“LAN”) 124 which may be configured in one or more of the well-known LAN topologies, e.g., star, daisy chain, etc., and may use a variety of different protocols, such as Ethernet, TCP/IP, etc. The exemplary computer devices 116 and 118 may communicate with each other and with other computer and other devices which are coupled with the LAN 124. Computer and other devices may be coupled with the LAN 124 via twisted pair wires, coaxial cable, fiber optics or other wired or wireless media. As shown in
Users of the exchange computer system 100 may include one or more market makers 130 which may maintain a market by providing constant bid and offer prices for a derivative or security to the exchange computer system 100, such as via one of the exemplary computer devices depicted. The exchange computer system 100 may also exchange information with other match or trade engines, such as trade engine 138. One skilled in the art will appreciate that numerous additional computers and systems may be coupled to exchange computer system 100. Such computers and systems may include clearing, regulatory and fee systems.
The operations of computer devices and systems shown in
Numerous additional servers, computers, handheld devices, personal digital assistants, telephones, and other devices may also be connected to exchange computer system 100. Moreover, one skilled in the art will appreciate that the topology shown in
Referring to
In a networked deployment, the computer system 200 may operate in the capacity of a server or as a client user computer in a client-server user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 200 can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system 200 can be implemented using electronic devices that provide voice, video, or data communication. Further, while a single computer system 200 is illustrated, the term “system” shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.
As illustrated in
The computer system 200 may include a memory 204 that can communicate via a bus 208. The memory 204 may be a main memory, a static memory, or a dynamic memory. The memory 204 may include, but is not limited to, computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one embodiment, the memory 204 includes a cache or random-access memory for the processor 202. In alternative embodiments, the memory 204 is separate from the processor 202, such as a cache memory of a processor, the system memory, or other memory. The memory 204 may be an external storage device or database for storing data. Examples include a hard drive, compact disc (“CD”), digital video disc (“DVD”), memory card, memory stick, floppy disc, universal serial bus (“USB”) memory device, or any other device operative to store data. The memory 204 is operable to store instructions executable by the processor 202. The functions, acts or tasks illustrated in the figures or described herein may be performed by the programmed processor 202 executing the instructions 212 stored in the memory 204. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firmware, micro-code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.
As shown, the computer system 200 may further include a display unit 214, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information. The display 214 may act as an interface for the user to see the functioning of the processor 202, or specifically as an interface with the software stored in the memory 204 or in the drive unit 206.
Additionally, the computer system 200 may include an input device 216 configured to allow a user to interact with any of the components of system 200. The input device 216 may be a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control, or any other device operative to interact with the system 200.
In a particular embodiment, as depicted in
The present disclosure contemplates a computer-readable medium that includes instructions 212 or receives and executes instructions 212 responsive to a propagated signal, so that a device connected to a network 220 can communicate voice, video, audio, images, or any other data over the network 220. Further, the instructions 212 may be transmitted or received over the network 220 via a communication interface 218. The communication interface 218 may be a part of the processor 202 or may be a separate component. The communication interface 218 may be created in software or may be a physical connection in hardware. The communication interface 218 is configured to connect with a network 220, external media, the display 214, or any other components in system 200, or combinations thereof. The connection with the network 220 may be a physical connection, such as a wired Ethernet connection or may be established wirelessly as discussed below. Likewise, the additional connections with other components of the system 200 may be physical connections or may be established wirelessly.
The network 220 may include wired networks, wireless networks, or combinations thereof. The wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, or WiMax network. Further, the network 220 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to, TCP/IP based networking protocols.
Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. While the computer-readable medium is shown to be a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, or a combination of one or more of them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random-access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
In an alternative embodiment, dedicated or otherwise specifically configured hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the methods described herein. Applications that may include the apparatus and systems of various embodiments can broadly include a variety of electronic and computer systems. One or more embodiments described herein may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.
In accordance with various embodiments of the present disclosure, the methods described herein may be implemented by software programs executable by a computer system. Further, in an exemplary, non-limited embodiment, implementations can include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement one or more of the methods or functionalities as described herein.
Although the present specification describes components and functions that may be implemented in particular embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP, HTTPS) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed herein are considered equivalents thereof.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and anyone or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical discs, or optical discs. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical discs; and CD ROM and DVD-ROM discs. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a device having a display, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. Feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback. Input from the user can be received in any form, including acoustic, speech, or tactile input.
Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
A system may depend on certain rules, logic, and inter-related objects and data. In technical and computing environments, a system may calculate values for multiple objects subject to rules, e.g., business or environment logic, associated with the objects. Certain object types may also depend on other object types. For example, a computing environment may include multiple objects of different types, e.g., base objects and composite objects. A composite object as used herein is an object whose value depends on, is related to, or is influenced by, the values of other objects, such as base objects or other composite objects. For example, a composite object may involve transactions between multiple, e.g., two, base objects. Or, a composite object may define a relationship between other objects. Thus, composite objects depend on the values of other system objects. In one embodiment, a composite object involves or defines a transaction or relationship between at least two other objects. For example, a composite object involves or defines a transaction or relationship between two base objects.
The optimization module in one application can rapidly and efficiently determine solutions for the objects that meet predetermined rules for the objects. Predetermined rules may be programmed into the computer. An example predetermined rule may be a rule about the difference in values, e.g., the net value, between contracts. The rules may be hard rules, or system requirements. Alternatively, rules may be soft rules that are not requirements but reflect system or user preferences.
For example, the disclosed embodiments may optimize the values of base objects by considering the effects of base object values on other composite objects that are related to the base objects. Moreover, the system environment may impose restrictions on the values of the composite objects. For example, the system may impose certain performance requirements on composite objects. Or, the system may impose a minimum or maximum value for a composite object value that is based on at least two base objects' values. Thus, the system attempts to select base object values that conform to the composite object value requirement. In such a computing environment, it may be desirable to optimize overall system behavior by assigning values to objects such that rules or relationships involving the objects, e.g., composite object definitions, are met.
In one embodiment, the computing may receive values for base objects and composite objects, and the computing system attempts to select values in accordance with relationships associated with the base objects and composite objects. In particular, the system may receive high and low values for each base and composite object. Even though a composite object may define a relationship between base objects, or be related to the base objects, the values received for the composite objects may be independent of the values received for the corresponding base objects, e.g., fluctuations in the values of the corresponding base objects may have no effect on the values received for the composite object, and vice versa.
In one embodiment, the composite object values define a range of values that is then compared to the transaction results involving two base objects, discussed in further detail herein.
In one embodiment, the disclosed embodiments provide systems and methods for efficiently selecting values for or assigning values to base objects based on the received values. In one embodiment, the disclosed embodiments may utilize composite objects associated with base objects as a guide to select values for the base objects. In one embodiment, the disclosed embodiments may consider multiple base objects in conjunction. Because composite objects, in one embodiment, depend on or are related to at least two base objects, a composite object associated with at least two base objects can be exploited to determine final settlement values for the two base objects.
It should be appreciated that that the received values for base objects may be considered to be subjective values for those base objects or based on a user's perception of the base objects. The system in one embodiment chooses one of the received subjective values for the base objects to determine a best objective value for each base object, where the value selected as the final value is one of the received values. In other words, the system selects one of multiple subjective values as an objective value for that object. Said yet another way, the system attempts to select one of many possible values for an object and assigns the single selected value of the object as the final value for that object. Thus the disclosed embodiments can be applied in any system needing to decide which of multiple possible options or values should be selected as the definitive option or value, where the decision is guided by the system's environment and other objects in the system that are related to the objects in question. For example, a system including at least two base objects and one composite object can utilize the composite object to select values for the base objects.
For example, as shown in
Although three base objects and four composite objects are illustrated in
Moreover, an object may be considered to be simultaneously both a base object and a composite object. For example, an object may both (i) depend upon other objects (and thus be considered a composite object) and (ii) be depended upon by other objects (and thus be considered a base object). It should be appreciated that whether an object is characterized as a base object or a composite object depends upon the relationship of that object with other objects in the computing system
In one embodiment, the system may store the relationships between composite objects and base objects as equations. For example, if composite object C1 defines the net value of base objects B1 and B2, then the following equation 1 defines C1 in terms of B1 and B2:
C1=B1−B2 Equation 1:
The computing system or optimization module may receive values for each of the objects. For example, as shown in
It should be appreciated that even if a composite object is associated with multiple base objects, the values received for the composite object are independent of the values received of the corresponding base objects. For example, the received values for each of C1, B1 and B2 are independent of the above equation 1. In other words, the received values for C1 are not calculated based on B1 and B2. In a financial exchange computer system, the received values may instead be based on, for example, market factors, trade data, user behavior or user predictions. Thus, it may not be the case that each value received for C1, B1 and B2 conforms to equation 1.
The disclosed embodiments attempt to filter the values of base objects so that only values of base objects that conform to equations defining composite objects are kept in the memory as possible base object values, as discussed in further detail below. Combinations of values for base objects that fail to conform to equations or relationships defined associated composite objects are eliminated from the system memory.
The optimization module then iteratively processes and analyzes combinations of multiple base objects. In particular, the optimization module generates all possible combinations of received values of multiple, e.g., two, base objects and tests each possible combination against the associated composite object received values. Again, composite objects that are associated with base objects can be said to define a desired relationship between the base objects. Any combination of values for base objects that does not result in a desired relationship between the base objects is eliminated from the memory associated with the optimization module. Such elimination reduces further processing load on the optimization module, resulting in quicker solution determination.
In one embodiment, the optimization module may eliminate solutions based on other system rules or preferences unrelated to composite objects. For example, the optimization module may eliminate solutions based on time of day or time of year. Or, the optimization module may determine probabilities for which of the possible solutions would actually be selected based on historical data, and eliminate solutions based on past performance and past solution selection.
Referring to
The optimization module then performs transactions on each possible solution in the solutions matrix. Specifically, the optimization module performs the same transaction that is defined by the associated composite object. For example, because the solutions matrix includes all possible solutions of the values of B1 and B2, each solution in the solutions matrix is tested against the composite object that is also associated with B1 and B2, namely, C1.
It should be appreciated that the transaction performed on each possible solution in the solutions matrix is the same transaction defined by composite object C1. For example, if composite object C1 is an object defining the difference between B1 and B2 values, the optimization module calculates the difference between the B1 and B2 values for each possible solution in the solutions matrix.
The optimization module accordingly performs the relevant transaction (using the associated composite object C1 as a guide) on each possible solution in the solutions matrix. In one embodiment, the optimization module stores the transaction results within the solutions matrix, as shown in
The optimization module then compares the solutions matrix transaction results to the received values for composite object C1. Any transaction result that does not meet or fall between the received values for composite object C1 is deemed to be an undesirable transaction result. The possible solution that let to such a transaction result is eliminated from the solutions matrix. For example, if optimization module determines that transaction results HB1-HB2 and HB1-LB2 are both outside of a range of values defined by and including HC1 and LC1, the optimization module eliminates those possible solutions from the solutions matrix, as shown in
It should accordingly be appreciated that the optimization module eliminated possible B1, B2 solutions whose transaction results do not conform to or are not valid for the composite object associated with B1 and B2, namely, C1. As used herein, transaction results between values of B1 and B2 are considered to be valid for composite object C1 if the transaction results are the same as one of the possible values for C1 or fall within a range of values defined by the possible values for C1. It should also be appreciated that the elimination of [HB1, HB2] and [HB1, LB2] as possible solutions for B1 and B2 reduces the overall data set of possible solutions, making subsequent calculations and operations on the solutions matrix faster and more efficient.
The optimization module then iteratively adds possible solutions to the current solution matrix, e.g., by considering the next base object B3, performs transactions between those solutions based on associated composite objects, and removes solutions whose transaction result is not valid for received values for the associated composite objects. Specifically, the optimization module updates the solutions matrix in light of the next base object B3, as shown in
The optimization module then performs transactions on each possible combination of B1 and B3 values in the solutions matrix. Specifically, the optimization module performs the same transaction that is defined by the associated composite object. For example, because the solutions matrix includes all the current possible solutions of the values of B1 and B3, each solution in the solutions matrix is tested against the composite object that is also associated with B1 and B3, namely, C2. For example, if composite object C2 is an object defining the difference between B1 and B3 values, the optimization module calculates the difference between the B1 and B3 values for each possible solution in the solutions matrix.
The optimization module accordingly performs the relevant transaction (using the associated composite object C2 as a guide) on each possible solution in the solutions matrix. In one embodiment, the optimization module stores the transaction results within the solutions matrix, as shown in
It should be understood that some of the possible solutions in the solutions matrix may include the same values for B1 and B3. For example, possible solutions [LB1, HB2, HB3] and [LB1, LB2, HB3] share the same values for B1 and B3. The optimization module in one embodiment is configured to re-use values for a previously performed transaction, instead of repeating the transaction. For example, the optimization module performs the appropriate B1-B3 transaction for [LB1, HB2, HB3]. When the optimization module is processing [LB1, LB2, HB3], the optimization module is configured to re-use or copy the transaction results from the [LB1, HB2, HB3] processing.
The optimization module then compares the solutions matrix transaction results to the received values for composite object C2. Any transaction result that does not meet or fall between the received values for composite object C2 is deemed to be an undesirable transaction result. The possible solution that let to such a transaction result is eliminated from the solutions matrix. For example, if optimization module determines that transaction result LB1-LB3 is outside of a range defined by and including HC2 and LC2, the optimization module eliminates this possible solution from the solutions matrix, as shown in
It should accordingly be appreciated that the optimization module eliminated possible solutions having B1, B3 values whose transaction results are not valid for the composite object associated with B1 and B3, namely, C2.
The optimization module continues iteratively processing the effects of multiple base objects analyzed simultaneously. The optimization module next considers the combination of B2 and B3. Because B2 values were added to the solutions matrix when the optimization module was analyzing the combination of B1 and B2, the optimization module does not need to update the solutions matrix. Instead, the optimization module can directly begin performing transactions between the B2 and B3 values. It should be appreciated, however, that if the optimization module were considering a fourth base object, e.g., an example base object B4, the optimization module would update the solutions matrix by including possible solutions due to the inclusion of a new base object.
As shown in
The optimization module accordingly performs the relevant transaction (using the associated composite object C3 as a guide) on each possible solution in the solutions matrix. In one embodiment, the optimization module stores the transaction results within the solutions matrix, as shown in
The optimization module then compares the solutions matrix transaction results to the received values for composite object C3. Any transaction result that does not meet or fall between the received values for composite object C3 is deemed to be an undesirable transaction result. The possible solution that let to such a transaction result is eliminated from the solutions matrix. For example, if optimization module determines that both transaction results HB2-LB3 and LB2-LB3 are within a range defined by and including HC3 and LC3, the optimization module does not eliminate any of the possible solutions.
It should accordingly be appreciated that the optimization module did not eliminate any possible solutions in the current iteration because all of the possible solutions had B2, B3 values whose transaction results were valid for the composite object associated with B2 and B3, namely, C3.
The optimization module then iteratively processes and analyzes combinations of all three base objects. The optimization module does not need to update the solutions matrix because the optimization module is not adding a new base object into consideration. Instead, the optimization module is going to consider the combination of B1, B2 and B3, each of which have previously been added to the solutions matrix. The optimization module can thus directly begin performing transactions between the B 1, B2 and B3 values.
As shown in
The optimization module accordingly performs the relevant transaction (using the associated composite object C4 as a guide) on each possible solution in the solutions matrix. In one embodiment, the optimization module stores the transaction results within the solutions matrix, as shown in
The optimization module then compares the solutions matrix transaction results to the received values for composite object C4. Any transaction result that does not meet or fall between the received values for composite object C4 is deemed to be an undesirable transaction result. The possible solution that let to such a transaction result is eliminated from the solutions matrix. For example, if optimization module determines that transaction result LB1-2*LB2+LB3 is outside of a range defined by and including HC4 and LC4, the optimization module eliminates this possible solution from the solutions matrix, as shown in
This iterative step leaves only one solution in the solutions matrix, namely, [LB1, HB2, LB3]. The optimization module accordingly selects [LB1, HB2, LB3] as values for base objects B1, B2 and B3, as shown in
Although each base and composite object in the examples of
It should be appreciated that in
In one embodiment, the order of processing base objects affects the final solutions assigned to the objects. In the examples associated with
The optimization module applies the extracted relationship to the received values of the objects. For example, the optimization module may have stored therein, or may have extracted, a relationship defining a composite object. The optimization module then performs transactions that apply the stored or extracted relationships upon the values of the corresponding base objects that are the subject of the relationships, as discussed herein. The optimization module may store the transaction results in a solutions matrix and compare the results to the received values for the corresponding composite objects, as discussed herein. The optimization module iteratively processes the composite object relationships in pre-defined order. The optimization module outputs the selected base object value for each base object. The optimization module may output an optimized solution including a value for B1 from one of the received possible values for B1, a value for B2 from one of the received possible values for B2, and so on, including a value for BN from one of the received possible values for BN.
It should be appreciated that although the optimization module utilizes information from the composite objects, the optimization module in one embodiment only outputs values for the base objects. In one embodiment, the optimization module may output values for base and composite objects, using information extracted from other composite objects.
In one embodiment, the steps of
The optimization module then eliminates solutions from the solutions matrix based on a composite object related to the base objects under consideration, as shown in block 1604. In particular, as discussed herein, the optimization module performs a transaction defined by the related composite object, compares the transaction results with all possible values of the related composite object, and eliminates possible solutions from the solutions matrix whose transaction result falls outside of a range defined by received values for, and thus are not valid for, the related composite object.
The optimization module then determines whether the environment includes any other base objects not yet considered, as shown in block 1606. If the environment, e.g., the optimization module, includes other base objects not yet considered, the optimization module selects the next base object to analyze and process. In one embodiment, for each base object, the system includes at least one composite object defining a relationship involving each base object. The system may include multiple composite objects that define different relationships for each base object.
Upon determining that the optimization module includes more base and composite objects to consider, the optimization module expands the solutions matrix by considering permutations of the possible solutions in the solutions matrix with the received values of a next base object, as shown in block 1608. Once the solutions matrix is expanded to consider the next base object, the optimization module again filters the solutions based on the composite object related to a newly available combination of object values due to the addition of the newly considered base object, as shown in block 1604.
If the optimization module determines that there are no more base and composite objects to consider in step 1606, the optimization module then checks how many possible solutions the solutions matrix contains, as shown in block 1610.
If the optimization module determines that the solutions matrix contains no possible solutions because they were filtered out or eliminated at step 1604, the optimization module reverts the solutions matrix to the version of the solutions matrix before the filtering at block 1604, as shown in block 1612. The optimization module may for example be capable of version control and storage, so that the optimization module can revert any of its components, such as the solutions matrix, to a previous version. The optimization module then again checks whether there are more base and composite objects to consider in block 1610.
If the optimization module determines that the solutions matrix contains one possible solution of values for all the considered base objects, the optimization module removes all the other values for the base objects, as shown in block 1614. The optimization module then selects the values from the sole possible solution in the solutions matrix as the values for each base object. Process 1600 then ends.
If the optimization module determines that the solutions matrix contains two or more possible solutions, the optimization module applies pre-configured tiebreakers, as shown in block 1616. It should be appreciated that there are no more base or composite objects to apply or consider to expand and filter the solutions matrix by the time the optimization module is processing block 1616. An example tiebreaker may compare the values in the possible solutions with historical values for the corresponding base objects. Moreover, the difference from historical values for the various base objects may be weighted.
For example, if process 1600 results in two possible solutions, where each possible solution includes values for three base objects, the optimization module may calculate the deviation or absolute difference of each value from a historical value, such as a volume weighted average value, for the corresponding base object, and sum the total deviations for the three objects. The solution whose values deviate the least from the historical value for each object is selected. In one embodiment, the deviation for some of the base objects may be weighted differently than the deviation for other base objects.
In one embodiment, the optimization module may include more than one tiebreaker, so that if a first tiebreaker does not result in a single solution, a second tiebreaker is applied. If, after all tiebreakers are applied, the solutions matrix still includes more than one possible solution, the optimization module may select a possible solution at random or based on alphabetical order.
The optimization module, in one embodiment, accordingly continues the iterative process of generating possible solutions for the solutions matrix and filtering or eliminating possible solutions from the solutions matrix based on the relationships defined by composite objects until all of the objects are processed and analyzed and until one solution remains in the solutions matrix. If all of the objects are processed and analyzed and the solutions matrix includes more than one possible solution, the optimization module applies tiebreakers between the remaining solutions, such as determining which solutions deviate from volume weighted average values. In one embodiment, the deviation differences may be weighted differently for different base objects.
The optimization module may be included in or applied to an exchange computer system. In one embodiment, an exchange computer system may convert contracts or legs to base objects and may convert spread instruments to composite objects.
When applied to a financial exchange computer system, the embodiments described herein may utilize trade related electronic messages such as mass quote messages, individual order messages, modification messages, cancelation messages, etc., so as to enact trading activity in an electronic market. The trading entity and/or market participant may have one or multiple trading terminals associated with the session. Furthermore, the financial instruments may be financial derivative products. Derivative products may include futures contracts, options on futures contracts, futures contracts that are functions of or related to other futures contracts, swaps, swaptions, or other financial instruments that have their price related to or derived from an underlying product, security, commodity, equity, index, or interest rate product. In one embodiment, the orders are for options contracts that belong to a common option class. Orders may also be for baskets, quadrants, other combinations of financial instruments, etc. The option contracts may have a plurality of strike prices and/or comprise put and call contracts. A mass quote message may be received at an exchange. As used herein, an exchange 100 includes a place or system that receives and/or executes orders.
It should be appreciated that the disclosed embodiments may be applicable to other types of messages depending upon the implementation. Further, the messages may comprise one or more data packets, datagrams or other collection of data formatted, arranged configured and/or packaged in a particular one or more protocols, e.g., the FIX protocol, TCP/IP, Ethernet, etc., suitable for transmission via a network 214 as was described, such as the message format and/or protocols described in U.S. Pat. No. 7,831,491 and U.S. Patent Publication No. 2005/0096999 A1, both of which are incorporated by reference herein in their entireties and relied upon. Further, the disclosed message management system may be implemented using an open message standard implementation, such as FIX Binary, FIX/FAST, or by an exchange-provided API.
Traders trading on an exchange including, for example, exchange computer system 100, often desire to trade multiple financial instruments in combination. Each component of the combination may be called a leg. Traders can submit orders for individual legs or in some cases can submit a single order for multiple financial instruments in an exchange-defined combination. Such orders may be called a strategy order, a spread order, or a variety of other names.
A spread instrument may involve the simultaneous purchase of one security and sale of a related security, called legs, as a unit. The legs of a spread instrument may be options or futures contracts, or combinations of the two. Trades in spread instruments are executed to yield an overall net position whose value, called the spread, depends on the difference between the prices of the legs. Spread instruments may be traded in an attempt to profit from the widening or narrowing of the spread, rather than from movement in the prices of the legs directly. Spread instruments are either “bought” or “sold” depending on whether the trade will profit from the widening or narrowing of the spread, respectively. An exchange often supports trading of common spreads as a unit rather than as individual legs, thus ensuring simultaneous execution of the two legs, eliminating the execution risk of one leg executing but the other failing.
One example of a spread instrument is a calendar spread instrument. The legs of a calendar spread instrument differ in delivery date of the underlier. The leg with the earlier occurring delivery date is often referred to as the lead month contract. A leg with a later occurring delivery date is often referred to as a deferred month contract. Another example of a spread instrument is a butterfly spread instrument, which includes three legs having different delivery dates. The delivery dates of the legs may be equidistant to each other. The counterparty orders that are matched against such a combination order may be individual, “outright” orders or may be part of other combination orders.
In other words, an exchange may receive, and hold or let rest on the books, outright orders for individual contracts as well as outright orders for spreads associated with the individual contracts. An outright order (for either a contract or for a spread) may include an outright bid or an outright offer, although some outright orders may bundle many bids or offers into one message (often called a mass quote).
A spread is an order for the price difference between two contracts. This results in the trader holding a long and a short position in two or more related futures or options on futures contracts, with the objective of profiting from a change in the price relationship. A typical spread product includes multiple legs, each of which may include one or more underlying financial instruments. A butterfly spread product, for example, may include three legs. The first leg may consist of buying a first contract. The second leg may consist of selling two of a second contract. The third leg may consist of buying a third contract. The price of a butterfly spread product may be calculated as:
Butterfly=Leg1-2xLeg2+Leg3 (equation 1)
In the above equation, Leg1 equals the price of the first contract, Leg2 equals the price of the second contract and Leg3 equals the price of the third contract. Thus, a butterfly spread could be assembled from two inter-delivery spreads in opposite directions with the center delivery month common to both spreads.
A calendar spread, also called an intra-commodity spread, for futures is an order for the simultaneous purchase and sale of the same futures contract in different contract months (i.e., buying a September CME S&P 500® futures contract and selling a December CME S&P 500 futures contract).
A crush spread is an order, usually in the soybean futures market, for the simultaneous purchase of soybean futures and the sale of soybean meal and soybean oil futures to establish a processing margin. A crack spread is an order for a specific spread trade involving simultaneously buying and selling contracts in crude oil and one or more derivative products, typically gasoline and heating oil. Oil refineries may trade a crack spread to hedge the price risk of their operations, while speculators attempt to profit from a change in the oil/gasoline price differential.
A straddle is an order for the purchase or sale of an equal number of puts and calls, with the same strike price and expiration dates. A long straddle is a straddle in which a long position is taken in both a put and a call option. A short straddle is a straddle in which a short position is taken in both a put and a call option. A strangle is an order for the purchase of a put and a call, in which the options have the same expiration and the put strike is lower than the call strike, called a long strangle. A strangle may also be the sale of a put and a call, in which the options have the same expiration and the put strike is lower than the call strike, called a short strangle. A pack is an order for the simultaneous purchase or sale of an equally weighted, consecutive series of four futures contracts, quoted on an average net change basis from the previous day's settlement price. Packs provide a readily available, widely accepted method for executing multiple futures contracts with a single transaction. A bundle is an order for the simultaneous sale or purchase of one each of a series of consecutive futures contracts. Bundles provide a readily available, widely accepted method for executing multiple futures contracts with a single transaction.
Thus, an exchange may match outright orders, such as individual contracts or spread orders (which as discussed above could include multiple individual contracts). The exchange may also imply orders from outright orders. For example, exchange computer system 100 may derive, identify, and/or advertise, publish, display, or otherwise make available for trading orders based on outright orders.
For example, two different outright orders may be resting on the books or be available to trade or match. The orders may be resting because there are no outright orders that match the resting orders. Thus, each of the orders may wait or rest on the books until an appropriate outright counteroffer comes into the exchange or is placed by a user of the exchange. The orders may be for two different contracts that only differ in delivery dates. It should be appreciated that such orders could be represented as a calendar spread order. Instead of waiting for two appropriate outright orders to be placed that would match the two existing or resting orders, the exchange computer system may identify a hypothetical spread order that, if entered into the system as a tradable spread order, would allow the exchange computer system to match the two outright orders. The exchange may thus advertise or make available a spread order to users of the exchange system that, if matched with a tradable spread order, would allow the exchange to also match the two resting orders. Thus, the match engine is configured to detect that the two resting orders may be combined into an order in the spread instrument and accordingly creates an implied order.
In other words, the exchange's matching system may imply the counteroffer order by using multiple orders to create the counteroffer order. Examples of spreads include implied IN, implied OUT, 2nd- or multiple-generation, crack spreads, straddle, strangle, butterfly, and pack spreads. Implied IN spread orders are derived from existing outright orders in individual legs. Implied OUT outright orders are derived from a combination of an existing spread order and an existing outright order in one of the individual underlying legs. Implied orders can fill in gaps in the market and allow spreads and outright futures traders to trade in a product where there would otherwise have been little or no available bids and asks.
For example, implied IN spreads may be created from existing outright orders in individual contracts where an outright order in a spread can be matched with other outright orders in the spread or with a combination of orders in the legs of the spread. An implied OUT spread may be created from the combination of an existing outright order in a spread and an existing outright order in one of the individual underlying leg.
By linking the spread and outright markets, implied spread trading increases market liquidity. For example, a buy in one contract month and an offer in another contract month in the same futures contract can create an implied market in the corresponding calendar spread. An exchange may match an order for a spread product with another order for the spread product. Some existing exchanges attempt to match orders for spread products with multiple orders for legs of the spread products. With such systems, every spread product contract is broken down into a collection of legs and an attempt is made to match orders for the legs. Examples of implied spread trading includes those disclosed in U.S. Patent Publication No. 2005/0203826, entitled “Implied Spread Trading System,” the entire disclosure of which is incorporated by reference herein and relied upon. Examples of implied markets include those disclosed in U.S. Pat. No. 7,039,610, entitled “Implied Market Trading System,” the entire disclosure of which is incorporated by reference herein and relied upon.
As an intermediary to electronic trading transactions, the exchange bears a certain amount of risk in each transaction that takes place. To that end, the clearing house implements risk management mechanisms to protect the exchange. One or more of the modules of the exchange computer system 100 may be configured to determine settlement prices for constituent contracts, such as deferred month contracts, of spread instruments, such as for example, settlement module 140.
One or more of the above-described modules of the exchange computer system 100 may be used to gather or obtain data to support the settlement price determination, as well as a subsequent margin requirement determination. For example, the order book module 110 and/or the market data module 112 may be used to receive, access, or otherwise obtain market data, such as bid-offer values of orders currently on the order books. The trade database 108 may be used to receive, access, or otherwise obtain trade data indicative of the prices and volumes of trades that were recently executed in a number of markets. In some cases, transaction data (and/or bid/ask data) may be gathered or obtained from open outcry pits and/or other sources and incorporated into the trade and market data from the electronic trading system(s).
In some cases, the outright market for the deferred month or other constituent contract may not be sufficiently active to provide market data (e.g., bid-offer data) and/or trade data. Spread instruments involving such contracts may nonetheless be made available by the exchange. The market data from the spread instruments may then be used to determine a settlement price for the constituent contract. The settlement price may be determined, for example, through a boundary constraint-based technique based on the market data (e.g., bid-offer data) for the spread instrument, as described in U.S. Patent Publication No. 2015/0073962 entitled “Boundary Constraint-Based Settlement in Spread Markets” (“the '962 Publication”), the entire disclosure of which is incorporated by reference herein and relied upon. Settlement price determination techniques may be implemented to cover calendar month spread instruments having different deferred month contracts.
As discussed above, a calendar spread order may be associated with two contracts or legs, and a butterfly spread order may be associated with three contracts or legs. As discussed above, the exchange system may calculate a settlement price for a contract. It should be appreciated that if an exchange system calculates a settlement price for a contract, the calculated settlement price also affects calendar spread orders and butterfly spread orders that are associated with that contract.
The settlement price that is selected by the exchange for a contract may be a settlement price that falls in a range defined by and including the lowest offer and highest bid for that contract. In some instances, multiple combinations of settlement prices may fall into such a range defined by and including the lowest offer and highest bid for a contract. For example, when the boundary constraint-based procedure of the '962 Publication is implemented, there may be instances where multiple combinations reside between the top of book or best bid and the top of book or best ask of the outright contracts. In one embodiment, the optimization module evaluates each of the potential solutions against the calendar spread and the butterfly markets associated with the outright contracts to select an optimum settlement price so that all relevant price discovery is accounted for in the value determination.
For example, an exchange computer system may calculate settlement prices for two contracts for the same underlier that differ only in delivery date. In some cases, the computer system's settlement calculation process may result in more than one settlement price for an individual contract. Thus, the system would need to select one value as the final settlement value or price. Once a value is selected for or assigned to each contract, the exchange may calculate an implied spread value between the two settlement prices for the two contracts. Each set of outright contract prices may imply a corresponding spread value. For example, for each pair of possible settlement prices for two different contracts, the exchange can calculate an implied calendar spread value, where the two legs are the two different contracts. Similarly, for three possible settlement prices for three different contracts, the exchange can calculate an implied butterfly spread value, where the three legs are the three different contracts. Thus, multiple prices may be possible values for an individual contract, and multiple contracts (that differ only in delivery dates) may make up a spread instrument.
For example, the implied spread values derived from two outright contracts can be tested against the tradable market in the spread instrument itself to determine which settlement prices for the underlying contracts would be valid for both the underlying contract market as well as the market in the tradable spread instrument.
Thus, the exchange may attempt to organize the values of the contracts so that if given a choice between multiple values for the contracts, the exchange is able to efficiently determine an optimum value for multiple contracts. However, this can require an exceedingly high amount of processing. For example, the exchange system's computers would need to calculate and keep track of data associated with all of the possible settlement prices for each contract, calculate an implied calendar spread value for each pair of possible settlement prices between two contracts, calculate an implied butterfly spread value for each triplet permutation of possible settlement prices between three contracts, and compare the calculated implied spread values (both calendar and butterfly spread values) against the tradable spread (both calendar and butterfly spread) instrument to determine which settlement prices should be selected. Such calculations are computationally expensive and may require too many computing resources to justify any benefits of selecting an optimum settlement price, such as price discovery and increased transparency. However, if the computations can be performed efficiently, e.g., quickly or in a short amount of time, the increase in computing time and costs may be justified by the overall benefits, and the exchange may experience a better assessment of risk due to the more accurate valuations. Thus, it would be beneficial to efficiently compute and select the optimum prices or values for each contract involved.
For example, a product may include several quarterly contracts that differ only in delivery date. For example, a Eurodollar futures contract offered by the CME may include forty quarterly contracts, e.g., March, June, September, and December, for ten years, e.g., the next ten years, e.g., 2016 to 2026. Each contract is a Eurodollar futures contract that has a delivery date of one of March, June, September, or December in one of ten years. The exchange may receive outright orders for any one of the forty contracts. Each of these futures contracts may be represented as a base object in the exchange computing system or environment.
The exchange may also receive orders for calendar spread instruments between any two of the forty contracts. The calendar spread orders may be represented as composite objects in the exchange computing system or environment.
In one embodiment, based on historical market data, and to reduce the number of permutations the exchange must monitor, the exchange may limit consideration to only certain spread instruments. The exchange may additionally or alternatively expand consideration to a wider set of spread instruments to include additional information that becomes relevant.
In one embodiment, based on historical market data, and to reduce the number of permutations the exchange must monitor, the exchange may limit calendar spread trading to 3-month calendar spread contracts (e.g., March-June 2016 calendar spread contracts), 6-month calendar spread contracts (e.g., March-September 2016 calendar spread contracts), 9-month calendar spread contracts (e.g., March-December 2016 calendar spread contracts) and 12-month calendar spread contracts (e.g., March 2016-March 2017 calendar spread contracts).
The exchange may also receive outright orders for butterfly spread orders between any three of the forty contracts. The butterfly spread orders may likewise be represented as composite objects in the exchange computing system or environment. In one embodiment, based on historical market data, and to reduce the number of permutations the exchange must monitor, the exchange may limit butterfly spread trading to 3-month butterfly spread contracts (e.g., March-June 2016 butterfly spread contracts) and 12-month butterfly spread contracts (e.g., March 2016-March 2017 butterfly spread contracts). It should be appreciated that the exchange calculates implied contract and spread values for contracts and spreads offered or traded on the exchange.
Thus, the exchange offers multiple contract or outright instruments that differ only in delivery dates, e.g., 40 Eurodollar contracts that are identical except for delivery dates, calendar spread instruments for a variety of pairs of the contracts, and butterfly spreads for a variety of triplets of the contracts. In addition, each contract or outright instrument, calendar spread instrument, and butterfly spread instrument may have multiple possible values, or prices that are valid for the market for that respective instrument. In one embodiment, each instrument offered can have at least two possible values that are valid for the respective instrument, namely, the tradable bid and the tradable ask. When multiple solutions are valid for each of the various instruments, the disclosed embodiments may be implemented to efficiently determine which of the multiple possible values is to be selected for the various outright contracts.
The disclosed settlement system may test implied calendar and butterfly spread values associated with possible price solutions, which are based on outright contracts, against tradable calendar and butterfly spread instrument markets, and eliminate possible price solutions based on the test. Eliminating price solutions from the set of possible price solutions reduces overall computing load on a settlement module of an exchange system and allows the exchange system to test related instrument relationships without an unnecessary or unjustifiable computational delay.
For example, a financial instrument may include several contracts, each having an outright market bid and offer. The contracts may be quoted in price increments called ticks. The bid and offer may be separated by multiple, e.g., three, ticks. Any of the ticks that are between the market bid and offer, including the bid and offer, may be valid settlement prices for the contract. Any of these ticks may thus be selected by the exchange as a settlement price for the contract. For example, a contract having a 45 bid and a 50-offer quoted in 1-unit increments, or ticks, could settle at 45, 46, 47, 48, 49 or 50 without violating the market. Thus, the exchange could select to settle the price for that contract at any of these prices, and each of these would be considered valid, as that term is used herein. Or, the bid and offer may be exactly one tick apart, meaning that the exchange could select either the bid or the offer as the settlement price and have selected valid prices for the contract, but there are no ticks between the bid and the offer that can be selected.
Settlement prices selected for two related contracts, e.g., December 2015 and March 2016 Eurodollar contracts, may or may not be valid for the tradable Eurodollar calendar spread instrument between December 2015 and March 2016, depending on the value of the tradable Eurodollar calendar spread instrument between December 2015 and March 2016. Similarly, settlement prices selected for three related contracts, e.g., December 2015, March 2016 and June 2016 Eurodollar contracts, may or may not be valid for a tradable butterfly spread instrument between December 2015, March 2016 and June 2016, depending on the value of the tradable butterfly spread instrument between December 2015, March 2016 and June 2016.
As discussed above, several prices or values may be considered to be valid for a tradable market. For example, for a given market, the tradable bid, the tradable offer, and any ticks between the tradable bid and offer may be possible values for that market. Thus, an exchange may be able to select any one of those values as the settlement price for a given contract, where each value is valid for the outright market for that contract.
For example, as shown in
Referring now to
When the Contract1 and the Contract2 solutions are considered together, there are NUMContract1×NUMContract2 number of possible solutions that are valid for both Contract1 and Contract2, where NUMContract1 represents the number of possible solutions for Contract1 and NUMContract2 represents the number of possible solutions for Contract2. For example, there are 3×2=6 possible solutions, shown in
To consider the effect of each possible solution on the associated tradable spread instruments, the exchange computer system may perform transactions on the values stored in the matrix, or calculate an implied spread value for each of the possible solutions and add that data to the first matrix, as illustrated in
Thus, the optimization module may be said to test Matrix 1 against the market in the tradable spread instrument between Contract1 and Contract2. In other words, the possible solutions in Matrix 1 are filtered or reduced based on the tradable spread instrument between Contract1 and Contract2. The tradable spread instrument between Contract1 and Contract2 in turn may also have more than one possible value. CalendarSpread1-2 may be a calendar spread between Contract1 and Contract2. As shown in
Thus, the optimization module filters the first matrix based on whether or not implied calendar spreads between possible contract prices are valid for the associated tradable calendar spread markets. In other words, the possible solutions that have associated implied spreads that are outside of the tradable calendar spread markets are eliminated from the first matrix, resulting in a second matrix. The first matrix of possible solutions has thus been decreased or reduced by filtering or testing the matrix against tradable spread data.
To summarize, the second matrix lists the possible solutions for two contracts, Contract1 and Contract2, where: (1) the values are valid for both outright contract markets, and (2) the implied calendar spread between the values for each solution is valid for the tradable calendar spread market for the same two contracts. In contrast, the values of the possible solutions in the first matrix can only be said to be valid for both outright contract markets. It should accordingly be appreciated to arrive at matrix 2 from matrix 1, the optimization module has eliminated the possible solutions for Contract1 and Contract2 whose implied calendar spread value is not valid for the market for the tradable calendar spread market between Contract1 and Contract2.
It should be appreciated that although
Once the matrix of possible solutions between two contracts has been filtered to eliminate certain solutions whose implied calendar spread value is not valid for the tradable calendar spread market between the two contracts, the optimization module may further process the remaining data in view of outright data for yet another contract. Again, this further processing, described below, is only performed on the reduced and filtered data set, resulting in an increase in processing speed and efficiency without eliminating any useful solutions.
For example, as shown in
The optimization module then adds the Contract3 solutions to the Contract1 and Contract2 possible solutions in Matrix 2, resulting in Matrix 3 illustrated in
Moreover, it should be noted Contract3 possible values are combined with the possible solutions in Matrix 2 to create additional permutations and possible solutions. However, solutions such as solutions 3, 5 and 6 which were eliminated in Matrix 2 are not considered in conjunction with Contract3's possible values. For the eliminated solutions, the optimization module does not need to even calculate the resulting combination of Contract1, Contract2 and Contract3, or the implied spread between Contract1 and Contract3. Thus, eliminating solutions that are not valid for the tradable calendar spread market between Contract1 and Contract2, as in Matrix 2, reduces the number of calculations performed when Contract3 data is considered. When the Matrix 2 solutions are considered in conjunction with the Contract3 possibilities, Possible Solutions 7, 8 and 9 are newly added to the overall possible solutions, resulting in Matrix 3.
The optimization module then calculates the implied spread between two of the three respective contracts for each possible solution, namely, the implied spread between Contract1 and Contract3 for possible solutions 1, 2, 4, 7, 8 and 9. This implied spread for each possible solution is listed in the third column of Matrix 3 in
The optimization module then compares or tests the implied calendar spread between Contract1 and Contract3 for each possible solution in Matrix 3 against the possible values for the tradable calendar spread market between Contract1 and Contract3. CalendarSpread1-3 may be a calendar spread between Contract1 and Contract3. As shown in
As shown in
The optimization module eliminates Possible Solutions 4 and 8 from Matrix 3, resulting in Matrix 4 illustrated in
The optimization module next compares or tests the implied calendar spread between Contract2 and Contract3 for each possible solution in Matrix 4 against the possible values for the tradable calendar spread between Contract2 and Contract3. CalendarSpread2-3 may be a calendar spread between Contract2 and Contract3. As shown in
As shown in
The optimization module eliminates Possible Solutions 2 and 7, resulting in Matrix 5 illustrated in
The optimization module next compares or tests the implied butterfly spread between Contract1, Contract2 and Contract3 for each possible solution in Matrix 5 against the possible values for the tradable butterfly spread instrument market between Contract1, Contract2 and Contract3. ButterflySpread1-2-3 may be a butterfly spread between Contract1, Contract2, and Contract3. As shown in
As shown in
The optimization module eliminates Solution 1, resulting in Matrix 6 illustrated in
It should be appreciated that in the examples of
It should also be appreciated that the possible solutions and sizes of the matrices in
For example, a contract, e.g., June 2015 Eurodollar contract, market may have a 9969 bid and a 9969.50 offer. Moreover, the market may have a 0.5 tradable tick, which is the price increment in which prices are quoted. Thus, there are two possibilities for the settlement of this contract, namely, 9969 or 9969.50. The exchange may select either value as a settlement price for the June 2015 Eurodollar contract, because both are valid for the June 2015 Eurodollar contract market. If the market had a 9969 bid and a 9970 offer with a 0.5 tick, then there would have been three possible settlement prices, namely, 9969, 9969.50 or 9970.
Additionally, the September 2015 Eurodollar contract market may have a 9956.50 bid and a 9957 offer, also with a 0.5 tick. Thus, there are two possibilities for the settlement of this contract, namely, 9956.50 and 9957. The exchange may select either value as a settlement price for the September 2015 Eurodollar contract, because both are valid for the September 2015 Eurodollar contract market. The markets for the June and September outright contracts are illustrated in
When both the June and September Eurodollar contract markets are considered together, there are four possible solutions for the settlement prices of the June and September contracts, namely, [9969, 9956.50], [9969, 9957], [9969.50, 9956.50], and [9969.50, 9957], as shown in the first two columns of the table in
Additionally, the market in the tradable spread instrument between the June and September contracts may have a 12 bid and 12.50 offer, also with a 0.5 tick. The market for the June-September spread contracts are illustrated in
Before selecting one of the four different possible combinations of settlement prices for the June and September contracts, the disclosed systems and method evaluate each of the potential contract solutions against the June 2015 to September 2015 Eurodollar spread market of 12 bid and 12.5 offer. In particular, the fourth column of the table in
The optimization module may also consider the possible solutions against additional contracts. It should be appreciated that the more contracts that are considered before selecting settlement prices, the more liquidity is maintained or created on the exchange. For example, the December 2015 Eurodollar contract market may have a 9939 bid and a 9939.50 offer, with a 0.5 tick. Thus, there are two possibilities for the settlement of this contract, namely, 9939 and 9939.50. The exchange may select either value as a settlement price for the December 2015 Eurodollar contract, because both are valid for the December 2015 Eurodollar contract market.
When the December 2015 contract is considered in addition to the June and September 2015 contracts, the number of possible solutions that are valid for these three contracts increases. Thus, the amount of data stored in memory and operated upon by the optimizing system and the price settlement system increases. In particular, the number of possible solutions increases from 3 possible solutions, namely, solutions 1, 2 and 4, to 3×2=6 possible solutions. Each one of solutions 1, 2 and 4 leads to two different solutions when considered in conjunction with the 2 possible solutions for the December 2015 contract, as shown in the second table in
The optimization module then calculates the implied June-December spread for each possible solution, as shown in the third column of the table in
As shown in
As shown in
The optimization module next considers the June, September and December butterfly spread instrument, which may have a −5.5 bid and −5 offer, as shown in
In one embodiment, the optimization module may attempt to determine the optimal solution for three different contracts by first considering all the permutations of possible settlement prices between two of the contracts, e.g., the first and second contracts, and filtering those permutations by eliminating those solution pairs whose implied spread is not valid for the tradable spread for that same contract pair. The surviving solution pairs are then expanded by considering permutations of the surviving solution pairs with a third contract, resulting in possible settlement prices for three contracts, and filters those permutations by eliminating solutions for which the implied spread value between two of the contracts, e.g., the first and third contracts, is not valid for the tradable spread for those same two contracts.
Thus, it should be appreciated that the optimization module strategically considers contract combinations and eliminates those solutions in which the implied spread value between contract prices is not valid for the tradable spread instrument for those same contracts. In one embodiment, the optimization module begins by considering a pair of contracts because without at least two contracts, there can be no spread to use to filter the possible solution set. Each time a new contract is considered, the number of possible solutions increases. For example, when the optimization module considers a third contract, the number of combinations of possible solutions increases. However, consideration of the third contract also allows the optimization module to filter the combinations of possible solutions by elimination those solutions where an implied spread between contracts fails the tradable spread instrument between the contracts.
In other words, each time a new contract is considered by the optimization module, the number of possible solutions is expanded due to the increase in possible combinations based on the new contract, and that expanded solution step is then filtered by eliminating solutions where an implied spread between contracts including the new contract fails the corresponding tradable spread instrument between contracts including the new contract. Moreover, the optimization module may begin with two contracts, consider the possible solutions and filter those solutions based on the implied spread/tradable spread test described above, then consider an additional contract, which involves expanding the number of possible solutions and filtering based on the implied spread/tradable spread test described above, then consider another additional contract, which involves expanding the number of possible solutions and filtering based on the implied spread/tradable spread test described above, and so on, e.g., in an iterative fashion, until the optimization module considers a predetermined number of contracts.
In one embodiment, the optimization module begins with two contracts, determines the set of possible solutions, filters the solutions by eliminating solutions whose implied spread value is not valid for the corresponding tradable spread resulting in a new solution set, considers a new contract, expands the current solution set by including the new possible combinations due to the new contract, filters the expanded solution set by eliminating solutions where an implied spread between contracts including the new contract fails the corresponding tradable spread instrument between contracts including the new contract resulting in a new solution set, and continues this process for new contracts. The process may end when there are no more new contracts to consider. The process may also end when eliminating solutions based on the implied spread/tradable spread iterative test described above results in no possible solutions. In this case, the optimization module selects a possible solution from a previous solution set having at least one possible solution.
If a possible solution set results in more than solution but the next filter results in no possible solutions, or if there are multiple possible solutions after all new contracts have been considered, the optimization module selects one of the possible solutions by comparing how close the solutions are to each contract's volume weighted average price. For example, the optimization module's process may result in two possible solutions, solution 1 having contract prices Contract1Price1, Contract2Price1 and Contract3Price1, and solution 2 having contract prices Contract1Price2, Contract2Price2 and Contract3Price2. The optimization module needs to select one of these two possible solutions for pricing three contracts, Contract1, Contract2 and Contract3. For each solution, the optimization module compares each contract price to the respective contract's volume weighted average price and for each solution, sums up the absolute values of the difference between each contract price to the respective contract's volume weighted average price, and picks the solution with the smallest sum. For example, as shown in
In one embodiment, the nearest month contract, e.g., Contract 1, price difference from VWAP is weighted more than the other months. For example, as shown in
The weighting factors used for the different contracts may be modified or adjusted. For example, the system may assign a different weighting factor to the different months.
It should be appreciated that while the example figures depict an array or matrix holding the relevant data, the data may be stored in the computer's memory in any convenient form or structure, such as a linked list, or through the use of pointers. As long as the computer can store the possible combinations of contract values and the associated differences between two values and their relationships, the actual location of the stored values and the format of the data and relationships are implementation specific.
Although some of the examples discussed herein relate to futures contracts and associated spread instruments, the disclosed embodiments for the optimization module may be applicable to options contracts, and in particular, to strike prices options contracts. For example, each options contract may include multiple strike prices, and an exchange system may receive multiple values for each strike price for an outright options contract. Moreover, even after the settlement module processes the received values, the exchange may have the choice of selecting one of multiple values for the strike prices for the options contracts. Thus, the optimization module may convert or translate each strike price for each options contract into a base object. The system may also convert spread instruments between strike prices into composite objects.
In one embodiment, the steps of
The optimization module may first receive a plurality of values for each of a plurality of base objects including a first and second base object, as shown in block 3302. The optimization module may also receive a plurality of values for a first composite object associated with the first and second base objects, as shown in block 3304. Thus, the optimization module receives values for base and composite objects.
The optimization module may then generate and store in the memory a solution set including combinations of values of the first and second base objects, as shown in block 3306. The optimization module may then, for each combination of values in the solution set, generate first transaction results by computing transactions between the values of the first and second base objects, as shown in block 3308.
The optimization module may then compare each of the first transaction results to a first range of values including the values of the first composite object, as shown in block 3310. The optimization module may then remove, from the solution set and from the memory, the combinations of the values of the first and second base objects corresponding to the first transaction results that are outside of the first range of values, as shown in block 3312.
The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.
While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.
Similarly, while operations are depicted in the drawings and described herein in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.
The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.
It is therefore intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that it is the following claims, including all equivalents, that are intended to define the spirit and scope of this invention.
This application is a continuation under 37 C.F.R. 1.53(b) of U.S. patent application Ser. No. 15/000,793 filed Jan. 19, 2016, now U.S. Pat. No. ______ , which is hereby incorporated by reference in its entirety and relied upon.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15000793 | Jan 2016 | US |
| Child | 16535617 | US |
