JP2019212118A - System, method, and program for managing vehicle dispatch - Google Patents

Abstract

To improve convenience of a user at a time of a dispatch request.SOLUTION: A dispatch management server 10 according to one embodiment of the present invention provides a dispatch management service for managing a dispatch of vehicle such as a taxi. The dispatch management server 10 automatically determines a boarding position of a user based on a current position of the user accompanying the dispatch request, and automatically selects a vehicle to be dispatched to the user based on the current position of the user and vehicle information of each vehicle; and since the dispatch management server requests the selected vehicle to pick up the vehicle at the determined boarding position, the user can make a dispatch request without specifying the boarding position and the vehicle type.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a system, a method, and a program for managing vehicle allocation.

  Conventionally, a system for managing allocation of vehicles such as taxis has been proposed (see, for example, Patent Document 1 below). In such a system, when a user makes a vehicle allocation request with designation of a boarding position (a pickup position), an empty vehicle traveling in an area near the designated boarding position is searched and allocated. Further, typically, the user can also search for a vehicle to be dispatched by specifying a condition (vehicle type or the like) related to the vehicle.

JP-A-2018-49408

  However, in the conventional system, it is necessary to specify the boarding position, the vehicle type, and the like at the time of the vehicle allocation request, and there may be a user who feels this troublesome. In particular, when a vehicle allocation request is made at a place visited for the first time, it is difficult for the user to specify an appropriate boarding position. Thus, the conventional system for managing vehicle allocation has room for improvement in the convenience of the user when requesting vehicle allocation.

  An embodiment of the present invention has an object of improving the convenience of a user when a vehicle is requested. Other objects of the embodiments of the present invention will become apparent by referring to the entire specification.

  A system according to an embodiment of the present invention is a system for managing vehicle allocation, and includes a storage device that stores at least vehicle information of each of a plurality of vehicles, and one or more computer processors. The one or more computer processors determine a boarding position of the user based on at least a process of accepting a vehicle allocation request with the current position of the user and the current position of the user in response to execution of a readable instruction. A process for selecting a vehicle to be assigned to the user from among the plurality of vehicles based on at least the current position of the user and vehicle information of each of the plurality of vehicles, and the selected vehicle And a process of requesting a pick-up at the determined boarding position.

  A method according to an embodiment of the present invention is a method for managing vehicle allocation, which is executed by one or more computers accessible to a storage device that stores at least vehicle information of each of a plurality of vehicles. Receiving a dispatch request with the current position of the user; determining the boarding position of the user based on at least the current position of the user; and the current position of the user and each of the plurality of vehicles Selecting a vehicle to be assigned to the user from the plurality of vehicles based on at least vehicle information; and requesting the selected vehicle to pick up at the boarding position determined.

  A program according to an embodiment of the present invention is a program for managing vehicle allocation, on one or more computers accessible to a storage device that stores at least vehicle information of each of a plurality of vehicles. In response to execution, the one or more computers receive a dispatch request with the current position of the user, a process of determining the boarding position of the user based on at least the current position of the user, A process of selecting a vehicle to be assigned to the user from among the plurality of vehicles based on at least the current position and vehicle information of each of the plurality of vehicles, and an arrival at the boarding position determined for the selected vehicle And processing for requesting.

  Various embodiments of the present invention improve user convenience when requesting a vehicle assignment.

