A message processing method, device, equipment and storage medium

Abstract

This article belongs to the field of automatic programming, and specifically relates to a message processing method, device, equipment and storage medium, which are suitable for processing multi-channel messages. The method includes: receiving multi-channel original messages; converting the multi-channel original messages into a target format according to preset conversion rules, and the target format includes preset definitions corresponding to different attribute information; through the preset definitions, matching the attribute information in the target format with the attribute information of historical messages to realize clearing processing of the multi-channel original messages. This article can quickly realize clearing processing of messages from different channels.

Description

Technical Field

[0001] This article belongs to the field of automatic programming, and specifically relates to a message processing method, device, equipment and storage medium. Background Art

[0002] SWIFT messages are a type of message specified by the messaging system provided by the Society for Worldwide Interbank Financial Telecommunications (SWIFT). Their standardized and regularized message format has become the primary means of interbank payment settlement. Existing SWIFT platforms include routing and clearing functions for SWIFT messages, but these functions primarily utilize the SWIFT message tag (TAG) field, failing to consider key elements from a business perspective. TAG field clearing can only clear messages of a single format. Consequently, SWIFT routing rule configuration has certain limitations and cannot support routing and clearing messages from other channel systems, such as the New York Clearing House interbank payment system and the electronic funds transfer system developed and maintained by the Federal Reserve System. In practice, clearing messages from different channels often requires manual intervention, significantly reducing message clearing efficiency. Therefore, improving the efficiency of message clearing from different channels has become a pressing technical challenge. Summary of the Invention

[0003] In view of the above-mentioned problems in the prior art, the purpose of this article is to provide a message processing method, device, equipment and storage medium, which can improve the efficiency of clearing and sorting messages received from different channels.

[0004] In order to solve the above technical problems, the specific technical solutions of this article are as follows:

[0005] On the one hand, this document provides a message processing method suitable for processing messages from multiple channels, the method comprising:

[0006] Receive original messages from multiple channels;

[0007] According to preset conversion rules, the multi-channel original messages are converted into a target format, wherein the target format includes preset definitions corresponding to different attribute information;

[0008] By means of the preset definition, the attribute information in the target format is matched with the attribute information of the historical message, thereby achieving clearing and sorting of the original messages from multiple channels.

[0009] Furthermore, the receiving of multi-channel original messages includes:

[0010] Acquire a multi-channel message original format, wherein the multi-channel original format includes message fields corresponding to different attribute information;

[0011] Determining a target format, wherein the target format includes preset definitions corresponding to different attribute information;

[0012] A conversion relationship between the original format of the multi-channel message and the target format is established to obtain a preset conversion rule for converting the original format of the multi-channel message into the target format.

[0013] Preferably, the establishing of the conversion relationship between the original format of the multi-channel message and the target format further comprises:

[0014] Obtain the relationship between different attribute information and message fields in the original format of multi-channel messages and generate data in data dictionary format;

[0015] Obtaining preset definitions corresponding to different attribute information in the target format to form a data dictionary specification definition including the preset definitions;

[0016] A data dictionary is generated according to the data dictionary format data and the data dictionary specification definition.

[0017] Optionally, the attribute information includes at least entity object parameters and business object parameters.

[0018] Furthermore, by using the preset definition, different attribute information in the target format is matched with attribute information of historical messages to implement clearing processing of the multi-channel original messages, further comprising:

[0019] Determining entity object parameters and business object parameters according to preset definitions corresponding to different attribute information in the target format;

[0020] Determining the entity object corresponding to the multi-channel original message according to the entity object parameter;

[0021] Matching the business object parameter with at least one historical message in the historical message queue of the entity object according to a preset matching rule;

[0022] If the match is successful, the historical message queue is determined as the target historical message queue, and the multi-channel original messages are sorted into the target historical message queue; or

[0023] If the matching is unsuccessful, the multi-channel original messages are sorted according to the preset sorting rules until the multi-channel original messages are sorted into a specific service queue.

[0024] Optionally, the historical message queue includes a received historical message queue and a sent historical message queue.

[0025] Optionally, the matching rule includes a matching range, a matching message type, a matching message category, and a matching element.

[0026] Furthermore, the preset clearing rules include at least one routing group, and the routing group is used to represent all routing rules of each entity object;

[0027] Each of the routing groups includes at least one routing set, wherein the routing set is used to represent all routing rules of each business object in a single entity object;

[0028] Each routing set includes a plurality of routing rules executed in a preset order, and routing processing is performed on the converted target format in sequence according to the routing rules.

[0029] Furthermore, the routing rules include keywords, operators and expected values;

