TRANSPORTATION SERVICE MANAGEMENT DEVICE, TRANSPORTATION SERVICE MANAGEMENT METHOD, AND TRANSPORTATION SERVICE MANAGEMENT PROGRAM

Abstract

To smoothly provide transportation services by vehicles.SOLUTION: A prediction unit 101 predicts demand for transportation services by vehicles for each time period, and extracts a time period during which it is predicted that the number of secured vehicles, which are vehicles secured for providing the transportation service, cannot meet the demand for the transportation service, as a shortage time period. A search unit 102 searches for supplementary vehicles, which are vehicles capable of providing the transportation services during the shortage time period, from vehicles other than the secured vehicles. A requesting unit 103 requests the supplementary vehicle to provide the transportation service during the shortage time period.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to managing transportation services using vehicles. [Background technology]

[0002] 2. Description of the Related Art As a transportation service using a vehicle, there is an on-demand transportation service in which a service user (hereinafter, also simply referred to as a user) can use a vehicle when necessary. Patent Document 1 discloses a technology relating to an on-demand transportation service. In on-demand transport services, users use an application to reserve the date and time of use and the boarding and disembarking locations. On-demand transport services are expected to be used for transporting elderly people and pregnant women who do not have transportation to hospitals, utilizing roadside stations, transporting agricultural products to roadside stations, etc. It is thought that use in rural areas (mountainous areas, etc.) will be particularly effective. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2021-18694 A Summary of the Invention [Problem to be solved by the invention]

[0004] Transportation service providers secure vehicles to provide services, but the demand for transportation services fluctuates from moment to moment. For this reason, it is difficult to flexibly match the number of vehicles to the fluctuations in demand. As a result, there is a problem that a sufficient number of vehicles cannot be secured during the time period when a user wants to use the service, and the user may give up using the service.

[0005] One of the main objectives of the present disclosure is to solve the above-mentioned problems. Specifically, the main objective of the present disclosure is to smoothly provide vehicle transportation services by flexibly replenishing vehicles. [Means for solving the problem]

[0006] A transportation service management device according to the present disclosure includes: Predicting the demand for vehicle transportation services by time period Confirmation that the vehicle is under the control of the transportation service operator A prediction unit that extracts a time period in which it is predicted that the number of vehicles in the fleet cannot meet the demand for the transportation service as a shortage time period; a search unit that searches for a replacement vehicle that can provide the transportation service during the shortage time period from among vehicles other than the reserved vehicles; and a request unit that requests the replenishment vehicle to provide the transportation service during the shortage time period. Effect of the Invention

[0007] According to the present disclosure, vehicles can be replenished promptly, and vehicle transportation services can be smoothly provided. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration according to a first embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of a hardware configuration of a transportation service management device according to the first embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of a functional configuration of a transportation service management device according to the first embodiment. [Figure 4] 4 is a flowchart showing an overview of the operation of the transportation service management device according to the first embodiment. [Diagram 5] 5 is a flowchart showing details of the operation of the transportation service management device according to the first embodiment. [Figure 6] 4A to 4C are diagrams showing examples of a demand vehicle number table, a secured vehicle number table, and a shortage vehicle number table according to the first embodiment. [Figure 7] 5 is a flowchart showing details of the operation of the transportation service management device according to the first embodiment. [Figure 8] FIG. 4 is a diagram showing an example of a recruitment message according to the first embodiment. [Figure 9]FIG. 4 is a diagram showing an example of a response message according to the first embodiment. [Figure 10] FIG. 4 is a diagram showing an example of a replenishment vehicle number table according to the first embodiment. [Figure 11] 5 is a flowchart showing details of the operation of the transportation service management device according to the first embodiment. [Figure 12] FIG. 4 is a diagram showing an example of a transportation request message according to the first embodiment. [Figure 13] FIG. 4 is a diagram showing an example of a request message according to the first embodiment. [Figure 14] FIG. 4 is a diagram showing an example of an acceptance message according to the first embodiment. [Figure 15] FIG. 4 is a diagram showing an example of a vehicle dispatch confirmation message according to the first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the embodiments will be described with reference to the drawings. In the following description of the embodiments and in the drawings, the same reference numerals denote the same or corresponding parts.

[0010] Embodiment 1 ***Configuration Description*** FIG. 1 shows an example of a system configuration according to the present embodiment. The transportation service management device 100 performs operations for realizing transportation services using vehicles. More specifically, the transportation service management device 100 performs operations such as predicting demand for transportation services, replenishing vehicles according to demand, accepting vehicle allocation requests, and arranging vehicle allocation. The transportation service management device 100 is a server device used by a transportation service provider or a contractor of the transportation service provider. A transportation service provider is a company that provides on-demand transportation services using vehicles. In the present embodiment, the transportation service refers to on-demand transportation services using vehicles.

[0011] The operation procedure of the transportation service management device 100 corresponds to a transportation service management method. Also, a program that realizes the operation of the transportation service management device 100 corresponds to a transportation service management program.

[0012] The transportation service management device 100 is connected to a roadside device 301, an ETC antenna 302, and a wireless base station device 303 via a network 200. ETC is an abbreviation for "Electronic Toll Collection System" and is a registered trademark.

