JP6667881B1 - Transaction support system, user server and transaction support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a transaction support system, a user server, and a transaction support method capable of appropriately conducting a transaction of a user. A transaction support system manages transaction information regarding transactions performed on an exchange. The transaction support system relates to two or more user servers corresponding to each of two or more users, and a transaction performed by the two or more user servers in response to access from the two or more user servers to the exchange. And a management server that manages transaction information. Each of the two or more user servers manages address information different from each other as address information used to access the exchange, and is assigned to each of the two or more users to access the exchange. The authority is managed, and a transaction is conducted with the exchange using the address information and the access authority. The management server manages the transaction information based on the information received from each of the two or more user servers without managing the access authority. [Selection diagram] Fig. 1

Description

  The present invention relates to a transaction support system, a user server, and a transaction support method.

  2. Description of the Related Art A mechanism (copy trade or mirror trade) for following an investment transaction of a follow-up user to an investment transaction of a reference user has been known (for example, Patent Document 1).

US Patent Application Publication No. 2013/0060672

  However, in the above-described mechanism, since the management server that performs the investment transaction of the follow-up user accesses the exchange directly, the access from the management server to the exchange increases as the number of follow-up users increases. Such an increase in access is determined to be a Dos attack, the exchange may deny access, and the follow-up user may not be properly transacted.

  Then, this invention is made in order to solve the above-mentioned subject, and an object of this invention is to provide the transaction support system, the user server, and the transaction support method which can perform a user's transaction appropriately. .

  A first feature is a transaction support system that manages transaction information relating to transactions performed on an exchange, and includes two or more user servers corresponding to two or more users, and the transaction from the two or more user servers. A management server that manages transaction information on transactions performed by the two or more user servers in response to access to the exchange, wherein each of the two or more user servers has an address used to access the exchange. The information manages different address information from each other, is assigned to each of the two or more users, manages access authority to access the exchange, and uses the address information and the access authority to exchange information on the exchange. And the management server does not manage the access authority, each of the two or more user servers Based on the information et received, and be required to manage the transaction information.

  A second feature is that, in the first feature, the management server outputs a tally result of the transaction information.

  A third feature is that in the first feature or the second feature, the two or more user servers are managed by each of the two or more users.

  A fourth feature is that, in the third feature, the two or more user server instances are started or stopped by each of the two or more users.

  A fifth feature is that in any one of the first to fourth features, the two or more users include a reference user and a follow-up user who performs a transaction that follows the transaction of the reference user. Make a summary.

  A sixth feature is the gist of the fifth feature, wherein the management server outputs the reference user candidate.

  A seventh feature is the fifth feature or the sixth feature, wherein the two or more user servers include a reference user server corresponding to the reference user, and a follow-up user server corresponding to the follow-up user, The reference user server writes the transaction difference to the management server based on a transaction difference between the transaction performance information of the reference user received from the exchange and the transaction management information of the reference user received from the management server. That is the gist.

  An eighth feature is the gist of the seventh feature, wherein when there is the transaction difference, the reference user server notifies the follow-up user server that the transaction difference exists.

  A ninth feature is the seventh feature or the eighth feature, wherein the follow-up user server receives the follow-up user's transaction result information received from the exchange and the reference user's transaction management information received from the management server. The gist of the present invention is to execute a transaction by accessing the exchange based on the following difference and write the execution result of the transaction based on the following difference to the management server.

  A tenth feature is based on the ninth feature citing the eighth feature, wherein the follow-up user server confirms the follow-up difference based on a notification that the transaction difference exists.

  An eleventh feature is the gist of the ninth feature, wherein the following user server periodically checks the following difference.

  A twelfth feature is a user server used in a transaction support system that manages transaction information relating to transactions performed on an exchange, and an address individually assigned to the user server as address information used to access the exchange. The subject matter includes a management unit that manages information and manages an access right to access the exchange, and a control unit that performs a transaction with the exchange using the address information and the access authority.

  A thirteenth feature is a transaction support method used in a transaction support system that manages transaction information on transactions performed on an exchange, wherein the transaction support system includes two or more user servers corresponding to two or more users, respectively. And a management server that manages transaction information related to transactions performed by the two or more user servers in response to access to the exchange from the two or more user servers, each of the two or more user servers Managing different address information as address information used for accessing the exchange, wherein each of the two or more user servers is assigned to each of the two or more users, and Managing access rights to access the server, and wherein each of the two or more user servers Using the contact information and the access authority, performing a transaction with the exchange, the management server, without managing the access authority, based on information received from each of the two or more user servers, And managing the transaction information.

  According to the present invention, there are provided a transaction support system, a user server, and a transaction support method that enable a user to appropriately perform a transaction.

