WO2021193052A1 - Vehicle dispatch management device, vehicle dispatch management method, and program - Google Patents

Vehicle dispatch management device, vehicle dispatch management method, and program Download PDF

Info

Publication number
WO2021193052A1
WO2021193052A1 PCT/JP2021/009440 JP2021009440W WO2021193052A1 WO 2021193052 A1 WO2021193052 A1 WO 2021193052A1 JP 2021009440 W JP2021009440 W JP 2021009440W WO 2021193052 A1 WO2021193052 A1 WO 2021193052A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle allocation
user
request
vehicle
taxi
Prior art date
Application number
PCT/JP2021/009440
Other languages
French (fr)
Japanese (ja)
Inventor
一晃 高橋
眞実 川崎
誠一郎 松本
洋平 橋本
弘之 増田
萌樹 小澤
浩一 佐々木
Original Assignee
ソニーグループ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ソニーグループ株式会社 filed Critical ソニーグループ株式会社
Priority to JP2022509555A priority Critical patent/JPWO2021193052A1/ja
Publication of WO2021193052A1 publication Critical patent/WO2021193052A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/123—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams

Definitions

  • the present technology relates to a vehicle allocation management device, a vehicle allocation management method, and a program, and more particularly to a vehicle allocation management device, a vehicle allocation management method, and a program that can improve the probability of being able to respond to a vehicle allocation request from a specific user such as a priority member. ..
  • a taxi dispatch system is known in which a suitable taxi is determined from a plurality of taxis and dispatched by referring to the taxi operation status (see, for example, Patent Document 1).
  • a method of requesting a taxi user to dispatch a taxi using a smartphone application has become widespread.
  • This technology was made in view of such a situation, and makes it possible to improve the probability of being able to respond to a vehicle allocation request from a specific user such as a priority member.
  • the vehicle allocation management device on one aspect of the present technology transmits a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device to the terminal device of the first user whose vehicle allocation has been confirmed, and the first
  • the management unit is provided to transmit to the terminal device of the second user that the vehicle can be dispatched or boarded.
  • the vehicle allocation management device transmits a request for transfer of the vehicle allocation right or permission to ride on the mobile device to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed. Then, when the notification for permitting the request is received from the terminal device of the first user, it is transmitted to the terminal device of the second user that the vehicle can be dispatched or boarded.
  • the program of one aspect of the present technology receives a process of receiving a request for transfer of the right to dispatch a mobile device or a request for permission to ride on the mobile device from the vehicle allocation management device to a computer, and a notification for granting the request to the vehicle allocation management.
  • the purpose is to execute a process of transmitting to the device and a process of receiving incentive information from the vehicle allocation management device in response to the notification of granting the request.
  • a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose allocation of the mobile device has been confirmed.
  • the notification for permitting the request is received from the terminal device, it is transmitted to the terminal device of the second user that the vehicle can be dispatched or boarded.
  • the vehicle allocation management device which is one aspect of the present technology, can be realized by causing a computer to execute a program.
  • the program to be executed by the computer can be provided by transmitting via a transmission medium or by recording on a recording medium.
  • the vehicle allocation management device may be an independent device or an internal block constituting one device.
  • FIG. 1 is a block diagram showing a configuration example of a taxi dispatch system according to an embodiment to which the present technology is applied.
  • the taxi dispatch system 1 of FIG. 1 is a system for dispatching a taxi as a mobile device to a user based on a request of a user who is a taxi user, and is a system of taxi companies of companies A, B, and C, respectively. It has a vehicle allocation management device 11A to 11C and a vehicle allocation management device 12 which is a vehicle allocation management device that integrally manages them.
  • the vehicle allocation management device 11A of company A is connected to one or more taxis 21A belonging to company A via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.
  • the vehicle allocation management device 11B of company B is connected to one or more taxis 21B belonging to company B via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.
  • the vehicle allocation management device 11C of company C is connected to one or more taxi 21Cs belonging to company C via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.
  • the individual taxi 21D that does not belong to the predetermined company is directly connected to the vehicle allocation integrated management device 12 via the vehicle allocation management device 11 without going through the vehicle allocation management device 11.
  • the taxis 21A to 21C of companies A, B, and C, and the individual taxi 21D are not particularly distinguished, they are simply referred to as taxi 21.
  • the predetermined network is, for example, 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, WAN (WideAreaNetwork), LAN (LocalAreaNetwork), Bluetooth (registration).
  • Wireless communication network that communicates in accordance with the standard (trademark), short-range wireless communication channel such as NFC (Near Field Communication), infrared communication channel, HDMI (registered trademark) (High-Definition Multimedia Interface) and USB ( It can be configured with a communication network or communication path of any communication standard, such as a wired communication communication network that conforms to standards such as Universal Serial Bus).
  • Company A's taxi 21A has an on-board unit 31 and a communication unit 32. Further, the taxi 21A of the company A is equipped with a terminal device 33.
  • the on-board unit 31 acquires necessary data from a toll meter, a GPS (Global Positioning System) receiver, a gyro sensor, a speedometer, etc. (all not shown), and represents a vehicle dynamics log of the vehicle (taxi 21A).
  • the vehicle dynamic data generation unit 34 for generating data is provided.
  • the vehicle dynamic data generation unit 34 acquires data such as the status of "actual vehicle”, “empty vehicle”, or “pick-up vehicle” and the fare (fare) from the fare meter, for example.
  • the status represents the business status of the taxi 21.
  • the vehicle dynamic data generation unit 34 acquires information such as the current position, moving speed, and moving direction of the vehicle from, for example, a GPS receiver, a gyro sensor, a speed meter, and the like.
  • the vehicle dynamic data generation unit 34 generates a company ID for identifying the company to which the taxi 21A belongs, a radio ID for identifying the vehicle of the taxi 21A, a crew ID for identifying the driver who is on the taxi 21A, and a status generation time.
  • Status time representing, taxi 21A position information latitude and longitude, taxi 21A running speed and direction of travel, "real vehicle”, “empty” or “pick-up” status, and status of "real vehicle” or “actual vehicle” or " In the case of "pick-up”, information such as the boarding place and destination of the taxi 21 is generated periodically or irregularly as vehicle dynamic data, and transmitted to the vehicle allocation management device 11A of company A via the communication unit 32. do.
  • the communication unit 32 transmits the vehicle dynamic data generated by the vehicle dynamic data generation unit 34 of the vehicle-mounted device 31 to the vehicle allocation management device 11A of the company A.
  • the communication unit 32 is composed of a network interface that performs network communication via a predetermined network.
  • the terminal device 33 is composed of an information processing device such as a smartphone or a tablet terminal, for example.
  • the driver application 35 which is an application program for the driver, is installed in the terminal device 33.
  • the driver application 35 acquires the data related to the vehicle allocation request from the vehicle allocation management device 12 and displays it on the display, or transmits the response data to the vehicle allocation request to the vehicle allocation management device 12 based on the driver's operation.
  • the driver application 35 directly communicates with the vehicle allocation integrated management device 12 via a network such as a wide area communication network for mobile communication.
  • the driver application 35 may communicate with the vehicle allocation integrated management device 12 via the vehicle allocation management device 11A of the company A via the communication unit 32.
  • Company B's taxi 21B and company C's taxi 21C are basically the same as company A's taxi 21A, except that the company is different, so the explanation is omitted.
  • the vehicle allocation management device 11A of company A collects vehicle dynamic data of one or more taxi 21A of company A and transmits the vehicle dynamic data to the vehicle allocation management device 12 and is transmitted from the vehicle allocation management device 12 to the taxi 21A of company A.
  • the data related to the vehicle dispatch request is relayed and transmitted to the designated taxi 21A of company A.
  • the vehicle allocation management device 11A of company A has a vehicle dynamic data management unit 41, an order information management unit 42, and a communication unit 43.
  • the vehicle allocation management device 11A of company A is composed of, for example, a server device (information processing device) having a network connection function.
  • the vehicle dynamic data management unit 41 manages the vehicle dynamic data supplied from each of the taxi 21A of company A. Specifically, the vehicle dynamic data management unit 41 stores the vehicle dynamic data supplied from each of the taxi 21A of the company A in the internal storage unit, and displays the vehicle dynamic data of each taxi 21A on a display (not shown). .. Further, the vehicle dynamic data management unit 41 transmits the vehicle dynamic data supplied from each taxi 21A to the vehicle allocation integrated management device 12.
  • the order information management unit 42 manages information on prior vehicle allocation requests (vehicle allocation reservations) from customers and the like. For example, when the operator of the taxi 21A of company A receives a call for a vehicle allocation reservation from a customer, the operator inputs information on the vehicle allocation reservation, for example, information such as a pick-up location, a pick-up time, a customer name, and a destination. Is input to the order information management unit 42.
  • the order information management unit 42 stores the information of the vehicle allocation reservation, and displays the vehicle allocation request when the predetermined time before the reservation time comes.
  • the operator who confirms the display of the vehicle allocation request makes a vehicle allocation request to the predetermined taxi 21A based on the vehicle dynamic data stored in the vehicle dynamic data management unit 41.
  • the order information management unit 42 may search for the optimum taxi 21A from the vehicle dynamics data of the vehicle dynamics data management unit 41 and make a vehicle allocation request before the reserved time.
  • the communication unit 43 performs predetermined communication with each of the vehicle allocation integrated management device 12 and the taxi 21A of company A. For example, the communication unit 43 transmits a vehicle allocation request from the vehicle allocation integrated management device 12 to a predetermined taxi 21A, and transmits vehicle dynamic data periodically acquired from each taxi 21A to the vehicle allocation integrated management device 12.
  • the vehicle allocation management devices 11B and 11C of the taxi companies of companies B and C are basically the same as the vehicle allocation management devices 11A of company A, except that the companies are different, so the description thereof will be omitted.
  • company A, company B, and company C are not particularly distinguished, they may be simply referred to as the vehicle allocation management device 11.
  • the vehicle allocation management device 12 transmits and receives data such as vehicle dynamic data and vehicle allocation request to and from the vehicle allocation management devices 11 of companies A, B, and C. Further, the vehicle allocation integrated management device 12 is an application program (hereinafter, referred to as a user application) 61 installed in a terminal device (hereinafter, referred to as a user terminal) 13 of a user who is a taxi user, for requesting a vehicle allocation. Both communicate via a predetermined network.
  • the vehicle allocation integrated management device 12 is composed of, for example, a server device having a network connection function.
  • the vehicle allocation management device 12 is a vehicle allocation management device that manages the vehicle allocation of all taxis 21.
  • the vehicle allocation integrated management device 12 includes a vehicle dynamic data management unit 51, a customer data management unit 52, an order information management unit 53, a vehicle allocation management unit 54, a taxi company communication unit 55, and an application communication unit 56.
  • the vehicle dynamic data management unit 51 manages the vehicle dynamic data supplied from the vehicle allocation management device 11 of each taxi company and each individual taxi 21D. Specifically, the vehicle dynamics data management unit 51 stores vehicle dynamics data supplied from the vehicle allocation management device 11 of each taxi company and each individual taxi 21D in an internal storage unit, and displays the vehicle dynamics data (not shown). To display.
  • the vehicle dynamic data includes the company ID of the taxi 21, the radio ID of the taxi 21, the crew ID, the status time, the position information of the taxi 21, the traveling speed and the direction of travel of the taxi 21, the status, and the status of "actual vehicle” or "pick-up". This is information such as the boarding place and destination of the taxi 21 in the case of.
  • the vehicle dynamic data management unit 51 records the company ID of the taxi 21, the radio ID of the taxi 21, the crew ID, the boarding place and the destination, the fare, etc. every time the status of one "actual vehicle” is completed. It is recorded in the internal storage as the actual vehicle data.
  • the customer data management unit 52 generates customer data based on the data input by the operator or transmitted from the user application 61, and stores it in the internal storage unit.
  • the customer data management unit 52 provides customer data such as a customer's name, a taxi company that the customer likes, a taxi company that wants the customer to preferentially dispatch a vehicle, a frequently used taxi stand, and an average waiting time for picking up. , Stored together with the customer ID, which is the identification information that identifies the customer.
  • the customer data may be data input (designated) by the user in the user application 61, or may be data generated by the customer data management unit 52 based on the user's boarding history or the like.
  • the user (customer) of the user application 61 is classified into either a general member or a priority member as a member type.
  • Priority members are members who receive preferential treatment over general members.
  • the priority member can be determined according to, for example, the usage frequency and usage amount for a certain period in the past, and can be a user whose usage frequency and usage amount are equal to or higher than a certain value. Alternatively, the priority member may assign a paid registration user who has charged a fixed amount.
  • the type of customer member is also stored.
  • the order information management unit 53 manages information on prior vehicle allocation requests (vehicle allocation reservations) from customers and the like.
  • the order information management unit 42 of each vehicle allocation management device 11 is the information of the vehicle allocation request (vehicle allocation reservation) received by each taxi company, whereas the order information management unit 53 is the reservation of the representative who controls each taxi company. It manages the information of the vehicle allocation request (vehicle allocation reservation) received by the center or the user application 61.
  • the order information management unit 53 makes a vehicle allocation request to the vehicle allocation management unit 54 before a predetermined time of the reservation time of the vehicle allocation reservation.
  • the vehicle allocation management unit 54 controls vehicle allocation based on a vehicle allocation request or a vehicle allocation reservation. For example, when the vehicle allocation request is transmitted from the user application 61, the vehicle allocation management unit 54 extracts the taxi 21 that satisfies the vehicle allocation request condition based on the vehicle dynamic data stored in the vehicle dynamic data management unit 51. Then, the dispatch request is sent to the extracted taxi 21. Further, when the vehicle allocation request is transmitted from the order information management unit 53, the vehicle allocation management unit 54 selects the taxi 21 that satisfies the vehicle allocation request condition based on the vehicle dynamic data stored in the vehicle dynamic data management unit 51. Extract and send a vehicle allocation request to the extracted taxi 21.
  • the taxi company communication unit 55 performs predetermined communication with each of the vehicle allocation management devices 11 of each taxi company. For example, the taxi company communication unit 55 receives vehicle dynamic data periodically transmitted from each taxi 21A and supplies the vehicle dynamic data to the vehicle dynamic data management unit 51, or receives a vehicle allocation request from the vehicle allocation management unit 54 for vehicle allocation management. It is transmitted to a predetermined taxi 21 via the device 11.
  • the taxi company communication unit 55 directly communicates with the taxi 21 of each taxi company without going through the vehicle allocation management device 11 of each taxi company to receive vehicle dynamic data or from the vehicle allocation management unit 54.
  • the vehicle dispatch request may be sent to a predetermined taxi 21.
  • the application communication unit 56 performs predetermined communication with the user application 61.
  • the application communication unit 56 receives a vehicle allocation request from the user application 61 and supplies it to the vehicle allocation management unit 54, or sends a vehicle allocation confirmation notification to the user application 61 when the allocation of a predetermined taxi 21 is confirmed. do.
  • the vehicle allocation integrated management device 12 is the user application 61 of a plurality of user terminals 13. And if necessary, the required communication can be performed.
  • the user terminal 13 is composed of, for example, an information processing device such as a smartphone or a tablet terminal, and performs predetermined communication with the vehicle allocation integrated management device 12.
  • the user application 61 requests the vehicle allocation integrated management device 12 to dispatch the taxi 21 based on the user's operation, and displays the vehicle allocation confirmation in response to the vehicle allocation request.
  • the user application 61 can display the current operation status of the taxi 21 on the display by acquiring the vehicle dynamic data in the vicinity of the user's current location from the vehicle allocation integrated management device 12.
  • the vehicle dispatch integrated management device 12 uses the vehicle dynamics of the vehicle dynamics data management unit 51. With reference to the data, the optimum taxi 21 is searched for, and a dispatch request is sent to the searched taxi 21.
  • the vehicle allocation integrated management device 12 When searching for the optimum taxi 21, the vehicle allocation integrated management device 12 first searches for a taxi 21 that responds to a request for a vehicle allocation from among the taxis 21 whose status is "empty”. ..
  • the vehicle allocation integrated management device 12 is constructed with a vehicle allocation control that can respond to a vehicle allocation request from a priority member among the users of the user application 61 with a higher probability than that of a general member.
  • the vehicle allocation integrated management device 12 is another user who is a general member.
  • the taxi 21 assigned to the vehicle allocation request of the above is controlled to allocate the taxi 21 that is picking up at the boarding place of the assigned user so as to reassign it to the priority member user.
  • a general member user who transfers the right to dispatch a vehicle is given a predetermined incentive as a reward for the transfer of the right to dispatch a vehicle.
  • the incentive may be, for example, an electronic coupon for a free pick-up fee or a discount coupon that can be used the next time the vehicle is dispatched, or a free ticket or discount coupon for shops that can be used around the current location or the destination. can.
  • the incentive may be a reward such as electronic money or points given to the transferor for the transfer of the vehicle allocation right.
  • FIG. 2 is a flowchart illustrating a flow of normal vehicle allocation control in the entire taxi dispatch system 1 when an “empty” taxi 21 can be assigned.
  • the vehicle allocation integrated management device 12 acquires the vehicle dynamic data of the taxi 21 from each taxi 21 periodically or irregularly, and updates the vehicle dynamic data of the vehicle dynamic data management unit 51. It is assumed that the process is always executed.
  • step S1 the user activates the user application 61, inputs the boarding place "X" and the destination "Y” to the user application 61, and operates the vehicle allocation request.
  • FIG. 3 shows an example of a vehicle allocation request screen of the user application 61 when the user application 61 is activated in order to make a vehicle allocation request.
  • an area map 81 for displaying a map of the vicinity of the current location, a vehicle allocation request operation unit 82 for performing a vehicle allocation request operation, a boarding place input unit 83 for inputting a boarding location, and a destination input unit for inputting a destination 84 and a payment setting unit 85 for designating a payment method are provided.
  • a taxi mark 91A representing a taxi 21 having a status of "empty” and a taxi mark 91B representing a taxi 21 having a status of "actual vehicle” or “picking up” are displayed on a map according to the current position of the taxi 21. It is displayed at the position of.
  • the taxi mark 91A whose status is "empty” and the taxi mark 91B whose status is “actual vehicle” or “pick-up” are different in display color or pattern and are displayed separately.
  • the taxi mark 91A having the status "empty” is represented in white (plain)
  • the taxi mark 91B having the status "actual vehicle” or "pick-up” is represented in gray.
  • the taxi mark 91B whose status is "actual vehicle” and the taxi mark 91B whose status is "pick-up” are shown in the same color or pattern without distinction, but the taxi mark of "actual vehicle”.
  • the 91B and the taxi mark 91B of "pick-up" may be displayed differently by color or pattern so as to be distinguishable.
  • the taxi mark 91A representing the taxi 21 having the status of "empty” will be referred to as the empty taxi mark 91A
  • the taxi mark 91B having the status of "actual vehicle” or "picking up” will be referred to as the actual vehicle / picking taxi mark 91B. I decided to.
  • the empty taxi mark 91A and the actual / pick-up taxi mark 91B it is simply referred to as the taxi mark 91.
  • the current location mark 93 indicating the user's current location acquired by the GPS receiver of the user terminal 13 and the boarding location mark 94 are displayed at positions corresponding to the boarding locations input by the user to the boarding location input unit 83.
  • the boarding place mark 94 can be freely moved to a desired place on the area map 81 by the user by touch operation, and the address corresponding to the place of the boarding place mark 94 is displayed on the boarding place input unit 83.
  • the operation bar 82A is displayed on the vehicle allocation request operation unit 82, and the vehicle allocation request can be executed by sliding the operation bar 82A to the right side.
  • the boarding place desired by the user is input to the boarding place input unit 83.
  • the boarding location input unit 83 may be left blank when the application is started, or the current location acquired by the GPS receiver may be input by default. If the boarding place input unit 83 is left blank, the boarding place mark 94 is also not displayed.
  • the destination which is the destination desired by the user, is input to the destination input unit 84.
  • the payment setting unit 85 can specify the payment method.
  • As the payment method for example, cash payment to pay the driver in cash, card payment to pay with the credit card registered in the user application 61, or the like can be selected.
  • the payment setting unit 85 of FIG. 3 shows a display example when card payment is specified.
  • the user application 61 displays the taxi mark 91 of the taxi 21 whose status is "empty”, “actual vehicle” or “pick-up”, which is located within a predetermined range according to the scale of the map with respect to the user's current location. It is displayed on the area map 81.
  • step S1 on the vehicle allocation request screen of FIG. 3, the user inputs the boarding place "X" to the boarding place input unit 83, inputs the destination "Y” to the destination input unit 84, and then the operation bar. Corresponds to the operation of sliding 82A to the right.
  • step S2 when the operation bar 82A is slid to the right by the user, in step S2, the user application 61 requests a vehicle allocation together with information on the boarding place “X” and the destination “Y”, and the vehicle allocation integrated management device 12 Send to.
  • step S11 the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the vehicle allocation request from the user application 61, refers to the current vehicle dynamic data managed by the vehicle dynamic data management unit 51, and can dispatch the taxi 21. Is extracted.
  • the taxi 21A of the company A having the status of "empty” is searched for the taxi 21 closest to the boarding place "X".
  • step S12 the vehicle allocation management unit 54 transmits a vehicle allocation request to the searched taxi 21A of company A.
  • step S21 the driver application 35 of the taxi 21A of the company A acquires the data related to the vehicle allocation request from the vehicle allocation integrated management device 12 (for example, the boarding place “X” and the destination “Y”) and displays it on the display. .. Then, when the driver performs a response operation to the effect that the vehicle allocation request is accepted, in step S22, the driver application 35 transmits a request acceptance notification to the effect that the vehicle allocation request is accepted to the vehicle allocation integrated management device 12.
  • the vehicle allocation integrated management device 12 for example, the boarding place “X” and the destination “Y”.
  • the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines the taxi 21A as the taxi to be dispatched, and in step S14, the user's driver application 35 is notified. Send a vehicle dispatch confirmation notice.
  • step S3 When the user's driver application 35 receives the vehicle allocation confirmation notification in step S3, the vehicle allocation confirmation display is performed. Then, when the taxi 21A of company A assigned to the user arrives at the boarding place "X”, in step S4, the user gets on the taxi 21A and starts moving to the destination "Y".
  • step S41 the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received.
  • step S41 If it is determined in step S41 that the vehicle allocation request has been received, the process proceeds to step S42.
  • the vehicle allocation request transmitted from the taxi 21 the user is identified together with the boarding place, destination, and payment method input on the vehicle allocation request screen of the user application 61, as explained with reference to FIG. Contains information such as the user ID and name to be used.
  • step S42 the vehicle allocation management unit 54 refers to the vehicle dynamics data stored in the vehicle dynamics data management unit 51, and from the taxi 21 whose status is "empty", the vehicle allocation request is made to the boarding place for a predetermined time.
  • the taxi 21 that can be dispatched within is extracted.
  • the vehicle allocation management unit 54 calculates the travel time from the current position of the taxi 21 to the boarding place specified by the user for the taxi 21 whose status is "empty", and the calculated travel time is within a predetermined time. Extract taxi 21.
  • step S43 the vehicle allocation management unit 54 determines the taxi 21 that can arrive at the boarding place earliest from the extracted one or more taxi 21 as a vehicle allocation candidate, and in step S44, determines the vehicle allocation candidate. Send a dispatch request to taxi 21.
  • step S45 the vehicle allocation management unit 54 determines whether or not the request acceptance notification has been received from the taxi 21 that has transmitted the vehicle allocation request.
  • step S45 if the taxi 21 that has sent the vehicle allocation request does not receive the request acceptance notification within a certain period of time (for example, 15 seconds), or if the request refusal notification is transmitted, the vehicle allocation management unit 54 It is determined that there is no request acceptance notification, and the process returns to step S43. As a result, the next taxi 21 that can respond to the vehicle allocation request is determined as a vehicle allocation candidate.
  • a certain period of time for example, 15 seconds
  • the vehicle allocation management unit 54 determines in step S45 that the request acceptance notification has been received from the taxi 21 that has sent the vehicle allocation request, and processes the process in step S46. Proceed.
  • step S46 the vehicle allocation management unit 54 determines the taxi 21 that has sent the request acceptance notification to the taxi 21 to be allocated, and transmits the vehicle allocation reservation information to the determined taxi 21.
  • the vehicle allocation reservation information is, for example, information such as the name of the user who has requested the vehicle allocation, the boarding place, the boarding time, and the destination.
  • step S47 the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the user application 61 that has requested the vehicle allocation.
  • the normal vehicle allocation process is executed as described above.
  • the user can be notified that there is no "empty" taxi 21 or can be dispatched. It is unavoidable to have the taxi 21 wait until the taxi 21 is completed, but the vehicle allocation integrated management device 12 controls the vehicle allocation for the priority members so as to respond to the vehicle allocation as much as possible.
  • the vehicle allocation integrated management device 12 if there is a vehicle allocation request from a priority member and there is no taxi 21 having a status of "empty”, the vehicle allocation request has already been confirmed and the status is "pick-up".
  • the taxi 21 that is "” the user of the taxi 21 who is dispatching to the boarding place near the boarding place of the priority member's dispatch request is notified of the transfer request of the vehicle dispatch right, and the vehicle dispatch right is transferred to that user.
  • the vehicle allocation control is executed so as to respond to the vehicle allocation request from the priority member.
  • FIG. 5 is a flowchart illustrating the flow of vehicle allocation control of the entire taxi vehicle allocation system 1 that deals with the vehicle allocation request from the priority member by transferring the vehicle allocation right when the "empty" taxi 21 cannot be assigned.
  • a user who is a priority member activates the user application 61 in step S61, and inputs the boarding place "X" and the destination "Y" to the user application 61. And perform the operation of the vehicle allocation request.
  • the operation of requesting vehicle allocation is the same as the operation described with reference to FIG.
  • step S62 the user application 61 transmits a vehicle allocation request to the vehicle allocation integrated management device 12 together with information on the boarding place "X" and the destination "Y".
  • step S81 the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the vehicle allocation request from the user application 61, refers to the current vehicle dynamic data managed by the vehicle dynamic data management unit 51, and can dispatch the taxi 21. Is extracted. Here, it is assumed that there is no taxi 21 having the status of "empty" in the taxi 21 closest to the boarding place "X".
  • step S82 the vehicle allocation management unit 54 extracts the taxi 21 that is picking up near the boarding place "X" of the priority member.
  • the vehicle allocation is confirmed at the boarding place "X1" near the boarding place "X", and the user A of the general member who is picking up (waiting for the arrival of the taxi 21) (hereinafter referred to as general user A).
  • general user A the user A of the general member who is picking up (waiting for the arrival of the taxi 21)
  • general user B the general member user B who is picking up the taxi is extracted.
  • step S83 the vehicle allocation management unit 54 transmits a transfer request requesting the transfer of the vehicle allocation right to the user application 61 of the general user A and the user application 61 of the general user B.
  • step S101 the user application 61 of the general user A receives the transfer request from the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12, and displays the transfer request screen on the display of the user terminal 13.
  • step S111 the user application 61 of the general user B also receives the transfer request from the vehicle allocation management unit 54 of the vehicle allocation management device 12, and displays the transfer request screen on the display of the user terminal 13.
  • FIG. 6 shows an example of a transfer request screen displayed on the display of the user terminal 13 when a transfer request from the vehicle allocation integrated management device 12 is received.
  • a window 124 with 121, a "transfer” button 122, and a “not transfer” button 123 is displayed.
  • the "transfer” button 122 is operated (pressed) when the user may transfer it.
  • the “do not transfer” button 123 is operated (pressed) when the user does not want to transfer.
  • step S102 the user application 61 of the general user A sends a request permission notification indicating that the vehicle allocation right may be transferred to the vehicle allocation integrated management device 12. Send.
  • step S112 the user application 61 of the general user B transmits a request refusal notice indicating that the vehicle allocation right is not transferred to the vehicle allocation integrated management device 12.
  • step S84 the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the request permission notification from the user application 61 of the general user A and the request refusal notification from the user application 61 of the general user B. Then, the vehicle allocation management unit 54 determines the taxi to be allocated to the priority member based on the received result. In this example, the taxi 21 being picked up by the general user A is determined to be the taxi to be dispatched to the priority member.
  • step S85 the vehicle allocation management unit 54 transmits a change notification of the vehicle allocation request to the driver application 35 of the taxi 21 that is picking up the taxi toward the boarding place of the general user A.
  • the change notification of the vehicle allocation request is, for example, that the vehicle allocation request has been changed from the previously confirmed general user A to a priority member, the name of the priority member, the changed boarding place "X", the boarding time, and the destination. It is information indicating such as.
  • step S141 the driver application 35 of the taxi 21 that is picking up the general user A acquires the data related to the change notification of the vehicle allocation request from the vehicle allocation integrated management device 12 and displays it on the display. Then, when the driver performs a response operation to accept the change in the vehicle allocation request, in step S142, the driver application 35 transmits a request acceptance notification to the effect that the change in the vehicle allocation request is accepted to the vehicle allocation integrated management device 12. do.
  • the vehicle allocation management unit 54 of the vehicle allocation management device 12 receives the request acceptance notification from the taxi 21, in step S86, the vehicle allocation management unit 54 transmits a transfer establishment notification to the user application 61 of the general user A to the effect that the transfer of the vehicle allocation right has been completed. do. Incentive information obtained by transferring the vehicle allocation right, such as the next electronic coupon for which the pick-up fee is free, is also transmitted to the user application 61 of the general user A together with the transfer completion notification. As a result, the general user A who has transferred the vehicle allocation right can use the electronic coupon with no pick-up fee the next time he / she makes a vehicle allocation request.
  • step S87 the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the driver application 35 of the priority member.
  • the order of steps S86 and S87 may be reversed or may be simultaneous (parallel).
  • the vehicle allocation confirmation display is performed.
  • step S181 the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received.
  • step S181 If it is determined in step S181 that the vehicle allocation request has been received, the process proceeds to step S182.
  • the vehicle allocation request received in step S181 is a vehicle allocation request from the priority member, the boarding place is “X”, and the destination is “Y”.
  • step S182 the vehicle allocation management unit 54 refers to the vehicle dynamics data stored in the vehicle dynamics data management unit 51, and from the taxi 21 whose status is "empty", the vehicle allocation request is made to the boarding place for a predetermined time.
  • the taxi 21 that can be dispatched within is extracted.
  • step S183 the vehicle dispatch management unit 54 can dispatch a taxi 21 having a status of "empty”, which can be dispatched to the boarding place "X" requested to be dispatched within a predetermined time. Determine if it exists.
  • step S183 If it is determined in step S183 that normal vehicle allocation is possible, the process proceeds to step S184, and the vehicle allocation management unit 54 executes the normal vehicle allocation process. Specifically, as the normal vehicle allocation process in step S184, the same process as the process in steps S43 to S47 of FIG. 4 is executed.
  • step S183 determines whether the user of the user application 61 that has sent the vehicle allocation request is a priority member. judge.
  • step S185 If it is determined in step S185 that the user is not a priority member, the process proceeds to step S186, and the vehicle allocation management unit 54 says, "Currently, there are no taxis available for dispatch. Please consider changing the vehicle allocation time. A message such as "" is sent to the user application 61 to propose a change in the vehicle allocation time to the user. Therefore, when the user is a general member, the transfer request processing of the vehicle allocation right is not executed.
  • step S185 if it is determined in step S185 that the user is a priority member, the process proceeds to step S187, and the vehicle allocation management unit 54 refers to the vehicle dynamic data of the vehicle dynamic data management unit 51 and gets on the priority member. It is determined whether or not there is a taxi 21 being picked up near the ground "X".
  • the vicinity of the boarding place "X" is, for example, a range in which the distance or time from the boarding place "X" is within a predetermined range.
  • step S187 If it is determined in step S187 that there is no taxi 21 being picked up near the boarding place "X" of the priority member, the process proceeds to step S186 described above. In this case, the vehicle allocation management unit 54 sends a message such as "There are currently no taxis available for dispatch in the surrounding area. Please consider changing the vehicle allocation time" to the user application 61.
  • step S187 if it is determined in step S187 that there is a taxi 21 being picked up near the boarding place "X" of the priority member, the process proceeds to step S188, and the vehicle allocation management unit 54 picks up the taxi near the boarding place "X".
  • a request for transfer of the vehicle allocation right is transmitted to the user application 61 of the user of the taxi 21 inside. Specifically, a request for transfer of the vehicle allocation right is transmitted to the user application 61 of the general user A and the user application 61 of the general user B.
  • step S189 the vehicle allocation management unit 54 waits for a response to the transmitted transfer request for the vehicle allocation right, that is, a request permission notification or a request refusal notification, and a request acceptance notification from one or more users (user application 61). Determine if there was. If the vehicle allocation management unit 54 does not receive the request permission notification within a certain period of time (for example, 15 seconds) from the user who sent the vehicle allocation right transfer request, the vehicle allocation management unit 54 recognizes that the request has been rejected and receives the request refusal notification. Can be treated in the same way as.
  • a response to the transmitted transfer request for the vehicle allocation right that is, a request permission notification or a request refusal notification, and a request acceptance notification from one or more users (user application 61). Determine if there was. If the vehicle allocation management unit 54 does not receive the request permission notification within a certain period of time (for example, 15 seconds) from the user who sent the vehicle allocation right transfer request, the vehicle allocation management unit 54 recognizes that the request has been rejected and receives the request refusal notification. Can be treated in
  • step S189 If it is determined in step S189 that there is no request acceptance notification from one or more users (user application 61), that is, the request refusal notification has been received from all users, the process proceeds to step S186 described above. In this case, a non-dispatchable message such as "There are no taxis that can be dispatched around" is transmitted from the vehicle dispatch management unit 54 to the user application 61.
  • step S189 if it is determined in step S189 that the request acceptance notification has been received from one or more users (user application 61), the process proceeds to step S190, and the vehicle allocation management unit 54 tells the user who has received the request acceptance notification. Determine if you are alone.
  • step S190 If it is determined in step S190 that there is only one user who has received the request acceptance notification, the process proceeds to step S191, and the vehicle allocation management unit 54 determines that the user who has received the request acceptance notification (in the example of FIG. 5, the user).
  • the taxi 21 that is picking up at A) is decided to be the taxi to be dispatched to the priority member.
  • step S190 if it is determined in step S190 that the request acceptance notification has been received from a plurality of users, the process proceeds to step S192, and the vehicle allocation management unit 54 selects the priority member from among the plurality of users who have received the request acceptance notification. Decide which taxi to dispatch.
  • the vehicle allocation management unit 54 selects, for example, the taxi 21 that can arrive at the boarding place "X" of the priority member earliest among the taxi 21 that are being picked up assigned to each of the plurality of users who have received the request acceptance notification. Decide on a taxi to dispatch to.
  • the vehicle allocation management unit 54 is assigned to the user with the lowest transfer amount among the plurality of users who have received the request acceptance notification.
  • the taxi 21 that is being picked up is decided as the taxi to be dispatched to the priority member.
  • the application for the transfer amount may be made to be input by the user in the window 124 of FIG. 6 for confirming whether or not the transfer of the vehicle allocation right is desired, or the user may input the vehicle allocation right on the setting screen of the user application 61 or the like.
  • the permissible amount of money for the transfer may be set in advance.
  • the taxi 21 being picked up assigned to the user with the lower membership type. May be decided as a taxi to be dispatched to priority members.
  • a plurality of users who have returned the request acceptance notification may negotiate by having a conversation via the driver application 35 to determine the user to whom the vehicle allocation right is to be transferred.
  • step S193 the vehicle allocation management unit 54 determines the taxi 21 in the vehicle to which the vehicle allocation right is transferred, in the above example.
  • the driver of the taxi 21 who is picking up at the boarding place "X1" of the general user A confirms the change information of the vehicle allocation request displayed on the display by the driver application 35, and performs an operation to accept the change of the vehicle allocation request. ..
  • a request acceptance notification to accept the change of the vehicle allocation request is transmitted from the driver application 35 to the vehicle allocation integrated management device 12, and is received by the vehicle allocation integrated management device 12.
  • step S194 the vehicle allocation management unit 54 transmits a transfer establishment notification to the effect that the transfer of the vehicle allocation right has been completed, and also transmits incentive information obtained by transferring the vehicle allocation right to the user application 61 of the general user A. ..
  • step S195 the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification indicating that the vehicle allocation has been confirmed in response to the vehicle allocation request to the user application 61 of the priority member.
  • the vehicle allocation confirmation notification includes, for example, information such as a number for identifying the taxi 21 to be allocated, a taxi company name, a radio number, and a pick-up arrival time, and is displayed on the display of the user terminal 13.
  • the pick-up arrival time is the scheduled time when the dispatched taxi 21 arrives at the boarding place "X". Further, the estimated fare from the boarding place "X" to the destination "Y", the estimated arrival time (estimated travel time), and the like may be displayed.
  • the order of steps S194 and S195 may be reversed or may be simultaneous (parallel).
  • a general member The taxi 21 that is being picked up and assigned to the vehicle allocation request of another user can be assigned to the priority member user. As a result, it is possible to improve the probability of being able to respond to a vehicle allocation request from a specific user such as a priority member.
  • the membership types of the users of the user application 61 are divided into general members and priority members, and the user who is the priority member can take over the vehicle allocation right.
  • the general member and the priority member can be transferred. It may be possible to acquire the right to transfer the vehicle allocation right, for example, by paying a predetermined additional charge each time a vehicle allocation request is made without determining the classification of the vehicle allocation.
  • the vehicle allocation management unit 54 extracts the taxi 21 capable of responding to the vehicle allocation request and determines that there is no taxi 21 having a status of "empty", as shown in FIG.
  • the vehicle dispatch request screen is displayed on the user application 61 of the user who performed the vehicle dispatch request operation.
  • the vehicle allocation control described with reference to FIGS. 5 to 7 when it is determined that the user is a priority member and there is no "empty" taxi 21 capable of responding to the vehicle allocation request, it is general.
  • the taxi 21 that can be dispatched to the member is searched for, but even if the user is a priority member, the dispatch request screen of FIG. 8 is displayed and the priority dispatch right is used. After confirming whether or not the taxi is available, the taxi 21 that can be dispatched may be searched. Alternatively, if it is determined that there is no "empty" taxi 21 that can be dispatched, "There are no taxis that can be dispatched around. XX people are waiting for dispatch. Priority dispatch will be given.
  • the priority member may be notified that the priority vehicle is being dispatched. If you notify that you are giving priority to a taxi, and if there is no taxi 21 that you can transfer, you can say, "There was no taxi to which you can transfer the right to assign a taxi.”
  • the execution result message may be displayed.
  • the user (transferee) who wants to transfer the vehicle allocation right may appeal the reason to the user (transferor) who transfers the vehicle allocation right via the user application 61.
  • the transferor may be notified by inputting in the user application 61 that he / she is likely to be late for the university entrance examination, is not in time for an important meeting, or is in a place where an empty taxi does not come.
  • the users to whom the vehicle allocation right is transferred are limited to general members, and the taxi 21 that can be allocated is searched, but the vehicle allocation right is transferred.
  • the users to be received are not limited to general members, but may be searched including priority members.
  • the vehicle allocation integrated management device 12 can acquire the user's setting information and store it in the customer data management unit 52 as customer data. In that case, the vehicle allocation integrated management device 12 selects a user who can request the transfer of the vehicle allocation right from the taxi 21 in the middle of the vehicle allocation (during pick-up) to the user who is set to transfer the vehicle allocation right. The transfer request of the vehicle allocation right is not sent to the user who is searched and is set not to transfer the vehicle allocation right.
  • the taxi 21 that may be transferred the right to dispatch the vehicle and the taxi 21 that is not transferred may be set separately so that the user can recognize them.
  • the user to whom the taxi 21 to which the vehicle allocation right may be transferred can be expected to receive a request for the transfer of the vehicle allocation right.
  • a user who wants to obtain an incentive may dare to use a taxi 21 in which the right to dispatch a vehicle may be transferred.
  • the set number and ratio of taxis 21 for which the right to dispatch vehicles may be transferred and taxi 21 for which dispatch rights are not transferred can be flexibly set depending on the business area, business hours, weather, presence / absence of events, and the like.
  • a user who can transfer the right to dispatch a taxi is searched from among taxis 21 that can arrive within a certain distance or time centering on the boarding place "X" of the priority member's request for dispatch. Made a transfer request.
  • the user who has transferred the right to dispatch a vehicle needs to search for another taxi 21 again or move by an alternative means such as a train or a bus.
  • a user who has made a vehicle allocation request close to each of the boarding place "X" and the destination "Y" of the priority member's vehicle allocation request is searched, and the user is requested to ride. If you send it and receive a notification of acceptance of the request, you can also take the method of riding with you. In this case, both the user who transfers the right to ride and the user who receives the right to ride can arrive at the destination by using the taxi 21.
  • FIG. 9 shows a case where the vehicle allocation integrated management device 12 transmits a vehicle allocation request to the user application 61 of a user who is requesting a vehicle allocation close to each of the boarding place “X” and the destination “Y” of the vehicle allocation request.
  • An example of a passenger request screen displayed on the display of the user terminal 13 to which the request is transmitted is shown.
  • the message 161 "There are passengers who wish to ride. If you allow passengers, the fare to the passenger's destination will be 0 yen. Do you want to allow passengers?"
  • a window 164 with a "Allow” button 162 and a “Don't Allow” button 163 is displayed.
  • the “permit” button 162 is operated (pressed) when the user may allow the ride.
  • the “not allowed” button 163 is operated (pressed) when the user does not want to allow riding.
  • a boarding place mark 181 indicating the boarding place of the user requested to ride On the area map 81, a boarding place mark 181 indicating the boarding place of the user requested to ride, a destination mark 182 indicating the destination, and a planned traveling route 183 of the user requested to ride are displayed.
  • a boarding place mark 184 indicating the boarding place of the user who wishes to ride and a destination mark 185 indicating the destination are also displayed.
  • the user requested to ride can determine the proximity (distance) between the boarding place and destination of the user requesting boarding and his / her boarding place and destination. It can be confirmed, and as an incentive, it is possible to confirm the standard that the fare will be 0 yen.
  • the user who is requested to ride inquires whether or not to change his / her destination according to the destination of the user who requested the ride, and permits the change, the user who is requested to ride May be given an incentive.
  • the process of vehicle allocation control when requesting a ride is basically the same as the process of FIGS. 5 and 7 for requesting the transfer of the vehicle allocation right, so detailed description thereof will be omitted.
  • the process of vehicle allocation control when making a ride request needs to consider not only the boarding place but also the destination when extracting the taxi 21 that can be boarded. The difference is that the transferor's fare can be discounted as an incentive.
  • both the transfer right transfer request and the boarding request may be sent to inquire whether either one is acceptable.
  • the request for transfer of the vehicle allocation right and the request for boarding are sent to the user who is close to the user who wishes to board the vehicle but is slightly away from the destination, and the request is accepted. You may ask if. If the transfer request is approved and the transferor gets off at the destination first, the fare to the transferor's destination will be free (paid by the transferee), or the transferee will get off at the destination first. If so, an incentive can be given to make the fare to the transferee's destination free (paid by the transferee).
  • the vehicle allocation integrated management device 12 extracts a taxi 21 close to the boarding place "X" of the priority member who wants to dispatch from the taxi 21 in the actual vehicle actually carrying the user, and the user of the taxi 21.
  • You may send a ride request or a transfer request to (user application 61).
  • the transferor can discount a part of the fare of the route portion on which the transferee boarded or a part of the total fare as an incentive, as in the modification of the passenger request described above.
  • the fare required for the transferor to transfer to the transferee may be free, and the transferee may pay the fare instead.
  • the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 requests a substitute taxi 21, and as an incentive for the transferor, the fare of the substitute taxi 21 is free. Or a discounted rate.
  • the taxi 21 to be boarded or transferred may be determined with the user who has a short remaining distance to the destination as the transferor.
  • the situation where there is a lot of taxi demand and there is no "empty" taxi 21 is the place, time, weather, for example, in an area where there is no other means of transportation such as a bus, or when commuting to work or school is concentrated. In some cases, it can be predicted in situations such as.
  • the vehicle allocation management unit 54 determines a busy time zone and place (boarding place, destination). You can make suggestions to avoid it.
  • a user changes the time or place of a vehicle allocation request in response to a request from the vehicle allocation management unit 54, it is possible to control the user to be given an incentive.
  • the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives, for example, a vehicle allocation request from a priority member user, and the status is "empty". If there is no taxi 21 at all, the user searches for a taxi 21 that is moving from the boarding place "X" entered in the dispatch request by the priority member user to a place within a predetermined range, and the user. The taxi 21 of A and the taxi 21 of user B are extracted.
  • the vehicle allocation management unit 54 transmits a request for transfer of the vehicle allocation right or permission to ride in the taxi 21 to the terminal device 13 of the user A or the user B (first user) whose taxi 21 has been confirmed to be allocated, and the user A
  • the terminal device 13 of the priority member user (second user) is notified that the vehicle can be dispatched or boarded.
  • the moving device may be an unmanned moving device such as a drone.
  • Computer configuration example> The series of processes described above can be executed by hardware or software.
  • the programs constituting the software are installed on the computer.
  • the computer includes a microcomputer embedded in dedicated hardware and, for example, a general-purpose personal computer capable of executing various functions by installing various programs.
  • FIG. 12 is a block diagram showing a configuration example of computer hardware when the computer executes each process executed by the vehicle allocation integrated management device 12, the user terminal 13, or the terminal device 33 by a program.
  • a CPU Central Processing Unit
  • ROM ReadOnly Memory
  • RAM RandomAccessMemory
  • An input / output interface 205 is further connected to the bus 204.
  • An input unit 206, an output unit 207, a storage unit 208, a communication unit 209, and a drive 210 are connected to the input / output interface 205.
  • the input unit 206 includes operation buttons, a keyboard, a mouse, a microphone, a touch panel, an input terminal, and the like.
  • the output unit 207 includes a display, a speaker, an output terminal, and the like.
  • the storage unit 208 includes a hard disk, a RAM disk, a non-volatile memory, and the like.
  • the communication unit 209 includes a network interface and the like.
  • the drive 210 drives a removable recording medium 211 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.
  • the CPU 201 loads the program stored in the storage unit 208 into the RAM 203 via the input / output interface 205 and the bus 204 and executes the above-described series. Is processed.
  • the RAM 203 also appropriately stores data and the like necessary for the CPU 201 to execute various processes.
  • the program executed by the computer can be recorded and provided on the removable recording medium 211 as a package media or the like, for example. Programs can also be provided via wired or wireless transmission media such as local area networks, the Internet, and digital satellite broadcasts.
  • the program can be installed in the storage unit 208 via the input / output interface 205 by mounting the removable recording medium 211 in the drive 210. Further, the program can be received by the communication unit 209 and installed in the storage unit 208 via a wired or wireless transmission medium. In addition, the program can be pre-installed in the ROM 202 or the storage unit 208.
  • the system means a set of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network, and a device in which a plurality of modules are housed in one housing are both systems. ..
  • the steps described in the flowchart are not necessarily processed in chronological order as well as in chronological order in the order described, but are called in parallel or are called. It may be executed at a necessary timing such as when.
  • this technology can have a cloud computing configuration in which one function is shared by a plurality of devices via a network and processed jointly.
  • each step described in the above flowchart can be executed by one device or shared by a plurality of devices.
  • one step includes a plurality of processes
  • the plurality of processes included in the one step can be executed by one device or shared by a plurality of devices.
  • the present technology can have the following configurations.
  • a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed, and the request is granted from the terminal device of the first user.
  • a vehicle allocation management device including a management unit that transmits the above-mentioned vehicle allocation or riding is possible to the terminal device of the second user when the notification is received.
  • the first user and the second user have different types of registered users.
  • the vehicle allocation management device according to (1) or (2), wherein the second user is a type in which vehicle allocation is prioritized over the first user.
  • the first user to whom the request is transmitted is a user whose allocation of the moving device that has been moved from the boarding place designated by the second user to a place within a predetermined range has been confirmed (1).
  • the management unit transmits a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device to the terminal devices of each of the plurality of first users whose allocation of the mobile device has been confirmed.
  • the vehicle allocation management device according to any one of 4).
  • the management unit can arrive at the boarding place designated by the second user earliest.
  • the first one has the lowest amount of transfer of the right to dispatch the vehicle or permission to ride on the mobile device.
  • the vehicle allocation management device according to (5) above, wherein the mobile device to be assigned to the user is determined to be the mobile device to be assigned to the second user.
  • the management unit transmits whether or not to perform preferential vehicle allocation to the terminal device of the second user, and when a reply is returned that the preferential vehicle allocation is performed, the vehicle allocation of the mobile device has been confirmed.
  • the vehicle allocation management device according to any one of (1) to (7) above, which transmits a request for transfer of the right to dispatch the vehicle or permission to ride on the mobile device to the terminal device of one user.
  • the management unit sends the request to the terminal device of the first user, and if the request is rejected by the first user, the incentive to send the request to the terminal device of the first user when the request is approved.
  • the vehicle allocation management device according to any one of (1) to (8) above, wherein the information is changed and the request is transmitted again.
  • the management unit When the management unit receives a notification for granting the request from the terminal device of the first user, the management unit transmits a notification of change in vehicle allocation of the mobile device to the terminal device mounted on the mobile device.
  • the vehicle allocation management device according to any one of 1) to (9).
  • the vehicle allocation management device A request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed, and the request is granted from the terminal device of the first user.

