Information processing method, information processing device, and information processing system

Abstract

The present technology relates to an information processing method, an information processing device, and an information processing system that make it possible to flexibly respond to a user's request in a service for transporting an object to be transported. The information processing system comprises at least one information processing device, and, in response to a sale request of an order from an ordering party including a platformer who provides a platform for arranging a mobile body that transports an object to be transported according to a user's order, searches for a contractor who can accept the order from among contractor candidates including other platformers. The present technology can be applied, for example, to a matching market for buying and selling ride-hailing orders for taxi ride-hailing services.

Description

Information Processing Method, Information Processing Apparatus, and Information Processing System

[0001] The present technology relates to an information processing method, an information processing apparatus, and an information processing system, and particularly relates to an information processing method, an information processing apparatus, and an information processing system that can flexibly respond to a user's order in a service for transporting a transport object.

[0002] Conventionally, when a request for transfer of the right to dispatch a taxi or permission for sharing a taxi is sent to the terminal device of a first user for whom taxi dispatching has been confirmed, and a notification of permission for the request is received from the terminal device of the first user, a technology has been proposed to send a message to the terminal device of a second user indicating that dispatching or sharing is possible (see, for example, Patent Document 1).

[0003] International Publication No. 2021 / 193052

[0004] However, in the invention described in Patent Document 1, transfer of the right to dispatch a taxi and permission for sharing are only carried out within the same platform that provides a service for arranging taxis. Therefore, for example, when the number of taxis within the platform is insufficient for the demand, the possibility of obtaining transfer of the right to dispatch a taxi and permission for sharing decreases.

[0005] The present technology has been made in view of such a situation, and enables flexible response to a user's order in a service for transporting a transport object such as a taxi.

[0006] The information processing method according to the first aspect of the present technology includes searching for an order-receiver who can receive the order from order candidates including other platforms in response to a request to sell the order from an order placer including a platform that provides a platform for arranging a moving object that transports a transport object in response to an order from a user.

[0007] The first aspect of this technology is an information processing device which includes a matching unit that searches for a contractor capable of accepting an order from among potential contractors, including other platform providers, in response to a request from a client, which is a platform provider that arranges a mobile vehicle to transport an object to be transported in response to an order from a client, for the sale of the said order.

[0008] The second aspect of this technology is an information processing system comprising: a plurality of first information processing systems that each provide a plurality of different platforms for arranging a mobile vehicle to transport an object to be transported in response to an order from a user; and a second information processing system that searches for other platforms capable of accepting the order in response to a request for the sale of the order from one of the platforms.

[0009] In the first aspect of this technology, in response to a request from a client, including a platform provider that arranges for a mobile vehicle to transport goods in accordance with a user's order, a contractor capable of accepting the order is searched for from among potential contractors, including other platform providers.

[0010] In a second aspect of this technology, multiple different platforms are provided, each arranging a mobile vehicle to transport an object in response to an order from a user, and in response to a request to sell an order from one of the platforms, other platforms capable of accepting the order are searched for.

[0011] This is a diagram illustrating the overview of this technology. This is a block diagram showing an example configuration of a dispatch system to which this technology is applied. This is a block diagram showing an example of the hierarchical structure of a dispatch system. This is a block diagram showing an example configuration of an integrated dispatch management system. This is a block diagram showing an example configuration of a user terminal. This is a block diagram showing an example configuration of a driver terminal. This is a block diagram showing an example configuration of a dispatch management device. This is a block diagram showing an example configuration of an integrated dispatch management server. This is a block diagram showing an example configuration of a matching market server. This is a flowchart illustrating the first embodiment of the processing of the integrated dispatch management server. This is a flowchart illustrating the details of the vehicle search process for our own APP. This is a flowchart illustrating the details of the sales process. This is a flowchart illustrating the details of the immediate purchase process. This is a flowchart illustrating the details of the inquiry response process. This is a flowchart illustrating the first embodiment of the processing of the matching market server. This is a flowchart illustrating the details of the matching process. This is a flowchart illustrating the details of the order process. This is a flowchart illustrating the second embodiment of the processing of the integrated dispatch management server. This is a flowchart illustrating the details of the inquiry response process. This is a flowchart illustrating the vehicle processing. This is a diagram showing an example of the inquiry condition setting screen. This is a diagram showing an example of the inquiry condition setting screen. This is a diagram showing an example of the inquiry condition setting screen. This is a diagram showing an example of the inquiry condition setting screen. This figure shows an example of the inquiry conditions setting screen. This is a flowchart explaining the details of the inquiry handling process. This figure shows an example of the vehicle dispatch order notification screen. This is a flowchart explaining a second embodiment of the matching market server processing. This is a flowchart explaining the details of the matching process. This is a flowchart explaining the details of a modified version of the matching process. This figure shows an example of the order screen. This figure shows an example of the order screen. This figure shows an example of the vehicle dispatch order simulation screen. This figure shows an example of the vehicle dispatch order simulation screen. This figure shows an example of the computer configuration.

[0012] The following describes the embodiments for implementing this technology. The explanation will proceed in the following order: 0. Overview of the Technology 1. Embodiments 2. Modifications 3. Others

[0013] <<0. Overview of this Technology>> First, we will explain the overview of this technology with reference to Figure 1.

[0014] This technology relates to a transportation service that transports goods from their origin to their destination.

[0015] Transportation services include, for example, transportation services that transport passengers, services that transport goods and luggage (including home delivery services), and delivery services that deliver food and beverages, etc.

[0016] The transported items are not particularly limited and include at least one of people and things. If the transported items are people, for example, this includes passengers, etc. If the transported items are things, for example, this includes living organisms other than people, plants, cargo, luggage, food and beverages, etc.

[0017] The means of transporting the transported goods are not particularly limited. For example, the means of transport may be a mobile body that moves by land, sea, or air. For example, a mobile body may include vehicles, aircraft (including drones), ships, etc. Furthermore, a mobile body may be driven by a driver or it may be unmanned. In addition, a mobile body may be, for example, a person or an animal.

[0018] The departure and destination locations may be any location or predetermined locations. For example, users of the transportation service may specify any location as their departure or destination, or they may choose from predetermined locations.

[0019] More specifically, this technology relates to a service (hereinafter referred to as the matching service) that enables the buying and selling of orders for transporting goods (hereinafter referred to as transport orders) in a matching market, as shown in Figure 1, for example. For example, the matching service matches a buyer or seller of a transport order with a seller or contractor who buys or accepts a transport order. The contractor is selected from among several potential buyers.

[0020] The matching market is an open market where various clients and contractors can participate. For example, a client may be an individual or an organization such as a corporation. For example, a potential contractor may be an individual or an organization such as a corporation. Also, for example, if the means of transportation is an unmanned mobile vehicle, the potential contractor may be the mobile vehicle itself.

[0021] A platform provider is a business that provides a platform for arranging vehicles to transport goods in response to transportation orders from users. For example, a platform provider arranges a vehicle to respond to a user's transportation order from among the vehicles it manages (hereinafter referred to as "its own vehicles"). Vehicles managed by a platform provider include, for example, vehicles owned by transportation service providers that have contracts with the platform provider, and vehicles owned by drivers that have direct contracts with the platform provider.

[0022] A platform provider can be either a client or a contractor (potential contractor). For example, if a platform provider does not have a vehicle in its fleet capable of fulfilling a user's transportation order, it can act as a client and sell the order to the matching market. Alternatively, a platform provider can act as a contractor and purchase or accept transportation orders that have been placed or sold to the matching market.

[0023] Therefore, platform providers can accept transportation orders that have been sold to the matching market by other platform providers. This makes it possible to share (arrange) transportation between platforms, increasing the probability of successful transportation arrangements and improving convenience for users of the platform.

[0024] Furthermore, transportation service providers may act as either clients or contractors in the matching market without going through a platform provider.

[0025] The following explanation primarily focuses on cases where the transportation service is a taxi and the object being transported is the passenger.

[0026] In this case, the ordering party includes, for example, users of the taxi dispatch application provided by the matching market (hereinafter referred to as the matching market dispatch application), and local governments that provide on-demand transportation.

[0027] A platform provider includes, for example, a business operator that operates a platform providing a ride-hailing service for dispatching taxis (hereinafter referred to as a ride-hailing platform). For example, a platform provider provides users with a ride-hailing app specifically for the ride-hailing platform (hereinafter referred to as a platform-specific ride-hailing app) and provides ride-hailing services using the platform-specific ride-hailing app.

[0028] Potential bidders include, for example, taxi operators who have direct contracts with matching markets, as well as individual taxi drivers.

[0029] For example, a taxi company could be the client.

[0030] Furthermore, taxi fare structures are not limited to the traditional base fare plus distance or time-based surcharges.

[0031] For example, the distance and time of travel may be predicted based on the departure point, destination, route, and road congestion, and the fare may be set in advance based on the predicted distance and time. In this case, the pre-set fare may be adjusted based on changes in the destination or route, changes in road congestion, etc.

[0032] Alternatively, dynamic pricing, for example, which involves raising fares during peak demand hours and lowering fares during off-peak hours, could be adopted.

[0033] <<1. Embodiments>> Next, embodiments of the present technology will be described with reference to Figures 2 to 32.

[0034] <Example Configuration of Dispatch System 1> Figure 2 shows an example configuration of dispatch system 1 to which this technology is applied.

[0035] Dispatch System 1 is a system that provides matching services, such as matching clients who place dispatch orders with service providers, through a matching marketplace.

[0036] The dispatch system 1 comprises a user terminal 11, a vehicle 12, a dispatch management device 13, a dispatch integrated management server 14, and a matching market server 15. The user terminal 11, vehicle 12, dispatch management device 13, dispatch integrated management server 14, and matching market server 15 are interconnected via a network 21.

[0037] The user terminal 11 is an information processing terminal used by users who order the dispatch of a vehicle 12. The user terminal 11 can be composed of, for example, a smartphone, tablet, PC (personal computer), wearable device, etc.

[0038] Vehicle 12 is a vehicle that transports the object to be transported (user). For example, vehicle 12 is not limited to conventional taxis, shared taxis, etc., but may also include vehicles used for ride-sharing.

[0039] The dispatch management device 13 is, for example, an information processing device managed by a taxi company. Each dispatch management device 13 corresponds to a different taxi company.

[0040] The dispatch management server 14 is an information processing device managed by a platform provider that operates a taxi dispatch service. Each dispatch management server 14 corresponds to a different dispatch platform.

[0041] The matching market server 15 is an information processing device managed by the operator of the matching market.

[0042] The network 21 can be composed of a communication network or communication path of any communication standard, such as the Internet, a public telephone line network, a wide-area communication network for mobile communication such as a so-called 4G line or 5G line, a WAN (Wide Area Network), a LAN (Local Area Network), a wireless communication network that performs communication compliant with the Bluetooth (registered trademark) standard, a communication path for short-range wireless communication such as NFC (Near Field Communication), a communication path for infrared communication, a communication network for wired communication compliant with standards such as HDMI (registered trademark) (High-Definition Multimedia Interface) and USB (Universal Serial Bus), etc.

[0043] Figure 3 shows the hierarchical structure of the vehicle dispatching system 1. The matching market server 15 is connected to the user terminal 11, the vehicle dispatching integrated management system 51, and the vehicle 12 via a network 21 not shown in the figure.

[0044] The user terminal 11 is a terminal that can directly place a vehicle dispatching order in the matching market using the vehicle dispatching APP for the matching market.

[0045] The vehicle dispatching integrated management system 51 is a system that realizes each vehicle dispatching platform. Each vehicle dispatching integrated management system 51 realizes a vehicle dispatching platform corresponding to a different vehicle dispatching service.

[0046] The vehicle 12 is a vehicle that can directly contract with the matching market and directly receive a vehicle dispatching order from the matching market. The driver of the vehicle 12 receives a vehicle dispatching order directly from the matching market, for example, by using a driver APP (hereinafter referred to as the driver APP for the matching market), which is an application for drivers provided by the matching market.

[0047] Figure 4 shows an example of the hierarchical structure of the vehicle dispatching integrated management system 51.

[0048] The vehicle allocation integrated management system 51 includes a user terminal 11, a vehicle 12, a vehicle allocation integrated management server 14, and a vehicle allocation management system 71. The vehicle allocation integrated management server 14 is connected to the user terminal 11, the vehicle 12, and the vehicle allocation management system 71 via a network 21 not shown in the figure. The vehicle allocation management system 71 includes the vehicle 12 and a vehicle allocation management device 13. The vehicle allocation management device 13 is connected to the vehicle 12 via a network 21 not shown in the figure.

[0049] The user terminal 11 connected to the vehicle allocation integrated management server 14 without passing through the vehicle allocation management device 13 is, for example, a terminal possessed by a user who uses a vehicle allocation service (vehicle allocation platform) provided by the vehicle allocation integrated management server 14. For example, the user uses the vehicle allocation service by executing a vehicle allocation APP for the platform using the user terminal 11.

[0050] Each vehicle allocation management system 71 corresponds to a taxi operator that has contracted with the vehicle allocation platform provided by the vehicle allocation integrated management server 14. Each vehicle allocation management system 71 corresponds to a different taxi operator. The vehicles 12 within the vehicle allocation management system 71 are vehicles owned and managed by the taxi operator who manages the vehicle allocation management system 71. Hereinafter, the vehicles 12 within the vehicle allocation management system 71 are referred to as the vehicles 12 of the corresponding taxi operator (itself).

[0051] For example, when there is only one taxi operator who has contracted with the vehicle allocation platform, there is only one vehicle allocation management system 71.

[0052] Vehicles 12 that are connected to the integrated dispatch management server 14 without going through the dispatch management device 13 are vehicles 12 owned by drivers who have a direct contract with the dispatch platform provided by the integrated dispatch management server 14. Drivers of vehicles 12 can, for example, use the driver APP (hereinafter referred to as the platform driver APP) provided by the dispatch platform provider to receive dispatch orders directly from the dispatch platform provider. For example, vehicles 12 owned by a taxi company can also connect directly to the integrated dispatch management server 14 without going through the dispatch management device 13 by using the platform driver APP, and receive dispatch orders directly from the dispatch platform provider.

[0053] Vehicles 12 within the integrated dispatch management system 51 (vehicles 12 within the dispatch management system 71, and vehicles 12 directly connected to the integrated dispatch management server 14) are managed by the dispatch platform and are capable of receiving dispatch orders from the dispatch platform. Hereinafter, vehicles 12 within the integrated dispatch management system 51 will be referred to as vehicles 12 of the corresponding dispatch platform (our company).

[0054] For example, a dispatch management device 13 managed by a taxi operator may be directly connected to a matching market server 15 via a network 21, allowing the taxi operator to directly buy and sell dispatch orders in the matching market.

[0055] <Example of User Terminal 11 Configuration> Figure 5 shows an example of the configuration of user terminal 11.

[0056] The user terminal 11 includes an input unit 101, a sensing unit 102, a control unit 103, an output unit 104, a communication unit 105, and a storage unit 106.