[0030] The keywords correspond to preset definitions corresponding to different attribute information in the target format;

[0031] The operator is used to implement clearing processing of different attribute information according to the keyword;

[0032] The expected value is used to determine a clearing path according to the clearing processing result of the operator.

[0033] Optionally, if the matching is unsuccessful, the multi-channel original messages are sorted according to a preset sorting rule until the multi-channel original messages are sorted into a specific service queue, further comprising:

[0034] Determining a routing set of the entity object according to the entity object corresponding to the multi-channel original message;

[0035] According to the routing set of the entity object and the business object parameters, the multi-channel original message is routed using the routing rules until the multi-channel original message is sorted into a specific business queue.

[0036] Furthermore, the routing process is performed on the multi-channel original messages according to the routing rules until the multi-channel original messages are sorted into specific service queues, further comprising:

[0037] Determining, based on the routing set of the entity object, a plurality of routing rules to be executed in a preset order in the routing set, each routing rule including a corresponding keyword, an operator, and an expected value;

[0038] Determining, based on the business object parameters, a preset definition corresponding to the business object parameters in a target format;

[0039] According to the preset order, the preset definition is used as a keyword, the operator is used to judge the expected value of the business object parameter corresponding to the preset definition, and the routing path is determined, thereby realizing the clearing of the multi-channel original messages.

[0040] Optionally, routing the multi-channel original message according to the routing set and business object parameters of the entity object using the routing rule until the multi-channel original message is cleared to a specific business queue, and then comprising:

[0041] Get the number of original messages received by each entity object and sort them by number;

[0042] The routing rule corresponding to the entity object with a larger number of multi-channel original messages is determined as the target routing rule, and the execution order of the target routing rules is adjusted so that the target routing rules are executed first.

[0043] Optionally, the method further includes performing routing processing on the multi-channel original message according to the routing set and business object parameters of the entity object using the routing rules until the multi-channel original message is cleared to a specific business queue, and then further includes:

[0044] Get the execution count of each routing rule in each entity object;

[0045] The execution order of the routing rules that are executed more times is adjusted so that the routing rules that are executed more times are executed first.

[0046] Preferably, the multi-channel original messages include external clearing system messages and internal transfer messages.

[0047] On the other hand, this document also provides a message processing device, the device comprising:

[0048] A message receiving device, used for receiving original messages from multiple channels;

[0049] A message conversion module, configured to convert the multi-channel original messages into a target format according to preset conversion rules, wherein the target format includes preset definitions corresponding to different attribute information;

[0050] The message sorting module is used to match the attribute information in the target format with the attribute information of the historical message through the preset definition, so as to realize the sorting processing of the original messages from multiple channels.

[0051] On the other hand, this document also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method steps described above when executing the computer program.

[0052] On the other hand, this document also provides a computer-readable storage medium, which stores an executable computer program, and when the computer program is executed by a processor, it implements the method steps described above.

[0053] By adopting the above technical solution, the message processing method, device, equipment and storage medium described in this article convert the received multi-channel original messages into messages in the target format, and then match the attribute information of the message in the target format with the attribute information of the received message, thereby quickly realizing the clearing and processing of multi-channel original messages. The method provided in this article can quickly realize the clearing and processing of messages from different channels.

[0054] In order to make the above and other purposes, features and advantages of this article more obvious and easy to understand, the following specifically cites preferred embodiments and provides detailed descriptions in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the technical solutions in the embodiments of this article or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of this article. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0056] Figure 1 The following is a schematic diagram showing the steps of the message processing method provided in the embodiment of this article;

[0057] Figure 2 A schematic diagram showing the steps of obtaining the preset conversion rules in the embodiment of this article is shown;

[0058] Figure 3 A schematic diagram of the steps for generating a data dictionary in an embodiment of this invention is shown;

[0059] Figure 4 The following is a schematic diagram of the steps of the message matching process in the embodiment of this article;

[0060] Figure 5 The following is a schematic diagram showing the steps of the message clearing process in the embodiment of this article;

[0061] Figure 6 A schematic diagram showing the steps of the detailed message clearing process in the embodiment of this article is shown;

[0062] Figure 7 A schematic diagram of the routing group structure in the embodiment of this invention is shown;

[0063] Figure 8 A logical diagram of message union execution in the embodiments of this document is shown;

[0064] Figure 9 A logical diagram of message intersection execution in the embodiments of this document is shown;

[0065] Figure 10 A logical diagram of random execution of messages in the embodiments of this document is shown;

[0066] Figure 11 A schematic diagram showing the steps of routing messages in the embodiment of this article is shown;

[0067] Figure 12 It shows a schematic diagram of the structure of the message processing device provided in the embodiments of this article;

