JP7344755B2 - Traffic management device, traffic management method, and terminal - Google Patents

Description

The present invention relates to a traffic management device, a traffic management method, and a terminal.

In recent years, for example, in areas with serious population decline and aging, the number of users of public transportation such as buses has decreased, and as ridership has declined, public transportation has become less frequent or even discontinued. It has been done.

In these areas, on-demand public transportation, such as on-demand buses and shared taxis that operate according to user requests, is attracting attention. Technologies related to operation control of on-demand public transportation are known (for example, see Patent Document 1 and Patent Document 2).

Patent No. 5928588 Japanese Patent Application Publication No. 2013-186541

However, with on-demand public transportation, routes may not be fixed or it may not be possible to estimate the time required to reach a destination. Therefore, it may be difficult for users to incorporate travel time into their schedules, making it difficult to use the service. On the other hand, if public transportation is a scheduled route type that operates on a fixed route at a fixed time, it is easy to estimate the required time, but due to cost and other reasons, few people use public transportation. Service may be difficult in some areas. For example, in view of this situation, it is desired to provide a management technique for operation that is preferable in situations where there are few users.

The present invention has been made in view of the above points, and an object of the present invention is to provide an operation management device, an operation management method, and a terminal for operating a mobile body according to an operation schedule that is easy to use even when there are few users. shall be.

An operation management device according to one aspect of the present invention has a plurality of operation schedules that define schedules for operating mobile objects on fixed routes, and each operation schedule overlaps with at least one other operation schedule in the execution time period. a reception unit that accepts reservations for multiple operation schedules, and a reservation control unit that, when a reservation is received at the reception unit, stops accepting reservations for an operation schedule whose execution time zone overlaps with the reserved operation schedule; a management unit that outputs instructions so that the mobile unit operates according to the reserved operation schedule; If the user cancels a reservation for the reserved operation schedule, and there are no other users who have made reservations for the canceled operation schedule, the reservation control unit may cancel the reservation for the canceled operation schedule. The present invention is characterized in that acceptance of reservations for an operation schedule whose execution time period overlaps with the canceled operation schedule is resumed .

A mobile object can be operated with an easy-to-use schedule even when there are few users.

It is a figure explaining operation of an exemplary mobile object. FIG. 3 is a diagram illustrating a schedule according to an embodiment. 1 is a diagram illustrating an operation management system according to an embodiment. 1 is a diagram illustrating a block configuration of a traffic management device according to an embodiment. FIG. 2 is a diagram illustrating a block configuration of a user's terminal according to an embodiment. FIG. 2 is a diagram illustrating a timetable according to an embodiment. FIG. 3 is a diagram illustrating an operation flow of reservation processing for an operation schedule according to an embodiment. FIG. 3 is a diagram illustrating a reservation reception screen according to the embodiment. FIG. 3 is a diagram illustrating an operational flow of reservation cancellation processing according to the embodiment. FIG. 3 is a diagram illustrating an operational flow of a display control process for a reservation reception screen according to an embodiment. FIG. 3 is another diagram illustrating a reservation reception screen according to the embodiment. 1 is a diagram illustrating a hardware configuration of a computer according to an embodiment.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the drawings. Note that the same reference numerals are given to corresponding elements in a plurality of drawings.

FIG. 1 is a diagram illustrating the operation of an exemplary mobile object 102. Note that the mobile object 102 may be, for example, a public transportation such as a bus that operates on regular routes. FIG. 1(a) is a diagram showing an exemplary operation schedule 101. As shown in FIG. The operation schedule 101 is, for example, information that defines a schedule for operating the mobile object 102 on a regular route, and may include an operation preparation period and a post-processing period in addition to the operation period required for the operation of the mobile object 102. good. For example, in FIG. 1A, the operation schedule 101 includes three periods: an inspection period, an operation period, and an energy charging period. Note that the inspection period and the energy charging period may not be included in the operation schedule 101 depending on the situation. The inspection period is, for example, a period during which defects or abnormalities in the mobile body are inspected before operation. The operation period is, for example, a period during which the mobile object 102 operates on a predetermined route. The energy filling period is, for example, a period in which the mobile body 102 is charged with energy consumed during operation. Filling with energy may include, for example, charging a storage battery and filling a fuel tank with gasoline, diesel oil, liquefied natural gas, compressed natural gas, hydrogen, heavy oil, and the like.

Moreover, in the example of FIG. 1(a), the mobile object 102 moves from point A to point B during the operation period, and then travels on a route returning to point A. For example, the area between point A and point B includes a plurality of boarding and alighting locations for passengers to get on and off the vehicle. The boarding and alighting place may be, for example, a stop such as a bus stop. The boarding and alighting place may be fixed at a fixed location, or may be moved within a predetermined area, such as being set somewhere within a predetermined area such as a village depending on the situation. Good too. Note that although an example is shown here in which the route is operated so as to connect point A to point B in the operation schedule 101, the embodiment is not limited to this. For example, it is assumed that the route of the operation schedule 101 includes a route that departs from point A, tours the boarding and alighting locations, and then returns to point A.

Further, FIG. 1(b) is a diagram showing an exemplary schedule. The schedule includes, for example, a plurality of schedules 101 executed during a predetermined period such as one day. In addition, in FIG. 1(b), a part of the schedule is extracted. Here, for example, assume that there is only one mobile object 102 that can be used to operate the route. In this case, once the mobile object 102 starts executing the operation schedule 101, the next operation schedule 101 cannot be started until the operation schedule 101 is completed. Therefore, in the schedule of FIG. 1(b), the plurality of schedules 101 are arranged so that their execution time periods do not overlap.

