Vehicle monitoring apparatus

Abstract

To provide a vehicle monitoring device capable of extracting vehicle data in a designated period from a database in short time.SOLUTION: A vehicle monitoring device according to one embodiment of the present invention includes a data reception unit, a database, and a control unit. The data reception unit receives vehicle data including information transmitted at a predetermined cycle on a position of a railway vehicle, date and time, and monitoring data of device. The database includes a plurality of table groups capable of storing the vehicle data. The control unit includes a data registration unit. The data registration unit calculates a day of the week from information related to the date and time included in the vehicle data, selects any one table group among the plurality of table groups on the basis of the calculated day of the week, and registers the vehicle data in the selected one table group.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a vehicle monitoring device that monitors a railway vehicle based on vehicle data transmitted from the railway vehicle.

Background Art

[0002] There is known a data analysis system that collects data such as the operating status of railway vehicle equipment and performs data analysis to detect abnormalities, predict abnormalities, etc. (see, for example, Patent Document 1). This type of data analysis system generally includes a receiving unit that receives vehicle data transmitted from a railway vehicle at a predetermined cycle, a database that stores the received vehicle data, and a control device that searches and extracts the vehicle data stored in the database.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a data analysis system for railway vehicles, since the database stores vehicle data at each time transmitted from the railway vehicle to be monitored, it is very difficult to search and extract records (vehicle data) for a specified period from the database storing this huge amount of vehicle data. This problem becomes more prominent as the number of railway vehicles to be monitored increases.

[0005] In view of the above circumstances, an object of the present invention is to provide a vehicle monitoring device capable of extracting vehicle data for a specified period from a database in a short time.

Means for Solving the Problems

[0006] A vehicle monitoring device according to one embodiment of the present invention includes a data receiving unit, a database, and a control unit. The data receiving unit receives vehicle data including information on the position, date and time, and monitoring data of devices of a railway vehicle transmitted at a predetermined cycle. The database has a plurality of table groups capable of storing the vehicle data. The control unit has a data registration unit. The data registration unit calculates the day of the week from the information related to the date and time included in the vehicle data, selects any one of the plurality of table groups based on the calculated day of the week, and registers the vehicle data in the selected one table group.

[0007] By thus distributing and storing individual vehicle data in different table groups according to the day of the week, the search area of the vehicle data is restricted, and thereby the target vehicle data can be extracted in a short time.

[0008] The plurality of table groups may include a first table group that stores vehicle data of a first day-of-week group that is a combination of two or more different non-consecutive days of the week, and a second table group that stores vehicle data of a second day-of-week group that is a combination of two or more different non-consecutive days of the week other than the first day-of-week group.

[0009] The first day-of-week group is a combination of two non-consecutive days of the week, the second day-of-week group is a combination of three non-consecutive days of the week, and the plurality of table groups may further include a third table group that stores vehicle data of a third day-of-week group that is a combination of two days of the week that do not belong to either the first day-of-week group or the second day-of-week group.

[0010] The plurality of table groups may each have a plurality of tables capable of storing the vehicle data in a predetermined time unit for each day of the week.

[0011] The plurality of table groups may execute a process of deleting vehicle data belonging to each day of the week on the day following that day of the week.

[0012] The control unit may further include a data extraction unit that extracts vehicle data at a specified date and time from the database based on a data acquisition instruction. The data extraction unit may calculate the day of the week of the specified date and time, select a corresponding table group from the plurality of table groups based on the calculated day of the week, and extract vehicle data at the specified date and time from the selected table group.

[0013] The control unit may be configured to determine whether the device is faulty based on the monitoring data of the device, and generate the data acquisition instruction when it is determined that the device is faulty.

[0014] When the data acquisition instruction is input, the data extraction unit may extract, from the database, the failure occurrence time related to the device determined to be faulty and the monitoring data for a predetermined time before and after the failure occurrence time.

Advantages of the Invention

[0015] According to the present invention, vehicle data for a specified period can be extracted from a database in a short time.

Brief Description of the Drawings

[0016]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Embodiments for Carrying Out the Invention

[0017] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0018] [System Overview] FIG. 1 is a schematic configuration diagram of a data analysis system 100 including a vehicle monitoring device according to an embodiment of the present invention. This data analysis system 100 analyzes the current position of the railway vehicle 1 and the presence or absence of equipment failures based on the vehicle data transmitted from the railway vehicle 1, and enables the analysis results to be viewed and analyzed on a website from the command post 3 and the vehicle base 4.

