Financial message conversion method and device, equipment, storage medium and product

Abstract

The invention discloses a financial message conversion method and device, equipment, a storage medium and a product, and relates to the technical field of financial messages, and the method comprises the steps: carrying out the analysis of a financial source message according to a message format file and interface structural data of the financial source message, and obtaining a multi-channel message; performing format conversion on the multi-channel message through a conversion mapping rule to obtain an internal format message, the internal format message being used for format decoupling between the multi-channel message and the target channel format message; and performing format conversion on the internal format message to obtain a target channel format message. According to the method, the messages of multiple channels are analyzed, internal format conversion is carried out on the channel messages, the internal format messages are used as middle layers, and the multi-channel messages and the target channel format messages are decoupled, so that the conversion rule number is reduced from the Cartesian product to the sum of the multi-channel message number and the target channel format message number; and the conversion efficiency of the financial message is improved.

Description

Technical Field

[0001] The present application relates to the field of financial message technology, and in particular to a financial message conversion method, device, equipment, storage medium and product. Background Art

[0002] In the financial industry, there are message transmission systems with multiple channels. Various financial message specifications are used internationally and financial messages are defined by various specifications. This results in financial messages in different standard formats and poor universal readability of financial messages.

[0003] Since the standard formats of messages from different channels are not unified, there is a problem of high workload and low efficiency for financial practitioners to manually convert messages. Summary of the invention

[0004] The main purpose of this application is to provide a financial message conversion method, device, equipment, storage medium and product, aiming to solve the technical problems of inconsistent standard formats of messages from different channels and low efficiency of manual message conversion.

[0005] To achieve the above objectives, the present application proposes a financial message conversion method, the method comprising:

[0006] Parsing the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message;

[0007] Performing format conversion on the multi-channel message by conversion mapping rules to obtain an internal format message, wherein the internal format message is used for format decoupling between the multi-channel message and the target channel format message;

[0008] The internal format message is format converted to obtain a target channel format message.

[0009] In one embodiment, the conversion mapping rule includes a one-to-one rule, a one-to-many rule or a many-to-one rule, and the internal format message includes at least one of a field path of a multi-channel message, a field path of an internal format message, a mapping processing function, a beginning character identifier of a field of a multi-channel message, and an extension class path name with a package name; the step of converting the format of the multi-channel message by using the conversion mapping rule to obtain the internal format message includes:

[0010] Mapping a field in the multi-channel message to a field in the internal message format according to the one-to-one rule to perform format conversion to obtain an internal format message;

[0011] Or, mapping a field in the multi-channel message to multiple fields in the internal message format through the one-to-many rule to perform format conversion to obtain an internal format message;

[0012] Or, the multiple fields in the multi-channel message are mapped to a field in the internal message format through the many-to-one rule to perform format conversion to obtain the internal format message.

[0013] In one embodiment, the step of converting the format of the multi-channel message by using the conversion mapping rule to obtain the internal format message includes:

[0014] Performing format conversion on the multi-channel messages according to conversion mapping rules to obtain internal conversion messages;

[0015] According to the technical implementation provided rules, preset abnormal information extension fields and financial source messages, the internal conversion message is structurally extended and converted to obtain an internal format message.

[0016] In one embodiment, before the step of converting the internal format message to obtain the target channel format message, the step further includes:

[0017] When the operation of format conversion of the multi-channel message through the conversion mapping rule fails, the Map structure of the multi-channel message is retrieved and assigned values ​​through a hard-coded extension implementation class to convert it into an internal format message. The hard-coded extension implementation class includes channel general message extension, specific message type extension and component extension.

[0018] In one embodiment, before the step of converting the internal format message to obtain the target channel format message, the step further includes:

[0019] When there is a failure in the preset field mapping in the operation of format conversion of the multi-channel message through the conversion mapping rule, the multi-channel message is format converted through the extended class path name with the package name corresponding to the pre-configured custom function to obtain an internal format message.

