JP5947622B2 - Telegram distribution device - Google Patents

Description

  The present invention relates to an apparatus that receives a message and distributes the message to a plurality of buffers. In particular, the present invention relates to an apparatus for storing a received electronic message in a database and transmitting the electronic message to one or a plurality of modules.

  Computers have become a central part of communication. For example, in financial operations such as banking and securities operations, a message may be received from outside the company or users of the same industry using a computer network, and the computer that received the message may distribute the message to the computer in the department that requires it. Has been done.

  A computer that receives a message from the outside has a database management system or is connected to a database server. After the received message is stored in the database, it is distributed from the database to a department that requires the message. The reason for storing the message once in the database in this way is that the format of the received message is different from the format of the message when allocating to each department, so it is necessary to convert the format, and there is a failure in the database. This is because a powerful recovery function is provided so that data is not lost even if it occurs.

  On the other hand, ISO20022 is enacted, and in the financial business, a transition from a conventional fixed-length message format to a message format as information representing a structured document based on XML (extensible Markup Language) is scheduled.

US Patent Application Publication No. 2011/0137791

  With the transition of the message format as described above, the size of the message is expected to increase. For this reason, it is required to store the received electronic message in a database and perform a process of distributing the received electronic message to a department that requires the electronic message at a higher speed.

  In order to cope with such a situation, an object of the present invention is to speed up the process of storing a received electronic message in a database and allocating the received electronic message to a department that needs the electronic message.

  As one embodiment of the present invention, a first buffer that holds data input to a database, a second buffer that holds data input to a module different from the database, and a receiving unit that receives a telegram of a specific format And the data of the specific format received by the receiving unit, the data input to the second buffer while maintaining the specific format, and the data input to the first buffer after being converted to another format There is provided a telegram distribution device having a separation unit for separating the message.

  According to the present invention, the received electronic message can be stored in the database management system, and the process of distributing to the department that needs the electronic message can be performed at a higher speed. In addition, even if a failure occurs in the database, it is possible to continue the process of distributing to a department that requires a message.

Functional block diagram of a system including a message distribution device according to an embodiment of the present invention The flowchart of the process of the message distribution apparatus which concerns on one Embodiment of this invention An example diagram of a message structure of a message distribution device according to an embodiment of the present invention An example figure of the data structure used for the process of the message distribution apparatus which concerns on one Embodiment of this invention Functional block diagram of a system including a message distribution device according to an embodiment of the present invention The flowchart of the process of the message distribution apparatus which concerns on one Embodiment of this invention An example figure of the data structure by which the message | telegram is recorded by the recording part of the message | telegram distribution apparatus which concerns on one Embodiment of this invention Functional block diagram of a system including a message distribution device according to an embodiment of the present invention The flowchart of the process of the message distribution apparatus which concerns on one Embodiment of this invention

  Hereinafter, embodiments for carrying out the present invention will be described as a plurality of embodiments. The present invention is not construed as being limited to the following embodiments, and the following embodiments can be modified and implemented.

(Embodiment 1)
FIG. 1 is a functional block diagram of a system including a message distribution device according to the present embodiment. The system 100 includes a message distribution device 101, a transmission server 106, a communication network 107, a database 108, and a module 109.

  The message distribution apparatus 101 and the transmission server 106 are connected via a communication network 107. The transmission server 106 transmits a message to the message distribution device 101 via the communication network 107. For example, in the financial industry, the transmission server 106 is a server installed at the Bank of Japan, and the message distribution device 101 is a server installed at one of financial institutions. The Bank of Japan performs fund settlement between financial institutions, and the transmission server 106 transmits a telegram representing the result of the fund settlement to the telegraphic distribution device 101 of the financial institution via the communication network 107. The format of the message at this time may be a specific format standardized by ISO20022.

  The electronic message distribution apparatus 101 includes a reception unit 102, a separation unit 103, a first buffer 104, and a second buffer 105.

  The receiving unit 102 is connected to the transmission server 106 via the communication network 107 and receives a message transmitted from the transmission server 106. In addition, the receiving unit 102 transmits the received electronic message to the separating unit 103. The received electronic message may be in a format standardized by, for example, ISO20022 described above. Further, when transmitting the message received by the receiving unit 102 to the separating unit 103, the format of the message may be transmitted as it is as it is received. However, the format in the physical aspect is converted according to the physical medium of communication and transmission, and the message format in the logical aspect according to the ISO20022 standard or the like may be left as it is.