As described above, the moving route of the moving object 102 that operates on a regular route is approximately fixed, so compared to on-demand public transportation, it is easier to estimate the time required to reach the destination. users have the advantage of easily incorporating travel time into their schedules. However, when the number of movable bodies 102 that can be used to operate a route is small, the number of operation schedules 101 that can be executed simultaneously is limited to the number of movable bodies 102, resulting in longer service intervals. For example, assume that the time required to execute one operation schedule 101 is 60 minutes, as shown in FIG. 1(a). In this case, the service interval in the schedule of FIG. 1(b) will be one every 60 minutes at the shortest. When the service interval becomes longer, the user may not be able to use the mobile object 102 at a time that is convenient for him or herself, reducing convenience for the user.

Furthermore, for example, as shown in FIG. 1(b), if a schedule is set up to run at a fixed time, the schedule 101 can be executed even if there are no passengers on board. This results in unnecessary costs.

As described above, in a situation where there are few users, it may be difficult to operate the mobile body 102 on a scheduled route type. Therefore, it is desired to provide a technology that can operate a mobile object according to an easy-to-use schedule even when there are few users.

In the embodiment described below, a travel schedule is created for a mobile object 102 operated on a fixed route so that the travel schedule 101 overlaps with at least one other travel schedule 101 in the execution time period. If a reservation is made for one of the operation schedules 101 out of the plurality of operation schedules 101 included in the operation schedule, reservations for other operation schedules 101 whose execution time periods overlap will be stopped, and the operation will be suspended. do.

FIG. 2 is a diagram illustrating a schedule 200 according to the embodiment. In addition, in FIG. 2, a part of the schedule 200 is extracted. For example, in FIG. 2A, the operation schedule 101b has the same execution time period as the operation schedule 101a and the operation schedule 101c. Note that, as described above, it is assumed here that there is only one mobile object 102 that can be used for operation on the route. In this case, since the three operation schedules 101a to 101c have overlapping execution time periods, only one of them can be executed by one mobile object 102.

However, in the embodiment, ride reservations from users are accepted for a plurality of operation schedules 101 in the operation table 200, and when a reservation is made for the operation schedule 101, other operation schedules 101 whose execution time periods overlap with the operation schedule 101 are accepted. We will stop accepting reservations and suspend operations. For example, FIG. 2(b) shows a case where a reservation is made for the operation schedule 101b, and the reservation confirms the operation of the operation schedule 101b, and also the operation schedule 101a whose execution time period overlaps with the operation schedule 101b. We have stopped accepting reservations for service schedule 101c and the service has been suspended. Then, the mobile body 102 is operated according to the reserved operation schedule 101b.

Thereby, even one moving object 102 can execute the operation schedule 101 included in the operation table 200. Further, when making a reservation, the user can select an operation schedule 101 that is convenient for him/her from among many operation schedules 101. Therefore, user convenience is improved.

Further, for example, since the operation of the overlapping operation schedule 101 due to the reservation is suspended, users who wish to use the mobile object 102 in the same time period thereafter are encouraged to ride in the reserved operation schedule 101. Furthermore, by not executing the service schedule 101 when no reservations are made, it is possible to avoid unnecessary costs such as carrying out service when there are no passengers.

Furthermore, since the above-described embodiment operates on a fixed route, it is easy for the user to estimate travel time and arrival time. Hereinafter, embodiments will be described in more detail.

FIG. 3 is a diagram illustrating the traffic management system 300 according to the embodiment. The traffic management system 300 includes, for example, a traffic management device 301, a mobile object 102, a user terminal 302, and a control terminal 303. In one example, the traffic management device 301 may be a server located in the cloud 310. The operation management device 301 is communicably connected to the mobile body 102 and the user's terminal 302 via a mobile communication network 350, which is an example of a network. Further, the traffic management device 301 is communicably connected to a control terminal 303 via the Internet, for example. The control terminal 303 may be, for example, a terminal installed in an office that is responsible for the operation of the mobile object 102, and the person in charge of operation management may collect information regarding the operation from the control terminal 303. . The control terminal 303 may be communicably connected to the mobile body 102 via the mobile communication network 350, for example.

The operation management device 301 receives, for example, a reservation for boarding the mobile object 102 from a user's terminal 302. The user's terminal 302 may be, for example, a smartphone, a tablet terminal, a mobile phone, or the like. The operation management device 301 also transmits operation instructions to the mobile object 102 via the control terminal 303 or directly to the mobile object 102, thereby managing the operation of the mobile object 102. . In addition, below, the case where operation instructions are transmitted to the mobile object 102 via the control terminal 303 will be explained as an example. In addition, the notification to the mobile body 102 may be executed, for example, by notifying a communication terminal provided in the mobile body 102 or a terminal held by the driver of the mobile body 102. The moving object 102 may be, for example, a vehicle, a ship, a train, or an airplane used for transportation or freight transportation. In the following, a case will be explained in which the moving object 102 is a bus.

FIG. 4 is a diagram illustrating a block configuration of the traffic management device 301 according to the embodiment. The traffic management device 301 includes, for example, a control section 401, a storage section 402, and a communication section 403. The control unit 401 operates as, for example, a reception unit 411, a reservation control unit 412, a management unit 413, and the like. The storage unit 402 may store, for example, information on reservations for the schedule 200, a timetable 600 (described later), and the schedule 101, and the like. The communication unit 403 communicates with the user's terminal 302, the control terminal 303, a communication terminal provided in the mobile object 102, and a terminal held by the driver, for example, according to instructions from the control unit 401. The details of each of these units and the information stored in the storage unit 402 will be described later.