FIG. 1 is a diagram illustrating a transaction support system 100 according to the embodiment. FIG. 2 is a diagram illustrating the MS 20 according to the embodiment. FIG. 3 is a diagram illustrating the management server 30 according to the embodiment. FIG. 4 is a diagram illustrating an example of transaction result information of a reference user according to the embodiment. FIG. 5 is a diagram illustrating an example of transaction management information of a reference user according to the embodiment. FIG. 6 is a diagram illustrating an example of transaction result information of a follow-up user according to the embodiment. FIG. 7 is a diagram illustrating an example of transaction management information of a reference user according to the embodiment. FIG. 8 is a diagram illustrating a transaction support method according to the embodiment. FIG. 9 is a diagram illustrating a transaction support method according to the embodiment. FIG. 10 is a diagram illustrating a transaction support method according to the embodiment.

Hereinafter, embodiments will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.
However, it should be noted that the drawings are schematic and ratios of dimensions may be different from actual ones. Therefore, specific dimensions and the like should be determined in consideration of the following description. Further, it is needless to say that the drawings may include portions having different dimensional relationships or ratios.

[Overview of disclosure]
A transaction support system according to an outline of disclosure manages transaction information on transactions performed on an exchange. The transaction support system relates to two or more user servers corresponding to each of two or more users, and a transaction performed by the two or more user servers in response to access from the two or more user servers to the exchange. A management server that manages transaction information. Each of the two or more user servers manages address information different from each other as address information used for accessing the exchange, and is assigned to each of the two or more users to access the exchange. Authority is managed and trades with the exchange using the address information and the access authority. The management server manages the transaction information based on information received from each of the two or more user servers without managing the access authority.

  In the summary of the disclosure, the management server does not manage the access authority, and each of two or more user servers having mutually different address information trades with the exchange using the access authority. According to such a configuration, by introducing the concept of the user server having the address information and the access authority, the user server does the transaction instead of the management server acting for the transaction. Therefore, access to the exchange is unlikely to be interpreted as a Dos attack, and the user's transaction can be appropriately performed.

  In the summary of the disclosure, the access authority is not centrally managed by the management server, but is discretely managed by two or more user servers. Therefore, it is possible to suppress the total stoppage of the transaction due to the failure of the management server, and it is also possible to suppress the unauthorized use of the access authority due to the cyber attack on the management server.

  In the summary of the disclosure, the information is managed centrally by a management server that manages transaction information. Therefore, it is not necessary to collect the transaction information from the user server every time the transaction information is requested, and the transaction information can be output even in the case where the user server instance is stopped.

