Reservation management apparatus and reservation management method
The reservation management system confirms user presence at the boarding location using facility terminals, ensuring authorized vehicle dispatch, addressing the issue of user availability in existing systems.
Patent Information
- Application Number
- PCT/JP2024/030767
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-28
- Publication Date
- 2026-03-05
AI Technical Summary
Existing vehicle dispatch systems cannot confirm if a user is present at the boarding location without a communication terminal, leading to potential mismatches between vehicle arrival and user availability.
A reservation management system that uses facility terminals installed in pre-registered locations to identify users and confirm their presence at the boarding location, ensuring vehicle dispatch only after approval from an approver.
Ensures vehicles are dispatched only when the user is present at the boarding location, adhering to approved reservations, thereby preventing unauthorized use and providing peace of mind for approvers.
Smart Images

Figure JP2024030767_05032026_PF_FP_ABST
Abstract
Description
Reservation management device and reservation management method
[0001] The present invention relates to a reservation management device and a reservation management method.
[0002] Patent Literature 1 discloses a vehicle dispatch support system including a vehicle dispatch support server, in which a mobile terminal requests vehicle dispatch by notifying the vehicle dispatch support server of information related to the current location of the mobile terminal and information related to a destination.
[0003] Japanese Patent Application Laid-Open No. 2003-109189
[0004] However, with the method disclosed in Patent Document 1, if a user who uses a vehicle does not have a terminal, it is not possible to confirm that the user is at the boarding location. Therefore, even if a vehicle arrives at the boarding location according to a vehicle reservation, there is a possibility that the user is not at the boarding location.
[0005] An object of the present invention is to provide a reservation management device and a reservation management method that can dispatch a vehicle after confirming that a user is at the boarding location.
[0006] A reservation management device according to one aspect of the present invention acquires identification information for identifying a user from a facility terminal installed in a pre-registered facility. If the user identified from the identification information acquired from the facility terminal is a user who requires approval from an approver, the reservation management device confirms the vehicle reservation based on the location of the facility terminal from which the user's identification information was acquired and the vehicle reservation candidates approved by the approver.
[0007] According to one aspect of the present invention, a vehicle can be dispatched after confirming that the user is at the boarding location.
[0008] Fig. 1 is a diagram schematically showing the configuration of a vehicle dispatch system according to this embodiment. Fig. 2 is a diagram explaining a user database. Fig. 3 is a diagram explaining a reservation management database. Fig. 4 is a flowchart showing the process of registering vehicle dispatch reservation candidates. Fig. 5 is a flowchart showing the process related to vehicle dispatch.
[0009] Hereinafter, with reference to the drawings, a reservation management device and a reservation management method according to this embodiment will be described using a vehicle dispatch service system as an example.
[0010] The configuration of a vehicle dispatch service system 1 according to this embodiment will be described with reference to FIG. 1. The vehicle dispatch service system 1 is a system that provides a service of transporting passengers using a vehicle Vc. The vehicle dispatch service system 1 can make a reservation for dispatching a vehicle Vc and dispatch the vehicle Vc based on the reservation. Here, a vehicle dispatch reservation refers to reserving the dispatch of a vehicle Vc by specifying the boarding location, boarding time, disembarking location, etc. of the vehicle Vc. Executing a vehicle dispatch refers to operating the vehicle Vc in accordance with the reservation.
[0011] The vehicle dispatch service system 1 of this embodiment is used by a user Pb and an approver Pa. The user Pb is a person who uses a vehicle Vc of the vehicle dispatch service system 1, i.e., a passenger. The approver Pa is a person who approves the user Pb's use of the service. In the vehicle dispatch service system 1, the user Pb can use the vehicle Vc within the scope registered by the approver Pa. An example of the approver Pa is a parent, and the user Pb is their child. However, the relationship between the approver Pa and the user Pb may be such that the approver Pa approves the actions of the user Pb. For example, the relationship between the approver Pa and the user Pb may be such that the approver Pa is an adult and the user Pb is their parent. The relationship between the approver Pa and the user Pb may also be such that the approver Pa is a guardian and the user Pb is a ward. In addition, this embodiment assumes that the user Pb does not possess a communication terminal such as a smartphone.
[0012] The vehicle dispatch service system 1 includes a reservation management server 10, a vehicle dispatch server 20, an approver terminal 30, and a facility terminal 40. The reservation management server 10, the vehicle dispatch server 20, the approver terminal 30, and the facility terminal 40 are connected via a network (not shown).
[0013] The reservation management server 10 manages vehicle dispatch reservations for vehicles Vc used by users Pb. The reservation management server 10 is operated by a different operator from the vehicle dispatch server 20 described below, but may also be operated by the same operator as the vehicle dispatch server 20. The reservation management server 10 includes a reservation management control device 11, a communication device 12, and a reservation management database (reservation management DB) 13.
[0014] The reservation management control device 11 is a microcomputer (controller) mainly composed of a CPU, memory, and an input / output interface. The CPU reads various computer programs stored in the memory and executes various commands contained in the programs.
[0015] The reservation management control device 11 can transmit and receive information between the vehicle dispatch server 20, the approver terminal 30, and the facility terminal 40 via the communication device 12. The reservation management control device 11 can also refer to information in the reservation management DB 13.
[0016] In this embodiment, the reservation management control device 11 acquires user identification information that identifies the user Pb from the facility terminal 40. The reservation management control device 11 determines whether the user Pb identified from the user identification information acquired from the facility terminal 40 is a user Pb that requires approval from the approver Pa. If the user Pb requires approval from the approver Pa, the reservation management control device 11 confirms the vehicle reservation based on the location of the facility terminal 40 from which the user identification information was acquired and the vehicle reservation candidates that the approver Pa has approved.
[0017] The communication device 12 communicates with the vehicle dispatch server 20, the approver terminal 30, and the facility terminal 40. The communication device 12 receives information from the vehicle dispatch server 20, the approver terminal 30, and the facility terminal 40, and transmits information to the vehicle dispatch server 20, the approver terminal 30, and the facility terminal 40. For example, the communication device 12 may be a device equipped with a mobile communication function such as 4G / LTE or 5G, or may be a device equipped with a Wi-Fi communication function.
[0018] The reservation management DB 13 is a storage device that stores various information necessary for reservation management. The reservation management DB 13 includes a user database (user DB) 13a shown in Fig. 2 and a vehicle reservation database (vehicle reservation DB) 13b shown in Fig. 3.
[0019] The user DB 13a records the correspondence between the approver Pa and the user Pb who needs approval from the approver Pa. The "Approver" column of the user DB 13a describes approver identification information that identifies the approver Pa, and the "User" column describes user identification information. Note that if there are multiple users Pb for the approver Pa, multiple users Pb may be recorded in the "User" column.
[0020] The vehicle reservation DB 13b records vehicle reservation candidates that the approver Pa has authorized the user Pb to use. The user Pb can only request a vehicle reservation from vehicle reservation candidates registered in the vehicle reservation DB 13b. The vehicle reservation candidates include information such as "Approver," "Boarding Time," "Boarding Location," "Dropping Location," "Number of People," and "Type." The "Approver" field contains the approver identification information of the approver Pa who registered the vehicle reservation candidate. The "Boarding Time," "Boarding Location," "Dropping Location," and "Number of People" are information necessary for reserving a vehicle Vc. The "Boarding Time," "Boarding Location," "Dropping Location," and "Number of People" fields contain the time or date of boarding the vehicle Vc, the boarding location for boarding the vehicle Vc, the drop-off location for disembarking from the vehicle Vc, and the number of people aboard the vehicle Vc, respectively. In this embodiment, the boarding location specified in the vehicle reservation candidate is selected from pre-registered facilities, i.e., facilities where a facility terminal 40 is installed. Note that the "Boarding Location" may be the address of the facility instead of the name of the facility. Furthermore, the information required for reserving a vehicle Vc only needs to include the "boarding time," "boarding location," and "drop-off location," and does not necessarily need to include the "number of people." The type indicates the type of vehicle reservation candidate. There are two types of vehicle reservations: advance reservations and permitted destinations. An advance reservation is a vehicle reservation candidate for which the boarding time, boarding location, drop-off location, and number of people are specified in advance. On the other hand, a permitted destination is a vehicle reservation candidate for which at least the drop-off location is specified by permission. Furthermore, an event such as a festival or a festival may be selected as a permitted destination. In this case, a database in which the location, date, time, or period of the event is stored in advance may be referenced, and a vehicle reservation candidate that specifies at least the drop-off location may be registered as a permitted destination based on information identified from this database.
[0021] 1, the vehicle dispatch server 20 dispatches vehicles Vc. The vehicle dispatch server 20 is operated, for example, by a business operator that provides a service of transporting passengers using vehicles Vc. The vehicle dispatch server 20 includes a vehicle dispatch control device 21, a communication device 22, and a vehicle dispatch database (vehicle dispatch DB) 23.
[0022] The vehicle allocation control device 21 is a microcomputer (controller) mainly composed of a CPU, memory, and input / output interface. The vehicle allocation control device 21 can send and receive information between the reservation management server 10, the facility terminal 40, and the vehicle Vc via the communication device 22. The vehicle allocation control device 21 can also refer to information in the vehicle allocation DB 23. The vehicle allocation control device 21 executes the allocation of the vehicle Vc based on the vehicle allocation reservation confirmed by the reservation management server 10.
[0023] The communication device 22 communicates with the reservation management server 10, the facility terminal 40, and the vehicle Vc. The function of the communication device 22 is the same as that of the communication device 12. The vehicle dispatch DB 23 records vehicle dispatch reservations confirmed by the reservation management server 10.
[0024] The approver terminal 30 is a terminal linked to the approver Pa, and specifically, a terminal carried by the approver Pa. The approver terminal 30 is a communication terminal with communication functions, such as a smartphone, a mobile phone, a personal digital assistant (PDA), or a wearable device. The approver terminal 30 is a computer equipped with a CPU (Central Processing Unit), memory, a communication device, a storage device, an input device, a display device, and a speaker. The approver terminal 30 transmits vehicle reservation candidates created by the approver Pa to the reservation management server 10, and presents information transmitted from the reservation management server 10 to the approver Pa using either or both of the display device and the speaker. In this embodiment, information display using a display device is exemplified as a method for the approver terminal 30 to present information to the approver, but information output using a speaker may also be used.
[0025] The facility terminal 40 is installed in a pre-registered facility. Specifically, the facility terminal 40 is installed in a facility that the user Pb visits in the course of their daily life, such as a school, a cram school, or a library. A user Pb who does not have a communication terminal can use the facility terminal 40 to request a vehicle dispatch reservation.
[0026] The facility terminal 40 includes a terminal control device 41 , a communication device 42 , an input device 43 , a display device 44 , and a reading device 45 .
[0027] The terminal control device 41 is a microcomputer (controller) mainly composed of a CPU, memory, and input / output interface. The terminal control device 41 can send and receive information between the reservation management server 10, the vehicle dispatch server 20, the approver terminal 30, and the facility terminal 40 via the communication device 42. In this embodiment, the terminal control device 41 transmits the user identification information read by the reading device 45 and information necessary for vehicle dispatch reservations to the reservation management server 10. The terminal control device 41 also displays information sent from the reservation management server 10 on the display device 44.
[0028] The communication device 42 communicates between the reservation management server 10, the approver terminal 30, and the facility terminal 40. The communication device 42 has the same functions as the communication device 12. The input device 43 is a device through which the user Pb performs input operations, such as a touch panel integrated with the display device 44. The display device 44 is a device that displays information to the user Pb, such as an LCD display. The reading device 45 is a device that reads user identification information, such as a camera. The user Pb possesses an identification code such as a two-dimensional code. The identification code embodies user identification information, information for accessing the reservation management server 10, and the like. By reading the identification code, the reading device 45 can obtain the information embodied in the two-dimensional code. The information obtained by the reading device 45 is output to the terminal control device 41. The user identification information may be biometric information such as a fingerprint or iris. The facility terminal 40 may also obtain the user identification information from the user Pb using wireless technology such as short-range communication.
[0029] Next, a reservation management method according to this embodiment will be described.
[0030] A method in which the approver Pa registers vehicle reservation candidates in the reservation management server 10 will be described with reference to FIG.
[0031] First, when the approver Pa launches the browser on the approver terminal 30, the approver terminal 30 retrieves a web page provided by the reservation management server 10 and displays it on the display device. The approver Pa uses an input device to input vehicle reservation candidates into input fields provided on the web page. When registering a pre-reservation, the approver Pa inputs information such as the boarding time, boarding location, disembarking location, and number of people. On the other hand, when registering an authorized destination, the approver Pa inputs information about the disembarking location. When the approver Pa operates the input device to transmit information, the approver terminal 30 generates information that associates the input information with supervisor identification information and transmits the generated information to the reservation management server 10 as a vehicle reservation candidate (S1). When registering an event as an authorized destination, the approver Pa selects the displayed event information. When the approver Pa operates the input device to transmit the selected event information, the approver terminal 30 generates information that associates the selected event information with the supervisor identification information, and transmits the generated information to the reservation management server 10 as a vehicle dispatch reservation candidate (S1).
[0032] The reservation management control device 11 of the reservation management server 10 acquires information on vehicle reservation candidates from the approver terminal 30. The reservation management control device 11 records the information on vehicle reservation candidates in the vehicle reservation DB 13b (S2).
[0033] In this embodiment, a method of registering vehicle reservation candidates using a browser has been exemplified, but vehicle reservation candidates may also be registered using a dedicated application installed on the approver terminal 30.
[0034] 5, a method for user Pb to use vehicle Vc will be described. User Pb uses vehicle Vc of this service when traveling from a facility that user Pb has visited to another location. To use the service, user Pb has his / her identification code read by reader 45 of facility terminal 40.
[0035] When the reader 45 of the facility terminal 40 reads the identification code of user Pb, the terminal control device 41 acquires the user identification information from the reader 45 (S10). The terminal control device 41 starts a browser, acquires a web page provided by the reservation management server 10, and displays it on the display device 44. The terminal control device 41 transmits the user identification information to the reservation management server 10.
[0036] The reservation management control device 11 of the reservation management server 10 acquires information from the facility terminal 40. The reservation management control device 11 refers to the user DB 13a and determines whether the user Pb identified from the user identification information is a user Pb who requires approval from the approver Pa (S11). Specifically, the reservation management control device 11 searches the user DB 13a to determine whether the user identification information acquired from the facility terminal 40 is in the user DB 13a. If the user identification information acquired from the facility terminal 40 is in the user DB 13a, the reservation management control device 11 determines that the user Pb identified from the user identification information acquired from the facility terminal 40 is a user Pb who requires approval from the approver Pa (S11: Yes).
[0037] The reservation management control device 11 identifies the approver identification information associated with the user identification information in the user DB 13a. The reservation management control device 11 searches the vehicle reservation DB 13b based on the identified approver identification information and extracts vehicle reservation candidates registered with the approver identification information (S12). The reservation management control device 11 transmits information on the extracted vehicle reservation candidates to the facility terminal 40.
[0038] Upon receiving the information from the reservation management server 10, the terminal control device 41 of the facility terminal 40 displays a list of vehicle reservation candidates on the display device 44 (S13). The display device 44 displays a list of vehicle reservation candidates as shown in FIG. 3. The user Pb uses the input device 43 of the facility terminal 40 to select a desired vehicle reservation candidate from the list of vehicle reservation candidates. After this selection is made, the terminal control device 41 confirms the selected vehicle reservation candidate as the request content of the user Pb (S14). The terminal control device 41 then transmits information about the vehicle reservation candidate selected by the user Pb, as well as the user Pb's current location, i.e., the location of the facility terminal 40, and information about the current time, to the reservation management server 10 (S15). If the reservation management server 10 maintains a correspondence between the location of the facility terminal 40 and facility identification information that identifies the facility terminal 40, the terminal control device 41 may transmit the facility identification information instead of the location of the facility terminal 40.
[0039] After receiving the information from the facility terminal 40, the reservation management control device 11 of the reservation management server 10 determines whether the boarding location specified in the vehicle reservation candidate selected by the user Pb matches the location of the facility terminal 40 from which the user identification information was obtained (S16). For example, if two adjacent facilities each have a facility terminal 40, the user Pb may use the facility terminal 40 of the adjacent facility instead of the boarding location specified in the vehicle reservation candidate (the facility terminal 40 of one facility). Therefore, if the boarding location specified in the vehicle reservation candidate does not match the location of the facility terminal 40 from which the user identification information was obtained, the reservation management control device 11 changes the boarding location of the vehicle reservation to the location of the facility terminal 40 from which the user identification information was obtained (S17). However, the reservation management control device 11 may allow the boarding location to be changed on the condition that the distance from the boarding location specified in the vehicle reservation candidate to the location of the facility terminal 40 from which the user identification information was obtained is within a predetermined threshold distance.
[0040] If the type of vehicle reservation candidate selected by user Pb is an authorized destination, the vehicle reservation candidate does not specify a boarding location. In this case, the reservation management control device 11 regards the location of the facility terminal 40 from which the user identification information was acquired as the boarding location specified in the vehicle reservation candidate (S16: YES), and performs the processes from step S18 onwards.
[0041] The reservation management control device 11 confirms the boarding time (S18). If the type of the vehicle dispatch reservation candidate is an advance reservation, the vehicle dispatch reservation candidate also includes the boarding time. However, the time at which user Pb arrives at the facility terminal 40 may be earlier or later than the boarding time specified in the vehicle dispatch reservation candidate. Also, if the type of the vehicle dispatch reservation candidate is an allowed destination, the vehicle dispatch reservation candidate does not include the boarding time. Therefore, the reservation management control device 11 confirms the boarding time based on the time transmitted from the facility terminal 40. For example, the reservation management control device 11 confirms the time obtained by adding a predetermined time to the time transmitted from the facility terminal 40 as the boarding time for the vehicle dispatch reservation.
[0042] The reservation management control device 11 confirms the ride reservation including the boarding time, boarding location, disembarking location, and number of people (S19). If the ride reservation candidate selected by user Pb is a pre-reservation, the boarding time, boarding location, disembarking location, and number of people are confirmed according to the information specified in the ride reservation candidate. However, if the boarding location is changed, the new boarding location after the change, i.e., the location of the facility terminal 40 that obtained the user identification information, is confirmed as the ride location. On the other hand, if the ride reservation candidate selected by user Pb is an authorized destination, the location of the facility terminal 40 that obtained the user identification information is confirmed as the ride location. Similarly, if the boarding time is changed, the new boarding time after the change is confirmed as the boarding time. Note that, in the case of an authorized destination, information regarding the number of people may not be required, and user Pb may be prompted to input the information when selecting a ride reservation candidate.
[0043] The reservation management control device 11 notifies the approver terminal 30 that the vehicle dispatch reservation has been confirmed. Upon receiving this notification, the approver terminal 30 displays information that the vehicle dispatch reservation has been confirmed on its display device (S20). If one or both of the boarding location and boarding time specified in the vehicle dispatch reservation candidate registered by the approver Pa are changed, the reservation management control device 11 includes information that one or both of the boarding location and boarding time have been changed in the above-mentioned notification. As a result, information that one or both of the boarding location and boarding time have been changed is displayed on the display device of the approver terminal 30. Note that the reservation management control device 11 may also include information in the above-mentioned notification requesting the approver Pa to approve the change of the boarding location and boarding time. In this case, the reservation management control device 11 may confirm the vehicle dispatch reservation on the condition that it has obtained information indicating the approver Pa's approval from the approver terminal 30.
[0044] The reservation management control device 11 transmits information about the confirmed vehicle dispatch reservation to the vehicle dispatch server 20. At this time, the reservation management control device 11 may transmit information about the confirmed vehicle dispatch reservation to the facility terminal 40.
[0045] Upon receiving the vehicle dispatch reservation information from the reservation management server 10, the vehicle dispatch control device 21 of the vehicle dispatch server 20 dispatches the vehicle Vc based on the confirmed vehicle dispatch reservation (S21). As a result, a dispatch instruction based on the vehicle dispatch reservation is notified to the vehicle Vc. The vehicle dispatch control device 21 also notifies the facility terminal 40 of the dispatch result of the vehicle Vc. Upon receiving the notification from the vehicle dispatch server 20, the terminal control device 41 of the facility terminal 40 displays the dispatch result of the vehicle Vc on the display device 44 (S22).
[0046] As described above, in this embodiment, the reservation management control device 11 confirms the vehicle reservation based on the location of the facility terminal 40 from which the user identification information was acquired and the vehicle reservation candidates permitted by the approver Pa. According to this configuration, the location of the facility terminal 40 from which the user identification information was read is set as the boarding location for the vehicle reservation, so even if the user Pb does not have a communication terminal, it is possible to confirm that the user Pb is at the boarding location. Therefore, it is possible to dispatch a vehicle after confirming that the user is at the boarding location. Furthermore, since the vehicle reservation is confirmed based on the vehicle reservation candidates permitted by the approver Pa, the vehicle reservation is confirmed within the scope permitted by the approver Pa. This makes it possible to restrict vehicle reservations from being made at will by the user Pb, allowing the approver Pa to use the service with peace of mind.
[0047] In this embodiment, the reservation management control device 11 confirms the vehicle reservation based on the vehicle reservation candidate when the boarding location specified in the vehicle reservation candidate matches the location of the facility terminal 40 that acquired the user identification information. According to this configuration, the vehicle reservation is confirmed on the condition that the user Pb is at the boarding location, so the vehicle can be dispatched after confirming that the user is at the boarding location.
[0048] The user identification information is an identification code possessed by the user Pb or biometric information of the user Pb. With this configuration, the facility terminal 40 can easily obtain the user identification information.
[0049] In this embodiment, when a vehicle dispatch reservation is confirmed, the reservation management control device 11 notifies the approver terminal 30 of the confirmation of the reservation. With this configuration, the approver Pa can know that the vehicle dispatch reservation used by the user Pb has been confirmed.
[0050] In this embodiment, when a vehicle dispatch reservation is confirmed, the reservation management control device 11 notifies the approver terminal 30 of the time when the vehicle dispatch reservation is confirmed. With this configuration, the approver Pa can know the time when the vehicle dispatch reservation used by the user Pb is confirmed.
[0051] When the reservation management control device 11 determines that the boarding time specified in the vehicle reservation candidate needs to be changed, it changes the boarding time to the new boarding time and confirms the vehicle reservation. Depending on the behavior of user Pb, the boarding time specified in the vehicle reservation candidate may differ significantly from the time when user Pb arrives at the facility terminal 40. In this case, the reservation management control device 11 can change the boarding time specified in the vehicle reservation candidate to the new boarding time and confirm the vehicle reservation. This can prevent inconveniences such as having to wait a long time for vehicle Vc or not being able to make a vehicle reservation because the boarding time is later than the boarding time specified in the vehicle reservation candidate.
[0052] The reservation management control device 11 notifies the approver terminal 30 of the change in boarding time. With this configuration, the approver Pa can know that the boarding time of the vehicle reservation candidate registered by the approver Pa has been changed.
[0053] If the boarding location specified in the vehicle dispatch reservation candidate differs from the location of the facility terminal 40 from which the user identification information was obtained, the reservation management control device 11 changes the boarding location to the location of the facility terminal 40 from which the user identification information was obtained and confirms the vehicle dispatch reservation. For example, if nearby facilities each have a facility terminal 40, user Pb may end up using the facility terminal 40 of one facility instead of the boarding location specified in the vehicle dispatch reservation candidate (the facility terminal 40 of one facility). With the above configuration, the boarding location can be flexibly changed, making it possible to provide a service that is easy for user Pb to use. Even in this case, the vehicle dispatch reservation is confirmed on the condition that user Pb is present at the boarding location, so a vehicle can be dispatched only after confirming that the user is present at the boarding location.
[0054] The reservation management control device 11 notifies the approver terminal 30 of the change in boarding location. With this configuration, the approver Pa can know that the boarding location of the vehicle reservation candidate registered by the approver Pa has been changed.
[0055] The present invention is not limited to the reservation management server (reservation management device) described above, but also includes the vehicle reservation method described in this embodiment. In this vehicle reservation method, a vehicle reservation is confirmed based on the location of the facility terminal 40 that acquired the user identification information and the vehicle reservation candidates authorized by the approver Pa. According to this method, by using the location of the facility terminal 40 that reads the user identification information as the boarding location, it is possible to confirm that the user Pb is present at the boarding location even if the user Pb does not have a communication terminal. Since the vehicle reservation is confirmed on the condition that the user Pb is present at the boarding location, a vehicle can be dispatched after confirming that the user is present at the boarding location. Furthermore, since the vehicle reservation is confirmed based on the vehicle reservation candidates authorized by the approver Pa, the vehicle reservation is confirmed within the scope permitted by the approver Pa. This makes it possible to restrict vehicle reservations from being made at will by the user Pb, allowing the approver Pa to use the service with peace of mind.
[0056] Although the embodiments of the present invention have been described above, the descriptions and drawings that form part of this disclosure should not be understood to limit the present invention. Various alternative embodiments, examples, and operating techniques will become apparent to those skilled in the art from this disclosure.
[0057] 1: Vehicle dispatch service system, 10: Reservation management server (reservation management device), 11: Reservation management control device (controller), 12: Communication device, 13: Reservation management database, 20: Vehicle dispatch server, 30: Approver terminal, 40: Facility terminal
Claims
1. A reservation management device that manages vehicle reservations used by users, comprising: a communication device that communicates with a facility terminal installed at a pre-registered facility that is capable of acquiring identification information that identifies the user; a storage device that includes: a user database in which the user and an approver who approves the user are registered in association with each other; and a reservation database in which vehicle reservation candidates that the approver has permitted the user to use are registered; and a controller, wherein the controller acquires the identification information from the facility terminal, and if the user identified from the identification information acquired from the facility terminal is a user who requires approval from the approver, the reservation management device confirms the vehicle reservation based on the location of the facility terminal that acquired the user's identification information and the vehicle reservation candidates approved by the approver.
2. The reservation management device of claim 1, wherein the controller confirms a vehicle reservation based on the vehicle reservation candidate when the boarding location specified in the vehicle reservation candidate matches the location of the facility terminal that obtained the user's identification information.
3. The reservation management device according to claim 1 or 2, wherein the identification information is an identification code possessed by the user or biometric information of the user.
4. A reservation management device according to any one of claims 1 to 3, wherein when the vehicle dispatch reservation is confirmed, the controller notifies the approver terminal linked to the approver of the reservation confirmation.
5. The reservation management device according to claim 4, wherein, when the vehicle dispatch reservation is confirmed, the controller notifies the approver terminal of the time when the vehicle dispatch reservation is confirmed.
6. A reservation management device as claimed in any one of claims 1 to 3, wherein, when the controller determines that a change in the boarding time specified in the vehicle dispatch reservation candidate is necessary, the controller changes the boarding time to a new time and confirms the vehicle dispatch reservation.
7. The reservation management device according to claim 6, wherein the controller notifies an approver terminal linked to the approver of the change in boarding time.
8. A reservation management device as described in claim 1, wherein, if the boarding location specified in the vehicle reservation candidate differs from the location of the facility terminal that obtained the user's identification information, the controller changes the boarding location to the location of the facility terminal that obtained the user's identification information and confirms the vehicle reservation.
9. The reservation management device according to claim 8, wherein the controller notifies an approver terminal linked to the approver of the change in boarding location.
10. A reservation management method executed by a controller that manages vehicle reservations for use by a user, comprising: accepting vehicle reservation candidates that an approver who approves the user has permitted the user to use; acquiring identification information that identifies the user from a facility terminal installed in a pre-registered facility; and, if the user identified from the identification information acquired from the facility terminal is a user who requires approval from the approver, confirming the vehicle reservation based on the location of the facility terminal that acquired the user's identification information and the vehicle reservation candidates approved by the approver.
Citation Information
Patent Citations
Vehicle authentication method and vehicle authentication device
JP2021018762A
Taxi call system
JP2023025405A
Method and apparatus for transportation wireless authorization
US20190164247A1
Systems and Methods for Mobile Dental Care
US20220130530A1