[0013] The network 200 is, for example, the Internet. Although not shown in the figure, the network 200 includes mechanisms such as a mail server and a DNS (Domain Name System) server for the transportation service management device 100 to transmit and receive communication messages to and from the roadside device 301, the ETC antenna 302, and the wireless base station device 303.

[0014] The roadside unit 301 is disposed on a roadway and is capable of wireless communication with a communication device 501 mounted on a vehicle 401 by, for example, Dedicated Short Range Communication (DSRC). Although only one roadside unit 301 is shown in FIG. 1, a plurality of roadside units 301 exist in a plurality of areas. The roadside unit 301 relays communication messages between the transportation service management apparatus 100 and the communication device 501 . The roadside device 301 corresponds to a communication device.

[0015] The ETC antenna 302 is an antenna placed in an ETC lane. The ETC antenna 302 is also capable of wireless communication with a communication device 501 mounted on the vehicle 401 by, for example, DSRC. Although only one ETC antenna 302 is shown in FIG. 1, multiple ETC antennas 302 exist in multiple areas. The ETC antenna 302 also relays communication messages between the transportation service management apparatus 100 and the communication device 501 . The ETC antenna 302 also corresponds to a communication device.

[0016] The wireless base station device 303 is, for example, a communication facility installed by a mobile phone service provider. Although only one wireless base station device 303 is shown in FIG. 1, a plurality of wireless base station devices 303 exist in a plurality of areas. The wireless base station device 303 is capable of wireless communication with a mobile terminal 502 carried by the vehicle manager 402 and a mobile terminal 502 carried by the service user 600 . The wireless base station device 303 relays communication messages between the transportation service management device 100 and the mobile terminal 502 . In addition, the wireless base station device 303 is also capable of wireless communication with the communication device 501 installed in the vehicle 401. However, for the sake of simplicity of explanation, in this embodiment, it is assumed that the wireless base station device 303 performs wireless communication only with the mobile terminal 502.

[0017] Vehicle 401 is a vehicle other than the reserved vehicle. A reserved vehicle is a vehicle that is reserved by a transportation service provider in order to provide transportation services. In other words, a reserved vehicle is a vehicle that is under the control of the transportation service provider and is obligated to provide transportation services according to the instructions of the transportation service provider. On the other hand, the vehicle 401 is a vehicle that is not under the control of a transportation service provider and is not obligated to provide transportation services. The vehicle 401 is also called a general vehicle. The vehicle 401 is equipped with a communication device 501 capable of wireless communication with the roadside device 301 and the ETC antenna 302. The communication device 501 is, for example, an ETC vehicle-mounted unit or a car navigation device. A mobile terminal 502 can also be used as the communication device 501.

[0018] The vehicle manager 402 is a person who manages the vehicle 401. The vehicle manager 402 is, for example, an individual or a company that owns the vehicle 401. The vehicle manager 402 does not need to own the vehicle 401, but only needs to have the authority to decide whether or not to use the vehicle 401 as a replacement vehicle, which will be described later.

[0019] In addition, some of the vehicle managers 402 have agreed in advance with the transportation service provider to use their own vehicles as replacement vehicles. Vehicles managed by such vehicle managers 402 are called replacement candidate vehicles. Replacement candidate vehicles are vehicles that are candidates for replacement vehicles. Such a vehicle manager 402 has already registered the communication address of his / her mobile terminal 502 in the transportation service management device 100. Therefore, even if the vehicle manager 402 is outside the vehicle 401, the transportation service management device 100 can send a recruitment message 701 (described later) to the mobile terminal 502 by using the registered communication address. The mobile terminal 502 is, for example, a smartphone. In this embodiment, for the sake of simplicity, it is assumed that the vehicle manager 402 inside the vehicle 401 has not agreed to use the vehicle 401 as a refill vehicle, and that the vehicle manager 402 outside the vehicle has agreed to use his or her own vehicle as a refill vehicle. The vehicle manager 402 may also be simply called the manager.

[0020] A service user 600 is a person who wishes to use a transportation service. It is assumed that the service user 600 also carries a mobile terminal 502 .

[0021] The method of communication between the transportation service management device 100 and the vehicle manager 402 or the service user 600 is not limited to that shown in FIG. For example, the transportation service management device 100 may communicate with the vehicle manager 402 or the service user 600 using other communication means such as a wired communication network or a Wi-Fi access point instead of the wireless base station device 303. Moreover, the vehicle manager 402 or the service user 600 may use a PC (Personal Computer) or the like instead of the mobile terminal 502.

[0022] The recruitment message 701 is a communication message notifying that vehicles capable of providing transportation services are being recruited. The recruitment message 701 is transmitted when the transportation service management device 100 predicts the demand for transportation services and determines that the demand cannot be met by the reserved vehicles alone. The recruitment message 701 is transmitted from the transportation service management device 100 to the communication device 501 or the mobile terminal 502 of the vehicle manager 402 via the roadside unit 301 , the ETC antenna 302 or the wireless base station device 303 . The recruitment message 701 is, for example, an email, a short message, or the like.

[0023] The response message 702 is a communication message responding to the recruitment message 701. In other words, the response message 702 is a communication message notifying that a transportation service is available. The response message 702 is transmitted from the communication device 501 or the mobile terminal 502 of the vehicle manager 402 to the transportation service management device 100 via the roadside device 301 , the ETC antenna 302 or the wireless base station device 303 . The response message 702 is, for example, an email, a short message, or the like.

