WO2013124980A1

WO2013124980A1 - Observation program specification device, train instrument observation system, observation program specification method, and program

Info

Publication number: WO2013124980A1
Application number: PCT/JP2012/054244
Authority: WO
Inventors: 石井　篤
Original assignee: 三菱電機株式会社
Priority date: 2012-02-22
Filing date: 2012-02-22
Publication date: 2013-08-29

Abstract

An above-ground observation server comprising a data reception part (401), a data observation part (402), and a storage part (410). The storage part (410) indicates a specified onboard instrument, which is requested for observation by an observation program, as an observation target, and stores an observation program management table (408) having a record of the observation target onboard instrument for each observation program of a plurality of observation programs. The data reception part (401) receives compiled data of the onboard instruments from data compiling devices (100) which are installed in multiple trains and which send compiled data at predetermined time intervals. The data observation part (402) detects compiled data of malfunctions occurring in the onboard instruments as detected compiled data on the basis of received compiled data (601), and on the basis of the detected compiled data, searches the observation program management table (408) for an observation program requesting observation of the malfunctioned onboard instruments recorded in the detected compiled data, and specifies the observation program that will give notification of the malfunction in the onboard instruments.

Description

Monitoring program specifying device, train equipment monitoring system, monitoring program specifying method and program

The present invention relates to a monitoring program specifying device, a train equipment monitoring system, a monitoring program specifying method, and a program for monitoring the state of equipment mounted on a train.

The conventional train equipment monitoring system enables wireless data communication between the on-board equipment and the ground system. When an abnormality occurs on the equipment on the car, the on-board data is acquired from the ground system in response to a command from the conductor. A method has been proposed (for example, Patent Document 1).

Japanese Patent Laid-Open No. 10-76952

The conventional monitoring system detects a failure occurring on the vehicle and transmits data from the vehicle to the ground by the operation of the driver. The conventional method has a problem that it takes time to detect the occurrence of a failure on the ground system side because of manual notification. An object of the present invention is to monitor a plurality of devices on a vehicle (meaning a state where the vehicle is mounted on the vehicle; the same applies hereinafter) from a plurality of ground systems while suppressing radio congestion. Another object of the present invention is to make it possible to monitor a plurality of devices on a vehicle and to monitor a plurality of trains from a ground system in units of line sections and wards.

The monitoring program specifying device of the present invention comprises:
Mounted on each train of a plurality of trains on a track composed of one or more vehicles, train identification information for identifying the mounted train, a mounting attribute indicating a predetermined attribute of the mounted train, From each mounting device that transmits aggregate data including train device information that identifies each device of a plurality of devices equipped on the mounted train and represents the state of each device, at a predetermined time interval, A data receiver for receiving the aggregated data;
Detection that detects the aggregated data in which a predetermined event has occurred in any of the devices identified from the train device information as detected aggregated data based on the train device information of the aggregated data received by the data receiving unit And
First device designation information in which at least one of the devices is designated as a monitoring target by a monitoring program that requests monitoring of the specific device, monitoring program identification information that identifies the monitoring program, and the first device designation information include A storage for storing monitoring program management information for each of the monitoring programs of the plurality of monitoring programs having monitoring program correspondence information associated with a specified attribute indicating an attribute that the train to be equipped with the equipment to be specified has. And
The specified attribute of the attribute indicated by the mounted attribute included in the detection aggregated data, and the first equipment designation information in which the device in which the event has occurred indicated by the train equipment information of the detection aggregated data is specified. And a specifying unit that specifies a monitoring program for notifying the device that the event has occurred by executing a search process for searching for the monitoring program correspondence information from the monitoring program management information. And

According to the present invention, it is not necessary for the ground monitoring program to individually communicate with the vehicle, so that congestion can be suppressed and efficient communication can be achieved in wireless communication with a limited bandwidth.

FIG. 3 is a diagram illustrating train formation in the first embodiment. 1 is a configuration diagram of a train equipment monitoring system 1000 according to Embodiment 1. FIG. FIG. 3 is a block diagram of the ground monitoring server 400 in the first embodiment. FIG. 6 shows a data structure of aggregated data 601 in the first embodiment. FIG. 3 shows a vehicle monitoring TBL 405 in the first embodiment. FIG. 3 is a diagram showing area-specific TBL 406 according to the first embodiment. FIG. 3 is a diagram showing composition management TBL 407 in the first embodiment. [Fig. 4] is a diagram showing a program management TBL 408 in the first embodiment. 3 is a flowchart showing the operation of the data aggregation device 100 according to the first embodiment. 6 is another flowchart showing the operation of the data aggregation device 100 according to the first embodiment. 5 is a flowchart showing the operation of the ground monitoring server 400 that has received a monitoring request 510 according to the first embodiment. The figure explaining the process of FIG. [Fig. 4] is a diagram showing a data configuration of a monitoring request 510 in the first embodiment. The flowchart of operation | movement of the ground monitoring server 400 when the track of the traveling vehicle in Embodiment 1 is changed. The figure explaining the process of FIG. The figure which shows the initial registration of the organization management TBL407 in Embodiment 1, and vehicle monitoring TBL405. The flowchart of operation | movement when the ground monitoring server 400 in Embodiment 1 implements monitoring. The figure explaining the process of FIG. The figure which shows the hardware constitutions of the data aggregation apparatus 100 in Embodiment 2, and the ground monitoring server 400.

Embodiment 1 FIG.
(Explanation of terms)
With reference to FIG. 1, the terminology used in the following description of the embodiment will be described.
(1) Vehicle: The train shown in FIG. 1 includes vehicles 1, 2, and 3. FIG. 1 shows three vehicles.
(2) Formation number: The formation means a vehicle configuration of a train composed of one or more vehicles. The organization number is information that identifies the organization.
(3) Line section: A line section is a route on which the train (train) travels.
(4) Affiliated ward: A affiliation ward (also simply referred to as a ward) is a jurisdiction to which a vehicle (organization) belongs. The vehicle belongs to one of the “wards”.
(5) Equipment information: As shown in FIG. 1, equipment (on-board equipment) is mounted on the train (train). In FIG. 1, the devices are shown as devices 201-1 to 201-3. The device information is information including information for identifying a device and information indicating the state of the device. What state is used as device information can be freely set.
(6) Monitoring target device information: The monitoring target device information is used in the vehicle monitoring information management table 405 of FIG. Information that associates a monitoring target device with a bit, such as “000001” (example of 6 bits). The rightmost is called the first bit, and the left is called second, third,... The first bit is assigned to a specific device 1 and the second bit is assigned to another specific device 2. The other bits are the same. If the bit is 1, the device corresponding to the bit is a monitoring target. In the following, the monitoring target device information is described as monitoring target device information 11 with reference numeral “11”, but the monitoring target device information 11 may be described as “monitoring bit string 11”. Moreover, although the monitoring target apparatus information (bit string) is also generated in S61 of FIG. 17, the bit string of S61 is a bit string indicating a failure. Therefore, the bit string generated in S61 is called “failure bit string 11-1” and is distinguished from “monitor bit string 11”. Of course, the bits in the same position in the monitoring bit string 11 and the failure bit string 11-1 are the same device. For example, the first bit of both is a specific device 1.
(7) In the following description, the monitoring target device information 11 is used for the vehicle monitoring information management table 405 and the area-specific monitoring target device information table 406, which are different types of tables. If desired, the information is represented as monitoring target device information 11 (405) and monitoring target device information 11 (406). The same applies to other data.

FIG. 2 is a system configuration diagram showing the overall configuration of the train equipment monitoring system 1000. FIG. 3 is a block diagram of the ground monitoring server 400 of FIG.

(System configuration)
The train equipment monitoring system 1000 includes a data aggregation device 100 (mounted device), a transmission / reception device 202, a radio base station 301, a ground monitoring server 400, and a plurality of monitoring terminal devices 501 (hereinafter referred to as monitoring terminals). Although only one train is shown in FIGS. 1 and 2, the data aggregation device 100 is mounted on each train of a plurality of trains. The ground monitoring server 400 receives the aggregated data 601 from each data aggregation device 100.
(1) The data aggregation device 100 aggregates data of each device on the vehicle and transmits the data to the ground.
(2) The transmission / reception device 202 transmits data to the ground side by wireless communication.
(3) The radio base station 301 receives data transmitted by radio communication from the transmission / reception device 202 and transfers the data to the ground monitoring server 400.
(4) The ground monitoring server 400 receives the data aggregated by the data aggregating apparatus 100, receives monitoring requests from a plurality of monitoring terminals 501, and monitors the state of the on-board equipment.
(5) The monitoring terminal 501 transmits a monitoring request to the ground monitoring server 400 and receives a notification from the ground monitoring server 400 when a failure or the like occurs on the vehicle.
Specifically, as shown in FIG. 2, a monitoring program is running on each monitoring terminal 501. This monitoring program transmits a monitoring request. Of course, a plurality of monitoring programs may operate on one monitoring terminal 501.

(Data Aggregation Device 100)
The data aggregation device 100 includes a data accumulation unit 101, a data aggregation unit 102, and a data transmission unit 103.
As shown in FIG. 2, the data aggregation device 100 is communicably connected to a plurality of devices equipped on the train. The data aggregating apparatus 100 automatically generates the aggregated data 601 and transmits the automatically generated aggregated data 601 at a predetermined time interval. The specific operation is as follows.
(1) The data storage unit 101 temporarily stores data acquired from on-vehicle equipment.
(2) The data aggregating unit 102 aggregates the data accumulated in the data accumulating unit 101 into one data set.
(3) The data transmission unit 103 transmits the aggregated data to the ground monitoring server 400 via the transmission / reception device 202.

(Ground monitoring server 400)
As shown in FIG. 3, the ground monitoring server 400 includes a data receiving unit 401, a data monitoring unit 402 (detection unit, specifying unit), a monitoring request processing unit 403, an abnormality notification unit 404, a vehicle monitoring information management table 405, and an area-specific information. A monitoring target device information table 406, a composition management table 407, a monitoring program management table 408, and a storage unit 410 are provided.
(1) The data receiving unit 401 receives the aggregated data 601 transmitted from the vehicle.
(2) The data monitoring unit 402 monitors the received aggregated data 601 whether an event corresponding to the monitoring condition specified from the monitoring terminal 501 has occurred.
(3) The monitoring request processing unit 403 receives a monitoring request from the monitoring terminal 501.
(4) The abnormality notification unit 404 notifies the occurrence of an abnormality to the monitoring program that has transmitted the monitoring request.

(Tables 405 to 408)
(5) Vehicle monitoring information management table 405:
The vehicle monitoring information management table 405 may be simply referred to as vehicle monitoring TBL 405 hereinafter. The vehicle monitoring TBL 405 is a table that summarizes monitoring target devices for each travel line section and affiliation section. The vehicle monitoring TBL 405 will be described in detail with reference to FIG.
(6) Area-specific monitored device information table 406:
The area-specific monitoring target device information table 406 may be simply referred to as an area-specific TBL 406 in the following. The area-specific TBL 406 is a table in which information on devices to be monitored is collected in units of monitoring areas (units of line wards and affiliated wards) requested by the monitoring terminal 501 (monitoring program). The area-specific TBL 406 will be described in detail with reference to FIG.
(7) Organization management table 407:
Hereinafter, the composition management table 407 may be referred to as composition management TBL 407.
The organization management TBL 407 is a table that manages the relationship between the organization, the line 12 on which the organization is traveling, and the ward to which the organization belongs. The organization management table 407 will be described in detail with reference to FIG.
(8) Monitoring program management table 408:
The monitoring program management table 408 may be simply referred to as program management TBL 408 hereinafter. The monitoring program management table 408 is a table having monitoring target device information requested from the monitoring program and monitoring area information. The program management TBL 408 will be described in detail with reference to FIG.

(9) The storage unit 40 stores each table such as the vehicle monitoring information management table 405, various information, data, and the like.

(Aggregated data 601)
FIG. 4 is a diagram illustrating an example of the aggregated data 601. The aggregated data 601 is data generated for each train (train). For example, aggregate data 601 for the composition is generated for the composition composed of three vehicles 1 to 3 in FIG. The aggregated data 601 has a basic information part 6011, a common information part 6012, and a device specific information part 6013. Aggregated data 601 is information in which information of each device mounted on the vehicle is integrated into one.
(1) The basic information part 6011 includes vehicle basic information such as a composition number 15, a vehicle type code, and a column number. The organization number 15 (train identification information) is information for identifying the organization (train) on which the data aggregation device 100 that transmitted the aggregated data 601 is mounted.
(2) The common information part 6012 is information common to each device of the vehicle such as a line section and a kilometer. The line ward 12 and the affiliation ward 13 are information (mounting attributes) indicating the attributes of the train on which the data aggregation device 100 is mounted. The line section 12 is an example of a first mounting attribute, and the belonging section 13 is an example of a second mounting attribute. In this example, there are a plurality (two) of mounting attributes.
(3) The device specific information part 6013 includes device information 1 and 2 (train device information) and the like. The device information 1, 2, etc. is information that identifies each device of a plurality of devices equipped in the organization on which the data aggregation device 100 is mounted and represents the state of each device.
(4) The data items shown in FIG. 4 are representative examples, and are not limited to these items.

(Description of each table)
Next, each table in FIGS. 5 to 8 will be described. In the following description, a row of each table may be referred to as a record. The vehicle monitoring TBL 405 and the composition management TBL 407 are mainly based on the aggregated data 601. That is, it is a table relating to a train that is actually running. On the other hand, the program monitoring TBL 408 and the area-specific TBL 406 are based on monitoring requests from the monitoring program. Records for each table are automatically generated.
(1) The record of the vehicle monitoring TBL 405 is registered in S51 of FIG.
(2) The area-specific TBL 406 record is registered in S34 of FIG.
(3) The record of the composition management TBL 407 is registered in S43 of FIG.
(4) The record of the program management TBL 408 is registered in S32 of FIG.

(Vehicle monitoring TBL405)
FIG. 5 shows the structure of the vehicle monitoring information management table 405 (mounting attribute management information). The record of the vehicle monitoring TBL 405 includes a monitoring bit string 11 (second device designation information), a line segment 12 of the train that is actually traveling (first mounting attribute), and a division 13 of the organization (second mounting attribute) )including. The vehicle monitoring TBL 405 has first and second plural (two in this example) mounting attributes. The vehicle monitoring TBL 405 is composed of a row of monitoring target device information 11, a row of line sections 12, and a row of wards 13. Each row is a record (mounting attribute correspondence information). The vehicle monitoring TBL 405 assigns a bit to each device on the vehicle and manages the monitoring target device on the vehicle by turning on the bit of the device requested to be monitored from the monitoring terminal 501. This bit string is the monitoring target device information 11. Hereinafter, as described at the beginning, the monitoring target device information 11 is also referred to as a “monitoring bit string 11”. Further, the vehicle monitoring TBL 405 includes information on the line segment 12 of the vehicle to which the monitoring bit string 11 is applied and the division 13 to which the vehicle to which the monitoring bit string 11 is applied belongs. Although details will be described later with reference to FIG. 14, the record of the vehicle monitoring TBL 405 is registered in S51 of FIG. As described in S <b> 51 of FIG. 14, among the records of the vehicle monitoring TBL 405, “Line 12, affiliated ward 13” is “Line 12, affiliated ward 13” of the received aggregated data 601. Therefore, “line ward 12, affiliated ward 13” is “line ward 12, affiliated ward 13” of the running train. On the other hand, the monitoring bit string 11 (405) of the record of the vehicle monitoring TBL 405 is caused by the monitoring bit string 11 (408) of the program monitoring TBL 408 as described later with reference to FIG. The monitoring bit string 11 (405) is an “OR” (union) of “a device whose line section 12 (405) is a monitoring area” and “a device whose belonging section 13 (405) is a monitoring area”. .

(Monitored device information table by area 406)
FIG. 6 shows the structure of the area-specific monitoring target device information table 406 (attribute-specific management information). The area-specific TBL 406 includes information (columns) of a monitoring bit string 11 (first device designation information), a line segment 12 (designated attribute), and an assigned district 13 (designated attribute). Each line is a record. The area-specific TBL 406 separately manages the line 12 and the affiliation of the monitoring target area requested from the monitoring terminal 501. That is, in the vehicle monitoring TBL 405, both the line section 12 and the section 13 to which the organization belongs are associated with one monitoring bit string 11 (405), but the area-specific TBL 406 has one monitoring Either the line segment 12 or the district to which the vehicle belongs is associated with the bit string 11 (406).

(Knitting management table 407)
FIG. 7 shows the structure of the composition management table 407 (train management information). The organization management TBL 407 is composed of information (columns) of organization number 15 (train identification information), line section 12 (installation attribute), affiliation section 13 (installation attribute), and branch office 14 (installation attribute). Each row is a record (train correspondence information). The branch office 14 is an upper group of the ward office 13, and one branch office is composed of a plurality of ward offices 13. The composition management TBL 407 has a record of the number of compositions that the aggregated data 601 received by the ground monitoring server 400 actually travels on the train.

(Monitoring program management table 408)
FIG. 8 shows the structure of the monitoring program management table 408 (monitoring program management information). The program management TBL 408 includes information (monitoring program identification information 16) for identifying the monitoring program that has transmitted the “monitoring request” from the monitoring terminal 501; the monitoring bit string 11 (first device monitoring information) of the monitoring target device specified by the program; Is composed of a row of areas to be monitored (line section 12 or affiliated section 13) designated. The “line section 12 or affiliation section 13” is an example, and these are designation attributes indicating attributes that the organization (train) equipped with the equipment designated by the monitoring bit string 11 (408) should have. Each row is a record (monitoring program correspondence information). The program management TBL 408 has as many records as the number of programs that have transmitted a monitoring request. As will be described later with reference to FIG. 11, the record of the program management TBL 408 is registered in S32 of FIG.

(Description of operation)
Next, the operation will be described. Here, an example will be described in which the knitting to be monitored is designated by the line ward 12, the affiliation ward 13 or the branch office 14 which is a higher group of the affiliation ward 13, and a plurality of knitting belonging thereto is monitored. In addition, the monitoring program (also referred to as an application) of the ground monitoring terminal 501 monitors some of a plurality of devices on the vehicle. The monitoring here is a function of notifying the application of the monitoring terminal 501 when an event to be notified to the monitoring terminal 501 such as the occurrence of a device failure occurs on the vehicle. Monitoring by the monitoring program is not an operation of constantly monitoring the state on the vehicle.

(Operation of Data Aggregation Device 100)
First, the operation of aggregating data of on-board equipment and transmitting it to the ground monitoring server 400 by the on-vehicle (mounted on the vehicle) data aggregating apparatus 100 will be described. 9 and 10 are flowcharts of a transmission process in which the data aggregating apparatus 100 collects on-board equipment data and transmits the aggregated data 601 to the ground monitoring server 400.

(Operation of data aggregation device 100: A)
In the data aggregating apparatus 100, two threads operate, and data generated in the equipment on the vehicle is collected by one thread (FIG. 9) (S11) and stored in the data storage unit 101 (S12). The data generation cycle of on-board equipment varies depending on the equipment. Here, the data aggregating apparatus 100 accumulates every time data is generated, and the data of the same device is overwritten and saved in the data accumulating unit 101. In the other thread (FIG. 10), the data aggregating apparatus 100 waits for the time processing of the data transmission interval to the ground set in advance (S21). The data aggregation unit 102 creates the device specific information part 6013 of the aggregated data 601 from the latest device data stored in the data storage unit 101 (S22). Further, the basic information part 6011 and the common information part 6012 are created from the information registered on the vehicle and the running data, and are integrated into one data format as the aggregated data 601 (S23). The data transmission unit 103 transmits the aggregated data 601 created in S23 to the ground monitoring server 400 using wireless communication (S24).

(Operation related to monitoring request: B-1)
Next, an operation in which the program of the monitoring terminal 501 transmits the “monitoring request 510” of the on-board equipment to the ground monitoring server 400 will be described.

FIG. 11 is a flowchart of the operation of the monitoring request processing unit 403 of the ground monitoring server 400 when the program of the monitoring terminal 501 transmits the “monitoring request 510” of the on-board equipment to the ground monitoring server 400. Further, S32 in FIG. 11 is a process for registering a record in the program management BL408. Further, S34 in FIG. 11 is a process of registering a record in the area-specific TBL 406. The subject of the operation in FIG. 11 is the monitoring request processing unit 403.

FIG. 12 is a diagram showing changes in data of the program management TBL 408, the area-specific TBL 406, and the vehicle monitoring TBL 405 in the flow of FIG. FIG. 13 shows the data structure of the monitoring request 510.

The monitoring program of the monitoring terminal 501 transmits the “monitoring request 510” of FIG. 13 to the ground monitoring server 400 at the start of vehicle monitoring. As shown in FIG. 13, the monitoring request 510 includes monitoring program identification information 511 (used for monitoring program identification information 16) for identifying a program, device identification information 512, and monitoring area information 513.
(1) The monitoring program identification information 511 is information for identifying the monitoring program that has transmitted the monitoring request 510. In FIG. 13, it is “PG4”.
(2) The device identification information 512 is information for identifying an on-vehicle device that the monitoring program requests to monitor. The device identification information 512 corresponds to the device information 1, 2 and the like included in the aggregated data 601. In FIG. 13, it is “device 5”.
(3) The monitoring area information 513 is information for designating the monitoring area of the organization such as the line ward 12 or the affiliated ward office 13 or the branch office 14 which organization is to be monitored. In FIG. 13, “line ward 12 = Tokaido line”, and the ward office 13 and the branch office 14 are not specified.

(S31)
When receiving the monitoring request 510 from the monitoring terminal 501, the monitoring request processing unit 403 refers to the device identification information 512 and generates the monitoring bit string 11 in which the monitoring device specified by the device identification information 512 is changed to a bit string (S 31). . To explain in a simplified manner, since it is “device 5” in FIG. 13, the monitoring request processing unit 403 uses the monitoring bit string 11 of <010000> as shown in FIG. 12 (monitoring bit string 11 of PG 4 of the program management TBL 408). Generate.

(S32)
S32 is a step of registering a record in the program management BL408. The monitoring request processing unit 403 sets the monitoring program identification information 16 for identifying the program of the monitoring terminal 501, the monitoring bit string 11 generated in S31, and the monitoring area (line section 12 or affiliated section 13) designated from the monitoring program. The added record is added to the program management BL 408 (S32, S32 in FIG. 12). In FIG. 12, the fifth line (PG4) of the program management TBL 408 is an added record. When the branch office 14 is designated as the monitoring area, the monitoring request processing unit 403 expands to the ward offices belonging to the branch office, and adds records to the program management TBL 408 as many as the ward offices. The monitoring request processing unit 403 has information on wards belonging to the branch office 14.

(S33)
The monitoring request processing unit 403 refers to the program management TBL 408, and extracts a record of the same line segment 12 (the affiliated district 13 when the affiliated district 13 is added) as the added record (S33). In FIG. 12, a record of “line section 12 = Tokaido line” is extracted from the program management BL408.

(S34)
The monitoring request processing unit 403 calculates the logical sum (union of designated devices) of the monitoring bit string 11 (408) of the extracted record. Then, the monitoring request processing unit 403 uses the newly calculated monitoring bit string 11 (408) for the monitoring bit string 11 (406) of the corresponding line section 12 of the TBL 406 for each area (the belonging section 13 in the case of the belonging section 13). Rewriting is performed (S34, S34 in FIG. 12). When there is no record corresponding to the area-specific TBL 406, a record having the contents of the record newly added to the composition management TBL 407 is registered in the area-specific TBL 406. In FIG. 12, since the extracted records are in the first, second, and fifth rows, the logical sum of these monitoring bit strings 11 (408) is <110100> (S34). Since the record in the first row of the area-specific TBL 406 has the same line 12 (Tokaido Line), the monitoring bit string 11 of the record in the first row is changed to the logical sum <110100>.

(S35)
The monitoring request processing unit 403 extracts, from the vehicle monitoring TBL 405, a record of the same line 12 as the line 12 of the area-specific TBL 406 updated in S34 (the assigned ward 13 in the case of the assigned ward 13) (S35). In FIG. 12, since the record in the first row (Tokaido Line) is updated in S34, the record (line 1, 3) of “Line 12 = Tokaido Line” is extracted from the vehicle monitoring TBL 405.

(S36)
Next, the record of the same affiliation 13 as the affiliation 13 of the record extracted from the vehicle monitoring TBL 405 in S35 (or the line ward 12 when extracted in the affiliation 13) is extracted from the TBL 406 by area (S36). ). In FIG. 12, in the area-specific TBL 406, the same ward 13 as the record of “first row, third row” extracted from the vehicle monitoring TBL 405 is “Kunitsu train ward” only. Therefore, the record (Kokutsu train ward) on the fourth line of the TBL 406 by area is extracted.

(S37)
Of the records extracted from the vehicle monitoring TBL 405 in S35, the monitoring request processing unit 403 records a record in which the same record of “line section 12, section 13” exists in the TBL 406 by area (in FIG. 12, one line of the vehicle monitoring TBL 405). The monitoring bit string 11 of the area-specific TBL 406 changed in S34 (the first line of the area-specific TBL 406 in FIG. 12) and the monitoring bit string 11 extracted from the area-specific TBL 406 in S36 (the fourth line of the area-specific TBL 406 in FIG. 12) ) (Union set of designated devices). The logical sum in FIG. 12 is <110110> because it is the logical sum of the first and fourth rows of the area-specific TBL 406. The monitoring request processing unit 403 rewrites the result as a new monitoring bit string 11 (405) of the vehicle monitoring TBL 405 (S37, S37 in FIG. 12). In FIG. 12, the monitoring bit string 11 in the first row of the vehicle monitoring TBL 405 is changed to <110110>.

(In case of changing the line while the train is running: B-2)
Next, the operation of the ground monitoring server 400 when the line segment 12 of the running vehicle is changed will be described. FIG. 14 is a flowchart when the line section is changed. Further, S43 in FIG. 14 is a process of registering a record in the composition management TBL 407. Moreover, S51 of FIG. 14 is a process in which a record is registered in the vehicle monitoring TBL 405. The subject of the operation in FIG. 14 is the data receiving unit 401.

FIG. 15 shows changes in data of the composition management TBL 407, the area-specific TBL 406, and the vehicle monitoring TBL 405 at that time.

(S41, S42)
When the data reception unit 401 of the ground inspection server receives the aggregated data 601 (also referred to as the received aggregated data 601) from the vehicle, a record having the same organization number 15 as the organization number 15 of the received aggregated data 601 is stored in the organization management TBL407. It is checked whether or not it exists (S41, S42).

(S43)
If the record having the same composition number 15 as the reception aggregated data 601 does not exist in the composition management TBL 407 (NO in S42), the data receiving unit 401 describes the composition number 15 and line segment 12 described in the reception aggregated data 601. The branch office 14 and the assigned ward office 13 are added as data to the row of the organization management TBL 407 (S43).

(S44, S45)
If there is a record having the same composition number 15 as the reception aggregated data 601 in the composition management TBL 407 (YES in S42), does the line segment 12 of the reception aggregated data 601 match the line segment 12 of the composition management TBL407? Is checked (S44). If the line sections 12 match (YES in S44), the process ends. In FIG. 15, it is assumed that the reception aggregated data 601 is the organization number 15 = 2, line segment 12 = Takasaki line, and affiliated district 13 = Kokutsu train district. If the line segments do not match (NO in S44), the line segment 12 of the corresponding record in the composition management TBL 407 is changed to the line segment 12 in the reception aggregated data 601 (S45, S45 in FIG. 15). In FIG. 15, since the line segment 12 does not match, the data reception unit 401 changes the line segment 12 of the second row record of the composition management TBL 407 from the Tokaido line to the Takasaki line.

(S46, S47, S48)
Next, the data receiving unit 401 refers to the area-specific TBL 406 to check whether the same record exists as the line 12 or the assigned ward 13 of the received aggregated data 601 (S46, S47). In FIG. 15, the line 12 (Takasaki Line) or the affiliation 13 (Kokutsu Train Ward) of the received aggregated data 601 is present in the area-specific TBL 406 (lines 3 and 4). Therefore, in the case of FIG. 15, the process proceeds from S47 to S49. If the same record as the line 12 and the affiliation 13 of the aggregated data 601 does not exist in the area-specific TBL 406 (NO in S47), the monitoring bit string 11 of all 0s is generated (S48). This monitoring bit string 11 is used in S50.

(S49)
When the same record as the line 12 and the affiliation 13 of the reception aggregated data 601 exists in the area-specific TBL 406 (YES in S47), the data reception unit 401 refers to the vehicle monitoring TBL 405. Then, it is checked whether there is a record in the vehicle monitoring TBL 405 that has “line section 12, affiliation section 13” of the received aggregated data 601 (S49). If a record exists, the process ends (YES in S49). In FIG. 15, it is assumed that there is no record in the check in S49. The record in the third row of the vehicle monitoring TBL 405 in FIG. 15 is a record registered in S51 below.

(S50, S51)
When the vehicle monitoring TBL 405 does not include the record of the line 12 and the affiliation 13 of the reception aggregated data 601 (NO in S49), the following processing is executed. The data receiving unit 401 calculates the logical sum (the union of designated devices) of the monitoring bit strings 11 of the records in the same line section 12 and the same belonging section 13 as the received aggregated data 601 extracted from the area-specific TBL 406 ( S50). In FIG. 15, since the records in the third and fourth rows of the TBL 406 for each area are extracted in S46, the logical sum of these monitoring bit strings 11 is calculated. That is, <001110> is calculated. Then, the data receiving unit 401 adds a record in which the monitoring bit string 11 (logical sum) calculated in S50, the line section 12 and the belonging section 13 of the received aggregated data 601 is set to the vehicle monitoring TBL 405 (S51, S51 of FIG. 15). FIG. 15 is a record in which the record in the third row of the vehicle monitoring TBL 405 is newly added.

The case where records are initially registered in the composition management TBL 407 and the vehicle management table 405 will be described with reference to the flowchart of FIG. 14 and FIG.

(S42)
In the initial case, since the record having the same composition number 15 as the received aggregated data 601 does not exist in the composition management TBL 407, the process proceeds to S43. In S43, the data reception unit 401 adds the composition number 15, line segment 12, branch office 14, affiliated division 13 and the like described in the reception aggregated data 601 as data to the row of the composition management TBL 407. In FIG. 16, a record is registered in the first line of the composition management TBL 407. The process proceeds to S46.

(S46)
The data receiving unit 401 refers to the area-specific TBL 406 to check whether the same record as the line 12 or the affiliated ward 13 of the received aggregated data 601 exists, but in FIG. The same record as the line ward 12 (Takasaki Line) or the affiliation ward 13 (Kokutsu train ward) is not in the TBL 406 by area. Therefore, the data receiving unit 401 generates the monitoring bit string 11 <000000> (S48).

(S49)
In FIG. 16, there is no record in the vehicle monitoring TBL 405 that is the same as the line 12 (Tokaido Line) or the affiliated ward 13 (Kokutsu train ward) in the received aggregated data 601.

(S50, S51)
The data receiving unit 401 uses <000000> calculated in S48 because no record was extracted in S46 (S50). The data receiving unit 401 adds to the vehicle monitoring TBL 405 a record having the monitoring bit string 11 calculated in S50 (S000000 passes because it passes S48), the line 12 of the received aggregated data 601 and the affiliation 13 (S51). . In FIG. 16, the record in the first row of the vehicle monitoring TBL 405 is a newly added record.

(Monitoring operation by the ground monitoring server 400: B-3)
Finally, the operation in which the ground monitoring server 400 receives the aggregated data 601 from the vehicle and monitors a plurality of devices will be described.

FIG. 17 is a flowchart in which the data monitoring unit 402 of the ground monitoring server 400 receives the aggregated data 601 from the data aggregating apparatus 100 and monitors a plurality of devices. The subject of the operation in FIG. 17 is the data monitoring unit 402. FIG. 18 shows a data reference relationship when the data monitoring unit 402 executes monitoring of a plurality of devices.

When receiving the aggregated data 601 from the data aggregating apparatus 100, the data receiving unit 401 passes the received aggregated data 601 to the data monitoring unit 402 after completion of the travel vehicle line segment change process shown in FIG. 14, and requests the monitoring process.

(S61)
The data monitoring unit 402 determines whether or not a monitoring target event has occurred (in this example, whether or not a failure has occurred) from each piece of device information (device information 1 and 2 in FIG. 4) of the received aggregated data 601. Whether or not a monitoring target event has occurred can be determined by monitoring changes in the aggregated data 601 (device information 1 and 2) transmitted from the data aggregating apparatus 100 at a predetermined interval (FIG. 10). If the data monitoring unit 402 determines that an event has occurred, the data monitoring unit 402 generates monitoring target device information 11 (hereinafter referred to as a failure bit string 11-1) in which all bits are “0”. Aggregated data 601 having device information determined to be an event occurrence is detected aggregated data. Naturally, the device corresponding to the bit in the failure bit string 11-1 is the same as the monitoring bit string 11. The data monitoring unit 402 turns on the bit corresponding to the device determined to have a failure among the bits of the failure bit string 11-1 of all bits “0” (S61, S61 in FIG. 18). In the example of FIG. 18, the failure bit string 11-1 is “000100”.

(S62, S63)
If all bits of the failure bit string 11-1 are off, it is determined that an event (failure) to be notified to the monitoring terminal 501 has not occurred, and the data monitoring unit 402 ends the process (YES in S62).
In the example of FIG. 18, the process proceeds to S63. If there is an on-bit in the failure bit string 11-1 (NO in S62), the data monitoring unit 402 reads from the vehicle monitoring TBL 405 “line segment 12, belonging district 13 of received aggregated data 601 (detected aggregated data)”. ”Is extracted (S63). In the example of FIG. 18, the record in the first row is extracted from the vehicle monitoring TBL 405.

(S64)
Then, the data monitoring unit 402 calculates a logical product of the failure bit string 11-1 created in S61 of FIG. 17 and the monitoring bit string 11 of the record of the vehicle monitoring TBL 405 extracted in S63 (S64). In the example of FIG. 18, the logical product of “000100” and “100110” is calculated. That is, <000100> AND <100110> = <000100>.

(S65, S66)
If this result is 0 (all bits are OFF) (YES in S65), the monitoring program of the monitoring terminal 501 that monitors the event of the corresponding device of this organization (the organization of the transmission source of the received aggregated data 601) is It is determined that it does not exist, and the process ends. If the result of the logical product is other than 0 (there is a bit that is turned on) (NO in S65), the data monitoring unit 402 sets the corresponding device of this organization (the organization of the transmission source of the received aggregated data 601). It is determined that there is a monitoring program that monitors the event. In this example, the result of the logical product of S64 is <000100>, so it is determined that the monitoring program exists. If there is a monitoring program, the data monitoring unit 402 extracts (searches) one record from the program management TBL 408 that has the same “line 12 or affiliation 13” in the received aggregated data 601 (S66). . The search processing is performed after S65 (S66 to S70).

(S67)
If there is no record in program management TBL 408 (NO in S67), the process ends. If there is a record (YES in S67), the process proceeds to S68. In the example of FIG. 18, the records of the first to third lines are extracted from the program management TBL 408, and the process proceeds to S68.

(S68)
The data monitoring unit 402 calculates the logical product of the monitoring bit string 11 (408) of the record extracted from the program management TBL 408 and the failure bit string 11-1 (S68). In the example of FIG. 18, the data monitoring unit 402 calculates a logical product of each monitoring bit string 11 in the first to third rows of the program management TBL 408 and <000100> (logical product of S64).

(S69)
If the logical product of S68 is 0 (YES in S69), it is determined that the corresponding program managed by the program management TBL 408 is not monitoring the event. Then, returning to the process of S66, the data monitoring unit 402 extracts from the program management TBL 408 the next record in which either “Line 12 or affiliation 13” of the received aggregated data 601 is the same, and executes the same process. To do. In the example of FIG. 18, only the logical product of the monitoring bit string 11 <000100> in the first row of the program management TBL 408 and <000100> (logical product of S64) is not zero.

(S70)
If the result of the logical product is other than 0 (YES in S69), the data monitoring unit 402 determines (identifies) that the corresponding program of the program management TBL 408 is monitoring the event (fault) that has occurred, and notifies the abnormality. A notification to the monitoring program is requested to the unit 404 (S70). In the example of FIG. 18, the logical product with the record in the first row of the program management TBL 408 is not zero. Therefore, the data monitoring unit 402 determines that the monitoring program 1 (PG1) is monitoring a failure that has occurred, and requests the abnormality notification unit 404 to notify the monitoring program 1 (PG1). In the example of FIG. 18, since the logical product of S68 is <000100>, it can be seen that a failure has occurred in the third bit device of the monitored device information 11 (408) of “PG1”.

After the abnormality notification unit 404 notifies the requested program of the occurrence of the abnormality, the data monitoring unit 402 returns to the record extraction processing from the program management TBL 408 in S66, and the “line 12 , Belonging ward 13 ”carries out the extraction processing of the next record that is the same.

The processing from S66 to S70 is performed for all the records of the program management TBL 408 in which either of the “line 12 and affiliation 13” of the received aggregated data 601 is the same.

As described above, the data aggregating apparatus 100 aggregates data of a plurality of devices on the vehicle and sends them to the ground. The ground monitoring server 400 receives monitoring requests 510 from a plurality of ground monitoring programs and performs on-vehicle monitoring. For this reason, there are the following effects.

(1) The data aggregating apparatus 100 transmits aggregated data 601 in which data on the vehicle is aggregated.
On the ground side that receives the aggregated data 601, the ground monitoring server 400 responds to the monitoring requests 510 from the individual monitoring programs and performs monitoring processing as a representative. For this reason, it is not necessary for the ground monitoring program to individually communicate with the vehicle, and efficient communication is possible in wireless communication with a limited bandwidth.
(2) A certain monitoring area (attribute of the monitoring target device) such as a composition belonging to a certain line section 12 (monitoring area) or a composition belonging to a certain section 13 (monitoring area) by area-specific TBL406 and vehicle monitoring TBL405. ) Can be monitored together.
(3) The monitoring target device of each organization is different depending on the attribute of the organization in which the monitoring target devices such as the line ward 12 and the affiliated ward 13 are equipped. However, it is not necessary to manage the monitoring target device information 1, the device information 2, and the like for each organization by the vehicle monitoring TBL 405 and the monitoring bit sequence 11 that represents the monitoring target device mounted on the vehicle in a bit sequence. Therefore, the management burden is reduced. Also, high-speed vehicle monitoring can be performed on the ground side by bit calculation.

Embodiment 2. FIG.
The second embodiment will be described with reference to FIG. In the second embodiment, the hardware configuration of the data aggregation device 100 and the ground monitoring server 400, which are computers, will be described. Both the data aggregation device 100 and the ground monitoring server 400 are computers and have the same configuration. Therefore, although the ground monitoring server 400 will be described below as an example, the description of the ground monitoring server 400 also applies to the data aggregation device 100.