FIG. 5 is a diagram illustrating a block configuration of the user terminal 302 according to the embodiment. Terminal 302 includes, for example, a control section 501, a storage section 502, a communication section 503, a display section 504, and an input section 505. The control unit 501 operates as, for example, a request unit 511 and a display control unit 512. The storage unit 502 may store, for example, reservation information for displaying a reservation reception screen 800, which will be described later. The communication unit 503 communicates with the operation management device 301 according to instructions from the control unit 501, for example. The display unit 504 displays information on a display screen, for example. Input unit 505 receives input from a user, for example. For example, the user may input information regarding a reservation, which will be described later, via the input unit 505. The details of each of these units and the information stored in the storage unit 502 will be described later.

FIG. 6 is a diagram illustrating a timetable 600 according to the embodiment. The timetable 600 shows scheduled departure times of a plurality of operation schedules 101 at boarding and alighting locations for each time slot. For example, FIG. 6 illustrates a timetable 600 at point A. Note that, as described in FIG. 2, the operation schedule 101 corresponding to the scheduled departure time of the timetable 600 may have an execution time period that overlaps at least in part with other operation schedules 101. Although the timetable 600 in FIG. 6 shows an example in which the operation schedule 101 is executed at 20-minute intervals, the embodiment is not limited to this, and other schedules such as 5-minute intervals and 10-minute intervals are shown. It may be an interval.

[Reservation reception process]
Next, a reservation process for boarding the moving object 102 according to the embodiment will be described. In addition, below, the case where the operation management apparatus 301 manages the operation of one mobile object 102 as the mobile object 102 which can be used for the operation of a route will be explained as an example. However, the embodiment is not limited to this, and the embodiment may be applied to operation management of a plurality of moving objects 102.

FIG. 7 is a diagram illustrating an operational flow of reservation processing for the operation schedule 101 according to the embodiment. For example, upon receiving a reservation information inquiry from the user's terminal 302, the control unit 401 of the operation management device 301 may start the operation flow shown in FIG. Note that the inquiry may include, for example, information about the boarding location where the user wishes to board the vehicle and the alighting location where the user desires to get off the vehicle.

In step 701 (hereinafter, step will be abbreviated as "S", for example, S701), the control unit 401 notifies the terminal 302 of reservation information. The reservation information includes, for example, information indicating the reservation status for the operation schedule 101 included in the operation table 200, and the control unit 501 of the terminal 302 controls the display screen of the display unit 504 of the terminal 302 based on the received reservation information. The reservation reception screen 800 may be displayed.

FIG. 8 is a diagram illustrating a reservation reception screen 800 displayed on the display unit 504 of the terminal 302 according to the embodiment. The reservation reception screen 800 includes, for example, information indicating the desired pick-up and drop-off locations that the user inputs into the input section 505 of the terminal 302 when inquiring about reservation information. In FIG. 8, an example is shown in which the boarding location is point A and the alighting location is point B. Further, on the reservation reception screen 800, a list 801 showing the reservation status for the operation schedule 101 is displayed. In the list 801, records in which departure times, arrival times, and reservation statuses are associated are registered, and each record corresponds to each of the operation schedules 101 of the operation table 200. The departure time is, for example, the time at which the train departs from the point A designated as the boarding location in each operation schedule 101 of the travel table 200. Further, the arrival time is the time at which the vehicle arrives at point B, which is the alighting place in each of the operation schedules 101 of the operation table 200. The reservation status is information indicating the reservation status for the operation schedule 101 corresponding to the record.

For example, the reservation reception screen 800 in FIG. "Empty" is displayed in the status.

Here, for example, assume that the user inputs an operation to apply for a reservation for the operation schedule 101 with a departure time of 11:20 on the terminal 302, and transmits the reservation application to the operation management device 301. Then, the operation flow in FIG. 7 proceeds to S702.

In S702, the control unit 401 of the operation management device 301 receives a reservation application from the terminal 302 via the mobile communication network 350 and the communication unit 403.

In S703, the control unit 401 registers the user's information in the operation schedule 101 for which the reservation was applied, and executes the reservation. For example, the control unit 401 may register user information for identifying the user and information on the user's boarding location and alighting location in the operation schedule 101 for which a reservation has been applied.

In S704, the control unit 401 determines whether the operation schedule 101 for which the reservation has been accepted already has another reservation. If no other reservation is included in the operation schedule 101 for which the reservation has been accepted (S704 is NO), the flow advances to S705.

In S705, the control unit 401 stops accepting reservations for the operation schedule 101 whose execution time slot overlaps with the operation schedule 101 for which the reservation has been made. This is because, as described with reference to FIG. 2, if the mobile unit 102 executes the service schedule 101 that has a reservation, the mobile unit 102 will not be able to execute other service schedules 101 that have overlapping time slots. It is.

Further, if there is already another reservation in the operation schedule 101 for which the reservation was accepted in S704, YES is determined in S704, and the flow advances to S706. This is because other operation schedules 101 whose execution time slots overlap with the operation schedule 101 for which reservations have been accepted are already set to stop accepting reservations when another reservation has been made.

In S706, the control unit 401 transmits a reservation completion notification to the user's terminal 302, indicating that the reservation has been completed. Note that the reservation completion notification may include other information such as operation information such as the time when the mobile object 102 will arrive at the reserved pick-up and drop-off locations.

