Synchronous processing method, device, equipment and storage medium for upstream and downstream business processes

Abstract

The present invention discloses a synchronous processing method, device, equipment and storage medium for upstream and downstream business processes. It relates to the field of cloud computing technology. The method comprises: generating and storing record messages at the start and end execution points of each sub-process in the processing flow of the upstream business respectively; the downstream business system sends a first record acquisition request to the upstream business system; when the upstream business system receives the first record acquisition request sent by the downstream business system, it acquires the stored record message based on the request and returns the record message to the downstream business system; the downstream business system receives and stores the record message returned by the upstream business system; when the downstream business system receives the input business number, it reads the record message corresponding to the number from the stored record message, and starts to execute the processing flow of the downstream business based on the read record message. The present invention can synchronize the business processes of the upstream business system and the downstream business system, and speed up the progress of the business processing flow.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of cloud computing technology, and in particular to a method, device, equipment and storage medium for synchronous processing of upstream and downstream business processes. Background Art

[0002] In the technical architecture systems of many financial institutions, component-based architecture design principles are mostly adopted. A single component is responsible for handling matters in a certain field, and complex functions are completed by different components in collaboration.

[0003] For example, in the field of corporate banking, the corporate credit process management system (CLPM) and the international settlement system (ISS) are two important components. For international settlement business involving the sending of SWIFT messages by banks, such as import certificates, international letters of guarantee, and interbank payment, etc., they must first go through the credit approval process in CLPM. After the process is approved, they must go to ISS for approval and send messages to complete the business. The traditional interaction between CLPM and ISS components is linear and sequential, but because the internal approval processes of CLPM and ISS are relatively long, the business processing time is lengthy and inefficient. Summary of the invention

[0004] The embodiment of the present invention provides a method for synchronously processing upstream and downstream business processes, which can enable the approval processes of the upstream business system and the downstream business system to proceed synchronously, thereby speeding up the progress of the business processing process.

[0005] In a first aspect, an embodiment of the present invention provides a method for synchronously processing upstream and downstream business processes, including:

[0006] Generate and store record messages at the start and end execution points of each sub-process in the processing flow of the upstream business, respectively; wherein each record message includes the business identifier of the upstream business, the process identifier of the corresponding sub-process, and business information;

[0007] When a first record acquisition request sent by a downstream business system is received, at least one stored record message is acquired based on the first record acquisition request, and the acquired record message is returned to the downstream business system, so that the downstream business system starts executing the processing flow of the downstream business based on the received record message.

[0008] In a second aspect, an embodiment of the present invention further provides a method for synchronously processing upstream and downstream business processes, including:

[0009] Periodically sending a first record acquisition request to an upstream business system, so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message includes a business identifier of the upstream business, a process identifier of the corresponding sub-process, and business information;

[0010] Receive the record message returned by the upstream business system and store the received record message;

[0011] When the input service number is received, each record message corresponding to the input service number is read from the stored record messages, and the processing flow of the downstream service is started to be executed based on the read record messages.

[0012] In a third aspect, an embodiment of the present invention further provides a system for synchronously processing upstream and downstream business processes, the system comprising:

[0013] The upstream business system is used to generate and store record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively; wherein each record message contains the business identifier of the upstream business, the process identifier of the corresponding sub-process and business information; upon receiving the first record acquisition request sent by the downstream business system, acquire at least one stored record message based on the first record acquisition request, and return the acquired record message to the downstream business system;

[0014] The downstream business system is used to periodically send a first record acquisition request to the upstream business system; receive the record message returned by the upstream business system and store the received record message; when receiving the input business number, read the record messages corresponding to the input business number from the stored record messages, and start executing the processing flow of the downstream business based on the read record messages.

[0015] In a fourth aspect, an embodiment of the present invention further provides a device for synchronously processing upstream and downstream business processes, the device comprising:

[0016] An information generation module, used to generate and store record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively; wherein each record message contains the business identifier of the upstream business, the process identifier of the corresponding sub-process and the business information;

[0017] The information sending module is used to obtain at least one stored record message based on the first record acquisition request when receiving the first record acquisition request sent by the downstream business system, and return the acquired record message to the downstream business system, so that the downstream business system starts to execute the processing flow of the downstream business based on the received record message.

[0018] In a fifth aspect, an embodiment of the present invention further provides a device for synchronously processing upstream and downstream business processes, the device comprising:

[0019] An information request module is used to periodically send a first record acquisition request to an upstream business system, so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message contains a business identifier of the upstream business, a process identifier of the corresponding sub-process, and business information;

[0020] An information storage module is used to receive the record message returned by the upstream business system and store the received record message;

[0021] The business processing module is used to read each record message corresponding to the input business number from the stored record messages when receiving the input business number, and start executing the processing flow of the downstream business based on the read record messages.

[0022] In a sixth aspect, an embodiment of the present invention further provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements a method for synchronously processing upstream and downstream business processes as described in any one of the embodiments of the present invention.

[0023] In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method for synchronous processing of upstream and downstream business processes as described in any one of the embodiments of the present invention is implemented.

[0024] In an embodiment of the present invention, the upstream business system generates and stores record messages at the starting execution point and the ending execution point of each sub-process in the processing flow of the upstream business respectively; the downstream business system periodically sends a first record acquisition request to the upstream business system; when the upstream business system receives the first record acquisition request sent by the downstream business system, the upstream business system acquires at least one stored record message based on the first record acquisition request, and returns the acquired record message to the downstream business system; the downstream business system receives the record message returned by the upstream business system, and stores the received record message; when the downstream business system receives the input business number, the downstream business system reads each record message corresponding to the input business number from the stored record message, and starts executing the processing flow of the downstream business based on the read record message. It can be seen that the embodiment of the present invention synchronizes the business-related information of each sub-process in the processing flow of executing the upstream business by the upstream business system to the downstream business system in a timely manner, so that the downstream business system can use the synchronized business-related information to execute the processing flow of the downstream business, thereby making the business processing flows of the upstream business system and the downstream business system synchronous, speeding up the business process processing progress, improving the processing efficiency, and solving the problem of long business processing time and low efficiency in the prior art due to the linear interaction between the upstream business system and the downstream business system, and the long business processing flows within the upstream business system and the downstream business system themselves. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0026] Figure 1 It is a flowchart of a method for synchronously processing upstream and downstream business processes in Embodiment 1 of the present invention;

[0027] Figure 2 It is a flowchart of a method for synchronously processing upstream and downstream business processes in Embodiment 3 of the present invention;

[0028] Figure 3 It is a flowchart of a method for synchronously processing upstream and downstream business processes in Embodiment 4 of the present invention;

[0029] Figure 4 It is a flowchart of a method for synchronously processing upstream and downstream business processes in Embodiment 5 of the present invention;

[0030] Figure 5It is a flowchart of a method for synchronously processing upstream and downstream business processes in Embodiment 6 of the present invention;

[0031] Figure 6 It is a flowchart of a synchronous processing method for upstream and downstream business processes of a synchronous processing system for upstream and downstream business processes in Embodiment 8 of the present invention;

[0032] Figure 7 It is a structural schematic diagram of a synchronous processing device for upstream and downstream business processes in Embodiment 9 of the present invention;

[0033] Figure 8 This is a structural schematic diagram of a synchronous processing device for upstream and downstream business processes in Embodiment 10 of the present invention;

[0034] Fig. 9 It is a structural schematic diagram of an electronic device in the eleventh embodiment of the present invention. DETAILED DESCRIPTION

[0035] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0036] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0037] Embodiment 1

