JP7729094B2 - Remotely operated taxi control method - Google Patents

Description

This disclosure relates to a mobility service that utilizes remotely driven taxis operated by remote drivers.

Patent Document 1 discloses a remote vehicle driving device that drives a vehicle remotely.

Japanese Patent Application Laid-Open No. 2004-295360

The inventors of this application have considered a mobility service that uses remotely driven taxis operated by remote drivers. One issue is that the remote driver may overlook traffic signs or violate traffic laws. Overlooking traffic signs or violating traffic laws could lead to an accident.

One objective of the present disclosure is to provide technology that can reduce the occurrence of accidents in mobility services that use remotely driven taxis operated by remote drivers.

A first aspect relates to a remotely driven taxi control method for controlling a remotely driven taxi driven by a remote driver.
The remote driving taxi control method is
A process of acquiring vehicle information indicating the driving status of the remote-driven taxi while it is being driven by the remote driver;
A process of determining whether or not the remote-controlled taxi is driving abnormally based on the vehicle information;
and a process of restricting the driving of a remote-controlled taxi that is driving abnormally.

The second aspect relates to a remotely driven taxi system that provides mobility services using remotely driven taxis driven by remote drivers.
The remote driving taxi system comprises one or more processors.
The one or more processors
Acquire vehicle information indicating the driving state of the remote-driven taxi while it is being driven by the remote driver;
Based on the vehicle information, determine whether the remotely driven taxi is driving abnormally,
Restrict the operation of remotely operated taxis that are driving abnormally.

According to the present disclosure, whether or not a remotely driven taxi is driving abnormally while being driven by a remote driver is determined. Then, the driving of a remotely driven taxi that is driving abnormally is restricted. Such driving restrictions can reduce the occurrence of accidents.

FIG. 1 is a conceptual diagram for explaining an overview of a remote-driving taxi service according to an embodiment of the present disclosure. 1 is a schematic diagram illustrating a configuration example of a remote-driving taxi system according to an embodiment of the present disclosure. FIG. 10 is a block diagram illustrating an allocation process according to an embodiment of the present disclosure. FIG. 2 is a conceptual diagram illustrating an example of vehicle management information according to an embodiment of the present disclosure. FIG. 2 is a conceptual diagram illustrating an example of driver management information according to an embodiment of the present disclosure. FIG. 10 is a conceptual diagram illustrating an example of allocation management information according to an embodiment of the present disclosure. 10 is a flowchart illustrating an example of an allocation process according to an embodiment of the present disclosure. 10 is a flowchart illustrating another example of the allocation process according to the embodiment of the present disclosure. FIG. 10 is a conceptual diagram for explaining an example of indicator light control according to an embodiment of the present disclosure. FIG. 1 is a conceptual diagram for explaining a travel restriction process according to an embodiment of the present disclosure. FIG. 1 is a block diagram illustrating an example configuration of a remote-driving taxi according to an embodiment of the present disclosure. FIG. 2 is a block diagram illustrating a configuration example of a remote driver terminal according to an embodiment of the present disclosure. 1 is a block diagram illustrating a configuration example of a remote-driving taxi management device according to an embodiment of the present disclosure. FIG.

Embodiments of the present disclosure will be described with reference to the accompanying drawings.

1. Remote-Driving Taxi Service FIG. 1 is a conceptual diagram for explaining an overview of the remote-driving taxi service. The remote-driving taxi service is a mobility service that uses a remote-driving taxi 100. The remote-driving taxi 100 is a vehicle that can be remotely driven, and is remotely driven (remotely operated) by a remote driver 1. Typically, no driver is on board the remote-driving taxi 100. The remote driver 1 is flexibly assigned to a remote-driving taxi 100 and drives the assigned remote-driving taxi 100. A user of the remote-driving taxi service can travel to a destination using the remote-driving taxi 100 driven by the remote driver 1.

One feature of the remote-driving taxi service is that the remote driver 1 is not tied to a vehicle or a location. For example, the remote driver 1 can drive a remote-driving taxi 100-1 in a first area and then immediately drive another remote-driving taxi 100-2 in a second area. Here, the first and second areas may be far apart. For example, the first area may be Hokkaido and the second area may be Kyushu. The remote driver 1 can drive any remote-driving taxi 100 in any area and perform work.

For comparison, consider existing taxi services. In existing taxi services, taxi drivers operate one taxi in a limited area. This means that taxi drivers are tied to the land and vehicle. For example, taxi drivers working in areas with few customers will naturally spend a lot of time doing nothing and waiting for customers. No matter how motivated they are to work, as long as there are no customers in that area, the taxi driver cannot work. This means a lost work opportunity. As another example, when a taxi driver picks up a customer for a long distance, they must drop the customer off in a distant location and then return from that distant location to their base. When returning from a distant location to their base, it is not always possible to pick up a customer at a convenient time. Having to drive long distances with an empty vehicle means a decrease in work efficiency.

On the other hand, with a remote-driving taxi service, the remote driver 1 is not tied to a vehicle or land, so the problems associated with existing taxi services do not arise. For example, the remote driver 1 does not need to wait for customers in areas with few users, but can work one after another in response to requests from users in various areas. Furthermore, in areas with few users, as long as remote-driving taxis 100 are deployed, it is possible to provide a remote-driving taxi service even without an actual driver. As another example, even if the remote driver 1 transports a passenger to a destination far from the departure point, the remote driver 1 does not need to drive the remote-driving taxi 100 back to the original departure point. If the remote driver 1 wants to continue working in another area, he or she can simply park the remote-driving taxi 100 he or she used previously in a taxi parking lot near the destination. That remote-driving taxi 100 can then be used by another remote driver 1.