In S707, the control unit 401 outputs an instruction to execute the reserved operation schedule 101, and this operation flow ends. For example, the control unit 401 may transmit an instruction to execute the reserved operation schedule 101 to the control terminal 303. When the control terminal 303 receives an instruction to execute the reserved operation schedule 101, the control terminal 303 may transmit the instruction to a communication terminal provided in the mobile object 102, a terminal held by the driver, or the like. Thereby, the driver of the mobile object 102 can execute the reserved operation schedule 101 according to the execution instruction.

FIG. 8(b) is a diagram illustrating a reservation acceptance screen 800 after the reservation is accepted. For example, in the operation flow of FIG. 7, assume that a reservation is accepted for the service schedule 101 with a departure time of 11:20. In this case, when a reservation information inquiry is subsequently received from another user's terminal 302, the control unit 401 of the operation management device 301 sends the reservation information to display the reservation reception screen 800 of FIG. 8(b) in S701. may be transmitted to another user's terminal 302. Then, a reservation reception screen 800 shown in FIG. 8(b) is displayed on the display screen of another user's terminal 302.

In FIG. 8B, the reservation status of the service schedule 101 with the departure time of 11:20 in the list 801 has been changed to information indicating that the service has been confirmed by reservation. Note that the reservation status may additionally include information on the number of remaining seats that can be boarded. On the other hand, the reserved service schedule 101 with a departure time of 11:20 and the service schedules 101 with departure times of 11:00 and 11:40, which overlap in execution time, are grayed out because their reservation status is set to reservation acceptance cancelled. , and users are no longer able to make reservations. In this way, by stopping accepting reservations for the operation schedules 101 to be executed during overlapping time periods, it becomes possible to provide the users with the operation schedules 101 that can actually be executed. In addition, by ceasing to accept reservations, subsequent users who wish to board the moving object 102 at 11:00, for example, are encouraged to make a reservation according to the operation schedule 101 with a departure time of 11:20, and The occupancy rate of the body 102 can be improved. Note that if it is not convenient for subsequent users, they can also make a reservation for the service schedule 101 after 12:00.

As described above, according to the operation flow shown in FIG. 7, the user can make a reservation by being presented with a larger number of operating schedules 101 than the number of actually available operating schedules 101. Therefore, the user can select the operation schedule 101 at the desired time from among many virtually presented operation schedules 101, and the convenience of transportation for the user is improved.

In the above-described embodiment, when a reservation is made for the operation schedule 101, acceptance of reservations for the operation schedule 101 whose execution time slot overlaps with that operation schedule 101 is stopped. Thereby, the mobile body 102 can be operated according to the actually executable operation schedule 101.

Further, for example, in the embodiment, since the execution of the operation schedule 101 is confirmed after a reservation is made, unnecessary operation of the mobile object 102 can be suppressed.

[Reservation cancellation process]
Next, reservation cancellation processing will be explained. FIG. 9 is a diagram illustrating an operational flow of reservation cancellation processing according to the embodiment. For example, upon receiving a reservation cancellation request from the user's terminal 302, the control unit 401 may start the operation flow shown in FIG. 9 .

In S901, the control unit 401 cancels the reservation by deleting the reservation information from the operation schedule 101 specified in the reservation cancellation request. Note that the reservation cancellation request may include information for specifying the reservation to be canceled. For example, a reservation cancellation request includes information identifying the service schedule 101 in which the reservation to be canceled is registered, user information for identifying the user who sent the reservation cancellation request, and information for identifying the flight reservation for the reservation to be canceled. May include location and drop-off location information.

In S902, the control unit 401 determines whether the operation schedule 101 in which the reservation was canceled includes another reservation. If there are no other reservations (NO in S902), the flow advances to S903.

In S903, the control unit 401 determines whether or not the operation period has not started in the operation schedule 101 for which the reservation has been canceled and the mobile object 102 has not yet departed. If the mobile object 102 has not yet departed (S903 is YES), the operation schedule 101 can be canceled, and the flow advances to S904.

In S904, the control unit 401 cancels the suspension of accepting reservations for the operation schedule 101 whose execution time period overlaps with the operation schedule 101 for which the reservation was canceled, and resumes accepting reservations.

In S905, the control unit 401 transmits a cancellation instruction to the control terminal 303 to cancel the execution of the operation schedule 101 whose reservation has been canceled, and the flow advances to S909. Note that, upon receiving the cancellation instruction, the control terminal 303 may notify the cancellation instruction to, for example, a communication terminal provided in the mobile object 102 or a terminal held by the driver. Thereby, the driver of the mobile object 102 can cancel the execution of the operation schedule 101.

Further, if the mobile object 102 has already departed in S903 (NO in S903), the flow advances to S906, and the control unit 401 sends a passage instruction to the control terminal 302 to instruct it to pass through the boarding and alighting place of the canceled reservation. and the flow advances to S909. Note that, upon receiving the passage instruction, the control terminal 303 may notify the passage instruction to, for example, a communication terminal provided in the mobile object 102 or a terminal held by the driver. This allows the driver to know that there is no need to stop at the pick-up/drop-off location where the reservation has been canceled.

Further, if the operation schedule 101 whose reservation was canceled in S902 includes a reservation by another reservist (YES in S902), the flow advances to S907.

In S907, the control unit 401 determines whether the boarding and alighting location of the user in the canceled reservation is the same as the boarding and alighting location in the reservation made by another person. If the boarding and alighting locations are the same (YES in S907), the flow advances to S909. On the other hand, if at least one of the boarding and alighting locations is different in S907 (NO in S907), the flow advances to S908.