[Embodiment]
(Transaction support system)
Hereinafter, a transaction support system according to an embodiment will be described. FIG. 1 is a diagram illustrating a transaction support system 100 according to the embodiment.

  As shown in FIG. 1, the transaction support system 100 includes a user terminal 10, an MS (Micro Server) 20, a management server 30, an exchange 40, and a network 50.

  The user terminal 10 is a terminal operated by a user. For example, the user terminal 10 is a personal computer, a smartphone, a tablet terminal, or the like. The user terminal 10 issues a transaction instruction. The transaction instruction may be an instruction for an independent transaction that does not follow the transaction of the reference user, or may be an instruction for a follow-up transaction that follows the transaction of the reference user.

  In the embodiment, the user terminal 10 is exemplified by a user terminal 10A and a user terminal 10B. The user terminal 10A may be an example of a terminal operated by the reference user. The user terminal 10B may be an example of a terminal operated by a following user who performs a following transaction.

  The MS 20 is an example of a user server. The MS 20 may be a virtual server or a physical server. Two or more MSs 20 may be managed by each of the two or more users. Here, management may mean having the authority to operate an instance of the MS 20. For example, two or more instances of MS 20 may be activated or deactivated by each of two or more users. The MS 20 manages address information individually assigned to the MS 20 as address information used to access the exchange 40. For example, the address information includes a global IP address. The MS 20 is individually assigned to a user, and manages an access right to access the exchange 40. For example, the access right includes an API (Application Programming Interface) key. The access authority may include a user ID and a password. The MS 20 transacts with the exchange 40 using the address information and the access authority. Details of the MS 20 will be described later (see FIG. 2).

  In the embodiment, the MS 20 is exemplified by the MS 20A and the MS 20B. The MS 20A is an example of a reference user server managed by a reference user. The MS 20B is an example of a follow-up user server managed by the follow-up user.

  The management server 30 manages transaction information relating to transactions performed on exchanges. The management server 30 manages the transaction information based on the information received from the MS 20 without managing the access authority. Details of the management server 30 will be described later (see FIG. 3).

  The exchange 40 is an entity that mediates electronic commerce. For example, e-commerce targets include virtual currency. The subject of e-commerce may include financial services such as securities. The following mainly describes a case where the target of electronic commerce is a virtual currency. FIG. 1 illustrates one exchange 40 as the exchange 40, but two or more exchanges 40 may be provided.

  The network 50 is a communication network for performing communication between the MS 20, the management server 30, and the exchange 40. For example, network 50 may include the Internet. The network 50 may include a mobile communication network, and may include a VPN (Virtual Private Network).

(User server)
Hereinafter, the user server according to the embodiment will be described. FIG. 2 is a diagram illustrating the MS 20 according to the embodiment. Since the MSs 20A and 20B have basically the same configuration, only the MS 20 will be described here.

  As shown in FIG. 2, the MS 20 has a communication unit 21, a management unit 22, and a control unit 23.

  The communication unit 21 is configured by a communication module. The communication module may be a wireless communication module conforming to a standard such as IEEE802.11a / b / g / n or a wired communication module conforming to a standard such as IEEE802.3.

  The communication unit 21 communicates with the user terminal 10. Specifically, the communication unit 21 receives a transaction instruction from the user terminal 10. The communication unit 21 transmits a transaction result corresponding to the transaction instruction to the user terminal 10.

  The communication unit 21 communicates with the management server 30. Specifically, the communication unit 21 receives the transaction management information from the management server 30. The transaction management information is information managed by the management server 30 and is an example of transaction information on a transaction performed at the exchange 40.

  The communication unit 21 communicates with the exchange 40. Specifically, the communication unit 21 transmits a transaction instruction to the exchange 40. The communication unit 21 receives a transaction result corresponding to the transaction instruction from the exchange 40. The communication unit 21 receives the transaction result information from the exchange 40. The transaction result information is information managed by the exchange 40, and is an example of transaction information on a transaction performed on the exchange 40. The transaction result information may be managed by a technology such as a blockchain.

  The management unit 22 includes a memory such as a non-volatile memory and / or a storage medium such as an HDD (Hard disc drive). The management unit 22 manages address information individually assigned to the MS 20 as address information used to access the exchange 40. The management unit 22 is individually assigned to the user and manages the access right to access the exchange 40.

  The control unit 23 includes at least one processor and / or at least one circuit. The control unit 23 controls each component provided in the MS 20. The control unit 23 trades with the exchange 40 using the address information and the access authority.