[0024] The request message 703 is a communication message requesting the provision of a transportation service. The request message 703 is transmitted from the transportation service management apparatus 100 to the communication device 501 or the mobile terminal 502 of the vehicle manager 402 via the roadside unit 301 , the ETC antenna 302 or the wireless base station apparatus 303 . The request message 703 is, for example, an e-mail or a short message.

[0025] The acceptance message 704 is a communication message responding to the request message 703. In other words, the response message 702 is a communication message notifying that the provision of the transportation service has been accepted. The acceptance message 704 is transmitted from the communication device 501 or the mobile terminal 502 of the vehicle manager 402 to the transportation service management device 100 via the roadside device 301 , the ETC antenna 302 or the wireless base station device 303 . The acceptance message 704 may be, for example, an email, a short message, or the like.

[0026] The transportation request message 705 is a communication message that requests the provision of a transportation service. In other words, the transportation request message 705 is a communication message that requests the dispatch of a vehicle. The transportation request message 705 is transmitted from the mobile terminal 502 of the service user 600 to the transportation service management device 100 via the wireless base station device 303 . The transportation request message 705 is, for example, an email, a short message, or the like.

[0027] The dispatch confirmation message 706 is a communication message that confirms the provision of a transportation service, i.e., that a vehicle will be dispatched. The dispatch confirmation message 706 is transmitted from the transportation service management device 100 to the mobile terminal 502 of the service user 600 via the wireless base station device 303 . The dispatch confirmation message 706 may be, for example, an email, a short message, or the like.

[0028] FIG. 2 shows an example of a hardware configuration of the transportation service management device 100 according to the present embodiment. FIG. 3 shows an example of a functional configuration of the transportation service management device 100 according to the present embodiment. First, an example of the hardware configuration of the transportation service management device 100 will be described with reference to FIG.

[0029] The transportation service management device 100 according to this embodiment is a computer. The transportation service management device 100 includes, as hardware, a processor 901, a main memory device 902, an auxiliary memory device 903, and a communication device 904. 3, the transportation service management device 100 includes, as functional components, a prediction unit 101, a search unit 102, a request unit 103, a communication unit 104, and a database 105. Among these, the functions of the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104 are realized, for example, by a program. The auxiliary storage device 903 stores programs for implementing the functions of the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104. These programs are loaded from the auxiliary storage device 903 to the main storage device 902. Then, the processor 901 executes these programs to perform the operations of a prediction unit 101, a search unit 102, a request unit 103, and a communication unit 104, which will be described later. FIG. 3 shows a schematic state in which a processor 901 is executing programs that realize the functions of the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104. In FIG. The database 105 is realized by, for example, the auxiliary storage device 903 .

[0030] Next, an example of a functional configuration of the transportation service management device 100 will be described with reference to FIG.

[0031] The prediction unit 101 predicts the demand for transportation services for each time period in each of a plurality of regions. Then, the prediction unit 101 extracts time periods and areas where it is predicted that the number of reserved vehicles will not be enough to meet the demand for transportation services as shortage time periods and shortage areas. The process performed by the prediction unit 101 corresponds to a prediction process.

[0032] The search unit 102 searches for a replenishment vehicle that can provide transportation services during the shortage time period for each shortage area from among the vehicles 401 other than the reserved vehicles. The process performed by the search unit 102 corresponds to a search process.

[0033] The request unit 103 requests the reserved vehicle or the replenishment vehicle to provide a transportation service to the service user 600. In a shortage area and shortage time period, the request unit 103 requests the provision of transportation services from replenishment vehicles, giving priority to secured vehicles. The process performed by the request unit 103 corresponds to a request process.

[0034] The communication unit 104 transmits and receives a recruitment message 701 , a response message 702 , a request message 703 , an acceptance message 704 , a transportation request message 705 , and a vehicle dispatch confirmation message 706 to and from the network 200 .

[0035] The database 105 stores various data. For example, the database 105 stores the communication address of the mobile terminal 502 . Moreover, the database 105 stores various tables, which will be described later. The database 105 also stores the area in which each roadside device 301 is located. Similarly, the database 105 stores the area in which each ETC antenna 302 is located. Similarly, the database 105 stores the area in which each wireless base station device 303 is located.

[0036] ***Explanation of Operation*** FIG. 4 shows an overview of the operation of the transportation service management device 100 according to the present embodiment.

[0037] First, in step S11, the prediction unit 101 predicts the demand for the transportation service for each region and time period. That is, the prediction unit 101 predicts the number of vehicles in demand, which is the number of vehicles required to provide the transportation service, for each region and time period. Then, the prediction unit 101 extracts shortage areas and shortage time slots where the number of secured vehicles is less than the number of demanded vehicles. In this embodiment, for the sake of simplicity, the "time period" is set to a unit of 15 minutes. The prediction unit 101 predicts the demand for each "time period" 15 minutes before the start of the "time period". For example, the prediction unit 101 predicts the demand for "9:15-9:29" at "9:00", which is 15 minutes before "9:15". Similarly, the prediction unit 101 predicts the demand for "9:30-9:44" at "9:15", which is 15 minutes before "9:30". Note that these are only examples, and the "time period" may be in different units such as 5 minutes, 30 minutes, or 1 hour. Demand prediction may also be performed at different timings such as 5 minutes, 30 minutes, or 1 hour.

