Reliable Transmission Method and System for Implementing DBF Interface Based on FDEP System

Abstract

An embodiment of the present application provides a reliable transmission method and system for implementing a DBF interface based on an FDEP system. The method includes: the DBF sender sends file attribute information to the DBF receiver; the DBF receiver determines file request information according to the received file attribute information and local file attribute information; when the file request information is preset file request information, the DBF receiver sends a data request to the DBF sender, and the data request includes file description information; the DBF sender sends a first response data packet to the DBF receiver according to the file description information in the data request, and the DBF record data in the first response data packet is the DBF record data determined according to the file description information; after receiving the first response data packet, the DBF receiver stores the DBF record data in the first response data packet and sends the current local file attribute information to the DBF sender, realizing reliable transmission between the DBF sender and the DBF receiver.

Description

Technical Field

[0001] This application relates to the technical field of data transmission, and specifically relates to a reliable transmission method and system for implementing a DBF interface based on an FDEP system. Background Art

[0002] The Financial Data Exchange Platform (FDEP) includes a message transmission system and a file transmission system. Among them, the message transmission system is used for data exchange of message packets between various financial institution systems.

[0003] Among them, the FDEP message transmission system does not guarantee the reliable transmission of data packets. Packet loss may occur during the transmission process. In extreme cases (such as when some modules are disconnected and then reconnected to other modules), packet disorder may even occur. Since the FDEP message transmission system itself does not support reliable transmission, and in practical applications, a reliable transmission function based on the FDEP message transmission system and the DBF file as an interface is often required. To support reliable transmission, usually, people generally use the request-response mode for communication. This method has problems such as complex processes, easy generation of errors and chaos. Especially when there is packet loss during the communication process, it is not easy to recover after an error, often resulting in inexplicable consequences, and the transmission efficiency is low. Summary of the Invention

[0004] The embodiments of this application provide a reliable transmission method and system for implementing a DBF interface based on an FDEP system, which can obtain corresponding data by the way that the DBF receiving end actively sends a data request to the DBF sending end, thereby realizing reliable transmission when the DBF sending end and the DBF receiving end perform data transmission. Its advantages are that requests can be repeatedly initiated in any state, and the transmission process can be continued in any state without worrying about any negative effects such as errors or chaos, which well adapts to the characteristic that the FDEP message transmission itself does not support reliable transmission, and has high efficiency.

[0005] The first aspect of the embodiments of this application provides a reliable transmission method for implementing a DBF interface based on an FDEP system. The method is applied to a reliable transmission system for implementing a DBF interface based on an FDEP system. The reliable transmission system for implementing a DBF interface based on an FDEP system includes a DBF sending end, a Financial Data Exchange Platform FDEP, and a DBF receiving end. The method includes:

[0006] The DBF sending end sends file attribute information to the DBF receiving end through the FDEP;

[0007] The DBF receiving end determines file request information according to the received file attribute information and local file attribute information;

[0008] When the file request information is preset file request information, the DBF receiving end sends a data request to the DBF sending end through the FDEP, where the data request includes file description information and a maximum buffer area of ​​T lines;

[0009] The DBF sending end sends a first response data packet to the DBF receiving end through the FDEP according to the file description information in the data request, wherein the DBF record data in the first response data packet is the DBF record data determined according to the file description information;

[0010] After receiving the first response data packet, the DBF receiving end stores the DBF record data in the first response data packet;

[0011] The DBF sending end continues to send a second response data packet to the DBF receiving end through the FDEP according to the file description information in the data request and the first response packet data;

[0012] In M <N+T的条件下,DBF发送端继续重复以上发送数据包的过程;否则暂停发送,并检测N、M和T的值,当再次满足该条件时继续重复以上发送数据包的过程;M为DBF发送端已发送的最大行数,N为从DBF发送端看来,DBF接收端已成功接收记录数,T为常数,指最大缓冲区。

[0013] In a possible implementation, in order to prevent the transmission process from being interrupted due to packet loss, the DBF receiving end periodically sends a data request to the DBF sending end through the FDEP, wherein the data request includes file description information and a maximum buffer of T lines;