[0020] In one embodiment, after the step of converting the format of the internal format message to obtain the target channel format message, the step further includes:

[0021] The target channel format message is converted into a visual message, and the visual message is sent to a user terminal, wherein the visual message includes HTML table data and explanations of message fields.

[0022] In addition, to achieve the above-mentioned purpose, the present application also proposes a financial message conversion device, the financial message conversion device comprising:

[0023] A message parsing module, used to parse the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message;

[0024] An internal conversion module, used to perform format conversion on the multi-channel message through a conversion mapping rule to obtain an internal format message, wherein the internal format message is used for format decoupling between the multi-channel message and the target channel format message;

[0025] The target conversion module is used to perform format conversion on the internal format message to obtain a target channel format message.

[0026] In addition, to achieve the above-mentioned purpose, the present application also proposes a financial message conversion device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the financial message conversion method described above.

[0027] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the financial message conversion method described above are implemented.

[0028] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the financial message conversion method described above are implemented.

[0029] The present application provides a financial message conversion method, which identifies and parses Swift, Swift ISO, CIPS, FXPS, MX and MT channel messages, converts the parsed message data into an internal message format according to the conversion mapping rules, and then converts it into a target channel message format through the internal format message. This embodiment parses messages from multiple channels, performs internal format conversion on the channel messages, and uses the internal format message as an intermediate layer to freely determine the target message channel to be converted, decouples the multi-channel messages from the target channel format messages, thereby reducing the number of conversion rules from the Cartesian product to the number of multi-channel messages plus the number of target channel format messages, greatly reducing the number and repetitiveness of the rules, reducing the repetitive work of developers, and improving the conversion efficiency of financial messages. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0032] Figure 1 A flowchart of the first embodiment of the financial message conversion method of the present application is provided;

[0033] Figure 2 A flowchart of the second embodiment of the financial message conversion method of the present application is provided;

[0034] Figure 3 A flowchart of the third embodiment of the financial message conversion method of the present application is provided;

[0035] Figure 4 A schematic diagram of the overall process of the financial message conversion method provided in this application;

[0036] Figure 5 This is a schematic diagram of the module structure of the financial message conversion device according to an embodiment of the present application;

[0037] Figure 6 Schematic diagram of the device structure of the hardware operating environment involved in the financial message conversion method in the embodiment of the present application.

[0038] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0039] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0040] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0041] The main solution of the embodiment of the present application is: to parse the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message; to convert the format of the multi-channel message through conversion mapping rules to obtain an internal format message, and the internal format message is used for format decoupling between the multi-channel message and the target channel format message; to convert the format of the internal format message to obtain a target channel format message.

[0042] In the prior art, there are multiple channels of message transmission systems in the financial industry, and various financial message specifications are used internationally, and financial messages are defined in various specifications, which leads to the existence of financial messages with different standard formats, and the universal readability of financial messages is poor. Due to the non-uniform standard formats of messages from different channels, there is a problem of large workload and low efficiency for financial practitioners to manually convert messages.

[0043] The present application provides a solution by identifying and parsing financial source messages from multiple channels, converting the parsed message data into an internal message format according to conversion mapping rules, and then converting it into a target channel message format through the internal message. The present application parses messages from multiple channels, performs internal format conversion on channel messages, and uses the internal message format as an intermediate layer to freely determine the target message channel to be converted, decouple the source message from the target message, and thereby reduce the number of conversion rules from the Cartesian product to the number of source messages plus the number of target message formats, greatly reducing the number and repetitiveness of rules, reducing the duplication of developers, and improving the conversion efficiency of financial messages.

[0044] It should be noted that the execution subject of the method of this embodiment can be a computing service device with financial message conversion, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc.; it can also be a financial message conversion device with the same or similar functions. This embodiment and the following embodiments will be described by taking the financial message conversion device as an example.

[0045] Based on this, the present application embodiment provides a financial message conversion method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the financial message conversion method of the present application.

