JP4460427B2 - Traffic diagram data management device, traffic diagram data editing device, and traffic diagram data management method - Google Patents

Description

  The present invention relates to a management technique for data edited by a plurality of terminals, and more particularly to a data management technique suitable for traffic schedule data.

  In Patent Literature 1, drawing data to be displayed on a plurality of terminals is divided into a plurality of meshes, an exclusive flag is managed for each mesh, and editing for a mesh for which the exclusive flag is set is given the exclusive flag. A technique for performing exclusive control of drawing data between a plurality of terminals by not accepting from terminals other than the terminals is disclosed.

  By the way, the train traffic schedule data includes time information of each station constituting the line section. Therefore, the traffic diagram data can be displayed as a graph in which the vertical axis represents each station constituting the line section and the horizontal axis represents time, that is, as drawing data. For this reason, the technique of patent document 1 can also be applied to exclusive control of traffic diagram data when editing traffic diagram data is received from a plurality of terminals.

JP-A-5-216946

  However, when the technology of Patent Document 1 is applied to exclusive control of traffic diagram data, the following problems arise. In other words, traffic schedule data is usually managed in units of effective dates. Here, in the case of a route with a large number of trains (for example, a route traveling in an urban area), several hundred to several thousand traffic schedule data may exist on the same enforcement day. Therefore, when traffic schedule data with the same enforcement date is displayed as a single drawing data on each of a plurality of terminals and editing is accepted, the drawing data is divided in order to realize exclusive control of the individual traffic diagram data. The mesh must be made small so that only one traffic diagram data is included in one mesh. For this reason, the number of meshes becomes enormous, and therefore the number of exclusion flags that must be managed for exclusive control of traffic diagram data also becomes enormous, increasing the processing load for exclusive control.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to reduce the processing load related to exclusive control of drawing data.

In order to solve the above problems, in the present invention, individual traffic diagrams included in traffic diagram data are classified hierarchically using a plurality of management items. For example, a traffic diagram data management device that receives a traffic diagram data update request from at least one traffic diagram data editing device and updates the traffic diagram data held by itself according to the received request. A traffic diagram data storage means in which a plurality of traffic schedule data of trains hierarchically classified by using an execution date, a line section, a type indicating the operation purpose, and a train number are stored, and stored in the traffic diagram data storage means The traffic diagram data transmitting means for reading out the traffic diagram data and transmitting it to the traffic diagram data editing device, the enforcement date, and the user information associated with the enforcement date are stored as an exclusion flag. Classification "exclusive flag storage means, enforcement date and line section, and user information associated with the enforcement date and line section Hierarchy “medium classification” exclusion flag storage means stored as an exclusion flag, an enforcement date, line section and type, and a hierarchy in which user information associated with the enforcement date, line section and type is stored as an exclusion flag “Sub-classification” exclusive flag storage means, the enforcement date, line section, type and train number, and the hierarchy “where the user information associated with the enforcement date, line section, type and train number is stored as an exclusion flag” Upon receipt of an exclusive flag registration request from the traffic schedule data editing device and the traffic diagram data editing device, the predetermined flag included in the exclusive flag registration request A process for searching whether or not user information associated with a specified value of a management item corresponding to the registered value is registered, and the associated user information is registered If the exclusive flag registration request and the associated user information are not registered, and the predetermined hierarchy is not the lowest hierarchy, the exclusive flag registration request includes the predetermined flag. A process for detecting whether or not a specified value of a management item of a hierarchy one level lower than that of the hierarchy is included, a case where the associated user information is not registered, and the predetermined hierarchy Is the lowest hierarchy, or when the specified value is not included in the process to detect, the user information included in the exclusive flag registration request is associated with the specified value of the management item, A process of registering as an exclusive flag in the exclusive flag storage means of a predetermined hierarchy, and a process of searching the predetermined hierarchy as a lower hierarchy if the specified value is included in the detecting process Processing for re-starting, exclusive flag registration means for executing until the exclusive flag is registered or registration is rejected, and when an update request is received from the traffic diagram data editing device, exclusive flag storage means for a predetermined hierarchy In addition, a process for searching whether or not user information associated with a specified value of a management item corresponding to the predetermined hierarchy included in the update request is registered, and the associated user information is registered. If the user information matches the information of the transmission source of the update request, and if the user information matches the information of the transmission source, the user information is stored in the traffic diagram data storage means according to the update request. A process for updating the traffic diagram data subject to the update request, a process for rejecting the traffic diagram data update when the information does not match the source information, When the attached user information is not registered, and the predetermined hierarchy is the highest hierarchy, the process of rejecting the traffic diagram data update and the associated user information are registered. If the predetermined hierarchy is not the highest hierarchy, the traffic diagram data is updated with the process of re-starting the search process with the predetermined hierarchy being one higher hierarchy, or The exclusive control means that executes until the update is rejected, wherein the exclusive flag registration means sequentially executes processes from the highest hierarchy, and the exclusive control means sequentially executes processes from the lowest hierarchy. It is a traffic diagram data management device characterized by being executed.

Further, the traffic diagram data management device of the present invention is a work storage means for storing the traffic diagram data received from the traffic diagram data management device, and the traffic diagram data stored in the work storage means is read and displayed. In addition to displaying the traffic diagram data displayed on the display device via the input device, the traffic diagram data editing request is generated in accordance with the received editing content and transmitted to the traffic diagram data management device. Traffic diagram data editing means, and the traffic diagram data editing means stores in the work storage means according to the received editing contents when the update request is not rejected by the traffic diagram data management device The traffic diagram data editing apparatus is characterized in that the traffic diagram data being updated is updated.

In addition, the traffic diagram data management device of the present invention displays the traffic diagram data editing means on the display device so that the state before editing and the state after editing of the traffic diagram data accepted for editing can be identified. This is a traffic diagram data editing device.

