JP5959451B2 - Real-time data transfer system and real-time data transfer method - Google Patents

Description

  The present invention relates to a real-time data transfer system and a real-time data transfer method for providing a real-time service to a user using a wireless mobile communication network and Internet communication.

  In recent years, communication using miniblogs or microblogs has become common. A feature of microblogging is that microblogging users (hereinafter referred to as “users”) post short sentences composed of tens to hundreds of tens of characters to the microblogging. Microblogging is conspicuously used as a simple blog where users can post casual words on microblogging and share their situation with other users.

  In addition, a miniblog can share information with other users by posting a comment with a URL (Uniform Resource Locator) in which the news article or the like has been described. Is possible. For this reason, miniblogs are not only used as a tool to get the latest information from friends, but are also widely used as information collection tools. For example, in a miniblog, by registering a user who is interested in the user's browsing list, the content of the user's remarks is automatically transmitted (PUSH). Recently, it is not uncommon for many media to utilize a Twitter (registered trademark) account and distribute information.

Twitter®, famous for microblogging, is a typical example of real-time services. Conventionally, a transfer system in a real-time service generally transmits received data as it is to a transmission destination without processing.
Patent Document 1 describes a technology that uses date information included in received data that is not real-time data.

JP 9-212456 A

For example, one of APIs (Application Programming Interface) provided by Twitter (registered trademark) is called a streaming API. The streaming API is configured to send update information from the server side to the client side while keeping an HTTP (Hypertext Transfer Protocol) connection open. When supplying real-time data acquired from such an API to the application side, the supplied data is generally copied and supplied to the buffer device on the output side of the transfer system. For this reason, a large load is applied between the buffer device and the application. This causes a problem that a failure occurs between the buffer device and the application, and real-time data is not successfully transferred to the application side.
An object of the present invention is to provide a real-time data transfer system and a real-time data transfer method that can transfer real-time data to an application satisfactorily.

In order to achieve the above object, a real-time data transfer method according to an aspect of the present invention is a real-time data transfer method for transferring real-time data received from a real-time data transmission system to an application on the transmission side, which is transferred to the application. A data receiving step for receiving data including the real-time data from the real-time data transmitting system, a receiving-side data holding step for temporarily holding the received data that is the data received in the data receiving step, and the reception A transfer step for transferring the real-time data included in the received data held in the side data holding step to the application side on the transmission side, and a transmission for temporarily holding the real-time data transferred in the transfer step A data holding step, a non-real time data filtering step for filtering non-real time data included in the received data and not the real time data, and a normal message storing information to be transmitted to the application included in the received data is deleted. A deletion message filtering step of filtering so that a deletion message included in the received data is not transmitted to the application when a predetermined condition is satisfied, and a tag is attached to the normal message included in the real-time data And a normal message distribution step of distributing the tagged normal message to the application according to the tag.
According to such a configuration, real-time data can be transferred to the application satisfactorily.

In the data receiving step, a date and time immediately after reception, which is a date and time immediately after receiving the received data, may be added to the received data.
According to such a configuration, it can be determined whether or not the received data is real-time data.
In the non-real-time data filtering step, a date and time information reading step of reading the date and time information in the received data by analyzing the received data held in the receiving side data holding step, a date and time included in the date and time information, A date and time comparison step for comparing the system date and time assigned to the analyzed received data; and in the date and time comparison step, a date and time included in the date and time information; and a date and time immediately after reception given to the analyzed reception data; And a received data deleting step of deleting the analyzed received data when it is determined that the difference is more than a predetermined threshold.
According to such a configuration, it can be determined whether or not the received data is real-time data.

Another reception side data holding for receiving and temporarily holding real-time data included in the received data and transmitted to the application through an acquisition path different from the reception data acquisition path in the reception side data holding step A system time comparison step of comparing a current time with a time of the date and time immediately after reception given to the reception data in the data reception step; and in the system time comparison step, the current time and the reception If it is determined that the time of the date and time immediately deviates from a predetermined time, the reception path of the reception data is changed from the acquisition path in the reception side data holding step to the other reception side data holding step. And an acquisition route switching step for switching to the acquisition route.
According to such a configuration, even if a failure occurs in the acquisition path in one of the reception data, the reception data can be acquired from another acquisition path, so that the downtime of the real-time data transfer system can be shortened. .

The deletion message filtering step is based on at least one of the information reading step of reading date information and ID information in the received data held in the receiving data holding step, and the read date information and ID information. An effective period determining step for determining an effective period of the delete message and a filtering step for filtering the delete message when it is determined that the effective period has been exceeded may be included.
According to such a configuration, it is possible to prevent unnecessary messages from being transmitted to the application.

The normal message distribution step includes a language analysis step of analyzing the normal message of the real-time data included in the received data acquired in the transfer step by using language analysis, and the normal message based on the analysis result A tagging step for assigning the tag to the tag, and a sorting step for sorting the normal message according to the tag given in the tagging step.
According to such a configuration, an appropriate message can be transmitted to the application.

In order to achieve the above object, a real-time data transfer system according to an aspect of the present invention is a real-time data transfer system that transfers real-time data received from a real-time data transmission system to an application on the transmission side, and transfers the real-time data to the application. A data receiving system that receives data including the real-time data from the real-time data transmission system, a receiving-side data holding device that temporarily holds received data that is the data received by the data receiving system, and the receiving-side data A transfer server that transfers the real-time data included in the received data acquired from a holding device to the application side on the transmission side, and a transmission-side data that temporarily holds the real-time data transferred from the transfer server. When deleting a holding device, a data filtering unit that filters non-real time data that is included in the received data and not the real time data, and a normal message that stores information that is included in the received data and is transmitted to the application A deletion message filtering unit that filters a deletion message included in the data so that it is not sent to the application when a predetermined condition is satisfied, and a tag is attached to the normal message included in the real-time data, and the tag And a normal message distribution unit that distributes the tagged normal message to the application.
According to such a configuration, real-time data can be transferred to the application satisfactorily.

  According to the present invention, real-time data can be successfully transferred to an application.

1 is a block diagram showing a schematic configuration of a real-time data transfer system 1 according to a first embodiment of the present invention. It is a block diagram which shows schematic structure of the transfer server 7 with which the real-time data transfer system 1 by the 1st Embodiment of this invention was equipped. It is a flowchart which shows an example of the flow of the real-time data transfer method by the 1st Embodiment of this invention. It is a flowchart which shows an example of the flow of the determination process (step S17) of the deletion message effective period in the real-time data transfer method by the 1st Embodiment of this invention. It is a figure which shows a flowchart, an example of a table, etc. which show an example of the flow of the message distribution process (step S23) using the tag in the real-time data transfer method by the 1st Embodiment of this invention. It is a figure which shows an example of the flow of a modified example of the determination process (step S17) of the effective period of the deletion message (step S17) in the real-time data transfer method according to the first embodiment of the present invention, and various tables. It is a figure which shows an example of the flow of a modification of the message distribution process (step S23) using the tag in the real-time data transfer method according to the first embodiment of the present invention, and various tables. It is a block diagram which shows schematic structure of the real-time data transfer system 2 by the 2nd Embodiment of this invention. It is a block diagram which shows schematic structure of the transfer server 8 with which the real-time data transfer system 2 by the 2nd Embodiment of this invention was equipped. It is a flowchart which shows an example of the flow of the real-time data transfer method by the 2nd Embodiment of this invention.