[0038] Next, in step S12, the search unit 102 searches for a replenishment vehicle. More specifically, the search unit 102 generates a solicitation message 701 soliciting the provision of transportation services in the shortage area and shortage time period. Then, the search unit 102 transmits the solicitation message 701 to the network 200 using the communication unit 104. As described above, the solicitation message 701 is distributed via the roadside unit 301, the ETC antenna 302, and the wireless base station device 303, and finally reaches the vehicle 401 (communication device 501) and the vehicle manager 402 (mobile terminal 502). Then, when the vehicle manager 402 (communication device 501) of the vehicle 401 that received the recruitment message 701 transmits a response message 702, the search unit 102 receives the response message 702 using the communication unit 104. Similarly, when the vehicle manager 402 (mobile terminal 502) that received the recruitment message 701 transmits the response message 702, the search unit 102 receives the response message 702 using the communication unit 104. The search unit 102 treats the vehicle 401 that is the source of the response message 702 as a replacement vehicle. The search unit 102 also treats a vehicle (a replacement candidate vehicle) managed by the vehicle manager 402 that is the source of the response message 702 as a replacement vehicle.

[0039] Next, in step S13, the request unit 103 requests the reserved vehicle or the replenishment vehicle to provide a transportation service. More specifically, when the request unit 103 receives a transportation request message 705 from the mobile terminal 502 of the service user 600, it requests the reserved vehicle or the replenishment vehicle to provide a transportation service to the service user 600. Since the number of secured vehicles can satisfy the number of vehicles in demand, if no replacement vehicles are arranged, the request unit 103 requests the provision of transportation services only from secured vehicles. On the other hand, in a shortage time period in a shortage area, the request unit 103 requests the provision of transportation services to replenishment vehicles in preference to the secured vehicles. After completing requests to all replenishment vehicles, the request unit 103 starts requests to secured vehicles. Specifically, the request unit 103 transmits a request message 703 to the reserved vehicle or the replenishment vehicle using the communication unit 104. Then, the request unit 103 receives an acceptance message 704 from the reserved vehicle or the replenishment vehicle using the communication unit 104. Upon receiving the acceptance message 704 , the request unit 103 uses the communication unit 104 to transmit a vehicle dispatch confirmation message 706 to the mobile terminal 502 of the service user 600 .

[0040] FIG. 5 shows details of step S11 in FIG. Steps S111 to S115 in FIG. 5 are performed for each region. In the following, it is assumed that the transportation service is provided in three areas: AAA, BBB, and CCC. It is also assumed that the transportation service is provided in one of the three areas: AAA, BBB, or CCC. It is assumed that the current time is "9:00", and the prediction unit 101 performs demand prediction for the AAA, BBB, and CCC regions from "9:15-9:29".

[0041] First, in step S111, the prediction unit 101 predicts the number of vehicles in demand for a target time period. As described above, since the current time is "9:00", the prediction unit 101 predicts the number of demanded vehicles for the time period "9:15-9:29". The prediction unit 101 may perform demand prediction by referring to, for example, the number of transportation requests in the past in the same time period in the same area (the number of transportation requests yesterday, the number of transportation requests one week ago, etc.). That is, the prediction unit 101 may perform demand prediction by referring to the number of transportation requests in the same area from "9:15-9:29" yesterday, the number of transportation requests in the same area from "9:15-9:29" one week ago, etc. The number of transportation requests is the number of transportation request messages 705 received. In addition, the prediction unit 101 may perform a demand prediction by referring to the number of transportation requests in the immediately preceding time period in the same region. In other words, the prediction unit 101 may perform a demand prediction by referring to the number of transportation requests in the time period "8:45-8:59" immediately preceding the current time "9:00". The prediction unit 101 may also perform demand prediction by referring to the number of transportation requests in the past in the same time period in adjacent regions and the number of transportation requests in the immediately preceding time period in adjacent regions. For example, to predict demand for "9:15-9:29" in region AAA, the prediction unit 101 may refer to the number of transportation requests from "9:15-9:29" yesterday in region BBB adjacent to region AAA. Furthermore, the prediction unit 101 may perform demand prediction taking into consideration the particularities of each day of the week, the presence or absence of events that will increase / decrease demand, and the like. Furthermore, the prediction unit 101 may perform demand prediction by combining the above parameters. There is no limit to the specific method that the forecasting unit 101 uses to forecast demand.

[0042] Next, in step S112, the prediction unit 101 compares the number of vehicles in demand with the number of vehicles secured for each region, and extracts the number of vehicles in short supply.

[0043] Fig. 6(a) shows an example of a demand vehicle number table. Fig. 6(a) shows a demand vehicle number table for area AAA. In the demand vehicle number table, a predicted value of the demand vehicle number for each time period is shown. Since the current time is "9:00", the prediction unit 101 predicts the number of vehicles in demand for "9:15-9:29" in area AAA. In (a) of Fig. 6, the number of vehicles in demand for "9:15-9:29" in area AAA is predicted to be "18". The number of vehicles in demand for "9:00-9:14" was predicted at "8:45," and the predicted value is listed as "15." On the other hand, the number of vehicles in demand for "9:30-9:44" is predicted at "9:15," so the predicted number of vehicles in demand is not listed.