Further, according to the traffic diagram data management method of the present invention, the traffic diagram data management device accepts a traffic diagram data update request from at least one traffic diagram data editing device, and the traffic diagram data held by itself according to the received request. A traffic diagram data management method to be updated, wherein the traffic diagram data management device includes a plurality of management items, and traffic classified hierarchically using an enforcement date, a line section, a type indicating an operation purpose, and a train number. Traffic schedule data storage means in which a plurality of timetable data are stored, an enforcement date, and user information associated with the enforcement date are stored as an exclusion flag. Exclusion of day and line ward and hierarchy “medium classification” where user information associated with the enforcement date and line ward is stored as an exclusion flag Lag storage means, enforcement date, line section and type, exclusive flag storage means of hierarchy "small classification" in which user information associated with the enforcement date, line section and type is stored as an exclusion flag, and enforcement date A line zone, type and train number, and an exclusive flag storage means of the hierarchy “for each traffic diagram data” in which user information associated with the enforcement date, line zone, type and train number is stored as an exclusive flag, The traffic diagram data management method includes a step of receiving an update request from the traffic diagram data editing device, and a user information associated with a management item included in the update request with respect to an exclusive flag storage means of a predetermined hierarchy If the associated user information is registered, the user information is the information of the transmission source of the update request. And the step of updating the traffic diagram data subject to the update request stored in the traffic diagram data storage means according to the update request when the information matches the source information, If the information does not match the information of the transmission source, the step of rejecting the update of the traffic diagram data, the case where the associated user information is not registered, and the predetermined hierarchy is the highest hierarchy , Refusing to update traffic diagram data, and when the associated user information is not registered and the predetermined hierarchy is not the highest hierarchy, the predetermined hierarchy is one level higher. The step of restarting the search process as a hierarchy is executed until the traffic diagram data is updated or the update is rejected. It is a traffic schedule data management method.

  According to the present invention, it is possible to reduce the number of exclusive flags, thereby reducing the processing load related to graphic exclusive control.

  Embodiments of the present invention will be described below.

  FIG. 1 is a schematic diagram of a traffic diagram data editing management system to which an embodiment of the present invention is applied. As shown in the figure, the traffic diagram data editing management system of the present embodiment is configured by a traffic diagram management server 1 and at least one traffic diagram editing terminal 2 connected to each other via a network 3 such as the Internet. Yes.

  The traffic schedule management server 1 holds traffic schedule data of trains. In addition, the traffic diagram data is edited from the traffic diagram editing terminal 2 and the edited content is reflected in the traffic diagram data held by itself. At this time, it is possible to prevent the traffic diagram data from being edited from the traffic diagram editing terminal 2 other than the traffic diagram editing terminal 2 that has acquired the exclusion for the traffic diagram data to be edited. Exclusive control is performed.

  As illustrated, the traffic diagram management server 1 includes a network IF unit 11 for connecting to the network 3, an exclusive control unit 12, a traffic diagram DB (database) 13, an exclusion flag management DB 14, and an update information management TL. (Table) 15.

  The traffic diagram DB 13 stores traffic diagram data of trains. FIG. 2 is a diagram showing an example of registered contents in the traffic diagram DB 13. As shown in the drawing, a traffic schedule record 130 is registered in the traffic schedule DB 13 for each train. The record 130 includes a field 131 for registering a train number uniquely assigned to a train, a field 132 for registering an enforcement date (train operation date), and a field 133 for registering a line section indicating a section of a route operated by the train. And a field 134 for registering a train operation purpose (business, forwarding, etc.) and a field 135 for registering train traffic schedule data.

  The train traffic schedule data registered in the field 135 includes information on each station (each station from the first station to the last station) constituting the line area, and the departure and / or arrival time at each station. Moreover, each data registered in the fields 131 to 134 is a management item for hierarchically classifying train traffic schedule data. Traffic schedule data is broadly categorized by the date of enforcement of the field 132, the date of enforcement of the fields 132, 133, and the middle class by the line zone, the minor classification by the date of enforcement of the fields 132, 133, 134, the line zone, and the type, and The train schedule data is specified by the enforcement date, line section, type, and train number of the fields 132, 133, 134, and 131.

  The exclusive flag management DB 14 stores an exclusive flag management TL for managing exclusive control of traffic diagram data for each level of traffic diagram data of trains managed hierarchically by a plurality of management items. As described above, the traffic schedule data is hierarchically managed in four levels for each of the major classification, middle classification, minor classification, and traffic schedule data. For this reason, the exclusive flag management TL is also provided for each of the four hierarchies of classification, middle classification, small classification, and traffic schedule data.

  FIG. 3 is a diagram showing an example of registered contents of the exclusive flag management DB 14, FIG. 3A is an example of registered contents of the exclusive flag management TL 141 corresponding to the hierarchy “major classification”, and FIG. FIG. 3C shows an example of registered contents of the exclusive flag management TL 143 corresponding to the hierarchy “small classification”, and FIG. 3D shows an example of registered contents of the exclusive flag management TL 142 corresponding to the “classification”. An example of registration contents of the exclusive flag management TL 144 corresponding to “for each diamond data” is shown.

  In the exclusive flag management TL 141, as shown in FIG. 3A, an exclusive flag record 1410 with an enforcement date as a unit is registered. The record 1410 includes a field 1411 for registering an enforcement date and a field 1415 for registering a user ID of a user who has acquired an exclusive flag for the traffic schedule data of all trains operating on the enforcement date.

  In the exclusive flag management TL 142, as shown in FIG. 3B, an exclusive flag record 1420 with the combination of the enforcement date and the line section as a unit is registered. The record 1420 includes a field 1421 for registering the enforcement date, a field 1422 for registering the line, and a user of a user who has acquired an exclusive flag for the traffic schedule data of all trains that operate the line on the enforcement date. And a field 1425 for registering an ID.

  In the exclusive flag management TL 143, as shown in FIG. 3C, an exclusive flag record 1430 with the combination of the enforcement date, the line section, and the type as a unit is registered. The record 1430 includes a field 1431 for registering an enforcement date, a field 1432 for registering a line section, a field 1433 for registering a classification, and the traffic of all trains that operate the line section for the purpose of the classification on the enforcement date. And a field 1435 for registering the user ID of the user who has acquired the exclusive flag for the diamond data.

  In the exclusive flag management TL 144, as shown in FIG. 3D, an exclusive flag record 1440 with the combination of the enforcement date, line section, type, and train number as a unit is registered. The record 1440 includes a field 1441 for registering an enforcement date, a field 1442 for registering a line section, a field 1443 for registering a type, a field 1444 for registering a train number, and a line 1 And a field 1445 for registering the user ID of the user who has acquired the exclusive flag for the traffic schedule data of the train having the train number operated for the purpose.

  In the update information management TL 15, an update information registration request (described later) received from the traffic schedule editing terminal 2 is registered. FIG. 4 is a diagram showing an example of registered contents of the update information management TL 15. As shown in the figure, a record 150 of an update information registration request (described later) received from the traffic schedule editing terminal 2 is registered in the update information management TL 15. The record 150 includes a field 151 for registering a user ID of a user, a field 152 for registering a request ID for identifying an update information registration request, an enforcement date and a line section for specifying traffic diagram data for requesting an update. The fields 153 to 156 for registering the type and train number, the field 157 for registering the updated contents (edit data) of the traffic diagram data, and the reflection indicating whether or not the updated contents have been reflected in the traffic diagram DB 13 And a field 158 for registering a situation.

  The exclusive control unit 12 includes an exclusive flag registration unit 121, a DB update unit 122, and a DB transfer unit 123. The exclusion flag registration unit 121 updates the exclusion flag management DB 14 in accordance with an exclusion flag registration request (described later) received from the traffic diagram editing terminal 2 via the network IF unit 11. The DB update unit 122 registers an update information registration request (described later) received from the traffic diagram editing terminal 2 via the network IF unit 11 in the update information management TL 15. In addition, the traffic diagram DB 13 is updated according to the update information registration request registered in the update information management TL 15. The DB transfer unit 123 reads the traffic diagram data from the update diagram DB 13 and transmits the traffic diagram data to the traffic diagram editing terminal 2 via the network IF unit 11.

  The traffic diagram editing terminal 2 edits traffic diagram data held by the traffic diagram management server 1 in accordance with an instruction from the user. As illustrated, the traffic diagram editing terminal 2 includes a network IF unit 21 for connecting to the network 3, a traffic diagram editing unit 22, an update information management TL23, a work storage unit 24, and an exclusive flag management TL25. A GUI (Graphical User Interface) unit 26 for displaying information and receiving operations and instructions from the user.

  In the update information management TL 23, update information, which is information for specifying the edited content of the traffic diagram data received from the user by the traffic diagram editing unit 22 via the GUI unit 26, is registered. FIG. 5 is a diagram showing an example of registered contents of the update information management TL23. As shown in the figure, a record 230 is registered in the update information management TL 23 every time the traffic diagram editing unit 22 accepts editing of traffic diagram data from the user via the GUI unit 26. The record 230 includes a field 231 for registering a request ID of an update information registration request, fields 232 to 235 for registering an execution date, a line section, a type, and a train number for specifying edited traffic schedule data, It has a field 236 for registering the change contents (edit data) of the diagram data, and a field 237 for registering a transmission status indicating whether or not an update information registration request including information of the fields 231 to 236 has been transmitted.

  In the work storage unit 24, traffic diagram data acquired from the traffic diagram management server 1 by the traffic diagram editing unit 22 via the network IF unit 21 is stored.

  The exclusive flag acquired by the user of the traffic schedule editing terminal 2 is registered in the exclusive flag management TL 25. FIG. 6 is a diagram showing an example of registered contents of the exclusive flag management TL 25. As shown in the figure, a record 250 is registered in the exclusive flag management TL 25 for each exclusive flag acquired by the user of the traffic schedule editing terminal 2. The record 250 includes a field 251 for registering an enforcement date of traffic diagram data to which the acquired exclusive flag is applied, a field 252 for registering a line zone of the traffic diagram data, and a type (operation purpose) of the traffic diagram data. It has a field 253 for registration and a field 254 for registering the train number of the traffic diagram data. Here, when the exclusive flag for the traffic schedule data of all trains operating on a certain effective date is acquired, the effective date is registered in the field 251 of the record 250 of the exclusive flag, and the other fields 252 to 254 are registered. Null data is registered. In addition, when the exclusive flag for the traffic schedule data of all trains operating on a certain line date is obtained, the effective date and the line area are registered in the fields 251 and 252 of the record 250 of the exclusive flag. Null data is registered in the other fields 253 and 254. In addition, when the exclusive flag for the traffic schedule data of all trains operating for a certain type of purpose on the line zone on a certain effective date is acquired, the effective date is displayed in the fields 251 to 253 of the record 250 of the exclusive flag. The line segment and the type are registered, and null data is registered in the other field 254. And when the exclusive flag with respect to the traffic diagram data of the train with a certain train number which operates for a certain kind of purpose on a certain line on a certain enforcement day is acquired, in the fields 251 to 254 of the record 250 of the exclusive flag, The enforcement date, the line segment, the classification and the train number are registered respectively.

  The traffic diagram editing unit 22 includes an exclusive flag registration request unit 221, an update information registration request unit 222, an edit reception unit 223, and a traffic diagram reading unit 224.

  The exclusive flag registration request unit 221 receives information specifying traffic diagram data (traffic diagram data to be edited) from which an exclusive flag is acquired from the user via the GUI unit 26 (management of any hierarchy that manages the traffic diagram data) Item information) is received and an exclusive flag registration request is created and transmitted to the traffic management server 1 via the network IF unit 21. FIG. 7 is a diagram schematically showing an exclusive flag registration request. As shown in the figure, the exclusive flag registration request 2210 registers the area 2211 for registering the user ID, the area 2212 for registering the enforcement date of the traffic schedule data for acquiring the exclusive flag, and the line schedule of the traffic schedule data for acquiring the exclusive flag. An area 2213 for registering a traffic diagram data type (operational purpose) for acquiring an exclusive flag, and an area 2215 for registering a train number of traffic diagram data for acquiring an exclusive flag. Similar to the record 250 of the exclusive flag management TL 25, the areas 2213 to 2215 may be null data depending on the hierarchy of traffic diagram data to be acquired. The exclusive flag registration request unit 221 registers the record 250 of the exclusive flag registration request 2210 transmitted to the traffic schedule management server 1 in the exclusive flag management TL 25.

  The update information registration request unit 222 periodically or whenever a new record 250 is added to the update information management TL 23, based on the record 230 in which the transmission status of the field 237 registered in the update information management TL 23 is “not yet”. Then, an update information registration request is created and transmitted to the traffic diagram management server 1 via the network IF unit 21. FIG. 8 is a diagram schematically showing an update information registration request. As shown in the figure, an update information registration request 2220 includes an area 2221 for registering a user ID, an area 2222 for registering a request ID for an update information registration request, an area 2223 for registering the enforcement date of traffic schedule data to be updated, and traffic to be updated. Area 2224 for registering a line segment of diagram data, an area 2225 for registering the type (operation purpose) of traffic diagram data to be updated, an area 2226 for registering a train number of traffic diagram data to be updated, and updated contents of traffic diagram data Has an area 2227 for registering.

  The edit accepting unit 223 displays the traffic diagram data stored in the work storage unit 24 on the GUI unit 26, and accepts the editing of the traffic diagram data from the user. Then, the received editing content is registered in the update information management TL23. At this time, with reference to the exclusive flag management TL 25, traffic diagram data other than the traffic diagram data for which the exclusive flag has been acquired is masked and displayed on the GUI unit 26, so that the traffic diagram data for which the exclusive flag has been acquired is displayed. Only accept edits from users.

  Then, the traffic diagram reading unit 224 downloads traffic diagram data from the traffic diagram management server 1 via the network IF unit 21 and stores the traffic diagram data in the work storage unit 24.

  The traffic diagram management server 1 and the traffic diagram editing terminal 2 described above include, for example, a CPU 901, a memory 902, an external storage device 903 such as an HDD, a CD-ROM, a DVD-ROM, an IC card, etc. as shown in FIG. A reading device 904 for reading data from a storage medium, an input device 906 such as a keyboard and a mouse, an output device 907 such as a monitor and a printer, a communication device 908 for connecting to the network 3, and these devices In a general computer system provided with a bus 909, the CPU 901 can execute the program loaded on the memory 902. This program is downloaded from the storage medium via the reading device 904 or from the network 3 via the communication device 908 to the external storage device 903, and then loaded onto the memory 902 and executed by the CPU 901. May be. Alternatively, it may be loaded directly on the memory 902 and not executed by the CPU 901 without going through the external storage device 903. In this case, a storage medium mounted on the memory 902, the external storage device 903, or the reading device 904 is used for each of the storage units 13-15 and 23-25. Further, a communication device 908 is used for the network IF units 11 and 21.

  Next, the operation of the traffic diagram data editing management system configured as described above will be described.

  First, the operation of the traffic schedule management server 1 will be described. FIG. 10 is a diagram for explaining the operation flow of the traffic diagram management server 1.

  When accessed from the traffic diagram editing terminal 2 via the network IF unit 11 (YES in S11), the exclusive control unit 12 receives a request from the traffic diagram editing terminal 2 and analyzes the content (S12). As a result of the analysis, if the request is a diagram data DL (download) request including a specified value of a predetermined management item, the DB transfer unit 123 performs processing. That is, the DB transfer unit 123 reads all the records 130 in which the designated values of the management items included in the traffic diagram data DL request are registered in the fields 131 to 134 of the management items from the traffic diagram DB 13 ( S13). In this embodiment, the enforcement date is used as the predetermined management item. However, the predetermined management item may be a combination of the enforcement date and the line section, or may be a combination of the enforcement date, the line section, and the type. Next, the DB transfer unit 123 transmits the read traffic diagram data record 130 to the transmission source of the diagram data DL request via the network IF unit 11 (S14).

  As a result of the analysis in S12, if the request is an exclusive flag registration request, the exclusive flag registration unit 121 performs an exclusive flag registration process described later (S15), and if the request is an update information registration request. Then, the DB update unit 122 performs an update information registration process described later (S16).

  11 and 12 are flowcharts for explaining the exclusive flag registration process (S15 in FIG. 10).

  First, the exclusion flag registration unit 121 identifies the enforcement date registered in the area 2212 of the exclusion flag registration request 2210 (see FIG. 7) received from the traffic diagram editing terminal 2 via the network IF unit 11, and executes the enforcement. The record 1410 in which the date is registered in the field 1411 is searched from the exclusive flag management TL 141 (see FIG. 4A) corresponding to the hierarchy “major classification” (S1501).

  If a corresponding record can be retrieved from the exclusive flag management TL 141 in S1501 (YES in S1502), an exclusive flag for traffic diagram data of all trains operating on the specified enforcement date has already been set. . In this case, the exclusive flag registration unit 121 performs predetermined error processing such as transmitting a rejection message of the exclusive flag registration request 2210 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11. (S1541).

  On the other hand, if the corresponding record cannot be retrieved from the exclusive flag management TL41 in S1501 (NO in S1502), the exclusive flag for the traffic schedule data of all trains operating on the specified enforcement date is not yet set. There will be no. In this case, it is checked whether or not the area 2213 for registering the line section of the exclusive flag registration request 2210 is null (S1503). If it is not null (NO in S1503), the exclusive flag is managed by exclusive flag management TLs 142 to 144 (see FIGS. 4B to 4C) corresponding to any hierarchy below the hierarchy “medium classification”. Should. In this case, the process proceeds to S1511. On the other hand, if it is null (YES in S1503), the exclusive flag should be managed by the exclusive flag management TL 141 corresponding to the hierarchy “major classification”. Therefore, a record 1410 is newly added to the exclusive flag management TL 141 corresponding to the hierarchy “major classification”, and the effective dates registered in the areas 2212 and 2211 of the exclusive flag registration request 2210 in the fields 1411 and 1415 of the record 1410. The user ID is registered (S1506). Thereafter, the process ends.

  In S1511, the exclusion flag registration unit 121 identifies the enforcement date and line zone registered in the areas 2212 and 2213 of the exclusion flag registration request 2210, and the enforcement date and line zone are registered in the fields 1421 and 1422. Is searched from the exclusive flag management table 142 corresponding to the hierarchy “medium classification”.

  If the corresponding record can be retrieved from the exclusion flag management table 142 in S1511 (YES in S1512), an exclusion flag for the traffic schedule data of all trains operating on the identified line on the specified enforcement date has already been set. Will be. In this case, the exclusive flag registration unit 121 performs predetermined error processing such as transmitting a rejection message of the exclusive flag registration request 2210 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11. (S1541).

  On the other hand, if the corresponding record could not be retrieved from the exclusive flag management TL 142 in S1511 (NO in S1512), the exclusive flag for the traffic schedule data of all trains operating on the specified line on the specified enforcement date Is not set yet. In this case, it is checked whether or not the area 2214 for registering the type of the exclusive flag registration request 2210 is null (S1513). If it is not null (NO in S1513), the exclusive flag should be managed by the exclusive flag management TL 143, 144 corresponding to any hierarchy below the hierarchy "sub-classification". In this case, the process proceeds to S1521. On the other hand, if it is null (YES in S1513), the exclusion flag should be managed by the exclusion flag management TL 142 corresponding to the hierarchy “medium category”. Therefore, a record 1420 is newly added to the exclusive flag management TL 142 corresponding to the hierarchy “medium class”, and is registered in the areas 2212, 2213, and 2211 of the exclusive flag registration request 2210 in the fields 1421, 1422, and 1425 of the record 1420. The effective date, line section, and user ID are registered (S1516). Thereafter, the process ends.

  In S1521, the exclusion flag registration unit 121 identifies the enforcement date, line section, and type registered in the areas 2212, 2213, and 2214 of the exclusion flag registration request 2210, and the enforcement date, line section, and type are fields. The records 1430 registered in 1431, 1432, and 1433 are searched from the exclusive flag management TL 143 corresponding to the hierarchy “small classification”.

  If the corresponding record can be retrieved from the exclusive flag management TL 143 in S1521, (YES in S1522), the traffic schedule data of all trains operating for the type that identifies the line segment identified on the identified enforcement date are targeted. The exclusion flag is already set. In this case, the exclusive flag registration unit 121 performs predetermined error processing such as transmitting a rejection message of the exclusive flag registration request 2210 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11. (S1541).

  On the other hand, if the corresponding record cannot be retrieved from the exclusive flag management TL 143 in S1521, (NO in S1522), the traffic diagram data of all trains that operate for the type that identifies the line segment identified on the identified enforcement date. This means that the exclusion flag for the target has not been set yet. In this case, it is checked whether or not the area 2215 for registering the train number of the exclusive flag registration request 2210 is null (S1523). If it is not null (NO in S1523), the exclusion flag should be managed by the exclusion flag management TL 144 corresponding to the hierarchy “per traffic schedule data”. In this case, the process proceeds to S1531. On the other hand, in the case of null (YES in S1523), the exclusive flag should be managed by the exclusive flag management TL 143 corresponding to the hierarchy “small classification”. Therefore, a record 1430 is newly added to the exclusive flag management TL 143 corresponding to the hierarchy “small classification”, and the fields 1431, 1432, 1433, and 1435 of the record 1430 are added to the areas 2212, 2213, 2214, and the exclusive flag registration request 2210. The enforcement date, line section, type, and user ID registered in 2211 are registered (S1526). Thereafter, the process ends.

  In S1531, the exclusion flag registration unit 121 identifies the enforcement date, line section, type, and train number registered in the areas 2212, 2213, 2214, and 2215 of the exclusion flag registration request 2210. The record 1440 in which the district, type, and train number are registered in the fields 1441, 1442, 1443, and 1444 is searched from the exclusive flag management TL 144 corresponding to the hierarchy “for each traffic schedule data”.

  If the corresponding record can be searched from the exclusive flag management TL 144 in S1531, the traffic schedule of the train having the specified train number that operates for the type that specified the line segment specified on the specified enforcement date is determined. The exclusive flag for the data is already set. In this case, the exclusive flag registration unit 121 performs predetermined error processing such as transmitting a rejection message of the exclusive flag registration request 2210 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11. (S1541).

  On the other hand, when the corresponding record cannot be searched from the exclusive flag management TL 144 in S1531 (NO in S1532), the train has the specified train number that operates for the type that specified the line section specified on the specified enforcement date. The exclusive flag for the train traffic schedule data is not set yet. In this case, a record 1440 is newly added to the exclusive flag management TL 144 and registered in the fields 1441, 1442, 1443, 1444, and 1445 of the record 1440 in the areas 2212, 2213, 2214, 2215, and 2211 of the exclusive flag registration request 2210. The enforcement date, line section, type, train number, and user ID are registered (S1533). Thereafter, the process ends.

  13 and 14 are flowcharts for explaining the update content reflecting process (S16 in FIG. 10).

  First, the DB update unit 122 performs the enforcement date, line section, and type registered in the areas 2223 to 2226 of the update information registration request 2220 (see FIG. 8) received from the traffic diagram editing terminal 2 via the network IF unit 11. The train number is specified, and the record 1440 in which the enforcement date, line section, type, and train number are registered in the fields 1441 to 1444 is searched from the exclusive flag management table 144 corresponding to the hierarchy “for each traffic data” (S1601). ).

  When the corresponding record 1440 can be searched from the exclusive flag management table 144 in S1601 (YES in S1602), the train having the specified train number that operates for the type that specifies the line section specified on the specified enforcement date is displayed. The exclusive flag for the traffic diagram data is already set. In this case, the DB update unit 122 checks whether the user ID registered in the field 1445 of the retrieved record 1440 matches the user ID registered in the area 2221 of the update information registration request 2220 ( S1603).

  When the user ID registered in the field 1445 of the record 1440 searched in S1601 matches the user ID registered in the area 2221 of the update information registration request 2220 (YES in S1603), the update information registration request 2220 is displayed. The transmitted user of the traffic diagram editing terminal 2 has acquired an exclusive flag for the traffic diagram data that is requested to be updated by the request. In this case, the DB update unit 122 newly adds the record 150 to the update information management TL 15 and registers the contents registered in the areas 2221 to 2227 of the update information registration request 2220 in the fields 151 to 157 of the record 150. . Also, the reflection status “not yet” is registered in the field 158 of the record 150 (S1604). Then, the DB update unit 122 extracts the record 150 having the reflection status “unknown” field 158 from the update information management TL15. Next, a record 130 in which the enforcement date, line section, type, and train number registered in the fields 153 to 156 of the extracted record 150 are registered in the fields 132 to 134 and 131 is searched from the traffic diagram DB 13. Then, the traffic schedule data registered in the field 135 of the retrieved record 130 is updated according to the changed content registered in the field 157 of the extracted record 150. In addition, the reflection status registered in the field 158 of the extracted record 150 is changed from “not yet” to “completed” (S1605).

  On the other hand, if the user ID registered in the field 1445 of the record 1440 searched in S1601 does not match the user ID registered in the area 2221 of the update information registration request 2220 (NO in S1603), an update information registration request The user of the traffic diagram editing terminal 2 that has transmitted 2220 has not acquired the exclusive flag for the traffic diagram data that is requested to be updated by the request. The exclusive flag is acquired by another user. In this case, the DB update unit 122 performs predetermined error processing such as transmitting a rejection message of the update information registration request 2220 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11 ( S1641).

  If the corresponding record 1440 cannot be retrieved from the exclusive flag management TL 144 in S1601 (NO in S1602), the train has the specified train number that operates for the specified type of the line segment specified on the specified enforcement date. The exclusive flag for the train traffic schedule data is not set. In this case, the DB update unit 122 identifies the enforcement date, line section, and type registered in the areas 2223 to 2225 of the update information registration request 2220, and the enforcement date, line section, and type are registered in the fields 1431 to 1433. The recorded record 1430 is searched from the exclusive flag management TL 143 corresponding to the hierarchy “small classification” (S1611).

  If the corresponding record 1430 can be searched from the exclusive flag management TL 143 in S1611 (YES in S1612), the traffic schedule data of all trains operating for the type that specified the line area specified on the specified enforcement date are targeted. The exclusive flag to be set is already set. In this case, the DB update unit 122 checks whether or not the user ID registered in the field 1435 of the retrieved record 1430 matches the user ID registered in the area 2221 of the update information registration request 2220 ( S1613).

  When the user ID registered in the field 1435 of the record 1430 searched in S1611 matches the user ID registered in the area 2221 of the update information registration request 2220 (YES in S1613), the update information registration request 2220 is displayed. The transmitted user of the traffic diagram editing terminal 2 has acquired an exclusive flag for the traffic diagram data that is requested to be updated by the request. In this case, the DB update unit 122 newly adds the record 150 to the update information management TL 15 and registers the contents registered in the areas 2221 to 2227 of the update information registration request 2220 in the fields 151 to 157 of the record 150. . Also, the reflection status “not yet” is registered in the field 158 of the record 150 (S1614). Then, the DB update unit 122 extracts the record 150 having the reflection status “unknown” field 158 from the update information management TL15. Next, a record 130 in which the enforcement date, line section, type, and train number registered in the fields 153 to 156 of the extracted record 150 are registered in the fields 132 to 134 and 131 is searched from the traffic diagram DB 13. Then, the traffic schedule data registered in the field 135 of the retrieved record 130 is updated according to the changed content registered in the field 157 of the extracted record 150. In addition, the reflection status registered in the field 158 of the extracted record 150 is changed from “not yet” to “completed” (S1605).

  On the other hand, if the user ID registered in the field 1435 of the record 1430 retrieved in S1611 does not match the user ID registered in the area 2221 of the update information registration request 2220 (NO in S1613), an update information registration request The user of the traffic diagram editing terminal 2 that has transmitted 2220 has not acquired the exclusive flag for the traffic diagram data that is requested to be updated by the request. The exclusive flag is acquired by another user. In this case, the DB update unit 122 performs predetermined error processing such as transmitting a rejection message of the update information registration request 2220 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11 ( S1641).

  If the corresponding record 1430 cannot be retrieved from the exclusive flag management table 143 in S1611 (NO in S1612), the traffic of all trains operated for the type specified in the line section specified on the specified enforcement date. The exclusive flag for the diamond data is not set. In this case, the DB update unit 122 identifies the enforcement date and line district registered in the areas 2223 and 2224 of the update information registration request 2220, and the enforcement date and line segment are registered in the fields 1421 and 1422. 1420 is searched from the exclusive flag management TL 142 corresponding to the hierarchy “medium class” (S1621).

  If the corresponding record 1420 can be retrieved from the exclusive flag management TL 142 in S1621, (YES in S1622), an exclusive flag for traffic schedule data of all trains operating on the specified line on the specified enforcement date has already been obtained. It will be set. In this case, the DB update unit 122 checks whether or not the user ID registered in the field 1425 of the searched record 1420 matches the user ID registered in the area 2221 of the update information registration request 2220 ( S1623).

  When the user ID registered in the field 1425 of the record 1420 searched in S1621 matches the user ID registered in the area 2221 of the update information registration request 2220 (YES in S1623), the update information registration request 2220 is displayed. The transmitted user of the traffic diagram editing terminal 2 has acquired an exclusive flag for the traffic diagram data that is requested to be updated by the request. In this case, the DB update unit 122 newly adds the record 150 to the update information management TL 15 and registers the contents registered in the areas 2221 to 2227 of the update information registration request 2220 in the fields 151 to 157 of the record 150. . Also, the reflection status “not yet” is registered in the field 158 of the record 150 (S1624). Then, the DB update unit 122 extracts the record 150 having the reflection status “unknown” field 158 from the update information management TL15. Next, a record 130 in which the enforcement date, line section, type, and train number registered in the fields 153 to 156 of the extracted record 150 are registered in the fields 132 to 134 and 131 is searched from the traffic diagram DB 13. Then, the traffic schedule data registered in the field 135 of the retrieved record 130 is updated according to the changed content registered in the field 157 of the extracted record 150. Also, the reflection status registered in the field 158 of the extracted record 150 is changed from “not yet” to “completed” (S1625).

  On the other hand, if the user ID registered in the field 1425 of the record 1420 searched in S1621 does not match the user ID registered in the area 2221 of the update information registration request 2220 (NO in S1623), an update information registration request The user of the traffic diagram editing terminal 2 that has transmitted 2220 has not acquired the exclusive flag for the traffic diagram data that is requested to be updated by the request. The exclusive flag is acquired by another user. In this case, the DB update unit 122 performs predetermined error processing such as transmitting a rejection message of the update information registration request 2220 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11 ( S1641).

  Also, if the corresponding record 1420 cannot be retrieved from the exclusive flag management TL 142 in S1621, (NO in S1622), an exclusive flag that targets traffic diagram data of all trains that operate on the specified line on the specified enforcement date. Is not set. In this case, the DB update unit 122 identifies the enforcement date registered in the area 2223 of the update information registration request 2220, and the record 1410 in which the enforcement date is registered in the field 1411 corresponds to the hierarchy “major classification”. The exclusive flag management TL 141 to be searched is searched (S1631).

  If the corresponding record 1410 can be retrieved from the exclusive flag management TL 141 in S1631 (YES in S1632), an exclusive flag for traffic schedule data of all trains operating on the specified enforcement date has already been set. Become. In this case, the DB update unit 122 checks whether or not the user ID registered in the field 1415 of the searched record 1410 matches the user ID registered in the area 2221 of the update information registration request 2220 ( S1633).

  If the user ID registered in the field 1415 of the record 1410 searched in S1631 matches the user ID registered in the area 2221 of the update information registration request 2220 (YES in S1633), the update information registration request 2220 is displayed. The transmitted user of the traffic diagram editing terminal 2 has acquired an exclusive flag for the traffic diagram data that is requested to be updated by the request. In this case, the DB update unit 122 newly adds the record 150 to the update information management TL 15 and registers the contents registered in the areas 2221 to 2227 of the update information registration request 2220 in the fields 151 to 157 of the record 150. . Also, the reflection status “not yet” is registered in the field 158 of this record 150 (S1634). Then, the DB update unit 122 extracts the record 150 having the reflection status “unknown” field 158 from the update information management TL15. Next, a record 130 in which the enforcement date, line section, type, and train number registered in the fields 153 to 156 of the extracted record 150 are registered in the fields 132 to 134 and 131 is searched from the traffic diagram DB 13. Then, the traffic schedule data registered in the field 135 of the retrieved record 130 is updated according to the changed content registered in the field 157 of the extracted record 150. Also, the reflection status registered in the field 158 of the extracted record 150 is changed from “not yet” to “completed” (S1625).

  On the other hand, if the user ID registered in the field 1415 of the record 1410 searched in S1631 does not match the user ID registered in the area 2221 of the update information registration request 2220 (NO in S1633), an update information registration request The user of the traffic diagram editing terminal 2 that has transmitted 2220 has not acquired the exclusive flag for the traffic diagram data that is requested to be updated by the request. The exclusive flag is acquired by another user. In this case, the DB update unit 122 performs predetermined error processing such as transmitting a rejection message of the update information registration request 2220 to the traffic diagram editing terminal 2 that is the transmission source of the request via the network IF unit 11 ( S1641).

  Next, the operation of the traffic diagram editing terminal 2 will be described. FIG. 15 is a diagram for explaining an operation flow of the traffic diagram editing terminal 2.

  First, when receiving an exclusive flag registration instruction from the user via the GUI unit 26 (YES in S201), the exclusive flag registration request unit 221 displays a management item reception screen as shown in FIG. 16 on the GUI unit 26. The management item for specifying the traffic schedule data to acquire the exclusive flag and the input of the information are received. In FIG. 16, reference numeral 2601 denotes a selection column for selecting a hierarchy of traffic diagram data to which the exclusion flag to be acquired is applied. The user can select the hierarchy shown in the pull-down menu (the hierarchy “large” shown in FIG. 3). A desired hierarchy can be selected from “classification”, “medium classification”, “small classification”, and “per traffic schedule data”). Reference numerals 2602 to 2605 are input / selection fields for inputting and selecting management item information for setting an exclusive flag for traffic schedule data in the hierarchy selected in the selection field 2601. Reference numeral 2602 is an input field for a management item “Effective Date”, reference numeral 2603 is a selection field for selecting a desired management item “Line” from the pull-down menu, and reference numeral 2604 is a desired management item “ A selection field for selecting “type”, and reference numeral 2605 is an input field for the management item “train number”. When the hierarchy “major classification” is selected in the selection field 2601, the input / selection fields 2603 to 2605 are displayed in gray, for example, and information cannot be input or selected. The enforcement date can be entered only in the input field 2602. When the hierarchy “medium classification” is selected in the selection field 2601, the input / selection fields 2604 and 2605 are displayed in gray, for example, and information cannot be input or selected. An execution date and a line section can be input and selected in the input column 2602 and the selection column 2603. When the hierarchy “small classification” is selected in the selection field 2601, the input / selection field 2605 is displayed in gray, for example, and information cannot be input or selected. In the input fields 2602 to 2604, the enforcement date, line section, and type can be entered and selected. When the hierarchy “every traffic schedule data” is selected in the selection field 2601, information can be input and selected in all the input / selection fields 2602 to 2605. Note that information to be displayed in the pull-down menu in the selection fields 2601, 2603, and 2604 is stored in advance in a memory or the like. The reference numeral 2606 is an enter / selection field 2601 to 2605, and a confirmation button for confirming the selected information. The reference numeral 2607 is an input / selection field 2601 to 2605, and a cancel button for canceling the selected information. Button.

  When the exclusive flag registration request unit 221 receives a management item and input of the information from the user via the GUI unit 26, the exclusive flag registration request unit 221 newly adds a record 250 to the exclusive flag management TL 25, and receives the management received in this record 250. Register item information. Further, an exclusive flag registration request 2210 including the received management item information and a pre-registered user ID is generated and transmitted to the traffic diagram management server 1 via the network IF unit 21 (S203). If an error notification such as an exclusion flag registration request rejection message is received from the traffic schedule management server 1 within a predetermined period (YES in S204), the record 250 added to the exclusion flag management TL 25 in S203 is deleted (S205). .

  When the traffic diagram reading unit 224 receives a DL instruction of traffic diagram data from the user via the GUI unit 26 (YES in S230), the traffic diagram data to be displayed is displayed on the GUI unit 26 and downloaded. The designation of the range is accepted (S231). In this embodiment, designation of the enforcement date is accepted.

  When the traffic diagram reading unit 224 receives a DL range designation from the user via the GUI unit 26, the traffic diagram reading unit 224 generates a traffic diagram data DL request including the designated DL range and a pre-registered user ID. This is transmitted to the traffic diagram management server 1 via the network IF unit 21 (S222). Then, traffic schedule data is received from the traffic schedule management server 1 and stored in the work storage unit 24 (S223). Receiving this, the edit reception part 223 displays the traffic diagram data memorize | stored in the memory | storage part 24 for work with a graph (S224).

  FIG. 17 shows an example of a traffic diagram data display screen. In this example, all traffic schedule data operated on the specified enforcement date (2004/11/16, 2004/11/27), with the vertical axis 2611 as each station constituting the line and the horizontal axis 2612 as time. Is displayed in a graph. The alphabet (symbol 2615) attached to the graph is a train number. The line type of the graph represents the type. Here, the solid line represents the type “business”, and the alternate long and short dash line represents the type “cargo”. The user selects a part of traffic diagram data 26 displayed in a graph on the traffic diagram data display screen with a cursor (not shown) via the GUI unit 26 and performs an operation such as dragging. The content is received by the edit reception unit 223, and traffic schedule data, which will be described later, is edited. Reference numeral 2613 is a confirmation button for the operation content, and reference numeral 2614 is a cancel button. It should be noted that existing graphic software technology can be used to accept editing of traffic diagram data using the GUI unit 26.

  In addition, when the traffic schedule data reading unit 224 reaches the update timing of the traffic schedule data stored in the work storage unit 24, for example, a predetermined time has elapsed (YES in both S220 and S221), A traffic diagram data DL request including a DL range (effective date) of the stored traffic diagram data and a user ID registered in advance is generated, and this request is transmitted to the traffic diagram management server 1 via the network IF unit 21. Transmit (S222). Then, traffic schedule data is received from the traffic schedule management server 1, and the stored contents of the work storage unit 24 are updated (S223). In response to this, the edit accepting unit 223 displays the updated traffic diagram data in the work storage unit 24 as a graph (S224).

  Further, when the editing accepting unit 24 accepts the traffic diagram data editing operation (YES in S211) via the traffic diagram data display screen (see FIG. 17) displayed on the GUI unit 26, the editing accepting unit 24 accepts the editing operation. It is checked whether or not the exclusive flag record 250 for the target traffic diagram data is registered in the exclusive flag management TL 25 (S212). Specifically, the same execution date as the traffic diagram data of the object for which the editing operation has been accepted is registered in the field 251, and the fields 2502, 253, and 254 of the line section, type, and train number are null records 250, The same execution date and line section as the traffic diagram data are registered in the fields 251 and 252 and the fields 253 and 254 of the type and train number are null records 250, and the traffic diagram data of the object for which the editing operation is accepted The same enforcement date, line section, and type are registered in the fields 251, 252, and 253, and the train number fields 252, 253, and 254 are null records 250, and the traffic diagram data for which the editing operation has been accepted. Record 25 in which the same enforcement date, line section, type, and train number are registered in fields 251 to 254 Of, any of the records examined whether that is registered.

  When no record is registered (NO in S212), the edit receiving unit 24 does not reflect the editing operation on the traffic diagram data display screen. In other words, the traffic diagram data that has received the editing operation stored in the work storage unit 24 is not reflected in the changed contents of the editing operation. Further, the editing accepting unit 24 notifies the user that the editing operation has been rejected by changing the color of the graph indicating the traffic diagram data for which the editing operation has been accepted (S218).

  On the other hand, when the exclusive flag record 250 for the traffic diagram data for which the editing operation has been accepted is registered in the exclusive flag management TL 25 (YES in S212), the editing accepting unit 24 changes, for example, by the editing operation The contents are provisionally received, and for example, as shown in FIG. 18, the contents of the provisionally accepted change are superimposed on the graph representing the traffic diagram data stored in the work storage unit 24 by changing the color and line type. Thus, the traffic diagram data display screen is changed so that the user can identify the edited content (S213). In FIG. 18, the traffic schedule data indicated by reference numeral 2621, that is, the traffic identified by the enforcement date “2004/11/26”, the line zone “α-ku”, the type “business”, and the train number “C”. The diagram data is traffic diagram data that has been edited. As indicated by reference numeral 2622, the contents changed by the editing operation are displayed together with the original traffic diagram data 2621 while changing the display form (for example, color and line type). Yes. By doing so, the user can confirm the editing operation performed by the user.

  Now, the edit reception part 223 changes the contents (the station name of each station whose time has been changed and the time after the change at the station), the enforcement date of the traffic schedule data edited by the editing operation, the line The update information request unit 222 is notified of the ward, type, and train number. In response to this, the update information request unit 222 adds a new record 230 to the update information management TL 23. Then, in the fields 232 to 236 of this record, the enforcement date, line section, type, train number, and change contents added from the edit reception unit 223 are registered. In the field 231, a unique request ID is generated and registered. Further, the update information request unit 222 registers the transmission status “not yet” in the field 237. Then, the update information request unit 222 generates an update information registration request 2220 including a user ID registered in advance and the registration contents of the fields 231 to 236 of the record 230, and the traffic diagram via the network IF unit 21. It transmits to the management server 1 (S214).

  Next, the update information request unit 222 receives an error notification such as an update information registration rejection message from the traffic schedule management server 1 within a predetermined period, or sends a normal response such as an update information registration permission message for a predetermined period. If it is received from the traffic schedule management server 1 (NO in S215), an update instruction for the work storage unit 24 is notified to the edit reception unit 223. In response to this, the edit accepting unit 24 updates the provisionally accepted editing operation to reflect the traffic data stored in the work storage unit 24 and the update in the work storage unit 24. The traffic diagram data is displayed in a graph (S216). Then, in order to allow the user to identify the updated portion, the edit receiving unit 24 displays the traffic diagram data 2622 changed by the editing operation as shown in FIG. Change the line type to display.

  On the other hand, if the update information requesting unit 222 receives an error notification such as an update information registration rejection message from the traffic schedule management server 1 within a predetermined period (YES in S215), the update information requesting unit 222 notifies the edit receiving unit 223 to that effect. In this case, the edit accepting unit 223 does not reflect the change content by the temporarily accepted editing operation in the traffic data stored in the work storage unit 24. In addition, the display of the change contents by the editing operation is stopped on the traffic diagram data display screen. Further, in order to enable the user to identify the portion for which editing has been rejected, as shown in FIG. 20, the editing accepting unit 24 displays traffic diagram data 2621 whose editing operation has been rejected, for example, for a predetermined time. Change the line type to display.

  Next, an operation example of the entire traffic diagram data editing management system of this embodiment will be described.

  FIG. 21 is a diagram for explaining the exchange of information between the traffic diagram management server 1 and the traffic diagram editing terminal 2.

  When the traffic diagram editing terminal 2 receives an instruction to register an exclusive flag from the user via the GUI unit 26, the traffic schedule editing terminal 2 executes S202 and S203 in FIG. As a result, the exclusion flag registration unit 121 accepts the management item for identifying the traffic schedule data for obtaining the exclusion flag from the user and the information (S401), and generates the exclusion flag registration request 2210 based on the accepted information. This is transmitted to the traffic diagram management server 1 via the network IF unit 21 (S402).

  In the traffic schedule management server 1, when the exclusion flag registration unit 121 receives the exclusion flag registration request 2210 from the traffic diagram editing terminal 2 via the network IF unit 11, S15 in FIG. 10 (the flow shown in FIG. 11 and FIG. 12). Execute. As a result, the exclusion flag registration request 2210 is registered in the exclusion flag management DB 14 when exclusion is not already acquired by other users for the traffic diagram data for which the exclusion flag registration request 2210 requests acquisition of exclusion (S411). .

  When the traffic diagram editing terminal 2 receives a DL instruction of traffic diagram data from the user via the GUI unit 26, the traffic diagram editing terminal 2 executes S231 and S222 in FIG. As a result, the traffic diagram reading unit 224 receives the DL range (effective date) of the traffic diagram data from the user (S403), generates a traffic diagram data DL request based on the received information, and sends it to the network IF unit 21. Via the traffic schedule management server 1 (S404).

  In the traffic diagram management server 1, when the DB transfer unit 123 receives a traffic diagram data DL request from the traffic diagram editing terminal 2 via the network IF unit 11, it executes S13S14 of FIG. As a result, the traffic diagram data in the DL range specified by the traffic diagram data DL request is read from the traffic diagram DB 13 and transmitted to the traffic diagram editing terminal 2 via the network IF unit 11 (S412).

  When the traffic diagram editing terminal 2 receives traffic diagram data from the traffic diagram management server 1 via the network IF unit 21, it executes S223 and S224 in FIG. Thereby, the traffic diagram reading unit 224 stores the received traffic diagram data in the work storage unit 24. Also, the edit accepting unit 223 displays the traffic diagram data stored in the work storage unit 24 as a graph on the GUI unit 26 (S405).

  When the traffic diagram editing terminal 2 accepts an editing operation of traffic diagram data being displayed on the GUI unit 26 from the user via the GUI unit 26, the traffic diagram editing terminal 2 executes S212 to S214 in FIG. As a result, the edit accepting unit 223 refers to the exclusion flag management TL25, and if the user of the traffic diagram editing terminal 2 has obtained the exclusion for the traffic diagram data that has been edited, the editing accepting unit 223 temporarily accepts the content changed by the editing operation. To do. Also, the update information registration request unit 222 generates an update information registration request 2220 based on the changed content, and transmits this to the traffic diagram management server 1 via the network IF unit 21 (S407). If there is no error notification or the like within a predetermined time, the edit receiving unit 223 updates the traffic diagram data in the work storage unit 24 and displays the updated traffic diagram data (S408).

  In the traffic diagram management server 1, when the DB update unit 122 receives the update information registration request 2220 from the traffic diagram editing terminal 2 via the network IF unit 11, S16 in FIG. 10 (the flow shown in FIG. 13 and FIG. 14). Execute. As a result, for the traffic diagram data for which the update information registration request 2220 requests an update, if the user who transmitted the request has obtained an exclusion for the traffic diagram data, the change contents included in the request are displayed. It is reflected in the traffic diagram DB 13 (S413).

  The embodiment of the present invention has been described above.

  According to the present embodiment, traffic diagram data is managed in a plurality of layers, and exclusive flag management TLs 141 to 144 are prepared for each layer, and an exclusive flag for certain traffic diagram data is managed by any one of the exclusive flag management TLs. is doing. For example, when the exclusive flag for the traffic schedule data of all trains operating on a certain effective date is registered in the exclusive flag management TL 141 of the hierarchy “major classification”, each exclusive flag management TL 141 of the hierarchy “major classification” or less thereafter. The exclusive flag for the traffic schedule data that operates on the effective date is not registered in ~ 144. In addition, when the exclusive flag for the traffic schedule data of all trains that operate on a certain day on the day of enforcement is registered in the exclusive flag management TL 142 of the hierarchy “medium classification”, each exclusion below the hierarchy “medium classification” In the flag management TLs 142 to 144, the exclusive flag for the traffic schedule data that operates the line on the enforcement date is not registered. In addition, when the exclusive flag for the traffic schedule data of all trains that operate on the line zone for a certain purpose on a certain effective date is registered in the exclusive flag management TL 143 of the hierarchy “sub-class”, the hierarchy “sub-class” thereafter. In each of the following exclusive flag management TLs 143 and 144, there is no registration of an exclusive flag for the traffic schedule data that operates the line section for the purpose of the type on the effective date. By doing in this way, the number of exclusive flags can be reduced compared with the technique of patent document 1 which divides drawing data into meshes and manages exclusive flags for each mesh. The processing load related to exclusive control can be reduced.

  In the present embodiment, as shown in FIGS. 11 and 12, the exclusive flag registration processing in the exclusive flag management DB 14 by the exclusive flag registration unit 121 is performed as follows. First, it is checked whether or not the record 1410 having the same enforcement date as the exclusive flag registration request 2210 is registered in the exclusive flag management TL 141 of the hierarchy “major classification”, and if it is registered, the request 2210 is rejected. Next, when a record 1410 having the same enforcement date is not registered and the exclusive flag registration request 2210 includes a line segment, the record 1420 having the same enforcement date and line segment as the request 2210 is included. Is registered in the exclusive flag management TL 142 of the hierarchy “medium class”, and if it is registered, the request 2210 is rejected. Further, if the record 1420 having the same enforcement date and line section is not registered and the type is included in the exclusive flag registration request 2210, the same enforcement date, line section and type as the request 2210 are set. It is checked whether or not the record 1430 possessed is registered in the exclusive flag management TL 142 of the hierarchy “small classification”, and if it is registered, the request 2210 is rejected. Furthermore, when a record 1430 having the same enforcement date, line section and type is not registered, and the train number is included in the exclusive flag registration request 2210, the same enforcement date and line as the request 2210 It is checked whether or not a record 1440 having a ward, type, and train number is registered in the exclusive flag management TL 144 of the hierarchy “per traffic schedule data”. If registered, the request 2210 is rejected. In this way, by determining whether or not an exclusive flag registration request can be made from the exclusive flag management TL of the upper layer to the exclusive flag management TL of the lower layer, the determination process can be performed quickly.

  Moreover, in this embodiment, as shown in FIG. 13 and FIG. 14, the update information reflection process to the traffic diagram DB 13 by the DB update unit 122 is performed as follows. First, it is checked whether or not a record 1440 having the same enforcement date, line section, line type, and train number as the update information registration request 2220 is registered in the exclusive flag management TL 144 of the hierarchy “per traffic schedule data”. If so, the request 2220 is rejected. Next, when the record 1440 having the same enforcement date, line section, line type, and train number is not registered, the record 1430 having the same enforcement date, line section, and line type as the request 2220 has the hierarchy “sub-classification”. It is checked whether it is registered in the exclusive flag management TL 143, and if it is registered, the request 2210 is rejected. Further, when a record 1430 having the same enforcement date, line section and line type is not registered, a record 1420 having the same enforcement date and line section as the request 2220 is registered in the exclusive flag management TL 142 of the hierarchy “medium classification”. Whether the request 2210 has been registered is rejected. Furthermore, if the record 1420 having the same enforcement date and line section is not registered, whether or not the record 1410 having the same enforcement date as the request 2220 is registered in the exclusive flag management TL 141 of the hierarchy “major classification”. If the request is registered, the request 2210 is rejected. In this way, by performing the determination as to whether or not the update information registration request is possible from the lower layer exclusive flag management TL to the upper layer exclusive flag management TL, the determination process can be quickly performed.

  In addition, this invention is not limited to said embodiment, Many deformation | transformation are possible within the range of the summary.

  For example, in the above embodiment, the case where traffic management data is managed in four layers for each of the major classification, middle classification, minor classification, and traffic schedule data using the enforcement date, line section, type, and train number is taken as an example. explained. However, the present invention is not limited to this. The present invention uses the first management item to manage the traffic schedule data at the first hierarchy, uses the first and second management items to manage the traffic schedule data at the second hierarchy, The present invention can be widely applied to a case where traffic schedule data is managed in a plurality of hierarchies using a plurality of management items, such as traffic schedule data being managed in a third hierarchy using the second and third management items.

  A combination of a plurality of management items may be handled as one data. For example, in FIG. 3 (B), the data obtained by connecting the enforcement date and the line section are registered in one field, and in FIG. 3 (C), the data obtained by connecting the enforcement date, the line section and the type are registered in one field. Then, in FIG. 3D, data obtained by connecting the enforcement date, line section, type, and train number may be registered in one field.

  In the above embodiment, the exclusive control in editing the traffic diagram data has been described as an example. However, the present invention is not limited to this. The present invention can be applied to graphic data other than traffic schedule data as long as it can be managed hierarchically using a plurality of management items.

