Vehicle dispatch management system, vehicle dispatch reservation management method, and computer program

The demand-based vehicle allocation management system addresses the challenge of flexible on-demand transportation by using reservation states and condition identifiers to allow free searches and prevent duplicates, improving service quality and user flexibility.

JP2024166248AActive Publication Date: 2024-11-28KDDI CORP
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2024153129
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-09-05
Publication Date
2024-11-28
Estimated Expiration
2041-07-29

AI Technical Summary

Technical Problem

Existing on-demand transportation systems fail to accommodate users who want to freely search for rides without reservations and do not allow for independent management of seat reservations due to the flexibility in travel routes, boarding and alighting points, and times, leading to difficulties in preventing duplicate reservations and free vehicle allocation searches.

Method used

A demand-based vehicle allocation management system with reservation states including 'unconfirmed', 'tentatively confirmed', and 'confirmed' that uses reservation condition identifiers to manage transitions between these states, ensuring no duplicate reservations by restricting or allowing vehicle allocation searches based on specific conditions.

Benefits of technology

The system enables free vehicle allocation searches while preventing duplicate reservations, allowing users to freely generate 'unconfirmed' reservations and safely transition to 'confirmed' without duplicates, enhancing service quality and flexibility in on-demand transportation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024166248000001_ABST
    Figure 2024166248000001_ABST
Patent Text Reader

Abstract

To implement reservation status management so that a user can freely perform vehicle dispatch search while preventing double booking.SOLUTION: A vehicle dispatch management system includes a reservation status management unit which shifts a reservation status of a demand in accordance with a user request. The reservation status management unit is configured to shift a reservation status of a target demand from "unfixed" to "fixed" when there is no other "tentatively fixed" demand in the same time zone for the same vehicle as the target demand and when reservation condition identifiers currently assigned to the vehicle and the time zone of the target demand coincide with a reservation condition identifier of the target demand. The reservation status management unit defines reservation condition identifiers currently assigned to the vehicle and the time zone of the "unfixed" demand, as a reservation condition identifier of the demand, and modifies the reservation condition identifiers currently assigned to the vehicle and the time zone of the demand to new reservation condition identifiers when the "tentatively fixed" demand shifts to "fixed" status.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a vehicle dispatch management system, a vehicle dispatch reservation management method, and a computer program. [Background technology]

[0002] On-demand transportation is a type of public transportation service that operates according to the demands of multiple users, and is based on advance reservations made by users. Regarding on-demand transportation, a reservation management technology is known, for example, as described in Patent Document 1. In this technology, in order to encourage multiple users to board the same vehicle service, a ride reservation is suggested to users who are likely to ride together based on past riding history. The interface of the user terminal for making reservations is disclosed as one in which reservation information such as the desired date and time, boarding location, and disembarking location is input and transmitted, and if the seat reservation is successful, the reservation is confirmed and the reservation result is displayed.

[0003] Furthermore, Non-Patent Document 1 describes a vehicle dispatch technology based on trip units that takes into account departure and return from bases in order to realize an operation in which out-of-service vehicles are kept waiting at bases, which is particularly necessary when using autonomous vehicles in on-demand transportation. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6432205 [Non-patent literature]

[0005] [Non-Patent Document 1] Aoi Koizuka, Tomohiko Ogishi, "A study on demand-based vehicle dispatching method in anticipation of the use of autonomous vehicles," Institute of Electronics, Information and Communication Engineers, 2020 Society Conference Proceedings, B-15-11, September 1, 2020 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the above-mentioned conventional technology cannot meet the diverse needs of users who are interested in on-demand transportation and want to freely search for vehicle dispatches, and users who want to check the scheduled departure time from the departure point and the scheduled arrival time at the destination before confirming the reservation. In order to meet the needs of such diverse users, it is possible to have a reservation status of "unconfirmed" that does not restrict other vehicle dispatch searches and the confirmation of reservations, and a "provisionally confirmed" status that does not restrict other vehicle dispatch searches but restricts the confirmation of other reservations, in addition to the "confirmed" reservation. On the other hand, in reservation status management, it is required to transition each reservation status while checking the consistency of the reservation. Here, a major feature of on-demand transportation is that it allows a large degree of freedom in the travel route, boarding and alighting points, boarding and alighting times, etc., so it is difficult to manage reservations independently for each predetermined operating section or seat, as in the case of reservations for trains such as the Shinkansen.

[0007] The present invention has been made in consideration of the above circumstances, and its purpose is to realize reservation status management that combines free vehicle dispatch searches with measures to prevent overlapping reservations in a demand-based vehicle dispatch management system that operates vehicles according to reservations. [Means for solving the problem]

[0008] In one aspect of the present invention, a demand-based vehicle dispatch management system that operates vehicles in response to reservations provides a "first state" and a "second state" as reservation states of a demand, the "first state" of the demand reservation state is a state in which no restrictions are imposed on the transition of the reservation state of other demands than the demand in question, and the "second state" of the demand reservation state is a state in which no restrictions are imposed on vehicle dispatch searches of other demands than the demand in question, but restrictions are imposed on the transition of the reservation state of other demands than the demand in question from the "first state" to the "second state", and the reservation states of the demands are managed and a user is provided. a reservation state management unit that transitions the reservation state of a demand in response to a user request, and a transition condition that permits the transition of the reservation state of a target demand from a "first state" to a "second state" includes the absence of another demand for the same vehicle and in the same time period as the target demand whose reservation state is the "second state," and the reservation state management unit determines whether or not to transition the reservation state of the target demand from the "first state" to the "second state" based on the transition condition, and changes the reservation state of the target demand to the "second state" according to the result of the determination. In one aspect of the present invention, in the above-mentioned vehicle dispatch management system, the reservation state of a demand, "third state", is a state in which a vehicle dispatch search for demands other than the demand is restricted, and the system further includes a reservation condition identifier information storage unit that provides a reservation condition identifier for each vehicle and time period and stores the latest reservation condition identifier for each vehicle and time period, and a demand information storage unit that stores demand-related information indicating the demand of each user and a reservation condition identifier for each demand, and a transition condition for permitting the transition of the reservation state of a target demand from "first state" to "second state" is that the same vehicle and and there is no other demand in the same time period whose reservation status is "second state", and the reservation condition identifier in the reservation condition identifier information storage unit currently assigned to the vehicle and time period of the target demand matches the reservation condition identifier of the target demand in the demand information storage unit, and when a demand in the reservation status "second state" transitions to a reservation status "third state", the reservation status management unit changes the reservation condition identifier in the reservation condition identifier information storage unit currently assigned to the vehicle and time period of the demand to a new reservation condition identifier. In one aspect of the present invention, in the above vehicle dispatch management system, a "third state" of a demand reservation state is a state in which a vehicle dispatch search for demands other than the demand in question is restricted, and a "fourth state" of a demand reservation state is a state in which a request for canceling a reservation of the demand in question is accepted, the system further includes a reservation condition identifier information storage unit that provides a reservation condition identifier assigned to each vehicle and time period and stores the latest reservation condition identifier for each vehicle and time period, and a demand information storage unit that stores demand-related information indicating each user's demand and a reservation condition identifier for each demand, and allows the reservation state of a target demand to transition from the "first state" to the "second state." The transition conditions that allow this transition are that there is no other demand for the same vehicle and time period as the target demand and whose reservation state is "second state", and that the reservation condition identifier in the reservation condition identifier information storage unit that is currently assigned to the vehicle and time period of the target demand matches the reservation condition identifier of the target demand in the demand information storage unit, and when a demand in the reservation state "third state" transitions to the reservation state "fourth state", the reservation state management unit changes the reservation condition identifier in the reservation condition identifier information storage unit that is currently assigned to the vehicle and time period of the demand to a new reservation condition identifier. One aspect of the present invention is a vehicle dispatch management system, in which the "first state" is a state in which no restrictions are imposed on the transition of vehicle dispatch searches and reservation states of demands other than the demand in question. One aspect of the present invention is a vehicle dispatch management system in which, in the above-mentioned vehicle dispatch management system, the reservation status management unit measures the elapsed time since a demand in the reservation status "first status" was generated, and includes as a transition condition for each reservation status of the demand that the elapsed time is equal to or less than a predetermined reservation confirmation grace time. One aspect of the present invention is a vehicle dispatch management system in which, in the above-mentioned vehicle dispatch management system, the reservation status management unit notifies a terminal device of a user of a demand in the reservation status "first state" that there is a conflict between multiple users for vehicle dispatch reservations for the demand in the reservation status "first state."

