Data conversion device and data conversion method
The data conversion device addresses the challenge of compatibility with multiple operation management systems by using a station/arrival/departure time structure graph and inter-station element integration to convert operation plan data effectively.
Patent Information
- Application Number
- JP2023071415
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-25
- Publication Date
- 2024-11-07
AI Technical Summary
Existing data conversion devices are inadequate for converting operation plan data of mobile objects, as they lack versatility to be compatible with various operation management systems.
A data conversion device that includes a station/arrival/departure time structure graph generation unit, an inter-station element integration/replication unit, and a mobile unit combining/dividing unit to convert operation plan data from a conversion source system to a destination system, utilizing a moving object three-element correspondence table and system data structure information.
Enables the conversion of operation plan data to be compatible with various operation management systems, ensuring seamless data transfer and synchronization across different systems.
Smart Images

Figure 2024157205000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a data conversion device and a data conversion method. [Background technology]
[0002] For example, operation plan data for a mobile body that travels on a fixed route, such as a train or a route bus, is managed by an operation management system adopted by an operating company such as a railway company. For example, when converting the operation management system adopted by an operating company to another operation management system, it is necessary to convert the operation plan data that was suitable for the original operation management system into operation plan data that is suitable for the destination operation management system.
[0003] Conventionally, in order to convert operation plan data, it was necessary to analyze the source and destination operation control systems and design and develop a data conversion device each time.
[0004] Regarding data conversion, for example, Patent Document 1 describes a data providing device that provides field data to a service device that provides a service using one or more field data collected at one or more fields, the data providing device comprising: a memory unit that stores pre-registered explanatory information for each of the field data including the specifications of the field data, explanatory information for the field data required by the service and the service including the specifications of the field data, and a conversion rule for converting the specifications of the field data to the specifications required by the service that uses the field data, and a field data conversion execution unit that, in response to a request for transfer of the field data from the service device, refers to the explanatory information for the field data, the explanatory information for the service, and the conversion rule, converts all of the field data used by the service provided by the service device into data of the specifications required by the service, and transmits the converted data to the service device. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2018-072958 A Summary of the Invention [Problem to be solved by the invention]
[0006] According to the data providing device described in Patent Document 1, it is possible to absorb the difference in granularity between source data and destination data. However, when converting operation plan data of a moving object, it is not enough to absorb the granularity alone, and currently there is no data conversion device that can convert operation plan data of a moving object while supporting various source and destination operation management systems.
[0007] The present invention has been made in consideration of the above points, and aims to provide a data conversion device, a data conversion method, and a data conversion system that have the versatility to accommodate various operation management systems that are the source and destination of the conversion, and can convert operation plan data of a moving body. [Means for solving the problem]
[0008] The present application includes a number of means for solving at least some of the above problems, examples of which are as follows.
[0009] In order to solve the above problem, a data conversion device according to one aspect of the present invention is a data conversion device that converts source system operation plan data into destination system operation plan data, the data conversion device comprising one or more arithmetic devices, one or more memory resources, and one or more storage devices, wherein the source system operation plan data is operation plan data for a mobile object that runs on a predetermined route and has a data structure suitable for the source system, the destination system operation plan data is operation plan data for a mobile object that runs on a predetermined route and has a data structure suitable for the destination system, the arithmetic device extracts mobile object three-element information consisting of information on a mobile object, a station, and arrival and departure times from the source system operation plan data based on a source system mobile object three-element correspondence table and source system data structure information, and extracts station information indicating a station where a mobile object travels based on the mobile object three-element information. the station / arrival time structure graph generating unit generating a station / arrival time structure graph consisting of a station node table representing arrival and departure times and an inter-station element table; an inter-station element integrating and replicating unit in which the calculation device integrates and replicates information of each item in the inter-station element table constituting the station / arrival time structure graph in accordance with an integration and replication rule; a moving unit combining and dividing unit in which the calculation device identifies a station at which the moving unit is to be switched based on a source system before and after operation information and the source system operation plan data, and combines and divides the inter-station element table constituting the station / arrival time structure graph into units of the moving unit; and a destination system operation plan data creating unit in which the calculation device generates the destination system operation plan data based on the source system operation plan data, the station / arrival time structure graph, and the destination system data structure information. Effect of the Invention
[0010] According to the present invention, the data can be versatile enough to be compatible with various traffic management systems as source and destination systems, and it is possible to convert operation plan data of a moving object.
[0011] Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is a diagram showing an overview of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of the configuration of a data conversion system according to an embodiment of the present invention. [Diagram 3] FIG. 3 is a diagram illustrating an example of the configuration of a computer that realizes the data conversion device. [Figure 4] FIG. 4 is a diagram showing an example of sample operation plan data for each system. [Diagram 5] FIG. 5 is a diagram showing an example of the data structure of the pre- and post-operation information of each system sample. [Figure 6] FIG. 6 is a diagram showing an example of the data structure of the system-mobile body three-element correspondence table. [Figure 7] FIG. 7 is a diagram showing an example of the data structure of each piece of system data structure information. [Figure 8] FIG. 8 is a flowchart showing an example of the data conversion process. [Figure 9A] FIG. 9A is a flowchart showing an example of the moving object switching information extraction process. [Figure 9B] FIG. 9B is a diagram showing an example of moving object switching information. [Figure 10A] FIG. 10A is a flowchart showing an example of the station / arrival / departure time structure graph generation process. [Figure 10B] FIG. 10B is a diagram illustrating an example of the moving object three-element information. [Figure 11] FIG. 11 is a diagram illustrating an example of the station node table. [Figure 12] FIG. 12 is a diagram illustrating an example of the inter-station element table. [Figure 13] FIG. 13 is a diagram showing an image of a station / arrival time structure graph. [Figure 14] FIG. 14 is a flowchart showing an example of the variation information extraction process. [Figure 15] FIG. 15 is a diagram showing the processes in steps S302 and S303. [Figure 16]FIG. 16 is a diagram showing the process of steps S304 to S310. [Figure 17] FIG. 17 is a diagram showing a display example of the data conversion setting information list screen. [Figure 18] FIG. 18 is a flowchart showing an example of the inter-station element integration and duplication process. [Figure 19] FIG. 19 is a diagram showing the process of step S503. [Figure 20] FIG. 20 is a diagram showing the processes in steps S504 and S505. [Figure 21] FIG. 21 is a flowchart showing an example of the moving object combining / splitting process. [Figure 22] FIG. 22 is a diagram showing the processes in steps S602 and S603. [Diagram 23] FIG. 23 is a diagram showing the processes in steps S606 to S608. [Figure 24] FIG. 24 is a diagram illustrating an example of the converted system operation plan data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In all the drawings for explaining the embodiment, the same members are generally given the same reference numerals, and the repeated description thereof will be omitted. In the following embodiments, the components (including element steps, etc.) are not necessarily essential, except when specifically indicated, or when it is clearly considered essential in principle. In addition, when it is said that "consists of A", "consists of A", "has A", or "includes A", it does not exclude other elements, except when it is specifically indicated that only that element is included. Similarly, in the following embodiments, when referring to the shape, positional relationship, etc. of the components, etc., it includes those that are substantially similar or similar to the shape, etc., except when it is specifically indicated, or when it is clearly considered not to be the case in principle.
[0014] <Summary of the Invention> FIG. 1 is a diagram showing an overview of the present invention.
[0015] The present invention is used, for example, in cases where an operations management system adopted by an operating company is converted to another operations management system, in which operation plan data suitable for the original operations management system (original system operation plan data) is converted to operation plan data suitable for the destination operations management system (destination system operation plan data).
[0016] In addition to the examples mentioned above, the present invention can also be applied to cases such as when trains of one railway company run on the lines of another railway company, when traffic control systems used in Japan are exported to foreign countries, and when operation plan data managed by a traffic control system is shared among other service systems (passenger information systems, etc.).
[0017] Specifically, the source system operation plan data is separated into three mobile body elements (mobile body, station, arrival and departure time) and other attributes, with stations where mobile bodies depart and arrive as nodes and routes between stations as edges, and a station / arrival and departure time structure graph is generated from the three mobile body elements. In addition, mobile body switching information and variation information are generated from each of the source system operation plan data and the destination system operation plan data. Then, the source system operation plan data is converted into destination system operation plan data based on the station / arrival and departure time structure graph, mobile body switching information, and variation information.
[0018] The mobile unit switching information is information that records the switching method (number change rules) associated with the mobile unit switching conditions at a station, specifically, the operation type (turnaround, splitting, merging, destination change, relay (platform change, destination change, etc.)) when the number (train number) representing a mobile unit physically connected at a station is changed.
[0019] The variation information is information that indicates the operation date of the moving object and the description method of the vehicle composition.
[0020] In the following embodiment, a railroad train is used as an example of a moving object. A train refers to a vehicle configuration in which one or more cars are coupled together. However, the moving object is not limited to a railroad train, but also includes buses, trams, monorails, and the like that run along a set route.
[0021] <Configuration example of data conversion system 10 according to one embodiment of the present invention> FIG. 2 shows an example of the configuration of a data conversion system 10 according to an embodiment of the present invention.
[0022] The data conversion system 10 includes a data conversion device 20, a source transportation service system 50 connected to the data conversion device 20 via a network 11, and a destination transportation service system 60.
[0023] The network 11 is a two-way communication network such as a Local Area Network (LAN), a Wide Area Network (WAN), or the Internet.
[0024] The original transportation service system 50 is, for example, a planning system that creates a railway operation plan. The destination transportation service system 60 is, for example, a traffic control system that manages railway operations, or a passenger information system that manages travel information services using railways. The original transportation service system 50 and the destination transportation service system 60 can be provided with one or more systems.
[0025] When multiple systems are provided in the destination transportation service system 60, in addition to being able to synchronize data between the source transportation service system 50 and the destination transportation service system 60, data can also be synchronized between the multiple systems provided in the destination transportation service system 60.
[0026] In addition, the source transportation service system 50 and the destination transportation service system 60 may be, in addition to a planning system, an operation management system, and a travel guidance system, for example, a timetable evaluation system, a delay prediction system, a traffic pedestrian flow simulation system, and the like.
[0027] In the following description, each system refers to the source transportation service system 50 and the destination transportation service system 60. The source transportation service system 50 may also be referred to as the source system, and the destination transportation service system 60 may also be referred to as the destination system.
[0028] The data conversion device 20 is realized by a general computer 100 (FIG. 3), such as a server computer or a personal computer.
[0029] 3 shows an example of the configuration of a general computer 100 that realizes the data conversion device 20. The computer 100 includes a processor 101 such as a central processing unit (CPU), a memory 102 such as a dynamic random access memory (DRAM), a storage 103 such as a hard disk drive (HDD) or a solid state drive (SSD), an input device 104 such as a keyboard, a mouse, or a media drive, an output device 105 such as a display, and a communication module 106 such as an Ethernet (registered trademark) card or a Wi-Fi (trademark) adapter.
[0030] The data conversion device 20 (computer 100) realizes each of the functional blocks of a data acquisition unit 21, a station / arrival / departure time structure graph generation unit 22, a setting information generation unit 23, and a data conversion unit 24 by the processor 101 executing a program 107 stored in a memory 102.
[0031] The program 107 executed by the processor 101 may be stored in advance in the memory 102, or may be downloaded from a removable medium (CD-ROM, flash memory, etc.) or a predetermined server via the network 11, stored in the storage 103, which is a non-transitory storage medium, and read out from the storage 103 when necessary. For this reason, the data conversion device 20 (computer 100) should preferably have an interface for reading data from a removable medium.
[0032] Furthermore, data conversion device 20 is a computer system configured on one physical computer, or on multiple logically or physically configured computers, and may operate on a virtual computer constructed on multiple physical computer resources. For example, multiple programs that realize the functions of data conversion device 20 may each operate on separate physical or logical computers, or multiple programs may be combined to operate on a single physical or logical computer.
[0033] Furthermore, the data conversion apparatus 20 (computer 100 ) holds integration and duplication rules 30 , an input DB (database) 31 , and an output DB 41 in the storage 103 .
[0034] The integration / duplication rules 30 record the integration / duplication process to be executed and its priority (the smaller the value, the higher the priority) in association with the combination of the variation types of the source transportation service system 50 and the destination transportation service system 60 (see FIG. 19). Note that the priority is set according to the variation type of the destination transportation service system 60, and is basically set so that the priority is highest when the variation type is "value type" and lowest when the variation type is "none."
[0035] The input DB 31 stores sample operation plan data for each system 32, sample before and after operation information for each system 33, a three-element correspondence table for each system 34, data structure information for each system 35, source system operation plan data 36, source system before and after operation information 37, and destination system data structure information 38.
[0036] The output DB 41 stores each system sample station / arrival time structure graph 42, each system mobile object switching information 43, each system variation information 44, converted system operation plan data 45, and a station / arrival time structure graph 46.
[0037] The data acquisition unit 21 acquires sample operation plan data, pre- and post-operation information, a mobile object three-element correspondence table, and data structure information from each system, and stores them in the input DB 31 as each-system sample operation plan data 32, each-system sample pre- and post-operation information 33, each-system mobile object three-element correspondence table 34, and each-system data structure information 35. The data acquisition unit 21 also acquires original operation plan data, pre- and post-operation information, and data structure information from the original transportation service system 50, and stores them in the input DB 31 as original system operation plan data 36, original system pre- and post-operation information 37, and destination system data structure information 38.
[0038] The station / arrival / departure time structure graph generating unit 22 executes a sample station / arrival / departure time structure graph generating process (step S2 in FIG. 8) and a station / arrival / departure time structure graph generating process (step S4 in FIG. 8) which will be described later.
[0039] The setting information generating unit 23 is divided into a moving object switching information extracting unit 231 and a variation information extracting unit 232. The moving object switching information extracting unit 231 executes a moving object switching information extracting process (step S1 in FIG. 8) described later. The variation information extracting unit 232 executes a variation information extracting process (step S3 in FIG. 8) described later.
[0040] The data conversion unit 24 is divided into an inter-station element integrating and duplicating unit 241, a moving body combining and dividing unit 242, and a converted system operation plan data generating unit 243. The inter-station element integrating and duplicating unit 241 executes an inter-station element integrating and duplicating process (step S5 in FIG. 8) described later. The moving body combining and dividing unit 242 executes a moving body combining and dividing process (step S6 in FIG. 8) described later. The converted system operation plan data generating unit 243 executes a converted system operation plan data generating process (step S7 in FIG. 8) described later.
[0041] Next, Fig. 4 shows an example of the data structure of the source system operation plan data 36, which is an example of the each-system sample operation plan data 32. Note that this figure is merely an example of operation plan data, and the data structure differs depending on each system.
[0042] The source system operation plan data 36 consists of a train table, a station table, and an arrival / departure time table. In the train table, information on each item, such as the station IDs of one or more stations where the train stops and the operation date, is recorded in association with a train number for identifying one train. In the station table, information on each item, such as the station code, time ID, running order (the order in which the train stops), and platform number, is recorded in association with each station ID recorded in the train table. In the arrival / departure time table, information on each item, such as the arrival time and departure time, is recorded in association with each time ID recorded in the station table.
[0043] In the case of the figure, for example, a train with train number "Tr-A" stops at stations with station IDs "St-AA" and "St-AB" in that order, and the operating day is Monday. The station with station ID "St-AA" has a station code "St-A", a time ID "Tm-AA", is first in the running order (the order in which the train stops), and stops at the track (platform) "Pf-3". Furthermore, the time ID "Tm-AA" in the arrival and departure time table indicates that the arrival time is "08:00:10" and the departure time is "08:02:20".
[0044] Next, FIG. 5 shows an example of the data structure of the pre- and post-system sample operation information 33. In FIG.
[0045] The previous and next operation information represents the relationship between the train number at the time of arrival of a train at each station where turning back, splitting, merging, destination change, relay, etc. occur, and the train number at the time of departure of the train.Information on each of the items (train number at the time of arrival), the next train number (train number at the time of departure), and the operation type (turning back, splitting, merging, destination change, relay, etc.) is recorded in correspondence with the station code of the station where turning back, splitting, merging, destination change, relay, etc. occur.
[0046] In the case of the figure, for example, when a train turns back at a station with station code "St-D", the train number of that train changes from "Tr-A" to "Tr-C". Also, when a train splits at a station with station code "St-C", the train number of that train is carried over from "Tr-A" without change.
[0047] Next, FIG. 6 shows, as an example of the each-system mobile object three-element correspondence table 34, a mobile object three-element correspondence table corresponding to the source system operation plan data 36 (FIG. 4).
[0048] The mobile object three-element correspondence table records information on each item of name and attribute name in correspondence with each of the three elements (mobile object, station, and arrival / departure time). Note that while the mobile object three elements are common to each system, the name and attribute name may differ depending on the system.
[0049] In the same figure, the name of "mobile object," one of the three elements, is "train," the attribute name is "train number," the name of "station," one of the three elements, is "station," the attribute name is "station code," the name of "arrival / departure time," one of the three elements, is "arrival / departure time," and the attribute names are "arrival time" and "departure time."
[0050] Next, FIG. 7 shows, as an example of each system data structure information 35, data structure information corresponding to the source system operation plan data 36 (FIG. 4).
[0051] The data structure information is associated with each table (train, station, arrival / departure time) of the operation plan data, and information on the attribute items of the table is recorded.
[0052] In the same figure, the "Train" table has train number, station ID, etc. as attributes, the "Station" table has station code, time ID, running order, track number, etc. as attributes, and the "Time" table has time ID, arrival time, departure time, etc. as attributes.
[0053] <Data Conversion Process by Data Conversion Device 20> FIG. 8 is a flowchart showing an example of the data conversion process performed by the data conversion device 20. In FIG.
[0054] As a premise for the data conversion process, it is assumed that the input DB 31 of the data conversion device 20 stores each system sample operation plan data 32, each system sample before and after operation information 33, each system mobile body three-element correspondence table 34, each system data structure information 35, source system operation plan data 36, source system before and after operation information 37, and destination system data structure information 38.
[0055] The data conversion process includes steps S1 to S3 executed for a source system and a destination system, and steps S4 to S7 executed for a combination of the source system and the destination system.
[0056] The data conversion process is started, for example, in response to a predetermined operation by a user. First, each system is designated as a processing target in sequence, and the mobile object switching information extraction unit 231 executes a mobile object switching information extraction process by referring to each system sample pre-post operation information 33, thereby generating each system mobile object switching information 43 and storing it in the output DB 41 (step S1).
[0057] <Details of the mobile object switching information extraction process (step S1 in FIG. 8)> FIG. 9A is a flowchart showing an example of a moving object switching information extraction process performed by the moving object switching information extraction unit 231.
[0058] First, the mobile body switching information extraction unit 231 acquires the before and after operation information corresponding to the system to be processed from each system sample before and after operation information 33 (step S101). Next, the mobile body switching information extraction unit 231 classifies the before and after operation information acquired in step S101 into operation types (turning back, splitting, merging, destination change, relay, etc.) (step S102).
[0059] Next, the mobile body switching information extraction unit 231 executes the process of steps S103 to S105 for each operation type. First, the mobile body switching information extraction unit 231 determines an operation type of interest, and determines whether or not the train number of the preceding train and the following train will be changed at a station where the operation type of interest is performed (step S103). Here, if it is determined that the train number of the preceding train and the following train will be changed (YES in step S103), the mobile body switching information extraction unit 231 advances the process to step S104.
[0060] Next, the mobile object switching information extraction unit 231 checks the method (change rule) of switching the train numbers of the preceding and succeeding trains (step S104). Examples of the method of switching the train numbers of the preceding and succeeding trains include having the train number of the preceding train inherited by the succeeding train, moving up the train number of the preceding train (increasing the number by 1) and assigning it to the train number of the succeeding train, and assigning to the succeeding train a train number that has no regularity with the train number of the preceding train.
[0061] Next, the mobile object switching information extraction unit 231 generates mobile object switching information (Figure 9B) that records the train number switching method in association with the operation type under consideration, and registers it in the each system mobile object switching information 43 of the output DB 41 (step S105).
[0062] 9B shows an example of the mobile object switching information generated in step S105. In the case of the figure, for example, the operation type "turn back" is associated with the switching method "irregular", the operation type "split" is associated with the switching method "inherit", and the operation type "merge" is associated with the switching method "advance".
[0063] In step S103, if the mobile object switching information extraction unit 231 determines that the train numbers of the preceding and succeeding trains are not changed (NO in step S103), steps S104 and S105 are skipped. Then, when the processes of steps S103 to S105 for all operation types are completed, the mobile object switching information extraction process is terminated.
[0064] Returning to Fig. 8, next, the station / arrival time structure graph generating unit 22 executes a sample station / arrival time structure graph generating process with reference to each system sample operation plan data 32, each system mobile body three-element correspondence table 34, and each system data structure information 35, thereby generating each system sample station / arrival time structure graph 42 and storing it in the output DB 41 (step S2).
[0065] <Details of the sample station / arrival / departure time structure graph generation process (step S2 in Fig. 8)> Next, FIG. 10A is a flowchart showing an example of a sample station / arrival time structure graph generation process by the station / arrival time structure graph generating unit 22.
[0066] First, the station / arrival time structure graph generating unit 22 refers to each system sample operation plan data 32, each system mobile object three-element correspondence table 34, and each system data structure information 35, and extracts mobile object three-element information (FIG. 10B) from the operation plan data corresponding to the target system to be processed. Furthermore, the station / arrival time structure graph generating unit 22 adds a running order indicating the order of stopping at each station based on the arrival and departure times of each mobile object (step S201).
[0067] 10B shows an example of the mobile object three-element information extracted in step S201. The mobile object three-element information records information on the mobile object, station, arrival and departure times, and running order of the mobile object three elements. In the case of the same figure, for example, it shows that the mobile object "Tr-A" departs from station "St-A" at "08:2:20", then passes through stations "St-B" and "St-C", and arrives at station "St-D" at "08:38:25".
[0068] Next, the station / arrival / departure time structure graph generating unit 22 generates a station node table (FIG. 11) based on the combination of the station and the arrival / departure time included in the extracted mobile object three-element information (step S202).
[0069] Fig. 11 shows an example of a station node table. In the station node table, station codes, arrival times, and departure times are recorded in association with station nodes. In the case of the same figure, for example, station node "B-1" is associated with station code "St-B", arrival time "08:06:45", and departure time "08:07:10". Note that if the same station and arrival / departure times are used by different moving objects, different station nodes are assigned.
[0070] Next, the station / arrival / departure time structure graph generating unit 22 generates an inter-station element table (FIG. 12) based on the moving object three element information extracted in step S201 (step S203).
[0071] Fig. 12 shows an example of an inter-station element table. The inter-station element table is information representing the departure and arrival stations of a moving object and their departure and arrival times, and records a moving object (train number), departure station node, arrival station node, departure station code, arrival station code, departure time, and arrival time in association with an inter-station element code. Inter-station element groups will be described later.
[0072] In the case of the same figure, for example, the inter-station element code "AB-1" is associated with the mobile unit (train number) [Tr-A], the departure station node "A-1", the arrival station node "B-1", the departure station code "St-A", the arrival station code "St-B", the departure time "08:02:00", and the arrival time "08:46:45".
[0073] Next, the station / arrival / departure time structure graph generating unit 22 classifies, among the inter-station elements in the inter-station element table generated in step S203, a plurality of inter-station elements having the same origin station code, arrival station code, departure time, and arrival time into the same inter-station element group, and classifies each inter-station element into a different inter-station element group for those that do not have the same origin station code, arrival station code, departure time, and arrival time (step S204). For example, in the case of Fig. 12, the inter-station element code "AB-1" and the inter-station element code "AB-2" have the same origin station code, arrival station code, departure time, and arrival time, and are therefore classified into the same inter-station element group "a".
[0074] Next, the station / arrival / departure time structure graph generating unit 22 stores the station node table generated in step S202 and the inter-station element tables classified into inter-station element groups in step S204 as a station / arrival / departure time structure graph corresponding to the system to be processed in the sample station / arrival / departure time structure graph 42 for each system in the output DB 41 (step S205). With this, the sample station / arrival / departure time structure graph generating process is terminated.
[0075] Fig. 13 shows an image of a station / arrival / departure time structure graph consisting of the station node table shown in Fig. 11 and the inter-station element table shown in Fig. 12. The station / arrival / departure time structure graph represents a moving object (train number), station nodes and station codes of stations where the train stops, arrival and departure times at the stations, and inter-station element codes to the next station where the train stops.
[0076] When generating a station / arrival / departure time structure graph corresponding to the source transportation service system 50, if there is a deficiency in the source system operation plan data, the station / arrival / departure time structure graph generation unit 22 creates a station / arrival / departure time structure graph by interpolating the deficiency using information from the source system operation plan data having the same station node or inter-station element.
[0077] Returning to Fig. 8, next, the variation information extraction unit 232 executes a variation information extraction process with reference to each system sample operation plan data 32, each system mobile object three-element correspondence table 34, and each system sample station / arrival / departure time structure graph 42, thereby generating each system variation information 44 and storing it in the output DB 41 (step S3).
[0078] <Details of the variation information extraction process (step S3 in FIG. 8)> FIG. 14 is a flowchart showing an example of a variation information extraction process performed by variation information extraction section 232.
[0079] First, the variation information extraction unit 232 acquires a sample station / arrival time structure graph corresponding to the system to be processed from each system sample station / arrival time structure graph 42 (step S301).
[0080] Next, the variation information extraction unit 232 refers to each system mobile object three-element correspondence table 34 for each inter-station element group in the inter-station element table included in the sample station / arrival / departure time structure graph acquired in step S301, and specifies that the attribute name of the mobile object in the processing target system is train number. Then, from each system sample operation plan data 32, it acquires the inter-station elements belonging to the target inter-station element group, the mobile object (train number), and the vehicle composition, operation date, type, etc. corresponding to the mobile object information (train number) (step S302).
[0081] FIG. 15 shows an example of inter-station elements belonging to the same inter-station element group a, moving bodies (train numbers), and information such as vehicle composition, operation dates, and types corresponding to the moving bodies (train numbers), acquired in step S302.
[0082] Next, the variation information extraction unit 232 refers to the information acquired in step S302 and detects attributes whose values vary depending on the inter-station element as candidates for variation attributes (step S303). For example, in the case of Fig. 15, vehicle composition and operation days are detected as attributes whose values vary depending on the inter-station element.
[0083] Next, variation information extraction unit 232 executes the processes of steps S304 to S310 in order for each attribute whose value differs depending on the inter-station element.
[0084] First, the variation information extraction unit 232 classifies non-target attributes, among the attributes whose values differ depending on the inter-station elements, into those with the same value (step S304).
[0085] Fig. 16 shows the classification result of the example shown in Fig. 15. For example, when the operation date is the target attribute, if the vehicle composition, which is not the target attribute, is classified by the same value, the vehicle composition is classified into three types: "1,2,3", "4,5,6", and "1,2,3,4,5,6". Also, for example, when the vehicle composition is the target attribute, if the operation date, which is not the target attribute, is classified by the same value, the vehicle composition is classified by the day of the week, such as "Monday", "Tuesday", etc.
[0086] Next, the variation information extraction unit 232 refers to the classification result of step S304 and determines whether the attribute value of the target attribute in the all-station element group is singular (step S305). If it is determined that the attribute value is singular (YES in step S305), then the variation information extraction unit 232 determines whether the attribute values of the target attribute in the all-station element group are different (step S306). If it is determined that the attribute values of the target attribute in the all-station element group are different (YES in step S306), then the variation information extraction unit 232 designates the target attribute as a variation attribute, determines its type to be "value type", and records it in each system variation information 44 (step S307).
[0087] If it is determined in step S306 that the attribute values of the target attribute in the all-station element group are not different (are the same) (NO in step S306), the target attribute is not designated as a variation attribute, and step S307 is skipped.
[0088] If it is determined in step S305 that the attribute value of the target attribute in the all-station element group is not singular (is plural) (NO in step S305), then variation information extraction unit 232 determines whether or not there is an inclusion relationship in the attribute values of the target attributes (step S308). If it is determined that there is an inclusion relationship in the attribute values of the target attributes (YES in step S308), then variation information extraction unit 232 designates the target attribute as a variation attribute, determines its type to be "subset type", and records it in each system variation information 44 (step S309).
[0089] If it is determined in step S308 that there is no inclusion relationship in the attribute values of the target attribute (NO in step S308), then variation information extraction unit 232 designates the target attribute as a variation attribute, determines its type to be "category type", and records this in each system variation information 44 (step S310). This ends the variation information extraction process.
[0090] In the case of FIG. 16, for example, the attribute values "Monday", "Tuesday", etc. of the target attribute "operation date" are singular and have different values, so the variation type is determined to be "value type". Also, for example, the attribute values "1,2,3", "4,5,6", "1,2,3,4,5,6", etc. of the target attribute "vehicle configuration" are not singular (they are plural), and "1,2,3,4,5,6" includes "1,2,3" and "4,5,6", so the variation type is determined to be "subset type". Also, although not shown in the figure, for example, when the attribute values of the target attribute "operation date" are "Monday, Tuesday, Wednesday, Thursday, Friday", "Saturday, Sunday, holiday", etc., these are not singular (they are plural) and there is no inclusion relationship, so the variation type is determined to be "classification type".
[0091] As described above, steps S1 to S3 are executed for each system as the processing target, and then steps S4 to S7 are executed for the combination of the source system and the destination system as the processing target, for example, in response to an operation by a user specifying the combination of the source system and the destination system.
[0092] FIG. 17 shows an example of a data conversion setting information list screen 1000 displayed as a UI screen presented to a user when, for example, a combination of a conversion source system and a conversion destination system is specified.
[0093] The data conversion setting information list screen 1000 displays a mobile object three-element correspondence table, variation information, and mobile object switching information corresponding to the conversion source system and the conversion destination system, respectively.
[0094] The user can check the mobile object three-element correspondence table, variation information, and mobile object switching information of the conversion source and destination on the data conversion setting information list screen 1000. In addition, if there is an error or no information recorded in the mobile object three-element correspondence table, variation information, and mobile object switching information of the conversion source and destination, the user can correct the error or add the no-recorded information.
[0095] Return to Fig. 8. Next, for example, a combination of a source system and a destination system designated by the user is set as a processing target, and the station / arrival / departure time structure graph generating unit 22 executes a source station / arrival / departure time structure graph generating process with reference to each system mobile object three-element correspondence table 34, each system data structure information 35, and the source system operation plan data 36, thereby generating a station / arrival / departure time structure graph 46 and storing it in the output DB 41 (step S4). Note that the source station / arrival / departure time structure graph generating process is similar to the sample station / arrival / departure time structure graph generating process (step S2), so a description thereof will be omitted.
[0096] Next, the inter-station element integration / duplication unit 241 refers to the integration / duplication rules 30, the source system operation plan data 36, each system variation information 44, and the station / arrival / departure time structure graph 46, and executes an inter-station element integration / duplication process to update the station / arrival / departure time structure graph 46 (step S5).
[0097] <Details of Inter-Station Element Integration and Replication Processing (Step S5 in Figure 8)> FIG. 18 is a flowchart showing an example of the inter-station element integrating and duplicating process performed by the inter-station element integrating and duplicating unit 241.
[0098] First, the inter-station element integration / duplication unit 241 acquires the station / arrival / departure time structure graph 46 (generated in step S4) based on the source system operation plan data 36 from the output DB 41 (step S501). Next, the inter-station element integration / duplication unit 241 acquires variation information corresponding to the source system and the destination system from each system variation information 44 (step S502). Next, the inter-station element integration / duplication unit 241 refers to the integration / duplication rules 30 and determines the integration / duplication processes to be executed and the execution order thereof (step S503).
[0099] FIG. 19 is a diagram showing the processing of step S503. For example, as shown in the figure, it is assumed that the type of the variation attribute "vehicle composition" in the conversion source system is "subset type", the type of the variation attribute "operation date" is "value type", and the type of the variation attribute "operation date" in the conversion destination system is "classification type". In this case, since the variation attribute "vehicle composition" has a variation type of "subset type" in the conversion source system and a variation type of "none" in the conversion destination system, it is determined to execute the processing of the ninth line "list and integrate elements of the union of values, priority 3". Furthermore, since the variation type of the variation attribute "operation date" in the conversion source system is "value type" and the variation type of the conversion destination system is "classification type", it is determined to execute the processing of the first line "list and integrate values into defined groups, priority 2". And, since the processing for the variation attribute "operation date" has a higher priority than the processing for the variation attribute "vehicle composition", it is determined that the processing order for the variation attribute "operation date" is first and the processing order for the variation attribute "vehicle composition" is second. When the priorities are equal, the order of processing may be determined by any method.
[0100] Next, the inter-station element integration / duplication unit 241 refers to the inter-station element table constituting the station / arrival / departure time structure graph 46, designates each inter-station element group as a processing target, and executes the processing of steps S504 and S505. First, the inter-station element integration / duplication unit 241 refers to the source system operation plan data 36, and assigns the attribute value of the variation information to the inter-station elements of the inter-station element group to be processed (step S504). Next, the inter-station element integration / duplication unit 241 executes the integration / duplication processing determined in step 503 according to the execution order (step S505).
[0101] FIG. 20 is a diagram showing the processing of steps S504 and S505. For example, when the processing target is the inter-station element group a, for example, the attribute values "1, 2, 3" of the variation attribute "vehicle composition" and the attribute value "month" of the variation attribute "operation date" are assigned to the inter-station element "AB-1" belonging to the inter-station element group a. The same is done for other inter-station elements (step S504). Next, a process of "listing and integrating the values of 'operation date' into a defined group" is performed. As a result, the attribute values of the variation attribute "operation date" are listed as "Monday, Tuesday, Wednesday, Thursday, Friday". Next, a process of "listing and integrating the elements of the union of the values of 'vehicle composition'" is performed. As a result, the attribute values of the variation attribute "vehicle composition" are listed as "1, 2, 3, 4, 5, 6". In the integration and duplication process, the inter-station elements, moving bodies, departure station nodes, arrival station nodes, etc. (not shown in FIG. 20) are also listed.
[0102] Then, after executing the processes of steps S504 and S505 for all inter-station element groups, the inter-station element integration and duplication unit 241 next updates the inter-station element tables constituting the station / arrival / departure time structure graph 46 to those after the integration and duplication process (step S506). With this, the inter-station element integration and duplication process is completed.
[0103] Returning to Fig. 8, next, the moving entity combining / splitting unit 242 refers to the source system operation plan data 36, the source system before and after operation information 37, each system moving entity switching information 43, and each system variation information 44, and executes moving entity combining / splitting processing to update the station / arrival / departure time structure graph 46 (step S6).
[0104] <Details of moving object combining / splitting process (step S6 in FIG. 8)> FIG. 21 is a flowchart showing an example of the moving object combining / splitting process performed by the moving object combining / splitting unit 242. As shown in FIG.
[0105] First, the moving object combining / splitting unit 242 acquires the station / arrival / departure time structure graph 46 (updated through step S3) based on the source system operation plan data 36 from the output DB 41 (step S601).
[0106] Next, the mobile unit combining / splitting unit 242 refers to the inter-station element table constituting the station / arrival / departure time structure graph 46, and executes the processes of steps S602 and S603 for the combination of adjacent inter-station element groups across the same station node list. The combination of adjacent inter-station element groups across the same station node list refers to the combination of inter-station element groups whose arrival station node and departure station node match.
[0107] First, the moving entity combining / splitting unit 242 judges whether or not the attributes "vehicle composition" and "operation date" have the same attribute value in the combination of station-to-station element groups (step S602). If it is judged that they have the same attribute value (YES in step S602), then the moving entity combining / splitting unit 242 assigns the same moving entity number to the combination of station-to-station element groups (step S603). Note that if it is judged that the attributes "vehicle composition" and "operation date" do not have the same attribute value in the combination of station-to-station element groups (NO in step S602), the processing of step S603 is skipped.
[0108] 22 is a diagram showing the processing of steps S602 and S603. In the case of the figure, for example, the destination station node of the inter-station element group a in the first row matches the departure station node of the inter-station element group b in the third row, so the inter-station element groups a and b are a combination of adjacent inter-station element groups across the same station node list. And, since the attribute values of the attributes "vehicle composition" and "operation date" of the combination of inter-station element groups have the same values "1, 2, 3, 4, 5, 6" and "Mon, Tue, Wed, Thu, Fri", respectively, the inter-station element groups a and b are assigned the same mobile unit number "Tr-XXX".
[0109] Next, the mobile unit combining / splitting unit 242 refers to each system mobile unit switching information 43 and acquires mobile unit switching information of each of the source transportation service system 50 and the destination transportation service system 60 (step S604). Next, the mobile unit combining / splitting unit 242 acquires the source system before and after operation information 37 (step S605).
[0110] Next, the mobile unit combining / splitting unit 242 compares the mobile unit switching information of the source transportation service system 50 with the mobile unit switching information of the destination transportation service system 60 to identify an operation type that does not exist in the mobile unit switching information of the source transportation service system 50 but exists in the mobile unit switching information of the destination transportation service system 60. Furthermore, the mobile unit combining / splitting unit 242 identifies stations where pre- and post-operations of the identified operation type occur (stations where a change in train number occurs) based on the source system pre- and post-operation information 37 (step S606).
[0111] Next, the moving entity combining / splitting unit 242 sequentially focuses on the stations identified in step S606, and executes the processes of steps S607 and S608. First, the moving entity combining / splitting unit 242 refers to the inter-station element table of the station / arrival / departure time structure graph 46, and acquires inter-station elements before and after the focused station (inter-station elements with the focused station as an arrival station node and inter-station elements with the focused station as a departure station node) that have the same moving entity number assigned (step S607).
[0112] Next, the mobile unit combining / splitting unit 242 changes the same mobile unit numbers assigned to the inter-station elements before and after the station of interest acquired in step S607 according to a switching method according to the operation type occurring at the station of interest (step S608).
[0113] FIG. 23 is a diagram showing the processing of steps S606 to 608. For example, as shown in the figure, if only "return" is recorded as the operation type in the original moving object switching information, and "return", "connection", "merge", and "split" are recorded as the operation types in the changed moving object switching information, in step S606, stations where the operation types "connection", "merge", and "split" occur are identified. Then, for example, if it is identified that "connection" occurs at station D, in step S607, among the inter-station elements d and e before and after station D, those that are assigned the same moving object number "Tr-ZZZ" are acquired. Then, the moving object number of the inter-station element d is changed to "Tr-ZZZ1", and the moving object number of the inter-station element e is changed to "Tr-ZZZ2". With this, the moving object combining / splitting processing is terminated.
[0114] Returning to Fig. 8, next, the converted system operation plan data generating unit 243 executes a converted system operation plan data generating process by referring to the source system operation plan data 36, the converted system data structure information 38, and the station / arrival / departure time structure graph 46, and stores the converted system operation plan data 45 obtained as a result in the output DB 41 (step S7).
[0115] 24 shows an example of the converted system operation plan data 45. In the converted system operation plan data 45, information on StatusCode, Arr, Depth, OperationDay, VehicleComposition, and TrainClass is recorded in association with TrainCode.
[0116] As is clear from a comparison between the destination system operation plan data 45 and the source system operation plan data 36 (FIG. 4), the destination system operation plan data 45 and the source system operation plan data 36 (FIG. 4) have substantially the same information content, but differ in data structure such as the names and order of items. In other words, the data conversion device 20 can convert the source system operation plan data 36 (FIG. 4) into the destination system operation plan data 45, which has a different data structure.
[0117] The present invention is not limited to the above-described embodiment, and various modifications are possible. For example, the above-described embodiment has been described in detail to clearly explain the present invention, and is not necessarily limited to those having all of the configurations described. In addition, it is possible to replace a part of the configuration of one embodiment with a configuration of another embodiment, or to add a part of the configuration of another embodiment.
[0118] In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware, for example, by designing a part or all of them in an integrated circuit. In addition, each of the above configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as a program, table, file, etc. that realizes each function can be placed in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD. In addition, the control lines and information lines are shown as those considered necessary for explanation, and not all control lines and information lines are necessarily shown in the product. In reality, it may be considered that almost all configurations are connected to each other. [Explanation of symbols]
[0119] 10. Data conversion system 11. Network 20. Data conversion device 21 Data acquisition section 22. Arrival / Departure Time Structure Graph Generation Unit 23. Setting information generation unit 231....Mobile object switching information extraction unit 232...Variation information extraction unit 24 Data conversion section 241···Inter-station element integration·duplicate section 242 Mobile body connection and division section 243: Destination system operation plan data generation unit 30. Integration and duplication rules 31 Input DB 32 System sample operation plan data 33 System sample pre- and post-operation information 34 System Mobile Three-Element Correspondence Table 35 System Data Structure Information 36... Original system operation plan data 37. Operational information of the source system before and after conversion 38. Destination system data structure information 41 Output DB 42 Arrival and Departure Time Structure Graph 43 System Mobile Switching Information 44 System variation information 45... Destination system operation plan data 46 Arrival and Departure Time Structure Graph 50..Source transportation service system 60... Destination transportation service system 100. Computer 101 Processor 102 Memory 103 Storage 104 Input Device 105 Output device 106 Communication module 107 Program 1000 Data conversion setting information list screen
Claims
1. A data conversion device for converting source system operation plan data into destination system operation plan data, One or more computing devices, one or more memory resources, and one or more storage devices; The source system operation plan data is operation plan data for a moving object that travels on a determined route, and has a data structure suitable for the source system, The conversion destination system operation plan data is operation plan data for a moving object that travels on a determined route, and has a data structure suitable for the conversion destination system, a station / arrival / departure time structure graph generating unit for extracting mobile object three-element information consisting of information on mobile objects, stations, and arrival / departure times from the original system operation plan data based on the original system mobile object three-element correspondence table and the original system data structure information, and generating a station / arrival / departure time structure graph consisting of a station node table representing stations and arrival / departure times through which the mobile object moves and an inter-station element table based on the mobile object three-element information; an inter-station element integration / duplication unit configured to integrate and duplicate information of each item in the inter-station element table that configures the station / arrival / departure time structure graph according to an integration / duplication rule; a mobile unit combining / dividing unit configured to identify a station at which the mobile unit is to be switched based on the pre-conversion system operation information and the pre-conversion system operation plan data, and to combine / divide the inter-station element table constituting the station / arrival / departure time structure graph into units of the mobile unit; A data conversion device characterized in that the calculation device has a destination system operation plan data creation unit that generates the destination system operation plan data based on the source system operation plan data, the station / arrival / departure time structure graph, and the destination system data structure information.
2. 2. The data conversion device according to claim 1, The data conversion device is characterized in that the inter-station element integrating / duplicating unit sets inter-station element groups in the inter-station element table that constitutes the station / arrival / departure time structure graph, in which inter-station element groups have the same arrival / departure times at the same station, and integrates and duplicates information of each item in the inter-station element table for each inter-station element group.
3. 2. The data conversion device according to claim 1, the computing device has a mobile object switching information extraction unit that extracts, from the sample pre- and post-sample operation information for each of the source system and the destination system, an operation type in which switching of an identification number for a physically connected mobile object occurs and a switching method of the identification number as mobile object switching information; The data conversion device is characterized in that the mobile object combining / splitting unit combines and splits the inter-station element table that constitutes the station / arrival / departure time structure graph into units of the mobile object based on a difference in the mobile object switching information between the source system and the destination system.
4. 4. The data conversion device according to claim 3, the inter-station element integration / duplicating unit sets an inter-station element group having the same arrival / departure time at the same station in the inter-station element table constituting the station / arrival / departure time structure graph, The data conversion device is characterized in that the mobile object combining / splitting unit assigns a common provisional mobile object number to adjacent inter-station element groups in the inter-station element table that have the same attribute values related to mobile objects, and then changes the provisional mobile object numbers based on a difference in the mobile object switching information between the source system and the destination system.
5. 2. The data conversion device according to claim 1, The arithmetic device has a variation information extraction unit that extracts, for each of the source system and the destination system, variation information that indicates a condition under which a variation occurs in the moving object from sample operation plan data, a sample station / arrival time structure graph based on the sample operation plan data, and a moving object three-element correspondence table based on the sample station / arrival time structure graph, A data conversion device characterized in that the inter-station element integration / duplication unit determines an integration / duplication process to be executed from among a plurality of integration / duplication processes defined by the integration / duplication rules based on the differences between the source system and the destination system of the variation information.
6. 6. The data conversion device according to claim 5, The variation information extraction unit sets at least one of the vehicle composition and operation days of the moving body as variation attributes, and generates the variation information by classifying the description method of the attribute value of the variation attribute into a variation type.
7. 7. The data conversion device according to claim 6, The data conversion device is characterized in that the inter-station element integration / duplication unit determines, for each variation attribute, an integration / duplication process to be executed from among a plurality of integration / duplication processes defined by the integration / duplication rules based on the combination of the variation types of the source system and the destination system.
8. 7. The data conversion device according to claim 6, A data conversion device characterized in that the inter-station element integration / duplication unit determines the order of execution of the integration / duplication process in accordance with the priority set in the integration / duplication rules based on the variation type of the destination system.
9. 2. The data conversion device according to claim 1, The data conversion device is characterized in that, when there is a deficiency in the source system operation plan data, the station / arrival / departure time structure graph generation unit interpolates the deficiency using information of the same station node or inter-station element in the source system operation plan data.
10. A data conversion method by a data conversion device in which a computer converts source system operation plan data into destination system operation plan data, comprising: The source system operation plan data is operation plan data for a moving object that travels on a determined route, and has a data structure suitable for the source system, The conversion destination system operation plan data is operation plan data for a moving object that travels on a determined route, and has a data structure suitable for the conversion destination system, The computer includes one or more arithmetic units, one or more memory resources, and one or more storage devices; a station / arrival / departure time structure graph generation step in which the arithmetic device extracts mobile object three-element information consisting of information on mobile objects, stations, and arrival / departure times from the original system operation plan data based on the original system mobile object three-element correspondence table and the original system data structure information, and generates a station / arrival / departure time structure graph consisting of a station node table representing stations and arrival / departure times through which mobile objects move and an inter-station element table based on the mobile object three-element information; an inter-station element integration / duplication step in which the calculation device integrates and duplicates information of each item in the inter-station element table constituting the station / arrival / departure time structure graph according to an integration / duplication rule; a moving body combining / dividing step in which the arithmetic device identifies a station at which the moving body is switched based on the conversion source system before and after operation information and the conversion source system operation plan data, and combines / divides the inter-station element table constituting the station / arrival / departure time structure graph into units of the moving body; A data conversion method comprising: a destination system operation plan data creation step in which the calculation device generates the destination system operation plan data based on the source system operation plan data, the station / arrival / departure time structure graph, and the destination system data structure information.
Citation Information
Patent Citations
Data providing device and data providing method
JP2018072958A