[0046] In this embodiment, the financial message conversion method includes steps S10 to S30:

[0047] Step S10, parsing the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message.

[0048] It is understandable that financial source messages from various channels can be received. Source messages refer to structured data received by the system, including but not limited to message format files, JSON data structures, and XML data structures. Financial source messages can include messages from channels such as Swift, SWIFT ISO, CIPS, MX, MT, and FXPS. Then, a unified message parsing engine is used to parse the message format files and interface structured data according to various message format templates of financial source messages from different channels. The corresponding template parsing package can be plugged in according to the message format requirements to form multi-channel messages. Channel message parsing generation and message conversion are divided into two functional packages. The message conversion package is only responsible for content field mapping and is decoupled from the message.

[0049] Step S20, performing format conversion on the multi-channel message by conversion mapping rules to obtain an internal format message, wherein the internal format message is used for format decoupling between the multi-channel message and the target channel format message.

[0050] It is understandable that the financial message channel structured object corresponding to the multi-channel message can be converted into a unified internal JSON message object format according to the preset conversion mapping rules to obtain the internal format message. The financial message channel structured object refers to the internal structure organization of the standardized message used to exchange information in financial transactions. The original financial message channel can be converted into the internal message object structure by using the conversion tool to generate a message conversion mapping rule file from the rule mapping description file. The original financial message structured object is converted into the internal JSON message format through the message conversion mapping rule file. The message fields are all strings by default, and the content mapping uniformly uses the String type. By using the internal format message as the middle layer, the target message channel to be converted can be freely determined, and the multi-channel message and the target channel format message are decoupled, so as to reduce the number of conversion rules from the Cartesian product to the number of multi-channel messages plus the number of target channel format messages, which greatly reduces the number and repetitiveness of the rules. The digital asset precipitation of the conversion rules is realized through the conversion rules and the internal message specifications, and the conversion rules are separated from the internal messages themselves, which reduces the difficulty of customized implementation of the conversion rules by each financial institution customer, and further reduces the investment of manpower and the accumulation of data assets.

[0051] Step S30, converting the internal format message to obtain a target channel format message.

[0052] It should be understood that the target channel format message is obtained by converting the internal format message into a target channel message structured object.

[0053] The present embodiment is described here with reference to a specific example. For example, by converting the source message MT103 of the SWIFT system into the target cross-border RMB system message cips.111.001.03 message, the corresponding MT103 and internal remittance message conversion mapping rules can be found through the source MT103 message. And then converted into an internal remittance message standard structured object through the conversion mapping rule, that is, an internal format message is obtained. Then, the internal format message is output as the cips.111.001.03 message in the cross-border RMB system through the cips.111.001.03 message and the internal remittance message conversion mapping rule, and the functions such as message forwarding and VOSTRO remittance can be realized without manual intervention after automatic conversion, reducing the risk of personnel intervention and misoperation.

[0054] This embodiment provides a financial message conversion method, which identifies and parses Swift, Swift ISO, CIPS, FXPS, MX and MT channel messages, converts the parsed message data into an internal message format according to the conversion mapping rules, and then converts it into a target channel message format through the internal format message. This embodiment parses messages from multiple channels, performs internal format conversion on the channel messages, and uses the internal format message as an intermediate layer to freely determine the target message channel to be converted, decouples the multi-channel messages from the target channel format messages, thereby reducing the number of conversion rules from the Cartesian product to the number of multi-channel messages plus the number of target channel format messages, greatly reducing the number and repetitiveness of the rules, reducing the repetitive work of developers, and improving the conversion efficiency of financial messages.

[0055] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 2 , the conversion mapping rule includes a one-to-one rule, a one-to-many rule or a many-to-one rule, the internal format message includes at least one of a field path of a multi-channel message, a field path of an internal format message, a mapping processing function, a beginning character identifier of a field of a multi-channel message, and an extension class path name with a package name; step S20, the financial message conversion method further includes steps S201 to S203:

[0056] Step S201 : Mapping a field in the multi-channel message to a field in the internal message format according to the one-to-one rule to perform format conversion to obtain an internal format message.

[0057] It should be understood that when converting the format of a multi-channel message, the fields can be mapped through conversion mapping rules to convert it into an internal format message. Among them, the conversion mapping rule may include a one-to-one rule, and the one-to-one rule is to map a field in the multi-channel message to a field in the internal message format for format conversion, thereby obtaining an internal format message. The conversion mapping rule can be configured in advance using Excel and converted to Json provider program reading through a tool. The configuration items included in the conversion mapping rule include the field path of the multi-channel message, the field path of the internal format message, the mapping processing function, the beginning character identifier of the field of the multi-channel message, and at least one of the extension class path name with the package name.

[0058] Take MT to MX as an example to explain the configuration column:

[0059] The message path, including the field path sourcePath of multi-channel messages and the field path targetPath of internal format messages, needs to be separated by ' / ' when multiple levels are involved. If a subdomain is a cyclic domain, it needs to be separated by '#'. The name of each level should be consistent with the capitalization of the attribute defined in the corresponding core package; for example: f71G / currency means the subdomain currency of the MT103 message field f71G; f71F#f71F / currency means the subdomain currency of the mapping f71F, and # means f71F is a cyclic domain;

[0060] sourcePath indicates the field path of the MT message;

[0061] targetPath indicates the corresponding path in pacs008;

[0062] funcName represents the mapping processing logic, and each option matches a background processing function;

[0063] param-controlString indicates that the mt field begins with a certain character, such as account= / 34x;

[0064] The field Extend Class indicates that when funcName is 8-custom function, you need to fill in the custom path with package name.

[0065] Step S202, or, mapping a field in the multi-channel message to multiple fields in the internal message format through the one-to-many rule to perform format conversion to obtain an internal format message.

[0066] It can be understood that the conversion mapping rules can also include one-to-many rules. The one-to-many rules are to map a field in a multi-channel message to multiple fields in an internal message. Through the one-to-many rules, a field in a multi-channel message can be mapped to multiple fields in the internal message format for format conversion to obtain an internal format message.

[0067] Step S203, or, mapping multiple fields in the multi-channel message to a field in the internal message format through the many-to-one rule to perform format conversion to obtain an internal format message.

[0068] It can be understood that the conversion mapping rules can also include one-to-many rules. The many-to-one rule is to map multiple fields in the source message / multi-channel message / target message to a field in the internal message. Through the many-to-one rule, multiple fields in the multi-channel message can be mapped to a field in the internal message format for format conversion to obtain an internal format message.

[0069] It should be noted that the above-mentioned one-to-one, one-to-many, many-to-one and other types of conversion mapping rules can be reversely mapped, that is, the internal format message is converted into the target channel format message and the financial source message. Flexible conversion algorithms and strategies are provided to meet the diversity of business needs; ensure that the generated messages comply with relevant standards and specifications and can be correctly parsed and processed by the target system.

[0070] In a feasible implementation manner, step S20 may further include steps S204 to S205:

[0071] Step S204: convert the format of the multi-channel message according to the conversion mapping rule to obtain an internal conversion message.

[0072] Step S205, performing structural extension conversion on the internal conversion message according to the rules provided by the technical implementation, the preset abnormal information extension field and the financial source message to obtain an internal format message.

[0073] It should be understood that here, the process of converting and converting multi-channel messages into internal format messages by means of conversion and mapping rules is explained in combination with examples. Based on SWIFT ISO, the existing financial messages such as CIPS, FXPS, MX, and MT are structurally expanded, and rules, abnormal information extension fields, and financial source messages are provided for technical implementation. The information extension structure forms the Jinxin Financial Internal Message 1.0, and the internal message structure is stored in the JSON data format that is easy to read, store, transmit, and expand.

