JP2005292981A - Message management device, data processing system, and computer program for the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently perform the communication of a message between modules. <P>SOLUTION: This data processing system 50 is provided with a plurality of processors 52 and 54 and a message manager 80 for managing message communication between processes. The processes 52 and 54 having one or more inputs and outputs include modules 60, 62, 64, 70, 72 and 74 for performing predetermined processing to input data and message managers 66 and 76 for managing the message communication in a process. The message managers 66 and 76 decide a transmission destination module based on a transmission origin module identifier included in a message received from the module in a process and the type of the message, and selectively performs processing to distribute the message in the process and processing to transmit it to a message manager 80 according to whether the module is inside or outside the process. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to message communication between functional modules operating on a computer, and more particularly to message communication between modules in a system in which a plurality of modules constitute one process and a plurality of processes realize one task. It relates to a system that speeds up.

  In the process of constructing a real-time speech recognition system or the like, it may be desired to confirm the performance such as the recognition rate by changing various settings for processing for speech recognition. Therefore, for example, it is convenient not only to operate the same program by changing option values and the like, but also to freely change the processing flow itself for experiments. Therefore, it is preferable to have a system in which a plurality of modules each having a specific function are prepared in advance, and these modules can be combined in an appropriate form according to the purpose.

  Furthermore, in order to confirm the experimental result quickly, it is convenient if not only one computer but also a plurality of computers can be connected to each other, and the modules can be operated separately in cooperation with each other on these computers.

  FIG. 1 shows what can be considered as a fundamental configuration for that purpose. The system 20 shown in FIG. 1 includes a first process 22 and a second process 24.

  The first process 22 includes a first module 30, a second module 32, and a third module 34. The second process 24 includes a fourth module 36, a fifth module 38, and a sixth module 40.

  For example, by executing the first process 22 on one computer and executing the second process 24 on another computer, the overall processing speed can be improved. Of course, there is no problem even if the first process 22 and the second process 24 are operated on the same computer.

  In order to realize such a system, in order to give the output of one module to the input of another module, the input and output of each module must be clearly defined in advance. It is necessary to consider how to pass data (messages) between processes.

  For example, modules included in the same process share the memory space in the process, so that messages can be exchanged at high speed. However, the system overhead required for communication between processes is large, and message communication between processes takes a relatively long time.

  In order to solve such a problem, it is conceivable to design a module so that a module communicates with different communication methods depending on whether the output destination of the module is in the same process or in a different process.

  However, if the module design is changed according to the output destination, the combination of modules is fixed, and the original purpose of modularization cannot be achieved. Therefore, there is a demand for a system that can efficiently perform communication between modules while retaining the advantages of modularization regardless of the process to which the modules belong.

  Therefore, an object of the present invention is to provide a message management device capable of efficiently communicating messages between freely combined modules, and a data processing system including such a message management device. is there.

  The message management device according to the first aspect of the present invention performs message communication between a plurality of modules and message communication between a plurality of modules and a module outside the process in a process including a plurality of modules. Each of the modules is uniquely specified by a module identifier, and a message communicated between the modules is a transmission source module identifier, a transmission destination module identifier, and a message to be transmitted. A message queue for temporarily storing the message, and the message stored in the message queue according to the destination module identifier of the message in the process. Message for delivery to the identified module Message flow management means for determining a message transmission destination module based on a message transmission source module identifier and a message type according to a predetermined data flow, and outputting the transmission destination module identifier In response to the message received from the module in the process, the message destination module identifier is obtained from the message flow management means based on the source module identifier and the message type included in the message, and the message A process for storing the message in the message queue according to whether or not the module specified by the acquired transmission destination module identifier is a module in the process, and a predetermined message transmission destination outside the process. Process to send The and a message distributing means for performing selectively.

  Preferably, the message distribution means includes module identifier storage means for storing a module identifier in the process, and in response to a message received from the module in the process, the source module identifier and the message included in the message. Based on the type, the means for obtaining the destination module identifier of the message from the message flow management means and the destination module identifier obtained by the means for obtaining are set as the destination module identifier of the received message. Means for determining whether the destination module identifier acquired by the means for acquiring is stored in the module identifier storage means, and means for acquiring by the determination means The acquired destination module identifier is the module identifier. In response to the determination that the message is stored in the child storage means, the means for storing the received message in the message queue, and the destination module identifier obtained by the means for obtaining by the judging means are Means for transmitting the received message to a predetermined message destination outside the process in response to determining that the module identifier is not stored in the module identifier storage means.

  A message management apparatus according to a second aspect of the present invention is a message management apparatus for managing message communication between modules in a system comprising a plurality of processes each including one or a plurality of modules, Each module is uniquely identified by a module identifier, and a message communicated between the modules includes a transmission source module identifier, a transmission destination module identifier, a type of message to be transmitted, and data to be transmitted. The message management apparatus determines a message transmission destination module based on a message transmission source module identifier and a message type according to a predetermined data flow, and outputs a transmission destination module identifier. From flow management means and modules in the process In response to the message, the message destination module identifier is acquired from the message flow management unit based on the source module identifier and the message type included in the message, and is specified by the acquired destination module identifier. Message distribution means for distributing the received message to the process including the module.

  When executed by a computer, the computer program according to the third aspect of the present invention causes the computer to operate as one of the message management devices described above.

  A data processing system according to a fourth aspect of the present invention is a data processing system including a plurality of processes and inter-process message management means for managing message communication for realizing a data flow between modules. . Each of the plurality of processes has one or a plurality of inputs and outputs, performs a predetermined process on the input data, outputs a plurality of modules, and a plurality of modules within the process. In-process message management means for managing message communication and message communication between a plurality of modules and modules outside the process. Each module is uniquely identified by a module identifier. The message communicated between the modules includes a transmission source module identifier, a transmission destination module identifier, a type of message to be transmitted, and data to be transmitted. In-process message management means includes a message queue for temporarily storing a message, and a message distribution for distributing the message stored in the message queue to a module specified by a destination module identifier of the message in the process. And a first message flow management means for determining a message destination module based on a message source module identifier and a message type according to a predetermined data flow and outputting the destination module identifier. In response to the message received from the module in the process, the message destination module identifier is obtained from the first message flow management means based on the source module identifier and the message type included in the message. The message The message is stored in the message queue according to whether or not the module specified by the acquired destination module identifier is a module in the process, and sent to the inter-process message management means. Message distribution means for selectively performing the processing to be performed.

  Preferably, the message distribution means includes module identifier storage means for storing a module identifier in the process, and in response to a message received from the module in the process, the source module identifier and the message included in the message. Based on the type, the means for obtaining the message destination module identifier from the first message flow management means, and the destination module identifier obtained by the means for obtaining the destination module identifier of the received message Means for determining whether or not the destination module identifier acquired by the means for acquiring is stored in the module identifier storage means, and for acquisition by the determination means The destination module identifier obtained by means of In response to the determination that the message identifier is stored in the message identifier storage means, the means for storing the received message in the message queue, and the destination module identifier obtained by the means for obtaining by the decision means Means for transmitting the received message to a predetermined message destination outside the process in response to determining that is not stored in the module identifier storage means.

  When executed by a computer, the computer program according to the fifth aspect of the present invention causes the computer to operate as one of the data processing systems described above.

  Hereinafter, a system according to an embodiment of the present invention will be described. This system is a system for performing speech recognition by combining a plurality of modules.

  When processing time-series data such as speech, if processing is performed in units of utterances, that is, processing is performed collectively after the end of speaking, a time lag corresponding to at least the utterance time occurs. As a result, it cannot be processed in real time.

  Therefore, in this system, the audio data is divided into units of a predetermined length (this is called a frame) at a time interval of about 10 msec, and the process is executed while transferring data between modules in units of frames. Data in units of frames is input to a certain module, and processing for the frame is performed by the module, and then passed to the next module. This frame unit data is referred to as an “event message (hereinafter abbreviated as event)”.

  There are several types of events depending on the type of data. For example, in the case of raw audio data, it is WAVE type, and in the case of feature parameters, it is FEATURE type. Therefore, in the input / output of a module, it is necessary to clearly define what type of data is input to or input from the module.

  When building a system, it is necessary to select a module according to the purpose and determine which output of which module is to be given to which input of which module in consideration of the data type. In this specification, the data flow between modules described in advance is called a flow definition in this specification, and is typically stored in a storage device in a computer-readable format.

  FIG. 2 shows a block diagram of the system 50. This system 50 includes a first process 52 and a second process 54, similar to the system 20 shown in FIG. 1. The system 50 further includes a flow definition file 58 that defines the flow of data between the modules constituting the first process 52 and the second process 54, the first process 52 and the second process 54, and the book. It is connected to the outside of the system 50 and controls the flow of events between the modules in the first process 52 and the second process 54 and between these modules and the outside of the system 50 according to the description of the flow definition file 58. A module manager 56.

  The first process 52 includes a first module 60, a second module 62, a third module 64, between these three modules 60, 62 and 64, and between these modules and the module manager 56. A message manager 66 for controlling the event flow according to the description of the flow definition file 58 and managing message communication within the process.

  Similarly to the first process 52, the second process 54 is a fourth module 70, a fifth module 72, a sixth module 74, and between these three modules 70, 72 and 74, and these modules. And a message manager 76 for controlling the flow of events between the module manager 56 and the module manager 56 according to the description of the flow definition file 58.

  Each of the modules 60 to 74 has one or more inputs and outputs. Each module has a function of internally processing input data according to a function specific to the module and outputting a result. For example, the voice feature extraction module receives voice data as an input and outputs its feature parameters.

  The module manager 56 includes an input module 82 for receiving an input given from the outside of the system 50, an output module 84 for giving an output from the system 50 to the outside, an input module 82, an output module 84, a message manager. And a message manager 80 for controlling the flow of events between the input module 82 and the output module 84 based on the description of the flow definition file 58. . That is, it can be said that the message manager 80 manages message communication between processes.

  FIG. 3 shows the configuration of the event 120 communicated between the modules. Referring to FIG. 3, event 120 includes a transmission source module identification number (hereinafter referred to as “ID”), a transmission destination module ID, an event type, and data contents. The event type is the type of data included in the event, and examples thereof include the WAVE type and the FEATURE type described above.

  FIG. 4 shows the contents described in the flow definition file 58 in a table format. Referring to FIG. 4, three items “process”, “arc”, and “file” are defined in the flow definition file 58.

  The process is information indicating which module is included in which process. arc (hereinafter referred to as “arc”) is information indicating what event is sent from which module to which module. This includes the event type. The file indicates what kind of event is sent from the outside to the system 50 and what result is outputted outside.

  FIG. 5 shows the configuration of the message manager 80 in block diagram form. Referring to FIG. 5, the message manager 80 determines the event destination module to be input to the message manager 80, and uses the event source module ID and the event type as keys to determine the module ID of the destination module. Based on the description of the flow management file 92, the module management table 94 having a structure capable of searching which module is included in which process, and the flow definition file 58. And a table creation processing unit 96 for creating the module management table 94.

  The message manager 80 is further connected to the first process 52, the second process 54, the input module 82 and the output module 84, and the event given from the first process 52, the second process 54 and the input module 82 is A message distribution processing unit 90 for outputting to any of the first process 52, the second process 54, and the output module 84 based on the descriptions of the flow management table 92 and the module management table 94 is included.

  FIG. 6 shows an example of the configuration of the flow management table 92, and FIG. 7 shows an example of the configuration of the module management table 94. Referring to FIG. 6, the flow management table 92 includes a plurality of entries, and each entry includes a transmission source module ID, an event type, and a transmission destination module ID. These correspond to descriptions of arcs in the flow definition file 58 shown in FIG. By searching the flow management table 92 using the transmission source module ID and event type (see FIG. 3) included in the received event as keys, it is determined which module the event should be transmitted to. This can be determined by looking at the ID column. Note that the flow management table 92 shown in FIG. 6 shows only a part of the information necessary for the configuration shown in FIG.

  Referring to FIG. 7, the module management table 94 also usually includes a plurality of entries. Each entry corresponds to a module and includes the process name to which the module belongs and the module ID of the module. The module management table 94 shown in FIG. 7 also shows only a part of information necessary for the configuration of the system 50 shown in FIG.

  Next, each part constituting the first process 52 and the second process 54 in FIG. 2 will be described. Since the configuration of each module is not directly related to the present invention, a detailed description thereof will be omitted. Since the message manager 66 and the message manager 76 have the same configuration, the message manager 66 will be described below.

  Referring to FIG. 8, the message manager 66 determines the event destination module to be input to the message manager 66, and uses the event source module ID and the event type as a key to specify the module ID of the destination module. Which module is included in the flow management table 102 of the same format as shown in FIG. 5 and the process managed by the message manager 66 (first process 52 in this embodiment). Based on the description of the module management table 100 that describes whether or not, the flow management table creation processing unit 106 for creating the flow management table 102 by copying the flow management table 92 shown in FIG. The module including the module ID included in the first process 52 And a module management table creation processing section 104 for creating Yuru management table 100.

  The message manager 66 further receives events from the first to third modules 60, 62, and 64 and the module manager 56, and refers to the flow management table 102 and the module management table 100 to refer to the event as the first to first modules. Message distribution processing unit 108 for determining which of the modules 60, 62 and 64 and module manager 56 should be transmitted and distributing the event according to the determination result, and message distribution processing by the message distribution processing unit 108 An event queue 110 for temporarily storing an event determined to be transmitted to a process managed by the unit 108 (first process 52 in the present embodiment) in FIFO format, and one event from the event queue 110 Read out one by one and included in the event Shinsaki based on the module ID, and a process in the message delivery unit 112 for delivering the event to one of the first to third module 60, 62 and 64.

  FIG. 9 schematically shows the format of the module management table 100. In the case of the first process 52 managed by the message manager 66, the modules included therein are the first module 60, the second module 62, and the third module 64. Therefore, the contents of the module management table 100 in this case are as shown in FIG.

  Actually, the message distribution processing unit 108 is realized by a program executed on computer hardware as will be described later. In the case of the present embodiment, different processing is performed depending on whether the transmission source of the event received by the message distribution processing unit 108 is in the process or outside the process. The control structure of the computer program for realizing each will be described with reference to FIGS.

  FIG. 10 is a flowchart of a processing program executed by the message distribution processing unit 108 of the message manager 66 shown in FIG. 8 when an event is received from a module in the process. The same applies to the message distribution processing unit 90 of the message manager 80 shown in FIG. Referring to FIG. 10, when an event is received from an in-process module, in step 130, the flow management table 102 is searched using the transmission source module ID and event type of the event as a key, and all corresponding arcs are extracted.

  Subsequently, the following processing is performed for all arcs found as a result of the processing in step 130. That is, in step 132, it is determined whether the destination module ID of the arc is that of the module in the process. If the destination module ID is that of the module in the process, the process proceeds to step 134; otherwise, the process proceeds to step 140.

  In step 134, the destination module ID included in the searched arc is set as the event destination. Since the destination module is in the same process, this event is output to the event queue 110 in step 136.

  On the other hand, in step 140, the destination module ID included in the arc searched for is set as the event destination. Since the destination module exists outside the process, this event is output to the module manager 56 in step 142.

  By performing the processing of steps 134, 136, 140 and 142 for all the arcs found in step 130, the number of events found for one event is generated, and the location of the destination module is determined. In response to the event queue 110 or the module manager 56, respectively.

  FIG. 11 is a flowchart of a processing program executed by the message distribution processing unit 90 of the message manager 80 shown in FIG. 5 when an event is received from outside the process. Referring to FIG. 11, when an event is received from outside the process, in step 160, a destination module ID in the event is searched in the module management table 94, and a process including the destination module is determined. In step 162, it is determined whether or not the determined process is itself. If it is the transmission destination, in step 164, the event is stored in its own event queue. If it is not the transmission destination, in step 166, the event is transmitted to the process including the transmission destination module.

  On the other hand, when the message manager 66 shown in FIG. 8 receives an event from outside the process, the destination of the event is guaranteed to be within the process. Therefore, the event is stored in the message distribution processing unit 108 shown in FIG.

-Operation-
With reference to FIGS. 2 to 11, the present system 50 having the above-described configuration operates as follows. First, referring to FIG. 2, a system configuration is first determined, and a flow definition file 58 is described according to the configuration and stored in a predetermined storage device. The table creation processing unit 96 shown in FIG. 5 creates the flow management table 92 and the module management table 94 shown in FIG. 5 based on the flow definition file 58. In each process, the flow management table creation processing unit 106 and the module management table creation processing unit 104 shown in FIG. 8 create the flow management table 102 and the module management table 100 based on the flow management table 92 and the flow definition file 58, respectively. .

  In operation, input data is provided to the input module 82. The input data is usually an audio data file in this system. In this system, since the file is handled in the same manner as the process, the frame data created from the input file is given to the input module 82 as an event. In the case of this example, if the modules are combined as shown in FIG. 1, the event destination module ID given to the input module 82 corresponds to the first module, and the event type is “WAVE”. " The transmission source module ID corresponds to the input file. This event is given from the input module 82 to the message manager 80.

  Referring to FIG. 5, the message distribution processing unit 90 of the message manager 80 refers to the flow management table 92 and the module management table 94 to determine a process including the module that is the destination of the event (FIG. 11). Step 160), sending the event to the process (step 164 or 166). In this example, it is assumed that this event is transmitted to the first process 52, for example.

  Referring to FIG. 8, message distribution processing unit 108 of message manager 66 stores the event in event queue 110 because the event is from outside the process. The in-process message delivery unit 112 reads the event from the event queue 110 and delivers the event to the module specified by the destination module ID.

  The module that has received this event returns the resulting event to the message distribution processing unit 108 of the message manager 66. At this time, a value is set by the module for each of the event transmission source module ID and the event type. No destination module ID is set.

  The message distribution processing unit 108 searches the flow management table 102 using the transmission source module ID and event type of the received event as keys (step 130 in FIG. 10), and obtains a matching arc. The message distribution processing unit 108 further refers to the module management table 100 to determine whether or not the transmission destination module is in the first process 52 (step 132). If within the first process 52 (that is, if the module ID exists in the module management table 100), the destination module ID included in the arc is set as the event destination module ID (step 134). ) The message distribution processing unit 108 writes this event to the event queue 110 (step 136).

  If the transmission destination is outside the first process 52, the transmission destination module ID included in the arc is set to the transmission destination module ID of the event (step 140), and this event is transmitted to the module manager 56 (step 142). ).

  As in the case of receiving the first input data, the message manager 80 of the module manager 56 determines the destination process of this event based on the flow management table 92 and the module management table 94 and sends the event to the message manager of that process. Send. When the flow management table 92 indicates that the message is to be output outside the system, the message distribution processing unit 90 outputs an event to the output module 84. The output module 84 further outputs this event to the outside.

  Thereafter, the message distribution processing unit 90 of the message manager 80 and the message managers 66 and 76 of the first process 52 and the second process 54 repeat the same processing as described above. As a result, data input to the input module 82 one after another from the outside is processed by a predetermined module, and the resulting event is output from the output module 84.

  In the system 50 described above, each module does not need to be aware of which module the event resulting from its processing is transmitted to. In any process, the message manager, not the module, decides the destination module, and if the destination module is in the same process, the event queue is used to deliver the event. Deliver the event. The module manager that has received the event distribution determines a transmission destination process based on the transmission destination module ID, and transmits it.

  Therefore, the independence of the module becomes extremely high, and it is not necessary to change the module according to the system configuration. Furthermore, regarding inter-process communication, all processes need only be transmitted to the module manager without regard to the destination process. Therefore, the overhead for communication between processes is reduced.

Therefore, by using such an inter-process communication mechanism, events can be distributed efficiently, and further, the independence of each module can be improved and a system can be freely assembled. Data is processed in each module while being transferred between processes, and each process can perform data processing in the correct order while adjusting the processing time by an event queue. As a result, a large amount of data processing such as voice recognition can be performed in real time. Further, since the modules can be freely combined, it is possible to easily perform performance experiments on systems having different configurations in a short time.
[Realization by computer]
The system of this embodiment is realized by computer hardware, a program executed by the computer hardware, and data stored in the computer hardware. FIG. 12 shows the external appearance of the computer system 330, and FIG. 13 shows the internal configuration of the computer system 330. As described above, this system can also be realized by connecting a plurality of computers via a network or the like.

  Referring to FIG. 12, this computer system 330 includes a computer 340 having an FD (flexible disk) drive 352 and a CD-ROM (compact disk read only memory) drive 350, a keyboard 346, a mouse 348, and a monitor 342. including.

  Referring to FIG. 13, in addition to the FD drive 352 and the CD-ROM drive 350, the computer 340 includes a CPU (Central Processing Unit) 356 and a bus 366 connected to the CPU 356, the FD drive 352, and the CD-ROM drive 350. And a read only memory (ROM) 358 for storing a boot-up program and the like, and a random access memory (RAM) 360 connected to the bus 366 for storing a program command, a system program, work data, and the like. Computer system 330 further includes a printer 344.

  The computer 340 further includes a network adapter board 368 that provides a connection to a local area network (LAN).

  A computer program for causing the computer system 330 to operate as the system 50 according to this embodiment (or a part of the first process 52, the second process 54, the module manager 56, etc.) is a CD- The data is stored in the CD-ROM 362 or FD 364 inserted in the ROM drive 350 or FD drive 352 and further transferred to the hard disk 354. Alternatively, the program may be transmitted to the computer 340 through a network and stored in the hard disk 354. The program is loaded into the RAM 360 when executed. The program may be loaded directly into the RAM 360 from the CD-ROM 362, from the FD 364, or via a network.

  This program includes a plurality of instructions that cause the computer 340 to operate as the processes 52 and 54, the module manager 56, and the modules executed in each process included in the system 50 according to the present embodiment. Some of the basic functions required for this are provided by operating system (OS) or third party programs running on the computer 340 or various toolkit modules installed on the computer 340. Therefore, this program does not necessarily include all functions necessary for realizing the system of this embodiment. This program need only include instructions that execute the above-described paraphrase rule selection device by calling an appropriate function or “tool” in a controlled manner so as to obtain a desired result. . The operation of computer system 330 is well known and will not be repeated here.

  In the above-described embodiment, the module management table is prepared for each process. However, the present invention is not limited to such an embodiment, and the same module management table may be used for all modules in the system. In the above embodiment, the module identifier is unique within the system. However, the present invention is not limited to such an embodiment, and the module identifier may be unique only within the process. However, in that case, in event communication, it is necessary to specify a transmission source and a transmission destination by a process name and a module identifier.

  The embodiment disclosed herein is merely an example, and the present invention is not limited to the above-described embodiment. The scope of the present invention is indicated by each claim in the claims after taking into account the description of the detailed description of the invention, and all modifications within the meaning and scope equivalent to the wording described therein are intended. Including.