[0038] Figure 1 This is a flowchart of a method for synchronously processing upstream and downstream business processes provided in Embodiment 1 of the present invention. This embodiment can be applied to an upstream business system. The method can be executed by a synchronous processing device for upstream and downstream business processes in an embodiment of the present invention. The device can be implemented in software and / or hardware. Figure 1 As shown, the method specifically comprises the following steps:

[0039] S101. Generate and store record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively; wherein each record message includes a business identifier of the upstream business, a process identifier of the corresponding sub-process, and business information.

[0040] The business identifier is a unique identifier of the upstream business, the process identifier of the corresponding sub-process is used to identify the business sub-process corresponding to the recorded message, and the business information is the business-related information recorded in the recorded message.

[0041] Exemplarily, if the upstream business being executed is a public credit process management business, the public credit process management business processing process includes a business approval sub-process, a contract application sub-process and a debt payment sub-process, then the business identifier is the trade financing number of the public credit process management business, the process identifier includes the business identifier corresponding to the business stage, the contract identifier corresponding to the contract stage and the payment identifier corresponding to the payment stage, the business information includes the amount, credit type, currency, term, over- and under-loading ratio, deposit ratio, handling agency, business start date, business expiration date, etc., and the embodiments of the present invention do not limit this.

[0042] Specifically, the start execution point and the end execution point of each sub-process in the processing flow of the upstream business respectively generate and store record messages, so that the downstream business system can know the process progress of the processing flow of the upstream business.

[0043] Exemplarily, if the upstream business being executed is a public credit process management business, and the public credit process management business processing flow includes a business approval sub-process, a contract application sub-process, and a debt payment sub-process, then the starting execution points and the ending execution points of the approval sub-process, the contract application sub-process, and the debt payment sub-process in the processing flow of the public credit process management business respectively generate and store record messages for recording the processing progress of the current public credit process management business and related business information.

[0044] Optionally, each record message also includes an effectiveness flag; wherein, the effectiveness flag contained in the record message generated at the termination execution point of the last sub-process in the processing flow of the upstream business is valid, so that the downstream business system executes the last sub-process in the processing flow of the downstream business when receiving the record message with the effectiveness flag as valid.

[0045] Among them, the effectiveness mark is used to indicate whether the processing flow of the upstream business has been completed. The downstream business system includes the ISS system of national settlement, the pricing list system, etc. The processing flow of the downstream business includes the input sub-flow, the approval sub-flow and the sending SWIFT message sub-flow, which is not limited in the embodiment of the present invention.

[0046] Specifically, the record messages stored at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business all contain an effectiveness identifier, but only the effectiveness identifier contained in the record message generated by the end execution point of the last sub-process is valid, and the effectiveness identifiers contained in all other record messages are invalid. When the downstream business system receives the record message with a valid effectiveness identifier from the upstream business system, it executes the last sub-process in the downstream business processing flow.

[0047] For example, if the upstream business being executed is a public credit process management business, which includes an approval sub-process, a contract application sub-process and a debt payment sub-process, and the downstream business is a national settlement business, which includes an input sub-process, an approval sub-process and a SWIFT message sending sub-process, then a record message containing a valid effectiveness flag will be generated at the termination execution point of the debt payment sub-process in the processing flow of the public credit process management business, and the national settlement system executes the SWIFT message sub-process in the processing flow of the national settlement business when receiving the record message with a valid effectiveness flag.

[0048] S102. When a first record acquisition request sent by a downstream business system is received, at least one stored record message is acquired based on the first record acquisition request, and the acquired record message is returned to the downstream business system, so that the downstream business system starts to execute the processing flow of the downstream business based on the received record message.

[0049] Among them, the first record acquisition request is a business information acquisition instruction sent by the downstream business system. Specifically, the business information acquisition instruction contains business information that needs to be provided by the upstream business when the downstream business is executed, such as the business information number, the number of business information items, the business information type, etc., which is not limited in this embodiment of the present invention.

[0050] Among them, obtaining at least one stored record message based on the first record acquisition request and returning the acquired record message to the downstream business system means that the upstream business system transmits one or more record messages to the downstream business system, and the transmitted message cannot be an empty message.

[0051] Exemplarily, the downstream business system sends a first record acquisition request to the upstream business system. The upstream business system passes the stored corresponding record message to the downstream business system based on the business information number, number of business information items, business information type and other information carried in the first record acquisition request. At this time, the downstream business system starts to execute the corresponding processing flow of the downstream business based on the received record message.

[0052] Optionally, the upstream business system receives a second record acquisition request sent by the downstream business system at the starting execution point of an intermediate sub-process in the processing flow of the downstream business; obtains the record message required to execute the intermediate sub-process based on the second record acquisition request, and returns the record message required to execute the intermediate sub-process to the downstream business system, so that the downstream business system executes the intermediate sub-process based on the received record message; wherein the intermediate sub-process is other sub-processes in the processing flow of the downstream business except the first sub-process.

[0053] Exemplarily, the downstream business may be a national settlement business, and the processing flow of the business includes an input sub-process, an approval sub-process, and a SWIFT message sending sub-process. The second record acquisition request is sent at the starting execution point of the approval sub-process and the SWIFT message sending sub-process. When the upstream business system receives the second record acquisition request sent by the downstream business system, it acquires the record message required for executing the intermediate sub-process based on the second record acquisition request, and returns the acquired record message to the downstream business system, so that the downstream business system executes the intermediate sub-process based on the received record message.

[0054] The technical solution of this embodiment generates and stores record messages at the start and end execution points of each sub-process in the processing flow of the upstream business, wherein each record message contains the business identifier of the upstream business, the process identifier of the corresponding sub-process, and business information; upon receiving the first record acquisition request sent by the downstream business system, at least one stored record message is acquired based on the first record acquisition request, and the acquired record message is returned to the downstream business system, so that the downstream business system starts to execute the processing flow of the downstream business based on the received record message. The business-related information of each sub-process in the processing flow of the upstream business system executing the upstream business can be synchronized to the downstream business system in a timely manner, so that the business processing flow of the upstream business system and the downstream business system is synchronized, which speeds up the processing progress of the business flow and improves the processing efficiency.

[0055] Embodiment 2

[0056] This embodiment is based on the above embodiment and describes the specific implementation method of step S102, which mainly includes:

[0057] Step 1: Read the starting primary key number carried in the record acquisition request.

[0058] Among them, when the record acquisition request is received for the first time, the starting primary key number is the preset primary key number agreed upon by the upstream business system and the downstream business system. When the record acquisition request is received subsequently, the starting primary key number is the primary key number of the last record message sent to the downstream business system.

[0059] Step 2: Obtain a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages.

[0060] Exemplarily, when the upstream business system stores the business record message, it stores the primary key number corresponding to the current record message. When the upstream business system receives the first record acquisition request sent by the downstream business system, based on the starting primary key number carried in the first record acquisition request and the record messages with a preset number generated after the record message corresponding to the starting primary key number, the upstream business system sends the relevant record messages stored in the upstream business system to the downstream business system. For example, if the starting primary key number carried in the first record acquisition request is 50, and the preset number of record messages generated after the record message corresponding to the starting primary key number is 10, then the upstream business system sends the stored record messages with primary key numbers 50 to 59 to the downstream business system.

[0061] The technical solution of this embodiment obtains a preset number of recorded messages generated after the recorded message corresponding to the starting primary key number from the stored recorded messages by reading the starting primary key number carried in the record acquisition request. The recorded messages can be accurately and quickly queried and read, shortening the time for information matching and reading, improving the acquisition rate of recorded messages, and accelerating the progress of business processing procedures.

[0062] Embodiment 3

