WO2020006903A1

WO2020006903A1 - Financial data interaction method, apparatus computer device and storage medium

Info

Publication number: WO2020006903A1
Application number: PCT/CN2018/108417
Authority: WO
Inventors: 刘建; 宁之孟; 魏尧东; 金明
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-07-02
Filing date: 2018-09-28
Publication date: 2020-01-09
Also published as: CN109062982A; CN109062982B

Abstract

Provided are a financial data interaction method, an apparatus, a computer device and a storage medium. Since multiple UKey interfaces are set on an enterprise front-end machine, and corresponding configurations are implemented, the enterprise front-end machine can perform direct bank-enterprise connection functions with multiple different types of banks to ensure the normal use of each bank account. In order to ensure the stable operation of the enterprise front-end machine and the efficiency of operation, the configuration of a cache queue and a thread pool is set in the enterprise front-end machine to perform various tasks in an orderly manner; Further, only a task ID is cached in the cache queue, and when it's the turn of the task, the specific direct bank-enterprise connection task is retrieved from an application server according to the task ID to save the cache space, and further improve the operating speed and operation stability of the enterprise front-end machine.

Description

Financial data interaction method, device, computer equipment and storage medium

This application claims priority from a Chinese patent application filed with the Chinese Patent Office on July 2, 2018, with an application number of 2018107078768, and the application name is "Methods, Devices, Computer Equipment, and Storage Media for Interactive Financial Data", the entire contents of which are hereby incorporated by reference. Incorporated in this application.

Technical field

The present application relates to the field of computers, and in particular, to a method, an apparatus, a computer device, and a storage medium for interacting financial data.

Background technique

Bank-enterprise direct connection is a new online banking system that connects directly to the corporate financial system. Bank-enterprise direct connection has realized the organic integration and smooth docking of banks and corporate computer systems through the Internet or dedicated line connection. At the same time, Bank-enterprise Direct Link can provide support for enterprises to develop and customize personalized functions in the financial system, with distinctive features of information synchronization, high efficiency and simplicity, personalized service, and safety and reliability. The bank-enterprise direct connection can be connected with the enterprise computer system and facilitate the completion of bank-related transactions in the enterprise system.

The enterprise needs to open the bank-enterprise direct account at the corresponding bank. When an enterprise performs financial data interaction with a bank through the financial system, it is necessary to set up an enterprise-side front-end machine that matches the bank-side front-end machine in the enterprise, and insert the corresponding UKey on the enterprise side before it can communicate with the corresponding bank-side The front-end machine interacts. In this way, if an enterprise establishes a bank-enterprise direct connection with different banks, it is necessary to set up multiple enterprise-end front-end machines. When interacting with different banks, select different enterprise-end front-end machines. That is, the traditional front-end bank of an enterprise can only connect one front-end bank. After the operation is completed, another front-end bank needs to be replaced, and multiple banks cannot be operated on one front-end bank at the same time.

technical problem

The main purpose of this application is to provide a financial data interaction method, device, computer equipment, and storage medium that facilitates the interaction of financial data between enterprises and different banks, without the need to convert the operation of the front end of the enterprise.

Technical solutions

In order to achieve the above-mentioned object of the invention, the present application proposes a method for financial data interaction, which uses an enterprise-end front-end to implement financial-data interaction between the enterprise-end financial system and the bank, wherein the enterprise-end front-end is provided with multiple UKey interfaces, The enterprise-end front-end processor corresponding to a plurality of the UKey interfaces is configured to complete financial data interaction with a plurality of bank-end front-end processors of different types of banks; the method includes:

Monitoring whether the application server of the front end of the enterprise sends a bank-enterprise direct connection task;

If yes, obtain the task ID of the bank-enterprise direct link task, and place the task ID in the corresponding cache queue;

When the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain the corresponding bank-enterprise direct task from the application server according to the task ID;

Analyze the bank-enterprise direct link task to obtain configuration information of the bank-side front-end processor corresponding to the bank-enterprise direct link task;

Sending the bank-enterprise direct connection task to the bank-end front-end processor according to the configuration information;

And sending a result message returned by the bank-side front end to the application server.

This application also provides a financial data interaction device, which uses an enterprise-end front-end to implement financial data interaction between the enterprise-side financial system and the bank-side, wherein the enterprise-end front-end is provided with multiple UKey interfaces, and the enterprise-end front-end The set-up corresponds to a plurality of the UKey interfaces configured to complete financial data interaction with a plurality of bank-end front-end machines of different types of banks; the device includes:

A monitoring unit, configured to monitor whether an application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task;

A cache unit, configured to: if the monitoring unit monitors the bank-enterprise direct link task sent by the application server, obtain a task ID of the bank-enterprise direct link task, and place the task ID in a corresponding cache queue;

An obtaining unit, configured to, when the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain the corresponding bank-enterprise direct task from the application server according to the task ID;

An analysis unit, configured to analyze the bank-enterprise direct link task to obtain configuration information of a bank-side front-end processor corresponding to the bank-enterprise direct link task;

A sending unit, configured to send the bank-enterprise direct connection task to the bank-end front-end processor according to the configuration information;

The forwarding unit is configured to send a result message returned by the bank-side front end to the application server.

The present application further provides a computer device including a memory and a processor, where the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, implements the steps of any of the foregoing methods.

The present application also provides a computer non-volatile readable storage medium having computer-readable instructions stored thereon, which are executed by a processor to implement the steps of the method according to any one of the foregoing.

Beneficial effect