The separation unit 103 maintains the format of the message received by the receiving unit 102 and the data input to the second buffer 105 and the data converted to another format and input to the first buffer 104 And to separate. For example, the separation unit 103 separates the message as data input to the second buffer 105 while the message format is maintained in a format standardized by ISO20022, and the second buffer 105 retains the separated message format. To enter. Also, the separation unit 103 separates the data input to the first buffer by converting the electronic message into another format and inputs the data to the first buffer. As another format, a format suitable for the schema of the database 108 can be cited. For example, there is a format of an INSERT statement for inputting into a specific table of the database 108.

  When the separating unit 103 separates the messages, there may be an overlap between the message input to the first buffer 104 and the message input to the second buffer 105. For example, the separating unit 103 may input all the messages received by the receiving unit 102 to the first buffer 104 and input a part of the messages received by the receiving unit 102 to the second buffer 105. In this case, the set of messages input to the second buffer 105 overlaps the message input to the first buffer 104 and the message input to the second buffer 105. Further, the separation unit 103 may input all the messages received by the reception unit 102 to both the first buffer 104 and the second buffer 105. In this case, all of the messages received by the receiving unit 102 overlap the message input to the first buffer 104 and the message input to the second buffer 105.

  The first buffer 104 holds data input to the database 108. The database 108 is a relational database, for example. The data input to the first buffer 104 is held by the first buffer 104 at least until it is input to the database 108. As a result, the data received and input to the first buffer 104 can be reliably input to the database 108. The first buffer 104 can be realized by, for example, a first-in first-out (First In First Out) queue structure.

  The second buffer 105 holds data input to a module 109 different from the database 108. The module 109 may include a communication interface for transmitting a message to another computer (server device). Further, the module 109 may be one of the modules constituting the message distribution device 101. Similarly to the first buffer 104, the second buffer 105 can also be realized by a first-in first-out (First In First Out) queue structure. As a result, when transmitting a message to another computer, the second buffer 105 can be used as a buffer for transmission even if reception waiting of the transmission destination computer occurs, and the message distribution device 101, the transmission destination, The bandwidth of communication with other computers can be used efficiently.

  A plurality of modules 109 may exist. In this case, the message distribution device 101 may further include a third buffer, a fourth buffer, and the like according to the number of modules 109. In this case, the separation unit 103 may separate the message received by the reception unit 102 into data input to the second buffer, the third buffer, the fourth buffer, or the like while maintaining the format.

  FIG. 2 is a flowchart for explaining the operation of the message distribution device 101 according to the present embodiment. The message distribution device 101 performs the process of the flowchart shown in FIG. 2 every time a message transmitted from the transmission server 106 via the communication network 107 becomes receivable. For example, when the electronic message distribution apparatus 101 is realized by using a computer, the processing of a program that is executed when an electronic message is received by the communication interface via the communication network 107 and executed is shown in FIG. It may be a process to be performed.

  A message is received as the processing of step S201. For example, a message is received by reading a message stored in the queue of the communication interface. In step S202, the electronic message is analyzed. The message has a specific format. For example, the message format may be an XML format. Since a message has a specific format, it is possible to perform analysis according to the format.

  FIG. 3A shows an example of a message. In this example, the message has the form of a structured document in XML. The tag “<message”, the tag “</ message>”, the tag “<type>”, and the tag "</ Type>" tag corresponding to, "<Destination>" tag and corresponding "</ Destination>" tag, "<Sent date>" tag and corresponding "</ Send> The format has a tag of “day>”. In the case of having such an XML format, it is possible to perform analysis in consideration of tag correspondence.

  For example, the parsing tree shown in FIG. 3B can be obtained by analyzing an example of the electronic message shown in FIG. The node 301 (root node) corresponds to a portion surrounded by a tag “<message>” and a tag “</ message>” corresponding thereto. The node 302 corresponds to a portion surrounded by a tag “<type>” and a tag “</ type>” corresponding thereto. The node 312 corresponds to “message 1”. The node 303 corresponds to a portion surrounded by a tag “<destination>” and a corresponding tag “</ destination>”. The node 313 corresponds to “destination 1”. The node 304 corresponds to a portion surrounded by a tag “<transmission date>” and a tag “</ transmission date>” corresponding thereto. The node 314 corresponds to “June 7, 2012”.

  In step S202, for example, a parse tree shown in FIG. 3B can be generated, and a route from the node 301 as the root node to the terminal node can be selected and analyzed.

  In step S203, based on the analysis in step S202, it is determined whether or not a message should be input to the second buffer. If it is determined that it should be input to the second buffer 105, the process proceeds to step S <b> 204 and a message is input to the second buffer 105. If it is determined that the data should not be input to the second buffer 105, step S204 is skipped.

  The determination in step S203 can be made according to the value corresponding to the node 312 connected to the node 302 with reference to the table shown in FIG. That is, if the portion enclosed by the tag “<type>” and the tag “</ type>” corresponding to this tag is “message 1”, the value of the separation destination column is 2. It is determined that the data should be input to the second buffer. If it is “message 2”, since the value of the separation destination column is 1 and not 2, it is determined that it should not be input to the second buffer.