In this way, a remote-driving taxi service will bring about significant benefits, such as increased employment opportunities and improved work efficiency. Below, we will explain the remote-driving taxi system that will realize this remote-driving taxi service.

2. Overview of the Remote-Driving Taxi System Fig. 2 is a schematic diagram showing an example configuration of a remote-driving taxi system 10 according to this embodiment. The remote-driving taxi system 10 provides a remote-driving taxi service. The remote-driving taxi system 10 includes one or more remote-driving taxis 100, one or more remote driver terminals 200, and a remote-driving taxi management device 300.

The remote-driven taxi 100 is a vehicle that can be remotely driven. The remote-driven taxi 100 is equipped with various sensors and can acquire information such as the current location, vehicle status, and surrounding conditions. The remote-driven taxi 100 can also communicate wirelessly with the remote-driven taxi management device 300.

The remote driver terminal 200 is a device used by the remote driver 1 to remotely drive (remotely operate) the remotely driven taxi 100. The remote driver terminal 200 is equipped with a display device. The remote driver terminal 200 also has remote operation members that the remote driver 1 operates when remotely driving the remotely driven taxi 100. The remote driver terminal 200 is also capable of communicating with the remotely driven taxi management device 300.

The remote-driving taxi management device 300 manages the remote-driving taxi service. For example, the remote-driving taxi management device 300 manages the remote driver 1 and the remote-driving taxi 100. The remote-driving taxi management device 300 can also communicate with each remote-driving taxi 100 and each remote driver terminal 200. The remote-driving taxi management device 300 may be included in a mobility service management system that manages all mobility services. Typically, the remote-driving taxi management device 300 is a management server on the cloud. The management server may be composed of multiple servers that perform distributed processing.

The remote-driving taxi system 10 may further include a user terminal 400. Examples of the user terminal 400 include a smartphone or a PC. The user terminal 400 executes an app for using the remote-driving taxi service. The user terminal 400 is also capable of communicating with the remote-driving taxi management device 300.

The basic flow of the remote-controlled taxi service is as follows:

First, the remote-driving taxi management device 300 performs an "allocation process" to allocate a remote driver 1 to a remote-driving taxi 100. Details of the allocation process will be described later.

The remote driver 1 remotely drives the assigned remotely driven taxi 100. Specifically, the remotely driven taxi 100 uses various sensors to acquire information such as the current location, vehicle status, and surrounding conditions, and transmits vehicle information VCL containing the acquired information to the remotely driven taxi management device 300. The remotely driven taxi management device 300 transfers the received vehicle information VCL to the remote driver terminal 200 used by the remote driver 1. The remote driver terminal 200 displays the received vehicle information VCL and map information on a display device. The remote driver 1 operates the remote control members of the remote driver terminal 200 while referring to the map information and vehicle information VCL displayed on the display device. The remote driver terminal 200 transmits operation information OPE, which indicates the amount of operation of the remotely controlled member, to the remotely driven taxi management device 300. The remotely driven taxi management device 300 transfers the received operation information OPE to the remotely driven taxi 100. The remotely driven taxi 100 controls the vehicle driving in accordance with the received operation information OPE.

The remote driver 1 drives the assigned remote-driving taxi 100 and picks up the user. The remote driver 1 then drives the remote-driving taxi 100 to the destination specified by the user. Upon arriving at the destination, the remote driver 1 drops the user off.

3 is a block diagram for explaining the allocation process performed by the remote-driving taxi management device 300 according to this embodiment. In the allocation process, the remote-driving taxi management device 300 flexibly allocates the remote drivers 1 to the remote-driving taxis 100.

The remote-driving taxi management device 300 holds management information 500 and executes allocation processing based on the management information 500. The management information 500 includes vehicle management information 510, driver management information 520, and allocation management information 530.

4 is a conceptual diagram illustrating an example of vehicle management information 510. The vehicle management information 510 is information for managing the remote-driven taxi 100, and includes an entry for each remote-driven taxi 100. For example, each entry includes a vehicle ID, vehicle model, usage status, driver in charge, current location, destination, driving status, etc.

The vehicle ID is identification information for the remote-driven taxi 100. The vehicle ID may include the license plate information (vehicle registration number) of the remote-driven taxi 100.

The vehicle type is the type of remote-controlled taxi 100. Examples of vehicle types include large, medium, and small. The vehicle type may also include the manufacturer and vehicle name.

The usage status is the current usage status of the remote-driven taxi 100. Examples of usage status include rental (actual vehicle), pick-up, and empty (available vehicle). The usage status also indicates whether any remote driver 1 is assigned to the remote-driven taxi 100.

The assigned driver indicates the driver ID of the remote driver 1 assigned to the remote-controlled taxi 100.

The current location is the current location of the remote-driven taxi 100. The current location is included in the vehicle information VCL sent from the remote-driven taxi 100.

The destination is the destination of the remote-driven taxi 100. For example, the destination is included in a service request REQ_U (described below) from the user. As another example, the destination may be specified by a user riding in the remote-driven taxi 100 and sent from the remote-driven taxi 100.

The driving status is the driving status of the remote-driven taxi 100. The driving status is included in the vehicle information VCL sent from the remote-driven taxi 100.

5 is a conceptual diagram illustrating an example of the driver management information 520. The driver management information 520 is information for managing the remote drivers 1, and includes an entry for each remote driver 1. For example, each entry includes a driver ID, driver status, assigned vehicle, driver characteristics, etc.

The driver ID is identification information for the remote driver 1. The driver ID may also include the name of the remote driver 1.

The driver status is the current status of the remote driver 1. Driver statuses include: in service (transporting passengers), picking up, available (available), etc. The driver status also indicates whether the remote driver 1 is assigned to any remote-driven taxi 100.