[0068] Figure 13 A schematic structural diagram of a computer device provided in the embodiments of this document is shown.

[0069] Description of the accompanying symbols:

[0070] 100. Message receiving module;

[0071] 200, message conversion module;

[0072] 300. Message sorting module;

[0073] 1302. Computer equipment;

[0074] 1304, processor;

[0075] 1306. Memory;

[0076] 1308, driving mechanism;

[0077] 1310, input / output module;

[0078] 1312. Input devices;

[0079] 1314. Output device;

[0080] 1316. Presentation equipment;

[0081] 1318. Graphical User Interface;

[0082] 1320, network interface;

[0083] 1322, communication link;

[0084] 1324. Communication bus. DETAILED DESCRIPTION

[0085] The following will be combined with the accompanying drawings to clearly and completely describe the technical solutions in the embodiments of this document. Obviously, the embodiments described are only part of the embodiments of this document, not all of the embodiments. Based on the embodiments of this document, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this document.

[0086] It should be noted that the terms "first," "second," and the like in the specification and claims herein and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product, or device comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or devices.

[0087] Since the formats of messages from different channels are different, for example, the message format of SWIFT MT is the TAG field, and messages from other payment channels may use formats such as XML. For single channel messages, such as SWIFT messages, the TAG field can be used for clearing, but for messages from different channels, such as the New York Clearing House Interbank Payments System in the United States and the electronic transfer system developed and maintained by the Federal Reserve System, they can no longer be cleared based on the TAG field. With the widespread development of international business, business transactions between different channels are becoming more and more frequent. In the existing technology, in some systems, the clearing of messages from different channels is mainly done manually, which greatly reduces the clearing efficiency and accuracy, and is not conducive to the smooth development of business. Some other systems also have system clearing settings, but the systems are relatively scattered, and the messages between channels cannot be correlated and matched with each other, which also reduces their clearing efficiency.

[0088] In order to solve the above problems, the embodiments of this specification provide a message processing method that can realize the clearing and processing of messages from different channels. Specifically, the message formats of different channels are converted into target formats through preset conversion rules, so that the locations of different attribute information can be identified through the converted target format, that is, the attribute information corresponding to the preset definition is determined through the preset definition in the target format, and then by matching it with the attribute information of historical messages, the clearing of messages received from different channels can be quickly realized.

[0089] Specifically, the embodiments of this document provide a message processing method that can quickly sort messages from different channels. Figure 1 It is a step diagram of a message processing method provided in the embodiment of this article. This specification provides the method operation steps described in the embodiment or flowchart, but it may include more or fewer operation steps based on conventional or non-creative work. The order of steps listed in the embodiment is only one way of executing the order of many steps and does not represent the only execution order. When the actual system or device product is executed, it can be executed in the order or in parallel according to the method shown in the embodiment or the accompanying drawings. Specifically, Figure 1 As shown, the method may include:

[0090] S101: receiving original messages from multiple channels;

[0091] S102: Converting the multi-channel original messages into a target format according to a preset conversion rule, wherein the target format includes preset definitions corresponding to different attribute information;

[0092] S103: Matching the attribute information in the target format with the attribute information of the historical message according to the preset definition, so as to implement clearing processing of the multi-channel original message.

[0093] In actual work, by converting the received multi-channel original messages into a target format, the target format can be understood as a format that can be recognized by the recipient (receiving bank), and determining different attribute information with different preset definitions according to the characteristics of the message, and then comparing the attribute information in the converted target format with the attribute information of the historical message to realize the clearing processing of the multi-channel original messages. This article can quickly determine the final clearing position or queue of messages from different channels through a one-time comparison, thereby avoiding the manual clearing of multi-channel messages in the existing technology, greatly improving the efficiency and accuracy of the clearing.

[0094] The preset conversion rule can be set in advance, specifically, obtaining the format information of the multi-channel message in advance, and determining the location of different attribute information according to the format information of the multi-channel message. The location of the different attribute information can be a message field, that is, a region block representing different information, such as line number, account number, business type, business data, currency, amount, etc. Figure 2 As shown, the expression of message fields and the structure of messages may vary depending on the format information. Converting different format information into a unified target format may include the following steps:

[0095] S201: Acquire a multi-channel message original format, where the multi-channel original format includes message fields corresponding to different attribute information;

[0096] S202: Determine a target format, where the target format includes preset definitions corresponding to different attribute information;

[0097] S203: Establishing a conversion relationship between the original format of the multi-channel message and the target format to obtain a preset conversion rule for converting the original format of the multi-channel message into the target format.