[0009] One aspect of the present invention is a vehicle dispatch reservation management method executed by a demand-based vehicle dispatch management system that operates vehicles in response to reservations, in which a "first state" and a "second state" are provided as reservation states of a demand, the "first state" of the demand reservation state is a state in which no restrictions are imposed on the transition of the reservation state of other demands than the demand in question, and the "second state" of the demand reservation state is a state in which no restrictions are imposed on vehicle dispatch searches of other demands than the demand in question, but restrictions are imposed on the transition of the reservation state of other demands than the demand in question from the "first state" to the "second state", and the reservation states of the demands are managed. The vehicle dispatch reservation management method includes a reservation state management step of transitioning the reservation state of a demand in response to a user request, and a transition condition for permitting the transition of the reservation state of a target demand from a "first state" to a "second state" includes the absence of another demand for the same vehicle and in the same time period as the target demand, whose reservation state is the "second state", and the reservation state management step determines whether or not to transition the reservation state of the target demand from the "first state" to the "second state" based on the transition condition, and changes the reservation state of the target demand to the "second state" in accordance with the result of the determination.

[0010] In one aspect of the present invention, a computer of a demand-based vehicle dispatch management system that operates vehicles in response to reservations is provided with a "first state" and a "second state" as reservation states of a demand, the "first state" of the demand reservation state being a state that does not impose restrictions on transitions of the reservation states of demands other than the demand in question, and the "second state" of the demand reservation state being a state that does not impose restrictions on vehicle dispatch searches of demands other than the demand in question, but imposes restrictions on transitions of the reservation states of demands other than the demand in question from the "first state" to the "second state", and the computer manages the reservation states of the demands and changes the reservation states of the demands in response to user requests. A computer program for executing a reservation state management step of transitioning a reservation state, wherein a transition condition for permitting the transition of the reservation state of a target demand from a "first state" to a "second state" includes the absence of another demand for the same vehicle and in the same time period as the target demand whose reservation state is the "second state", and the reservation state management step determines whether or not to transition the reservation state of the target demand from the "first state" to the "second state" based on the transition condition, and changes the reservation state of the target demand to the "second state" according to the result of the determination. Effect of the Invention

[0011] According to the present invention, in a demand-based vehicle dispatch management system that operates vehicles according to reservations, it is possible to achieve reservation status management that combines free vehicle dispatch searches with measures to prevent overlapping reservations. [Brief description of the drawings]

[0012] [Figure 1] 1 is a block diagram showing an example of the configuration of a vehicle dispatch management system according to an embodiment; [Diagram 2] FIG. 2 is a diagram for explaining an example of a trip according to an embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of an operation of the vehicle dispatch management system according to an embodiment. [Figure 4] FIG. 11 is an explanatory diagram of a reservation state and a state transition of a demand according to an embodiment. [Diagram 5] FIG. 11 is an explanatory diagram of an example of a transition of a reservation state according to an embodiment. [Figure 6] FIG. 11 is an explanatory diagram of an example of a transition of a reservation state according to an embodiment. [Figure 7] FIG. 4 is an explanatory diagram for explaining a correspondence relationship between a trip and a reservation condition identifier according to an embodiment. [Figure 8] FIG. 4 is a diagram illustrating an example of the configuration of a display screen of a terminal device according to an embodiment. [Figure 9] FIG. 4 is a diagram illustrating an example of the configuration of a display screen of a terminal device according to an embodiment. [Figure 10] FIG. 4 is a diagram illustrating an example of the configuration of a display screen of a terminal device according to an embodiment. [Figure 11] FIG. 4 is a diagram illustrating an example of the configuration of a display screen of a terminal device according to an embodiment. [Figure 12] FIG. 4 is a diagram illustrating an example of the configuration of a display screen of a terminal device according to an embodiment. [Figure 13] FIG. 4 is a diagram illustrating an example of the configuration of a display screen of a terminal device according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. 1 is a block diagram showing an example of the configuration of a vehicle dispatch management system according to an embodiment. A vehicle dispatch management system 1 according to this embodiment is a demand-based traffic management system. In a demand-based traffic management system, vehicles are operated according to reservations made by users.

[0014] In this embodiment, vehicle dispatch management is performed on a trip basis. A trip refers to a series of vehicle operations from a base at a base departure time, through one or more demand stopovers (starting points (boarding points) or destinations (dropping points)), and back to the base at a base return time.

[0015] The vehicle dispatch management system 1 includes a terminal device 20-1, a terminal device 20-2, a terminal device 20-3, an in-vehicle device 30, and a management server 100. The terminal device 20-1, the terminal device 20-2, the terminal device 20-3, the in-vehicle device 30, and the management server 100 are connected via a network NW. The network NW is a wireless or wired communication network. The network NW includes the Internet and an intranet. Specifically, the network NW is an information communication network configured by a WAN (Wide Area Network), a LAN (Local Area Network), and the like. The WAN includes, for example, a mobile phone network, a PHS (Personal Handy-phone System) network, a PSTN (Public Switched Telephone Network), a dedicated communication line network, and a VPN (Virtual Private Network).

[0016] The terminal device 20-1 is used by a user. The user operates the terminal device 20-1 to reserve a vehicle. When reserving a vehicle, the user specifies information specifying the boarding location and information specifying the disembarking location. Based on the user's operation, the terminal device 20-1 creates a ride reservation request addressed to the management server 100, including ride reservation information (demand). The ride reservation information includes information specifying the boarding location and information specifying the disembarking location. The terminal device 20-1 transmits the created ride reservation request to the management server 100.

[0017] The management server 100 receives the boarding reservation request transmitted by the terminal device 20-1. The management server 100 stores location information of the base where the vehicle is to wait. The management server 100 acquires the boarding reservation information included in the received boarding reservation request, and searches for a route from the first base to the first base or the second base via the boarding location and the disembarking location based on the acquired boarding reservation information and the stored location information of the base.

[0018] Based on the route search result, the management server 100 creates a new vehicle operation schedule that departs from the first base at a first time, passes through the boarding location and the disembarking location, and returns to the first base or the second base at a second time. Based on the created new operation schedule and each of the existing operation schedules of one or more vehicles that are already in operation, the management server 100 determines whether operation according to the new operation schedule is possible. The management server 100 determines whether a trip can be formed with a new demand alone by determining that the time period of the trip with the new demand alone does not overlap with the time period of an existing trip.

[0019] When the management server 100 determines that operation according to the new operation schedule is possible, it creates a boarding reservation response addressed to the terminal device 20-1 and including the new operation schedule. The management server 100 transmits the created boarding reservation response to the terminal device 20-1. The terminal device 20-1 receives the boarding reservation response transmitted by the management server 100 and displays the new operation schedule contained in the received boarding reservation response.

[0020] In addition, the management server 100 creates a vehicle dispatch request addressed to the vehicle-mounted device 30 and including the new operation schedule. The management server 100 transmits the created vehicle dispatch request to the vehicle-mounted device 30. The vehicle-mounted device 30 receives the vehicle dispatch request transmitted by the management server 100. If the vehicle VE in which the vehicle-mounted device 30 is mounted is a manually driven vehicle, the vehicle-mounted device 30 displays the new operation schedule included in the received vehicle dispatch request. If the vehicle VE in which the vehicle-mounted device 30 is mounted is an autonomous vehicle, the vehicle-mounted device 30 outputs the new operation schedule included in the received vehicle dispatch request to the autonomous driving system of the vehicle VE.

[0021] The terminal device 20-1, the terminal device 20-2, the terminal device 20-3, the vehicle-mounted device 30, and the management server 100 included in the vehicle dispatch management system 1 will be described below in order.

[0022] (Terminal Device) The terminal device 20-1, the terminal device 20-2, and the terminal device 20-3 are realized by, for example, a personal computer, a mobile phone, a tablet, a smartphone, a PHS (Personal Handy-phone System), a PDA (Personal Digital Assistant), or the like.

[0023] The terminal device 20-1 is a mobile device carried by a user. The user uses the terminal device 20-1 to make a reservation for a ride. A ride reservation application is installed in the terminal device 20-1. The ride reservation application causes the terminal device 20-1 to create ride reservation information based on the user's operation.

[0024] Ride reservations include instantaneous reservations and advance reservations. Instantaneous reservations are made when a person wishes to board a vehicle immediately, and information specifying the boarding location and information specifying the disembarking location are specified. An example of information specifying the boarding location and information specifying the disembarking location is a place name or some other information indicating a location. When an instantaneous reservation is made, the ride reservation information includes information specifying the boarding location and information specifying the disembarking location.

[0025] On the other hand, an advance reservation is when a boarding time or alighting time is desired, and information specifying the boarding location, information specifying the alighting location, and information indicating the desired departure time or information indicating the desired alighting time are specified. When an advance reservation is made, the boarding reservation information includes information specifying the boarding location, information specifying the alighting location, and information indicating the desired departure time or information indicating the desired alighting time.

[0026] The ride reservation app causes the terminal device 20-1 to create a ride reservation request including ride reservation information and addressed to the management server 100. The ride reservation app causes the terminal device 20-1 to transmit the ride reservation request created by the terminal device 20-1 to the management server 100. The ride reservation app causes the terminal device 20-1 to receive the ride reservation response transmitted by the management server 100, and to process the ride reservation information included in the received ride reservation response.

