CN111447257A - Message conversion method and device - Google Patents
Message conversion method and device Download PDFInfo
- Publication number
- CN111447257A CN111447257A CN202010158655.7A CN202010158655A CN111447257A CN 111447257 A CN111447257 A CN 111447257A CN 202010158655 A CN202010158655 A CN 202010158655A CN 111447257 A CN111447257 A CN 111447257A
- Authority
- CN
- China
- Prior art keywords
- message
- node
- conversion
- data object
- intermediate data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Communication Control (AREA)
Abstract
The invention discloses a message conversion method and a message conversion device, and relates to the technical field of computers. The method comprises the following steps: calling a first message adapter corresponding to the received original message according to the message format of the original message, and performing format conversion on the original message based on the first message adapter to obtain an intermediate data object; converting the content of the intermediate data object based on a message conversion configuration table to obtain a target data object; and calling a second message adapter corresponding to the target message according to the message format of the target message, and performing format conversion on the target data object based on the second message adapter to obtain the target message. Through the steps, various types of messages can be converted, and the problems that the existing hard coding message conversion mode is poor in universality and cannot be popularized quickly are solved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for message conversion.
Background
At present, application service systems of different organizations usually have differences in message formats and contents, which affects system interaction among different organizations to a certain extent. In the prior art, corresponding message conversion codes are often customized and developed in a hard coding mode according to different access channels and different message formats.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: because hard codes in the prior art are more and are customized development, new applications are redeployed for new access channels; almost has no universality, can not be produced and can not be popularized quickly.
Disclosure of Invention
In view of the above, the present invention provides a message conversion method and device, which can convert various types of messages, and solve the problems of poor generality, inability to promote quickly, and the like of the existing hard-coded message conversion method.
To achieve the above object, according to one aspect of the present invention, a message conversion method is provided.
The message conversion method of the invention comprises the following steps: calling a first message adapter corresponding to the received original message according to the message format of the original message, and performing format conversion on the original message based on the first message adapter to obtain an intermediate data object; converting the content of the intermediate data object based on a message conversion configuration table to obtain a target data object; and calling a second message adapter corresponding to the target message according to the message format of the target message, and performing format conversion on the target data object based on the second message adapter to obtain the target message.
Optionally, the original packet includes a FIX packet, an XM L packet, or a JSON packet, the intermediate data object and the target data object are Map objects, and the target packet includes a FIX packet, an XM L packet, or a JSON packet.
Optionally, the processing the content of the intermediate data object based on the packet conversion configuration table to obtain the target data object includes: inquiring a message conversion configuration table according to the message code of the original message; under the condition that first message conversion configuration information corresponding to the message code of the original message exists in the message conversion configuration table, processing the content of the intermediate data object according to the first message conversion configuration information to obtain a target data object; and directly taking the intermediate data object as the target data object under the condition that the first message conversion configuration information corresponding to the message code of the original message does not exist in the message conversion configuration table.
Optionally, the processing the content of the intermediate data object according to the first packet conversion configuration information to obtain a target data object includes: circularly acquiring each message node of the intermediate data object; when the node type of the message node in the intermediate data object is a leaf node, performing message node conversion processing according to the conversion rule of the message node in the first message conversion configuration information; and when the node type of the message node in the intermediate data object is a non-leaf node, performing recursive processing on the message node until the leaf node under the message node is obtained, and performing conversion processing on the leaf node under the message node.
Optionally, when the node type of the packet node in the intermediate data object is a non-leaf node, performing recursive processing on the packet node until a leaf node below the packet node is obtained, and performing conversion processing on the leaf node below the packet node includes: when the node type of the message node is a non-leaf node, inquiring a message conversion configuration table according to the message code under the message node in the first message conversion configuration information to obtain second message conversion configuration information corresponding to the message code under the message node; circularly acquiring each message node in the second message conversion configuration information; and when the node type of the message node in the second message conversion configuration information is a leaf node, performing message node conversion processing according to the conversion rule of the message node in the second message conversion configuration information.
Optionally, the method further comprises: before the intermediate data object is directly used as the target data object, inquiring a special case message node conversion configuration table and a general message node conversion configuration table according to the message node of the intermediate data object, and confirming that no corresponding node conversion rule exists in the special case message node conversion configuration table and the general message node conversion configuration table.
Optionally, the performing, according to the conversion rule of the packet node in the first packet conversion configuration information, packet node conversion processing includes at least one of the following: data dictionary translation, constant assignment, regular expression replacement, decimal digit supplement and date format conversion.
To achieve the above object, according to another aspect of the present invention, there is provided a message converting apparatus.
The message conversion device of the present invention comprises: the first message adaptation module is used for calling a first message adapter corresponding to the received original message according to the message format of the original message, and carrying out format conversion on the original message based on the first message adapter so as to obtain an intermediate data object; the data conversion module is used for carrying out conversion processing on the content of the intermediate data object based on a message conversion configuration table so as to obtain a target data object; and the second message adaptation module is used for calling a corresponding second message adapter according to the message format of the target message and carrying out format conversion on the target data object based on the second message adapter so as to obtain the target message.
To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.
The electronic device of the present invention includes: one or more processors; and storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors implement the message conversion method of the present invention.
To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable medium.
The computer-readable medium of the present invention has stored thereon a computer program which, when executed by a processor, implements the message conversion method of the present invention.
One embodiment of the above invention has the following advantages or benefits: the method comprises the steps of calling a first message adapter corresponding to a received original message according to the message format of the original message, carrying out format conversion on the original message based on the first message adapter to obtain an intermediate data object, carrying out conversion processing on the content of the intermediate data object based on a message conversion configuration table to obtain a target data object, calling a second message adapter corresponding to the target message according to the message format of the target message, and carrying out format conversion on the target data object based on the second message adapter to obtain the target message.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic main flow chart of a message conversion method according to a first embodiment of the present invention;
fig. 2 is a schematic main flow chart of a message conversion method according to a second embodiment of the present invention;
FIG. 3 is a schematic flow chart showing the steps of data conversion processing in the second embodiment of the present invention;
FIG. 4 is a schematic diagram of an alternative embodiment of step S304 in FIG. 3;
fig. 5 is a schematic main flow chart of a message conversion method according to a third embodiment of the present invention;
fig. 6 is a schematic diagram of main modules of a message conversion apparatus according to a fourth embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
FIG. 8 is a schematic block diagram of a computer system suitable for use with the electronic device to implement an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic main flow chart of a message conversion method according to a first embodiment of the present invention. As shown in fig. 1, the message conversion method according to the embodiment of the present invention includes:
step S101, calling a first message adapter corresponding to the received original message according to the message format of the original message, and performing format conversion on the original message based on the first message adapter to obtain an intermediate data object.
Illustratively, the original message (which may also be referred to as an "access message") includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript object Notification), which is an open standard data exchange format based on a subset of JavaScript syntax.
The method comprises the steps of obtaining a first message adapter, a first message adapter and a second message adapter, wherein the first message adapter can be called as a front message adapter and used for converting an original message into an intermediate data object, and the first message adapter can be preset with multiple types, such as FIX message to intermediate data object, XM L message to intermediate data object, JSON message to intermediate data object and other types of message adapters.
Illustratively, the intermediate data object may be a Map object. A Map object is an object that maps a key to a value, and has the following properties: a mapping cannot contain duplicate keys, each of which can only map to one value at most. It should be noted that the intermediate data object may also be other forms of objects without affecting the implementation of the present invention.
And step S102, converting the content of the intermediate data object based on the message conversion configuration table to obtain a target data object.
The message conversion configuration table may include message conversion configuration information such as a message node mapping relationship (or referred to as a "conversion rule of a message node"). The message node mapping relationship defines a mapping relationship between message nodes. In specific implementation, one key value pair in the intermediate data object can be regarded as a message node, and the message node mapping relation indicates what key value pair each key value pair in the intermediate data object is to be converted into and the value in the key value pair is not to be changed.
Wherein the target data object is in the same format as the intermediate data object. For example, when the intermediate data object is a Map object, the target data object is also a Map object. In this step, the conversion process performed on the content of the intermediate data object includes, but is not limited to: data dictionary translation, constant assignment, regular expression replacement, decimal digit supplement and date format conversion.
Step S103, calling a second message adapter corresponding to the target message according to the message format of the target message, and performing format conversion on the target data object based on the second message adapter to obtain the target message.
Illustratively, the target message includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript Object Notification, which is an open standard data exchange format based on a subset of JavaScript syntax) messages.
In the step, a plurality of types of second message adapters can be preset, such as message adapters of types of converting the target data object into a FIX message, converting the target data object into an XM L message, converting the target data object into a JSON message, and the like.
In the embodiment of the invention, various types of messages can be converted through the steps, and the problems of poor universality, incapability of rapid popularization and the like of the conventional hard coded message conversion mode are solved.
Fig. 2 is a schematic main flow chart of a message conversion method according to a second embodiment of the present invention. As shown in fig. 2, the message conversion method according to the embodiment of the present invention includes:
step S201, calling a first message adapter corresponding to the received original message according to the message format of the original message, and performing format conversion on the original message based on the first message adapter to obtain an intermediate data object.
Illustratively, the original message (which may also be referred to as an "access message") includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript object Notification), which is an open standard data exchange format based on a subset of JavaScript syntax.
Illustratively, the intermediate data object may be a Map object. A Map object is an object that maps a key to a value, and has the following properties: a mapping cannot contain duplicate keys, each of which can only map to one value at most. It should be noted that the intermediate data object may also be other forms of objects without affecting the implementation of the present invention.
The method comprises the steps of obtaining a first message adapter, a first message adapter and a second message adapter, wherein the first message adapter can be called as a front message adapter and used for converting an original message into an intermediate data object, and the first message adapter can be preset with multiple types, such as FIX message to Map object, XM L message to Map object, JSON message to Map object and other types of message adapters.
The following describes in detail a processing flow of converting the format of the original packet based on the first packet adapter to obtain an intermediate data object, taking FIX packet to Map object and JSON packet to Map object as examples.
Exemplarily, when the original packet is a FIX packet, performing format conversion on the original packet based on the first packet adapter to obtain the intermediate data object in the Map format specifically includes: converting the FIX Message into a Message object (the Message object inherits FieldMap and comprises two TreeMap objects, one containing a domain and the other containing a Group) through third-party software (such as a Quickfix Message engine), sequentially reading key-value pairs in the Message object, and putting the read key-value pairs into the Map to obtain an intermediate data object.
Exemplarily, when the original packet is a JSON packet, performing format conversion on the original packet based on the first packet adapter to obtain the intermediate data object in the Map format specifically includes: the JSON message is directly converted into a Map object by a method (such as a JSON.
Step S202, inquiring a message conversion configuration table according to the message code of the original message.
The message conversion configuration table may include a message code and message conversion configuration information corresponding to the message code. In this step, the message conversion configuration table may be queried according to the message code of the original message. When the query result indicates that the first message conversion configuration information corresponding to the message code of the original message exists in the message conversion configuration table, executing step S203; and when the query result indicates that the first message conversion configuration information corresponding to the message code of the original message does not exist in the message conversion configuration table, executing step S204.
Step S203, processing the content of the intermediate data object according to the first message conversion configuration information to obtain a target data object.
Illustratively, the first packet conversion configuration information may include configuration information such as packet node type, packet node mapping relationship (or "conversion rule of packet node"), and the like. The message node types may include leaf nodes and non-leaf nodes, and the message node mapping relationship defines a mapping relationship between message nodes. In specific implementation, one key value pair in the intermediate data object can be regarded as a message node, and the message node mapping relation indicates what key value pair each key value pair in the intermediate data object is to be converted into and the value in the key value pair is not to be changed.
Wherein the target data object is in the same format as the intermediate data object. For example, when the intermediate data object is a Map object, the target data object is also a Map object. In this step, the conversion process performed on the content of the intermediate data object includes, but is not limited to: data dictionary translation, constant assignment, regular expression replacement, decimal digit supplement and date format conversion.
And step S204, directly taking the intermediate data object as a target data object.
When the query result of step S202 indicates that the first packet conversion configuration information corresponding to the packet code of the original packet does not exist in the packet conversion configuration table, the intermediate data object may be directly used as the target data object. That is, in this case, the intermediate data object is identical in format and content to the target data object.
In the embodiment of the invention, the message conversion configuration information is set in the configuration table in advance in the dimension of message coding, and the configuration table is inquired according to the message coding of the access message so as to carry out data content conversion according to the inquired corresponding message conversion configuration information, so that not only can different conversion requirements of different messages be flexibly met, but also the configuration is simple and the expandability is strong.
Step S205, calling a second message adapter corresponding to the target message according to the message format of the target message, and performing format conversion on the target data object based on the second message adapter to obtain the target message.
Illustratively, the target message includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript Object Notification, which is an open standard data exchange format based on a subset of JavaScript syntax) messages.
In the step, a plurality of types of second message adapters can be preset, such as message adapters of types of converting the target data object into a FIX message, converting the target data object into an XM L message, converting the target data object into a JSON message, and the like.
A detailed description will be given below of a processing flow for performing format conversion on the target data object based on the second packet adapter to obtain the target packet, by taking Map object to FIX packet as an example.
Exemplarily, when the target packet is a FIX packet, performing format conversion on the target data object in the Map format based on the second packet adapter to obtain the target packet specifically includes: reading a key value pair in the Map object, and assembling a Message object according to the read key value pair; and processing the Message object (mainly setting Message header and tail information) through third-party software (such as a Quickfix Message engine) to obtain a target Message in a FIX Message format.
In the embodiment of the invention, the steps not only can flexibly meet different conversion requirements of different messages, but also have simple configuration and strong expandability, and the problems of poor universality, incapability of quick popularization and the like of the conventional hard coded message conversion mode are solved.
Fig. 3 is a schematic flow chart of the data conversion processing steps in the second embodiment of the present invention. The flow shown in fig. 3 is a detailed description of step S203 in the embodiment shown in fig. 2. As shown in fig. 3, the data conversion processing steps in the embodiment of the present invention specifically include:
step S301, a message node of the intermediate data object is obtained.
The intermediate data object may be a Map object, and one packet node of the intermediate data object may be a key value pair in the Map object.
Step S302, judging whether the node type of the message node is a leaf node.
In the embodiment of the invention, the node types of the message nodes comprise leaf nodes and non-leaf nodes, wherein the leaf nodes can be understood as bottommost nodes or nodes needing direct conversion processing, the non-leaf nodes can be understood as non-bottommost nodes, further, the non-leaf nodes can be divided into common nodes, common group nodes and dynamic nodes, the common nodes refer to nodes needing to obtain contents from common messages (the common messages refer to the nodes which are extracted from common contents contained in a plurality of messages and placed in one message), the common group nodes refer to L ist (L ist is a linear data structure) nodes contained in the messages, and the dynamic nodes refer to nodes needing dynamic acquisition according to actual services.
Further, when the node type of the message node is a leaf node, step S303 is executed; when the node type of the message node is a non-leaf node, step S304 is executed.
Step S303, performing a message node conversion process according to the conversion rule of the message node in the first message conversion configuration information.
Illustratively, the message node conversion processing according to the conversion rule of the message node includes but is not limited to: data dictionary translation (e.g., incoming value of 1, data dictionary translation result of 01), constant assignment, regular expression replacement, decimal digit complement, date format conversion.
And S304, performing recursion processing on the message node until a leaf node under the message node is obtained, and performing conversion processing on the leaf node under the message node.
In the step, the non-leaf nodes are subjected to recursion processing until the leaf nodes are obtained, and then the leaf nodes are subjected to conversion processing according to the corresponding conversion rules. How step S304 is implemented will be described in detail below with reference to fig. 4.
Step S305, judging whether all message nodes are acquired.
When all the message nodes in the intermediate data object have been acquired, executing step S306; and when all the message nodes are not acquired, executing the step S301 again until all the message nodes of the intermediate data object are acquired.
And S306, assembling to obtain the target data object.
In the embodiment of the invention, the conversion processing of various message contents is realized through the steps, and the content conversion requirements of different messages are met. In specific implementation, only the message conversion configuration information corresponding to each message code needs to be configured in advance, and thus, various messages can be flexibly converted during subsequent conversion processing, so that the flexibility and the expandability of message conversion are improved, and the difficulty in code development and maintenance of message conversion is reduced.
Fig. 4 is a schematic diagram of an alternative embodiment of step S304 in fig. 3. As shown in fig. 4, this alternative embodiment specifically includes:
step S401, inquiring a message conversion configuration table according to the message code under the message node in the first message conversion configuration information to obtain second message conversion configuration information corresponding to the message code under the message node.
The first message conversion configuration information and the second message conversion configuration information are both message conversion configuration information corresponding to message codes, and the difference between the first message conversion configuration information and the second message conversion configuration information is mainly as follows: both belong to message conversion configuration information corresponding to different message codes.
Illustratively, the first packet conversion configuration information may include information such as a node type, a packet encoding under a node, a packet node mapping relationship (or "conversion rule of packet node"), a description of the node, and the like.
The common node is a node which needs to obtain content from a common message (the common message is a node which extracts common content contained in a plurality of messages and puts the common content in one message), the common group node is an L ist (L ist is a linear data structure) node contained in the message, and the dynamic node is a node which needs to dynamically obtain according to actual services.
Wherein the message node mapping relationship defines a mapping relationship between message nodes. In specific implementation, one key value pair in the intermediate data object can be regarded as a message node, and the message node mapping relation indicates what key value pair each key value pair in the intermediate data object is to be converted into and the value in the key value pair is not to be changed.
In this step, when the packet node is a non-leaf node, the packet code under the packet node may be obtained from the first packet conversion configuration information, and the packet conversion configuration table may be queried according to the packet code under the packet node, so as to obtain the second packet conversion configuration information corresponding to the packet code. The second packet conversion configuration information may include, for example, a node type, a packet coding under a node, a packet node mapping relationship (or "conversion rule of packet node"), a description of the node, and so on.
Step S402, each message node in the second message conversion configuration information is obtained in a circulating mode.
Step S403, when the node type of the packet node in the second packet conversion configuration information is a leaf node, performing packet node conversion processing according to the conversion rule of the packet node in the second packet conversion configuration information.
Illustratively, the performing the packet node conversion processing according to the conversion rule of the packet node in the second packet conversion configuration information includes, but is not limited to: data dictionary translation (e.g., incoming value of 1, data dictionary translation result of 01), constant assignment, regular expression replacement, decimal digit complement, date format conversion.
In the embodiment of the invention, the recursion processing of the non-leaf nodes can be realized through the steps until the leaf nodes are obtained and are converted. Furthermore, different node types are configured and processed differently when message conversion is carried out, so that the flexibility and the universality of the message conversion are improved.
Fig. 5 is a schematic main flow chart of a message conversion method according to a third embodiment of the present invention. As shown in fig. 5, the message conversion method according to the embodiment of the present invention includes:
step S501, calling a corresponding first message adapter according to the message format of the received original message, and performing format conversion on the original message based on the first message adapter to obtain an intermediate data object.
Illustratively, the original message (which may also be referred to as an "access message") includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript object Notification), which is an open standard data exchange format based on a subset of JavaScript syntax.
The method comprises the steps of obtaining a first message adapter, a first message adapter and a second message adapter, wherein the first message adapter can be called as a front message adapter and used for converting an original message into an intermediate data object, and the first message adapter can be preset with multiple types, such as FIX message to intermediate data object, XM L message to intermediate data object, JSON message to intermediate data object and other types of message adapters.
Illustratively, the intermediate data object may be a Map object. A Map object is an object that maps a key to a value, and has the following properties: a mapping cannot contain duplicate keys, each of which can only map to one value at most. It should be noted that the intermediate data object may also be other forms of objects without affecting the implementation of the present invention.
Step S502, inquiring a system message conversion configuration table according to the message code of the original message.
The system message conversion configuration table defines a full-scale message node mapping relationship (or message node conversion rule) in a message by using message codes as dimensions. That is, in a system message conversion configuration table, it is defined for each attribute in the message that needs not to be converted, specifically how to be converted.
When the first message conversion configuration information corresponding to the message code exists in the system message conversion configuration table, executing step S505; if the first packet conversion configuration information corresponding to the packet code does not exist in the system packet conversion configuration table, step S503 is executed.
Step S503, inquiring a special case message node conversion configuration table according to the message node identification of the intermediate data object.
The special case message node conversion configuration table defines a conversion rule of partial attributes by using message nodes or attributes as dimensions, and the conversion rule is irrelevant to message coding. The special case message node conversion configuration table is mainly set for the condition that different conversions are carried out in different messages by the same attribute. For example, for the same attribute "AAA" in the message "messg 01" and the message "messg 02", the conversion rule of the special case message node corresponding to the message "AAA" is different, the former converts the message into "BBB", and the latter converts the message into "CCC".
In an optional implementation manner of this step, each packet node of the intermediate data object may be cyclically acquired, and the conversion configuration table of the specific packet node may be queried according to the identifier of the packet node. When the special case message node conversion configuration table has the corresponding special case message node conversion rule, executing step S505; if there is no special case message node conversion rule in the special case message node conversion configuration table, step S504 is executed.
Step S504, inquiring the conversion configuration table of the universal message node according to the message node identification of the intermediate data object.
The general message node conversion configuration table defines conversion rules of partial attributes by using message nodes or attributes as dimensions, and the conversion rules are irrelevant to message coding. The general message node conversion configuration table is mainly set for the condition that the same attribute performs the same conversion in different messages. For example, for the same attribute "AAA" in the message "messg 01" and the message "messg 02", the corresponding common message node conversion rules are the same, and are all converted into "CCC".
In an optional implementation manner of this step, each packet node of the intermediate data object may be cyclically acquired, and the general packet node conversion configuration table may be queried according to the packet node identifier. When the corresponding general message node conversion rule exists in the general message node conversion configuration table, executing step S505; if there is no corresponding message node conversion rule in the general message node conversion configuration table, step S506 is executed.
Step S505, performing conversion processing on the intermediate data object according to the first message conversion configuration information, or the special case message node conversion rule, or the general message node conversion rule, so as to obtain a target data object.
Specifically, when the system message conversion configuration table is queried to have corresponding first message conversion configuration information according to step S502, the intermediate data object is subjected to conversion processing according to the first message conversion configuration information to obtain a target data object; when the special case message node conversion configuration table is inquired according to the step S503 and a corresponding special case message node conversion rule exists, the intermediate data object is converted according to the special case message node conversion rule to obtain a target data object; when the universal message node conversion configuration table is inquired to have the corresponding universal message node conversion rule according to the step S504, the intermediate data object is converted according to the universal message node conversion rule to obtain the target data object. Further, after step S505, step S507 is executed.
In the embodiment of the invention, the message conversion configuration table is set, which is beneficial to realizing the message conversion by taking the message as the dimension; meanwhile, by setting a special case message node conversion configuration table and a general message node conversion configuration table, message conversion with message nodes or attribute dimensions is facilitated. Further, the message conversion configuration table, the special case message node conversion configuration table and the general message node conversion configuration table are queried through the steps from the step S502 to the step S505, and a corresponding conversion strategy is determined according to a query result, so that the universality of message conversion is further improved.
And step S506, directly taking the intermediate data object as the target data object.
Further, after step S506, step S507 is executed.
Step S507, according to the message format of the target message, calling a corresponding second message adapter, and performing format conversion on the target data object based on the second message adapter to obtain the target message.
Illustratively, the target message includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript Object Notification, which is an open standard data exchange format based on a subset of JavaScript syntax) messages.
In the step, a plurality of types of second message adapters can be preset, such as message adapters of types of converting the target data object into a FIX message, converting the target data object into an XM L message, converting the target data object into a JSON message, and the like.
A detailed description will be given below of a processing flow for performing format conversion on the target data object based on the second packet adapter to obtain the target packet, by taking Map object to FIX packet as an example.
Exemplarily, when the target packet is a FIX packet, performing format conversion on the target data object in the Map format based on the second packet adapter to obtain the target packet specifically includes: reading a key value pair in the Map object, and assembling a Message object according to the read key value pair; and processing the Message object (mainly setting Message header and tail information) through third-party software (such as a Quickfix Message engine) to obtain a target Message in a FIX Message format.
In the embodiment of the invention, the steps not only can flexibly meet different conversion requirements of different messages, but also have simple configuration and strong expandability, and the problems of poor universality, incapability of quick popularization and the like of the conventional hard coded message conversion mode are solved.
Fig. 6 is a schematic diagram of main modules of a message conversion apparatus according to a fourth embodiment of the present invention. As shown in fig. 6, a message conversion apparatus 600 according to an embodiment of the present invention includes: a first message adaptation module 601, a data conversion module 602, and a second message adaptation module 603.
The first packet adaptation module 601 is configured to call a corresponding first packet adapter according to a packet format of a received original packet, and perform format conversion on the original packet based on the first packet adapter to obtain an intermediate data object.
Illustratively, the original message (which may also be referred to as an "access message") includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript object Notification), which is an open standard data exchange format based on a subset of JavaScript syntax.
The first message adapter 601 can call the corresponding first message adapter according to the message format of the original message, for example, if the original message is a FIX message, the message adapter of the Fix message to the intermediate data object can be called, and format conversion is performed on the original message based on the message adapter to obtain the intermediate data object, and if the original message is a JSON message, the message adapter of the JSON message to the intermediate data object can be called, and format conversion is performed on the original message based on the message adapter to obtain the intermediate data object.
Illustratively, the intermediate data object may be a Map object. A Map object is an object that maps a key to a value, and has the following properties: a mapping cannot contain duplicate keys, each of which can only map to one value at most. It should be noted that the intermediate data object may also be other forms of objects without affecting the implementation of the present invention.
A data conversion module 602, configured to perform conversion processing on the content of the intermediate data object based on the message conversion configuration table, so as to obtain a target data object.
The message conversion configuration table may include message conversion configuration information such as a message node mapping relationship (or referred to as a "conversion rule of a message node"). The message node mapping relationship defines a mapping relationship between message nodes. In specific implementation, one key value pair in the intermediate data object can be regarded as a message node, and the message node mapping relation indicates what key value pair each key value pair in the intermediate data object is to be converted into and the value in the key value pair is not to be changed.
Wherein the target data object is in the same format as the intermediate data object. For example, when the intermediate data object is a Map object, the target data object is also a Map object. In this step, the conversion process performed on the content of the intermediate data object includes, but is not limited to: data dictionary translation, constant assignment, regular expression replacement, decimal digit supplement and date format conversion.
The second packet adaptation module 603 is configured to call a second packet adapter corresponding to the target packet according to the packet format of the target packet, and perform format conversion on the target data object based on the second packet adapter to obtain the target packet.
Illustratively, the target message includes, but is not limited to, FIX (financial information exchange protocol) messages, XM L (extensible markup language) messages, or JSON (JavaScript Object Notification, which is an open standard data exchange format based on a subset of JavaScript syntax) messages.
The second message adapter may be configured to be a plurality of types of second message adapters in advance, for example, a message adapter of a type that a target data object is converted into a FIX message, a target data object is converted into an XM L message, a target data object is converted into a JSON message, or the like.
In the embodiment of the invention, various types of messages can be converted through the modules, and the problems of poor universality, incapability of rapid popularization and the like of the conventional hard coding message conversion mode are solved.
Fig. 7 shows an exemplary system architecture 700 to which the message conversion method or the message conversion apparatus according to the embodiments of the present invention can be applied.
As shown in fig. 7, the system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 serves to provide a medium for communication links between the terminal devices 701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. The terminal devices 701, 702, 703 may have various communication client applications installed thereon, such as a financial service application, a shopping application, a web browser application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 705 may be a server providing various services, such as a background management server providing support for financial services applications or websites browsed by the user using the terminal devices 701, 702, 703. The background management server may perform processing such as message conversion on the access message, and transmit a processing result (e.g., a target message obtained by conversion) to another system module or feed back the processing result to the terminal device.
It should be noted that the message conversion method provided by the embodiment of the present invention is generally executed by the server 705, and accordingly, the message conversion apparatus is generally disposed in the server 705.
It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use in implementing an electronic device of an embodiment of the present invention. The computer system illustrated in FIG. 8 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
To the I/O interface 805, AN input section 806 including a keyboard, a mouse, and the like, AN output section 807 including a network interface card such as a Cathode Ray Tube (CRT), a liquid crystal display (L CD), and the like, a speaker, and the like, a storage section 808 including a hard disk, and the like, and a communication section 809 including a network interface card such as a L AN card, a modem, and the like are connected, the communication section 809 performs communication processing via a network such as the internet, a drive 810 is also connected to the I/O interface 805 as necessary, a removable medium 811 such as a magnetic disk, AN optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted into the storage section 808 as.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 801.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises a first message adaptation module, a data conversion module and a second message adaptation module. The names of these modules do not in some cases form a limitation on the modules themselves, for example, the first message adaptation module may also be described as a "module that converts the format of the original message".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: calling a first message adapter corresponding to the received original message according to the message format of the original message, and performing format conversion on the original message based on the first message adapter to obtain an intermediate data object; converting the content of the intermediate data object based on a message conversion configuration table to obtain a target data object; and calling a second message adapter corresponding to the target message according to the message format of the target message, and performing format conversion on the target data object based on the second message adapter to obtain the target message.
According to the technical scheme of the embodiment of the invention, various types of messages can be converted, and the problems of poor universality, incapability of rapid popularization and the like of the conventional hard coded message conversion mode are solved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A message conversion method, characterized in that the method comprises:
calling a first message adapter corresponding to the received original message according to the message format of the original message, and performing format conversion on the original message based on the first message adapter to obtain an intermediate data object;
converting the content of the intermediate data object based on a message conversion configuration table to obtain a target data object;
and calling a second message adapter corresponding to the target message according to the message format of the target message, and performing format conversion on the target data object based on the second message adapter to obtain the target message.
2. The method of claim 1, wherein the original message comprises a FIX message, an XM L message, or a JSON message, wherein the intermediate data object and the target data object are Map objects, and wherein the target message comprises a FIX message, an XM L message, or a JSON message.
3. The method of claim 1, wherein the processing the content of the intermediate data object based on the message conversion configuration table to obtain the target data object comprises:
inquiring a message conversion configuration table according to the message code of the original message; under the condition that first message conversion configuration information corresponding to the message code of the original message exists in the message conversion configuration table, processing the content of the intermediate data object according to the first message conversion configuration information to obtain a target data object; and directly taking the intermediate data object as the target data object under the condition that the first message conversion configuration information corresponding to the message code of the original message does not exist in the message conversion configuration table.
4. The method of claim 3, wherein the processing the content of the intermediate data object according to the first packet conversion configuration information to obtain a target data object comprises:
circularly acquiring each message node of the intermediate data object; when the node type of the message node in the intermediate data object is a leaf node, performing message node conversion processing according to the conversion rule of the message node in the first message conversion configuration information; and when the node type of the message node in the intermediate data object is a non-leaf node, performing recursive processing on the message node until the leaf node under the message node is obtained, and performing conversion processing on the leaf node under the message node.
5. The method according to claim 4, wherein when the node type of the packet node in the intermediate data object is a non-leaf node, performing recursive processing on the packet node until a leaf node below the packet node is obtained, and performing conversion processing on the leaf node below the packet node includes:
when the node type of the message node is a non-leaf node, inquiring a message conversion configuration table according to the message code under the message node in the first message conversion configuration information to obtain second message conversion configuration information corresponding to the message code under the message node; circularly acquiring each message node in the second message conversion configuration information; and when the node type of the message node in the second message conversion configuration information is a leaf node, performing message node conversion processing according to the conversion rule of the message node in the second message conversion configuration information.
6. The method of claim 3, further comprising:
before the intermediate data object is directly used as the target data object, inquiring a special case message node conversion configuration table and a general message node conversion configuration table according to the message node of the intermediate data object, and confirming that no corresponding node conversion rule exists in the special case message node conversion configuration table and the general message node conversion configuration table.
7. The method according to claim 6, wherein the performing packet node conversion processing according to the conversion rule of the packet node in the first packet conversion configuration information comprises at least one of: data dictionary translation, constant assignment, regular expression replacement, decimal digit supplement and date format conversion.
8. A message conversion apparatus, the apparatus comprising:
the first message adaptation module is used for calling a first message adapter corresponding to the received original message according to the message format of the original message, and carrying out format conversion on the original message based on the first message adapter so as to obtain an intermediate data object;
the data conversion module is used for carrying out conversion processing on the content of the intermediate data object based on a message conversion configuration table so as to obtain a target data object;
and the second message adaptation module is used for calling a corresponding second message adapter according to the message format of the target message and carrying out format conversion on the target data object based on the second message adapter so as to obtain the target message.
9. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010158655.7A CN111447257B (en) | 2020-03-09 | 2020-03-09 | Message conversion method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010158655.7A CN111447257B (en) | 2020-03-09 | 2020-03-09 | Message conversion method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111447257A true CN111447257A (en) | 2020-07-24 |
| CN111447257B CN111447257B (en) | 2022-10-21 |
Family
ID=71653164
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010158655.7A Active CN111447257B (en) | 2020-03-09 | 2020-03-09 | Message conversion method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111447257B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112185494A (en) * | 2020-09-03 | 2021-01-05 | 武汉联影医疗科技有限公司 | Data storage method and device, computer equipment and storage medium |
| CN112217896A (en) * | 2020-10-13 | 2021-01-12 | 北京思特奇信息技术股份有限公司 | JSON message conversion method and related device |
| CN112383533A (en) * | 2020-11-10 | 2021-02-19 | 中国农业银行股份有限公司 | Message format conversion method and device |
| CN113132371A (en) * | 2021-04-13 | 2021-07-16 | 中国邮政储蓄银行股份有限公司 | Message conversion method, device, computer readable storage medium and processor |
| CN113783860A (en) * | 2021-09-01 | 2021-12-10 | 建信金融科技有限责任公司 | Message processing method, device and equipment based on visual configuration |
| CN114040008A (en) * | 2021-11-05 | 2022-02-11 | 光大科技有限公司 | Message processing method and device |
| CN114500666A (en) * | 2021-12-29 | 2022-05-13 | 海南同享数字科技有限公司 | XML-based custom message general method and device and electronic equipment |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7152205B2 (en) * | 2000-12-18 | 2006-12-19 | Siemens Corporate Research, Inc. | System for multimedia document and file processing and format conversion |
| US20080141272A1 (en) * | 2006-12-06 | 2008-06-12 | Borgendale Kenneth W | Application Message Conversion Using A Feed Adapter |
| CN101325514A (en) * | 2008-07-21 | 2008-12-17 | 中兴通讯股份有限公司 | Communication network management adapter frame with configurable flow and implementing method |
| US20100050101A1 (en) * | 2008-08-21 | 2010-02-25 | Palm, Inc. | Converting Information Objects |
| CN104935499A (en) * | 2015-05-28 | 2015-09-23 | 杭州华三通信技术有限公司 | Message format conversion method and equipment |
| CN106469158A (en) * | 2015-08-17 | 2017-03-01 | 杭州海康威视系统技术有限公司 | Method of data synchronization and device |
| US9639631B2 (en) * | 2013-02-27 | 2017-05-02 | Cellco Partnership | Converting XML to JSON with configurable output |
| CN106959948A (en) * | 2016-01-08 | 2017-07-18 | 普华诚信信息技术有限公司 | The system and its preprocess method pre-processed for distributed nature to big data |
| CN107145540A (en) * | 2017-04-24 | 2017-09-08 | 北京邮电大学 | The diagram file textual conversion equipment and method of the version control function of class uml diagram |
| CN110166463A (en) * | 2019-05-27 | 2019-08-23 | 中国银联股份有限公司 | A kind of message transmissions conversion method and device |
| CN110445860A (en) * | 2019-08-06 | 2019-11-12 | 深圳市金证科技股份有限公司 | A kind of file transmitting method, device, terminal device and storage medium |
| US10552443B1 (en) * | 2016-08-11 | 2020-02-04 | MuleSoft, Inc. | Schemaless to relational representation conversion |
-
2020
- 2020-03-09 CN CN202010158655.7A patent/CN111447257B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7152205B2 (en) * | 2000-12-18 | 2006-12-19 | Siemens Corporate Research, Inc. | System for multimedia document and file processing and format conversion |
| US20080141272A1 (en) * | 2006-12-06 | 2008-06-12 | Borgendale Kenneth W | Application Message Conversion Using A Feed Adapter |
| CN101325514A (en) * | 2008-07-21 | 2008-12-17 | 中兴通讯股份有限公司 | Communication network management adapter frame with configurable flow and implementing method |
| US20100050101A1 (en) * | 2008-08-21 | 2010-02-25 | Palm, Inc. | Converting Information Objects |
| US9639631B2 (en) * | 2013-02-27 | 2017-05-02 | Cellco Partnership | Converting XML to JSON with configurable output |
| CN104935499A (en) * | 2015-05-28 | 2015-09-23 | 杭州华三通信技术有限公司 | Message format conversion method and equipment |
| CN106469158A (en) * | 2015-08-17 | 2017-03-01 | 杭州海康威视系统技术有限公司 | Method of data synchronization and device |
| CN106959948A (en) * | 2016-01-08 | 2017-07-18 | 普华诚信信息技术有限公司 | The system and its preprocess method pre-processed for distributed nature to big data |
| US10552443B1 (en) * | 2016-08-11 | 2020-02-04 | MuleSoft, Inc. | Schemaless to relational representation conversion |
| CN107145540A (en) * | 2017-04-24 | 2017-09-08 | 北京邮电大学 | The diagram file textual conversion equipment and method of the version control function of class uml diagram |
| CN110166463A (en) * | 2019-05-27 | 2019-08-23 | 中国银联股份有限公司 | A kind of message transmissions conversion method and device |
| CN110445860A (en) * | 2019-08-06 | 2019-11-12 | 深圳市金证科技股份有限公司 | A kind of file transmitting method, device, terminal device and storage medium |
Non-Patent Citations (4)
| Title |
|---|
| DTS/CABLE-00017-3: "TECHNICAL SPECIFICATION Integrated broadband cable telecommunication networks (CABLE); Fourth Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 3: MAC and Upper Layer Protocols Interface; ", 《ETSI TS 103 311-3》 * |
| DTS/CABLE-00017-3: "TECHNICAL SPECIFICATION Integrated broadband cable telecommunication networks (CABLE); Fourth Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 3: MAC and Upper Layer Protocols Interface; ", 《ETSI TS 103 311-3》, 28 February 2017 (2017-02-28) * |
| 易小华等: "面向MapReduce的数据处理流程开发方法", 《计算机科学与探索》 * |
| 易小华等: "面向MapReduce的数据处理流程开发方法", 《计算机科学与探索》, no. 02, 15 February 2011 (2011-02-15) * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112185494A (en) * | 2020-09-03 | 2021-01-05 | 武汉联影医疗科技有限公司 | Data storage method and device, computer equipment and storage medium |
| CN112185494B (en) * | 2020-09-03 | 2023-04-25 | 武汉联影医疗科技有限公司 | Data storage method, device, computer equipment and storage medium |
| CN112217896A (en) * | 2020-10-13 | 2021-01-12 | 北京思特奇信息技术股份有限公司 | JSON message conversion method and related device |
| CN112383533A (en) * | 2020-11-10 | 2021-02-19 | 中国农业银行股份有限公司 | Message format conversion method and device |
| CN112383533B (en) * | 2020-11-10 | 2023-07-28 | 中国农业银行股份有限公司 | Message format conversion method and device |
| CN113132371A (en) * | 2021-04-13 | 2021-07-16 | 中国邮政储蓄银行股份有限公司 | Message conversion method, device, computer readable storage medium and processor |
| CN113783860A (en) * | 2021-09-01 | 2021-12-10 | 建信金融科技有限责任公司 | Message processing method, device and equipment based on visual configuration |
| CN113783860B (en) * | 2021-09-01 | 2023-11-28 | 建信金融科技有限责任公司 | Message processing method, device, equipment and storage medium based on visual configuration |
| CN114040008A (en) * | 2021-11-05 | 2022-02-11 | 光大科技有限公司 | Message processing method and device |
| CN114500666A (en) * | 2021-12-29 | 2022-05-13 | 海南同享数字科技有限公司 | XML-based custom message general method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111447257B (en) | 2022-10-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111447257B (en) | Message conversion method and device | |
| CN112184367B (en) | Order processing method and device | |
| CN110471848B (en) | Method and device for dynamically returning message | |
| CN110858202A (en) | Method and device for generating where clause in database query statement | |
| CN113076153B (en) | Interface calling method and device | |
| CN111427899A (en) | Method, device, equipment and computer readable medium for storing file | |
| CN116775167A (en) | Service processing method, device, electronic equipment and computer readable medium | |
| CN112948138A (en) | Method and device for processing message | |
| CN113779018A (en) | Data processing method and device | |
| CN112487765B (en) | Method and device for generating notification text | |
| CN114866628A (en) | Message processing method, device, equipment and storage medium | |
| CN113556370A (en) | Service calling method and device | |
| CN110858240A (en) | Front-end module loading method and device | |
| CN112214500A (en) | Data comparison method and device, electronic equipment and storage medium | |
| CN112311833B (en) | Data updating method and device | |
| CN113766437B (en) | Short message sending method and device | |
| CN113448652A (en) | Request processing method and device | |
| CN113760714A (en) | Software testing method and device | |
| CN114090569A (en) | Method, device, equipment and computer readable medium for processing data | |
| CN117201597A (en) | Message processing method, device, electronic equipment and storage medium | |
| CN113535163A (en) | Method and device for generating message | |
| CN113761039A (en) | Method and device for processing information | |
| CN116756449A (en) | Method and device for loading product information data | |
| CN115422067A (en) | Interface testing method and device | |
| CN114091044A (en) | System authority management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220923 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |