Driving condition monitoring device

Abstract

To provide an operation status monitoring apparatus enabling reflection of a reliable operation method by accurately estimating the content of operation manipulation corresponding to a vehicle position.SOLUTION: One of representative operation status monitoring apparatuses of the present invention is an operation status monitoring apparatus presenting the relationship between a vehicle position of a vehicle travelling on a rail and the content of operation manipulation of the vehicle, the apparatus comprising a sound collection unit that collects manipulation sound of a master controller handle, and estimating the content of operation manipulation on the basis of the manipulation sound of the master controller handle collected by the sound collection unit.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a driving condition monitoring device. [Background technology]

[0002] There is a variability in the driving skills of train drivers when they run on tracks. This causes a variability in the amount of power consumed by trains when running between stations, even when the trains are running between the same stations at the same time, based on the running speed pattern between stations (hereinafter referred to as "running pattern"). However, if we can reduce the variation in driving patterns based on the driver's driving technique and standardize the driving patterns of all trains to energy-efficient patterns, it will be possible to make railway operations more energy-efficient.

[0003] One measure to reduce variations in driving patterns is to provide driver training in which drivers review their driving patterns after each trip. In this driver training, for example, driving patterns during operation are stored in the device, and the driver can then visualize the driving patterns during their free time and review them along with data on driving operations and power consumption, which can be used to improve their own driving operations. Here, in order to store the train running patterns, it is necessary to input the vehicle position and vehicle speed.

[0004] Conventionally, to obtain vehicle position and vehicle speed, particularly to obtain highly accurate vehicle position and vehicle speed that can be used for driver training, it was necessary to obtain the information from the train's vehicle information device. However, obtaining this information from a vehicle information device requires modifying the vehicle information device itself to be able to obtain highly accurate vehicle position and speed. Furthermore, there is the problem that this is difficult to achieve for vehicles that do not have or cannot be equipped with a vehicle information device.

[0005] One method for obtaining this information without obtaining highly accurate vehicle position and vehicle speed from a vehicle information device is to bring a mobile terminal equipped with a GPS receiving function into the vehicle, calculate the vehicle position from the latitude and longitude information obtained by the GPS receiving function, and also utilize the vehicle speed that can be obtained from the GPS receiving function.

[0006] When reviewing driving patterns, it is important to understand driving operations according to vehicle position in addition to information on vehicle speed according to vehicle position, because for the driver, vehicle speed is ultimately the result of driving operations, and the input information that causes changes in vehicle speed is driving operations.

[0007] One method for estimating the content of driving operations using a configuration independent of the vehicle information device is to calculate vehicle acceleration by differential calculation of the vehicle speed obtained from a GPS receiver, and to estimate the driving operation from the estimated driving force required to generate that acceleration. Patent Document 1 discloses a technology for providing driving assistance using a GPS receiver, and describes that the performance of notch operation, which is one of the driving input devices, is estimated from the vehicle speed. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-247247 Summary of the Invention [Problem to be solved by the invention]

[0009] However, the accuracy of vehicle speed obtained from a GPS receiver varies depending on the reception status of radio waves from GPS satellites, and therefore is not necessarily accurate enough for reviewing driving methods. The influence of such dependence on the reception status of radio waves from GPS satellites on a driving condition monitoring device is not considered even in Patent Document 1. Therefore, an object of the present invention is to provide a driving situation monitoring device that enables a driver to review his or her driving method by estimating the content of driving operations corresponding to the vehicle position. [Means for solving the problem]

[0010] In order to solve the above problems, one of the representative driving situation monitoring devices of the present invention is a driving situation monitoring device that presents the relationship between the vehicle position of a vehicle running on a track and the driving operation content of the vehicle, and is characterized by having a sound collection unit that collects the operation sound of the master controller handle, and estimating the driving operation content based on the operation sound of the master controller handle collected by the sound collection unit. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide a driving situation monitoring device that enables a driver to review his or her driving method by estimating the details of the driving operation corresponding to the vehicle position. Problems, configurations, and effects other than those described above will become apparent from the following description of the preferred embodiments. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram showing an example of the configuration of a driving condition monitoring device according to a first embodiment. [Figure 2] FIG. 10 is a diagram showing an example of the relationship between the type of railway vehicle and the number of notches in the master controller handle. [Figure 3] FIG. 10 is a diagram showing an example of the relationship between the notch position and the driving force corresponding to the speed. [Figure 4] FIG. 10 is a diagram showing an example of a notch opening state estimation result. [Figure 5] FIG. 10 is a diagram showing an example of visualization of driving operation history. [Figure 6] FIG. 10 is a diagram showing an example of a flowchart of processing executed by a notch opening state estimating unit. [Figure 7] FIG. 10 is a diagram showing an example of a flowchart of processing executed by a notch opening state estimating unit. [Figure 8]FIG. 10 is a diagram showing the relationship between the master controller handle operation time and the number of sounds. [Figure 9] FIG. 10 is a diagram showing an example of estimation of notch position candidates for missed detection of master controller handle operation sound. [Figure 10] FIG. 10 is a diagram showing an example of the configuration of a driving condition monitoring device according to a second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, with reference to the drawings, a first embodiment and a second embodiment will be described as modes for carrying out the present invention. Note that the present invention is not limited to these embodiments. In addition, in the drawings, the same parts are denoted by the same reference numerals. When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. When there is no need to distinguish between these multiple components, the subscripts may be omitted. In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0014] [First embodiment] First, the first embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating an example of the configuration of a driving condition monitoring device 10 according to an embodiment of the present disclosure. The driving status monitoring device 10 visualizes the running pattern between stations in railway vehicles based on the vehicle position and vehicle speed estimated using GPS, allowing the driver to review their driving operations. The railway vehicle whose running pattern is visualized by the driving situation monitoring device 10 is operated by operating a master controller handle, which is a general input device for driving operations on railways. Here, "mascon" is an abbreviation for "master controller", which is a device installed on the driver's cab of a railway vehicle and operated by the driver to control the speed. The mascon is also called the main controller. The mascon controls the acceleration and deceleration of the railway vehicle. The mascon determines the command state for controlling the acceleration and deceleration of the railway vehicle based on the position of the mascon handle. The mascon in this embodiment determines the command state based on the notch input state of the mascon handle, but it may be determined otherwise. For example, it may be determined based only on the position of the mascon handle. In this embodiment, the driving situation monitoring device 10 is a tablet terminal having a Global Positioning System (GPS) function as satellite positioning information, but other hardware may also be used.