[0044] Fig. 6(b) shows an example of the secured vehicle number table. Fig. 6(b) shows the secured vehicle number table for area AAA. In the secured vehicle number table, the number of secured vehicles and secured vehicle detailed information are shown for each time period. Each secured vehicle is assigned a "ranking" that is the order in which it will be requested to provide services. There is no restriction on the method of determining the "ranking." The secured vehicle detailed information field shows the secured vehicle detailed information in descending order of rank. The secured vehicle detailed information includes, for example, the secured vehicle's vehicle identification (ID), communication address, license plate value, and administrator's identifier (administrator's name).

[0045] The prediction unit 101 compares the number of demanded vehicles in the demanded vehicle number table of Fig. 6(a) with the number of secured vehicles in the secured vehicle number table of Fig. 6(b). If the number of demanded vehicles is greater than the number of secured vehicles, the prediction unit 101 extracts the difference in the number of vehicles as the number of vehicles in short supply.

[0046] Then, in step S113, the prediction unit 101 generates or updates a vehicle shortage number table. That is, if the shortage vehicle number table has not been generated, the prediction unit 101 generates a shortage vehicle number table in which the shortage vehicle number extracted in step S112 is indicated. Moreover, if the shortage vehicle number table has already been generated, the prediction unit 101 reads out the shortage vehicle number table from the database 105. Then, the prediction unit 101 adds the shortage vehicle number table extracted in step S112 to the shortage vehicle number table, and updates the shortage vehicle number table.

[0047] 6(c) shows an example of a vehicle shortage table, which indicates the number of vehicles that are in short supply for each time period. Here, the prediction unit 101 adds "8" as the number of vehicles in short supply for "9:15-9:29" in area AAA. A time period in which the number of vehicles in short supply is "1" or more is a shortage time period, and a region in which a shortage time period exists in the vehicle shortage table is a shortage region. In FIG. 6(c), “9:00-9:14” and “9:15-9:29” are shortage time periods, and area AAA is a shortage area.

[0048] Next, in step S114, the prediction unit 101 stores the vehicle shortage table in the database 105.

[0049] Finally, in step S115, the prediction unit 101 outputs a search instruction to the search unit 102. The search instruction is a command that instructs the search unit 102 to search for a replenishment vehicle. Here, the prediction unit 101 issues an instruction to search for auxiliary vehicles to make up for the shortage of vehicles in the area AAA between "9:15-9:29."

[0050] FIG. 7 shows details of step S12 in FIG. The process in FIG. 7 starts when the search unit 102 receives the search instruction output in step S115 in FIG. Steps S121 to S127 in FIG. 7 are performed for each shortage area. The operation for the shortage area AAA will be described below.

[0051] First, in step S121, the search unit 102 generates a recruitment message 701. Since the current time is "9:00", the search unit 102 generates a recruitment message 701 for "9:15-9:29" in area AAA. 8 shows an example of a recruitment message 701. In the recruitment message 701, the shortage time period "9:15-9:29" is indicated as the recruitment time period, and the shortage area "AAA" is indicated as the recruitment area.

[0052] Next, in step S122, the search unit 102 transmits the recruitment message 701 to the network 200 using the communication unit 104. That is, the search unit 102 outputs the recruitment message 701 to the communication unit 104, and the communication unit 104 transmits the recruitment message 701 to the network 200. The communication unit 104 transmits the recruitment message 701 to the roadside units 301 and ETC antennas 302 arranged in the shortage area AAA. In addition, the communication unit 104 may transmit the recruitment message 701 to the roadside units 301 and ETC antennas 302 arranged in the neighboring areas, taking into consideration the possibility that the vehicles 401 in the neighboring areas of the shortage area AAA may apply for the recruitment message 701. In addition, the communication unit 104 transmits a recruitment message 701 to a vehicle manager 402 who can provide replenishment vehicles in the shortage area AAA.

[0053] When the communication device 501 or the mobile terminal 502 that has received the recruitment message 701 transmits a response message 702, in step S123, the search unit 102 receives the response message 702 using the communication unit 104. That is, the communication unit 104 receives the response message 702, the communication unit 104 outputs the response message 702 to the search unit 102, and the search unit 102 receives the response message 702. Each time the searching unit 102 receives a response message 702, the searching unit 102 counts the number of received response messages 702.

[0054] 9 shows an example of the response message 702. In the response message 702, the recruitment time period and recruitment area are the same as those shown in the recruitment message 701. The vehicle ID is the ID of the vehicle 401 equipped with the communication device 501 that received the recruitment message 701, or the ID of a vehicle (replacement candidate vehicle) managed by the vehicle manager 402 carrying the mobile terminal 502 that received the recruitment message 701. The number is the license plate value of the vehicle 401 equipped with the communication device 501 that received the recruitment message 701, or the license plate value of a vehicle (candidate vehicle for replacement) managed by the vehicle manager 402 carrying the mobile terminal 502 that received the recruitment message 701. The vehicle manager 402 may manually input the license plate value, or the license plate value stored in the ETC card or other storage medium of the vehicle 401 may be transferred to the response message 702. The manager is the identifier (name / title) of the vehicle manager 402 of the vehicle 401 in which the communication device 501 that received the recruitment message 701 is installed, or the identifier (name / title) of the vehicle manager 402 carrying the mobile terminal 502 that received the recruitment message 701. The address is the communication address of the communication device 501 that received the recruitment message 701 or the communication address of the mobile terminal 502 that received the recruitment message 701. Note that any other communication address may be used as long as it is a communication address used by the vehicle manager 402. The vehicle manager 402 may manually input the communication address, or the communication address stored in the ETC card of the vehicle 401 or another storage medium may be copied into the response message 702.

[0055] Next, in step S124, the searching unit 102 determines whether or not the number of received response messages 702 has reached the replenishment upper limit number. The upper limit of the replenishment number is the upper limit of the number of replenishment vehicles. For example, the upper limit of the replenishment number may be set to about 120 to 150% of the number of vehicles in short supply. The extent of the upper limit of the replenishment number is determined by the transportation service provider.

[0056] If the number of received response messages 702 reaches the upper replenishment limit number, the process proceeds to step S125. On the other hand, if the number of received response messages 702 has not reached the upper replenishment limit number, step S123 continues.

[0057] In step S125, the search unit 102 transmits a recruitment end message to the network 200 using the communication unit 104. The recruitment end message is a communication message notifying that recruitment of replacement vehicles is ended. The communication device 501 and the mobile terminal 502 that receive the message indicating the end of recruitment notify the vehicle manager 402 that recruitment of replenishment vehicles has ended.

[0058] In step S126, the search unit 102 generates or updates a replenishment vehicle number table. In other words, if the replenishment vehicle number table has not been generated, the search unit 102 generates a replenishment vehicle number table indicating the number of replenishment vehicles obtained by receiving the response message 702 . Moreover, if the replenishment vehicle number table has already been generated, the search unit 102 reads out the replenishment vehicle number table from the database 105. Then, the search unit 102 adds the number of replenishment vehicles obtained by receiving the response message 702 to the replenishment vehicle number table, and updates the replenishment vehicle number table. Then, in step S127, the search unit 102 stores the generated or updated replenishment vehicle number table in the database 105.

[0059] FIG. 10 shows an example of a replenishment vehicle number table. The replenishment vehicle number table in FIG. 10 is a replenishment vehicle number table for region AAA. The replacement vehicle number table shows the number of vehicles that are lacking, the number of replacement vehicles, and detailed information about the replacement vehicles for each time period. Here, the searching unit 102 registers the number of replenishment vehicles "12" for "9:15-9:29" in area AAA. In the column of the supplementary vehicle detail information, the supplementary vehicle detail information is displayed in descending order of rank. The supplementary vehicle detail information includes, for example, the vehicle ID of the supplementary vehicle, the communication address, the number plate value, and the administrator's identifier (the administrator's name / name). These are extracted from the response message 702. For example, the order of the replacement vehicles may be determined in the order of the first-come-first-served response messages 702. Alternatively, the order of the replacement vehicles may be determined in the order of the number of times the vehicles have responded to the recruitment message 701 in the past. The method of determining the order of the replacement vehicles may be arbitrary.

