JP2001034660A - Function decentralized type control method for ordering management system for transaction market - Google Patents
Function decentralized type control method for ordering management system for transaction marketInfo
- Publication number
- JP2001034660A JP2001034660A JP24026399A JP24026399A JP2001034660A JP 2001034660 A JP2001034660 A JP 2001034660A JP 24026399 A JP24026399 A JP 24026399A JP 24026399 A JP24026399 A JP 24026399A JP 2001034660 A JP2001034660 A JP 2001034660A
- Authority
- JP
- Japan
- Prior art keywords
- order
- function
- market
- status
- processing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
【0001】[0001]
【発明に属する技術分野】取引市場(東京証券取引所
等)への発注システムにおける、オーダ管理機能部、ラ
イン制御機能部とデータベース部(メモリ展開可)に処
理を分散することにより、システム全般の拡張性及び発
注能力の強化(取引市場の注文における執行処理の制御
を行うことにより複雑な注文処理)、フォルトトレラン
ス(システム無停止技術)への対応を目的とする発明で
ある。BACKGROUND OF THE INVENTION In an ordering system for a trading market (Tokyo Stock Exchange, etc.), the processing is distributed to an order management function section, a line control function section, and a database section (memory development is possible), so that the entire system can be realized. The present invention aims at enhancing expandability and ordering capability (complex order processing by controlling execution processing in trading market orders) and fault tolerance (system non-stop technology).
【0002】[0002]
【従来の技術】各注文データは、オーダ管理機能部に登
録され、データベース部に内容を記録された後に、指定
された市場に接続されているライン制御機能部へオーダ
管理機能部より送信される。注文データは各制御系(デ
ータベース部、ライン制御機能部)へ受け渡す(プッシ
ュ型)される形で転送される。オーダ管理機能部よりデ
ータベース部への書込みとライン制御機能部への注文の
転送は注文入力が行われた際に随時処理(注文データの
入力にエラーが無いことが前提)されるため、実質、証
券取引所等が提供している注文受付形態(成行、指値、
寄り、引け、不成り)のみである。2. Description of the Related Art Each order data is registered in an order management function unit, recorded in a database unit, and then transmitted from the order management function unit to a line control function unit connected to a designated market. . The order data is transferred (push type) to each control system (database unit, line control function unit). Since the writing from the order management function unit to the database unit and the transfer of the order to the line control function unit are processed at any time when the order is input (assuming that there is no error in the input of the order data), Order reception forms provided by stock exchanges (marketing, limit,
(Close, close, unsuccessful).
【0003】[0003]
【発明が解決しようとする課題】これまでのシステムは
1つのオーダ管理機能が、複数又は全ての市場の各取引
について一元管理していたため、他市場のメンテナンス
(修正)による影響をダイレクトに受ける形になってい
る。そのため接続する取引市場等(システム)が増える
とシステム全体(特にオーダ管理機能)の修正が必要と
なり、発注管理システムを拡張・開発しようとする場
合、その取引市場に合わせたインターフェースに対応す
るために膨大な開発コストの負担を余儀なくされる。従
来の発注管理システムにおいて、オーダ管理機能は、対
ライン(接続市場)に対する制御を行う必要があり処理
負担が高くなるだけではなく、システム障害時の制御
(データの受渡等)が難しくなる。特殊注文(一定の時
間や目標とする価格になった場合に注文の発注、注文の
訂正、注文の取消を行う等)を処理する場合、証券会社
等の顧客や担当者がその都度に注文指示を出さなければ
ならない。そのため、執行要員の確保や価格等の市況情
報を監視する特殊な技術が必要となり、高度な注文を簡
単に処理する事ができない状況である。従来型の発注管
理システムのデータ処理および制御機能ではシステムで
の一層の拡張性、信頼性および経済性、注文処理におけ
る一層の合理化、電子化を促すことが困難である。In the conventional system, since one order management function centrally manages each transaction in a plurality or all markets, the system is directly affected by maintenance (modification) in another market. It has become. Therefore, if the number of trading markets (systems) to be connected to increases, the entire system (particularly the order management function) needs to be modified. When expanding and developing an order management system, it is necessary to use an interface that matches the trading market. The enormous development costs have to be borne. In the conventional order management system, the order management function needs to control the line (connected market), which not only increases the processing load but also makes it difficult to control (data transfer, etc.) when a system failure occurs. When processing special orders (ordering, correcting orders, canceling orders at a certain time or when a target price is reached, etc.), customers and representatives of securities companies etc. give orders each time Must be issued. For this reason, a special technique for monitoring market information such as securing of execution personnel and prices is required, and it is difficult to process advanced orders easily. With the data processing and control functions of conventional order management systems, it is difficult to promote more scalability, reliability and economy in the system, more rationalization of order processing, and digitization.
【0004】[0004]
【課題を解決するための手段】従来のオーダ管理機能を
分解し、オーダ管理機能部、データベース部、ライン制
御部にコントロールを分散させ、処理の負担を減らすと
共に、各機能の修正時の影響度や対障害性を少なくす
る。注文データの処理において、注文データの内容はデ
ータベース(メモリ展開含む)に登録させる。複数の独
立して稼動するライン制御機能が登録された注文データ
を参照し、該当するその注文データが‘未処理’のステ
ータスの場合のみライン制御機能部が処理できる。注文
データのステイタスの制御はオーダ管理機能が行う他
に、ライン制御機能やトリガー機能も制御する事ができ
る。これが機能分散の基本的な新しい考え方である。ま
た、ライン制御機能部の独立は、接続先市場が増えた場
合でも単純にライン制御機能(インターフェース)を作
成するのみで、その内容(市場名等)をデータベース上
に登録するのみで稼動・接続できる。これによりデータ
ベース部を基本とするオーダ管理機能部の修正が不用と
なり、新規市場接続の作業(システム開発等)が大幅に
簡素化されることになる。Means for Solving the Problems The conventional order management function is disassembled and the control is distributed to the order management function section, database section and line control section, thereby reducing the processing load and the degree of influence when each function is modified. And disability. In the processing of the order data, the contents of the order data are registered in a database (including memory development). The line control function unit refers to order data in which a plurality of independently operating line control functions are registered, and can process the line control function unit only when the corresponding order data has a status of “unprocessed”. The control of the status of the order data can be performed not only by the order management function but also by a line control function and a trigger function. This is the basic new concept of function distribution. Independent of the line control function unit, even if the number of connected markets increases, simply create a line control function (interface) and operate and connect only by registering its contents (market name etc.) on the database. it can. This eliminates the need to modify the order management function section based on the database section, and greatly simplifies the work of connecting to a new market (system development, etc.).
【0005】[0005]
【発明の実施の形態】本発明の基本的な構造の特長およ
びその他の特長は上述のような構成であるが、添付図面
を参照しながら図解的に具体例を基に以下の説明を行
う。このシステムの説明にあたり、具体例として東京証
券取引所(以下:東証)に上場している株式を例に説明
する。請求項1で記したように本発明では証券取引等の
少なくとも1つの取引市場において採用されている有価
証券、商品先物等が対象であり、その代表例として説明
上例示しているに過ぎない。なお、このシステム自体は
この分野での技術に長けた人には知られているいずれか
のプログラム言語でコード化することができる。さて図
面に戻ると図1及び図2は注文データが処理されるフロ
ーの全体図を示したものである。今回の説明では図2の
コンピュータのメモリーを利用した場合を例に処理のフ
ローを説明する。はじめに、東証に注文を発注するに
は、銘柄コードを指定し、売買区分(売りたいのか買い
たいのかを指定する項目)、数量(売買したい株数)、
価格(売買したい希望価格)を指定する。さらに、指定
した注文に注文条件(注文有効時間指定のための‘寄
り’、‘引け’等を指定する)を付ける場合もあるが基
本的には前記の注文項目を指定して発注する(図2の
(1))。発注された注文データは出線(2)を通じて
データベース部(3)に書き込まれる。書き込まれた注
文データは記録・保存され取引ログとして利用される。
データベース部に記録された注文データには処理の状態
を示したステイタスと呼ばれるフィールドがあり、注文
データ書き込み時には‘登録中’となる。ステイタスが
‘登録中’となっている注文データは出線(4)を通じ
オーダー管理機能部(5)が読み取り発注可能な注文で
あるかを判断する。判断の内容は前記注文項目の内容に
不備がないか、あるいは当該注文にはトリガーとなる条
件が指定されているかを判断する。仮に注文項目に不備
があればオーダー管理機能部はデータベース部に記録さ
れている当該注文データのステイタスを‘エラー’と変
更する。ステイタスが‘エラー’の場合には出線(2)
を通じて注文入力(1)の画面で確認し、再度、注文入
力する。もし注文データの注文項目に不備がなく、トリ
ガーとなる条件が無ければステイタスを‘未処理’に変
更すると共にデータベース部にある注文データをメモリ
ー部(15)に出線(14)を通じコピーする。今回の
説明ではステイタスが‘未処理’の場合、当該取引市場
に発注可能であることを意味するが、このステイタスの
表示(今回は‘未処理’で説明)は特に他の表現でも可
能である。メモリー部は指定した各取引所毎に分類する
ことも可能である。今回の注文は東証の上場株式である
ため、出線(11t)を通じて常時監視しているライン
制御機能部(10t)が注文データを取り込む。ライン
制御機能部で取り込まれた注文データは各取引所(この
場合東証)のプロトコルに変換し出線(12t)を通じ
て取引市場(13t)に注文を転送する。ではこの注文
にトリガーとなる条件が付いていた場合の処理の流れで
あるが、図2の出線(4)注文のチェック(注文項目の
不備やトリガーのチェック)時にトリガーが付いている
場合、オーダー管理機能部は注文データのステイタスを
‘待機’に変更すると共にトリガー発注機能部(6)に
トリガーとなる条件がクリアされるまで外部情報(7)
を出線(8)を通じ監視・比較する。外部情報とは時間
情報、価格情報(東証相場報道や情報ベンダー等)、約
定情報(注文受付通知や約定通知等)、口座情報(口座
毎の約定情報や口座残高情報等)があり、例えばトリガ
ーの条件が時間要素の場合には、指定したトリガー時間
と現在の時刻を比較したり、価格要素の場合には、指定
したトリガー価格と現在の株価と比較したりしてトリガ
ーの条件がクリアするまで監視する。トリガー発注機能
部で監視・比較し、トリガーの条件がクリアされ取引市
場に注文が発注可能になった場合、オーダー管理機能部
を通じて当該注文データのステイタスを‘未処理’に変
更する。以下の処理は上述と同じである。実際のトリガ
ー設定の手順は第3図の流れにより処理される。トリガ
ーの条件付きの注文設定を開始(16)するにあたり、
その注文設定は新規の注文であるのか、あるいは既に発
注済みの注文に対してトリガーの条件を設定するのかの
判断に分かれる(17)。新規注文の場合はそのまま注
文入力(銘柄コード、売買区分、数量、価格等)する
(18)。既に発注された銘柄に対してトリガーの条件
を設定する場合には注文番号を指定する(19)。この
処理の終了後、それぞれ出線(20)、(21)を通じ
てトリガーの条件を設定した当該銘柄(新規注文の銘柄
あるいは指定した注文番号の銘柄)がトリガーの条件が
クリアした場合に何らかのアクション(当該銘柄の発
注、当該銘柄の訂正、当該銘柄の取消)を起こすのかど
うかを判断する(22)。当該銘柄に対してアクション
を起こす場合には出線(23)を通じてトリガーの条件
の内容を設定する(26)。例えば、前記(18)にお
いてあるA銘柄を200円で1000株買いの注文に対
して14時になったらというトリガーの条件を設定した
場合、では14時になったら何をするのかをここで設定
する(注文の発注なのか指値を成行に訂正するのか
等)。また、判断(22)で当該銘柄以外にアクション
を起こす場合は、例えば前記A銘柄に設定したトリガー
の条件がクリアーされた場合にはB銘柄が何らかのアク
ションを起こすのであるが、その時の銘柄とその内容
(発注する場合は注文項目の設定)を指定する(2
5)。次にトリガーの条件を設定する銘柄とトリガーの
条件がクリアーした場合にアクションを起こす銘柄(ア
クション内容含む)が決まれば、実際にトリガーの条件
を設定するかになる(26)。ここで設定するトリガー
の条件の要素は請求項3で記した時間要素、市況情報を
利用した価格要素等からなる。トリガーの条件の設定が
終了し複数の設定が無ければここでトリガー設定処理は
終了し、実行(28)に移る。さらに複数のトリガーの
条件を指定したい場合には組合せ処理(29)により、
トリガーグループを指定する。これは指定するトリガー
の条件が全てクリアーしなければならないAND条件の
場合は同一トリガーグループを指定し、OR条件(指定
したトリガーの条件がいずれかクリアされた場合に処理
される場合)の場合には異なるトリガーグループを指定
する。また、複数のトリガー条件の設定を行う場合に
は、一度その条件がクリアすれば良いのか、常にクリア
されなければならないのかを指定する(29)。なお、
処理(18)や(25)は複数の銘柄を指定することが
可能であり、俗に言う‘バスケット売買’を指定するこ
とも可能である。この場合は、銘柄コードや注文番号の
代わりにバスケット番号なるものを指定することにな
る。DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The basic structural features and other features of the present invention are as described above, but the following description will be made based on specific examples with reference to the accompanying drawings. In describing this system, a stock listed on the Tokyo Stock Exchange (hereinafter, TSE) will be described as a specific example. As described in claim 1, in the present invention, securities, commodity futures, and the like adopted in at least one trading market such as securities trading are the targets, and are merely illustrated as representative examples for explanation. The system itself can be coded in any programming language known to those skilled in the art. Now, returning to the drawings, FIGS. 1 and 2 show an overall view of a flow in which order data is processed. In this description, the processing flow will be described using a case where the memory of the computer in FIG. 2 is used as an example. First, to place an order with the TSE, specify the stock code, buy / sell category (item to specify whether you want to sell or buy), quantity (the number of shares you want to buy or sell),
Specify the price (the price you want to buy or sell). Further, in some cases, order conditions (designating “close”, “close”, etc. for designating the order effective time) may be added to the designated order, but basically the order is designated by specifying the above-mentioned order item (FIG. 2 (1)). The ordered data is written to the database section (3) through the outgoing line (2). The written order data is recorded and stored and used as a transaction log.
The order data recorded in the database unit has a field called status indicating the processing state, and is "registered" when the order data is written. The order management function unit (5) reads the order data whose status is "registering" through the outgoing line (4) and determines whether the order is orderable. The content of the determination is to determine whether there is any deficiency in the content of the order item or whether a condition to be a trigger is specified in the order. If the order item is defective, the order management function unit changes the status of the order data recorded in the database unit to “error”. Outgoing line if status is 'Error' (2)
Confirm on the screen of order input (1) through, and input the order again. If there is no defect in the order item of the order data and there is no trigger condition, the status is changed to "unprocessed" and the order data in the database unit is copied to the memory unit (15) through the outgoing line (14). In this description, if the status is "unprocessed", it means that it is possible to place an order in the trading market, but this status display (this time described as "unprocessed") can be expressed in other ways. . The memory unit can be classified for each designated exchange. Since this order is a listed stock on the TSE, the line control function unit (10t), which is constantly monitoring through the outgoing line (11t), takes in the order data. The order data taken in by the line control function unit is converted into the protocol of each exchange (TSE in this case) and the order is transferred to the trading market (13t) through the outgoing line (12t). Here is the flow of processing when this order has a trigger condition. If the trigger is attached at the time of outgoing check (4) of the order (check for incomplete items or trigger) in FIG. The order management function unit changes the status of the order data to "standby" and the external information (7) until the trigger condition is cleared in the trigger order function unit (6).
Are monitored and compared through outgoing line (8). External information includes time information, price information (TSE market report, information vendor, etc.), contract information (order acceptance notification, contract notification, etc.), and account information (contract information for each account, account balance information, etc.). If the condition is a time element, the trigger condition is cleared by comparing the specified trigger time with the current time, and if the condition is a price element, comparing the specified trigger price with the current stock price Monitor until. When the trigger condition is cleared and the order can be ordered in the trading market, the status of the order data is changed to “unprocessed” through the order management function unit. The following processing is the same as described above. The actual trigger setting procedure is processed according to the flow of FIG. In starting (16) order setting with trigger condition,
The order setting is divided into a judgment as to whether the order is a new order or whether a trigger condition is set for an already placed order (17). In the case of a new order, the order is entered as it is (brand code, trading category, quantity, price, etc.) (18). When setting trigger conditions for a brand that has already been ordered, an order number is specified (19). After this process is completed, if the trigger condition is cleared for the brand (the brand of the new order or the brand of the designated order number) for which the trigger condition has been set through outgoing lines (20) and (21), an action ( It is determined whether or not an order for the issue, correction of the issue, and cancellation of the issue) will occur (22). When an action is to be taken on the brand, the content of the trigger condition is set through outgoing line (23) (26). For example, when the trigger condition is set at 14:00 for an order for buying 1000 shares for 200 yen for a certain A brand in (18), then what to do at 14:00 is set here ( Whether to place the order or correct the limit to market). In addition, when an action other than the above-mentioned issue is taken in the judgment (22), for example, if the condition of the trigger set for the above-mentioned A issue is cleared, the B issue takes some action. Specify the contents (setting of order items when ordering) (2
5). Next, when the brand for setting the trigger condition and the brand (including the action content) to be activated when the trigger condition is cleared are determined, the trigger condition is actually set (26). Elements of the trigger conditions set here include a time element described in claim 3, a price element using market condition information, and the like. If the setting of the trigger condition is completed and there is no plurality of settings, the trigger setting process ends here and the process proceeds to execution (28). Further, when it is desired to specify a plurality of trigger conditions, the combination process (29)
Specify a trigger group. This specifies the same trigger group if all the specified trigger conditions must be cleared, and the OR condition (if any of the specified trigger conditions are cleared). Specifies a different trigger group. When setting a plurality of trigger conditions, it is specified whether the conditions should be cleared once or whether they should always be cleared (29). In addition,
In the processes (18) and (25), it is possible to designate a plurality of brands, and it is also possible to designate so-called 'basket trading'. In this case, a basket number is specified instead of the brand code and the order number.
【0006】[0006]
【発明の効果】本発明は以上のような構成であるため、
新しい取引市場(新しい商品含む)が増えた場合にもラ
イン制御機能を増設し、オーダー管理機能にその情報を
登録するのみで、もっと明確に言えばプログラムの修正
なしでデータベースへの登録のみで対応が可能であり、
優れた拡張性が実現できた。また各機能(オーダー管理
機能部、ライン制御機能部、データベース部)の2重
化、3重化が可能なため一部に障害が発生した場合にも
並列稼動する同機能がサポートするためシステム全体の
機能は継続して動作する安定性(フォルトトレラント)
が実現できた。注文処理においては、トリガー発注機能
をオーダー管理機能に付けることによりこれまでには必
要であった人間によるオペレーションを自動化すること
により合理化、電子化を大きく促すことが可能になっ
た。なおこのトリガー発注機能の発明によりインターネ
ット等によるオンライン取引の操作回数を大幅に削減で
きる効果も生まれた。また、トリガー発注機能の応用で
24時間、365日の注文受付や継続性のあるデアイ注
文(週中注文等)が簡単に対応できる。Since the present invention has the above-described structure,
Even if new trading markets (including new products) increase, line control functions are added and information is simply registered in the order management function. More specifically, it is possible to register only in the database without modifying the program. Is possible,
Excellent scalability was achieved. In addition, since each function (order management function unit, line control function unit, database unit) can be duplicated and tripled, the same system that operates in parallel even if a failure occurs partially supports the entire system Function is continuously operating (fault tolerant)
Was realized. In order processing, by adding a trigger ordering function to the order management function, it has become possible to greatly promote rationalization and computerization by automating human operations that have been required so far. In addition, the invention of the trigger ordering function also has an effect that the number of operations of online transactions on the Internet or the like can be significantly reduced. In addition, application of the trigger ordering function makes it possible to easily accept orders for 24 hours and 365 days, and to continuously order daily orders (such as weekly orders).
【図1】システム制御の処理の流れ図1FIG. 1 is a flowchart 1 of a system control process.
【図2】システム制御の処理の流れ図2FIG. 2 is a flowchart 2 of a system control process;
【図3】トリガーの条件設定の流れ図FIG. 3 is a flowchart of trigger condition setting.
Claims (5)
れている有価証券、商品先物等の取引注文を発注、管理
するコンピュータを主に使用するデータ処理システムの
制御方法であり、注文データの処理において注文入力さ
れた注文データがはじめに書込まれ記録・保存されるデ
ータベース(メモリー展開含む)を有し、記録された各
注文データには注文処理の状況を示すステイタスと呼ば
れるフィールドがあり、前記ステイタスの内容を注文処
理状況に応じ書き換え処理を行う機能(オーダ管理機
能)を有し、各取引市場毎に接続されているライン制御
機能部がステイタスの内容を常に問合せ監視し、ステイ
タスの内容がある定められた値になった場合にはその注
文データを取り込み該当する接続先取引市場のプロトコ
ル(各取引市場毎のデータ形式)に変換し取引市場に注
文を転送する機能(ライン制御機能)を有し処理するこ
とを特徴とする取引市場用発注管理システムの機能分散
型制御方法である。1. A method of controlling a data processing system mainly using a computer for ordering and managing trading orders of securities, commodity futures, etc. employed in at least one trading market, wherein the order is processed in order data processing. It has a database (including memory expansion) in which input order data is written and recorded / stored first, and each recorded order data has a field called status indicating the status of order processing. Has a function (order management function) of rewriting according to the order processing status, and the line control function unit connected to each trading market constantly inquires and monitors the content of the status, and the status content is determined. When the value reaches the value, the order data is taken in and the protocol of the corresponding connected exchange market (for each exchange market) It is a functional distributed control method trading market for order management system, which comprises processing has the function of transferring (line control function) the order to the converted transaction market over data format).
ー管理機能には、前記ステイタスの内容を注文処理状況
に応じ書き換え処理を行う機能の他に、注文データの処
理速度を向上させるための機能として、ステイタスの内
容が取引市場に注文データを転送可能な値になった場合
にはデータベースに記録されている注文データをライン
制御機能の使用するメモリー上に振り分ける事も可能と
しており、この処理を行う場合には前記ライン制御機能
部は注文データの問合せ監視先をデータベースからライ
ン制御機能の使用するメモリーとすることを特徴とする
取引市場用発注管理システムの機能分散型制御方法であ
る。2. The order management function according to claim 1, further comprising a function of rewriting the contents of the status according to the order processing status, and an order processing function for improving the processing speed of order data. As a function of, if the status content becomes a value that allows order data to be transferred to the trading market, it is also possible to distribute the order data recorded in the database to the memory used by the line control function, In performing the processing, the line control function unit is a function-distributed control method of an order management system for a trading market, wherein a monitoring destination of an inquiry of order data is a memory used by a line control function from a database.
ー管理機能のステイタスの書き換え処理において、ステ
イタスの書き換え処理の判断に、注文入力(訂正、取消
含む)する際に入力することが可能な「トリガー」とな
る複数の要素(時間、取引市場からの制御通知、時価を
はじめとする市況情報等)を有し、前記「トリガー」の
条件がクリアされた時にステイタスの内容を取引市場に
注文データを転送することが可能な値に変更する機能を
有し、その判断する上で必要なあらゆる情報(デジタル
データ)を取り込む機能を有し、システムで自動的に監
視させる事により、本来、人間が行うべき作業(顧客か
らの条件注文を執行する事)を自動化処理する機能を有
し処理すること(トリガー発注機能)を特徴とする取引
市場用発注管理システムの機能分散型制御方法である。3. In the status rewriting process of the order management function described in claim 1, it is possible to input when order input (including correction and cancellation) in the determination of the status rewriting process. Has a plurality of elements (time, control notification from the market, market information including market value, etc.) that serve as "triggers", and when the conditions of the "trigger" are cleared, the contents of the status are transmitted to the market. It has a function to change the order data to a value that can be transferred, a function to capture all information (digital data) necessary for the determination, and a system to automatically monitor, An order management system for the trading market, which has the function of automating and processing the tasks to be performed by humans (executing conditional orders from customers) (trigger ordering function). It is a functional distributed control method systems out.
ー発注機能には、取引市場の「発注」、「訂正」、「取
消」の制御に対し設定されるだけではなく、注文および
訂正データの内容自体を設定、修正する事もできる機能
を有し処理することを特徴とする取引市場用発注管理シ
ステムの機能分散型制御方法である。4. The trigger ordering function described in claim 3 is not only set for the control of "ordering", "correction", and "cancellation" of the trading market, but also for ordering and correcting. This is a function-distributed control method of an order management system for a trading market, which has a function of setting and modifying the content of data itself and performing processing.
ー発注機能における各要素(時間、取引市場からの制御
通知、時価をはじめとする市況情報等)はグループ指定
する事により各々に複数の条件設定(「AND」処理、
「OR」処理)することが可能であり、全ての条件がク
リアされた時に、ステイタスの書き換えを行う機能を有
し処理することを特徴とする取引市場用発注管理システ
ムの機能分散型制御方法である。5. Each of the elements (time, control notification from the market, market price information and other market information, etc.) in the trigger ordering function described in claim 3 is plural by specifying a group. Condition setting ("AND" processing,
"OR" processing), and has a function of rewriting the status when all the conditions are cleared. is there.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP24026399A JP4330719B2 (en) | 1999-07-23 | 1999-07-23 | Control method of order management system for trading market and order management system for trading market |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP24026399A JP4330719B2 (en) | 1999-07-23 | 1999-07-23 | Control method of order management system for trading market and order management system for trading market |
Publications (2)
Publication Number | Publication Date |
---|---|
JP2001034660A true JP2001034660A (en) | 2001-02-09 |
JP4330719B2 JP4330719B2 (en) | 2009-09-16 |
Family
ID=17056902
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
JP24026399A Expired - Fee Related JP4330719B2 (en) | 1999-07-23 | 1999-07-23 | Control method of order management system for trading market and order management system for trading market |
Country Status (1)
Country | Link |
---|---|
JP (1) | JP4330719B2 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002366739A (en) * | 2001-06-07 | 2002-12-20 | Hitachi Ltd | Electronic commerce ordering performing method, its implementation system and its processing program |
JP2004310761A (en) * | 2003-03-27 | 2004-11-04 | Daiwa Securities Group Inc | Securities transaction support system and securities transaction support method |
JP2005527889A (en) * | 2002-03-13 | 2005-09-15 | オーエムエックス テクノロジー アクチーボラゲット | Automatic trading system and automatic trading method |
JP2005301328A (en) * | 2003-07-10 | 2005-10-27 | Finalabo Co Ltd | Open interest management system with loss cut function at independent open interest-based designated rate to be executed uniformly for all open interests in customer account in stock credit transaction, held stock management system with loss cut function at independent stock-based designated rate to be executed uniformly for all stocks in customer account, and open interest management system with loss cut function at independent open interest-based designated deposit keeping rate to be executed uniformly for open interests in customer account in stock credit transaction |
JP2007052768A (en) * | 2006-05-01 | 2007-03-01 | Takuomi Mochida | Article purchase support system, terminal, article purchase management server, article purchase support method, and article purchase support program |
JP2008130002A (en) * | 2006-11-24 | 2008-06-05 | Moneysquare Japan Inc | Financial product transaction management apparatus and program |
JP2009043293A (en) * | 2008-11-28 | 2009-02-26 | Takuomi Mochida | Merchandise purchase support system, terminal, merchandise purchase management server, merchandise purchase support method, and merchandise purchase support program |
JP2009151434A (en) * | 2007-12-19 | 2009-07-09 | Moneysquare Japan Inc | Financial product dealing management device and program |
JP2011123907A (en) * | 2004-02-13 | 2011-06-23 | Omx Technology Ab | Multi site solution for security trading |
JP2012164030A (en) * | 2011-02-03 | 2012-08-30 | Rakuten Inc | Purchase reservation device, purchase reservation program, computer-readable storage media recording the purchase reservation program, and purchase reservation method |
JP2013152750A (en) * | 2010-01-13 | 2013-08-08 | Moneysquare Japan Inc | Method for financial product transaction management and program |
JP2016119119A (en) * | 2015-06-18 | 2016-06-30 | 株式会社マネースクウェアHd | Financial product transaction management device, and financial product transaction management method in financial product transaction management system |
WO2021155188A1 (en) * | 2020-01-31 | 2021-08-05 | Cfph, Llc | System and method for managing and processing sequenced events in a distributed network |
JP2022010045A (en) * | 2019-05-23 | 2022-01-14 | 株式会社マネースクエアHd | Financial product transaction management device, financial product transaction management method in financial product transaction management system, and program |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5481315B2 (en) | 2010-08-20 | 2014-04-23 | 株式会社東芝 | Securities trading system and equipment |
-
1999
- 1999-07-23 JP JP24026399A patent/JP4330719B2/en not_active Expired - Fee Related
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002366739A (en) * | 2001-06-07 | 2002-12-20 | Hitachi Ltd | Electronic commerce ordering performing method, its implementation system and its processing program |
JP2005527889A (en) * | 2002-03-13 | 2005-09-15 | オーエムエックス テクノロジー アクチーボラゲット | Automatic trading system and automatic trading method |
JP2004310761A (en) * | 2003-03-27 | 2004-11-04 | Daiwa Securities Group Inc | Securities transaction support system and securities transaction support method |
JP2005301328A (en) * | 2003-07-10 | 2005-10-27 | Finalabo Co Ltd | Open interest management system with loss cut function at independent open interest-based designated rate to be executed uniformly for all open interests in customer account in stock credit transaction, held stock management system with loss cut function at independent stock-based designated rate to be executed uniformly for all stocks in customer account, and open interest management system with loss cut function at independent open interest-based designated deposit keeping rate to be executed uniformly for open interests in customer account in stock credit transaction |
JP2011123907A (en) * | 2004-02-13 | 2011-06-23 | Omx Technology Ab | Multi site solution for security trading |
JP2007052768A (en) * | 2006-05-01 | 2007-03-01 | Takuomi Mochida | Article purchase support system, terminal, article purchase management server, article purchase support method, and article purchase support program |
JP2008130002A (en) * | 2006-11-24 | 2008-06-05 | Moneysquare Japan Inc | Financial product transaction management apparatus and program |
JP2010108518A (en) * | 2007-12-19 | 2010-05-13 | Moneysquare Japan Inc | Transaction management device for financial product, and program |
JP2009151434A (en) * | 2007-12-19 | 2009-07-09 | Moneysquare Japan Inc | Financial product dealing management device and program |
JP2009043293A (en) * | 2008-11-28 | 2009-02-26 | Takuomi Mochida | Merchandise purchase support system, terminal, merchandise purchase management server, merchandise purchase support method, and merchandise purchase support program |
JP2013152750A (en) * | 2010-01-13 | 2013-08-08 | Moneysquare Japan Inc | Method for financial product transaction management and program |
JP2012164030A (en) * | 2011-02-03 | 2012-08-30 | Rakuten Inc | Purchase reservation device, purchase reservation program, computer-readable storage media recording the purchase reservation program, and purchase reservation method |
JP2016119119A (en) * | 2015-06-18 | 2016-06-30 | 株式会社マネースクウェアHd | Financial product transaction management device, and financial product transaction management method in financial product transaction management system |
JP2022010045A (en) * | 2019-05-23 | 2022-01-14 | 株式会社マネースクエアHd | Financial product transaction management device, financial product transaction management method in financial product transaction management system, and program |
JP7197220B2 (en) | 2019-05-23 | 2022-12-27 | 株式会社マネースクエアHd | Financial instrument transaction management device, financial instrument transaction management method and program in financial instrument transaction management system |
WO2021155188A1 (en) * | 2020-01-31 | 2021-08-05 | Cfph, Llc | System and method for managing and processing sequenced events in a distributed network |
US11842400B2 (en) | 2020-01-31 | 2023-12-12 | Cfph, Llc | System and method for managing events in a queue of a distributed network |
Also Published As
Publication number | Publication date |
---|---|
JP4330719B2 (en) | 2009-09-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP2001034660A (en) | Function decentralized type control method for ordering management system for transaction market | |
US10510114B2 (en) | Distributed trading bus architecture | |
US20110145095A1 (en) | Order Fulfillment Method | |
US20100257260A1 (en) | System and method for dynamically modifying synchronized business information server interfaces | |
US7349861B1 (en) | Value chain management | |
US7370009B1 (en) | Extreme capacity management in an electronic marketplace environment | |
US20020069121A1 (en) | Supply assurance | |
KR102334336B1 (en) | Online shared sales platform and methods of operation thereof | |
CN105654251A (en) | Business flow realization method in field of ERP | |
US8195521B1 (en) | Method of and system for processing transactions | |
Laage-Hellman et al. | Information technology and the efficiency of materials supply: The implementation of EDI in the Swedish construction industry | |
EP1208508A1 (en) | Interest matching and price improvement platform method and system | |
Klein et al. | Designing robust business processes | |
JP2005513651A (en) | Method and system for trading energy contracts on an exchange | |
JP5154290B2 (en) | BUY / ORDER ORDER CONTROL DEVICE AND BUY / ORDER ORDER CONTROL METHOD | |
Conway | Supplier affiliated extended supply chain backbones | |
Pennington | The collateral-linked currency forward (CLCF) contract: blockchain-enabled OTC currency forward market infrastructure | |
JP4233010B2 (en) | Defined contribution pension system and program that runs on computer | |
AU2023226650A1 (en) | Method of managing assets | |
Dabous et al. | Information systems and IT architectures for securities trading | |
Hill et al. | Strategy and structure in the multiproduct firm | |
Hoffman | Current developments on e-business and enterprise | |
JP2002099767A (en) | Electronic commerce system and electronic commerce center | |
JP2007523422A (en) | Data processing device, data structure, and method for distributing financial information for a financial information database | |
Zuccaro | Information systems should be both useful and used: the Benetton experience |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
A621 | Written request for application examination |
Free format text: JAPANESE INTERMEDIATE CODE: A621 Effective date: 20060509 |
|
A131 | Notification of reasons for refusal |
Free format text: JAPANESE INTERMEDIATE CODE: A131 Effective date: 20090217 |
|
A521 | Request for written amendment filed |
Free format text: JAPANESE INTERMEDIATE CODE: A523 Effective date: 20090417 |
|
A521 | Request for written amendment filed |
Free format text: JAPANESE INTERMEDIATE CODE: A821 Effective date: 20090417 |
|
TRDD | Decision of grant or rejection written | ||
A01 | Written decision to grant a patent or to grant a registration (utility model) |
Free format text: JAPANESE INTERMEDIATE CODE: A01 Effective date: 20090609 |
|
A01 | Written decision to grant a patent or to grant a registration (utility model) |
Free format text: JAPANESE INTERMEDIATE CODE: A01 |
|
A61 | First payment of annual fees (during grant procedure) |
Free format text: JAPANESE INTERMEDIATE CODE: A61 Effective date: 20090617 |
|
R150 | Certificate of patent or registration of utility model |
Ref document number: 4330719 Country of ref document: JP Free format text: JAPANESE INTERMEDIATE CODE: R150 Free format text: JAPANESE INTERMEDIATE CODE: R150 |
|
FPAY | Renewal fee payment (event date is renewal date of database) |
Free format text: PAYMENT UNTIL: 20120626 Year of fee payment: 3 |
|
FPAY | Renewal fee payment (event date is renewal date of database) |
Free format text: PAYMENT UNTIL: 20130626 Year of fee payment: 4 |
|
R250 | Receipt of annual fees |
Free format text: JAPANESE INTERMEDIATE CODE: R250 |
|
R250 | Receipt of annual fees |
Free format text: JAPANESE INTERMEDIATE CODE: R250 |
|
R250 | Receipt of annual fees |
Free format text: JAPANESE INTERMEDIATE CODE: R250 |
|
R250 | Receipt of annual fees |
Free format text: JAPANESE INTERMEDIATE CODE: R250 |
|
R250 | Receipt of annual fees |
Free format text: JAPANESE INTERMEDIATE CODE: R250 |
|
R250 | Receipt of annual fees |
Free format text: JAPANESE INTERMEDIATE CODE: R250 |
|
R250 | Receipt of annual fees |
Free format text: JAPANESE INTERMEDIATE CODE: R250 |
|
LAPS | Cancellation because of no payment of annual fees |