Information processing device, information processing method, and program
By connecting vehicles in on-demand transportation systems based on request similarity, the system optimizes routes to enhance user convenience and maintain efficiency in sparsely populated areas.
Patent Information
- Application Number
- JP2023086774
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-26
- Publication Date
- 2024-12-06
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In on-demand transportation systems, vehicles in sparsely populated areas take longer routes to accommodate multiple user requests, leading to decreased user convenience and efficiency for transport operators.
The system connects multiple vehicles in a partial travel section based on similarity of requests to create a connected travel plan, allowing one driver to operate multiple vehicles, thereby optimizing routes and reducing unnecessary detours.
This approach enhances user convenience by minimizing travel time and maintains transportation efficiency by reducing the need for multiple vehicles to serve individual requests.
Smart Images

Figure 2024169912000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to an information processing device, an information processing method, and a program. [Background technology]
[0002] In low-density areas, the expansion of "transportation gap areas" where it is difficult to access public transportation such as trains and route buses is becoming a social issue. In such areas, the introduction of shared-ride on-demand transportation is progressing in order to balance meeting transportation demand with profitability (transportation efficiency, i.e., the number of passengers per vehicle trip) for transportation service providers (bus operators, local governments, etc.). Shared-ride on-demand transportation (hereinafter simply called on-demand transportation) is a transportation system that accepts requests from users consisting of boarding and alighting locations and desired times, and dynamically creates a driving plan to transport multiple users who meet similar conditions specified in the request in a single vehicle. Shared-ride on-demand transportation is also called demand transportation or on-demand bus.
[0003] The on-demand transportation system disclosed in Patent Document 1 generates a travel route by applying a predetermined criterion after receiving a travel request from each user (including information on boarding and disembarking locations, boarding time, and disembarking time). In addition, when this on-demand transportation system receives a request after creating a travel route, it updates the travel route by applying the same criterion. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Application Publication No. 10-241091 Summary of the Invention [Problem to be solved by the invention]
[0005] In this type of on-demand transportation, in order to respond to requests from multiple users with a single trip by one vehicle, a route that is longer than the shortest route for each user is set as the driving route of the vehicle. In particular, in areas with low population density, it is typical that it takes a significantly longer time to reach the destination (for example, an extra hour is required compared to traveling the shortest distance) because the vehicle travels to boarding and disembarking points that are dispersed over a wide geographical area. This is a major source of dissatisfaction for users and reduces their convenience. If the number of vehicles to respond to requests is increased to resolve this situation, the drivers of each vehicle will have to work at least from the departure time to the arrival time of the vehicle they are responsible for, which will worsen the transportation efficiency for the transportation company.
[0006] Therefore, one of the objectives that the embodiments disclosed in this specification aim to achieve is to provide an information processing device, an information processing method, and a program that can suppress a decrease in transportation efficiency while also suppressing a decrease in convenience. [Means for solving the problem]
[0007] The information processing device according to the first aspect includes: a request acquisition unit that acquires request information transmitted from a user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; a connected driving plan creation unit that creates a driving plan for each of the vehicles so that the vehicles, which are assigned to each of the request information, travel in a connected state in a partial travel section when the similarity of the plurality of pieces of request information satisfies a predetermined criterion; and an output unit that outputs the travel plan; has.
[0008] In the information processing method according to the second aspect, An information processing device, Acquire request information transmitted from the user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; If the similarity between the plurality of pieces of request information satisfies a predetermined criterion, a travel plan is created for each of the vehicles so that the plurality of vehicles, which are assigned to each of the pieces of request information, travel in a connected state in a partial travel section; The driving plan is output.
[0009] The program according to the third aspect comprises: a request acquisition step of acquiring request information transmitted from a user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; a coupled driving plan creation step of creating a driving plan for each of the vehicles assigned to each of the request information so that the vehicles travel in a coupled state in a partial driving section when the similarity of the plurality of pieces of request information satisfies a predetermined criterion; An output step of outputting the driving plan; to be executed by the computer. Effect of the Invention
[0010] According to the above-described aspects, it is possible to provide an information processing device, an information processing method, and a program that can suppress a decrease in convenience while suppressing a decrease in transportation efficiency. [Brief description of the drawings]
[0011] [Figure 1] 1 is a block diagram showing a configuration of an information processing device according to a first embodiment; [Diagram 2] FIG. 2 is a schematic diagram showing an example of an area in which mobility services are provided. [Figure 3A] FIG. 2 is a schematic diagram showing the correspondence between vehicles and drivers. [Figure 3B] FIG. 2 is a schematic diagram showing the correspondence between vehicles and drivers. [Figure 4] FIG. 11 is a schematic diagram showing a configuration example of a mobility system according to a second embodiment. [Diagram 5] FIG. 4 is a schematic diagram showing an example of travel plan data. [Figure 6] FIG. 2 is a schematic diagram showing an example of a travel route. [Figure 7] FIG. 2 is a schematic diagram showing an example of a driver schedule. [Figure 8] FIG. 13 is a schematic diagram showing an example of a screen for inputting a reservation request. [Figure 9] FIG. 2 is a schematic diagram showing an example of a driving plan. [Figure 10] FIG. 2 is a schematic diagram showing an example of a driving plan. [Figure 11] FIG. 4 is a schematic diagram showing an example of travel plan data. [Figure 12] FIG. 2 is a schematic diagram showing an example of a driver schedule. [Figure 13] FIG. 11 is a diagram showing an example of information notified to a driver. [Figure 14] FIG. 2 is a schematic diagram showing an example of a navigation screen. [Figure 15] FIG. 1 is a block diagram showing the configuration of a computer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] <Embodiment 1> 1 is a block diagram showing a configuration of an information processing device 1 according to embodiment 1. As shown in FIG. 1, the information processing device 1 includes a request acquisition unit 2, a joint driving schedule creation unit 3, and an output unit 4.
[0013] The request acquisition unit 2 acquires request information transmitted from a user terminal. Here, the request information includes a start point of the use of the vehicle, an end point of the use of the vehicle, and a time when the vehicle is used. The request information may further include other information. The vehicle is, for example, a vehicle remotely driven by a driver, but may be a vehicle driven with the driver on board. In addition, the vehicle is specifically, for example, a vehicle, but may not necessarily be a vehicle as long as it has a function of traveling on the ground and transporting objects. In addition, the objects to be transported are not limited to people, and may be cargo. When the similarity of the acquired multiple request information satisfies a predetermined criterion, the linked driving plan creation unit 3 creates a driving plan for each vehicle so that multiple vehicles, consisting of vehicles assigned to each request information, travel in a linked state in a partial driving section. The output unit 4 outputs the driving plan for each vehicle created by the linked driving plan creation unit 3 to an arbitrary device. In addition, the output of the driving plan may be, specifically, a display of the driving plan, a transmission of the driving plan, or a printing of the driving plan.
[0014] According to the information processing device 1 of the first embodiment, when the similarity of the request information satisfies a predetermined criterion, a driving plan is created and output so that a plurality of vehicles travel in a partial travel section in a coupled state. Therefore, according to this driving plan, only one driver needs to perform driving duties in a section where a plurality of vehicles travel in a coupled state. Therefore, efficient transportation can be realized. In addition, according to this driving plan, since a single vehicle does not respond to a plurality of requests, a decrease in convenience for users can be suppressed. In other words, since each vehicle does not travel on a long-distance travel route to respond to all requests, a significant increase in transportation time can be suppressed. Therefore, according to the information processing device 1, a decrease in convenience can be suppressed while a decrease in transportation efficiency can be suppressed.
[0015] In the above description, the information processing device 1 having the configuration shown in Fig. 1 has been described, but the manner in which the above-mentioned effects are obtained is not limited to the device. For example, the same effects can be obtained in an information processing method including the above-mentioned processing of the information processing device 1, a program that performs the above-mentioned processing of the information processing device 1, or a non-transitory computer-readable medium on which the program is stored.
[0016] <Embodiment 2> First, an outline of the second embodiment will be described. In the mobility service realized by the second embodiment, remotely driven vehicles are used, which are vehicles that can be driven remotely using wireless communication and in which a plurality of vehicles can be physically or logically connected. The remotely driven vehicles may be owned or rented by a user, or may be owned by a transportation service provider (transport business operator). The mobility service realized by the second embodiment generally operates as follows.
[0017] 1. The reservation server 15 accepts reservation requests from passengers, including information on boarding and disembarking points, and the time of use of the mobility service, and creates a driving plan (i.e., vehicle allocation and a driving route including time information) to meet the request. 2. A driver is assigned to the driving plan. The driver remotely drives the assigned vehicle via wireless communication. When multiple vehicles are connected, one driver virtually drives the connected vehicles as if they were one vehicle. 3. If there is commonality (or similarity) in the travel routes and times between multiple reservation requests, the reservation server 15 outputs a travel plan that includes travel with multiple vehicles coupled together.
[0018] According to such a mobility service, multiple vehicles operate in a coupled state in sections where the route is shared, and operate in a separate state in other sections. Therefore, only one driver needs to perform driving duties in sections where multiple vehicles operate in a coupled state. This makes it possible to suppress a decrease in transportation efficiency per driver. In addition, since this mobility service does not respond to multiple requests using one vehicle, it is possible to suppress a decrease in convenience for users. In other words, since one vehicle does not travel on a long, circuitous route to respond to each request, it is possible to suppress a significant increase in transportation time.
[0019] FIG. 2 shows an example of an area in which the mobility service according to the present embodiment is provided. The positional relationship of the elements shown in FIG. 2 is merely an example, and is not limited to the positional relationship shown in FIG. 2. The vehicles 11_1, 11_2, 11_3, and 11_4 are all remotely operated vehicles, and are vehicles that are driven according to the operation of a remote driver (not shown) located in another location. In the following description, when the vehicles 11_1, 11_2, 11_3, and 11_4 are mentioned without any particular distinction, they are simply referred to as the vehicles 11. In FIG. 2, four vehicles 11 are shown, but in providing this mobility service, the number of vehicles 11 may be two or more, and the number is not limited to four. In addition, in the area shown in FIG. 2, the home 90_A of user A, the home 90_B of user B, and the home 90_C of user C are located. In addition, when the homes 90_A, 90_B, and 90_C are mentioned without any particular distinction, they are simply referred to as the homes 90. In addition, in the area shown in FIG. 2, facilities 91_1, 91_2, and 91_3 are located as facilities that can be destinations for the user. When the facilities 91_1, 91_2, and 91_3 are mentioned without any particular distinction, they are simply referred to as the facility 91. The facility 91 is, for example, a government office, a supermarket, a clinic, and the like, but is not limited thereto. The home 90 and the facility 91 are specific examples of spots that are candidates for the start point (i.e., the boarding point) of the use of the vehicle 11 by the user or the end point (i.e., the disembarking point) of the use of the vehicle 11 in the area shown in FIG. 2. The spots are connected to each other by a road 93 through which the vehicle 11 can pass. Furthermore, in the area shown in FIG. 2, parking lots 92_1, 92_2, and 92_3 where the vehicle 11 can be parked are provided at locations connected to the road 93. When the parking lots 92_1, 92_2, and 92_3 are mentioned without any particular distinction, they are simply referred to as the parking lot 92. The numbers of spots such as the homes 90 and the facilities 91 and the number of parking lots 92 described above are merely examples, and are not limited to the numbers shown in FIG.
[0020] 3A and 3B are schematic diagrams showing the correspondence between the vehicle 11 and the driver 80. FIG. 3A is a schematic diagram showing the correspondence between the vehicle 11 and the driver 80 in a state where the vehicle 11 is not connected to other vehicles 11, that is, in a separated state. The vehicle 11 travels according to commands transmitted from the remote control device 12 by the driver 80 operating the remote control device 12. In the state shown in FIG. 3A, one driver can drive only one vehicle 11. FIG. 3B is a schematic diagram showing the correspondence between the vehicle 11 and the driver 80 in a state where multiple vehicles 11 (three vehicles 11 as an example here) are connected. These vehicles 11 travel as one virtual vehicle according to commands transmitted from one remote control device 12. In this state, one driver can simultaneously drive the multiple connected vehicles 11 by operating one remote control device 12.
[0021] For example, when vehicles 11 are connected using a physical coupler, the control target of the remote control device 12 is the leading vehicle 11, and the second and subsequent vehicles 11 following the leading vehicle 11 are towed by the preceding vehicle 11. Alternatively, the vehicles 11 may be connected by loading other vehicles 11 onto one vehicle 11, in which case the control target of the remote control device 12 is the vehicle 11 carrying the other vehicles 11. Furthermore, the connection of the vehicles 11 in this embodiment is not limited to physical connection, and may be logical connection such as platooning using vehicle-to-vehicle communication (Vehicle to Vehicle, V2V) or automatic tracking of a leading vehicle using camera image recognition. In these cases, the control target of the remote control device 12 is, for example, the leading vehicle 11. In this way, the connected vehicles 11 can move together in accordance with a single command from one remote control device 12.
[0022] 4 is a schematic diagram showing a configuration example of a mobility system 10 for realizing a mobility service according to the present embodiment. The mobility system 10 includes a vehicle 11, a remote control device 12, a user terminal 13, a driver terminal 14, and a reservation server 15. These components of the mobility system 10 are connected to each other via a network 16, which is a wireless or wired network. The network 16 is, for example, a fifth generation mobile communication network (5G), Wi-Fi (registered trademark), Ethernet (registered trademark), the Internet, etc., but is not limited to these.
[0023] The vehicle 11 is a remotely operated vehicle equipped with a function of traveling according to commands transmitted from a remote control device 12. The vehicle 11 may have built-in or connected sensors (camera, microphone, speedometer, accelerometer, etc.) and may have a function of transmitting the measurement results of the sensors to the remote control device 12 as monitoring information. In particular, the vehicle 11 has a function of traveling virtually as one vehicle when multiple vehicles 11 are connected together. The vehicle 11 is, for example, an electric vehicle (EV) or a gasoline engine vehicle. The mobility system 10 includes any number of vehicles 11.
[0024] The remote control device 12 is a device operated by a driver to remotely control the vehicle 11. The remote control device 12 includes an input device (e.g., an input device simulating the steering devices of the vehicle 11, such as a steering wheel, an accelerator, and a brake) and an output device (e.g., a display device simulating a window of the vehicle 11). The remote control device 12 also includes a function of converting an operation by the driver into an instruction (i.e., a control signal) to the vehicle 11 and transmitting it, and a function of receiving monitoring information transmitted from the vehicle 11 and outputting it to an output device. The remote control device 12 can be installed in any location, such as a control center that consolidates multiple remote control devices 12 and multiple drivers, or the driver's home. The mobility system 10 includes any number of remote control devices 12.
[0025] The user terminal 13 is a terminal (e.g., a smartphone, a tablet, a personal computer, etc.) operated by a user (passenger) of the mobility service provided by the mobility system 10. The user terminal 13 has a function of sending a reservation request to the reservation server 15 based on an operation from the user, and a function of receiving a reservation result output from the reservation server 15 and displaying the contents. The mobility system 10 includes any number of user terminals 13.
[0026] The driver terminal 14 is a terminal (e.g., a smartphone, a tablet, a personal computer, etc.) operated by the driver, and has a function of receiving allocation information notified from the reservation server 15 and displaying the contents. The driver terminal 14 may be incorporated in the same housing as the remote control device 12. The mobility system 10 includes any number of driver terminals 14.
[0027] The reservation server 15 is a server device (information processing device) that has a function of accepting a reservation request sent from the user terminal 13 and allocating a vehicle 11 and a driver to the reservation request in order to realize transportation according to the reservation request. The reservation server 15 corresponds to the information processing device 1 described above.
[0028] As shown in FIG. 4, the reservation server 15 includes a request acquisition unit 101, a driving plan creation unit 102, a linked driving plan creation unit 103, a driver assignment unit 104, an output unit 105, a map data storage unit 106, a driving plan data storage unit 107, and a driver schedule storage unit 108.
[0029] The request acquisition unit 101 acquires a reservation request transmitted from the user terminal 13. The request acquisition unit 101 is a component corresponding to the request acquisition unit 2 described above. The driving plan creation unit 102 creates a driving plan for the vehicle 11 that satisfies the conditions indicated in the acquired reservation request. The connected driving plan creation unit 103 creates a driving plan for driving the multiple vehicles 11 in a connected state based on multiple driving plans for multiple reservation requests. That is, the connected driving plan creation unit 103 corrects each of the multiple driving plans created by the driving plan creation unit 102 to a driving plan including connected driving. The connected driving plan creation unit 103 is a component corresponding to the connected driving plan creation unit 3 described above. When the similarity of the multiple reservation requests satisfies a predetermined criterion, the connected driving plan creation unit 103 creates a driving plan for each vehicle 11 so that the multiple vehicles 11 drive in a connected state in a partial driving section. Here, the multiple vehicles 11 to be connected are a group of vehicles 11 assigned to each reservation request. In this embodiment, as described later, the calculation of the similarity of reservation requests is performed by calculating the similarity of driving plans created based on the reservation requests. The driver allocation unit 104 assigns a driver to the created driving plan and creates a driver's schedule (hereinafter referred to as a driver schedule). In particular, the driver allocation unit 104 assigns one driver to drive a plurality of vehicles 11 collectively for a partial driving section where the vehicles 11 travel in a coupled state. The output unit 105 outputs the created driving plan and driver schedule to another device. The output unit 105 is a component corresponding to the output unit 4 described above.
[0030] The map data storage unit 106 stores map data for the area in which the mobility service is provided. The map data includes information on roads and information on spots that can be boarding and disembarking points. The map data is used for creating a driving plan, etc. The information on roads and each spot in FIG. 2 is an example of map data. The driving plan data storage unit 107 stores the created driving plan. The driver schedule storage unit 108 stores the created driver schedule.
[0031] FIG. 5 is a schematic diagram showing an example of driving plan data created by the driving plan creation unit 102. This figure shows the driving plans of each vehicle 11 scheduled for October 2, 2023. In this example, the driving plan of the vehicle 11_1 is as follows. According to this driving plan, the vehicle 11_1 departs from the parking lot 92_2 in front of the user A's home 90_A after 8:00 and arrives at the parking lot 92_3 in front of the facility 91_1 before 9:00. After that, the vehicle 11_1 parks in the parking lot 92_3 until after 9:00, and then transports the user A to the parking lot 92_2 at 10:00. In this example, the driving plan of the vehicle 11_2 is as follows. According to this driving plan, the vehicle 11_2 departs from the parking lot 92_1 at 8:50, picks up the user B in front of the user B's home 90_B, and picks up the user B. Thereafter, vehicle 11_2 arrives at facility 91_3 at 10:20 to drop off user B, and is driven back to arrive at parking lot 92_1 at 10:55. The travel plan thus includes the departure point of vehicle 11, the start point of use of the user (boarding point), the end point of use of the user (drop-off point), and the end point of vehicle 11, as well as the departure time from the departure point, the start time of use of the user, the end time of use of the user, and the arrival time at the end point. Note that the departure point of vehicle 11 and the start point of use of the user may be the same. Also, the end point of use of the user and the end point of vehicle 11 may be the same.
[0032] Fig. 6 is a schematic diagram showing an example of a driving route recorded as a part of the driving plan data. The driving route shown in Fig. 6 corresponds to the driving plan for the vehicle 11_2 in the driving plan shown in Fig. 5, and shows a series of driving routes from the parking lot 92_1 to the front of the home 90_B of the user B, via the facility 91_3, and back to the parking lot 92_1.
[0033] FIG. 7 is a schematic diagram showing an example of a driver schedule created by the driver allocation unit 104. The driver schedule shown in this figure corresponds to the driving plan data shown in FIG. 5 and FIG. 6. FIG. 7 shows that a driver A is assigned to driving the vehicle 11_1. That is, the driver A remotely drives the vehicle 11_1, thereby realizing the driving from when the vehicle 11_1 leaves the parking lot 92_2 to when it arrives at the parking lot 92_3, and the driving from when the vehicle 11_1 leaves the parking lot 92_3 to when it arrives at the parking lot 92_2. FIG. 7 also shows that a driver B is assigned to driving the vehicle 11_2. That is, the driver B remotely drives the vehicle 11_2, thereby realizing the driving from when the vehicle 11_2 leaves the parking lot 92_1, to when it returns to the parking lot 92_1 via the front of the home 90_B and the facility 91_3.
[0034] Next, the operation of the reservation server 15 will be specifically described. The explanation will be given on the premise that the locations of the spots and roads are as shown in Fig. 2. Also, here, an example of processing will be shown in the case where the reservation server 15 accepts a new reservation request in a state in which the driving plan and driver schedule shown in Figs. 5 to 7 have already been created.
[0035] [First step: getting a reservation request] This step is performed as processing of the request acquisition unit 101. The reservation request is information that requests transportation and specifies transportation conditions. Specifically, the reservation request includes an identifier (user ID) of a user requesting transportation, a start point (boarding point) of use of the vehicle 11, an end point (drop-off point) of use of the vehicle 11, and time information (at least one of the start time of use and the end time of use) regarding the time to use the vehicle 11. Here, the start time of use refers to the time of departure from the start point of use, i.e., the boarding point, and can also be called the boarding time. Furthermore, the end time of use refers to the target time to arrive at the end point of use, i.e., the drop-off point, and can also be called the drop-off time. The reservation request may further include other information. For example, the reservation request may include information indicating the number of passengers, and may include information indicating the desired type of vehicle 11. Furthermore, the reservation request may further include information indicating an allowable range of time fluctuation of the time specified as the time to use the vehicle 11. Specifically, for example, the reservation request may include information indicating an allowable range for a usage start time that is earlier than the time specified as the usage start time, and may include information indicating an allowable range for a usage end time that is later than the time specified as the usage end time. The reservation request is also referred to as request information. The request acquisition unit 101 acquires the reservation request by receiving the reservation request transmitted from the user terminal 13 via the network 16.
[0036] FIG. 8 is a diagram showing an example of a screen for inputting a reservation request, displayed on the user terminal 13. Typically, this screen is generated by an application program installed in the user terminal 13, or is generated by a Web browser according to data (more specifically, data in HTML (Hyper Text Markup Language) format, etc.) transmitted from the reservation server 15. Prior to displaying the screen for inputting a reservation request, a user authentication process may be performed. The screen shown in FIG. 8 shows an example of a screen displayed on the user terminal 13 of user C. In this screen, the home of user C (i.e., home 90_C) is specified as the boarding point, a supermarket corresponding to facility 91_2 is specified as the disembarking point, and 10:30 on October 2, 2023 is specified as the arrival time at the disembarking point (end of use time).
[0037] [Second step: Vehicle allocation and driving plan creation] This step is performed as processing by the driving plan creation unit 102. The driving plan creation unit 102 of the reservation server 15 creates a driving plan based on the reservation request acquired by the request acquisition unit 101. Specifically, the driving plan creation unit 102 selects a vehicle 11 to be assigned to the reservation request, and calculates a driving plan that satisfies the transportation conditions specified in the reservation request. Specifically, the driving plan creation unit 102 creates a driving plan including a driving route from a departure point to a destination point for the vehicle 11 assigned to the reservation request, and time information indicating the time when the driving will be performed.
[0038] Any method known in on-demand transportation can be used for the method of selecting the vehicle 11 and the method of calculating the driving plan in this step. Here, as an example, the driving plan creation unit 102 creates a driving plan according to the following rules. For the driving route, a route with the smallest expected value of the driving time from the use start point to the use end point is selected. The constraint conditions for the selection of the vehicle 11 are, for example, the following conditions. The selectable vehicles 11 are the vehicles 11 that can move to the use start point by the use start time, that are not reserved from the departure time of the departure point to the arrival time of the end point, that can move to the use end point by the use end time, and that satisfy the specified vehicle conditions. The specified vehicle conditions are the vehicle type conditions and the number of passengers conditions specified in the reservation request. If only the use end time (i.e., the target arrival time to arrive at the drop-off point) is specified in the reservation request, and the use start time is not specified, for example, the following time is set as the use start time. In this case, for example, the latest departure time from the use start point that allows the drop-off point to be reached by the target arrival time is used as the use start time. Note that an earlier time may be used as the start time of use. Also, if only the start time of use (i.e. the departure time from the boarding point) is specified in the reservation request and the end time of use is not specified, the following times, for example, are set as the end time of use. In this case, for example, the earliest time at which the boarding point can be departed from and the disembarking point can be reached is used as the end time of use. Note that a later time may be used as the end time of use. If there are multiple vehicles 11 that satisfy the constraint conditions, a vehicle 11 with other reservations for the same day may be selected with priority.
[0039] Fig. 9 is a schematic diagram showing an example of a driving plan created for a new reservation request. Fig. 9 shows an example of a driving plan created by the driving plan creation unit 102 when the request acquisition unit 101 acquires the new reservation request shown in Fig. 8 in a state in which the map data shown in Fig. 2 and the driving plan data shown in Fig. 5 are stored in the reservation server 15. In this example, the vehicles 11_1 and 11_2 have already been assigned to other reservation requests, and it is impossible to assign these vehicles to the reservation request shown in Fig. 8. For this reason, the driving plan creation unit 102 assigns the vehicle 11_3, which has not yet been reserved, to the new reservation request.
[0040] 9 includes information on the following driving routes (1) to (4) for the vehicle 11_3. Note that, here, it is assumed that a rule is preset for generating a driving plan for the vehicle 11_3 to forward the vehicle to the parking lot 92_1 after transporting passengers if no other reservation request is assigned to the vehicle 11_3. (1) At 9:00, the vehicle 11_3 leaves the parking lot 92_1 in which it had been parked, and heads to the home 90_C of the user C, which is designated as the starting point of use, to pick up the user C. (2) The vehicle 11_3 arrives in front of the house 90_C at 9:30, picks up the user C there, and starts transportation to the facility 91_2 (supermarket) which is the drop-off point (end point of use). (3) The vehicle 11_3 arrives at the facility 91_2 (supermarket) at 10:30, drops off the user C there, and starts its forwarding to the parking lot 92_1 which is the final destination. (4) Vehicle 11_3 arrives at parking lot 92_1 at 11:00 and parks there.
[0041] [Third step: Creating a driving plan including vehicle connections] This step is performed as processing of the linked driving plan creation unit 103. The linked driving plan creation unit 103 compares the driving plan created in the second step (hereinafter, for convenience, referred to as "driving plan A") with other driving plans already stored as driving plan data. Note that driving plan A may be called a target driving plan since it is a driving plan to be processed in this step. Then, when there is another driving plan that has commonality with driving plan A in driving route and driving timing (driving date and driving time zone), the linked driving plan creation unit 103 generates a driving plan including the coupling of the vehicles 11. The linked driving plan creation unit 103 updates (modifies) each driving plan that has commonality to a driving plan including the coupling of the vehicles 11. That is, the linked driving plan creation unit 103 updates the driving plan whose data is already stored in the driving plan data storage unit 107 and the driving plan corresponding to the new reservation request created in the second step to a driving plan including the coupling of the vehicles 11.
[0042] The concrete processing procedure of creating a driving plan including vehicle coupling by the joint driving plan creating unit 103 will be described below. First, the joint driving plan creating unit 103 refers to the date information (driving date) included in the driving plan A, and acquires all driving plans having the same driving date as the driving plan A among the driving plans whose data has already been stored in the driving plan data storage unit 107. Since each acquired driving plan is a candidate for a driving plan to be changed to a driving plan in which the vehicle 11 is coupled, hereinafter, it will be referred to as a candidate driving plan for coupling. Here, each acquired driving plan (candidate driving plan for coupling) is a series of driving plans from a starting point to a destination point for one vehicle 11. Note that the entire area in which the mobility service is provided may be divided into a plurality of sub-areas, and in this case, the joint driving plan creating unit 103 may acquire only driving plans for transportation within the same sub-area as the sub-area in which transportation by the driving plan A is performed.
[0043] Next, the linked driving plan creation unit 103 calculates the similarity between each of the linked candidate driving plans and the driving plan A. This calculates the similarity between the reservation request (request information) corresponding to the driving plan A and the reservation request (request information) corresponding to the linked candidate driving plans. Although various definitions are possible for the similarity, it is predefined so that the longer the common part of the driving route and the closer the driving time zone of the common driving route, the higher the similarity. Therefore, the calculated similarity can be said to be the similarity between the reservation requests for the driving route and driving time zone of the vehicle 11 to realize the transportation requested in the reservation request. When calculating the similarity between the driving plan A and the linked candidate driving plans, the linked driving plan creation unit 103 may change a part of the driving route by allowing the driving time to extend within a predetermined range in either or both of the driving plan A and the linked candidate driving plans. In other words, the linked driving plan creation unit 103 may modify the driving route so that a common section occurs in the driving route. In addition, when calculating the similarity, the linked driving plan creation unit 103 may change the driving time zone within a predetermined tolerance range in either or both of the driving plan A or the candidate linked driving plan. If the user specifies a tolerance range for time variation in the reservation request, the driving route or driving time zone may be changed within this tolerance range. In this way, the linked driving plan creation unit 103 may correct the driving route or driving time zone when driving without coupling with other vehicles 11 within a predetermined tolerance range, and calculate the similarity using the corrected driving route or driving time zone. This makes it possible to realize many linked driving runs, and further improve transportation efficiency. The above-mentioned predetermined tolerance range may be, for example, a tolerance range of a deviation from the distance of the shortest route, or a tolerance range of a deviation from a specified or set time.
[0044] After calculating the similarity, the joint driving plan creation unit 103 modifies each pair of the driving plan A and the joint candidate driving plan, whose similarity is equal to or greater than a predetermined threshold, to a driving plan including the coupling of the vehicle 11. That is, the joint driving plan creation unit 103 creates a driving plan in which the vehicle 11 travels in a state in which the vehicle 11 is coupled in a common driving section. When there are a plurality of joint candidate driving plans whose similarity with the driving plan A is equal to or greater than a threshold, the joint driving plan creation unit 103 may create a driving plan including the coupling of the vehicle 11 for the joint candidate driving plan having the highest similarity among the joint candidate driving plans. When the driving route or the driving time zone is changed during the calculation of the similarity, the joint driving plan creation unit 103 creates a driving plan that reflects the change and includes the coupling of the vehicle 11. When changing the driving route or the driving time zone during the calculation of the similarity, the allowable range of change may be set to be larger in a section in which no passengers are picked up (a pick-up section or a non-delivery section) than in a section in which passengers are transported. In other words, the tolerance range for the travel section in which the vehicle 11 travels when the vehicle 11 does not have a transportation object (a person in this embodiment) on board may be larger than the tolerance range for the travel section in which the vehicle 11 travels when the vehicle 11 has the transportation object on board. This can suppress the impact on users. In this way, the tolerance of the deviation amount of the travel route and the tolerance of the deviation amount of the travel time zone may differ depending on whether the section is a boarding section or not. In addition, in creating a travel plan including coupling of the vehicles 11, constraint conditions such as a combination of vehicles that can be coupled and a maximum number of vehicles that can be coupled may be set. In this case, the coupled travel plan creation unit 103 creates a travel plan including coupling of the vehicles 11 so as to satisfy the constraint conditions.
[0045] Here, we will explain driving plans including coupling between vehicles 11_2 and 11_3 using as examples the driving plan for vehicle 11_2 shown in Figure 6 (corresponding to the above-mentioned coupling candidate driving plan) and the driving plan for vehicle 11_3 shown in Figure 9 (corresponding to the above-mentioned driving plan A).
[0046] The driving plans shown in FIG. 6 and FIG. 9 are both scheduled for travel from 9:00 to 11:00 on October 2, 2023, and include a partially common section in the travel route. Therefore, the similarity between the two is high, and both are targets for creating a driving plan including coupling. Here, for example, if a section that does not transport passengers is preferentially set as a coupling section, a part of the pick-up section from leaving the parking lot 92_1 to the home 90_B or home 90_C and a part of the forwarding section from dropping off passengers to returning to the parking lot 92_1 will be the driving section in the coupled state.
[0047] FIG. 10 is a schematic diagram showing an example of a driving plan created by the coupled driving plan creating unit 103. Here, a driving plan is created in which the vehicles 11_2 and 11_3 travel in a coupled state on a route 71a from the parking lot 92_1 to point A (an intermediate point for picking up the vehicle) and on a route 71b from point B (an intermediate point for forwarding the vehicle) to the parking lot 92_1. In the figure, the route 72 indicates a route on which the vehicle 11_2 travels alone, and the route 73 indicates a route on which the vehicle 11_3 travels alone. For this example, driving plan data expressed in the same format as the driving plan data shown in FIG. 5 is shown in FIG. 11. In FIG. 5, a driving plan for the vehicle 11_2 alone was created, whereas in FIG. 11, the driving plan is updated so that the vehicles 11_2 and 11_3 travel in a coupled state in some sections for picking up the vehicle and forwarding the vehicle.
[0048] [Fourth step: Driver assignment] This step is performed as processing by the driver allocation unit 104. The driver allocation unit 104 allocates a driver who remotely drives the vehicle 11 to the driving plan created in the second step or the third step. As a constraint condition for driver allocation, the driver to be allocated must be a driver who has not been allocated to another driving plan whose driving date and driving time period overlap with the driving plan to be allocated. If there is no driver who satisfies this condition, the processing of the reservation request acquired in the first step fails, and the driving plan data for the created driving plan is not stored. Note that, if the driving plan data has already been stored before this step, a rollback to the state before storage is performed. The driver allocation unit 104 determines a driver to be allocated to the driving plan from among the drivers who satisfy the constraint condition according to a predetermined priority. Any priority standard can be used. As an example, the driver allocation unit 104 preferentially selects a driver who is allocated to another driving plan on the same day, unless the availability rate (the time allocated to driving out of the total working hours) meets a predetermined value. When the driver allocation is successful, the driver allocation unit 104 stores the driving schedule in the driver schedule storage unit 108. In addition, the linked driving plan creation unit 103 or the driving plan creation unit 102 stores driving plan data for the created driving plan in the driving plan data storage unit 107.
[0049] An example of driver allocation results for the specific driving plan shown in Fig. 11 is shown in Fig. 12. Compared with the driving schedule (Fig. 7) before creating a driving plan including vehicle coupling, the driving schedule shown in Fig. 12 differs from the driving schedule in Fig. 7 in the following points. In the driving schedule shown in Fig. 12, the driving of the vehicle 11_3 is assigned to the driver C. Also, in the driving schedule shown in Fig. 12, the schedule of the driver B assigned to the vehicle 11_2 is changed to a schedule in which the driver B drives the vehicles 11_2 and 11_3 in a coupled state in a partial driving section.
[0050] [Fifth step: Output of driving plan] This step is performed as a process of the output unit 105. When the driver allocation is successful in the fourth step, the output unit 105 notifies the user terminal 13, which is the transmission source of the reservation request, of the successful reservation as a response to the reservation request acquired in the first step. In addition, the output unit 105 outputs the driving plan (driving plan data) to an arbitrary device. The output unit 105 may transmit the driving plan data to the driver terminal 14 of the driver to whom the driving plan indicated in this data is assigned, or may transmit it to another device that manages operation. In addition, the output unit 105 may transmit the driving plan data to the user terminal 13, which is the transmission source of the reservation request. In addition, the output unit 105 notifies the driver terminal 14 of the driver corresponding to the driver schedule at a predetermined timing. The notification timing can be set arbitrarily. As an example, the driving schedule of the driver assigned to the next day's driving plan is notified to the driver terminal 14 once a day. Of course, the output unit 105 may notify the driver terminal 14 of the driver schedule immediately at the time when the driving plan is confirmed. When the driver's terminal 14 receives the driving schedule, it displays information such as that shown in FIG.
[0051] The reservation server 15 may provide a function that allows the user or the driver to negotiate with the reservation server 15 before the reservation is confirmed. For example, if the available travel time does not meet the conditions of the time specified by the user in the reservation request, the reservation server 15 may send an inquiry notice to the user terminal 13 to inquire of the user whether or not to make a reservation for transportation at the available travel time. Then, the reservation server 15 may make a reservation for such transportation only when a response to the effect that the reservation is made is received from the user terminal 13, that is, when the user agrees. That is, the reservation server 15 may create a travel plan for such transportation as a finalized version of the travel plan. Also, if the travel date and time specified in the reservation request and the transmission date and time of the reservation request itself are close to each other, the reservation server 15 may send the following notification. In this case, the reservation server 15 may send an inquiry notice to the driver terminal 14 to inquire of the driver to whom the travel plan corresponding to this reservation request is assigned whether or not to make the reservation. For example, if the travel date specified in the reservation request and the transmission date of the reservation request itself are the same day, the reservation server 15 may send an inquiry notification to the driver terminal 14. Then, the reservation server 15 may establish the reservation only when a response to the effect that the reservation is established is obtained from the driver terminal 14, that is, when the driver agrees. In other words, the reservation server 15 may create a finalized driver schedule.
[0052] The output unit 105 may output information to assist the driver who drives the vehicle 11 during the travel of the vehicle 11 to a device used by the driver (for example, the remote control device 12). In particular, the output unit 105 may output information on the vehicle 11 to be coupled to the vehicle 11 driven by the driver based on a travel plan. This makes it easier for the driver to recognize the coupled vehicle 11. For example, as shown in FIG. 14, the output unit 105 may output information to identify the coupled vehicle 11 to the vehicle 11 driven by the driver on a navigation screen. Specifically, in FIG. 14, a display is provided on a navigation screen (for example, a screen displayed on the remote control device 12) for the driver who drives the vehicle 11_2 to identify the coupled vehicle 11_3 in front of the vehicle 11_2 driven by the driver. It is preferable that the display to identify the coupled vehicle is an emphasized display to attract the driver's attention. The information on the vehicle 11 output by the output unit 105 may be information indicating the external characteristics of the coupled vehicle 11.
[0053] The second embodiment has been described above. According to this embodiment, a plurality of vehicles 11 can be driven in a coupled state in a section that shares a common route. Then, according to this embodiment, only one driver is assigned to the driving of the plurality of vehicles 11 in such a section. Therefore, only one driver needs to perform driving duties in such a section. Therefore, efficient transportation can be realized. Also, since each vehicle 11 does not need to drive on a long route, an increase in transportation time can be prevented. Therefore, according to this embodiment, it is possible to suppress a decrease in convenience while suppressing a decrease in transportation efficiency.
[0054] The above-mentioned functions (processing) of the remote control device 12, the user terminal 13, the driver terminal 14, or the reservation server 15 may be realized by a computer 500 having the following configuration, for example.
[0055] 15 is a block diagram showing the configuration of a computer 500 that realizes the processing of the remote control device 12, the user terminal 13, the driver terminal 14, or the reservation server 15. As shown in FIG. 15, the computer 500 includes a memory 501 and a processor 502.
[0056] The memory 501 is configured, for example, by a combination of a volatile memory and a non-volatile memory. The memory 501 is used to store programs executed by the processor 502, data used for various processes, and the like. The map data storage unit 106, the driving plan data storage unit 107, and the driver schedule storage unit 108 may be realized by the memory 501. However, these may be realized by any other storage device.
[0057] The processor 502 reads out and executes programs from the memory 501 to perform processing of each device. The processor 502 may be, for example, a microprocessor, a microprocessor unit (MPU), or a central processing unit (CPU). The processor 502 may include multiple processors.
[0058] The program includes a set of instructions (or software code) that, when loaded into a computer, causes the computer to perform one or more functions described in the embodiments. The program may be stored in a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, the computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disk or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, the transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.
[0059] The present invention is not limited to the above-described embodiment, and can be modified as appropriate without departing from the spirit of the present invention. For example, the object of transportation does not have to be a user, but may be cargo designated by a user, or may be both a user and cargo. When the object of transportation includes cargo, the reservation server 15 may also create a plan for the schedule of personnel or robots in charge of loading the cargo onto the vehicle 11 and unloading the cargo from the vehicle 11. The above-described reservation server 15 may also be used for a driving service that drives the vehicle 11 managed by the user instead of an on-demand transportation service.
[0060] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes. (Appendix 1) a request acquisition unit that acquires request information transmitted from a user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; a connected driving plan creation unit that creates a driving plan for each of the vehicles so that the vehicles, which are assigned to each of the request information, travel in a connected state in a partial travel section when the similarity of the plurality of pieces of request information satisfies a predetermined criterion; and an output unit that outputs the travel plan; An information processing device having the above configuration. (Appendix 2) The vehicle is a vehicle remotely operated by a driver. 2. An information processing device according to claim 1. (Appendix 3) a driver allocation unit that allocates one driver to collectively drive the plurality of vehicles to the partial travel section along which the plurality of vehicles travel in a coupled state; 3. The information processing device according to claim 1 or 2, further comprising: (Appendix 4) The degree of similarity is a degree of similarity between the request information regarding a travel route of the vehicle and a travel time period of the vehicle for realizing the transportation requested in the request information. 4. The information processing device according to claim 1 . (Appendix 5) The joint driving plan creation unit modifies, within a predetermined allowable range, the driving route or the driving time zone in a case where the vehicle is driven without being connected to another vehicle, and calculates the similarity between the request information using the modified driving route or the driving time zone. 5. The information processing device according to claim 4. (Appendix 6) The predetermined tolerance range for a travel section on which the vehicle travels when the transportation object is not on board the vehicle is larger than the predetermined tolerance range for a travel section on which the vehicle travels when the transportation object is on board the vehicle. 6. The information processing device according to claim 5. (Appendix 7) The output unit further outputs information about a vehicle to be connected to the vehicle to a device used by a driver of the vehicle. 7. An information processing device according to any one of claims 1 to 6. (Appendix 8) An information processing device, Acquire request information transmitted from the user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; If the similarity between the plurality of pieces of request information satisfies a predetermined criterion, a travel plan is created for each of the vehicles so that the plurality of vehicles, which are assigned to each of the pieces of request information, travel in a connected state in a partial travel section; Output the driving plan Information processing methods. (Appendix 9) a request acquisition step of acquiring request information transmitted from a user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; a coupled driving plan creation step of creating a driving plan for each of the vehicles assigned to each of the request information so that the vehicles travel in a coupled state in a partial driving section when the similarity of the plurality of pieces of request information satisfies a predetermined criterion; An output step of outputting the driving plan; A program that causes a computer to execute the following. [Explanation of symbols]
[0061] 1. Information processing device 2. Request Acquisition Unit 3. Joint Driving Planning Department 4 Output section 10 Mobility Systems 11 Vehicles 12 Remote Control Device 13 User terminal 14 Driver's terminal 15 Reservation Server 16 Network 101 Request Acquisition Unit 102 Driving Plan Creation Department 103 Joint Driving Planning Department 104 Driver Allocation Department 105 Output section 106 Map data storage unit 107 Driving plan data storage unit 108 Driver schedule memory unit 500 Computers 501 Memory 502 processor
Claims
1. a request acquisition unit that acquires request information transmitted from a user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; a connected driving plan creation unit that creates a driving plan for each of the vehicles so that the vehicles, which are assigned to each of the request information, travel in a connected state in a partial travel section when the similarity of the plurality of pieces of request information satisfies a predetermined criterion; an output unit that outputs the travel plan; An information processing device having the above configuration.
2. The vehicle is a vehicle remotely operated by a driver. The information processing device according to claim 1 .
3. a driver allocation unit that allocates one driver to collectively drive the plurality of vehicles to the partial travel section along which the plurality of vehicles travel in a coupled state; The information processing device according to claim 1 or 2, further comprising:
4. The degree of similarity is a degree of similarity between the request information regarding a travel route of the vehicle and a travel time period of the vehicle for realizing the transportation requested in the request information. The information processing device according to claim 1 .
5. The joint driving plan creation unit modifies, within a predetermined allowable range, the driving route or the driving time period in a case where the vehicle is driven without being connected to another vehicle, and calculates the similarity between the request information using the modified driving route or the driving time period. The information processing device according to claim 4.
6. The predetermined tolerance range for a travel section on which the vehicle travels when the transportation object is not on board the vehicle is larger than the predetermined tolerance range for a travel section on which the vehicle travels when the transportation object is on board the vehicle. The information processing device according to claim 5 .
7. The output unit further outputs information about a vehicle to be connected to the vehicle to a device used by a driver of the vehicle. The information processing device according to claim 1 .
8. An information processing device, Acquire request information transmitted from the user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; If the similarity between the plurality of pieces of request information satisfies a predetermined criterion, a travel plan is created for each of the vehicles so that the plurality of vehicles, each of which is assigned to each piece of request information, travels in a connected state in a partial travel section; Output the driving plan Information processing methods.
9. a request acquisition step of acquiring request information transmitted from a user terminal, the request information including a start point of use of the vehicle, an end point of use of the vehicle, and a time of use of the vehicle; a coupled driving plan creation step of creating a driving plan for each of the vehicles assigned to each of the request information so that the vehicles travel in a coupled state in a partial driving section when the similarity of the plurality of pieces of request information satisfies a predetermined criterion; An output step of outputting the driving plan; A program that causes a computer to execute the following.
Citation Information
Patent Citations
System and method for adjusting personal traffic
JP1998241091A