In S908, the control unit 401 transmits a passing instruction to the control terminal 303, instructing the user to pass through a boarding and alighting place of the user whose reservation has been canceled that does not match the boarding and alighting place of the other reservation user. Then, the flow advances to S909. Note that, upon receiving the passage instruction, the control terminal 303 may transmit the passage instruction to, for example, a communication terminal provided in the mobile object 102 or a terminal held by the driver. This allows the driver to know that there is no need to stop at the boarding/alighting location for which the driver has been instructed to pass.

In S909, the control unit 401 notifies the terminal 302 of the user who sent the reservation cancellation request that the cancellation is complete, and this operation flow ends.

Note that it is assumed that S904 of the operation flow in FIG. 9 is executed and reservation acceptance is resumed. In this case, on the reservation reception screen 800 displayed on the user's terminal 302, the reservation status of the operation schedule 101 for which the reservation was canceled and the operation schedule 101 whose time period overlaps with that operation schedule 101 is displayed as ``no reservation is made''. It may be set to "empty" to indicate that there is no data.

According to the above operation flow of FIG. 9, when all reservations for the operation schedule 101 are cancelled, the control unit 401 resumes accepting reservations for the operation schedule 101 whose time slot overlaps with that operation schedule 101. be able to.

According to the operation flow in FIG. 9, if the boarding and alighting location of the user who canceled the reservation does not match the boarding and alighting location of other reservation users, the control unit 401 causes the user to pass through the unmatched boarding and alighting location. Additionally, the operation of the mobile object 102 can be managed.

[Display control of reservation reception screen]
Next, display control of the reservation reception screen 800 executed by the control unit 501 of the user's terminal 302 will be explained. FIG. 10 is a diagram illustrating an operation flow of display control processing of the reservation reception screen 800 according to the embodiment. Note that the control unit 501 of the user's terminal 302 may start the operation flow shown in FIG. 10, for example, when an instruction to execute an inquiry about reservation information is input. The execution instruction for the reservation information inquiry may include, for example, information on the boarding location and the alighting location desired by the user.

In S1001, the control unit 501 of the user's terminal 302 sends an inquiry to the operation management device 301 requesting provision of reservation information between the boarding location and the alighting location desired by the user. In S1002, the control unit 501 receives reservation information in response from the operation management device 301.

In S1003, the control unit 501 of the user's terminal 302 determines whether, among the plurality of operation schedules 101 included in the operation schedule 200 notified in the reservation information, the execution time period overlaps with the operation schedule 101 for which the reservation has been made. The operation schedule 101 is set to stop accepting reservations. This makes it possible to prohibit a reservation for an operation schedule 101 whose execution time slot overlaps with the operation schedule 101 in which the reservation has been made.

In S1004, the control unit 501 determines whether or not there is an operation schedule 101 for which the user is the only one who has made a reservation, among the plurality of operation schedules 101 included in the operation table 200 notified in the reservation information. For example, if there is one reservation included in the operation schedule 101 and the user information of the reservation matches the own user information stored in the storage unit 502, the control unit 501 determines YES. In this case, the flow advances to S1005.

In S1005, the control unit 501 determines whether the mobile object 102 that executes the reserved operation schedule 101 has not yet departed. Note that the control unit 501 may, for example, make an inquiry to the operation management device 301 and receive information on the operation status of the mobile object 102 indicating whether or not the mobile object 102 has started operation. In another embodiment, the operation management device 301 may transmit the reservation information including information on the operation state of the mobile object 102, and the reservation information received in S1002 includes information on the operation state of the mobile object 102. May be included. If the mobile body 102 has already departed (NO in S1005), the operation of the mobile body 102 cannot be canceled, so the flow advances to S1007. On the other hand, if the vehicle has not yet departed (YES in S1005), the execution of the operation schedule 101 can be canceled, and the flow advances to S1006.

In S1006, the control unit 501 displays and sets the reservation status of the operation schedule 101 for which only the user has made a reservation to be changeable. Note that the changeable display setting indicates that, for example, if you cancel your reservation for the currently reserved service schedule 101, you can change your reservation to another service schedule 101 that has an overlapping execution time period. .

On the other hand, for example, if there is another reservation holder in the service schedule 101 reserved in S1004 (NO in S1004), the flow advances to S1007. This means that, for example, if there is another person making a reservation for the service schedule 101 that has been reserved (S1004 is NO), the service schedule 101 will be executed for the other user even if the reservation is canceled. This is because it cannot be transferred. Note that in S1004, the determination may be NO even if there is no service schedule 101 that the user has reserved.

Then, in S1007, the control unit 501 displays the reservation reception screen 800 on the display screen of the display unit 504, and this operation flow ends.

FIG. 11 is another diagram illustrating the reservation reception screen 800 according to the embodiment. FIG. 11A shows an example of a reservation reception screen 800 that is displayed when the display is set to be changeable in S1006. As shown in FIG. 11(a), when making a reservation for the service schedule 101 with a departure time of 11:20, the service schedules 101 with departure times of 11:00 and 11:40 are grayed out and reservations are no longer accepted. ing. However, if the mobile unit 102 that executes the service schedule 101 with the departure time of 11:20 has not yet departed, the user can cancel the reservation and the service schedule 102 with the departure times of 11:00 and 11:40 Reservations are possible. Therefore, "reservation change possible" is displayed in the reservation status. Then, by referring to the reservation reception screen 800 in FIG. 11(a), the user can consider whether or not to change the reservation according to his/her convenience.

