A joint risk control method, device, equipment and readable storage medium

Abstract

The application discloses a kind of joint risk control methods, applied to financial transaction field, the method of the present application is by adding connection maintenance unit for maintaining the TCP connection between counter and gateway is not closed, connection maintenance unit will be received from the information of counter and gateway copy and after protocol analysis, it is forwarded to risk control unit to carry out risk judgment or database update, according to the judgment result control connection maintenance unit sends corresponding information to counter or gateway.The application maintains the TCP connection of target counter and target gateway is not closed by increasing connection maintenance unit, so that target counter and target gateway are directly connected, which avoids the shortcomings of the prior art that TCP connection between counter and gateway needs to be interrupted, and TCP connection between counter and gateway and joint risk control system is established respectively to transmit information.The application also discloses a kind of joint risk control device, equipment and computer readable storage medium, which have the above beneficial effects.

Description

Technical Field

[0001] This invention relates to the field of financial transactions, and in particular to a joint risk control method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] The main purpose of a joint risk control system is to perform unified risk control on transaction orders from multiple counters. In existing related technologies, the method to implement a joint risk control system is to directly add the joint risk control system between the transaction counter and the transaction gateway, interrupt the TCP connection between the transaction counter and the transaction gateway, and establish separate TCP connections between the transaction counter and the transaction gateway and the joint risk control system. The implementation of the above method requires that the OMS system of the transaction counter supports the private protocol of the joint risk control system or that the joint risk control system simulates the transaction gateway and interfaces with the transaction counter.

[0003] The problem with this approach is that OMS system developers need to support the proprietary protocols of joint risk control system developers, not standard exchange protocols. Different OMS system developers investing heavily and risking their own developers to support a particular joint risk control system's proprietary protocol is extremely difficult. Furthermore, it's highly impractical for brokerages to persuade different OMS system developers to modify their existing standard exchange protocols to support a competitor's proprietary protocol. The problem with the joint risk control system needing to simulate a trading gateway is that the specific design of the trading gateway is not publicly disclosed. It handles core functions such as rule checks and network flow control before orders are sent to the exchange's matching system. Simulating a trading gateway without disclosing its architecture and functionality carries significant risks. Additionally, simulating an exchange gateway can lead to information asymmetry. For example, if the TCP connection between the joint risk control system and the trading gateway fails, the joint risk control system might have received an order, and the OMS system might have changed the order status to "pending," but the order might not actually have been sent to the trading gateway. Summary of the Invention

[0004] The purpose of this invention is to provide a joint risk control method, apparatus, device, and readable storage medium for application in the financial transaction field. This invention maintains the existing TCP connection between the target counter and the target gateway by adding a connection maintenance unit, avoiding the drawbacks of existing related technologies that require interrupting the TCP connection between the trading counter and the trading gateway, and separately establishing TCP connections between the trading counter and the trading gateway and the joint risk control system for information transmission.

[0005] To achieve the above objectives, the present invention provides a joint risk control method, comprising:

[0006] The system receives order information supporting the target exchange protocol sent by the target counter through a TCP connection established with the target gateway via the network port; wherein, the TCP connection is transferred to the connection maintenance unit via the routing unit, and the connection maintenance unit is used to maintain the TCP connection from being interrupted.

[0007] The order information is sent to the connection maintenance unit via the TCP connection, so that the connection maintenance unit sends the copied and parsed order information to the risk control unit for risk assessment; wherein, the connection maintenance unit supports maintaining multiple TCP connections simultaneously without disconnection, and the risk control unit supports performing the risk assessment on the information of multiple TCP connections;

[0008] If a risk exists, the connection maintenance unit is controlled to send the corresponding service rejection information to the target counter through the TCP connection; if no risk exists, the connection maintenance unit is controlled to send the order information to the target gateway through the TCP connection.

[0009] The system receives the return receipt information supporting the target exchange protocol from the target gateway via the TCP connection, and sends the return receipt information to the connection maintenance unit via the TCP connection. The connection maintenance unit then sends the copied protocol-parsed return receipt information to the risk control unit for database update. After that, the return receipt information is sent to the target counter via the TCP connection.

[0010] Optional, also includes:

[0011] Set up an external risk control interface to connect to an external risk control system.

[0012] Optionally, after setting up the external risk control interface for connecting to the external risk control system, the method further includes:

[0013] When a user detects an anomaly at the target counter, the circuit breaker mechanism is activated via the external risk control interface.

[0014] Optionally, when a user detects an anomaly at the target counter, controlling the activation of the circuit breaker mechanism via the external risk control interface includes:

[0015] The TCP connection between the target counter and the target gateway is disconnected via the external risk control interface.

[0016] To achieve the above objectives, the present invention also provides a combined risk control device, comprising:

[0017] The order reporting module is used to receive order information supporting the target exchange protocol sent by the target counter through a TCP connection established with the target gateway via the network port; wherein, the TCP connection is transferred to the connection maintenance unit via the routing unit, and the connection maintenance unit is used to maintain the TCP connection from being interrupted;

[0018] The risk control module is used to send the order information to the connection maintenance unit through the TCP connection, so that the connection maintenance unit sends the copied and parsed order information to the risk control unit for risk assessment; wherein, the connection maintenance unit supports maintaining multiple TCP connections simultaneously without disconnection, and the risk control unit supports performing the risk assessment on the information of multiple TCP connections;

[0019] The processing module is used to control the connection maintenance unit to send the corresponding service rejection information to the target counter through the TCP connection if there is a risk; if there is no risk, it controls the connection maintenance unit to send the order information to the target gateway through the TCP connection.

[0020] The receipt module is used to receive receipt information supporting the target exchange protocol fed back by the target gateway through the TCP connection, and send the receipt information to the connection maintenance unit through the TCP connection. Then, the connection maintenance unit sends the copied protocol-parsed receipt information to the risk control unit for database update, and then sends the receipt information to the target counter through the TCP connection.

[0021] Optional, also includes:

[0022] An external risk control module is used to set up an external risk control interface for connecting to an external risk control system.

[0023] Optionally, the external risk control module further includes:

[0024] The circuit breaker module is used to activate the circuit breaker mechanism through the external risk control interface when the user detects an anomaly at the target counter.

[0025] Optionally, the fuse module includes:

[0026] The connection disconnection unit controls the disconnection of the TCP connection between the target counter and the target gateway through the external risk control interface.

[0027] To achieve the above objectives, the present invention also provides a combined risk control device, comprising:

[0028] Memory, used to store computer programs;

[0029] A processor, used to implement any of the aforementioned joint risk control methods when executing the computer program.

[0030] To achieve the above objectives, the present invention also provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement any of the aforementioned joint risk control methods.

[0031] As can be seen, the present invention maintains the TCP connection between the original target counter and the target gateway by adding a connection maintenance unit, so that the target counter and the target gateway can be directly connected. This avoids the disadvantage of existing related technologies that require interrupting the TCP connection between the transaction counter and the transaction gateway and establishing separate TCP connections between the transaction counter and the transaction gateway and the joint risk control system for information transmission. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0033] Figure 1 A flowchart of a joint risk control method provided in an embodiment of the present invention;

[0034] Figure 2 A specific embodiment of a joint risk control method provided by the present invention is shown in the figure;

[0035] Figure 3 A physical wiring diagram provided for an embodiment of the present invention;

[0036] Figure 4 A schematic diagram of a joint risk control method provided in an embodiment of the present invention;

[0037] Figure 5 This is a structural block diagram of a combined risk control device provided in an embodiment of the present invention. Detailed Implementation

[0038] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0039] The main purpose of the joint risk control system is to conduct unified risk control on transaction orders from multiple counters, solving problems that cannot be solved by a single counter risk control system. For example, when the same account places orders on different counters, there are risk control requirements such as preventing self-trading, verifying funds, and verifying positions for that account. In addition, the overall risk control requirements at the brokerage company level cannot be achieved on a single trading counter.

[0040] For securities firms, a joint risk control system is a pressing need. Currently, most securities firms' joint risk control system solutions mainly involve interrupting the TCP (Transmission Control Protocol) connection between the trading desk and the trading gateway, and establishing separate TCP connections between the trading desk and the trading gateway and the joint risk control system for information transmission. This method requires the trading desk's OMS (Order Management System) to support the joint risk control system's proprietary protocol for interface integration, or the joint risk control system to simulate the trading gateway and interface with the trading desk. The pain points and main reasons for this are as follows:

[0041] OMS system developers need to support not standard exchange protocols, but proprietary protocols developed by joint risk control system developers. Different OMS system developers would have to invest heavily and face high risks in supporting the proprietary protocol of a particular joint risk control system. Furthermore, it is highly impractical for securities firms to persuade different OMS system developers to modify their existing standard exchange protocols to support proprietary protocols developed by competitors.

[0042] The problem with simulating a trading gateway in a joint risk control system is that the specific design of the trading gateway is not publicly disclosed. It undertakes core functions such as rule checks and network flow control before orders are sent to the exchange's matching system. Simulating a trading gateway without disclosing the system architecture and functions poses a significant risk. In addition, simulating an exchange gateway can also lead to information asymmetry. For example, if the TCP connection between the joint risk control system and the trading gateway fails, there may be a situation where the joint risk control system has received an order, and the OMS system has modified the order status to be pending, but in reality, the order has not been sent to the trading gateway.

[0043] Both of the above scenarios present numerous and largely unsolvable problems in practical implementation, preventing most securities firms from using a joint risk control system. Furthermore, both systems suffer from significant latency and performance fluctuations. This invention addresses these issues by adding a connection maintenance unit to maintain the existing TCP connection between the target counter and the target gateway, enabling direct connection between them without modifying the existing OMS system. This allows for seamless integration with the joint risk control system, achieving non-intrusive deployment without altering the existing TCP connection between the OMS system and the TGW (Trade Gateway). The OMS system remains connected to the TGW system, eliminating the need for additional TCP connections. This system utilizes FPGA (Field-Programmable Gate Array) hardware for risk control and storage, enabling device-level, seat-level, and account-level joint risk control across multiple OMS systems. It fulfills the risk control requirements of securities firms, providing comprehensive pre-event, during-event, and post-event risk control solutions.

[0044] The following combination Figure 1 , Figure 1 A flowchart of a joint risk control method provided in an embodiment of the present invention, the method may include:

[0045] S101: Receives order information supporting the target exchange protocol sent by the target counter through a TCP connection established with the target gateway via the network port; wherein, the TCP connection is transferred to the connection maintenance unit via the routing unit, and the connection maintenance unit is used to maintain the TCP connection from being interrupted.

[0046] The trading gateways and trading desks connect to the joint risk control system via hardware network ports. This embodiment does not limit the number of network ports; typically, 24 ports can be set up for accessing multiple trading desks, multiple trading gateways, and multiple external risk control systems, as well as for receiving market data. This embodiment also does not limit the number of trading desks and trading gateways connected to the joint risk control system. Joint risk control means that all information sent by trading desks and trading gateways must undergo pre-processing by the joint risk control system. This embodiment selects any group of trading desks and trading gateways as the target desks and gateways for the joint risk control process, but this does not mean that the joint risk control system can only process information from any group of trading desks and trading gateways. The joint risk control system can process information from any trading desk and trading gateway.

[0047] The connection maintenance unit can simultaneously maintain TCP connections for multiple trading desks and trading gateways. The risk control unit can also perform joint risk control on information transmitted through multiple connections to achieve joint risk control for multiple desks. In existing related technologies, trading desks need to support the private protocol of the joint risk control system to access it. In this embodiment, by maintaining the original TCP connections without disconnecting, the joint risk control system can parse and perform risk control on information that supports the target exchange protocol. Third-party trading desk systems can seamlessly access the joint risk control system without changing their interfaces.

[0048] The joint risk control system in this embodiment typically employs FPGA hardware risk control. FPGAs offer high throughput and low latency, enabling stable system performance at the nanosecond level, meeting the low latency requirements of trading systems. The routing unit, connection maintenance unit, and risk control unit in this embodiment are all hardware units on an FPGA. The TCP connection between the target counter and the target gateway can be routed to the connection maintenance unit via the routing unit. The connection maintenance unit maintains the existing TCP connection between the target counter and the target gateway. The risk control unit can act as a bypass connected to the connection maintenance unit. In this embodiment, a TCP connection is pre-established with the target counter before it sends order information supporting the target exchange protocol. Data transmitted through this TCP connection can be forwarded by the routing unit. The routing unit can typically handle data routing across multiple network ports; therefore, the joint risk control system possesses some Ethernet routing capabilities.