[0027] The terminal device 20-2 is, for example, a device used by a person sitting in the driver's seat of a vehicle. For example, the terminal device 20-2 may be fixed to the driver's seat like a car navigation system. An example of a person sitting in the driver's seat of a vehicle is a driver. However, if the vehicle is an autonomous vehicle, the conductor may use the terminal device 20-2. An operation application is installed in the terminal device 20-2. The operation application causes the terminal device 20-2 to receive information about the operation of the vehicle, such as information that identifies the boarding location of the user, information that identifies the disembarking location, and route information, transmitted by the management server 100. The operation application causes the terminal device 20-2 to display the boarding location, disembarking location, and route information on a map displayed on the display unit, based on the received information about the operation of the vehicle.

[0028] The operation application causes the terminal device 20-2 to perform processing related to vehicle operation. When a point corresponding to a boarding location or disembarking location on a map displayed on the display unit of the terminal device 20-2 is pressed, the operation application causes the terminal device 20-2 to create operation information addressed to the management server 100, the operation information including information indicating the time of pressing and information indicating the boarding location or disembarking location corresponding to the pressed point. The operation application causes the terminal device 20-2 to transmit the created operation information to the management server 100.

[0029] The terminal device 20-3 is a device used by a person who gets in a vehicle. For example, the terminal device 20-3 may be fixed to the driver's seat like a car navigation system. The terminal device 20-3 may be used by a user who does not usually carry a smartphone or a tablet. An operation status notification management app is installed in the terminal device 20-3. The operation status notification app causes the terminal device 20-3 to receive the boarding information, disembarking information, and route information of the user transmitted by the management server 100. The operation status notification app causes the terminal device 20-3 to display boarding and disembarking locations and route information on a map displayed on the display unit based on the received boarding information, disembarking information, and route information of the user. However, depending on the environment in which the terminal device 20-3 is used, the contents displayed on the terminal device 20-3 may be restricted in consideration of privacy.

[0030] (onboard device) The on-board device 30 is mounted on the vehicle VE. An on-board application is installed on the on-board device 30. The on-board application is software that runs in the vehicle VE. The on-board application causes the on-board device 30 to transmit position information of the vehicle VE and CAN (Controller Area Network) data to the management server 100. If the vehicle VE in which the on-board device 30 is mounted is an autonomous vehicle, the on-board device 30 cooperates with the autonomous driving system of the vehicle VE. In this case, the on-board application causes the on-board device 30 to receive route information transmitted by the management server 100 and outputs the received route information to the autonomous driving system.

[0031] (Management Server) The management server 100 includes a communication unit 102 , a reception unit 104 , a vehicle dispatch processing unit 106 , a route search unit 108 , a reservation status management unit 109 , and a storage unit 110 .

[0032] Each function of the management server 100 is realized by the management server 100 including computer hardware such as a CPU (Central Processing Unit) and a memory, and the CPU executes a computer program stored in the memory. The management server 100 may be configured using a general-purpose computer device, or may be configured as a dedicated hardware device. For example, the management server 100 may be realized by a device such as a personal computer, a server, or an industrial computer. For example, the management server 100 may be configured using a server computer connected to a communication network such as the Internet. Each function of the management server 100 may be realized by cloud computing. The management server 100 may be realized by a single computer, or may be realized by distributing the functions of the management server 100 to multiple computers. The management server 100 may be configured to open a website using, for example, a WWW system.

[0033] The communication unit 102 is realized by a communication module. The communication unit 102 communicates with other devices such as the terminal device 20-1, the terminal device 20-2, the terminal device 20-3, and the vehicle-mounted device 30 via the network NW. The communication unit 102 receives a ride reservation request transmitted by the terminal device 20-1. The communication unit 102 also transmits a ride reservation response output by the vehicle allocation processing unit 106 to the terminal device 20-1. The communication unit 102 transmits the vehicle allocation request output by the vehicle allocation processing unit 106 to the vehicle-mounted device 30.

[0034] The storage unit 110 is realized by, for example, a RAM, a ROM, a HDD, a flash memory, or a hybrid storage device in which a plurality of these are combined. The storage unit 110 stores a program (vehicle dispatch management application) executed by the management server 100. The storage unit 110 also stores identification information (hereinafter referred to as "base ID") of a base where a vehicle is to be kept waiting and location information of the base in association with each other. The storage unit 110 also stores various data required for the management server 100 to dispatch a vehicle. For example, the storage unit 110 stores demand information 110a, vehicle information 110b, user information 110c, and reservation condition identifier information 110d as data required for dispatching a vehicle.

[0035] The demand information 110a includes one or more pieces of demand-related information that associates a user's identification information (hereinafter referred to as "user ID"), ride reservation information included in a ride reservation request transmitted by the user's terminal device 20-1, and a ride reservation processing status. The demand information 110a also includes a reservation condition identifier for each demand. Vehicle information 110b includes one or more pieces of vehicle-related information that associate vehicle identification information (hereinafter referred to as "vehicle ID"), information indicating the vehicle's operating schedule, information indicating the vehicle's capacity, information indicating the waiting location base, such as a base ID, rest time information, conductor information, current location information, and status information. The user information 110c includes one or more pieces of user-related information that associates information indicating the user's name, information indicating the user's sex, information indicating the user's age, and information indicating the user's condition.

[0036] The reservation condition identifier information 110d has the latest reservation condition identifier. The reservation condition identifier is an identifier that identifies a vehicle and a time period, and is assigned to each vehicle and time period. Therefore, the reservation condition identifier is different for each vehicle. Furthermore, the reservation condition identifier is different for each time period, even for the same vehicle. Furthermore, the reservation condition identifier is changed according to specified update conditions. As a result, the reservation condition identifier information 110d has the latest reservation condition identifier for each vehicle and time period. The latest reservation condition identifier for a certain vehicle and time period is the reservation condition identifier currently assigned to that vehicle and time period.

[0037] The reception unit 104 receives the ride reservation request received by the communication unit 102, and acquires the ride reservation information included in the received ride reservation request. The reservation state management unit 109 acquires the boarding reservation information acquired by the reception unit 104. The reservation state management unit 109 executes a reservation state management process for the demand, based on the boarding reservation information acquired by the reception unit 104.

[0038] The vehicle allocation processing unit 106 receives a vehicle allocation calculation request together with the boarding reservation information from the reservation state management unit 109. The vehicle allocation processing unit 106 updates the demand information 110a stored in the storage unit 110 based on the acquired boarding reservation information.

[0039] The vehicle dispatch processing unit 106 acquires the vehicle ID, information indicating the vehicle operation schedule, information indicating the vehicle's capacity, information indicating the base of the waiting place, rest time information, current location information, and status information included in one or more pieces of vehicle-related information from the vehicle information 110b stored in the storage unit 110. The vehicle dispatch processing unit 106 determines whether or not a vehicle can be dispatched that satisfies the boarding reservation information based on the acquired vehicle ID, information indicating the vehicle operation schedule, information indicating the vehicle's capacity, information indicating the base of the waiting place, rest time information, current location information, status information, and position information of the base where the vehicle is to wait.

[0040] The vehicle allocation processing unit 106 performs processing on the premise that a vehicle that has no demand during operation will wait at a designated base. The vehicle allocation processing unit 106 performs operation management on a trip basis. Here, a trip will be described.

[0041] FIG. 2 is a diagram for explaining an example of a trip. The boarding location (starting point) included in the boarding reservation information (demand) is O (Origin), and the disembarking location (destination) is D (Destination). The arrival time of the vehicle at the boarding location (starting point) is t O Let the arrival time of the vehicle at the destination be t D The time of departure from the base is t BS The time of arrival at the base is t BG In this way, the vehicle BS Departing from the base at time t BG The entire journey from the departure point to the return to the base is called a trip.

[0042] In the example of Fig. 2, trip 1 and trip 2 are shown. As shown in Fig. 2, a plurality of trips may be formed during the operation hours of a day. Trip 1 is a trip in which a vehicle travels from a time t BS1 At time t O1 Arrives at boarding location O1 at time t D1 Arrives at drop-off location D1 at time t BG1 Trip 2 is a series of trips from the vehicle at time t BG1 A time t that is later than BS2 Depart from base BG2 at time t O2 Arrives at boarding point O2 at time t O3 Arrives at boarding location O3 at time t D2 At time t D3 At time t BG2 This is the entire operation from 0:00 to 0:00 and back to base BG2.

[0043] The dispatch processing unit 106 acquires information for specifying the boarding location and information for specifying the disembarking location included in the boarding reservation information. The dispatch processing unit 106 outputs the acquired information for specifying the boarding location and information for specifying the disembarking location to the route search unit 108.

