Universal message management method and system based on ISO20022 standard
By adopting the general message management method of ISO20022 standard and Json format in the message management system, the complexity of message management and the accuracy and speed of manual audits in the multi-payment channel are solved, and high adaptability, fast and accurate message management is achieved.
Patent Information
- Application Number
- CN202510145023.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-10
- Publication Date
- 2025-05-13
AI Technical Summary
When commercial banks have multiple payment channels, it is difficult to understand the meaning of the message, difficult to edit the message content, and difficult to convert the message channels, resulting in the service and data governance process being blocked, and there are accuracy and speed problems with manual revision and auditing.
Using a general message management method and system based on ISO20022 standard, ISO20022 is used as the standard communication message structure and Json format is used as the basic message format to form a message management solution that can be converted in multiple message formats, realizing the standardized data storage and the use of multi-channel unified data dictionary.
It greatly improves the adaptability of message management, significantly improves the revision speed and accuracy, reduces the complexity and cost of manual audits, and realizes the standardization and automation of message processing.
Smart Images
Figure CN119996524A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technology, and in particular to a universal message management method based on the ISO20022 standard and a universal message management system based on the ISO20022 standard. Background Art
[0002] At present, when most banks conduct cross-border transactions, due to the different payment and settlement requirements in different countries and regions, payment messages require a large degree of manual review, revision, and conversion, so a message management system is needed to assist in the manual processing of such business.
[0003] However, most of the existing message management systems use one message format, one data dictionary, and one data storage management solution for each payment channel. The service interface and message storage provided to the outside are forcibly bound to the corresponding payment channel. Therefore, when a commercial bank has multiple payment channels, it will be difficult to understand the meaning of the message, edit the message content, and switch the message channel.
[0004] like Figure 1 As shown in the figure, taking the three foreign currency payment channels of common domestic commercial banks as an example, this message management solution has the following three common problems:
[0005] (1) The message management system of the three payment channels A, B, and C provides three message service specifications and three data dictionaries. The management system and business system must comply with the three service specifications at the same time, which greatly hinders the service and data governance process of commercial banks and runs counter to the general direction of technological iteration and upgrading of existing commercial banks.
[0006] (II) There are actual conversions between the three payment channels A, B, and C, so the three systems must have the function of converting messages to the other two channels. As the number of payment channels increases, the number of such conversion functions will increase in a permutation and combination manner, bringing huge costs and risks to the upgrade of the bank system.
[0007] (III) If there is cross-border payment business, due to the great differences in business specifications in different countries and regions, a large part of the message processing requires manual revision, review, etc. If the message specifications stored in different payment systems are completely inconsistent, business personnel need to query different message specification documents when revising, and the accuracy and speed of revision cannot be guaranteed. Summary of the invention
[0008] In response to the above problems, the present invention provides a universal message management method and system based on the ISO20022 standard. By taking ISO20022 as the standard communication message structure and the Json format as the basic message format, a message management solution capable of converting multiple message formats is formed, thereby ensuring that the stored data also meets the standardization requirements, greatly improving the adaptability of message management, greatly increasing the revision speed, and improving the accuracy of revised messages.
[0009] To achieve the above object, the present invention provides a general message management method based on ISO20022 standard, comprising:
[0010] After business processing based on the business system, a message application is initiated to the message management system, and the application interface adopts the ISO20022 standard;
[0011] Convert the received XML format standard message into ISO20022 standard JSON format message;
[0012] Performing verification and business processing on the JSON format message, and storing the JSON format message;
[0013] The JSON format message is converted into an annotation text, and the converted metadata annotation text is revised or directly sent according to the manual review result.
[0014] In the above technical solution, preferably, the step of converting the received standard message in XML format into a message in JSON format according to the ISO20022 standard includes:
[0015] The standard message in XML format received by the application interface is converted into a JSON format message based on the ISO20022 standard through the ISO20022 data dictionary.
[0016] In the above technical solution, preferably, the JSON format message is subjected to verification processing and business processing, and the JSON format message is stored, and the specific process includes:
[0017] Performing rationality check, message rule check, security check and message flow processing on the converted JSON format message;
[0018] The preset key fields in the JSON format message are stored in a horizontal table, and the remaining preset fields are stored in a general message field in a String format.
[0019] In the above technical solution, preferably, the specific process of converting the JSON format message into annotated text includes:
[0020] Based on a multi-channel unified data dictionary, each field in the JSON format message is annotated and converted into readable text to obtain metadata annotation text.
[0021] In the above technical solution, preferably, the converted metadata annotation text is revised or directly sent according to the manual review result, and the specific process includes:
[0022] Manually reviewing the metadata annotation text obtained by conversion;
[0023] If the manual review result shows that the message is completely correct, the metadata annotation text is mapped one-to-one to the original message and sent directly;
[0024] If the manual review result shows that there is a problem with the message, the metadata annotation text is rendered as an operable interface, the message is revised based on the operable interface, and the message is sent after the message is reviewed to be completely correct;
[0025] If the manual review result shows that the message is correct but the format is different, the metadata annotation text is converted one-to-one into a new JSON format message, and is reprocessed and reviewed before being sent.
[0026] The present invention also proposes a universal message management system based on the ISO20022 standard, which applies the universal message management method based on the ISO20022 standard disclosed in any one of the above technical solutions, including:
[0027] The message application module is used to initiate a message application to the message management system after business processing based on the business system, and the application interface adopts the ISO20022 standard;
[0028] The message conversion module is used to convert the received standard message in XML format into the JSON format message of ISO20022 standard;
[0029] A message processing module, used to perform verification and business processing on the JSON format message, and store the JSON format message;
[0030] The message review module is used to convert the annotation text of the JSON format message, and revise or directly send the converted metadata annotation text according to the manual review result.
[0031] In the above technical solution, preferably, the message conversion module is specifically used for:
[0032] The standard message in XML format received by the application interface is converted into a JSON format message based on the ISO20022 standard through the ISO20022 data dictionary.
[0033] In the above technical solution, preferably, the message processing module is specifically used to:
[0034] Performing rationality check, message rule check, security check and message flow processing on the converted JSON format message;
[0035] The preset key fields in the JSON format message are stored in a horizontal table, and the remaining preset fields are stored in a general message field in a String format.
[0036] In the above technical solution, preferably, the message review module is specifically used to:
[0037] Based on a multi-channel unified data dictionary, each field in the JSON format message is annotated and converted into readable text to obtain metadata annotation text.
[0038] In the above technical solution, preferably, the message review module is also used to:
[0039] Manually reviewing the metadata annotation text obtained by conversion;
[0040] If the manual review result shows that the message is completely correct, the metadata annotation text is mapped one-to-one to the original message and sent directly;
[0041] If the manual review result shows that there is a problem with the message, the metadata annotation text is rendered as an operable interface, the message is revised based on the operable interface, and the message is sent after the message is reviewed to be completely correct;
[0042] If the manual review result shows that the message is correct but the format is different, the metadata annotation text is converted one-to-one into a new JSON format message, and is reprocessed and reviewed before being sent.
[0043] Compared with the prior art, the beneficial effects of the present invention are: by using ISO20022 as the standard communication message structure and Json format as the basic message format, a message management solution that can convert multiple message formats is formed, which can ensure that the stored data also meets the standardization requirements, greatly improve the adaptability of message management, greatly improve the revision speed, and improve the accuracy of revised messages. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 It is a flow chart of a message management method in the prior art;
[0045] Figure 2 A flowchart of a general message management method based on the ISO20022 standard disclosed in an embodiment of the present invention;
[0046] Figure 3A schematic diagram of an example of an interface provided to the outside by a message management system disclosed in an embodiment of the present invention;
[0047] Figure 4 A sample schematic diagram of converting the standard XML disclosed in an embodiment of the present invention into the Json format;
[0048] Figure 5 A schematic diagram of a storage example of message data disclosed in an embodiment of the present invention;
[0049] Figure 6 The present invention is a schematic diagram of the operation of the AMH global message management system disclosed in one embodiment of the present invention. DETAILED DESCRIPTION
[0050] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0051] The present invention is further described in detail below in conjunction with the accompanying drawings:
[0052] like Figure 2 As shown, a general message management method based on the ISO20022 standard provided by the present invention includes:
[0053] After business processing based on the business system, a message application is initiated to the message management system, and the application interface adopts the ISO20022 standard;
[0054] Convert the received XML format standard message into ISO20022 standard JSON format message;
[0055] Perform verification and business processing on JSON format messages, and store JSON format messages;
[0056] The annotation text of the JSON format message is converted, and the converted metadata annotation text is revised or sent directly according to the manual review results.
[0057] In this implementation, by using ISO20022 as the standard communication message structure and Json format as the basic message format, a message management solution that can convert multiple message formats is formed, which can ensure that the stored data also meets the standardization requirements, greatly improve the adaptability of message management, greatly improve the revision speed, and improve the accuracy of revised messages.
[0058] In the above implementation, preferably, the received standard message in XML format is converted into a message in JSON format of ISO20022 standard, and the specific process includes:
[0059] The standard message in XML format received by the application interface is converted into a JSON format message based on the ISO20022 standard through the ISO20022 data dictionary.
[0060] like Figure 3 and Figure 4 As shown, specifically, ISO20022 is used as the standard communication message structure, and JSON format is used as the basic message format, forming a new message management solution that can convert multiple message formats. The operator operates the business system to process the business rationality and accounts. After the processing is completed, the business system initiates a "message application" to the message management system. Different from the traditional processing solution, the application interface format needs to use the ISO20022 standard XML format message, and all business systems and operating systems use the same message format.
[0061] During the implementation process, the message management platform receives the message application and converts the standard message application in XML format into the ISO20022 standard JSON format message through the ISO20022 data dictionary. The JSON format is superior to XML in terms of readability, convenience and efficiency, and XML and JSON can be seamlessly converted, so the conversion of XML to JSON format is used here.
[0062] like Figure 5 As shown, in the above implementation, preferably, the JSON format message is verified and processed, and the JSON format message is stored. The specific process includes:
[0063] Perform rationality check, message rule check, security check and message flow processing on the converted JSON format message;
[0064] The preset key fields in the JSON format message are stored in a horizontal table, and the remaining preset fields are stored in the general message field in String format.
[0065] Specifically, unlike traditional storage solutions, it is not necessary to split all message fields and store them in a horizontal table. Most message fields do not have to be continued here. Only the "key fields" related to message management need to be stored in a horizontal table, and the remaining fields are stored in the "general message" field in String format in Json format. Due to the easy-to-read and easy-to-modify characteristics of the Json format, when the general message needs to be modified, only the JsonObj.get() or JsonObj.set() method is needed.
[0066] In the above implementation, preferably, the specific process of converting the comment text of the JSON format message includes:
[0067] Based on a multi-channel unified data dictionary, each field in the JSON format message is annotated and converted into readable text to obtain metadata annotation text.
[0068] In the above implementation, preferably, the converted metadata annotation text is revised or directly sent according to the manual review result, and the specific process includes:
[0069] Manually review the converted metadata annotation text;
[0070] If the manual review result shows that the message is completely correct, the metadata annotation text is mapped one-to-one to the original message and sent directly;
[0071] If the manual review result shows that there is a problem with the message, the metadata annotation text is rendered as an operational interface, the message is revised based on the operational interface, and the message is sent after the review message is completely correct;
[0072] If the manual review result shows that the message is correct but the format is different, the metadata annotation text is converted one-to-one into a new JSON format message, and it is reprocessed and reviewed before being sent.
[0073] During the implementation process, there are three possibilities for regular manual review: (1) the message is completely correct and can be sent directly; (2) there are problems with the message and manual revision is required; (3) the message content is correct, but due to business needs, it needs to be converted to other message formats or converted to other payment channels for sending.
[0074] Since the message formats of different channels are very different, the ISO 20022 standard JSON format messages stored in the database require a "multi-channel unified data dictionary". During the manual review stage, the system needs to convert the stored JSON format messages into "metadata annotation text" through this data dictionary, that is, readable text with annotations on the usage meaning of each field. Figure 5 The "Global BIC Number" field in the manual review data flow example shown contains its name, position in the message, length, value range and other attributes in the "metadata annotation text" after annotation. It can be directly rendered as an interface for modification, or packaged as a message for sending. It can also be quickly converted into the "metadata annotation text" of messages in other formats.
[0075] For the above three possible audit results of manual review:
[0076] (1) The first possibility of manual review. That is, the message is completely correct and is sent directly. In this case, the message management platform maps the "metadata annotation text" to the "original message sent" through a one-to-one field, and sends it directly.
[0077] (2) The second possibility of manual review. That is, there are problems with the message and it needs to be revised manually. In this case, the "metadata annotation text" is directly rendered into an operable VUE interface through the management interface. The teller can complete the revision of the message by directly entering the page fields through the interface. After multiple people review it, the message can be sent again.
[0078] (3) The third possibility of manual review. That is, the message content is correct, but due to business needs, it needs to be converted to other message formats or converted to other payment channels for sending. At this time, due to the huge differences in message structures and data dictionaries of different channels, the "metadata annotation text" needs to be converted into a new Json format message.
[0079] The conversion process is usually implemented with code, but because the "multi-channel unified data dictionary" is used, most of the conversion code can be completed through one-to-one field mapping, which greatly reduces the workload of customized code development. After the conversion is completed, the new message needs to be processed again, as well as the message storage and subsequent manual review and delivery.
[0080] like Figure 6 As shown, according to the above general message management method based on ISO20022 standard, GMH global message management system was independently developed as the operating device of this solution. GMH global message management system provides standard ISO20022 interface to the bank's Swift business system, international settlement system, CIPS business system and core business system. At the same time, it provides message management related functions to the bank's business operation end, including but not limited to: manual approval, queue management, message modification, message conversion and other functions. "Multi-channel unified data dictionary" can quickly describe the fields of stored ISO20022 standard Json messages, so the conversion and revision of messages in actual use are very fast and convenient. Due to the high degree of uniformity of fields, the actual message rationality verification, encryption processing, message encapsulation and compliance transactions can be uniformly processed, and the degree of platformization is greatly improved.
[0081] The present invention further proposes a universal message management system based on the ISO20022 standard, which applies the universal message management method based on the ISO20022 standard disclosed in any one of the above implementation modes, including:
[0082] The message application module is used to initiate a message application to the message management system after business processing based on the business system, and the application interface adopts the ISO20022 standard;
[0083] The message conversion module is used to convert the received standard message in XML format into the JSON format message of ISO20022 standard;
[0084] The message processing module is used to perform verification and business processing on JSON format messages and store JSON format messages;
[0085] The message review module is used to convert the annotation text of the JSON format message and revise or directly send the converted metadata annotation text according to the manual review results.
[0086] In the above implementation, preferably, the message conversion module is specifically used for:
[0087] The standard message in XML format received by the application interface is converted into a JSON format message based on the ISO20022 standard through the ISO20022 data dictionary.
[0088] In the above implementation, preferably, the message processing module is specifically used for:
[0089] Perform rationality check, message rule check, security check and message flow processing on the converted JSON format message;
[0090] The preset key fields in the JSON format message are stored in a horizontal table, and the remaining preset fields are stored in the general message field in String format.
[0091] In the above implementation, preferably, the message review module is specifically used for:
[0092] Based on a multi-channel unified data dictionary, each field in the JSON format message is annotated and converted into readable text to obtain metadata annotation text.
[0093] In the above implementation, preferably, the message review module is also used for:
[0094] Manually review the converted metadata annotation text;
[0095] If the manual review result shows that the message is completely correct, the metadata annotation text is mapped one-to-one to the original message and sent directly;
[0096] If the manual review result shows that there is a problem with the message, the metadata annotation text is rendered as an operational interface, the message is revised based on the operational interface, and the message is sent after the review message is completely correct;
[0097] If the manual review result shows that the message is correct but the format is different, the metadata annotation text is converted one-to-one into a new JSON format message, and it is reprocessed and reviewed before being sent.
[0098] According to the universal message management system based on the ISO20022 standard disclosed in the above implementation mode, the functions to be implemented by each module thereof correspond to the steps of the universal message management method based on the ISO20022 standard disclosed in the above implementation mode. During the implementation process, operations are performed with reference to the above implementation mode, which will not be repeated here.
[0099] According to the general message management method and system based on ISO20022 standard disclosed in the above implementation mode, the GMH global message management system is used as the operating device of this verification solution. In actual use, it can solve all the problems of the existing message management solution and has more advantages, as detailed as follows:
[0100] a) Standardization: One of the directions of commercial bank technology development is service standardization and data standardization. Compared with traditional message management solutions, this solution can perfectly achieve this goal. The services provided to the outside world are standard ISO20022 interfaces, which meet the service standardization requirements. Data storage also uses a multi-channel unified data dictionary to ensure that the stored data also meets the standardization requirements.
[0101] b) High adaptability: Compared with traditional message management solutions, this solution greatly improves the adaptability of message management. In particular, when existing commercial banks connect to multiple payment channels, they can revise messages for all channels through one or one type of management page, without the need for one revision page for each channel or even one message, which greatly improves the adaptability of message management. And with the increase in overseas banks or overseas branches of domestic commercial banks, the differences in message management due to different countries and regions will increase. Only highly adaptable message management solutions can effectively balance the contradiction between system security and stable operation.
[0102] c) Fast speed: The fast speed of this message management solution is mainly reflected in the new message. The payment channel will regularly add or revise the message. In the conventional message management, the message function is strongly bound to the code, so the message revision function is very cumbersome, which seriously restricts the speed of revising the message. The message management solution of the present invention adopts the standard ISO20022 specification internally and adopts a unified data dictionary to maximize the elimination of the code binding problem. Therefore, most of the message revisions encountered in actual use can be completed through the configuration file, and the revision speed is greatly improved.
[0103] d) High accuracy: Since ISO20022 is an international financial standard, the accuracy and applicability of its data dictionary are very high. The value range is further standardized through a unified data dictionary, so the value range of the teller's revised message is very accurate. There will be no unreasonable message that cannot be used due to the teller entering the wrong value range.
[0104] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A general message management method based on ISO20022 standard, characterized in that: include: After business processing based on the business system, a message application is initiated to the message management system, and the application interface adopts the ISO20022 standard; Convert the received XML format standard message into ISO20022 standard JSON format message; Performing verification and business processing on the JSON format message, and storing the JSON format message; The JSON format message is converted into an annotation text, and the converted metadata annotation text is revised or directly sent according to the manual review result.
2. The universal message management method based on the ISO20022 standard according to claim 1 is characterized in that: The process of converting the received standard message in XML format into a message in JSON format in ISO20022 standard includes: The standard message in XML format received by the application interface is converted into a JSON format message based on the ISO20022 standard through the ISO20022 data dictionary.
3. The universal message management method based on the ISO20022 standard according to claim 2 is characterized in that: Verification and business processing are performed on the JSON format message, and the JSON format message is stored. The specific process includes: Performing rationality check, message rule check, security check and message flow processing on the converted JSON format message; The preset key fields in the JSON format message are stored in a horizontal table, and the remaining preset fields are stored in a general message field in a String format.
4. The universal message management method based on the ISO20022 standard according to claim 3 is characterized in that: The specific process of converting the annotation text of the JSON format message includes: Based on a multi-channel unified data dictionary, each field in the JSON format message is annotated and converted into readable text to obtain metadata annotation text.
5. The universal message management method based on ISO20022 standard according to claim 4 is characterized in that: The converted metadata annotation text is revised or sent directly according to the manual review results. The specific process includes: Manually reviewing the metadata annotation text obtained by conversion; If the manual review result shows that the message is completely correct, the metadata annotation text is mapped one-to-one to the original message and sent directly; If the manual review result shows that there is a problem with the message, the metadata annotation text is rendered as an operable interface, the message is revised based on the operable interface, and the message is sent after the message is reviewed to be completely correct; If the manual review result shows that the message is correct but the format is different, the metadata annotation text is converted one-to-one into a new JSON format message, and is reprocessed and reviewed before being sent.
6. A universal message management system based on ISO20022 standard, characterized in that: The general message management method based on the ISO20022 standard as claimed in any one of claims 1 to 5 is applied, comprising: The message application module is used to initiate a message application to the message management system after business processing based on the business system, and the application interface adopts the ISO20022 standard; The message conversion module is used to convert the received standard message in XML format into the JSON format message of ISO20022 standard; A message processing module, used to perform verification and business processing on the JSON format message, and store the JSON format message; The message review module is used to convert the annotation text of the JSON format message, and revise or directly send the converted metadata annotation text according to the manual review result.
7. The universal message management system based on ISO20022 standard according to claim 6, characterized in that: The message conversion module is specifically used for: The standard message in XML format received by the application interface is converted into a JSON format message based on the ISO20022 standard through the ISO20022 data dictionary.
8. The universal message management system based on ISO20022 standard according to claim 7, characterized in that: The message processing module is specifically used for: Performing rationality check, message rule check, security check and message flow processing on the converted JSON format message; The preset key fields in the JSON format message are stored in a horizontal table, and the remaining preset fields are stored in a general message field in a String format.
9. The universal message management system based on ISO20022 standard according to claim 8, characterized in that: The message audit module is specifically used for: Based on a multi-channel unified data dictionary, each field in the JSON format message is annotated and converted into readable text to obtain metadata annotation text.
10. The universal message management system based on ISO20022 standard according to claim 9, characterized in that: The message audit module is also used for: Manually reviewing the metadata annotation text obtained by conversion; If the manual review result shows that the message is completely correct, the metadata annotation text is mapped one-to-one to the original message and sent directly; If the manual review result shows that there is a problem with the message, the metadata annotation text is rendered as an operable interface, the message is revised based on the operable interface, and the message is sent after the message is reviewed to be completely correct; If the manual review result shows that the message is correct but the format is different, the metadata annotation text is converted one-to-one into a new JSON format message, and is reprocessed and reviewed before being sent.