JP7596901B2 - Vehicle allocation control device and vehicle allocation control method - Google Patents

Description

The present invention relates to a vehicle dispatch control device and a vehicle dispatch control method.

A public vehicle usage support system that can support the use of public vehicles is known (see Patent Document 1). The usage support system recognizes the operation information of public vehicles and extracts public vehicles that meet the boarding and disembarking conditions desired by the user.

JP 2020-47017 A

Patent Document 1 does not take into consideration the risk of users contracting an infectious disease or the risk of infecting other passengers (collectively referred to as "infection risk"). On the other hand, the reduced transport efficiency of shared vehicles due to the prohibition of shared rides increases energy consumption.

The present invention was made in consideration of the above problems, and its purpose is to provide a vehicle dispatch control device and a vehicle dispatch control method that reduce the risk of infection during carpooling while suppressing declines in transportation efficiency.

In view of the above object, a vehicle dispatch control device according to one aspect of the present invention receives a signal indicating a vehicle dispatch request permitting ridesharing from a user terminal device owned by a first user, determines whether the first user is infected with a predetermined infectious disease, and if the first user is not infected, determines whether the first user's movement history includes a first infection risk history of staying in a location with a congestion level equal to or above a predetermined value for a predetermined period of time or longer, and prohibits the first user who is determined to be infected or whose movement history includes the first infection risk history from sharing a ride with other users who do not have antibodies to the infectious disease.

According to one aspect of the present invention, it is possible to reduce the risk of infection when sharing a ride while suppressing a decrease in transportation efficiency.

FIG. 1 is a block diagram showing a configuration of a vehicle dispatch control system 1 including a vehicle dispatch control device 100 according to a first embodiment of the present invention. FIG. 2 is a flowchart showing an example of a control flow by the control device 10 (controller) of the vehicle dispatch control device 100. FIG. 3 is a flowchart showing a detailed procedure of step S02 in FIG. 2 according to the first embodiment. FIG. 4 is a flowchart showing a detailed procedure of step S02 in FIG. 2 according to the second embodiment.

The following describes an embodiment of the present invention with reference to the drawings.

First Embodiment
With reference to FIG. 1, the vehicle allocation control device 100 according to the first embodiment of the present invention will be described as a vehicle allocation control system 1. The vehicle allocation control system 1 is a system that controls the allocation of multiple shared vehicles shared by multiple users. The vehicle allocation control device 100 processes vehicle allocation requests from multiple users and allocates the shared vehicles. The vehicle allocation control system 1 has the vehicle allocation control device 100, in-vehicle devices 200V1 to 200Vn (hereinafter, sometimes collectively referred to as in-vehicle devices 200Vn) that are provided in multiple shared vehicles V1 to Vn (hereinafter, sometimes collectively referred to as shared vehicles Vn) used by multiple users, and user terminal devices 400A to 400Z (hereinafter, sometimes collectively referred to as user terminal devices 400A) that are owned by multiple users. The number of in-vehicle devices 200V1 to 200Vn and user terminal devices 400A to 400Z that constitute the vehicle allocation control system 1 of this embodiment is not limited.

The shared vehicle Vn is a vehicle equipped with an automatic driving function that allows it to travel automatically without a driver. The shared vehicle Vn is equipped with a drive mechanism and a steering mechanism, and these mechanisms are controlled completely automatically by the automatic driving function. The shared vehicle Vn may be equipped with a manual driving function that allows it to travel by the driver's operation, or may be a vehicle that can switch between the automatic driving function and the manual driving function. The automatic driving function of this embodiment can appropriately use the automatic driving technology at the time of filing of this application. The shared vehicle Vn does not need to be equipped with an automatic driving function.

The vehicle dispatch control device 100, the in-vehicle devices 200V1 to 200Vn, and the user terminal devices 400A to 400Z each have a communication device (20, 220, 420), and can exchange information with each other via a telecommunications network such as the Internet 300.

The user terminal device 400A of this embodiment is a computer that includes a ROM (Read Only Memory) that stores a program applied to the user terminal device 400A of this embodiment, a CPU (Central Processing Unit) that serves as an operating circuit that executes each function by executing the program stored in the ROM, and a RAM (Random Access Memory) that functions as an accessible storage device. The user terminal device 400A may be a personal computer, a smartphone, a PDA (Personal Digital Assistant), or other portable terminal device.

The user terminal device 400A includes an input device 410 that accepts a request (allocation request) from each user to use the shared vehicle Vn, a communication device 420, a display device 430 for notifying each user of information, and a control device 440 that executes a control process for the use of the shared vehicle Vn by the user. The control device 440 acquires information on the current location of the user operating the user terminal device 400A using a position acquisition device such as a GPS (Global Positioning System) receiver (not shown) provided in the user terminal device 400A. The control device 440 transmits the acquired current location information to the vehicle allocation control device 100 via the communication device 420. The control device 440 transmits input information such as a request (allocation request) from each user to use the shared vehicle Vn to the vehicle allocation control device 100 via the communication device 420. The request (allocation request) includes the user's ID information, the user's current location information, the user's desired boarding location information, the user's desired disembarking location information, the user's desired boarding time information, etc.

The vehicle-mounted device 200Vn includes a GPS receiver 210 that detects the current position of each shared vehicle Vn, a communication device 220 that communicates with external devices such as the vehicle dispatch control device 100, and a control device 230 that executes control processing for the use of the shared vehicle Vn by users. The control device 230 transmits current position information acquired using the GPS receiver 210 to the vehicle dispatch control device 100 via the communication device 220. The control device 230 notifies the user of information transmitted from the vehicle dispatch control device 100 using a display, speaker, etc. (not shown). In this embodiment, the control device 230 receives information about other users who wish to share a ride in the shared vehicle Vn from the vehicle dispatch control device 100 and notifies the user. In this embodiment, "share a ride" refers to multiple people riding together in one shared vehicle, for example, referring to strangers riding in one shared vehicle.

The vehicle dispatch control device 100 includes a control device 10 that functions as a server for the vehicle dispatch control system 1 and executes control processing for managing and operating the vehicle dispatch control system 1, a communication device 20 that can communicate with the vehicle-mounted device 200Vn and the user terminal device 400A, and a database 30 that stores information received by the communication device 20, information on each shared vehicle Vn, etc. The database 30 stores shared vehicle information 31, usage requests 32 (vehicle dispatch requests) received from users, map information 33, user information 34, and traffic information 35.

The shared vehicle information 31 is information about each shared vehicle Vn. The shared vehicle information 31 includes information about the current location of each shared vehicle Vn, the remaining fuel or power capacity of each shared vehicle Vn, malfunction information, the current usage status of each shared vehicle Vn, etc.

The usage request 32 is usage request information for the shared vehicle Vn input by each user via the user terminal device 400A. The usage request 32 includes information indicating the user's ID information, information on the user's current location, the boarding location (starting point), disembarking location (destination), scheduled boarding time (scheduled departure time), scheduled disembarking time (scheduled arrival time), etc., set by the user. The scheduled boarding time and scheduled disembarking time may each have a time range. The boarding location and disembarking location may each be a boarding area and a disembarking area having an area equal to or greater than a certain value.

Map information 33 is map information including information on road structures, facilities, etc. User information 34 is information on all users who can use the vehicle dispatch control system. User information 34 includes ID information of all users and information on the current locations of all users. Traffic information 35 is traffic information including the traffic conditions of vehicles traveling on roads, the status of construction work being carried out on roads, and information on traffic accidents.

As shown in FIG. 1, the control device 10 (controller) of the vehicle dispatch control device 100 includes a ROM 12 that stores programs for executing processes to manage and operate the vehicle dispatch control system 1, a CPU 11 that functions as an operating circuit that functions as the vehicle dispatch control device 100 by executing the programs stored in the ROM 12, and a RAM 13 that functions as an accessible storage device.

With reference to FIG. 2, an example of a control flow (vehicle dispatch control method) by the control device 10 (controller) of the vehicle dispatch control device 100 in FIG. 1 will be described. In step S01, the control device 10 communicates with the user terminal device 400A and receives a signal indicating input information including a usage request (vehicle dispatch request) requesting the use of the shared vehicle Vn from the first user. The usage request includes ride-sharing availability information indicating whether the user wishes to ride the shared vehicle Vn alone or whether ride-sharing with other users is permitted. The control device 10 calculates a driving plan based on the usage request. The driving plan is determined by the position coordinates of the boarding position, the position coordinates of the disembarking position, the driving route of the shared vehicle Vn, the scheduled departure time at the boarding position, and the scheduled arrival time at the disembarking position. When calculating the route from the boarding position to the disembarking position, the control device 10 takes into account vehicle arrival delays due to road congestion, etc., using the map information 33 and traffic information 35. In this embodiment, a case will be described in which the control device 10 receives a usage request from the first user to allow ride-sharing with other users in step S01.

Proceeding to step S02, the control device 10 determines whether or not to prohibit the first user from sharing a ride with other users based on the risk of the first user infecting the other user. If the risk of infection is high, pairings that increase the risk of infection can be avoided by prohibiting the first user from sharing a ride with other users who have a high risk of infection. Details of step S02 will be described later with reference to FIG. 3.

Proceeding to step S03, the control device 10 searches for a second user who satisfies the carpooling conditions and can ride with the first user from among other users who were not prohibited from riding in step S02. If a candidate who satisfies the carpooling conditions is found (YES in step S04), proceed to step S05. If a candidate who satisfies the carpooling conditions is not found (NO in step S04), proceed to step S08. The carpooling conditions include the allowable range of changes to the first user's driving plan (boarding location, disembarking location, driving route, scheduled boarding time, scheduled disembarking time) associated with the carpooling, the gender and age of the carpooling partner, etc. For example, if the driving plan for the first user and the second user to ride together falls within the time range of the scheduled boarding time and scheduled disembarking time and the boarding area and disembarking area indicated in the first user's usage request 32, it can be determined that the carpooling conditions are met.

In step S05, the control device 10 calculates a new driving plan (carpooling driving plan) for the first user and the second user to share a ride based on the usage requests 32 of the first user and the second user and the carpooling conditions. The carpooling driving plan includes the boarding positions, disembarking positions, boarding times, and disembarking times of the first user and the second user in addition to the driving route. Proceeding to step S06, the control device 10 selects an available shared vehicle from the multiple shared vehicles Vn based on the carpooling driving plan, with reference to the shared vehicle information 31.

Proceeding to step S07, the control device 10 communicates with each of the user terminal devices 400A of the first and second users, and transmits a signal indicating the completion of the reservation of the shared vehicle V1 to be used and the carpooling trip plan. Upon receiving the signal, the display device 430 of the user terminal device 400A displays the completion of the reservation of the shared vehicle V1 and the carpooling trip plan. At the same time, the control device 10 communicates with the in-vehicle device 200Vn of the shared vehicle V1 to be used, and transmits a signal indicating the carpooling trip plan to dispatch the vehicle. This allows the first and second users to ride together in a single shared vehicle V1.

Meanwhile, in step S08, the control device 10 selects an available shared vehicle from the multiple shared vehicles Vn based on the driving plan calculated in step S01 and with reference to the shared vehicle information 31. Proceeding to step S09, the control device 10 communicates with the user terminal device 400A of the first user and transmits a signal indicating the completion of the reservation of the shared vehicle V1 to be used and the driving plan. Upon receiving the signal, the display device 430 of the user terminal device 400A presents the completion of the reservation of the shared vehicle V1 and the driving plan. At the same time, the control device 10 communicates with the in-vehicle device 200Vn of the shared vehicle V1 to be used and transmits a signal indicating the driving plan to dispatch the vehicle. This allows the first user to use the shared vehicle V1 alone.

In this way, the vehicle dispatch control device 100 can process vehicle dispatch requests from multiple users, including a first user and a second user, and dispatch a shared vehicle to be used.

Next, referring to FIG. 3, the specific contents of the process of determining whether or not to prohibit ride-sharing (step S02 in FIG. 2) performed by the vehicle dispatch control device 100 to reduce the risk of infection during ride-sharing while suppressing a decline in transportation efficiency will be described. Step S02 includes steps S201 to S211 in FIG. 3.

In step S201, the control device 10 determines whether the first user is currently infected with a specified infectious disease. Specific methods of determination include a method based on self-reporting by the first user, or a method based on information on infected persons with a specified infectious disease provided by a public institution such as the national government, a local government, or a public hospital. For example, in the case of COVID-19, one method is to use the COVID-19 Infection Information Identification and Management Support System (HER-SYS), which was developed and introduced by the Ministry of Health, Labor and Welfare to centrally grasp and manage information on infected persons, etc.

If it is determined that the first user is currently infected (YES in S201), in step S202, the control device 10 determines that the first user is infected. Proceeding to step S203, the control device 10 prohibits the first user determined to be infected from sharing a ride with other users who have a high risk of infection. Specifically, the control device 10 prohibits the first user determined to be infected from sharing a ride with other users who do not have antibodies to the infectious disease. Other users who do not have antibodies to the infectious disease are people who have no history of infection or have not been vaccinated against the infectious disease within a specified period of time. As a result, other users who do not have antibodies to the infectious disease are excluded from the search targets in step S03, and pairing with the first user who has a high risk of infection is prohibited. Therefore, sharing a ride with the first user who has a high risk of infection and other users who do not have antibodies to the infectious disease who have a high risk of infection, i.e., sharing a ride with a high risk of infection, is prohibited.

If it is determined that the user is not currently infected (NO in S201), in step S204, the control device 10 determines whether data indicating the movement history of the first user from the present to the time before the specified incubation period of the infection exists without interruption for a period longer than the specified period. The "specified incubation period of the infection" is the period from infection with a specified infection to onset of symptoms, for example, 12.5 days (in the case of a new coronavirus infection). The movement history can be calculated from information on the current location of the first user acquired using a location acquisition device equipped in the user terminal device 400A. For example, when the current location of the first user cannot be tracked for several hours or half a day or more, such as traveling by airplane, the first user's behavior during that period may include a high risk of infection. For this reason, the control device 10 makes a negative determination (NO in S204) and proceeds to step S205.

In step S205, the control device 10 determines that the first user is likely to be infected. Proceeding to step S206, the control device 10 prohibits the first user determined to be likely to be infected from sharing a ride with other users who are at high risk of infection, for example, those who do not have antibodies to the infectious disease. As a result, other users who do not have antibodies to the infectious disease are excluded from the search targets of step S03, and are prohibited from pairing with the first user who is at high risk of infection.

On the other hand, if the determination in step S204 is affirmative, the process proceeds to step S207, where the control device 10 determines whether or not there is a missing portion in the first user's movement history from the present until a predetermined infectious disease incubation period. In other words, the control device 10 determines whether or not there is a portion in the first user's most recent movement history that is interrupted for less than a predetermined period of time. If the determination is negative (NO in S207), the process proceeds to step S210, and if the determination is affirmative (YES in S207), the process proceeds to step S208.

In step S208, the control device 10 determines whether there is a movement history of the first user prior to the specified incubation period of the infectious disease. If the determination is positive (YES in S208), the control device 10 uses the movement history of the first user prior to the specified incubation period of the infectious disease to complement the missing portion of the movement history from the present to the specified incubation period of the infectious disease. For example, the control device 10 predicts that the first user will behave in the same manner as at least one movement history of the same month, day of the week, and time period prior to the specified incubation period of the infectious disease, and complements the missing portion of the movement history. Then, the process proceeds to step S210.

In step S210, the control device 10 judges whether or not the first infection risk history is included in the movement history of the first user from the present to the predetermined incubation period of the infection. The "first infection risk history" is a history of staying in a place where the congestion level is equal to or higher than a predetermined value for a predetermined period (15 minutes) or more. The criterion for judging whether or not the first infection risk history exists differs depending on the type of the infection. Specifically, the criterion value (predetermined value) of the congestion level and the criterion period (predetermined period) of the stay period vary depending on the type of the infection. This makes it possible to appropriately judge whether or not the first infection risk history exists depending on the type of the infection. The "place where the congestion level is equal to or higher than a predetermined value" includes facilities registered in the infection risk POI database. The infection risk POI database is updated with information from public institutions such as the national government, local governments, and public hospitals. Facilities that meet the following conditions (1) to (3) are registered in the infection risk POI database. In addition, "enclosed" refers to an indoor space that does not comply with the standards for adjusting the air environment in the Building Management Act. "Crowded" means that the density is 0.5 people/m2 ^or more when the maximum capacity is in use under standard operating conditions. "Close contact" means that conversations or vocalizations are conducted within a distance of 1 meter under standard operating conditions.
(1) The facility is a facility where a cluster infection has occurred. (2) The facility is located in a municipality where the number of infected people per capita is higher than a specified value. (3) The facility meets the conditions of being confined, crowded, and close contact (a classification estimated from published values or the construction date, use, etc. of the facility).

If the determination in step S210 is positive, proceed to step S205 described above; if the determination in step S210 is negative, proceed to step S211. The first user is not infected, and the movement history of the first user does not include a first infection risk history, which is a history of staying in a place with a congestion level of a predetermined value or more for a predetermined period of time or more. Therefore, in step S211, the control device 10 determines that the first user is a person who is unlikely to be infected. In this case, from step S03 onwards, the first user is allowed to share a ride with other users who are at high risk of infection, including other users who do not have antibodies to the infectious disease. Therefore, it is possible to improve the transportation efficiency by sharing a ride while reducing the risk of infection when sharing a ride.

As described above, the first embodiment provides the following advantages:

In steps S203 and S206, the control device 10 prohibits the first user who is determined to be infected or whose movement history includes a first infection risk history from sharing a ride with other users who do not have antibodies to the infectious disease. This prohibits the first user who is at high risk of infecting others from sharing a ride with other users who are at high risk of becoming infected. This makes it possible to reduce the risk of infection when sharing a ride while suppressing a decrease in transportation efficiency.

Other users who do not have antibodies to an infectious disease are those who have no history of infection or have not been vaccinated against an infectious disease within a specified period of time. This makes it possible to correctly determine other users who do not have antibodies to an infectious disease. Specific methods for determining infection history and vaccination history include, as with infected person information, a method of determining based on self-reporting by the first user, or information on infected people of a specified infectious disease provided by public institutions such as the national government, local governments, and public hospitals.

The control device 10 identifies a second user who can share a ride with the first user from among other users who are not prohibited from sharing a ride (YES in S03 and S04), selects a shared vehicle that can be used by the first and second users (S06), and presents to the user terminal devices 400A owned by the first and second users at least a reservation completion for the shared vehicle V1 and a driving plan for the shared vehicle V1. This makes it possible to present a ride sharing option with a low risk of infection, thereby reducing the risk of infection during ride sharing and suppressing a decrease in transportation efficiency.

Second Embodiment
In the second embodiment, an example will be described in which the control device 10 prohibits a first user who has a high risk of infecting the ride-sharing partner from sharing a ride with another user who is likely to become seriously ill if infected in step S02. In the second embodiment, step S02 in Fig. 2 further includes steps S212 to S214 in Fig. 4 which are performed after step S211 in Fig. 3. The control device 10 executes a ride-sharing prohibition determination based on the infection risk shown in Figs. 3 and 4 for other users who may be ride-sharing partners of the first user in the same manner as for the first user.

Specifically, after step S211, the process proceeds to step S212, where the control device 10 determines whether the other user who has been determined to be unlikely to be infected is likely to become seriously ill if infected with an infectious disease. The criteria for determining whether a person is likely to become seriously ill if infected with an infectious disease are predetermined according to the type of infectious disease. Specifically, if a person meets at least one of the following criteria: being elderly (aged 65 or older), being an infant (aged 5 or younger), being pregnant, having a chronic or underlying illness, or having a BMI (Body Mass Index) of 30 or higher, it can be determined that the person is likely to become seriously ill if infected with an infectious disease.

If the determination in step S212 is positive, the control device 10 determines the other user as a person who is unlikely to be infected and who is likely to become seriously ill if infected with an infectious disease (step S213). On the other hand, if the determination in step S212 is negative, the control device 10 determines the other user as a person who is unlikely to be infected and who is unlikely to become seriously ill if infected with an infectious disease (step S214).

On the other hand, in the processing of steps S203 and S206 for the first user, the control device 10 prohibits the first user determined to be infected from sharing a ride with other users who are likely to become seriously ill if infected with the infectious disease. That is, the control device 10 prohibits the first user determined to be positive in step S201 from sharing a ride with other users determined to be positive in step S212. As a result, the first user determined to be infected is prohibited from sharing a ride not only with other users who do not have antibodies to the infectious disease (high risk of infection), but also with other users who are likely to become seriously ill if infected with the infectious disease (high risk of severe illness). This further reduces the risk of infection, allowing users to use the ride-hailing service with peace of mind.

Other Embodiments
As described above, the embodiment of the present invention has been described, but the description and drawings forming a part of this disclosure should not be understood as limiting this invention. From this disclosure, various alternative embodiments, examples and operating techniques will become apparent to those skilled in the art.

The control device 10 may suggest to the manager of the shared vehicle V1 that the vehicle interior of the shared vehicle V1 be disinfected or ventilated after use by a first user who has been determined to be infected or whose movement history includes a first infection risk history. This can reduce the risk of infection from viruses or bacteria remaining in the shared vehicle V1 after use by the first user.

The control device 10 may prohibit a first user who is determined to be infected or whose movement history includes a first infection risk history from sharing a ride with all other users. This allows the first user who is at high risk of infection to ride alone in the shared vehicle V1, further reducing the risk of infection, allowing users to use the ride-hailing service with peace of mind.

For a first user who is determined to be not infected and whose movement history does not include the first infection risk history, the control device 10 may identify a second user who may ride with the first user from among other users who are determined to be not infected and whose movement history does not include the first infection risk history. This allows users to ride together with others who have a low risk of infecting the other person, further reducing the risk of infection and allowing users to use the ride-hailing service with peace of mind.

The control device 10 may determine whether the history of the first user's use of the shared vehicle V1 includes a history of sharing with other users who have a high risk of infection (second infection risk history). In the case of a positive determination, the control device 10 may determine the first user as a person with a high risk of infection and prohibit the first user from sharing with other users who do not have antibodies to the infectious disease. Alternatively, the control device 10 may further prohibit the first user from sharing with other users who have a higher risk of developing severe symptoms than a predetermined reference value, which indicates the possibility of developing severe symptoms when infected with an infectious disease. In this way, if the first user's ride-sharing history includes a ride-sharing history with a high risk of infection (second infection risk history), the first user can be prohibited from sharing with other users in the same manner as in the case where the first user is an infected person, and the first user's movement history includes the first infection risk history. This further reduces the risk of infection, allowing the user to use the ride-hailing service with peace of mind.

10 Control device (controller)
32 Request for use (dispatch request)
100 Vehicle allocation control device 400A User terminal device Vn Shared vehicle

Claims (10)

A vehicle dispatch control device including a controller that processes a vehicle dispatch request from a user who wishes to use a shared vehicle shared by a plurality of users,
The controller:
receiving a signal indicating the ride sharing request from a user terminal device owned by a first user, the ride sharing request allowing the first user to share a ride;
determining whether the first user is infected with a predetermined infectious disease;
If the first user is not the infected person, determining whether or not the movement history of the first user includes a first infection risk history, which is a history of staying in a place with a congestion degree of a predetermined value or more for a predetermined period of time or more,
prohibiting the first user, who is determined to be an infected person or whose movement history includes the first infection risk history, from sharing a ride with another user who does not have an antibody to the infectious disease;
Vehicle dispatch control device. Other users who do not have antibodies to the infectious disease are those who have no history of infection or have not been vaccinated against the infectious disease within a specified period of time.
The vehicle dispatch control device according to claim 1 . The controller further prohibits the first user, who is determined to be an infected person or whose movement history includes the first infection risk history, from sharing a ride with another user who has a risk of serious illness, which indicates a possibility of serious illness if infected with the infectious disease, higher than a predetermined reference value.
The vehicle dispatch control device according to claim 1 or 2. The controller:
Identifying a second user who is able to share a ride with the first user from among other users who are not prohibited from sharing a ride with the first user;
Selecting a shared vehicle available to the first user and the second user;
presenting at least a completion of the reservation of the shared vehicle and a ride-sharing plan for the shared vehicle to each of user terminal devices owned by the first user and the second user;
The vehicle dispatch control device according to any one of claims 1 to 3. The controller proposes to an administrator of the shared vehicle to perform at least one of disinfection and ventilation on the vehicle interior of the shared vehicle after the first user, who is determined to be an infected person or whose movement history includes the first infection risk history, has used the shared vehicle.
The vehicle dispatch control device according to any one of claims 1 to 4. The criteria for determining whether or not there is a first infection risk history differ depending on the type of the infectious disease.
The vehicle dispatch control device according to any one of claims 1 to 5. The controller prohibits the first user, who is determined to be an infected person or whose movement history includes the first infection risk history, from sharing a ride with all other users.
The vehicle dispatch control device according to claim 1 or 2. The controller, for the first user who is determined to be not an infected person and whose movement history does not include the first infection risk history, identifies a second user who may ride with the first user from among other users who are determined to be not an infected person and whose movement history does not include the first infection risk history.
The vehicle dispatch control device according to claim 7. The controller:
Determine whether the history of the first user using the shared vehicle includes a history of the first user sharing the vehicle with another user who is determined to be an infected person or whose movement history includes the first infection risk history;
A vehicle dispatch control device as described in any one of claims 1 to 6, which prohibits the first user, who is determined to be not an infected person and whose travel history does not include the first infection risk history, and whose history of using the shared vehicle includes a history of sharing a vehicle with another user who is determined to be an infected person or whose travel history includes the first infection risk history, from sharing a vehicle with another user who does not have antibodies to the infectious disease. A vehicle dispatch control method for processing a vehicle dispatch request from a user who wishes to use a shared vehicle shared by a plurality of users, comprising:
receiving a signal from a first user indicating the ride request allowing for carpooling;
determining whether the first user is infected with a predetermined infectious disease;
If the first user is not the infected person, determining whether or not the movement history of the first user includes a first infection risk history, which is a history of staying in a place with a congestion degree of a predetermined value or more for a predetermined period of time or more,
prohibiting the first user, who is determined to be an infected person or whose movement history includes the first infection risk history, from sharing a ride with another user who does not have an antibody to the infectious disease;
Vehicle dispatch control method.

Images