[0044] The route search unit 108 acquires the information specifying the boarding location and the information specifying the disembarking location output by the vehicle dispatch processing unit 106. The route search unit 108 acquires information that associates the base ID of the base where the vehicle is to be waited for, stored in the storage unit 110, with the position information of the base. Based on the acquired information specifying the boarding location and the information specifying the disembarking location, the base ID where the vehicle is to be waited for, and the position information of the base, the route search unit 108 selects the base ID of the base where the vehicle to be dispatched to the boarding location is waiting, and the base ID of the base where the vehicle is to head to after the disembarking location. The base where the vehicle to be dispatched to the boarding location is waiting and the base where the vehicle is to head to after the disembarking location may be the same or different. Below, the case where the first base is selected as the base where the vehicle to be dispatched to the boarding location is waiting, and the second base is selected as the base where the vehicle is to head to after the disembarking location will be described. Here, the first base and the second base are stored in the storage unit 110.

[0045] The route search unit 108 searches for a route from the first base via the boarding location and disembarking location to the second base based on the acquired information identifying the boarding location and information identifying the disembarking location, the base ID of the first base where the vehicle is waiting, and information associating the location information of the first base, and derives the time required to travel from the first base via the boarding location and disembarking location to the second base via the route.

[0046] For example, the route search unit 108 searches for a route that travels from the first base to the second base via the boarding location and the disembarking location in the shortest distance, and derives the time required to travel from the first base to the second base via the boarding location and the disembarking location on the route. For example, the route search unit 108 derives the time required to travel from the first base to the boarding location, the time required to travel from the boarding location to the disembarking location, and the time required to travel from the disembarking location to the second base. The route search unit 108 outputs information indicating the result of the route search and information indicating the result of the derived time to the vehicle dispatch processing unit 106.

[0047] The vehicle allocation processing unit 106 acquires information indicating the result of the route search and information indicating the result of the required time output by the route search unit 108. The vehicle allocation processing unit 106 determines whether or not vehicle allocation is possible based on the information indicating the result of the route search and the information indicating the result of the required time.

[0048] The vehicle allocation processing unit 106 determines whether a trip can be formed by the new demand alone. Specifically, when a trip formed by the new demand alone is assumed, the vehicle allocation processing unit 106 determines whether the trip formed by the new demand alone overlaps with an existing trip in a chronological order. When the vehicle allocation processing unit 106 determines that there is no overlap with an existing trip in a chronological order, it determines that a trip can be formed by the new demand alone and that a vehicle can be allocated. The process in which the vehicle allocation processor 106 determines whether there is any overlap with an existing trip in time series will be described below.

[0049] 3 is a diagram showing an example of the operation of the vehicle dispatch management system according to the present embodiment. FIG. 3 shows an example of a trip. In the trip shown in FIG. 3, a vehicle O1min From time t O1max arrives at boarding location O1 during time t O1max Assume that the vehicle must depart from boarding location O1 at time t D1min From time t D1max Suppose that the vehicle must arrive at drop-off location D1 between TW is the time between the departure time from the boarding location and the time a certain time before the departure time. W is defined as the waiting time at the boarding location (starting point) of the demand. T R is the time between the guaranteed arrival time at the drop-off location (even if there is an additional delay, the vehicle will arrive at this time at the latest) and a certain time before that. R is the time required to absorb delays due to trips that are expected to be added in the future, and is defined as the slack time until arrival. Equations (1) and (2) hold. t O1max -t O1min =T W (1) t D1max -t D1min =T R (2) From equation (1), condition t O1 The constraints on t O1min ≦t O1 ≦t O1max From equation (2), t D1 The constraints on t D1min ≦t D1 ≦t D1max It becomes.

[0050] Whether or not a trip can be formed based on a single new demand will be described separately for the case where an immediate reservation is made and the case where an advance reservation is made.

[0051] (If an instant reservation is made) When an immediate reservation is made, the vehicle is considered to be currently waiting at the first base. The vehicle dispatch processing unit 106 determines the earliest possible time that the vehicle waiting at the first base can depart from the base as t BS Then, the remaining time t O1 , t D1 , t BG is the travel time between each point output by the route search unit 108 at time t BS At this time, the dispatch processing unit 106 forms a trip by sequentially adding O1max At this point in time t O1 At time t D1min At this point in time tD1 Let us assume that.

[0052] (Advance reservation) Whether or not a trip can be formed with a single new demand when an advance reservation is made will be described separately for the case where a desired departure time is specified and the case where a desired arrival time is specified. When a desired departure time is specified, the dispatch processing unit 106 sets the desired departure time as t O1 At time t O1 The departure time from the first base to arrive at the boarding point O1 at t BS The remaining time t D1 , t BG Similarly to the case of instantaneous reservation, the travel time between each point output by the route search unit 108 is calculated as the time t BS A trip is formed by adding these in order. When the desired arrival time is specified, the dispatch processing unit 106 sets the desired arrival time as t D1max and the arrival time is t D1max Determined by t D1min Let the time be t D1 The remaining time t BS , t O1 , t BG Similarly to the case of instantaneous reservation, the travel time between each point output by the route search unit 108 is calculated as the time t D1 A trip is formed by subtracting from the

[0053] From the above, we can see that trip formation for a single new demand can be expressed by the time series relationship in Figure 3, regardless of whether immediate booking or advance booking is specified.

[0054] The vehicle allocation processing unit 106 determines whether a trip with only the new demand is established. Specifically, the vehicle allocation processing unit 106 determines whether the time slot from tBS to tBG of the trip with only the new demand overlaps with the time slot of an existing trip. The vehicle allocation processing unit 106 determines that a vehicle can be allocated if a trip can be formed with a new demand alone because the time period from tBS to tBG of the trip with the new demand alone does not overlap with the time period of an existing trip. If the vehicle allocation processing unit 106 determines that a vehicle can be allocated, it creates a ride reservation response addressed to the terminal device 20-1, the ride reservation response including information indicating that a vehicle can be allocated, information specifying the trip, and information indicating the reservation status of the demand. The reservation status of the demand will be described later. The vehicle allocation processing unit 106 outputs the created ride reservation response to the communication unit 102. When it is determined that a vehicle can be dispatched and the reservation status of the corresponding demand is “confirmed”, the vehicle dispatch processing unit 106 creates a vehicle dispatch request including information for identifying the trip and addressed to the in-vehicle device 30. The vehicle dispatch processing unit 106 outputs the created vehicle dispatch request to the communication unit 102.

[0055] If the time period from tBS to tBG of the trip of the new demand alone overlaps with the time period of the existing trip, and therefore it is impossible to form a trip of the new demand alone, the vehicle allocation processing unit 106 determines that vehicle allocation is impossible. If it is determined that vehicle allocation is impossible, the vehicle allocation processing unit 106 creates a ride reservation response addressed to the terminal device 20-1, including information indicating that vehicle allocation is impossible. The vehicle allocation processing unit 106 outputs the created ride reservation response to the communication unit 102.

[0056] (Reservation status management unit, vehicle reservation management method) The reservation status management unit 109 and the vehicle dispatch reservation management method according to this embodiment will be described in detail below. 4 is an explanatory diagram of the reservation states and state transitions of a demand according to the present embodiment. As shown in Fig. 4, the reservation states of a demand are provided in four types: "unconfirmed", "provisionally confirmed", "confirmed", and "cancelled".

[0057] The reservation status management unit 109 executes a reservation status management process for a demand based on the boarding reservation information accepted by the acceptance unit 104. When the request for ride reservation information received by the reception unit 104 is "creating a new reservation," the reservation status management unit 109 issues a vehicle allocation calculation request to the vehicle allocation processing unit 106. The vehicle allocation processing unit 106 searches for a vehicle allocation that satisfies the ride reservation information, based on a trip consisting of existing demands with a "confirmed" reservation status. When the reservation status management unit 109 finds the vehicle allocation, it generates new demand information as a demand with an "unconfirmed" reservation status, and stores the generated new demand information in the storage unit 110.

[0058] When the request for ride reservation information received by the reception unit 104 is a “provisionally confirmed reservation” that specifies a demand with a reservation status of “unconfirmed,” the reservation status management unit 109 checks whether a specified transition condition is met and then changes the reservation status of the demand from “unconfirmed” to “provisionally confirmed.”

[0059] When the request for ride reservation information received by the reception unit 104 is a “confirmed reservation” request specifying a demand with a “provisionally confirmed” reservation status, the reservation status management unit 109 checks whether a specified transition condition is met and then changes the reservation status of the demand from “provisionally confirmed” to “confirmed.”

[0060] If the request for ride reservation information accepted by the acceptance unit 104 is for canceling a reservation, the reservation status management unit 109 changes the reservation status of the specified demand to “cancelled”.