Landscapes

  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Remote Sensing (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Traffic Control Systems (AREA)

Abstract

The present invention pertains to a vehicle dispatch management device, a vehicle dispatch management method, and a program with which it is possible to improve the probability of being able to respond to a vehicle dispatch request from a specific user such as a priority member. This vehicle dispatch integrated management device transmits a request to transfer the right to a vehicle dispatch or a request for permission to ride together in a taxi to a terminal device belonging to a first user for whom dispatch of a taxi has been confirmed, and if a notification granting the request is received from the terminal device belonging to the first user, transmits that it is possible to dispatch a vehicle or to ride together to a terminal device belonging to a second user. The present invention can be applied to a taxi vehicle dispatch system, for example.

Description

配車管理装置、配車管理方法、およびプログラムVehicle allocation management device, vehicle allocation management method, and program
　本技術は、配車管理装置、配車管理方法、およびプログラムに関し、特に、優先会員等の特定のユーザからの配車依頼に対応できる確率を向上できるようにした配車管理装置、配車管理方法、およびプログラムに関する。 The present technology relates to a vehicle allocation management device, a vehicle allocation management method, and a program, and more particularly to a vehicle allocation management device, a vehicle allocation management method, and a program that can improve the probability of being able to respond to a vehicle allocation request from a specific user such as a priority member. ..
　タクシーの運行状況を参照し、複数のタクシーの中から適したタクシーを決定して配車するタクシーの配車システムが知られている（例えば、特許文献１参照）。近年では、タクシー利用者がスマートフォンのアプリを使って配車を依頼する依頼方法も普及してきている。 A taxi dispatch system is known in which a suitable taxi is determined from a plurality of taxis and dispatched by referring to the taxi operation status (see, for example, Patent Document 1). In recent years, a method of requesting a taxi user to dispatch a taxi using a smartphone application has become widespread.
　配車を依頼できるアプリの利用者のうち、利用頻度や利用額が多いユーザや、有料登録のユーザなどに対して、一般会員とは別の優先会員とする制度を設けた場合、優先会員からの配車の依頼に対しては、必ず応えられることが望ましい。 Among the users of the app that can request vehicle dispatch, if a system is set up to make priority members different from general members for users who use frequently and usage amount, users who are registered for a fee, etc., the priority members will It is desirable to be able to respond to requests for vehicle dispatch.
特開２００３－１０９１９１号公報Japanese Unexamined Patent Publication No. 2003-109191
　しかしながら、配車依頼の場所や時間、天候、その他の状況によってタクシー需要が多い場合は必ず存在し、希望の配車依頼に対して必ず応えられることが難しい場合がある。そうであるからといって、優先会員からの配車依頼に対する応答用の配車余剰枠を設けておくことは無駄になる場合もあり得るし、仮に配車余剰枠を設けておいたとしても、どの場所から配車依頼がなされるかが不明であるため、即座に対応できるかどうかは不明である。 However, there is always a lot of taxi demand depending on the location, time, weather, and other conditions of the vehicle dispatch request, and it may be difficult to always respond to the desired vehicle dispatch request. Even so, it may be useless to provide a vehicle allocation surplus frame for responding to a vehicle allocation request from a priority member, and even if a vehicle allocation surplus frame is provided, any place. Since it is unclear whether a vehicle dispatch request will be made from, it is unclear whether it will be possible to respond immediately.
　本技術は、このような状況に鑑みてなされたものであり、優先会員等の特定のユーザからの配車依頼に対応できる確率を向上させることができるようにするものである。 This technology was made in view of such a situation, and makes it possible to improve the probability of being able to respond to a vehicle allocation request from a specific user such as a priority member.
　本技術の一側面の配車管理装置は、移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信し、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、第２のユーザの端末装置へ、前記配車または同乗が可能であることを送信する管理部を備える。 The vehicle allocation management device on one aspect of the present technology transmits a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device to the terminal device of the first user whose vehicle allocation has been confirmed, and the first When a notification for permitting the request is received from the terminal device of the user, the management unit is provided to transmit to the terminal device of the second user that the vehicle can be dispatched or boarded.
　本技術の一側面の配車管理方法は、配車管理装置が、移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信し、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、第２のユーザの端末装置へ、前記配車または同乗が可能であることを送信する。 In the vehicle allocation management method of one aspect of the present technology, the vehicle allocation management device transmits a request for transfer of the vehicle allocation right or permission to ride on the mobile device to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed. Then, when the notification for permitting the request is received from the terminal device of the first user, it is transmitted to the terminal device of the second user that the vehicle can be dispatched or boarded.
　本技術の一側面のプログラムは、コンピュータに、移動装置の配車の権利譲渡または前記移動装置への同乗許可の依頼を、配車管理装置から受信する処理と、前記依頼を許諾する通知を前記配車管理装置へ送信する処理と、前記依頼を許諾する通知に応じて、前記配車管理装置から、インセンティブ情報を受信する処理とを実行させるためのものである。 The program of one aspect of the present technology receives a process of receiving a request for transfer of the right to dispatch a mobile device or a request for permission to ride on the mobile device from the vehicle allocation management device to a computer, and a notification for granting the request to the vehicle allocation management. The purpose is to execute a process of transmitting to the device and a process of receiving incentive information from the vehicle allocation management device in response to the notification of granting the request.
　本技術の一側面においては、移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼が送信され、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、第２のユーザの端末装置へ、前記配車または同乗が可能であることが送信される。 In one aspect of the present technology, a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose allocation of the mobile device has been confirmed. When the notification for permitting the request is received from the terminal device, it is transmitted to the terminal device of the second user that the vehicle can be dispatched or boarded.
　なお、本技術の一側面の配車管理装置は、コンピュータにプログラムを実行させることにより実現することができる。コンピュータに実行させるプログラムは、伝送媒体を介して伝送することにより、又は、記録媒体に記録して、提供することができる。 The vehicle allocation management device, which is one aspect of the present technology, can be realized by causing a computer to execute a program. The program to be executed by the computer can be provided by transmitting via a transmission medium or by recording on a recording medium.
　配車管理装置は、独立した装置であっても良いし、１つの装置を構成している内部ブロックであっても良い。 The vehicle allocation management device may be an independent device or an internal block constituting one device.
本技術を適用した実施の形態であるタクシー配車システムの構成例を示すブロック図である。It is a block diagram which shows the configuration example of the taxi dispatch system which is the embodiment to which this technology is applied. 通常配車制御の流れを説明するフローチャートである。It is a flowchart explaining the flow of normal vehicle allocation control. ユーザアプリの配車依頼画面の例を示す図である。It is a figure which shows the example of the vehicle dispatch request screen of a user application. 配車統合管理装置による通常配車処理を説明するフローチャートである。It is a flowchart explaining the normal vehicle allocation processing by a vehicle allocation integrated management device. 配車権利の譲渡で対処する配車制御の流れを説明するフローチャートである。It is a flowchart explaining the flow of the vehicle allocation control to deal with by the transfer of the vehicle allocation right. ユーザ端末のディスプレイに表示される譲渡依頼画面の例を示す図である。It is a figure which shows the example of the transfer request screen displayed on the display of a user terminal. 配車権利譲渡の依頼を行う配車処理の詳細を説明するフローチャートである。It is a flowchart explaining the detail of the vehicle allocation process which requests the transfer of the vehicle allocation right. 「空車」のタクシーが１台も存在しない場合の配車依頼画面を示す図である。It is a figure which shows the dispatch request screen when there is no "empty" taxi. 同乗依頼画面の例を示す図である。It is a figure which shows the example of the passenger request screen. 本技術を適用したコンピュータの一実施の形態の構成例を示すブロック図である。It is a block diagram which shows the structural example of one Embodiment of the computer to which this technique is applied.
　以下、添付図面を参照しながら、本技術を実施するための形態（以下、実施の形態という）について説明する。なお、本明細書及び図面において、実質的に同一の機能構成を有する構成要素については、同一の符号を付することにより重複説明を省略する。説明は以下の順序で行う。
１．タクシー配車システムの構成例
２．通常配車制御の流れ
３．配車統合管理装置の通常配車処理
４．配車権利譲渡の依頼を行う場合の配車制御の流れ
５．配車権利譲渡の依頼を行う配車統合管理装置の配車処理
６．同乗依頼を行う変形例
７．配車権利譲渡の変形例
８．実施の形態のまとめ
９．コンピュータ構成例 Hereinafter, embodiments for carrying out the present technology (hereinafter referred to as embodiments) will be described with reference to the accompanying drawings. In the present specification and the drawings, components having substantially the same functional configuration are designated by the same reference numerals, so that duplicate description will be omitted. The explanation will be given in the following order.
1. 1. Configuration example of taxi dispatch system 2. Flow of normal vehicle allocation control 3. Normal vehicle allocation processing of the vehicle allocation integrated management device 4. Flow of vehicle allocation control when requesting transfer of vehicle allocation right 5. Vehicle allocation processing of the vehicle allocation integrated management device that requests the transfer of vehicle allocation rights 6. Modification example of making a ride request 7. Modification example of transfer of vehicle allocation right 8. Summary of embodiments 9. Computer configuration example
＜１．タクシー配車システムの構成例＞
　図１は、本技術を適用した実施の形態であるタクシー配車システムの構成例を示すブロック図である。 <1. Configuration example of taxi dispatch system>
FIG. 1 is a block diagram showing a configuration example of a taxi dispatch system according to an embodiment to which the present technology is applied.
　図１のタクシー配車システム１は、タクシーの利用者であるユーザの依頼に基づいて、移動装置としてのタクシーをユーザに配車するシステムであり、A社、B社、およびC社それぞれのタクシー会社の配車管理装置１１A乃至１１Cと、それらを統合管理する配車管理装置である配車統合管理装置１２とを有する。 The taxi dispatch system 1 of FIG. 1 is a system for dispatching a taxi as a mobile device to a user based on a request of a user who is a taxi user, and is a system of taxi companies of companies A, B, and C, respectively. It has a vehicle allocation management device 11A to 11C and a vehicle allocation management device 12 which is a vehicle allocation management device that integrally manages them.
　A社の配車管理装置１１Aは、A社に属する１以上のタクシー２１Aと所定のネットワークを介して接続されるとともに、配車統合管理装置１２とも所定のネットワークを介して接続されている。 The vehicle allocation management device 11A of company A is connected to one or more taxis 21A belonging to company A via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.
　同様に、B社の配車管理装置１１Bは、B社に属する１以上のタクシー２１Bと所定のネットワークを介して接続されるとともに、配車統合管理装置１２とも所定のネットワークを介して接続されている。 Similarly, the vehicle allocation management device 11B of company B is connected to one or more taxis 21B belonging to company B via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.
　同様に、C社の配車管理装置１１Cは、C社に属する１以上のタクシー２１Cと所定のネットワークを介して接続されるとともに、配車統合管理装置１２とも所定のネットワークを介して接続されている。 Similarly, the vehicle allocation management device 11C of company C is connected to one or more taxi 21Cs belonging to company C via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.
　また、所定の会社に属さない個人タクシー２１Dは、配車管理装置１１を介さず、直接、配車統合管理装置１２と所定のネットワークを介して接続されている。A社、B社、およびC社それぞれのタクシー２１A乃至２１C、並びに、個人タクシー２１Dを特に区別しない場合には、単に、タクシー２１と称する。 Further, the individual taxi 21D that does not belong to the predetermined company is directly connected to the vehicle allocation integrated management device 12 via the vehicle allocation management device 11 without going through the vehicle allocation management device 11. When the taxis 21A to 21C of companies A, B, and C, and the individual taxi 21D are not particularly distinguished, they are simply referred to as taxi 21.
　ここで、所定のネットワークは、例えば、インターネット、公衆電話回線網、所謂4G回線や5G回線等の携帯通信用の広域通信網、WAN（Wide Area Network）、LAN（Local Area Network）、Bluetooth（登録商標）規格に準拠した通信を行う無線通信網、NFC（Near Field Communication）等の近距離無線通信の通信路、赤外線通信の通信路、HDMI（登録商標）（High-Definition Multimedia Interface）やUSB（Universal Serial Bus）等の規格に準拠した有線通信の通信網等、任意の通信規格の通信網や通信路で構成することができる。 Here, the predetermined network is, for example, 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, WAN (WideAreaNetwork), LAN (LocalAreaNetwork), Bluetooth (registration). Wireless communication network that communicates in accordance with the standard (trademark), short-range wireless communication channel such as NFC (Near Field Communication), infrared communication channel, HDMI (registered trademark) (High-Definition Multimedia Interface) and USB ( It can be configured with a communication network or communication path of any communication standard, such as a wired communication communication network that conforms to standards such as Universal Serial Bus).
　A社のタクシー２１Aは、車載器３１と、通信部３２とを有する。また、A社のタクシー２１Aには、端末装置３３が搭載されている。 Company A's taxi 21A has an on-board unit 31 and a communication unit 32. Further, the taxi 21A of the company A is equipped with a terminal device 33.
　車載器３１は、料金メータ、GPS (Global Positioning System)受信機、ジャイロセンサ、速度メータなど（いずれも不図示）から、必要なデータを取得し、車両（タクシー２１A）の動態ログを表す車両動態データを生成する車両動態データ生成部３４を備える。 The on-board unit 31 acquires necessary data from a toll meter, a GPS (Global Positioning System) receiver, a gyro sensor, a speedometer, etc. (all not shown), and represents a vehicle dynamics log of the vehicle (taxi 21A). The vehicle dynamic data generation unit 34 for generating data is provided.
　車両動態データ生成部３４は、例えば、料金メータから、「実車」、「空車」、または「迎車」のステータスと、料金（運賃）などのデータを取得する。ステータスは、タクシー２１の営業状態を表す。また、車両動態データ生成部３４は、例えば、GPS受信機、ジャイロセンサ、速度メータなどから、車両の現在位置、移動速度および移動方向などの情報を取得する。 The vehicle dynamic data generation unit 34 acquires data such as the status of "actual vehicle", "empty vehicle", or "pick-up vehicle" and the fare (fare) from the fare meter, for example. The status represents the business status of the taxi 21. Further, the vehicle dynamic data generation unit 34 acquires information such as the current position, moving speed, and moving direction of the vehicle from, for example, a GPS receiver, a gyro sensor, a speed meter, and the like.
　そして、車両動態データ生成部３４は、タクシー２１Aが所属する会社を識別する会社ID、タクシー２１Aの車両を識別する無線ID、タクシー２１Aに乗務しているドライバを識別する乗務員ID、ステータスの生成時刻を表すステータス時刻、タクシー２１Aの位置情報である緯度および経度、タクシー２１Aの走行速度および進行方向、「実車」、「空車」、または、「迎車」のステータス、並びに、ステータスが「実車」または「迎車」の場合にはそのタクシー２１の乗車地および目的地、などの情報を、車両動態データとして定期的または不定期に生成し、通信部３２を介して、A社の配車管理装置１１Aに送信する。 Then, the vehicle dynamic data generation unit 34 generates a company ID for identifying the company to which the taxi 21A belongs, a radio ID for identifying the vehicle of the taxi 21A, a crew ID for identifying the driver who is on the taxi 21A, and a status generation time. Status time representing, taxi 21A position information latitude and longitude, taxi 21A running speed and direction of travel, "real vehicle", "empty" or "pick-up" status, and status of "real vehicle" or "actual vehicle" or " In the case of "pick-up", information such as the boarding place and destination of the taxi 21 is generated periodically or irregularly as vehicle dynamic data, and transmitted to the vehicle allocation management device 11A of company A via the communication unit 32. do.
　通信部３２は、車載器３１の車両動態データ生成部３４で生成された車両動態データを、A社の配車管理装置１１Aに送信する。通信部３２は、所定のネットワークを介したネットワーク通信を行うネットワークインタフェースで構成される。 The communication unit 32 transmits the vehicle dynamic data generated by the vehicle dynamic data generation unit 34 of the vehicle-mounted device 31 to the vehicle allocation management device 11A of the company A. The communication unit 32 is composed of a network interface that performs network communication via a predetermined network.
　端末装置３３は、例えば、スマートフォンやタブレット端末等の情報処理装置で構成される。端末装置３３には、ドライバ用のアプリケーションプログラムであるドライバアプリ３５がインストールされている。ドライバアプリ３５は、配車統合管理装置１２からの配車依頼に関するデータを取得してディスプレイに表示したり、ドライバの操作に基づき、配車依頼に対する応答のデータを配車統合管理装置１２に送信する。ドライバアプリ３５は、携帯通信用の広域通信網などのネットワークを介して直接、配車統合管理装置１２と通信を行う。なお、ドライバアプリ３５は、通信部３２を介して、A社の配車管理装置１１Aを経由して、配車統合管理装置１２と通信を行ってもよい。 The terminal device 33 is composed of an information processing device such as a smartphone or a tablet terminal, for example. The driver application 35, which is an application program for the driver, is installed in the terminal device 33. The driver application 35 acquires the data related to the vehicle allocation request from the vehicle allocation management device 12 and displays it on the display, or transmits the response data to the vehicle allocation request to the vehicle allocation management device 12 based on the driver's operation. The driver application 35 directly communicates with the vehicle allocation integrated management device 12 via a network such as a wide area communication network for mobile communication. The driver application 35 may communicate with the vehicle allocation integrated management device 12 via the vehicle allocation management device 11A of the company A via the communication unit 32.
　B社のタクシー２１Bと、C社のタクシー２１Cも、会社が異なるのみで、A社のタクシー２１Aと基本的に同様であるので、その説明は省略する。 Company B's taxi 21B and company C's taxi 21C are basically the same as company A's taxi 21A, except that the company is different, so the explanation is omitted.
　A社の配車管理装置１１Aは、１以上のA社のタクシー２１Aの車両動態データを収集し、配車統合管理装置１２に送信するとともに、配車統合管理装置１２からA社のタクシー２１Aへ送信される配車依頼に関するデータを中継して、指定されたA社のタクシー２１Aへ送信する。 The vehicle allocation management device 11A of company A collects vehicle dynamic data of one or more taxi 21A of company A and transmits the vehicle dynamic data to the vehicle allocation management device 12 and is transmitted from the vehicle allocation management device 12 to the taxi 21A of company A. The data related to the vehicle dispatch request is relayed and transmitted to the designated taxi 21A of company A.
　A社の配車管理装置１１Aは、車両動態データ管理部４１、注文情報管理部４２、および、通信部４３を有する。A社の配車管理装置１１Aは、例えば、ネットワーク接続機能を有するサーバ装置（情報処理装置）で構成される。 The vehicle allocation management device 11A of company A has a vehicle dynamic data management unit 41, an order information management unit 42, and a communication unit 43. The vehicle allocation management device 11A of company A is composed of, for example, a server device (information processing device) having a network connection function.
　車両動態データ管理部４１は、A社のタクシー２１Aそれぞれから供給される車両動態データを管理する。具体的には、車両動態データ管理部４１は、A社のタクシー２１Aそれぞれから供給される車両動態データを内部の記憶部に記憶し、各タクシー２１Aの車両動態データを不図示のディスプレイに表示させる。また、車両動態データ管理部４１は、各タクシー２１Aから供給される車両動態データを配車統合管理装置１２に送信する。 The vehicle dynamic data management unit 41 manages the vehicle dynamic data supplied from each of the taxi 21A of company A. Specifically, the vehicle dynamic data management unit 41 stores the vehicle dynamic data supplied from each of the taxi 21A of the company A in the internal storage unit, and displays the vehicle dynamic data of each taxi 21A on a display (not shown). .. Further, the vehicle dynamic data management unit 41 transmits the vehicle dynamic data supplied from each taxi 21A to the vehicle allocation integrated management device 12.
　A社のタクシー２１Aの運行を管理するオペレータは、A社に配車依頼の電話等があった場合、車両動態データ管理部４１に記憶されている、A社の各タクシー２１Aの現在位置や、「実車」または「空車」等のステータスを確認し、配車依頼に対応可能なタクシー２１Aを検索したり、割り当てることができる。 When the operator who manages the operation of the taxi 21A of the company A receives a call for dispatching the taxi to the company A, the current position of each taxi 21A of the company A, which is stored in the vehicle dynamics data management unit 41, and " You can check the status of "actual vehicle" or "empty vehicle" and search for or assign a taxi 21A that can respond to a vehicle allocation request.
　注文情報管理部４２は、顧客等からの事前の配車依頼（配車予約）の情報を管理する。例えば、A社のタクシー２１Aのオペレータが、顧客から配車予約の電話を受け付けた場合、オペレータは、配車予約の情報、例えば、迎車場所、迎車時刻、顧客名、目的地などの情報を、操作端末から注文情報管理部４２に入力する。注文情報管理部４２は、配車予約の情報を記憶し、予約時刻の所定時間前になると、配車依頼の表示を行う。配車依頼の表示を確認したオペレータは、車両動態データ管理部４１に記憶されている車両動態データに基づいて、所定のタクシー２１Aに配車依頼を行う。なお、注文情報管理部４２が、予約時刻の所定時間前になると、車両動態データ管理部４１の車両動態データから、最適なタクシー２１Aを検索し、配車依頼を行ってもよい。 The order information management unit 42 manages information on prior vehicle allocation requests (vehicle allocation reservations) from customers and the like. For example, when the operator of the taxi 21A of company A receives a call for a vehicle allocation reservation from a customer, the operator inputs information on the vehicle allocation reservation, for example, information such as a pick-up location, a pick-up time, a customer name, and a destination. Is input to the order information management unit 42. The order information management unit 42 stores the information of the vehicle allocation reservation, and displays the vehicle allocation request when the predetermined time before the reservation time comes. The operator who confirms the display of the vehicle allocation request makes a vehicle allocation request to the predetermined taxi 21A based on the vehicle dynamic data stored in the vehicle dynamic data management unit 41. The order information management unit 42 may search for the optimum taxi 21A from the vehicle dynamics data of the vehicle dynamics data management unit 41 and make a vehicle allocation request before the reserved time.
　通信部４３は、配車統合管理装置１２およびA社のタクシー２１Aそれぞれと所定の通信を行う。例えば、通信部４３は、配車統合管理装置１２からの配車依頼を所定のタクシー２１Aに送信したり、各タクシー２１Aから定期的に取得される車両動態データを、配車統合管理装置１２に送信する。 The communication unit 43 performs predetermined communication with each of the vehicle allocation integrated management device 12 and the taxi 21A of company A. For example, the communication unit 43 transmits a vehicle allocation request from the vehicle allocation integrated management device 12 to a predetermined taxi 21A, and transmits vehicle dynamic data periodically acquired from each taxi 21A to the vehicle allocation integrated management device 12.
　B社およびC社それぞれのタクシー会社の配車管理装置１１Bおよび１１Cも、会社が異なるのみで、A社の配車管理装置１１Aと基本的に同様であるので、その説明は省略する。なお、A社、B社、およびC社を特に区別しない場合、単に、配車管理装置１１と称する場合がある。 The vehicle allocation management devices 11B and 11C of the taxi companies of companies B and C are basically the same as the vehicle allocation management devices 11A of company A, except that the companies are different, so the description thereof will be omitted. When company A, company B, and company C are not particularly distinguished, they may be simply referred to as the vehicle allocation management device 11.
　配車統合管理装置１２は、A社、B社、およびC社の配車管理装置１１との間で、車両動態データや配車依頼などのデータを送受信する。また、配車統合管理装置１２は、タクシーの利用者であるユーザの端末装置（以下、ユーザ端末と称する。）１３にインストールされた、配車依頼を行うアプリケーションプログラム（以下、ユーザアプリと称する。）６１とも、所定のネットワークを介して通信を行う。配車統合管理装置１２は、例えば、ネットワーク接続機能を有するサーバ装置で構成される。 The vehicle allocation management device 12 transmits and receives data such as vehicle dynamic data and vehicle allocation request to and from the vehicle allocation management devices 11 of companies A, B, and C. Further, the vehicle allocation integrated management device 12 is an application program (hereinafter, referred to as a user application) 61 installed in a terminal device (hereinafter, referred to as a user terminal) 13 of a user who is a taxi user, for requesting a vehicle allocation. Both communicate via a predetermined network. The vehicle allocation integrated management device 12 is composed of, for example, a server device having a network connection function.
　配車統合管理装置１２は、全てのタクシー２１の配車を管理する配車管理装置である。配車統合管理装置１２は、車両動態データ管理部５１、顧客データ管理部５２、注文情報管理部５３、配車管理部５４、タクシー会社通信部５５、および、アプリ通信部５６を有する。 The vehicle allocation management device 12 is a vehicle allocation management device that manages the vehicle allocation of all taxis 21. The vehicle allocation integrated management device 12 includes a vehicle dynamic data management unit 51, a customer data management unit 52, an order information management unit 53, a vehicle allocation management unit 54, a taxi company communication unit 55, and an application communication unit 56.
　車両動態データ管理部５１は、各タクシー会社の配車管理装置１１、および、各個人タクシー２１Dから供給される車両動態データを管理する。具体的には、車両動態データ管理部５１は、各タクシー会社の配車管理装置１１および各個人タクシー２１Dから供給される車両動態データを内部の記憶部に記憶し、車両動態データを不図示のディスプレイに表示させる。車両動態データは、タクシー２１の会社ID、タクシー２１の無線ID、乗務員ID、ステータス時刻、タクシー２１の位置情報、タクシー２１の走行速度および進行方向、ステータス、並びに、ステータスが「実車」または「迎車」の場合のタクシー２１の乗車地および目的地などの情報である。また、車両動態データ管理部５１は、１回の「実車」のステータスが終了するごとに、タクシー２１の会社ID、タクシー２１の無線ID、乗務員ID、乗車地および目的地、料金などを、過去の実車データとして内部の記憶部に記録する。 The vehicle dynamic data management unit 51 manages the vehicle dynamic data supplied from the vehicle allocation management device 11 of each taxi company and each individual taxi 21D. Specifically, the vehicle dynamics data management unit 51 stores vehicle dynamics data supplied from the vehicle allocation management device 11 of each taxi company and each individual taxi 21D in an internal storage unit, and displays the vehicle dynamics data (not shown). To display. The vehicle dynamic data includes the company ID of the taxi 21, the radio ID of the taxi 21, the crew ID, the status time, the position information of the taxi 21, the traveling speed and the direction of travel of the taxi 21, the status, and the status of "actual vehicle" or "pick-up". This is information such as the boarding place and destination of the taxi 21 in the case of. In addition, the vehicle dynamic data management unit 51 records the company ID of the taxi 21, the radio ID of the taxi 21, the crew ID, the boarding place and the destination, the fare, etc. every time the status of one "actual vehicle" is completed. It is recorded in the internal storage as the actual vehicle data.
　顧客データ管理部５２は、オペレータによって入力されたり、ユーザアプリ６１から送信されてくるデータに基づいて、顧客データを生成し、内部の記憶部に記憶する。例えば、顧客データ管理部５２は、顧客データとして、顧客の名前、顧客が好きなタクシー会社や優先的に配車して欲しいタクシー会社、よく利用するタクシー乗り場、迎車に対する平均待ち時間、などの情報を、顧客を識別する識別情報である顧客IDとともに記憶する。顧客データは、ユーザアプリ６１においてユーザが入力（指定）したデータであってもよし、ユーザの乗車履歴などに基づいて、顧客データ管理部５２が生成したデータでもよい。 The customer data management unit 52 generates customer data based on the data input by the operator or transmitted from the user application 61, and stores it in the internal storage unit. For example, the customer data management unit 52 provides customer data such as a customer's name, a taxi company that the customer likes, a taxi company that wants the customer to preferentially dispatch a vehicle, a frequently used taxi stand, and an average waiting time for picking up. , Stored together with the customer ID, which is the identification information that identifies the customer. The customer data may be data input (designated) by the user in the user application 61, or may be data generated by the customer data management unit 52 based on the user's boarding history or the like.
　ユーザアプリ６１の利用者（顧客）は、会員の種別として、一般会員か、または、優先会員のいずれかに分類される。優先会員は、一般会員よりも優遇措置が得られる会員である。優先会員は、例えば、過去の一定期間の利用頻度や利用額に応じて決定することができ、利用頻度や利用額が一定値以上のユーザとすることができる。あるいはまた、優先会員は、一定額の課金を行った有料登録のユーザを割り当てるようにしてもよい。顧客データ管理部５２が記憶する顧客データには、顧客の会員の種別も記憶されている。 The user (customer) of the user application 61 is classified into either a general member or a priority member as a member type. Priority members are members who receive preferential treatment over general members. The priority member can be determined according to, for example, the usage frequency and usage amount for a certain period in the past, and can be a user whose usage frequency and usage amount are equal to or higher than a certain value. Alternatively, the priority member may assign a paid registration user who has charged a fixed amount. In the customer data stored in the customer data management unit 52, the type of customer member is also stored.
　注文情報管理部５３は、顧客等からの事前の配車依頼（配車予約）の情報を管理する。各配車管理装置１１の注文情報管理部４２は、各タクシー会社が受け付けた配車依頼（配車予約）の情報であるのに対して、注文情報管理部５３は、各タクシー会社を統括する代表の予約センターやユーザアプリ６１で受け付けた配車依頼（配車予約）の情報を管理する。注文情報管理部５３は、配車予約の予約時刻の所定時間前になると、配車管理部５４に配車依頼を行う。 The order information management unit 53 manages information on prior vehicle allocation requests (vehicle allocation reservations) from customers and the like. The order information management unit 42 of each vehicle allocation management device 11 is the information of the vehicle allocation request (vehicle allocation reservation) received by each taxi company, whereas the order information management unit 53 is the reservation of the representative who controls each taxi company. It manages the information of the vehicle allocation request (vehicle allocation reservation) received by the center or the user application 61. The order information management unit 53 makes a vehicle allocation request to the vehicle allocation management unit 54 before a predetermined time of the reservation time of the vehicle allocation reservation.
　配車管理部５４は、配車依頼または配車予約に基づく配車の制御を行う。例えば、配車管理部５４は、ユーザアプリ６１から配車依頼が送信されてくると、車両動態データ管理部５１に記憶されている車両動態データに基づいて、配車依頼の条件を満たすタクシー２１を抽出して、抽出したタクシー２１に配車依頼を送信する。また、配車管理部５４は、注文情報管理部５３から配車依頼が送信されてくると、車両動態データ管理部５１に記憶されている車両動態データに基づいて、配車依頼の条件を満たすタクシー２１を抽出して、抽出したタクシー２１に配車依頼を送信する。 The vehicle allocation management unit 54 controls vehicle allocation based on a vehicle allocation request or a vehicle allocation reservation. For example, when the vehicle allocation request is transmitted from the user application 61, the vehicle allocation management unit 54 extracts the taxi 21 that satisfies the vehicle allocation request condition based on the vehicle dynamic data stored in the vehicle dynamic data management unit 51. Then, the dispatch request is sent to the extracted taxi 21. Further, when the vehicle allocation request is transmitted from the order information management unit 53, the vehicle allocation management unit 54 selects the taxi 21 that satisfies the vehicle allocation request condition based on the vehicle dynamic data stored in the vehicle dynamic data management unit 51. Extract and send a vehicle allocation request to the extracted taxi 21.
　タクシー会社通信部５５は、各タクシー会社の配車管理装置１１それぞれと所定の通信を行う。例えば、タクシー会社通信部５５は、各タクシー２１Aから定期的に送信されてくる車両動態データを受信し、車両動態データ管理部５１に供給したり、配車管理部５４からの配車依頼を、配車管理装置１１を介して所定のタクシー２１に送信する。 The taxi company communication unit 55 performs predetermined communication with each of the vehicle allocation management devices 11 of each taxi company. For example, the taxi company communication unit 55 receives vehicle dynamic data periodically transmitted from each taxi 21A and supplies the vehicle dynamic data to the vehicle dynamic data management unit 51, or receives a vehicle allocation request from the vehicle allocation management unit 54 for vehicle allocation management. It is transmitted to a predetermined taxi 21 via the device 11.
　なお、タクシー会社通信部５５は、各タクシー会社の配車管理装置１１を介さずに、直接、各タクシー会社のタクシー２１と通信を行うことにより、車両動態データを受信したり、配車管理部５４からの配車依頼を所定のタクシー２１に送信するようにしてもよい。 The taxi company communication unit 55 directly communicates with the taxi 21 of each taxi company without going through the vehicle allocation management device 11 of each taxi company to receive vehicle dynamic data or from the vehicle allocation management unit 54. The vehicle dispatch request may be sent to a predetermined taxi 21.
　アプリ通信部５６は、ユーザアプリ６１と所定の通信を行う。例えば、アプリ通信部５６は、ユーザアプリ６１からの配車依頼を受信して、配車管理部５４に供給したり、所定のタクシー２１の配車が確定した場合に、配車確定通知をユーザアプリ６１へ送信する。 The application communication unit 56 performs predetermined communication with the user application 61. For example, the application communication unit 56 receives a vehicle allocation request from the user application 61 and supplies it to the vehicle allocation management unit 54, or sends a vehicle allocation confirmation notification to the user application 61 when the allocation of a predetermined taxi 21 is confirmed. do.
　なお、図１では、理解を容易にするため、1人のユーザに対応するユーザ端末１３とユーザアプリ６１しか図示されていないが、配車統合管理装置１２は、複数のユーザ端末１３のユーザアプリ６１と必要に応じて、所要の通信を行うことができる。 Although only the user terminal 13 and the user application 61 corresponding to one user are shown in FIG. 1 for easy understanding, the vehicle allocation integrated management device 12 is the user application 61 of a plurality of user terminals 13. And if necessary, the required communication can be performed.
　ユーザ端末１３は、例えば、スマートフォンやタブレット端末等の情報処理装置で構成され、配車統合管理装置１２と所定の通信を行う。ユーザアプリ６１は、ユーザの操作に基づいて、タクシー２１の配車を配車統合管理装置１２に依頼したり、配車依頼に応じた配車確定の表示を行う。また、ユーザアプリ６１は、配車統合管理装置１２から、ユーザの現在地近傍の車両動態データを取得することで、現在のタクシー２１の運行状況などをディスプレイに表示することもできる。 The user terminal 13 is composed of, for example, an information processing device such as a smartphone or a tablet terminal, and performs predetermined communication with the vehicle allocation integrated management device 12. The user application 61 requests the vehicle allocation integrated management device 12 to dispatch the taxi 21 based on the user's operation, and displays the vehicle allocation confirmation in response to the vehicle allocation request. In addition, the user application 61 can display the current operation status of the taxi 21 on the display by acquiring the vehicle dynamic data in the vicinity of the user's current location from the vehicle allocation integrated management device 12.
　以上のように構成されるタクシー配車システム１においては、ユーザがユーザアプリ６１を操作して、タクシー２１の配車依頼を行った場合、配車統合管理装置１２は、車両動態データ管理部５１の車両動態データを参照して、最適なタクシー２１を探索し、探索されたタクシー２１に配車依頼を送信する。 In the taxi dispatch system 1 configured as described above, when the user operates the user application 61 to request the taxi 21 to be dispatched, the vehicle dispatch integrated management device 12 uses the vehicle dynamics of the vehicle dynamics data management unit 51. With reference to the data, the optimum taxi 21 is searched for, and a dispatch request is sent to the searched taxi 21.
　配車統合管理装置１２は、最適なタクシー２１を探索する場合に、最初に、タクシー２１のステータスが「空車」であるタクシー２１のなかから、配車依頼の要求に応えるタクシー２１があるかを探索する。 When searching for the optimum taxi 21, the vehicle allocation integrated management device 12 first searches for a taxi 21 that responds to a request for a vehicle allocation from among the taxis 21 whose status is "empty". ..
　しかしながら、配車依頼の場所や時間、天候、その他の状況によってタクシー需要が多い場合は必ず存在し、希望の配車依頼に対して必ず応えられることが難しい場合がある。 However, there is always a lot of taxi demand depending on the location, time, weather, and other conditions of the vehicle dispatch request, and it may be difficult to always respond to the desired vehicle dispatch request.
　そこで、配車統合管理装置１２では、ユーザアプリ６１の利用者のうち、優先会員からの配車依頼に対しては、一般会員と比較して高い確率で応えられるような配車制御が構築されている。 Therefore, the vehicle allocation integrated management device 12 is constructed with a vehicle allocation control that can respond to a vehicle allocation request from a priority member among the users of the user application 61 with a higher probability than that of a general member.
　具体的には、優先会員であるユーザが配車依頼を行った際に、ステータスが「空車」であるタクシー２１が１台も存在しない場合、配車統合管理装置１２は、一般会員である他のユーザの配車依頼に割り当てたタクシー２１であって、割り当てられたユーザの乗車地に迎車中のタクシー２１を、優先会員のユーザに割り当て直すような配車の制御を行う。配車の権利を譲渡する一般会員のユーザには、配車権利の譲渡に対する報酬として所定のインセンティブが与えられる。インセンティブは、例えば、次回、配車を利用した際に利用できる迎車料金無料や割引券の電子クーポンであったり、現在地周辺や目的地周辺で利用できるショップ等の無料券や割引券などとすることができる。あるいはまた、インセンティブは、配車権利の譲渡に対して、譲渡人に与えられる、電子マネー、ポイントなどの報酬であってもよい。 Specifically, when a user who is a priority member makes a vehicle allocation request and there is no taxi 21 whose status is "empty", the vehicle allocation integrated management device 12 is another user who is a general member. The taxi 21 assigned to the vehicle allocation request of the above is controlled to allocate the taxi 21 that is picking up at the boarding place of the assigned user so as to reassign it to the priority member user. A general member user who transfers the right to dispatch a vehicle is given a predetermined incentive as a reward for the transfer of the right to dispatch a vehicle. The incentive may be, for example, an electronic coupon for a free pick-up fee or a discount coupon that can be used the next time the vehicle is dispatched, or a free ticket or discount coupon for shops that can be used around the current location or the destination. can. Alternatively, the incentive may be a reward such as electronic money or points given to the transferor for the transfer of the vehicle allocation right.
　以下では、最初に、一般会員と優先会員とを区別せずに、ユーザが配車依頼を行った際に、ステータスが「空車」であるタクシー２１が１台以上存在し、ユーザからの配車依頼に対して、「空車」のタクシー２１を割り当てることができる場合の配車の制御（通常配車制御）について説明する。次に、「空車」のタクシー２１が存在しないような状況において、優先会員からの配車依頼に対して応えることができるようにした配車の制御について説明する。 In the following, first, when the user makes a vehicle dispatch request without distinguishing between a general member and a priority member, there is one or more taxis 21 whose status is "empty", and the user requests a vehicle dispatch. On the other hand, the control of vehicle allocation (normal vehicle allocation control) when the "empty" taxi 21 can be assigned will be described. Next, in a situation where the "empty" taxi 21 does not exist, the vehicle allocation control that enables the response to the vehicle allocation request from the priority member will be described.
＜２．通常配車制御の流れ＞
　図２は、「空車」のタクシー２１を割り当てることができる場合の、タクシー配車システム１全体における通常配車制御の流れを説明するフローチャートである。 <2. Flow of normal vehicle allocation control ＞
FIG. 2 is a flowchart illustrating a flow of normal vehicle allocation control in the entire taxi dispatch system 1 when an “empty” taxi 21 can be assigned.
　なお、図２の処理とは別に、配車統合管理装置１２が、タクシー２１の車両動態データを各タクシー２１から定期的または不定期に取得し、車両動態データ管理部５１の車両動態データを更新する処理が、常時実行されていることとする。 In addition to the processing of FIG. 2, the vehicle allocation integrated management device 12 acquires the vehicle dynamic data of the taxi 21 from each taxi 21 periodically or irregularly, and updates the vehicle dynamic data of the vehicle dynamic data management unit 51. It is assumed that the process is always executed.
　最初に、ユーザが、ステップＳ１において、ユーザアプリ６１を起動し、ユーザアプリ６１に乗車地「Ｘ」および目的地「Ｙ」を入力して配車依頼の操作を行う。 First, in step S1, the user activates the user application 61, inputs the boarding place "X" and the destination "Y" to the user application 61, and operates the vehicle allocation request.
　図３は、ユーザが配車依頼を行うために、ユーザアプリ６１を起動した場合のユーザアプリ６１の配車依頼画面の例を示している。 FIG. 3 shows an example of a vehicle allocation request screen of the user application 61 when the user application 61 is activated in order to make a vehicle allocation request.
　図３の配車依頼画面には、現在地近傍の地図を表示するエリアマップ８１、配車依頼操作を行う配車依頼操作部８２、乗車地を入力する乗車地入力部８３、目的地を入力する目的地入力部８４、および、支払方法を指定する支払設定部８５が設けられている。 On the vehicle allocation request screen of FIG. 3, an area map 81 for displaying a map of the vicinity of the current location, a vehicle allocation request operation unit 82 for performing a vehicle allocation request operation, a boarding place input unit 83 for inputting a boarding location, and a destination input unit for inputting a destination 84 and a payment setting unit 85 for designating a payment method are provided.
　エリアマップ８１には、ステータスが「空車」のタクシー２１を表すタクシーマーク９１Aと、ステータスが「実車」または「迎車」のタクシー２１を表すタクシーマーク９１Bとが、タクシー２１の現在位置に応じた地図上の位置に表示されている。ステータスが「空車」のタクシーマーク９１Aと、ステータスが「実車」または「迎車」のタクシーマーク９１Bとでは、表示の色または模様が異なっており、区別して表示されている。図３の例では、ステータスが「空車」のタクシーマーク９１Aは、白色（無地）で表され、ステータスが「実車」または「迎車」のタクシーマーク９１Bは、灰色で表されている。 On the area map 81, a taxi mark 91A representing a taxi 21 having a status of "empty" and a taxi mark 91B representing a taxi 21 having a status of "actual vehicle" or "picking up" are displayed on a map according to the current position of the taxi 21. It is displayed at the position of. The taxi mark 91A whose status is "empty" and the taxi mark 91B whose status is "actual vehicle" or "pick-up" are different in display color or pattern and are displayed separately. In the example of FIG. 3, the taxi mark 91A having the status "empty" is represented in white (plain), and the taxi mark 91B having the status "actual vehicle" or "pick-up" is represented in gray.
　なお、図３の例では、ステータスが「実車」のタクシーマーク９１Bと、「迎車」のタクシーマーク９１Bとを区別することなく、同一の色または模様で表しているが、「実車」のタクシーマーク９１Bと、「迎車」のタクシーマーク９１Bとを区別可能に色または模様などで異なる表示としてもよい。 In the example of FIG. 3, the taxi mark 91B whose status is "actual vehicle" and the taxi mark 91B whose status is "pick-up" are shown in the same color or pattern without distinction, but the taxi mark of "actual vehicle". The 91B and the taxi mark 91B of "pick-up" may be displayed differently by color or pattern so as to be distinguishable.
　以下では、ステータスが「空車」のタクシー２１を表すタクシーマーク９１Aを、空車タクシーマーク９１Aと称し、ステータスが「実車」または「迎車」のタクシーマーク９１Bを、実車・迎車タクシーマーク９１Bと称して説明することとする。空車タクシーマーク９１Aと実車・迎車タクシーマーク９１Bとを特に区別しない場合、単にタクシーマーク９１と称する。 In the following, the taxi mark 91A representing the taxi 21 having the status of "empty" will be referred to as the empty taxi mark 91A, and the taxi mark 91B having the status of "actual vehicle" or "picking up" will be referred to as the actual vehicle / picking taxi mark 91B. I decided to. When there is no particular distinction between the empty taxi mark 91A and the actual / pick-up taxi mark 91B, it is simply referred to as the taxi mark 91.
　エリアマップ８１には、ユーザ端末１３のGPS受信機で取得されたユーザの現在地を示す現在地マーク９３と、ユーザによって乗車地入力部８３に入力された乗車地に対応する位置に乗車地マーク９４が表示されている。乗車地マーク９４は、ユーザがタッチ操作により、エリアマップ８１上の所望の場所に自由に移動させることができ、乗車地マーク９４の場所に応じた住所が、乗車地入力部８３に表示される。 On the area map 81, the current location mark 93 indicating the user's current location acquired by the GPS receiver of the user terminal 13 and the boarding location mark 94 are displayed at positions corresponding to the boarding locations input by the user to the boarding location input unit 83. Has been done. The boarding place mark 94 can be freely moved to a desired place on the area map 81 by the user by touch operation, and the address corresponding to the place of the boarding place mark 94 is displayed on the boarding place input unit 83.
　配車依頼操作部８２には、操作バー８２Aが表示されており、操作バー８２Aを右側にスライドすることにより、配車依頼を実行することができる。 The operation bar 82A is displayed on the vehicle allocation request operation unit 82, and the vehicle allocation request can be executed by sliding the operation bar 82A to the right side.
　乗車地入力部８３には、ユーザが希望する乗車地が入力される。乗車地入力部８３は、アプリ起動時には空欄とされてもよいし、GPS受信機で取得された現在地がデフォルトで入力されてもよい。乗車地入力部８３が空欄とされる場合には、乗車地マーク９４も表示されない。 The boarding place desired by the user is input to the boarding place input unit 83. The boarding location input unit 83 may be left blank when the application is started, or the current location acquired by the GPS receiver may be input by default. If the boarding place input unit 83 is left blank, the boarding place mark 94 is also not displayed.
　目的地入力部８４には、ユーザが希望する行き先である目的地が入力される。 The destination, which is the destination desired by the user, is input to the destination input unit 84.
　支払設定部８５では、支払方法を指定することができる。支払方法には、例えば、ドライバに現金で支払う現金払いや、ユーザアプリ６１に登録されているクレジットカードで支払うカード払いなどを選択することができる。図３の支払設定部８５には、カード払いを指定した際の表示例が示されている。 The payment setting unit 85 can specify the payment method. As the payment method, for example, cash payment to pay the driver in cash, card payment to pay with the credit card registered in the user application 61, or the like can be selected. The payment setting unit 85 of FIG. 3 shows a display example when card payment is specified.
　アプリ起動時には、ユーザアプリ６１は、ユーザの現在地に対して地図の縮尺に応じた所定の範囲内に位置する、ステータスが「空車」、「実車」または「迎車」のタクシー２１のタクシーマーク９１をエリアマップ８１上に表示する。 When the application is started, the user application 61 displays the taxi mark 91 of the taxi 21 whose status is "empty", "actual vehicle" or "pick-up", which is located within a predetermined range according to the scale of the map with respect to the user's current location. It is displayed on the area map 81.
　ステップＳ１の処理は、図３の配車依頼画面において、ユーザが、乗車地入力部８３に乗車地「Ｘ」を入力し、目的地入力部８４に目的地「Ｙ」を入力した後、操作バー８２Aを右側にスライドする操作に対応する。 In the process of step S1, on the vehicle allocation request screen of FIG. 3, the user inputs the boarding place "X" to the boarding place input unit 83, inputs the destination "Y" to the destination input unit 84, and then the operation bar. Corresponds to the operation of sliding 82A to the right.
　図２に戻り、ユーザによって操作バー８２Aが右側にスライドされると、ステップＳ２において、ユーザアプリ６１は、乗車地「Ｘ」および目的地「Ｙ」の情報とともに配車依頼を、配車統合管理装置１２に送信する。 Returning to FIG. 2, when the operation bar 82A is slid to the right by the user, in step S2, the user application 61 requests a vehicle allocation together with information on the boarding place “X” and the destination “Y”, and the vehicle allocation integrated management device 12 Send to.
　ステップＳ１１において、配車統合管理装置１２の配車管理部５４は、ユーザアプリ６１からの配車依頼を受信し、車両動態データ管理部５１が管理する現在の車両動態データを参照し、配車可能なタクシー２１を抽出する。ここで、乗車地「Ｘ」に最も近いタクシー２１で、「空車」のステータスを有するA社のタクシー２１Aが、検索されたとする。 In step S11, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the vehicle allocation request from the user application 61, refers to the current vehicle dynamic data managed by the vehicle dynamic data management unit 51, and can dispatch the taxi 21. Is extracted. Here, it is assumed that the taxi 21A of the company A having the status of "empty" is searched for the taxi 21 closest to the boarding place "X".
　ステップＳ１２において、配車管理部５４は、検索されたA社のタクシー２１Aに配車依頼を送信する。 In step S12, the vehicle allocation management unit 54 transmits a vehicle allocation request to the searched taxi 21A of company A.
　ステップＳ２１において、A社のタクシー２１Aのドライバアプリ３５は、配車統合管理装置１２からの配車依頼に関するデータ（例えば、乗車地「Ｘ」および目的地「Ｙ」など）を取得してディスプレイに表示する。そして、ドライバが、配車依頼を受諾する旨の応答操作を行うと、ステップＳ２２において、ドライバアプリ３５は、配車依頼を受諾する旨の依頼受諾通知を、配車統合管理装置１２に送信する。 In step S21, the driver application 35 of the taxi 21A of the company A acquires the data related to the vehicle allocation request from the vehicle allocation integrated management device 12 (for example, the boarding place “X” and the destination “Y”) and displays it on the display. .. Then, when the driver performs a response operation to the effect that the vehicle allocation request is accepted, in step S22, the driver application 35 transmits a request acceptance notification to the effect that the vehicle allocation request is accepted to the vehicle allocation integrated management device 12.
　配車統合管理装置１２の配車管理部５４は、ステップＳ１３において、タクシー２１Aからの依頼受諾通知を受信すると、そのタクシー２１Aを、配車するタクシーに決定し、ステップＳ１４において、ユーザのドライバアプリ３５に、配車確定通知を送信する。 Upon receiving the request acceptance notification from the taxi 21A in step S13, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines the taxi 21A as the taxi to be dispatched, and in step S14, the user's driver application 35 is notified. Send a vehicle dispatch confirmation notice.
　ユーザのドライバアプリ３５は、ステップＳ３において、配車確定通知を受信すると、配車確定表示を行う。そして、ユーザに割り当てられたA社のタクシー２１Aが、乗車地「Ｘ」に到着すると、ステップＳ４において、ユーザは、タクシー２１Aに乗車し、目的地「Ｙ」への移動を開始する。 When the user's driver application 35 receives the vehicle allocation confirmation notification in step S3, the vehicle allocation confirmation display is performed. Then, when the taxi 21A of company A assigned to the user arrives at the boarding place "X", in step S4, the user gets on the taxi 21A and starts moving to the destination "Y".
＜３．配車統合管理装置の通常配車処理＞
　次に、図２を参照して説明したタクシー配車システム１全体の配車制御の流れのうち、配車統合管理装置１２による通常配車処理について、図４のフローチャートを参照して説明する。図４の処理は、例えば、配車統合管理装置１２としてのサーバ装置において配車処理を実行するプログラムが起動されたとき、開始される。 <3. Normal vehicle allocation processing of vehicle allocation integrated management device>
Next, among the flow of vehicle allocation control of the entire taxi vehicle allocation system 1 described with reference to FIG. 2, the normal vehicle allocation process by the vehicle allocation integrated management device 12 will be described with reference to the flowchart of FIG. The process of FIG. 4 is started, for example, when a program for executing the vehicle allocation process is started in the server device as the vehicle allocation integrated management device 12.
　初めに、ステップＳ４１において、配車統合管理装置１２の配車管理部５４は、ユーザアプリ６１から、配車依頼を受信したかを判定し、配車依頼を受信したと判定されるまで待機する。 First, in step S41, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received.
　ステップＳ４１で、配車依頼を受信したと判定された場合、処理はステップＳ４２に進む。タクシー２１から送信されてくる配車依頼には、図３を参照して説明したように、ユーザアプリ６１の配車依頼画面で入力された、乗車地、目的地、および、支払方法とともに、ユーザを識別するユーザIDおよび名前などの情報が含まれる。 If it is determined in step S41 that the vehicle allocation request has been received, the process proceeds to step S42. In the vehicle allocation request transmitted from the taxi 21, the user is identified together with the boarding place, destination, and payment method input on the vehicle allocation request screen of the user application 61, as explained with reference to FIG. Contains information such as the user ID and name to be used.
　ステップＳ４２において、配車管理部５４は、車両動態データ管理部５１に記憶されている車両動態データを参照し、ステータスが「空車」のタクシー２１のなかから、配車依頼があった乗車地に所定時間以内に配車可能なタクシー２１を抽出する。例えば、配車管理部５４は、ステータスが「空車」のタクシー２１について、タクシー２１の現在位置から、ユーザが指定した乗車地までの移動時間を計算し、計算された移動時間が所定時間以内であるタクシー２１を抽出する。 In step S42, the vehicle allocation management unit 54 refers to the vehicle dynamics data stored in the vehicle dynamics data management unit 51, and from the taxi 21 whose status is "empty", the vehicle allocation request is made to the boarding place for a predetermined time. The taxi 21 that can be dispatched within is extracted. For example, the vehicle allocation management unit 54 calculates the travel time from the current position of the taxi 21 to the boarding place specified by the user for the taxi 21 whose status is "empty", and the calculated travel time is within a predetermined time. Extract taxi 21.
　ステップＳ４３において、配車管理部５４は、抽出された１台以上のタクシー２１のなかから、乗車地に一番早く到着可能なタクシー２１を配車候補に決定し、ステップＳ４４において、配車候補に決定したタクシー２１に配車依頼を送信する。 In step S43, the vehicle allocation management unit 54 determines the taxi 21 that can arrive at the boarding place earliest from the extracted one or more taxi 21 as a vehicle allocation candidate, and in step S44, determines the vehicle allocation candidate. Send a dispatch request to taxi 21.
　ステップＳ４５において、配車管理部５４は、配車依頼を送信したタクシー２１から、依頼受諾通知があったか否かを判定する。 In step S45, the vehicle allocation management unit 54 determines whether or not the request acceptance notification has been received from the taxi 21 that has transmitted the vehicle allocation request.
　ステップＳ４５で、配車依頼を送信したタクシー２１から依頼受諾通知を一定時間内（例えば、１５秒）に受信しなかった場合、または、依頼拒否通知が送信されてきた場合、配車管理部５４は、依頼受諾通知がないと判定し、処理をステップＳ４３に戻す。これにより、配車依頼に対応可能な次のタクシー２１が配車候補に決定される。 In step S45, if the taxi 21 that has sent the vehicle allocation request does not receive the request acceptance notification within a certain period of time (for example, 15 seconds), or if the request refusal notification is transmitted, the vehicle allocation management unit 54 It is determined that there is no request acceptance notification, and the process returns to step S43. As a result, the next taxi 21 that can respond to the vehicle allocation request is determined as a vehicle allocation candidate.
　一方、配車依頼を送信したタクシー２１から依頼受諾通知を受信した場合、配車管理部５４は、ステップＳ４５で、配車依頼を送信したタクシー２１から依頼受諾通知があったと判定し、処理をステップＳ４６に進める。 On the other hand, when the request acceptance notification is received from the taxi 21 that has sent the vehicle allocation request, the vehicle allocation management unit 54 determines in step S45 that the request acceptance notification has been received from the taxi 21 that has sent the vehicle allocation request, and processes the process in step S46. Proceed.
　ステップＳ４６において、配車管理部５４は、依頼受諾通知を送信してきたタクシー２１を、配車するタクシー２１に決定し、決定したタクシー２１に配車予約情報を送信する。配車予約情報は、例えば、配車依頼をしてきたユーザの名前、乗車地、乗車時刻、目的地などの情報である。 In step S46, the vehicle allocation management unit 54 determines the taxi 21 that has sent the request acceptance notification to the taxi 21 to be allocated, and transmits the vehicle allocation reservation information to the determined taxi 21. The vehicle allocation reservation information is, for example, information such as the name of the user who has requested the vehicle allocation, the boarding place, the boarding time, and the destination.
　そして、ステップＳ４７において、配車管理部５４は、配車依頼をしてきたユーザアプリ６１に配車確定通知を送信する。 Then, in step S47, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the user application 61 that has requested the vehicle allocation.
　通常配車処理は、以上のように実行される。 The normal vehicle allocation process is executed as described above.
　ユーザが配車依頼を行った際に、ステータスが「空車」であるタクシー２１が１台以上存在する場合には、一般会員または優先会員の区別関係なく、ユーザの配車依頼に即座に応えることができる。 When the user makes a vehicle dispatch request, if there is one or more taxi 21 whose status is "empty", the user's vehicle dispatch request can be immediately responded to regardless of whether it is a general member or a priority member. ..
＜４．配車権利譲渡の依頼を行う場合の配車制御の流れ＞
　次に、ユーザが配車依頼を行った際に、ステータスが「空車」であるタクシー２１が１台も存在しない場合を想定する。 <4. Flow of vehicle allocation control when requesting transfer of vehicle allocation right>
Next, it is assumed that there is no taxi 21 whose status is "empty" when the user requests the vehicle allocation.
　「空車」のタクシー２１が１台も存在しない場合、配車依頼を行ったユーザの会員種別が一般会員である場合には、ユーザに、「空車」のタクシー２１がない旨のメッセージや、配車可能なタクシー２１ができるまで待ってもらうこともやむを得ないが、配車統合管理装置１２は、優先会員に対しては、できるだけ配車に応えるように配車の制御を行う。 If there is no "empty" taxi 21 or if the member type of the user who requested the dispatch is a general member, the user can be notified that there is no "empty" taxi 21 or can be dispatched. It is unavoidable to have the taxi 21 wait until the taxi 21 is completed, but the vehicle allocation integrated management device 12 controls the vehicle allocation for the priority members so as to respond to the vehicle allocation as much as possible.
　具体的には、配車統合管理装置１２は、優先会員から配車依頼があり、ステータスが「空車」であるタクシー２１が１台も存在しない場合には、既に配車依頼が確定し、ステータスが「迎車」となっているタクシー２１のなかで、優先会員の配車依頼の乗車地に近い乗車地に配車中のタクシー２１のユーザに配車権利の譲渡依頼を通知し、そのユーザに配車の権利を譲ってもらうことで、優先会員からの配車依頼に応えるような配車制御を実行する。 Specifically, in the vehicle allocation integrated management device 12, if there is a vehicle allocation request from a priority member and there is no taxi 21 having a status of "empty", the vehicle allocation request has already been confirmed and the status is "pick-up". Among the taxi 21 that is "", the user of the taxi 21 who is dispatching to the boarding place near the boarding place of the priority member's dispatch request is notified of the transfer request of the vehicle dispatch right, and the vehicle dispatch right is transferred to that user. By receiving the taxi, the vehicle allocation control is executed so as to respond to the vehicle allocation request from the priority member.
　図５は、「空車」のタクシー２１を割り当てることができない場合に、優先会員からの配車依頼に配車権利の譲渡で対処するタクシー配車システム１全体の配車制御の流れを説明するフローチャートである。 FIG. 5 is a flowchart illustrating the flow of vehicle allocation control of the entire taxi vehicle allocation system 1 that deals with the vehicle allocation request from the priority member by transferring the vehicle allocation right when the "empty" taxi 21 cannot be assigned.
　最初に、優先会員であるユーザ（以下、単に、優先会員と称する。）が、ステップＳ６１において、ユーザアプリ６１を起動し、ユーザアプリ６１に乗車地「Ｘ」および目的地「Ｙ」を入力して配車依頼の操作を行う。配車依頼の操作は、図３を参照して説明した操作と同様である。 First, a user who is a priority member (hereinafter, simply referred to as a priority member) activates the user application 61 in step S61, and inputs the boarding place "X" and the destination "Y" to the user application 61. And perform the operation of the vehicle allocation request. The operation of requesting vehicle allocation is the same as the operation described with reference to FIG.
　優先会員によって操作バー８２Aが右側にスライドされると、ステップＳ６２において、ユーザアプリ６１は、乗車地「Ｘ」および目的地「Ｙ」の情報とともに配車依頼を、配車統合管理装置１２に送信する。 When the operation bar 82A is slid to the right by the priority member, in step S62, the user application 61 transmits a vehicle allocation request to the vehicle allocation integrated management device 12 together with information on the boarding place "X" and the destination "Y".
　ステップＳ８１において、配車統合管理装置１２の配車管理部５４は、ユーザアプリ６１からの配車依頼を受信し、車両動態データ管理部５１が管理する現在の車両動態データを参照し、配車可能なタクシー２１を抽出する。ここで、乗車地「Ｘ」に最も近いタクシー２１で、「空車」のステータスを有するタクシー２１が１台も存在しないとする。 In step S81, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the vehicle allocation request from the user application 61, refers to the current vehicle dynamic data managed by the vehicle dynamic data management unit 51, and can dispatch the taxi 21. Is extracted. Here, it is assumed that there is no taxi 21 having the status of "empty" in the taxi 21 closest to the boarding place "X".
　次に、ステップＳ８２において、配車管理部５４は、優先会員の乗車地「Ｘ」付近に迎車中のタクシー２１を抽出する。この抽出処理により、乗車地「Ｘ」の近くである乗車地「Ｘ１」に配車が確定し、迎車中（タクシー２１の到着待ち）である一般会員のユーザＡ（以下、一般ユーザＡと称する。）と、乗車地「Ｘ」の近くである乗車地「Ｘ２」に配車が確定し、迎車中である一般会員のユーザＢ（以下、一般ユーザＢと称する。）が抽出されたとする。 Next, in step S82, the vehicle allocation management unit 54 extracts the taxi 21 that is picking up near the boarding place "X" of the priority member. By this extraction process, the vehicle allocation is confirmed at the boarding place "X1" near the boarding place "X", and the user A of the general member who is picking up (waiting for the arrival of the taxi 21) (hereinafter referred to as general user A). ), And it is assumed that the vehicle allocation is confirmed at the boarding place "X2" near the boarding place "X", and the general member user B (hereinafter referred to as general user B) who is picking up the taxi is extracted.
　ステップＳ８３において、配車管理部５４は、一般ユーザＡのユーザアプリ６１および、一般ユーザＢのユーザアプリ６１に、配車権利の譲渡を依頼する譲渡依頼を送信する。 In step S83, the vehicle allocation management unit 54 transmits a transfer request requesting the transfer of the vehicle allocation right to the user application 61 of the general user A and the user application 61 of the general user B.
　ステップＳ１０１において、一般ユーザＡのユーザアプリ６１は、配車統合管理装置１２の配車管理部５４からの譲渡依頼を受信し、譲渡依頼画面をユーザ端末１３のディスプレイに表示する。 In step S101, the user application 61 of the general user A receives the transfer request from the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12, and displays the transfer request screen on the display of the user terminal 13.
　ステップＳ１１１において、一般ユーザＢのユーザアプリ６１も、配車統合管理装置１２の配車管理部５４からの譲渡依頼を受信し、譲渡依頼画面をユーザ端末１３のディスプレイに表示する。 In step S111, the user application 61 of the general user B also receives the transfer request from the vehicle allocation management unit 54 of the vehicle allocation management device 12, and displays the transfer request screen on the display of the user terminal 13.
　図６は、配車統合管理装置１２からの譲渡依頼を受信した場合に、ユーザ端末１３のディスプレイに表示される譲渡依頼画面の例を示している。 FIG. 6 shows an example of a transfer request screen displayed on the display of the user terminal 13 when a transfer request from the vehicle allocation integrated management device 12 is received.
　譲渡依頼画面では、図６に示されるように、エリアマップ８１上に、「配車権利の譲渡希望者がいます。譲渡した場合、次回の迎車料金が無料になります。譲渡しますか？」のメッセージ１２１と、「譲渡する」ボタン１２２、および、「譲渡しない」ボタン１２３を備えるウィンドウ１２４が表示される。「譲渡する」ボタン１２２は、ユーザが譲渡してもよい場合に操作（押下）される。「譲渡しない」ボタン１２３は、ユーザが譲渡したくない場合に操作（押下）される。 On the transfer request screen, as shown in Fig. 6, on the area map 81, the message "There is a person who wants to transfer the vehicle allocation right. If you transfer, the next pick-up fee will be free. Do you want to transfer?" A window 124 with 121, a "transfer" button 122, and a "not transfer" button 123 is displayed. The "transfer" button 122 is operated (pressed) when the user may transfer it. The "do not transfer" button 123 is operated (pressed) when the user does not want to transfer.
　図５の処理では、一般ユーザＡが「譲渡する」ボタン１２２を操作し、一般ユーザＢは「譲渡しない」ボタン１２３を操作したとする。 In the process of FIG. 5, it is assumed that the general user A operates the "transfer" button 122, and the general user B operates the "not transfer" button 123.
　一般ユーザＡが「譲渡する」ボタン１２２を操作すると、ステップＳ１０２において、一般ユーザＡのユーザアプリ６１は、配車権利の譲渡をしてもよい旨を表す依頼許諾通知を、配車統合管理装置１２に送信する。 When the general user A operates the "transfer" button 122, in step S102, the user application 61 of the general user A sends a request permission notification indicating that the vehicle allocation right may be transferred to the vehicle allocation integrated management device 12. Send.
　一般ユーザBが「譲渡しない」ボタン１２３を操作すると、ステップＳ１１２において、一般ユーザBのユーザアプリ６１は、配車権利の譲渡をしない旨を表す依頼拒否通知を、配車統合管理装置１２に送信する。 When the general user B operates the "do not transfer" button 123, in step S112, the user application 61 of the general user B transmits a request refusal notice indicating that the vehicle allocation right is not transferred to the vehicle allocation integrated management device 12.
　配車統合管理装置１２の配車管理部５４は、ステップＳ８４において、一般ユーザＡのユーザアプリ６１からの依頼許諾通知を受信するとともに、一般ユーザBのユーザアプリ６１からの依頼拒否通知を受信する。そして、配車管理部５４は、受信した結果に基づいて、優先会員に配車するタクシーを決定する。この例では、一般ユーザＡに迎車中のタクシー２１が、優先会員に配車するタクシーに決定される。 In step S84, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the request permission notification from the user application 61 of the general user A and the request refusal notification from the user application 61 of the general user B. Then, the vehicle allocation management unit 54 determines the taxi to be allocated to the priority member based on the received result. In this example, the taxi 21 being picked up by the general user A is determined to be the taxi to be dispatched to the priority member.
　ステップＳ８５において、配車管理部５４は、一般ユーザＡの乗車地に向けて迎車中のタクシー２１のドライバアプリ３５に、配車依頼の変更通知を送信する。配車依頼の変更通知は、例えば、配車依頼が、先に確定された一般ユーザＡから優先会員に変更されたことと、優先会員の名前、変更後の乗車地「Ｘ」、乗車時刻、目的地などを示す情報である。 In step S85, the vehicle allocation management unit 54 transmits a change notification of the vehicle allocation request to the driver application 35 of the taxi 21 that is picking up the taxi toward the boarding place of the general user A. The change notification of the vehicle allocation request is, for example, that the vehicle allocation request has been changed from the previously confirmed general user A to a priority member, the name of the priority member, the changed boarding place "X", the boarding time, and the destination. It is information indicating such as.
　ステップＳ１４１において、一般ユーザＡへ迎車中のタクシー２１のドライバアプリ３５は、配車統合管理装置１２からの配車依頼の変更通知に関するデータを取得してディスプレイに表示する。そして、ドライバが、配車依頼の変更を受諾する旨の応答操作を行うと、ステップＳ１４２において、ドライバアプリ３５は、配車依頼の変更を受諾する旨の依頼受諾通知を、配車統合管理装置１２に送信する。 In step S141, the driver application 35 of the taxi 21 that is picking up the general user A acquires the data related to the change notification of the vehicle allocation request from the vehicle allocation integrated management device 12 and displays it on the display. Then, when the driver performs a response operation to accept the change in the vehicle allocation request, in step S142, the driver application 35 transmits a request acceptance notification to the effect that the change in the vehicle allocation request is accepted to the vehicle allocation integrated management device 12. do.
　配車統合管理装置１２の配車管理部５４は、タクシー２１からの依頼受諾通知を受信すると、ステップＳ８６において、一般ユーザＡのユーザアプリ６１に、配車権利の譲渡が成立した旨の譲渡成立通知を送信する。一般ユーザＡのユーザアプリ６１には、次回の迎車料金無料の電子クーポンなど、配車権利を譲渡したことにより得られるインセンティブ情報も、譲渡成立通知とともに送信される。これにより、配車権利を譲渡した一般ユーザＡは、次回、配車依頼を行う際、迎車料金無料の電子クーポンを利用することができる。 When the vehicle allocation management unit 54 of the vehicle allocation management device 12 receives the request acceptance notification from the taxi 21, in step S86, the vehicle allocation management unit 54 transmits a transfer establishment notification to the user application 61 of the general user A to the effect that the transfer of the vehicle allocation right has been completed. do. Incentive information obtained by transferring the vehicle allocation right, such as the next electronic coupon for which the pick-up fee is free, is also transmitted to the user application 61 of the general user A together with the transfer completion notification. As a result, the general user A who has transferred the vehicle allocation right can use the electronic coupon with no pick-up fee the next time he / she makes a vehicle allocation request.
　さらに、配車管理部５４は、ステップＳ８７において、優先会員のドライバアプリ３５に、配車確定通知を送信する。ステップＳ８６とステップＳ８７の順番は逆でもよいし、同時（並列）でもよい。 Further, in step S87, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the driver application 35 of the priority member. The order of steps S86 and S87 may be reversed or may be simultaneous (parallel).
　優先会員のドライバアプリ３５は、ステップＳ６３において、配車確定通知を受信すると、配車確定表示を行う。 When the driver application 35 of the priority member receives the vehicle allocation confirmation notification in step S63, the vehicle allocation confirmation display is performed.
＜５．配車権利譲渡の依頼を行う配車統合管理装置の配車処理＞
　次に、図５に示したタクシー配車システム１全体の配車制御処理のうち、配車統合管理装置１２による配車処理の詳細について、図７のフローチャートを参照して説明する。図７の処理は、例えば、配車統合管理装置１２としてのサーバ装置において配車処理を実行するプログラムが起動されたとき、開始される。 <5. Vehicle allocation processing of the vehicle allocation integrated management device that requests the transfer of vehicle allocation rights>
Next, among the vehicle allocation control processes for the entire taxi vehicle allocation system 1 shown in FIG. 5, the details of the vehicle allocation process by the vehicle allocation integrated management device 12 will be described with reference to the flowchart of FIG. 7. The process of FIG. 7 is started, for example, when a program for executing the vehicle allocation process is started in the server device as the vehicle allocation integrated management device 12.
　初めに、ステップＳ１８１において、配車統合管理装置１２の配車管理部５４は、ユーザアプリ６１から、配車依頼を受信したかを判定し、配車依頼を受信したと判定されるまで待機する。 First, in step S181, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received.
　ステップＳ１８１で、配車依頼を受信したと判定された場合、処理はステップＳ１８２に進む。図７の配車処理においても、図５と同様に、ステップＳ１８１で受信した配車依頼は優先会員からの配車依頼であり、乗車地は「Ｘ」、目的地は「Ｙ」であるとする。 If it is determined in step S181 that the vehicle allocation request has been received, the process proceeds to step S182. In the vehicle allocation process of FIG. 7, similarly to FIG. 5, the vehicle allocation request received in step S181 is a vehicle allocation request from the priority member, the boarding place is “X”, and the destination is “Y”.
　ステップＳ１８２において、配車管理部５４は、車両動態データ管理部５１に記憶されている車両動態データを参照し、ステータスが「空車」のタクシー２１のなかから、配車依頼があった乗車地に所定時間以内に配車可能なタクシー２１を抽出する。 In step S182, the vehicle allocation management unit 54 refers to the vehicle dynamics data stored in the vehicle dynamics data management unit 51, and from the taxi 21 whose status is "empty", the vehicle allocation request is made to the boarding place for a predetermined time. The taxi 21 that can be dispatched within is extracted.
　ステップＳ１８３において、配車管理部５４は、通常配車が可能であるか、換言すれば、配車依頼があった乗車地「Ｘ」に所定時間以内に配車可能な、ステータスが「空車」のタクシー２１が存在するかを判定する。 In step S183, the vehicle dispatch management unit 54 can dispatch a taxi 21 having a status of "empty", which can be dispatched to the boarding place "X" requested to be dispatched within a predetermined time. Determine if it exists.
　ステップＳ１８３で、通常配車が可能であると判定された場合、処理はステップＳ１８４に進み、配車管理部５４は、通常配車処理を実行する。ステップＳ１８４の通常配車処理としては、具体的には、図４のステップＳ４３乃至Ｓ４７の処理と同じ処理が実行される。 If it is determined in step S183 that normal vehicle allocation is possible, the process proceeds to step S184, and the vehicle allocation management unit 54 executes the normal vehicle allocation process. Specifically, as the normal vehicle allocation process in step S184, the same process as the process in steps S43 to S47 of FIG. 4 is executed.
　一方、ステップＳ１８３で、通常配車が可能ではないと判定された場合、処理はステップＳ１８５に進み、配車管理部５４は、配車依頼を送信してきたユーザアプリ６１のユーザが、優先会員であるかを判定する。 On the other hand, if it is determined in step S183 that normal vehicle allocation is not possible, the process proceeds to step S185, and the vehicle allocation management unit 54 determines whether the user of the user application 61 that has sent the vehicle allocation request is a priority member. judge.
　ステップＳ１８５で、ユーザが優先会員ではないと判定された場合、処理はステップＳ１８６に進み、配車管理部５４は、「現在、周囲に配車可能なタクシーはありません。配車時刻の変更を検討してください」等のメッセージをユーザアプリ６１に送信し、配車時間の変更をユーザに提案する。したがって、ユーザが一般会員である場合には、配車権利の譲渡依頼処理は実行されない。 If it is determined in step S185 that the user is not a priority member, the process proceeds to step S186, and the vehicle allocation management unit 54 says, "Currently, there are no taxis available for dispatch. Please consider changing the vehicle allocation time. A message such as "" is sent to the user application 61 to propose a change in the vehicle allocation time to the user. Therefore, when the user is a general member, the transfer request processing of the vehicle allocation right is not executed.
　一方、ステップＳ１８５で、ユーザが優先会員であると判定された場合、処理はステップＳ１８７に進み、配車管理部５４は、車両動態データ管理部５１の車両動態データを参照して、優先会員の乗車地「Ｘ」付近に迎車中のタクシー２１が存在するかを判定する。乗車地「Ｘ」付近とは、例えば、乗車地「Ｘ」からの距離または時間が所定範囲内となる範囲である。 On the other hand, if it is determined in step S185 that the user is a priority member, the process proceeds to step S187, and the vehicle allocation management unit 54 refers to the vehicle dynamic data of the vehicle dynamic data management unit 51 and gets on the priority member. It is determined whether or not there is a taxi 21 being picked up near the ground "X". The vicinity of the boarding place "X" is, for example, a range in which the distance or time from the boarding place "X" is within a predetermined range.
　図７の配車処理では、図５で説明した処理と同様、乗車地「Ｘ」の近くである乗車地「Ｘ１」でタクシー２１の到着待ち（迎車中）の一般ユーザＡと、乗車地「Ｘ」の近くである乗車地「Ｘ２」でタクシー２１の到着待ち（迎車中）の一般ユーザＢが存在するとする。 In the vehicle allocation process of FIG. 7, similar to the process described with reference to FIG. It is assumed that there is a general user B waiting for the arrival of the taxi 21 (while picking up the taxi) at the boarding place "X2" near the "X2".
　ステップＳ１８７で、優先会員の乗車地「Ｘ」付近に迎車中のタクシー２１が存在しないと判定された場合、処理は上述したステップＳ１８６に進む。この場合、配車管理部５４は、「現在、周囲に配車可能なタクシーはありません。配車時刻の変更を検討してください」等のメッセージを、ユーザアプリ６１に送信する。 If it is determined in step S187 that there is no taxi 21 being picked up near the boarding place "X" of the priority member, the process proceeds to step S186 described above. In this case, the vehicle allocation management unit 54 sends a message such as "There are currently no taxis available for dispatch in the surrounding area. Please consider changing the vehicle allocation time" to the user application 61.
　一方、ステップＳ１８７で、優先会員の乗車地「Ｘ」付近に迎車中のタクシー２１が存在すると判定された場合、処理はステップＳ１８８に進み、配車管理部５４は、乗車地「Ｘ」付近に迎車中のタクシー２１のユーザのユーザアプリ６１に、配車権利の譲渡依頼を送信する。具体的には、一般ユーザＡのユーザアプリ６１、および、一般ユーザＢのユーザアプリ６１に、配車権利の譲渡依頼が送信される。 On the other hand, if it is determined in step S187 that there is a taxi 21 being picked up near the boarding place "X" of the priority member, the process proceeds to step S188, and the vehicle allocation management unit 54 picks up the taxi near the boarding place "X". A request for transfer of the vehicle allocation right is transmitted to the user application 61 of the user of the taxi 21 inside. Specifically, a request for transfer of the vehicle allocation right is transmitted to the user application 61 of the general user A and the user application 61 of the general user B.
　そして、ステップＳ１８９において、配車管理部５４は、送信した配車権利の譲渡依頼に対する返答、すなわち、依頼許諾通知または依頼拒否通知を待機し、１人以上のユーザ（のユーザアプリ６１）から依頼受諾通知があったかを判定する。配車管理部５４は、配車権利の譲渡依頼を送信したユーザから、一定時間内（例えば、１５秒）に依頼許諾通知を受信しなかった場合、依頼が拒否されたと認識し、依頼拒否通知の受信と同等に扱うことができる。 Then, in step S189, the vehicle allocation management unit 54 waits for a response to the transmitted transfer request for the vehicle allocation right, that is, a request permission notification or a request refusal notification, and a request acceptance notification from one or more users (user application 61). Determine if there was. If the vehicle allocation management unit 54 does not receive the request permission notification within a certain period of time (for example, 15 seconds) from the user who sent the vehicle allocation right transfer request, the vehicle allocation management unit 54 recognizes that the request has been rejected and receives the request refusal notification. Can be treated in the same way as.
　ステップＳ１８９で、１人以上のユーザ（のユーザアプリ６１）から依頼受諾通知がない、すなわち、全てのユーザから依頼拒否通知が受信されたと判定された場合、処理は上述したステップＳ１８６に進む。この場合、「周囲に配車可能なタクシーはありません。」等の配車不可メッセージが、配車管理部５４からユーザアプリ６１に送信される。 If it is determined in step S189 that there is no request acceptance notification from one or more users (user application 61), that is, the request refusal notification has been received from all users, the process proceeds to step S186 described above. In this case, a non-dispatchable message such as "There are no taxis that can be dispatched around" is transmitted from the vehicle dispatch management unit 54 to the user application 61.
　一方、ステップＳ１８９で、１人以上のユーザ（のユーザアプリ６１）から依頼受諾通知があったと判定された場合、処理はステップＳ１９０に進み、配車管理部５４は、依頼受諾通知があったユーザは１人であるかを判定する。 On the other hand, if it is determined in step S189 that the request acceptance notification has been received from one or more users (user application 61), the process proceeds to step S190, and the vehicle allocation management unit 54 tells the user who has received the request acceptance notification. Determine if you are alone.
　ステップＳ１９０で、依頼受諾通知があったユーザは１人であると判定された場合、処理はステップＳ１９１に進み、配車管理部５４は、依頼受諾通知があったユーザ（図５の例では、ユーザＡ）に迎車中のタクシー２１を、優先会員に配車するタクシーに決定する。 If it is determined in step S190 that there is only one user who has received the request acceptance notification, the process proceeds to step S191, and the vehicle allocation management unit 54 determines that the user who has received the request acceptance notification (in the example of FIG. 5, the user). The taxi 21 that is picking up at A) is decided to be the taxi to be dispatched to the priority member.
　一方、ステップＳ１９０で、複数のユーザから依頼受諾通知があったと判定された場合、処理はステップＳ１９２に進み、配車管理部５４は、依頼受諾通知があった複数のユーザのなかから、優先会員に配車するタクシーを決定する。配車管理部５４は、例えば、依頼受諾通知があった複数のユーザそれぞれに割り当てられた迎車中のタクシー２１のうち、最も早く優先会員の乗車地「Ｘ」に到着可能なタクシー２１を、優先会員に配車するタクシーに決定する。また例えば、配車権利の譲渡に対する報酬としての金額を譲渡人であるユーザが申請する場合、配車管理部５４は、依頼受諾通知があった複数のユーザのうち、譲渡金額が最も安いユーザに割り当てられた迎車中のタクシー２１を、優先会員に配車するタクシーを決定する。譲渡金額の申請は、例えば、配車権利の譲渡を希望するか否かを確認する図６のウィンドウ１２４において、ユーザに入力させてもよいし、ユーザアプリ６１の設定画面等において、ユーザが配車権利を譲渡する際の許容金額を予め設定してもよい。 On the other hand, if it is determined in step S190 that the request acceptance notification has been received from a plurality of users, the process proceeds to step S192, and the vehicle allocation management unit 54 selects the priority member from among the plurality of users who have received the request acceptance notification. Decide which taxi to dispatch. The vehicle allocation management unit 54 selects, for example, the taxi 21 that can arrive at the boarding place "X" of the priority member earliest among the taxi 21 that are being picked up assigned to each of the plurality of users who have received the request acceptance notification. Decide on a taxi to dispatch to. Further, for example, when a user who is the transferor applies for an amount as a reward for the transfer of the vehicle allocation right, the vehicle allocation management unit 54 is assigned to the user with the lowest transfer amount among the plurality of users who have received the request acceptance notification. The taxi 21 that is being picked up is decided as the taxi to be dispatched to the priority member. The application for the transfer amount may be made to be input by the user in the window 124 of FIG. 6 for confirming whether or not the transfer of the vehicle allocation right is desired, or the user may input the vehicle allocation right on the setting screen of the user application 61 or the like. The permissible amount of money for the transfer may be set in advance.
　例えば、会員種別が、ゴールド会員、シルバー会員、ブロンズ会員のように複数あり、依頼受諾通知を返信した複数のユーザの会員種別が異なる場合、会員種別の低いユーザに割り当てられた迎車中のタクシー２１を、優先会員に配車するタクシーに決定してもよい。また例えば、依頼受諾通知を返信した複数のユーザが、ドライバアプリ３５を介して会話するなどして交渉し、配車権利を譲渡するユーザを決定してもよい。 For example, if there are a plurality of membership types such as a gold member, a silver member, and a bronze member, and the membership types of the plurality of users who have returned the request acceptance notification are different, the taxi 21 being picked up assigned to the user with the lower membership type. May be decided as a taxi to be dispatched to priority members. Further, for example, a plurality of users who have returned the request acceptance notification may negotiate by having a conversation via the driver application 35 to determine the user to whom the vehicle allocation right is to be transferred.
　ステップＳ１９１またはステップＳ１９２の処理により、配車権利を譲渡する迎車中のタクシー２１が決定されると、ステップＳ１９３において、配車管理部５４は、配車権利を譲渡する迎車中のタクシー２１、上述の例では、一般ユーザＡの乗車地「Ｘ１」に迎車中のタクシー２１のドライバアプリ３５に、配車依頼の変更通知を送信する。一般ユーザＡの乗車地「Ｘ１」に迎車中のタクシー２１のドライバは、ドライバアプリ３５によりディスプレイに表示された、配車依頼の変更情報を確認し、配車依頼の変更を受諾する旨の操作を行う。ドライバの操作に基づいて、配車依頼の変更を受諾する旨の依頼受諾通知が、ドライバアプリ３５から配車統合管理装置１２に送信され、配車統合管理装置１２で受信される。 When the taxi 21 in the vehicle to which the vehicle allocation right is transferred is determined by the process of step S191 or step S192, in step S193, the vehicle allocation management unit 54 determines the taxi 21 in the vehicle to which the vehicle allocation right is transferred, in the above example. , Sends a change notification of the vehicle allocation request to the driver application 35 of the taxi 21 that is picking up at the boarding place "X1" of the general user A. The driver of the taxi 21 who is picking up at the boarding place "X1" of the general user A confirms the change information of the vehicle allocation request displayed on the display by the driver application 35, and performs an operation to accept the change of the vehicle allocation request. .. Based on the operation of the driver, a request acceptance notification to accept the change of the vehicle allocation request is transmitted from the driver application 35 to the vehicle allocation integrated management device 12, and is received by the vehicle allocation integrated management device 12.
　ステップＳ１９４において、配車管理部５４は、一般ユーザＡのユーザアプリ６１に、配車権利の譲渡が成立した旨の譲渡成立通知を送信するとともに、配車権利を譲渡したことにより得られるインセンティブ情報を送信する。 In step S194, the vehicle allocation management unit 54 transmits a transfer establishment notification to the effect that the transfer of the vehicle allocation right has been completed, and also transmits incentive information obtained by transferring the vehicle allocation right to the user application 61 of the general user A. ..
　ステップＳ１９５において、配車管理部５４は、優先会員のユーザアプリ６１に、配車依頼に対して配車が確定したことを表す配車確定通知を送信する。配車確定通知には、例えば、配車するタクシー２１を識別するナンバー、タクシー会社名、無線番号、迎車到着時刻などの情報が含まれ、ユーザ端末１３のディスプレイに表示される。迎車到着時刻は、配車されたタクシー２１が乗車地「Ｘ」に到着する予定時刻である。また、乗車地「Ｘ」から目的地「Ｙ」までの予想料金や到着予想時刻（予想移動時間）などを表示してもよい。ステップＳ１９４とステップＳ１９５の順番は逆でもよいし、同時（並列）でもよい。 In step S195, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification indicating that the vehicle allocation has been confirmed in response to the vehicle allocation request to the user application 61 of the priority member. The vehicle allocation confirmation notification includes, for example, information such as a number for identifying the taxi 21 to be allocated, a taxi company name, a radio number, and a pick-up arrival time, and is displayed on the display of the user terminal 13. The pick-up arrival time is the scheduled time when the dispatched taxi 21 arrives at the boarding place "X". Further, the estimated fare from the boarding place "X" to the destination "Y", the estimated arrival time (estimated travel time), and the like may be displayed. The order of steps S194 and S195 may be reversed or may be simultaneous (parallel).
　以上のように、配車権利の譲渡を可能とした配車制御によれば、優先会員から配車依頼があり、ステータスが「空車」であるタクシー２１が１台も存在しない場合であっても、一般会員である他のユーザの配車依頼に割り当てられた迎車中のタクシー２１を、優先会員のユーザに割り当てることができる。これにより、優先会員等の特定のユーザからの配車依頼に対応できる確率を向上させることができる。 As described above, according to the vehicle allocation control that enables the transfer of the vehicle allocation right, even if there is no taxi 21 whose status is "empty" due to a vehicle allocation request from the priority member, a general member The taxi 21 that is being picked up and assigned to the vehicle allocation request of another user can be assigned to the priority member user. As a result, it is possible to improve the probability of being able to respond to a vehicle allocation request from a specific user such as a priority member.
　また、配車権利の譲渡に応じた一般ユーザには、次回の配車時に利用できる、迎車料金無料や優先予約権等の電子クーポン、電子マネー、ポイントなどの報酬が、インセンティブとして付与される。これにより、配車権利を譲渡した譲渡人も一定のメリットを享受できるので、配車権利の譲渡が促進される。 In addition, general users who have transferred the vehicle dispatch right will be given incentives such as electronic coupons such as free pick-up fee and priority reservation right, electronic money, and points that can be used at the next vehicle dispatch. As a result, the transferor who has transferred the vehicle allocation right can also enjoy a certain merit, and thus the transfer of the vehicle allocation right is promoted.
　上述した実施の形態では、ユーザアプリ６１の利用者の会員種別として、一般会員と優先会員とに区分し、優先会員であるユーザが配車権利を譲り受けることができることとしたが、一般会員と優先会員の区分を決めずに、例えば、１回の配車依頼を行う度に所定の追加料金を支払うことなどによって、配車権利を譲渡してもらう権利を獲得できるようにしてもよい。 In the above-described embodiment, the membership types of the users of the user application 61 are divided into general members and priority members, and the user who is the priority member can take over the vehicle allocation right. However, the general member and the priority member can be transferred. It may be possible to acquire the right to transfer the vehicle allocation right, for example, by paying a predetermined additional charge each time a vehicle allocation request is made without determining the classification of the vehicle allocation.
　例えば、配車管理部５４は、配車依頼に対応可能なタクシー２１を抽出した結果、ステータスが「空車」であるタクシー２１が１台も存在しないと判定された場合に、図８に示されるような配車依頼画面を、配車依頼操作を行ったユーザのユーザアプリ６１に表示させる。 For example, when the vehicle allocation management unit 54 extracts the taxi 21 capable of responding to the vehicle allocation request and determines that there is no taxi 21 having a status of "empty", as shown in FIG. The vehicle dispatch request screen is displayed on the user application 61 of the user who performed the vehicle dispatch request operation.
　図８の配車依頼画面には、エリアマップ８１上に、「周囲に配車可能なタクシーはありません。あなたの前にＸＸ人が配車を待っています。優先配車権を使用しますか？」のメッセージ１４１と、「使用する」ボタン１４２、および、「使用しない」ボタン１４３を備えるウィンドウ１４４が表示される。「使用する」ボタン１４２は、ユーザが優先配車権を使用する場合に操作（押下）される。「使用しない」ボタン１４３は、ユーザが優先配車権を使用したくない場合に操作（押下）される。ユーザが優先配車権を使用すると、１回の使用に付き、所定の料金がカード決済等により支払われる。 On the vehicle dispatch request screen of FIG. 8, on the area map 81, the message "There are no taxis available for dispatch. XX people are waiting for dispatch in front of you. Do you want to use the priority dispatch right?" Message 141 A window 144 with the "use" button 142 and the "not use" button 143 is displayed. The "use" button 142 is operated (pressed) when the user uses the priority vehicle allocation right. The "not use" button 143 is operated (pressed) when the user does not want to use the priority vehicle allocation right. When the user uses the priority vehicle allocation right, a predetermined fee is paid by card payment or the like for each use.
　また、図５乃至図７を参照して説明した配車制御では、ユーザが優先会員であり、配車依頼に対応可能な「空車」のタクシー２１が１台も存在しないと判定された場合に、一般会員に迎車中のタクシー２１のなかで配車可能な迎車中のタクシー２１を検索したが、ユーザが優先会員である場合においても、図８の配車依頼画面を表示して、優先配車権を使用するか否かを確認してから、配車可能な迎車中のタクシー２１を検索するようにしてもよい。あるいはまた、配車可能な「空車」のタクシー２１が存在しないと判定された場合に、「周囲に配車可能なタクシーはありません。あなたの前にＸＸ人が配車を待っています。優先配車を行います。」等のメッセージを表示することで、優先配車を行っている旨を優先会員に通知してもよい。優先配車を行っている旨を通知した場合には、仮に、譲渡してもらえそうなタクシー２１が存在しない場合、「配車権利を譲渡可能なタクシーはありませんでした。」のように、優先配車の実行結果のメッセージを表示してもよい。 Further, in the vehicle allocation control described with reference to FIGS. 5 to 7, when it is determined that the user is a priority member and there is no "empty" taxi 21 capable of responding to the vehicle allocation request, it is general. The taxi 21 that can be dispatched to the member is searched for, but even if the user is a priority member, the dispatch request screen of FIG. 8 is displayed and the priority dispatch right is used. After confirming whether or not the taxi is available, the taxi 21 that can be dispatched may be searched. Alternatively, if it is determined that there is no "empty" taxi 21 that can be dispatched, "There are no taxis that can be dispatched around. XX people are waiting for dispatch. Priority dispatch will be given. By displaying a message such as ".", The priority member may be notified that the priority vehicle is being dispatched. If you notify that you are giving priority to a taxi, and if there is no taxi 21 that you can transfer, you can say, "There was no taxi to which you can transfer the right to assign a taxi." The execution result message may be displayed.
　優先会員の乗車地「Ｘ」付近に迎車中のタクシー２１が存在するにもかかわらず、全てのユーザから拒否された場合、報酬や割引額を上げるなど、譲渡人であるユーザに有利になるようにインセンティブを変更し、再度、配車権利の譲渡依頼を送信してもよい。「配車権利を譲渡可能なタクシーはありませんでした。報酬を変更しますか？」のように、報酬の変更を、配車権利を譲渡してもらうユーザに確認してもよい。配車権利を譲渡してもらうユーザ（譲受人）、または、配車権利を譲渡するユーザ（譲渡人）のどちらかが主導権を持って、インセンティブの変更を提案し、譲受人と譲渡人が交渉によりインセンティブを決定し、配車権利を譲渡するか否かを決定してもよい。 Even though there is a taxi 21 that is picking up near the boarding place "X" of the priority member, if it is rejected by all users, it will be advantageous to the user who is the transferor, such as raising the reward and discount amount. You may change the incentive to and send the request for transfer of the vehicle allocation right again. You may ask the user to transfer the vehicle dispatch right to confirm the change in the reward, such as "There was no taxi to which the vehicle dispatch right can be transferred. Do you want to change the reward?" Either the user who transfers the vehicle allocation right (transferee) or the user who transfers the vehicle allocation right (transferor) takes the initiative and proposes a change in incentive, and the transferee and the transferor negotiate. You may decide the incentive and decide whether or not to transfer the right to dispatch the vehicle.
　配車権利を譲渡して欲しいユーザ（譲受人）は、その理由を、ユーザアプリ６１を介して、配車権利を譲渡するユーザ（譲渡人）にアピールしてもよい。例えば、大学受験に遅刻しそう、大事な会議に間に合わない、空車タクシーがこない場所にいる、などを、ユーザアプリ６１で入力し、譲渡人に通知してもよい。 The user (transferee) who wants to transfer the vehicle allocation right may appeal the reason to the user (transferor) who transfers the vehicle allocation right via the user application 61. For example, the transferor may be notified by inputting in the user application 61 that he / she is likely to be late for the university entrance examination, is not in time for an important meeting, or is in a place where an empty taxi does not come.
　図５乃至図７を参照して説明した配車制御では、配車権利を譲渡してもらうユーザを一般会員に限定して、配車可能な迎車中のタクシー２１を検索したが、配車権利を譲渡してもらうユーザを、一般会員に限定せずに、優先会員を含めて検索するようにしてもよい。 In the vehicle allocation control described with reference to FIGS. 5 to 7, the users to whom the vehicle allocation right is transferred are limited to general members, and the taxi 21 that can be allocated is searched, but the vehicle allocation right is transferred. The users to be received are not limited to general members, but may be searched including priority members.
　また、ユーザアプリ６１の設定画面等において、配車権利を譲渡してもよいか否か、配車権利を譲渡する場合には、いくら以上の報酬であれば譲渡するか、などを設定情報として予め登録しておき、配車統合管理装置１２は、ユーザの設定情報を取得して、顧客データ管理部５２に顧客データとして記憶しておくことができる。その場合、配車統合管理装置１２は、配車権利を譲渡してもよいと設定されているユーザに対して配車途中（迎車中）のタクシー２１のなかから、配車権利の譲渡依頼が可能なユーザを検索し、配車権利を譲渡したくないと設定されているユーザに対しては、配車権利の譲渡依頼を送信しない。 In addition, on the setting screen of the user application 61, etc., whether or not the vehicle allocation right may be transferred, and if the vehicle allocation right is transferred, how much or more the reward should be transferred, etc. are registered in advance as setting information. However, the vehicle allocation integrated management device 12 can acquire the user's setting information and store it in the customer data management unit 52 as customer data. In that case, the vehicle allocation integrated management device 12 selects a user who can request the transfer of the vehicle allocation right from the taxi 21 in the middle of the vehicle allocation (during pick-up) to the user who is set to transfer the vehicle allocation right. The transfer request of the vehicle allocation right is not sent to the user who is searched and is set not to transfer the vehicle allocation right.
　あるはまた、ユーザの設定情報を基にするのではなく、１回ごとの配車依頼成立時に、「配車権利の譲渡依頼がくる可能性があります。譲渡依頼がきた場合は、譲渡しますか？」のようなメッセージを表示し、１回ごとに、ユーザの譲渡の可否を確認しておき、譲渡可能と返答したユーザのタクシー２１のなかから、譲渡依頼が可能なユーザを検索してもよい。 Also, instead of based on the user's setting information, when each vehicle allocation request is completed, "There is a possibility that a transfer request for the vehicle allocation right will come. If a transfer request comes, do you transfer it?" A message such as "" may be displayed, and the transferability of the user may be confirmed each time, and the user who can request the transfer may be searched from the taxi 21 of the user who replied that the transfer is possible. ..
　配車権利の譲渡が行われる可能性があるタクシー２１と、行われないタクシー２１とを区別して設定してユーザが認識できるようにしておいてもよい。この場合、配車権利の譲渡が行われる可能性があるタクシー２１が配車されるユーザは、配車権利の譲渡の依頼がくることを予想することができる。インセンティブを獲得したいユーザは、敢えて、配車権利の譲渡が行われる可能性があるタクシー２１を利用することもあり得る。配車権利の譲渡が行われる可能性があるタクシー２１と、行われないタクシー２１との設定台数、割合は、営業地域、営業時間帯、天候、イベントの有無などによりフレキシブルに設定することができる。 The taxi 21 that may be transferred the right to dispatch the vehicle and the taxi 21 that is not transferred may be set separately so that the user can recognize them. In this case, the user to whom the taxi 21 to which the vehicle allocation right may be transferred can be expected to receive a request for the transfer of the vehicle allocation right. A user who wants to obtain an incentive may dare to use a taxi 21 in which the right to dispatch a vehicle may be transferred. The set number and ratio of taxis 21 for which the right to dispatch vehicles may be transferred and taxi 21 for which dispatch rights are not transferred can be flexibly set depending on the business area, business hours, weather, presence / absence of events, and the like.
＜６．同乗依頼を行う変形例＞
　上述した実施の形態では、優先会員の配車依頼の乗車地「Ｘ」を中心として一定範囲内の距離または時間で到着可能なタクシー２１のなかから、配車の権利を譲渡可能なユーザを検索し、譲渡依頼を行うようにした。配車の権利を譲渡したユーザは、別のタクシー２１をもう一度探したり、電車、バス等の代替手段で移動する必要がある。 <6. Modification example of making a ride request>
In the above-described embodiment, a user who can transfer the right to dispatch a taxi is searched from among taxis 21 that can arrive within a certain distance or time centering on the boarding place "X" of the priority member's request for dispatch. Made a transfer request. The user who has transferred the right to dispatch a vehicle needs to search for another taxi 21 again or move by an alternative means such as a train or a bus.
　配車統合管理装置１２によるその他の配車制御として、優先会員の配車依頼の乗車地「Ｘ」と目的地「Ｙ」のそれぞれに近い配車依頼をしているユーザを検索し、そのユーザに同乗依頼を送信し、依頼受諾通知があった場合に、同乗する方法も取り得る。この場合、同乗の権利を譲渡するユーザと、譲り受けるユーザの両者がタクシー２１を利用して目的地まで到着することができる。 As other vehicle allocation control by the vehicle allocation integrated management device 12, a user who has made a vehicle allocation request close to each of the boarding place "X" and the destination "Y" of the priority member's vehicle allocation request is searched, and the user is requested to ride. If you send it and receive a notification of acceptance of the request, you can also take the method of riding with you. In this case, both the user who transfers the right to ride and the user who receives the right to ride can arrive at the destination by using the taxi 21.
　図９は、配車統合管理装置１２が、配車依頼の乗車地「Ｘ」と目的地「Ｙ」のそれぞれに近い配車依頼をしているユーザのユーザアプリ６１に同乗依頼を送信した場合に、同乗依頼が送信されたユーザ端末１３のディスプレイに表示される同乗依頼画面の例を示している。 FIG. 9 shows a case where the vehicle allocation integrated management device 12 transmits a vehicle allocation request to the user application 61 of a user who is requesting a vehicle allocation close to each of the boarding place “X” and the destination “Y” of the vehicle allocation request. An example of a passenger request screen displayed on the display of the user terminal 13 to which the request is transmitted is shown.
　図９の同乗依頼画面では、「同乗希望者がいます。同乗を許可した場合、同乗者の目的地までの運賃が０円になります。同乗を許可しますか？」のメッセージ１６１と、「許可する」ボタン１６２、および、「許可しない」ボタン１６３を備えるウィンドウ１６４が表示される。「許可する」ボタン１６２は、ユーザが同乗を許可してもよい場合に操作（押下）される。「許可しない」ボタン１６３は、ユーザが同乗を許可したくない場合に操作（押下）される。 On the passenger request screen shown in Fig. 9, the message 161 "There are passengers who wish to ride. If you allow passengers, the fare to the passenger's destination will be 0 yen. Do you want to allow passengers?" A window 164 with a "Allow" button 162 and a "Don't Allow" button 163 is displayed. The "permit" button 162 is operated (pressed) when the user may allow the ride. The "not allowed" button 163 is operated (pressed) when the user does not want to allow riding.
　エリアマップ８１上には、同乗を依頼されたユーザの乗車地を示す乗車地マーク１８１および目的地を示す目的地マーク１８２と、同乗を依頼されたユーザの予定走行ルート１８３とが表示されている。また、同乗希望者であるユーザの乗車地を示す乗車地マーク１８４および目的地を示す目的地マーク１８５も表示されている。 On the area map 81, a boarding place mark 181 indicating the boarding place of the user requested to ride, a destination mark 182 indicating the destination, and a planned traveling route 183 of the user requested to ride are displayed. In addition, a boarding place mark 184 indicating the boarding place of the user who wishes to ride and a destination mark 185 indicating the destination are also displayed.
　同乗を依頼されたユーザは、図９の同乗依頼画面を参照することにより、同乗を依頼してきたユーザの乗車地および目的地と、自分の乗車地および目的地との近さ（遠さ）を確認することができ、インセンティブとして、運賃が０円になる目安を確認することができる。同乗を依頼されたユーザが、自分の目的地を、同乗を依頼してきたユーザの目的地に合わせて変更してもよいか否かを問い合わせ、変更を許可した場合に、同乗を依頼されたユーザにインセンティブを与えてもよい。 By referring to the boarding request screen of FIG. 9, the user requested to ride can determine the proximity (distance) between the boarding place and destination of the user requesting boarding and his / her boarding place and destination. It can be confirmed, and as an incentive, it is possible to confirm the standard that the fare will be 0 yen. When the user who is requested to ride inquires whether or not to change his / her destination according to the destination of the user who requested the ride, and permits the change, the user who is requested to ride May be given an incentive.
　同乗依頼を行う場合の配車制御の処理は、配車権利の譲渡依頼を行う図５および図７の処理と基本的に同様であるので、その詳細な説明は省略する。同乗依頼を行う場合の配車制御の処理は、配車権利の譲渡依頼を行う処理と比較して、同乗可能なタクシー２１を抽出する場合に、乗車地だけでなく、目的地も考慮する必要がある点、インセンティブとして、譲渡人の運賃を割り引くことができる点などが異なる。 The process of vehicle allocation control when requesting a ride is basically the same as the process of FIGS. 5 and 7 for requesting the transfer of the vehicle allocation right, so detailed description thereof will be omitted. Compared with the process of requesting the transfer of the vehicle allocation right, the process of vehicle allocation control when making a ride request needs to consider not only the boarding place but also the destination when extracting the taxi 21 that can be boarded. The difference is that the transferor's fare can be discounted as an incentive.
　乗車地と目的地の両方が近いユーザに対しては、配車権利の譲渡依頼と、同乗依頼の両方を送信し、どちらか一方でも受諾可能かどうかを問い合わせるようにしてもよい。 For users who are close to both the boarding place and the destination, both the transfer right transfer request and the boarding request may be sent to inquire whether either one is acceptable.
　さらには、乗車地については同乗希望のユーザと近いが、目的地については多少離れている同乗候補のユーザに対して、配車権利の譲渡依頼と、同乗依頼の両方を送信し、依頼を受諾するかどうかを問い合わせてもよい。同乗依頼が許可された場合、譲渡人が先に目的地で降車する場合には、譲渡人の目的地までの運賃を無料（譲受人が支払う）にしたり、譲受人が先に目的地で降車する場合には、譲受人の目的地までの運賃を無料（譲受人が支払う）にするインセンティブを付与することができる。 Furthermore, the request for transfer of the vehicle allocation right and the request for boarding are sent to the user who is close to the user who wishes to board the vehicle but is slightly away from the destination, and the request is accepted. You may ask if. If the transfer request is approved and the transferor gets off at the destination first, the fare to the transferor's destination will be free (paid by the transferee), or the transferee will get off at the destination first. If so, an incentive can be given to make the fare to the transferee's destination free (paid by the transferee).
＜７．配車権利譲渡の変形例＞
　上述した実施の形態では、優先会員であるユーザが配車依頼を行った際に、ステータスが「空車」であるタクシー２１が１台も存在しない場合、配車統合管理装置１２は、迎車中のタクシー２１のなかで、配車を希望する優先会員の乗車地「Ｘ」に近いタクシー２１を抽出した。 <7. Modification example of transfer of vehicle allocation right>
In the above-described embodiment, when a user who is a priority member makes a vehicle allocation request and there is no taxi 21 having a status of "empty", the vehicle allocation integrated management device 12 uses the taxi 21 being picked up. Among them, taxi 21 near the boarding place "X" of the priority member who wishes to be dispatched was extracted.
　その他、配車統合管理装置１２は、ユーザを実際に乗せている実車中のタクシー２１のなかから、配車を希望する優先会員の乗車地「Ｘ」に近いタクシー２１を抽出し、そのタクシー２１のユーザ（のユーザアプリ６１）に、同乗依頼または譲渡依頼を送信してもよい。同乗依頼の場合、上述した同乗依頼の変形例と同様に、譲渡人は、インセンティブとして、譲受人が乗車する経路部分の運賃や、全体の運賃の一部を割り引くことができる。譲渡依頼の場合、譲渡人のインセンティブとして、譲渡人が譲受人に譲渡するまでにかかった運賃を無料とし、代わりに、譲受人が運賃を支払うようにすることができる。譲渡人が譲受人に譲渡してタクシー２１を降車した場合、配車統合管理装置１２の配車管理部５４は、代わりのタクシー２１を要請し、譲渡人のインセンティブとして、代わりのタクシー２１の運賃を無料にしたり、割引料金にしてもよい。同乗依頼または譲渡依頼を許諾可能なユーザが複数いる場合には、目的地までの残りの距離が少ないユーザを譲渡人として、同乗または譲渡するタクシー２１を決定してもよい。 In addition, the vehicle allocation integrated management device 12 extracts a taxi 21 close to the boarding place "X" of the priority member who wants to dispatch from the taxi 21 in the actual vehicle actually carrying the user, and the user of the taxi 21. You may send a ride request or a transfer request to (user application 61). In the case of a passenger request, the transferor can discount a part of the fare of the route portion on which the transferee boarded or a part of the total fare as an incentive, as in the modification of the passenger request described above. In the case of a transfer request, as an incentive for the transferor, the fare required for the transferor to transfer to the transferee may be free, and the transferee may pay the fare instead. When the transferor transfers the taxi 21 to the transferee and gets off the taxi 21, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 requests a substitute taxi 21, and as an incentive for the transferor, the fare of the substitute taxi 21 is free. Or a discounted rate. When there are a plurality of users who can grant a ride request or a transfer request, the taxi 21 to be boarded or transferred may be determined with the user who has a short remaining distance to the destination as the transferor.
　優先会員の乗車地「Ｘ」付近に迎車中のタクシー２１が存在せず、配車権利を譲渡してくれるユーザや、同乗を許可してくれるユーザがいない場合に、配車予約が確定しているユーザに、配車予約の時刻を３０分ないし１時間程度ずらせないか依頼し、配車予約の時間をずらしてくれた場合に、そのユーザにインセンティブを付与するように制御することができる。 A user whose vehicle allocation reservation is confirmed when there is no taxi 21 being picked up near the boarding place "X" of the priority member and there is no user who transfers the vehicle allocation right or allows the passenger to ride. It is possible to request whether or not to shift the time of the vehicle allocation reservation by about 30 minutes to 1 hour, and to give an incentive to the user when the time of the vehicle allocation reservation is shifted.
　タクシー需要が多く、「空車」のタクシー２１が存在しないような状況は、例えば、バス等のその他の移動手段がない地域であったり、通勤、通学が集中する時間帯など、場所や時間、天候、などの状況で予測できる場合もある。 The situation where there is a lot of taxi demand and there is no "empty" taxi 21 is the place, time, weather, for example, in an area where there is no other means of transportation such as a bus, or when commuting to work or school is concentrated. In some cases, it can be predicted in situations such as.
　そのようなタクシー需給の逼迫が予想される時間、場所に、ユーザのユーザアプリ６１から配車依頼が行われた場合、配車管理部５４は、混雑する時間帯や場所（乗車地、目的地）を回避するような提案を行うことができる。ユーザが、配車管理部５４からの依頼に対して、配車依頼の時間や場所の変更を行った場合、そのユーザにインセンティブを付与するように制御することができる。 When a vehicle allocation request is made from the user application 61 at a time and place where such a tight supply and demand of taxi is expected, the vehicle allocation management unit 54 determines a busy time zone and place (boarding place, destination). You can make suggestions to avoid it. When a user changes the time or place of a vehicle allocation request in response to a request from the vehicle allocation management unit 54, it is possible to control the user to be given an incentive.
＜８．実施の形態のまとめ＞
　以上、本技術を適用した実施の形態であるタクシー配車システム１によれば、配車統合管理装置１２の配車管理部５４は、例えば、優先会員のユーザから配車依頼があり、ステータスが「空車」であるタクシー２１が１台も存在しない場合には、優先会員のユーザが配車依頼で入力した乗車地「Ｘ」から所定の範囲内の場所へ移動している迎車中のタクシー２１を検索し、ユーザAのタクシー２１や、ユーザBのタクシー２１を抽出する。配車管理部５４は、タクシー２１の配車が確定済みのユーザAやユーザB（第１のユーザ）の端末装置１３に、配車の権利譲渡またはタクシー２１への同乗許可の依頼を送信し、ユーザAやユーザBの端末装置１３から、依頼を許諾する通知を受信した場合、優先会員のユーザ（第２のユーザ）の端末装置１３へ、配車または同乗が可能であることを送信する。 <8. Summary of embodiments>
As described above, according to the taxi dispatch system 1 of the embodiment to which the present technology is applied, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives, for example, a vehicle allocation request from a priority member user, and the status is "empty". If there is no taxi 21 at all, the user searches for a taxi 21 that is moving from the boarding place "X" entered in the dispatch request by the priority member user to a place within a predetermined range, and the user. The taxi 21 of A and the taxi 21 of user B are extracted. The vehicle allocation management unit 54 transmits a request for transfer of the vehicle allocation right or permission to ride in the taxi 21 to the terminal device 13 of the user A or the user B (first user) whose taxi 21 has been confirmed to be allocated, and the user A When a notification for permitting the request is received from the terminal device 13 of the user B or the user B, the terminal device 13 of the priority member user (second user) is notified that the vehicle can be dispatched or boarded.
　これにより、優先会員等の特定のユーザからの配車依頼に対応できる確率を向上させることができる。 This makes it possible to improve the probability of being able to respond to a vehicle allocation request from a specific user such as a priority member.
　上述した実施の形態では、移動装置として、タクシーの配車を制御する例について説明したが、お客（人）を乗せるその他の移動装置、具体的には、バス、電車、飛行機、船、ヘリコプターなどや、物（荷物）を載せる移動装置、トラック、ダンプ等の移動装置にも適用することができる。また、移動装置は、ドローン等の無人で動く装置であってもよい。 In the above-described embodiment, an example of controlling the dispatch of a taxi as a mobile device has been described, but other mobile devices for carrying customers (people), specifically, buses, trains, airplanes, ships, helicopters, etc. , It can also be applied to mobile devices such as mobile devices for loading objects (luggage), trucks, and dumps. Further, the moving device may be an unmanned moving device such as a drone.
＜９．コンピュータ構成例＞
　上述した一連の処理は、ハードウエアにより実行することもできるし、ソフトウエアにより実行することもできる。一連の処理をソフトウエアにより実行する場合には、そのソフトウエアを構成するプログラムが、コンピュータにインストールされる。ここで、コンピュータには、専用のハードウエアに組み込まれているマイクロコンピュータや、各種のプログラムをインストールすることで、各種の機能を実行することが可能な、例えば汎用のパーソナルコンピュータなどが含まれる。 <9. Computer configuration example>
The series of processes described above can be executed by hardware or software. When a series of processes are executed by software, the programs constituting the software are installed on the computer. Here, the computer includes a microcomputer embedded in dedicated hardware and, for example, a general-purpose personal computer capable of executing various functions by installing various programs.
　図１２は、配車統合管理装置１２、ユーザ端末１３、または、端末装置３３が実行する各処理をコンピュータがプログラムにより実行する場合の、コンピュータのハードウエアの構成例を示すブロック図である。 FIG. 12 is a block diagram showing a configuration example of computer hardware when the computer executes each process executed by the vehicle allocation integrated management device 12, the user terminal 13, or the terminal device 33 by a program.
　コンピュータにおいて、CPU（Central Processing Unit）２０１，ROM（Read Only Memory）２０２，RAM（Random Access Memory）２０３は、バス２０４により相互に接続されている。 In a computer, a CPU (Central Processing Unit) 201, a ROM (ReadOnly Memory) 202, and a RAM (RandomAccessMemory) 203 are connected to each other by a bus 204.
　バス２０４には、さらに、入出力インタフェース２０５が接続されている。入出力インタフェース２０５には、入力部２０６、出力部２０７、記憶部２０８、通信部２０９、及びドライブ２１０が接続されている。 An input / output interface 205 is further connected to the bus 204. An input unit 206, an output unit 207, a storage unit 208, a communication unit 209, and a drive 210 are connected to the input / output interface 205.
　入力部２０６は、操作ボタン、キーボード、マウス、マイクロホン、タッチパネル、入力端子などよりなる。出力部２０７は、ディスプレイ、スピーカ、出力端子などよりなる。記憶部２０８は、ハードディスク、RAMディスク、不揮発性のメモリなどよりなる。通信部２０９は、ネットワークインタフェースなどよりなる。ドライブ２１０は、磁気ディスク、光ディスク、光磁気ディスク、或いは半導体メモリなどのリムーバブル記録媒体２１１を駆動する。 The input unit 206 includes operation buttons, a keyboard, a mouse, a microphone, a touch panel, an input terminal, and the like. The output unit 207 includes a display, a speaker, an output terminal, and the like. The storage unit 208 includes a hard disk, a RAM disk, a non-volatile memory, and the like. The communication unit 209 includes a network interface and the like. The drive 210 drives a removable recording medium 211 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.
　以上のように構成されるコンピュータでは、CPU２０１が、例えば、記憶部２０８に記憶されているプログラムを、入出力インタフェース２０５及びバス２０４を介して、RAM２０３にロードして実行することにより、上述した一連の処理が行われる。RAM２０３にはまた、CPU２０１が各種の処理を実行する上において必要なデータなども適宜記憶される。 In the computer configured as described above, the CPU 201 loads the program stored in the storage unit 208 into the RAM 203 via the input / output interface 205 and the bus 204 and executes the above-described series. Is processed. The RAM 203 also appropriately stores data and the like necessary for the CPU 201 to execute various processes.
　コンピュータ（CPU２０１）が実行するプログラムは、例えば、パッケージメディア等としてのリムーバブル記録媒体２１１に記録して提供することができる。また、プログラムは、ローカルエリアネットワーク、インターネット、デジタル衛星放送といった、有線または無線の伝送媒体を介して提供することができる。 The program executed by the computer (CPU201) can be recorded and provided on the removable recording medium 211 as a package media or the like, for example. Programs can also be provided via wired or wireless transmission media such as local area networks, the Internet, and digital satellite broadcasts.
　コンピュータでは、プログラムは、リムーバブル記録媒体２１１をドライブ２１０に装着することにより、入出力インタフェース２０５を介して、記憶部２０８にインストールすることができる。また、プログラムは、有線または無線の伝送媒体を介して、通信部２０９で受信し、記憶部２０８にインストールすることができる。その他、プログラムは、ROM２０２や記憶部２０８に、あらかじめインストールしておくことができる。 In the computer, the program can be installed in the storage unit 208 via the input / output interface 205 by mounting the removable recording medium 211 in the drive 210. Further, the program can be received by the communication unit 209 and installed in the storage unit 208 via a wired or wireless transmission medium. In addition, the program can be pre-installed in the ROM 202 or the storage unit 208.
　本明細書において、システムとは、複数の構成要素（装置、モジュール（部品）等）の集合を意味し、すべての構成要素が同一筐体中にあるか否かは問わない。したがって、別個の筐体に収納され、ネットワークを介して接続されている複数の装置、及び、１つの筐体の中に複数のモジュールが収納されている１つの装置は、いずれも、システムである。 In the present specification, the system means a set of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network, and a device in which a plurality of modules are housed in one housing are both systems. ..
　また、本明細書において、フローチャートに記述されたステップは、記載された順序に沿って時系列的に行われる場合はもちろん、必ずしも時系列的に処理されなくとも、並列に、あるいは呼び出しが行われたとき等の必要なタイミングで実行されてもよい。 Further, in the present specification, the steps described in the flowchart are not necessarily processed in chronological order as well as in chronological order in the order described, but are called in parallel or are called. It may be executed at a necessary timing such as when.
　本技術の実施の形態は、上述した実施の形態に限定されるものではなく、本技術の要旨を逸脱しない範囲において種々の変更が可能である。 The embodiment of the present technology is not limited to the above-described embodiment, and various changes can be made without departing from the gist of the present technology.
　例えば、上述した実施の形態の全てまたは一部を組み合わせた形態を採用することができる。 For example, a form in which all or a part of the above-described embodiments are combined can be adopted.
　例えば、本技術は、１つの機能をネットワークを介して複数の装置で分担、共同して処理するクラウドコンピューティングの構成をとることができる。 For example, this technology can have a cloud computing configuration in which one function is shared by a plurality of devices via a network and processed jointly.
　また、上述のフローチャートで説明した各ステップは、１つの装置で実行する他、複数の装置で分担して実行することができる。 In addition, each step described in the above flowchart can be executed by one device or shared by a plurality of devices.
　さらに、１つのステップに複数の処理が含まれる場合には、その１つのステップに含まれる複数の処理は、１つの装置で実行する他、複数の装置で分担して実行することができる。 Further, when one step includes a plurality of processes, the plurality of processes included in the one step can be executed by one device or shared by a plurality of devices.
　なお、本明細書に記載された効果はあくまで例示であって限定されるものではなく、本明細書に記載されたもの以外の効果があってもよい。 It should be noted that the effects described in the present specification are merely examples and are not limited, and effects other than those described in the present specification may be obtained.
　なお、本技術は、以下の構成を取ることができる。
（１）
　移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信し、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、第２のユーザの端末装置へ、前記配車または同乗が可能であることを送信する管理部を備える
　配車管理装置。
（２）
　前記管理部は、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記第１のユーザの端末装置にインセンティブ情報を送信する
　前記（１）に記載の配車管理装置。
（３）
　前記第１のユーザと前記第２のユーザは、登録されているユーザの種別が異なり、
　前記第２のユーザは、前記第１のユーザよりも配車が優先される種別である
　前記（１）または（２）に記載の配車管理装置。
（４）
　前記依頼が送信される前記第１のユーザは、前記第２のユーザが指定した乗車地から所定の範囲内の場所へ移動している前記移動装置の配車が確定済みのユーザである
　前記（１）乃至（３）のいずれかに記載の配車管理装置。
（５）
　前記管理部は、移動装置の配車が確定済みの複数の前記第１のユーザそれぞれの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信する
　前記（１）乃至（４）のいずれかに記載の配車管理装置。
（６）
　前記管理部は、複数の前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記第２のユーザが指定した乗車地へ最も早く到着可能な前記移動装置の前記第１のユーザへ配車する移動装置を、前記第２のユーザへ割り当てる移動装置に決定する
　前記（５）に記載の配車管理装置。
（７）
　前記管理部は、複数の前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記配車の権利譲渡または前記移動装置への同乗許可の金額が最も安い前記第１のユーザへ配車する移動装置を、前記第２のユーザへ割り当てる移動装置に決定する
　前記（５）に記載の配車管理装置。
（８）
　前記管理部は、優先的な配車を行うか否かを前記第２のユーザの端末装置へ送信し、前記優先的な配車を行うと返信されてきた場合、移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信する
　前記（１）乃至（７）のいずれかに記載の配車管理装置。
（９）
　前記管理部は、前記第１のユーザの端末装置に前記依頼を送信し、前記第１のユーザから拒否された場合、前記依頼を許諾した場合に前記第１のユーザの端末装置に送信するインセンティブ情報を変更し、再度、前記依頼を送信する
　前記（１）乃至（８）のいずれかに記載の配車管理装置。
（１０）
　前記管理部は、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記移動装置に搭載された端末装置へ、前記移動装置の配車の変更通知を送信する
　前記（１）乃至（９）のいずれかに記載の配車管理装置。
（１１）
　配車管理装置が、
　移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信し、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、第２のユーザの端末装置へ、前記配車または同乗が可能であることを送信する
　配車管理方法。
（１２）
　コンピュータに、
　移動装置の配車の権利譲渡または前記移動装置への同乗許可の依頼を、配車管理装置から受信する処理と、
　前記依頼を許諾する通知を前記配車管理装置へ送信する処理と、
　前記依頼を許諾する通知に応じて、前記配車管理装置から、インセンティブ情報を受信する処理と
　を実行させるためのプログラム。 The present technology can have the following configurations.
(1)
A request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed, and the request is granted from the terminal device of the first user. A vehicle allocation management device including a management unit that transmits the above-mentioned vehicle allocation or riding is possible to the terminal device of the second user when the notification is received.
(2)
The vehicle allocation management device according to (1), wherein when the management unit receives a notification for granting the request from the terminal device of the first user, the management unit transmits incentive information to the terminal device of the first user. ..
(3)
The first user and the second user have different types of registered users.
The vehicle allocation management device according to (1) or (2), wherein the second user is a type in which vehicle allocation is prioritized over the first user.
(4)
The first user to whom the request is transmitted is a user whose allocation of the moving device that has been moved from the boarding place designated by the second user to a place within a predetermined range has been confirmed (1). ) To (3).
(5)
The management unit transmits a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device to the terminal devices of each of the plurality of first users whose allocation of the mobile device has been confirmed. The vehicle allocation management device according to any one of 4).
(6)
When the management unit receives notifications for granting the request from the terminal devices of the plurality of first users, the management unit can arrive at the boarding place designated by the second user earliest. The vehicle allocation management device according to (5) above, wherein the mobile device to be assigned to one user is determined to be the mobile device to be assigned to the second user.
(7)
When the management unit receives notifications for granting the request from the terminal devices of the plurality of first users, the first one has the lowest amount of transfer of the right to dispatch the vehicle or permission to ride on the mobile device. The vehicle allocation management device according to (5) above, wherein the mobile device to be assigned to the user is determined to be the mobile device to be assigned to the second user.
(8)
The management unit transmits whether or not to perform preferential vehicle allocation to the terminal device of the second user, and when a reply is returned that the preferential vehicle allocation is performed, the vehicle allocation of the mobile device has been confirmed. The vehicle allocation management device according to any one of (1) to (7) above, which transmits a request for transfer of the right to dispatch the vehicle or permission to ride on the mobile device to the terminal device of one user.
(9)
The management unit sends the request to the terminal device of the first user, and if the request is rejected by the first user, the incentive to send the request to the terminal device of the first user when the request is approved. The vehicle allocation management device according to any one of (1) to (8) above, wherein the information is changed and the request is transmitted again.
(10)
When the management unit receives a notification for granting the request from the terminal device of the first user, the management unit transmits a notification of change in vehicle allocation of the mobile device to the terminal device mounted on the mobile device. The vehicle allocation management device according to any one of 1) to (9).
(11)
The vehicle allocation management device
A request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed, and the request is granted from the terminal device of the first user. When the notification is received, the vehicle allocation management method of transmitting to the terminal device of the second user that the vehicle can be dispatched or can be boarded.
(12)
On the computer
The process of receiving a request for transfer of the right to dispatch a mobile device or permission to ride on the mobile device from the vehicle allocation management device, and
The process of sending a notification to approve the request to the vehicle allocation management device, and
A program for executing a process of receiving incentive information from the vehicle allocation management device in response to a notification for granting the request.
　１　タクシー配車システム，　１１　配車管理装置，　１２　配車統合管理装置，　１３　端末装置（ユーザ端末），　２１　タクシー，　３１　車載器，　３３　端末装置，　３４　車両動態データ生成部，　３５　ドライバアプリ，　４１　車両動態データ管理部，　４２　注文情報管理部，　５１　車両動態データ管理部，　５２　顧客データ管理部，　５３　注文情報管理部，　５４　配車管理部，　６１　ユーザアプリ，　２０１　CPU，　２０２　ROM，　２０３　RAM，　２０６　入力部，　２０７　出力部，　２０８　記憶部，　２０９　通信部，　２１０　ドライブ 1 taxi dispatch system, 11 vehicle allocation management device, 12 vehicle allocation integrated management device, 13 terminal device (user terminal), 21 taxi, 31 in-vehicle device, 33 terminal device, 34 vehicle dynamic data generator, 35 driver application, 41 vehicle dynamic data Management department, 42 order information management department, 51 vehicle dynamics data management department, 52 customer data management department, 53 order information management department, 54 vehicle allocation management department, 61 user application, 201 CPU, 202 ROM, 203 RAM, 206 input department, 207 output unit, 208 storage unit, 209 communication unit, 210 drive