[0063] Figure 2 This is a flowchart of a method for synchronously processing upstream and downstream business processes provided by Embodiment 3 of the present invention. Based on the above embodiments, this embodiment adds the following steps:

[0064] S201. Receive an information error prompt message sent by a downstream business system; wherein the information error prompt message is sent by the downstream business system when detecting an error in a received record message.

[0065] The method of receiving the information error prompt message sent by the downstream business system may be an information prompt, a window pop-up, an audio-visual display, etc., which is not limited in the embodiment of the present invention.

[0066] S202: prompting the user to modify the erroneous recorded message according to the information error prompt message.

[0067] S203: Obtain a modification message after modifying the erroneous record message, and synchronize the modification message to a downstream business system.

[0068] Specifically, the user will modify the erroneous record message according to the information error prompt message. After the modification is completed, the upstream business system will synchronize the modified message to the downstream business system.

[0069] Exemplarily, after the downstream business system obtains the record message from the upstream business system, it will check the correctness of the obtained record message in real time. If it is found that the record message is wrong, it will send an information error prompt message to the upstream business system, and prompt the user to modify the erroneous record message through information prompts, window pop-ups, and sound and light displays. After receiving the prompt of record message errors sent by the downstream business system, the upstream business system will correct the relevant messages and synchronize the corrected messages to the downstream business system.

[0070] Optionally, the upstream business system receives an error correction reminder message sent by the downstream business system; wherein, the error correction reminder message is sent by the downstream business system when no modification message is received within a preset time period after detecting an error in a received record message; the error correction reminder message is sent to the communication account of the processing personnel corresponding to the erroneous record message to remind the personnel to modify the erroneous record message.

[0071] The preset time may be 10 minutes, 30 minutes, 60 minutes, etc., which is not limited in the embodiment of the present invention.

[0072] Exemplarily, the preset time is set to 10 minutes. After 10 minutes, if the downstream business system has not received the modification message sent by the upstream business system, the downstream business system will send an error correction reminder message to the upstream business system, reminding the upstream business system to correct the error message. The upstream business system sends an error correction reminder message to the communication account of the processing personnel corresponding to the erroneous record message, reminding the personnel to modify the erroneous record message in time.

[0073] The technical solution of this embodiment is to receive an information error prompt message sent by a downstream business system; wherein the information error prompt message is sent by the downstream business system when an error is detected in a received record message. According to the information error prompt message, the user is prompted to modify the erroneous record message. A modification message after modifying the erroneous record message is obtained, and the modification message is synchronized to the downstream business system. The erroneous information in the business processing flow can be detected and corrected in a timely manner, which greatly reduces the business processing time and improves the business processing efficiency.

[0074] Embodiment 4

[0075] Figure 3 This is a flowchart of a method for synchronously processing upstream and downstream business processes provided in Embodiment 4 of the present invention. This embodiment is applicable to downstream business systems. The method can be executed by a synchronous processing device for upstream and downstream business processes in an embodiment of the present invention. The device can be implemented in software and / or hardware, such as Figure 3 As shown, the method specifically comprises the following steps:

[0076] S301. Periodically send a first record acquisition request to the upstream business system so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message contains the business identifier of the upstream business, the process identifier of the corresponding sub-process, and the business information.

[0077] Among them, the first record acquisition request is a business information acquisition instruction sent by the downstream business system. Specifically, the business information acquisition instruction contains business information that needs to be provided by the upstream business when the downstream business is executed, such as the business information number, the number of business information items, the business information type, etc., which is not limited in this embodiment of the present invention.

[0078] The business identifier is a unique identifier of the upstream business, the process identifier of the corresponding sub-process is used to identify the business sub-process corresponding to the recorded message, and the business information is information related to the business recorded in the recorded message.

[0079] Exemplarily, if the upstream business being executed is a public credit process management business, the public credit process management business processing process includes a business approval sub-process, a contract application sub-process and a debt payment sub-process, then the business identifier is the trade financing number of the public credit process management business, the process identifier includes the business identifier corresponding to the business stage, the contract identifier corresponding to the contract stage and the payment identifier corresponding to the payment stage, the business information includes the amount, credit type, currency, term, over- and under-loading ratio, deposit ratio, handling agency, business start date, business expiration date, etc., and the embodiments of the present invention do not limit this.

[0080] Specifically, periodically sending a first record acquisition request to the upstream business system means sending a first record acquisition request to the upstream system when each preset time is reached, and obtaining the start execution point and the end execution point of each sub-process within this preset time by the upstream business system to generate and store record messages respectively. The preset time can be 10 minutes, 30 minutes, 60 minutes, etc., which is not limited to the embodiment of the present invention.

[0081] Exemplarily, if the preset duration is 10 minutes, a first record acquisition request is sent to the upstream business system every 10 minutes, and the start execution point and end execution point of each sub-process of the upstream business system within the time period are acquired and stored to generate and store record messages respectively.

[0082] S302: Receive a record message returned by an upstream business system, and store the received record message.

[0083] S303: When the input service number is received, each record message corresponding to the input service number is read from the stored record messages, and the processing flow of the downstream service is started based on the read record messages.

[0084] The business number is a unique identifier for the recorded message. Specifically, by querying the input business number, the corresponding recorded messages can be found more quickly, which is simpler and more convenient than information query.

[0085] For example, if the service number corresponding to the record message A is 35, the record message A can be obtained by directly reading the record message with the service number 35.

[0086] Optionally, after reading each record message corresponding to the input business number from the stored record message and before starting to execute the processing flow of the downstream business based on the read record message, the read record message will be visually displayed; after detecting a confirmation instruction for the displayed record message, the operation of starting to execute the processing flow of the downstream business based on the read record message is triggered.

[0087] Among them, the visual display includes interface display and information prompts, etc.; specifically, if the displayed record message is correct, the record message is confirmed. After detecting the confirmation instruction for the displayed record message, the operation of starting to execute the processing flow of the downstream business based on the read record message is triggered. If the displayed record information is incorrect, the record information can be modified or an information error prompt message can be sent to the upstream business system.

[0088] The technical solution of this embodiment is to periodically send a first record acquisition request to the upstream business system, receive the record message returned by the upstream business system, and store the received record message; when the input business number is received, read the record messages corresponding to the input business number from the stored record messages, and start executing the processing flow of the downstream business based on the read record messages. By timely synchronizing the business-related information of each sub-process in the processing flow of executing the upstream business by the upstream business system to the downstream business system, the downstream business system can use the synchronized business-related information to execute the processing flow of the downstream business, so that the business processing flow of the upstream business system and the downstream business system is synchronized, which speeds up the processing progress of the business flow and improves the processing efficiency.

[0089] Embodiment 5

[0090] Figure 4 This is a flowchart of a method for synchronously processing upstream and downstream business processes provided in Embodiment 5 of the present invention. This embodiment is based on Embodiment 4 above and further includes the following steps after S303:

[0091] S401, at the start execution point of the last sub-process in the downstream business processing flow, determining whether a record message with a validity mark as valid is stored.

[0092] The validity flag is used to indicate the validity of the recorded message. Specifically, the recorded messages stored at the start and end execution points of each sub-process in the processing flow of the upstream business all contain the validity flag, but only the validity flag contained in the recorded message generated by the end execution point of the last sub-process is valid, and the validity flags contained in all other recorded messages are invalid. If the test result is valid, execute step S402, if the test result is invalid, execute step S403.

[0093] S402: If a record message with a validity mark as valid is stored, the last sub-process in the processing flow of the downstream business is executed.