[0015] The driving situation monitoring device 10 mainly includes a GPS receiving unit 101, a on-track position estimating unit 102, a vehicle speed estimating unit 103, an operation unit 104, a route information management unit 105, a notch input state estimating unit 106, a sound collecting unit 107, a characteristic sound detecting unit 108, a driving operation history accumulating unit 109, and a driving operation history transmitting unit 110.

[0016] <GPS receiving unit> Based on the received GPS signals, the GPS receiving unit 101 generates latitude and longitude 151 at a predetermined time period and transmits them to the on-track position estimating unit 102. The GPS receiving unit 101 is also referred to as a satellite positioning information receiving unit that receives satellite positioning information. In this embodiment, GPS signals received from the Global Positioning System (GPS) are used as satellite positioning information, but positioning information from other satellite positioning systems may be used as long as the position of the railway vehicle can be measured.

[0017] The time period of the latitude and longitude 151 generated by the GPS receiving unit 101 is set in consideration of the driver's review of driving operations through visualization of the driving pattern.

[0018] For example, if the time period is too short, the visualized driving pattern may contain vibration components that do not exist in the actual vehicle speed due to the influence of positional variations caused by the accuracy limits of GPS. For example, if the time period is too long, the visualized driving pattern will have poor reproducibility of changes in vehicle speed, making it difficult for the driver to review his driving operations.

[0019] The time period of the latitude and longitude 151 is set taking into consideration a period that is not affected by such factors.

[0020] <Orbital position estimation section> The on-track position estimation unit 102 estimates the on-track position 152 by calculation based on the latitude and longitude 151 received from the GPS receiving unit 101 and the track shape 154 received from the route information management unit 105 . The on-track position estimation unit 102 transmits the estimated on-track position 152 to the vehicle speed estimation unit 103 , the route information management unit 105 , the notch engagement state estimation unit 106 and the driving operation history accumulation unit 109 .

[0021] Here, the track shape 154 is a representation of the shape of the track on which the vehicle is running, expressed as point sequence data. Each point in the sequence of points is associated with a value representing latitude, longitude, and absolute position along the orbit. A typical example of a value representing absolute position along the orbit is kilometers (hereinafter, this parameter will be referred to as "kilometers").

[0022] For example, in car navigation systems, a technology is generally implemented that maps the position of a moving vehicle along a predetermined route based on the latitude and longitude of the moving vehicle obtained by GPS. On the other hand, the on-track position estimation unit 102 compares the data of the track shape 154 with the latitude and longitude 151 to estimate the on-track position 152 corresponding to the latitude and longitude 151, so that the technology of this car navigation system can be applied.

[0023] <Vehicle speed estimation unit> The vehicle speed estimation unit 103 estimates an estimated speed 153 by calculation based on the on-track position 152 received from the on-track position estimation unit 102 . In this embodiment, the vehicle speed estimation unit 103 calculates the estimated speed 153 by, for example, dividing the difference between the on-track positions 152 of adjacent periods by the time for one period. The vehicle speed estimation unit 103 transmits the estimated speed 153 to the notch engagement state estimation unit 106 and the driving operation history accumulation unit 109 .

[0024] The vehicle speed estimation unit 103 may estimate the estimated speed 153 by a method other than calculation. For example, the estimated speed 153 may be obtained directly from the GPS 101 receiving unit.

[0025] <Operation section> The operation unit 104 receives route information 155 input by the driver's operation. The operation unit 104 transmits the received route information 155 to the route information management unit 105. In this embodiment, the operation unit 104 is a touch panel of the driving situation monitoring device 10, which is a tablet terminal, but may be other hardware as long as it can accept inputs from the driver's operations.

[0026] The route information 155 includes, for example, the current station, the destination station, the train type, and the train number, but other information may be added.

[0027] <Route information management department> The path information management unit 105 receives the path information 155 from the operation unit 104 and the on-orbit position 152 from the on-orbit position estimation unit 102 . The track information management unit 105 transmits the track shape 154 to the on-track position estimation unit 102. The track information management unit 105 also transmits the running distance between stations 156 to the notch closing state estimation unit 106. The route information management unit 105 stores, as a database, route shape data of the route on which the railroad vehicle runs. Here, the track shape 154 is, as described above, a representation of the shape of the track on which the vehicle is traveling, using point sequence data.