It is a figure which shows the structural example of the system which consists of a some process each containing several modules. 1 is a block diagram of a system 50 according to an embodiment of the present invention. FIG. 6 is a diagram illustrating a configuration of an event 120. 6 is a diagram showing a configuration of a flow definition file 58. FIG. It is a block diagram of the message manager 80 of the module manager 56 shown in FIG. It is a figure which shows the structure of the flow management table 92. FIG. It is a figure which shows the structure of the module management table 94. FIG. FIG. 3 is a block diagram of the message manager 66 of the first process 52 shown in FIG. 3 is a diagram showing a configuration of a module management table 100. FIG. It is a flowchart which shows the process performed by each message distribution process part when the event in a process is received. It is a flowchart which shows the process performed when the message distribution process part 90 of the module manager 56 receives an out-of-process event. It is an external view of the computer system for implement | achieving the process of the system 50 which concerns on one embodiment of this invention, or its one part. It is a block diagram which shows the internal structure of the computer system shown in FIG.

Explanation of symbols

50 systems, 52, 54 processes, 56 module managers, 58 flow definition files, 60, 62, 64, 70, 72, 74 modules, 66, 76, 80 message managers, 82 input modules, 84 output modules, 90, 108 messages Distribution processing unit, 92, 102 Flow management table, 94, 100 Module management table, 96 Table creation processing unit, 104 Module management table creation processing unit, 106 Flow management table creation processing unit, 110 Event queue, 112 In-process message delivery Part