[0094] Among them, the processing flow of downstream business includes an input sub-flow, an approval sub-flow and a SWIFT message sending sub-flow. The last sub-flow in the processing flow of downstream business refers to the SWIFT message sending sub-flow.

[0095] Specifically, when the downstream business receives a record message with an effectiveness mark as valid from the upstream business system, the sending SWIFT message sub-process in the downstream business processing flow is executed.

[0096] Exemplarily, the processing flow of the upstream business includes a business approval sub-process, a contract application sub-process and a debt payment sub-process, and the processing flow of the downstream business includes an input sub-process, an approval sub-process and a SWIFT message sending sub-process. Only the effectiveness mark contained in the record message generated by the termination execution point of the debt payment sub-process in the processing flow of the upstream business is valid. The starting execution point of the SWIFT message sending sub-process in the downstream business processing flow needs to detect whether a record message with a valid effectiveness mark is stored, that is, to detect whether the upstream business process is completed. Only when it is detected that a record message with a valid effectiveness mark is stored, the SWIFT message sending sub-process in the downstream business processing flow is executed.

[0097] S403: If no record message with the validity mark being valid is stored, an error message is issued, or the process returns to the step of determining whether a record message with the validity mark being valid is stored.

[0098] Optionally, at the starting execution point of the intermediate sub-process in the processing flow of the downstream business, if the record message required for executing the intermediate sub-process is not stored, the upstream business system may be waited for to send the required record message. Preferably, a second record acquisition message may be actively sent to the upstream business system, so that the upstream business system acquires the record message required for executing the intermediate sub-process based on the second record acquisition request.

[0099] Based on the record message required for executing the intermediate sub-process returned by the upstream business system, the intermediate sub-process is executed; wherein the intermediate sub-process is the other sub-process in the processing flow of the downstream business except the first sub-process.

[0100] The technical solution of this embodiment determines whether a record message with an effective mark is stored at the starting execution point of the last sub-process in the downstream business processing flow; if a record message with an effective mark is stored, the last sub-process in the downstream business processing flow is executed; if a record message with an effective mark is not stored, an error message is issued, or the step of determining whether a record message with an effective mark is stored is returned. The process of the downstream business system can be processed timely and effectively, and the business processing efficiency is improved.

[0101] Embodiment 6

[0102] Figure 5 This is a flowchart of a method for synchronously processing upstream and downstream business processes provided by Embodiment 6 of the present invention. This embodiment is based on the above Embodiments 4 to 5, and describes the specific implementation method of step S301, which mainly includes:

[0103] S501, when the current scheduled polling time arrives, determine the current value of the starting primary key number; wherein, the initial value of the starting primary key number is the value agreed with the upstream business system, and the subsequent value of the starting primary key number is the primary key number of the last record message returned by the upstream business system.

[0104] The scheduled polling time may be 10 minutes, 30 minutes, 60 minutes, etc., which is not limited in the embodiment of the present invention.

[0105] Exemplarily, when the current scheduled polling time arrives, the current value of the starting primary key number is determined. If the starting primary key number is obtained for the first time, the value of the starting primary key number is the value agreed with the upstream business system. Otherwise, the value of the starting primary key number is the primary key number of the last recorded message returned by the upstream business system last time. For example, the initial value of the starting primary key number agreed with the upstream business system is 50. When the first scheduled polling time arrives, the starting primary key number obtained is 50. If the primary key number of the last recorded message returned after reading the information is 60, then the starting primary key number when the next scheduled polling time arrives is 60.

[0106] S502: Generate a first record acquisition request including a starting primary key number.

[0107] S503: Send a first record acquisition request to the upstream business system, so that the upstream business system acquires and returns a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages.

[0108] Among them, when obtaining the record message for the first time, the starting primary key number is the preset primary key number agreed upon by the upstream business system and the downstream business system. When obtaining the record message subsequently, the starting primary key number is the primary key number of the last record message obtained last time.

[0109] Exemplarily, when the upstream business system stores the record message, it stores the primary key number corresponding to the current record message. When the downstream business system sends the first record acquisition request to the upstream business system, based on the starting primary key number carried in the first record acquisition request and the record message corresponding to the starting primary key number, the preset number of record messages generated after the record message corresponding to the starting primary key number, etc., the corresponding stored record message of the upstream business system is acquired. For example, if the starting primary key number carried in the first record acquisition request is 50, and the preset number of record messages generated after the record message corresponding to the starting primary key number is 10, then the record messages with primary key numbers 50 to 59 stored in the upstream business system are acquired, and 60 is stored as the starting primary key number for the next information acquisition.

[0110] The technical solution of this embodiment is to determine the current value of the starting primary key number when the current scheduled polling time arrives; wherein the initial value of the starting primary key number is the value agreed with the upstream business system, and the subsequent starting primary key number is the primary key number of the last record message returned by the upstream business system last time; generate a first record acquisition request containing the starting primary key number; send the first record acquisition request to the upstream business system, so that the upstream business system acquires and returns a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages. The record messages can be accurately and quickly queried and read, shortening the time for information matching and reading, improving the acquisition rate of record messages, and accelerating the progress of business processing procedures.

[0111] Embodiment 7

[0112] This embodiment is optimized based on the above-mentioned Embodiment 4 to Embodiment 6, and the following steps are added:

[0113] Step 1: When an error is detected in a received record message, the processing flow of the downstream business is stopped, and an information error prompt message is sent to the upstream business system, so that the upstream business system prompts the user to modify the erroneous record message after receiving the information error prompt message and obtains a modified message after modifying the erroneous record message.

[0114] Specifically, after the downstream business system receives the record message returned by the upstream business system, it inputs the business information contained in the received record message into a preset message detection model, and determines whether the record message is wrong according to the output result of the preset message detection model.

[0115] Among them, the preset message detection model is a model pre-trained based on multiple sample record messages using a supervised model training method. Specifically, the model training process includes: initializing the preset message detection model; for each sample record message, inputting the information contained in the sample record message into the preset message detection model; obtaining the result of whether the sample record message output by the preset message detection model is wrong, and calculating the loss function based on the result and the label data corresponding to the sample record message whether it is wrong; adjusting the network parameters in the preset message detection model based on the value of the calculated loss function until the output result of the preset message detection model converges or reaches the preset number of training times.

[0116] Exemplarily, after the downstream business system receives the record message returned by the upstream business system, it will input the business information contained in the received record message into the preset message detection model, and determine whether the received record message is correct based on the preset message detection model. If it is correct, the corresponding business process will continue to execute. If the information is incorrect, an information error prompt message will be sent to the upstream business system through information prompts, window pop-ups, and sound and light displays, prompting the user to modify the erroneous record message.

[0117] Optionally, it is also possible to manually confirm whether the recorded message is correct. Specifically, the read recorded message is displayed visually such as interface display, information prompt, etc., and manually confirm whether the displayed recorded message is correct.

[0118] Step 2: Receive the modification message sent by the upstream business system, and continue to execute the processing flow of the downstream business based on the modification message.

[0119] Specifically, after the upstream business system changes the record message, it will send the modified message to the downstream business system so that the downstream business system can detect the modified business message and continue to execute the corresponding processing flow.

[0120] Optionally, if the modification message is not received within a preset time period after detecting that the received record message is erroneous, an error correction reminder message is sent to the upstream business system, so that the upstream business system sends an error correction reminder message to the communication account of the processing personnel corresponding to the erroneous record message, so as to remind the personnel to modify the erroneous record message.