[0028] In order to improve the efficiency of the search process for the on-track position 152 in the on-track position estimation unit 102, the route information management unit 105 transmits the track shape 154 to the on-track position estimation unit 102, limited to data on sections where the vehicle is likely to travel based on the route information 155.

[0029] The running distance 156 is information about the distance between stations where the vehicle is currently traveling. The running distance 156 is determined based on the train number included in the received route information 155, the timetable information stored in advance in the route information management unit 105, the current time, and the received on-track position 152. The reason why the distance between stations 156 includes the received on-track position 152 is to prepare for the case where a delay occurs and the appropriate distance between stations 156 cannot be extracted by comparing the timetable information with the current time.

[0030] <Notch insertion state estimation unit> Next, the notch opening state estimating unit 106 will be described with reference to FIGS. FIG. 2 is a diagram showing an example of the relationship between the type of railway vehicle and the number of notches in the master controller handle. FIG. 3 is a diagram showing an example of the relationship between the notch position and the driving force corresponding to the speed. FIG. 4 is a diagram showing an example of the notch closing state estimation result 157. The notch engagement state estimation unit 106 generates a notch engagement state estimation result 157 and presents the relationship between the vehicle position and the driving operation content. The notch engagement state estimation unit 106 transmits the generated notch engagement state estimation result 157 to the driving operation history accumulation unit 109. The notch opening state estimation result 157 is data that includes a set of time and the number of notch stages. The details of the processing by the notch opening state estimation unit 106 will be described later. The notch engagement state estimation unit 106 receives the estimated speed 153 from the vehicle speed estimation unit 103 to generate the notch engagement state estimation result 157. Similarly, the notch engagement state estimation unit 106 receives the running distance between stations 156 from the route information management unit 105. Similarly, the notch engagement state estimation unit 106 receives the master controller handle operation sound detection result 159 from the characteristic sound detection unit 108.

[0031] Depending on the type of vehicle for which the driving operation history is being created, the number of notches on the master controller handle may differ. For this reason, the number of notches on the master controller handle for each vehicle model is stored as internal information in advance, as shown in Figure 2, and the notch position and driving force for each speed are also stored as internal information for each vehicle model, as shown in Figure 3. In this embodiment, the railcar controls acceleration and deceleration based on the position of the master controller handle, so that the notch engagement state estimating unit 106 also functions as a driving operation content estimating unit.

[0032] <Sound collection part> The sound collection unit 107 has a sound collection function for collecting sounds around the driving condition monitoring device 10 . The driving situation monitoring device 10 is installed so that the sounds that the sound collection unit 107 can collect include at least the sound of operating the master controller handle. The sound collection unit 107 transmits the sound collection result 158 ​​to the characteristic sound detection unit 108 .

[0033] In this embodiment, the sound collection unit 107 is a microphone attached to the driving condition monitoring device 10, which is a tablet terminal, but it may be other hardware as long as it has a sound collection function for collecting surrounding sounds. For example, it may be an external microphone that can be connected to the driving condition monitoring device 10 either wired or wirelessly.

[0034] In this embodiment, the driving condition monitoring device 10 is installed as close as possible to the location where the master control handle is operated. In other words, the sound collection unit 107 is installed in a position where it can collect the operation sound when the master control handle is operated. For example, this allows the sound collection unit 107 to accurately capture the master control handle operation sound.

[0035] <Characteristic sound detection section> The characteristic sound detection unit 108 extracts the master controller handle operation sound from the sound collection result 158 ​​transmitted from the sound collection unit 107. The characteristic sound detection unit 108 detects master controller handle operation sounds about 10 times per second based on the frequency and speed of general master controller handle operation by the driver, but may also detect them at other intervals. In either case, it is desirable to determine the interval taking into account detailed driving operations, an increase in the amount of data handled, and an increase in the analysis load.

[0036] Specifically, the characteristic sound detection unit 108 extracts the master controller handle operation sound from the sound collection result 158 ​​based on the characteristics of the master controller handle operation sound using a general audio feature extraction method. A typical method for extracting features of speech may be, for example, a pattern matching method or deep learning.

[0037] The characteristic sound detection unit 108 transmits the master controller handle operation sound detection result 159 to the notch engagement state estimation unit 106. The master controller handle operation sound detection result 159 includes the time when the master controller handle operation sound occurred and the number of times the master controller handle sounds. Here, the number of times the master controller handle rings is the operating sound generated at each notch that is passed through when the master controller handle is moved between multiple notches during operation.

[0038] <Driving operation history storage unit> The driving operation history accumulation unit 109 generates a driving operation history 160 based on the on-track position 152, the estimated speed 153, and the notch engagement state estimation result 157. The driving operation history accumulation unit 109 transmits the generated driving operation history 160 to the driving operation history transmission unit 110. The driving operation history 160 includes at least data on the driving pattern and notch engagement history of the vehicle equipped with the driving condition monitoring device. The data on running patterns is time-series data on vehicle positions and speeds, and is information on a unit basis for train operation, such as each station-to-station run or each route. The notch insertion history data is time-series data of vehicle position and notch information, and is information in units of train operation, such as for each station-to-station run or each route.

[0039] The driving operation history 160 may include data other than the driving pattern and notch engagement history data. For example, in this embodiment, the driving operation history 160 includes time-series data of power consumption estimated from the driving pattern and notch engagement history data. This allows the user of the operation status monitoring device to check the running pattern between stations, the notch insertion history, and the resulting relationship with power consumption. Furthermore, for comparison, by preparing in advance the running pattern, notch insertion history, and power consumption data for an ideal running mode from the perspective of energy conservation and including this in the operation operation history 160, the user of the operation status monitoring device can check the differences between the ideal running mode and the current running pattern and notch insertion history, along with the differences in power consumption.

[0040] <Driving operation history transmission unit> The driving operation history transmission unit 110 is a display unit that visualizes and outputs the data of the driving operation history 160 to the user of the driving situation monitoring device 10.

[0041] Next, an example of visualization of the driving operation history 160 will be described with reference to FIG. The graph shown in the upper part of Figure 5 is a visualization example, with the horizontal axis representing vehicle position and the vertical axis representing vehicle speed. The graph shown in the middle part of Figure 5 is a visualization example, with the horizontal axis representing vehicle position and the vertical axis representing the number of notches inserted. The graph shown in the lower part of Figure 5 is a visualization example, with the horizontal axis representing vehicle position and the vertical axis representing power consumption. The table shown in the lower part of Figure 5 is a visualization example, with graphs showing power consumption between stations and running time. In the graph of Figure 5, the black solid line indicates the actual measurement, and the black chain line indicates the energy-saving state, that is, the ideal state.

[0042] By visualizing this graph, it is possible to review the detailed driving operation history. For example, by comparing the same vehicle position in the graph shown in the upper part of Figure 5 with the graph shown in the middle part of Figure 5, it is possible to review the notch closing operation at that vehicle position and the speed in that case. Furthermore, if the driving operation history 160 includes driving pattern data and notch engagement history data for comparison, these can be displayed in an overlapping manner to facilitate comparison.

[0043] For example, by comparing the same vehicle position in the graph shown in the upper part of Figure 5 with the graph shown in the lower part of Figure 5, it is possible to review the notch closing operation at that vehicle position and the power consumption in that case. Furthermore, by visualizing the graphs and tables, it becomes easier to understand the relationship between running patterns, notch input history, and power consumption.In addition, it is possible to understand the overall evaluation results across stations.

[0044] The driving operation history transmission unit 110 may notify the driver when the evaluation result of the estimation accuracy of the driving operation details by the notch engagement state estimation unit 106 is equal to or less than a set threshold. In this case, the driving operation history transmission unit 110 also functions as a notification unit.

[0045] Next, an example of processing by the notch opening state estimation unit 106 will be described with reference to FIG. FIG. 6 is a diagram showing an example of a flowchart of the process executed by the notch opening state estimation unit 106. The notch engagement state estimation unit 106 executes the process shown in FIG. 6 at the timing when the master controller handle operation sound detection result 159 is updated.

[0046] In STEP 601, the master controller handle operation time is acquired. Specifically, the notch engagement state estimation unit 106 acquires the master controller handle operation time from the master controller handle operation sound detection result 159.

[0047] In STEP 602, the average acceleration of the relevant section is calculated. Specifically, the notch engagement state estimation unit 106 calculates the average acceleration for the section based on the vehicle acceleration from the previous master controller handle operation time obtained during the previous processing to the master controller handle operation time obtained during the current processing. Here, the acceleration is the time derivative of the estimated speed 153 obtained from the vehicle speed estimation unit 103, and is the actual acceleration calculated from the speed and travel distance based on the position information measured based on the measured on-track position 152.

[0048] In STEP 603, the running resistance is calculated from the current vehicle position and speed. Specifically, the notch engagement state estimation unit 106 calculates the running resistance using a running resistance calculation formula. Note that the running resistance calculation formula is well known, so a detailed explanation of the principles behind it will be omitted. Here, the notch engagement state estimation unit 106 may acquire internal information such as the line shape, gradient, and air resistance characteristics of the vehicle, which are the driving environment, and calculate the running resistance taking this internal information into consideration.

[0049] In STEP 604, the driving force for realizing the average acceleration calculated in STEP 602 is calculated. Specifically, the notch closing state estimation unit 106 calculates the driving force from the following equation of motion.

number

[0050] In STEP 605, the notch positions that realize the driving force and braking force are calculated. Specifically, the notch engagement state estimation unit 106 calculates the notch position that will result in the driving force and braking force that are closest to the driving force obtained in STEP 604 from the specifications of the master controller handle regarding the driving force and braking force for each speed. For example, the notch engagement state estimation unit 106 acquires and stores in advance as internal information the relationship between the driving force corresponding to the notch position and the speed, as shown in FIG. 3, and calculates and estimates the notch position using this internal information.

[0051] In STEP 606, it is determined whether or not the absolute value of the difference between the two accelerations from the previous master controller handle operation time to the current master controller handle operation time exceeds a threshold value. If the absolute value of the difference between the two accelerations exceeds the threshold, the process proceeds to STEP 608. If not, the process proceeds to STEP 607. Here, the two accelerations are the estimated acceleration obtained by solving the equation of motion again from the notch position identified in STEP 605 and the actually measured acceleration obtained in STEP 602. Specifically, the notch closing state estimation unit 106 compares the absolute values ​​of the differences between the two accelerations. Here, the equation of motion between the time of the previous master controller handle operation and the time of the current master controller handle operation is formulated as follows:

number

[0052] The threshold value, which is set in advance as internal information, may be adjusted for each section and vehicle type. For example, the threshold value may be set by calculating the acceleration at each notch for the average number of occupants on that section before operation begins, and then subtracting the acceleration corresponding to each adjacent notch and setting the median value of the difference as the threshold. In this case, if the acceleration at the P5 notch is 2.5 km / h·s and the acceleration at the P4 notch is 2.0 km / h·s, the threshold value would be 0.25. Furthermore, because the relationship between notch position and acceleration differs depending on vehicle speed, vehicle weight, and route conditions, the relationship between the notch and acceleration is calculated using the equation of motion when determining the threshold value.

[0053] In STEP 607, the notch engagement state estimation unit 106 transmits the notch position determined in STEP 605 to the driving operation history accumulation unit 109, and the process ends.

[0054] In STEP 608, the notch engagement state estimation unit 106 transmits the period from the previous master controller handle operation time to the current time as "notch position unknown" to the driving operation history accumulation unit 109, and ends the process. In this embodiment, the notch opening state estimation unit 106 directly compares the absolute value of the difference between the two accelerations with the threshold value, but the method for determining the estimation accuracy of the notch position is not limited to this. For example, it is also possible to predefine the relationship between the absolute value of the difference between the accelerations and the estimation accuracy so that if the estimation accuracy value is below the threshold value, the accuracy is determined to be poor.

[0055] Next, the processing of the notch engagement state estimation unit 106 when a master controller handle operation sound is not detected will be described with reference to FIGS. FIG. 7 is a diagram showing an example of a flowchart of the process executed by the notch opening state estimation unit 106. FIG. 8 is a diagram showing the relationship between the master controller handle operation time and the number of sounds. The processing in Figure 7 differs from the processing in Figure 6 in that it uses an algorithm to correct the notch position when a master controller handle operation sound is missed by measuring the number of times the master controller handle operation sound occurs. In the following description, components that are the same as or equivalent to those in the processing of FIG. 6 described above are given the same reference numerals, and their description will be simplified or omitted. In the process of FIG. 7, STEP 608 is deleted from the process of FIG. 6, and STEP 700 and STEPs 708 to 710 are added.

[0056] In STEP 700, it is determined whether or not the operation has ended. If the operation has ended, the process proceeds to STEP 708, and if the operation is still in progress, the process proceeds to STEP 601. The notch closing state estimation unit 106 may use, for example, manual operation by the driver on the operation unit 104 as a method of determining the start and end of operation. In this case, the operation unit 104 is provided with a function for inputting the start and end of data acquisition. The notch closing state estimation unit 106 may automatically determine the start and end of operation using, for example, a method of determining that the train is traveling on the main line from route map data and the position and speed acquired by GPS, a method of determining by voice recognition the sound associated with inserting and removing the master control key in the driver's cab, a method of determining the start / end of master control operation by voice, a method of determining the opening and closing of the door associated with entering and exiting the driver's cab by voice, etc. In this case, these methods may be used alone or in combination.

[0057] In STEP 708, the notch position and the number of times the master controller handle sounds at the time when the notch position is determined are obtained before and after the section in which it is determined that the absolute value of the difference between the two accelerations exceeds the threshold. The two accelerations are the estimated acceleration obtained from the notch position obtained in STEP 606 and the actually measured acceleration obtained in STEP 602.

[0058] At this time, the notch position is determined for master controller handle operation when it is determined that the absolute value of the difference between the two accelerations between the time of the previous master controller handle operation and the time of the current master controller handle operation does not exceed the threshold value, and for emergency brakes that are applied before and after the start of operation. Here, the number of times the master controller handle sounds is generated is acquired according to the time when the master controller handle operation sound is generated, as shown in FIG.

[0059] Next, the processing in STEP 709 will be described with reference to FIG. Fig. 9 is a diagram showing an example of estimation of notch position candidates for missed detection of master controller steering wheel operation sound. The graph in Fig. 9 shows vehicle positions L0 to L4 on the horizontal axis and notch operations B2 to P4 on the vertical axis. In Fig. 9, the black dotted line is a graph showing the actual notch insertion history. The black dashed-dotted line in Fig. 9 is a graph showing the notch insertion history before estimation. Furthermore, the black solid line in Fig. 9 is a graph showing the notch insertion history after estimation. In STEP 709, candidates for the notch position in the section where the notch insertion history is unknown are estimated. Specifically, for a section where the notch engagement history is unknown, the notch engagement state estimation unit 106 estimates candidates for the notch position based on the results of comparing the estimated notch positions determined before and after the section, the number of times the master controller handle operation sound has been emitted, and the acceleration obtained by time-differentiating the estimated speed 153 obtained from the vehicle speed estimation unit 103, for adjacent sections. For example, if the acceleration is positive, it is determined that the notch position has changed in the notch up direction by the number of rings. For example, if the acceleration is negative, it is determined that the acceleration has changed in the notch-down direction by the number of rings. For example, if the acceleration is 0, it is determined that the notch is neither up nor down, and the notch position is not changed.

[0060] The example in Figure 9 is based on the following assumptions: "The actual notch insertion history is P1 from L0 to L1, with three notch-up operations at L1, two notch-down operations at L2, and four notch-down operations at L3. In response to this, the sound collection unit 104 and the notch engagement state estimation unit 106 acquire data showing that the master controller handle operation sound has been emitted three times and the acceleration direction is positive in L1, and also acquire data showing that the master controller handle operation sound has been emitted four times and the acceleration direction is negative in L3. However, the sound collection unit 104 was unable to acquire data on the two occurrences of master controller handle operation sound at L2. As a result, the section from L1 to L3 is an unknown section of the notch engagement history. For this reason, in Figure 9, the section from L0 to L1 is P1 for all dotted lines, dashed dot lines, and solid lines. For the section from L1 to L2', the dotted lines and solid lines are P4, and the dashed dot lines are not shown. For the section from L2' to L2, the dotted lines are P4, and the solid lines are P2. For the section from L2 to L3, the dotted lines and solid lines are P2, and the dashed dot lines are not shown. For the section from L3 to L4, the dotted lines, dashed dot lines, and solid lines all show B2. Note that in Figure 9, the dotted lines, dashed dot lines, and solid lines have the same values, and even in places where they overlap, they are shown side by side for notation purposes. In such a case, the notch engagement history for the unknown section is estimated as follows: the notch in the section from L0 to L1 is P1, the notch from L3 to L4 is B2, and the notch engagement state estimation unit 106 estimates that three notch-up operations were performed at L1 because the master controller handle operation sound was emitted three times and the acceleration direction was positive, and that four notch-down operations were performed at L3 because the master controller handle operation sound was emitted four times and the acceleration direction was negative, so it can be inferred that two notch-down operations were performed between L1 and L3.Incidentally, since it is unlikely that a notch-up operation and a notch-down operation would be performed with a single master controller handle operation except due to an operational error, it is assumed that consecutive master controller handle operation sounds are operations in the same direction. In this case, in FIG. 9, the notch insertion history after estimation can be represented as shown by the solid line in FIG. 9, which indicates two notch down operations at position L2' in the section from L1 to L3. In this case, it is highly likely that the position L2 where the notch operation actually occurred and the position L2' where the notch operation was estimated to have occurred are different. However, since the notch operation in the section where the notch operation history is unknown can be identified, and depending on the size of the section where the notch operation history is unknown, L2 and L2' can be treated as errors that do not interfere with reviewing driving operations.

[0061] In STEP 710 , the notch position determined in STEP 709 is transmitted to the driving operation history accumulation unit 109 .

[0062] Even if there is an oversight of detection of the master controller handle operation sound, the algorithm shown in STEP 708 to STEP 710 of FIG. 7 makes it possible to estimate what kind of master controller handle operation was performed in the unknown notch operation section from the information in the sections before and after that.

[0063] As described above, the driving condition monitoring device 10 of this embodiment can visualize the running pattern between stations based on the vehicle position and speed estimated using GPS in a railway vehicle. This can be used to help the driver review his or her driving operation. In other words, by reducing the variation in running patterns and aligning them to energy-efficient running patterns, energy savings in railway operation can be achieved.

[0064] [Second embodiment] Next, a second embodiment will be described with reference to FIG. FIG. 10 is a diagram showing an example of the configuration of a driving condition monitoring device 20 according to this embodiment. The driving situation monitoring device 20 of the second embodiment differs from the first embodiment in that the railway vehicle is provided with an acceleration measuring device that can measure actual acceleration without relying on a GPS function. In the following description, the same or equivalent components as those in the first embodiment described above are denoted by the same reference numerals, and the description thereof will be simplified or omitted. Furthermore, the railway vehicle whose running pattern is visualized by the driving situation monitoring device 20 is also operated by operating the master controller handle.

[0065] The driving condition monitoring device 20 mainly includes an acceleration measurement unit 1001, a vehicle speed estimation unit 1002, an on-track position estimation unit 1003, an operation unit 104, a route information management unit 105, a notch engagement state estimation unit 1006, a sound collection unit 107, a characteristic sound detection unit 108, a driving operation history accumulation unit 109, and a driving operation history transmission unit 110.

[0066] <Acceleration measurement unit> The acceleration measurement unit 1001 outputs the acceleration measurement results measured by the acceleration measurement device at a predetermined time period. The acceleration measurement unit 1001 transmits the output measured acceleration to the vehicle speed estimation unit 1002 and the notch engagement state estimation unit 1006. Here, the time period is about 10 times per second, taking into consideration the purpose of the driving situation monitoring device, which is to enable the driver to reflect on their driving operation by visualizing the driving pattern, but other periods may also be used.

[0067] For example, if the time period is too short, the amount of data increases, increasing the processing load, and problems such as poor reproducibility of vehicle speed and position estimation in post-processing occur due to the influence of small vibration noise. For example, if the time period is too long, it becomes impossible to detect small changes in acceleration, which leads to problems such as worsening the integral error in estimating vehicle speed and position. In either case, the time period is determined based on a balance between the need for a review of driving operations, an increase in the amount of data to be handled, and suppression of an increase in the analysis load in subsequent processing units.

[0068] The acceleration measuring unit 1001 also acquires gravitational acceleration using an acceleration measuring device, so the acceleration measuring unit 1001 needs to separate the acceleration due to acceleration and deceleration of the vehicle from the gravitational acceleration. The acceleration measuring unit 1001 can use, for example, a method of separating gravitational acceleration by taking into account the attitude of the acceleration measuring device, or a method of separating gravitational acceleration by acquiring only high-frequency acceleration changes using a high-pass filter. Note that these methods are well known, so a detailed explanation of their principles will be omitted.

[0069] <Vehicle speed estimation unit> The vehicle speed estimation unit 1002 estimates the vehicle speed based on the acceleration obtained from the acceleration measurement unit 1001, the time period, and the speed at the time of the previous processing. The vehicle speed estimation unit 1002 transmits the estimated speed 1052 to the on-track position estimation unit 1003 and the driving operation history accumulation unit 109.

[0070] <Orbital position estimation section> The on-track position estimating unit 1003 estimates the on-track position based on the speed and time period obtained from the vehicle speed estimating unit 1002 and the position at the time of the previous processing. The on-orbit position estimation unit 1003 estimates the on-orbit position including an error due to an integral error. In order to correct this error, the on-track position estimation unit 1003 corrects the current vehicle position to the stopping position of the station where the train is currently stopped when the train stops at the next station during operation. At this time, the on-track position estimation unit 1003 acquires the section where the train is currently running from the route information management unit 105.

[0071] The on-track position estimation unit 1003 acquires the stopping position at each station as internal information in advance. The on-track position estimation unit 1003 performs the following calculation to correct the on-track position of the time-on-track position history from one station before.

number

[0072] <Notch insertion state estimation unit> The notch engagement state estimation unit 1006 generates a notch engagement state estimation result 157 and presents the relationship between the vehicle position and the driving operation content. The notch engagement state estimation unit 106 transmits the generated notch engagement state estimation result 157 to the driving operation history accumulation unit 109.

[0073] Unlike notch opening state estimation unit 106 , notch opening state estimation unit 1006 generates notch opening state estimation result 157 using acceleration information 1051 .

[0074] The notch engagement state estimation unit 1006 receives acceleration information 1051 from the acceleration measurement unit 1001 to generate the notch engagement state estimation result 157. Similarly, the notch engagement state estimation unit 1006 receives an estimated speed 1052 from the vehicle speed estimation unit 1002. Similarly, the notch engagement state estimation unit 1006 receives a running distance between stations 156 from the route information management unit 105. Similarly, the notch engagement state estimation unit 1006 receives a master controller handle operation sound detection result 159 from the characteristic sound detection unit 108.

[0075] As described above, according to the driving situation monitoring device 20 of this embodiment, the driving situation monitoring device 20 visualizes the running pattern between stations based on the vehicle position and vehicle speed estimated using the acceleration obtained using the acceleration measurement unit 1001 and the operating sound obtained using the sound collection unit 107 when operating the master controller handle in a railway vehicle, thereby enabling the driver to review his driving operation. This allows the function to be realized in a system without a GPS function, and can also play a complementary role when the GPS function does not function effectively even if the system is equipped with a GPS function. In other words, the vehicle position and vehicle speed can be estimated by means other than the GPS function and used to review the driving operation.

[0076] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the present invention.

[0077] For example, the driving condition monitoring device 20 of the second embodiment may be provided with the GPS receiving unit 101 and the on-track position estimating unit 102 in addition to the acceleration measuring unit 1001, the vehicle speed estimating unit 1002, and the on-track position estimating unit 1003. This allows the vehicle position estimation based on the acceleration measurement results and the vehicle position estimation based on the GPS to be used in a way that complements each other's weaknesses, thereby expanding the range of applications for the driving condition monitoring device.

[0078] The present invention can also take the following forms. (Aspect 1) A driving situation monitoring device that displays a relationship between a vehicle position of a vehicle traveling on a track and a driving operation content of the vehicle, It is equipped with a sound collection unit that collects surrounding sounds, including the sound of operating the master controller handle. The driving operation details are estimated based on the operation sound of the master controller handle collected by the sound collection unit. A driving condition monitoring device characterized by: (Aspect 2) The driving condition monitoring device according to aspect 1, a satellite positioning information receiving unit for receiving satellite positioning information; The vehicle position is estimated based on the satellite positioning information. A driving condition monitoring device characterized by: (Aspect 3) The driving condition monitoring device according to aspect 1 or 2, Equipped with an acceleration measurement unit capable of outputting actual measured acceleration, The vehicle position is estimated based on the acceleration measurement result of the acceleration measurement unit. A driving condition monitoring device characterized by: (Aspect 4) The driving condition monitoring device according to aspect 3, The driving operation details of the vehicle including the estimated acceleration are estimated based on the time when the operation sound of the master controller handle is detected, the specifications of the master controller handle, and the actually measured acceleration. A driving condition monitoring device characterized by: (Aspect 5) A driving condition monitoring device according to aspect 4, The accuracy of estimating the driving operation details is evaluated based on the absolute value of the difference between the estimated acceleration of the vehicle at the time when the operation sound of the master control handle is detected and the actually measured acceleration. A driving condition monitoring device characterized by: (Aspect 6) A driving condition monitoring device according to aspect 5, a notification unit that notifies when the evaluation result of the estimation accuracy is below a threshold value; A driving condition monitoring device characterized by: (Aspect 7) A driving situation monitoring device according to aspect 6, By comparing the number of occurrences of the operation sound of the master controller handle with the acceleration of the vehicle, a detection failure of the operation sound of the master controller handle is detected. A driving condition monitoring device characterized by: (Aspect 8) A driving situation monitoring device according to aspect 7, The driving operation content is corrected based on the detection failure. A driving condition monitoring device characterized by: (Aspect 9) A driving condition monitoring device according to any one of aspects 3 to 8, a characteristic sound detection unit that detects the operation sound based on the characteristics of the operation sound of the master controller handle from the surrounding sounds collected by the sound collection unit; a driving operation content estimation unit that estimates the driving operation content based on the operation time of the master control handle operation sound detected by the characteristic sound detection unit. A driving condition monitoring device characterized by: (Aspect 10) A driving condition monitoring device according to any one of aspects 1 to 9, The driving operation content is a command state for controlling acceleration / deceleration of the vehicle. A driving condition monitoring device characterized by: (Aspect 11) A driving situation monitoring device according to aspect 10, The command state for controlling the acceleration / deceleration of the vehicle is a notch-in state. A driving condition monitoring device characterized by: (Aspect 12) A driving condition monitoring device according to any one of aspects 1 to 11, a display unit that displays the relationship between the vehicle position and the driving operation content, and the relationship between the vehicle position and the vehicle speed; A driving condition monitoring device characterized by: (Aspect 13) A driving condition monitoring device according to aspect 12, The display unit visualizes and outputs the relationship between the vehicle position and the driving operation content, and the relationship between the vehicle position and the vehicle speed. A driving condition monitoring device characterized by: (Aspect 14) The driving condition monitoring device according to aspect 12 or 13, The display unit estimates the amount of power consumption while the vehicle is running and visualizes the history of the amount of power consumption. A driving condition monitoring device characterized by: [Explanation of symbols]