Further, FIG. 11(b) illustrates a reservation reception screen 800 that is displayed when the determination in S1004 is NO. In this case, the reservation status for the schedule 101 with departure times of 11:00 and 11:40 is displayed as canceled, and the user cancels the reservation made for schedule 101 with the departure time of 11:20. You can find out that you cannot transfer your reservation even if you do so. In addition, as shown in FIG. 11(b), the reservation reception screen 800 allows you to transfer reservations for the operation schedules 101 marked with "*" such as "*Because there is a reservation by another user." You may also display the reason why it is not possible. By displaying in this way, the user can know the reason why the reservation cannot be transferred. Note that other reasons may be displayed as the reason, such as "*Because the flight has already departed."

Then, when the user inputs a reservation instruction to reserve the operation schedule 101 based on the reservation reception screen 800, the control unit 501 of the user's terminal 302 may transmit the reservation instruction to the operation management device 301. .

According to the above operation flow of FIG. 10, if there is a reserved operation schedule in the reservation information received from the operation management device 301, the control unit 501 performs an operation that overlaps the reserved operation schedule 101 in the execution time period. The display unit 504 displays a reservation acceptance screen 800 in which reservation acceptance for the current operation schedule has been canceled. Therefore, users can be prevented from making a reservation for the service schedule 101 that will no longer be operated due to the reservation.

Further, according to the operation flow in FIG. 10, if the user is the only one who has made a reservation for the operation schedule 101 and the mobile object 102 has not yet departed, the user selects the operation schedule 101 for the time period of execution. It can be known that it is possible to move to another overlapping schedule 101.

Note that although the operation flow in FIG. 10 describes an example in which the reservation status is set on the user's terminal 302, the embodiment is not limited to this, and may be executed on the operation management device 301. Similarly, even if the operation management device 301 executes the control to stop accepting reservations for the operation schedule 101 whose execution time slots overlap due to reservations in the above-described embodiment, the user's terminal 302 can perform operation management. It may also be executed based on notification information notified from the device 301.

As described above, in the above embodiment, a plurality of operation schedules 101 having a greater number of overlaps than the number of moving bodies 102 managed by the operation management device 301 in route operation are virtually constructed and provided. Therefore, the user can select the operation schedule 101 from a wide range of operation schedules 101 options.

In addition, the execution of the operation schedule 101 is determined based on the reservation, and since the operation is suspended by stopping accepting reservations for the duplicate operation schedule 101, it is possible to provide an executable operation schedule 101 to the mobile object 102. .

In addition, by canceling the acceptance of reservations for duplicate operation schedules 101, passengers can be concentrated on the operation schedule 101 whose execution has been confirmed by reservation, and the profit margin of the provider who provides the operation service of the mobile object 102 can be improved.

In addition, in the above-mentioned embodiment, the control unit 401 of the traffic management device 301 operates as the reception unit 411 in the process of S702, for example. Further, in the processing of S705 and S904, the control unit 401 of the operation management device 301 operates as, for example, the reservation control unit 412. In the process of S707, the control unit 401 of the traffic management device 301 operates as the management unit 413, for example. Further, in the process of S1001, the control unit 501 of the user's terminal 302 operates as the requesting unit 511. In the process of S1007, the control unit 501 of the user's terminal 302 operates as, for example, the display control unit 512.

Although some embodiments have been illustrated above, the embodiments are not limited thereto. For example, the operational flow described above is an example, and if possible, the operational flow may be executed by changing the order of processing, may include additional processing, or may include some processing. May be omitted.

Further, in the above-described embodiment, an example is described in which the embodiment is applied to operation management of a mobile body 102 of public transportation such as a bus. However, embodiments are not limited thereto. For example, if the embodiment is a transportation system for scheduled routes with low demand and a desire to reduce the number of flights, the embodiment can be used not only on public roads but also on private land such as inside a factory, transportation of passengers between bases, and transportation system for logistics. It can also be applied to As an example, the embodiments may be applied to the operation management of ships and airplanes operated on predetermined routes. Further, the embodiment may be applied to transport cargo by the moving body 102 instead of passengers and to transport the cargo efficiently.

Further, in the above-described embodiment, the case where there is one mobile body 102 that can be used on the route is described as an example, but the embodiment is not limited to this. For example, the embodiment can be applied even when there are a plurality of moving objects 102 that can be used on a route. In this case, when the last one of the plurality of moving objects 102 is to depart due to the execution of the operation schedule 101, the control unit 401 of the operation management device 301 is configured to The process of the above-described embodiment may be executed, and reception of reservations for subsequent operation schedules 101 whose execution time slots overlap with the operation schedule 101 may be stopped. In addition, if there is an operation schedule 101 in the operation schedule 101 for which reservation acceptance is to be canceled, among the plurality of mobile objects 102, the mobile object 102 that departed by executing the other operation schedule 101 can return in time. For example, the control unit 401 does not have to stop accepting reservations for the operation schedule 101. Further, in order to execute such processing, the traffic management device 301 may store the number of mobile bodies 102 that can be used for operation on the route in the storage unit 402, and manage the mobile bodies 102.

Further, for example, if there are a plurality of moving objects 102 whose operation on a route is managed by the operation management device 301, the operation table 200 has a maximum number of overlaps in the operation schedule 101 than the number of the plurality of moving objects 102. It may be arranged so that there are many. For example, assume that the number of moving objects 102 whose operation is managed by the operation management device 301 on that route is two. In this case, by assembling the schedule 200 so that at most three or more schedules 101 overlap, it is possible to present the user with more schedules 101 than actually executable schedules 101. can.