[0098] By using the same target format, format differences between messages from different channels are avoided, enabling direct identification. For example, message fields in messages from different channels are broken down into granular, business elements with distinct business semantics. Based on these business semantics (pre-defined definitions), the corresponding business elements can be obtained. This fast and convenient conversion method ensures the identification and clearing of messages from different channels.

[0099] The target format can be the message format setting of the receiver itself, or a universal format set according to actual conditions. It only needs to be recognizable by the receiver and will not be described in detail in this embodiment of the specification.

[0100] In the embodiment of this specification, a standard data dictionary can be set in the message field to realize the conversion between the original format and the target format of the multi-channel message. Specifically, Figure 3 As shown, the following steps may be included:

[0101] S301: Obtain the relationship between different attribute information and message fields in the original format of multi-channel messages and generate data in a data dictionary format;

[0102] S302: Acquire preset definitions corresponding to different attribute information in the target format to form a data dictionary specification definition including the preset definitions;

[0103] S303: Generate a data dictionary according to the data dictionary format data and the data dictionary specification definition.

[0104] The data dictionary format data can represent the attribute information corresponding to different message domains, and the data dictionary specification definition represents the preset definition of different attribute information, that is, business semantics. Each of the preset definitions corresponds to a message domain. For example, the preset definition can be a noun such as a legal entity, a bank number, a business type, an amount, a currency, etc., and the attribute information can be a specific parameter corresponding to the preset definition. In this way, the format messages of different channels can be quickly converted into a recognizable form through the preset data dictionary, which is convenient for sorting. In actual work, the data dictionary can be set in advance, so that when receiving messages from different channels, fast conversion and sorting can be achieved. A data dictionary can be set for the message format of each channel, or the message formats of all channels can be converted through a data dictionary. The specific setting method is not limited in the embodiments of this specification.

[0105] In the embodiment of this specification, the attribute information includes at least entity object parameters and business object parameters. The entity object parameters can represent the identification information of the corresponding legal entity. Therefore, by extracting the entity object parameters through the preset definition, the legal object position to which the received message belongs can be obtained, and then different business object parameters are continued to be determined according to the preset definition until the final clearing position of the received message is determined.

[0106] In the embodiments of this specification, Figure 4 As shown, the matching of different attribute information in the target format with attribute information of historical messages to achieve clearing processing of the multi-channel original messages further includes:

[0107] S401: Determine entity object parameters and business object parameters according to preset definitions corresponding to different attribute information in the target format;

[0108] S402: Determine the entity object corresponding to the multi-channel original message according to the entity object parameter;

[0109] S403: Matching the business object parameter with at least one historical message in the historical message queue of the entity object according to a preset matching rule;

[0110] S404: If the match succeeds, the historical message queue is determined as a target historical message queue, and the multi-channel original message is sorted into the target historical message queue; or

[0111] S405: If the matching is unsuccessful, the multi-channel original messages are sorted according to a preset sorting rule until the multi-channel original messages are sorted into a specific service queue.

[0112] In actual work, when the entity object has been determined, its historical message information can be obtained through the determined entity object. Specifically, it can be determined by the line number of the entity object. When the line number of the received message line is determined to be AAAAAA through the preset definition after conversion, its entity object can be determined to be A. Then, the historical message in entity A is matched with the received message. When the historical message that successfully matches the received message is determined, the received message is cleared into the historical message. Through this matching method, the messages received from different channels can be quickly cleared.

[0113] For example, assume that historical report M has been cleared to business queue C of entity A's system B. Upon receipt, report N is cleared to the legal entity defined in the pre-set legal entity definition. Report N is then matched according to the legal entity's report matching rules (e.g., same currency, amount, value date, same business number as related business numbers, etc.). Assuming a successful match between N and M, N is directly routed to the queue cleared by M, i.e., business queue C of entity A's system B.

[0114] The historical message queue may include a message reception history queue and a message transmission history queue. When the received message is not matched in the message reception history queue, the message transmission history queue may continue to be matched. For example, the sent message M is sent to the external system A. After the incoming message N is received, the legal entity is first separated out according to the preset definition of the legal entity, and then matched according to the message reception matching rules of this legal entity. If no match is found, the message is matched according to the message transmission matching rules. If the incoming message N successfully matches the message transmission M, the incoming message N directly enters the system and service queue corresponding to the message transmission M.

[0115] It should be noted that the message matching rules and the incoming message matching rules are set in a similar way. The business can be set according to the data dictionary corresponding to the message domain. The only difference is the matching data. The message matching is to match the received message with the previously sent message, and the message matching is to match the received message with the previously received message.