The block diagram which shows schematically the structure of the network containing the vehicle allocation management server 10 which concerns on one Embodiment of this invention. The block diagram which shows the function of the dispatch management server 10 roughly. The figure which illustrates the information managed in the user information table 411. The figure which illustrates the information managed in the vehicle information table 412. The figure which illustrates the information managed in the dispatch request information table 413. The figure which illustrates the top screen 501. The flowchart which illustrates the process which the dispatch management server 10 performs. The figure which illustrates screen 502 during arrangement. The figure which illustrates the vehicle arrival request confirmation screen 100. The figure which illustrates the vehicle waiting screen 503. The figure which illustrates screen 110 during an incoming vehicle. The figure which illustrates the arrival report screen. The figure which illustrates boarding report screen. The figure which illustrates the vehicle waiting screen 503. The figure which illustrates the vehicle waiting screen 503. The figure which illustrates condition specification screen 504. The flowchart which illustrates the process which the dispatch management server 10 performs.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a configuration diagram schematically showing a configuration of a network including a vehicle allocation management server 10 according to an embodiment of the present invention. As illustrated, the server 10 is communicably connected to a user terminal 32 and a driver terminal 34 via a communication network 20 such as the Internet. In FIG. 1, only one user terminal 32 and driver terminal 34 are shown, but the server 10 is connected to a plurality of user terminals 32 and driver terminals 34 so as to communicate with each other. The server 10 provides a dispatch management service that manages the dispatch of vehicles such as taxis. The vehicle allocation management server 10 is an example of a device that implements all or part of the system of the present invention.

  The vehicle allocation management server 10 is configured as a general computer, and as shown in FIG. 1, a computer processor 11 configured as a CPU or GPU, a main memory 12, an input / output I / F 13, and a communication I / F 14 and a storage (storage device) 15, and these components are electrically connected via a bus or the like (not shown).

  The computer processor 11 reads various programs stored in the storage 15 or the like into the main memory 12 and executes various instructions included in the programs. The main memory 12 is configured by, for example, a DRAM.

  The input / output I / F 13 is various input / output devices for exchanging information with a user or the like. The input / output I / F 13 includes, for example, an information input device such as a keyboard and a pointing device (for example, a mouse and a touch panel), a voice input device such as a microphone, and an image input device such as a camera. The input / output I / F 13 includes an image output device (display device) such as a display and an audio output device such as a speaker.

  The communication I / F 14 is implemented as hardware such as a network adapter, various types of communication software, and combinations thereof, and is configured to realize wired or wireless communication via the communication network 20 or the like.

  The storage 15 is configured by, for example, a magnetic disk or a flash memory. The storage 15 stores various programs including an operating system, various data, and the like.

  In the present embodiment, the server 10 may be configured using a plurality of computers each having the hardware configuration described above. For example, the server 10 can be configured by a plurality of server devices.

  The user terminal 32 and the driver terminal 34 have a configuration as a general computer, and are configured as, for example, a smartphone, a tablet terminal, a personal computer, and a wearable device. The user terminal 32 is operated by a user who uses a vehicle such as a taxi. The driver terminal 34 is operated by a vehicle driver.

  In the present embodiment, the vehicle allocation management server 10 can be configured to have functions as a web server and an application server. In this case, the web browser or other application (for example, the user terminal 32 or the driver terminal 34) (for example, Various processes are executed in response to a request from the application for the dispatch management service), and screen data (for example, HTML data) and control data corresponding to the result of the process are transmitted. On the user terminal 32 and the driver terminal 34, a web page or other screen based on the received data is displayed.

  Next, the function which the vehicle allocation management server 10 of this embodiment has is demonstrated. FIG. 2 is a block diagram schematically showing the functions of the server 10. As illustrated, the server 10 includes an information storage management unit 41 that stores and manages information, a basic function control unit 42 that controls basic functions of the vehicle allocation management service, and a vehicle allocation request management unit that manages vehicle allocation requests from users. 43 and an incoming vehicle request management unit 44 that manages incoming vehicle requests for vehicles. These functions are realized by the cooperation of hardware such as the computer processor 11 and the main memory 12 and various programs and data stored in the storage 15, for example, in the main memory 12. This is realized by the computer processor 11 executing instructions included in the read program. 2 may be realized by the cooperation of the vehicle allocation management server 10 and the user terminal 32 or the driver terminal 34, or may be realized by the user terminal 32 or the driver terminal 34. .

  The information storage management unit 41 of the server 10 includes a storage 15 and the like, and stores and manages various information. For example, as illustrated in FIG. 2, the information storage management unit 41 manages a user information table 411 that manages information related to a user of a vehicle allocation management service, and a vehicle information table that manages information related to a vehicle to be allocated in the vehicle allocation management service. 412, a vehicle allocation request information table 413 for managing information related to a vehicle allocation request from a user, and road map data 415.

  The basic function control unit 42 of the server 10 executes various processes related to the control of the basic function of the dispatch management service. For example, the basic function control unit 42 transmits HTML data or control data of various screens related to the basic function to the user terminal 32 or the driver terminal 34, and the user through the screen displayed on the user terminal 32 or the driver terminal 34. Alternatively, various processing is executed in response to an operation input by the driver, and HTML data or control data corresponding to the result of the processing is transmitted to the user terminal 32 or the driver terminal 34. Basic functions controlled by the basic function control unit 42 include, for example, login processing (user authentication), payment processing, user management (for example, update of the user information table 411), and vehicle management (for example, vehicle Update of the information table 412) and the like.

  The vehicle allocation request management unit 43 of the server 10 executes various processes related to management of vehicle allocation requests from users. In the present embodiment, the vehicle allocation request management unit 43 is configured to receive a vehicle allocation request from a user, and the vehicle allocation request is accompanied by the current position of the user. For example, the vehicle allocation request management unit 43 is configured to receive a vehicle allocation request by the user that is performed via a screen displayed on the user terminal 32. When receiving the vehicle allocation request, the vehicle allocation request management unit 43 receives the location information of the user terminal 32. , Configured to be acquired from the user terminal 32.

  The vehicle allocation request management unit 43 is configured to determine the user's boarding position (receiving position) based at least on the current position of the user. Similarly, the vehicle allocation request management unit 43 selects a vehicle to be allocated to the user from the plurality of vehicles based on at least the current position of the user and the vehicle information of each of the plurality of vehicles to be allocated. It is configured. The vehicle information of each vehicle is managed in the vehicle information table 412, for example.

  The incoming vehicle request management unit 44 of the server 10 executes various processes related to incoming vehicle requests for vehicles. In this embodiment, the incoming vehicle request management unit 44 is configured to request an incoming vehicle to the determined boarding position with respect to the vehicle selected as the vehicle to be assigned to the user. For example, the incoming vehicle request management unit 44 is configured to transmit information for requesting an incoming vehicle to the driver terminal 34 of the driver corresponding to the selected vehicle, and the information includes at least the boarding position of the user. . The correspondence relationship between the vehicle and the driver terminal 34 (driver) is managed, for example, in the vehicle information table 412.

  As described above, the vehicle allocation management server 10 according to the present embodiment automatically determines the user's boarding position based on the user's current position accompanying the vehicle allocation request, and also the user's current position and vehicle information of each vehicle. The vehicle to be assigned to the user is automatically selected based on the request, and the selected vehicle is requested to pick up at the determined boarding position. Therefore, the user can dispatch the vehicle without specifying the boarding position and the vehicle type. Requests can be made. That is, the vehicle allocation management server 10 according to the present embodiment improves user convenience when making a vehicle allocation request.

  In the present embodiment, the vehicle allocation request management unit 43 may be configured to change the content of vehicle allocation in response to a request from the user after requesting an incoming vehicle for the selected vehicle. In this case, the incoming vehicle request management unit 44 is configured to notify the changed vehicle allocation details to the vehicle that requested the incoming vehicle. The change in the contents of dispatch can include, but is not limited to, changing the boarding position and setting (and changing) the getting-off position (destination). Such a configuration allows the user to simply make a vehicle allocation request, and then change the vehicle allocation details (for example, change the boarding position, set the getting-off position, etc.) as necessary.

  In the present embodiment, the determination of the user's boarding position can be performed by applying various rules based on the current position of the user. For example, the vehicle allocation request management unit 43 is configured to determine the user's boarding position so as to avoid a non-recommended stop position that is not recommended as a boarding position although the vehicle can be stopped. The non-recommended stop position includes, for example, a road with a guardrail, a taxi stand (because troubles such as erroneous boarding by other users may occur), and the like, and can be managed in the road map data 415. Such a configuration prevents a stop position that is not appropriate as the user's boarding position from being determined as the boarding position.

  In addition, for example, the vehicle allocation request management unit 43 can stop a vehicle that is within a predetermined range based on the user's current position (for example, within a predetermined distance from the user's current position). The recommended stop position recommended as the position may be determined as the boarding position of the user. Such a recommended stop position can be set by, for example, an operator of a vehicle allocation management service and managed in the road map data 415. Such a configuration encourages the stop position recommended as the boarding position for the user to be determined as the boarding position.

  For example, the vehicle allocation request management unit 43 may be configured to determine the boarding position of the user based on at least the attribute information of the user in addition to the current position of the user. User attribute information can be managed in the user information table 411. The user attribute information includes, for example, whether or not a wheelchair is used. In this case, the vehicle allocation request management unit 43 provides a boarding position suitable for riding in a state where the wheelchair is used to the user who uses the wheelchair. Configured to determine. A boarding position suitable for boarding with a wheelchair is used, for example, in the road map data 415. Such a configuration supports the determination of the boarding position suitable for the user's attribute information.

  In the present embodiment, selection of a vehicle to be assigned to a user can be performed by applying various rules based on the current position of the user and vehicle information. The vehicle information includes, for example, the current position of the vehicle and the vehicle allocation state (empty vehicle etc.). In this case, the vehicle allocation request management unit 43 gives priority to an empty vehicle near the user's current location. May be configured to select a vehicle to be assigned to.

  In addition to the current position of the user, the vehicle allocation request management unit 43 can be configured to select a vehicle to be assigned to the user based on at least the attribute information of the user. For example, the vehicle allocation request management unit 43 is configured to assign a vehicle that can be boarded and exited in a state where the wheelchair is used to a user who uses the wheelchair. Whether the vehicle is capable of getting on and off in a state where a wheelchair is used can be managed in the vehicle information table 412 as a part of the vehicle information. Such a configuration supports selection of a vehicle that matches the user's attribute information.

  Next, a specific example of the vehicle allocation management server 10 of this embodiment having such a function will be described. In this specific example, the vehicle allocation management server 10 provides a vehicle allocation management service for taxis of a plurality of taxi companies. In the present embodiment, the vehicle subject to vehicle allocation management is not limited to a taxi of a taxi company, and may include a private car for a general public.

  FIG. 3 illustrates information managed in the user information table 411 in this example. The user information table 411 manages information related to the user of the vehicle allocation management service, and as shown in the figure, the user information table 411 is associated with a “user account” for identifying an individual user, such as “user basic information”, “wheelchair use flag”, Manage information. The basic user information includes, for example, name, contact information, payment information (credit card information, etc.) and the like. The wheelchair use flag indicates whether or not the wheelchair is used.

  FIG. 4 illustrates information managed in the vehicle information table 412 in this example. The vehicle information table 412 manages information related to each of a plurality of vehicles that are targets of the vehicle allocation management service, and is associated with a “vehicle ID” that identifies individual vehicles, as shown in the drawing, Information such as “taxi company information”, “UD taxi flag”, “facility X entrance permission flag”, “current position”, “allocation status”, “driver account” for identifying the corresponding driver is managed. The basic vehicle information includes the vehicle type, the number of people who can board the vehicle, an image (photograph or drawing) corresponding to the appearance of the vehicle, and a number. The UD taxi flag indicates whether the UD taxi is designed for use by a wheelchair user, an elderly person, or the like. The facility X entrance permission flag indicates whether or not the facility X is permitted to enter the specific facility X. The facility X includes, for example, various factories and military facilities. As the current position, position information transmitted from the information terminal or driver terminal 34 mounted on the vehicle is set. A value corresponding to each state including “rental”, “receiving vehicle”, and “empty vehicle” is set as the dispatch state.

  FIG. 5 illustrates information managed in the dispatch request information table 413 in this example. The vehicle allocation request information table 413 manages information related to the vehicle allocation request from the user, and identifies the user who made the vehicle allocation request in association with the “vehicle allocation request ID” that identifies an individual vehicle allocation request, as shown in FIG. Information such as “user account”, “boarding position”, “getting off position”, “payment method”, “vehicle ID” for identifying the assigned vehicle is managed.

  FIG. 6 illustrates a top screen 501 displayed on the user terminal 32 of the user who uses the vehicle allocation management service of this example. As shown in the figure, the top screen 501 has a map display area 52 and an information display area 54 located below the area 52.

  In the initial state, the map display area 52 displays a map of a predetermined range centered on the current position of the user (user terminal 32) at a predetermined scale, and a user object UO corresponding to the user is arranged on the map. Yes. Further, the map display area 52 is a vehicle corresponding to a vehicle that is subject to the vehicle allocation management service (that is, a vehicle managed in the vehicle information table 412) within the range of the displayed map. An object VO is arranged on the map. The display positions of the user object UO and the vehicle object VO change (move) as the user or the vehicle moves.

  The map display area 52 is configured such that the range of the displayed map slides by a slide operation or the like by the user. As the displayed map range slides, the display positions of the user object UO and the vehicle object VO also change.

  The information display area 54 displays an indication of the waiting time at the current time when the user makes a vehicle allocation request (“5 to 8 minutes” in the example of FIG. 6) and “call a taxi with one tap”. A first button 61 and a second button 62 displayed as “Call a taxi by specifying conditions”. The standard of the waiting time is calculated based on, for example, the distance between each of a predetermined number (for example, three) of empty vehicles and the user in order of increasing distance from the current position of the user.

  The first button 61 is a button for making a dispatch request without specifying a condition (with one tap), and the second button 62 is a button for making a dispatch request by specifying a condition. First, a case where a vehicle allocation request is made without specifying conditions will be described.

  FIG. 7 is a flowchart illustrating a process executed by the vehicle allocation management server 10 in response to the selection of the first button 61 by the user. First, as shown in the figure, the server 10 determines the user's boarding position (receiving position) based on the current position of the user (step S100). The determined boarding position is registered in the dispatch request table 413.

  The determination of the boarding position based on the current position of the user can be realized by applying various rules. In this example, when there is a recommended stop position that can be stopped and recommended as a boarding position within a predetermined distance range from the current position of the user, the recommended stop position (of a predetermined distance) If there are a plurality of recommended stop positions within the range, the recommended stop position closest to the user's current position is determined as the user's boarding position. Such a recommended stop position is set in advance by, for example, an operator of a vehicle allocation management service and registered in the road map data 415. For example, in the vehicle allocation management service, the operating company can set a position that has been individually specified as a boarding position by many users in the past as a recommended stop position. Such a recommended stop position can be said to be a taxi stand virtually provided in the dispatch management service of this example.

  Further, in this example, when there is no recommended stop position within a predetermined distance from the user's current position, the stop position where the vehicle can stop is the closest stop position from the user's current position. Is determined as the user's boarding position. At this time, the boarding position is determined so as to avoid a position predetermined as a non-recommended stop position that is not appropriate as the boarding position. Such a non-recommended stop position is preset by, for example, an operator of a vehicle allocation management service and registered in the road map data 415. For example, the operator can set a road with a guardrail, a taxi stand, and the like as a non-recommended stop position. In another example of the present embodiment, the non-recommended stop position is automatically set based on information acquired from an external system or the like. For example, the non-recommended stop position can be automatically set based on road construction schedule or traffic regulation information acquired from an external system or the like.

  When the user's boarding position is thus determined, the server 10 next selects a vehicle to be assigned to the user based on the user's current position, wheelchair use flag (attribute information), and vehicle information of each vehicle (step). S110).

  In this example, basically, an empty vehicle closest to the current position of the user is assigned to the user, but in the following cases, vehicles to be assigned are restricted. First, when the user is a user who uses a wheelchair (identified by referring to a wheelchair use flag in the user information table 411), the vehicle to be assigned is a UD taxi vehicle (a UD taxi in the vehicle information table 412). Specified by referring to the flag). Further, when the current position of the user is within the site of the facility X, the vehicle to be assigned is identified by referring to a vehicle having an entrance permission for the facility X (referring to the facility X entrance permission flag in the vehicle information table 412). Restricted).

  Here, when the vehicles to be allocated are restricted, the target vehicle (for example, a vehicle of a UD taxi or a vehicle having permission to enter the facility X) has a predetermined distance from the current position of the user. If the user does not exist within the range, the user may be managed as a vehicle waiting state (automatically or through confirmation by the user). When the user enters a waiting state for dispatching, the server 10 waits for the target vehicle, and assigns the target vehicle when the target vehicle falls within a predetermined distance from the current position of the user. Further, when there is no vehicle having permission to enter the facility X within a predetermined distance from the user's current position, the user's boarding position is set outside the facility X (automatically or by user confirmation). Change) and assign a vehicle that does not have permission to enter the facility X. In this case, for example, the reason why the user's boarding position cannot be set in the site of the facility X (reason for dispatching, for example, “cannot arrange a vehicle that can handle this area”, etc.) is displayed. It is preferable to display an area where the position cannot be set (specifically, within the site of the facility X) so as to be visible (for example, display as a semi-transparent specific color (for example, red) area).

  When the vehicle to be assigned to the user is thus selected, the server 10 next requests the selected vehicle to pick up the vehicle (step S120). FIG. 8 illustrates an arrangement screen 502 displayed on the user terminal 32 in response to a request for an incoming vehicle for the selected vehicle. The in-order screen 502 includes a map display area 52 and an information display area 54, similar to the top screen 501. As shown in the figure, in the map display area 52 of the ordering screen 502, the character string “I am arranging a taxi” is displayed superimposed on the map, and the pin-shaped display indicating “Get here” is displayed. A boarding position designation object 521 is arranged on the map. The said boarding position designation | designated object 521 is arrange | positioned in the position on the map corresponding to the determined boarding position. In the boarding position designation object 521, the traveling direction of the vehicle at the boarding position may be displayed with an arrow or the like.

  The information display area 54 of the in-order screen 502 includes a cancel button 63 for displaying a guideline for the waiting time at the present time and canceling the incoming vehicle request. The user selects the cancel button 63 when, for example, the selection operation for the first button 61 on the top screen 501 is mistakenly performed. In response to the selection of the button 63, the server 10 performs a predetermined canceling process for canceling the pick-up request.

  FIG. 9 exemplifies the incoming vehicle request confirmation screen 100 displayed on the driver terminal 34 of the driver corresponding to the vehicle that has received the incoming vehicle request. The driver corresponding to the vehicle is specified by the driver account in the vehicle information table 412. As shown in the figure, a first button 102 that displays “OK” and a second button 104 that displays “Cancel” are arranged side by side in the up-and-down direction. The driver selects the first button 102 when accepting the request for an incoming car, and selects the second button 104 when not accepting (denied) the incoming car request.

  Further, the arrival request confirmation screen 100 is configured such that if the first button 102 is not selected within 10 seconds after the display, the second button 104 is automatically selected (that is, the request for the arrival is rejected). Has been. At the lower end of the first button 102, a circular object 1021 that counts down the 10 seconds is arranged. In this way, the driver can reject the request for an incoming vehicle by leaving it for 10 seconds instead of selecting the second button 104.

  When the first button 102 on the incoming vehicle request confirmation screen 100 is selected by the driver and the incoming vehicle request is accepted (YES in step S130), the allocation of vehicles to the user is confirmed (step S140). In response to the confirmation of the vehicle assignment, the server 10 registers the corresponding vehicle ID in the vehicle allocation request information table 413 and changes the vehicle allocation state in the vehicle information table 412 of the corresponding vehicle to “arrival vehicle”. On the other hand, when the second button 104 on the incoming request confirmation screen 100 is selected by the driver and the incoming request is rejected (NO in step S130), the server 10 again selects the vehicle to be assigned (step S110).

  FIG. 10 exemplifies a waiting-for-arrival screen 503 displayed on the user terminal 32 in response to the confirmation of vehicle assignment (acceptance of an incoming request by the driver). The waiting-for-arrival screen 503 has a map display area 52 and an information display area 54, similarly to the top screen 501 and the arranging screen 502. As shown in the figure, the information display area 54 of the waiting-for-arrival screen 503 displays a guideline for the waiting time at the present time, and information related to the assigned vehicle (vehicle image (photograph or figure), and related vehicle). Other information (for example, taxi company name, vehicle number, etc.) is displayed, a first button 64 displaying “Destination setting”, and a second button 65 displaying “Message” Have

  The first button 64 is a button for the user to set / change the destination (alighting position). The second button 65 is a button for the user to chat with the driver of the assigned vehicle. In response to the selection of the second button 65, a chat screen is displayed. As described above, in this example, the text chat between the user and the driver becomes possible according to the confirmation of the allocation of the vehicle.

  FIG. 11 exemplifies the on-arrival screen 110 displayed on the driver terminal 34 in response to the confirmation of the vehicle assignment. As shown in the figure, the on-arrival screen 110 has a map display area 112, a first button 114 displayed as “arrival”, and a second button 116 displayed as “message”.

  The map display area 112 displays a map whose scale is adjusted to include the range from the driver's vehicle to the boarding position. In the map display area 112, a driver vehicle object DO corresponding to the driver's vehicle and a boarding position object PO corresponding to the boarding position are arranged on the map. In the map display area 112, the scale of the map (the range of the displayed map) changes (enlarges) as the vehicle approaches the boarding position. In addition, a navigation start button 1122 displayed as “navigation” is arranged in the upper right corner of the map display area 112. When the button 1122 is selected by the driver, a general navigation function with the boarding position as the destination is started.

  The first button 114 is a button for the driver to report arrival at the boarding position. The second button 116 is a button for the driver to chat with the user. In response to the selection of the second button 116, a chat screen is displayed.

  When the first button 114 is selected by the driver, an arrival report screen 120 illustrated in FIG. 12 is displayed on the driver terminal 34. Note that the arrival report screen 120 may be displayed automatically (without selection of the arrival button 114) when the position of the driver's vehicle falls within a predetermined range from the boarding position.

  On the arrival report screen 120, as shown in the figure, a first button 122 displayed as "arrival at the destination" and a second button 124 displayed as "Cancel" are arranged in the vertical direction. When the first button 122 is selected by the driver, arrival at the destination (boarding position) is reported to the server 10. In response to the report of arrival at the boarding position, the server 10 transmits a predetermined message to the user terminal 32. The user can know the arrival of the vehicle via the predetermined message. In addition, the driver can perform necessary communication from the arrival at the boarding position until the user gets on through the text chat described above.

  FIG. 13 illustrates a boarding report screen 130 displayed on the driver terminal 34 in response to the selection of the first button 122. On the boarding report screen 130, as shown in the figure, a first button 132 displayed as “boarding completed” and a second button 134 displayed as “cancel” are arranged in the vertical direction. When the first button 132 is selected by the driver, the user's boarding is reported to the server 10. When receiving the report, the server 10 changes the dispatch state in the vehicle information table 412 of the corresponding vehicle to “rental”.

  Here, in this example, the user can change the boarding position determined after selecting the first button 61 on the top screen 501 and making a vehicle allocation request. Specifically, by changing the position of the boarding position designation object 521 on the map via the map display area 52 of the ordering screen 502 illustrated in FIG. 8 or the waiting-for-arrival screen 503 illustrated in FIG. The position can be changed. For example, the position of the object 521 is changed by a slide operation on the boarding position designation object 521.

  FIG. 14 illustrates a waiting-for-arrival screen 503 when the position of the boarding position designation object 521 on the map is changed. As shown in the drawing, a confirmation object 56 for confirming whether or not the boarding position needs to be changed is displayed on the map display area 52 in accordance with the change of the boarding position designation object 521 on the map. The confirmation object 56 includes a first button 561 displaying “Yes” and a second button 562 displaying “No”. When the first button 561 is selected, the change in the boarding position is confirmed, the boarding position after the change is transmitted to the corresponding driver terminal 34, and the boarding position in the dispatch request information table 413 is updated. In addition, when the position of the vehicle heading to the boarding position before the change is within a predetermined distance from the boarding position, the change of the boarding position may be prohibited (impossible). . Further, an upper limit may be set for a range in which the boarding position can be changed (a distance between the boarding position before the change and the boarding position after the change).

  In this example, the boarding position designation object 521 is configured so that it cannot be placed in the map display area 52 at a position corresponding to the above-described non-recommended stop position. FIG. 15 illustrates a waiting-for-arrival screen 503 in a state where a change in the position of the boarding position designation object 521 (for example, a slide operation) is started. As illustrated, in the map display area 52, an area A1 corresponding to the non-recommended stop position is displayed so as to be visible in accordance with the start of the change of the position of the boarding position designation object 521 (for example, a semitransparent specific Color (for example, displayed as a red region). The user can know the existence of the non-recommended stop position by the area A1. In addition, in the said area | region A1, you may make it display the reason (For example, "it cannot dispatch because it is a taxi stand vicinity" etc.) set as a non-recommended stop position. In addition to the area A1 corresponding to the non-recommended stop position, in addition to the area A1 corresponding to the non-recommended stop position, the above-described area corresponding to the recommended stop position is displayed so as to be visible (for example, translucent) It is also possible to guide to another recommended stop position in such a manner that it is displayed as a specific color (for example, blue) area different from the area corresponding to the non-recommended stop position.

  In this way, in this example, the user can make a taxi dispatch request with a simple one-tap operation of selecting the first button 61 on the top screen 501. ) And during the waiting period for arrival, it is possible to change the boarding position and set the destination.

  In the foregoing, the case where a vehicle dispatch request is made without specifying conditions has been described. Next, a case where a vehicle allocation request is made by specifying conditions will be described. FIG. 16 illustrates a condition designation screen 504 displayed on the user terminal 32 in response to the selection of the second button 62 on the top screen 501. The condition designation screen 504 has a map display area 52 and an information display area 54, as with the top screen 501, the ordering screen 502, and the waiting-for-arrival screen 503.

  A boarding position designation object 521 is arranged in the map display area 52 of the condition designation screen 504. The user can individually specify the boarding position by changing the position of the object 521. Note that the map display area 52 of the condition designation screen 504 is not recommended when the position change of the boarding position designation object 521 is started, like the map display area 52 of the arrangement screen 502 and the waiting-for-arrival screen 503 described above. An area corresponding to the position is displayed so as to be visible, and the object 521 is configured not to be placed at the non-recommended stop position.

  The information display area 54 of the condition designation screen 504 displays an indication of the waiting time at the present time, a first button 66 for setting a destination, a second button 67 for selecting a payment method, and a vehicle type. A third button 68 for designating and a fourth button 69 displaying “Request”.

  When the first button 66 is selected by the user, a screen for setting a destination (alighting position) is displayed, and the user can set the destination in advance via the screen. Note that the user can omit the destination setting.

  When the second button 67 is selected by the user, a screen for selecting a payment method is displayed, and the user can set a payment method in advance via the screen. In this example, the payment method is either in-vehicle payment or Internet payment (including credit card payment), and in-vehicle payment is set in the initial state.

  When the third button 68 is selected by the user, a screen for selecting a vehicle type or the like of the vehicle to be arranged is displayed, and the user can set the vehicle type or the like via the screen. In this screen, in addition to the vehicle type, it is also possible to specify whether or not the vehicle is a UD taxi and whether or not the facility X is permitted to enter.

  The fourth button 69 is a button for the user to make a vehicle allocation request. FIG. 17 is a flowchart illustrating the process executed by the vehicle allocation management server 10 in response to the selection of the fourth button 69 by the user. First, as shown in the figure, the server 10 determines the boarding position (receiving position) of the user based on designation by the user (step S200). Specifically, the position on the map of the boarding position designation object 521 in the map display area 52 of the condition designation screen 504 is determined as the boarding position of the user.

  Once the user's boarding position is determined in this manner, the server 10 next selects a vehicle to be assigned to the user based on the user's boarding position, designation by the user (vehicle type, etc.), and vehicle information of each vehicle (step). S210). Basically, a vehicle that is the nearest empty vehicle from the user's boarding position and that matches the vehicle type specified by the user is assigned to the user. As described above, the target vehicle (for example, a specific vehicle type, a UD taxi vehicle, or a vehicle having permission to enter the facility X) does not exist within a predetermined distance from the user's boarding position. In this case, the user may be managed as a waiting state for dispatching (automatically or through confirmation by the user), or the facility X is permitted to enter the facility X within a predetermined distance from the user's boarding position. When there is no vehicle having a vehicle, the user's boarding position is changed outside the facility X (automatically or through user confirmation), and a vehicle that does not have permission to enter the facility X is assigned. May be.

  Then, the server 10 requests the selected vehicle to pick up the vehicle (step S220). The subsequent processing is the same as the flowchart illustrated in FIG. 7 executed in response to the selection of the first button 61 on the top screen 501. When the vehicle is accepted by the corresponding driver, the vehicle is assigned to the user. Is determined (step S240), and if the corresponding driver rejects the incoming vehicle request (NO in step S230), the server 10 again selects a vehicle to be allocated (step S210). Thus, in this example, by selecting the second button 62 on the top screen 501, the user can also specify conditions individually and make a vehicle allocation request.

  The vehicle allocation management server 10 according to the present embodiment described above automatically determines the user's boarding position based on the user's current position accompanying the vehicle allocation request, and also the user's current position and vehicle information of each vehicle. Based on (for example, current position, UD taxi flag, facility X entrance permission flag, etc.), a vehicle to be assigned to the user is automatically selected, and the selected vehicle is picked up at the boarding position determined. Since the request is made, the user can make a vehicle allocation request without specifying the boarding position, the vehicle type, and the like. That is, the vehicle allocation management server 10 according to the present embodiment improves user convenience when making a vehicle allocation request.

  The processes and procedures described in the present specification are implemented by software, hardware, or any combination thereof other than those explicitly described. For example, the processes and procedures described in this specification are realized by mounting logic corresponding to the processes and procedures on a medium such as an integrated circuit, a volatile memory, a nonvolatile memory, and a magnetic disk. The processing and procedure described in this specification can be implemented as a computer program corresponding to the processing / procedure and executed by various computers.

  Even if the processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, multiple software, multiple Component and / or multiple modules. Also, the software and hardware elements described herein can be implemented by integrating them into fewer components or by disassembling them into more components.

  In the present specification, when the constituent elements of the invention are described as one or a plurality, or when they are described without being limited to one or a plurality of cases, they should be understood separately in context. The component may be either singular or plural.