[0019] The railway vehicle 1 is a train formation to be monitored in this system, and it does not matter whether it is in operation or not. The number of railway vehicles 1 (formation number) is typically plural, and a plurality of railway vehicles 1 are simultaneously monitored by the vehicle monitoring device 2. Note that the number of railway vehicles 1 to be monitored may be singular.

[0020] The vehicle data transmitted from each railway vehicle 1 includes information regarding the position, date and time, and monitoring data of the equipment of the railway vehicle 1.

[0021] The information regarding the position and date and time is GPS data obtained by a GPS (Global Positioning System) receiver (not shown) equipped on the railway vehicle 1. The monitoring data of the equipment is monitoring data indicating the state of the equipment to be monitored attached to the railway vehicle 1, and includes data regarding all the vehicles forming the railway vehicle 1. The vehicle data further includes identification information including the vehicle type, formation number, train number, type, etc. of the railway vehicle 1.

[0022] Examples of the monitoring data include a speed signal, a control voltage, a straight air pipe pressure, a brake cylinder pressure, a brake pipe pressure, an original air dam pressure, a notch signal, and other equipment operation signals. In addition, monitoring data regarding the state of passenger compartment equipment such as doors and air conditioning / lighting equipment is included.

[0023] The monitoring data of each of these vehicles is collected by the monitoring device 10 and transmitted by the distribution device 11 together with the GPS data. The vehicle data transmitted from each railway vehicle is transmitted to the vehicle monitoring device 2 via, for example, an LTE (Long Term Evolution) network. The transmission cycle is not particularly limited and is 200 ms (milliseconds) in this embodiment.

[0024] The vehicle monitoring device 2 includes a data receiving unit 20 that receives vehicle data transmitted from each railway vehicle 1 at a predetermined cycle (200 ms), a control unit 21 that analyzes the received vehicle data, and a database 22 that stores the received vehicle data.

[0025] The data receiving unit 20 is a receiving device that receives vehicle data including information on the position, date and time, and monitoring data of devices of each railway vehicle 1 transmitted at a predetermined cycle. The database 22 is a data storage device having a plurality of table groups capable of storing vehicle data. The control unit 21 is an information processing device that stores the vehicle data of each railway vehicle 1 received via the data receiving unit 20 in the database 22, and determines the presence or absence of device failure (abnormality) for each railway vehicle 1 based on the monitoring data included in the vehicle data. The control unit 21 further has a function of forming a display screen for displaying a list of current vehicle states and a map screen showing the current positions of the respective railway vehicles 1 based on the received vehicle data.

[0026] The vehicle monitoring device 2 is configured as a cloud server. The command post 3 and the vehicle base 4 can be connected to the vehicle monitoring device 2 via the Internet line, and each includes a client terminal capable of browsing various display screens and map screens formed by the vehicle monitoring device 2.

[0027] [Database] FIG. 2 is a conceptual diagram showing the configuration of the database 22. The database 22 includes a temporary storage database unit 221 in which the vehicle data received by the receiving unit 22 is temporarily stored, a backup database unit 222 in which all vehicle data is stored, and a reference database unit 223 in which reference data to be collated when determining device failure is stored. These database units 221 to 223 are not limited to being constructed in the same database 22 as described above, and may be constructed in separate databases.

[0028] FIG. 3 is a conceptual diagram showing the configuration of the primary storage database unit 221. The temporary storage database unit 221 includes a first table group 31, a second table group 32, and a third table group 33. The vehicle data stored in these plurality of table groups 31 to 33 is determined according to the day of the week calculated based on the information related to the date and time included in the vehicle data. In this embodiment, each day of the week including Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, and Saturday is adopted as the day of the week.

[0029] For example, the first table group 31 stores vehicle data of a first day-of-week group that is a combination of two or more different non-consecutive days of the week. The second table group 32 stores vehicle data of a second day-of-week group that is a combination of two or more different non-consecutive days of the week and is a day of the week other than the first day-of-week group.

[0030] More specifically, the first day-of-week group is a combination of two non-consecutive days of the week, for example, Sunday and Wednesday. The second day-of-week group is a combination of three non-consecutive days of the week, for example, Monday, Thursday, and Saturday. In this case, the third table group 33 is configured to store vehicle data for Tuesday and Friday, which are combinations of two days of the week that do not belong to either the first day-of-week group or the second day-of-week group.

[0031] As shown in FIG. 3, the first to third table groups 31 to 33 each have a plurality of time tables T0, T1, ···, Tn that can store the vehicle data in predetermined time units for each day of the week. In this embodiment, it is configured to temporarily store vehicle data for one hour. In this case, the number of time tables is 24. The time table T0 can store vehicle data for the 0:00 am hour, the time table T1 can store vehicle data for the 1:00 am hour, and the time table T23 (n = 23) can store vehicle data for the 11:00 pm (23:00) hour.

[0032] Note that the first to third table groups 31 to 33 are configured to execute a process of deleting vehicle data belonging to each day of the week on the day following that day of the week. For example, the vehicle data for Sunday stored in the first table group 31 is saved in the backup database unit 222 on Monday, the day following Sunday, and then deleted from the first table group 31. The timing of deletion is not particularly limited, and in this embodiment, it is set to a predetermined time on the day following (for example, 2:00 am).

[0033] [Control Unit] Next, the control unit 21 will be described. The control unit 21 can be realized by hardware elements used in a computer such as a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and necessary software. The control unit 21 controls the overall operation of the vehicle monitoring device 2.

[0034] FIG. 4 is a functional block diagram showing the configuration of the control unit 21. As shown in FIG. 4, the control unit 21 includes a data registration unit 41, a data extraction unit 42, a failure determination unit 43, a display image formation unit 44, a map image formation unit 45, and a position correction unit 46. Note that the map image formation unit 45 and the position correction unit 46 may be configured by the same functional block.

[0035] (Data Registration Unit) The data registration unit 41 calculates the day of the week from the information related to the date and time included in the vehicle data, selects any one of the first to third table groups 31 to 33 based on the calculated day of the week, and is configured to register the vehicle data in the selected one table group.

[0036] FIG. 5 is a flowchart showing an example of the processing procedure executed in the data registration unit 41.

[0037] The data registration unit 41 acquires the date and time from the vehicle data received via the data reception unit 20 (ST101). The information related to the date and time of the vehicle data is acquired from the GPS data included in the vehicle data. The information related to the date and time includes the date (year, month, and day) of the transmission date of the vehicle data and the time information every 200 milliseconds based on the transmission time.

[0038] Subsequently, the data registration unit 41 acquires the time information from the acquired date and time (ST102), and calculates the day of the week from the acquired date (ST103). In the present embodiment, for example, the day of the week is calculated using Zeller's formula.

[0039] Subsequently, the data registration unit 41 determines whether the calculated day of the week is Sunday or Wednesday (ST104). If the calculated day of the week is Sunday or Wednesday, it selects the first table group 31 as the registration destination for the vehicle data (ST106). If the calculated day of the week is other than Sunday or Wednesday, it determines whether the day of the week is Monday, Thursday, or Saturday (ST105).

[0040] And if the calculated day of the week is Monday, Thursday, or Saturday, the data registration unit 41 selects the second table group 32 as the registration destination for the vehicle data (ST107). If the day of the week is Tuesday or Friday, it selects the third table group 33 as the registration destination for the vehicle data (ST108).

[0041] Subsequently, the data registration unit 41 registers the vehicle data in the time table corresponding to the time information acquired in ST102 among the time tables T0 to T23 in the selected table groups 31 to 33 (ST109).

[0042] The above processing is repeatedly executed for each received vehicle data. Also, in the time tables T0 to T23 of each table group 31 to 33, vehicle information of a plurality of railway vehicles 1 with different formations is commonly stored.

[0043] (Data extraction unit) The data extraction unit 42 is configured to extract vehicle data of a specified date and time from the database based on a data acquisition instruction.

[0044] The data acquisition instruction is generated by a failure determination unit 43 described later. The data extraction unit 42 calculates the day of the week from the specified date and time based on the data acquisition instruction, selects the table groups 31 to 33 corresponding to the day of the week from the temporary storage database unit 221, and extracts the vehicle data of the corresponding time from the tables T0 to T23 (Figure 3) of the selected table groups. Since the vehicle data is thus distributed to the database groups 31 to 33 according to the day of the week, the vehicle data of the specified date and time can be extracted from the database 22 in a short time.

[0045] FIG. 6 is a flowchart showing an example of a processing procedure executed in the data extraction unit 42.