[0116] The matching rules may include matching scope, matching message type, matching message type and matching elements. For example, the matching scope may adopt matching methods such as received message and historical received message, received message and historical sent message, etc.; the matching message type may be that if the received message is a SWIFT MT message, then the matching message type may be a SWIFT MT message, or other types of messages, such as the Clearing House Interbank Payment System (CHIPS) message; the message type may be different types of the same message type, for example, SWIFT MT messages may include MT102 and MT103; the matching elements may be specific business parameters in the message, such as the message sequence number, specific business number and interest value date, etc. By dividing the matching elements, the received message can be matched to a specific business queue. In some other embodiments, the matching elements may also be set according to the specific message type of the received message, which is not limited in this specification.

[0117] It should be noted that in actual work, it is difficult to generate two completely identical message types. Therefore, the matching of matching elements can be carried out more quickly through the matching degree. For example, when the matching degree of two messages reaches the preset value, it means that the matching is completed. In this way, messages from different channels can be quickly cleared and the efficiency of clearing can be improved. In some other embodiments, matching can also be performed based on the weight relationship of different matching elements, so that the clearing queue of received messages can be adjusted at any time. The specific setting process is not limited in this manual.

[0118] In addition, in order to improve the matching efficiency, a preset number of historical messages can be selected as matching objects according to the matching type or matching category, and the selected historical messages can be representative messages, which can reduce the number of matching times of the received messages and improve the matching efficiency.

[0119] In the embodiment of this specification, when the matching is unsuccessful, the multi-channel original message is sorted according to the preset sorting rules, specifically, Figure 7 As shown, the preset clearing rules include at least one routing group, and the routing group is used to represent all routing rules of each entity object;

[0120] Each of the routing groups includes at least one routing set, wherein the routing set is used to represent all routing rules of each business object in a single entity object;

[0121] Each routing set includes multiple routing rules executed in a preset order. These routing rules are used to route the converted target format in sequence. The final exit of all routes is a queue (which can be one or more). The queue is the processing method for routing results. The role of the queue must be clear and can be explained by the system. Optionally, the queue can include at least one of the following types:

[0122] 1) Branch queue: The message is assigned to a branch;

[0123] 2) System queue: The document is sent to a certain system;

[0124] 3) Business processing queue: specific to the system's specific processing queue, such as outgoing remittance, incoming remittance, etc.

[0125] 4) External queue: The queue corresponding to the external system to which the message is sent;

[0126] 5) Internal transfer queue: for internal transfer of messages between legal entities within the group;

[0127] 6) Queue for processing: Users directly put certain types of messages into the queue for processing;

[0128] 7) Print queue: Send the message to the specified printer queue;

[0129] 8) File queue: The message is sent to the file queue to generate a file;

[0130] 9) Manual processing (download, print, archive and clear);

[0131] 10) Archive queue: message archiving.

[0132] Each routing rule may include keywords, operators, and expected values; the keywords correspond to preset definitions corresponding to different attribute information in the target format; the operators are used to implement clearing processing of different attribute information based on the keywords; the expected value is used to determine the clearing path based on the clearing processing result of the operator. If the result of the operator is met, the routing result configured for the routing point will be returned.

[0133] Different operators can be included according to different keywords. The following table 1 shows the types of operators:

[0134] Table 1 Operator types

[0135]

[0136] In actual work, it also includes compound conditions of operators, such as:

[0137] 1) Simultaneously meet (and): The default compound form, which means that one or more "condition elements" under the compound condition meet the "AND" logical relationship;

[0138] 2) Any satisfaction: represents that one or more "condition elements" under the compound conditions satisfy the "OR" logical relationship;

[0139] 3) Does not exist: A single "conditional element" representing a "conditional element" under a compound condition satisfies the "NOT" logical relationship.

[0140] The expected routing result after the routing rules are met, generally pointing to a routing set to continue the entire routing process or put the message into a queue.

[0141] Therefore, if Figure 5 As shown, if the matching is unsuccessful, the multi-channel original message is cleared according to the preset clearing rules until the multi-channel original message is cleared to a specific service queue, further comprising:

[0142] S501: Determine a routing set of the entity object according to the entity object corresponding to the multi-channel original message;

[0143] S502: According to the routing set of the entity object and the business object parameters, the multi-channel original message is routed using the routing rules until the multi-channel original message is sorted into a specific business queue.

[0144] The execution of the routing rules is carried out smoothly in accordance with the execution order specified in the routing set, specifically, Figure 6 As shown, the following steps may be included:

[0145] S601: Determine, based on a routing set of the entity object, a plurality of routing rules to be executed in a preset order in the routing set, each routing rule including a corresponding keyword, an operator, and an expected value;