The financial data interaction method, device, computer equipment and storage medium of this application, because multiple UKey interfaces are set on the enterprise-end front-end processor and corresponding configurations are performed, the enterprise-end front-end processor can communicate with multiple different types of The bank performs the bank-enterprise direct connection function to ensure the normal use of each bank account. In order to ensure the stable operation and efficiency of the enterprise-side front-end processor, the cache queue and thread pool configuration will be set in the enterprise-side front-end processor to perform various tasks in an orderly manner; further, the cache queue Only the task ID is cached. When it is the task's turn, the specific bank-enterprise direct connection task is retrieved from the application server according to the task ID to save cache space and further improve the operation speed and stable operation of the enterprise front-end processor. Sex.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic flowchart of a financial data interaction method according to an embodiment of the present invention;

FIG. 2 is a detailed flowchart of step S2 of a financial data interaction method according to an embodiment of the present invention; FIG.

3 is a schematic flowchart of a financial data interaction method according to an embodiment of the present invention;

4 is a schematic structural block diagram of a financial data interaction device according to an embodiment of the present invention;

5 is a schematic block diagram of a structure of a cache unit according to an embodiment of the present invention;

FIG. 6 is a schematic structural block diagram of a financial data interaction device according to an embodiment of the present invention; FIG.

7 is a schematic block diagram of a structure of a monitoring unit according to an embodiment of the present invention;

FIG. 8 is a schematic block diagram of a computer device according to an embodiment of the present invention.

Best Mode of the Invention

In order to make the purpose, technical solution, and advantages of the present application clearer, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

Referring to FIG. 1, an embodiment of the present application provides a method for financial data interaction, which uses an enterprise-end front-end machine to implement financial-data interaction between an enterprise-side financial system and a bank-side, wherein the enterprise-end front-end machine is provided with multiple UKey interfaces. The enterprise front-end processor corresponds to a plurality of the UKey interfaces and is configured to complete financial data interaction with a plurality of different bank-end front-end processors.

The above-mentioned enterprise-side front-end machine refers to the front-end machine set on the enterprise side, and is an intermediate device when the enterprise-side financial system is directly connected with the bank-bank-enterprise. The foregoing enterprise-side front-end machine is configured to complete data interaction with a plurality of different types of bank-side front-end machines. The configuration process is that when an enterprise-side front-end machine is installed, the enterprise-side front-end machine has an administrator interface. Enter the specified configuration information in the preset interface. The configuration information includes the enterprise ID, the enterprise front-end processor number, the bank server IP, the bank port, the bank-enterprise direct connection number of the bank, and the bank-end front-end processor version number. , Banks and other corporate financial systems and banks complete the necessary parameters for direct bank-enterprise integration, and configure the number of threads to configure multi-threaded tasks; then send the configuration results to the application corresponding to the enterprise front-end processor server. That is, configure the bank-enterprise direct account number and related information that are applied for. When an enterprise needs to log in to each bank-enterprise direct account to obtain data (transaction data, query data, etc.) in its corresponding bank, it only needs to be in the enterprise. The corresponding UKey (a small storage device directly connected to the computer via USB, with password verification function, and reliable and high speed) can be inserted into the front-end machine, which can realize an enterprise-side front-end machine and a number of different types of banks. Set-up connection, the enterprise centrally and centrally manages the user's bank UKey without the need for bank switching operations. The front-end of the enterprise can easily obtain the account information, transaction flow information, and balance information of each bank-enterprise direct account of the enterprise, and can perform related operations such as payment, collection, and transfer. The above major banks refer to different banks. For example, ICBC and China Construction Bank belong to two different major banks, that is, banks using different front-end processors are considered to be different major banks.

The above financial data interaction method includes steps:

S1. Monitor whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task;

S2: If yes, obtain the task ID of the bank-enterprise direct task, and place the task ID in the corresponding cache queue;

S3. When the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain the corresponding bank-enterprise direct connection task from the application server according to the task ID;

S4: Analyze the bank-enterprise direct link task to obtain configuration information of the bank-side front-end processor corresponding to the bank-enterprise direct link task;

S5. Send the bank-enterprise direct connection task to the bank-end front-end processor according to the configuration information;

S6. Send a result message returned by the bank-side front end to the application server.

As described in step S1 above, the application server refers to a third-party application server that provides the enterprise-side front-end processor to the enterprise. As the management background of the enterprise-side front-end processor, tasks issued by the enterprise will first enter the application server. It is then sent by the application server to the enterprise front end. The tasks issued by the above-mentioned enterprises are tasks of various business operations such as the management and scheduling of bank accounts and funds issued by the enterprise through the financial system. The above-mentioned bank-enterprise direct link task is that the enterprise initiates a request through the financial system, the request is sent to the application server, and the application server initiates the corresponding task to the enterprise-end front-end processor according to this request.

As described in step S2 above, the above-mentioned bank-enterprise direct link task exists in the form of a message. The above-mentioned task ID is only an identifier and has no task content, so as to prevent the message of the bank-enterprise direct link task from being directly placed on the enterprise side The front-end machine occupies the running space of the enterprise-end front-end machine, which reduces the operating speed. Because the above-mentioned enterprise-side front-end machine can be connected to multiple bank-side front-end machines, there will be more direct bank-enterprise tasks of various types, and the packets of various bank-enterprise direct-connection tasks will be directly stacked on the enterprise-side front-end machine. In the cache, it will greatly reduce the operating efficiency of the front end of the enterprise side, and even crash. Therefore, in this embodiment, the task ID is only placed in the cache of the enterprise-end front-end processor, which greatly reduces the cache space requirement of the enterprise-end front-end processor and improves the quality of the operating environment.

As described in step S3 above, the above thread pool is a form of multi-threaded processing. Tasks are added to the queue during processing, and then these tasks are automatically started after the threads are created. Thread pool threads are background threads. Each thread uses the default stack size, runs at the default priority, and is in a multithreaded apartment. If a thread is idle in managed code (such as waiting for an event), the thread pool inserts another worker thread to keep all processors busy. If all thread pool threads remain busy all the time, but the queue contains pending work, the thread pool will create another worker thread after a period of time, but the number of threads will never exceed the maximum. Threads that exceed the maximum can be queued, but they will not start until other threads have completed. In this application, a specified number of threads are always maintained in the thread pool. When a thread is idle, the task is obtained from the above cache queue. Because the cache queue is only a task ID, it is adjusted to the application server according to the task ID. Take the corresponding bank-enterprise direct mission. The number of threads in the above thread pool can be configured when the enterprise-side front-end processor is configured, such as 5, 10, 20, etc., which can be configured according to specific needs.

As described in the above steps S4 and S5, because the above-mentioned bank-enterprise direct connection task is targeted, such as calling the bank statement of the bank account corresponding to the type a bank, the configuration information will include the bank end corresponding to the type a bank The serial number of the front-end processor and the IP of the bank server corresponding to the type a bank are all information in the application server that is configured when the front-end processor of the enterprise is installed and sent to the corresponding front-end server of the enterprise. Therefore, the above application server will automatically write this information into the bank-enterprise direct connection task according to the request of the enterprise, so that the enterprise-end front-end processor can accurately connect to the corresponding bank-end front-end processor.

As described in step S6 above, when the front end of the bank receives the direct bank-enterprise task, it will forward it to the corresponding bank server, and the bank server will retrieve the corresponding data generation result message and send it to the first bank. The machine is set up to return to the enterprise-end front-end machine, and the enterprise-end front-end machine is forwarding to the application server, and the application server finally feeds back the result message to the financial software system of the enterprise.

Referring to FIG. 2, in one embodiment, the step S2 of obtaining the task ID of the bank-enterprise direct link task and putting the task ID into a corresponding cache queue includes:

S21: Obtain a task ID of the bank-enterprise direct link task;

S22. Determine the attributes of the task ID, where the attributes include transaction attributes and query attributes;

S23. Put the task ID into a cache queue of a corresponding attribute according to the determination result.

As described in the above steps S21, S22, and S23, the attributes of the task ID are generally determined by the request issued by the financial system of the enterprise. They can include transaction attributes and query attributes. The query attributes are the query of the company's bank flow, account balance, and payment. The attributes corresponding to requests such as status, and the transaction attributes are the attributes corresponding to requests such as payment and transfer. In the front end of the enterprise, a transaction cache queue corresponding to the transaction attribute and a query cache queue corresponding to the query attribute are also provided. A transaction thread pool corresponding to the transaction cache queue and a query thread pool corresponding to the query cache queue are also set. Each task ID in the two cache queues is sorted and processed according to a preset priority, for example, the level of payment is higher than the level of querying the bank flow. Specifically, each task is provided with a type identifier, and the type identifier can be divided into 1-8 levels, and the highest level is 1, which represents emergency tasks and is given priority processing. Various bank-enterprise direct tasks correspond to different type identifiers, and their corresponding task IDs have the same type identifier.

Referring to FIG. 3, in an embodiment, before the step S1 of monitoring whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task, the method includes:

S101. Determine whether a UKey device corresponding to various types of banks is inserted into the enterprise-end front-end processor;

S102. If not, an alarm is issued.

As described in steps S101 and S102 above, collect the identifier of the UKey device corresponding to the type of bank inserted in each UKey interface, and then compare the identifier with the identifier representing various types of banks configured when the front end of the enterprise is configured. If the collected logos completely cover the logos representing various types of banks configured when the enterprise-end front-end is configured, it is determined that UKey devices corresponding to various types of banks are inserted into the enterprise-end front-end, and subsequent steps such as step S1 can be performed. If not, extract the type of bank corresponding to the uncovered logo and send it to the relevant personnel of the enterprise to report the alarm. At this time, the relevant personnel of the enterprise can perform corresponding processing and forget the inserted UKey device or the insertion place will be loose. Re-insertion of UKey equipment caused by poor contact to ensure the interaction between the enterprise and the banks. In another embodiment, it is also possible to determine whether the number of the obtained UKey device identification is the same as the identification number (not duplicate) representing various types of banks configured when the enterprise front end is configured, because a bank will only issue one UKey For enterprises, when the number is the same, it can basically be judged that UKey equipment corresponding to various types of banks is inserted into the front end of the enterprise. Although this judgment method has defects, the judgment speed will be faster.

In one embodiment, the financial data interaction method further includes: sending a heartbeat detection packet to detect a connection status with the application server; and if the connection status is disconnected, sending an alarm message.

Theoretically, the enterprise front-end machine and the application server should be online for a long time, but because it is an electronic product, it will inevitably fail or upgrade. At this time, the enterprise front-end machine and the application server may lose the connection. This method detects the connection status between the enterprise front end and the application server. When the connection between the two fails, an alarm message needs to be issued. There are two types of alarm messages. The first is to send information such as emails to relevant personnel of the enterprise, and / or to the relevant personnel of the third party who provides the front end of the enterprise. The second is to send specified information to connect with it. The bank-side front-end machine is sent to the bank's relevant management system by the bank-side front-end machine to inform the bank-side staff. The bank-side staff can manually notify the corresponding staff of the enterprise-side that a disconnection failure has occurred. The above-mentioned sending of the heartbeat detection packet can ensure that the financial person at the enterprise side knows whether the front-end processor of the enterprise side and the application server are disconnected, so as to timely process things that should be completed directly by the bank and enterprise.