[0061] Here, an example of reservation state transition processing performed by the reservation state management unit 109 according to this embodiment will be described with reference to Fig. 5. Fig. 5 is an explanatory diagram of an example of reservation state transition according to this embodiment. Fig. 5 shows an example in which reservations from two users (reservation 1, reservation 2) are for the same vehicle and the same time slot and are made at approximately the same time.

[0062] First, the demand R1 of reservation 1 accepted by the accepting unit 104 is put into an "unconfirmed" reservation state by creating a new reservation R1a. In this "unconfirmed" reservation state, the demand R1 of reservation 1 is not restricted from other reservations, so the demand R2 of reservation 2 accepted by the accepting unit 104 immediately thereafter is also put into an "unconfirmed" reservation state by creating a new reservation R2a. Next, the demand R1 of reservation 1 transitions to a "provisionally confirmed" reservation state by provisionally confirming the reservation R1b. At this point, the demand R1 of reservation 1 in the "provisionally confirmed" state is restricted from transitioning to a reservation state for other reservations in order to guarantee a state transition from the "provisionally confirmed" reservation state to the "confirmed" state. Specifically, when a demand in the "provisionally confirmed" reservation state exists, a restriction is placed so that other demands for the same vehicle and time period as the demand in question cannot transition from the "unconfirmed" reservation state to the "provisionally confirmed" state.

[0063] 5, a request for tentatively confirming a reservation for demand R2 of reservation 2 is received by the reception unit 104 immediately after tentatively confirming reservation R1b of reservation 1, but due to restrictions imposed by demand R1 of reservation 1 in the "tentatively confirmed" reservation state, the transition from the "unconfirmed" reservation state to "tentatively confirmed" fails. Meanwhile, demand R1 of reservation 1, which has entered the "tentatively confirmed" reservation state, transitions to the "confirmed" reservation state due to reservation confirmation R1c received by the reception unit 104, and the trip information for demand R1 of reservation 1 in demand information 110a managed by the storage unit 110 is updated.

[0064] Next, reservation state transition conditions and transition processes will be described. (Create a demand with a reservation status of "unconfirmed") The condition for allowing the generation of a demand with a reservation status of "unconfirmed" is that the vehicle dispatch processing unit 106 finds a vehicle dispatch that satisfies the boarding reservation information. The vehicle dispatch processing unit 106 searches for a vehicle dispatch that satisfies the boarding reservation information (vehicle dispatch search) based on a trip composed of existing demands with a reservation status of "confirmed". Therefore, when the vehicle dispatch processing unit 106 finds a vehicle dispatch that satisfies the boarding reservation information, the trip of the new demand alone does not overlap with a trip composed of demands with a reservation status of "confirmed". The process of generating a demand with a reservation status of "unconfirmed" involves generating a new demand and registering it in the storage unit 110 with a reservation status of "unconfirmed", obtaining a reservation condition identifier (reservation condition ID) that identifies a vehicle dispatch (vehicle and time zone) to the new demand found by the vehicle dispatch processing unit 106 from the reservation condition identifier information 110d, and recording the obtained reservation condition identifier in the demand information 110a as the reservation condition identifier of the new demand.

[0065] (Transition from reservation status "Unconfirmed" to "Provisionally confirmed") The conditions for permitting a demand (target demand) with a reservation status of "unconfirmed" to transition to a reservation status of "tentatively confirmed" are that there is no other demand for the same vehicle and time period as the target demand that has a reservation status of "tentatively confirmed", and that the reservation condition identifier currently assigned to the vehicle and time period of the target demand matches the reservation condition identifier of the target demand in the demand information 110a. The reservation condition identifier currently assigned to a vehicle and time period is the reservation condition identifier of the vehicle and time period in the reservation condition identifier information 110d. The process of transitioning a target demand with a reservation status of "unconfirmed" to a reservation status of "tentatively confirmed" changes the registration of the reservation status of the target demand from "unconfirmed" to "tentatively confirmed".

[0066] (Transition from reservation status "provisionally confirmed" to "confirmed") The condition for permitting a demand (target demand) in the reservation state "provisionally confirmed" to transition to the reservation state "confirmed" is unconditional. The process of transitioning a demand (target demand) in the reservation state "provisionally confirmed" to the reservation state "confirmed" changes the reservation condition identifier currently assigned to the vehicle and time period of the target demand to a new reservation condition identifier, and updates the trip information in the demand information 110a including the target demand. The process of changing the reservation condition identifier currently assigned to a vehicle and time period to a new reservation condition identifier changes the reservation condition identifier of the vehicle and time period in the reservation condition identifier information 110d to the new reservation condition identifier.

[0067] (Transition from reservation status "Unconfirmed", "Provisionally confirmed" and "Confirmed" to "Cancelled") The condition for permitting a demand (target demand) in the reservation states of "unconfirmed", "provisionally confirmed", and "confirmed" to transition to the reservation state of "cancelled" is unconditional. The process of transitioning a demand (target demand) in the reservation states of "unconfirmed", "provisionally confirmed", and "confirmed" to the reservation state of "cancelled" deletes the registration of the target demand. Furthermore, the process of transitioning a demand (target demand) in the reservation state of "confirmed" to the reservation state of "cancelled" changes the reservation condition identifier currently assigned to the vehicle and time period of the target demand to a new reservation condition identifier, and updates the information of the trip in the demand information 110a including the target demand.

[0068] A reservation confirmation grace period condition may be added to the above-mentioned transition conditions for each reservation state. This reservation confirmation grace period condition sets an upper limit (reservation confirmation grace period) on the elapsed time from when a demand in the reservation state "unconfirmed" is generated until the demand transitions to the reservation state "confirmed". The reservation state management unit 109 measures the elapsed time from when a demand in the reservation state "unconfirmed" is generated, and includes in the transition conditions that the elapsed time of the measurement result is equal to or less than a predetermined reservation confirmation grace period when the demand transitions to each reservation state, that is, when the demand transitions from "unconfirmed" to "provisionally confirmed" or from "provisionally confirmed" to "confirmed".

[0069] Next, the reservation condition identifier will be described in detail. The reservation condition identifier is an identifier that identifies a vehicle and a time period, and is assigned to each vehicle and time period. Therefore, the reservation condition identifier is different for each vehicle. Furthermore, even for the same vehicle, the reservation condition identifier is different for each time period. An example of a reservation condition identifier is a combination of the vehicle ID of the vehicle to which the identifier is assigned and the current time when the reservation condition identifier is updated (assigned a new one or changed to an existing value).

[0070] The reservation condition identifier functions as a flag for confirming that there is no change in the trip corresponding to the vehicle and time period of the new demand from the time when the vehicle allocation processing unit 106 performs a vehicle allocation search to generate a new demand with a reservation status of "unconfirmed". This point will be described below.

[0071] In this embodiment, it is guaranteed that a demand in the reservation status "provisionally confirmed" can make a state transition from the reservation status "provisionally confirmed" to the reservation status "confirmed." On the other hand, a new demand in the reservation state "unconfirmed" can be generated as long as it does not overlap with a trip (vehicle and time period) configured by a demand in the reservation state "confirmed" through a vehicle dispatch search by the vehicle dispatch processing unit 106. In other words, even if the vehicle and time period of the new demand overlap with a trip (vehicle and time period) configured by a demand in the reservation state "tentatively confirmed" at the time of generating the new demand in the reservation state "unconfirmed", the new demand can be generated. This is because a user does not necessarily confirm a reservation for a demand in the reservation state "tentatively confirmed", and therefore, in order to meet the vehicle dispatch search needs of other users, no restriction is imposed on the generation of a new demand in the reservation state "unconfirmed" due to the demand in the reservation state "tentatively confirmed", thereby expanding the opportunities to generate a new demand in the reservation state "unconfirmed". In order to ensure that a demand in the "provisionally confirmed" reservation state transitions to the "confirmed" reservation state and to increase the opportunity to generate a new demand in the "unconfirmed" reservation state, a reservation condition identifier is used.

[0072] As a specific example, a method for using a reservation condition identifier in reservation state transition processing performed by the reservation state management unit 109 will be described with reference to Fig. 6. Fig. 6 is an explanatory diagram of an example of reservation state transition according to this embodiment. Like Fig. 5, Fig. 6 shows an example in which reservations from two users (reservation 1, reservation 2) are for the same vehicle and the same time slot and are made at approximately the same time.

[0073] First, the demand R1 of reservation 1 accepted by the reception unit 104 becomes in an "unconfirmed" reservation state due to new reservation creation R1a. At this time, the reservation state management unit 109 acquires the reservation condition identifier Rid1 currently assigned to the allocation (vehicle and time period) to the demand R1 of reservation 1 found by the allocation processing unit 106 from the reservation condition identifier information 110d, and records the acquired reservation condition identifier in the demand information 110a as the reservation condition identifier of the demand R1 of reservation 1. At this "unconfirmed" reservation state stage, the demand R1 of reservation 1 is not restricted with respect to other reservations.

