KR20120047899A - On-demand bus service scheduling system and method using service history - Google Patents

Abstract

The on-demand bus operation scheduling system extracts and extracts characteristic information regarding the passenger's elevation in advance from a database storing the history of the operation in accordance with the reservation and the result of the passenger's elevation, and the history of the operation stored in the database. Means for storing information in the database corresponding to the reservation included in the service history corresponding to the information and the extracted characteristic information, and the current characteristics for determining the driving schedule match the characteristics indicated by the characteristic information. A means for determining a service schedule of the on demand bus is provided on the basis of the reservation information included in the service history corresponding to the information.

Description

On-demand bus scheduling system and its method using on-going driving record {ON-DEMAND BUS SERVICE SCHEDULING SYSTEM AND METHOD USING SERVICE HISTORY}

This application claims the priority of Japanese Patent Application No. 2009-164678 for which it applied on July 13, 2009 in 2009, and quotes in this application with reference to the content.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an on demand bus system that operates in accordance with a request from a user, and more particularly, to a service scheduling system and a service scheduling method.

On-demand buses are examined to reduce traffic congestion and to save energy in transportation organizations. Regarding the on demand bus system, when a request for a particular ride is received from a visitor using a ride position, a destination, a desired ride time, and the number of passengers, a system for determining an appropriate route to a destination that satisfies the request is disclosed in Patent Document 1 Is disclosed in. The route of the on-demand bus described in Patent Document 1 includes a ride point of use required by all passengers, a destination of passengers, each current position of a plurality of buses, a currently scheduled route of each bus, and traffic conditions. Is determined as a function of

Patent Document 1: Japanese Patent Laid-Open No. 10-241091

According to the technology described in Patent Literature 1, each passenger's request (ride position, destination, desired ride time) is satisfied by determining the route. However, with the enlargement of the on demand bus system, for example, the expansion of the service area, the increase in the number of buses running, and the increase in passengers, it takes time to determine the route, so that there is little time for the desired ride time. There is a case where the request cannot be met. In order to solve the case where such a request cannot be met, there is an operation that secures the time required for determining the route, for example, 30 minutes before the desired ride time or 1 hour before, but such an operation is on demand. Compromise the intrinsic convenience of the bus.

In such a situation, there is a need for a travel schedule system of an on demand bus system that shortens the time required for route determination.

In order to solve the above problems, a service scheduling system and method for an on demand bus utilizing the following service results are disclosed.

The service scheduling system extracts and extracts characteristic information on the passenger's elevation in advance from a database storing the operation record according to the reservation and the result of the passenger's elevation in the on demand bus and the operation record stored in the database. Means for storing information indicative of reservations included in the service history corresponding to the extracted information and the extracted characteristic information in a database;

When the current situation in which the service schedule is determined matches the situation indicated by the property information, a means for determining the service schedule of the on demand bus is provided based on the reservation information included in the service history corresponding to the matched property information. do.

A more preferable service scheduling system has a service history according to the reservation and the result of the passenger's getting up and down at least when the passenger's getting on and off, at least one time of the getting on and off time, and the date and time when the on-demand bus ran. Include information about

A more preferable service scheduling system extracts the characteristic information from the service history based on the regularity of at least one time of the lift position and the lift time of the passenger.

A more preferable service scheduling system is based on the correlation between each piece of information of the passenger's elevation position, at least one time of the elevation time, and the weather information of the date and time when the on-demand bus was operated as a result of the characteristic information from the operation results. Extract

According to the present invention, since the service schedule is determined in advance from the service history, the time required for determining the service schedule can be shortened, or a service plan with many passengers can be generated.

1 is a configuration diagram of an on demand bus system according to the present embodiment.
2 is a structural example of a reservation information table.
3 is a structural example of a performance information table.
4 is a structural example of a characteristic information table.
5 is a flowchart of a process for determining a travel schedule.
6 is an illustration of a target area of operation of a bus.
7A is an example of the determined driving schedule.
7B is an example of the determined driving schedule.
8 is an example of the determined driving schedule.