[0074] It is understandable that when converting financial messages, the technical implementation provides rules that refer to a set of rules and standards established by technical means in the process of converting financial messages to ensure that messages of different formats can be accurately and efficiently converted and interoperable. The abnormal information extension field is a pre-set extended information field for handling abnormal situations. It refers to a special field in the message used to record and transmit abnormal situation information. These fields enable financial institutions to quickly identify and respond to abnormal situations when processing cross-border payments, such as remittance refunds and erroneous transactions.

[0075] In this embodiment, the internal conversion message is structurally expanded by providing rules, abnormal information extension fields, and information such as the original incoming message through technical implementation, so that the message can be further converted into a more standardized internal message.

[0076] In this embodiment, by providing complex conversion scenarios such as one-to-one, one-to-many, and many-to-one, channel messages are converted to internal messages, and flexible conversion algorithms and strategies are provided to meet the diversity of business needs; and in the conversion mapping rules, the field path of the multi-channel message, the field path of the internal message format, the mapping processing function, the beginning character identifier of the field of the multi-channel message, and the extension class path name with the package name and other configuration items are configured, so that the message can be converted into a more standardized internal message, ensuring that the generated message complies with the relevant standards and specifications and can be correctly parsed and processed by the target system.

[0077] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above description, and will not be described in detail later. Figure 3 Before step S30, step A20 may also be included:

[0078] Step A20, when the operation of format conversion of the multi-channel message through the conversion mapping rule fails, the Map structure of the multi-channel message is retrieved and assigned values ​​through the hard-coded extension implementation class to convert it into an internal format message. The hard-coded extension implementation class includes channel general message extension, specific message type extension and component extension.

[0079] It is worth noting that in addition to configuring the conversion mapping rules, some special scenarios cannot be implemented through configuration and need to be handled through hard-coded extension implementation classes. This type of implementation class mainly performs value acquisition and assignment operations on the Map structure of the original message and the Map structure of the target message. There are three main types of extension implementation classes:

[0080] Channel general message extension: the parse method indicates that the internal message is converted to the target message, and the format method indicates that the source message is converted to the internal message;

[0081] Extension of specific message types: the parse method indicates that the internal message is converted to the target message, and the format method indicates that the source message is converted to the internal message;

[0082] Component extension: Add bank combination domain and customer group domain components to simplify mapping configuration. Take MT103 as an example. There are combination domains related to the correspondent bank such as f52, f53, f54, f55, f56, f57, and combination domains related to the customer such as f50, f59 in the message.

[0083] In this embodiment, for some special scenarios that cannot be implemented through configuration except for configuring message mapping relationships, class processing is implemented through hard-coded extensions. This type of implementation class mainly obtains and assigns values ​​to the Map structure of the original message and the Map structure of the target message, thereby being able to handle situations that cannot be implemented through configuration and improving the accuracy of message conversion.

[0084] In another feasible implementation manner, before step S30, step B20 may also be included:

[0085] Step B20: When there is a failure in the preset field mapping in the operation of format conversion of the multi-channel message through the conversion mapping rule, the multi-channel message is format converted through the extended class path name with the package name corresponding to the pre-configured custom function to obtain an internal format message.

[0086] It should be noted that in message conversion, when there is a preset field mapping failure in the operation of format conversion of multi-channel messages through conversion mapping rules, that is, there are fields that cannot be directly mapped, it can be achieved through custom functions and by configuring custom function names. For example, if a column cannot be directly mapped, you can map the funcName column to 8-custom function, and fill in the path name of the extension class with the package name in the custom function column. The extension class needs to implement the MappingFunction interface.

[0087] In this embodiment, when there is a failure in the mapping of preset fields in the operation of format conversion of multi-channel messages through conversion mapping rules, the format of the multi-channel messages is converted by the extended class path name with the package name corresponding to the pre-configured custom function, so that when a column cannot be directly mapped, the conversion of the message field can be achieved by setting a custom function.

[0088] In another feasible implementation manner, after step S30, step S40 may also be included:

[0089] Step S40, converting the target channel format message into a visual message, and sending the visual message to the user terminal, wherein the visual message includes HTML table data and explanations of message fields.

[0090] It is understandable that after converting the internal JSON message format into the target channel message structured object, the target channel message structure can be output through a unified message parsing engine, which can be structured data in JSON / XML format. At the same time, it supports converting the target channel format message into a visual message, which can include visual HTML table data and Chinese explanations of message fields, and then sends the visual message to the user terminal, so that financial practitioners can view the message more conveniently.

[0091] In this embodiment, the target channel format message is converted into a visual message including HTML table data and explanations of the message fields, and the visual message is sent to the user terminal for financial practitioners to view, thereby improving the readability of the message and facilitating viewing by financial personnel.

[0092] In this embodiment, the conversion rules are digitized and deposited as assets through conversion rules and internal message specifications, and the conversion rules are separated from the internal messages themselves, thereby reducing the difficulty of customized conversion rules for customers of various financial institutions, further reducing manpower investment and accumulation of data assets, and realizing functions such as message forwarding and VOSTRO remittance without human intervention through automated conversion, thereby reducing the risk of human intervention and misoperation.

[0093] For example, to help understand the implementation process of the financial message conversion method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 4 , Figure 4 A schematic diagram of the overall process of a financial message conversion method is provided, specifically:

[0094] Through the unified message parsing engine, the message format files and interface structured data are parsed according to various message format templates of channels such as Swift, Swift ISO, CIPS, FXPS, MX and MT. According to the conversion rules, the corresponding financial message channel structured objects are converted into the unified internal JSON message object format. The original financial message channel can be converted into the internal message object structure by using the conversion tool to generate the message conversion mapping rule file from the rule mapping description file, and the original financial message structured object is converted into the internal JSON message format through the message conversion mapping rule file. For some special scenarios that cannot be implemented through configuration, they need to be handled through hard-coded extension implementation classes. Then, it is converted into the target channel message structured object through the internal JSON message format. Then, the target channel message structure or JSON / XML structured data can be output through the unified message parsing engine, and it also supports conversion into visual HTML table data and Chinese explanation of message fields to provide financial practitioners with more convenient message viewing.

[0095] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the financial message conversion method of the present application. More forms of simple transformations based on this technical concept are all within the scope of protection of the present application.

[0096] This application also provides a financial message conversion device, please refer to Figure 5 , the financial message conversion device comprises:

[0097] A message parsing module 10, configured to parse the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message;

[0098] The internal conversion module 20 is used to convert the format of the multi-channel message through the conversion mapping rule to obtain an internal format message, wherein the internal format message is used for format decoupling between the multi-channel message and the target channel format message;

[0099] The target conversion module 30 is used to perform format conversion on the internal format message to obtain a target channel format message.

[0100] The financial message conversion device provided by the present application adopts the financial message conversion method in the above embodiment to solve the technical problem. Compared with the prior art, the beneficial effects of the financial message conversion device provided by the present application are the same as the beneficial effects of the financial message conversion method provided by the above embodiment, and other technical features in the financial message conversion device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0101] The present application provides a financial message conversion device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the financial message conversion method in the above-mentioned embodiment one.

[0102] Reference below Figure 6 , which shows a schematic diagram of the structure of a financial message conversion device suitable for implementing the embodiment of the present application. The financial message conversion device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The financial message conversion device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0103] like Figure 6As shown, the financial message conversion device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM) 1004. In the RAM 1004, various programs and data required for the operation of the financial message conversion device are also stored. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the financial message conversion device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a financial message conversion device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0104] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0105] The financial message conversion device provided by the present application adopts the financial message conversion method in the above embodiment, which can solve the technical problem of financial message conversion. Compared with the prior art, the beneficial effects of the financial message conversion device provided by the present application are the same as the beneficial effects of the financial message conversion method provided by the above embodiment, and other technical features in the financial message conversion device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0106] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0107] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0108] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the financial message conversion method in the above-mentioned embodiment.