Claims (12)

  1. 　移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信し、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、第２のユーザの端末装置へ、前記配車または同乗が可能であることを送信する管理部を備える
    　配車管理装置。     A request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed, and the request is granted from the terminal device of the first user. A vehicle allocation management device including a management unit that transmits the above-mentioned vehicle allocation or riding is possible to the terminal device of the second user when the notification is received.
  2. 　前記管理部は、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記第１のユーザの端末装置にインセンティブ情報を送信する
    　請求項１に記載の配車管理装置。     The vehicle allocation management device according to claim 1, wherein when the management unit receives a notification for granting the request from the terminal device of the first user, the management unit transmits incentive information to the terminal device of the first user.
  3. 　前記第１のユーザと前記第２のユーザは、登録されているユーザの種別が異なり、
    　前記第２のユーザは、前記第１のユーザよりも配車が優先される種別である
    　請求項１に記載の配車管理装置。     The first user and the second user have different types of registered users.
    The vehicle allocation management device according to claim 1, wherein the second user is a type in which vehicle allocation is prioritized over the first user.
  4. 　前記依頼が送信される前記第１のユーザは、前記第２のユーザが指定した乗車地から所定の範囲内の場所へ移動している前記移動装置の配車が確定済みのユーザである
    　請求項１に記載の配車管理装置。     The first user to whom the request is transmitted is a user whose allocation of the mobile device has been confirmed to be moving from the boarding place designated by the second user to a place within a predetermined range. Vehicle allocation management device described in.
  5. 　前記管理部は、移動装置の配車が確定済みの複数の前記第１のユーザそれぞれの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信する
    　請求項１に記載の配車管理装置。     The first aspect of claim 1, wherein the management unit transmits a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device to the terminal devices of each of the plurality of first users whose allocation of the mobile device has been confirmed. Vehicle allocation management device.
  6. 　前記管理部は、複数の前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記第２のユーザが指定した乗車地へ最も早く到着可能な前記移動装置の前記第１のユーザへ配車する移動装置を、前記第２のユーザへ割り当てる移動装置に決定する
    　請求項５に記載の配車管理装置。     When the management unit receives notifications for granting the request from the terminal devices of the plurality of first users, the management unit can arrive at the boarding place designated by the second user earliest. The vehicle allocation management device according to claim 5, wherein the mobile device for allocating a vehicle to one user is determined to be a mobile device to be assigned to the second user.
  7. 　前記管理部は、複数の前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記配車の権利譲渡または前記移動装置への同乗許可の金額が最も安い前記第１のユーザへ配車する移動装置を、前記第２のユーザへ割り当てる移動装置に決定する
    　請求項５に記載の配車管理装置。     When the management unit receives notifications for granting the request from the terminal devices of the plurality of first users, the first one has the lowest amount of transfer of the right to dispatch the vehicle or permission to ride on the mobile device. The vehicle allocation management device according to claim 5, wherein the mobile device to be assigned to the user is determined to be the mobile device to be assigned to the second user.
  8. 　前記管理部は、優先的な配車を行うか否かを前記第２のユーザの端末装置へ送信し、前記優先的な配車を行うと返信されてきた場合、移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信する
    　請求項１に記載の配車管理装置。     The management unit transmits whether or not to perform preferential vehicle allocation to the terminal device of the second user, and when a reply is returned that the preferential vehicle allocation is performed, the vehicle allocation of the mobile device has been confirmed. The vehicle allocation management device according to claim 1, wherein a request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the user.
  9. 　前記管理部は、前記第１のユーザの端末装置に前記依頼を送信し、前記第１のユーザから拒否された場合、前記依頼を許諾した場合に前記第１のユーザの端末装置に送信するインセンティブ情報を変更し、再度、前記依頼を送信する
    　請求項１に記載の配車管理装置。     The management unit sends the request to the terminal device of the first user, and if the request is rejected by the first user, the incentive to send the request to the terminal device of the first user when the request is approved. The vehicle allocation management device according to claim 1, wherein the information is changed and the request is transmitted again.
  10. 　前記管理部は、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、前記移動装置に搭載された端末装置へ、前記移動装置の配車の変更通知を送信する
    　請求項１に記載の配車管理装置。     When the management unit receives a notification for granting the request from the terminal device of the first user, the management unit transmits a change notification of the vehicle allocation of the mobile device to the terminal device mounted on the mobile device. The vehicle allocation management device according to 1.
  11. 　配車管理装置が、
    　移動装置の配車が確定済みの第１のユーザの端末装置に、前記配車の権利譲渡または前記移動装置への同乗許可の依頼を送信し、前記第１のユーザの端末装置から、前記依頼を許諾する通知を受信した場合、第２のユーザの端末装置へ、前記配車または同乗が可能であることを送信する
    　配車管理方法。     The vehicle allocation management device
    A request for transfer of the right to allocate the vehicle or permission to ride on the mobile device is transmitted to the terminal device of the first user whose vehicle allocation of the mobile device has been confirmed, and the request is granted from the terminal device of the first user. When the notification is received, the vehicle allocation management method of transmitting to the terminal device of the second user that the vehicle can be dispatched or can be boarded.
  12. 　コンピュータに、
    　移動装置の配車の権利譲渡または前記移動装置への同乗許可の依頼を、配車管理装置から受信する処理と、
    　前記依頼を許諾する通知を前記配車管理装置へ送信する処理と、
    　前記依頼を許諾する通知に応じて、前記配車管理装置から、インセンティブ情報を受信する処理と
    　を実行させるためのプログラム。     On the computer
    The process of receiving a request for transfer of the right to dispatch a mobile device or permission to ride on the mobile device from the vehicle allocation management device, and
    The process of sending a notification to approve the request to the vehicle allocation management device, and
    A program for executing a process of receiving incentive information from the vehicle allocation management device in response to a notification for granting the request.