(Management server)
Hereinafter, the management server according to the embodiment will be described. FIG. 3 is a diagram illustrating the management server 30 according to the embodiment.

  As shown in FIG. 3, the management server 30 includes a communication unit 31, a management unit 32, and a control unit 33.

  The communication unit 31 includes a communication module. The communication module may be a wireless communication module conforming to a standard such as IEEE802.11a / b / g / n or a wired communication module conforming to a standard such as IEEE802.3.

  The communication unit 31 communicates with the MS 20. Specifically, communication unit 31 transmits the transaction management information to MS 20. The communication unit 31 may communicate with the user terminal 10. Specifically, the communication unit 31 may transmit the totalization result of the transaction information to the user terminal 10. The communication unit 31 may be configured not to directly access the exchange 40.

  The management unit 32 includes a memory such as a non-volatile memory or / and a storage medium such as a HDD (Hard disc drive). The management unit 32 manages transaction information on transactions performed on the exchange. The transaction information managed by the management unit 32 may be referred to as transaction management information.

  In the embodiment, the management unit 32 may manage the reference user candidates. Although not particularly limited, the reference user candidate may be a user (trader) achieving a profit rate equal to or higher than a threshold, or a user (trader) achieving a profit amount equal to or higher than the threshold. , A user (trader) having a number of followers equal to or greater than a threshold value. The reference user candidates may be ranked by at least one of a profit rate, a profit amount, and the number of followers. For example, the profit rate may be a value obtained by summing the ratio of the profit amount of the transaction to the investment amount of the transaction in a certain past period. The profit amount may be a value obtained by summing the ratio of the profit amount of the transaction in a certain period in the past. The number of followers is the number of follow-up users who follow the user (trader).

  The control unit 33 includes at least one processor and / or at least one circuit. The control unit 33 controls each component provided in the MS 20. The control unit 33 may output the candidate of the reference user. For example, the reference user candidate may be transmitted from the communication unit 31 to a terminal of a user who does not use the transaction support system 100. The reference user candidate may be transmitted from the communication unit 31 to a terminal of a user who has already used the transaction support system 100.

(Reference user server)
Hereinafter, a case where the MS 20 is a reference user server will be further described. When MS 20 is a reference user server (ie, MS 20A), MS 20A may perform the following operation.

  The MS 20A performs an independent transaction with the exchange 40 based on a transaction instruction received from the user terminal 10A. The MS 20 </ b> A may write the transaction difference in the management server 30 based on the transaction difference between the transaction history information of the reference user received from the exchange 40 and the transaction management information of the reference user received from the management server 30.

  For example, a case where the transaction performance information of the reference user is the information shown in FIG. 4 and the transaction management information of the reference user is the information shown in FIG. As shown in FIGS. 4 and 5, the transaction record information and the transaction management information have the same format. , User ID, exchange ID, transaction date and time, currency type, amount, transaction type and other information elements. No. Is information for identifying each record. The user ID is information for identifying a user. The exchange ID is information for identifying the exchange 40. The transaction date and time is the date on which the transaction was performed. The currency type is the type of the virtual currency to be traded. The amount is a unit indicating the value of the virtual currency. The transaction type is information indicating whether the transaction is a selling transaction or a buying transaction.

  In such a case, the transaction management information shown in FIG. 5 records are not included. That is, No. Record 5 is the transaction difference. Therefore, MS20A is No. 5 is written to the management server 30. For example, the MS 20A (communication unit 21) sends a No. to the management server 30. By transmitting the record of No. 5, 5 records are written.

  Further, when there is a transaction difference, the MS 20A may notify the follow-up user server that the transaction difference exists. For example, the MS 20A (communication unit 21) may notify the following user server of the presence of the transaction difference by transmitting an indicator that the transaction difference exists. However, the indicator is No. Note that it does not include 5 records.