[First Embodiment]
(Schematic configuration of the real-time data transfer system 1 and the transfer server 7)
A real-time data transfer system and a real-time data transfer method according to a first embodiment of the present invention will be described with reference to FIGS. First, a schematic configuration of the real-time data transfer system according to the present embodiment will be described with reference to FIGS.

FIG. 1 shows a schematic configuration of a real-time data transfer system 1 according to the present embodiment. In FIG. 1, in order to facilitate understanding, in addition to the real-time data transfer system 1, a real-time data transmission system 11 provided on the reception side of the real-time data transfer system 1 and an application group provided on the transmission side. 13 is shown.
As shown in FIG. 1, the real-time data transfer system 1 according to the present embodiment receives real-time data received from the real-time data transmission system 11 in n applications 13-1, 13-2,. .., 13-n (n is a natural number). The real-time data transfer system 1 includes a data reception system 3, a reception side data holding device 5, a transfer server 7, and a transmission side data holding device 9.

  The data receiving system 3 receives data including real-time data transferred to the applications 13-1, 13-2, and 13-n from the real-time data transmitting system 11. Further, the data receiving system 3 gives the data the system date and time (an example of the date and time immediately after reception) of the real-time data transfer system 1 immediately after receiving the data from the real-time data transmitting system 11.

  The data transmitted by the real-time data transmission system 11 includes real-time data and non-real-time data that is not real-time data. Real-time data is data whose delay time is predetermined within a certain time. The delay time includes, for example, the time from when real-time data is generated until it is transmitted to the real-time data transfer system 1 and the time until the real-time data received by the real-time data transfer system 1 is transferred to the application group 13. . Non-real-time data is data that was originally real-time data, but whose delay time has exceeded a certain time.

  Real-time data and non-real-time data usually include messages. The normal message stores information to be transferred to the application together with information on the date and time of creation of the normal message. In addition, the real-time data and the non-real-time data include a deletion message that is given when it is desired to delete a normal message. The deletion message holds ID information of a normal message to be deleted. When the predetermined condition is not satisfied (details will be described later), the real-time data transfer system 1 transfers the deletion message to the application that has transmitted the normal message having the ID information. The application that has received the deletion message deletes the normal message to be deleted based on the ID information.

  The receiving side data holding device 5 temporarily holds received data that is data received by the data receiving system 3. The receiving-side data holding device 5 functions as a buffer device that temporarily holds the received data. For this reason, for example, even when a communication failure occurs between the transmission-side data holding device 9 and the application group 13 or when the transfer server 7 is replaced, the data transfer cannot be performed. You can continue to receive data. As a result, the real-time data transfer system 1 can reduce downtime, which is a system stop time.

  The transfer server 7 acquires real-time data included in the reception data held in the reception-side data holding device 5 from the reception-side data holding device 5 and transfers it to the application group 13 side on the transmission side. More specifically, the transfer server 7 transfers real-time data included in the acquired received data to the transmission-side application group 13 via the transmission-side data holding device 9.

  Here, a schematic configuration of the transfer server 7 will be described with reference to FIG. FIG. 2 is a block diagram showing a schematic configuration of the transfer server 7. As shown in FIG. 2, the transfer server 7 includes a control unit 7a, a data acquisition / holding unit 7b, a non-real-time data filtering unit 7c, a deletion message filtering unit 7d, a normal message sorting unit 7e, and a normal message. It has an output unit 7f and a bus line 7g.

The control unit 7a controls the data acquisition / holding unit 7b, the non-real time data filtering unit 7c, the deletion message filtering unit 7d, the normal message sorting unit 7e, and the normal message output unit 7f in an integrated manner. It has become. The control unit 7a controls data transmission / reception between these components via the bus line 7g.
The data acquisition / holding unit 7b is configured to acquire and temporarily hold the received data held in the receiving-side data holding device 5 based on a command from the control unit 7a.

  The non-real time data filtering unit 7c is configured to filter, that is, delete non-real time data included in the received data. The non-real-time data filtering unit 7c analyzes the received data acquired by the data acquisition / holding unit 7b provided in the transfer server 7 and analyzes the date / time information in the received data (the creation date / time of the normal message included in the received data). Information). The non-real-time data filtering unit 7 c compares the date and time included in the read date and time information with the system date and time of the transfer server 7 attached to the received data analyzed by the data receiving system 3. Further, when the non-real time data filtering unit 7c determines that the date and time of the received data and the system date and time of the transfer server 7 are more than a predetermined threshold, the normal message included in the received data is deleted. Yes. In this way, the transfer server 7 deletes non-real time data that is not real time data and does not transfer it to the application. Thereby, the real-time data transfer system 1 can prevent sending unnecessary messages to the application.

  Although details will be described later, the non-real-time data filtering unit 7c determines whether or not the received data is a deletion message, that is, whether it is a deletion message or a normal message. If the non-real-time data filtering unit 7c determines that the received data is a normal message, the non-real-time data filtering unit 7c executes non-real-time data deletion determination / deletion processing.

  If the non-real-time data filtering unit 7c determines that the received data is a deletion message, the deletion message filtering unit 7d performs filtering, that is, deletes the deletion message so as not to be transmitted to the application group 13 when a predetermined condition is satisfied. It has become. The deletion message filtering unit 7d reads the date / time information and ID information of the normal message included in the received data acquired by the data acquisition / holding unit 7b, and deletes the deletion message based on at least one of the read date / time information and the ID information. Determine the validity period.

The valid period is a period during which the deletion message is valid, that is, a period during which a normal message targeted for deletion can be deleted.
The deletion message filtering unit 7d filters, that is, deletes deletion messages that have exceeded the valid period. The deletion message filtering unit 7d transmits a deletion message that does not exceed the valid period to the application via the transmission side data holding device 9. In this way, the transfer server 7 does not transfer a deletion message that has exceeded the valid period to the application. Thereby, the real-time data transfer system 1 can prevent sending an unnecessary deletion message to the application.

  The normal message sorting unit 7e attaches a tag to the normal message included in the real-time data, and distributes the normal message to the application according to the assigned tag. The normal message distribution unit 7e distributes the normal message to the application using the tag as a key. The normal message distribution unit 7e analyzes the normal message of real-time data included in the received data acquired by the data acquisition / holding unit 7b using language analysis. Further, the normal message sorting unit 7e attaches a tag to the normal message based on the analysis result, and distributes the normal message to the application according to the assigned tag.

The normal message output unit 7f transmits the normal message sorted by the normal message sorting unit 7e and the deletion message within the valid period to the transmission side data holding device 9.
Returning to FIG. 1, the transmission-side data holding device 9 temporarily holds a normal message included in the real-time data transferred from the transfer server 7. The transmission side data holding device 9 functions as a buffer device that temporarily holds a normal message. The transmission side data holding device 9 stores normal messages corresponding to the applications 13-1, 13-2, and 13-n in the application group 13 in the transfer queue. The normal message is stored in the transfer queue, starts being transferred when it is accessed from the application, and is transmitted to the corresponding application 13-1, 13-2,..., 13-n. The transmission side data holding device 9 is designated with an expiration time for automatically deleting a normal message when there is no access from each service (application). The transmission side data holding device 9 is configured to automatically delete the registered normal message (real-time data) when the specified expiration time has elapsed since the normal message was registered. As a result, the real-time data transfer system 1 can prevent a large amount of real-time data from being accumulated in the transmission-side data holding device 9 for a long time. The transmission side data holding device 9 holds the expiration time by the setting file.

  The application group 13 includes a plurality (n in this example) of applications 13-1, 13-2, ..., 13-n. The applications 13-1, 13-2,..., 13-n are software having a function of performing work that a user such as a computer or a mobile terminal device wants to execute on the computer or the mobile terminal device.

The connection between the real-time data transmission system 11 and the data reception system 3 and the connection between the transmission-side data holding device 9 and each of the applications 13-1, 13-2,. Either of them may be used. Moreover, these connections may be directly connected, or may be a logic connection via an arbitrary communication network.
The data reception system 3, the reception side data holding device 5, the transfer server 7, and the transmission side data holding device 9 may be realized as physically separate devices, respectively, or as functions of the real-time data transfer system 1. It may be realized.

  In the present embodiment, the transfer server 7 includes a non-real-time data filtering unit 7c, a deletion message filtering unit 7d, and a normal message sorting unit 7e, but the non-real-time data filtering unit 7c, deletion message filtering At least one of the unit 7 d and the normal message sorting unit 7 e may be provided in the real-time data transfer system 1 separately from the transfer server 7.

(Real-time data transfer method)
Next, the real-time data transfer method according to this embodiment will be described with reference to FIGS. 3 to 7 with reference to FIGS. FIG. 3 is a flowchart showing an example of the flow of the real-time data transfer method according to this embodiment.
As shown in FIG. 3, in the real-time data transfer method according to the present embodiment, first, data is received (step S1 (an example of a data reception step)), and the process proceeds to step S3. In step S1, for example, the data reception system 3 provided in the real-time data transfer system 1 transmits data including real-time data to be transmitted to the applications 13-1, 13-2,. Receive from.

  In step S3 following step S1, the system date and time is given to the received data received, and the process proceeds to step S5. In step S3, for example, the data receiving system 3 gives the system date and time (an example of date and time immediately after reception) of the real-time data transfer system 1 immediately after receiving data from the real-time data transmitting system 11 to the data. For example, when the received data received by the data receiving system 3 is in the JSON (Java Script (registered trademark) Object Notation) format, a plurality of messages are collected in the received data. The plurality of messages includes a normal message and a deletion message. The data receiving system 3 gives the system date and time information to the received data in the form of ““ timestamp ”:”, for example. Thereby, the system date and time with the same date and time are given to the plurality of messages.

In step S5 following step S3, the reception data received in step S1 is stored, and the process proceeds to step S7. In step S5 (an example of a reception side data holding step), for example, the reception data received by the data reception system 3 is temporarily held in the reception side data holding device 5.
In step S7 following step S5, the received data is divided for each message, and the process proceeds to step S9. In step S7, for example, the data acquisition / holding unit 7b provided in the transfer server 7 divides and holds, for example, 1000 normal messages included in the acquired received data for each message.

The received data held in the receiving side data holding step (step S5) is obtained by the processing of step S7, the processing of loop 1 (steps S9 to S23) starting from the next step S9 and the processing of loop 2 (steps S25 to S29). A transfer step for transferring the included real-time data to the application group 13 side on the transmission side is executed.
In step S9, the process of loop 1 is started, and the process proceeds to step S11.

  In step S11, the message is analyzed to read the date information, and the process proceeds to step S13. In step S11 (an example of the date information reading step), for example, the reception data held in the reception side data holding step (step S5) is analyzed to read the date information in the reception data. More specifically, the non-real-time data filtering unit 7c acquires data of the first message among a plurality (1000 in this example) of messages held in step S5 and acquired and decomposed in step S7. -Obtained from the holding unit 7b and analyzed to read date / time information (information on the date / time of creation of the first message).

  In step S13 following step S11, the date / time information of the message is compared with the system date / time given in step S3, and the process proceeds to step S15. In step S13 (an example of a date / time comparison step), for example, the non-real-time data filtering unit 7c applies the date / time included in the date / time information of the first message analyzed in step S13 and the received data including the first message. For example, the system date and time of "" timestamp ":" given in step S3 is compared.

  In step S15 subsequent to step S13, it is determined whether or not the first message is a deletion message. If it is determined in step S15 that the first message is a deletion message, the process proceeds to step S17. If it is determined that the first message is not a deletion message, that is, a normal message, the process proceeds to step S19. In step S15, for example, the non-real time data filtering unit 7c determines whether or not the first message is a deletion message. The non-real-time data filtering unit 7c, for example, based on the format of the first message (JSON format in this example) or the presence / absence of date / time information stored in the first message. It is determined whether or not the eye message is a deletion message.

  In step S19 after No in step S15, it is determined whether or not the date and time of the message and the date and time of the system date and time are more than a predetermined threshold. If it is determined in step S19 (an example of date / time comparison step) that the date / time of the message and the date / time of the system date / time are different from each other by a predetermined threshold value or more, the process proceeds to step S21. Shifts to step S23 if it is determined that they are not deviating more than a predetermined threshold. In step S19, for example, the non-real time data filtering unit 7c determines that the date and time of the first message read in step S11 and the date and time of the system date and time given in step S3 are more than a predetermined threshold. If so, the process of step S21 is executed. On the other hand, when the non-real time data filtering unit 7c determines that the date / time of the first message read in step S11 and the date / time of the system date / time given in step S3 are not different from a predetermined threshold value or more. Performs the process of step S23.

  In step S21 following Yes in step S19, the message is deleted, and the process proceeds to step S25. In step S21 (an example of the received data deletion step), for example, the non-real time data filtering unit 7c determines that the first message included in the received data exceeds a delay time that can be processed as real time data, Delete the first message. For example, the non-real time data filtering unit 7c notifies the control unit 7a that the first message is a deletion target. Upon receiving the notification from the non-real-time data filtering unit 7c, the control unit 7a transmits a deletion instruction for the first message to the data acquisition / holding unit 7b. The data acquisition / holding unit 7b that has received the deletion command deletes the message to be deleted.

  On the other hand, in step S17 after Yes in step S15, the deletion message valid period determination process is executed, and the process proceeds to step S25. In step S17 (an example of a deletion message filtering step), when a normal message that stores information to be transmitted to the application included in the data received in step S1 is deleted, the deletion message included in the data satisfies a predetermined condition. If so, it is filtered so that it is not sent to the application.

  FIG. 4 is a flowchart illustrating an example of a deletion message valid period determination process. As shown in FIG. 4, in the determination process of the deletion message validity period, first, among the plurality of normal messages included in the received data acquired by the transfer server 7 in step S7, the ID number (an example of ID information) is the latest. A normal message is extracted (step S101), and the process proceeds to step S103. In the present embodiment, for example, the ID number has a larger value for new messages. Note that the sorting order of the ID number values is an example, and is not limited to this as long as the ID numbers are sorted so that the latest normal message can be extracted. In step S101 (an example of an information reading step), for example, the deletion message filtering unit 7d acquires all the normal messages held in the data acquisition / holding unit 7b, and extracts the normal message with the latest ID number. For example, in the case of JSON format data, since the data includes a plurality of normal messages, the deletion message filtering unit 7d reads the ID numbers of the plurality of normal messages and extracts the latest normal message.

  In step S103 following step S101, the ID number of the deletion message is compared with the latest ID number of the extracted normal message, and the process proceeds to step S105. In step S103 (an example of the validity period determination step), for example, the deletion message filtering unit 7d includes the ID number of the deletion message transmitted together with the normal message having the latest ID number and the extracted normal message. Compare the latest ID number. In step S103, if the deletion message filtering unit 7d determines that there is no deletion message transmitted together with the normal message having the latest ID number, the deletion message filtering unit 7d does not execute step S105 and step 107, but deletes the deletion message. The valid period determination process ends, and the process proceeds to step S25 (see FIG. 3).

  In step S105 following step S103, it is determined whether or not the difference between the latest ID number of the normal message and the ID number of the deletion message is greater than or equal to a threshold value. In step S105 (an example of an effective period determination step), when it is determined that the difference is equal to or greater than the threshold (when a predetermined condition is satisfied), the process proceeds to step S107, and it is determined that the difference is smaller than the threshold. In this case, the process for determining the deletion message validity period is terminated, and the process proceeds to step S21 (see FIG. 3). In step S105, for example, the deletion message filtering unit 7d subtracts the ID number of the deletion message from the latest ID number of the normal message, and determines whether the subtraction result is equal to or greater than a threshold value.

  For example, the threshold value is set to a value obtained by multiplying a predetermined coefficient (for example, the number of digits of the ID number to be compared) by the accumulation days. For example, when determining by comparing the upper 4 digits of the ID number of the normal message and the ID number of the deletion message, the predetermined coefficient is “4”. In the present embodiment, for example, the number of accumulation days is set to “3”. Further, the predetermined coefficient and the accumulation days can be changed by, for example, a setting file. Further, when the comparison is made using all digits of the ID number of the normal message and the ID number of the deletion message, the threshold value is set to a predetermined value (for example, 1,000,000,000,000). The predetermined value can be changed, for example, in a setting file.

  In step S107 following step S105, the deletion message is dropped, the deletion message valid period determination process is terminated, and the process proceeds to step S25 (see FIG. 3). In step S107 (an example of a filtering step for filtering a deletion message), for example, the deletion message filtering unit 7d filters the deletion message, that is, deletes the deletion message. For example, the deletion message filtering unit 7d notifies the control unit 7a that the deletion message is a deletion target. Upon receiving the notification from the deletion message filtering unit 7d, the control unit 7a transmits a deletion instruction for the deletion message to the data acquisition / holding unit 7b. The data acquisition / holding unit 7b that has received the deletion command deletes the deletion message to be deleted.

Here, the process for determining the validity period of the deletion message will be described in detail.
In general, for example, JSON format data transmitted from the real-time data transmission system 11 has a plurality of deletion messages and a plurality of normal messages in a lump. The transfer server 7 acquires the lump of data.
The deletion message is transmitted when it is desired to delete the normal message, and holds the ID information of the normal message to be deleted.

  The normal message includes the ID information and the posting date and time of the normal message in the JSON format data. For this reason, data with an old posting date / time can be deleted using the posting date / time information. On the other hand, the deletion message does not include date / time information in the JSON format data, and includes only ID information. For this reason, it is impossible to determine whether or not the data (normal message) to be deleted by the deletion message is data that needs to be kept alive, using the date / time information.

  Therefore, in the present embodiment, the deletion message is filtered using the ID information of the normal message acquired together with the deletion message. An ID number, which is one of the ID information of the normal message included in the real-time data, is given sequentially by data in one JSON format. For this reason, in the present embodiment, the ID number of the deletion message is compared with the ID number of the normal message transmitted together with the deletion message, and the deletion message is transferred to each application according to the comparison result. It is determined whether or not. The real-time data transfer method and the real-time data transfer system 1 according to the present embodiment, when the difference between the latest ID number of the normal message in the received data and the ID number of the delete message is greater than or equal to the threshold value, Is excluded from being transferred to the application, and delete messages are filtered. The threshold value is configured to be changeable in the setting file.

  Returning to FIG. 3, in step S <b> 23 next to No in step S <b> 19, message distribution processing is executed using tags. In step S23 (an example of a normal message distribution step), a setting is applied to assign a tag to the normal message included in the data stored in step S5, and distribute the tagged normal message to the application according to the assigned tag. Process.

FIG. 5 is a flowchart illustrating an example of a flow of message distribution processing using tags. FIG. 5 shows a map and a setting file used in message distribution processing using tags, on the right side of the flowchart.
As shown in FIG. 5, in the message distribution process using tags, first, a normal message included in the received data acquired by the transfer server 7 in step S7 is analyzed using language determination (an example of language analysis). (Step S201). In step S201 (an example of a language analysis step), for example, the normal message sorting unit 7e performs language determination for each message divided in step 7.

  In step S201, for example, the normal message sorting unit 7e performs language determination of the first message included in the data received from the real-time data transmission system 11 and divided for each message by a line feed code. The normal message distribution unit 7e performs language determination using a general language determination module. The normal message sorting unit 7e outputs the language determination result of the first message.

  In step S203 following step S201, tagging data is added to the map, and the process proceeds to step S205. As shown on the right side of the flowchart in FIG. 5, the normal message sorting unit 7e has a tagging data holding map M1. The tagging data holding map M1 is composed of two columns. “Tag (language)” in the first column indicates a tag corresponding to the language of the message. “Value” in the second column indicates a normal message held in the tagging data map M1. In FIG. 5, for example, in the “tag (language)” column, “Ja” indicating Japanese, “Eng” indicating English, and all the determined language tags are used as tags used in the present embodiment. “All” shown is listed. In this example, when all Japanese and English are acquired, “All” is designated as a tag. “Text A”, “Text B”, and “Text C” listed in the “Value” column indicate normal messages.

  In step S203 (an example of a tagging step), for example, the normal message sorting unit 7e adds a tag to the normal message based on the language determination result in step S201 and adds the normal message to the tagging data holding map M1. More specifically, if the normal message sorting unit 7e determines that the first message is in Japanese, the Value column associated with the tag “Ja” in the tagging data holding map M1. The first message is added to (in this example, the first message is represented as “text A”).

In step S205 following step S203, registration processing for registering a message corresponding to the tag in the transfer queue of the normal message output unit 7f is started.
When the registration process to the transfer queue starts in step S205, the tag used in the transmission side data holding device 9 (the tag set in the transfer queue) and the “tag” field of the tagging data holding map M1 are next. It is determined whether or not the tags listed in the above match (step S207). If it is determined that both tags match, the process proceeds to step S209. If it is determined that both tags do not match, the process proceeds to step S211. In step S207, the determination process is sequentially executed for all tags registered as tags used in the transmission side data holding device 9.

  In step S207, for example, it is assumed that “Ja” is set in the first transfer queue of the transmission-side data holding device 9 as shown below the tagging data holding map M1 in FIG. The normal message distribution unit 7e matches “Ja” in the first line of the “tag” column of the tagging data holding map M1 with the tag “Ja” set in the setting file of the transmission side data holding device 9. The determination is made and the process proceeds to step S209.

  In step S209 following step S207, a message corresponding to the tag is registered in the transfer queue. In step S209, for example, the normal message sorting unit 7e sends a normal message associated with a tag that matches the tag set in the setting file F1 to a transfer queue (message storage) (not shown) provided in the normal message output unit 7f. Register). For example, the normal message sorting unit 7e notifies the control unit 7a that the tag “Ja” and the first message associated with the tag are to be registered in the transfer queue. Receiving the notification from the normal message distribution unit 7e, the control unit 7a transmits a registration command for registering the first message in the transfer queue corresponding to the tag “Ja”. The normal message output unit 7 f that has received the registration command registers the first message in the transfer queue corresponding to the tag “Ja”.

If it is determined in step S207 that the two tags do not match, the process proceeds to step S211.
In step S207 No or in step S211 after step S209, it is determined whether or not all transfer queues have been processed. If it is determined that all transfer queues have been processed, a message using a tag is used. This distribution process ends, and the process proceeds to step S23 (see FIG. 3). On the other hand, if it is determined in step S211 that the processing of all transfer queues has not been completed, the process returns to step S205, and the processing of steps S205 to S211 is repeatedly executed until the processing of all transfer queues is completed.

Returning to FIG. 3, in step S25 following step S17 or step S21, a transfer step for transferring the real-time data included in the received data acquired in the receiving side data holding step (step S5) to the transmitting side for all messages. It is determined whether or not it has been completed. If it is determined in step S23 that the transfer step has been completed for all messages, the process proceeds to step S25. On the other hand, if it is determined that the transfer step has not been completed for all messages, the process returns to step S9, the next message is acquired, and the processes from step S11 to step S25 are executed. Until the transfer step is completed for all messages, the processing from step S9 to S25 is repeatedly executed.
In step S27 following step S25, message storage processing is started for the transmission side data holding device for all tags.

In step S29 following step S27, the message is stored in the transmission side data holding device, and the process proceeds to step S31. For example, the normal message output unit 7f transfers the normal message registered in its own transfer queue to the transfer queue corresponding to the same tag as the tag associated with the normal message provided in the transmission side data holding device 9. To do. When it is determined that the message transfer process to the transmission side data holding device 9 has been completed for all the normal messages registered in the transfer queue of the normal message output unit 7f, the real-time data transfer process ends. On the other hand, if it is determined that the message transfer process has not been completed for all normal messages, the process returns to step S27, the next normal message is acquired, and the processes of steps S29 and S31 are executed. The processing from step S27 to S31 is repeatedly executed until the message transfer processing is completed for all messages.
The normal message received by the receiving side data holding device 5 is copied and registered in the transfer queue of the sending side data holding device 9. The normal message registered in the transfer queue is transmitted to the accessed applications 13-1, 13-2, ..., 13-n.

  As described above, the real-time data transfer system 1 according to the present embodiment has a reception-side data holding device and a transmission-side data holding device that temporarily hold data on each of the data reception side and the data transmission side. doing. That is, the real-time data transfer system 1 has a configuration in which a data receiving unit and a data transmitting unit are blocked for each function, and both functional blocks are connected by a transfer server. As a result, the real-time data transfer system 1 can easily isolate a problem in the occurrence of a failure, and can localize the point of occurrence of the failure.

In addition, the real-time data transfer system 1 compares the system date and time when the data is received by the data receiving system with the date and time information held by the received data itself. Is not sent to the application. Thereby, the real-time data transfer system 1 can prevent erroneous data transmission.
In addition, the real-time data transfer system 1 determines whether or not a deletion message is necessary using ID information of a normal message received together with the deletion message. Thereby, the real-time data transfer system 1 can filter the deletion message without date information.

  In addition, the real-time data transfer system 1 can tag real-time data and transfer the real-time data to an application according to the tag. The real-time data transfer system 1 can tag real-time data using at least one of language determination and morphological analysis described later, and transfer real-time data to an application that uses the same tag as the assigned tag. Thereby, since the real-time data transfer system 1 can transfer only necessary data to the application, it is possible to reduce the load on the application side.

(Modification 1)
Next, a real-time data transfer system and a real-time data transfer method according to the first modification of the present embodiment will be described with reference to FIGS. 1 to 3 and FIG. The real-time data transfer system and the real-time data transfer method according to the present modification are different from the deletion message valid period determination process (step S17) shown in FIG. This is the same as the transfer method. Therefore, only the deletion message validity period determination process (step S17) in this modification will be described below, and description of the configuration of the real-time data transfer method and the real-time data transfer system other than the determination process will be omitted.

  FIG. 6 is a flowchart illustrating an example of the flow of the deletion message valid period determination process in the present modification. FIG. 6 also shows a table and a setting file used in the determination process of the deletion message validity period on the right side of the flowchart. As shown in FIG. 6, in the determination process of the deletion message validity period in this modification, first, the ID information (ID number) and date / time information of the first normal message of each day among the normal messages in the real-time data are acquired. And hold (step S301), the process proceeds to step S303. In step S301, for example, the deletion message filtering unit 7d acquires all the dates of the normal message held in the data acquisition / holding unit 7b and the same ID and the minimum ID number, and FIG. It is held in the minimum ID number management table T1 shown on the right side of the flowchart. The minimum ID number management table T1 includes two items, “data” and “Start_ID”. “Data” indicates the date acquired by the deletion message filtering unit 7d from the data acquisition / holding unit 7b. “Start_ID” indicates the minimum ID number acquired by the deletion message filtering unit 7d from the data acquisition / holding unit 7b. The minimum ID number management table T1 can hold the date and time acquired by the deletion message filtering unit 7d from the data acquisition / holding unit 7b in association with the minimum ID number.

  For example, the minimum ID number of the normal message that is held in the data acquisition / holding unit 7b and the date / time information date is “October 16” is “1”, and the date / time information date is “October 17”. It is assumed that the smallest ID number in the normal message “day” is “101”. In this case, as illustrated in FIG. 6, the deletion message filtering unit 7d holds October 16 (10/16) in the first line of the “data” field, and “1” in the first line of the “Start_ID” field. ". Further, the deletion message filtering unit 7d holds October 17 (10/17) in the second row of the “data” column, and holds “101” in the second row of the “Start_ID” column.

  In step S303 following step S301, it is determined whether or not a delete message has been received. If it is determined in step S303 that a delete message has been received, the process proceeds to step S305. If it is determined that no delete message has been received, the process for determining the deletion message validity period is terminated without executing steps S305 to 311 described later. The process proceeds to step S21 (see FIG. 3). In step S303, for example, the deletion message filtering unit 7d determines that the deletion message has been received if the deletion message is held in the data acquisition / holding unit 7b, and the deletion message filtering unit 7b does not hold the deletion message. It is determined that no delete message has been received.

  In step S305 subsequent to step S303, the reception date / time of the deletion message is determined based on the held normal message ID number and date / time information (date), and the process proceeds to step S307. In step S307, for example, the deletion message filtering unit 7d acquires the ID number of the deletion message held in the data acquisition / holding unit 7b, and the ID of the normal message held in the minimum ID number management table T1. The reception date and time of the deletion message is determined by comparing with the number. As shown below the minimum ID number management table T2 in FIG. 6, it is assumed that the ID number (Start_ID) of the deletion message is “50”. The deletion message filtering unit 7d refers to the minimum ID number management table T1, and the date “October 16” is associated with the ID number “1”, and the date “October 17” is the ID number “101”. Are associated with each other, it is determined that the reception date / time is October 16 from ID numbers “1” to “100”. The deletion message filtering unit 7d determines that the reception date and time of the deletion message is October 16, since the ID number of the deletion message is “50”.

  In step S307 following step S305, it is determined whether or not the normal message to be deleted is alive. If it is determined that the normal message to be deleted is alive, the process proceeds to step S309, and the normal message to be deleted is If it determines with not alive, it will transfer to step S311. In step S307, for example, if the deletion message filtering unit 7d determines that the reception date and time of the deletion message is within the validity period of the deletion message, the deletion message filtering unit 7d determines that the normal message to be deleted is alive. On the other hand, when the deletion message filtering unit 7d determines that the reception date and time of the deletion message exceeds the valid period of the deletion message, the deletion message filtering unit 7d determines that the normal message to be deleted is not alive. The deletion message filtering unit 7d determines whether the reception date / time of the deletion message is within the effective period of the deletion message based on the setting file in which the effective period is set. As shown below the deletion message in FIG. 6, the setting file F2 in which the validity period is set specifies the number of days of the message storage period (in FIG. 6, the number of days is represented by “x”). ing. The deletion message filtering unit 7d acquires the current system time (including date) of the transfer server 7, and if the difference between the system time and the reception date / time of the deletion message is within the number of days of the message storage period, the deletion period is valid. If the difference exceeds the number of days, it is determined that it is outside the valid period.

  In step S309 subsequent to step S307, the deletion message is transferred to the transmission side data holding device, the deletion message valid period determination process is terminated, and the process proceeds to step S25 (see FIG. 3). In step S309, for example, the deletion message filtering unit 7d transmits the deletion message to the transmission side data holding device 9 via the normal message output unit 7f. For example, the deletion message filtering unit 7d notifies the control unit 7a that the deletion message is within the valid period. Receiving the notification from the deletion message filtering unit 7d, the control unit 7a transmits an output command for outputting the deletion message to the transmission side data holding device 9 to the normal message output unit 7f. The normal message output unit 7 f that has received the output command outputs a deletion message to the transmission side data holding device 9.

  On the other hand, in step S311 following step S307, the deletion message is dropped, the processing for determining the validity period of the deletion message is terminated, and the process proceeds to step S25 (see FIG. 3). In step S311, for example, the deletion message filtering unit 7d filters, that is, deletes the deletion message. For example, the deletion message filtering unit 7d notifies the control unit 7a that the deletion message is a deletion target. Upon receiving the notification from the deletion message filtering unit 7d, the control unit 7a transmits a deletion instruction for the deletion message to the data acquisition / holding unit 7b. The data acquisition / holding unit 7b that has received the deletion command deletes the deletion message to be deleted.

  As described above, according to the real-time data transfer system and the real-time data transfer method according to this modification, it is possible to prevent the deletion message outside the valid period from being transferred to the transmission-side data holding device. As a result, the real-time data transfer system and the real-time data transfer method according to the present modification can delete unnecessary data in the transfer server, thereby reducing the probability of failure occurrence between the transmission-side data holding device and the application.

(Modification 2)
Next, a real-time data transfer system and a real-time data transfer method according to the second modification of the present embodiment will be described with reference to FIGS. 1 to 3 and FIG. The real-time data transfer system and the real-time data transfer method according to the present modification are different from the real-time data transfer system and the real-time data according to the above embodiment except that the message distribution process (step S23) using the tag shown in FIG. This is the same as the data transfer method. For this reason, only the message distribution process (step S23) using the tag in this modification will be described below, and the description of the configuration of the real-time data transfer method and the real-time data transfer system other than the determination process will be omitted.

FIG. 7 is a flowchart illustrating an example of a flow of message distribution processing using tags. FIG. 7 also shows various tables and the like used in message distribution processing using tags on the right side of the flowchart.
As shown in FIG. 7, in message distribution processing using tags, first, morphological analysis (an example of language analysis) is performed on the normal message included in the received data acquired by the transfer server 7 in step S7 (see FIG. 3). (Step S401). In step S401 (an example of language analysis step), for example, the normal message sorting unit 7e performs morphological analysis for each message divided in step 7.

  As shown on the right side in FIG. 7, the normal message sorting unit 7e has a morpheme analysis table T2 in which words (morphemes) used in an application are associated with tags specific to the application. The morphological analysis table T2 is composed of three columns. The first column “morpheme” indicates the word used in the application, the second column “part of speech” indicates the part of speech of the word as “morpheme”, and the third column “tag” indicates the tag specific to the application. ing. In this example, the morpheme “Kyoto” is associated with the part of speech “noun” and the tag “Poi”. The morpheme “attempted murder” is associated with the part of speech “noun” and the tag “NG”. The morpheme “train” is associated with the part of speech “noun” and the tag “Train”. Further, the “program” of the morpheme is associated with the part of speech “noun” and the tag “TV”. Note that the morpheme analysis table T2 is an example, and it is of course possible to include a verb, an adjective, and the like in the word “morpheme”.

In step S401, the normal message sorting unit 7e refers to the morpheme analysis table T2, and finds a word that matches the word listed in the “morpheme” column of the morpheme analysis table T2 in the first message. Outputs the word and the tags listed in the “tag” column and associated with the word as the morphological analysis result.
In step S403 following step S401, tagging data is added to the map, and the process proceeds to step S405. As shown below the morphological analysis table T2 in FIG. 7, the normal message sorting unit 7e has a tagging data holding map M2. The tagging data holding map M2 is composed of two columns. The “tag” in the first column indicates the same tag as the “tag” in the third column of the morphological analysis table T2. In the “tag” column, the same tags listed in the “tag” in the third column of the morphological analysis table T2 are listed. “Value” in the second column indicates a normal message held in the tagging data map M2.

  In step S403 (an example of a tagging step), for example, the normal message sorting unit 7e adds a tag to the normal message and adds the normal message to the tagging data holding map M2 based on the morphological analysis result in step S401. . More specifically, when the word “Kyoto” is found in the first message, for example, the normal message sorting unit 7e is associated with the tag “Poi” of the tagging data holding map M2. The first message is added to the Value column (in this example, the first message is represented as “text 1”). Similarly, when the normal message sorting unit 7e finds a word listed in the “morpheme” column of the morpheme analysis table T2 in the first message, it is associated with the tag corresponding to the word. The first message is added to the “Value” field.

In step S405 following step S403, registration processing for registering a message corresponding to the tag in the transfer queue of the normal message output unit 7f is started.
When the registration process to the transfer queue starts in step S405, the tag used in the transmission side data holding device 9 (the tag set in the transfer queue) and the “tag” column of the tagging data holding map M2 It is determined whether or not the tags listed in the above match (step S407). If it is determined that both tags match, the process proceeds to step S409. If it is determined that both tags do not match, the process proceeds to step S411. In step S407, the determination process is sequentially executed for all tags registered as tags to be used in the transmission side data holding device 9.

  In step S407, for example, it is assumed that “Poi” is set in the first transfer queue of the transmission-side data holding device 9 as shown below the tagged data holding map M2 in FIG. The normal message distribution unit 7e matches “Poi” in the first line of the “Tag” column of the tagging data holding map M1 with the tag “Poi” set in the setting file of the transmission side data holding device 9. The determination is made and the process proceeds to step S409.

  In step S409 following step S407, a message corresponding to the tag is registered in the transfer queue. In step S409, for example, the normal message sorting unit 7e sends a normal message associated with a tag that matches the tag set in the setting file F3 to a transfer queue (message storage) (not shown) provided in the normal message output unit 7f. Register). For example, the normal message distribution unit 7e notifies the control unit 7a that the tag “Poi” and the first message associated with the tag are to be registered in the transfer queue. Upon receiving the notification from the normal message distribution unit 7e, the control unit 7a transmits a registration command for registering the first message in the transfer queue corresponding to the tag “Poi” to the normal message output unit 7f. The normal message output unit 7 f that has received the registration command registers the first message in the transfer queue corresponding to the tag “Poi”.

If it is determined in step S407 that the two tags do not match, the process proceeds to step S411.
In step S407 No or in step S411 following step S409, it is determined whether or not all transfer queues have been processed. If it is determined that all transfer queues have been processed, a message using a tag is used. This distribution process ends, and the process proceeds to step S25 (see FIG. 3). On the other hand, if it is determined in step S411 that the processing of all transfer queues has not been completed, the process returns to step S405, the next message is acquired, and the processes from step S407 to S411 are executed. Until the processing of all the transfer queues is completed, the processing of steps S405 to S411 is repeatedly executed.

  As described above, according to the real-time data transfer system and the real-time data transfer method according to this modification, real-time data is tagged using language determination, and real-time data is transferred to an application that uses the same tag as the assigned tag. can do. As a result, the real-time data transfer system can reduce the load on the application side.

[Second Embodiment]
(Schematic configuration of the real-time data transfer system 2 and the transfer server 8)
Next, a real-time data transfer system and a real-time data transfer method according to the second embodiment of the present invention will be described with reference to FIGS. First, a schematic configuration of the real-time data transfer system according to the present embodiment will be described with reference to FIG.

  FIG. 8 shows a schematic configuration of the real-time data transfer system 2 according to the present embodiment. In FIG. 8, in order to facilitate understanding, in addition to the real-time data transfer system 2, a real-time data transmission system 11 provided on the reception side of the real-time data transfer system 2 and an application group provided on the reception side. 13 is shown. Moreover, the same code | symbol is attached | subjected to the component which show | plays the function and effect | action similar to the real-time data transfer system 1 by the said 1st Embodiment, and the description is abbreviate | omitted.

  As shown in FIG. 8, the real-time data transfer system 2 includes a data reception system 3, a reception side data holding device 5, a transfer server 8, and a transmission side data holding device 9. Further, the real-time data transfer system 2 has the same configuration as that of the reception-side data holding device 5 and receives a reception-side data holding device (another reception side) that temporarily holds real-time data included in the reception data and transmitted to the application. An example of a data holding device) 15 is provided. The receiving side data holding device 15 is configured to input the same data as the receiving side data holding device 5 almost simultaneously. The receiving-side data holding device 5 is a device that is normally used (a receiving-side data holding device as a positive). The reception-side data holding device 15 is a secondary (standby) device (reception-side data holding device as a secondary) used when a failure occurs in the reception-side data holding device 5. As described above, the reception side data holding device of the real-time data transfer system 2 has two processes of the primary side and the secondary side. Normally, the transfer server 8 accesses the process of the reception side data holding device 5 that is positive. Get received data. When the transfer server 8 goes to obtain the received data, and an exception abnormality occurs in the process of the receiving data holding device 5, the transfer server 8 receives the receiving data from the process of the receiving data holding device 15 as the subordinate. The acquisition route of received data is switched so that it can be acquired.

  Here, a schematic configuration of the transfer server 8 will be described with reference to FIG. FIG. 9 is a block diagram showing a schematic configuration of the transfer server 8. As shown in FIG. 9, the transfer server 8 includes a control unit 8a, a data acquisition / holding unit 8b, a non-real time data filtering unit 8c, a deletion message filtering unit 8d, a normal message sorting unit 8e, and a message output. Unit 8f, bus line 8g, system time comparison unit 8h, and acquisition path switching unit 8i. The control unit 8a, the data acquisition / holding unit 8b, the non-real-time data filtering unit 8c, the deletion message filtering unit 8d, the normal message sorting unit 8e, the message output unit 8f, and the bus line 8g are the control unit 7a, the data acquisition / holding unit. 7b, the non-real-time data filtering unit 7c, the deletion message filtering unit 7d, the normal message sorting unit 7e, the normal message output unit 7f, and the bus line 7g have the same configuration and exhibit the same functions.

  The system time comparison unit 8h compares the current system time of the transfer server 8 with the time of the system date and time given to the received data by the data reception system 3. In addition, the acquisition path switching unit 8i determines that the current system time by the system time comparison unit 8h and the time of the system date and time given to the received data by the data reception system 3 are different from a predetermined time. In this case, the reception data acquisition path is switched from the reception side data holding device 5 to the reception side data holding device 15.

(Real-time data transfer method according to modification 2)
Next, a real-time data transfer method according to this modification will be described with reference to FIGS. 8 and 9 and FIG. The real-time data transfer method according to the present modification is substantially the same as the real-time data transfer method according to the above-described embodiment except that the reception data acquisition path is changed, and different points will be described below.

  FIG. 10 is a flowchart showing an example of the flow of the real-time data transfer method according to this modification. The processing in steps S501 to S509 shown in FIG. 10 is the same as the processing in steps S1 to S9 shown in FIG. In this embodiment, in step S501, the receiving side data holding device 15 receives data from the receiving data system 3 when the receiving side data holding device 5 receives data from the receiving data system 3 (separately). An example of receiving side data holding step).

In step S511 following step S509, the current system time is acquired, and the process proceeds to step S513. In step S511, for example, the system time comparison unit 8h acquires the current system time of the transfer server 8.
In step S513 following step S511, the current system time of the transfer server 8 is compared with the system date and time given in step S503, and the process proceeds to step S515. In step S513 (an example of a system time comparison step), for example, the system time comparison unit 8h is given to the current system time of the transfer server 8 acquired in step S511 and the received data including the first message in step S503. For example, the system date and time of ““ timestamp ”:” is compared.

  In step S515 subsequent to step S513, it is determined whether or not the first message is a deletion message. If it is determined in step S515 that the first message is a deletion message, the process proceeds to step S517. If it is determined that the first message is not a deletion message, that is, a normal message, the process proceeds to step S519. In step S515, for example, the non-real time data filtering unit 8c determines whether or not the first message is a deletion message.

  In step S519 following No in step S515, whether or not the difference between the current system time and the time of the system date and time given to the received data including the first message deviates from a predetermined time. Determine whether. If it is determined in step S519 that both times are deviated from the predetermined time, the process proceeds to step S521. If it is determined that both times are not deviated from the predetermined time, the process proceeds to step S523. In step S519, for example, the system time comparison unit 8h determines that the difference between the current system time of the transfer server 8 and the time of the system date and time given to the received data including the first message is more than the predetermined time. If it is determined that there is not, the process proceeds to step S523. On the other hand, if the system time comparison unit 8h determines that the difference between the two times is deviated from the predetermined time, the system time comparison unit 8h proceeds to step S521.