[0074] Next, demand R2 of reservation 2, which was accepted by the accepting unit 104 immediately after reservation 1, becomes in an "unconfirmed" reservation state due to new reservation creation R2a. At this time, the reservation state management unit 109 acquires the reservation condition identifier Rid1 currently assigned to the allocation (vehicle and time period) to demand R2 of reservation 2 found by the allocation processing unit 106 from the reservation condition identifier information 110d, and records the acquired reservation condition identifier in the demand information 110a as the reservation condition identifier of demand R2 of reservation 2. Therefore, at this point, the same reservation condition identifier Rid1 is recorded in the demand information 110a for demand R1 of reservation 1 and demand R2 of reservation 2, for which the same allocation (vehicle and time period) was found.

[0075] At this stage, the reservation status management unit 109 may notify the terminal device 20-1 of each user who has made a vehicle reservation with the reservation status of “unconfirmed” that there is a conflict between multiple users over vehicle reservations for a demand with the reservation status of “unconfirmed.” For example, when there are multiple demands R1, R2 in the reservation status "unconfirmed" and the same reservation condition identifier Rid1 currently assigned to the vehicle dispatch (vehicle and time period) to be reserved is recorded in the demand information 110a, the reservation status management unit 109 may notify the terminal devices 20-1 of the users of all the demands R1, R2 in the reservation status "unconfirmed" that vehicle dispatch reservations in the reservation status "unconfirmed" have been made by multiple users. This makes it possible to notify the users of all the demands R1, R2 in the reservation status "unconfirmed" that vehicle dispatch reservations in the reservation status "unconfirmed" are currently competing among multiple users. For example, when there is at least one demand R1 in a reservation status of "unconfirmed" and the same reservation condition identifier Rid1 as the reservation condition identifier currently assigned to the vehicle dispatch (vehicle and time period) to be reserved is recorded in the demand information 110a, the reservation status management unit 109 may notify the terminal device 20-1 of the user of another demand R2 in a reservation status of "unconfirmed" for which the reservation condition identifier Rid1 is newly recorded in the demand information 110a, that vehicle dispatch reservations in the reservation status of "unconfirmed" have been made by multiple users. This makes it possible to notify the user of the new demand R2 in the reservation status of "unconfirmed" that vehicle dispatch reservations in the reservation status of "unconfirmed" are currently competing among multiple users.

[0076] Next, the demand R1 of reservation 1 transitions to a reservation state of "provisionally confirmed" by the reservation provisional confirmation R1b. At this time, the reservation state management unit 109 confirms that the demand R1 of reservation 1 satisfies the transition condition from the reservation state "unconfirmed" to "provisionally confirmed". As described above, the transition condition is "Condition A1: There is no other demand in the reservation state "provisionally confirmed" for the same vehicle and time period as the target demand R1 in the reservation state "unconfirmed"" and "Condition B1: The reservation condition identifier currently assigned to the vehicle and time period of the target demand R1 matches the reservation condition identifier Rid1 of the target demand R1 in the demand information 110a". At this point, the demand R2 of reservation 2 is still in the reservation state of "unconfirmed", so the above condition A1 is satisfied. Also, at this point, the reservation condition identifier currently assigned to the vehicle and time period of the demand R1 of reservation 1 is "Rid1", so the above condition B1 is also satisfied. Therefore, the transition condition is satisfied, and the reservation status management unit 109 changes the registration of the reservation status of demand R1 of reservation 1 from "unconfirmed" to "provisionally confirmed."

[0077] Next, demand R1 of reservation 1, which has been in the "provisionally confirmed" reservation state, transitions to the "confirmed" reservation state by reservation confirmation R1c received by the reception unit 104. At this time, the reservation state management unit 109 changes the reservation condition identifier "Rid1" currently assigned to the vehicle and time period of demand R1 of reservation 1 to a new reservation condition identifier "Rid1'", and updates the corresponding information in the demand information 110a with the changed reservation condition identifier Rid1' as the reservation condition identifier of demand R1 of reservation 1. The process of changing the reservation condition identifier "Rid1" currently assigned to the vehicle and time period of demand R1 of reservation 1 to the new reservation condition identifier "Rid1'" changes the reservation condition identifier "Rid1" of the vehicle and time period in the reservation condition identifier information 110d to the new reservation condition identifier "Rid1'".

[0078] Next, the request for provisional reservation confirmation of the demand R2 of reservation 2 is received by the reception unit 104 immediately after the reservation confirmation R1c of reservation 1. At this time, the reservation status management unit 109 confirms that the demand R2 of reservation 2 satisfies the transition condition from the reservation status "unconfirmed" to "provisionally confirmed". As described above, the transition condition is "Condition A2: There is no other demand for the same vehicle and the same time slot as the target demand R2 in the reservation status "unconfirmed" and whose reservation status is "provisionally confirmed"" and "Condition B2: The reservation condition identifier currently assigned to the vehicle and time slot of the target demand R2 matches the reservation condition identifier Rid1 of the target demand R2 in the demand information 110a". At this point, the demand R1 of reservation 1 is in the reservation status "confirmed", and there is no other demand for the same vehicle and the same time slot as the demand R2 of reservation 2 and whose reservation status is "provisionally confirmed", so the above condition A2 is satisfied. On the other hand, at this point in time, the reservation condition identifier currently assigned to the vehicle and time period of demand R2 of reservation 2 (i.e., the reservation condition identifier of the vehicle and time period in the reservation condition identifier information 110d) has changed to "Rid1'", which does not match the reservation condition identifier Rid1 of the demand R2 in the demand information 110a. Therefore, the above condition B2 is not satisfied. Since the transition condition is not satisfied, the reservation status management unit 109 does not transition the reservation status of demand R2 of reservation 2 from "unconfirmed" to "tentatively confirmed". Then, the reservation status management unit 109 notifies the terminal device 20-1 of the user of reservation 2 that the vehicle dispatch reservation of reservation 2 cannot be transitioned from the reservation status "unconfirmed" to "tentatively confirmed".

[0079] In the example of FIG. 6, the demand R2 of reservation 2 satisfies the condition A2, among the transition conditions for transitioning from the reservation state "unconfirmed" to "provisionally confirmed", that is, "There is no other demand in the reservation state "provisionally confirmed" for the same vehicle and in the same time period as the target demand R2 in the reservation state "unconfirmed". This is because another demand R1 in the same vehicle and in the same time period as the target demand R2 has transitioned from the reservation state "provisionally confirmed" to "confirmed". Therefore, in this case, the target demand R2 must not be transitioned from the reservation state "unconfirmed" to "provisionally confirmed". This is because if the target demand R2 is transitioned from the reservation state "unconfirmed" to "provisionally confirmed", it must be guaranteed that the target demand R2 can transition from the reservation state "provisionally confirmed" to "confirmed", and there is a possibility that the vehicle dispatch reservation of reservation 2 will be confirmed in overlap with the vehicle dispatch reservation of reservation 1 that has already been confirmed.

[0080] Therefore, in this embodiment, when the demand R1 in the reservation state "provisionally confirmed" transitions to the reservation state "confirmed," the reservation condition identifier "Rid1" currently assigned to the vehicle and time period of the demand R1 is changed to a new reservation condition identifier "Rid1'." Furthermore, as a transition condition for transitioning the demand R2 of reservation 2 from the reservation state "unconfirmed" to "provisionally confirmed," "Condition B2: the reservation condition identifier currently assigned to the vehicle and time period of the target demand matches the reservation condition identifier of the target demand in the demand information 110a." As a result, even if the demand R2 of reservation 2 satisfies condition A2, it does not satisfy condition B2, and the state transition from the reservation state "unconfirmed" to "provisionally confirmed" is not allowed, so that it is possible to prevent the vehicle dispatch reservation of reservation 2 from being confirmed in an overlapping manner with the vehicle dispatch reservation of reservation 1 that has already been confirmed.

[0081] In this manner, according to this embodiment, by using the reservation condition identifier, it is possible to obtain the exceptional effect of simultaneously guaranteeing the state transition of a demand in the reservation status of "provisionally confirmed" to the reservation status of "confirmed" and fulfilling the opportunity to generate a new demand in the reservation status of "unconfirmed".

[0082] FIG. 7 is an explanatory diagram for explaining the correspondence between trips and reservation condition identifiers according to this embodiment. A reservation condition identifier is assigned for each vehicle and time period, and in the example of FIG. 7, time periods are defined in 30-minute intervals. Therefore, a different reservation condition identifier value is set for each 30-minute time period for one vehicle. Also, a different reservation condition identifier value is set for each vehicle. Therefore, the reservation condition identifier information 110d has the latest reservation condition identifier for each vehicle and each 30-minute time period.