[0109] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0110] The computer-readable storage medium may be included in the financial message conversion device; or may exist independently without being assembled into the financial message conversion device.

[0111] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the financial message conversion device, the financial message conversion device: parses the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message; performs format conversion on the multi-channel message through conversion mapping rules to obtain an internal format message, and the internal format message is used for format decoupling between the multi-channel message and the target channel format message; performs format conversion on the internal format message to obtain a target channel format message.

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

[0113] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0114] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0115] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned financial message conversion method, and can solve the technical problem. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the financial message conversion method provided in the above-mentioned embodiment, and will not be repeated here.

[0116] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned financial message conversion method when executed by a processor.

[0117] The computer program product provided by the present application can solve the technical problem. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the financial message conversion method provided by the above embodiment, which will not be elaborated here.

[0118] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A financial message conversion method, characterized in that: The method includes: Parsing the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message; Performing format conversion on the multi-channel message by conversion mapping rules to obtain an internal format message, wherein the internal format message is used for format decoupling between the multi-channel message and the target channel format message; The internal format message is format converted to obtain a target channel format message.

2. The method according to claim 1, characterized in that The conversion mapping rule includes a one-to-one rule, a one-to-many rule or a many-to-one rule, and the internal format message includes at least one of a field path of a multi-channel message, a field path of an internal format message, a mapping processing function, a beginning character identifier of a field of a multi-channel message, and an extension class path name with a package name; The step of converting the format of the multi-channel message by converting the mapping rule to obtain the internal format message includes: Mapping a field in the multi-channel message to a field in the internal message format according to the one-to-one rule to perform format conversion to obtain an internal format message; Or, mapping a field in the multi-channel message to multiple fields in the internal message format through the one-to-many rule to perform format conversion to obtain an internal format message; Or, the multiple fields in the multi-channel message are mapped to a field in the internal message format through the many-to-one rule to perform format conversion to obtain the internal format message.

3. The method according to claim 1, characterized in that The step of converting the format of the multi-channel message by converting the mapping rule to obtain the internal format message includes: Performing format conversion on the multi-channel messages according to conversion mapping rules to obtain internal conversion messages; According to the technical implementation provided rules, preset abnormal information extension fields and financial source messages, the internal conversion message is structurally extended and converted to obtain an internal format message.

4. The method according to claim 1, characterized in that Before the step of converting the internal format message to obtain the target channel format message, the step further includes: When the operation of format conversion of the multi-channel message through the conversion mapping rule fails, the Map structure of the multi-channel message is retrieved and assigned values ​​through a hard-coded extension implementation class to convert it into an internal format message. The hard-coded extension implementation class includes channel general message extension, specific message type extension and component extension.

5. The method according to claim 1, characterized in that Before the step of converting the internal format message to obtain the target channel format message, the step further includes: When there is a failure in the preset field mapping in the operation of format conversion of the multi-channel message through the conversion mapping rule, the multi-channel message is format converted through the extended class path name with the package name corresponding to the pre-configured custom function to obtain an internal format message.

6. The method according to any one of claims 1 to 5, characterized in that After the step of converting the internal format message to obtain the target channel format message, the method further includes: The target channel format message is converted into a visual message, and the visual message is sent to a user terminal, wherein the visual message includes HTML table data and explanations of message fields.

7. A financial message conversion device, characterized in that: The financial message conversion device comprises: A message parsing module, used to parse the financial source message according to the message format file and interface structured data of the financial source message to obtain a multi-channel message; An internal conversion module, used to perform format conversion on the multi-channel message through a conversion mapping rule to obtain an internal format message, wherein the internal format message is used for format decoupling between the multi-channel message and the target channel format message; The target conversion module is used to perform format conversion on the internal format message to obtain a target channel format message.

8. A financial message conversion device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the financial message conversion method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the financial message conversion method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the financial message conversion method according to any one of claims 1 to 6 are implemented.

Images