JP2024111987A - Information processing device and information processing method - Google Patents

Abstract

A technology is provided that can appropriately allocate vehicles that are used both as taxis and demand transportation vehicles to vehicles that perform demand operation.
[Solution] An exemplary information processing device is an information processing device equipped with a controller, which presents demand operation information to a vehicle device installed in a vehicle that is used both as a taxi vehicle and a demand transportation vehicle, and recruits drivers to perform demand operation.
[Selected figure] Figure 3

Description

The present invention relates to vehicle dispatch technology for on-demand transportation services.

A demand-based operation management system that generates a bus operation plan in response to a user request is known (see, for example, Patent Document 1). Patent Document 1 discloses that an operation plan is generated in which the bus operation route, operation time, etc. are dynamically changed in response to a user request to use the bus. A demand transportation vehicle performs demand operation according to the generated operation plan.

International Publication No. 2020/262673

Taxi vehicles may also be used as demand transportation vehicles. In this case, a driver who is given an operation plan for demand operation changes the taxi vehicle into a demand transportation vehicle and performs demand operation. When switching from a taxi vehicle to a demand transportation vehicle, a preparation period is required to operate as a demand transportation vehicle. The preparation period includes, for example, the work time required to change the vehicle's appearance due to the change in business type, and the travel time required to travel to the departure point of the demand operation.

Considering the preparation period for the above technique and the need to reliably secure drivers (including vehicles) capable of on-demand operation, it is necessary to secure drivers well in advance of the start time of on-demand operation (for example, one hour before). If a system were simply structured to secure drivers for on-demand operation early, there is a concern that this would result in a large loss of opportunities to operate as a taxi.

In addition, during times when taxi usage is high, it may be difficult to secure a taxi vehicle capable of on-demand operation. In such cases, operators may need to manually search for a taxi vehicle capable of on-demand operation, for example by making a phone call, which could impose a heavy burden on the operator.

In view of the above, the present invention aims to provide a technology that can appropriately allocate vehicles that are used both as taxi vehicles and demand transportation vehicles to vehicles that perform demand operation.

An exemplary information processing device of the present invention is an information processing device equipped with a controller, and the controller presents on-demand operation information to a vehicle device disposed in a vehicle that is used both as a taxi vehicle and a demand transportation vehicle, and recruits drivers to perform on-demand operation.

According to an exemplary embodiment of the present invention, vehicles that are used both as taxi vehicles and demand transportation vehicles can be appropriately assigned to vehicles performing demand operation.

A block diagram showing the general configuration of a demand operation management system. A block diagram showing the configuration of a demand operation management device. Block diagram showing the configuration of a driver recruitment device FIG. 13 is a diagram showing a specific example of demand operation information displayed on a display screen of a vehicle device. FIG. 13 is a diagram showing a specific example of demand operation information displayed on a display screen of a vehicle device. FIG. 13 is a diagram showing an example of a vehicle information table; A flowchart illustrating an example of a method for securing a demand-selected vehicle. FIG. 1 is a block diagram showing a schematic configuration of a demand operation system according to a modified example. A flowchart illustrating a flow of a method for securing a demand-selected vehicle according to a modified example.

An exemplary embodiment of the present invention will now be described in detail with reference to the drawings.

<1. Demand operation system>
1 is a block diagram showing a schematic configuration of a demand-responsive operation system 100 according to an embodiment of the present invention. The demand-responsive operation system 100 is a system that realizes demand-responsive transportation, which is a regional public transportation system that operates routes and schedules in response to user reservations.

In this embodiment, vehicles that perform demand operation include vehicles that can be used as both taxi vehicles and demand transportation vehicles. A vehicle that can be used as both a taxi vehicle and a demand transportation vehicle is a vehicle that can perform both taxi operation and demand operation with one vehicle. A vehicle that can be used as both a taxi vehicle and a demand transportation vehicle may be, for example, a minivan, a minivan, a sedan, a bus, a welfare vehicle, etc. A welfare vehicle is, for example, a vehicle that can carry a passenger in a wheelchair as is.

When a vehicle is used as a taxi (operates a taxi service), the vehicle transports the user (passenger) under an individual contract in response to a ride request from the user. The taxi vehicle can pick up users at any time while moving from place to place. The taxi vehicle can also accept reservations from users at any time. A demand transportation vehicle is a vehicle used for demand-based transportation. For example, a demand transportation vehicle operates a predetermined route in sequence in response to a reservation from a user. For example, a demand transportation vehicle is set up so that a route can be freely designed in response to the reservation status from the user, and operates only between reserved stops (bus stops, etc.) via the shortest route.

As shown in FIG. 1, the on-demand operation system 100 includes a on-demand operation management device 1, a driver recruitment device 2, a vehicle device 3, and a reservation terminal device 4.

The demand operation management device 1 manages demand operation. This management includes management of ride reservations, management of operation plans for demand operation, and management of vehicles that perform demand operation. The demand operation management device 1 is connected by wire or wirelessly to a communication network 5 consisting of the Internet, etc.

The driver recruiting device 2 recruits drivers who perform on-demand operation. More specifically, the drivers are drivers of vehicles that can be used as both taxi vehicles and demand transportation vehicles. That is, the driver recruiting device 2 recruits drivers who perform on-demand operation work, targeting drivers who drive vehicles that can be used as both taxi vehicles and demand transportation vehicles. Note that the recruitment of drivers is intended to include the recruitment of vehicles that the drivers will drive.