[0049] S102: The order information is sent to the connection maintenance unit via a TCP connection, so that the connection maintenance unit sends the copied and parsed order information to the risk control unit for risk assessment; wherein, the connection maintenance unit supports maintaining multiple TCP connections simultaneously without disconnection, and the risk control unit supports risk assessment of information from multiple TCP connections.

[0050] Understandably, in existing related technologies, setting up a joint risk control system requires interrupting the existing TCP connection between the trading counter and the trading gateway, and establishing separate TCP connections between the trading counter and the trading gateway and the joint risk control system. This embodiment maintains the existing TCP connection between the target counter and the target gateway by setting up a connection maintenance unit. This TCP connection can connect the target counter, the routing unit, the connection maintenance unit, and the target gateway. Order information supporting the target exchange protocol can be forwarded to the connection maintenance unit via the routing unit. After receiving the order information, the connection maintenance unit can copy the order information and forward the copied order information after protocol parsing to the risk control unit for risk assessment.

[0051] S103: If a risk exists, the control connection maintenance unit sends the corresponding service rejection information to the target counter via a TCP connection; if no risk exists, the control connection maintenance unit sends the order information to the target gateway via a TCP connection.

[0052] This embodiment does not limit the specific method by which the risk control unit performs risk assessment. The risk control unit can perform the calculation, comparison, and interception of the order information. If the order information is risky, the connection maintenance unit sends the corresponding business rejection information to the transaction counter via the existing TCP connection to remind the transaction personnel that the transaction has failed. If the order information is not risky, the connection maintenance unit sends the order information to the target gateway via the existing TCP connection to complete the transaction.

[0053] S104: Receive the order information that supports the target exchange protocol from the target gateway via TCP connection, and send the order information to the connection maintenance unit via TCP connection. Then, the connection maintenance unit sends the copied protocol-parsed order information to the risk control unit for database update, and then sends the order information to the target counter via TCP connection.

[0054] Understandably, after a transaction is completed, the target gateway will send back a confirmation message that supports the target exchange's protocol via the TCP connection. After receiving the confirmation message, the FPGA will forward it to the connection maintenance unit. The connection maintenance unit will copy the confirmation message and parse the protocol before sending it to the risk control unit for database update so that the risk control unit can confirm that the transaction is completed. After the database update is completed, the confirmation message will be sent to the trading desk via the original TCP connection.

[0055] Furthermore, to prevent the performance of the built-in risk control unit from failing to meet system requirements, this embodiment typically sets up an external risk control interface on the FPGA. This external interface allows connection to a more powerful external risk control unit for risk control processing. The extended external risk control interface enables pre-event risk control, as well as in-event or post-event risk control. This embodiment does not limit the number of external risk control interfaces or the number of external risk control units that can be connected. Furthermore, this embodiment can also set up a circuit breaker mechanism to ensure the transaction security of the joint risk control system. The joint risk control system itself is a pre-event risk control system, and it also supports the access of third-party post-event risk control systems. When a user determines that a trading counter has abnormal behavior, they can control the activation of the circuit breaker mechanism through the external risk control interface to ensure system security. This embodiment does not limit the specific method of initiating the circuit breaker mechanism; generally, it can involve controlling the disconnection of the target counter's TCP connection with the target gateway.

[0056] This embodiment maintains the existing TCP connection between the target counter and the target gateway by adding a connection maintenance unit, so that the target counter and the target gateway can connect directly. This avoids the disadvantage of existing related technologies that require interrupting the TCP connection between the transaction counter and the transaction gateway and establishing separate TCP connections between the transaction counter and the transaction gateway and the joint risk control system for information transmission.

[0057] The following combination Figure 2 , Figure 2 This is a flowchart illustrating a joint risk control method provided in an embodiment of the present invention, wherein an FPGA can be used as hardware risk control. This specific embodiment may include:

[0058] 1. The FPGA receives order information sent by the trading desk that supports the target exchange protocol.

[0059] 2. The order information is forwarded to the connection maintenance unit via the routing unit, so that the connection maintenance unit can send the copied, protocol-parsed order information to the risk control unit for risk assessment.

[0060] 3. If a risk exists, the connection maintenance unit will send the corresponding service rejection information to the transaction counter.

[0061] 4. If there is no risk, the connection maintenance unit will send the order information to the transaction gateway.