PCT/JP2021/009440 2020-03-24 2021-03-10 Vehicle dispatch management device, vehicle dispatch management method, and program WO2021193052A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2022509555A JPWO2021193052A1 (en) 2020-03-24 2021-03-10

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020052974 2020-03-24
JP2020-052974 2020-03-24

Publications (1)

Publication Number Publication Date
WO2021193052A1 true WO2021193052A1 (en) 2021-09-30

Family

ID=77891453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/009440 WO2021193052A1 (en) 2020-03-24 2021-03-10 Vehicle dispatch management device, vehicle dispatch management method, and program

Country Status (2)

Country Link
JP (1) JPWO2021193052A1 (en)
WO (1) WO2021193052A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019219781A (en) * 2018-06-18 2019-12-26 日産自動車株式会社 Business vehicle operation system
JP2020038472A (en) * 2018-09-04 2020-03-12 トヨタ自動車株式会社 Information processor and information processing method and program

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019219781A (en) * 2018-06-18 2019-12-26 日産自動車株式会社 Business vehicle operation system
JP2020038472A (en) * 2018-09-04 2020-03-12 トヨタ自動車株式会社 Information processor and information processing method and program

Also Published As

Publication number Publication date
JPWO2021193052A1 (en) 2021-09-30

Similar Documents