[0057] In the following, when any part of the user terminal 11 communicates with other devices of the dispatch system 1 via the communication unit 105 and the network 21, the phrase "via the communication unit 105 and the network 21" will be omitted. For example, when the control unit 103 communicates with the matching market server 15 via the communication unit 105 and the network 21, it will be written as "the control unit 103 communicates with the matching market server 15."

[0058] The input unit 101 is equipped with various input devices for operating the user terminal 11 and inputting various types of data to the control unit 103. The input unit 101 supplies the input data received via each input device to the control unit 103.

[0059] The sensing unit 102 is equipped with various sensors for detecting the state of the user terminal 11 and the surrounding environment of the user terminal 11. For example, the sensing unit 102 includes a camera, an IMU (Inertial Measurement Unit), a GNSS (Global Navigation Satellite System) receiver, etc. The sensing unit 102 supplies sensor data indicating the detection results of each sensor to the control unit 103.

[0060] The control unit 103 is composed of a processor such as a CPU (Central Processing Unit) and an MPU (Micro Processing Unit). The control unit 103 includes a self-position estimation unit 111 and an information processing unit 112.

[0061] The self-position estimation unit 111 estimates the current position and orientation of the user terminal 11 based on the sensor data.

[0062] The information processing unit 112 is implemented, for example, by the control unit 103 executing a dispatch APP (platform dispatch APP or matching market dispatch APP). The information processing unit 112 includes a UI (User Interface) control unit 121 and an order processing unit 122.

[0063] The UI control unit 121 controls the input unit 101 and the output unit 104 to control the UI of the dispatch app. For example, the UI control unit 121 controls the display and operation of various screens of the dispatch app.

[0064] The order processing unit 122 executes the order processing for dispatch orders in response to operations on the dispatch APP. For example, the order processing unit 122 generates information related to dispatch orders and transmits it to the dispatch integrated management server 14 or the matching market server 15.

[0065] Furthermore, for example, a user can input an evaluation of the driver of the dispatched vehicle 12 via the input unit 101. The evaluation of the driver can be expressed, for example, by a numerical value, a number of stars, or a comment. The order processing unit 122 transmits information indicating the driver's evaluation to the dispatch integrated management server 14 or the matching market server 15.

[0066] The output unit 104 is equipped with various output devices that output various types of information and data, such as visual information, auditory information, and tactile information.

[0067] The communication unit 105 communicates with other devices of the dispatch system 1 via the network 21.

[0068] The storage unit 106 stores the data necessary for processing the user terminal 11.

[0069] <Example of the configuration of the driver terminal 151> Figure 6 shows an example of the configuration of the driver terminal 151 installed in the vehicle 12.

[0070] The driver terminal 151 consists of at least one of the following: an in-vehicle device installed in the vehicle 12, and an information processing terminal such as a tablet or smartphone held by the driver. The driver terminal 151 may consist of two or more devices. For example, the driver terminal 151 may consist of a combination of an in-vehicle device and an information processing terminal.

[0071] The driver terminal 151 includes an input unit 161, a sensing unit 162, a control unit 163, an output unit 164, a communication unit 165, and a storage unit 166.

[0072] In the following, when each part of the driver terminal 151 communicates with other devices of the dispatch system 1 via the communication unit 165 and the network 21, the phrase "via the communication unit 165 and the network 21" will be omitted. For example, when the control unit 163 communicates with the matching market server 15 via the communication unit 165 and the network 21, it will be written as "the control unit 163 communicates with the matching market server 15."

[0073] The input unit 161 is equipped with various input devices for operating the driver terminal 151 and inputting various data to the control unit 163. The input unit 161 supplies the input data received via each input device to the control unit 163.

[0074] The sensing unit 162 includes various sensors for detecting the state of the vehicle 12, the state of the driver and passengers, and the conditions around the vehicle 12. The sensing unit 162 may also include sensors provided on the vehicle 12. For example, the sensing unit 162 may include a camera, radar, seat sensor, biosensor, speed sensor, IMU, GNSS receiver, taxi fare meter, etc. The sensing unit 162 supplies sensor data indicating the detection results of each sensor to the control unit 163.

[0075] The control unit 163 is composed of a processor such as a CPU or MPU. The control unit 163 includes a self-position estimation unit 171, a vehicle motion data generation unit 172, and an information processing unit 173.

[0076] The self-position estimation unit 171 estimates the current position and direction of travel of the vehicle 12 based on the sensor data.

[0077] The vehicle movement data generation unit 172 detects the movement of the vehicle 12 based on the input data, sensor data, and the estimation results of the self-position estimation unit 171, and generates vehicle movement data indicating the movement of the vehicle 12. The vehicle movement data generation unit 172 transmits the vehicle movement data to the dispatch management device 13, the dispatch integrated management server 14, and the matching market server 15.

[0078] The information processing unit 173 is implemented, for example, by the control unit 163 executing a driver APP (a platform driver APP or a matching market driver APP). The information processing unit 173 includes a UI control unit 181 and an order management unit 182.

[0079] The UI control unit 181 controls the input unit 161 and the output unit 164 to control the UI of the driver app. For example, the UI control unit 181 controls the display and operation of various screens of the driver app.

[0080] The order management unit 182 manages dispatch orders requested from the dispatch management device 13, the dispatch integrated management server 14, or the matching market server 15. Dispatch orders requested by the order management unit 182 (vehicles 12) include, for example, dispatch orders placed directly by the dispatch management device 13 (taxi operators) without going through the dispatch platform, dispatch orders placed by the dispatch integrated management server 14 via the dispatch platform, and dispatch orders sold to the matching market server 15 (matching market).

[0081] For example, the order management unit 182 receives information regarding dispatch orders from the dispatch management device 13, the dispatch integrated management server 14, or the matching market server 15, and stores it in the storage unit 166. For example, information regarding dispatch orders is presented to the driver via the output unit 164.

[0082] For example, the driver determines whether or not they can fulfill the dispatch order corresponding to the dispatch order information, and inputs the determination result to the control unit 163 via the input unit 161. The order management unit 182 transmits information indicating whether or not the dispatch order can be fulfilled to the dispatch management device 13, the dispatch integrated management server 14, or the matching market server 15. For example, if the order management unit 182 does not receive a response from the driver to the dispatch order within a predetermined time, it transmits information indicating that the dispatch order cannot be fulfilled (no response) to the dispatch management device 13, the dispatch integrated management server 14, or the matching market server 15.

[0083] For example, when the order management unit 182 responds to a dispatch order, it transmits information regarding the actual performance of the dispatch order to the dispatch management device 13, the dispatch integrated management server 14, or the matching market server 15, or stores it in the storage unit 166.

[0084] For example, drivers can input ratings for users (passengers). User ratings can be expressed as numerical values, star ratings, comments, etc. The order management unit 182 transmits information indicating the user rating to the dispatch management device 13, the dispatch integrated management server 14, or the matching market server 15.

[0085] For example, when the order management unit 182 receives a dispatch order directly from the matching market, it registers the conditions for purchasing (receiving) the dispatch order with the matching market and modifies them as appropriate. Specifically, for example, the order management unit 182 generates information indicating the conditions for receiving inquiries for dispatch orders from the matching market and transmits it to the matching market server 15, thereby registering or modifying the inquiry conditions.

[0086] The output unit 164 is equipped with various output devices that output various types of information and data, such as visual information, auditory information, and tactile information.

[0087] The communication unit 165 communicates with other devices of the dispatch system 1 via the network 21.

[0088] The memory unit 166 stores the data necessary for processing the driver terminal 151.

[0089] <Example of the configuration of the dispatch management device 13> Figure 7 shows an example of the configuration of the dispatch management device 13.

[0090] The dispatch management device 13 includes an input unit 201, a control unit 202, an output unit 203, a communication unit 204, and a storage unit 205.

[0091] In the following, when each part of the dispatch management device 13 communicates with other devices of the dispatch system 1 via the communication unit 204 and the network 21, the phrase "via the communication unit 204 and the network 21" will be omitted. For example, when the control unit 202 communicates with the integrated dispatch management server 14 via the communication unit 204 and the network 21, it will be written as "the control unit 202 communicates with the integrated dispatch management server 14."

[0092] The input unit 201 is equipped with various input devices for operating the dispatch management device 13 and inputting various data to the control unit 202. The input unit 201 supplies the input data received via each input device to the control unit 202.

[0093] The control unit 202 is composed of a processor such as a CPU and MPU. The control unit 202 includes a vehicle movement data management unit 211, an order management unit 212, and a dispatch management unit 213.

[0094] The vehicle movement data management unit 211 receives and manages vehicle movement data from each of the company's vehicles 12 under the control of the dispatch management device 13. For example, the vehicle movement data management unit 211 stores and updates the vehicle movement data received from each vehicle 12 in the storage unit 205. This allows the vehicle movement data management unit 211 to recognize changes in the time-series movement of each vehicle 12. For example, the vehicle movement data management unit 211 displays the movement of each vehicle 12 on the output unit 203 based on the vehicle movement data of each vehicle 12. For example, the vehicle movement data management unit 211 transmits the vehicle movement data of each vehicle 12 to the dispatch integrated management server 14 corresponding to the contracted dispatch platform.

[0095] The order management unit 212 manages dispatch orders requested from user terminals 11, the dispatch integrated management server 14, or the matching market server 15. Dispatch orders requested to the order management unit 212 (dispatch management device 13) include, for example, dispatch orders placed directly with the dispatch management device 13 (taxi operators) without going through the dispatch platform, dispatch orders placed with the dispatch integrated management server 14 via the dispatch platform, and dispatch orders sold to the matching market server 15 (matching market).

[0096] For example, the order management unit 212 receives information regarding dispatch orders from the user terminal 11, the dispatch integrated management server 14, or the matching market server 15, and stores it in the storage unit 205. For example, the order management unit 212 receives information regarding the actual performance of dispatch orders and information indicating evaluations of users (passengers) from the vehicle 12, and transmits it to the dispatch integrated management server 14 or the matching market server 15 as necessary.

[0097] For example, when the order management unit 212 receives a dispatch order directly from the matching market, it registers the conditions for purchasing (receiving) the dispatch order with the matching market and modifies them as appropriate. Specifically, for example, the order management unit 212 generates information indicating the conditions for receiving inquiries for dispatch orders from the matching market, and registers or modifies the inquiry conditions by transmitting it to the matching market server 15 via the dispatch integration management server 14 as needed.

[0098] For example, when the order management unit 212 sells a dispatch order to the matching market, it generates information regarding the dispatch order and the sales conditions, and transmits it to the matching market server 15 via the dispatch integration management server 14 as needed.

[0099] The dispatch management unit 213 manages the dispatch of the company's vehicles 12 under the control of the dispatch management device 13. For example, the dispatch management unit 213 searches for vehicles 12 that can respond to dispatch orders based on vehicle movement data for each vehicle 12 managed by the vehicle movement data management unit 211. For example, the dispatch management unit 213 transmits information about dispatch orders to vehicles 12 that are requesting or inquiring about responding to dispatch orders. For example, the dispatch management unit 213 receives information from vehicles 12 indicating whether or not they can respond to dispatch orders and transmits it to the dispatch integrated management server 14 or the matching market server 15 as necessary.

[0100] The output unit 203 is equipped with various output devices that output various types of information and data, such as visual information, auditory information, and tactile information.

[0101] The communication unit 204 communicates with other devices of the dispatch system 1 via the network 21.

[0102] The storage unit 205 stores the data necessary for processing by the dispatch management device 13.

[0103] <Example Configuration of the Dispatch Integrated Management Server 14> Figure 8 shows an example configuration of the dispatch integrated management server 14.

[0104] The vehicle dispatch integrated management server 14 includes an input unit 251, a control unit 252, an output unit 253, a communication unit 254, and a storage unit 255.

[0105] In the following, when each part of the dispatch integrated management server 14 communicates with other devices of the dispatch system 1 via the communication unit 254 and the network 21, the phrase "via the communication unit 254 and the network 21" will be omitted. For example, when the control unit 252 communicates with the matching market server 15 via the communication unit 254 and the network 21, it will be written as "the control unit 252 communicates with the matching market server 15."

[0106] The input unit 251 is equipped with various input devices for operating the vehicle dispatch integrated management server 14 and inputting various data to the control unit 252. The input unit 251 supplies the input data received via each input device to the control unit 252.

[0107] The control unit 252 is composed of a processor such as a CPU or MPU. The control unit 252 includes a vehicle movement data management unit 261, a customer data management unit 262, an order management unit 263, a dispatch management unit 264, a user terminal control unit 265, and a driver terminal control unit 266.

[0108] The Vehicle Movement Data Management Unit 261 receives and manages vehicle movement data for each of the company's vehicles 12 from the vehicles 12 under the command of the Dispatch Integrated Management Server 14 or the Dispatch Management Device 13. For example, the Vehicle Movement Data Management Unit 261 stores or updates the vehicle movement data received from each vehicle 12 in the Storage Unit 255. This allows the Vehicle Movement Data Management Unit 261 to recognize changes in the time-series movement of each vehicle 12. The Vehicle Movement Data Management Unit 261 transmits the vehicle movement data for each vehicle 12 to the Matching Market Server 15.

[0109] The vehicle movement data may also include, for example, rating information indicating an evaluation of the driver of each vehicle 12, which is entered by the user via the dispatch app.

[0110] The customer data management unit 262 manages customer data relating to customers using the ride-hailing platform. For example, the customer data management unit 262 generates customer data based on data received from the user terminal 11 via the platform's ride-hailing app, data received from the vehicle 12 via the platform's driver app, and the user's ride history, and stores it in the storage unit 255. The customer data includes information such as the customer's name, preferred taxi companies or taxi companies they would like to be prioritized for dispatch, frequently used taxi stands, average waiting time for a ride, and rating information indicating the customer's evaluation.

[0111] The order management unit 263 manages dispatch orders requested from user terminals 11 or matching market servers 15. Dispatch orders requested to the order management unit 263 (dispatch integrated management server 14) include, for example, dispatch orders placed with the dispatch integrated management server 14 via the dispatch platform, and dispatch orders sold to the matching market server 15 (matching market).

[0112] For example, the order management unit 263 receives information regarding dispatch orders from the user terminal 11 or the matching market server 15 and stores it in the storage unit 255. For example, the order management unit 263 receives information regarding the actual performance of dispatch orders and information indicating evaluations of users (passengers) from the vehicle 12 or the dispatch management device 13, and transmits it to the matching market server 15 or stores it in the storage unit 255 as necessary.

[0113] For example, the order management unit 263 registers the conditions for purchasing (receiving) dispatch orders from the matching market in the matching market and modifies them as appropriate. Specifically, for example, the order management unit 263 generates information indicating the conditions for purchasing dispatch orders from the matching market or the conditions for receiving inquiries for dispatch orders, and transmits this information to the matching market server 15, thereby registering or modifying the purchase conditions and inquiry conditions.

[0114] For example, when the order management unit 263 sells a dispatch order to the matching market, it generates information regarding the dispatch order and the sales conditions, and either transmits it to the matching market server 15 or stores it in the storage unit 255.