[0046] When a data acquisition instruction is input (ST201), the data extraction unit 42 acquires the time of the acquired vehicle data (ST202) and calculates the day of the week of the specified date (ST203). Also in this case, the day of the week is calculated using Zeller's formula.

[0047] Subsequently, the data extraction unit 42 determines whether the calculated day of the week is Sunday or Wednesday (ST204). If the calculated day of the week is Sunday or Wednesday, the first table group 31 is selected as the extraction destination of the vehicle data (ST206). If the calculated day of the week is a day other than Sunday or Wednesday, it is determined whether the day of the week is Monday, Thursday, or Saturday (ST205).

[0048] Then, when the calculated day of the week is Monday, Thursday, or Saturday, the data extraction unit 42 selects the second table group 32 as the extraction destination of the vehicle data (ST207). When the day of the week is Tuesday or Friday, the data extraction unit 42 selects the third table group 33 as the extraction destination of the vehicle data (ST208).

[0049] Subsequently, the data extraction unit 42 extracts the acquired vehicle data from the time table corresponding to the time information acquired in ST202 among the respective time tables T0 to T23 in the selected table groups 31 to 33 (ST209).

[0050] When a data acquisition instruction is input, the data extraction unit 42 extracts the failure occurrence time related to the device determined to be faulty and the monitoring data for a predetermined time before and after that from the database 22 (temporary storage database unit 221).

[0051] By extracting not only the monitoring data at the time of failure but also the monitoring data within a predetermined time before and after it, the time change of the monitoring data can be grasped. The above-mentioned predetermined time can be arbitrarily set, for example, it is 1 minute. In this case, after the predetermined time has elapsed since the data acquisition instruction was input, the data extraction unit 42 executes the above-described data extraction process.

[0052] (Failure determination unit) The failure determination unit 43 is configured to determine the presence or absence of failure of each device based on the monitoring data of each device included in the received vehicle data, and generate the above data acquisition instruction when it is determined that the device has failed.

[0053] The method for determining the presence or absence of failure is not particularly limited. For example, when the difference when compared with the monitoring data of the same formation vehicle obtained last time is a predetermined value or more, it is determined as a failure (or abnormality). As the monitoring data obtained last time, it may be the same monitoring data obtained immediately before, or may be the average value of the same monitoring data for a predetermined period up to immediately before.

[0054] Alternatively, the failure determination unit 43 may determine the failure of the device based on the information indicating the presence or absence of abnormality in the monitoring data transmitted from the railway vehicle 1. In this case, the presence or absence of abnormality of the device is determined in the monitor device 10 of the railway vehicle 1 that collects the monitoring data, and the determination result is linked to the monitoring data and transmitted from the distribution device 11.

[0055] Alternatively, a threshold value indicating the abnormality of the monitoring data may be set in advance for each device, and when the received monitoring data exceeds the threshold value, it may be determined that the device has failed. The threshold value may be stored, for example, in the reference database unit 223 (FIG. 2) of the database 22.

[0056] When there is a railway vehicle 1 that cannot receive vehicle data, the failure determination unit 43 determines that there is a communication failure for that railway vehicle 1. When the failure determination unit 43 determines a communication failure, it does not generate a data acquisition instruction, but is not limited to this, and may also generate a data acquisition instruction when determining a communication failure.

[0057] The data acquisition instruction generated by the failure determination unit 43 is input to the data extraction unit 42. When the data acquisition instruction is input, the data extraction unit 42 is configured to extract, from the same time tables T0 to T23, not only the monitoring data of the device determined to have failed but also the monitoring data for a predetermined time before and after the occurrence time of the failure related to other devices related to the device. By extracting the monitoring data not only for the device determined to have failed but also for other related devices, it becomes easier to identify the cause of the failure.

[0058] The above other devices are not limited to a single one and may be plural. For example, when the monitoring data regarding the straight air pipe pressure is determined to be abnormal, other related monitoring data such as the brake cylinder pressure, brake pipe pressure, and original air dam pressure is also extracted. Such combinations of highly related monitoring data may be stored in advance in the reference database section 223 (Figure 2) of the database 22 for each individual monitoring data.