EMBODIMENT OF THE INVENTION Hereinafter, embodiment of this invention is described using drawing. 1, the block diagram of the on demand bus system of this embodiment is shown. The on demand system includes a reservation reception system 2 that accepts a request from a user who wishes to ride on an on demand bus (hereinafter, referred to as a bus) 1, a reservation information from the reservation reception system 2, and a bus ( The service which collects the service scheduling system 3 which determines the service schedule of the bus 1, the service information of the bus 1 based on the service results of 1), and stores it in the service database 5 as the service history. Has an information system 4. The service history of the bus 1 used by the service scheduling system 3 is stored in the service database 5. In addition, although the details are omitted, it is the current information of the area (operation area: the whole area that operates the bus) operating the on demand bus system, and the congestion information (congestion, road section or The travel time of a predetermined section), weather conditions, and the like are collected, and stored in association with the date and time information (date, date, day of the week, holiday, time, etc.) in the operation database 5.

Although one bus is shown in FIG. 1, the number of buses is determined according to the area of an operation area and the number of guests of an on demand bus system. The number of buses is determined in units of one area, between one area and another within the operating area, based on time zones and geographic features such as the presence of shopping malls, hospitals, public facilities, and even steep slopes. . A bus which is not assigned to an area may be prepared, and may be temporarily assigned to an area where a small number of users wish to ride the bus in response to a request from the user.

In the description of the present embodiment, the service scheduling system 3 that determines the service schedule of the bus so as to satisfy the passenger's desire to ride on the dispatched bus is described in detail.

In FIG. 1, for ease of understanding, the reservation reception system 2, the travel scheduling system 3, the travel information system 4, and the travel database 5 are shown separately, but in one computer having a database system. It may implement | achieve by a distributed system by several computers according to the load and a function of each system.

In addition, the bus 1 includes a radio communication device for communication with the travel scheduling system 3 and the travel information system 4, and the GPS for grasping the position and the current time of the bus 1 Global Positioning System) device. The position and current time of the bus 1 are transmitted to the service information system 4 as service information.

The reservation reception system 2 accepts the request from the user who wishes to ride by mail or telephone. The operator may receive the boarding request from the user and input the received content into the reservation reception system 2, but when the user becomes familiar with (boarding desired position, boarding desired position, boarding desired time or boarding desired time, and number of passengers) If you become accustomed to the delivery of the requirements necessary for riding, etc.), automatic reception is possible. In the case of an email, the content of boarding desired is extracted as reservation information by using the mail which uses a predetermined | prescribed format, or by parsing and semantic analysis of the sentence of an email in the reservation reception system 2. As shown in FIG. In the case of a telephone, the speech recognition apparatus is operated at the previous stage of the structure of accepting by mail to extract a sentence. Extracting reservation information from this sentence is the same as that of the mail.

Even in the case of an e-mail or a telephone, in the case of automatic reception, the lack of a requirement for boarding desire is found at the stage of extracting reservation information. In this case, the addition of the missing information is requested by a reply mail or a callback of the telephone.

The structural example of the reservation information table contained in the service database 5 is shown in FIG. 2, and the structural example of the performance information table is shown in FIG. The content of the reservation information table stores the reservation information received by the reservation acceptance system 2 by the program in the operation scheduling system 3. This program is activated by a reception interrupt from the reservation acceptance system 2, stores reservation information in the reservation information table via the operation scheduling system 3, and sends a response to the received reservation information to the operation scheduling system 3 ), The obtained response is returned to the user, and the processing is terminated.

The reservation information table has each column of the reservation number 50, the passenger information 51, the reservation information 52, and the reservation confirmation flag 53. As shown in FIG. The reservation information 52 further includes a month day 54, a day 55, a ride (desired) time 56, a get off (desired) time 57, a ride (desired) position 58, a get off (desired) position And the number of ride (desired) people 60.

The reservation number 52 is used when responding to the user that the reception is completed, and is used by the service scheduling system 2 to identify the reservation information 52 reflected in the service schedule. Although mentioned later, when storing the driving result in the driving database 5, it is also used in order to identify which reservation information corresponds to which reservation information.

The passenger information 51 is, for example, a passenger identifier for identifying a passenger (same meaning as a user). Using a passenger identifier as a key, a passenger database storing attribute information such as a passenger's name, address, telephone number, and the like is searched. The reservation confirmation flag 53 is a flag indicating that the reservation information 52 is reflected in the service schedule and the confirmed reservation information is returned as a response to the user. In other words, the service scheduling system 2 has shown that the reservation confirmation flag 53 reflects the reservation information of ON to the service schedule of the bus 1. In the reservation confirmation flag 53, a blank indicates OFF and * indicates a pending state. The pending state will be described later.