[0115] For example, the order management unit 263 executes settlement processing for dispatch orders based on information regarding the sales conditions and performance of the dispatch orders.

[0116] For example, if the order management unit 263 is the ordering party, it obtains or sets a rating indicating an evaluation of the service provider and notifies the matching market server 15.

[0117] The dispatch management unit 264 manages the dispatch of the company's vehicles 12 under the control of the integrated dispatch management server 14. For example, the dispatch management unit 264 searches for vehicles 12 that can respond to dispatch orders based on vehicle movement data for each vehicle 12 managed by the vehicle movement data management unit 261. For example, the dispatch management unit 264 transmits information about dispatch orders to vehicles 12 that are requesting or inquiring about responding to dispatch orders, via the dispatch management device 13 as needed. For example, the dispatch management unit 264 receives information from vehicles 12 indicating whether or not they can respond to dispatch orders, via the dispatch management device 13 as needed, and transmits it to the matching market server 15 as needed.

[0118] The user terminal control unit 265 communicates with the user terminal 11 and controls the execution of the platform dispatch APP on the user terminal 11.

[0119] The driver terminal control unit 266 communicates with the driver terminal 151 and controls the execution of the platform driver APP on the driver terminal 151.

[0120] The output unit 253 is equipped with various output devices that output various types of information and data, such as visual information, auditory information, and tactile information.

[0121] The communication unit 254 communicates with other devices of the dispatch system 1 via the network 21.

[0122] The storage unit 255 stores the data necessary for processing by the vehicle dispatch integrated management server 14.

[0123] <Example Configuration of Matching Market Server 15> Figure 9 shows an example configuration of the matching market server 15.

[0124] The matching market server 15 includes an input unit 301, a control unit 302, an output unit 303, a communication unit 304, and a storage unit 305.

[0125] In the following, when each part of the matching market server 15 communicates with other devices of the dispatch system 1 via the communication unit 304 and the network 21, the phrase "via the communication unit 304 and the network 21" will be omitted. For example, when the control unit 302 communicates with the dispatch integrated management server 14 via the communication unit 304 and the network 21, it will be written as "the control unit 302 communicates with the dispatch integrated management server 14."

[0126] The input unit 301 is equipped with various input devices for operating the matching market server 15 and inputting various types of data to the control unit 302. The input unit 301 supplies the input data received via each input device to the control unit 302.

[0127] The control unit 302 is composed of a processor such as a CPU or MPU. The control unit 302 includes a vehicle movement data management unit 311, a customer data management unit 312, an order management unit 313, a matching unit 314, a user terminal control unit 315, and a driver terminal control unit 316.

[0128] The vehicle movement data management unit 311 manages the vehicle movement data of each vehicle 12. For example, the vehicle movement data management unit 311 stores or updates the vehicle movement data of each vehicle 12 received from each vehicle 12, the dispatch management device 13, or the dispatch integrated management server 14 in the storage unit 305. In this way, the vehicle movement data management unit 311 recognizes changes in the time-series movement of each vehicle 12.

[0129] The vehicle movement data may also include, for example, rating information indicating an evaluation of the driver of each vehicle 12, which is entered by the user via the dispatch app.

[0130] The customer data management unit 312 manages customer data relating to customers using the matching market. For example, the customer data management unit 312 generates customer data based on data received from the user terminal 11 via the matching market dispatch APP, data received from the vehicle 12 via the matching market driver APP, and the user's ride history, and stores it in the storage unit 305. For example, the customer data management unit 312 may also acquire customer data from the dispatch integrated management server 14 and store it in the storage unit 305. Customer data includes information such as the customer's name, preferred taxi companies or taxi companies the customer wants to be dispatched to preferentially, frequently used taxi stands, average waiting time for pickup, and rating information indicating the customer's evaluation.

[0131] The order management unit 313 manages dispatch orders sold to the matching market by the ordering party (e.g., platform provider, taxi operator, user, etc.). For example, the order management unit 313 receives information about dispatch orders and sales conditions from the ordering party and stores it in the storage unit 305. For example, the order management unit 313 notifies the ordering party whether or not the dispatch order can be sold based on the results of the matching process by the matching unit 314. For example, the order management unit 313 executes the process of placing a dispatch order with the recipient selected by the matching unit 314. For example, the order management unit 313 receives information about the actual performance of the dispatch order from the recipient and transmits it to the ordering party or stores it in the storage unit 305.

[0132] The matching unit 314 matches the person who places a dispatch order (e.g., a platform provider, a taxi operator, a user, etc.) with a candidate who can accept the order (e.g., a platform provider, a taxi operator, a driver, etc.). For example, the matching unit 314 searches for and selects a person who can accept a dispatch order based on the sales conditions of the dispatch order presented by the person who places the order and the purchase conditions of the dispatch order presented by the candidate who can accept the order, and also uses vehicle movement data of each vehicle 12 as needed, and inquires with the candidate whether or not they can accept the dispatch order. The matching unit 314 also receives information regarding the purchase conditions of the dispatch order from the candidate and executes a process to register or change the purchase conditions of the candidate.

[0133] The user terminal control unit 315 controls the execution of the matching market dispatch APP on the user terminal 11.

[0134] The driver terminal control unit 316 controls the execution of the driver APP for the matching market on the driver terminal 151.

[0135] The output unit 303 is equipped with various output devices that output various types of information and data, such as visual information, auditory information, and tactile information.

[0136] The communication unit 304 communicates with other devices of the dispatch system 1 via the network 21.

[0137] The memory unit 305 stores the data necessary for processing by the matching market server 15.

[0138] <First Embodiment of Processing of Dispatch System 1> Next, a first embodiment of processing of dispatch system 1 will be described with reference to Figures 10 to 17.

[0139] <Processing of the Dispatch Management Server 14> First, the processing of the Dispatch Management Server 14 will be explained by referring to the flowchart in Figure 10.

[0140] In step S1, the order management unit 263 determines whether or not to register or change the immediate purchase conditions for the vehicle dispatch order.

[0141] An immediate purchase is the action (process) of a potential customer purchasing (accepting) a vehicle dispatch order from the matching market before conducting a vehicle search within their own company. The conditions for an immediate purchase are that the potential customer purchases (accepts) a vehicle dispatch order from the matching market before conducting a vehicle search within their own company.

[0142] The immediate purchase conditions include information indicating whether the prospective buyer is willing to accept an immediate purchase. Furthermore, if the prospective buyer accepts an immediate purchase, the immediate purchase conditions include the conditions under which the prospective buyer will immediately purchase the dispatch order. In other words, dispatch orders whose sales conditions in the matching market meet the immediate purchase conditions are eligible for immediate purchase by the prospective buyer. Conversely, dispatch orders whose sales conditions in the matching market do not meet the immediate purchase conditions are excluded from being eligible for immediate purchase by the prospective buyer.

[0143] For example, the conditions for immediate purchase include "conditions regarding the order details," "contract terms unrelated to penalties," and "maximum penalty amount."

[0144] "Order details" include, for example, "date and time of boarding," "boarding location," "destination," "number of passengers," "passenger rating," and "optional conditions."

[0145] The "boarding date and time" indicates, for example, the range of boarding dates and times for the ride-hailing order that is eligible for immediate purchase. For example, if the "boarding date and time" includes the current time, it becomes possible to immediately purchase an immediate ride-hailing order. For example, if the "boarding date and time" includes a future date and time, it becomes possible to immediately purchase a reserved ride-hailing order within the specified date and time range.

[0146] "Pick-up location" refers to the range of pick-up locations (departure points) for a ride-hailing order that is eligible for immediate purchase.

[0147] "Destination" refers to the range of destinations for a ride-hailing order that is being purchased immediately.

[0148] "Number of passengers" and "passenger rating" are conditions relating to the passengers who are the transported goods of vehicle 12. "Number of passengers" indicates, for example, the range of the number of passengers in a ride-hailing order that is eligible for immediate purchase. "Passenger rating" indicates, for example, the range of the passenger ratings in a ride-hailing order that is eligible for immediate purchase.

[0149] "Optional conditions" include, for example, "vehicle type," "whether or not highway use is permitted," and "type of driver's license."

[0150] "Vehicle type" is one of the conditions relating to the vehicle 12, which is a mobile vehicle used to transport passengers. "Vehicle type" indicates, for example, the vehicle type of the vehicle 12 in a dispatch order that is eligible for immediate purchase. For example, if a vehicle type is specified in a dispatch order, and the specified vehicle type is registered in "Vehicle Type," the dispatch order will be eligible for immediate purchase. If the specified vehicle type is not registered in "Vehicle Type," the dispatch order will not be eligible for immediate purchase.

[0151] "Whether or not expressways can be used" is one of the conditions regarding the route used to transport passengers. For example, "Whether or not expressways can be used" indicates whether or not a ride order using an expressway will be eligible for immediate purchase.

[0152] Furthermore, for example, the conditions could include whether or not the use of toll roads other than expressways is permitted.

[0153] "License type" is one of the conditions relating to the driver of vehicle 12. "License type" indicates, for example, the type of license of the driver of vehicle 12 in a dispatch order that is eligible for immediate purchase. For example, if the type of license of the driver is specified in a dispatch order, and the specified license type is registered in "License type", the dispatch order will be eligible for immediate purchase. If the specified license type is not registered in "License type", the dispatch order will not be eligible for immediate purchase.

[0154] For example, in ride-hailing services, the type of driver's license may be limited to a commercial driver's license (Type 2) in order to exclude ride-sharing services.

[0155] "Contract terms unrelated to penalty clauses" include, for example, "order amount conditions."

[0156] "Order amount conditions" are one of the conditions related to fares (charges). "Order amount conditions" indicate, for example, the order amount conditions for dispatch orders that are eligible for immediate purchase. "Order amount conditions" include, for example, a minimum order amount per unit distance (e.g., 1 km), a minimum order amount per unit time (e.g., 1 minute), and a minimum base fare.

[0157] The "Penalty Limit" is the condition regarding penalties incurred if the conditions specified in the dispatch order are not met. For example, the "Penalty Limit" indicates the maximum penalty for dispatch orders that qualify for immediate purchase. For example, dispatch orders with a penalty of less than or equal to the "Penalty Limit" are eligible for immediate purchase, while dispatch orders with a penalty exceeding the "Penalty Limit" are not eligible for immediate purchase.

[0158] "Penalty limit" indicates, for example, the conditions under which a penalty will be incurred and the maximum amount. For example, "Penalty limit" includes "Pickup time penalty limit," "Riding time penalty limit," and "Transportation failure penalty limit."

[0159] The "maximum penalty for pickup time" indicates the conditions under which a penalty for pickup time will be incurred and the maximum amount. A penalty for pickup time will be incurred, for example, if the pickup time from the time the service provider receives the dispatch order until the vehicle 12 arrives at the pick-up location exceeds the allowable time (hereinafter referred to as the allowable pickup time), and will be paid by the service provider to the client.

[0160] For example, if the penalty for exceeding the pickup time is a fixed amount, a predetermined penalty will be incurred if the actual pickup time exceeds the allowable pickup time. In contrast, the maximum amount of the penalty for exceeding the pickup time and the allowable pickup time are set as the "maximum penalty for exceeding the pickup time."

[0161] For example, if the pickup time penalty is based on a per-minute system, a penalty will be incurred calculated as the amount of time (minutes) that exceeds the allowable pickup time multiplied by the pickup time penalty per minute. The maximum amount of the pickup time penalty per minute and the allowable pickup time are set as the "pickup time penalty limit."

[0162] The "Maximum Limit for Penalty for Travel Time" indicates the conditions under which a penalty for travel time will be incurred and the maximum amount. A penalty for travel time will be incurred, for example, when the travel time, which is the time required from the boarding location to the destination, exceeds the allowable time (hereinafter referred to as the allowable travel time), and will be paid by the contractor to the client.

[0163] For example, if the penalty for exceeding the allowed travel time is a fixed amount, a predetermined penalty will be incurred when the actual travel time exceeds the allowed travel time. The maximum amount of the penalty and the allowed travel time are set as the "maximum amount of the penalty for exceeding the allowed travel time."

[0164] For example, if the penalty for exceeding the allowed travel time is calculated on a per-minute basis, the penalty will be calculated as the amount of time (in minutes) that exceeds the allowed travel time multiplied by the per-minute travel time penalty. The maximum per-minute travel time penalty and the allowed travel time are set as the "travel time penalty limit."

[0165] The "Transportation Failure Penalty Limit" indicates, for example, the maximum amount of the penalty for a transportation failure. A transportation failure penalty is incurred, for example, when the contractor is unable to transport passengers to their destination due to their own fault, and is paid by the contractor to the client. The maximum amount of the transportation failure penalty is set as the "Transportation Failure Penalty Limit."

[0166] For example, if the administrator of the dispatch platform inputs the immediate purchase conditions to be registered or changed to the control unit 252 via the input unit 251, the order management unit 263 determines that the immediate purchase conditions for the dispatch order should be registered or changed, and the process proceeds to step S2.

[0167] In step S2, the order management unit 263 requests the matching market server 15 to register or change the immediate purchase conditions for the vehicle dispatch order. Specifically, the order management unit 263 transmits information regarding the immediate purchase conditions (hereinafter referred to as immediate purchase condition information) to the matching market server 15 and requests the registration or change of the immediate purchase conditions.

[0168] In response to this, as will be described later, the matching market server 15 registers or modifies the immediate purchase conditions of the dispatch integrated management server 14 (potential customers).

[0169] The process then proceeds to step S3.

[0170] On the other hand, if it is determined in step S1 that the conditions for immediate purchase of the vehicle dispatch order are not to be registered or changed, the process in step S2 is skipped and the process proceeds to step S3.

[0171] In step S3, the order management unit 263 determines whether or not to register or change the inquiry conditions for the vehicle dispatch order.

[0172] The inquiry conditions indicate the conditions under which a potential customer (the integrated dispatch management server 14) will respond to inquiries for dispatch orders in the matching market. For example, the inquiry conditions are those under which a potential customer will purchase (accept) a dispatch order from the matching market after conducting a vehicle search within their own company.

[0173] The items in the inquiry conditions are, for example, the same as the items in the immediate purchase conditions described above. Also, the settings for each item in the inquiry conditions may be the same as or different from the settings for each item in the immediate purchase conditions. The prospective buyer will respond to inquiries for dispatch orders in the matching market whose sales conditions meet the inquiry conditions, and will not respond to inquiries for dispatch orders in the matching market whose sales conditions do not meet the inquiry conditions.

[0174] For example, if the administrator of the dispatch platform inputs the inquiry conditions to be registered or modified to the control unit 252 via the input unit 251, the order management unit 263 determines that the inquiry conditions for the dispatch order should be registered or modified, and the process proceeds to step S4.

[0175] In step S4, the order management unit 263 requests the matching market server 15 to register or change the inquiry conditions for the dispatch order. Specifically, the order management unit 263 sends information indicating the inquiry conditions (hereinafter referred to as inquiry condition information) to the matching market server 15 and requests the registration or change of the inquiry conditions.