DESCRIPTION OF SYMBOLS 10 Vehicle dispatch management server 11 Computer processor 20 Communication network 32 User terminal 34 Driver terminal 41 Information storage management part 42 Basic function control part 43 Vehicle dispatch request management part 44 Pick-up request management part 100 Pick-up request confirmation screen 110 Pick-up request screen 120 Arrival report screen 130 Boarding report screen 501 Top screen 502 Arranging screen 503 Waiting for arrival screen 504 Condition specification screen

Claims (10)

A system for managing vehicle allocation,
A storage device that stores at least vehicle information of each of the plurality of vehicles, and one or more computer processors,
The one or more computer processors are responsive to execution of readable instructions,
A process of accepting a vehicle allocation request with the current position of the user;
A process of determining the user's boarding position based at least on the current position of the user;
A process of selecting a vehicle to be allocated to the user from the plurality of vehicles based on at least the current position of the user and vehicle information of each of the plurality of vehicles;
Executing a process of requesting the selected vehicle to pick up at the boarding position determined.
system. The one or more computer processors further execute a process of changing the dispatch details in response to a request from the user after a request for an incoming vehicle for the selected vehicle.
The process of changing the dispatch details includes notifying the selected vehicle of the dispatch details after the change,
The system of claim 1. The process of changing the dispatch details includes changing the determined boarding position.
The system of claim 2. The process of changing the dispatch details includes setting the getting-off position of the user.
The system according to claim 2 or 3. The storage device further stores information on a non-recommended stop position that is not recommended as a boarding position although the vehicle can be stopped.
The process of determining the boarding position includes determining the boarding position of the user so as to avoid the non-recommended stop position.
The system according to claim 1. The storage device further stores information related to a recommended stop position where the vehicle can be stopped and recommended as a boarding position;
The process of determining the boarding position includes determining the recommended stop position present within a predetermined range based on the current position of the user as the boarding position of the user.
The system according to any one of claims 1 to 5. The storage device further stores user information including attribute information of each of a plurality of users,
The process of determining the boarding position includes determining the boarding position of the user based at least on the attribute information of the user in addition to the current position of the user.
The system according to claim 1. The storage device further stores user information including attribute information of each of a plurality of users,
The process of selecting the vehicle includes selecting a vehicle to be assigned to the user based on at least the attribute information of the user in addition to the current position of the user.
The system according to claim 1. A method for managing vehicle allocation, executed by one or more computers accessible to a storage device that stores at least vehicle information for each of a plurality of vehicles,
Receiving a dispatch request with the current location of the user;
Determining the user's boarding position based at least on the current position of the user;
Selecting a vehicle to be assigned to the user from the plurality of vehicles based at least on the current position of the user and vehicle information of each of the plurality of vehicles;
Requesting the selected vehicle to pick up at the boarding position determined,
Method. A program for managing vehicle allocation,
In response to execution on one or more computers accessible to a storage device that stores at least the vehicle information of each of the plurality of vehicles, the one or more computers,
A process of accepting a vehicle allocation request with the current position of the user;
A process of determining the user's boarding position based at least on the current position of the user;
A process of selecting a vehicle to be allocated to the user from the plurality of vehicles based on at least the current position of the user and vehicle information of each of the plurality of vehicles;
Requesting the selected vehicle to pick up at the boarding position determined.
program.

Images