[0062] 5. Receive receipt information and send it to the connection maintenance unit so that the connection maintenance unit can send the copied and parsed receipt information to the risk control unit for database update and then send the receipt information to the transaction gateway.

[0063] The following combination Figure 3 , Figure 3 This is a physical wiring diagram provided for an embodiment of the present invention.

[0064] from Figure 3 It can be seen that this invention does not limit the number of FPGA network ports, nor the number of trading counters and trading gateways. The trading gateway can physically connect the trading counters to the joint risk control hardware devices via the network ports. Functionally, this solution also implements a routing algorithm based on ARP (Address Resolution Protocol), which can replace switches to achieve data routing functions based on different physical network ports. An external risk control interface can be set on the FPGA, through which a more powerful external risk control system can be connected for risk control processing. This embodiment does not limit the number of external risk control interfaces, nor the number of external risk control systems that can be connected.

[0065] The following combination Figure 4 , Figure 4This is a schematic diagram of a joint risk control method provided in an embodiment of the present invention.

[0066] In this scheme, the target gateway and target counter are arbitrarily selected from multiple trading gateways and trading counters connected to the joint risk control hardware device as examples. The connection maintenance unit is used to maintain the TCP connection between the target counter and the target gateway without interruption. Order information sent by the trading counter that supports the target exchange protocol is not directly sent to the target gateway after passing through the routing unit, but is instead forwarded to the connection maintenance unit. Data transmission between the routing unit and the connection maintenance unit still uses the original TCP connection. The risk control unit connects to the connection maintenance unit as a bypass. The connection maintenance unit copies the received information, parses the protocol, and forwards it to the risk control unit for risk control processing. Based on the processing result, it sends the corresponding information to the target gateway or target counter through the original TCP connection. If the transaction is completed, the target gateway will report receipt information that supports the target exchange protocol. After receiving the receipt information, the connection maintenance unit copies and parses it before sending it to the risk control unit for database updates. Then, it sends the receipt information to the target counter through the original TCP connection.

[0067] The following describes the joint risk control device, equipment, and readable storage medium provided in the embodiments of the present invention. The joint risk control device, equipment, and readable storage medium described below can be referred to in correspondence with the joint risk control method described above.

[0068] The following combination Figure 5 , Figure 5 This is a structural block diagram of a combined risk control device provided in an embodiment of the present invention. The device may include:

[0069] The order reporting module 100 is used to receive order information supporting the target exchange protocol sent by the target counter through a TCP connection established with the target gateway via the network port; wherein, the TCP connection is transferred to the connection maintenance unit via the routing unit, and the connection maintenance unit is used to maintain the TCP connection from being interrupted.

[0070] The risk control module 200 is used to send the order information to the connection maintenance unit via a TCP connection, so that the connection maintenance unit can send the copied and parsed order information to the risk control unit for risk assessment. The connection maintenance unit supports maintaining multiple TCP connections simultaneously without disconnection, and the risk control unit supports risk assessment of information from multiple TCP connections.

[0071] The processing module 300 is used to control the connection maintenance unit to send the corresponding service rejection information to the target counter via TCP connection if there is a risk; if there is no risk, the control connection maintenance unit sends the order information to the target gateway via TCP connection.

[0072] The receipt module 400 is used to receive receipt information that supports the target exchange protocol fed back by the target gateway through a TCP connection. It then sends the receipt information to the connection maintenance unit through a TCP connection. The connection maintenance unit then sends the copied protocol-parsed receipt information to the risk control unit for database updates. Finally, it sends the receipt information to the target counter through a TCP connection.

[0073] Based on the above embodiments, the present invention maintains the TCP connection between the original target counter and the target gateway by adding a connection maintenance unit, so that the target counter and the target gateway can be directly connected. This avoids the disadvantage of existing related technologies that require interrupting the TCP connection between the transaction counter and the transaction gateway and establishing separate TCP connections between the transaction counter and the transaction gateway and the joint risk control system for information transmission.

[0074] Based on the above embodiments, the device further includes:

[0075] An external risk control module is used to set up an external risk control interface for connecting to an external risk control system.

[0076] Based on the above embodiments, the external risk control module also includes:

[0077] The circuit breaker module is used to activate the circuit breaker mechanism via an external risk control interface when a user detects an anomaly at the target counter.