[0176] In response to this, as will be described later, the matching market server 15 registers or modifies the inquiry conditions of the vehicle dispatch integrated management server 14 (potential customers).

[0177] The process then proceeds to step S5.

[0178] On the other hand, if it is determined in step S3 that the vehicle dispatch order inquiry conditions are not to be registered or changed, the process in step S4 is skipped and the process proceeds to step S5.

[0179] In step S5, the order management unit 263 determines whether or not it has received a dispatch order from its own APP.

[0180] Here, the company's own APP refers to the platform-based dispatch APP provided by the dispatch platform provider that corresponds to the dispatch integrated management server 14. For example, when the order management unit 263 receives information regarding a dispatch order (hereinafter referred to as dispatch order information) from a user terminal 11 running the company's own APP, it determines that a dispatch order has been received from the company's own APP, and the process proceeds to step S6.

[0181] Ride-hailing order information includes, for example, "date and time of pickup," "pickup location," "destination," "number of passengers," "availability of ride-hailing in the matching market," and "optional conditions."

[0182] "Date and time of ride" indicates, for example, whether it's an immediate dispatch or a scheduled dispatch. If it's a scheduled dispatch, "Date and time of ride" indicates the desired date and time of ride.

[0183] "Boarding location" indicates the desired boarding location.

[0184] "Destination" indicates the desired destination.

[0185] "Number of passengers" is one of the conditions relating to the passengers who are the object of transport by vehicle 12. "Number of passengers" indicates the number of passengers who wish to board.

[0186] "Availability of dispatch in the matching market" indicates whether or not a vehicle can be dispatched in the matching market if it cannot be dispatched using the integrated dispatch management system 51 (platformer) that corresponds to the dispatch APP.

[0187] Optional conditions are those that are set as options if the user requests them. For example, optional conditions may include "vehicle type," "whether or not highway use is permitted," and "type of driver's license."

[0188] "Vehicle type" is one of the conditions relating to the vehicle 12, which is a mobile vehicle for transporting passengers. "Vehicle type" indicates the type of vehicle 12 desired by the user.

[0189] "Whether or not expressways can be used" is one of the conditions regarding the route used to transport passengers. "Whether or not expressways can be used" indicates whether or not the use of expressways is permitted.

[0190] Furthermore, it may be possible to set conditions such as whether or not to use toll roads other than expressways are permitted.

[0191] "Type of license" is one of the conditions concerning the driver of vehicle 12. "Type of license" indicates the type of license that the driver of vehicle 12 will hold, as desired by the user.

[0192] In step S6, the dispatch management server 14 executes the vehicle search process for its own APP.

[0193] Here, we will explain the vehicle search process for our company's APP by referring to the flowchart in Figure 11.

[0194] In step S51, the dispatch management unit 264 determines whether or not to search for a vehicle within its own company. If it is determined that a vehicle should be searched within its own company, the process proceeds to step S52.

[0195] In step S52, the dispatch management unit 264 searches for a vehicle within the company. For example, the dispatch management unit 264 searches for a vehicle 12 that can respond to a dispatch order based on the movement of each of the company's vehicles 12, which is managed by the vehicle movement data management unit 261.

[0196] In step S53, the dispatch management unit 264 determines whether or not a vehicle can be dispatched within the company. If the dispatch management unit 264 finds a vehicle 12 that can respond to the dispatch order, it determines that a vehicle can be dispatched within the company, and the process proceeds to step S54.

[0197] In step S54, the dispatch management unit 264 dispatches a vehicle within the company. Specifically, the dispatch management unit 264 selects one vehicle from the vehicles 12 that are available to handle the dispatch order. The dispatch management unit 264 transmits the dispatch order information to the selected vehicle 12 via the dispatch management device 13 as needed.

[0198] In response, the driver of vehicle 12, upon receiving the dispatch order information, responds to the dispatch order based on the dispatch order information. That is, the driver drives vehicle 12, picks up the user at the pick-up location, and transports them to their destination.

[0199] After that, the vehicle search process for our company's APP is completed.

[0200] On the other hand, in step S53, if the dispatch management unit 264 cannot find a vehicle 12 that can fulfill the dispatch order, it determines that it cannot dispatch a vehicle within its own company, and the process proceeds to step S55.

[0201] In step S55, the order management unit 263 determines whether or not to sell the dispatch order to the matching market. For example, if the dispatch order information indicates that the user does not wish to use the matching market for dispatch, the order management unit 263 determines not to sell the dispatch order to the matching market, and the process proceeds to step S56.

[0202] In step S56, the user terminal control unit 265 notifies the user that a vehicle cannot be dispatched. Specifically, the user terminal control unit 265 controls the platform vehicle dispatch APP running on the user terminal 11 and displays information indicating that a vehicle cannot be dispatched on the user terminal 11.

[0203] After that, the vehicle search process for our company's APP is completed.

[0204] On the other hand, in step S55, for example, if the order management unit 263 determines that the user wishes to use the matching market for dispatch orders, it will sell the dispatch order to the matching market, and the process proceeds to step S57.

[0205] Furthermore, if it is determined in step S51 that no vehicle can be found within the company, the process proceeds to step S57. This occurs, for example, when it is clear that no vehicle 12 available for dispatch within the company is available, such as during peak season or due to a natural disaster.

[0206] In step S57, the vehicle dispatch management server 14 executes the sale process.

[0207] Now, we will explain the details of the sale process by referring to the flowchart in Figure 12.

[0208] In step S101, the order management unit 263 sets the sales conditions.

[0209] The sale conditions are the terms and conditions for selling ride-hailing orders in the matching market.

[0210] The terms of sale include, for example, dispatch order information, ordering party conditions, contract terms unrelated to penalties, conditions under which penalties are incurred, and conditions for selecting the contractor.

[0211] The dispatch order information is the dispatch order information received from the user terminal 11 described above. However, the item "availability of dispatch in the matching market" is removed from the dispatch order information.

[0212] "Ordering party conditions" are the conditions set by the party selling the dispatch order (the ordering party). "Ordering party conditions" include, for example, "contractor blocking conditions" and "contractor rating conditions." "Contractor blocking conditions" and "contractor rating conditions" are conditions that restrict the contractor.

[0213] "Contractor blocking conditions" are one of the conditions related to contractors. "Contractor blocking conditions" are conditions that indicate potential contractors to be excluded from accepting dispatch orders. "Contractor exclusion conditions" are used, for example, to prevent potential contractors with a bad reputation from accepting dispatch orders.

[0214] "Contractor rating conditions" are one of the conditions related to contractors. "Contractor rating conditions" are conditions that restrict the rating of contractors who accept dispatch orders. "Contractor rating conditions" are used, for example, to prevent low-rated candidates from accepting dispatch orders.

[0215] Furthermore, the "ordering party's conditions" may include, for example, conditions that specifically designate the contractor who will accept the dispatch order.

[0216] "Contract terms unrelated to penalty clauses" include, for example, "order amount conditions" and "vehicle search time limits."

[0217] "Order amount conditions" are one of the conditions related to fares (charges). "Order amount conditions" indicate the conditions for the amount at which a dispatch order will be accepted. "Order amount conditions" include, for example, the order amount per unit distance (e.g., 1 km), the order amount per unit time (e.g., 1 minute), and the base charge.

[0218] The "vehicle search time limit" indicates the time limit for searching for a vehicle 12 that can be dispatched. For example, if a vehicle 12 that can be dispatched is not found within the vehicle search time limit, the sale of the dispatch order in the matching market will be canceled.

[0219] "Penalty conditions" indicate, for example, the conditions and amounts under which penalties will be incurred. For example, "Penalty conditions" include "Pickup time penalty conditions," "Boarding time penalty conditions," and "Transportation failure penalty conditions."

[0220] The "Pickup Time Penalty Conditions" indicate the conditions and amounts under which the above-mentioned pickup time penalty will be incurred. For example, if the pickup time penalty is a fixed amount, the "Pickup Time Penalty Conditions" include the amount of the pickup time penalty and the allowable pickup time. For example, if the pickup time penalty is based on usage, the "Pickup Time Penalty Conditions" include the amount of the pickup time penalty per minute and the allowable pickup time.

[0221] The "Riding Time Penalty Conditions" indicate the conditions and amounts under which the aforementioned riding time penalty will be incurred. For example, if the riding time penalty is a fixed amount, the "Riding Time Penalty Conditions" include the amount of the riding time penalty and the allowable riding time. For example, if the riding time penalty is based on usage, the "Riding Time Penalty Conditions" include the amount of the riding time penalty per minute and the allowable riding time.

[0222] The "Transportation Failure Penalty Conditions" indicate the conditions and amounts under which the aforementioned transportation failure penalty will be incurred.

[0223] The "Contractor Selection Criteria" indicates the conditions for selecting a contractor when there are multiple candidates capable of accepting a dispatch order. These criteria can be set, for example, by rating, first-come, first-served, or randomly.

[0224] For example, if the "contractor selection criteria" is set to be in order of rating, the candidate with the higher rating will be given priority in being selected as the contractor. For example, if the "contractor selection criteria" is set to be on a first-come, first-served basis, the candidate who applied earlier will be given priority in being selected as the contractor.

[0225] For example, the order management unit 263 sets sales conditions according to predetermined rules based on dispatch order information and past history stored in the storage unit 255.

[0226] Alternatively, for example, the order management unit 263 sets the sales conditions based on information entered by the dispatch platform administrator via the input unit 251.

[0227] In step S102, the order management unit 263 requests the matching market to sell the dispatch order. Specifically, the order management unit 263 generates dispatch order sale information including the sale conditions and transmits it to the matching market server 15.

[0228] As a result, the dispatch integrated management server 14 (the dispatch platform that manages it) becomes the ordering party.

[0229] In response to this, as will be described later, the matching market server 15 searches for potential customers who can accept the dispatch order. Based on the results of the search for potential customers, the matching market server 15 notifies the dispatch integrated management server 14 whether or not a dispatch is possible.

[0230] In step S103, the order management unit 263 determines whether or not a vehicle is available in the matching market based on a notification from the matching market server 15. If it is determined that a vehicle is available in the matching market, the process proceeds to step S104.

[0231] In step S104, the order management unit 263 receives performance information for dispatch orders from the recipient.

[0232] For example, as will be described later, the matching market server 15 receives performance information showing the actual results for dispatch orders from the dispatch order recipient and transmits it to the dispatch integrated management server 14.

[0233] The performance information includes, for example, the identification information of the person who received the dispatch order, the identification information of the dispatch order, the identification information of the dispatched vehicle 12, the success or failure of passenger transport, the actual value of the pick-up time, the actual value of the ride time, and the actual value of the ride distance.

[0234] In response, the order management unit 263 receives performance information from the matching market server 15.

[0235] In step S105, the order management unit 263 executes settlement processing based on the sales conditions and performance information. For example, the order management unit 263 calculates the order amount and penalty for breach of contract for the recipient based on the sales conditions and performance information. For example, the order management unit 263 executes a procedure to pay the matching market an amount equal to the order amount minus the penalty, plus a market commission.

[0236] In response to this, for example, the matching market server 15 receives market fees and executes procedures to pay control fees to the contractors.

[0237] For example, if the penalty fee exceeds the order amount, the order management unit 263 will request the matching market to pay the amount obtained by subtracting the order amount from the penalty fee, and will carry out the procedure to pay the market commission.

[0238] In response to this, for example, the matching market server 15 receives market fees, invoices the contractors for the payment, and executes the procedure to pay the ordering party (dispatch integrated management server 14).

[0239] In step S106, the dispatch management server 14 evaluates the contractor.

[0240] For example, the order management unit 263 sets a rating for the contractor based on at least one of the following: sales conditions, performance information, and evaluations of drivers entered by the user into the user terminal 11. This ensures that, for example, the degree to which the sales conditions are met and the evaluations of drivers managed by the contractor are reflected in the contractor's rating. The order management unit 263 then notifies the matching market server 15 of the contractor's rating.

[0241] In response, the matching unit 314 of the matching market server 15 stores the rating for the recipient in the storage unit 305.

[0242] For example, the administrator of the dispatch platform may input a rating indicating an evaluation of the contractor to the control unit 252 via the input unit 251.

[0243] After that, the sale process is complete.

[0244] On the other hand, if in step S103 the order management unit 263 determines, based on a notification from the matching market server 15, that a vehicle is not available for dispatch in the matching market, the process proceeds to step S107.

[0245] In step S107, the user is notified that a vehicle cannot be dispatched, similar to the process in step S56 in Figure 11.

[0246] After that, the sale process is complete.

[0247] Returning to Figure 11, after the sales process in step S57, the vehicle search process for our own APP is completed.

[0248] Returning to Figure 10, after the vehicle search process for our company's APP in step S6, the process proceeds to step S7.

[0249] On the other hand, if it is determined in step S5 that no dispatch order has been received from the company's APP, the process in step S6 is skipped, and the process proceeds to step S7.

[0250] In step S7, the order management unit 263 determines whether or not an immediate purchase request for a vehicle dispatch order has been received from the matching market.

[0251] For example, as will be described later, when the matching market server 15 requests the integrated dispatch management server 14 to make an immediate purchase of a dispatch order, it sends the immediate purchase request information, which includes the dispatch order sale information received from the ordering party, to the integrated dispatch management server 14.

[0252] In response, when the order management unit 263 receives information requesting immediate purchase, it determines that an immediate purchase request for a vehicle dispatch order has been made from the matching market, and the process proceeds to step S8.

[0253] As a result, the dispatch integrated management server 14 (the dispatch platform that manages it) becomes the contractor.

[0254] In step S8, the vehicle dispatch integrated management server 14 executes the immediate purchase process.

[0255] Now, referring to the flowchart in Figure 13, we will explain the details of the instant purchase process.

[0256] In step S151, the vehicle is searched for within the company, similar to the process in step S52 in Figure 11.

[0257] In step S152, it is determined whether or not a vehicle can be dispatched within the company, similar to the process in step S53 in Figure 11. If it is determined that a vehicle can be dispatched within the company, the process proceeds to step S153.

[0258] In step S153, the vehicle is dispatched within the company, similar to the process in step S54 in Figure 11.

[0259] In step S154, the order management unit 263 receives performance information for dispatch orders from the vehicle 12.

[0260] For example, the order management unit 182 of the dispatched vehicle 12 transmits the above-mentioned performance information to the integrated dispatch management server 14 via the dispatch management device 13 as needed.

[0261] In response, the order management unit 263 receives performance information from the vehicle 12.

[0262] In step S155, the order management unit 263 transmits performance information for the dispatch order to the matching market server 15. Specifically, the order management unit 263 adds necessary information (for example, identification information of the orderer (dispatch integrated management server 14)) to the performance information received from the vehicle 12 and transmits it to the matching market server 15.

[0263] After that, the instant purchase process is complete.

[0264] On the other hand, if it is determined in step S152 that it is not possible to dispatch a vehicle within the company, the process proceeds to step S156.

[0265] In step S156, the order management unit 263 notifies the matching market server 15 that vehicle dispatch is not possible.

[0266] In this case, although a detailed explanation will be omitted, the settlement of the penalty fee and other related processes will be carried out.

[0267] After that, the instant purchase process is complete.

[0268] Returning to Figure 10, after the immediate purchase process in step S8, the process proceeds to step S9.

[0269] On the other hand, if it is determined in step S7 that no immediate purchase order for vehicle dispatch has been requested from the matching market, the process in step S8 is skipped, and the process proceeds to step S9.

[0270] In step S9, the order management unit 263 determines whether or not it has received a vehicle dispatch order inquiry from the matching market.

[0271] For example, as will be described later, when the matching market server 15 requests the dispatch integrated management server 14 to accept a dispatch order, it sends the dispatch integrated management server 14 order request information, including dispatch order sales information.

[0272] In response, when the order management unit 263 receives order inquiry information, it determines that it has received an inquiry for a vehicle dispatch order from the matching market, and the process proceeds to step S10.

[0273] In step S10, the vehicle dispatch integrated management server 14 executes inquiry response processing.

[0274] Here, we will explain the details of the inquiry handling process by referring to the flowchart in Figure 14.

[0275] In step S201, the vehicle is searched for within the company, similar to the process in step S52 in Figure 11.

[0276] In step S202, it is determined whether or not a vehicle can be dispatched within the company, similar to the process in step S53 in Figure 11. If it is determined that a vehicle can be dispatched within the company, the process proceeds to step S203.

[0277] In step S203, the order management unit 263 notifies the matching market server 15 that a vehicle is available for dispatch.

[0278] In response to this, as will be described later, the matching market server 15 selects a bidder from among the candidates who can accept the order and places a dispatch order with the selected bidder.

[0279] In step S204, the order management unit 263 determines whether or not a dispatch order has been placed. If it is determined that a dispatch order has been placed, the process proceeds to step S205.

[0280] As a result, the dispatch platform provider that manages the integrated dispatch management server 14 becomes the contractor.

[0281] In steps S205 to S207, the same process as in steps S153 to S155 in Figure 13 is executed.

[0282] After that, the inquiry processing is completed.

[0283] On the other hand, if it is determined in step S204 that no dispatch order was placed, the processing in steps S205 to S207 is skipped, and the inquiry handling process ends.

[0284] Furthermore, if it is determined in step S202 that a vehicle cannot be dispatched within the company, the process proceeds to step S206.

[0285] In step S208, similar to the process in step S156 in Figure 13, the matching market server 15 is notified that a vehicle cannot be dispatched.

[0286] After that, the inquiry processing is completed.

[0287] Returning to Figure 10, after the inquiry handling process in step S10, the process returns to step S1, and the processes from step S1 onward are executed.

[0288] On the other hand, if it is determined in step S9 that no dispatch orders have been received from the matching market, the process returns to step S1, and the processes from step S1 onward are executed.

[0289] <Processing by Matching Market Server 15> Next, referring to the flowchart in Figure 15, the processing performed by the Matching Market Server 15 in correspondence with the processing of the Vehicle Dispatch Integrated Management Server 14 in Figure 10 will be explained.

[0290] In step S301, the matching unit 314 determines whether or not a request has been made by the prospective customer to register or change the immediate purchase conditions. Specifically, if the matching unit 314 receives immediate purchase condition information from the prospective customer (dispatch integrated management server 14), it determines that the prospective customer's immediate purchase conditions should be registered or changed, and the process proceeds to step S302.

[0291] In step S302, the matching unit 314 registers or modifies the immediate purchase conditions of the prospective buyer. Specifically, the matching unit 314 stores the immediate purchase conditions of the prospective buyer in the storage unit 305 or modifies the immediate purchase conditions of the prospective buyer stored in the storage unit 305, based on the immediate purchase condition information.

[0292] The process then proceeds to step S303.

[0293] On the other hand, if it is determined in step S301 that the prospective buyer has not requested registration or modification of the immediate purchase conditions, the process in step S302 is skipped, and the process proceeds to step S303.

[0294] In step S303, the matching unit 314 determines whether or not a request has been made by the prospective customer to register or change the inquiry conditions. Specifically, if the matching unit 314 receives inquiry condition information from the prospective customer (dispatch integrated management server 14), it determines that the prospective customer's inquiry conditions should be registered or changed, and the process proceeds to step S304.

[0295] In step S304, the matching unit 314 registers or modifies the inquiry conditions of the prospective customer. Specifically, based on the received information, the matching unit 314 stores the inquiry conditions of the prospective customer in the storage unit 305, or modifies the inquiry conditions of the prospective customer stored in the storage unit 305.

[0296] The process then proceeds to step S305.

[0297] On the other hand, if it is determined in step S303 that the prospective customer has not requested the registration or modification of the inquiry conditions, the process in step S304 is skipped, and the process proceeds to step S305.

[0298] In step S305, the matching unit 314 determines whether or not a request has been made to sell the dispatch order. Specifically, if the matching unit 314 receives dispatch order sale information from the ordering party (dispatch integrated management server 14), it determines that a request has been made to sell the dispatch order, and the process proceeds to step S306.

[0299] In step S306, the matching market server 15 performs the matching process.

[0300] Now, we will explain the details of the matching process by referring to the flowchart in Figure 16.

[0301] In step S351, the matching unit 314 determines whether or not there are any potential customers who can make an immediate purchase. Specifically, the matching unit 314 compares the sales conditions included in the vehicle dispatch order sales information with the immediate purchase conditions of each potential customer stored in the storage unit 305. If there are no potential customers whose immediate purchase conditions satisfy the sales conditions, the matching unit 314 determines that there are no potential customers who can make an immediate purchase, and the process proceeds to step S352.

[0302] In step S352, the matching unit 314 determines whether or not there are any potential customers who can make an inquiry. Specifically, the matching unit 314 compares the sales conditions included in the vehicle dispatch order sales information with the inquiry conditions of each potential customer stored in the storage unit 305. If there is a potential customer whose inquiry conditions satisfy the sales conditions, the matching unit 314 determines that there are potential customers who can make an inquiry, and the process proceeds to step S353.

[0303] In step S353, the matching unit 314 simultaneously inquires with potential customers who are likely to make an inquiry whether they can accept the dispatch order. Specifically, the matching unit 314 generates order inquiry information including dispatch order sales information and simultaneously sends it to potential customers who are likely to make an inquiry, thereby inquiring (inquiring) whether they can accept the dispatch order.

[0304] In step S354, the matching unit 314 determines whether or not a suitable candidate for accepting the order has been found. If none of the candidates who were inquired about the feasibility of accepting the dispatch order have not notified the matching unit 314 that they are able to accept the order (dispatch is possible), the matching unit 314 determines that no suitable candidate for accepting the order has been found, and the process proceeds to step S355.

[0305] On the other hand, in step S352, if there are no prospective buyers whose inquiry conditions meet the sales conditions, the matching unit 314 determines that there are no prospective buyers who can make an inquiry, skips the processing in steps S353 and S354, and proceeds to step S355.

[0306] In steps S355 to S358, the same process as in steps S301 to S304 in Figure 15 is executed. As a result, if a request is received from a potential buyer, the potential buyer's immediate purchase conditions or inquiry conditions are registered or updated.

[0307] In step S359, the matching unit 314 determines whether the vehicle search time limit has elapsed. If the matching unit 314 determines that the vehicle search time limit set in the sales conditions has not yet elapsed since the request for sale of the dispatch order was made, the process returns to step S351.

[0308] Subsequently, steps S351 to S359 are repeatedly executed until it is determined in step S351 that there is a potential customer who can make an immediate purchase, or in step S354 that a potential customer who can make an order has been found, or in step S359 that the vehicle search time limit has expired.

[0309] On the other hand, if it is determined in step S359 that the vehicle search time limit has elapsed, the process proceeds to step S360.

[0310] In step S360, the order management unit 313 notifies the ordering party (for example, the vehicle dispatch integrated management server 14, the user terminal 11, etc.) that vehicle dispatch is not possible.

[0311] The matching process then ends.

[0312] On the other hand, if it is determined in step S351 that there is a potential customer who can make an immediate purchase, or if it is determined in step S354 that a potential customer who can make an order has been found, the process proceeds to step S361.

[0313] In step S361, the matching unit 314 selects the recipient.

[0314] For example, if there is only one potential buyer (one person) who can make an immediate purchase, the matching unit 314 selects that potential buyer as the buyer. On the other hand, if there are multiple potential buyers who can make an immediate purchase, the matching unit 314 selects a buyer based on the buyer selection criteria included in the sales conditions.

[0315] For example, if, as a result of inquiries, only one company (or one person) is found to be capable of accepting the dispatch order, the matching unit 314 selects that candidate as the successful bidder. On the other hand, if, for example, there are multiple candidates who are capable of accepting the dispatch order, the matching unit 314 selects a successful bidder based on the successful bidder selection criteria included in the sales conditions.

[0316] In step S362, the order management unit 313 notifies the ordering party (for example, the vehicle dispatch integrated management server 14, the user terminal 11, etc.) that a vehicle is available for dispatch.

[0317] In step S363, the matching market server 15 executes the order processing.

[0318] Now, we will explain the details of the order processing by referring to the flowchart in Figure 17.

[0319] In step S401, the order management unit 313 places a dispatch order with the contractor. Specifically, the order management unit 313 places a dispatch order with the contractor by transmitting dispatch order sales information to the contractor (for example, the dispatch integrated management server 14, the driver terminal 151, etc.).

[0320] In step S402, the order management unit 313 receives performance information for dispatch orders from the recipient.

[0321] This performance information was transmitted by the contractor, for example, in step S155 of Figure 13 or step S207 of Figure 14 as described above.

[0322] In step S403, the order management unit 313 transmits performance information for the dispatch order to the ordering party (for example, the dispatch integrated management server 14, the user terminal 11, etc.). Specifically, the order management unit 313 adds necessary information to the performance information received from the receiving party and transmits it to the ordering party.

[0323] After that, the order processing is complete.

[0324] Returning to Figure 16, the matching process ends after the order processing in step S363.

[0325] Returning to Figure 15, after the matching process in step S306, the process returns to step S301, and the processes from step S301 onward are executed.

[0326] On the other hand, if it is determined in step S305 that the sale of the vehicle dispatch order has not been requested, the process returns to step S301, and the processes from step S301 onward are executed.

[0327] As described above, if a ride-hailing platform cannot dispatch a vehicle internally, it can, for example, sell the dispatch order to another ride-hailing platform or a vehicle manager via a matching marketplace, and arrange for a vehicle 12 that is under the control of (contracted with) another ride-hailing platform or a vehicle 12 that is not contracted with any ride-hailing platform.

[0328] This reduces the probability of dispatch failures for dispatching platforms, which are the clients, and improves user trust and satisfaction.

[0329] Furthermore, users will be able to ride in vehicles 12 that are contracted with a different ride-hailing platform than the one they normally use, without having to take any special action. This increases the probability of successfully arranging a vehicle 12, improving user convenience.

[0330] Furthermore, for example, users using different ride-hailing platforms will be able to ride in the same shared taxi.

[0331] <Second Embodiment of Processing of Dispatch System 1> Next, a second embodiment of processing of dispatch system 1 will be described with reference to Figures 18 to 29.

[0332] In this second embodiment, the matching market server 15 primarily performs the vehicle search process. In this second embodiment, the processing of vehicles 12 that are not contracted with the dispatch platform, which was omitted from the explanation in the first embodiment, will also be explained.

[0333] <Processing of the Dispatch Management Server 14> First, the processing of the Dispatch Management Server 14 will be explained with reference to the flowchart in Figure 18.

[0334] In step S501, a decision is made whether to register or change the dispatch order inquiry conditions, similar to the process in step S3 in Figure 10. If it is determined that the dispatch order inquiry conditions should be registered or changed, the process proceeds to step S502.

[0335] In step S502, similar to the process in step S4 of Figure 10, a request is made to the matching market server 15 to register or change the dispatch order inquiry conditions.

[0336] The process then proceeds to step S503.

[0337] On the other hand, if it is determined in step S501 that the vehicle dispatch order inquiry conditions are not to be registered or changed, the process in step S502 is skipped, and the process proceeds to step S503.

[0338] In step S503, the vehicle movement data management unit 261 determines whether or not to notify the movement of its own vehicle 12 (vehicle 12 under the dispatch platform). For example, if the conditions for notifying the movement of its own vehicle 12 are met, the vehicle movement data management unit 261 determines to notify the movement of its own vehicle 12, and the process proceeds to step S504.

[0339] Furthermore, the conditions for notifying the status of the company's vehicles 12 can be set arbitrarily. For example, the conditions for notifying the status of the company's vehicles 12 can be set to include when the status of the company's vehicles 12 changes at predetermined time intervals.

[0340] In step S504, the vehicle movement data management unit 261 notifies the matching market server 15 of the movement of its vehicles 12. Specifically, the vehicle movement data management unit 261 transmits vehicle movement data showing the movement of each of its vehicles 12 to the matching market server 15.

[0341] Vehicle movement data includes, for example, the status of vehicle 12, current location, speed, direction of travel, vehicle type, passenger capacity, type of service provided, type of license held by the driver, driver rating, and information for ride-sharing.

[0342] The status of vehicle 12 indicates, for example, the operating status of vehicle 12. The operating status of vehicle 12 can be classified into, for example, occupied, vacant, on call, or out of service. In addition, the operating status of vehicle 12 may include the fares for passengers transported by vehicle 12.

[0343] The types of services offered can be categorized, for example, into regular taxis, shared taxis, ride-sharing services, etc.

[0344] Information for shared rides includes, for example, if vehicle 12 is a shared taxi, the latest number of passengers (or groups), the number of additional passengers (or groups) that can be accommodated, and the conditions for shared ride acceptance, such as whether the user who has already boarded will allow other passengers to board.

[0345] The process then proceeds to step S505.

[0346] On the other hand, in step S503, if the conditions for notifying the movement of its own vehicle 12 are not met, the vehicle movement data management unit 261 determines that it will not notify the movement of its own vehicle 12, skips the process in step S504, and proceeds to step S505.

[0347] In step S505, similar to the process in step S5 of Figure 10, it is determined whether or not a dispatch order has been received from the company's APP. If it is determined that a dispatch order has been received from the company's APP, the process proceeds to step S506.

[0348] In step S506, the vehicle search process for the company's APP is executed in the same manner as the process in step S6 of Figure 10.

[0349] The process then proceeds to step S507.

[0350] On the other hand, if it is determined in step S505 that no dispatch order has been received from the company's APP, the process in step S506 is skipped, and the process proceeds to step S507.

[0351] In step S507, the order management unit 263 determines whether or not it has received an inquiry for a vehicle dispatch order from the matching market. If the order management unit 263 receives order inquiry information from the matching market server 15, it determines that it has received an inquiry for a vehicle dispatch order from the matching market, and the process proceeds to step S508.

[0352] As will be described later, in this case, the order inquiry information specifies the vehicle 12 to which dispatch is requested.

[0353] In step S508, the vehicle dispatch integrated management server 14 executes inquiry response processing.

[0354] Here, we will explain the details of the inquiry handling process by referring to the flowchart in Figure 19.

[0355] In step S551, the dispatch management unit 264 determines whether or not the designated vehicle 12 is available for dispatch.

[0356] For example, the driver terminal control unit 266 communicates with the driver terminal 151 of the designated vehicle 12, presents the details of the dispatch order to the driver terminal 151, and inquires whether it is possible to fulfill the order.

[0357] In response, the driver terminal 151 notifies the dispatch management server 14 whether or not it can respond to the dispatch order entered by the driver.

[0358] In response, the driver terminal control unit 266 determines whether or not the designated vehicle 12 can be dispatched based on the driver's response.

[0359] For example, the dispatch management unit 264 may determine whether or not the designated vehicle 12 is available for dispatch based on the vehicle movement data management unit 261 manages the movement of the designated vehicle 12.

[0360] If it is determined that the designated vehicle 12 is available for dispatch, the process proceeds to step S552.

[0361] In step S552, the dispatch management unit 264 notifies the matching market server 15 that a vehicle is available for dispatch.

[0362] In step S553, the dispatch management unit 264 dispatches the designated vehicle 12. For example, the dispatch management unit 264 transmits dispatch order information to the designated vehicle 12 via the dispatch management device 13 as needed.

[0363] In response, the driver of vehicle 12, upon receiving the dispatch order information, responds to the dispatch order based on the dispatch order information. That is, the driver drives vehicle 12, picks up the user at the pick-up location, and transports them to their destination.

[0364] In steps S554 to S555, the same process as in steps S206 to S207 in Figure 14 is executed.

[0365] After that, the inquiry processing is completed.

[0366] On the other hand, if it is determined in step S551 that the designated vehicle 12 cannot be dispatched, the process proceeds to step S556.

[0367] In step S556, the dispatch management unit 264 notifies the matching market server 15 that dispatch is not possible.

[0368] After that, the inquiry processing is completed.

[0369] Returning to Figure 18, after the inquiry handling process in step S508, the process returns to step S501, and the processes from step S501 onward are executed.

[0370] On the other hand, if it is determined in step S507 that no orders have been received from the matching market, the process returns to step S501, and the processes from step S501 onward are executed.

[0371] <Processing of Vehicle 12> Next, the processing of Vehicle 12 will be explained with reference to the flowchart in Figure 20.

[0372] In step S601, the order management unit 182 of the driver terminal 151 determines whether or not to register or change the dispatch order inquiry conditions.

[0373] For example, the UI control unit 181 of the driver terminal 151 displays the inquiry condition setting screen on the output unit 164 under the control of the driver terminal control unit 316 of the matching market server 15.

[0374] Here, we will explain an example of the inquiry condition setting screen with reference to Figures 21 to 25.

[0375] The inquiry condition setting screens in Figures 21 and 22 include an operation area 401 and a map area 402. The map area 402 and the operation area 401 are displayed side by side in a vertical direction. The operation area 401 can be scrolled vertically, and the displayed content of the operation area 401 differs between Figure 21 and Figure 22.

[0376] The operation area 401 includes a reception range setting field 411, a fare setting field 412, a distance-based additional amount setting field 413, a passenger rating setting field 414, a maximum number of passenger groups setting field 415, and a reservation order handling setting field 416.

[0377] The reception range setting field 411 is used to set the reception range for receiving inquiries for dispatch orders. The reception range is defined, for example, by the radius of a circle centered on the current location of the vehicle 12. For example, dispatch orders whose pick-up location is within the reception range are set as targets for receiving inquiries. In other words, dispatch orders whose pick-up location is within the reception range are targets for vehicle 12 to be approached for order acceptance. In this example, the reception range is set to a radius of 2 km.

[0378] The fare setting field 412 is used to set the minimum fare for dispatch orders that are eligible to receive inquiries. For example, dispatch orders with an estimated fare equal to or greater than the minimum fare are set as eligible to receive inquiries. In other words, dispatch orders with an estimated fare equal to or greater than the minimum fare are eligible to be offered a contract to vehicle 12. In this example, the minimum fare is set to 2,500 yen.

[0379] The distance-based surcharge setting field 413 is used to set the minimum distance-based surcharge for dispatch orders that receive inquiries. The distance-based surcharge is an amount added to the fare for every predetermined unit distance (for example, 1 km).

[0380] For example, dispatch orders where the distance-based surcharge is equal to or greater than the minimum distance-based surcharge are set as targets for receiving inquiries. In other words, dispatch orders where the distance-based surcharge is equal to or greater than the minimum distance-based surcharge are targeted for vehicle 12 to be approached for an order. In this example, the minimum distance-based surcharge is set to 300 yen.

[0381] By setting a minimum distance-based surcharge, for example, ride-hailing orders with a high estimated fare but a low per-distance surcharge will be excluded.

[0382] The passenger rating setting field 414 is used to set the minimum passenger rating for dispatch orders that are eligible to receive inquiries. For example, dispatch orders with passenger ratings equal to or higher than the minimum rating are set as eligible to receive inquiries. In other words, dispatch orders with passenger ratings equal to or higher than the minimum rating are eligible to be approached to accept the order from vehicle 12. In this example, the minimum rating is set to 4.

[0383] Furthermore, the criteria for passenger ratings may not be set using specific values, but rather using relative values, such as passengers in the top x% of ratings.

[0384] The maximum number of shared rides setting field 415 is used to set the maximum number of shared rides, for example, when vehicle 12 is a shared taxi. For example, vehicle 12 responds to ride-hailing requests when the number of shared rides is less than the maximum number of shared rides. In this example, the maximum number of shared rides is set to 3.

[0385] The reservation order handling setting field 416 is used to set whether or not to handle reservation orders. If it is set to handle reservation orders, both reservation orders and immediate dispatch orders will be set as targets for receiving inquiries. In other words, both reservation orders and immediate dispatch orders will be targeted for proposing orders to vehicle 12. On the other hand, if it is set to not handle reservation orders (reservation orders excluded), only immediate dispatch orders will be set as targets for receiving inquiries. In other words, only immediate dispatch orders will be targeted for proposing orders to vehicle 12.

[0386] For example, with pre-orders, drivers may be reluctant to accept them because they need to wait for passengers before the scheduled time. For example, a pre-order handling setting field 416 may be provided for such drivers.

[0387] Map area 402 displays a map of the area surrounding the vehicle 12's current location. Map area 402 also displays the current location 421, reception range 422, and information on dispatch orders that are not subject to inquiries 423.

[0388] The current position 421 indicates the current position and direction of travel of the vehicle 12.

[0389] The reception range 422 indicates the current reception range, based on the reception range set in the reception range setting field 411.

[0390] The non-requested dispatch order information 423 indicates information about non-requested dispatch orders within the displayed map. Non-requested dispatch orders are dispatch orders that do not meet the request conditions for vehicle 12. For example, in the example in Figure 21, the non-requested dispatch order information 423 shows the pick-up location and estimated fare for the non-requested dispatch order. For example, in the example in Figure 22, the non-requested dispatch order information 423 shows the pick-up location and distance to the pick-up location for the non-requested dispatch order.

[0391] Furthermore, the display function for the non-inquiry vehicle dispatch order information 423 may be made available to turn on or off.

[0392] Figure 23 shows another example of the inquiry conditions setting screen. Note that the same reference numerals are used for parts corresponding to the inquiry conditions setting screens in Figures 21 and 22, and their explanations are omitted as appropriate.

[0393] The inquiry conditions setting screen in Figure 23 includes an operation area 401 and a map area 402.

[0394] The operation area 401 includes a status field 451, a reception range setting field 452, and an entry restriction condition setting field 453.

[0395] The status column 451 indicates the status of the vehicle 12. For example, "Accepting a dispatch order" is displayed in the status column 451, or "Stopped" is displayed when the vehicle 12 is stopped, such as when the driver is on a break.

[0396] Unlike the reception range setting field in Figure 21, the reception range in the reception range setting field 452 is defined by the pick-up time, which is the time required to reach the pick-up location. For example, dispatch orders with an estimated pick-up time within the reception range are set as targets for receiving inquiries. In other words, dispatch orders with an estimated pick-up time within the reception range are targets for soliciting orders from vehicle 12. In this example, the reception range is set to within 5 minutes.

[0397] In this case, the reception range is not necessarily circular. For example, the area in front of vehicle 12 becomes wider, while the area behind vehicle 12 where a U-turn is required becomes narrower.

[0398] The entry restriction condition setting field 453 is used to set the entry restriction condition to on or off. Furthermore, when the entry restriction condition is set to on, the entry restriction condition setting field 453 is used to set the specified time and location for the entry restriction condition. For example, the dispatch orders that receive inquiries are limited to those that can be delivered to the specified location by the specified time. This means that, for example, dispatch orders with distant destinations that prevent the vehicle 12 from being delivered to the specified location by the specified time are excluded from inquiries. In other words, for example, dispatch orders with distant destinations that prevent the vehicle 12 from being delivered to the specified location by the specified time are not eligible for an offer to deliver the vehicle 12.

[0399] Map area 402 displays the current location 421, reception range 422, and dispatch order information 423 that is not subject to inquiry, similar to the examples in Figures 21 and 22.

[0400] In this example, the non-requested dispatch order information 423 shows the pick-up location and estimated pick-up time for the dispatch order that is not subject to a request.

[0401] Figure 24 shows an example of the inquiry condition setting screen when vehicle 12 is stopped.

[0402] In this case, "Stopped" will be displayed in status column 451.

[0403] For example, the driver app for the matching market can be linked with driver apps for other platforms. For instance, if a dispatch order is received by another platform's driver app and the status of vehicle 12 becomes "in use," the status field 451 may be automatically set to display "Stopped."

[0404] For example, you could also display the reason why it's "stopped."

[0405] The link button 454 is pressed when linking with other ride-hailing applications.

[0406] Furthermore, for example, a revised proposal to ease the inquiry conditions may be suggested based on the status of vehicle dispatch orders for vehicle 12 (and its driver). For example, if demand is low during off-peak hours and vehicle 12 is available, making it difficult to accept dispatch orders, or if more than a predetermined amount of time has passed since the last dispatch order was handled, or if the number of dispatch orders received within a predetermined time period is below a predetermined threshold, a revised proposal to ease the inquiry conditions may be suggested.

[0407] For example, the UI control unit 181, under the control of the driver terminal control unit 316 of the matching market server 15, displays the inquiry condition setting screen shown in Figure 25 on the output unit 164, thereby proposing proposed changes to the inquiry conditions.

[0408] The inquiry condition setting screen in Figure 25 is a screen that displays recommended values ​​for inquiry conditions, etc., in addition to the inquiry condition setting screen in Figure 21. In Figure 25, the parts corresponding to the inquiry condition setting screen in Figure 21 are denoted by the same reference numerals, and their explanations are omitted as appropriate.

[0409] For example, the recommended minimum fare is displayed in the fare setting field 412. In this example, the recommended minimum fare is 1,500 yen, compared to the current fare of 2,500 yen.

[0410] For example, the recommended minimum distance surcharge amount is displayed in the distance surcharge amount setting field 413. In this example, 200 yen is displayed as the recommended minimum distance surcharge amount, compared to the current 300 yen.

[0411] Additionally, a message 471 is displayed at the bottom of map area 402 prompting users to change their inquiry conditions due to low current demand.

[0412] For example, the driver can fine-tune the inquiry conditions by referring to the recommended values ​​for each setting item.

[0413] Furthermore, the driver can turn the automatic setting mode on or off by operating the automatic setting mode button 472. When the automatic setting mode is on, the inquiry conditions are automatically changed by being set to the recommended values. It may also be possible to allow the driver to make further fine adjustments after the inquiry conditions have been automatically set.

[0414] Furthermore, the recommended values ​​for inquiry conditions may be set based on the vehicle 12 (or its driver)'s dispatch order acceptance status (e.g., difficulty of acceptance). For example, the recommended values ​​for inquiry conditions may change in a direction that relaxes the inquiry conditions as the elapsed time since the last dispatch order is handled increases, or as the number of dispatch orders accepted within a predetermined time decreases.

[0415] Furthermore, if the inquiry conditions are significantly different from the market rate, a notification to that effect may be sent via message or similar means. Similarly, if the set minimum fare is lower than the market rate, a notification to that effect may be sent via message or similar means.

[0416] This allows drivers to set appropriate inquiry conditions so that they can accept dispatch orders.

[0417] For example, if a driver inputs the inquiry conditions to be registered or modified to the control unit 163 via the input unit 161, the order management unit 182 determines that the inquiry conditions for the dispatch order will be registered or modified, and the process proceeds to step S602.

[0418] In step S602, the order management unit 182 requests the matching market server 15 to register or change the inquiry conditions for the dispatch order. Specifically, the order management unit 182 transmits inquiry condition information indicating the inquiry conditions to the matching market server 15 and requests the registration or change of the inquiry conditions.

[0419] In response, the matching market server 15 registers or modifies the inquiry conditions for the vehicle 12 (potential customer).

[0420] The process then proceeds to step S603.

[0421] On the other hand, if it is determined in step S601 that the inquiry conditions for the matching market will not be registered or changed, the process in step S602 is skipped, and the process proceeds to step S603.

[0422] In step S603, the vehicle movement data generation unit 172 determines whether or not to notify the movement of vehicle 12. For example, if the conditions for notifying the movement of vehicle 12 are met, the vehicle movement data generation unit 172 determines to notify the movement of vehicle 12, and the process proceeds to step S604.

[0423] Furthermore, the conditions for notifying the movement of vehicle 12 can be set arbitrarily. For example, the conditions for notifying the movement of vehicle 12 can be set to include when the movement of vehicle 12 changes at predetermined time intervals.

[0424] In step S604, the vehicle movement data generation unit 172 notifies the matching market server 15 of the movement of the vehicle 12. Specifically, the vehicle movement data generation unit 172 generates vehicle movement data showing the movement of the vehicle 12 and transmits it to the matching market server 15.

[0425] The content of the vehicle movement data is, for example, the same as the vehicle movement data transmitted from the vehicle dispatch integrated management server 14 in step S504 of Figure 18 described above.

[0426] The process then proceeds to step S605.

[0427] On the other hand, if it is determined in step S603 that the movement of vehicle 12 is not to be notified, the process in step S604 is skipped, and the process proceeds to step S605.

[0428] In step S605, the order management unit 182 determines whether or not it has received a vehicle dispatch order inquiry from the matching market.

[0429] For example, when the matching market server 15 approaches a vehicle 12 to inquire about accepting a dispatch order, it sends order inquiry information, including dispatch order sales information, to the vehicle 12.

[0430] In response, when the order management unit 182 receives order inquiry information, it determines that it has received an inquiry for a vehicle dispatch order from the matching market, and the process proceeds to step S606.

[0431] In step S606, the vehicle 12 performs inquiry response processing.

[0432] Here, we will explain the details of the inquiry handling process by referring to the flowchart in Figure 26.

[0433] In step S651, the order management unit 182 determines whether or not the vehicle 12 is available for dispatch.

[0434] For example, the output unit 164, under the control of the UI control unit 181, presents information regarding the dispatch order to the driver. For example, the dispatch order notification screen shown in Figure 27 is displayed.

[0435] Note that the same reference numerals are used in the diagram to indicate the parts corresponding to the inquiry condition setting screen in Figure 21, and their explanations are omitted as appropriate.

[0436] The dispatch order notification screen includes an operation area 401 and a map area 402.

[0437] The operation area 401 displays a message notifying the user that an order has been placed from the matching market. The operation area 401 also includes an order button 501.

[0438] The order button 501 is operated when accepting a vehicle dispatch order that has been presented. The order button 501 also displays the time limit for accepting orders.

[0439] Map area 402 displays the current location 421, reception range 422, boarding location 511, destination 512, route 513, and estimated fare 514.

[0440] The boarding location 511 indicates the boarding location for the ride dispatch order.

[0441] Destination 512 indicates the destination of the ride-hailing order.

[0442] Route 513 shows the recommended route from boarding location 511 to destination 512.

[0443] The estimated fare of 514 represents the estimated fare for the ride-hailing order.

[0444] In response, the driver looks at the information regarding the dispatch order and decides whether or not to respond to the dispatch order. The driver inputs the result of the decision on whether or not to respond to the dispatch order to the control unit 163 via the input unit 161.

[0445] In response, if the order management unit 182 determines that vehicle 12 can be dispatched based on the judgment result entered by the driver, the process proceeds to step S652.

[0446] In step S652, the order management unit 182 notifies the matching market server 15 that a vehicle is available for dispatch.

[0447] In step S653, vehicle 12 responds to a dispatch order. Specifically, under the driver's control, vehicle 12 picks up the user at the pick-up location and transports them to their destination.

[0448] In step S654, the order management unit 182 transmits performance information for the dispatch order to the matching market server 15. For example, the order management unit 182 generates performance information showing the actual results for the dispatch order.

[0449] The performance information includes, for example, the identification information of the vehicle dispatch order, the identification information of the vehicle 12, the success or failure of the passenger transportation, the actual value of the pick-up time, the actual value of the boarding time, and the actual value of the boarding distance.

[0450] Note that, for example, the order management unit 182 may automatically generate the performance information, or the driver may input all or part of the performance information.

[0451] The order management unit 182 transmits the performance information to the matching market server 15.

[0452] After that, the negotiation response process ends.

[0453] On the other hand, in step S651, if it is determined that the vehicle 12 cannot be dispatched, the process proceeds to step S655.

[0454] In step S655, the order management unit 182 notifies the matching market server 15 that the vehicle cannot be dispatched.

[0455] After that, the negotiation response process ends.

[0456] Returning to FIG. 20, after the negotiation process in step S606, the process returns to step S601, and the processes after step S601 are executed.

[0457] On the other hand, in step S605, if it is determined that no negotiation for the vehicle dispatch order has been received from the matching market, the process returns to step S601, and the processes after step S601 are executed.

[0458] <Processing of Matching Market Server 15> Next, referring to the flowchart of FIG. 28, the processing executed by the matching market server 15 corresponding to the processing of the vehicle dispatch integration management server 14 in FIG. 18 and the processing of the vehicle 12 in FIG. 20 will be described.

[0459] In steps S701 to S702, the same processing as steps S303 to S304 in FIG. 15 is executed.

[0460] In step S703, the vehicle movement data management unit 311 determines whether or not the movement of vehicle 12 has been notified by the prospective customer (vehicle 12 or the integrated dispatch management server 14). Specifically, if the vehicle movement data management unit 311 receives vehicle movement data from the prospective customer, it determines that the movement of vehicle 12 has been notified by the prospective customer, and the process proceeds to step S704.

[0461] In step S704, the vehicle movement data management unit 311 updates the movement of the vehicles 12. Specifically, the vehicle movement data management unit 311 updates the vehicle movement data for each vehicle 12 stored in the storage unit 305 based on the received vehicle movement data.

[0462] The process then proceeds to step S705.

[0463] On the other hand, if it is determined in step S703 that the prospective customer has not notified the vehicle 12 of its current status, the process in step S704 is skipped, and the process proceeds to step S705.

[0464] In step S705, it is determined whether or not a request has been made to sell the dispatch order, similar to the process in step S305 in Figure 15. If it is determined that a request has been made to sell the dispatch order, the process proceeds to step S706.

[0465] In step S706, the matching market server 15 performs the matching process.

[0466] Now, we will explain the details of the matching process by referring to the flowchart in Figure 29.

[0467] In step S751, the matching unit 314 determines whether or not there is a vehicle 12 that meets the sales conditions. Specifically, the matching unit 314 compares the inquiry conditions of each prospective buyer (each vehicle 12), and the latest status of each vehicle 12 with the sales conditions. If the matching unit 314 determines, based on the comparison results, that there is a vehicle 12 that meets the sales conditions, the process proceeds to step S752.

[0468] In step S752, the matching unit 314 sounds out potential buyers for accepting the dispatch order. Specifically, if a vehicle 12 that meets the sales conditions exists under the dispatch integrated management server 14, the matching unit 314 sends the dispatch inquiry information, including the sales conditions for the dispatch order, to the dispatch integrated management server 14 to inquire whether it is possible to accept the dispatch order. If no vehicle 12 that meets the sales conditions exists under the dispatch integrated management server 14, the matching unit 314 sends the dispatch inquiry information to the vehicle 12 to inquire whether it is possible to accept the dispatch order.

[0469] In this case, the matching unit 314 may select one or more vehicles 12 from among the vehicles 12 that meet the sales conditions to solicit acceptance of the dispatch order. The method of selecting the vehicles 12 is not particularly limited. For example, the vehicles 12 may be selected randomly, in order of the highest driver rating, or in order of proximity to the pickup location of the delivery order.

[0470] In step S753, it is determined whether or not a suitable candidate for receiving the order has been found, similar to the process in step S354 in Figure 16. If it is determined that no suitable candidate for receiving the order has been found, the process proceeds to step S754.

[0471] On the other hand, if it is determined in step S751 that there are no vehicles 12 that meet the sales conditions, the processing in steps S752 to S753 is skipped, and the process proceeds to step S754.

[0472] In steps S754 to S757, the same process as in steps S701 to S704 in Figure 28 is executed.

[0473] In step S758, it is determined whether the vehicle search time limit has elapsed, similar to the process in step S359 in Figure 16. If it is determined that the vehicle search time limit has not elapsed, the process returns to step S751.

[0474] Thereafter, until it is determined in step S753 that an order-receivable order candidate has been found or until it is determined in step S758 that the vehicle search restriction time has elapsed, the processes of steps S751 to S758 are repeatedly executed.

[0475] On the other hand, if it is determined in step S758 that the vehicle search restriction time has elapsed, the process proceeds to step S759.

[0476] In step S759, in the same manner as the process of step S360 in FIG. 16, non-dispatchability is notified to the order placer.

[0477] Thereafter, the matching process ends.

[0478] On the other hand, if it is determined in step S753 that an order-receivable order candidate has been found, the process proceeds to step S760.

[0479] In step S760, the matching unit 314 selects an order receiver. For example, if there is only one order candidate who can receive the vehicle dispatch order (one person), the matching unit 314 selects that order candidate as the order receiver. On the other hand, for example, if there are multiple order candidates who can receive the vehicle dispatch order, the matching unit 314 selects an order receiver based on the order receiver selection conditions included in the selling conditions, etc.

[0480] In step S761, in the same manner as the process of step S362 in FIG. 16, dispatchability is notified to the order placer.

[0481] In step S762, in the same manner as the process of step S363 in FIG. 16, the order placement process is executed.

[0482] Thereafter, the matching process ends.

[0483] Returning to FIG. 28, after the matching process in step S706, the process returns to step S701, and the processes after step S701 are executed.

[0484] On the other hand, if it is determined in step S705 that the sale of the vehicle dispatch order has not been requested, the process returns to step S701, and the processes after step S701 are executed.

[0485] As described above, the matching market server 15 can collect the movements of each vehicle 12 and specify the vehicle 12 for which a dispatch order is to be requested. Furthermore, by recognizing the movements of each vehicle 12, the matching market server 15 can arrange for vehicles 12 more quickly.

[0486] Furthermore, for example, individual vehicle drivers 12 will also be able to participate in the matching market. For example, ride-hailing platform providers are expected to require high levels of discipline from the drivers they contract with in order to enhance their brand image and customer satisfaction.

[0487] In contrast, since the matching market is not affiliated with any particular company, it is expected that participating drivers will have greater freedom. Furthermore, it is expected that drivers will be able to choose which ride-hailing orders they receive within the matching market. Moreover, drivers can easily participate in the matching market simply by installing the matching market driver app on their driver terminal 151.

[0488] <Modified Matching Process> Next, with reference to the flowchart in Figure 30, a modified version of the matching process in step S706 of Figure 28 will be described.

[0489] In steps S801 to S803, the same process as in steps S751 to S753 in Figure 29 is executed.

[0490] In step S804, similar to the process in step S754 in Figure 29, it is determined whether or not it is possible to accept the dispatch order for the selected vehicle 12. If it is determined that it is not possible to accept the dispatch order for the selected vehicle 12, the process proceeds to step S805.

[0491] In step S805, the order management unit 313 determines whether or not the dispatch order was placed directly by the user. If it is determined that the dispatch order was placed directly by the user, that is, if the dispatch order was placed with the matching market using the matching market dispatch APP, the process proceeds to step S806.

[0492] In step S806, the user terminal control unit 315 controls the user terminal 11 to propose to the user a relaxation of the dispatch order conditions.

[0493] For example, the UI control unit 121 of the user terminal 11 displays the order screen on the output unit 104 under the control of the user terminal control unit 315.

[0494] Figure 31 shows an example of an order screen. Note that Figure 31 shows an example of an order screen after the departure and destination locations have been entered.

[0495] The order screen includes an operation area 601 and a map area 602.

[0496] The operation area 601 includes an order area 611, a recommendation setting button 612, a continuous search button 613, a vehicle search range setting field 614, a fare setting field 615, and a driver rating setting field 616.

[0497] Order area 611 is operated when ordering a vehicle from the matching market based on the entered conditions.

[0498] The recommendation setting button 612 is used to configure the recommendation setting function. The recommendation setting function is a function in which the matching unit 314 of the matching market server 15 suggests recommended dispatch order conditions to the user based on the movements of vehicles 12 around the user.

[0499] When the continuous search button 613 is pressed, the continuous search function is executed. The continuous search function is a function that continues searching for a vehicle 12 that meets the conditions of the dispatch order until a vehicle 12 that meets the conditions appears, if no vehicle 12 that meets the conditions of the dispatch order exists.

[0500] The vehicle search range setting field 614 is used to set the range in which the vehicle 12 will be searched. The vehicle search range is set, for example, based on the estimated time when the vehicle 12 is expected to arrive at the pick-up location (estimated pick-up time). In this example, the vehicle search range is set to an area within 5 minutes of the estimated pick-up time from the pick-up location.

[0501] For example, the vehicle search range may be defined by a distance (e.g., radius) centered on the boarding location.

[0502] The fare setting field 615 is used to set the upper limit of the estimated fare from the boarding location to the destination. In this example, the upper limit of the estimated fare is set to 2,500 yen.

[0503] The driver rating setting field 616 is used to set the minimum driver rating. In this example, the minimum driver rating is set to 4. That is, the user has specified that the vehicle 12 will be driven by a driver with a rating of 4 or higher.

[0504] Map area 602 displays a map of the area surrounding the user (user terminal 11). Map area 602 also displays the starting point 621, the search range 622, vehicles 623A to 623C, and the route 624.

[0505] The vehicle detection range 622 indicates the vehicle detection range set in the vehicle detection range setting field 614.

[0506] Vehicles 623A to 623C indicate the location of vehicle 12 that meets the conditions of the dispatch order.

[0507] Route 624 indicates the route from the departure point 621 to the destination.

[0508] For example, if the recommendation setting function is turned on, and there are no vehicles 12 that meet the conditions for the dispatch order, a setting change will be suggested on the order screen, as shown in Figure 32.

[0509] Specifically, a message recommending a setting change will be displayed in the order area 611.

[0510] The recommended vehicle search range is displayed in the vehicle search range setting field 614. In this example, it is suggested to change the vehicle search range from the current 5 minutes to 8 minutes.

[0511] The fare setting section 615 displays the recommended estimated fare conditions. In this example, it is suggested to change the upper limit of the estimated fare from the current 2,500 yen to 3,500 yen.

[0512] In this way, a proposal is made to relax the conditions for dispatch orders.

[0513] The conditions for proposing a change to the dispatch order conditions are set based on, for example, at least one of the demand and supply of vehicles 12. For example, a change to the dispatch order conditions may be proposed if the supply of vehicles 12 is below a predetermined threshold, or if the demand for vehicles 12 is greater than the supply and the difference is above a predetermined threshold.

[0514] Furthermore, the recommended values ​​for proposed changes to the dispatch order conditions may be set based on at least one of the demand and supply of vehicles 12. For example, the recommended values ​​for proposed changes to the dispatch order conditions may be set based on the supply of vehicles 12, or the difference between the demand and supply of vehicles 12.

[0515] Returning to Figure 30, in step S807, the order management unit 313 determines whether or not a change in the conditions of the dispatch order has been requested.

[0516] For example, if a user changes the dispatch order conditions on the order screen shown in Figure 32 using the input unit 101 of the user terminal 11, the order processing unit 122 sends dispatch order change information indicating the changed dispatch order conditions to the matching market server 15.

[0517] In response, when the order management unit 313 of the matching market server 15 receives dispatch order change information from the user terminal 11, it determines that a change in the dispatch order conditions has been requested, and the process proceeds to step S808.

[0518] In step S808, the order management unit 313 changes the sales conditions. That is, the order management unit 313 reflects the changes in the dispatch order conditions in the sales conditions of the dispatch order.

[0519] The process then proceeds to step S809.

[0520] On the other hand, if it is determined in step S807 that no change has been requested to the dispatch order conditions, the process in step S808 is skipped, and the process proceeds to step S809.

[0521] Furthermore, if it is determined in step S805 that the dispatch order was not directly ordered by the user, that is, if the dispatch order was sold to the matching market by the ordering party, the processing in steps S806 to S808 is skipped, and the process proceeds to step S809.

[0522] In steps S809 to S814, the same process as in steps S755 to S760 in Figure 29 is executed, and the matching process is completed.

[0523] On the other hand, if it is determined in step S804 that it is possible to accept the dispatch order for the selected vehicle 12, the process proceeds to step S815.

[0524] In steps S815 to S817, the same process as in steps S761 to S763 in Figure 29 is executed, and the matching process is completed.

[0525] As a result, users have a higher probability of being able to set the conditions for their ride-hailing order appropriately and arrange for a vehicle 12 in a short amount of time.

[0526] <<2. Modified Examples>> Below, we will describe modified examples of the embodiments of the present technology described above.

[0527] <Vehicle dispatch order simulation function> For example, a vehicle dispatch order simulation function may be provided to potential customers.