[0059] The failure determination unit 43 stores the latest information of the monitoring data for which the presence or absence of a failure has been determined in the reference database 223. Also, the failure determination unit 43 registers the device determined to be abnormal and its monitoring data in the reference database section 223 (failure registration). Furthermore, when the failure determination unit 43 determines that the monitoring data of a device that was determined to be abnormal in the past has returned to a normal value, it considers that the failure of the device has been resolved and cancels the failure registration (cancellation registration).

[0060] (Display Image Formation Unit) The display image formation unit 44 is configured to form a list display image (first display image) that displays in a list the formation information of each railway vehicle 1 and the vehicle state regarding the presence or absence of a failure based on the vehicle data transmitted from a plurality of railway vehicles 1.

[0061] FIG. 7 is a diagram showing an example of the list display image V1. The display image forming unit 44 forms the list display image V1 shown in FIG. 7 based on the latest monitoring data of each device stored in the reference database unit 223. The list display image V1 is generated as an image file that can be browsed by the user at the command post 3 or the vehicle base 4.

[0062] The list display image V1 displays the vehicle states of all formations (railway vehicle 1) to be monitored. Examples of the vehicle states include the presence or absence of a failure, an icon for switching the display of detailed information, the current position, the vehicle type, the formation number, the state (the presence or absence of a failure and its details), the train number, the type, the destination, the rear station, the distance in kilometers, the speed, the notch, etc., and the display items can be arbitrarily set. Here, the formation including the monitoring data determined to be a failure is displayed at the top, and the formation determined to have a communication failure is displayed at the bottom.

[0063] The list display image V1 is updated with the latest information, for example, in units of several seconds, several tens of seconds, or several minutes. Thereby, the vehicle information of all formations can be presented in real time.

[0064] In this way, since the latest information is presented not only for a specific formation but also for all formations, an abnormal formation can be quickly grasped and identified. Also, by clicking the icon V11 displayed on the list display screen V1, it is configured to be possible to switch and display the history of the state of the formation determined to have a failure, the detailed information of each formation, and the current position on a separate screen.

[0065] The display image forming unit 44 forms a failure history image V2 of the formation (formation number 0999) determined to have a failure, as shown in FIG. 8, for example. The failure history image V2 is generated as an image file that can be browsed by the user at the command post 3 or the vehicle base 4.

[0066] In the failure history image V2, the history of failures and releases of the formation is displayed in chronological order (with the latest information on top) based on the failure registration and cancellation registration stored in the reference database unit 223. The display items include graphs of the monitored data at the time of failure occurrence / cancellation, failure occurrence / cancellation, train type, formation number, occurrence / cancellation date and time, failed equipment, failure name, vehicle with failure occurrence, vehicle with failure cancellation, etc. For the vehicle with failure occurrence / cancellation, the corresponding vehicle number is displayed in a manner different from other vehicle numbers (for example, highlighted).

[0067] The graph of the monitored data at the time of failure occurrence / cancellation means the time change of the monitored data of the equipment for which failure registration or cancellation registration has been performed in the failure determination unit 43. By clicking on the icon V21 displayed in each history, the screen can be switched to a graph image (second display image) that displays the time change of the monitored data for one minute before and after the failure occurrence / cancellation time as shown in, for example, FIG. 9.

[0068] The display image forming unit 44 forms a graph image V3 as shown in FIG. 9 for each history item shown in FIG. 8. The graph image V3 shows the time change of the monitored data for a predetermined time (one minute in this embodiment) before and after the failure occurrence / failure cancellation time when the failure occurrence / failure cancellation time is set to 0 seconds. The monitored data includes the monitored data of the equipment for which failure determination (or its cancellation) has been made by the data extraction unit 42 based on a data acquisition instruction, and the failure occurrence (or its cancellation) time of other equipment related to the said equipment and the monitored data for a predetermined time before and after that. The graph image V3 is generated as an image file that can be browsed by the user at the command post 3 or the vehicle base 4.

[0069] The graph image V3 shows time (seconds) on the horizontal axis and the type of sensor and its state value on the vertical axis. The graph image V3 simultaneously displays digital data S1 and analog data S2. Examples of the digital data S1 include the ON / OFF of the emergency brake and the standby brake, and it may be displayed for each vehicle. Examples of the analog data S2 include speed, notch (step number display), brake cylinder pressure, brake pipe pressure, etc.

[0070] Further, when there is a missing part in the time series of the vehicle data of the formation, the display screen forming unit 44 is configured to superimpose and display a data missing part Vd, which is an image indicating the period corresponding to the missing part, on the graph image V3.