For example, the control unit 401 of the operation management device 301 may set the number of reservations in the operation schedule 101 to a predetermined ratio to the number of reservations that can be accepted by the mobile object 102 (for example, the number of passengers who can ride). If the number exceeds the limit, information indicating the reservation status of the service schedule may be transmitted to the control terminal 303. Thereby, the person in charge of operation management using the control terminal 303 can arrange an additional mobile object 102 for operating a special flight or the like. In this way, for example, even in a situation where there are more people making reservations than in normal times, it is possible to supply mobile objects 102 in accordance with demand.

Additionally, the embodiments described above may be implemented in combination with various other techniques. For example, the embodiments described above may be implemented in combination with unmanned scheduled route bus service technology. In this case, by making a reservation system for boarding as described above, it is possible to detect and prevent return rides, which are difficult to detect on unmanned buses and the like, at the time of reservation. Note that turning around and boarding is, for example, the act of getting on the moving body 102, moving once to a boarding and alighting place in the opposite direction to the destination, and then turning back from there and riding to the destination.

Further, for example, by equipping the moving body 102 with a sensor and a communication device that detect whether a seatbelt is attached or detached, the control unit 401 of the operation management device 301 can detect whether a passenger who has made a reservation based on the information about seatbelt attachment or detachment is actually It becomes possible to obtain from the communication device information as to whether or not the user has boarded the moving body 102. If it is detected that the passenger who made the reservation did not board the train, the control unit 401 of the operation management device 301 may control the passenger to accept a reservation in place of the passenger who did not board the train on the subsequent route. good.

Further, although the above-described embodiment has been described with reference to the operation schedule 101 for one route, the embodiment is not limited to this. In another embodiment, the travel schedule 200 may be generated by mixing the travel schedules 101 of a plurality of different routes to generate the travel schedule 200 including the travel schedules 101 whose execution time slots overlap. For example, an operation schedule 101 for operating a first route, an operation schedule 101 for operating a second route, and an operation schedule 101 for operating a third route are mixed together to generate an operation schedule 200 and presented to the user. shall be. In this case as well, as described in the above embodiment, by stopping accepting reservations for the operation schedule 101 whose execution time zone overlaps with the operation schedule 101 for which the reservation has been made and suspending the operation, the operation schedule can be suspended. The operation schedule 101 included in 200 can be executed. This allows us to offer users a wide range of choices in terms of time and route. Moreover, it becomes possible to share the mobile body 102 on a plurality of routes, and it is possible to improve the utilization efficiency of the mobile body 102.

FIG. 12 shows the hardware of a computer 1200 for realizing an operation management device 301, a user terminal 302, a control terminal 303, and a communication terminal provided in a mobile object 102 and a terminal held by a driver according to the embodiment. FIG. 2 is a diagram illustrating a hardware configuration.

The hardware configuration of the computer 1200 in FIG. 12 includes, for example, a processor 1201, a memory 1202, a storage device 1203, a reading device 1204, a communication interface 1206, an input/output interface 1207, a display device 1211, and an input device 1212. Note that the processor 1201, memory 1202, storage device 1203, reading device 1204, communication interface 1206, and input/output interface 1207 are connected to each other via a bus 1208, for example.

The processor 1201 may be, for example, a single processor, a multiprocessor, or a multicore. The processor 1201 provides some or all of the functions of the above-described processing by using the memory 1202 to execute, for example, a program that describes the steps of the above-described operational flow. For example, the processor 1201 of the operation management device 301 operates as the control unit 401, reception unit 411, reservation control unit 412, and management unit 413 by reading and executing a program stored in the storage device 1203. Further, the processor 1201 of the user's terminal 302 operates as a control unit 501, a request unit 511, and a display control unit 512 by reading and executing a program stored in the storage device 1203.

Memory 1202 is, for example, a semiconductor memory and may include a RAM area and a ROM area. The storage device 1203 is, for example, a hard disk, a semiconductor memory such as a flash memory, or an external storage device. Note that RAM is an abbreviation for Random Access Memory. Further, ROM is an abbreviation for Read Only Memory.

Reading device 1204 accesses removable storage medium 1205 according to instructions from processor 1201 . The removable storage medium 1205 is, for example, a semiconductor device (USB memory, SD card, etc.), a medium in which information is input/output by magnetic action (magnetic disk, etc.), or a medium (CD, etc.) in which information is input/output by optical action. - ROM, DVD, etc.). Note that USB is an abbreviation for Universal Serial Bus. CD is an abbreviation for Compact Disc. DVD is an abbreviation for Digital Versatile Disk.

Note that the storage unit 402 and the storage unit 502 described above may include, for example, a memory 1202, a storage device 1203, and a removable storage medium 1205. For example, the storage device 1203 of the operation management device 301 stores information on reservations for the operation table 200, the timetable 600, and the operation schedule 101. Further, for example, the storage device 1203 of the user's terminal 302 stores reservation information for displaying the reservation reception screen 800.

The communication interface 1206 may transmit and receive data via the Internet or the mobile communication network 350 according to instructions from the processor 1201. Communication interface 1206 is an example of communication unit 403 and communication unit 503 described above.

Input/output interface 1207 may be, for example, an interface between an input device and an output device. In the example of FIG. 12, the input/output interface 1207 is connected to a display device 1211 such as a display and an input device 1212. The display device 1211 is an example of the display unit 504 described above. For example, the display device 1211 of the user's terminal 302 may display the reservation reception screen 800. The input device 1212 is a device that receives input from a user, such as a keyboard, mouse, touch panel, or microphone. Note that when a microphone is connected to the input/output interface 1207 as the input device 1212, the user may input voice input to the microphone, for example. Input device 1212 is an example of input unit 505 described above. Further, the input/output interface 1207 may be connected to other devices such as output devices such as speakers and printers.

