Message processing method and device, computer device, readable storage medium and program product

Abstract

The application relates to the field of data processing, and particularly discloses a message processing method and device, computer equipment, a readable storage medium and a program product. The method comprises the following steps: obtaining a to-be-sent message, determining whether the to-be-sent message is an abnormal message according to message information of the to-be-sent message, and in the case that the to-be-sent message is a non-abnormal message, sending a query request to a message receiving end, then receiving a query result sent by the message receiving end, and in the case that the query result is that the message receiving end has not received the to-be-sent message, sending the to-be-sent message to the message receiving end; the query request is used for querying whether the message receiving end has received the to-be-sent message. The above method avoids sending abnormal to-be-sent messages to the message receiving end through twice abnormal message inspection, i.e., the first abnormal message inspection is performed by the message sending end according to the message information of the to-be-sent message, and the second query is performed on whether the message receiving end has received the to-be-sent message.

Description

Message processing methods, apparatus, computer equipment, readable storage media and program products Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a message processing method, apparatus, computer equipment, readable storage medium, and program product. Background Technology

[0002] Against the backdrop of the globalization of large financial institutions' operations and the booming development of financial technology, various financial institutions need to exchange messages based on their respective business. However, when exchanging messages between financial institutions, there may be abnormal message transmission situations (such as duplicate message transmission, missing message transmission, etc.). In particular, the abnormal transmission of duplicate messages may cause huge losses to various financial institutions.

[0003] Currently, in the event of a message duplication anomaly, technicians need to obtain the message sending logs and check each message sending record in the logs to identify the duplicated messages and then recall them.

[0004] Therefore, how to efficiently avoid sending duplicate messages to the receiving end has become an urgent problem to be solved. Summary of the Invention

[0005] Therefore, it is necessary to provide a message processing method, apparatus, computer equipment, readable storage medium, and program product that can efficiently avoid sending duplicate messages, in order to address the above-mentioned technical problems.

[0006] Firstly, this application provides a message processing method applied at a message sending end, comprising:

[0007] Obtain the message to be sent;

[0008] Based on the message information of the message to be sent, determine whether the message to be sent is an abnormal message;

[0009] If the message to be sent is not an abnormal message, a query request is sent to the message receiver; the query request is used to check whether the message receiver has received the message to be sent.

[0010] Receive the query result sent by the message receiver, and if the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0011] In one embodiment, the aforementioned message information includes the sending time, settlement date, status, and number of the message to be sent. Determining whether the message to be sent is an abnormal message based on this message information includes:

[0012] Based on the sending time, settlement date, and status of the message to be sent, determine whether the message to be sent meets the sending conditions; the sending conditions include whether the sending time is within the preset time range, or whether the settlement date conforms to the preset settlement date rules, or whether the status is an abnormal status;

[0013] If the message to be sent does not meet the sending conditions, then the message to be sent is determined to be an abnormal message;

[0014] If the message to be sent meets the sending conditions, then determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent.

[0015] In one embodiment, determining whether a message to be sent is an abnormal message based on its status and number includes:

[0016] Determine whether the status of the message to be sent is temporary;

[0017] If so, then the message to be sent is determined to be a non-abnormal message;

[0018] If not, determine whether the message to be sent is an abnormal message based on the message number.

[0019] In one embodiment, determining whether a message to be sent is an abnormal message based on the message number includes:

[0020] Retrieve the message records of sent messages, and query whether there is a message number to be sent in the message records of sent messages;

[0021] If it exists, determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent;

[0022] If it does not exist, the message to be sent will be determined as a non-abnormal message.

[0023] In one embodiment, determining whether a message to be sent is an abnormal message based on a record in the message log that matches the message number to be sent includes:

[0024] If a record in the message record that matches the number of the message to be sent meets the first preset condition, then the message to be sent is identified as an abnormal message; the first preset condition includes a processing status of successful processing, or a response status of successful processing and a processing status of invalidation.

[0025] If a record in the message log that matches the number of the message to be sent meets the second preset condition, then the message to be sent is determined to be a non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

[0026] In one embodiment, the method further includes:

[0027] If the message to be sent is an abnormal message, update the status of the message to be sent to the duplicate sending status and stop sending the message to the message receiver.

[0028] In one embodiment, the method further includes:

[0029] If the query result shows that the message receiver has a message with the same number as the message to be sent, the status of the message to be sent is updated to the sent status, and the sending of the message to be sent to the message receiver is stopped.

[0030] In one embodiment, the method further includes:

[0031] Receive message reply information sent by the message receiving end; message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information;

[0032] If the message reply message is a message reception success message, then the status of the message to be sent will be updated to the sent status, and the status of the message to be sent will be recorded as sent successfully in the message record of the sent messages.

[0033] If the message reply message is a message reception failure message, then the status of the message to be sent will be updated to the sending failure status, and the status of the message to be sent will be recorded as the sending failure status in the message record of the sent messages.

[0034] If the message reply is "Message received unknown" or "Message sent timed out", an abnormal message alarm will be issued, and the status of the message to be sent will be recorded as "Message received unknown" or "Message sent timed out" in the message record of the sent messages.

[0035] Secondly, this application provides a message processing method applied at a message receiving end, including:

[0036] Receive query requests sent by the message sender;

[0037] Based on the number of the message to be sent carried in the query request, the message receiving database at the message receiving end is searched to see if there is a message with the same number as the message to be sent, and the query result is obtained.

[0038] Send the query results to the message sender;

[0039] Receive messages to be sent by the message sender.

[0040] In one embodiment, the method further includes:

[0041] Obtain the status of the message to be sent, and determine the message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown, or message transmission timeout.

[0042] Thirdly, this application also provides a message processing apparatus, comprising:

[0043] The acquisition module is used to acquire messages to be sent.

[0044] The determination module is used to determine whether a message to be sent is an abnormal message based on the message information of the message to be sent;

[0045] The first sending module is used to send a query request to the message receiving end when the message to be sent is a non-abnormal message; the query request is used to check whether the message receiving end has received the message to be sent.

[0046] The second sending module is used to receive the query result sent by the message receiving end, and if the query result indicates that the message receiving end has not received the message to be sent, it sends the message to be sent to the message receiving end.

[0047] In one embodiment, the message information includes the sending time, delivery date, status, and number of the message to be sent, and the determining module includes:

[0048] The first determining unit is used to determine whether the message to be sent meets the sending conditions based on the sending time, settlement date and status of the message to be sent; the sending conditions include whether the sending time is within a preset time range, or whether the settlement date conforms to the preset settlement date rules, or whether the status is an abnormal status;

[0049] The second determining unit is used to determine that the message to be sent is an abnormal message if the message to be sent does not meet the sending conditions.

[0050] The third determining unit is used to determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent if the message to be sent meets the sending conditions.

[0051] In one embodiment, the third determining unit is specifically used to: determine whether the state of the message to be sent is temporary; if so, determine that the message to be sent is a non-abnormal message; if not, determine whether the message to be sent is an abnormal message based on the number of the message to be sent.

[0052] In one embodiment, the third determining unit is specifically used to: obtain the message record of the sent message and query whether there is a number of the message to be sent in the message record of the sent message; if there is, determine whether the message to be sent is an abnormal message based on the record in the message record that is consistent with the number of the message to be sent; if there is no record, determine the message to be sent as a non-abnormal message.