[0083] 7(1) is set for one vehicle VE_1, spanning a time period "from 13:00 to 13:30" and a time period "from 13:30 to 14:00". Therefore, trip J1 is associated with a reservation condition identifier corresponding to the time period "from 13:00 to 13:30" and a reservation condition identifier corresponding to the time period "from 13:30 to 14:00" for the target vehicle VE_1.

[0084] 7(2) is set for one vehicle VE_2, spanning the time period "13:00 to 13:30", the time period "13:30 to 14:00", and the time period "14:00 to 14:30". Therefore, trip J2 is associated with a reservation condition identifier corresponding to the time period "13:00 to 13:30", a reservation condition identifier corresponding to the time period "13:30 to 14:00", and a reservation condition identifier corresponding to the time period "14:00 to 14:30", all of which are related to the target vehicle VE_2.

[0085] The reservation state management unit 109 refers to the reservation condition identifier associated with the target trip when a new demand is generated or when the reservation state of an existing demand changes.

[0086] The reservation status management unit 109 has been described in detail above.

[0087] (How to reserve a vehicle) Next, the vehicle reservation method according to the present embodiment will be described using examples of screens displayed on the display device (e.g., a touch panel) of the terminal device 20-1. Figures 8 to 13 are diagrams showing examples of the display screens of the terminal device according to the present embodiment.

[0088] The screens shown in Figures 8 to 13 are generated based on data related to vehicle reservation transmitted and received between the terminal device 20-1 and the management server 100. The display data for the screens shown in Figures 8 to 13 may be generated by the terminal device 20-1, or may be generated by the management server 100 and transmitted to the terminal device 20-1.

[0089] FIG. 8 is an example of the vehicle reservation screen 400 in its initial state. In the vehicle reservation screen 400 of FIG. 8, a display portion 401 displays user information of the user making the reservation (user ID, registration date, name, nickname, gender, age, phone number, email address, home address, notes, etc.).

[0090] In the display portion 402, the user can select an option for the ride search. The radio buttons allow the selection of "cart only" or "integrated search." If the user selects "cart only," a ride search is performed using only on-demand vehicles. On the other hand, if the user selects "integrated search," a ride search is performed that involves transfers between on-demand vehicles and other public transportation. In the display portion 402, the information selected in the checkbox for refusing ride sharing and the pull-down list for the number of people reserved are both used in the ride search process.

[0091] In the display section 403, the user selects the departure point and destination and specifies the time (instant reservation, desired departure time specification, desired arrival time specification). The departure point and destination can be specified by searching in the input form, specifying the home using the home input button, selecting from the map displayed in the display section 404, etc. The display section 405 is provided with a vehicle dispatch search button, a search result display field, a provisional confirmation button, and a cancel button.

[0092] 8, when the user inputs the necessary information into display areas 402 and 403 and then presses the vehicle dispatch search button, ride reservation information including the input information is transmitted as a ride reservation request from terminal device 20-1 to management server 100. In management server 100, reservation status management unit 109 performs a vehicle dispatch search via vehicle dispatch processing unit 106 in response to a request to create a new reservation based on the ride reservation information acquired via reception unit 104.

[0093] 9 is an example of the vehicle allocation reservation screen 400 when a vehicle allocation available is found by the vehicle allocation search. Since a vehicle allocation available is found by the vehicle allocation search, the reservation status management unit 109 creates a new demand with a reservation status of “unconfirmed” at this stage.

[0094] 9, the display section 405 displays the scheduled departure time, scheduled arrival time, departure point information, destination information, number of people, vehicle ID, etc. of possible vehicles found by the vehicle search in the search result display field, along with a provisional confirmation button and a cancel button. Also, the map in the display section 404 displays the route from the departure point to the destination corresponding to the display content of the display section 405. When the cancel button is pressed at this stage, the operation information is transmitted from the terminal device 20-1 to the management server 100, and the reservation status management section 109 changes the reservation status of the demand from "unconfirmed" to "cancelled" in response to the cancellation request made by the operation information.

[0095] On the other hand, Fig. 10 shows an example of the vehicle dispatch reservation screen 400 when no available vehicle dispatch is found by the vehicle dispatch search. In this case, a new demand is not created, and when the user presses the OK button, the initial state screen of the vehicle dispatch reservation screen 400 in Fig. 8 is displayed again.

[0096] 9, when a user presses the provisional confirmation button, ride reservation information including the operation information is transmitted as a ride reservation request from the terminal device 20-1 to the management server 100. In the management server 100, in response to a request for provisional confirmation of a reservation based on the ride reservation information acquired via the reception unit 104, the reservation status management unit 109 confirms that the transition condition from the reservation status "unconfirmed" to "provisionally confirmed" is satisfied, and then changes the reservation status of the demand from "unconfirmed" to "provisionally confirmed."

[0097] Fig. 11 is an example of the vehicle reservation screen 400 when the reservation status of a demand is changed to "provisionally confirmed". In the vehicle reservation screen 400 in Fig. 11, a button for confirming the reservation ("Yes") and a button for canceling the confirmed reservation ("No") are provided at the end of the display portion 405. When the button for canceling the confirmed reservation ("No") is pressed at this stage, the operation information is transmitted from the terminal device 20-1 to the management server 100, and the reservation status management unit 109 changes the reservation status of the demand from "provisionally confirmed" to "cancelled" in response to the cancellation request by the operation information.

[0098] 11, when the user presses a button for confirming the reservation ("Yes"), ride reservation information including the operation information is transmitted as a ride reservation request from the terminal device 20-1 to the management server 100. In the management server 100, the reservation status management unit 109 changes the reservation status of the demand from "provisionally confirmed" to "confirmed" in response to the request for reservation confirmation based on the ride reservation information acquired via the reception unit 104.

[0099] Fig. 12 is an example of the vehicle reservation screen 400 when the reservation status of the demand is changed to "confirmed". The vehicle reservation screen 400 in Fig. 12 displays a message indicating that the reservation has been confirmed, and displays buttons for selecting the next screen to be displayed ("Go to top", "Continue").

[0100] FIG. 13 is an example of a screen configuration that displays reservation information of a demand whose reservation status is "confirmed." The reservation status details screen shown in FIG. 13 allows the user to check detailed reservation information of a demand whose reservation status is "confirmed." In addition, the user can cancel a reservation of the demand whose reservation status is "confirmed" by pressing a reservation cancel button provided on the reservation status details screen shown in FIG. 13. When the reservation cancel button is pressed on the reservation status details screen in FIG. 13, the operation information is transmitted from terminal device 20-1 to management server 100, and reservation status management unit 109 changes the reservation status of the demand from "confirmed" to "cancelled" in response to the cancellation request made by the operation information.

[0101] As described above, according to this embodiment, in a demand-based vehicle dispatch management system that operates vehicles in response to reservations, the reservation states of a demand are set to "unconfirmed," "provisionally confirmed," and "confirmed." The demand reservation state "unconfirmed" is a state in which no restrictions are imposed on vehicle dispatch searches and reservation state transitions of demands other than the demand in question, and the demand reservation state "provisionally confirmed" is a state in which no restrictions are imposed on vehicle dispatch searches of demands other than the demand in question, but restrictions are imposed on the transition of the reservation state of demands other than the demand in question from "unconfirmed" to "provisionally confirmed." The reservation status of a demand is "confirmed" and is a status that restricts vehicle dispatch searches for demands other than the demand in question. The system includes a reservation condition identifier for identifying a vehicle and a time period, a reservation condition identifier information storage unit (reservation condition identifier information 110d of the storage unit 110) that stores the latest reservation condition identifier for each vehicle and time period, a demand information storage unit (demand information 110a of the storage unit 110) that stores demand-related information indicating each user's demand and a reservation condition identifier for each demand, and a demand information storage unit (demand information 110a of the storage unit 110) that manages the reservation status of a demand and transitions the reservation status of a demand in response to a user request. and a reservation state management unit for recording a reservation state of a new demand for which a vehicle dispatch search has been successful as a reservation state of “unconfirmed”, and a transition condition for permitting a transition of the reservation state of a target demand from “unconfirmed” to “provisionally confirmed” is that there is no other demand for the same vehicle and time period as the target demand whose reservation state is “provisionally confirmed”, and that the reservation condition identifier currently assigned to the vehicle and time period of the target demand matches the reservation condition identifier of the target demand in the demand information storage unit. The reservation state management unit records a new demand for which a vehicle dispatch search has been successful as a reservation state of “unconfirmed”, and records a new demand for which a vehicle dispatch search has been successful as a reservation state of “unconfirmed”. the reservation condition identifier currently assigned to the vehicle and time slot of the demand in the reservation condition identifier information storage unit is stored in the demand information storage unit as the reservation condition identifier of the demand, and when a demand in a reservation state of “provisionally confirmed” transitions to a reservation state of “confirmed”, the reservation state management unit changes the reservation condition identifier currently assigned to the vehicle and time slot of the demand in the reservation condition identifier information storage unit to a new reservation condition identifier, and the reservation state management unit determines whether or not to transition the reservation state of the target demand from “unconfirmed” to “provisionally confirmed” based on the transition condition,According to the result of the determination, the reservation status of the target demand is changed to "provisionally confirmed".