Various programs for implementing the above-described embodiments are stored in the operation management device 301, the user's terminal 302, the control terminal 303, the communication terminal provided in the mobile object 102, and the driver in the following formats, for example. provided to the terminal.
(1) Installed in the storage device 1203 in advance.
(2) Provided by removable storage medium 1205;
(3) Provided by a server such as a program server.

Note that the hardware configuration of the computer 1200 described with reference to FIG. 12 is an example, and the embodiment is not limited thereto. For example, some of the components described above may be replaced or deleted, or new components may be added. Further, in another embodiment, for example, some or all of the functions of the above-described functional units may be implemented as hardware such as FPGA and SoC. Note that FPGA is an abbreviation for Field Programmable Gate Array. SoC is an abbreviation for System-on-a-chip.

Above, several embodiments are described. However, the embodiments are not limited to the embodiments described above, but should be understood to include various modifications and alternative forms of the embodiments described above. For example, it will be understood that the various embodiments can be embodied by changing the components without departing from the spirit and scope thereof. Furthermore, it will be understood that various embodiments can be implemented by appropriately combining the plurality of components disclosed in the embodiments described above. Furthermore, various embodiments can be implemented by deleting or replacing some components from all the components shown in the embodiments, or adding some components to the components shown in the embodiments. Those skilled in the art will understand that this can be done.

101 Operation schedule 102 Mobile object 200 Operation schedule 300 Operation management system 301 Operation management device 302 Terminal 303 Control terminal 310 Cloud 350 Mobile communication network 401 Control section 402 Storage section 403 Communication section 411 Reception section 412 Reservation control section 413 Management section 501 Control unit 502 Storage unit 503 Communication unit 504 Display unit 505 Input unit 511 Request unit 512 Display control unit 600 Timetable 800 Reservation reception screen 801 List 1200 Computer 1201 Processor 1202 Memory 1203 Storage device 1204 Reading device 1205 Removable storage medium 1206 Communication interface 1207 Input/output interface 1208 Bus 1211 Display device 1212 Input device

Claims (6)

A reception desk that accepts reservations for a plurality of operation schedules that define schedules for operating mobile objects on fixed routes, each operation schedule having overlap with at least one other operation schedule in its execution time period. Department and
a reservation control unit that, when a reservation is received by the reception unit, stops accepting reservations for an operation schedule whose execution time zone overlaps with the reserved operation schedule;
a management unit that outputs an instruction for the mobile object to operate according to the reserved operation schedule;
including;
The maximum number of overlaps in the time period of execution of the plurality of operation schedules is greater than the number of mobile objects managed by the management unit in operation of the fixed route,
When a user cancels a reservation for the reserved operation schedule, the reservation control unit is configured to cancel the reservation for the canceled operation schedule and the execution time if there is no other user who has made a reservation for the canceled operation schedule. An operation management device characterized by restarting acceptance of reservations for operation schedules with overlapping bands . The time period for executing the plurality of operation schedules includes, in addition to the operation period for operation of the regular route, an inspection period for pre-operation inspection, and a period for charging the energy used by the mobile object for operation. 2. The traffic management device according to claim 1, wherein the traffic management device includes at least one of the following filling periods. If the number of reservations received by the reception unit for one operation schedule exceeds a predetermined percentage of the number of reservations that can be accepted by the mobile object, the management unit may accept reservations for one operation schedule. The traffic management device according to claim 1 or 2, wherein the traffic management device outputs information indicating the status of the traffic control device. Accepting reservations for the plurality of operation schedules, each of which defines a schedule for operating a mobile object on a fixed route, each operation schedule having an overlap with at least one other operation schedule in its execution time period;
If we receive a reservation, we will stop accepting reservations for service schedules that overlap with the reserved service schedule, and
outputting an instruction for the mobile object to operate according to the reserved operation schedule;
including that
The maximum number of overlaps in the execution time period of the plurality of operation schedules is greater than the number of the mobile objects whose operation is managed on the regular route,
If a user cancels a reservation for the reserved service schedule, and there are no other users who have made reservations for the canceled service schedule, a service schedule whose execution time period overlaps with the canceled service schedule. 1. An operation management method executed by a computer, characterized by restarting acceptance of reservations for . A plurality of operation schedules defining a schedule for operating a mobile object on a fixed route, each operation schedule having overlap with at least one other operation schedule in the execution time period, and the reservation status for the plurality of operation schedules. a request unit that requests provision of reservation information indicated;
If there is a reserved operation schedule in the provided reservation information, the display device displays a reservation reception screen in which reservations are no longer accepted for operation schedules whose execution time slots overlap with the reserved operation schedule. a display control unit for displaying;
including;
The maximum number of overlaps in the execution time period of the plurality of operation schedules is greater than the number of the mobile objects whose operation is managed on the regular route,
If a user cancels a reservation for the reserved service schedule, and if there are no other users who have made a reservation for the canceled service schedule, the service whose execution time period overlaps with the canceled service schedule will be cancelled. A terminal , characterized in that the display device displays the reservation acceptance screen for restarting acceptance of reservations for the schedule . If the reservation person for the reserved operation schedule in the reservation information is the only user who has requested provision of the reservation information, the display control unit may display the reserved operation schedule and the execution time period. 6. The terminal according to claim 5 , wherein the display device displays the reservation acceptance screen indicating that a reservation can be changed to an overlapping schedule.

Images