[0053] In one embodiment, the third determining unit is specifically used to: if a record in the message record that matches the number of the message to be sent meets a first preset condition, then the message to be sent is determined to be an abnormal message; the first preset condition includes a processing status of processing success, or a response status of processing success and a processing status of failure; if a record in the message record that matches the number of the message to be sent meets a second preset condition, then the message to be sent is determined to be a non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

[0054] In one embodiment, the above-mentioned device further includes: a first update module, configured to update the status of the message to be sent to a duplicate sending status and stop sending the message to be sent to the message receiving end when the message to be sent is an abnormal message.

[0055] In one embodiment, the above-mentioned device further includes: a second update module, configured to update the status of the message to be sent to a sent status and stop sending the message to be sent to the message receiver when the query result shows that there is a message with the same number as the message to be sent at the message receiver.

[0056] In one embodiment, the above-described apparatus further includes:

[0057] The receiving module receives message reply information sent by the message receiving end; the message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information;

[0058] The third update module updates the status of the message to be sent to the sent status if the message reply information is a message reception success information, and records the status of the message to be sent as sent success in the message record of the sent message.

[0059] The fourth update module updates the status of the message to be sent to the sending failure status if the message reply information is a message reception failure information, and records the status of the message to be sent as a sending failure status in the message record of the sent messages.

[0060] The fifth update module, if the message reply information is unknown message or message transmission timeout information, will issue an abnormal message alarm information and record the status of the message to be sent as unknown message reception or transmission timeout status in the message record of the sent messages.

[0061] Fourthly, a message processing apparatus is also provided, applied at a message receiving end, including:

[0062] The first receiving module is used to receive query requests sent by the message sender;

[0063] The acquisition module is used to query the message receiving database of the message receiving end to see if there is a message with the same number as the message to be sent, based on the number of the message to be sent carried in the query request, and to obtain the query result.

[0064] The sending module is used to send the query results to the message sending end;

[0065] The second receiving module is used to receive messages to be sent by the message sending end.

[0066] In one embodiment, the above-mentioned apparatus further includes: a determining module, configured to obtain the status of the message to be sent, and determine message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown, or message transmission timeout.

[0067] Fifthly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0068] Obtain the message to be sent;

[0069] Based on the message information of the message to be sent, determine whether the message to be sent is an abnormal message;

[0070] If the message to be sent is not an abnormal message, a query request is sent to the message receiver; the query request is used to check whether the message receiver has received the message to be sent.

[0071] Receive the query result sent by the message receiver, and if the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0072] Sixthly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0073] Receive query requests sent by the message sender;

[0074] Based on the number of the message to be sent carried in the query request, the message receiving database at the message receiving end is searched to see if there is a message with the same number as the message to be sent, and the query result is obtained.

[0075] Send the query results to the message sender;

[0076] Receive messages to be sent by the message sender.

[0077] Seventhly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0078] Obtain the message to be sent;

[0079] Based on the message information of the message to be sent, determine whether the message to be sent is an abnormal message;

[0080] If the message to be sent is not an abnormal message, a query request is sent to the message receiver; the query request is used to check whether the message receiver has received the message to be sent.

[0081] Receive the query result sent by the message receiver, and if the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0082] Eighthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0083] Receive query requests sent by the message sender;

[0084] Based on the number of the message to be sent carried in the query request, the message receiving database at the message receiving end is searched to see if there is a message with the same number as the message to be sent, and the query result is obtained.

[0085] Send the query results to the message sender;

[0086] Receive messages to be sent by the message sender.

[0087] Ninthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0088] Obtain the message to be sent;

[0089] Based on the message information of the message to be sent, determine whether the message to be sent is an abnormal message;

[0090] If the message to be sent is not an abnormal message, a query request is sent to the message receiver; the query request is used to check whether the message receiver has received the message to be sent.

[0091] Receive the query result sent by the message receiver, and if the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0092] Ninthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0093] Receive query requests sent by the message sender;

[0094] Based on the number of the message to be sent carried in the query request, the message receiving database at the message receiving end is searched to see if there is a message with the same number as the message to be sent, and the query result is obtained.

[0095] Send the query results to the message sender;

[0096] Receive messages to be sent by the message sender.

[0097] The aforementioned message processing method, apparatus, computer equipment, readable storage medium, and program product employ two abnormal message checks: first, the message sender checks for abnormal messages based on the message information to be sent; second, the message receiver checks whether it has already received the message to be sent. This avoids sending abnormal messages to the message receiver, preventing potential adverse effects such as information overload. Furthermore, for special messages in the financial industry (e.g., messages with large single payment amounts), the aforementioned method can effectively prevent duplicate messages from being sent to the receiver, greatly improving the user experience. Attached Figure Description

[0098] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0099] Figure 1 is an application environment diagram of a message processing method in one embodiment;

[0100] Figure 2 is a flowchart of a message processing method in one embodiment;

[0101] Figure 3 is a flowchart illustrating the message processing method in another embodiment;

[0102] Figure 4 is a flowchart illustrating the message processing method in another embodiment;

[0103] Figure 5 is a flowchart illustrating the message processing method in another embodiment;

[0104] Figure 6 is a flowchart illustrating the message processing method in another embodiment;

[0105] Figure 7 is a flowchart illustrating the message processing method in another embodiment;

[0106] Figure 8 is a flowchart illustrating the message processing method in another embodiment;

[0107] Figure 9 is a flowchart illustrating the message processing method in another embodiment;

[0108] Figure 10 is a flowchart illustrating a message processing method in another embodiment;

[0109] Figure 11 is a flowchart illustrating a message processing method in another embodiment;

[0110] Figure 12 is a structural block diagram of a message processing device in one embodiment;

[0111] Figure 13 is a structural block diagram of a message processing device in one embodiment;

[0112] Figure 14 is an internal structure diagram of a computer device in one embodiment. Detailed Implementation

[0113] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. It should be noted that existing industry solutions such as software, components, and models may be mentioned in the embodiments of this application. These should be considered exemplary and are intended only to illustrate the feasibility of implementing the technical solutions of this application, but do not imply that the applicant has already used or necessarily used such solutions.

[0114] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with relevant regulations. The acquisition, storage, use and processing of data in the technical solution of this application all comply with the relevant provisions of national laws and regulations.

[0115] Against the backdrop of the globalization of large financial institutions' operations and the booming development of financial technology, various financial institutions need to exchange messages based on their respective business. However, when exchanging messages between financial institutions, there may be abnormal message transmission situations (such as duplicate message transmission, missing message transmission, etc.). In particular, the abnormal transmission of duplicate messages may cause huge losses to various financial institutions.

[0116] Currently, when message duplication occurs, technicians need to obtain the message transmission logs and check each message transmission record in the logs to identify and retract the duplicated messages. Therefore, efficiently preventing the transmission of duplicate messages is a pressing issue. This application aims to solve this problem.