In FIG. 19 showing hardware resources, the ground monitoring server 400 includes a CPU 810 (Central Processing Unit) that executes a program. The CPU 810 is connected to a ROM (Read Only Memory) 811, a RAM (Random Access Memory) 812, a display device 813, a keyboard 814, a mouse 815, a communication board 816, a CDD 818, and a magnetic disk device 820 via a bus 825. Control hardware devices. Instead of the magnetic disk device 820, a storage device such as an optical disk device or a flash memory may be used.

The RAM 812 is an example of a volatile memory. Storage media such as the ROM 811, the CDD 818, and the magnetic disk device 820 are examples of nonvolatile memories. These are examples of a data storage unit or storage unit, storage unit, and buffer. The communication board 816, the keyboard 814, and the like are examples of an input unit and an input device. The communication board 816, the display device 813, and the like are examples of an output unit and an output device.

The magnetic disk device 820 stores an operating system 821 (OS), a window system 822, a program group 823, and a file group 824. The programs in the program group 823 are executed by the CPU 810, the operating system 821, and the window system 822.

The OS 821 and the program group 823 store programs that execute the functions described as “unit” in the description of the above embodiments. The program is read and executed by the CPU 810.

The file group 824 includes, as described in the above embodiment, “determination result”, “calculation result”, “extraction result”, “generation result”, and “processing result”. The described information, data, signal values, variable values, parameters, and the like are stored as items of “˜file” and “˜database”. The “˜file” and “˜database” (for example, various tables such as the vehicle monitoring TBL 405) are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 810 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.

In the description of the embodiment described above, the data and signal values are the memory of the RAM 812, the compact disk of the CDD 818, the magnetic disk of the magnetic disk device 820, other optical disks, mini disks, and DVDs (Digital Versatile Disk). Or the like. Data and signals are transmitted on-line via the bus 825, signal lines, cables, and other transmission media.

In the above description of the embodiment, what has been described as “to part” may be “to means”, and “to step”, “to procedure”, and “to process”. May be. That is, what has been described as “˜unit” may be implemented by software alone, a combination of software and hardware, or a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 810 and executed by the CPU 810. In other words, the program causes the computer to function as the “˜unit” described above. Alternatively, it causes the computer to execute the procedures and methods of “to” described above.

In the above embodiment, the data aggregation device 100 and the ground monitoring server 400 have been described, but it is also possible to grasp the operation of these devices as a method. It is also possible to grasp the operation of these devices as a program.

11 monitoring bit string, 12 line ward, 13 ward, 14 branch office, 15 organization number, 16 monitoring program identification information, 601 aggregation data, 6011 basic information part, 6012 common information part, 6013 device specific information part, 100 data aggregation device, 101 data storage unit, 102 data aggregation unit, 103 data transmission unit, 1000 train equipment monitoring system, 201 on-board equipment, 202 transmission / reception device, 301 wireless base station, 400 ground monitoring server, 401 data receiving part, 402 data monitoring part, 403 monitoring request processing unit, 404 abnormality notification unit, 405 vehicle monitoring TBL, 406 TBL by area, 407 organization management TBL, 408 program management TBL, 501 monitoring terminal, 510 monitoring request, 511 monitoring program identification information 512 device identification information, 513 monitoring area information.

Claims