[0078] Based on the above embodiments, the fuse module includes:

[0079] The connection disconnection unit controls the disconnection of the TCP connection between the target counter and the target gateway via an external risk control interface.

[0080] Based on the above embodiments, the present invention also provides a combined risk control device, which may include a memory and a processor. The memory stores a computer program, and when the processor calls the computer program in the memory, it can implement the steps provided in the above embodiments. Of course, the device may also include various necessary network interfaces, power supplies, and other components.

[0081] The present invention also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by an execution terminal or processor, it can implement the joint risk control method provided in the embodiments of the present invention. The storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0082] This document uses specific examples to illustrate the principles and implementation methods of the present invention, and the various embodiments are progressively related. Each embodiment focuses on the differences from other embodiments, and similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, please refer to the corresponding method section. The above description of the embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. For those skilled in the art, several improvements and modifications can be made to the present invention without departing from the principles of the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

[0083] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

Claims

1. A joint risk control method, characterized in that, include: The system receives order information supporting the target exchange protocol sent by the target counter through a TCP connection established with the target gateway via the network port; wherein, the TCP connection is transferred to the connection maintenance unit via the routing unit, and the connection maintenance unit is used to maintain the TCP connection from being interrupted. The order information is sent to the connection maintenance unit via the TCP connection, so that the connection maintenance unit sends the copied and parsed order information to the risk control unit for risk assessment; wherein, the connection maintenance unit supports maintaining multiple TCP connections simultaneously without disconnection, and the risk control unit supports performing the risk assessment on the information of multiple TCP connections; If a risk exists, the connection maintenance unit is controlled to send the corresponding service rejection information to the target counter through the TCP connection; if no risk exists, the connection maintenance unit is controlled to send the order information to the target gateway through the TCP connection. The system receives the return receipt information supporting the target exchange protocol from the target gateway via the TCP connection, and sends the return receipt information to the connection maintenance unit via the TCP connection. Then, the connection maintenance unit sends the copied protocol-parsed return receipt information to the risk control unit for database update, and then sends the return receipt information to the target counter via the TCP connection. An external risk control interface is set up to connect to an external risk control system; when a user detects an anomaly at the target counter, the circuit breaker mechanism is activated through the external risk control interface.

2. The joint risk control method according to claim 1, characterized in that, When a user detects an anomaly at the target counter, the circuit breaker mechanism is activated via the external risk control interface, including: The TCP connection between the target counter and the target gateway is disconnected via the external risk control interface.

3. A combined risk control device, characterized in that, include: The order reporting module is used to receive order information supporting the target exchange protocol sent by the target counter through a TCP connection established with the target gateway via the network port; wherein, the TCP connection is transferred to the connection maintenance unit via the routing unit, and the connection maintenance unit is used to maintain the TCP connection from being interrupted; The risk control module is used to send the order information to the connection maintenance unit through the TCP connection, so that the connection maintenance unit sends the copied and parsed order information to the risk control unit for risk assessment; wherein, the connection maintenance unit supports maintaining multiple TCP connections simultaneously without disconnection, and the risk control unit supports performing the risk assessment on the information of multiple TCP connections; The processing module is used to control the connection maintenance unit to send the corresponding service rejection information to the target counter through the TCP connection if there is a risk; if there is no risk, it controls the connection maintenance unit to send the order information to the target gateway through the TCP connection. The receipt module is used to receive receipt information that supports the target exchange protocol fed back by the target gateway through the TCP connection, and send the receipt information to the connection maintenance unit through the TCP connection, so that the connection maintenance unit sends the copied protocol-parsed receipt information to the risk control unit for database update, and then sends the receipt information to the target counter through the TCP connection. An external risk control module is used to set up an external risk control interface for connecting to an external risk control system. The external risk control module also includes a circuit breaker module, which is used to control the activation of the circuit breaker mechanism through the external risk control interface when the user detects an anomaly in the target counter.

4. The combined risk control device according to claim 3, characterized in that, The fuse module includes: The connection disconnection unit controls the disconnection of the TCP connection between the target counter and the target gateway through the external risk control interface.

5. A combined risk control device, characterized in that, include: Memory, used to store computer programs; A processor for implementing the joint risk control method as described in claim 1 or 2 when executing the computer program.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the joint risk control method as described in claim 1 or 2.

Images