[0117] After introducing the background technology of the message processing method provided in the embodiments of this application, the implementation environment involved in the message processing method provided in the embodiments of this application will be briefly described below. The message processing method provided in the embodiments of this application can be applied to the implementation environment shown in FIG1. ​​The implementation environment shown in FIG1 includes at least a message sending end 101 and a message receiving end 102. It should be noted that either end in the implementation environment can be designated as the message sending end 101 or the message receiving end 102, and all other ends in the implementation environment besides either end can be identified as the message receiving end 102 and the message sending end 101. In the implementation environment, the message sending end 101 can send a task instruction to the message receiving end 102 to instruct the message receiving end 102 to perform the corresponding task according to the instruction, and the message receiving end 102 can also send a task instruction to the message sending end 101 to instruct the message sending end 101 to perform the corresponding task according to the instruction. In addition, message sender 101 can also send messages to message receiver 102, and message receiver 102 can also send messages to message sender 101. It should be noted that message sender 101 and message receiver 102 can be connected through a communication network.

[0118] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0119] In one embodiment, as shown in FIG2, a message processing method is provided. Taking the application of this method to the message sender 101 in FIG1 as an example, the method includes the following steps:

[0120] S201. Obtain the message to be sent.

[0121] In this embodiment of the application, when it is necessary to send a message to the message receiving end, in order to avoid the repeated transmission of the message, it is necessary to perform a duplicate check on the message to be sent. At this time, one or more messages to be sent can be obtained from the message report to be sent at the message sending end, or the message list to be sent can be queried to obtain any one message to be sent or all messages to be sent in the message list.

[0122] S202. Determine whether the message to be sent is an abnormal message based on the message information of the message to be sent.

[0123] Among them, abnormal messages refer to duplicate messages, that is, before the message to be sent is sent, the message sender has already sent a message that is identical to the message to be sent to the message receiver.

[0124] The message information includes the message sending time, delivery date, status, and number.

[0125] In this embodiment of the application, after obtaining the message to be sent, it is possible to determine whether the message to be sent is an abnormal message based on the message's sending time, settlement date, status, and number.

[0126] Optionally, anomaly checks can be performed on the messages to be sent in sequence according to their sending time, settlement date, status, and number to determine whether the messages to be sent are abnormal.

[0127] Optionally, anomaly detection can be performed on the message to be sent based on at least one of the following: sending time, settlement date, status, and number, to determine whether the message to be sent is an abnormal message.

[0128] S203. If the message to be sent is not an abnormal message, send a query request to the message receiving end.

[0129] The query request is used to check whether the message receiver has received the message to be sent.

[0130] In this embodiment of the application, if the message to be sent is determined to be a non-abnormal message based on the message information of the message to be sent, the message sender can send a query request to the message receiver to query whether the message receiver has received the message to be sent.

[0131] Optionally, the query request may include the identification information (e.g., number information) of the message to be sent. After the message sender sends the query request to the message receiver, the message receiver queries its message database based on the number information of the message to be sent in the query request to see if there is a message with the same number as the message to be sent. If it exists, it means that the message receiver has received a message with the same number as the message to be sent before, and a query result indicating that the message to be sent has been received is generated. If it does not exist, it means that the message receiver has not received a message with the same number as the message to be sent before, and a query result indicating that the message to be sent has not been received is generated.

[0132] S204. Receive the query result sent by the message receiving end, and if the query result indicates that the message receiving end has not received the message to be sent, send the message to be sent to the message receiving end.

[0133] In this embodiment of the application, after the message receiving end generates a query result and sends the query result to the message receiving end, the message sending end receives the query result sent by the message receiving end, and if the query result indicates that the message receiving end has not received the message to be sent, the message to be sent is sent to the message receiving end.

[0134] The message processing method provided in this application is applied to a message sending end. It acquires a message to be sent, determines whether the message is abnormal based on its message information, and if the message is not abnormal, sends a query request to a message receiving end. It then receives the query result from the message receiving end. If the query result indicates that the message receiving end has not received the message, it sends the message to the message receiving end. The query request is used to check whether the message receiving end has received the message. This method uses two abnormal message checks: first, the message sending end checks for abnormal messages based on the message information; second, it checks whether the message receiving end has received the message. This avoids sending abnormal messages to the message receiving end, preventing potential information overload and other adverse effects. Furthermore, for special messages in the financial industry (e.g., messages with large single payment amounts), this method effectively avoids sending duplicate messages to the receiving end, greatly improving user experience.

[0135] In one embodiment, based on the embodiment shown in Figure 2, the above message information includes the message sending time, delivery date, status, and number. The process of determining whether the message to be sent is an abnormal message can be described, as shown in Figure 3. The above S202, "Determining whether the message to be sent is an abnormal message based on the message information of the message to be sent," includes:

[0136] S301. Based on the sending time, settlement date and status of the message to be sent, determine whether the message to be sent meets the sending conditions. If the message to be sent does not meet the sending conditions, then execute S302 below. If the message to be sent meets the sending conditions, then execute S303 below.

[0137] The sending conditions include whether the sending time is within a preset time range, whether the settlement date conforms to a preset settlement date rule, or whether the status is abnormal. For example, the preset time range refers to the channel window time range of the message sender and receiver; the preset settlement date rule refers to the settlement date rule for the corresponding currency in the message to be sent; and abnormal status includes frozen status, abnormal status, etc. Determining whether the message to be sent meets the sending conditions is to prevent modification by the interface during message processing.

[0138] In this embodiment of the application, after obtaining the message to be sent, it can be determined in sequence whether the sending time of the message to be sent is within a preset time range, whether the settlement date conforms to the preset settlement date rule, and whether the status of the message to be sent is an abnormal state. If the sending time of the message to be sent is within the preset time range, the settlement date conforms to the preset settlement date rule, and the status of the message to be sent is not abnormal, then the following S302 is executed. If the sending time of the message to be sent is within the preset time range, the settlement date conforms to the preset settlement date rule, and the status of the message to be sent is not abnormal, then the following S303 is executed.

[0139] S302. Determine that the message to be sent is an abnormal message.

[0140] In this embodiment of the application, if the sending time of the message to be sent is within a preset time range, the delivery date conforms to the preset delivery date rules, and the status of the message to be sent is not abnormal, then the message to be sent is determined to be an abnormal message.

[0141] S303. Determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent.

[0142] In this embodiment of the application, if the sending time of the message to be sent is not within the preset time range, or the delivery date does not conform to the preset delivery date rule, or the status of the message to be sent is abnormal, then the status and number of the message to be sent are used to further determine whether the message to be sent is an abnormal message.

[0143] It should be noted that as long as it is determined that the sending time of the message to be sent is not within the preset time range, or the settlement date does not conform to the preset settlement date rule, or the status of the message to be sent is an abnormal status, it is possible to continue to determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent.

[0144] Optionally, it can be determined whether the message to be sent is an abnormal message based on whether the status of the message to be sent meets a preset status, or based on whether the number of the message to be sent meets a preset condition.

[0145] Optionally, the following provides a specific implementation method for determining whether a message to be sent is an abnormal message based on its status and number, as shown in Figure 4. The above-mentioned S303 "determining whether a message to be sent is an abnormal message based on its status and number" includes:

[0146] S401. Determine whether the state of the message to be sent is temporary. If the state of the message to be sent is temporary, then execute S402 below. If the state of the message to be sent is not temporary, then execute S403 below.