In step S205, conversion into another format is performed. For example, the format is changed to a format corresponding to the schema of the database 108. That is, it is assumed that the table shown in FIG. As the columns of the table, a “type” column 322, a “destination” column 323,..., A “transmission date” column 324 are defined, which are “<type>” and “<destination>”, respectively. , ..., and "<sent date>" tag,
INSERT INTO table (type, destination, ..., transmission date) VALUES ("message 1", "destination 1", ..., "June 7, 2012");
To the SQL INSERT statement format.

  In step S206, the message converted in step S205 is input to the first buffer 104.

  Note that, as described above, when there are a plurality of modules and the message distribution device 101 has the third buffer, the fourth buffer, and the like according to the number of modules, the step is based on the analysis of step S202. In S203, in addition to whether to input to the second buffer, it is determined whether to input to the third buffer, the fourth buffer, etc., and in step S204, the buffer determined to be input Enter a message in

  Further, the processes in steps S205 and S206 can be executed at an arbitrary time after step S201.

  As described above, according to the present embodiment, the received electronic message can be stored in the database, separated into modules corresponding to the departments that need the electronic message, input, and distributed. In this case, since the module can be input and distributed without going through the database, processing can be performed at high speed. In addition, even if a failure occurs in the database management system, it is possible to continue the process of distributing to a department that requires a message.

(Embodiment 2)
As a second embodiment of the present invention, a description will be given of a form in which a received electronic message can be recorded separately from a database.

  FIG. 5 is a functional block diagram of a system according to the second embodiment of the present invention. The system 500 includes a message distribution device 501, a transmission server 106, a communication network 107, a database 108, and a module 109. In addition, since the same code | symbol is used for the part which has the same or similar function as Embodiment 1, description of the part which has the same code | symbol is abbreviate | omitted below.

  The message distribution device 501 includes a receiving unit 102, a separating unit 103, a first buffer 104, a second buffer 105, and a recording unit 502.

  The recording unit 502 records a message received by the receiving unit 102. For example, the packet structure when the message is received by the receiving unit 102 may be recorded as it is. Alternatively, the receiving unit 102 may perform recording as a format of information when the received electronic message is transmitted to the separating unit 103. If necessary, information such as the reception date and time may be added, information such as a message header and footer may be deleted, or the format may be changed and recorded.

  The recording unit 502 preferably records the message permanently. For this reason, it is preferable that the recording unit 502 does not record using only a volatile memory, but records a message using a hard disk or the like by any electromagnetic or optical means.

  FIG. 6 is a flowchart for explaining the processing flow of the message distribution device 501 according to the present embodiment. Similar to the processing of the flowchart shown in FIG. 2, a message is received as the processing of step S201. Next, as the process of step S601, the received message is recorded in the recording unit 502. For example, the received electronic message is transmitted to the recording unit 502, and the recording unit 502 records the electronic message.

  FIG. 7 shows an example of a data structure in which the recording unit 502 records a message. For example, a table having a “number” column indicating the order in which messages are received and a “message” column in which the received messages are stored can be used. Instead of the “number” column, a column storing the reception date and time and the recording date and time may be used.

  The subsequent step S202 and subsequent steps are the same as those in the flowchart of FIG.

  Note that when there are a plurality of modules and the message distribution device 501 has a third buffer, a fourth buffer, and the like according to the number of modules, based on the analysis in step S202, In addition to whether to input to the second buffer, it is determined whether to input to the third buffer, the fourth buffer, etc. In step S204, a message is input to the buffer determined to be input. The other things are the same as in the first embodiment.

  Similarly, steps S205 and S206 can be executed at an arbitrary time after step S201, as in the first embodiment.

  In the present embodiment, since the received electronic message is recorded in the recording unit 502 in addition to the database 108, it is possible to further prepare for data loss.