[0014] After the DBF receiving end receives the DBF record data, if the DBF data is the expected record data, it writes it into the DBF file; otherwise, the DBF receiving end sends a data request to the DBF sending end through the FDEP, and temporarily stores the data in the memory at the same time, and the temporarily stored data can temporarily store S data packets at most; after receiving the corresponding file position data, if there is data temporarily stored in the memory, it is determined whether the data is the required data, if so, it is used directly, otherwise it continues to wait for receiving data or initiates a new request; or, the data is not temporarily stored, the data is discarded, and a data request is re-initiated at the current line number, where S is a constant.

[0015] In a possible implementation, the file description information includes: a starting record row number of the DBF record data and a maximum number of records of the DBF record data transmitted in a single time.

[0016] The second aspect of the embodiments of the present application provides a reliable transmission system for implementing a DBF interface based on an FDEP system. The reliable transmission system for implementing a DBF interface based on an FDEP system includes a DBF sender, a financial data exchange platform FDEP, and a DBF receiver. Among them,

[0017] The DBF sender is configured to send file attribute information to the DBF receiver through the FDEP.

[0018] The DBF receiver is configured to determine file request information according to the received file attribute information and local file attribute information.

[0019] When the file request information is preset file request information, the DBF receiver is configured to send a data request to the DBF sender through the FDEP. The data request includes file description information and a maximum buffer of T rows.

[0020] The DBF sender is configured to send a first response data packet to the DBF receiver through the FDEP according to the file description information in the data request. The DBF record data in the first response data packet is the DBF record data determined according to the file description information.

[0021] The DBF receiver is configured to store the DBF record data in the first response data packet after receiving the first response data packet.

[0022] The DBF sender is configured to continue to send a second response data packet to the DBF receiver through the FDEP according to the file description information in the data request and the first response packet data.

[0023] Under the condition of M < N + T, the DBF sender is configured to continue to repeat the above process of sending data packets; otherwise, pause sending and detect the values of N, M, and T. When the condition is met again, continue to repeat the above process of sending data packets. M is the maximum number of rows sent by the DBF sender, N is the number of successfully received records from the perspective of the DBF sender at the DBF receiver, and T is a constant, referring to the maximum buffer.

[0024] In a possible implementation, to prevent packet loss from causing an interruption in the transmission process, the DBF receiver is configured to periodically send a data request to the DBF sender through the FDEP. The data request includes file description information and a maximum buffer of T rows.

[0025] The DBF receiving end is used to write the DBF record data into the DBF file if the received DBF data is the expected record data. Otherwise, the DBF receiving end sends a data request to the DBF sending end through the FDEP, and temporarily stores the data in the memory. The temporarily stored data can store at most S data packets. When the corresponding file position data is received, if there is data temporarily stored in the memory, it is determined whether the data is the required data. If so, it is directly used; otherwise, continue to wait for receiving data or initiate a new request. Alternatively, the data is not temporarily stored, discarded, and a data request is initiated again at the current line number, where S is a constant.

[0026] In a possible implementation manner, the file description information includes: the starting record line number of the DBF record data and the maximum number of record data transmitted each time.

[0027] A third aspect of the embodiments of the present application provides a server, including a processor, an input device, an output device, and a memory. The processor, the input device, the output device, and the memory are interconnected. Among them, the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the step instructions executed by the DBF receiving end or the DBF sending end in the first aspect of the embodiments of the present application.

[0028] A fourth aspect of the embodiments of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program for electronic data exchange. The computer program enables a computer to execute some or all of the steps executed by the DBF receiving end or the DBF sending end in the first aspect of the embodiments of the present application.

[0029] A fifth aspect of the embodiments of the present application provides a computer program product. The computer program product includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to enable a computer to execute some or all of the steps executed by the DBF receiving end or the DBF sending end in the first aspect of the embodiments of the present application. The computer program product can be a software installation package.

[0030] Implementing the embodiments of the present application has at least the following beneficial effects:

[0031] The DBF sending end sends file attribute information to the DBF receiving end.