[0147] In this embodiment of the application, when it is determined that the message to be sent meets the sending conditions, the message sending end can update the state of the message to be sent, that is, update the message to be sent from the original state to the temporary state. After the state update is completed, it is further determined whether the state of the message to be sent has been successfully updated to the temporary state. If the state of the message to be sent is successfully updated to the temporary state, then the following S402 is executed. If the state of the message to be sent is not successfully updated to the temporary state, then the following S403 is executed.

[0148] S402. Determine that the message to be sent is a non-abnormal message.

[0149] In this embodiment of the application, if the status of the message to be sent is successfully updated to the temporary state, the message to be sent is determined to be a non-abnormal message, and the next judgment step is performed.

[0150] S403. Determine whether the message to be sent is an abnormal message based on the message number.

[0151] In this embodiment of the application, if the status of the message to be sent is not successfully updated to the temporary state, it is necessary to further determine whether the message to be sent is an abnormal message based on the number of the message to be sent.

[0152] Optionally, the following provides a specific implementation method for determining whether a message to be sent is an abnormal message, as shown in Figure 5. The above-mentioned S403 "determining whether a message to be sent is an abnormal message based on the message number" includes:

[0153] S501. Obtain the message record of the sent messages and query whether there is a message number to be sent in the message record of the sent messages. If it exists, execute S502 below. If it does not exist, execute S503 below.

[0154] Among them, message records refer to the response status information and processing status information of sent messages. For example, the processing status information of a sent message is "processed successfully", or the response status information of a sent message is "response successful and processing status information is "processing failed", or the response status information of a sent message is "response failed", or the response status information of a sent message is "response successful and processing status information is "failed".

[0155] In this embodiment of the application, the message record of the sent message can be obtained from the message sending end, and according to the number of the message to be sent, the message record of the sent message can be queried to see if the number of the message to be sent exists. If the number of the message to be sent exists in the message record of the sent message, then S502 is executed below; if the number of the message to be sent does not exist in the message record of the sent message, then S503 is executed below.

[0156] S502. Determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent.

[0157] In this embodiment of the application, if there is a number of a message to be sent in the message record of the sent message, then it is further determined whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent.

[0158] Optionally, the determination of whether a message to be sent is an abnormal message can be made based on the following rules, where the record in the message record that matches the number of the message to be sent is used to determine whether the message to be sent is an abnormal message. As shown in Figure 6, the above S502 "determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent" includes:

[0159] S601. If a record in the message record that has the same number as the message to be sent meets the first preset condition, then the message to be sent is determined to be an abnormal message.

[0160] The first preset condition includes a processing status of successful processing, or a response status of successful processing and a processing status of failed processing.

[0161] In this embodiment of the application, if the record in the message record that matches the number of the message to be sent includes a processing status of "processing successful", or a response status of "processing successful" and a processing status of "failure", then the message to be sent is directly determined to be an abnormal message.

[0162] S602. If a record in the message record that has the same number as the message to be sent meets the second preset condition, then the message to be sent is determined to be a non-abnormal message.

[0163] The second preset condition includes either a response status of processing failure or a response status of processing success and a processing status of processing failure.

[0164] In this embodiment of the application, if the record in the message record that matches the number of the message to be sent includes a response status of processing failure, or a response status of processing success and a processing status of processing failure, then the message to be sent is directly determined to be a non-abnormal message.

[0165] S503. Determine the message to be sent as a non-abnormal message.

[0166] In this embodiment of the application, if the number of the message to be sent does not exist in the message record of the sent message, the message to be sent is directly determined as a non-abnormal message.

[0167] The method for determining whether a message to be sent is an abnormal message provided in this application improves the accuracy of the message sender in determining whether a message to be sent is an abnormal message by judging information such as the message sending time, delivery date, status and number of the message to be sent. This further avoids the possibility of sending abnormal messages to the message receiver.

[0168] In one embodiment, based on the embodiment shown in FIG2, as shown in FIG7, the above method further includes:

[0169] S205. If the message to be sent is an abnormal message, update the status of the message to be sent to the duplicate sending status and stop sending the message to be sent to the message receiving end.

[0170] In this embodiment of the application, if the message to be sent is determined to be an abnormal message based on the message information of the message to be sent, the status of the message to be sent can be directly updated to the duplicate sending status, and the message to be sent to the message receiving end can be stopped.

[0171] The message processing method provided in this application updates the status of abnormal messages to be sent to a retransmission status, which can prevent the mistransmission of messages in the future and thus reduce certain economic losses. In addition, stopping the transmission of abnormal messages to be sent to the message receiving end can prevent the message from being retransmitted, improving the user experience. Furthermore, it can also prevent unknown anomalies from occurring during subsequent processing, which could cause the message to fail to update from a sent status to a retransmission status, resulting in subsequent retransmission.

[0172] In one embodiment, based on the embodiment shown in FIG2, as shown in FIG8, the above method further includes:

[0173] S206. Receive message reply information sent by the receiving end.

[0174] The message response information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information.

[0175] In this embodiment of the application, after the message sender sends the message to be sent to the message receiver, the message receiver generates corresponding message reply information according to the reception status of the message to be sent, and returns the message reply information to the message sender so that the message sender can receive the message reply information sent by the message receiver.

[0176] Optionally, if the message receiver successfully receives the message to be sent, it generates a message reception success message; if the message receiver fails to receive the message to be sent, it generates a message reception failure message; if the message receiver does not receive the message to be sent, it generates a message reception unknown message; if the message receiver times out receiving the message to be sent, it generates a message reception timeout message.

[0177] S207. If the message reply message is a message reception success message, then update the status of the message to be sent to the sent status, and record the status of the message to be sent as the sent success status in the message record of the sent messages.

[0178] S208. If the message reply information is a message reception failure information, then update the status of the message to be sent to the sending failure status, and record the status of the message to be sent as the sending failure status in the message record of the sent messages.

[0179] S209. If the message reply information is message reception unknown or message transmission timeout, then issue an abnormal message alarm and record the status of the message to be sent as message reception unknown or transmission timeout in the message record of the sent messages.

[0180] In this embodiment, if the message reply information is a message reception success message, the status of the message to be sent is updated to the sent status, and the status of the message to be sent is recorded as a successful send in the message record of the sent messages. If the message reply information is a message reception failure message, the status of the message to be sent is updated to the send failure status, and the status of the message to be sent is recorded as a send failure in the message record of the sent messages. If the message reply information is a message reception unknown message or a message sending timeout message, an abnormal message alarm message is issued, and the status of the message to be sent is recorded as a message reception unknown state or a sending timeout state in the message record of the sent messages.

[0181] The message processing method provided in this application modifies the status of a message to be sent by message reply information and records the modified status of the message to be sent in the message record of sent messages, so as to serve as a basis for review when performing message duplication checks in the future, thereby improving the message processing efficiency.

[0182] In one embodiment, as shown in FIG9, a message processing method is provided. Taking the application of this method to the message receiver 102 in FIG1 as an example, the method includes the following steps:

[0183] S601, Receive the query request sent by the message sender.