In one embodiment, the above-mentioned step S1 of monitoring whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task includes:

S11. Monitor whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task through a long connection.

As described in step S11 above, because the bank-enterprise direct connection task received by the front-end server of the enterprise may be continuous, the service is monitored by using a long connection method, so that each operation is not disconnected, and the next time it is processed directly It is sufficient to send data packets without establishing a TCP (Transmission Control Protocol) connection to maintain the efficiency of processing tasks. In this embodiment, the front end of the enterprise side and the application server use the block input output (BIO) synchronous blocking mode for a long connection. Different bank-enterprise direct tasks cannot be performed at the same time, so they need to be performed in accordance with the order of instructions. One instruction can be executed before the next instruction can be executed. It cannot be executed asynchronously. Therefore, in this application, the front end of the enterprise uses the BIO synchronous blocking mode and the application server Make a long connection.

In one embodiment, the messages sent by the enterprise front end and the application server are serialized using Protocol Buffers.

Protocol Buffers It is a lightweight and efficient structured data storage format, which can be used for serialization of structured data, or serialization. It is very suitable for data storage or RPC data exchange format. Language-independent, platform-independent, and extensible serialization structure data format that can be used in communication protocols, data storage, etc., simply The main advantages of Protobuf are: simple and fast. This application uses GOOGLE's Protocol Buffers for serialization, which can improve the efficiency of message packaging and sending.

In the financial data interaction method of the embodiment of the present application, since multiple UKey interfaces are set on the enterprise-end front-end unit and corresponding configurations are performed, the enterprise-side front-end unit can directly connect with banks of different types with different types of banks Function to ensure the normal use of each bank account. In order to ensure the stable operation and efficiency of the enterprise-side front-end processor, the cache queue and thread pool configuration will be set in the enterprise-side front-end processor to perform various tasks in an orderly manner; further, the cache queue Only the task ID is cached. When it is the task's turn, the specific bank-enterprise direct connection task is retrieved from the application server according to the task ID to save cache space and further improve the operation speed and stable operation of the enterprise front-end processor. Sex.

Referring to FIG. 4, an embodiment of the present application provides a financial data interaction device, which uses an enterprise-end front-end processor to implement financial-data interaction between an enterprise-end financial system and a bank-side, wherein the enterprise-end front-end processor is provided with multiple UKey interfaces. The enterprise front-end processor corresponds to a plurality of the UKey interfaces and is configured to complete financial data interaction with a plurality of different bank-end front-end processors.

The above-mentioned enterprise-side front-end machine refers to the front-end machine set on the enterprise side, and is an intermediate device when the enterprise-side financial system is directly connected with the bank-bank-enterprise. The foregoing enterprise-side front-end machine is configured to complete data interaction with a plurality of different types of bank-side front-end machines. The configuration process is that when an enterprise-side front-end machine is installed, the enterprise-side front-end machine has an administrator interface. Enter the specified configuration information in the preset interface. The configuration information includes the enterprise ID, the enterprise front-end processor number, the bank server IP, the bank port, the bank-enterprise direct connection number of the bank, and the bank-end front-end processor version number. , Banks and other corporate financial systems and banks complete the necessary parameters for direct bank-enterprise integration, and configure the number of threads to configure multi-threaded tasks; then send the configuration results to the application corresponding to the enterprise front-end processor server. That is, configure the bank-enterprise direct account number and related information that are applied for. When an enterprise needs to log in to each bank-enterprise direct account to obtain data (transaction data, query data, etc.) in its corresponding bank, it only needs to be in the enterprise. The corresponding UKey can be inserted into the front-end machine, and an enterprise-side front-end machine can be connected to multiple front-end machines of different types of banks. The enterprise centrally manages the user's bank UKey, without the need for bank switching operations. The front-end of the enterprise can easily obtain the account information, transaction flow information, and balance information of each bank-enterprise direct account of the enterprise, and can perform related operations such as payment, collection, and transfer. The above major banks refer to different banks. For example, ICBC and China Construction Bank belong to two different major banks, that is, banks using different front-end processors are considered to be different major banks.

The above financial data interaction device includes steps:

The monitoring unit 10 is configured to monitor whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task;

The cache unit 20 is configured to: if the monitoring unit monitors the bank-enterprise direct link task sent by the application server, obtain a task ID of the bank-enterprise direct link task, and place the task ID in a corresponding cache queue ;

An obtaining unit 30, configured to obtain a corresponding bank-enterprise direct task from the application server according to the task ID when the thread pool corresponding to the cache queue acquires a task from the cache queue;

An analysis unit 40 is configured to analyze the bank-enterprise direct link task to obtain configuration information of a bank-side front-end processor corresponding to the bank-enterprise direct link task;

A sending unit 50, configured to send the bank-enterprise direct connection task to the bank-side front-end processor according to the configuration information;

The forwarding unit 60 is configured to send a result message returned by the bank-end front end to the application server.

In the monitoring unit 10, the application server refers to a third-party application server that provides an enterprise-side front-end machine to an enterprise. As an application background of the enterprise-side front-end machine, tasks issued by the enterprise will first enter the application server. It is then sent by the application server to the enterprise front end. The tasks issued by the above-mentioned enterprises are tasks of various business operations such as the management and scheduling of bank accounts and funds issued by the enterprise through the financial system. The above-mentioned bank-enterprise direct link task is that the enterprise initiates a request through the financial system, the request is sent to the application server, and the application server initiates the corresponding task to the enterprise-end front-end processor according to this request.

In the buffer unit 20, the bank-enterprise direct link task exists in the form of a message, and the task ID is only an identifier, and there is no task content to prevent the message of the bank-enterprise direct link task from being directly placed on the enterprise side. The front-end machine occupies the running space of the enterprise-end front-end machine, which reduces the operating speed. Because the above-mentioned enterprise-side front-end machine can be connected to multiple bank-side front-end machines, there will be more direct bank-enterprise tasks of various types, and the packets of various bank-enterprise direct-connection tasks will be directly stacked on the enterprise-side front-end machine In the cache, it will greatly reduce the operating efficiency of the front end of the enterprise side, and even crash. Therefore, in this embodiment, the task ID is only placed in the cache of the enterprise-end front-end processor, which greatly reduces the cache space requirement of the enterprise-end front-end processor and improves the quality of the operating environment.

In the above obtaining unit 30, the above thread pool is a multi-threaded processing form, and tasks are added to the queue during the processing, and then these tasks are automatically started after the threads are created. Thread pool threads are background threads. Each thread uses the default stack size, runs at the default priority, and is in a multithreaded apartment. If a thread is idle in managed code (such as waiting for an event), the thread pool inserts another worker thread to keep all processors busy. If all thread pool threads remain busy all the time, but the queue contains pending work, the thread pool will create another worker thread after a period of time, but the number of threads will never exceed the maximum. Threads that exceed the maximum can be queued, but they will not start until other threads have completed. In this application, a specified number of threads are always maintained in the thread pool. When a thread is idle, the task is obtained from the above cache queue. Because the cache queue is only a task ID, it is adjusted to the application server according to the task ID. Take the corresponding bank-enterprise direct mission. The number of threads in the above thread pool can be configured when the enterprise-side front-end processor is configured, such as 5, 10, 20, etc., which can be configured according to specific needs.

In the above parsing unit 40 and sending unit 50, because the above-mentioned bank-enterprise direct link task is targeted, such as calling the current account of a bank account corresponding to a type A bank, the configuration information will include the corresponding The number of the bank-side front-end machine, the bank server IP corresponding to a type A bank, and so on, all of this information is configured when the enterprise-side front-end machine is installed and sent to the application server corresponding to the enterprise-side front-end machine. Therefore, the above application server will automatically write this information into the bank-enterprise direct connection task according to the request of the enterprise, so that the enterprise-end front-end processor can accurately connect to the corresponding bank-end front-end processor.

In the forwarding unit 60, when the front end of the bank receives the direct bank-enterprise task, it will forward it to the corresponding bank server, and the bank server will retrieve the corresponding data generation result message and send it to the first bank. The machine is set up to return to the enterprise-end front-end machine, and the enterprise-end front-end machine is forwarding to the application server, and the application server finally feeds back the result message to the financial software system of the enterprise.

Referring to FIG. 5, in an embodiment, the cache unit 20 includes:

An obtaining module 21, configured to obtain a task ID of the bank-enterprise direct link task;

A judging module 22, configured to judge attributes of the task ID, where the attributes include transaction attributes and query attributes;

The cache module 23 is configured to place the task ID into a cache queue of a corresponding attribute according to a determination result.

In the acquisition module 21, judgment module 22, and cache module 23 described above, the attribute of the task ID is generally determined by the request issued by the financial system of the enterprise, and may specifically include the transaction attribute and the query attribute. The query attribute is the bank flow of the query enterprise, Account balance, payment status, and other corresponding attributes are requested, while transaction attributes are those corresponding to requests such as payments and transfers. In the front end of the enterprise, a transaction cache queue corresponding to the transaction attribute and a query cache queue corresponding to the query attribute are also provided. A transaction thread pool corresponding to the transaction cache queue and a query thread pool corresponding to the query cache queue are also set. Each task ID in the two cache queues is sorted and processed according to a preset priority, for example, the level of payment is higher than the level of querying the bank flow. Specifically, each task is provided with a type identifier, and the type identifier can be divided into 1-8 levels, and the highest level is 1, which represents emergency tasks and is given priority processing. Various bank-enterprise direct tasks correspond to different type identifiers, and their corresponding task IDs have the same type identifier.

Referring to FIG. 6, in one embodiment, the foregoing financial data interaction device further includes:

A judging unit 101, configured to judge whether a UKey device corresponding to various types of banks is inserted into the enterprise-end front-end processor;

The first alarm unit 102 is configured to alarm if it is determined that UKey devices corresponding to various types of banks are not plugged into the front end of the enterprise.

In the above-mentioned judgment unit 101 and alarm unit 102, the identifiers corresponding to the types of banks of the UKey devices inserted in each UKey interface are collected, and then the identifiers are compared with the identifiers representing various types of banks configured when the enterprise-side front-end processor is configured. Yes, if the collected logos fully cover the logos representing various types of banks configured when the enterprise-end front end is configured, it is determined that UKey devices corresponding to various types of banks are inserted into the enterprise-end front end. Otherwise, it will not be The type of bank corresponding to the covered identifier is extracted and sent to the relevant personnel of the enterprise to report the alarm. At this time, the relevant personnel of the enterprise can take corresponding measures to forget the inserted UKey device or the insertion place is loose, which will cause the UKey device to have poor contact. Plug in, etc. to ensure the interaction between the business and the banks. In another embodiment, it is also possible to determine whether the number of the obtained UKey device identification is the same as the identification number (not duplicate) representing various types of banks configured when the enterprise front end is configured, because a bank will only issue one UKey For enterprises, when the number is the same, it can basically be judged that UKey equipment corresponding to various types of banks is inserted into the front end of the enterprise. Although this judgment method has defects, the judgment speed will be faster.