The driver recruiting device 2 is connected to the communication network 5 by wire or wirelessly. The driver recruiting device 2 is provided so as to be able to communicate with the demand operation management device 1. The driver recruiting device 2 may be configured to communicate with the demand operation management device 1 via the communication network 5. The driver recruiting device 2 may also be configured to communicate with the demand operation management device 1 by being connected to the demand operation management device 1 by wire or wirelessly.

The vehicle device 3 is disposed in a vehicle that is used both as a taxi vehicle and a demand transportation vehicle. The vehicle device 3 may be an on-board device that is always installed in the vehicle, or a portable device that can be carried from the vehicle. The portable device may be, for example, a tablet terminal or a smartphone. The vehicle device 3 includes a display device that displays images. The vehicle device 3 also includes an input device such as a touch panel. The vehicle device 3 is provided so as to be connectable to the communication network 5 wirelessly. The vehicle device 3 is provided so as to be able to communicate with the demand operation management device 1 and the driver recruitment device 2 via the communication network 5.

Note that in FIG. 1, only one vehicle device 3 is shown connected to the communication network 5, but in reality, multiple vehicle devices 3 are connected to the communication network 5.

The reservation terminal device 4 is a terminal device for a user to reserve a vehicle for on-demand operation. The reservation terminal device 4 is connected to the communication network 5 by wire or wirelessly. The reservation terminal device 4 is configured to be able to communicate with the on-demand operation management device 1 via the communication network 5. The reservation terminal device 4 may be, for example, a personal computer, a shared computer, a smartphone, or a tablet terminal.

Note that, although FIG. 1 shows only one reservation terminal device 4 connected to the communication network 5, the number of reservation terminal devices 4 connected to the communication network 5 may be multiple.

In addition, in this embodiment, the user is configured to receive the demand operation service by using web reservations. However, the user may also receive the demand operation service by using telephone reservations instead of or in addition to web reservations. In other words, the demand operation system 100 does not necessarily have to include a reservation terminal device 4 for web reservations. When telephone reservations are used, the operator may input reservation information into the demand operation management device 1.

In addition, in this embodiment, the demand operation management device 1 and the driver recruiting device 2 are separate devices, but the two may be configured as a single device. In other words, the demand operation management device 1 may include the driver recruiting device 2. A device that combines the two may be a so-called server.

2. Demand operation management device
Fig. 2 is a block diagram showing a configuration of a demand operation management device 1 according to an embodiment of the present invention. In Fig. 2, components necessary for explaining the features of the embodiment are shown, and descriptions of general components are omitted. The demand operation management device 1 is a server. The demand operation management device 1 may be a physical server or a cloud server. The demand operation management device 1 may be, for example, a device owned by a private company such as a taxi company, or a device owned by a local government.

As shown in FIG. 2, the demand operation management device 1 includes a controller 11, a memory unit 12, and a communication unit 13. The demand operation management device 1 may be a so-called computer device. The demand operation management device 1 may also be configured to include an input device such as a keyboard and an output device such as a display.

The controller 11 includes a processor that performs calculations and the like. The processor may include, for example, a CPU (Central Processing Unit). The controller 11 may be configured with one processor or multiple processors. When configured with multiple processors, the processors only need to be connected to each other so that they can communicate with each other. Note that when the demand operation management device 1 is configured as a cloud server, the CPU that constitutes the processor may be a virtual CPU.

The memory unit 12 is configured to include volatile memory and non-volatile memory. The volatile memory may include, for example, RAM (Random Access Memory). The non-volatile memory may include, for example, ROM (Read Only Memory), flash memory, or a hard disk drive. The non-volatile memory stores programs and data that can be read by a computer.

The communication unit 13 is configured as a communication interface having an interface circuit for connecting to the communication network 5 (see FIG. 1).

As shown in FIG. 2, the controller 11 includes, as its functions, a reservation reception unit 111, an operation plan management unit 112, and a vehicle dispatch management unit 113. In this embodiment, the functions of the controller 11 are realized by a processor executing calculations according to a program stored in the memory unit 12.

The scope of this embodiment may include a computer program that causes a processor (computer) to realize at least some of the functions of the demand operation management device 1. The scope of this embodiment may also include a computer-readable non-volatile recording medium that records such a computer program. The non-volatile recording medium may be, for example, an optical recording medium (e.g., an optical disk), a magneto-optical recording medium (e.g., a magneto-optical disk), a USB memory, or an SD card, in addition to the non-volatile memory described above.

The functional units 111 to 113 may be realized by one program, or may be realized by separate programs for each functional unit. The functional units 111 to 113 may be realized as separate servers. As described above, the functional units 111 to 113 may be realized by having a processor execute a program, that is, by software, or may be realized by other methods. The functional units 111 to 113 may be realized by using, for example, an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). That is, the functional units 111 to 113 may be realized by hardware using a dedicated IC or the like. The functional units 111 to 113 may be realized by using both software and hardware. The functional units 111 to 113 are conceptual components. The function executed by one component may be distributed to multiple components. The functions of multiple components may be integrated into one component.

The reservation reception unit 111 acquires ride reservation information of a user who wishes to use the demand operation service from outside the demand operation management device 1. The ride reservation information includes, for example, the desired date and time of boarding, the boarding location, and the disembarking location. The boarding location and the disembarking location may be, for example, an existing bus stop, but may also be other locations. The reservation reception unit 111 acquires the ride reservation information from the reservation terminal device 4, for example, via the communication network 5 and the communication unit 13. When a user makes a ride reservation by telephone, the reservation reception unit 111 acquires, for example, the ride reservation information input by an operator using an input device.

The operation plan management unit 112 manages an operation plan according to the acquired boarding reservation information. For example, the operation plan management unit 112 updates an existing operation plan according to the boarding reservation information. The operation plan management unit 112 also generates a new operation plan according to the boarding reservation information. Note that the operation plan includes, for example, the departure point and destination of the demand operation, the route from the departure point to the destination, the user's boarding point and disembarking point, the scheduled arrival time at the boarding point, and the like. The operation plan management unit 112 may manage a single operation plan or multiple operation plans.

The vehicle allocation management unit 113 manages the drivers and vehicles that perform demand operation according to the operation plan. In addition, the vehicle allocation management unit 113 distributes the operation plan required for demand operation to each vehicle that has been decided to perform demand operation, using the vehicle device 3. This allows the drivers of vehicles that have been decided to perform demand operation to perform demand operation according to the operation plan.

<3. Driver Recruitment Device>
Fig. 3 is a block diagram showing the configuration of the driver recruiting device 2 according to the embodiment of the present invention. In Fig. 3, components necessary for explaining the features of the embodiment are shown, and descriptions of general components are omitted. When explaining the driver recruiting device 2, descriptions of contents that overlap with the explanation of the above-mentioned on-demand operation management device 1 will be omitted as appropriate.

The driver recruiting device 2 is a server. Like the demand operation management device 1, the driver recruiting device 2 may be, for example, a device owned by a private company such as a taxi company, or a device owned by a local government. The driver recruiting device 2 is an example of an information processing device of the present invention. As described above, the driver recruiting device 2 may be included in the demand operation management device 1. In such a configuration, a device in which the demand operation management device and the driver recruiting device are integrated may be the information processing device of the present invention. The information processing device may be a single server equipped with the functions of the demand operation management device and the functions of the driver recruiting device.

As described above, the driver recruiting device 2 is an example of an information processing device of the present invention. Also, as shown in FIG. 3, the driver recruiting device 2 includes a controller 21, a memory unit 22, and a communication unit 23. That is, the information processing device 2 includes the controller 21. The driver recruiting device 2 may be a computer device.

The controller 21 includes a processor that performs arithmetic processing and the like. The processor may include, for example, a CPU. The memory unit 22 includes a volatile memory and a non-volatile memory. The non-volatile memory stores computer-readable programs and data. The communication unit 23 is configured as a communication interface having an interface circuit for connecting to the communication network 5 (see FIG. 1).

As shown in FIG. 3, the controller 21 has, as its functions, an operation plan monitoring unit 211, a recruitment processing unit 212, and an application processing unit 213. In this embodiment, the functions of the controller 21 are realized by the processor executing arithmetic processing according to a program stored in the memory unit 22.

The scope of this embodiment may include a computer program that causes a processor (computer) to realize at least some of the functions of the driver recruiting device 2. The scope of this embodiment may also include a computer-readable non-volatile recording medium that records such a computer program.

Functional units 211-213 may be realized by one program, or may be configured such that each functional unit is realized by a separate program. Functional units 211-213 may be realized as separate servers. Functional units 211-213 may be realized by software, or may be realized by other methods. Functional units 211-213 may be realized by hardware, or may be realized by a combination of software and hardware. Functional units 211-213 are conceptual components, and may be distributed across multiple components or integrated with other components.

The operation plan monitoring unit 211 monitors the operation plan managed by the demand operation management device 1. In detail, the operation plan monitoring unit 211 monitors the update status of the operation plan information. The operation plan monitoring unit 211 periodically acquires the operation plan information from the demand operation management device 1 and updates the operation plan information. The operation plan monitoring unit 211 keeps track of the latest operation plan.

The recruitment processing unit 212 presents the demand operation information to the vehicle device 3 and recruits drivers who will perform demand operation. That is, the controller 21 presents the demand operation information to the vehicle device 3 and recruits drivers who will perform demand operation. With this configuration, the driver and vehicle who will perform demand operation can be determined without using the vehicle dispatch center that dispatches vehicles for demand operation. That is, according to this embodiment, the vehicle dispatch time and vehicle dispatch labor can be reduced. Also, according to this embodiment, the burden on the operator who dispatches vehicles can be reduced. Also, with this configuration, the driver can take on demand operation work while considering the convenience of his/her own taxi business. For example, a driver who is performing taxi work can determine whether or not to take on demand operation work by considering the destination of the passenger and the arrival time at the destination. For this reason, it is possible to perform demand operation work while reducing the possibility of losing taxi business opportunities unnecessarily, which can contribute to improving sales. Also, with this configuration, the driver can select demand operation that is operated in an area where he/she is good at and perform demand operation work. In this case, demand operation will be carried out by someone with a thorough understanding of traffic conditions, which is expected to improve the safety of demand operation.

In this embodiment, the recruitment processing unit 212 presents the demand operation information to the vehicle device 3 upon request from a driver using the vehicle device 3. However, the demand operation information may be presented periodically to each vehicle device 3 (each vehicle) connected to the driver recruitment device 2 via the communication network 5. In detail, the presentation of the demand operation information is the distribution of the demand operation information to the vehicle device 3 in order to display the demand operation information on the display screen of the vehicle device 3.

Application software (hereinafter, referred to as the app) for displaying on a display screen the demand operation information distributed from the driver recruiting device 2 is installed on the vehicle device 3. The processor included in the vehicle device 3 executes calculation processing according to the app, and the demand operation information is displayed on the display screen. Drivers can understand operation plans for which drivers are being recruited by using the demand operation information displayed on the display screen. Then, drivers who have viewed the demand operation information can apply for the recruitment using the vehicle device 3.

In detail, the demand operation information is an operation plan for demand operation that includes time information related to the operation and passenger boarding and disembarking location information. Because it includes time information and location information, the driver can take into consideration the future schedule of the taxi business and his/her current location and appropriately decide whether or not to apply for a demand operation job. Note that the demand operation information may be composed of only one operation plan, but may also be composed of multiple operation plans.

Figures 4A and 4B are diagrams showing specific examples of demand operation information displayed on the display screen 3a of the vehicle device 3. Figure 4A is a diagram showing an example of a screen that displays a list of operation plans for which drivers are being recruited. Figure 4B is a diagram showing an example of a screen that is displayed when one operation plan is selected from the list of operation plans shown in Figure 4A.

The screen shown in FIG. 4A displays an operation plan list 31, a current time 32, an update button 33, and a scroll section 34. The operation plan list 31 shows a list of operation plans for which drivers are being recruited. In the example shown in FIG. 4, the operation plan list 31 displays the route name of the route on which demand operation is performed, the start time of the demand operation, the departure point of the demand operation, and the scheduled end time of the demand operation. The operation plan list 31 also displays the estimated arrival time from the current position of the vehicle to which the demand operation information has been delivered to the departure point of the demand operation. Displaying the estimated arrival time makes it easier for drivers to decide whether or not to apply for the recruitment.

The update button 33 is a button for updating the operation plan for which drivers are being recruited to the latest information. When the driver operates the update button 33 (for example, by touching), the latest information is distributed from the driver recruiting device 2. The scroll section 34 is an operation area for displaying the display contents of the operation plan list 31 on the display screen 3a while moving them up and down. The scroll section 34 is provided in anticipation of the possibility that there may be many operation plans for which drivers are being recruited and all of the operation plans cannot be displayed at once on the display screen 3a. The scroll section 34 is provided so that it can be operated, for example, by touching.

When the driver touches the display area of a certain route in the operation plan list 31, a detailed operation plan for the touched route is displayed on the display screen 3a. In the example shown in FIG. 4A, the display area of a certain route is a strip-shaped area extending in the left-right direction that includes all of the areas that display the route name, operation start time, departure point, estimated end time, and estimated arrival time. The screen shown in FIG. 4B is the screen that appears when the display area of route B in the operation plan list 31 shown in FIG. 4 is touched.

In the example shown in FIG. 4A, operation plans determined by drivers in response to applications for recruitment are displayed in a grayed-out state in the operation plan list 31. In detail, the operation plan for route A is displayed in a grayed-out state. Routes displayed in a grayed-out state cannot be selected. In other words, even if the display area of a route displayed in a grayed-out state is touched, the screen does not transition to a screen displaying a detailed operation plan. In this example, operation plans determined by drivers in response to recruitment are displayed in a grayed-out state, but this is an example. Operation plans determined by drivers in response to recruitment may also be configured not to be displayed in the operation plan list 31.

The screen shown in FIG. 4B displays the current time 32, update button 33, and scroll section 34, similar to the screen shown in FIG. 4A. In addition, instead of the operation plan list 31, plan details 35 showing the detailed contents of the operation plan of the selected route are displayed. In addition to the information displayed on the screen of FIG. 4A, the plan details 35 displays boarding and alighting locations, the number of passengers boarding and alighting, and the estimated arrival time at the boarding and alighting locations. In addition, the screen shown in FIG. 4B displays an application button 36 and a back button 37. The application button 36 is a button that the driver operates (e.g., by touching) when applying for a driver recruitment. The back button 37 is a button that the driver operates (e.g., by touching) when returning to the screen showing the operation plan list 31. In addition, in the screen shown in FIG. 4B, the scroll section 34 is used to move the display contents of the plan details 35 up and down while displaying them.

In a preferred embodiment, the recruitment processing unit 212 changes the presentation mode for each vehicle (vehicle device 3) when presenting the demand operation information to the vehicle device 3. That is, the controller 21 changes the presentation mode for presenting the demand operation information for each vehicle. It is preferable that the controller 21 changes the presentation mode based on at least one of the vehicle's position information and information on the vehicle's driver. With this configuration, recruitment content according to the driver's current situation, the driver's preferences, etc. can be displayed on the display screen of the vehicle device 3.

The change in presentation mode may be a change in the order in which multiple pieces of demand operation information are presented, or a change in the number of pieces of demand operation information presented. This allows the presentation mode to be changed for each vehicle with simple processing.

Changes in the presentation mode of the demand operation information for each vehicle (vehicle device 3) will be described below with specific examples. In this embodiment, the memory unit 22 of the driver recruiting device 2 stores a vehicle information table 221 (see FIG. 5) in which information about each vehicle in which a vehicle device 3 is installed is tabulated. Before explaining changes in the presentation mode of the demand operation information, the vehicle information table 221 will be described. Note that FIG. 5 is a diagram showing an example of the vehicle information table 221.

Items in the vehicle information table 221 include "Vehicle ID," "Current location," "Driver ID," "Gender," "Business area," and "Reputation."

The item "Vehicle ID" stores vehicle ID data, which is identification information for identifying each vehicle registered in the demand operation system 100. The vehicle ID data is also the primary key of the data record in the vehicle information table 221. That is, in the vehicle information table 221, a data record is configured for each vehicle ID data, and data for each item linked to the vehicle ID data is stored in the data record. For example, when the vehicle device 3 requests the driver recruiting device 2 to distribute demand operation information, the vehicle ID data is transmitted from the vehicle device 3 to the driver recruiting device 2. This allows the driver recruiting device 2 to extract data for each item linked to the vehicle ID data.

The item "current location" stores current location data indicating the current location of the vehicle. The current location data can be acquired, for example, by using a GPS (Global Positioning System) sensor equipped in the vehicle device 3. The current location data includes, for example, latitude data and longitude data. The current location data is updated by obtaining appropriate information from the vehicle device 3. For example, when the vehicle device 3 requests the driver recruiting device 2 to distribute demand operation information, the current location data may be transmitted to the driver recruiting device 2 together with the vehicle ID data. As another example, the current location data may be transmitted from the vehicle device 3 to the driver recruiting device 2 on a regular basis.

The "Driver ID" item stores driver ID data, which is identification information for identifying the driver who drives the vehicle. Normally, the vehicle driven by a driver is fixed, and the vehicle ID data and driver ID data form a fixed pair. However, the driver who drives the vehicle may change, in which case the driver ID linked to the vehicle ID data will change.

The "Gender" item stores gender data indicating the gender of the driver who drives the vehicle. The gender data is data linked to the driver ID data. When the driver ID data linked to the vehicle ID data is changed, the gender data linked to the vehicle ID data is also changed. The gender data is registered, for example, when the driver ID is registered.

The item "Business Area" stores business area data indicating the main area (region) in which the driver who drives the vehicle performs his/her business. Business area data is data linked to driver ID data. When the driver ID data linked to the vehicle ID data is changed, the business area data linked to the vehicle ID data is also changed. Business area data is registered, for example, when the driver ID is registered.

The item "reputation" stores reputation data indicating the reputation of the driver who drives the vehicle. The reputation data is data linked to the driver ID data. When the driver ID data linked to the vehicle ID data is changed, the reputation data linked to the vehicle ID data is also changed. The reputation data is, for example, the evaluation results of users (passengers) who have used a vehicle operated on demand. The evaluation results are, for example, A rank, B rank, C rank, etc., in order of best reputation. The evaluation results are, for example, transmitted from a terminal device owned by the user to the driver recruitment device 2 via the communication network 5.

For example, when there are multiple operation plans for which drivers are being recruited, the recruitment processing unit 212 changes the presentation order of the operation plans according to the current position data of the vehicle requesting the presentation of the operation plan. For example, the closer the departure point of the demand operation is to the current position of the vehicle, the earlier the operation plan is presented. In the example shown in FIG. 4A, the closer the departure point of the demand operation is to the current position of the vehicle, the higher the operation plan (route) is displayed. Note that whether or not the operation plan is close to the current position may be determined based on the distance or the time required to arrive.

For example, when there are multiple operation plans for which drivers are being recruited, the recruitment processing unit 212 changes the presentation order of the operation plans according to the business area data of the driver of the vehicle requesting the presentation of the operation plan. For example, the operation plan for demand operation in an area that matches the business area data is presented first. In the example shown in FIG. 4A, the operation plan for demand operation in an area that matches the business area data is displayed at the top.

For example, when there are multiple operation plans for which drivers are being recruited, the recruitment processing unit 212 changes the presentation order of the operation plans according to the gender data of the driver of the vehicle requesting the presentation of the operation plan. For example, when the driver is female, the operation plan for on-demand operation in which only female passengers are on board is presented first. In the example shown in FIG. 4A, the operation plan for on-demand operation in which only female passengers are on board is displayed at the top.

In the above example, the order in which operation plans are presented is changed, but the number of operation plans presented may also be changed. Among the multiple operation plans, there may be an operation plan that is presented only to drivers with specific attributes. Also, among the multiple operation plans, there may be an operation plan that is not presented to drivers with specific attributes. For example, the recruitment processing unit 212 may determine whether to present an operation plan depending on the reputation data of the driver of the vehicle requesting the presentation of the operation plan. For example, there may be an operation plan that is not presented to a driver who has caused trouble in the past.

Returning to FIG. 3, the application processing unit 213 accepts applications for the recruitment of drivers for on-demand operation and processes the applications. Applications for the recruitment of drivers are made using a vehicle device 3 that is installed in the vehicle that the driver will be driving. In response to the application, the driver recruiting device 2 acquires an operation plan in which the driver wishes to perform on-demand operations. In addition, in response to the application, the driver recruiting device 2 acquires information on the driver and vehicle that will perform on-demand operation. In detail, the driver and vehicle information may be the driver ID data and vehicle ID data described above.

In this embodiment, the application processing unit 213 determines a driver who will perform on-demand operation in response to an application for recruitment. That is, the controller 21 determines a driver who will perform on-demand operation in response to an application for recruitment. A driver for each operation plan can be determined according to the driver application status. Note that the determination of the driver also includes the determination of the vehicle. In addition, the process of determining a driver for each operation plan in response to an application may be performed by the on-demand operation management device 1, rather than the driver recruitment device 2.

The application processing unit 213 may, for example, determine the driver on a first-come, first-served basis. Alternatively, the application processing unit 213 may determine the driver by accepting applications for a certain period of time. In this case, multiple drivers may apply for the same operation plan. In such a case, the application processing unit 213 may determine the driver who is determined to be most highly rated based on reputation data (see FIG. 5) among the drivers who applied to be the driver for on-demand operation.

As another example of a case where there are multiple applications for the same operation plan, the application processing unit 213 may determine a driver to perform on-demand operation according to the user's (passenger's) desired information. The desired information may be, for example, information provided using the reservation terminal device 4 when reserving a ride. The application processing unit 213 may, for example, determine the driver with attributes closest to the desired information from the driver attribute information linked to the driver ID data as the driver for on-demand operation. For example, if there are many passengers who wish to ride quietly, a quiet driver may be preferentially determined as the driver for on-demand operation, rather than a talkative driver.

In addition, when multiple drivers apply, the application processing unit 213 may have the user select a driver. The application processing unit 213 may also select a driver based on the number of on-demand operation operations performed (track record).

For an operation plan in which a driver has been determined, the application processing unit 213 transmits information about the determined driver and vehicle information to the demand operation management device 1. In response, the demand operation management device 1 (vehicle dispatch management unit 113) distributes detailed information about the operation plan for the demand operation to the vehicle device 3 installed in the vehicle driven by the target driver. The driver who receives the detailed information about the operation plan performs the demand operation work in accordance with the operation plan.

After it is decided to perform on-demand operation, the driver may be able to cancel his/her duties as a driver performing on-demand operation. For example, the controller 21 may be configured to accept a cancellation notice from a driver who has been decided to perform on-demand operation. The cancellation notice may be made using the vehicle device 3. The controller 21 may be configured to accept the cancellation notice when the cancellation notice satisfies a predetermined condition. The predetermined condition may be, for example, that the cancellation notice is made a predetermined time (e.g., two hours) before the start time of the operation in the operation plan. By configuring the system to accept cancellation notices, it is possible to reduce the loss of opportunities to perform taxi operations. When a cancellation notice is accepted, a driver may be recruited again for the corresponding operation plan.

<4. How to secure vehicles for demand operation>
Next, a method for securing a vehicle that performs on-demand operation will be described using the driver recruiting device 2. In the following, a vehicle that can be used as both a taxi vehicle and a demand transportation vehicle and that performs on-demand operation (selects the demand operation service) may be referred to as a demand selection vehicle.

The method for securing a demand-selected vehicle described here is one example of the information processing method of the present invention. The information processing method executed by the driver recruitment device (information processing device) 2 includes a process for presenting demand operation information to a vehicle device 3 disposed in a vehicle that is used both as a taxi vehicle and a demand transportation vehicle, and recruiting drivers to perform demand operation. A specific example of the information processing method (demand-selected vehicle securing method) is described below.

Figure 6 is a flow chart illustrating the flow of a method for securing a demand-selected vehicle according to an embodiment of the present invention. The method shown in Figure 6 is a method for securing a vehicle that performs demand operation (demand-selected vehicle) from among vehicles that are used both as taxi vehicles and demand transportation vehicles.

The scope of this embodiment includes a computer program that causes a computer device to realize the method of securing a demand-selected vehicle of this embodiment. Also, a computer-readable non-volatile recording medium that records such a computer program is also included in the scope of this embodiment. Also, the computer program that causes a computer device to realize the method of securing a demand-selected vehicle of this embodiment may be composed of only one program, or may be composed of multiple programs.

In step S1, the operation plan monitoring unit 211 starts monitoring the operation plan of the demand operation managed by the demand operation management device 1. The operation plan is updated as appropriate in response to reservations from users. The operation plan monitoring unit 211 constantly obtains the latest operation plan by monitoring the operation plan. Once monitoring of the operation plan starts, processing proceeds to the next step S2.

In step S2, the recruitment processing unit 212 starts monitoring whether or not there is a request from the driver to present an operation plan. The driver makes a request to present an operation plan using the vehicle device 3 installed in the vehicle that the driver is driving. In detail, it is expected that requests to present an operation plan will be made by multiple drivers. When there is a request to present an operation plan, the recruitment processing unit 212 presents the operation plan each time. Note that, as described above, the presentation mode of the operation plan may differ for each vehicle.

By this presentation, the driver who has requested the presentation of the operation plan can check the latest operation plan on the display screen 3a of the vehicle device 3. In addition, the driver who has requested the presentation of the operation plan can apply for a driver recruitment set for each operation plan. In detail, the operation plan list 31 as shown in FIG. 4A described above is displayed on the display screen 3a. Then, by performing an operation (such as a touch operation) in accordance with the display on the display screen 3a, the driver can apply for the driver recruitment. For example, by operating the application button 36 shown in FIG. 4B, the driver can apply for the driver recruitment. When monitoring for the presence or absence of a request for presentation of an operation plan is started, the process proceeds to the next step S3.

In step S3, the application processing unit 213 monitors whether or not there are applications for the driver recruitment. The application processing unit 213 periodically (e.g., every minute) monitors whether or not there are applications for the driver recruitment. For example, when the above-mentioned application button 36 is operated, the application processing unit 213 can recognize that a driver recruitment has occurred. If a driver application has been received (Yes in step S3), processing proceeds to the next step S4. If no driver application has been received (No in step S3), the application processing unit 213 continues processing in step S3.

In step S4, the application processing unit 213 determines a driver for the operation plan for which an application has been made in response to the driver recruitment. Here, it is assumed that the driver is determined on a first-come, first-served basis. However, as described above, the driver may be determined by a method other than first-come, first-served. By determining the driver, the vehicle driven by the driver can be secured as a demand-selected vehicle. Once the driver is determined, the process proceeds to the next step S5.

In step S5, the application processing unit 213 notifies the demand operation management device 1 that the demand-selected vehicle has been secured. As a result, the demand operation management device 1 notifies the driver of the vehicle that has been selected to perform the demand operation of details of the operation plan for the demand operation. In detail, the details of the operation plan for the demand operation are notified via the vehicle device 3. The driver recruiting device 2 may notify the driver via the vehicle device 3 that the driver has been selected to perform the demand operation and details of the operation plan. In addition, there may be cases where a driver who applied is not selected. In such a case, the driver recruiting device 2 may notify the driver via the vehicle device 3. When the demand operation management device 1 is notified that the demand-selected vehicle has been secured, the process proceeds to the next step S6.

In step S6, the application processing unit 213 determines whether or not there is an operation plan for which a driver has not been determined. If there is an operation plan for which a driver has not been determined (Yes in step S6), the process returns to step S3. If there is no operation plan for which a driver has not been determined (No in step S6), the process shown in FIG. 6 is completed.

As described above, when a demand-selected vehicle is secured using a driver recruitment method, it is possible to secure a demand-selected vehicle without using a dispatch center that dispatches vehicles for demand-selected operations. In addition, when a demand-selected vehicle is secured using a driver recruitment method, the driver can take on demand-operated operations while taking into consideration the convenience of his or her own taxi operations. This makes it possible to perform demand-operated operations while reducing the possibility of losing taxi operations, which can contribute to increased sales.

5. Modifications
7 is a block diagram showing a schematic configuration of a demand service system 100A according to a modified example. The demand service system 100A according to the modified example further includes a vehicle dispatch device 6 in addition to a demand service management device 1, a driver recruiting device 2, a vehicle device 3, and a reservation terminal device 4.

The dispatch device 6 assigns vehicles to perform demand operation from among a plurality of vehicles that are used both as taxi vehicles and demand vehicles. The dispatch device 6 is, for example, a server provided by a taxi company or the like. The server may be a physical server or a cloud server. The dispatch device 6 is connected to the communication network 5 by wire or wirelessly. The dispatch device 6 is configured to be able to communicate with the demand operation management device 1 and the vehicle device 3 via the communication network 5.

The dispatch device 6 dispatches vehicles that perform demand operation in response to instructions from the demand operation management device 1. In this modified example, as will be described in detail later, the demand operation management device 1 issues dispatch instructions to the dispatch device 6 for operation plans for which the driver recruiting device 2 was unable to secure a driver (demand selected vehicle).

In FIG. 7, only one dispatch device 6 connected to the communication network 5 is shown, but the number of dispatch devices 6 connected to the communication network 5 may be multiple. In addition, in a modified example, a vehicle used as both a taxi vehicle and a demand vehicle may be a vehicle that is linked to a dispatch center operated by a taxi company or the like that has a dispatch device 6, or a vehicle owned by a private taxi operator that is not linked to a dispatch center.

The vehicle dispatch device 6 may also be included in the demand operation management device 1. The demand operation management device 1, the driver recruiting device 2, and the vehicle dispatch device 6 may be configured as a single device. For example, the demand operation management device 1, the driver recruiting device 2, and the vehicle dispatch device 6 may be a single server provided by a taxi company or the like.

Figure 8 is a flow chart illustrating the flow of a method for securing a demand-selected vehicle according to a modified example. The method for securing a demand-selected vehicle according to the modified example differs from the method for securing a demand-selected vehicle according to the embodiment described above (see Figure 6) in that the processes of steps S7 and S8 are added. Since the process is the same as the embodiment described above except for the part related to the additional process, a description thereof will be omitted. The additional process will be described below. Note that in the configuration of the modified example, a vehicle (driver) secured as a demand-selected vehicle may be connected to a vehicle dispatch center. In such a case, the driver selected as the driver for the demand-selected operation notifies the vehicle dispatch center accordingly. The notification may be performed using the vehicle device 3.

In the above embodiment, if there is no driver application in the processing of step S3 (No in step S3), the application processing unit 213 (see FIG. 3) continues the processing of step S3. In this modified example, if there is no driver application in the processing of step S3 (No in step S3), the application processing unit 213 proceeds to the processing of step S7. This is different from the above embodiment.

In step S7, the application processing unit 213 determines whether it is the application deadline. The application deadline is, for example, one hour before the operation start time in the operation plan (see, for example, FIG. 4A, etc.). In addition, if there are multiple operation plans, the application deadline is given to each of the multiple operation plans. If it is the application deadline (Yes in step S7), processing proceeds to the next step S8. If it is not the application deadline (No in step S7), processing returns to step S3.

In step S8, the application processing unit 213 performs a vehicle dispatch request process. In detail, the application processing unit 213 notifies the demand operation management device 1 that an operation plan has occurred for which a demand-selected vehicle could not be secured by the application deadline. In response, the demand operation management device 1 makes a vehicle dispatch request to the vehicle dispatch device 6 for the operation plan for which a demand-selected vehicle could not be secured. This vehicle dispatch request includes a driver determination process. In response to the vehicle dispatch request, the vehicle dispatch device 6 performs a vehicle dispatch process for a vehicle that will perform a demand operation. When the vehicle dispatch request process is completed, the process proceeds to step S6.

As can be seen from the above, in the modified example, if there are no applications for a driver recruitment, the controller 21 requests another device to determine a driver for on-demand operation. By configuring in this way, it is possible to reduce the possibility of a situation occurring in which a vehicle and its driver for on-demand operation cannot be secured.

The dispatch device 6 that receives a dispatch request from the demand operation management device 1 performs the following process, for example. The dispatch device 6 automatically attempts to secure a vehicle for demand operation from among taxi vehicles currently performing taxi operations. If the dispatch device 6 is unable to secure a vehicle for demand operation by a predetermined time (e.g., 50 minutes) before the operation start time, it notifies the operator at the dispatch center of this fact. In this case, the operator manually secures a vehicle for demand operation. In the configuration of the modified example, basically, a demand-selected vehicle can be secured for each operation plan by recruiting drivers using the driver recruiting device 2. For this reason, securing a vehicle for demand operation using the dispatch device 6 and an operator is a last resort. In other words, the possibility of an increase in dispatch time and dispatch labor can be kept low by using the dispatch device 6 and an operator. In addition, the possibility of an increase in the burden on the operator can also be kept low.

In addition, when the on-demand operation management device 1, the driver recruiting device 2, and the vehicle dispatching device 6 are a single device, the controller of the device may be configured to automatically determine a driver to perform on-demand operation when there are no applications for the driver recruitment.

<6. Notes>
An exemplary program of the present invention may be a program for causing a computer to execute an information processing method, and the program may be configured to cause the computer to function as a means for presenting on-demand operation information to a vehicle device disposed in a vehicle that is used both as a taxi vehicle and a demand transportation vehicle, and for recruiting drivers to perform on-demand operation.

<7. Important points to note>
Various technical features disclosed in the description of the invention may be modified in various ways without departing from the spirit of the technical creation. Furthermore, the embodiments and modifications disclosed in the description of the invention may be combined to the extent possible.

In the above embodiment and modified examples, drivers are recruited for all operation plans, but this is merely an example. Drivers may be recruited for only some of the operation plans. For example, if there is a vehicle that is used exclusively as a demand transportation vehicle, each operation plan may be assigned to that vehicle, and drivers may be recruited for the remaining operation plans.

2...Driver recruitment device (information processing device)
21: Controller 3: Vehicle device

Claims (10)

An information processing device including a controller,
The controller is an information processing device that presents on-demand operation information to a vehicle device disposed in a vehicle that is used both as a taxi vehicle and a demand transportation vehicle, and recruits drivers to perform on-demand operation. The information processing device according to claim 1, wherein the demand operation information is an operation plan for the demand operation including time information related to the operation and passenger boarding and disembarking location information. The information processing device according to claim 1 or 2, wherein the controller changes the presentation mode of the demand operation information for each vehicle. The information processing device according to claim 3, wherein the controller changes the presentation mode based on at least one of the vehicle's position information and information about the driver of the vehicle. The information processing device according to claim 3, wherein the change in the presentation mode is a change in the order in which the multiple pieces of demand operation information are presented, or a change in the number of pieces of demand operation information to be presented. The information processing device according to claim 1 or 2, wherein the controller determines the driver who will perform the demand operation in response to the application for the recruitment. The information processing device according to claim 6, wherein the controller accepts a cancellation notification from a driver who has decided to perform the demand operation. The information processing device according to claim 1 or 2, wherein the controller requests another device to determine the driver who will perform the demand operation if there are no applications for the recruitment. The information processing device according to claim 1, wherein the vehicle used as both the taxi vehicle and the demand transportation vehicle is a vehicle capable of operating as a taxi in addition to the demand transportation. An information processing method in which an information processing device executes a process of presenting on-demand operation information to a vehicle device installed in a vehicle that is used both as a taxi vehicle and a demand transportation vehicle, and recruiting drivers to perform on-demand operation.