[0184] In this embodiment of the application, after the message sender sends a query request to the message receiver, the message receiver receives the query request.

[0185] S602. Based on the number of the message to be sent carried in the query request, query the message receiving database of the message receiving end to see if there is a message with the same number as the message to be sent, and obtain the query result.

[0186] The message number to be sent is, for example, a unique service number or a global tracking number plus a sequence number.

[0187] In this embodiment of the application, after receiving a query request sent by the message sender, the message receiver can query the message receiving database of the message receiver to see if there is a message with the same number as the message to be sent, based on the number of the message to be sent carried in the query request. The query result is either that there is a message with the same number as the message to be sent, or that there is no message with the same number as the message to be sent.

[0188] S603. Send the query results to the message sending end.

[0189] In this embodiment of the application, after obtaining the query result that there is a message with the same number as the message to be sent, or the query result that there is no message with the same number as the message to be sent, the message receiving end can send the query result to the message sending end.

[0190] S604. Receive the message to be sent by the message sender.

[0191] In this embodiment of the application, after the message sender sends the message to be sent to the message receiver, the message receiver receives the message to be sent by the message sender, generates corresponding message reply information according to the reception status of the message to be sent, and feeds back the message reply information to the message sender.

[0192] This method employs two abnormal message checks: first, the message sender checks for abnormal messages based on the message information to be sent; second, it checks whether the message receiver has already received the message to be sent. This avoids sending abnormal messages to the message receiver, preventing potential adverse effects such as information overload. Furthermore, for special messages in the financial industry (e.g., messages with large single payment amounts), this method can effectively prevent duplicate messages from being sent to the receiver, greatly improving the user experience.

[0193] In one embodiment, based on the embodiment shown in FIG9, as shown in FIG10, the above method further includes:

[0194] S605. Obtain the status of the message to be sent, and determine the message reply information based on the status of the message to be sent.

[0195] The message response information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information.

[0196] In this embodiment of the application, after the message receiving end receives the message to be sent by the message sending end, it obtains the status of the message to be sent, generates corresponding message reply information according to the status of the message to be sent, and sends the corresponding message reply information to the message sending end.

[0197] Optionally, if the status of the message to be sent is a successful reception status, then a corresponding message reception success message is generated; if the status of the message to be sent is a failed reception status, then a corresponding message reception failure message is generated; if the status of the message to be sent is an unknown reception status, then a corresponding message reception unknown message is generated; if the status of the message to be sent is a timeout reception status, then a corresponding message reception timeout message is generated.

[0198] In one embodiment, as shown in Figure 11, a message processing method is also provided, including:

[0199] S10. Obtain the message to be sent;

[0200] S11. Based on the sending time, settlement date and status of the message to be sent, determine whether the message to be sent meets the sending conditions. If the message to be sent does not meet the sending conditions, execute S12-S13. If the message to be sent meets the sending conditions, execute S14.

[0201] S12, then the message to be sent is determined to be an abnormal message;

[0202] S13. If the message to be sent is an abnormal message, update the status of the message to be sent to the duplicate sending status and stop sending the message to be sent to the message receiving end.

[0203] S14. Determine whether the status of the message to be sent is temporary. If yes, proceed to S15; otherwise, proceed to S16.

[0204] S15. Determine that the message to be sent is a non-abnormal message;

[0205] S16. Obtain the message record of the sent messages, and check if there is a message number to be sent in the message record of the sent messages. If it exists, execute S17; if it does not exist, execute S18.

[0206] S17. Determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent;

[0207] S18. Determine the message to be sent as a non-abnormal message;

[0208] S19. If the message to be sent is a non-abnormal message, send a query request to the message receiving end.

[0209] S20. Receive the query request sent by the message sender;

[0210] S21. Based on the number of the message to be sent carried in the query request, query the message receiving database of the message receiving end to see if there is a message with the same number as the message to be sent, and obtain the query result.

[0211] S22. Send the query results to the message sender;

[0212] S23. Receive the query results sent by the receiving end of the message;

[0213] S24. If the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0214] S25. Receive the message to be sent by the message sender;

[0215] S26. Obtain the status of the message to be sent, and determine the message reply information based on the status of the message to be sent;

[0216] S27. Send the message reply information to the message sender;

[0217] S28. Receive the message reply information sent by the message receiver and modify the status of the message to be sent according to the message reply information;

[0218] S29. If the query result shows that the message receiver has a message with the same number as the message to be sent, update the status of the message to be sent to the sent status and stop sending the message to be sent to the message receiver.

[0219] The above method employs two abnormal message checks: first, the message sender checks for abnormal messages based on the message information to be sent; second, it checks whether the message receiver has already received the message to be sent. This avoids sending abnormal messages to the message receiver, preventing potential adverse effects such as information overload. Furthermore, for special messages in the financial industry (e.g., messages with large single payment amounts), this method can effectively prevent duplicate messages from being sent to the receiver, greatly improving the user experience.

[0220] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0221] Based on the same inventive concept, this application also provides a message processing apparatus for implementing the message processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more message processing apparatus embodiments provided below can be found in the limitations of the message processing method described above, and will not be repeated here.

[0222] In an exemplary embodiment, as shown in FIG12, a message processing apparatus is provided, including: an acquisition module 10, a determination module 11, a first sending module 12, and a second sending module 13, wherein:

[0223] The acquisition module 10 is used to acquire the message to be sent.

[0224] The determination module 11 is used to determine whether the message to be sent is an abnormal message based on the message information of the message to be sent.

[0225] The first sending module 12 is used to send a query request to the message receiving end when the message to be sent is a non-abnormal message; the query request is used to query whether the message receiving end has received the message to be sent.

[0226] The second sending module 13 is used to receive the query result sent by the message receiving end, and send the message to be sent to the message receiving end if the query result indicates that the message receiving end has not received the message to be sent.

[0227] In an exemplary embodiment, the aforementioned message information includes the sending time, delivery date, status, and number of the message to be sent. The aforementioned determining module 11 includes: a first determining unit, a second determining unit, and a third determining unit, wherein:

[0228] The first determining unit is specifically used to determine whether the message to be sent meets the sending conditions based on the sending time, settlement date and status of the message to be sent; the sending conditions include whether the sending time is within a preset time range, or whether the settlement date conforms to the preset settlement date rules, or whether the status is an abnormal status;

[0229] The second determining unit is specifically used to determine that the message to be sent is an abnormal message if the message to be sent does not meet the sending conditions.

[0230] The third determining unit is specifically used to determine whether a message to be sent is an abnormal message based on its status and number, if the message to be sent meets the sending conditions.

[0231] In an exemplary embodiment, the third determining unit is further configured to determine whether the state of the message to be sent is temporary; if so, the message to be sent is determined to be a non-abnormal message; if not, the message to be sent is determined to be an abnormal message based on the number of the message to be sent.

[0232] In an exemplary embodiment, the third determining unit is further configured to obtain the message record of the sent message and query whether there is a number of the message to be sent in the message record of the sent message; if there is, determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent; if there is no record, determine the message to be sent as a non-abnormal message.