[0032] The DBF receiver determines file request information based on the received file attribute information and local file attribute information. When the file request information is preset file request information, the DBF receiver sends a data request to the DBF sender. The data request includes file description information. The DBF sender sends a first response data packet to the DBF receiver according to the file description information in the data request. The DBF record data in the first response data packet is the DBF record data determined according to the file description information. After receiving the first response data packet, the DBF receiver stores the DBF record data in the first response data packet and sends the current local file attribute information to the DBF sender. Therefore, it is possible to obtain corresponding data by the method of the DBF receiver actively sending a data request to the DBF sender, thus realizing reliable data transmission between the DBF sender and the DBF receiver. And requests can be repeated in any state, and the transmission process can be continued in any state without worrying about any negative effects such as errors or chaos, which well adapts to the characteristic that the FDEP message transmission itself does not support reliable transmission and has high transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0034] Figure 1A FIG. [ID] is a schematic diagram of a reliable transmission system for implementing a DBF interface based on an FDEP system provided by an embodiment of the present application;

[0035] Figure 1B FIG. [ID] is a schematic diagram of DBF record data in a DBF file format provided by an embodiment of the present application;

[0036] Figure 2 FIG. [ID] is a schematic flowchart of a reliable transmission method for implementing a DBF interface based on an FDEP system provided by an embodiment of the present application;

[0037] Figure 3 FIG. [ID] is a schematic structural diagram of a server provided by an embodiment of the present application;

[0038] Figure 4 FIG. [ID] is a schematic diagram of a reliable transmission system for implementing a DBF interface based on an FDEP system provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0039] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0040] The terms "first", "second", etc. in the specification and claims of the present application and the above accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products or devices.

[0041] Referring to "embodiment" in the present application means that the specific features, structures or characteristics described in connection with the embodiment may be included in at least one embodiment of the present application. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described in the present application may be combined with other embodiments.

[0042] Please refer to Figure 1A , Figure 1A which is a schematic diagram of a reliable transmission system for implementing a DBF interface based on an FDEP system provided by an embodiment of the present application. As Figure 1AAs shown, the reliable transmission system implementing the DBF interface based on the FDEP system includes a DBF sender, a financial data exchange platform FDEP, and a DBF receiver. Here, the DBF sender is taken as the DBF sender and the DBF receiver is taken as the DBF receiver for illustration. Among them, FDEP is the financial data exchange platform. The response data packets, data requests, etc. between the DBF sender and the DBF receiver are all forwarded through the FDEP and thus sent to the other party. The application programs in the DBF sender and the DBF receiver are connected through the API (Application Programming Interface). The response data packets record data in the DBF as the BDF file format. The BDF (database file) file format is a special file format. As an open file storage format rather than a database management system, DBF still has the advantages of being simple, clear, and easy to reach a consistent understanding. The DBF file format is still widely used as a data interface in today's securities industry. There are usually two ways to use the DBF interface file. One is the refreshing type, which means rewriting the entire file at once, such as market quotes; the second is the appending type, which means continuously appending new records to the file later. A typical application is the entrustment or execution return of stocks. In the embodiment of this application, it refers to the second appending type of usage. It should be particularly noted that although the above systems use the DBF file, they only regard the DBF as an open, easy-to-understand file storage format that is easy for all parties to reach a consistent understanding, and it has nothing to do with the database management system. The DBF in the embodiment of this application is also used as a storage interface format and has nothing to do with the database management system. Changing the DBF to other suffix names will not affect any processing methods, processes, and processing results in this article. Figure 1B Figure 2 shows a schematic diagram of the DBF record data in the DBF file format.

[0043] Please refer to Figure 2 , Figure 2 FIG. 1 is a schematic flowchart of a reliable transmission method implementing the DBF interface based on the FDEP system provided by an embodiment of this application. As Figure 2 shown, this method is applied to the reliable transmission system implementing the DBF interface based on the FDEP system. The reliable transmission system implementing the DBF interface based on the FDEP system includes a DBF sender, a financial data exchange platform FDEP, and a DBF receiver. The DBF sender and the DBF receiver can be servers. The method includes:

[0044] 201. The DBF sender sends file attribute information to the DBF receiver through the FDEP.

[0045] Among them, the file attribute information may include the file header and the total number of records of the DBF record data in the DBF file. The function family for sending messages through FDEP is MrSend. The DBF sender initiates a file task by sending the file attribute information to the DBF receiver.

[0046] 202. The DBF receiver determines file request information according to the received file attribute information and local file attribute information.

[0047] The DBF receiver can determine the line number of the DBF record data according to the total number of records recorded in the file attribute information, so as to determine the file request information. The file request information may be whether to make a file request, which can be specifically understood as whether to send a data request.

[0048] 203. When the file request information is preset file request information, the DBF receiver sends a data request to the DBF sender through the FDEP. The data request includes file description information and the maximum buffer T lines.

[0049] The preset file request information can be set through empirical values or historical data. Specifically, for example, it can be file request information indicating the sending of a data request.

[0050] The file description information may include the starting record line number of the DBF record data and the maximum number of records of the DBF record data transmitted each time.

[0051] 204. The DBF sender sends a first response data packet to the DBF receiver through the FDEP according to the file description information in the data request. The DBF record data in the first response data packet is the DBF record data determined according to the file description information.

[0052] The number of records corresponding to the first response data packet can be determined according to the maximum number of records of the DBF record data transmitted each time. Based on this number of records and the starting record line number in the file description information, the DBF record data to be sent corresponding to the first response data packet is extracted, and packaging processing is performed based on the DBF record data to be sent, so as to obtain the first response data packet.

[0053] 205. After receiving the first response data packet, the DBF receiver stores the DBF record data in the first response data packet.

[0054] After receiving the first response data packet, the information receiving end stores the DBF record data in the first response data packet and sends the current local file attribute information, which may include the latest line number (which can also be understood as the current maximum line number) of the successful writing of the DBF record data in the first response data packet into the DBF file. If part of the message for sending the current local file attribute information is lost, the loss can also be ignored. Each time the DBF sending end receives this report, it can consider that the records of all lines before this report have been successfully uploaded (increasing only), and the benchmark is moved backward, so that new file data can be sent continuously.

[0055] Of course, when there are multiple first response data packets, after receiving the first response data packet, the DBF receiving end can decide when to stop receiving this data packet, and at this time, it can send a corresponding request to stop receiving to the DBF sending end, so as to achieve flexible acquisition of DBF record data.

[0056] 206. The DBF sending end continues to send a second response data packet to the DBF receiving end through the FDEP according to the file description information and the first response packet data in the data request;

[0057] 207. Under the condition of M < N + T, the DBF sending end continues to repeat the above process of sending data packets; otherwise, it pauses sending and detects the values of N, M, and T, and continues to repeat the above process of sending data packets when the condition is met again; M is the maximum number of lines sent by the DBF sending end, N is the number of records successfully received by the DBF receiving end from the perspective of the DBF sending end, and T is a constant, referring to the maximum buffer.

[0058] In this example, the DBF receiver determines file request information based on the received file attribute information and local file attribute information. When the file request information is preset file request information, the DBF receiver sends a data request to the DBF sender. The data request includes file description information. The DBF sender sends a first response data packet to the DBF receiver according to the file description information in the data request. The DBF record data in the first response data packet is the DBF record data determined according to the file description information. After receiving the first response data packet, the DBF receiver stores the DBF record data in the first response data packet and sends the current local file attribute information to the DBF sender. Therefore, it is possible to obtain corresponding data by the method of the DBF receiver actively sending a data request to the DBF sender, thus realizing reliable data transmission between the DBF sender and the DBF receiver. And requests can be repeatedly initiated in any state, and the transmission process can be continued in any state without worrying about any negative effects such as errors or chaos, which well adapts to the characteristic that the FDEP message transmission itself does not support reliable transmission and has high efficiency.

[0059] In a possible implementation manner, the file description information includes: the starting record line number of the DBF record data and the maximum number of record data of the DBF record data transmitted each time.

[0060] In a possible implementation manner, to prevent the interruption of the transmission process caused by packet loss, the DBF receiver regularly sends a data request to the DBF sender through the FDEP. The data request includes file description information and the maximum buffer T rows;

