WO2021193052A1 - Dispositif et procédé de gestion de déploiement de véhicules ainsi que programme - Google Patents

Dispositif et procédé de gestion de déploiement de véhicules ainsi que programme 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
English (en)
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/fr

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

La présente invention concerne un dispositif et un procédé de gestion de déploiement de véhicule ainsi qu'un programme au moyen desquels il est possible d'améliorer la probabilité de pouvoir répondre à une demande de déploiement de véhicule d'un utilisateur spécifique tel qu'un membre prioritaire. Le présent dispositif de gestion intégré de déploiement de véhicule transmet une demande de transfert du droit à un répartiteur de véhicule, ou une demande d'autorisation de rouler ensemble dans un taxi, à un dispositif terminal appartenant à un premier utilisateur pour lequel un déploiement d'un taxi a été confirmé, et si une notification accordant la demande est reçue du dispositif terminal appartenant au premier utilisateur, transmet la possibilité de déployer un véhicule, ou de rouler ensemble, à un dispositif terminal appartenant à un second utilisateur. La présente invention peut s'appliquer par exemple à un système de déploiement de véhicule taxi.
PCT/JP2021/009440 2020-03-24 2021-03-10 Dispositif et procédé de gestion de déploiement de véhicules ainsi que programme WO2021193052A1 (fr)

Priority Applications (1)

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

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=77891453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/009440 WO2021193052A1 (fr) 2020-03-24 2021-03-10 Dispositif et procédé de gestion de déploiement de véhicules ainsi que programme

Country Status (2)

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

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019219781A (ja) * 2018-06-18 2019-12-26 日産自動車株式会社 営業用車両運用システム
JP2020038472A (ja) * 2018-09-04 2020-03-12 トヨタ自動車株式会社 情報処理装置、情報処理方法及びプログラム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019219781A (ja) * 2018-06-18 2019-12-26 日産自動車株式会社 営業用車両運用システム
JP2020038472A (ja) * 2018-09-04 2020-03-12 トヨタ自動車株式会社 情報処理装置、情報処理方法及びプログラム

Also Published As

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

Similar Documents

Publication Publication Date Title
US20220335363A1 (en) System and method for transportation
CN108475466B (zh) 用于匹配和显示服务请求和可用车辆的***和方法
JP7010194B2 (ja) 車両派遣システム、サーバおよび情報処理方法
JP2012088925A (ja) エコタクシー配車支援システム
WO2003100744A1 (fr) Systeme de communication
WO2019243883A1 (fr) Système d'exploitation de véhicules utilitaires
KR20220152972A (ko) 통합 교통 서비스 제공 시스템 및 방법
KR20070049336A (ko) 운송 서비스 시스템의 운영방법
JP2003308596A (ja) 乗合タクシー予約・運行システム
JP7042201B2 (ja) プログラム、情報処理方法、及び情報処理装置
JPWO2019176819A1 (ja) 配車課金装置
JP7276191B2 (ja) サーバ、車両運行システム、車両運行方法及び車両運行プログラム
JP2020119441A (ja) 配車プログラム及び配車システム
WO2021193052A1 (fr) Dispositif et procédé de gestion de déploiement de véhicules ainsi que programme
JP2021152761A (ja) 配車管理装置、配車管理方法、およびプログラム
WO2021182131A1 (fr) Système d'attribution de véhicule, procédé de gestion d'attribution de véhicule et programme
JP2005258840A (ja) 車両運行管理システム、車両運行管理方法、および車両運行管理装置
JP7152288B2 (ja) コンテンツを提供するためのシステム、方法、及びプログラム
CN113807855A (zh) 结算代理装置、结算代理***、结算代理方法及结算代理程序
SG191453A1 (en) System and method for flexible and efficient public transportation
JP2002222492A (ja) 最適車両配車方法および最適車両配車システム
JP7288419B2 (ja) 情報処理装置、情報処理方法及び情報処理システム
US20230188932A1 (en) Technique for determination of a passenger, and ticketing for the passenger in a public transport
WO2024101140A1 (fr) Système, procédé et programme de traitement d'informations
JP2022077568A (ja) 情報処理システム、情報処理方法及び情報処理プログラム

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