[0060] Finally, in step S127, the search unit 102 stores the replenishment vehicle number table in the database 105.

[0061] FIG. 11 shows details of step S13 in FIG.

[0062] In step S131, the request unit 103 judges whether or not a transportation request message 705 has been received from the service user 600. If a transportation request message 705 has been received, the process proceeds to step S132.

[0063] In step S 132 , the request unit 103 determines the transportation request area and transportation request time zone from the transportation request message 705 . The transportation request area is an area in which the service user 600 requests transportation services. The transportation request time period is a time period in which the service user 600 requests transportation services.

[0064] FIG. 12 shows an example of a transport request message 705 .

[0065] The request message number is an identification number of the transport request message 705 . The boarding time is the time when the service user 600 desires to board. In other words, the boarding time indicates the starting time of the transportation service desired by the service user 600. The boarding point is a point where the service user 600 desires to board. In other words, the boarding point indicates a starting point of the transportation service desired by the service user 600. The drop-off point is a point where the service user 600 wishes to get off. In other words, the drop-off point indicates the end point of the transportation service that the service user 600 wishes to finish. The user name is the name or title of the service user 600. Also, a column for the number of passengers may be added to the transportation request message 705 . If the service user 600 agrees, the service user's 600 mobile phone number may be included in the transport request message 705 .

[0066] The request unit 103 determines the transportation requested time period from the boarding time in the transportation request message 705. In the example of Fig. 12, since the boarding time is "9:15", the request unit 103 determines "9:15-9:29" as the transportation requested time period. In addition, the request unit 103 determines the transportation request area from the boarding point. In the example of Fig. 12, since the boarding point is "AAA station rotary", the request unit 103 determines "AAA" as the transportation request area.

[0067] Next, in step S133, the request unit 103 determines whether or not a replenishment vehicle is registered for the combination of the transportation request time slot and the transportation request area. Specifically, the request unit 103 refers to a replenishment vehicle number table for the transportation request area and determines whether or not a replenishment vehicle is registered for the transportation request time period. In the example of the transportation request message 705 in FIG. 12, the request unit 103 refers to "9:15-9:29" in the replenishment vehicle number table in FIG. 10 and determines that a replenishment vehicle is registered.

[0068] If a replenishment vehicle is registered for the combination of the transportation request time slot and the transportation request area, the process proceeds to step S134. On the other hand, if a replenishment vehicle is not registered for the combination of the transportation request time slot and the transportation request area, the process proceeds to step S136.