The assigned vehicle indicates the vehicle ID of the remote-driven taxi 100 to which the remote driver 1 is assigned.

Driver characteristics indicate the preferences and characteristics of remote driver 1. For example, driver characteristics include desired area, desired vehicle type, rank, earned points, etc.

The desired area is an area that remote driver 1 prefers. The desired area is specified in advance by remote driver 1. For example, remote driver 1 may specify an area where he or she is familiar with the roads as the desired area.

The desired vehicle type is the vehicle type of the remote-driven taxi 100 that the remote driver 1 prefers. The desired vehicle type is specified in advance by the remote driver 1.

The rank is the current rank of remote driver 1. For example, remote driver 1 may be ranked from 5 stars to no stars. As another example, remote driver 1 may be ranked as excellent (SS), good (S), average (A), apprentice (B), etc. The rank of remote driver 1 may reflect a user's rating. The rank may be reflected in the taxi fare. The rank may be reflected in remote driver 1's salary.

Earned points are the points that remote driver 1 has earned to date. For example, points increase according to the number of times passengers are picked up. As another example, points increase according to the distance traveled while carrying passengers. As points increase, the rank may increase.

The existence of ranks and points is expected to improve the quality of service and increase motivation to work. Ranks and points also add a gamification element to the remote-controlled taxi service. As a result, remote drivers 1 can enjoy their work. This also contributes to increased motivation to work and improved service quality.

6 is a conceptual diagram illustrating an example of the allocation management information 530. The allocation management information 530 is information for managing the allocation status between the remote driver 1 and the remote-driving taxi 100. For example, the allocation management information 530 includes allocation relationship information 531, an unallocated taxi list 532, and an unallocated driver list 533.

The allocation relationship information 531 indicates the correspondence between the assigned remote-driven taxi 100 and the remote driver 1. For example, the allocation relationship information 531 indicates the correspondence between the vehicle ID of the remote-driven taxi 100 and the driver ID of the remote driver 1 assigned to that remote-driven taxi 100. If the target user to whom the remote driver 1 (remote-driven taxi 100) will provide service has already been determined, the allocation relationship information 531 also indicates the correspondence with that target user.

A remotely driven taxi 100 to which a remote driver 1 has not yet been assigned is hereinafter referred to as an "unassigned taxi 100N." The unassigned taxi list 532 is a list of unassigned taxis 100N and indicates the vehicle IDs of the unassigned taxis 100N. The unassigned taxi list 532 may also include a queue-style waiting list. The waiting list indicates the priority of the unassigned taxis 100N regarding the assignment process.

A remote driver 1 who has not yet been assigned to a remotely driven taxi 100 will be referred to as an "unassigned driver 1N." The unassigned driver list 533 is a list of unassigned drivers 1N and indicates the driver IDs of the unassigned drivers 1N. The unassigned driver list 533 may also include a queue-style waiting list. The waiting list indicates the priority of the unassigned drivers 1N for the assignment process.

7 is a flowchart showing an example of the allocation process performed by the remote-driving taxi management device 300 according to this embodiment. In this example, it is assumed that the remote driver 1 is waiting for a customer in front of a station or searching for a customer in the city.

In step S310, the unassigned driver 1N operates the remote driver terminal 200 to send an allocation request REQ_D to the remote-driving taxi management device 300. For convenience, the unassigned driver 1N who issues the allocation request REQ_D is referred to as the "requesting driver 1R." The remote-driving taxi management device 300 receives the allocation request REQ_D from the remote driver terminal 200.

In step S320, the remote-driving taxi management device 300 executes the allocation process in response to the allocation request REQ_D. Specifically, the remote-driving taxi management device 300 selects one of the unallocated taxis 100N based on the management information 500. The unallocated taxi 100N is obtained from the unallocated taxi list 532. For convenience, the selected unallocated taxi 100N is referred to as the "first remote-driving taxi 100S." The remote-driving taxi management device 300 assigns the requesting driver 1R to the first remote-driving taxi 100S.

If the unallocated taxi list 532 includes a waiting list, the remote-driven taxi management device 300 may select the first remote-driven taxi 100S according to the priority indicated in the waiting list.

The remotely driven taxi management device 300 may select a first remotely driven taxi 100S based on driver characteristic information included in the driver management information 520. The driver characteristic information includes the desired area and desired vehicle type of the requesting driver 1R. For example, the remotely driven taxi management device 300 may select an unassigned taxi 100N located in the desired area of the requesting driver 1R as the first remotely driven taxi 100S. As another example, the remotely driven taxi management device 300 may select an unassigned taxi 100N that matches the desired vehicle type of the requesting driver 1R as the first remotely driven taxi 100S. The current location and vehicle type of each unassigned taxi 100N are obtained from the vehicle management information 510.

In step S330, the remote-driving taxi management device 300 updates the management information 500 based on the results of the allocation process. In particular, the remote-driving taxi management device 300 updates the management information 500 related to the requesting driver 1R and the first remote-driving taxi 100S.

In step S340, the remote-driving taxi management device 300 sends an allocation notification ASN to the remote driver terminal 200. The allocation notification ASN notifies the remote driver terminal 200 that the allocation process has been completed, the assigned first remote-driving taxi 100S, etc. The remote driver terminal 200 presents the allocation notification ASN to the requesting driver 1R.

In addition, if there are no unassigned taxis 100N that can be assigned, the remote-driving taxi management device 300 may register the requesting driver 1R as "waiting for assignment" in the unassigned driver list 533 (waiting list).

After the allocation process is complete, the remote driver 1 can drive the allocated remote-driving taxi 100. For example, the remote driver 1 can wait for customers in front of a station. As another example, the remote driver 1 can search for customers in the city.