[0061] After the DBF receiver receives the DBF record data, if the DBF data is the expected record data, it is written into the DBF file. Otherwise, the DBF receiver sends a data request to the DBF sender through the FDEP and temporarily stores the data in the memory. The temporarily stored data is stored in at most S data packets; when the corresponding file position data is received, if there is data temporarily stored in the memory, it is determined whether the data is the required data. If so, it is directly used. Otherwise, continue to wait for the received data or initiate a new request; or, do not temporarily store the data, discard the data, and re-initiate a data request at the current line number, where S is a constant.

[0062] In a possible implementation manner, the file description information includes: the starting record line number of the DBF record data and the maximum number of record data of the DBF record data transmitted each time.

[0063] In a possible implementation, a possible DBF sender sends a first response data packet to the DBF receiver through FDEP according to the file description information in the data request, including:

[0064] A1. The DBF sender obtains the starting record line number of the DBF record data in the file description information and the maximum number of DBF record data for a single transmission;

[0065] A2. The DBF sender obtains the sending status information of the DBF sender;

[0066] A3. The DBF sender determines the number of records corresponding to the first response data packet according to the sending status information and the maximum number of DBF record data for a single transmission;

[0067] A4. The DBF sender determines the DBF record data to be sent according to the starting record line number of the DBF record data and the number of records corresponding to the first response data packet;

[0068] A5. The DBF sender determines the file header of the first response data packet;

[0069] A6. The DBF sender performs encapsulation processing at least according to the file header and the DBF record data to be sent to obtain the first response data packet;

[0070] A7. The DBF sender sends the first response data packet to the DBF receiver through FDEP.

[0071] The file extraction can be performed according to the starting record line number according to the number of records corresponding to the first response data packet to obtain the DBF record data to be sent. The file header of the first response data packet may include from which line the DBF record data of this transmission starts, how many lines in total, and the maximum number of lines of data available at the DBF sender.

[0072] The DBF sender sending the first response data packet to the DBF receiver can be understood as: the DBF sender forwards the first response data packet to the DBF receiver through FDEP.

[0073] In this example, by determining the sending status information of the DBF sender in the file description information, the maximum number of DBF record data for a single transmission, the number of records corresponding to the determined first response data packet, and the starting record line number of the DBF record data, the DBF record data to be sent is extracted and encapsulated into the first response data packet for sending, realizing reliable transmission when sending the first response data packet.

[0074] In a possible implementation, when the DBF record data in the response data packet received by the DBF receiver is different from the requested DBF record data, the following method can also be executed:

[0075] B1. If the DBF record data in the second response data packet received by the DBF receiver is different from the DBF record data determined by the file description information in the data request, cache the DBF record data in the second response data packet;

[0076] B2. The DBF receiver determines whether there is a file location corresponding to the DBF record data to be cached in the second response data packet. If so, store the DBF record data in the second response data packet at the file location.

[0077] Among them, a specific example can be: for the DBF receiver, there is a window for receiving data with a maximum not exceeding S. That is to say, if it is the data at the current required position, it is directly saved to the file. However, if it is not the file data at the current position, it means that packet loss or out-of-order may have occurred. Then, it is temporarily stored in the memory, but at most S packets are temporarily stored. When the corresponding file location data is received, if there is data temporarily stored in the memory, check whether it is the required data. If so, use it directly; otherwise, continue to wait for the received data or initiate a new request. For the receiver, if it is not the data required at the current file location, the data can also be not temporarily stored and directly discarded, and a data request is initiated again at the current line number.

[0078] If the DBF receiver believes that the packet at a certain position has been lost, it can re-initiate a request for the data at that position without worrying about any negative effects.

[0079] In a specific embodiment, a specific reliable transmission method for implementing the DBF interface based on the FDEP system is provided. The method includes:

[0080] Step 1. The DBF sender initiates a file task. The DBF sender reads the local DBF file header and sends the file header and the total number of record data in the local DBF file to the peer. The function family for sending messages through FDEP is MrSend.

[0081] Step 2. The DBF receiver receives the file header and the total number of records, generates or writes to the local file, and gives a response. The function family for receiving messages through FDEP is MrReceive.

[0082] Step 3. If the DBF receiver detects that the line number of the other party is larger than its own, the DBF receiver actively sends a data request to the other party. When recording data in the request, it is not initiated actively by the sender, but by the receiver, which can ensure the reliability and repeatability of the task. If the other party does not receive it, it can be initiated multiple times without worrying about any negative effects.

[0083] The main parameters for initiating the request are: the starting record line number of the request, that is, the confirmed received line number + 1, and the maximum number of records transmitted at one time (determined as a fixed parameter according to the size that can be transmitted by a single FDEP packet).

[0084] If the total number of records of the DBF sender is the same as that of the receiver, it can be not sent, and wait until the numbers at both ends are found to be inconsistent before sending.

[0085] Step 4. After receiving the record request, the DBF sender does not give only one response, but continuously fetches subsequent records from the DBF file and sends them to the other party. The number of records sent in each packet is fixed (except when the end of the file has been reached), but does not exceed N lines at most. Here, N is based on the receiving position reported by the DBF receiver (the position refers to the line number of the DBF, the same below) (dividing the number by the length of a single transmission).

[0086] The main parameters for each data transmission are: the record data transmitted this time, starting from which line, how many lines in total, and the maximum number of lines the sender currently has.

[0087] Step 5. Every time the DBF receiver receives a response data packet, it reports to the DBF sender the latest line number that has been successfully written into the DBF file. If part of the report packet is lost, it can be ignored. Every time the sender receives this report, it can consider that all the records of the lines before this report have been successfully uploaded (only increasing and not decreasing), and this benchmark is moved backward.

[0088] For the DBF receiver, there is a window with a maximum of S for receiving data. If it is the data at the current required position, it is directly saved to the file. However, if it is not the data at the current file position, it means that there may be packet loss or out-of-order. Then, it is temporarily stored in memory, but at most S packets are temporarily stored. When the data at the corresponding file position is received, if there is data temporarily stored in memory, it checks whether the data is the required data. If so, it is directly used; otherwise, it continues to wait for the received data or initiates a new request. For the receiver, if it is not the data required at the current file position, it can also not temporarily store the data, directly discard it, and initiate a data request again at the current line number.

[0089] If the DBF receiver believes that a packet at a certain position has been lost, it can re-initiate a request for the data at that position.

[0090] It may also include the following methods:

[0091] Specifically, it can be three timed operations:

[0092] a) To prevent any form of interruption during data transmission, if the DBF receiver does not receive data from the DBF sender within a certain time (such as 3 seconds, which can be checked by a timer), it is considered that the transmission times out, and a file data request can be initiated again at the current position. After receiving this request, the sender must start giving a series of responses from this position again, reset the current reference position to the data position of the new request, and repeat the above process.

[0093] b) To prevent the loss of a large number or all of the file position progress report packets, the DBF receiver needs to regularly send a report packet of the current position to the other party.

[0094] c) At the DBF sender, when it detects that a new record is appended, it should immediately report its current maximum row number to the other party.

[0095] For the sending or reporting of the above information, it is not necessary to send a separate data packet each time. Instead, these information can be carried along when transmitting other data packets to reduce the number of data packet transmissions and improve efficiency. Moreover, repeatedly carrying these information multiple times can bring about an improvement in efficiency without any disadvantages.

[0096] In the embodiments of this application, when data interaction and communication occur between the DBF sender and the DBF receiver, data forwarding is performed through FDEP to achieve data interaction, communication, etc.

[0097] Consistent with the above embodiments, please refer to Figure 3 , Figure 3 which is a schematic structural diagram of a terminal provided by the embodiments of this application. As shown in the figure, it includes a processor, an input device, an output device, and a memory. The processor, input device, output device, and memory are interconnected. Among them, the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions. The above program includes methods for executing the operations performed by the DBF sender or the DBF receiver in the foregoing embodiments.

[0098] The above mainly introduces the solution of the embodiment of the present application from the perspective of the execution process on the method side. It can be understood that in order for the terminal to implement the above functions, it includes the corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments provided in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0099] The embodiments of the present application can divide the functions of the terminal according to the above method examples. For example, each functional unit can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation.

[0100] Consistent with the above, please refer to Figure 4 , Figure 4 which is a schematic diagram of a reliable transmission system for implementing the DBF interface based on the FDEP system provided by the embodiments of the present application. As Figure 4 shown, the reliable transmission system for implementing the DBF interface based on the FDEP system includes a DBF sending end, a financial data exchange platform FDEP, and a DBF receiving end, where