[0146] S602: Determine, based on the business object parameters, a preset definition corresponding to the business object parameters in the target format;

[0147] S603: According to the preset order, using the preset definition as a keyword, using the operator to judge the expected value of the business object parameter corresponding to the preset definition, and determining the routing path, thereby achieving the clearing of the multi-channel original messages.

[0148] In actual operation, for example, assuming the recipient is receiver, in the routing set of the legal entity clearing routing group, the rule receiver = "PCBCJPJTXXX" can be used to clear to the XX branch entity. Assuming the message type is msgtype, in the routing set of the entity clearing routing group of the XX branch, the rule msgtype = "103" can be used to clear to system A. Assuming the beneficiary account number is recvacct, and "%" represents a wildcard character, the routing set of the 103 message in the routing group of system A of the XX branch can be routed to the credit card repayment queue according to the rule recvacct like "ABCDEF%", where ABCDEF can be the credit card BIN feature.

[0149] It should be noted that the execution result of a specific routing rule may not be a specific business queue. Through operators and expected values, the execution result can be other routing rules or routing sets. Therefore, the types and execution orders of routing rules in the routing set are different for different entity objects. The execution order is expressed as the execution logic for clearing received messages. In actual work, there can be the following execution logics: union, intersection and random. The union is to execute all the routing rules under it in sequence. Any routing result obtained by successful execution is executed as the result of the routing set. The union rule can be used in scenarios such as one message multiple transfers and broadcast messages. Figure 8As shown in the figure, it is a logical diagram of the union execution; the intersection is to execute all the routing rules under it in sequence. If the results returned by the successfully executed routing rules are the same, then the result is executed, otherwise the default result is executed, such as Figure 9 As shown in the figure, it is a logical diagram of intersection execution; Random is to execute the routing rules in order until the first routing rule that is successfully executed appears, then exit and execute the result returned by it, as shown in the figure below. Figure 10 The following is a logic diagram of random execution.

[0150] The message processing method provided above is for clearing and sorting multi-channel messages, which may include messages from other external clearing systems. In some other embodiments, they may also include internal transfer messages, such as clearing messages sent from foreign branches to the headquarters (such as messages sent from China Construction Bank XX branch to China Construction Bank headquarters). Although these messages are sent within the group, the clearing systems used are different, and therefore they can also be cleared using the method provided above.

[0151] It should be noted that, when it is determined that the message sent is an internal transfer message, the clearing of the internal transfer message can also be achieved by the above method, such as Figure 11 As shown, for example, the message sent enters the message routing group of this entity (message line) and is routed according to the routing rules in the message routing set. It can be routed to a specific external queue, message review queue, system internal transfer queue, etc. The specific message routing settings are consistent with the above-mentioned message receiving settings and will not be repeated in this manual.

[0152] Based on the above-mentioned processing of received messages, in order to improve the processing efficiency of subsequent messages, the following steps may also be included:

[0153] Get the number of original messages received by each entity object through multiple channels and sort them by number.

[0154] The routing rule corresponding to the entity object with a larger number of multi-channel original messages is determined as the target routing rule, and the execution order of the target routing rules is adjusted so that the target routing rules are executed first.

[0155] It can be understood that when setting different routing rules, users can adjust the execution order of routing as needed, so that the routing rules corresponding to messages with higher frequency can be placed at the front of the routing to improve the execution efficiency of automatic routing. Furthermore, the message processing system can also have the function of automatically counting the execution status of routing. When running batches in a preset time period (such as the end of the day), the priority of the routing rules can be adjusted according to the number of routing executions over a period of time, and sorted according to the priority to improve the overall execution efficiency of routing.

[0156] In addition to the above adjustments to high-frequency messages, you can also make adjustments based on the actual execution of routing rules. Specifically, you can:

[0157] Get the execution count of each routing rule in each entity object;

[0158] The execution order of the routing rules that are executed more times is adjusted so that the routing rules that are executed more times are executed first.

[0159] In the embodiments of this specification, by adding a routing rule statistics function, users can view the message flow status and the number of rule execution statistics, which is convenient for users to adjust the order and logic of the rules and improve execution efficiency and accuracy; it should be noted that when the routing rules are modified, the messages can still flow automatically according to the previous rules, and the rule modifications will not take effect immediately after approval.

[0160] In order to avoid malfunctions in the operation of the adjusted routing rules, a reset function can also be set to quickly restore the routing rules before the adjustment, thereby improving the efficiency of message processing.