Publication Publication Date Title
US20220335363A1 (en) System and method for transportation
CN108475466B (en) System and method for matching and displaying service requests and available vehicles
JP7010194B2 (en) Vehicle dispatch system, server and information processing method
JP2012088925A (en) Ecological taxi dispatch support system
WO2003100744A1 (en) Communication system
WO2019243883A1 (en) System for operating commercial vehicles
KR20220152972A (en) System and method for providing integrated transportation services
KR20070049336A (en) Management method of transport service system
JP2003308596A (en) Taxi-sharing reservation operation system
JP7042201B2 (en) Programs, information processing methods, and information processing equipment
JPWO2019176819A1 (en) Vehicle dispatch billing device
JP7276191B2 (en) SERVER, VEHICLE OPERATION SYSTEM, VEHICLE OPERATION METHOD AND VEHICLE OPERATION PROGRAM
JP7083859B2 (en) Public transportation system
WO2021193052A1 (en) Vehicle dispatch management device, vehicle dispatch management method, and program
JP2021152761A (en) Vehicle allocation management device, vehicle allocation management method, and program
WO2021182131A1 (en) Vehicle allocation system, vehicle allocation management method, and program
JP2005258840A (en) Vehicle-running management system, vehicle-running management method, and vehicle running management device
JP7152288B2 (en) System, method and program for providing content
CN113807855A (en) Settlement agent device, settlement agent system, settlement agent method, and settlement agent program
SG191453A1 (en) System and method for flexible and efficient public transportation
JP2002222492A (en) Method and system for optimum vehicle distribution
JP7288419B2 (en) Information processing device, information processing method, and information processing system
US20230188932A1 (en) Technique for determination of a passenger, and ticketing for the passenger in a public transport
WO2024101140A1 (en) Information processing system, information processing method, and program
JP2022077568A (en) Information processing system, information processing method, and information processing program

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21776521

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022509555

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21776521

Country of ref document: EP

Kind code of ref document: A1