Mounted on each train of a plurality of trains on a track composed of one or more vehicles, train identification information for identifying the mounted train, a mounting attribute indicating a predetermined attribute of the mounted train, From each mounting device that transmits aggregate data including train device information that identifies each device of a plurality of devices equipped on the mounted train and represents the state of each device, at a predetermined time interval, A data receiver for receiving the aggregated data;
Detection that detects the aggregated data in which a predetermined event has occurred in any of the devices identified from the train device information as detected aggregated data based on the train device information of the aggregated data received by the data receiving unit And
First device designation information in which at least one of the devices is designated as a monitoring target by a monitoring program that requests monitoring of the specific device, monitoring program identification information that identifies the monitoring program, and the first device designation information include A storage for storing monitoring program management information for each of the monitoring programs of the plurality of monitoring programs having monitoring program correspondence information associated with a specified attribute indicating an attribute that the train to be equipped with the equipment to be specified has. And
The specified attribute of the attribute indicated by the mounted attribute included in the detection aggregated data, and the first equipment designation information in which the device in which the event has occurred indicated by the train equipment information of the detection aggregated data is specified. And a specifying unit that specifies a monitoring program for notifying the device that the event has occurred by executing a search process for searching for the monitoring program correspondence information from the monitoring program management information. A monitoring program identification device.
Each said mounting device is
2. The communicably connected to a plurality of devices equipped on the train, the aggregated data is automatically generated, and the automatically generated aggregated data is transmitted at the determined time interval. Monitoring program specific device.
The storage unit further includes:
The mounting attribute is associated with second device designation information in which at least one device requested to be monitored by the monitoring program among the devices equipped on the train having the mounting attribute is designated as a monitoring target. Storing mounting attribute management information having the mounting attribute corresponding information for each of the different mounting attributes,
The specific part is:
The mounting attribute correspondence information including the mounting attribute included in the detection aggregated data and the second device designation information in which the device in which the event indicated by the train device information of the detection aggregated data occurs is designated. Whether the mounting attribute management information is present before the search process is executed. If the result of the confirmation is that the mounting attribute correspondence information does not exist, the search process is not started, and the mounting attribute correspondence information exists. The monitoring program specifying device according to claim 1, wherein the search process is started when the search is performed.
The mounting attribute correspondence information of each of the mounting attribute management information is
It has a plurality of different loading attributes for the train that is actually operating,
The aggregated data is
Including a plurality of different mounting attributes,
The specific part is:
The mounting having all of the plurality of mounting attributes included in the detection aggregated data, and the second device designation information in which the device in which the event indicated by the train equipment information of the detection aggregated data occurs is designated. Whether or not the attribute correspondence information is included in the mounting attribute management information is confirmed before execution of the search process. If the result of the confirmation is that the mounting attribute correspondence information does not exist, the search process is not started, 4. The monitoring program specifying device according to claim 3, wherein the search process is started when correspondence information exists.
The storage unit further includes:
Attribute-specific management information having attribute-specific correspondence information in which the designated attribute is associated with the first device designation information for each different designated attribute;
Each of the monitoring programs of the plurality of monitoring programs is
A monitoring request including the first device designation information, the monitoring program identification information, and the designation attribute;
The monitoring program specifying device further includes:
The monitoring request is received, new monitoring program correspondence information is generated from the received monitoring request and added to the monitoring program management information, and the designation that is the same as the designation attribute of the added monitoring program correspondence information The monitoring program correspondence information having attributes is extracted from the monitoring program management information, and designated as the monitoring target by the first device designation information of the extracted monitoring program correspondence information and the newly added monitoring program correspondence information The specified attribute of the newly added monitoring program correspondence information is added to the attribute-specific correspondence information of the attribute-specific management information of the storage unit. The attribute-specific correspondence information is replaced as the first device designation information, and the first device designation information is replaced. The mounting attribute correspondence information having the mounting attribute of the attribute indicated by the specified attribute of the attribute-specific correspondence information is extracted from the mounting attribute management information, and the mounting attribute included in the extracted mounting attribute correspondence information is included. The attribute-specific correspondence information is extracted from the attribute-specific management information, and the first device designation information of the extracted attribute-specific correspondence information and the first device designation information replaced with the union are designated. The union of the devices is obtained, and the result of the obtained union is obtained from the mounting attribute correspondence information having the mounting attribute of the attribute indicated by the designated attribute of the attribute-specific correspondence information in which the first device designation information is replaced. The monitoring program specifying device according to claim 4, further comprising a monitoring request processing unit to be replaced as second device designation information.
The storage unit further includes:
Train management information having train correspondence information in which the train identification information and the plurality of mounted attributes are associated with each other for the different train identification information,
The aggregated data is
Among the plurality of mounting attributes, including the mounting attributes that can be changed to other attributes according to the travel of the train,
The data receiver is
When receiving the aggregated data,
The train correspondence information having the train identification information included in the received aggregated data is extracted from the train management information, and the plurality of mounted attributes of the extracted train correspondence information and included in the received aggregated data Determine whether the mounting attributes match,
When it is determined that they do not match, the installed attribute of the extracted train correspondence information is matched with the mounted attribute included in the received aggregated data,
Extracting the attribute-specific correspondence information having the mounted attribute included in the received aggregated data from the attribute-specific management information,
By referring to the mounting attribute management information, the mounting attribute correspondence information having the mounting attribute included in the received aggregated data is searched, and when the mounting attribute correspondence information is not found, the attribute-specific management information is used. The union of the devices specified as the monitoring target by the first device designation information of the extracted attribute-specific correspondence information is obtained, and the result of the obtained union is included as the second device designation information. The monitoring program specifying device according to claim 5, wherein new mounting attribute correspondence information having the mounting attribute included in the aggregated data is added to the mounting attribute management information.
Mounted on each train of a plurality of trains on a track composed of one or more vehicles, train identification information for identifying the mounted train, a mounting attribute indicating a predetermined attribute of the mounted train, Each mounted apparatus that identifies each device of a plurality of devices mounted on the mounted train and transmits aggregate data including train device information that represents the state of each device at a predetermined time interval;
A data receiving unit that receives the aggregated data from each of the mounted devices;
Detection that detects the aggregated data in which a predetermined event has occurred in any of the devices identified from the train device information as detected aggregated data based on the train device information of the aggregated data received by the data receiving unit And
First device designation information in which at least one of the devices is designated as a monitoring target by a monitoring program that requests monitoring of the specific device, monitoring program identification information that identifies the monitoring program, and the first device designation information include A storage for storing monitoring program management information for each of the monitoring programs of the plurality of monitoring programs having monitoring program correspondence information associated with a specified attribute indicating an attribute that the train to be equipped with the equipment to be specified has. And
The designation attribute of the attribute indicated by the mounted attribute included in the detection aggregated data, and the first equipment designation information in which the equipment in which the event has occurred indicated by the train equipment information of the detection collection data is designated. A monitoring program specifying unit comprising: a specifying unit that specifies a monitoring program for notifying that the event has occurred to the device by executing a search process for searching the monitoring program correspondence information having the monitoring program management information. Train equipment monitoring system.
Each said mounting device is
8. The plurality of devices equipped on the train are communicably connected, the aggregated data is automatically generated, and the automatically generated aggregated data is transmitted at the determined time interval. Train equipment monitoring system.
In the monitoring program specifying method performed by the monitoring program specifying device including the data receiving unit, the detecting unit, the storage unit, and the specifying unit,
(1) The data receiving unit is mounted on each train of a plurality of trains on a track composed of one or more vehicles, train identification information for identifying the mounted train, and the installed train Aggregated data including a mounting attribute indicating a predetermined attribute and train device information that identifies each device of a plurality of devices equipped on the mounted train and represents the state of each device, at a predetermined time interval Receiving the aggregated data from each mounted device to transmit,
(2) The aggregated data in which the detection unit has generated a predetermined event in any of the devices identified from the train device information based on the train device information of the aggregated data received by the data receiving unit. Are detected as aggregated data,
(3) First storage device designation information in which at least one device is designated as a monitoring target by a monitoring program that requests monitoring of the specific device, and monitoring program identification information that identifies the monitoring program. The monitoring program correspondence information associated with the designation attribute indicating the attribute to be possessed by the train equipped with the equipment designated by the first equipment designation information is provided for each of the monitoring programs of the plurality of the monitoring programs. Store monitoring program management information,
(4) The specific unit has specified the specified attribute of the attribute indicated by the mounted attribute included in the detection aggregated data and the equipment in which the event indicated by the train equipment information of the detection collection data has occurred. Specifying a monitoring program for notifying the device that the event has occurred by executing a search process for searching the monitoring program management information for the monitoring program correspondence information having the first device designation information. A monitoring program specifying method characterized by the above.
Computer
Mounted on each train of a plurality of trains on a track composed of one or more vehicles, train identification information for identifying the mounted train, a mounting attribute indicating a predetermined attribute of the mounted train, From each mounting device that transmits aggregate data including train device information that identifies each device of a plurality of devices equipped on the mounted train and represents the state of each device, at a predetermined time interval, A data receiver for receiving the aggregated data,
Detection that detects the aggregated data in which a predetermined event has occurred in any of the devices identified from the train device information as detected aggregated data based on the train device information of the aggregated data received by the data receiving unit And
First device designation information in which at least one of the devices is designated as a monitoring target by a monitoring program that requests monitoring of the specific device, monitoring program identification information that identifies the monitoring program, and the first device designation information include A storage for storing monitoring program management information for each of the monitoring programs of the plurality of monitoring programs having monitoring program correspondence information associated with a specified attribute indicating an attribute that the train to be equipped with the equipment to be specified has. And
The designation attribute of the attribute indicated by the mounted attribute included in the detection aggregated data, and the first equipment designation information in which the equipment in which the event has occurred indicated by the train equipment information of the detection collection data is designated. A specifying unit for specifying a monitoring program for notifying the device that the event has occurred by executing search processing for searching the monitoring program correspondence information having the monitoring program management information;
Program to function as.