[0071] The data missing part Vd is for warning the user that the state during the period is not based on the vehicle data. This avoids an incorrect determination of the failure location, and thus the reliability of the display data can be ensured. Note that the monitoring data corresponding to the data missing period is held at a predetermined value (OFF in the case of digital data, 0 in the case of analog data, and notch off (N) in the case of a notch signal). Note that this is not limited thereto, and the display of the monitoring data may be omitted during the data missing period.

[0072] According to the present embodiment, by displaying the failure occurrence time and the monitoring data for a predetermined time before and after it on the graph image V3, the time course of the device related to the failure can be grasped. Further, since the time changes of the monitoring data of a plurality of related devices are also displayed simultaneously, the information necessary for specifying the failure location and analyzing the cause of the failure can be presented. Such information is particularly useful for the operator at the vehicle base 4, and the repair preparation for the failure of the formation can be efficiently performed. Note that the number and type of the monitoring data to be displayed can be arbitrarily selected by the user's input operation, and thus the user's requirements can be flexibly met.

[0073] (Map image forming unit, position correcting unit) The map image forming unit 45 is configured to form a map image in which the position of the railway vehicle 1 to be monitored is superimposed on map data including the line on which the railway vehicle 1 to be monitored travels.

[0074] The line on which the railway vehicle 1 to be monitored travels refers to the individual business lines on which the individual railway vehicles 1 travel. When the travel line differs depending on the destination, the line is specified according to the formation number etc. of the railway vehicle 1. The line data and map data of the above line are stored in, for example, the reference database unit 223.

[0075] For the track data, for example, open data provided as positioning data from the Ministry of Land, Infrastructure, Transport and Tourism is used. The track data is not a single line, but a collection of multiple straight lines (two points). Also, the position of the railway vehicle 1 is calculated based on the GPS information (latitude and longitude information) included in the vehicle data transmitted from the railway vehicle 1.

[0076] Here, the latitude and longitude of GPS may calculate incorrect position information due to factors such as the sensitivity of the in-vehicle antenna, the number of satellites captured by the GPS unit, and the reflection of radio waves due to the surrounding environment, and the vehicle may appear to be in a location where it actually does not exist.

[0077] For example, FIG. 10(A) shows an example of a map image when the position of the vehicle calculated based on the GPS information is actually superimposed and displayed on the map data. In this map image V4, P indicates the current position of the vehicle. However, although the track on which the vehicle actually travels is R1, as a result of being calculated based on incorrect position information, the position P of the vehicle displayed on the map may be displayed at a position between the track R1 and another adjacent track R2.

[0078] Therefore, in this embodiment, it has a position correction unit 46 that corrects the vehicle position on the track data plotted on the map. The position correction unit 46 determines whether the railway vehicle 1 is located on the track based on the information related to the position included in the vehicle data and the track data. When it is determined that the railway vehicle 1 is not located on the track, the map image is configured to correct the vehicle position displayed on the map data so that it is located on the track.

[0079] As a result, as shown in the map image V5 in FIG. 10(B), the current position P of the vehicle can be correctly displayed on the track R1, so that the current vehicle position can be provided to the user without causing confusion or misunderstanding.

[0080] The position correction unit 46 is configured to correct the map image so that the railway vehicle 1 is located at a position on the nearest track R1 from the position of the railway vehicle 1 (FIG. 10(B)). The map image V5 is generated as an image file that can be browsed by a user at the command post 3 or the vehicle base 4.

[0081] The calculation of the nearest can be performed, for example, according to the following procedure. First, since the track data is composed of a group of straight lines of different sizes, a line is drawn from the current position of the vehicle to the intermediate points of each straight line in the group of straight lines, and the one with the shortest distance is selected as the nearest section. Next, a point orthogonal to the nearest section from the current position of the vehicle is estimated as the nearest point, and the current position of the vehicle is set to this nearest point.

[0082] To calculate the distance between two points, a value considering the curvature and distortion of the earth is calculated using the Haversine formula. The Haversine formula is an equation for approximating the earth as an ellipsoid and obtaining the distance and azimuth between two points. Since the Haversine formula is well-known, its description is omitted here.