[0069] In step S134, the request unit 103 generates a request message 703 addressed to the top-ranked replenishment vehicle in the replenishment vehicle detail information field of the replenishment vehicle number table.

[0070] FIG. 13 shows an example of the request message 703 . In the request message 703 , the request message number is an identification number of the request message 703 . The request message number, boarding time, boarding point, drop-off point, and user name are the same as those shown in the transportation request message 705.

[0071] Next, in step S135, the request unit 103 deletes the top-ranked replenishment vehicle detailed information from the replenishment vehicle number table, and also decrements the number of replenishment vehicles in the replenishment vehicle number table by one.

[0072] In step S136, the request unit 103 generates a request message 703 addressed to the secured vehicle with the highest ranking in the secured vehicle detailed information field of the secured vehicle number table. The request message 703 addressed to the reserved vehicle is also as shown in FIG.

[0073] Next, in step S137, the request unit 103 deletes the highest ranked secured vehicle detail information from the secured vehicle number table, and also decrements the secured vehicle number in the secured vehicle number table by one.

[0074] Next, in step S 138 , the request unit 103 uses the communication unit 104 to transmit a request message 703 to the network 200 . As a result, the request message 703 reaches the refill or reserved vehicle.

[0075] Next, in step S139, the request unit 103 determines whether or not an acceptance message 704 has been received from the replenishment vehicle or the secured vehicle. If the acceptance message 704 has been received, the process proceeds to step S140. On the other hand, if the acceptance message 704 has not been received, the process proceeds to step S141.

[0076] FIG. 14 shows an example of an acceptance message 704 . The acceptance message 704 contains the same content as the request message 703 .

[0077] In step S 140 , the request unit 103 uses the communication unit 104 to transmit a dispatch confirmation message 706 to the network 200 . As a result, a dispatch confirmation message 706 reaches the service user 600 .

[0078] FIG. 15 shows an example of a dispatch confirmation message 706 .

[0079] In the vehicle allocation confirmation message 706, the number is the number plate value of the replacement vehicle or the reserved vehicle. The request unit 103 extracts these from the replenishment vehicle detail information in the replenishment vehicle number table (FIG. 10) or the secured vehicle detail information in the secured vehicle number table (FIG. 6). The request message number, the request message number, the boarding time, the boarding point, the alighting point, and the user name are the same as those shown in the request message 703. If the fleet manager 402 agrees, the mobile phone number of the fleet manager 402 may be included in the dispatch confirmation message 706 .

[0080] On the other hand, if the acceptance message 704 is not received in step S139, the request unit 103 determines in step S141 whether or not an acceptance impossible message has been received. The non-acceptance message is a message notifying that the replenishment vehicle or the reserved vehicle to which the request message 703 was sent cannot accept the provision of transportation services.

[0081] If an unacceptable message is received, the process returns to step S133, and the request unit 103 assigns another replenishment vehicle or a reserved vehicle to the transportation request message 705. If the request unit 103 does not receive an unacceptable message, the request unit 103 waits for a predetermined time, and determines whether the predetermined time has elapsed in step S142. If the request unit 103 does not receive an acceptance message 704 or an unacceptable message even after the predetermined time has elapsed, the process returns to step S133, and the request unit 103 assigns another replenishment vehicle or reserved vehicle to the transportation request message 705.

[0082] The service user 600 who received the dispatch confirmation message 706 heads to the boarding point at the boarding time. Then, the service user 600 finds a replacement vehicle or a reserved vehicle corresponding to the number shown in the dispatch confirmation message 706, confirms that the person is the vehicle manager 402 shown in the dispatch confirmation message 706, and receives the transportation service. On the other hand, the vehicle manager 402 who sent the acceptance message 704 heads to the boarding point at the boarding time indicated in the request message 703. Then, the vehicle manager 402 confirms that the user is the service user 600 indicated in the request message 703, and provides the transportation service.

[0083] In this embodiment, no mention is made of charging processing. The transportation service management device 100 may perform any type of charging processing. The fee for the transportation service is not particularly set. For example, the service user 600 may pay a fixed fee determined in advance to the vehicle manager 402. Similarly, in this embodiment, there is no particular provision for a usage fee (fees) for the transportation service management device 100. For example, it is conceivable that the usage fee for the transportation service management device 100 is free of charge.

[0084] ***Description of the Effects of the Embodiment*** As described above, according to this embodiment, vehicles can be replenished dynamically, and vehicle-based transportation services can be smoothly provided. In other words, by dynamically replenishing vehicles in response to ever-changing demand, it is possible to avoid situations in which users give up on using the service due to a shortage of vehicles, and it is possible to provide transportation services to users smoothly.

[0085] In the above, an example has been described in which the transportation service management device 100 manages transportation services in a plurality of regions. When the transportation service management device 100 manages transportation services in only one region, the processes in Figs. 5 and 7 need only be performed for that one region.

[0086] Also, only a part of the procedure described in this embodiment may be performed. Furthermore, at least a part of the procedure described in this embodiment may be combined with a procedure not described in this embodiment. Furthermore, the configuration and procedures described in this embodiment may be modified as necessary.