(Embodiment 3)
As Embodiment 3 of the present invention, a mode in which a database can be restored using a message recorded by a recording unit will be described.

  FIG. 8 is a functional block diagram of a system according to the third embodiment of the present invention. The system 800 includes a message distribution device 801, a transmission server 106, a communication network 107, a database 108, and a module 109.

  The message distribution device 801 includes a receiving unit 102, a separating unit 103, a first buffer 104, a second buffer 105, a recording unit 502, and a restoration unit 802.

  The recovery unit 802 is a unit for recovering the database 108 using a message recorded in the recording unit 502 when a failure occurs in the database 108.

  An example of a specific procedure for restoring the database 108 by the restoration unit 802 is as shown in the flowchart of FIG. That is, as the processing in step 901, the transaction log of the database 108 is referred to, and the transaction existing when the failure occurs is rolled back. As the processing in step S902, a message recorded in the recording unit 502 after the time of rollback is obtained. If the messages are recorded in the recording unit 502 in the order received, the message received and recorded first after the occurrence of the failure is obtained, and the message recorded after the message is obtained.

  In step S903, the message obtained in step S902 is input to the database. At this time, the restoration unit 903 may convert the message obtained in step S902 into another format and input the message to the first buffer 104 as in the separation unit 103. Further, the restoration unit 802 may transmit the message obtained in step S <b> 902 by designating the separation unit 103 to input to the first buffer 104. In addition, if a message has not been input to the second buffer 105 after the failure of the database, the restoration unit 802 sends the message to the separation unit 103 so that the reception unit 102 transmits the message to the separation unit 103. May be communicated.

  In the present embodiment, the receiving unit 102 may receive a message while the processing of FIG. 9 is being performed, and the recording unit 502 may be configured to record the received message. As a result, it is possible to operate the message distribution device 801 at all times, and financial transactions and the like on 24 hours 365 days are possible.

Claims (7)

A first buffer for holding data input to the database;
A second buffer for holding data input to a module different from the database;
A receiving unit for receiving a message in a specific format;
The message of the specific format received by the receiving unit, the data input to the second buffer while maintaining the specific format, the data input to the first buffer after being converted to another format, A message distribution device having a separation unit for separating the message.   The message distribution device according to claim 1, further comprising a recording unit that records a message received by the receiving unit.   The message distribution device according to claim 2, further comprising: a recovery unit that recovers the database using a message recorded in the recording unit when the database has failed.   The separation unit changes the message to a format corresponding to the schema of the database when separating the message in the specific format received by the receiving unit as data input to the first buffer. The electronic message distribution apparatus according to claim 1.   5. The message distribution device according to claim 1, wherein the second buffer is a buffer for transmitting input data to a server device that communicates with the message distribution device.   The electronic message distribution device according to claim 1, wherein the electronic message is information representing a structured document. The electronic message distribution device according to claim 6, wherein the separation unit determines another server based on specific tag information of the electronic message and distributes the electronic message received by the reception unit.

Images