Each item of the reservation information 52 is made clear by the example mentioned later. However, the parenthesis time of the column of the riding time 56 and-(hyphen) of the column of the getting off time 57 are demonstrated. The requirements necessary for the ride request by the reservation reception system 2 have been described in terms of a desired ride position, a desired position for getting off, a desired ride time or a desired time for getting off, and the number of passengers. If both the desired ride time and the desired ride time are required, the situation in which the bus 1 which strictly adheres to the designated desired time occurs in the ride desired position and the disembarked desired position occurs, so that one of the requirements is required. do. When the boarding desired time is specified,-(hyphen) is stored in the column of the getting off time 57. When the getting-off desired time is specified, the arrival prediction time of the bus 1 to the boarding (desired) position 58 determined by the travel scheduling system 2 is stored in parentheses in the column of the boarding time 58. This arrival estimated time is included in the response returned to the user as confirmed reservation information, so that the user can wait for the bus 1 before the expected arrival time at the boarding desired position.

In actual operation of the on-demand bus system of the present embodiment, in consideration of sudden road obstacles due to a traffic accident or the like, the boarding desired time and the getting off desired time have an allowable width of, for example, ± 2 minutes and ± 5 minutes. Is operated.

In addition, the reservation information table shown in FIG. 2 has shown the state of 10:10 on Sunday, June 21 in order to demonstrate a specific example later.

As for the content of the performance information table, the service information received by the service information system 4 from the bus 1 is stored by the service information system 4. The driving information from the bus 1 includes not only information according to the running (position, speed, etc.) of the bus, but also lifting information (location, time, etc.) of each passenger. In this embodiment, since the running schedule of the bus 1 is determined based on the elevation information of each passenger as a result, the information according to the running of the bus is omitted. The performance information table has each column of the reservation number 50, the passenger information 51, and the performance information 61. As shown in FIG. The performance information 52 further includes columns such as the ride time 62, the get off time 63, the ride position 64, the get off position 65, the number of people on the ride 66, and the door car 67. The reservation number 50 and the passenger information 51 are the same as the reservation number 50 and the passenger information 51 of the reservation information table, and each record of the performance information table is each reservation information 52 of the reservation information table. In response, the driving record is stored. Therefore, the reservation information and the performance information are collectively called the operation performance. Here, although the reservation information table and the performance information table are divided and explained, you may comprise one table which made the reservation number 50 and the passenger information 51 common. Each item of the performance information 61 becomes clear by the example mentioned later.

In addition, the performance information table shown in FIG. 3 has shown the state of 10:10 on Sunday, June 21 in order to demonstrate a specific example later.

In FIG. 4, the structural example of the characteristic information table contained in the running database 5 is shown. The characteristic information table has a characteristic column 70 for storing the characteristic of the passenger obtained from the driving record stored in the reservation information table and the performance information table, and a reservation number 71 indicating the characteristic. The characteristics of the passengers are obtained by data mining techniques or other techniques based on the repair planning method, which find correlations and regularities (patterns) between the items of the driving performance (contents of the reservation information table and contents of the performance information table). The characteristic of No. 1 of FIG. 4 is that "Passenger A gets on from every position α every Sunday and gets off at 10:25 from position β." It is a characteristic based on regularity obtained from reservation numbers 25, 75, 102, 126 and the like. The characteristic of No. 2 is that "Passenger B gets on at 10:15 from position (gamma) and gets off at position (beta) when it rains on Sunday, and gets off at position (beta)."). It is a characteristic based on the regularity, the boarding matter 62, the disembarkation time 63, etc. obtained from the reservation numbers 26, 127, etc., and the correlation between items with the weather 68.

5 shows a flowchart of processing for the service scheduling system 3 to determine the service schedule. This process starts execution one day before the on-demand bus system starts operating. First, it is determined whether there is characteristic information (step 100). The criterion for this determination is the date and time information corresponding to the current information stored in the operation database 5 described briefly, and in particular, the current time. In other words, it is determined whether there is characteristic information including the ride time within a predetermined time from the current time. The predetermined time is, for example, 10 minutes. If it is too long, the modification of the operation schedule determined for the reservation of the new ride request is large, and if it is too short, there is a possibility that the operation schedule cannot be determined until the time when the operation schedule should be determined. In other words, this determination determines whether or not the current situation (including time) for determining the driving schedule matches the situation indicated by any one of the characteristic information.