[0161] The message processing method, apparatus, device and storage medium provided in the embodiments of this specification convert the received multi-channel original messages into messages in a target format, and then match the attribute information of the messages in the target format with the attribute information of the received messages, thereby quickly realizing the clearing and processing of multi-channel original messages. This article solves the problem of differences in standard labels of different messages by defining a standardized data dictionary, and uses a standardized data dictionary to define message matching rules and message routing rules, fully considering the universality and readability of the rules, and is applicable to messages from different external channels.

[0162] Based on the same inventive concept, the embodiment of this specification also provides a message processing device, such as Figure 12 As shown, the device includes:

[0163] The message receiving device 100 is used to receive original messages from multiple channels;

[0164] The message conversion module 200 is used to convert the multi-channel original message into a target format according to a preset conversion rule, wherein the target format includes preset definitions corresponding to different attribute information;

[0165] The message sorting module 300 is used to match the attribute information in the target format with the attribute information of the historical message according to the preset definition, so as to implement sorting processing of the multi-channel original message.

[0166] The beneficial effects achieved by the above-mentioned device are consistent with the beneficial effects achieved by the above-mentioned method and will not be described in detail in this specification.

[0167] like Figure 13 As shown, a computer device provided in an embodiment of the present invention is shown. The computer device 1302 may include one or more processors 1304, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 1302 may also include any memory 1306 for storing any type of information, such as code, settings, data, etc. For example, without limitation, the memory 1306 may include any one or more combinations of the following: any type of RAM, any type of ROM, a flash memory device, a hard disk, an optical disk, etc. More generally, any memory may use any technology to store information. Furthermore, any memory may provide volatile or non-volatile retention of information. Furthermore, any memory may represent a fixed or removable component of the computer device 1302. In one embodiment, when the processor 1304 executes associated instructions stored in any memory or combination of memories, the computer device 1302 may perform any operation of the associated instructions. The computer device 1302 also includes one or more drive mechanisms 1308, such as a hard disk drive mechanism, an optical disk drive mechanism, etc., for interacting with any memory.

[0168] Computer device 1302 may also include an input / output module 1310 (I / O) for receiving various inputs (via input devices 1312) and providing various outputs (via output devices 1314). A specific output mechanism may include a presentation device 1316 and an associated graphical user interface (GUI) 1318. In other embodiments, input / output module 1310 (I / O), input devices 1312, and output devices 1314 may not be included, and the computer device 1302 may simply be a computer device on a network. Computer device 1302 may also include one or more network interfaces 1320 for exchanging data with other devices via one or more communication links 1322. One or more communication buses 1324 couple the components described above together.

[0169] The communication link 1322 can be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 1322 can include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0170] Corresponding to Figures 1-6 The embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which executes the steps of the above method when executed by a processor.

[0171] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program causes the processor to execute the following Figures 1 to 6 The method shown.

[0172] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0173] It should also be understood that in the embodiments herein, the term "and / or" merely describes an association between associated objects, indicating that three possible relationships exist. For example, "A and / or B" could represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates an "or" relationship between the associated objects.

[0174] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the composition and steps of each example according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this document.

[0175] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0176] In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices, or units, or can be an electrical, mechanical, or other form of connection.

[0177] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments herein.

[0178] In addition, the functional units in the various embodiments herein may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0179] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0180] This article uses specific embodiments to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for those skilled in the art, based on the ideas of this article, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation to this article.

Claims

1. A message processing method, adapted for processing messages from multiple channels, characterized in that: The method comprises: Receive original messages from multiple channels; According to preset conversion rules, the multi-channel original messages are converted into a target format, wherein the target format includes preset definitions corresponding to different attribute information; Matching the attribute information in the target format with the attribute information of the historical message through the preset definition to achieve clearing and processing of the original messages from multiple channels; The receiving of multi-channel original messages includes: Acquire a multi-channel message original format, wherein the multi-channel original format includes message fields corresponding to different attribute information; Determining a target format, wherein the target format includes preset definitions corresponding to different attribute information; Establishing a conversion relationship between the original format of the multi-channel message and the target format to obtain a preset conversion rule for converting the original format of the multi-channel message into the target format; The establishing of the conversion relationship between the original format of the multi-channel message and the target format further comprises: Obtain the relationship between different attribute information and message fields in the original format of multi-channel messages and generate data in data dictionary format; Obtaining preset definitions corresponding to different attribute information in the target format to form a data dictionary specification definition including the preset definitions; A data dictionary is generated according to the data dictionary format data and the data dictionary specification definition.

2. The method according to claim 1, characterized in that The attribute information includes at least entity object parameters and business object parameters.