[0233] In an exemplary embodiment, the third determining unit is further configured to determine the message to be sent as an abnormal message if a record in the message record that matches the number of the message to be sent meets a first preset condition; the first preset condition includes a processing status of processing success, or a response status of processing success and a processing status of failure; if a record in the message record that matches the number of the message to be sent meets a second preset condition, the message to be sent is determined as a non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

[0234] In an exemplary embodiment, the above apparatus further includes: a first update module, configured to update the status of the message to be sent to a duplicate sending status and stop sending the message to be sent to the message receiving end when the message to be sent is an abnormal message.

[0235] In an exemplary embodiment, the above apparatus further includes: a second update module, configured to update the status of the message to be sent to a sent status and stop sending the message to be sent to the message receiver when the query result indicates that there is a message with the same number as the message to be sent at the message receiver.

[0236] In an exemplary embodiment, the above-described apparatus further includes: a receiving module, a third updating module, a fourth updating module, and a fifth updating module, wherein:

[0237] The receiving module is used to receive message reply information sent by the message receiving end; the message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information;

[0238] The third update module is used to update the status of the message to be sent to the sent status if the message reply information is a message reception success information, and to record the status of the message to be sent as a sent success status in the message record of the sent messages.

[0239] The fourth update module is used to update the status of the message to be sent to the sending failure status if the message reply information is a message reception failure information, and to record the status of the message to be sent to the sending failure status in the message record of the sent messages.

[0240] The fifth update module is used to issue an abnormal message alarm if the message reply information is unknown or the message transmission timeout information, and to record the status of the message to be sent as unknown or timeout in the message record of the sent messages.

[0241] In an exemplary embodiment, as shown in FIG13, a message processing apparatus is provided, comprising: a first receiving module 20, an acquisition module 21, a sending module 22, and a second receiving module 23, wherein:

[0242] The first receiving module 20 is used to receive query requests sent by the message sending end;

[0243] The acquisition module 21 is used to query the message receiving database of the message receiving end to see if there is a message with the same number as the message to be sent, based on the number of the message to be sent carried in the query request, and to obtain the query result.

[0244] Sending module 22 is used to send the query results to the message sending end;

[0245] The second receiving module 23 is used to receive the message to be sent by the message sending end.

[0246] In an exemplary embodiment, the above apparatus further includes: a determining module, configured to obtain the status of the message to be sent, and determine message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown, or message transmission timeout.

[0247] Each module in the aforementioned message processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0248] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram is shown in Figure 14. The computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is connected to the system bus via the I / O interfaces. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device stores data for messages to be sent. The I / O interfaces of the computer device are used for exchanging information between the processor and external devices. The communication interface of the computer device is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a message processing method.

[0249] Those skilled in the art will understand that the structure shown in Figure 14 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or may combine certain components, or may have different component arrangements.

[0250] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0251] Obtain the message to be sent;

[0252] Based on the message information of the message to be sent, determine whether the message to be sent is an abnormal message;

[0253] If the message to be sent is not an abnormal message, a query request is sent to the message receiver; the query request is used to check whether the message receiver has received the message to be sent.

[0254] Receive the query result sent by the message receiver, and if the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0255] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0256] Based on the sending time, settlement date, and status of the message to be sent, determine whether the message to be sent meets the sending conditions; the sending conditions include whether the sending time is within the preset time range, or whether the settlement date conforms to the preset settlement date rules, or whether the status is an abnormal status;

[0257] If the message to be sent does not meet the sending conditions, then the message to be sent is determined to be an abnormal message;

[0258] If the message to be sent meets the sending conditions, then determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent.

[0259] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0260] Determine whether the status of the message to be sent is temporary;

[0261] If so, then the message to be sent is determined to be a non-abnormal message;

[0262] If not, determine whether the message to be sent is an abnormal message based on the message number.

[0263] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0264] Retrieve the message records of sent messages, and query whether there is a message number to be sent in the message records of sent messages;

[0265] If it exists, determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent;

[0266] If it does not exist, the message to be sent will be determined as a non-abnormal message.

[0267] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0268] If a record in the message record that matches the number of the message to be sent meets the first preset condition, then the message to be sent is identified as an abnormal message; the first preset condition includes a processing status of successful processing, or a response status of successful processing and a processing status of invalidation.

[0269] If a record in the message log that matches the number of the message to be sent meets the second preset condition, then the message to be sent is determined to be a non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

[0270] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0271] If the message to be sent is an abnormal message, update the status of the message to be sent to the duplicate sending status and stop sending the message to the message receiver.

[0272] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0273] If the query result shows that the message receiver has a message with the same number as the message to be sent, the status of the message to be sent is updated to the sent status, and the sending of the message to be sent to the message receiver is stopped.

[0274] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0275] Receive message reply information sent by the message receiving end; message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information;

[0276] If the message reply message is a message reception success message, then the status of the message to be sent will be updated to the sent status, and the status of the message to be sent will be recorded as sent successfully in the message record of the sent messages.

[0277] If the message reply message is a message reception failure message, then the status of the message to be sent will be updated to the sending failure status, and the status of the message to be sent will be recorded as the sending failure status in the message record of the sent messages.

[0278] If the message reply is "Message received unknown" or "Message sent timed out", an abnormal message alarm will be issued, and the status of the message to be sent will be recorded as "Message received unknown" or "Message sent timed out" in the message record of the sent messages.

[0279] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0280] Receive query requests sent by the message sender;

[0281] Based on the number of the message to be sent carried in the query request, the message receiving database at the message receiving end is searched to see if there is a message with the same number as the message to be sent, and the query result is obtained.

[0282] Send the query results to the message sender;

[0283] Receive messages to be sent by the message sender.

[0284] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0285] Obtain the status of the message to be sent, and determine the message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown, or message transmission timeout.

[0286] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0287] Obtain the message to be sent;

[0288] Based on the message information of the message to be sent, determine whether the message to be sent is an abnormal message;

[0289] If the message to be sent is not an abnormal message, a query request is sent to the message receiver; the query request is used to check whether the message receiver has received the message to be sent.

[0290] Receive the query result sent by the message receiver, and if the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0291] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0292] Based on the sending time, settlement date, and status of the message to be sent, determine whether the message to be sent meets the sending conditions; the sending conditions include whether the sending time is within the preset time range, or whether the settlement date conforms to the preset settlement date rules, or whether the status is an abnormal status;

[0293] If the message to be sent does not meet the sending conditions, then the message to be sent is determined to be an abnormal message;

[0294] If the message to be sent meets the sending conditions, then determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent.

[0295] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0296] Determine whether the status of the message to be sent is temporary;

[0297] If so, then the message to be sent is determined to be a non-abnormal message;

[0298] If not, determine whether the message to be sent is an abnormal message based on the message number.

[0299] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0300] Retrieve the message records of sent messages, and query whether there is a message number to be sent in the message records of sent messages;

[0301] If it exists, determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent;

[0302] If it does not exist, the message to be sent will be determined as a non-abnormal message.

[0303] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0304] If a record in the message record that matches the number of the message to be sent meets the first preset condition, then the message to be sent is identified as an abnormal message; the first preset condition includes a processing status of successful processing, or a response status of successful processing and a processing status of invalidation.

[0305] If a record in the message log that matches the number of the message to be sent meets the second preset condition, then the message to be sent is determined to be a non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