[0083] In the calculation, the unit of the positioning information is converted to radians. Latitude is expressed in the range from 0 to 90 degrees north from the equator and from 0 to 90 degrees south. North latitude is a positive value, and south latitude is a negative value. For example, since the latitude of Tokyo is about 35.6895 degrees north, when converted to radians, it is as follows. Radian = (π / 180)×35.6895 ≈ 0.6228 radian

[0084] Longitude is expressed in the range from 0 to 180 degrees east or from 0 to 180 degrees west from the prime meridian (usually the Greenwich meridian). East longitude is a positive value, and west longitude is a negative value. For example, since the longitude of Tokyo is about 139.6917 degrees east, when converted to radians, it is as follows. Radian = (π / 180)×139.6917 ≈ 2.4395 radian

[0085] Furthermore, since the difference information of GPS and the track information have different positioning units, it is necessary to align these units. To accurately place the corrected vehicle position on the map, for example, the latitude and longitude obtained by converting the calculation result of the distance between two points into the World Geodetic System decimal notation may be used.

[0086] Furthermore, in the present embodiment, when the position correction unit 46 determines that the railway vehicle 1 is located within a predetermined area (correction exclusion area), it is configured to execute a process of not correcting the map image.

[0087] For example, a vehicle in a vehicle base or a siding is not in commercial operation. If this vehicle is corrected and drawn on the track, there is a risk of causing confusion as if it is on the track when it is not in commercial operation.

[0088] Therefore, in the present embodiment, as shown in the map image V6 of FIG. 10(C), a predetermined area where the vehicle base and the siding are located is set as a correction exclusion area A, and when the current position of the vehicle is located within the correction exclusion area A, the correction process of the vehicle position onto the track is not executed. As a result, since a vehicle that is not in commercial operation is not drawn on the track, it is possible to prevent causing confusion to the user.

[0089] The correction exclusion area A is stored in, for example, the reference database unit 223. The map image V6 is generated as an image file that can be browsed by the user at the command post 3 or the vehicle base 4.

[0090] To determine whether the current position of the vehicle is within the correction exclusion area A, the map is treated as a two-dimensional graph, and "the inside / outside determination of point P with respect to the polygon T" is performed using the correction exclusion area A displayed as the polygon T and the vehicle position (P). Known methods can be adopted for this determination algorithm, and for example, the Crossing Number Algolithm, the Winding Number Algolithm, etc. can be adopted.

[0091] FIG. 11 is a flowchart showing an example of a processing procedure executed in the map image forming unit 45 and the position correction unit 46.

[0092] The map image forming unit 45 acquires the track data of the track R1 from the reference database unit 223 (ST301), and acquires the position information from the vehicle data transmitted from the railway vehicle 1 (ST302). The track R1 is the track on which the railway vehicle 1 to be displayed on the map travels, and is specified by the formation number of the vehicle as described above.

[0093] Subsequently, the position correction unit 46 determines whether the vehicle position is outside the correction exclusion area A from the acquired position information (ST303). When the vehicle position is outside the correction exclusion area A, it is determined whether the vehicle position is on the track R1 (ST304). When the vehicle position is not on the track R1, the position (nearest point) on the nearest track R1 is calculated from the vehicle position by the method as described above (ST305), and the vehicle position is corrected to the calculated nearest point (ST306).

[0094] The map image forming unit 45 forms a map image in which the vehicle position is corrected by the position correction unit 46 (ST307). On the other hand, when the vehicle position is within the correction exclusion area A (No in ST303), or when the vehicle position is on the track R1 (Yes in ST304), the map image forming unit 45 forms a map image in which the vehicle position before correction is superimposed on the map data (ST307).

[0095] [Operation] Subsequently, a typical operation of the vehicle monitoring device 2 of the present embodiment configured as described above will be described. FIG. 12 is a diagram showing an example of a processing procedure executed in the vehicle monitoring device 2.

[0096] The vehicle monitoring device 2 receives vehicle data from all railway vehicles 1 to be monitored by the data receiving unit (ST401).

[0097] Subsequently, the vehicle monitoring device 2 registers the received vehicle data in the database 22. At this time, it is stored in the time tables T0 to T23 of the table groups 31 to 33 sorted according to the day of the week and time calculated from the date of the vehicle data as described above. By thus sorting and storing the individual vehicle data in different table groups according to the day of the week, the search area of the vehicle data is restricted, and thereby the target vehicle data can be extracted in a short time. Also, for the failure analysis of railway vehicles, it is sufficient to have the monitoring data for the previous day, so at least three table groups for storing the vehicle data are sufficient.