[0087] ***Additional hardware configuration information*** Finally, a supplementary explanation of the hardware configuration of the transportation service management device 100 will be given. The processor 901 shown in FIG. 2 is an integrated circuit (IC) that performs processing. The processor 901 is a CPU (Central Processing Unit), a DSP (Digital Signal Processor), or the like. The main storage device 902 shown in FIG. 2 is a RAM (Random Access Memory). The auxiliary storage device 903 shown in FIG. 2 is a ROM (Read Only Memory), a flash memory, a HDD (Hard Disk Drive), or the like. The communication device 904 shown in FIG. 2 is an electronic circuit that performs data communication processing. The communication device 904 is, for example, a communication chip or a NIC (Network Interface Card).

[0088] The auxiliary storage device 903 also stores an OS (Operating System). At least a part of the OS is executed by the processor 901 . The processor 901 executes programs that realize the functions of the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104 while executing at least a part of the OS. The processor 901 executes the OS, which performs task management, memory management, file management, communication control, and the like. In addition, at least one of information, data, signal values, and variable values ​​indicating the results of processing by the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104 is stored in at least one of the main memory device 902, the auxiliary memory device 903, a register within the processor 901, and a cache memory. Furthermore, the programs for realizing the functions of the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104 may be stored in a portable recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, a DVD, etc. Then, the portable recording medium storing the programs for realizing the functions of the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104 may be distributed.

[0089] Furthermore, the "part" in the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104 may be read as a "circuit" or a "step" or a "procedure" or a "process" or a "circuitry". Furthermore, the transportation service management device 100 may be realized by a processing circuit. The processing circuit is, for example, a logic IC (Integrated Circuit), a GA (Gate Array), an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Gate Array). In this case, the prediction unit 101, the search unit 102, the request unit 103, and the communication unit 104 are each realized as part of a processing circuit. In this specification, the higher-level concept of a processor and a processing circuit is called "processing circuitry." That is, a processor and a processing circuit are each specific examples of "processing circuitry." [Explanation of symbols]

[0090] 100 Transportation service management device, 101 Prediction unit, 102 Search unit, 103 Request unit, 104 Communication unit, 105 Database, 200 Network, 301 Roadside unit, 302 ETC antenna, 303 Wireless base station device, 401 Vehicle, 402 Vehicle manager, 501 Communication device, 502 Mobile terminal, 600 Service user, 701 Recruitment message, 702 Response message, 703 Request message, 704 Acceptance message, 705 Transportation request message, 706 Vehicle dispatch confirmation message, 901 Processor, 902 Main memory device, 903 Auxiliary memory device, 904 Communication device.

Claims

1. A prediction unit that predicts a demand for a vehicle transportation service for each time period and extracts, as a shortage time period, a time period in which the demand for the transportation service is predicted to be insufficient with the number of reserved vehicles, which are vehicles under the management of a transport service operator; a search unit that searches for a replacement vehicle that can provide the transportation service during the shortage time period from among vehicles other than the reserved vehicles; a request unit that requests the replenishment vehicle to provide the transportation service during the shortage time period.

2. The prediction unit is predicting a demand for the transportation service for each time period in each of a plurality of regions, and extracting the shortage time period for each region; The search unit is Searching for the replenishment vehicle by region; The request unit, The transportation service management device according to claim 1 , wherein the supply vehicles are requested to provide the transportation service during the shortage time period for each region.

3. The search unit is As a search for the replenishment vehicle, a recruitment message is transmitted via a communication device installed on the roadway, the recruitment message being a communication message notifying that vehicles capable of providing the transportation service during the shortage time period are being recruited; A transportation service management device as described in claim 1, wherein when a response message, which is a communication message notifying that the transportation service can be provided during the shortage time period, is received from any of the vehicles that received the recruitment message, the vehicle that sent the response message is treated as the replenishment vehicle.

4. The search unit is As part of the search for the replenishment vehicle, a recruitment message is sent to a manager who manages candidate replenishment vehicles that are candidates for the replenishment vehicle, the recruitment message being a communication message notifying the manager that a vehicle capable of providing the transportation service during the shortage time period is being recruited; The transportation service management device described in claim 1 , wherein when a response message is received from the manager, which is a communication message notifying that the transportation service can be provided by the replacement candidate vehicle during the shortage time period, the replacement candidate vehicle is treated as the replacement vehicle.

5. The request unit, The transportation service management device according to claim 1 , wherein the transportation service is requested to the replenishment vehicles in priority to the reserved vehicles during the shortage time period.

6. A prediction process in which a computer predicts the demand for vehicle transportation services by time period and extracts, as a shortage time period, a time period in which the number of reserved vehicles, which are vehicles under the management of a transport service operator, is not expected to meet the demand for the transport service; A search process in which the computer searches for a replacement vehicle that can provide the transportation service during the shortage time period from among vehicles other than the reserved vehicles; A transportation service management method comprising a request process in which the computer requests the replenishment vehicle to provide the transportation service during the shortage time period.

7. A prediction process for predicting a demand for a vehicle-based transportation service for each time period, and extracting a time period in which the demand for the transportation service is predicted to be insufficient with the number of reserved vehicles under the management of the transportation service operator as a shortage time period; A search process for searching for a replacement vehicle that can provide the transportation service during the shortage time period from among vehicles other than the reserved vehicles; and a request process for requesting the replenishment vehicle to provide the transportation service during the shortage time period.

Images