[0102] With the configuration according to this embodiment, a user who is interested in on-demand transportation and wants to search for vehicle dispatching but does not intend to confirm a reservation can freely generate a demand with a reservation status of "unconfirmed" and check the vehicle dispatch search results. Also, a user who intends to confirm a reservation can change a demand with a reservation status of "unconfirmed" to a reservation status of "provisionally confirmed" after confirming the scheduled departure time from the departure point and the scheduled arrival time at the destination, and then change the demand with a reservation status of "provisionally confirmed" to a reservation status of "confirmed" without worrying about overlapping reservations. In this way, according to this embodiment, in a demand-based vehicle dispatch management system that operates vehicles according to reservations, it is possible to achieve a reservation status management that combines a free vehicle dispatch search and measures to prevent overlapping reservations.

[0103] Furthermore, this will make it possible to improve the overall service quality of on-demand transportation services, for example, and thereby contribute to Goal 9 of the United Nations-led Sustainable Development Goals (SDGs), which is to "build resilient infrastructure, promote sustainable industrialization and foster innovation."

[0104] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like that do not deviate from the gist of the present invention are also included.

[0105] In addition, a computer program for implementing the functions of each of the above-mentioned devices may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed. Note that the "computer system" referred to here may include hardware such as an OS and peripheral devices. In addition, the term "computer-readable recording medium" refers to writable non-volatile memory such as a flexible disk, an optical magnetic disk, a ROM, or a flash memory, a portable medium such as a DVD (Digital Versatile Disc), or a storage device such as a hard disk built into a computer system.

[0106] Furthermore, the term "computer-readable recording medium" includes devices that retain a program for a certain period of time, such as volatile memory (e.g., DRAM (Dynamic Random Access Memory)) within a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. The program may be transmitted from a computer system in which the program is stored in a storage device or the like to another computer system via a transmission medium, or by a transmission wave in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for implementing some of the functions described above, or may be a so-called differential file (differential program) that can implement the functions described above in combination with a program already recorded in the computer system. [Explanation of symbols]

[0107] 1...vehicle dispatch management system, 20-1, 20-2, 20-3...terminal devices, 30...vehicle-mounted device, 100...management server, 102...communication unit, 104...reception unit, 106...vehicle dispatch processing unit, 108...route search unit, 109...reservation status management unit, 110...storage unit, 110a...demand information, 110b...vehicle information, 110c...user information, 110d...reservation condition identifier information, VE...vehicle, NW...network

Claims

1. In a demand-based vehicle dispatch management system that operates vehicles according to reservations, A "first state" and a "second state" are provided as reservation states of a demand, The reservation state of a demand is a "first state" that does not impose any restriction on the transition of the reservation states of demands other than the demand in question, The reservation state of a demand is the "second state", which does not impose any restriction on vehicle dispatch searches for demands other than the demand in question, but imposes restrictions on transitions of the reservation states of demands other than the demand in question from the "first state" to the "second state", A reservation state management unit that manages a reservation state of a demand and transitions the reservation state of the demand in response to a user request, A transition condition for permitting the reservation state of the target demand to transition from the “first state” to the “second state” includes that there is no other demand in the same vehicle and in the same time period as the target demand and whose reservation state is the “second state”, the reservation state management unit determines whether to transition the reservation state of the target demand from a “first state” to a “second state” based on the transition condition, and changes the reservation state of the target demand to the “second state” in accordance with a result of the determination; Vehicle dispatch management system.

2. The reservation state of a demand is the "third state", which restricts vehicle dispatch searches for demands other than the demand in question. A reservation condition identifier is provided for each vehicle and each time period. a reservation condition identifier information storage unit that stores the latest reservation condition identifier for each vehicle and each time period; a demand information storage unit that stores demand-related information indicating a demand of each user and a reservation condition identifier for each demand, A transition condition for permitting the transition of the reservation state of a target demand from “first state” to “second state” is that there is no other demand in the same vehicle and time period as the target demand, the reservation state of which is “second state”, and the reservation condition identifier in the reservation condition identifier information storage unit currently assigned to the vehicle and time period of the target demand matches the reservation condition identifier of the target demand in the demand information storage unit. When a demand in a reservation state "second state" transitions to a reservation state "third state", the reservation state management unit changes the reservation condition identifier currently assigned to the vehicle and time period of the demand in the reservation condition identifier information storage unit to a new reservation condition identifier. The vehicle dispatch management system according to claim 1 .

3. The reservation state of a demand is the "third state", which restricts vehicle dispatch searches for demands other than the demand in question. The fourth demand reservation state is a state in which a request to cancel the reservation of the demand has been accepted. A reservation condition identifier is provided for each vehicle and each time period. a reservation condition identifier information storage unit that stores the latest reservation condition identifier for each vehicle and each time period; a demand information storage unit that stores demand-related information indicating a demand of each user and a reservation condition identifier for each demand, A transition condition for permitting the transition of the reservation state of a target demand from “first state” to “second state” is that there is no other demand in the same vehicle and time period as the target demand, the reservation state of which is “second state”, and the reservation condition identifier in the reservation condition identifier information storage unit currently assigned to the vehicle and time period of the target demand matches the reservation condition identifier of the target demand in the demand information storage unit. When a demand in a reservation state "third state" transitions to a reservation state "fourth state", the reservation state management unit changes the reservation condition identifier currently assigned to the vehicle and time period of the demand in the reservation condition identifier information storage unit to a new reservation condition identifier. The vehicle dispatch management system according to claim 1 .

4. The "first state" is a state in which no restrictions are imposed on the transition of vehicle dispatch searches and reservation states of demands other than the demand in question. The vehicle dispatch management system according to claim 1 .

5. the reservation state management unit measures an elapsed time since a demand in a reservation state "first state" was generated, and includes, as a transition condition of each reservation state of the demand, the elapsed time being equal to or less than a predetermined reservation confirmation grace period; The vehicle dispatch management system according to claim 1 .

6. the reservation state management unit notifies a terminal device of a user of the demand in the reservation state "first state" that a vehicle dispatch reservation for the demand in the reservation state "first state" is competing among a plurality of users; The vehicle dispatch management system according to claim 1 .

7. A vehicle dispatch reservation management method executed by a demand-type vehicle dispatch management system that operates vehicles according to reservations, comprising: A "first state" and a "second state" are provided as reservation states of a demand, The reservation state of a demand is a "first state" that does not impose any restriction on the transition of the reservation states of demands other than the demand in question, The reservation state of a demand is the "second state", which does not impose any restriction on vehicle dispatch searches for demands other than the demand in question, but imposes restrictions on transitions of the reservation states of demands other than the demand in question from the "first state" to the "second state", a reservation state management step of managing a reservation state of a demand and transitioning the reservation state of the demand in response to a user request; A transition condition for permitting the reservation state of the target demand to transition from the “first state” to the “second state” includes that there is no other demand in the same vehicle and in the same time period as the target demand and whose reservation state is the “second state”, the reservation state management step determines whether or not to transition a reservation state of a target demand from a “first state” to a “second state” based on the transition condition, and changes the reservation state of the target demand to the “second state” in accordance with a result of the determination; How to manage vehicle reservations.

8. The computer of the demand-based vehicle dispatch management system that operates vehicles according to reservations, A "first state" and a "second state" are provided as reservation states of a demand, The reservation state of a demand is a "first state" that does not impose any restriction on the transition of the reservation states of demands other than the demand in question, The reservation state of a demand is the "second state", which does not impose any restriction on vehicle dispatch searches for demands other than the demand in question, but imposes restrictions on transitions of the reservation states of demands other than the demand in question from the "first state" to the "second state", A computer program for executing a reservation state management step of managing a reservation state of a demand and transitioning the reservation state of the demand in response to a user request, A transition condition for permitting the reservation state of the target demand to transition from the “first state” to the “second state” includes that there is no other demand in the same vehicle and in the same time period as the target demand and whose reservation state is the “second state”, the reservation state management step determines whether or not to transition a reservation state of a target demand from a “first state” to a “second state” based on the transition condition, and changes the reservation state of the target demand to the “second state” in accordance with a result of the determination; Computer program.

Citation Information

Patent Citations

  • Information system, program, and information processing method

    JP2011186795A

  • Apparatus and method for managing vehicle dispatch

    JP2014032459A

  • Product purchase support device, product purchase support system, product purchase support method and program

    JP2016040676A

  • Vehicle lending system, vehicle lending method, and management server

    JP2017016450A

  • Ticketing system, terminal and ticket-vending machine

    JP2020008891A