[0306] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0307] If the message to be sent is an abnormal message, update the status of the message to be sent to the duplicate sending status and stop sending the message to the message receiver.

[0308] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0309] If the query result shows that the message receiver has a message with the same number as the message to be sent, the status of the message to be sent is updated to the sent status, and the sending of the message to be sent to the message receiver is stopped.

[0310] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0311] Receive message reply information sent by the message receiving end; message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information;

[0312] If the message reply message is a message reception success message, then the status of the message to be sent will be updated to the sent status, and the status of the message to be sent will be recorded as sent successfully in the message record of the sent messages.

[0313] If the message reply message is a message reception failure message, then the status of the message to be sent will be updated to the sending failure status, and the status of the message to be sent will be recorded as the sending failure status in the message record of the sent messages.

[0314] If the message reply is "Message received unknown" or "Message sent timed out", an abnormal message alarm will be issued, and the status of the message to be sent will be recorded as "Message received unknown" or "Message sent timed out" in the message record of the sent messages.

[0315] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0316] Receive query requests sent by the message sender;

[0317] Based on the number of the message to be sent carried in the query request, the message receiving database at the message receiving end is searched to see if there is a message with the same number as the message to be sent, and the query result is obtained.

[0318] Send the query results to the message sender;

[0319] Receive messages to be sent by the message sender.

[0320] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0321] Obtain the status of the message to be sent, and determine the message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown, or message transmission timeout.

[0322] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0323] Obtain the message to be sent;

[0324] Based on the message information of the message to be sent, determine whether the message to be sent is an abnormal message;

[0325] If the message to be sent is not an abnormal message, a query request is sent to the message receiver; the query request is used to check whether the message receiver has received the message to be sent.

[0326] Receive the query result sent by the message receiver, and if the query result indicates that the message receiver has not received the message to be sent, send the message to be sent to the message receiver.

[0327] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0328] Based on the sending time, settlement date, and status of the message to be sent, determine whether the message to be sent meets the sending conditions; the sending conditions include whether the sending time is within the preset time range, or whether the settlement date conforms to the preset settlement date rules, or whether the status is an abnormal status;

[0329] If the message to be sent does not meet the sending conditions, then the message to be sent is determined to be an abnormal message;

[0330] If the message to be sent meets the sending conditions, then determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent.

[0331] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0332] Determine whether the status of the message to be sent is temporary;

[0333] If so, then the message to be sent is determined to be a non-abnormal message;

[0334] If not, determine whether the message to be sent is an abnormal message based on the message number.

[0335] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0336] Retrieve the message records of sent messages, and query whether there is a message number to be sent in the message records of sent messages;

[0337] If it exists, determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent;

[0338] If it does not exist, the message to be sent will be determined as a non-abnormal message.

[0339] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0340] If a record in the message record that matches the number of the message to be sent meets the first preset condition, then the message to be sent is identified as an abnormal message; the first preset condition includes a processing status of successful processing, or a response status of successful processing and a processing status of invalidation.

[0341] If a record in the message log that matches the number of the message to be sent meets the second preset condition, then the message to be sent is determined to be a non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

[0342] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0343] If the message to be sent is an abnormal message, update the status of the message to be sent to the duplicate sending status and stop sending the message to the message receiver.

[0344] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0345] If the query result shows that the message receiver has a message with the same number as the message to be sent, the status of the message to be sent is updated to the sent status, and the sending of the message to be sent to the message receiver is stopped.

[0346] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0347] Receive message reply information sent by the message receiving end; message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information;

[0348] If the message reply message is a message reception success message, then the status of the message to be sent will be updated to the sent status, and the status of the message to be sent will be recorded as sent successfully in the message record of the sent messages.

[0349] If the message reply message is a message reception failure message, then the status of the message to be sent will be updated to the sending failure status, and the status of the message to be sent will be recorded as the sending failure status in the message record of the sent messages.

[0350] If the message reply is "Message received unknown" or "Message sent timed out", an abnormal message alarm will be issued, and the status of the message to be sent will be recorded as "Message received unknown" or "Message sent timed out" in the message record of the sent messages.

[0351] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0352] Receive query requests sent by the message sender;

[0353] Based on the number of the message to be sent carried in the query request, the message receiving database at the message receiving end is searched to see if there is a message with the same number as the message to be sent, and the query result is obtained.

[0354] Send the query results to the message sender;

[0355] Receive messages to be sent by the message sender.

[0356] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0357] Obtain the status of the message to be sent, and determine the message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown, or message transmission timeout.

[0358] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0359] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0360] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A message processing method, characterized in that, Applied to a message sending end, the method includes: acquiring a message to be sent; determining whether the message to be sent is an abnormal message based on the message information of the message to be sent; if the message to be sent is not an abnormal message, sending a query request to a message receiving end; the query request is used to query whether the message receiving end has received the message to be sent; receiving the query result sent by the message receiving end, and if the query result indicates that the message receiving end has not received the message to be sent, sending the message to be sent to the message receiving end; the message information includes the sending time, delivery date, status, and number of the message to be sent, and the step of determining whether the message to be sent is an abnormal message based on the message information of the message to be sent includes... The process includes: determining whether a message to be sent meets sending conditions based on its sending time, settlement date, and status; the sending conditions include whether the sending time is within a preset time range, or whether the settlement date conforms to a preset settlement date rule, or whether the status is an abnormal status; if the message to be sent does not meet the sending conditions, then the message to be sent is determined to be an abnormal message; if the message to be sent meets the sending conditions, then determining whether the message to be sent is an abnormal message based on its status and number, wherein the number is used to query whether there is a message with the same number as the message to be sent, and the status of the message to be sent is used to determine whether it is an abnormal message by judging whether it meets a preset status.

2. The method according to claim 1, characterized in that, The step of determining whether the message to be sent is an abnormal message based on its status and number includes: determining whether the status of the message to be sent is temporary; if so, determining that the message to be sent is a non-abnormal message; if not, determining whether the message to be sent is an abnormal message based on its number.

3. The method according to claim 2, characterized in that, The step of determining whether the message to be sent is an abnormal message based on the message number to be sent includes: obtaining the message record of sent messages and querying whether the message number to be sent exists in the message record of sent messages; if it exists, determining whether the message to be sent is an abnormal message based on the record in the message record that matches the message number to be sent; if it does not exist, determining the message to be sent as a non-abnormal message.

4. The method according to claim 3, characterized in that, The step of determining whether a message to be sent is an abnormal message based on a record in the message record that matches the number of the message to be sent includes: if a record in the message record that matches the number of the message to be sent satisfies a first preset condition, then the message to be sent is determined to be an abnormal message; the first preset condition includes a processing status of processing success, or a response status of processing success and a processing status of failure; if a record in the message record that matches the number of the message to be sent satisfies a second preset condition, then the message to be sent is determined to be a non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

5. The method according to claim 1, characterized in that, The method further includes: if the message to be sent is the abnormal message, updating the status of the message to be sent to a duplicate sending status, and stopping the sending of the message to be sent to the message receiving end.