In one embodiment, the foregoing financial data interaction device further includes:

A heartbeat sending unit, configured to send a heartbeat detection packet to detect a connection status with the application server;

The second alarm unit is configured to issue an alarm message if the connection state is disconnected.

Referring to FIG. 7, in one embodiment, the monitoring unit 10 includes:

The long-connection monitoring module 11 monitors whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task through a long connection.

In the above-mentioned long connection monitoring module 11, because the bank-enterprise direct connection task received by the front end of the enterprise may be continuous, the service is monitored using the long connection method, so that it will not be disconnected after each operation and processed next time. You can send data packets directly without establishing a TCP connection to maintain the efficiency of processing tasks. In this embodiment, the front end of the enterprise side and the application server use the BIO synchronous blocking mode for a long connection. Different bank-enterprise direct tasks cannot be performed at the same time, so they need to be performed in accordance with the order of instructions. One instruction can be executed before the next instruction can be executed. It cannot be executed asynchronously. Therefore, in this application, the front end of the enterprise uses the BIO synchronous blocking mode and the application server Make a long connection.

A serialization unit is used to serialize the packets sent by the foregoing enterprise-end front-end machine and the application server to each other using Protocol Buffers.

Protocol Buffers It is a lightweight and efficient structured data storage format, which can be used for serialization of structured data, or serialization. It is very suitable for data storage or RPC data exchange format. Language-independent, platform-independent, and extensible serialization structure data format that can be used in communication protocols, data storage, etc., simply The main advantages of Protobuf are: simple and fast. This application uses GOOGLE's Protocol Buffers for serialization, which can improve the efficiency of packet encapsulation and transmission.

In the financial data interaction device in the embodiment of the present application, since multiple UKey interfaces are set on the enterprise-end front-end processor and corresponding configurations are performed, the enterprise-end front-end processor can directly connect with banks of different types with different types of banks. Function to ensure the normal use of each bank account. In order to ensure the stable operation and efficiency of the enterprise-side front-end processor, the cache queue and thread pool configuration will be set in the enterprise-side front-end processor to perform various tasks in an orderly manner; further, the cache queue Only the task ID is cached. When it is the task's turn, the specific bank-enterprise direct connection task is retrieved from the application server according to the task ID to save cache space and further improve the operation speed and stable operation of the enterprise front-end processor Sex.

Referring to FIG. 8, an embodiment of the present application further provides a computer device. The computer device may be a server, and its internal structure may be as shown in FIG. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the computer design processor is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer-readable instructions, and a database. The memory provides an environment for operating systems and computer-readable instructions in a non-volatile storage medium. The database of the computer equipment is used to store financial data interaction method programs and the like. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer-readable instructions are executed by a processor to implement a method of financial data interaction.

The processor executes the financial data interaction method, and uses an enterprise-end front-end processor to implement financial-data interaction between the enterprise-end financial system and the bank-side. The enterprise-end front-end processor is provided with multiple UKey interfaces. Corresponding to a plurality of the UKey interfaces are configured to complete financial data interaction with a plurality of bank-end front-end machines of different types of banks, and the steps of the method are: monitoring whether an application server of the enterprise-end front-end machine sends a bank If the task is directly connected to the enterprise, if yes, obtain the task ID of the bank-enterprise directly connected task and put the task ID into the corresponding cache queue; when the thread pool corresponding to the cache queue is obtained from the cache queue At the time of the task, the corresponding bank-enterprise direct link task is obtained from the application server according to the task ID; the bank-enterprise direct link task is analyzed to obtain the bank-side front-end processor corresponding to the bank-enterprise direct link task. Configuration information; sending the bank-enterprise direct connection task to the bank-side front-end processor according to the configuration information; and sending a result message returned by the bank-side front-end processor to the application Service is.

In one embodiment, the step of obtaining the task ID of the bank-enterprise direct link task and putting the task ID into a corresponding cache queue includes: obtaining the task ID of the bank-enterprise direct link task; Determine the attributes of the task ID, where the attributes include transaction attributes and query attributes; and place the task ID in a cache queue of the corresponding attributes according to the determination result.

In one embodiment, before the step of monitoring whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task, the method includes: judging whether or not UKey equipment corresponding to various types of banks is inserted into the enterprise-end front-end processor; If not, an alarm is issued.

In one embodiment, the step of monitoring whether the application server of the enterprise-side front-end processor sends a bank-enterprise direct connection task includes: monitoring whether the application server of the enterprise-side front-end processor sends a bank-enterprise through a long connection. Direct missions.

In one embodiment, the enterprise-end front-end unit and the application server adopt a BIO synchronous blocking mode for a long connection.

In one embodiment, the packets sent by the enterprise-end front-end unit and the application server to each other are serialized using Protocol Buffers.

Those skilled in the art can understand that the structure shown in FIG. 8 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied.

In the computer equipment in the embodiment of the present application, because multiple UKey interfaces are set on the enterprise-end front-end processor and corresponding configurations are performed, the enterprise-end front-end processor can perform bank-enterprise direct connection functions with multiple different types of banks. To ensure the normal use of each bank account. In order to ensure the stable operation and efficiency of the enterprise-side front-end processor, the cache queue and thread pool configuration will be set in the enterprise-side front-end processor to perform various tasks in an orderly manner; further, the cache queue Only the task ID is cached. When it is the task's turn, the specific bank-enterprise direct connection task is retrieved from the application server according to the task ID to save cache space and further improve the operation speed and stable operation of the enterprise front-end processor. Sex.