[0121] Exemplarily, the preset time is set to 10 minutes. When the preset message detection model determines that the received business information is erroneous, an information error prompt message is sent to the upstream business system through information prompts, window pop-ups, and sound and light displays, prompting the user to modify the erroneous record message. Ten minutes later, if the downstream business system has not received the modification message sent by the upstream business system, the downstream business system will send an error correction reminder message to the upstream business system, so that the upstream business system will send an error correction reminder message to the communication account of the processing personnel corresponding to the erroneous record message, reminding the personnel to modify the erroneous record message in time.

[0122] The technical solution of this embodiment stops executing the processing flow of the downstream business when detecting an error in the received record message, and sends an information error prompt message to the upstream business system, so that the upstream business system prompts the user to modify the erroneous record message after receiving the information error prompt message and obtains a modified message after modifying the erroneous record message; receives the modified message sent by the upstream business system, and continues to execute the processing flow of the downstream business based on the modified message. It can detect and correct the error information in the business processing flow in a timely manner, greatly reducing the business processing time and improving the business processing efficiency.

[0123] Embodiment 8

[0124] Figure 6 This is a flowchart of a synchronous processing method for upstream and downstream business processes provided by Embodiment 8 of the present invention. This embodiment can be applied to the interaction between the upstream business system and the downstream business system, such as Figure 6 As shown, the method specifically comprises the following steps:

[0125] S601. The upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively; wherein each of the record messages contains the business identifier of the upstream business, the process identifier of the corresponding sub-process and business information.

[0126] The business identifier is a unique identifier of the upstream business, the process identifier of the corresponding sub-process is used to identify the business sub-process corresponding to the recorded message, and the business information is the business-related information recorded in the recorded message.

[0127] Exemplarily, if the upstream business being executed is a public credit process management business, the public credit process management business processing process includes a business approval sub-process, a contract application sub-process and a debt payment sub-process, then the business identifier is the trade financing number of the public credit process management business, the process identifier includes the business identifier corresponding to the business stage, the contract identifier corresponding to the contract stage and the payment identifier corresponding to the payment stage, the business information includes the amount, credit type, currency, term, over- and under-loading ratio, deposit ratio, handling agency, business start date, business expiration date, etc., and the embodiments of the present invention do not limit this.

[0128] Specifically, the start execution point and the end execution point of each sub-process in the processing flow of the upstream business respectively generate and store record messages, so that the downstream business system can know the process progress of the processing flow of the upstream business.

[0129] Exemplarily, if the upstream business being executed is a public credit process management business, and the public credit process management business processing flow includes a business approval sub-process, a contract application sub-process, and a debt payment sub-process, then the starting execution points and the ending execution points of the approval sub-process, the contract application sub-process, and the debt payment sub-process in the processing flow of the public credit process management business respectively generate and store record messages for recording the processing progress of the current public credit process management business and related business information.

[0130] S602: The downstream business system periodically sends a first record acquisition request to the upstream business system.

[0131] Among them, the first record acquisition request is a business information acquisition instruction sent by the downstream business system. Specifically, the business information acquisition instruction contains business information that the upstream business needs to provide when the downstream business is executed, such as the business information number, the number of business information items, the business information type, etc.

[0132] Specifically, periodically sending a first record acquisition request to the upstream business system means sending a first record acquisition request to the upstream system when each preset time is reached, and obtaining the start execution point and end execution point of each sub-process within this preset time by the upstream business system to generate and store record messages respectively. The preset time can be 10 minutes, 30 minutes, 60 minutes, etc., which is not limited to the embodiment of the present invention.

[0133] Exemplarily, if the preset duration is 10 minutes, a first record acquisition request is sent to the upstream business system every 10 minutes, and the start execution point and end execution point of each sub-process of the upstream business system within the time period are acquired and stored to generate and store record messages respectively.

[0134] S603: When receiving the first record acquisition request sent by the downstream business system, the upstream business system acquires at least one stored record message based on the first record acquisition request, and returns the acquired record message to the downstream business system.

[0135] Among them, obtaining at least one stored record message based on the first record acquisition request and returning the acquired record message to the downstream business system means that the upstream business system transmits one or more record messages to the downstream business system, and the transmitted message cannot be an empty message.

[0136] Exemplarily, the downstream business system sends a first record acquisition request to the upstream business system. The upstream business system passes the stored corresponding record message to the downstream business system based on the business information number, number of business information items, business information type and other information carried in the first record acquisition request. At this time, the downstream business system starts to execute the corresponding processing flow of the downstream business based on the received record message.

[0137] Optionally, the upstream business system receives a second record acquisition request sent by the downstream business system at the starting execution point of an intermediate sub-process in the processing flow of the downstream business; obtains the record message required to execute the intermediate sub-process based on the second record acquisition request, and returns the record message required to execute the intermediate sub-process to the downstream business system, so that the downstream business system executes the intermediate sub-process based on the received record message; wherein the intermediate sub-process is other sub-processes in the processing flow of the downstream business except the first sub-process.

[0138] Exemplarily, the downstream business may be a national settlement business, and the processing flow of the business includes an input sub-process, an approval sub-process, and a SWIFT message sending sub-process. The second record acquisition request is sent at the starting execution point of the approval sub-process and the SWIFT message sending sub-process. When the upstream business system receives the second record acquisition request sent by the downstream business system, it acquires the record message required for executing the intermediate sub-process based on the second record acquisition request, and returns the acquired record message to the downstream business system, so that the downstream business system executes the intermediate sub-process based on the received record message.

[0139] S604: The downstream business system receives the record message returned by the upstream business system, and stores the received record message.

[0140] S605: When the input service number is received, each record message corresponding to the input service number is read from the stored record messages, and the processing flow of the downstream service is started based on the read record messages.

[0141] Among them, the business number is the symbolic information of the recorded message. Specifically, by querying the input business number, the corresponding recorded messages can be found more quickly, which is more concise and convenient than information query.

[0142] For example, if the service number corresponding to the record message A is 35, the record message A can be obtained by directly reading the record message with the service number 35.

[0143] Optionally, after reading each record message corresponding to the input business number from the stored record message and before starting to execute the processing flow of the downstream business based on the read record message, the read record message will be visually displayed; after detecting a confirmation instruction for the displayed record message, the operation of starting to execute the processing flow of the downstream business based on the read record message is triggered.

[0144] Among them, the visual display includes interface display, information prompts, etc.; specifically, if the displayed record message is correct, the record message is confirmed. After detecting the confirmation instruction for the displayed record message, the operation of starting to execute the downstream business processing flow based on the read record message is triggered. If the displayed record information is incorrect, the record information can be modified or an information error prompt message can be sent to the upstream business system.

[0145] Optionally, when the downstream business system detects that the received record message is wrong, it stops executing the processing flow of the downstream business and sends an information error prompt message to the upstream business system, so that the upstream business system prompts the user to modify the erroneous record message after receiving the information error prompt message and obtains a modification message after modifying the erroneous record message. After receiving the modification message sent by the upstream business system, the downstream business system continues to execute the processing flow of the downstream business based on the modification message.

[0146] Exemplarily, after the downstream business system receives the business message returned by the upstream business system, the business information contained in the received record message will be input into the preset message detection model, and whether the received business information is correct will be determined according to the preset message detection model. When the preset message detection model determines that the received business information is wrong, an information error prompt message will be sent to the upstream business system through information prompts, window pop-ups, and sound and light displays, prompting the user to modify the erroneous record message. The preset time is set to 10 minutes. After ten minutes, if the downstream business system has not received the modification message sent by the upstream business system, the downstream business system will once again send an error correction reminder message to the upstream business system, and the upstream business system will send an error correction reminder message to the communication account of the processing personnel corresponding to the erroneous record message, reminding the personnel to modify the erroneous record message in time.