3-3. Allocation Processing in Response to a Request from a User FIG. 8 is a flowchart showing another example of the allocation processing performed by the remote-driving taxi management device 300 according to this embodiment.

In step S350, the remote-driving taxi management device 300 receives a service request REQ_U from the user.

For example, the user runs an app on the user terminal 400 and inputs a service request REQ_U. The service request REQ_U includes a desired boarding location specified by the user. Alternatively, the current location of the user terminal 400 may be considered as the desired boarding location. The service request REQ_U may include a desired boarding time specified by the user. The service request REQ_U may include a destination specified by the user. The service request REQ_U may include the model of the remote-driven taxi 100 desired by the user. The service request REQ_U may include the rank of the remote driver 1 desired by the user. The service request REQ_U may include the driver ID of the remote driver 1 designated by the user. The app on the user terminal 400 sends the service request REQ_U to the remote-driven taxi management device 300.

As another example, an exterior HMI (Human Machine Interface) may be attached to the side of the remote-driven taxi 100. In this case, the user can communicate their desire to use the remote-driven taxi 100 by operating the exterior HMI. For example, the user presses the "Start Use Button" displayed on the exterior HMI. The user may also operate the exterior HMI to specify the rank of the desired remote driver 1. In response to the user's operation of the exterior HMI, the remote-driven taxi 100 transmits a service request REQ_U to the remote-driven taxi management device 300. The service request REQ_U includes the vehicle ID and current location of the remote-driven taxi 100. The current location of the remote-driven taxi 100 corresponds to the desired boarding location.

In step S360, the remote-driving taxi management device 300 executes an allocation process in response to the service request REQ_U. Specifically, the remote-driving taxi management device 300 selects an unallocated taxi 100N and an unallocated driver 1N to provide services to the user based on the management information 500. In other words, the remote-driving taxi management device 300 selects one of the unallocated taxis 100N and one of the unallocated drivers 1N and assigns them to the user. For convenience, the selected unallocated taxi 100N is referred to as the "first remote-driving taxi 100S." Also, for convenience, the selected unallocated driver 1N is referred to as the "first remote-driving driver 1S." The remote-driving taxi management device 300 assigns the first remote-driving driver 1S to the first remote-driving taxi 100S.

For example, if a user wishes to use a remote-driven taxi 100 by operating the vehicle's exterior HMI, the remote-driven taxi management device 300 selects that remote-driven taxi 100 as the first remote-driven taxi 100S.

When a service request REQ_U is sent from the user terminal 400, it is as follows: The service request REQ_U includes the desired boarding location. The vehicle management information 510 includes the current location of each remotely driven taxi 100. The unassigned taxi 100N is obtained from the unassigned taxi list 532. Based on the management information 500, the remotely driven taxi management device 300 selects an unassigned taxi 100N that is closest to the desired boarding location as the first remotely driven taxi 100S. More specifically, the remotely driven taxi management device 300 selects the first remotely driven taxi 100S from the unassigned taxis 100N that exist within a predetermined range from the desired boarding location.

If the unallocated taxi list 532 includes a waiting list, the remote-driven taxi management device 300 may select the first remote-driven taxi 100S according to the priority indicated in the waiting list.

If the service request REQ_U includes the user's desired vehicle type, the remote-driving taxi management device 300 may select an unallocated taxi 100N that matches the user's desired vehicle type as the first remote-driving taxi 100S.

Regarding the first remote driver 1S, the following applies: The remote-driving taxi management device 300 selects the first remote driver 1S from among the unassigned drivers 1N. The unassigned driver 1N is obtained from the unassigned driver list 533. If the unassigned driver list 533 includes a waiting list, the remote-driving taxi management device 300 may select the first remote driver 1S according to the priority indicated in the waiting list.

The remote-driving taxi management device 300 may select the first remote driver 1S based on the driver characteristic information included in the driver management information 520.

For example, the driver characteristic information includes the desired area of each remote driver 1. The current location of the first remote-driven taxi 100S is obtained from the vehicle management information 510. The remote-driven taxi management device 300 may select an unassigned driver 1N whose desired area includes the current location of the first remote-driven taxi 100S as the first remote driver 1S.

As an example, the driver characteristic information includes the desired vehicle type of each remote driver 1. The vehicle type of the first remote-driven taxi 100S is obtained from the vehicle management information 510. The remote-driven taxi management device 300 may select an unassigned driver 1N whose desired vehicle type matches the vehicle type of the first remote-driven taxi 100S as the first remote driver 1S.

As yet another example, the driver characteristic information includes the rank of each remote driver 1. A service request REQ_U from a user may include the rank of the remote driver 1 desired by the user. The remote driving taxi management device 300 may select an unassigned driver 1N whose rank is equal to or higher than the user's desired rank as the first remote driver 1S.

As yet another example, the user may designate a desired remote driver 1. In that case, the service request REQ_U includes the driver ID of the remote driver 1 designated by the user. The remote driving taxi management device 300 selects the remote driver 1 designated by the user as the first remote driver IS.

The remote-driving taxi management device 300 may distribute a service request REQ_U to the remote driver terminals 200 of all unassigned drivers 1N who meet the conditions. If the unassigned driver 1N wishes to provide a service to that user, he or she may respond to the remote-driving taxi management device 300 with an intention to accept. The remote-driving taxi management device 300 may select the unassigned driver 1N who responds with an intention to accept as the first remote driver 1S on a first-come, first-served basis.

The remote-controlled taxi management device 300 assigns the selected first remote-controlled driver 1S to the selected first remote-controlled taxi 100S.

In step S370, the remote-driving taxi management device 300 updates the management information 500 based on the results of the allocation process. In particular, the remote-driving taxi management device 300 updates the management information 500 related to the first remote driver 1S and the first remote-driving taxi 100S.