[0528] The dispatch order simulation function simulates the order status of past dispatch orders based on set inquiry conditions (purchase conditions), and presents the resulting simulation information.

[0529] For example, under the control of the driver terminal control unit 316 of the matching market server 15, the driver terminal 151 that runs the matching market driver APP displays the dispatch order simulation screen shown in Figures 33 and 34.

[0530] The dispatch order simulation screen in Figure 33 includes a time setting field 701, an estimated number of orders field 702, a clear button 703, a reception range setting field 704, a fare setting field 705, and a distance-based additional amount setting field 706.

[0531] The time setting field 701 is used to set the time period to be simulated. In this example, the previous 12 hours are set.

[0532] The Estimated Number of Orders column 702 shows the estimated number of orders based on the simulation (an estimated number of dispatch orders received under the specified conditions) and the actual number of orders (the number of dispatch orders received). In this example, it is shown that the estimated number of orders is 15 and the actual number of orders is 8.

[0533] The clear button 703 is operated to clear the simulation settings.

[0534] The reception range setting field 704 is used to set the reception range conditions, which are expressed by a radius. In this example, the reception range is set to within a radius of 2.5 km.

[0535] The fare setting field 705 is used to set the minimum fare conditions. In this example, the minimum fare is set to 2,200 yen.

[0536] The distance-based charge amount setting field 706 is used to set the minimum distance-based charge amount. In this example, the minimum distance-based charge amount is set to 300 yen.

[0537] The dispatch order simulation screen in Figure 34 includes the setting area 721 and the map area 722.

[0538] The setting area 721 includes a timeline 731, a reception range setting field 732, and an entry restriction condition setting field 733.

[0539] Timeline 731 is used to set the time for displaying the order status of a ride-hailing order. In this example, it is set to 12:05.

[0540] The reception range setting field 732 is used to set the conditions for the reception range, which is expressed by the pick-up time. In this example, the reception range is set to within 7 minutes.

[0541] The entry restriction condition setting field 733 is used to set entry restriction conditions. In this example, it is limited to dispatch orders that can be delivered to the designated location by 04:00.

[0542] Map area 722 displays a map and information about the area surrounding vehicle 12 at the time set in timeline 731. Specifically, the location 741 and reception range 742 of vehicle 12 are displayed. In addition, available dispatch order information 743 is displayed regarding available dispatch orders. Available dispatch order information 743 includes the departure location and pickup time.

[0543] As a result, for example, by manipulating the timeline 731, information showing the time-series changes in the order status of dispatch orders around vehicle 12 is presented under the set conditions.

[0544] Furthermore, the display of the available dispatch order information 743, such as its color, may be changed depending on whether the dispatch order has been accepted or not. In addition, the departure location of the available dispatch order information 743 may be obscured to protect personal information.

[0545] As described above, drivers can simulate past dispatch order acceptance status over time while changing the dispatch order inquiry conditions. This allows drivers to, for example, set inquiry conditions more appropriately and increase the number of dispatch orders accepted and sales.

[0546] <Other variations> In the above explanation, when the matching unit 314 of the matching market server 15 finds a vehicle 12 that meets the sales conditions, it is shown as an example in which it solicits a dispatch order from a potential buyer who manages the vehicle 12 before placing the order. However, it is also possible to place the order without soliciting a dispatch order.

[0547] For example, the processing of the dispatch management device 13, the dispatch integrated management server 14, and the matching market server 15 may be divided and executed by multiple devices.

[0548] The terms and conditions for vehicle dispatch orders, sales conditions, immediate purchase conditions, and inquiry conditions are not limited to the examples given above and can be modified as appropriate.

[0549] The screen examples shown in Figures 21-25, 27, and 31-34 are just examples, and the displayed content and layout can be changed as appropriate.

[0550] As explained in the overview of this technology, this technology can be applied to transportation services that transport items other than taxis from a point of origin to a destination. For example, by applying this technology, if a platform provider that provides transportation services is unable to arrange a vehicle to transport the items within its own network, it will be possible to buy and sell transportation orders in a matching market.

[0551] <<3. Others>> <Example of Computer Configuration> The series of processes described above can be executed by hardware or by software. When the series of processes are executed by software, the programs that make up that software are installed on the computer. Here, a computer includes computers that are built into dedicated hardware, as well as general-purpose personal computers that can perform various functions by installing various programs.

[0552] Figure 35 is a block diagram showing an example of the hardware configuration of a computer that executes the series of processes described above using a program.

[0553] In computer 1000, the CPU (Central Processing Unit) 1001, ROM (Read-Only Memory) 1002, and RAM (Random Access Memory) 1003 are interconnected by a bus 1004.

[0554] An input / output interface 1005 is further connected to the bus 1004. An input unit 1006, an output unit 1007, a storage unit 1008, a communication unit 1009, and a drive 1010 are connected to the input / output interface 1005.

[0555] The input unit 1006 consists of input switches, buttons, a microphone, an image sensor, etc. The output unit 1007 consists of a display, a speaker, etc. The storage unit 1008 consists of a hard disk or non-volatile memory, etc. The communication unit 1009 consists of a network interface, etc. The drive 1010 drives removable media 1011 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory.

[0556] In the computer 1000 configured as described above, the CPU 1001 loads, for example, a program stored in the memory unit 1008 into the RAM 1003 via the input / output interface 1005 and the bus 1004, and executes it, thereby performing the series of processes described above.

[0557] The program executed by the computer 1000 (CPU 1001) can be provided by recording it on a removable medium 1011, such as a package medium. The program can also be provided via wired or wireless transmission media, such as a local area network, the internet, or digital satellite broadcasting.

[0558] In computer 1000, programs can be installed in the storage unit 1008 via the input / output interface 1005 by inserting the removable media 1011 into the drive 1010. Alternatively, programs can be received by the communication unit 1009 via a wired or wireless transmission medium and installed in the storage unit 1008. Furthermore, programs can be pre-installed in the ROM 1002 or the storage unit 1008.

[0559] The programs executed by the computer may be programs that are processed chronologically in the order described herein, or they may be programs that are processed in parallel or at necessary times, such as when a call is made.

[0560] Furthermore, in this specification, a system means a collection of multiple components (devices, modules (parts), etc.), regardless of whether all components are located in the same enclosure or not. Therefore, multiple devices housed in separate enclosures and connected via a network, and a single device in which multiple modules are housed in one enclosure, are both considered systems.

[0561] Furthermore, the embodiments of this technology are not limited to those described above, and various modifications are possible without departing from the spirit of this technology.

[0562] For example, this technology can be configured as cloud computing, where a single function is shared and processed collaboratively by multiple devices via a network.

[0563] Furthermore, each step described in the flowchart above can be performed by a single device, or it can be divided and performed by multiple devices.

[0564] Furthermore, if a single step includes multiple processes, those processes can be executed by a single device or shared among multiple devices.

[0565] <Examples of configuration combinations> This technology can also be configured as follows:

[0566] (1) An information processing method comprising an information processing system comprising one or more information processing devices, which searches for a contractor capable of accepting an order from among potential contractors, including other platform providers, in response to a request for sale of an order from a client, including a platform provider that provides a platform for arranging a mobile vehicle to transport an object to be transported in response to an order from a user. (2) The information processing method according to (1), wherein the information processing system searches for the contractor based on the sales conditions presented by the client and the purchase conditions presented by the potential contractors. (3) The information processing method according to (2), wherein the information processing system searches for the contractor based on the dynamic data of the mobile vehicle managed by each of the potential contractors. (4) The information processing method according to (3), wherein the information processing system selects the mobile vehicle corresponding to the order based on the sales conditions, the purchase conditions, and the dynamic data of the mobile vehicle. (5) The information processing method according to (4), wherein the information processing system requests or inquires with the potential contractors who manage the selected mobile vehicle to transport the object to be transported by the selected mobile vehicle. (6) The information processing method according to any one of (2) to (5) above, further comprising: the information processing system sounding out the prospective bidders who meet the sales conditions whether or not they can accept the order; selecting the bidder from among the prospective bidders who are able to accept the order; and placing the order with the selected bidder. (7) The information processing method according to any one of (2) to (6) above, wherein the sales conditions and purchase conditions include conditions relating to at least one of the following: date and time of transport, place of origin, destination, the transported goods, and the price. (8) The information processing method according to (7) above, wherein the sales conditions further include conditions relating to at least one of the following: the mobile body, the driver who operates the mobile body, and the route for transporting the transported goods. (9) The information processing method according to (7) or (8) above, wherein the sales conditions further include conditions that restrict or specify the bidder. (10) The information processing method according to any one of (7) to (9) above, wherein the sales conditions further include conditions relating to penalties in the event that the conditions specified by the order are not met.(11) The information processing method according to any one of (7) to (10), wherein the sales conditions further include a time limit for searching for the bidder. (12) The information processing method according to any one of (2) to (11), wherein the information processing system proposes proposed changes to the purchase conditions to the bidder candidate based on the bidder candidate's order status. (13) The information processing method according to any one of (2) to (12), wherein the information processing system changes the bidder candidate's purchase conditions based on the bidder candidate's order status. (14) The information processing method according to any one of (2) to (13), wherein the information processing system presents the bidder candidate with simulation information that simulates past order status based on the purchase conditions. (15) The information processing method according to (14), wherein the simulation information includes an estimated number of orders received. (16) The information processing method according to (14) or (15), wherein the simulation information includes information showing the time-series changes in the order status. (17) The information processing system is the information processing method according to any one of (2) to (16) above, wherein the information processing system proposes to the user a change in the conditions of the order based on at least one of the demand quantity and supply quantity of the mobile body. (18) The information processing method according to any one of (2) to (17) above, wherein the purchase conditions include a first purchase condition for accepting the order before searching for a mobile body that can be ordered from among the mobile bodies managed by the prospective order recipient, and a second purchase condition for accepting the order after searching for a mobile body that can be ordered from among the mobile bodies managed by the prospective order recipient. (19) The information processing method according to (1) to (18) above, wherein the mobile body is a taxi, and the platform provider arranges a taxi to transport the user in response to a dispatch order from the user. (20) An information processing device comprising a matching unit that searches for a recipient capable of accepting the order from among prospective order recipients, including other platform providers, in response to a request for sale of the order from a client, which is a platform provider that provides a platform for arranging a mobile body to transport an object to be transported in response to an order from a client.(21) An information processing system comprising: a plurality of first information processing systems that each provide a plurality of different platforms for arranging a mobile body to transport an object to be transported in response to an order from a user; and a second information processing system that searches for other platforms capable of accepting the order in response to a request to sell the order from one of the platforms.

[0567] Furthermore, the effects described herein are merely illustrative and not limiting; other effects may also occur.

[0568] 1 Dispatch system, 11 User terminal, 12 Vehicle 12 Dispatch management device, 14 Dispatch integrated management server 14 Matching market server, 51 Dispatch integrated management system, 71 Dispatch management system, 103 Control unit, 112 Information processing unit, 121 UI control unit, 122 Order processing unit, 151 Driver terminal, 163 Control unit, 172 Vehicle movement data generation unit, 173 Information processing unit, 181 UI control unit, 182 Order management unit, 202 Control unit, 211 Vehicle movement data management unit, 212 Order management unit, 213 Dispatch management unit, 252 Control unit, 261 Vehicle movement data management unit, 263 Order management unit, 264 Dispatch management unit, 265 User terminal control unit, 266 Driver terminal control unit, 302 Control unit, 311 Vehicle movement data management unit, 313 Order management unit, 314 Matching unit, 315 User terminal control unit, 316 Driver terminal control unit

Claims

1. An information processing method comprising an information processing system having one or more information processing devices, which includes searching for a contractor capable of accepting an order from among potential contractors, including other platform providers, in response to a request for the sale of an order from a client, including a platform provider that arranges a mobile vehicle to transport an object to be transported in response to an order from a user.

2. The information processing method according to claim 1, wherein the information processing system searches for the contractor based on the sales conditions presented by the ordering party and the purchase conditions presented by the prospective contractor.

3. The information processing method according to claim 2, wherein the information processing system searches for the successful bidder based on the dynamic data of the mobile body managed by each of the prospective bidders.

4. The information processing method according to claim 3, wherein the information processing system selects the mobile body corresponding to the order based on the sales conditions, the purchase conditions, and the movement data of the mobile body.

5. The information processing method according to claim 4, wherein the information processing system requests or inquires with the candidate for receiving the order who manages the selected mobile body to transport the object to be transported by the selected mobile body.

6. The information processing method according to claim 2, further comprising: the information processing system inquiring whether or not it can accept the order from the prospective buyers who meet the sales conditions; selecting a buyer from among the prospective buyers who are capable of accepting the order; and placing the order with the selected buyer.

7. The information processing method according to claim 2, wherein the sales conditions and purchase conditions include conditions relating to at least one of the following: date and time of transport, place of origin, destination, item to be transported, and fee.

8. The information processing method according to claim 7, wherein the sales conditions further include conditions relating to at least one of the following: the mobile body, the driver operating the mobile body, and the route for transporting the transported object.

9. The information processing method according to claim 7, wherein the sales conditions further include conditions that restrict or specify the recipient.

10. The information processing method according to claim 7, wherein the sales conditions further include conditions relating to penalties in the event that the conditions specified by the order are not met.

11. The information processing method according to claim 7, wherein the sales conditions further include a time limit for searching for the recipient.

12. The information processing method according to claim 2, wherein the information processing system proposes to the candidate for the order a proposed change to the purchase conditions based on the order status of the candidate for the order.

13. The information processing method according to claim 2, wherein the information processing system modifies the purchase conditions of the prospective customer based on the order status of the prospective customer.

14. The information processing method according to claim 2, wherein the information processing system presents to the prospective customer the simulated order status of past orders based on the purchase conditions.

15. The information processing method according to claim 14, wherein the simulation information includes an estimated number of orders received.

16. The information processing method according to claim 14, wherein the simulation information includes information showing the time-series changes in the order status.

17. The information processing method according to claim 2, wherein the information processing system proposes to the user a change in the order conditions based on at least one of the demand and supply quantities of the mobile body.

18. The information processing method according to claim 2, wherein the purchase conditions include a first purchase condition for accepting the order before searching for a mobile body that can be ordered from among the mobile bodies managed by the prospective customer, and a second purchase condition for accepting the order after searching for a mobile body that can be ordered from among the mobile bodies managed by the prospective customer.

19. The information processing method according to claim 1, wherein the mobile entity is a taxi, and the platform provider arranges a taxi to transport a user in response to a ride order from the user.

20. An information processing device comprising a matching unit that searches for a contractor capable of accepting an order from among potential contractors, including other platform providers, in response to a request from a client, which is a platform provider that arranges a mobile vehicle to transport goods in accordance with an order from a user, for the sale of the said order.

21. An information processing system comprising: a plurality of first information processing systems that each provide a plurality of different platforms for arranging a mobile body to transport an object to be transported in response to an order from a user; and a second information processing system that searches for other platforms capable of accepting the order in response to a request to sell the order from one of the platforms.

Images