[0147] Optionally, at the start execution point of the last sub-process in the downstream business processing flow, it is necessary to determine whether a record message with an effective mark is stored. If so, the last sub-process in the downstream business processing flow is executed. If not, it is necessary to send a request to the upstream business system to receive the record message returned by the upstream business system and store the received record message until a record message with an effective mark is stored.

[0148] Among them, the effectiveness flag is used to indicate the validity of the record message. Specifically, the record messages stored at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business all contain the effectiveness flag, but only the effectiveness flag contained in the record message generated by the end execution point of the last sub-process is valid, and the effectiveness flags contained in all other record messages are invalid.

[0149] Exemplarily, the processing flow of the upstream business includes a business approval sub-flow, a contract application sub-flow and a debt payment sub-flow, and the processing flow of the downstream business includes an input sub-flow, an approval sub-flow and a SWIFT message sending sub-flow. Only the effective mark contained in the record message generated by the termination execution point of the debt payment sub-flow in the processing flow of the upstream business is valid. The starting execution point of the SWIFT message sending sub-flow in the downstream business processing flow needs to detect whether a record message with a valid effective mark is stored, that is, to detect whether the upstream business process is completed. Only when it is detected that a record message with a valid effective mark is stored, the SWIFT message sending sub-flow in the downstream business processing flow is executed. If the record message required for executing the intermediate sub-flow is not stored, you can wait for the upstream business system to send the required record message. Preferably, you can also actively send a second record acquisition message to the upstream business system, so that the upstream business system can obtain the record message required for executing the SWIFT message sending sub-flow based on the second record acquisition request.

[0150] The technical solution of this embodiment is to generate and store record messages at the starting execution point and the ending execution point of each sub-process in the processing flow of the upstream business through the upstream business system; the downstream business system sends a first record acquisition request to the upstream business system at regular intervals; when the upstream business system receives the first record acquisition request sent by the downstream business system, it acquires at least one stored record message based on the first record acquisition request, and returns the acquired record message to the downstream business system; the downstream business system receives the record message returned by the upstream business system and stores the received record message; when the downstream business system receives the input business number, it reads each record message corresponding to the input business number from the stored record message, and starts to execute the processing flow of the downstream business based on the read record message. The problem of lengthy business processing time and low efficiency caused by linear interaction between the upstream business system and the downstream business system components and the long approval process of the upstream business system and the downstream business system itself is solved. The embodiment of the present invention synchronizes the key information of the key nodes of the business process approval in the upstream business system to the downstream business system, so that the approval process of the upstream business system and the downstream business system can be synchronized, thereby accelerating the progress of the business processing process.

[0151] Embodiment 9

[0152] The synchronous processing device for upstream and downstream business processes provided in Embodiment 9 of the present invention can execute the synchronous processing method for upstream and downstream business processes provided in any of Embodiments 1 to 3 of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0153] Figure 7 A schematic diagram of a structure of a synchronous processing device for upstream and downstream business processes provided in Example 9, such as Figure 7 As shown, it includes: an information generating module 701 and an information sending module 702.

[0154] The information generation module 701 is used to generate and store record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively; wherein each record message contains the business identifier of the upstream business, the process identifier of the corresponding sub-process and the business information.

[0155] The information sending module 702 is used to obtain at least one stored record message based on the first record acquisition request when receiving the first record acquisition request sent by the downstream business system, and return the acquired record message to the downstream business system, so that the downstream business system starts to execute the processing flow of the downstream business based on the received record message.

[0156] The synchronous processing device for upstream and downstream business processes provided in this embodiment is to implement the synchronous processing method for upstream and downstream business processes of the above embodiments one to three. The implementation principle and technical effects of the synchronous processing device for upstream and downstream business processes provided in this embodiment are similar to those of the above embodiments and will not be repeated here.

[0157] Optionally, the information generation module 701 is specifically used to generate record information containing an effectiveness indication; wherein, the effectiveness identifier contained in the record message generated at the termination execution point of the last sub-process in the processing flow of the upstream business is valid, so that the downstream business system executes the last sub-process in the processing flow of the downstream business when receiving the record message with the effectiveness identifier as valid.

[0158] Optionally, the information generation module 701 is specifically configured to store a primary key number corresponding to the current record message when storing each record message; wherein each primary key number is used to represent the generation order of the corresponding record message.

[0159] The information sending module 702 is specifically used to obtain at least one stored record message based on the first record acquisition request, including: reading the starting primary key number carried in the record acquisition request, and obtaining a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages.

[0160] Optionally, the synchronization processing device for upstream and downstream business processes further includes: an information detection module 703 , an information processing module 704 , a second record acquisition request module 705 and a second information sending module 706 .

[0161] The information detection module 703 is used to receive an information error prompt message sent by a downstream business system; wherein the information error prompt message is sent by the downstream business system when it detects that a received record message is wrong.

[0162] The information processing module 704 is used to prompt the user to modify the erroneous record message according to the information error prompt message; obtain the modified message after modifying the erroneous record message, and synchronize the modified message to the downstream business system.

[0163] The second record acquisition request module 705 is used to receive a second record acquisition request sent by the downstream business system at the start execution point of the intermediate sub-process in the processing flow of the downstream business after returning the acquired record message to the downstream business system.

[0164] The second information sending module 706 is used to obtain the record message required for executing the intermediate sub-process based on the second record acquisition request, and return the record message required for executing the intermediate sub-process to the downstream business system, so that the downstream business system executes the intermediate sub-process based on the received record message; wherein the intermediate sub-process is other sub-processes in the processing flow of the downstream business except the first sub-process.

[0165] Optionally, the information processing module 704 is specifically used to receive error correction reminder messages sent by downstream business systems; wherein, the error correction reminder message is sent by the downstream business system when no modification message is received within a preset time period after detecting an error in a received record message; the error correction reminder message is sent to the communication account of the processing personnel corresponding to the erroneous record message to remind the personnel to modify the erroneous record message.

[0166] Embodiment 10

[0167] The synchronous processing device for upstream and downstream business processes provided in the tenth embodiment of the present invention can execute the synchronous processing method for upstream and downstream business processes provided in any of the above-mentioned fourth to seventh embodiments of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0168] Figure 8 A schematic diagram of the structure of a synchronous processing device for upstream and downstream business processes provided in Example 10, such as Figure 8 As shown, it includes: an information request module 801, an information storage module 802 and a business processing module 803.

[0169] The information request module 801 is used to periodically send a first record acquisition request to the upstream business system so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the starting execution point and the ending execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message contains the business identifier of the upstream business, the process identifier of the corresponding sub-process, and the business information.

[0170] The information storage module 802 is used to receive the record message returned by the upstream business system and store the received record message.

[0171] The business processing module 803 is used to read each record message corresponding to the input business number from the stored record messages when receiving the input business number, and start executing the processing flow of the downstream business based on the read record messages.

[0172] The synchronous processing device for upstream and downstream business processes provided in this embodiment is to implement the synchronous processing method for upstream and downstream business processes of the above-mentioned embodiments four to seven. The implementation principle and technical effects of the synchronous processing device for upstream and downstream business processes provided in this embodiment are similar to those of the above-mentioned embodiments and will not be repeated here.

[0173] The information request module 801 is specifically used to determine the current value of the starting primary key number when the current scheduled polling time arrives; wherein the initial value of the starting primary key number is a value agreed upon with the upstream business system, and the subsequent value of the starting primary key number is the primary key number of the last record message returned by the upstream business system last time; generate a first record acquisition request including the starting primary key number; send the first record acquisition request to the upstream business system, so that the upstream business system obtains and returns a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages.

[0174] Optionally, the synchronous processing device for upstream and downstream business processes also includes: a business confirmation module, an information processing module and a second information processing module.

[0175] After reading each record message corresponding to the input business number from the stored record message and before starting to execute the processing flow of the downstream business based on the read record message, the business confirmation module is used to visually display the read record message; after detecting the confirmation instruction for the displayed record message, it triggers the operation of starting to execute the processing flow of the downstream business based on the read record message.

[0176] After starting to execute the processing flow of the downstream business based on the read record message, the business confirmation module is specifically used to determine whether a record message with an effectiveness mark as valid is stored at the starting execution point of the last sub-flow in the downstream business processing flow; if so, execute the last sub-flow in the processing flow of the downstream business.

[0177] The information processing module is used to stop executing the processing flow of the downstream business when an error is detected in the received record message, and send an information error prompt message to the upstream business system, so that the upstream business system prompts the user to modify the erroneous record message after receiving the information error prompt message and obtains the modification message after modifying the erroneous record message; receive the modification message sent by the upstream business system, and continue to execute the processing flow of the downstream business based on the modification message.

[0178] The information processing module is specifically used to send an error correction reminder message to the upstream business system if no modification message is received within a preset time period after detecting that a received record message is erroneous, so that the upstream business system sends an error correction reminder message to the communication account of the processing personnel corresponding to the erroneous record message to remind the personnel to modify the erroneous record message.

[0179] The information processing module is specifically used to input the business information contained in the received recorded message into a preset message detection model, and determine whether the recorded message is wrong according to the output result of the preset message detection model; wherein the preset message detection model is a model pre-trained based on multiple sample recorded messages using a supervised model training method.

[0180] After starting to execute the processing flow of the downstream business based on the read record message, the second information processing module is used to send a second record acquisition message to the upstream business system at the starting execution point of the intermediate sub-process in the processing flow of the downstream business, if the record message required for executing the intermediate sub-process is not stored, so that the upstream business system obtains the record message required for executing the intermediate sub-process based on the second record acquisition request; based on the record message required for executing the intermediate sub-process returned by the upstream business system, execute the intermediate sub-process; wherein the intermediate sub-process is other sub-processes in the processing flow of the downstream business except the first sub-process.

[0181] Embodiment 11

[0182] Fig. 9 This is a schematic diagram of the structure of an electronic device in the eleventh embodiment of the present invention. Fig. 9 A block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention is shown. Fig. 9 The electronic device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0183] like Fig. 9 As shown, the electronic device 12 is in the form of a general purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).

[0184] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0185] The electronic device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0186] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Fig. 9 not shown, usually called a "hard drive"). Although Fig. 9 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0187] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0188] The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 12, and / or communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed through an input / output (I / O) interface 22. In addition, the electronic device 12 in this embodiment, the display 24 does not exist as an independent individual, but is embedded in the mirror surface. When the display surface of the display 24 is not displayed, the display surface of the display 24 is visually integrated with the mirror surface. In addition, the electronic device 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through a network adapter 20. Fig. 9As shown, the network adapter 20 communicates with other modules of the electronic device 12 via the bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0189] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the synchronization processing method of upstream and downstream business processes applied to the upstream business system and the synchronization processing method of upstream and downstream business processes applied to the downstream business system provided in the embodiments of the present invention.

[0190] The synchronous processing method for upstream and downstream business processes applied to the upstream business system includes:

[0191] Generate and store record messages at the start and end execution points of each sub-process in the processing flow of the upstream business, respectively; wherein each record message includes the business identifier of the upstream business, the process identifier of the corresponding sub-process, and business information;

[0192] When a first record acquisition request sent by a downstream business system is received, at least one stored record message is acquired based on the first record acquisition request, and the acquired record message is returned to the downstream business system, so that the downstream business system starts executing the processing flow of the downstream business based on the received record message.

[0193] The synchronous processing method of the upstream and downstream business processes applied to the downstream business system includes:

[0194] Periodically sending a first record acquisition request to an upstream business system, so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message includes a business identifier of the upstream business, a process identifier of the corresponding sub-process, and business information;

[0195] Receive the record message returned by the upstream business system and store the received record message;

[0196] When the input service number is received, each record message corresponding to the input service number is read from the stored record messages, and the processing flow of the downstream service is started to be executed based on the read record messages.

[0197] Embodiment 12

[0198] Embodiment twelfth of the present invention provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the method for synchronously processing upstream and downstream business processes as provided in all embodiments of the invention of this application is implemented, including a method for synchronously processing upstream and downstream business processes applied to an upstream business system and a method for synchronously processing upstream and downstream business processes applied to a downstream business system.

[0199] The synchronous processing method for upstream and downstream business processes applied to the upstream business system includes:

[0200] Generate and store record messages at the start and end execution points of each sub-process in the processing flow of the upstream business, respectively; wherein each record message includes the business identifier of the upstream business, the process identifier of the corresponding sub-process, and business information;

[0201] When a first record acquisition request sent by a downstream business system is received, at least one stored record message is acquired based on the first record acquisition request, and the acquired record message is returned to the downstream business system, so that the downstream business system starts executing the processing flow of the downstream business based on the received record message.

[0202] The synchronous processing method of the upstream and downstream business processes applied to the downstream business system includes:

[0203] Periodically sending a first record acquisition request to an upstream business system, so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message includes a business identifier of the upstream business, a process identifier of the corresponding sub-process, and business information;

[0204] Receive the record message returned by the upstream business system and store the received record message;

[0205] When the input service number is received, each record message corresponding to the input service number is read from the stored record messages, and the processing flow of the downstream service is started to be executed based on the read record messages.

[0206] Any combination of one or more computer-readable media can be used. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0207] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0208] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0209] Computer program code for performing the operation of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0210] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A synchronous processing method for upstream and downstream business processes, characterized in that: The method comprises: Generate and store record messages at the start and end execution points of each sub-process in the processing flow of the upstream business, respectively; wherein each record message contains the business identifier of the upstream business, the process identifier of the corresponding sub-process, and business information; When receiving a first record acquisition request sent by a downstream business system, acquiring at least one stored record message based on the first record acquisition request, and returning the acquired record message to the downstream business system, so that the downstream business system starts to execute the processing flow of the downstream business based on the received record message; When storing each of the recorded messages, the primary key number corresponding to the current recorded message is also stored; wherein each of the primary key numbers is used to characterize the generation order of the corresponding recorded message; The acquiring at least one stored record message based on the first record acquisition request includes: The starting primary key number carried in the record acquisition request is read, and a preset number of record messages generated after the record message corresponding to the starting primary key number are acquired from the stored record messages.

2. The method according to claim 1, characterized in that Each of the recorded messages also includes a validity mark; Among them, the effectiveness mark contained in the record message generated by the termination execution point of the last sub-process in the processing flow of the upstream business is valid, so that the downstream business system executes the last sub-process in the processing flow of the downstream business when receiving the record message with the effectiveness mark as valid.

3. The method according to claim 1, characterized in that The method further comprises: Receiving an information error prompt message sent by the downstream business system; wherein the information error prompt message is sent by the downstream business system when detecting an error in a received record message; Prompt the user to modify the erroneous recorded message according to the information error prompt message; A modification message is obtained after modifying the erroneous record message, and the modification message is synchronized to the downstream business system.

4. The method according to claim 3, characterized in that: The method further comprises: Receiving an error correction reminder message sent by the downstream business system; wherein the error correction reminder message is sent by the downstream business system when the modification message is not received within a preset time period after the received record message error is detected; The error correction reminder message is sent to the communication account of the processing personnel corresponding to the erroneous record message to remind the personnel to modify the erroneous record message.