If there is characteristic information, it is determined whether or not there is reservation information (step 110). Although the reservation information also includes reservation information for riding in five hours, if there is reservation information, a service schedule corresponding to the reservation information is determined. This is because the user is waiting for a response indicating whether the bus 1 can be boarded in accordance with the desired ride. As mentioned above, in the case of the reservation information which specified the getting-down desired time, the virtual riding desired time in a boarding position is calculated by subtracting the travel time between the getting-down desired time and the getting-down position. The running time may use a slightly longer time than the successful running time, and does not have to be a strict value.

If there is the reservation information, the operation schedule is determined using the characteristic information and the reservation information (step 120). If not, the operation schedule is determined using the characteristic information (step 140).

In step 100, if there is no characteristic information, it is determined whether there is reservation information (step 150). If there is reservation information, a travel schedule is determined using the reservation information (step 160). If there is no reservation information, the flow returns to step 100. In other words, if there is no characteristic information and no reservation information within a predetermined time from the current time, an idle loop is executed by executing steps 100 and 150.

The bus 1 is notified of the operation schedule determined in any one of step 120, step 140, and step 160 (including the case where the already determined one is corrected) (step 130).

An example of the process of determining a driving schedule is shown. The target area of the bus 1 of this example is shown in FIG. In FIG. 6, the solid line indicates the road on which the bus 1 can travel. The broken line shows some examples of the travel route determined as the travel schedule of the bus 1. The Greek letters α, β, γ, ... denote a user's riding position or getting off position. x1, x2,... And the like indicate the intersection position. In reality, latitude and longitude are used for positional information such as the boarding position and the getting off position, but the symbol (Greek character and xn (n = 1, 2, 3, ...) is used here.

A first example will be described. The current time is set to 10:00 on Sunday, June 7, and the predetermined time set in step 100 of FIG. 5 is 10 minutes. Referring to the characteristic table shown in FIG. 4, the characteristic 70 of No. 1 is determined as characteristic information (step 100). The reservation number corresponding to the characteristic information of No. 1 is obtained. In view of the current time in the column of the reservation number 71, the latest reservation number is 75. The reservation content whose value of a reservation number is 75 is copied, 102 is added to the reservation number 50 as new reservation information, and it stores in the reservation information table with the copy content. At this time, the reservation confirmation flag is set to * (pending).

Since there is no reservation information within 10 minutes of the predetermined time (step 110: NO), the operation schedule using the characteristic information is determined (step 140). In this step, it is assumed that the reservation information whose value of the reservation number field 50 corresponding to the characteristic information is 102 is temporarily reserved, and determines the travel schedule.

The travel schedule shown in FIG. 7A is obtained. The service schedule shown in FIG. 7A indicates that the bus 1 departs from the position α at 10:10 and arrives at the position β at 10:25 via the intersections x1, x2, x3, x4, and x5.

The determination of the driving schedule is based on the shortest time path search or the shortest distance path search from the origin to the destination. These include a table of travel times for each road section (for example, between intersections) and the up and down direction corresponding to the distance, and add these distances or travel times for each candidate path and display a minimum value. How to choose a path. When traveling time changes with the road congestion degree, the traveling time according to the congestion degree is provided in a table, and used.

When reservation information whose value of the reservation number column 50 is 102 is reserved, the service scheduling system 3 changes the reservation confirmation flag 53 from * to ON, and changes the reservation acceptance system 2 to the effect of reservation. Notify User A via

By notifying the bus 1 of the determined service schedule (step 130), the bus 1 operates to arrive at the position α at 10:10. When it is not yet reserved by the user A at 10:10 arriving at the position α, the service scheduling system 3 cancels the service of the bus 1 unless the service schedule corresponds to the reservation information from another user.

A second example will be described. Time passes from the first example and assumes the present time 10:07 on Sunday, June 7. Referring to the characteristic table shown in FIG. 4, since there is no characteristic information (step 100: 'no'), and there is reservation information in which the value of the field of the reservation number 50 is 103 (step 150: 'yes'), reservation information Determine the driving schedule using (step 160). In addition, since the reservation information table of FIG. 2 shows the state of 10:10 on Sunday, June 21, the reservation confirmation flag 53 of the row whose value of the column of the reservation number 50 is 103 shows ON. However, it is OFF (blank) at 10:07 on Sunday, June 7th. At the time of 10:07, the bus 1 has already run toward the position α by the service schedule shown in Fig. 7A. If the schedule of the reservation number 50 reflects the reservation information of 103 and reflects the schedule information, the schedule is again as shown in FIG. 7B. That is, at time 10: 17, the traveling route to the position β and the position η is obtained via the position Δ. Similarly, the path search from the position Δ to the position β and the path search from the position β to the position η are performed. FIG. 7B shows that the service schedule is determined by modifying the service schedule of the bus 1 determined to be 10:00 on Sunday, June 7.