In step S380, the remote-driving taxi management device 300 sends an allocation notification ASN to the remote driver terminal 200 of the first remote driver 1S. The allocation notification ASN notifies the requesting driver 1R that the allocation process is complete, the assigned first remote-driving taxi 100S, the desired boarding location, the desired boarding time, the destination, etc. The remote driver terminal 200 presents the allocation notification ASN to the requesting driver 1R.

The remote-driving taxi management device 300 also transmits service information INF to the user terminal 400. The service information INF includes information about the first remote-driving driver 1S and the first remote-driving taxi 100S who provide the service to the user. For example, the service information INF may include the vehicle type and license plate information of the first remote-driving taxi 100S. The service information INF may also include the name and rank of the first remote-driving driver 1S.

After the allocation process is completed, the first remote driver 1S can drive the allocated first remote-controlled taxi 100S. The first remote driver 1S moves the first remote-controlled taxi 100S to the desired pickup location and picks up the user.

4. Indicator Light Control Whether the remote-driven taxi 100 is currently available or not depends on the current usage status of the remote-driven taxi 100. For example, if the usage status is "rent" or "pick-up", the remote-driven taxi 100 is unavailable. On the other hand, if the usage status is "vacant", the remote-driven taxi 100 is available.

However, because the remote-driven taxi 100 does not have a driver on board, it may be difficult for the user to determine whether the remote-driven taxi 100 is available for use. Therefore, the remote-driven taxi system 10 according to this embodiment performs "indicator light control" to appropriately notify the user whether the remote-driven taxi 100 is available for use.

Figure 9 is a conceptual diagram illustrating an example of indicator light control according to this embodiment. The remote-driven taxi 100 is equipped with an indicator light 140 that indicates whether it is currently available. Typically, the indicator light 140 is attached to the ceiling of the remote-driven taxi 100. When the indicator light 140 is lit, it means that the remote-driven taxi 100 is currently available. On the other hand, when the indicator light 140 is off, it means that the remote-driven taxi 100 is currently unavailable.

As described above, the vehicle management information 510 indicates the usage status of each remote-driven taxi 100. Furthermore, the allocation management information 530 indicates the allocation status between the remote driver 1 and the remote-driven taxi 100. The remote-driven taxi system 10 according to this embodiment performs indicator light control based on the management information 500.

First, consider a remote-driven taxi 100 to which a remote driver 1 has already been assigned. The remote-driven taxi system 10 automatically turns on the indicator light 140 of a remote-driven taxi 100 that is currently available, and automatically turns off the indicator light 140 of a remote-driven taxi 100 that is currently unavailable. More specifically, the remote-driven taxi management device 300 recognizes the usage status of a remote-driven taxi 100 to which a remote driver 1 has already been assigned, based on the management information 500. The remote-driven taxi management device 300 then transmits instruction information INS to the remote-driven taxi 100 instructing it to turn on/off the indicator light 140 depending on the usage status. The remote-driven taxi 100 automatically turns on or off its own indicator light 140 in accordance with the received instruction information INS. In this way, the remote-driven taxi system 10 (remote-driven taxi management device 300) automatically controls the lighting status of the indicator light 140 of the remote-driven taxi 100.

Next, consider an unassigned taxi 100N that has not yet been assigned to a remote driver 1. Note that the unassigned taxi 100N can be recognized based on the unassigned taxi list 532.

In a first example, the remote-driving taxi system 10 automatically turns off the indicator light 140 of the unassigned taxi 100N.

In the second example, the "number of unassigned drivers 1N" is taken into consideration. Unassigned drivers 1N can be recognized based on the unassigned driver list 533. If an unassigned driver 1N exists, the unassigned driver 1N can be immediately assigned to an unassigned taxi 100N in response to a service request REQ_U from the user. In other words, if an unassigned driver 1N exists, the unassigned taxi 100N can be immediately made available without making the user wait. From the above perspective, the remote-driving taxi system 10 selects unassigned taxis 100N for which to turn on the indicator light 140 depending on the number of unassigned drivers 1N. For example, the remote-driving taxi system 10 selects unassigned taxis 100N that are equal to or less than the number of unassigned drivers 1N. The remote-driving taxi system 10 may select the same number of unassigned taxis 100N as the number of unassigned drivers 1N. The remote-driving taxi system 10 then automatically turns on the indicator light 140 of the selected unassigned taxi 100N and automatically turns off the indicator lights 140 of the other unassigned taxis 100N. By appropriately lighting up the indicator light 140 of the unassigned taxi 100N, the user's options can be increased.

In a third example, the unassigned taxi list 532 includes a waiting list indicating the priority of unassigned taxis 100N for the assignment process. It is expected that a remote driver 1 can be assigned immediately or with a short waiting time to an unassigned taxi 100N that is at the top of the waiting list. From the above perspective, the remote-driving taxi system 10 selects an unassigned taxi 100N that is within a predetermined rank from the top of the waiting list. The remote-driving taxi system 10 then automatically turns on the indicator light 140 of the selected unassigned taxi 100N and automatically turns off the indicator lights 140 of the other unassigned taxis 100N. By appropriately turning on the indicator lights 140 of unassigned taxis 100N, it is possible to increase the user's options.

In any of the above first to third examples, the remote-driving taxi management device 300 can determine whether to turn on the indicator light 140 for each unassigned taxi 100N based on the management information 500. The remote-driving taxi management device 300 then transmits instruction information INS to the unassigned taxi 100N instructing it to turn on/off the indicator light 140. The unassigned taxi 100N automatically turns on or off its own indicator light 140 in accordance with the received instruction information INS. In this way, the remote-driving taxi system 10 (remote-driving taxi management device 300) automatically controls the lighting state of the indicator light 140 of the remote-driving taxi 100.