[0079] 101 GPS receiver 102 Orbital position estimation section 103 Vehicle speed estimation unit 104 Operation section 105 Route Information Management Department 106 Notch insertion state estimation unit 107 Sound collection section 108 Characteristic Sound Detector 109 Driving operation history storage unit 110 Driving operation history transmission unit 151 Latitude and Longitude 152 Orbital position 153, 1052 Estimated speed 154 Track Shape 155 Route information 156 Stations 157 Notch insertion state estimation results 158 Sound collection results 159 Master controller handle operation sound detection results 160 Driving operation history 1001 Acceleration measurement unit 1002 Vehicle speed estimation unit 1003 Orbital position estimation section 1006 Notch insertion state estimation unit 1051 Acceleration Information Position on track 1053

Claims

1. A driving situation monitoring device that displays a relationship between a vehicle position of a vehicle traveling on a track and a driving operation content of the vehicle, It is equipped with a sound collection unit that collects the sound of the master controller handle operation. The driving operation details are estimated based on the operation sound of the master controller handle collected by the sound collection unit. A driving condition monitoring device characterized by:

2. The driving condition monitoring device according to claim 1, a satellite positioning information receiving unit for receiving satellite positioning information; The vehicle position is estimated based on the satellite positioning information. A driving condition monitoring device characterized by:

3. The driving condition monitoring device according to claim 1, Equipped with an acceleration measurement unit capable of outputting actual measured acceleration, The vehicle position is estimated based on the acceleration measurement result of the acceleration measurement unit. A driving condition monitoring device characterized by:

4. The driving condition monitoring device according to claim 3, The driving operation details of the vehicle, including the estimated acceleration, are estimated based on the time when the operation sound of the master controller handle is detected, the specifications of the master controller handle, and the actually measured acceleration. A driving condition monitoring device characterized by:

5. The driving condition monitoring device according to claim 4, The accuracy of estimating the driving operation details is evaluated based on the absolute value of the difference between the estimated acceleration of the vehicle at the time when the operation sound of the master controller handle is detected and the actually measured acceleration. A driving condition monitoring device characterized by:

6. The driving condition monitoring device according to claim 5, a notification unit that notifies when the evaluation result of the estimation accuracy is below a threshold value; A driving condition monitoring device characterized by:

7. The driving condition monitoring device according to claim 6, By comparing the number of occurrences of the operation sound of the master controller handle with the estimated acceleration of the vehicle, a detection failure of the operation sound of the master controller handle is detected. A driving condition monitoring device characterized by:

8. The driving condition monitoring device according to claim 7, The driving operation content is corrected based on the detection failure. A driving condition monitoring device characterized by:

9. The driving condition monitoring device according to claim 3, a characteristic sound detection unit that detects the operation sound based on the characteristics of the operation sound of the master controller handle from the operation sound collected by the sound collection unit; a driving operation content estimation unit that estimates the driving operation content based on the operation time of the master control handle operation sound detected by the characteristic sound detection unit. A driving condition monitoring device characterized by:

10. The driving condition monitoring device according to claim 1, The driving operation content is a command state for controlling acceleration / deceleration of the vehicle. A driving condition monitoring device characterized by:

11. The driving condition monitoring device according to claim 10, The command state for controlling the acceleration / deceleration of the vehicle is a notch-in state. A driving condition monitoring device characterized by:

12. The driving condition monitoring device according to claim 1, a display unit that displays the relationship between the vehicle position and the driving operation content, and the relationship between the vehicle position and the vehicle speed; A driving condition monitoring device characterized by:

13. The driving condition monitoring device according to claim 12, The display unit visualizes and outputs the relationship between the vehicle position and the driving operation content, and the relationship between the vehicle position and the vehicle speed. A driving condition monitoring device characterized by:

14. The driving condition monitoring device according to claim 12, The display unit estimates the amount of power consumption while the vehicle is running and visualizes the history of the amount of power consumption. A driving condition monitoring device characterized by:

Images