As a result of the route search, if the constraint of 10:17 at the position Δ and 10:25 arrival at the position β cannot be satisfied, the reservation information with the value 103 in the field of the reservation number 50 is based on the operation schedule of the other bus. It is used for the decision. When we cannot incorporate in service schedule of any bus, we inform about user C who sent reservation information that value of column of reservation number 50 is 103 together with the intention that reservation cannot be made with the intention that we cannot make reservation do.

A third example will be described. The date and time pass from the second example and assume the present time on Sunday, June 21 10:10, rainy day. Already referring to the characteristic table shown in FIG. 4, in response to the reservation information whose value of the field of the reservation number 50 is 158 at 10:00, a travel schedule is determined using No. 1 of the characteristic information, and 10 Corresponding to the reservation information in which the value of the column of the reservation number 50 is 159 at: 05, the service schedule is determined using No. 2 of the characteristic information. These are shown in service schedule No. 1 and No. 2 of FIG. At 10:10, there is no new characteristic information (Step 100: No), and since the value of the field of the reservation number 50 has a reservation information of 160 (Step 150: Yes), the service schedule using the reservation information (Step 160). As a result, service schedule No. 3 in FIG. 8 is obtained. Since the value of the field of the reservation number 50 cannot reflect the reservation information of 160, it is abbreviate | omitted about determination of a driving schedule as it is the same as the example mentioned above.

According to the present embodiment, since the service schedule is determined in advance from the service history, the time required for the determination of the service schedule can be shortened. Since the requirements of the running schedule are reflected in the running schedule, the time required for determining the driving schedule can be shortened, and the occurrence of a situation that cannot meet the needs of the passengers can be reduced. have. As a result, the sharing schedule can determine a large number of driving schedules.

1: On Demand Bus
2: reservation reception system
3: driving scheduling system
4: driving information system
5: driving database

Claims (8)

A database for storing passengers on and off the buses according to their reservations and performances;
Extracting characteristic information about the ascent of the passenger in advance from the driving record stored in the database, and matching the extracted characteristic information with information indicating the reservation included in the driving record corresponding to the extracted characteristic information. Means for storing in,
The service schedule of the on-demand bus based on the reservation information included in the service history corresponding to the matched feature information when the current situation in which the service schedule is determined matches the situation indicated by the feature information. A service scheduling system for an on-demand bus, characterized in that it provides a means for determining. The method of claim 1,
The driving record according to the reservation and the track record regarding the lift of the passenger is based on at least one time of the lift position of the passenger, the lift time, and the weather on the date when the on-demand bus was operated as the track record. A service scheduling system for an on demand bus, comprising information. The method of claim 2,
And the characteristic information is extracted from the service history based on the regularity of the elevation position of the passenger and at least one time of the elevation time. The method of claim 2,
The characteristic from the driving record is based on a correlation between the lift position of the passenger, at least one time of the lift time, and the information on the weather information of the date and time when the on-demand bus was operated as the track record. An on-demand bus operation scheduling system for extracting information. As a method of determining the on-demand bus service schedule by a computer having a database for storing a passenger's on / off bus according to its reservation and performance,
Extracting characteristic information about the ascent of the passenger from the driving record stored in the database,
Storing information indicative of the reservation included in the driving record corresponding to the extracted characteristic information and the extracted characteristic information in the database,
The service schedule of the on-demand bus based on the reservation information included in the service history corresponding to the matched feature information when the current situation in which the service schedule is determined matches the situation indicated by the feature information. The operation scheduling method of the on-demand bus, characterized in that for determining. The method of claim 5,
The driving record according to the reservation and the track record regarding the lift of the passenger stored in the database is at least one time of the lift position of the passenger, the lift time, and the on-demand bus as the track record. A service scheduling method for an on-demand bus, characterized in that it includes information about a weather of a date and time. The method of claim 6,
And the computer extracts the characteristic information from the driving record based on the regularity of the elevating position of the passenger and the at least one time of the elevating time. The method of claim 6,
The computer is configured to perform the operation based on a correlation between the elevating position of the passenger, at least one time of the elevating time, and the information on the weather information of the date and time when the on demand bus was operated as the performance. The service scheduling method of the on-demand bus, characterized in that the characteristic information is extracted from the results.

Images