6. The method according to claim 1, characterized in that, The method further includes: if the query result indicates that the message receiving end has a message with the same number as the message to be sent, updating the status of the message to be sent to the sent status and stopping the sending of the message to be sent to the message receiving end.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: receiving message reply information sent by the message receiving end; the message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information; if the message reply information is message reception success information, then the status of the message to be sent is updated to sent status, and the status of the message to be sent is recorded as sent success status in the message record of sent messages; if the message reply information is message reception failure information, then the status of the message to be sent is updated to sent failure status, and the status of the message to be sent is recorded as sent failure status in the message record of sent messages; if the message reply information is message reception unknown information or message transmission timeout information, then an abnormal message alarm information is issued, and the status of the message to be sent is recorded as message reception unknown status or transmission timeout status in the message record of sent messages.

8. A message processing method, characterized in that, Applied to a message receiving end, the method includes: receiving a query request sent by a message sending end, wherein the query request is sent by the message sending end after determining whether the message to be sent is a non-abnormal message based on the message information of the message to be sent, wherein the message information includes the sending time, settlement date, status, and number of the message to be sent; and determining whether the message to be sent is an abnormal message based on the message information includes: determining whether the message to be sent meets the sending conditions based on the sending time, settlement date, and status of the message to be sent; the sending conditions include whether the sending time is within a preset time range, or whether the settlement date conforms to a preset settlement date rule, or whether the status is an abnormal status; if the message is not an abnormal message, the method is as follows: If the message to be sent does not meet the sending conditions, then the message to be sent is determined to be an abnormal message; if the message to be sent meets the sending conditions, then based on the status and number of the message to be sent, it is determined whether the message to be sent is an abnormal message, wherein the number is used to query whether there is a message with the same number as the message to be sent, and the status of the message to be sent is used to determine whether it is an abnormal message by judging whether a preset status is met; based on the number of the message to be sent carried in the query request, the message receiving database of the message receiving end is queried to see if there is a message with the same number as the message to be sent, and the query result is obtained; the query result is sent to the message sending end; and the message to be sent sent by the message sending end is received.

9. The method according to claim 8, characterized in that, The method further includes: obtaining the status of the message to be sent, and determining message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information.

10. A message processing apparatus, characterized in that, The device, applied to a message sending end, includes: an acquisition module for acquiring a message to be sent; a determination module for determining whether the message to be sent is an abnormal message based on its message information; a first sending module for sending a query request to a message receiving end when the message to be sent is not an abnormal message; the query request is used to query whether the message receiving end has received the message to be sent; a second sending module for receiving the query result sent by the message receiving end, and sending the message to be sent to the message receiving end when the query result indicates that the message receiving end has not received the message to be sent; the message information includes the sending time, delivery date, status, and number of the message to be sent; the determination module includes: a first determination unit for... Based on the sending time, settlement date, and status of the message to be sent, determine whether the message to be sent meets the sending conditions; the sending conditions include whether the sending time is within a preset time range, or whether the settlement date conforms to a preset settlement date rule, or whether the status is an abnormal status; the second determining unit is used to determine that the message to be sent is an abnormal message if the message to be sent does not meet the sending conditions; the third determining unit is used to determine whether the message to be sent is an abnormal message based on the status and number of the message to be sent if the message to be sent meets the sending conditions, wherein the number is used to query whether there is a message with the same number as the message to be sent, and the status of the message to be sent is used to determine whether it is an abnormal message by judging whether it meets a preset status.

11. The apparatus according to claim 10, characterized in that, The third determining unit is specifically used to: determine whether the state of the message to be sent is temporary; if so, determine that the message to be sent is a non-abnormal message; if not, determine whether the message to be sent is an abnormal message based on the number of the message to be sent.

12. The apparatus according to claim 10, characterized in that, The third determining unit is specifically used to: obtain the message record of the sent message, and query whether the number of the message to be sent exists in the message record of the sent message; if it exists, determine whether the message to be sent is an abnormal message based on the record in the message record that matches the number of the message to be sent. If it does not exist, the message to be sent will be determined as a non-abnormal message.

13. The apparatus according to claim 10, characterized in that, The third determining unit is specifically configured to: if a record in the message record that matches the number of the message to be sent satisfies a first preset condition, then determine the message to be sent as the abnormal message; the first preset condition includes a processing status of processing success, or a response status of processing success and a processing status of failure; if a record in the message record that matches the number of the message to be sent satisfies a second preset condition, then determine the message to be sent as the non-abnormal message; the second preset condition includes a response status of processing failure, or a response status of processing success and a processing status of processing failure.

14. The apparatus according to claim 10, characterized in that, The device further includes: a first update module, configured to update the status of the message to be sent to a duplicate sending status and stop sending the message to be sent to the message receiving end when the message to be sent is the abnormal message.

15. The apparatus according to claim 10, characterized in that, The device further includes a second update module, configured to update the status of the message to be sent to a sent status and stop sending the message to the message receiving end when the query result indicates that there is a message with the same number as the message to be sent at the message receiving end.

16. The apparatus according to any one of claims 10-15, characterized in that, The device further includes: a receiving module for receiving message reply information sent by the message receiving end; the message reply information includes message reception success information, message reception failure information, message reception unknown information, or message transmission timeout information; a third updating module for updating the status of the message to be sent to a sent status if the message reply information is message reception success information, and recording the status of the message to be sent as a sent success status in the message record of the sent messages; a fourth updating module for updating the status of the message to be sent to a sent failure status if the message reply information is message reception failure information, and recording the status of the message to be sent as a sent failure status in the message record of the sent messages; and a fifth updating module for issuing an abnormal message alarm information if the message reply information is message reception unknown information or message transmission timeout information, and recording the status of the message to be sent as message reception unknown status or transmission timeout status in the message record of the sent messages.

17. A message processing apparatus, characterized in that, The device, applied to a message receiving end, includes: a first receiving module, configured to receive a query request sent by a message sending end. The query request is sent by the message sending end after determining whether the message to be sent is a non-abnormal message based on its message information. The message information includes the sending time, settlement date, status, and number of the message to be sent. The method for determining whether the message to be sent is an abnormal message based on the message information includes: determining whether the message to be sent meets sending conditions based on its sending time, settlement date, and status; the sending conditions include whether the sending time is within a preset time range, or whether the settlement date conforms to a preset settlement date rule, or whether the status is an abnormal status; if the message to be sent is not... If the sending conditions are met, the message to be sent is determined to be an abnormal message; if the message to be sent meets the sending conditions, it is determined whether the message to be sent is an abnormal message based on the status and number of the message to be sent, wherein the number is used to query whether there is a message with the same number as the message to be sent, and the status of the message to be sent is used to determine whether it is an abnormal message by judging whether a preset status is met; the acquisition module is used to query the message receiving database of the message receiving end based on the number of the message to be sent carried in the query request to see if there is a message with the same number as the message to be sent, and obtain the query result; the sending module is used to send the query result to the message sending end; the second receiving module is used to receive the message to be sent sent by the message sending end.

18. The apparatus according to claim 17, characterized in that, The device further includes: a determining module, used to obtain the status of the message to be sent, and determine message reply information based on the status of the message to be sent; the message reply information includes message reception success information, message reception failure information, message reception unknown, or message transmission timeout.

19. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 9.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

21. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

Images