[0098] Subsequently, based on the monitoring data of the devices included in the received vehicle data, the vehicle monitoring device 2 determines the presence or absence of a failure of the device, and the monitoring data determined to be a failure is registered as a failure in the reference database unit 223 (ST403).

[0099] Subsequently, the vehicle monitoring device 2 forms a list display image V1 showing the vehicle state of each vehicle, a failure history image V2, a graph image V3 showing the time change of the failed device, and a map image showing the vehicle position (ST404). Since these images are generated as image files that can be browsed by the user at the command post 3 or the vehicle base 4, the state and current position of the devices of each vehicle can be grasped in real time, and it is possible to perform analysis of the failure data and preparatory work for repair before the vehicle with the failure location arrives at the vehicle base.

[0100] As described above, the embodiments of the present invention have been described, but the present invention is not limited only to the above-described embodiments, and it goes without saying that various modifications can be made.

[0101] For example, in the above embodiments, three table groups for storing vehicle data are used, but it may be constructed with seven different table groups for each day of the week. Also, the days of the week are not limited to the seven days of the week, and may be the six days of the week (Sensho, Tomohiki, Sefu, Butsumetsu, Taian, Akaguchi). In this case, a storage table for vehicle data can be constructed with two table groups.

Explanation of Reference Numerals

[0102] 1… Railway vehicle 2… Vehicle monitoring device 3… Command post 4… Vehicle base 10… Monitor device 11… Distribution device 20… Data receiving unit 21… Control unit 22… Database 31… First table group 32… Second table group 33… Third table group 41… Data registration unit 42… Data extraction unit 43… Fault determination unit 44… Display image formation unit 45… Map image formation unit 46… Position correction unit 100… Data analysis system 221… Temporary storage database section 222… Backup database section 223… Reference database section

Claims

1. a data receiving unit that receives vehicle data including information regarding the position of the railway vehicle, date and time, and equipment monitoring data transmitted at a predetermined interval; a database having a plurality of tables capable of storing the vehicle data; a control unit having a data registration unit that calculates a day of the week from information related to the date and time included in the vehicle data, selects one of the plurality of table groups based on the calculated day of the week, and registers the vehicle data in the one selected table group; A vehicle monitoring device comprising:

2. 2. The vehicle monitoring device according to claim 1, The plurality of table groups include: a first table group storing vehicle data for a first group of days of the week, the first group being a combination of two or more different non-consecutive days of the week; a second table group for storing vehicle data for a second group of days of the week that is a combination of two or more different non-consecutive days of the week other than the first group of days of the week; Vehicle monitoring device.

3. 3. The vehicle monitoring device according to claim 2, the first group of days of the week is a combination of two non-consecutive days of the week, the second group of days is a combination of three non-consecutive days of the week; The plurality of table groups further includes a third table group that stores vehicle data for a third group of days of the week that is a combination of two days of the week that do not belong to either the first group of days of the week or the second group of days of the week. Vehicle monitoring device.

4. 2. The vehicle monitoring device according to claim 1, The plurality of table groups each include a plurality of tables capable of storing the vehicle data for each day of the week in a predetermined time unit. Vehicle monitoring device.

5. 2. The vehicle monitoring device according to claim 1, The plurality of table groups executes a process of erasing vehicle data belonging to each day of the week on the day following the day of the week. Vehicle monitoring device.

6. 2. The vehicle monitoring device according to claim 1, The control unit further includes a data extraction unit that extracts vehicle data for a specified date and time from the database based on a data acquisition instruction, The data extraction unit calculates the day of the week of the specified date and time, selects a corresponding table group from the plurality of table groups based on the calculated day of the week, and extracts vehicle data of the specified date and time from the selected table group. Vehicle monitoring device.

7. 7. The vehicle monitoring device according to claim 6, The control unit further includes a failure determination unit that determines whether or not the device is malfunctioning based on monitoring data of the device, and generates the data acquisition instruction when it determines that the device is malfunctioning. Vehicle monitoring device.

8. The vehicle monitoring device according to claim 7, When the data acquisition instruction is input, the data extraction unit extracts from the database monitoring data relating to the equipment determined to be in a fault, the monitoring data including the time of the fault occurrence and a predetermined period of time before and after the fault occurrence. Vehicle monitoring device.

Images