As a variant, when the indicator light 140 is turned on, its "appearance" may be changed depending on whether or not a remote driver 1 has already been assigned to the remote-driven taxi 100. For example, if a remote driver 1 has been assigned, the indicator light 140 may be turned on more brightly than when a remote driver 1 has not been assigned.

As described above, the indicator light 140 of the remote-driven taxi 100 turns on/off to appropriately notify the user whether the remote-driven taxi 100 is available. This allows the user to easily recognize whether the remote-driven taxi 100 is available.

5. Driving Restriction Processing FIG. 10 is a conceptual diagram for explaining the "driving restriction processing" according to this embodiment. The remotely driven taxi system 10 restricts the driving of the specified remotely driven taxi 100 as necessary. For example, the driving restriction includes setting the upper limit vehicle speed to a value lower than the default value. As another example, the driving restriction includes an emergency stop. As yet another example, the driving restriction includes retreating to a safe position such as the shoulder of the road.

For example, the remote-driven taxi management device 300 acquires vehicle information VCL, including the driving status, from the remote-driven taxi 100 while it is being driven by the remote driver 1. Based on the vehicle information VCL, the remote-driven taxi management device 300 monitors the driving status of the remote-driven taxi 100 and determines whether or not there is abnormal driving. Here, abnormal driving includes overlooking traffic signs, violating traffic laws, meandering, etc. Regarding violations of traffic laws, there may be unavoidable circumstances, so a certain degree of tolerance may be set. If abnormal driving is detected, the remote-driven taxi management device 300 transmits instruction information INS to the remote-driven taxi 100 that is driving abnormally, instructing it to impose driving restrictions. Upon receiving the instruction information INS, the remote-driven taxi 100 imposes driving restrictions accordingly.

As another example, the remote-driven taxi 100 itself may acquire vehicle information VCL while being driven by the remote driver 1 and determine whether or not it is driving abnormally based on the vehicle information VCL. If abnormal driving is detected, the remote-driven taxi 100 will impose driving restrictions.

As yet another example, the remote driver terminal 200 may be equipped with a driver monitor that detects the biometric information of the remote driver 1 (heart rate, pulse, eye movement, etc.). The remote driver terminal 200 determines whether or not there is an abnormality in the remote driver 1 based on the detection results from the driver monitor. Abnormalities in the remote driver 1 include falling asleep or sudden illness. If an abnormality in the remote driver 1 is detected, the remote driver terminal 200 notifies the remote-driving taxi management device 300 of the occurrence of a driver abnormality. The remote-driving taxi management device 300 transmits instruction information INS to the remote-driving taxi 100 being driven by the remote driver 1 with the abnormality, instructing it to impose driving restrictions. Upon receiving the instruction information INS, the remote-driving taxi 100 imposes driving restrictions accordingly.

As yet another example, the remote-driving taxi management device 300 may receive biometric information detected by the driver monitor from the remote driver terminal 200. In this case, the remote-driving taxi management device 300 determines whether or not there is an abnormality with the remote driver 1.

In this way, the remote-driven taxi system 10 (remote-driven taxi management device 300, remote-driven taxi 100) controls the remote-driven taxi 100 to impose driving restrictions as necessary. Such driving restrictions make it possible to reduce the occurrence of accidents.

Furthermore, the history of abnormal driving may be reflected in the evaluation and salary of remote driver 1. This is expected to improve remote driver 1's awareness and lead to more careful remote driving by remote driver 1. This will also contribute to reducing accidents.

11 is a block diagram showing an example of the configuration of a remotely driven taxi 100 according to this embodiment. The remotely driven taxi 100 includes a communication device 110, a sensor group 120, a driving device 130, indicator lights 140, a control device 150, an exterior HMI 160, and an interior HMI 170.

The communication device 110 communicates with the remote-driving taxi management device 300.

The sensor group 120 includes vehicle condition sensors that detect the condition of the remote-driven taxi 100. The vehicle condition sensors include a speed sensor, an acceleration sensor, a yaw rate sensor, a steering angle sensor, etc. The sensor group 120 also includes a position sensor that detects the position of the remote-driven taxi 100. An example of a position sensor is a GPS (Global Positioning System) sensor. The sensor group 120 also includes a recognition sensor that recognizes (detects) the situation around the remote-driven taxi 100. Examples of recognition sensors include a camera, LIDAR (Laser Imaging Detection and Ranging), radar, etc.

The traveling device 130 includes a steering device 131, a drive device 132, and a braking device 133. The steering device 131 steers the wheels. For example, the steering device 131 includes an electric power steering (EPS) device. The drive device 132 is a power source that generates driving force. Examples of the drive device 132 include an engine, an electric motor, and an in-wheel motor. The braking device 133 generates braking force.

The indicator light 140 indicates whether the remotely driven taxi 100 is currently available. Typically, the indicator light 140 is mounted on the ceiling of the remotely driven taxi 100.

The control device 150 controls the remote-driving taxi 100. The control device 150 includes one or more processors 151 (hereinafter simply referred to as processor 151) and one or more storage devices 152 (hereinafter simply referred to as storage devices 152). The processor 151 executes various processes. For example, the processor 151 includes a CPU (Central Processing Unit). The storage device 152 stores various information required for processing by the processor 151. Examples of the storage device 152 include volatile memory, non-volatile memory, HDD (Hard Disk Drive), SSD (Solid State Drive), etc. The control device 150 may include one or more ECUs (Electronic Control Units).

The vehicle control program PROG1 is a computer program executed by the processor 151. The vehicle control program PROG1 is stored in the storage device 152. Alternatively, the vehicle control program PROG1 may be recorded on a computer-readable recording medium. The functions of the control device 150 are realized when the processor 151 executes the vehicle control program PROG1.