An embodiment of the present application further provides a computer non-volatile readable storage medium, which stores computer-readable instructions. When the computer-readable instructions are executed by a processor, a method for interacting financial data is implemented. Machine to realize the financial data interaction between the enterprise-side financial system and the bank, wherein the enterprise-end front-end machine is provided with multiple UKey interfaces, and the enterprise-side front-end machine corresponds to the plurality of UKey interfaces and is configured to be able to communicate with multiple Different types of banks' front-end processors complete financial data interaction; the method includes: monitoring whether the application server of the enterprise-end front-end processors sends bank-enterprise direct link tasks; if so, obtaining the bank-enterprise direct link tasks The task ID and put the task ID into the corresponding cache queue; when the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain a corresponding one from the application server according to the task ID The bank-enterprise direct link task; analyzing the bank-enterprise direct link task to obtain configuration information of a bank-side front-end machine corresponding to the bank-enterprise direct link task; according to the configuration The bank information is sent to the task Direct bank FEP end; the end result of the bank FEP returns the packet to the application server.

In the above financial data interaction method, because multiple UKey interfaces are set on the enterprise-end front-end machine and corresponding configurations are performed, the enterprise-side front-end machine can perform direct bank-enterprise functions with multiple different types of banks to ensure Normal use of each bank account. In order to ensure the stable operation and efficiency of the enterprise-side front-end processor, the cache queue and thread pool configuration will be set in the enterprise-side front-end processor to perform various tasks in an orderly manner; further, the cache queue Only the task ID is cached. When it is the task's turn, the specific bank-enterprise direct connection task is retrieved from the application server according to the task ID to save cache space and further improve the operation speed and stable operation of the enterprise front-end processor. Sex.

In one embodiment, the step of the processor acquiring the task ID of the bank-enterprise direct link task and placing the task ID in a corresponding cache queue includes: acquiring the task of the bank-enterprise direct link task. ID; judging the attributes of the task ID, wherein the attributes include transaction attributes and query attributes; and placing the task ID in a cache queue of the corresponding attribute according to the judgment result.

In one embodiment, before the step of the processor monitoring whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task, the method includes: determining whether a UKey corresponding to various types of banks is inserted into the enterprise-end front-end processor. Equipment; if not, alarm.

In one embodiment, the processor further controls the front end of the enterprise to send a heartbeat detection packet to detect the connection status with the application server; if the connection status is disconnected, an alarm message is issued.

In one embodiment, the step of the processor monitoring whether the application server of the enterprise-side front-end processor sends a bank-enterprise direct connection task includes: monitoring whether the application server of the enterprise-side front-end processor sends through a long connection. Bank-enterprise direct link mission.

In one embodiment, the processor controls the enterprise-end front end and the application server to use the BIO synchronous blocking mode for a long connection.

In one embodiment, the processor controls the packets sent by the enterprise front end and the application server to each other, and uses Protocol Buffers for serialization.

A person of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by using computer-readable instructions to instruct related hardware. The computer-readable instructions can be stored in a nonvolatile computer In the readable storage medium, the computer-readable instructions, when executed, may include the processes of the embodiments of the methods described above. Wherein, any reference to the storage, storage, database, or other media provided in this application and used in the embodiments may include non-volatile and / or volatile storage. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual-speed data rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

The above is only a preferred embodiment of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the description of the application and the drawings, or directly or indirectly used in other related The technical fields are equally included in the patent protection scope of this application.

Claims

A financial data interaction method is characterized in that an enterprise-side front-end machine is used to implement financial data interaction between an enterprise-side financial system and a bank-side. The enterprise-side front-end machine is provided with multiple UKey interfaces. The device corresponding to multiple UKey interfaces is configured to complete financial data interaction with multiple front-end banks of different types of banks; the method includes:

Monitoring whether the application server of the front end of the enterprise sends a bank-enterprise direct connection task;

If yes, obtain the task ID of the bank-enterprise direct link task, and place the task ID in the corresponding cache queue;

When the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain the corresponding bank-enterprise direct task from the application server according to the task ID;

Analyze the bank-enterprise direct link task to obtain configuration information of the bank-side front-end processor corresponding to the bank-enterprise direct link task;

Sending the bank-enterprise direct connection task to the bank-end front-end processor according to the configuration information;

And sending a result message returned by the bank-side front end to the application server.
The method for interactive financial data according to claim 1, wherein the step of obtaining a task ID of the bank-enterprise direct link task and placing the task ID in a corresponding cache queue comprises:

Obtaining a task ID of the bank-enterprise direct task;

Determining the attributes of the task ID, where the attributes include transaction attributes and query attributes;

The task ID is put into a cache queue of a corresponding attribute according to a determination result.
The method for interactive financial data according to claim 1, wherein before the step of monitoring whether an application server of the enterprise front-end processor sends a bank-enterprise direct connection task, comprises:

Determining whether UKey equipment corresponding to various types of banks is inserted into the front-end of the enterprise end;

If not, an alarm is issued.
The method according to claim 1, wherein the method further comprises:

Sending a heartbeat detection packet to detect a connection status with the application server;

If the connection status is disconnected, an alarm message is issued.
The method for interactive financial data according to claim 4, wherein the step of monitoring whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task comprises:

Whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task through a long connection.
The method for interactive financial data according to claim 5, wherein the front end of the enterprise side and the application server adopt a BIO synchronous blocking mode for a long connection.
The method for interactive financial data according to claim 1, wherein the messages sent by the enterprise-end front end and the application server are serialized using Protocol Buffers.
A financial data interaction device, characterized in that an enterprise-end front-end machine is used to implement financial data interaction between an enterprise-end financial system and a bank-side, wherein the enterprise-end front-end machine is provided with multiple UKey interfaces, and the enterprise-end front-end machine The set-up corresponds to a plurality of the UKey interfaces configured to complete financial data interaction with a plurality of bank-end front-end machines of different types of banks; the device includes:

A monitoring unit, configured to monitor whether an application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task;

A cache unit, configured to: if the monitoring unit monitors the bank-enterprise direct link task sent by the application server, obtain a task ID of the bank-enterprise direct link task, and place the task ID in a corresponding cache queue;

An obtaining unit, configured to, when the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain the corresponding bank-enterprise direct task from the application server according to the task ID;

An analysis unit, configured to analyze the bank-enterprise direct link task to obtain configuration information of a bank-side front-end processor corresponding to the bank-enterprise direct link task;

A sending unit, configured to send the bank-enterprise direct connection task to the bank-end front-end processor according to the configuration information;

The forwarding unit is configured to send a result message returned by the bank-side front end to the application server.
The financial data interaction device according to claim 8, wherein the cache unit comprises:

An acquisition module for acquiring a task ID of the bank-enterprise direct link task;

A judging module, configured to judge attributes of the task ID, wherein the attributes include transaction attributes and query attributes;

The cache module is configured to put the task ID into a cache queue of a corresponding attribute according to a judgment result.
The financial data interaction device according to claim 8, wherein the financial data interaction device further comprises:

A judging unit, configured to judge whether a UKey device corresponding to various types of banks is inserted into the front end of the enterprise;

The first alarm unit is configured to alarm if it is determined that UKey equipment corresponding to various types of banks is not inserted into the front-end of the enterprise side.
The financial data interaction device according to claim 8, wherein the financial data interaction device further comprises:

A heartbeat sending unit, configured to send a heartbeat detection packet to detect a connection status with the application server;

The second alarm unit is configured to issue an alarm message if the connection state is disconnected.
The financial data interaction device according to claim 11, wherein the monitoring unit comprises:

The long-connection monitoring module is configured to monitor whether the application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task through a long connection.
The financial data interaction device according to claim 12, wherein the enterprise-end front-end unit and the application server adopt a BIO synchronous blocking mode for a long connection.
The financial data interaction device according to claim 8, wherein the financial data interaction device further comprises:

A serialization unit is configured to serialize a message sent by the enterprise-end front-end unit and the application server to each other using Protocol Buffers.
A computer device includes a memory and a processor. The memory stores computer-readable instructions, and is characterized in that the processor implements a financial data interaction method when the processor executes the computer-readable instructions. The financial system on the enterprise side interacts with the financial data on the bank side, wherein the front-end unit of the enterprise side is provided with multiple UKey interfaces, and the front-end unit of the enterprise side is configured to be able to communicate with multiple different banks. Different types of bank-end front-end machines complete financial data interaction; the method includes:

Monitoring whether the application server of the front end of the enterprise sends a bank-enterprise direct connection task;

If yes, obtain the task ID of the bank-enterprise direct link task, and place the task ID in the corresponding cache queue;

When the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain the corresponding bank-enterprise direct task from the application server according to the task ID;

Analyze the bank-enterprise direct link task to obtain configuration information of the bank-side front-end processor corresponding to the bank-enterprise direct link task;

Sending the bank-enterprise direct connection task to the bank-end front-end processor according to the configuration information;

And sending a result message returned by the bank-side front end to the application server.
The computer device according to claim 15, wherein the step of obtaining a task ID of the bank-enterprise direct link task and placing the task ID in a corresponding cache queue comprises:

Obtaining a task ID of the bank-enterprise direct task;

Determining the attributes of the task ID, where the attributes include transaction attributes and query attributes;

The task ID is put into a cache queue of a corresponding attribute according to a determination result.
The computer device according to claim 15, wherein before the step of monitoring whether an application server of the enterprise-end front-end processor sends a bank-enterprise direct connection task, comprises:

Determining whether UKey equipment corresponding to various types of banks is inserted into the front-end of the enterprise end;

If not, an alarm is issued.
The method according to claim 15, wherein the method further comprises:

Sending a heartbeat detection packet to detect a connection status with the application server;

If the connection status is disconnected, an alarm message is issued.
A computer non-volatile readable storage medium storing computer-readable instructions thereon, characterized in that when the computer-readable instructions are executed by a processor, a financial data interaction method is implemented, and an enterprise-side front-end processor is used to implement an enterprise Financial system interacts with the financial data of the bank, wherein the front end of the enterprise side is provided with multiple UKey interfaces, and the front end of the enterprise side corresponds to the plurality of UKey interfaces and is configured to be able to interact with multiple different bank types Bank-end front-end machine completes financial data interaction; the method includes:

Monitoring whether the application server of the front end of the enterprise sends a bank-enterprise direct connection task;

If yes, obtain the task ID of the bank-enterprise direct link task, and place the task ID in the corresponding cache queue;

When the thread pool corresponding to the cache queue obtains a task from the cache queue, obtain the corresponding bank-enterprise direct task from the application server according to the task ID;

Analyze the bank-enterprise direct link task to obtain configuration information of the bank-side front-end processor corresponding to the bank-enterprise direct link task;

Sending the bank-enterprise direct connection task to the bank-end front-end processor according to the configuration information;

And sending a result message returned by the bank-side front end to the application server.
The computer non-volatile readable storage medium according to claim 19, wherein the acquiring the task ID of the bank-enterprise direct task and putting the task ID into a corresponding cache queue Steps, including:

Obtaining a task ID of the bank-enterprise direct task;

Determining the attributes of the task ID, where the attributes include transaction attributes and query attributes;

The task ID is put into a cache queue of a corresponding attribute according to a determination result.