(Following user server)
Hereinafter, the case where the MS 20 is a follow-up user server will be further described. When MS 20 is a follow-up user server (ie, MS 20B), MS 20B may perform the following operation.

  The MS 20B executes a transaction by accessing the exchange 40 based on a difference between the transaction result information of the follow-up user received from the exchange 40 and the transaction management information of the reference user received from the management server 30, and The execution result of the transaction based on the difference may be written to the management server.

  For example, a case where the transaction result information of the following user is the information shown in FIG. 6 and the transaction management information of the reference user is the information shown in FIG. 7 will be exemplified. As shown in FIGS. 6 and 7, the transaction record information and the transaction management information have the same format as in FIGS. , User ID, exchange ID, transaction date and time, currency type, amount, transaction type and other information elements.

  Here, a case where the transaction management information of the reference user shown in FIG. 7 is the same as the transaction record information of the reference user shown in FIG. 4 is illustrated. In other words, FIG. 7 shows the transaction difference between FIG. 4 and FIG. 5 shows a state in which the record No. 5 has been written to the management server 30.

  Since there is a time lag between the independent transaction of the referring user and the following transaction of the following user, the closing rate of the following user may be different from the closing rate of the reference user. Therefore, the amount of money of the record included in FIG. 6 may be different from the amount of money of the record included in FIG.

  In such a case, the transaction performance information shown in FIG. 5 records are not included. That is, No. Record 5 is the tracking difference. The MS 20B receives the No. Attempt to execute a transaction (follow-up transaction) similar to that of record 5 with exchange 40. The MS 20B may write the execution result of the transaction (follow-up transaction) based on the follow-up difference in the management server 30. For example, by transmitting the execution result of the follow-up transaction from the MS 20B (communication unit 21) to the management server 30, the execution result of the follow-up transaction is written.

  Here, the MS 20B may confirm the follow-up difference based on the notification that the transaction difference exists. In other words, the MS 20B may check the following difference when receiving the above-mentioned indicator from the MS 20A. Alternatively, the MS 20B may periodically check the tracking difference.

(Transaction support method)
Hereinafter, a transaction support method according to the embodiment will be described. 8 to 10 are diagrams illustrating a transaction support method according to the embodiment.

  First, the operation of the reference user server (MS 20A) will be mainly described.

  As shown in FIG. 8, in step S10, the MS 20A receives a transaction instruction (independent transaction instruction) from the user terminal 10A.

  In step S11, the MS 20A requests execution of an independent transaction based on the transaction instruction received from the user terminal 10A by accessing the exchange 40 using the address information and the access authority.

  In step S12, the MS 20A receives an execution result for the execution request from the exchange 40. The execution result may be a result of executing the entire execution request, a result of executing a part of the execution request, or a result of rejecting the execution request.

  In step S13, the MS 20A transmits the execution result received from the exchange 40 to the user terminal 10A.

  In step S20, the MS 20A requests the exchange 40 for transaction result information of the reference user by accessing the exchange 40 using the address information and the access authority.

  In step S21, the MS 20A receives the transaction result information of the reference user from the exchange 40.

  In step S22, the MS 20A requests the management server 30 for transaction management information of the reference user.

  In step S23, the MS 20A receives the transaction management information of the reference user from the management server 30.

  In step S24, the MS 20A writes the transaction difference to the management server 30 based on the transaction difference between the transaction performance information of the reference user and the transaction management information of the reference user.

  In step S25, the MS 20A transmits an indicator to the effect that a transaction difference exists to the MS 20B.

  Here, the MS 20A may periodically perform the processing of steps S20 to S25 (hereinafter, the processing for confirming the transaction difference). Alternatively, the MS 20A may perform a transaction difference confirmation process for each independent transaction.

  Second, the operation of the following user server (MS20B) will be mainly described.

  As shown in FIG. 9, in step S25, the MS 20B receives from the MS 20B an indicator that a transaction difference exists.

  In step S30, the MS 20B requests the exchange 40 for the transaction result information of the following user by accessing the exchange 40 using the address information and the access authority.

  In step S31, the MS 20A receives the transaction result information of the follow-up user from the exchange 40.

  In step S32, the MS 20B requests the management server 30 for transaction management information of the reference user.

  In step S33, the MS 20B receives the transaction management information of the reference user from the management server 30.

  In step S34, the MS 20B accesses the exchange 40 using the address information and the access authority, and requests execution of a follow-up transaction based on a follow-up difference between the transaction result information of the follow-up user and the transaction management information of the reference user. I do.

  In step S35, the MS 20B receives the execution result for the execution request from the exchange 40. The execution result may be a result of executing the entire execution request, a result of executing a part of the execution request, or a result of rejecting the execution request.

  In step S36, the MS 20B transmits the execution result received from the exchange 40 to the user terminal 10B. The process of step S36 may be omitted.

  In step S37, the MS 20B writes the execution result of the following transaction based on the following difference to the management server 30.

  Here, the case where the confirmation process of the tracking difference is performed in response to the reception of the indicator is illustrated. However, embodiments are not limited to this. As described above, the tracking difference confirmation processing may be performed periodically.

  Third, output of the tally result of the transaction information will be described.

  As shown in FIG. 10, in step S41, the user terminal 10A requests the management server 30 for the totalization result of the transaction information. In step S42, the user terminal 10A receives the totalization result of the transaction information from the management server 30.

  Similarly, in step S51, the user terminal 10B requests the management server 30 for the totalization result of the transaction information. In step S52, the user terminal 10B receives the totalization result of the transaction information from the management server 30.

  Here, the case where the management server 30 transmits the tally result of the transaction information in response to the request of the user terminal 10 has been illustrated. However, embodiments are not limited to this. The management server 30 may periodically transmit the tally result of the transaction information. For example, the management server 30 may transmit the tally result of the transaction information as a monthly report. Alternatively, the management server 30 may transmit the tally result of the transaction information at a predetermined timing. For example, the predetermined timing may include a timing when the profit rate or the profit amount exceeds a predetermined value, or may include a timing when the profit rate or the profit amount falls below a predetermined value.