The exterior HMI 160 is attached to the side of the remote-driven taxi 100. The user can communicate their desire to use the remote-driven taxi 100 by operating the exterior HMI 160. For example, the user presses the "Start Use" button displayed on the exterior HMI 160.

The in-vehicle HMI 170 is installed inside the remote-controlled taxi 100. The in-vehicle HMI 170 includes a display device, speaker, microphone, touch panel, etc. The user can use the in-vehicle HMI 170 to communicate their destination to the remote driver 1. The user can also converse with the remote driver 1 via the in-vehicle HMI 170.

6-2. Information Acquisition Processing, Communication Processing The processor 151 uses the sensor group 120 to acquire driving environment information ENV that indicates the driving environment of the remote-driven taxi 100. The driving environment information ENV is stored in the storage device 152. The driving environment information ENV includes vehicle position information, vehicle state information, and surrounding situation information. The vehicle position information indicates the position of the remote-driven taxi 100 detected by the position sensor. The vehicle state information indicates the vehicle state detected by the vehicle state sensor.

The surrounding situation information indicates the recognition results obtained by the recognition sensor. For example, the surrounding situation information includes images captured by a camera. The surrounding situation information may also include object information regarding objects around the remote-driven taxi 100. Examples of objects around the remote-driven taxi 100 include pedestrians, other vehicles (preceding vehicles, parked vehicles, etc.), signs, white lines, roadside structures, etc. The object information indicates the relative position and relative speed of the object with respect to the remote-driven taxi 100.

The vehicle information VCL is used by the remote driver 1 when remotely driving the remotely driven taxi 100. The vehicle information VCL includes at least a portion of the driving environment information ENV described above. For example, the vehicle information VCL includes vehicle position information, vehicle status information, and surrounding situation information. The vehicle information VCL may also include the current usage status of the remotely driven taxi 100. The vehicle management information 510 is updated based on this usage status. The vehicle information VCL may also include information input by the user through the exterior HMI 160 or the interior HMI 170.

The processor 151 communicates with the remote-driving taxi management device 300 via the communication device 110. For example, the processor 151 transmits vehicle information VCL to the remote-driving taxi management device 300. As another example, the processor 151 transmits a service request REQ_U to the remote-driving taxi management device 300. As yet another example, the processor 151 receives operation information OPE from the remote-driving taxi management device 300. As yet another example, the processor 151 receives instruction information INS from the remote-driving taxi management device 300.

6-3. Vehicle Driving Control The processor 151 executes vehicle driving control to control the driving of the remotely driven taxi 100. The vehicle driving control includes steering control, drive control, and braking control. The processor 151 executes vehicle driving control by controlling the driving device 130. More specifically, the processor 151 executes steering control by controlling the steering device 131. The processor 151 executes drive control by controlling the drive device 132. The processor 151 executes braking control by controlling the brake device 133.

During remote driving, the processor 151 controls vehicle driving in accordance with the operation information OPE received from the remote driving taxi management device 300.

In relation to indicator light control (see Section 4 above), the processor 151 receives instruction information INS from the remote driving taxi management device 300 instructing it to turn on/off the indicator light 140. The processor 151 automatically turns on or off the indicator light 140 in accordance with the received instruction information INS.

In connection with the driving restriction process (see Section 5 above), the processor 151 receives instruction information INS instructing driving restrictions from the remote-driving taxi management device 300. The processor 151 imposes driving restrictions in accordance with the received instruction information INS.

Alternatively, processor 151 may determine whether the vehicle is driving abnormally based on vehicle information VCL. If abnormal driving is detected, processor 151 imposes driving restrictions.

12 is a block diagram showing an example of the configuration of a remote driver terminal 200 according to this embodiment. The remote driver terminal 200 includes a communication device 210, a display device 220, a remote control member 230, a driver monitor 240, and a control device 250.

The communication device 210 communicates with the remote-driving taxi management device 300.

The display device 220 displays various information to present it to the remote driver 1.

The remote control members 230 are members operated by the remote driver 1 when remotely driving (remotely operating) the remote-controlled taxi 100. The remote control members 230 include a steering wheel 231, an accelerator pedal 232, a brake pedal 233, turn signals, etc.

The driver monitor 240 detects the remote driver 1's biometric information (heart rate, pulse, eye movement, etc.).

The control device 250 controls the remote driver terminal 200. The control device 250 includes one or more processors 251 (hereinafter simply referred to as processor 251) and one or more storage devices 252 (hereinafter simply referred to as storage devices 252). The processor 251 executes various processes. For example, the processor 251 includes a CPU. The storage device 252 stores various information required for processing by the processor 251. Examples of the storage device 252 include volatile memory, non-volatile memory, HDD, SSD, etc.

The remote driving program PROG2 is a computer program executed by the processor 251. The remote driving program PROG2 is stored in the storage device 252. Alternatively, the remote driving program PROG2 may be recorded on a computer-readable recording medium. The remote driving program PROG2 may be provided via a network. The functions of the control device 250 are realized when the processor 251 executes the remote driving program PROG2.

7-2. Remote driving processing The processor 251 communicates with the remote-driving taxi management device 300 via the communication device 210. The processor 251 receives vehicle information VCL transmitted from the remote-driving taxi 100 to which the remote driver 1 is assigned. The vehicle information VCL is stored in the storage device 252. The processor 251 presents the vehicle information VCL to the remote driver 1 by displaying the vehicle information VCL on the display device 220. The processor 251 also displays map information on the display device 220. The remote driver 1 can understand the status of the remote-driving taxi 100 based on the map information and vehicle information VCL displayed on the display device 220.