FIG. 1 is a schematic diagram of a traffic diagram data editing management system to which an embodiment of the present invention is applied. FIG. 2 is a diagram showing an example of registered contents in the traffic diagram DB 13. FIG. 3 is a diagram showing an example of registered contents in the exclusive flag management DB 14, FIG. 3A is an example of registered contents of the exclusive flag management TL 141 corresponding to the hierarchy “major classification”, and FIG. FIG. 3C shows an example of registered contents of the exclusive flag management TL 143 corresponding to the hierarchy “small classification”, and FIG. 3D shows an example of registered contents of the exclusive flag management TL 142 corresponding to the “classification”. It is a figure which shows the example of registration content of the exclusive flag management TL144 corresponding to "traffic diagram data of". FIG. 4 is a diagram showing an example of registered contents of the update information management TL 15. FIG. 5 is a diagram showing an example of registered contents of the update information management TL23. FIG. 6 is a diagram showing an example of registered contents of the exclusive flag management TL 25. FIG. 7 is a diagram schematically showing an exclusive flag registration request. FIG. 8 is a diagram schematically showing an update information registration request. FIG. 9 is a diagram illustrating a hardware configuration example of the traffic diagram management server 1 and the traffic diagram editing terminal 2. FIG. 10 is a diagram for explaining the operation flow of the traffic diagram management server 1. FIG. 11 is a flowchart for explaining the exclusive flag registration process (S15 in FIG. 10). FIG. 12 is a flowchart for explaining the exclusive flag registration process (S15 in FIG. 10). FIG. 13 is a flowchart for explaining the update content reflection processing (S16 in FIG. 10). FIG. 14 is a flowchart for explaining the update content reflection processing (S16 in FIG. 10). FIG. 15 is a diagram for explaining an operation flow of the traffic diagram editing terminal 2. FIG. 16 is a diagram illustrating an example of a management item reception screen. FIG. 17 shows an example of a traffic diagram data display screen. FIG. 18 is a diagram showing an example of an edited content identification display screen for traffic diagram data. FIG. 19 is a diagram showing an example of an updated part identification display screen of traffic diagram data. FIG. 20 is a diagram illustrating an example of a traffic diagram data update rejection identification display screen. FIG. 21 is a diagram for explaining the exchange of information between the traffic diagram management server 1 and the traffic diagram editing terminal 2.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Traffic schedule management server, 2 ... Traffic schedule edit terminal, 3 ... Network, 11 ... Network IF part, 12 ... Exclusive control part, 13 ... Traffic schedule DB, 14 ... Exclusive flag management DB, 15 ... Update information management TL, DESCRIPTION OF SYMBOLS 21 ... Network IF part, 22 ... Traffic schedule edit part, 23 ... Update information management TL, 24 ... Work storage part, 25 ... Exclusive flag management TL, 26 ... GUI part, 121 ... Exclusive flag registration part, 122 ... DB update , 123 ... DB transfer part, 221 ... Exclusive flag registration request part, 222 ... Update information registration request part, 223 ... Edit reception part, 224 ... Traffic diagram reading part