(Action and effect)
In the embodiment, the management server 30 does not manage the access authority, and each of the two or more MSs 20 having different address information trades with the exchange 40 using the access authority. According to such a configuration, by introducing the concept of the MS 20 having the address information and the access authority, the MS 20 does the transaction instead of the management server 30 acting for the transaction. Therefore, it is unlikely that access to the exchange 40 is interpreted as a Dos attack, and the user can appropriately conduct a transaction.

  In the embodiment, the access authority is not centrally managed by the management server 30, but is discretely managed by two or more MSs 20. Therefore, it is possible to suppress the total suspension of the transaction due to the failure of the management server 30, and it is also possible to suppress the unauthorized use of the access authority due to the cyber attack on the management server 30.

  In the embodiment, the information is managed centrally by the management server 30 that manages the transaction information. Therefore, it is not necessary to collect transaction information from the MS 20 every time the transaction information is requested, and even in a case where the instance of the MS 20 is stopped, the transaction information can be output.

[Other Embodiments]
Although the present invention has been described with reference to the above-described embodiments, it should not be understood that the description and drawings forming part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples, and operation techniques will be apparent to those skilled in the art.

  In the embodiment, the MS 20 receives the transaction result information from the exchange 40 without managing the transaction result information. However, embodiments are not limited to this. The MS 20 may manage the transaction result information.

  In the embodiment, the indicator transmitted from the MS 20A (the reference user server) to the MS 20B (the following user server) does not include the transaction management information of the reference user. However, embodiments are not limited to this. For example, when the MS 20A manages the transaction management information of the reference user, the transaction management information of the reference user may be transmitted from the MS 20A to the MS 20B. The transaction management information of the reference user may be transmitted together with the indicator. The transaction management information of the reference user may include the transaction difference without including data other than the transaction difference (the record of No. 5 shown in FIG. 4).

  Although not particularly mentioned in the embodiment, the tallying result of the transaction information may include a tallying result regarding a transaction of a requester of the tallying result, or may include a tallying result regarding a transaction of another person other than the requester of the tallying result. When there are two or more exchanges 40, the tally result of the transaction information may include the tally result of each exchange 40. The aggregation result of the transaction information may include at least one of a profit rate and a profit amount. The aggregation result of the transaction information may include the user (trader) ranked by at least one of the profit rate and the profit amount. The aggregation result of the transaction information may be transmitted to a terminal of a user who has already used the transaction support system 100, or may be transmitted to a terminal of a user who has not used the transaction support system 100.

  Although not particularly mentioned in the embodiment, the profit ratio may take a negative value. A negative rate of return may be considered a loss rate. Similarly, the profit amount may take a negative value. A negative profit may be considered a loss. The profit amount may include an unrealized gain and an unrealized loss.

  Although not specifically mentioned in the embodiment, the reference user may be an individual trader or an organization such as a securities company. The reference user may be a user who makes a transaction using AI (Artificial Intelligence).

  Although not particularly mentioned in the embodiment, a program that causes a computer to execute each process performed by at least one of the MS 20 and the management server 30 may be provided. Further, the program may be recorded on a computer-readable medium. With a computer readable medium, it is possible to install the program on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, but may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.

  Alternatively, a chip configured by a memory that stores a program for executing each process performed by at least one of the MS 20 and the management server 30 and a processor that executes the program stored in the memory may be provided.

  DESCRIPTION OF SYMBOLS 10 ... User terminal, 20 ... MS, 21 ... Communication part, 22 ... Management part, 23 ... Control part, 30 ... Management server, 31 ... Communication part, 32 ... Management part, 33 ... Control part, 40 ... Exchange, 50 ... Network, 100 ... Transaction support system