3. The method according to claim 2, characterized in that By using the preset definition, different attribute information in the target format is matched with attribute information of historical messages to implement clearing processing of the multi-channel original messages, further comprising: Determining entity object parameters and business object parameters according to preset definitions corresponding to different attribute information in the target format; Determining the entity object corresponding to the multi-channel original message according to the entity object parameter; Matching the business object parameter with at least one historical message in the historical message queue of the entity object according to a preset matching rule; If the match is successful, the historical message queue is determined as the target historical message queue, and the multi-channel original messages are sorted into the target historical message queue; or If the matching is unsuccessful, the multi-channel original messages are sorted according to the preset sorting rules until the multi-channel original messages are sorted into a specific service queue.

4. The method according to claim 3, characterized in that The historical message queue includes a received historical message queue and a sent historical message queue.

5. The method according to claim 3, characterized in that The matching rules include matching scope, matching message type, matching message category and matching elements.

6. The method according to claim 3, characterized in that The preset clearing rules include at least one routing group, and the routing group is used to represent all routing rules of each entity object; Each of the routing groups includes at least one routing set, wherein the routing set is used to represent all routing rules of each business object in a single entity object; Each routing set includes a plurality of routing rules executed in a preset order, and routing processing is performed on the converted target format in sequence according to the routing rules.

7. The method according to claim 6, characterized in that The routing rules include keywords, operators and expected values; The keywords correspond to preset definitions corresponding to different attribute information in the target format; The operator is used to implement clearing processing of different attribute information according to the keyword; The expected value is used to determine a clearing path according to the clearing processing result of the operator.

8. The method according to claim 7, characterized in that If the matching is unsuccessful, the multi-channel original messages are sorted according to a preset sorting rule until the multi-channel original messages are sorted into a specific service queue, further comprising: Determining a routing set of the entity object according to the entity object corresponding to the multi-channel original message; According to the routing set of the entity object and the business object parameters, the multi-channel original message is routed using the routing rules until the multi-channel original message is sorted into a specific business queue.

9. The method according to claim 8, characterized in that The routing process of the multi-channel original messages according to the routing rules until the multi-channel original messages are sorted into specific service queues further includes: Determining, based on the routing set of the entity object, a plurality of routing rules to be executed in a preset order in the routing set, each routing rule including a corresponding keyword, an operator, and an expected value; Determining, based on the business object parameters, a preset definition corresponding to the business object parameters in a target format; According to the preset order, the preset definition is used as a keyword, the operator is used to judge the expected value of the business object parameter corresponding to the preset definition, and the routing path is determined, thereby realizing the clearing of the multi-channel original messages.

10. The method according to claim 8, characterized in that The method further comprises: performing routing processing on the multi-channel original message according to the routing set of the entity object and the business object parameter by the routing rule until the multi-channel original message is cleared to a specific business queue, and then comprising: Get the number of original messages received by each entity object through multiple channels and sort them by number. The routing rule corresponding to the entity object with a larger number of multi-channel original messages is determined as the target routing rule, and the execution order of the target routing rules is adjusted so that the target routing rules are executed first.

11. The method according to claim 8, characterized in that The method further includes routing the multi-channel original message according to the routing set of the entity object and the business object parameter by using the routing rule until the multi-channel original message is cleared to a specific business queue, and then further includes: Get the execution count of each routing rule in each entity object; The execution order of the routing rules that are executed more times is adjusted so that the routing rules that are executed more times are executed first.

12. The method according to claim 1, characterized in that The multi-channel original messages include external clearing system messages and internal transfer messages.

13. A message processing device, characterized in that: The device comprises: A message receiving device, used for receiving original messages from multiple channels; A message conversion module, configured to convert the multi-channel original messages into a target format according to preset conversion rules, wherein the target format includes preset definitions corresponding to different attribute information; A message sorting module, configured to match the attribute information in the target format with the attribute information of historical messages according to the preset definition, thereby achieving sorting of the original messages from multiple channels; The message receiving device is also used to, before receiving the multi-channel original message, obtain the original format of the multi-channel message, the multi-channel original format includes message fields corresponding to different attribute information; determine the target format, the target format includes preset definitions corresponding to different attribute information; establish a conversion relationship between the multi-channel message original format and the target format to obtain preset conversion rules for converting the multi-channel message original format into the target format; the establishment of the conversion relationship between the multi-channel message original format and the target format further includes: obtaining the relationship between different attribute information and message fields in the multi-channel message original format, and generating data dictionary format data; obtaining the preset definitions corresponding to different attribute information in the target format to form a data dictionary specification definition including the preset definitions; and generating a data dictionary based on the data dictionary format data and the data dictionary specification definition.

14. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method steps according to any one of claims 1 to 12 are implemented.

15. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps according to any one of claims 1 to 12 are implemented.

Images