[0101] the DBF sending end is used to send file attribute information to the DBF receiving end through the FDEP;

[0102] the DBF receiving end is used to determine file request information according to the received file attribute information and local file attribute information;

[0103] when the file request information is preset file request information, the DBF receiving end is used to send a data request to the DBF sending end through the FDEP, and the data request includes file description information and the maximum buffer T rows;

[0104] the DBF sending end is used to send a first response data packet to the DBF receiving end through the FDEP according to the file description information in the data request, and the DBF record data in the first response data packet is the DBF record data determined according to the file description information;

[0105] The DBF receiver is used to store the DBF record data in the first response data packet after receiving the first response data packet;

[0106] The DBF sender is used to continue to send a second response data packet to the DBF receiver through the FDEP according to the file description information and the first response packet data in the data request;

[0107] Under the condition of M < N + T, the DBF sender is used to continue to repeat the above process of sending data packets; otherwise, pause sending, and detect the values of N, M, and T, and continue to repeat the above process of sending data packets when the condition is met again; M is the maximum number of lines sent by the DBF sender, N is the number of records successfully received by the DBF receiver from the perspective of the DBF sender, and T is a constant, referring to the maximum buffer.

[0108] In a possible implementation manner, to prevent packet loss from causing an interruption in the transmission process, the DBF receiver is used to periodically send a data request to the DBF sender through the FDEP, and the data request includes file description information and the maximum buffer of T lines;

[0109] The DBF receiver is used to, after receiving the DBF record data, if the DBF data is the expected record data, write it into the DBF file; otherwise, the DBF receiver sends a data request to the DBF sender through the FDEP, and temporarily stores the data in the memory at the same time. The temporarily stored data can store at most S data packets; when the corresponding file position data is received, if there is data temporarily stored in the memory, determine whether the data is the required data. If so, directly use it; otherwise, continue to wait for receiving data or initiate a new request; or, do not temporarily store the data, discard the data, and re-initiate a data request at the current line number, where S is a constant.

[0110] In a possible implementation manner, the file description information includes: the starting record line number of the DBF record data and the maximum number of records of the DBF record data transmitted each time.

[0111] The embodiment of the present application also provides a computer storage medium. The computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any one of the reliable transmission methods for implementing a DBF interface based on the FDEP system as described in the above method embodiments.

[0112] The embodiment of the present application also provides a computer program product. The computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program enables a computer to execute part or all of the steps of any one of the reliable transmission methods for implementing a DBF interface based on the FDEP system as described in the above method embodiments.

[0113] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0114] In the above embodiments, the descriptions of the respective embodiments have their own focuses. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0115] In the several embodiments provided by this application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical or other forms.

[0116] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0117] In addition, the functional units in the respective embodiments of the application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software program modules.

[0118] When the integrated unit is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as USB flash drives, read-only memories (ROM), random access memories (RAM), mobile hard disks, magnetic disks, or optical discs.

[0119] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing relevant hardware through a program. This program can be stored in a computer-readable memory, and the memory can include: flash drives, read-only memories, random access memories, magnetic disks, or optical discs, etc.

[0120] The above has introduced the embodiments of the present application in detail. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.

Claims

1. A reliable transmission method for implementing a DBF interface based on the FDEP system, characterized in that, The method is applied to a reliable transmission system for implementing a DBF interface based on an FDEP system, wherein the reliable transmission system for implementing a DBF interface based on an FDEP system includes a DBF sending end, a financial data exchange platform FDEP, and a DBF receiving end, and the method includes: The DBF sending end sends file attribute information to the DBF receiving end through the FDEP; The DBF receiving end determines the file request information according to the received file attribute information and the local file attribute information; When the file request information is preset file request information, the DBF receiving end sends a data request to the DBF sending end through the FDEP, where the data request includes file description information and a maximum buffer area of ​​T lines; The DBF sending end sends a first response data packet to the DBF receiving end through the FDEP according to the file description information in the data request, wherein the DBF record data in the first response data packet is the DBF record data determined according to the file description information; After receiving the first response data packet, the DBF receiving end stores the DBF record data in the first response data packet; The DBF sending end continues to send a second response data packet to the DBF receiving end through the FDEP according to the file description information in the data request and the first response packet data; In M <N+T的条件下,DBF发送端继续重复以上发送数据包的过程;否则暂停发送,并检测N、M和T的值,当再次满足该条件时继续重复以上发送数据包的过程;M为DBF发送端已发送的最大行数,N为从DBF发送端看来,DBF接收端已成功接收记录数,T为常数,指最大缓冲区。 2. The method according to claim 1, wherein To prevent the transmission process from being interrupted due to packet loss, the DBF receiving end periodically sends a data request to the DBF sending end through the FDEP, wherein the data request includes file description information and a maximum buffer of T lines; After receiving the DBF record data, if the DBF data is the expected record data, the DBF receiving end writes it into the DBF file; otherwise, the DBF receiving end sends a data request to the DBF sending end through the FDEP, and temporarily stores the data in the memory at most. After receiving the corresponding file position data, if there is data temporarily stored in the memory, determine whether the corresponding file position data is the required data. If so, use it directly, otherwise continue to wait for receiving data or initiate a new request; or, do not temporarily store the data, discard the data, and re-initiate a data request at the current line number, where S is a constant.

3. The method according to claim 1, characterized in that, The file description information includes: the starting record row number of the DBF record data and the maximum number of records of the DBF record data transmitted in a single time.

4. A reliable transmission system for implementing a DBF interface based on an FDEP system, characterized in that, The reliable transmission system for implementing the DBF interface based on the FDEP system includes a DBF sending end, a financial data exchange platform FDEP and a DBF receiving end, wherein: The DBF sending end is used to send file attribute information to the DBF receiving end through the FDEP; The DBF receiving end is used to determine file request information according to the received file attribute information and local file attribute information; When the file request information is preset file request information, the DBF receiving end is used to send a data request to the DBF sending end through the FDEP, and the data request includes file description information and the maximum buffer T rows; The DBF sending end is used to send a first response data packet to the DBF receiving end through the FDEP according to the file description information in the data request, and the DBF record data in the first response data packet is the DBF record data determined according to the file description information; The DBF receiving end is used to store the DBF record data in the first response data packet after receiving the first response data packet; The DBF sending end is used to continue to send a second response data packet to the DBF receiving end through the FDEP according to the file description information in the data request and the first response packet data; Under the condition of M < N + T, the DBF sending end is used to continue to repeat the above process of sending data packets; otherwise, pause sending and detect the values of N, M, and T, and continue to repeat the above process of sending data packets when the condition is met again; M is the maximum number of rows sent by the DBF sending end, N is the number of records successfully received by the DBF receiving end from the perspective of the DBF sending end, and T is a constant, referring to the maximum buffer.

5. The system according to claim 4, wherein To prevent packet loss from causing an interruption in the transmission process, the DBF receiving end is used to periodically send a data request to the DBF sending end through the FDEP, and the data request includes file description information and the maximum buffer T rows; After receiving the DBF record data, the DBF receiving end is used to write the DBF record data into the DBF file if the DBF data is the expected record data; otherwise, the DBF receiving end sends a data request to the DBF sending end through the FDEP and temporarily stores the data in the memory. The temporarily stored data can be stored in at most S data packets; when the corresponding file position data is received, if there is temporarily stored data in the memory, it is determined whether the corresponding file position data is the required data. If so, it is directly used; otherwise, continue to wait for the received data or initiate a new request; or, do not temporarily store the data, discard the data, and re-initiate a data request at the current line number, where S is a constant.

6. The system according to claim 4, characterized in that, The file description information includes: the starting record line number of the DBF record data and the maximum number of records of the DBF record data transmitted each time.

7. A server, characterized in that, It includes a processor, an input device, an output device, and a memory. The processor, input device, output device, and memory are interconnected. Among them, the memory is used to store a computer program, and the computer program includes program instructions. The processor is configured to call the program instructions to execute the method performed by the DBF receiving end or the DBF sending end in any one of claims 1-3.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to execute the method performed by the DBF receiver or the DBF transmitter in any one of claims 1-3.

Images