Claims (13)

A transaction support system for managing transaction information on transactions performed on an exchange,
Two or more user servers corresponding to each of the two or more users;
A management server that manages transaction information relating to transactions performed by the two or more user servers in response to access to the exchange from the two or more user servers,
Each of the two or more user servers,
As address information used to access the exchange, manage address information different from each other,
Assigned to each of the two or more users and managing access rights to access the exchange;
Using the address information and the access authority, trade with the exchange,
The transaction support system, wherein the management server manages the transaction information based on information received from each of the two or more user servers without managing the access authority.   The transaction support system according to claim 1, wherein the management server outputs a result of counting the transaction information.   The transaction support system according to claim 1, wherein the two or more user servers are managed by each of the two or more users.   The transaction support system according to claim 3, wherein the instances of the two or more user servers are started or stopped by each of the two or more users.   The transaction support system according to any one of claims 1 to 4, wherein the two or more users include a reference user and a follow-up user who conducts a transaction following the transaction of the reference user.   The transaction support system according to claim 5, wherein the management server outputs the reference user candidate. The two or more user servers include a reference user server corresponding to the reference user, and a follow-up user server corresponding to the follow-up user,
The reference user server writes the transaction difference to the management server based on a transaction difference between the transaction performance information of the reference user received from the exchange and the transaction management information of the reference user received from the management server. The transaction support system according to claim 5 or claim 6.   The transaction support system according to claim 7, wherein the reference user server notifies the following user server that the transaction difference exists when the transaction difference exists.   The follow-up user server, based on a follow-up difference between the transaction result information of the follow-up user received from the exchange and the transaction management information of the reference user received from the management server, executes a transaction by accessing the exchange. The transaction support system according to claim 7, wherein the transaction support system executes the transaction and writes a transaction execution result based on the tracking difference to the management server.   The transaction support system according to claim 9, wherein the follow-up user server confirms the follow-up difference based on a notification that the transaction difference exists.   The transaction support system according to claim 9, wherein the following user server periodically checks the following difference. A user server used in a transaction support system that manages transaction information on transactions performed on an exchange,
A management unit that manages address information individually assigned to the user server as address information used for accessing the exchange, and manages access authority to access the exchange.
A control unit for performing a transaction with the exchange using the address information and the access authority. A trading support method for use in a trading support system that manages trading information related to trading performed on an exchange,
The transaction support system includes:
Two or more user servers corresponding to each of the two or more users;
A management server that manages transaction information relating to transactions performed by the two or more user servers in response to access to the exchange from the two or more user servers,
A step in which each of the two or more user servers manages different address information as address information used to access the exchange;
Each of said two or more user servers being assigned to each of said two or more users, managing access rights to access said exchange;
A step in which each of the two or more user servers performs a transaction with the exchange using the address information and the access authority;
A step in which the management server manages the transaction information based on information received from each of the two or more user servers without managing the access authority.

Images