Since the processing from step S517 following step Yes in step S515 to step S530 is the same as the processing from step S17 to step S31 in the first embodiment except for step S513, description thereof will be omitted. .
In step S521 following Yes in step S519, the reception data acquisition path is switched to acquire the reception data, and the process proceeds to step S507. In step S521 (an example of an acquisition path switching step), the acquisition path switching unit 8i switches the acquisition path of received data from the reception-side data holding device 5 to the reception-side data holding device 15.

  In step S507 following step S521, the received data received from the receiving-side data holding device 15 is divided for each message, and the process proceeds to step S509. In step S507, for example, the data acquisition / holding unit 7b provided in the transfer server 8 divides and holds a plurality of normal messages included in the acquired received data for each message.

  In steps S521 to S507, the transfer server 8 operates as follows. For example, the acquisition path switching unit 8i notifies the control unit 8a that the reception data acquisition path is switched. Receiving the notification from the acquisition path switching unit 8i, the control unit 8a transmits an acquisition command for acquiring the reception data from the reception-side data holding device 15 to the data acquisition / holding unit 8b. The data acquisition / holding unit 8b that has received the acquisition command acquires the reception data from the acquisition path connected to the reception-side data holding device 15 instead of the acquisition path connected to the reception-side data holding device 5. Hold. In FIG. 8, the acquisition path on the receiving data holding device 5 side is represented only by a solid line connecting the receiving data holding device 5 and the transfer server 8, and the acquisition path on the receiving data holding device 15 side is The broken line and the solid line connecting the receiving side data holding device 5 and the transfer server 8 are shown.

  If the real-time data transfer system 2 according to the present embodiment determines in step S519 that the difference between the current system time and the assigned system time has deviated from the predetermined time, the reception-side data that is spare The acquisition path is switched to the holding device 15 side. As a result, the real-time data transfer system 2 can quickly recover real-time data transfer.

  The processing after step S509 after the acquisition path is switched is the same as the processing after step S509 before the acquisition path is switched. However, in step S519 after the acquisition path is switched, if it is determined that the difference between the current system time and the assigned system time is more than the predetermined time, the real-time data transfer system 2 performs the data transfer operation. finish. In this case, there is a possibility that some trouble has occurred in either the primary or secondary acquisition path. For this reason, the real-time data transfer system 2 interrupts the data transfer process and notifies the maintenance person of the real-time data transfer system 2 of the abnormality.

As described above, the real-time data transfer system 2 according to the present embodiment can obtain the same effects as the real-time data transfer system 1 according to the first embodiment.
Furthermore, the real-time data transfer system 2 according to the present embodiment can monitor the flow of real-time data based on the date / time information given by the data receiving system and the system time of the transfer server. Thereby, the real-time data transfer system 2 can automatically detect the occurrence of a failure such as a data stack in the communication path between the data receiving system and the transfer server. Further, the real-time data transfer system 2 can prevent or prevent the occurrence of a failure by switching the data acquisition path to a backup path (backup path).

The present invention is not limited to the above embodiment, and various modifications can be made.
In the first embodiment, the deletion message filtering is performed by using only the deletion message or the normal message ID number (see FIG. 4), the deletion message ID number, the normal message ID number, and the date and time information. The method is executed in any one of the methods to be used (see FIG. 6), but the present invention is not limited to this. For example, the real-time data transfer system may be adapted to filter delete messages using both methods.

  In the first embodiment, either one of morphological analysis and language determination is used for language analysis. However, the present invention is not limited to this. For example, the real-time data transfer system may perform language analysis using both morphological analysis and language determination. Thereby, the real-time data transfer system can transmit a message suitable for various applications.

  Further, the transfer server 7 in the first embodiment can execute the processes in steps S511, S513, and S519 shown in FIG. 10 in the second embodiment instead of the processes in steps S11, S13, and S19 shown in FIG. As described above, a system time comparison unit may be provided. Further, the transfer server 8 in the second embodiment executes the processes in steps S11, S13, and S19 shown in FIG. 3 in the first embodiment instead of the processes in steps S511, S513, and S519 shown in FIG. May be.

  The scope of the present invention is not limited to the illustrated and described exemplary embodiments, but includes all embodiments that provide the same effects as those intended by the present invention. Furthermore, the scope of the invention is not limited to the combinations of features of the invention defined by the claims, but can be defined by any desired combination of particular features among all the disclosed features.

1, 2 Real-time data transfer system 3 Data reception system 5 Receiving side data holding device 7, 8 Transfer server 7a, 8a Control unit 7b, 8b Data acquisition / holding unit 7c, 8c Non-real time data filtering unit 7d, 8d Delete message filtering unit 7e, 8e Normal message distribution unit 7f, 8f Normal message output unit 7g, 8g Bus line 8h System time comparison unit 8i Acquisition path switching unit 9 Transmission side data holding device 11 Real-time data transmission system 13 Application group 13-1, 13- 2, 13-n application

Claims (7)

A real-time data transfer method for transferring real-time data received from a real-time data transmission system to an application on the transmission side,
A data receiving step for receiving data including the real-time data transferred to the application from the real-time data transmission system;
A receiving-side data holding step for temporarily holding received data that is the data received in the data receiving step;
A transfer step of transferring the real-time data included in the reception data held in the reception side data holding step to the application side of the transmission side;
A transmission-side data holding step for temporarily holding the real-time data transferred in the transfer step;
A non-real time data filtering step of filtering non-real time data included in the received data and not the real time data;
Deletion for filtering so that a deletion message included in the reception data is not transmitted to the application when a predetermined condition is satisfied when a normal message storing information to be transmitted to the application included in the reception data is deleted A message filtering step;
A normal message sorting step of assigning a tag to the normal message included in the real-time data, and allocating the tagged normal message to the application according to the assigned tag. Transfer method. The real-time data transfer method according to claim 1, wherein, in the data receiving step, a date and time immediately after reception, which is a date and time immediately after receiving the received data, is given to the received data. The non-real time data filtering step includes:
Date and time information reading step for analyzing the received data held in the receiving side data holding step and reading date and time information in the received data;
A date and time comparison step for comparing the date and time included in the date and time information with the system date and time given to the analyzed received data;
In the date and time comparison step, when it is determined that the date and time included in the date and time information and the date and time immediately after reception given to the analyzed reception data are different from each other by a predetermined threshold or more, the analyzed reception The method of claim 2, further comprising: a received data deleting step for deleting data. Another reception side data holding for receiving and temporarily holding real-time data included in the received data and transmitted to the application through an acquisition path different from the reception data acquisition path in the reception side data holding step Steps,
A system time comparison step of comparing the current time with the time of the date and time immediately after reception given to the reception data in the data reception step;
In the system time comparison step, when it is determined that the current time and the time immediately after reception are different from a predetermined time, the reception data acquisition route is stored in the reception data 3. The real-time data transfer method according to claim 2, further comprising: an acquisition path switching step of switching from the acquisition path in the step to the acquisition path in the other receiving side data holding step. The delete message filtering step includes:
An information reading step for reading date and time information and ID information in the received data held in the receiving side data holding step;
An effective period determination step of determining an effective period of the deletion message based on at least one of the read date and time information and the ID information;
5. The real-time data transfer method according to claim 1, further comprising: a filtering step of filtering the deletion message when it is determined that the valid period has been exceeded. . In the normal message distribution step,
A language analysis step of analyzing the normal message of the real-time data included in the received data acquired in the transfer step using language analysis;
A tagging step of adding the tag to the normal message based on an analysis result;
The real-time data transfer method according to claim 1, further comprising: a distribution step of distributing the normal message according to the tag given in the tagging step. A real-time data transfer system for transferring real-time data received from a real-time data transmission system to an application on the transmission side,
A data receiving system for receiving data including the real-time data to be transferred to the application from the real-time data transmitting system;
A receiving-side data holding device that temporarily holds received data that is the data received by the data receiving system;
A transfer server for transferring the real-time data contained in the received data acquired from the receiving-side data holding device to the application side on the transmitting side;
A transmission-side data holding device that temporarily holds the real-time data transferred from the transfer server;
A data filtering unit that filters non-real time data that is included in the received data and is not the real time data;
A deletion message that filters a deletion message included in the data so as not to be transmitted to the application when a predetermined condition is satisfied when a normal message storing information to be transmitted to the application included in the received data is deleted A filtering unit;
A normal message allocating unit that assigns a tag to the normal message included in the real-time data and distributes the tagged normal message to the application according to the assigned tag. Transfer system.

Images