5. The method according to claim 1, characterized in that After returning the acquired record message to the downstream business system, the method further includes: Receiving a second record acquisition request sent by the downstream business system at a starting execution point of an intermediate sub-process in a processing flow of the downstream business; Based on the second record acquisition request, the record message required for executing the intermediate sub-process is obtained, and the record message required for executing the intermediate sub-process is returned to the downstream business system, so that the downstream business system executes the intermediate sub-process based on the received record message; wherein the intermediate sub-process is other sub-processes in the processing flow of the downstream business except the first sub-process.

6. The method according to any one of claims 1 to 5, characterized in that The upstream business system is the corporate credit process management CLPM system, and the downstream business system is the international settlement ISS system; The processing flow of the upstream business includes a business approval sub-flow, a contract application sub-flow and a debt payment sub-flow; the processing flow of the downstream business includes an input sub-flow, an approval sub-flow and a SWIFT message sending sub-flow.

7. A synchronous processing method for upstream and downstream business processes, characterized in that: The method comprises: Periodically sending a first record acquisition request to an upstream business system, so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message contains a business identifier of the upstream business, a process identifier of the corresponding sub-process, and business information; Receiving the record message returned by the upstream business system, and storing the received record message; When receiving the input service number, reading each record message corresponding to the input service number from the stored record messages, and starting to execute the processing flow of the downstream service based on the read record message; The step of sending a first record acquisition request to an upstream business system at a fixed time, so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request, includes: When the current scheduled polling time arrives, determine the current value of the starting primary key number; wherein the initial value of the starting primary key number is the value agreed with the upstream business system, and the subsequent value of the starting primary key number is the primary key number of the last recorded message returned by the upstream business system last time; Generate a first record acquisition request including the starting primary key number; The first record acquisition request is sent to the upstream business system, so that the upstream business system acquires and returns a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages.

8. The method according to claim 7, characterized in that After reading each record message corresponding to the input service number from the stored record messages and before starting to execute the processing flow of the downstream service based on the read record message, the method further includes: Visually displaying the read recorded message; After detecting a confirmation instruction for the displayed record message, an operation of starting to execute a processing flow of a downstream service based on the read record message is triggered.

9. The method according to claim 7, characterized in that: Each of the record messages also includes a validity flag, and the validity flag in the record message sent at the termination execution point of the last sub-process in the upstream business processing process is valid; After starting to execute the processing flow of the downstream business based on the read record message, the method further includes: At the start execution point of the last sub-process in the downstream business processing flow, determining whether a record message with a validity mark as valid is stored; If so, the last sub-process in the processing flow of the downstream business is executed.

10. The method according to claim 7, characterized in that The method further comprises: When an error is detected in a received record message, the processing flow of the downstream business is stopped, and an information error prompt message is sent to the upstream business system, so that the upstream business system prompts the user to modify the erroneous record message after receiving the information error prompt message and obtains a modified message after modifying the erroneous record message; The modification message sent by the upstream service system is received, and the processing flow of the downstream service is continued based on the modification message.

11. The method according to claim 10, characterized in that The method further comprises: If the modification message is not received within a preset time period after detecting that the received record message is erroneous, an error correction reminder message is sent to the upstream business system, so that the upstream business system sends an error correction reminder message to the communication account of the processing personnel corresponding to the erroneous record message to remind the personnel to modify the erroneous record message.

12. The method according to claim 10, characterized in that The detecting that a received record message is wrong comprises: Inputting the service information contained in the received recorded message into a preset message detection model, and determining whether the recorded message is wrong according to the output result of the preset message detection model; The preset message detection model is a model trained in advance based on multiple sample recorded messages using a supervised model training method.

13. The method according to claim 7, characterized in that After starting to execute the processing flow of the downstream business based on the read record message, the method further includes: At the starting execution point of the intermediate sub-process in the processing flow of the downstream business, if the record message required for executing the intermediate sub-process is not stored, sending a second record acquisition message to the upstream business system, so that the upstream business system acquires the record message required for executing the intermediate sub-process based on the second record acquisition request; Based on the record message required for executing the intermediate sub-process returned by the upstream business system, the intermediate sub-process is executed; wherein the intermediate sub-process is the other sub-process in the processing flow of the downstream business except the first sub-process.

14. The method according to any one of claims 7 to 13, characterized in that: The upstream business system is the CLPM system, and the downstream business system is the ISS; The upstream business processing flow includes a business approval sub-flow, a contract application sub-flow and a debt payment sub-flow; the downstream business processing flow includes an input sub-flow, an approval sub-flow and a SWIFT message sending sub-flow.

15. A synchronous processing system for upstream and downstream business processes, characterized in that: The system comprises: an upstream business system, configured to generate and store record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively; wherein each of the record messages contains the business identifier of the upstream business, the process identifier of the corresponding sub-process and business information; upon receiving a first record acquisition request sent by a downstream business system, acquiring at least one stored record message based on the first record acquisition request, and returning the acquired record message to the downstream business system; When storing each of the recorded messages, the primary key number corresponding to the current recorded message is also stored; wherein each of the primary key numbers is used to characterize the generation order of the corresponding recorded message; The acquiring at least one stored record message based on the first record acquisition request includes: Read the starting primary key number carried in the record acquisition request, and acquire a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages; The downstream business system is used to periodically send the first record acquisition request to the upstream business system; receive the record message returned by the upstream business system, and store the received record message; when receiving the input business number, read the record messages corresponding to the input business number from the stored record messages, and start executing the processing flow of the downstream business based on the read record message.

16. A synchronous processing device for upstream and downstream business processes, characterized in that: include: An information generation module, used to generate and store record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively; wherein each of the record messages contains the business identifier of the upstream business, the process identifier of the corresponding sub-process and business information; An information sending module, configured to, upon receiving a first record acquisition request sent by a downstream business system, acquire at least one stored record message based on the first record acquisition request, and return the acquired record message to the downstream business system, so that the downstream business system starts executing a processing flow of the downstream business based on the received record message; The information generation module is specifically used to store the primary key number corresponding to the current record message when storing each record message; wherein each primary key number is used to represent the generation order of the corresponding record message; The information sending module is specifically used to read the starting primary key number carried in the record acquisition request, and obtain a preset number of record messages generated after the record message corresponding to the starting primary key number from the stored record messages.

17. A synchronous processing device for upstream and downstream business processes, characterized in that: include: An information request module, used for periodically sending a first record acquisition request to an upstream business system, so that the upstream business system acquires and returns at least one stored record message based on the first record acquisition request; wherein the upstream business system generates and stores record messages at the start execution point and the end execution point of each sub-process in the processing flow of the upstream business, respectively, and each record message contains a business identifier of the upstream business, a process identifier of the corresponding sub-process, and business information; An information storage module, used for receiving the record message returned by the upstream business system and storing the received record message; A business processing module, configured to, upon receiving an input business number, read each record message corresponding to the input business number from the stored record messages, and start executing a processing flow of a downstream business based on the read record message; When storing each of the recorded messages, the primary key number corresponding to the current recorded message is also stored; wherein each of the primary key numbers is used to characterize the generation order of the corresponding recorded message; The acquiring and returning at least one stored record message based on the first record acquisition request includes: The starting primary key number carried in the record acquisition request is read, and a preset number of record messages generated after the record message corresponding to the starting primary key number are acquired from the stored record messages.

18. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the method for synchronously processing upstream and downstream business processes as described in any one of claims 1 to 14 is implemented.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, it implements the method for synchronously processing upstream and downstream business processes as described in any one of claims 1 to 14.

Images