Claims (4)

Accepting an update request for traffic diamond data from at least one traffic diamond data editing device, a traffic diamonds data management apparatus itself in accordance with the requirements accepted updates the traffic diamond data held,
Traffic schedule data storage means in which a plurality of traffic schedule data of trains classified hierarchically using train dates and the enforcement date, line section, type of operation purpose, and train number are stored as a plurality of management items ,
And traffic diamond data transmission means for the transportation timetable data storage means reads the stored traffic diamond data, and transmits the traffic timetable data editing device,
An exclusive flag storage means of the hierarchy “major classification” in which the effective date and the user information associated with the effective date are stored as an exclusive flag;
An exclusive flag storage means of the hierarchy “medium classification” in which the effective date and the line area, and the user information associated with the effective date and the line area are stored as an exclusive flag,
An exclusive flag storage means of a hierarchy “sub-class” in which the effective date, line section and type, and user information associated with the effective date, line section and type are stored as an exclusive flag,
An exclusive flag storage means for the hierarchy “for each traffic diagram data” in which the enforcement date, line section, type and train number, and user information associated with the enforcement date, line section, type and train number are stored as an exclusive flag; ,
When an exclusive flag registration request is received from the traffic diagram data editing device,
A process of searching whether or not user information associated with a specified value of a management item corresponding to the predetermined hierarchy included in the exclusive flag registration request is registered in an exclusive flag storage unit of a predetermined hierarchy;
When the associated user information is registered, a process of refusing registration of the exclusive flag;
When the associated user information is not registered and the predetermined hierarchy is not the lowest hierarchy, the exclusive flag registration request includes a management item of a hierarchy one level lower than the predetermined hierarchy A process for detecting whether or not the specified value is further included,
When the associated user information is not registered and the predetermined hierarchy is the lowest hierarchy, or when the specified value is not included in the detection process, the exclusive A process of associating the user information included in the flag registration request with the specified value of the management item and registering it as an exclusion flag in the exclusion flag storage means of the predetermined hierarchy;
If the specified value is included in the detecting process, a process of restarting the search process as the predetermined hierarchy one lower hierarchy,
The exclusive flag registration means for executing until the exclusive flag is registered or the registration is rejected,
When an update request is received from the traffic diagram data editing device,
A process of searching whether or not user information associated with a specified value of a management item corresponding to the predetermined hierarchy included in the update request is registered in an exclusive flag storage unit of a predetermined hierarchy;
When the associated user information is registered, a process for checking whether or not the user information matches the information of the transmission source of the update request;
If it matches the information of the transmission source, the process of updating the traffic diagram data subject to the update request stored in the traffic diagram data storage means according to the update request;
If it does not match the sender's information, processing to refuse traffic diagram data update,
When the associated user information is not registered, and the predetermined hierarchy is the highest hierarchy, a process of rejecting the update of traffic diagram data;
When the associated user information is not registered, and when the predetermined hierarchy is not the highest hierarchy, the search process is restarted with the predetermined hierarchy being one higher hierarchy. When,
The exclusive control means for executing until the traffic diagram data is updated or the update is rejected ,
The exclusive flag registration means sequentially executes processing from the highest level,
The traffic diagram data management apparatus , wherein the exclusive control means sequentially executes processing from the lowest hierarchy . A traffic diagram data editing device for editing traffic diagram data held by the traffic diagram data management device according to claim 1 ,
Working storage means for storing traffic diagram data received from the traffic diagram data management device;
And displays on the display device reads the traffic diamond data stored in said working storage means, accepting editing of traffic diamond data displayed on the display device via the input device, the traffic in accordance with the edits received A traffic diagram data editing means for generating a diagram data update request and transmitting it to the traffic diagram data management device;
The traffic diagram data editing means includes:
The traffic when the diamond data the update request by the management device has not been rejected, the traffic timetable data editing apparatus characterized by updating the traffic diamond data stored in said working storage means in accordance with the edits accepted . The traffic diagram data editing device according to claim 2 ,
The traffic diagram data editing means includes:
A traffic diagram data editing apparatus, wherein the traffic diagram data that has been edited is displayed on the display device so that a state before editing and a state after editing can be identified. Traffic timetable data management apparatus, a traffic diamond data management method of updating the traffic diamond data accepting the update request traffic diamond data from at least one traffic diamond data editing device, itself in accordance with request received is held,
The traffic diagram data management device is a traffic diagram data storage in which a plurality of traffic diagram data classified hierarchically by using an enforcement date, a line section, a type indicating an operation purpose, and a train number are stored as a plurality of management items. Means,
An exclusive flag storage means of the hierarchy “major classification” in which the effective date and the user information associated with the effective date are stored as an exclusive flag;
An exclusive flag storage means of a hierarchy “medium classification” in which the effective date and the line area, and the user information associated with the effective date and the line area are stored as an exclusive flag,
An exclusive flag storage means of a hierarchy “sub-class” in which the effective date, line section and type, and user information associated with the effective date, line section and type are stored as an exclusive flag,
An exclusive flag storage means for the hierarchy “for each traffic diagram data” in which the enforcement date, line section, type and train number, and user information associated with the enforcement date, line section, type and train number are stored as an exclusive flag; The traffic diagram data management method comprises:
Receiving an update request from the traffic diagram data editing device;
For exclusive flag storage means of a predetermined hierarchy,
Searching whether user information associated with the management item included in the update request is registered;
If the associated user information is registered, checking whether the user information matches the information of the transmission source of the update request;
If it matches the information of the transmission source, updating the traffic diagram data subject to the update request stored in the traffic diagram data storage means according to the update request;
If it does not match the sender's information, rejecting the traffic diagram data update;
When the associated user information is not registered and the predetermined hierarchy is the highest hierarchy, the step of rejecting the traffic diagram data update;
If the associated user information is not registered, and if the predetermined hierarchy is not the highest hierarchy, the search process is restarted with the predetermined hierarchy being one higher hierarchy. When,
A traffic diamonds data updates, or traffic diamond data management method and executes until the update is rejected.

Images