Claims (7)

A message management apparatus for managing message communication between the plurality of modules and message communication between the plurality of modules and a module outside the process in a process including a plurality of modules,
Each module is uniquely identified by a module identifier,
A message communicated between each module includes a source module identifier, a destination module identifier, a type of message to be transmitted, and data to be transmitted,
The message management device includes:
A message queue to temporarily store messages,
Message delivery means for delivering a message stored in the message queue to a module specified by a destination module identifier of the message in the process;
A message flow management means for determining a message destination module based on a message source module identifier and a message type according to a predetermined data flow, and outputting the destination module identifier;
In response to a message received from a module in the process, based on a source module identifier and a message type included in the message, a message destination module identifier is obtained from the message flow management unit, and the message A process for storing the message in the message queue according to whether or not the module specified by the acquired transmission destination module identifier is a module in the process, and a predetermined message outside the process. A message management device including message distribution means for selectively performing processing for transmission to a transmission destination. The message distribution means includes:
Module identifier storage means for storing a module identifier in the process;
Means for obtaining a message destination module identifier from the message flow management means based on a source module identifier and message type included in the message in response to a message received from a module in the process; ,
Means for setting the destination module identifier obtained by the means for obtaining as the destination module identifier of the received message;
Determination means for determining whether or not the transmission destination module identifier acquired by the acquisition means is stored in the module identifier storage means;
The received message is stored in the message queue in response to determining that the destination module identifier acquired by the acquiring unit is stored in the module identifier storage unit by the determining unit. Means for
In response to determining that the transmission destination module identifier acquired by the acquiring unit is not stored in the module identifier storage unit by the determining unit, the received message is sent out of the process. The message management apparatus according to claim 1, further comprising means for transmitting to a predetermined message transmission destination. A message management device for managing message communication between modules in a system comprising a plurality of processes each including one or a plurality of modules,
Each module in the system is uniquely identified by a module identifier,
A message communicated between each module includes a source module identifier, a destination module identifier, a type of message to be transmitted, and data to be transmitted,
The message management device includes:
A message flow management means for determining a message destination module based on a message source module identifier and a message type according to a predetermined data flow, and outputting the destination module identifier;
In response to the message received from the module in the process, the message destination module identifier of the message is acquired from the message flow management unit based on the source module identifier and the message type included in the message. A message distribution unit for distributing the received message to a process including a module specified by a transmission destination module identifier. A computer program that, when executed by a computer, causes the computer to operate as the message management device according to any one of claims 1 to 3. Multiple processes,
A data processing system including an inter-process message management means for managing message communication for realizing a data flow between the processes,
Each of the plurality of processes is
A plurality of modules each having one or a plurality of inputs and outputs, performing predetermined processing on the input data, and outputting;
In-process message management means for managing message communication between the plurality of modules and message communication between the plurality of modules and modules outside the process in the process,
Each module is uniquely identified by a module identifier,
A message communicated between each module includes a source module identifier, a destination module identifier, a type of message to be transmitted, and data to be transmitted,
The in-process message management means includes:
A message queue to temporarily store messages,
Message delivery means for delivering a message stored in the message queue to a module specified by a destination module identifier of the message in the process;
First message flow management means for determining a message destination module based on a message source module identifier and a message type according to a predetermined data flow, and outputting the destination module identifier;
In response to the message received from the module in the process, based on the source module identifier and message type included in the message, obtain the message destination module identifier from the first message flow management means, and A process for storing the message in the message queue according to whether or not the module specified by the acquired transmission destination module identifier is a module in the process, and the interprocess message management. Message distribution means for selectively performing processing to be transmitted to the means. The message distribution means includes:
Module identifier storage means for storing a module identifier in the process;
In response to a message received from a module in the process, to acquire a message destination module identifier from the first message flow management means based on a source module identifier and a message type included in the message Means of
Means for setting the destination module identifier obtained by the means for obtaining as the destination module identifier of the received message;
Determination means for determining whether or not the transmission destination module identifier acquired by the acquisition means is stored in the module identifier storage means;
The received message is stored in the message queue in response to determining that the destination module identifier acquired by the acquiring unit is stored in the module identifier storage unit by the determining unit. Means for
In response to determining that the transmission destination module identifier acquired by the acquiring unit is not stored in the module identifier storage unit by the determining unit, the received message is sent out of the process. Means for transmitting to a predetermined message destination. A computer program that, when executed by a computer, causes the computer to operate as the data processing system according to claim 5 or 6.

Images