The remote driver 1 operates the remote control member 230. The processor 251 acquires the amount of operation of the remote control member 230 by the remote driver 1. The amount of operation is detected by a sensor installed on the remote control member 230. The processor 251 generates operation information OPE that reflects the amount of operation and transmits the operation information OPE to the remote-driving taxi management device 300.

In connection with the allocation process (see Section 3-2 above), the processor 251 transmits an allocation request REQ_D input by the remote driver 1 to the remote-driving taxi management device 300. The processor 251 also receives an allocation notification ASN from the remote-driving taxi management device 300.

7-4. Information notification process The processor 251 may notify the remote-driving taxi management device 300 of the current driver status via the communication device 210. Based on the driver status, the driver management information 520 is updated.

7-5. Driving Restriction Processing In relation to the driving restriction processing (see Section 5 above), the processor 251 determines whether or not there is an abnormality in the remote driver 1 based on the detection results by the driver monitor 240. If an abnormality in the remote driver 1 is detected, the processor 251 notifies the remote-driving taxi management device 300 of the occurrence of a driver abnormality. Alternatively, the processor 251 may transmit biometric information detected by the driver monitor to the remote-driving taxi management device 300.

13 is a block diagram showing an example of the configuration of a remote-driving taxi management device 300 according to this embodiment. The remote-driving taxi management device 300 includes a communication device 310 and a control device 350.

The communication device 310 communicates with each of the remote-driven taxi 100, the remote driver terminal 200, and the user terminal 400.

The control device 350 controls the remote-driving taxi management device 300. The control device 350 includes one or more processors 351 (hereinafter simply referred to as processor 351) and one or more storage devices 352 (hereinafter simply referred to as storage devices 352). The processor 351 executes various processes. For example, the processor 351 includes a CPU. The storage device 352 stores various information required for processing by the processor 351. For example, management information 500 (see Figure 3) is stored in the storage device 352. Examples of the storage device 352 include volatile memory, non-volatile memory, HDD, SSD, etc.

The management program PROG3 is a computer program executed by the processor 351. The management program PROG3 is stored in the storage device 352. Alternatively, the management program PROG3 may be recorded on a computer-readable recording medium. The management program PROG3 may be provided via a network. The functions of the control device 350 are realized when the processor 351 executes the management program PROG3.

8-2. Remote driving processing The processor 351 communicates with the remote-driven taxi 100 and the remote driver terminal 200 via the communication device 310. The processor 351 receives vehicle information VCL from the remote-driven taxi 100 and transfers the vehicle information VCL to the remote driver terminal 200. The processor 351 also receives operation information OPE from the remote driver terminal 200 and transfers the operation information OPE to the remote-driven taxi 100.

8-3. Allocation Processing In connection with the allocation processing (see Section 3 above), the processor 351 receives an allocation request REQ_D from the remote driver terminal 200. The processor 351 also receives a service request REQ_U from the remote-driven taxi 100 or the user terminal 400. In response to the allocation request REQ_D or the service request REQ_U, the processor 351 performs the allocation processing based on the management information 500 (see Sections 3-2 and 3-3 above). The processor 351 updates the management information 500 based on the results of the allocation processing. The processor 351 also transmits an allocation notification ASN to the remote driver terminal 200. The processor 351 also transmits service information INF to the user terminal 400.

In relation to indicator light control (see Section 4 above), the processor 351 recognizes the usage status, etc. of each remote-driven taxi 100 based on the management information 500, and determines whether to turn on or off the indicator light 140. Then, the processor 351 transmits instruction information INS to the remote-driven taxi 100 instructing it to turn on or off the indicator light 140.

8-5. Driving Restriction Processing In connection with the driving restriction processing (see Section 5 above), the processor 351 acquires vehicle information VCL from the remote-driven taxi 100 while it is being driven by the remote driver 1. Based on the vehicle information VCL, the processor 351 monitors the driving status of the remote-driven taxi 100 and determines whether or not it is driving abnormally. The processor 351 transmits instruction information INS instructing a driving restriction to a remote-driven taxi 100 that is driving abnormally.

The processor 351 also receives notification of a driver abnormality from the remote driver terminal 200. The processor 351 transmits instruction information INS instructing the remote-driven taxi 100 being driven by the remote driver 1 in whom the abnormality occurred to impose driving restrictions.

9. Demand Forecasting It is useful to forecast the demand for remotely driven taxi services for each area. For example, based on the demand forecast, the placement of remotely driven taxis 100 can be optimized for each area. For example, more remotely driven taxis 100 can be placed in advance in areas with high demand. This increases service opportunities and leads to increased revenue. In addition, user waiting times are reduced, improving user satisfaction.

1 Remote driver 10 Remotely driven taxi system 100 Remotely driven taxi 140 Indicator light 150 Control device 151 Processor 152 Storage device 200 Remote driver terminal 250 Control device 251 Processor 252 Storage device 300 Remotely driven taxi management device 350 Control device 351 Processor 352 Storage device 400 User terminal 500 Management information 510 Vehicle management information 520 Driver management information 530 Allocation management information 531 Allocation relationship information 532 Unallocated taxi list 533 Unallocated driver list INF Service information INS Instruction information OPE Operation information REQ_U Service request REQ_D Allocation request VCL Vehicle information

Claims (1)

1. A remotely driven taxi control method for controlling a remotely driven taxi operated by a remote driver by one or more processors , comprising:
A process of acquiring vehicle information indicating a driving state of the remote-driven taxi while being driven by the remote driver;
A process of monitoring the driving state of the remote-driven taxi based on the vehicle information and determining whether or not the remote-driven taxi is driving abnormally due to driving by the remote driver ;
and a process of restricting the driving of the remote-controlled taxi that is driving abnormally ,
The abnormal driving is one of failing to notice a traffic sign, violating traffic laws, and meandering.
Remote driving taxi control method.