JP2022117858A - Ride-sharing support system, ride-sharing support method, and ride-sharing support program - Google Patents

Abstract

To provide a ride-sharing support system, a ride-sharing support method, and a ride-sharing support program capable of improving convenience of users who use ride-sharing services.SOLUTION: A ride-sharing support system 100 includes: an acquisition processing unit 112 that acquires information on a first destination from a first user who uses a ride-sharing vehicle; a notification processing unit 117 that notifies a second user belonging to the same group as the first user of an inquiry as to whether or not to visit the first destination using the ride-sharing vehicle by ride-sharing with the first user; an identification processing unit 113 that identifies a driver of the ride-sharing vehicle; and a vehicle allocation processing unit 116 that outputs a vehicle allocation request to the driver identified by the identification processing unit 113.SELECTED DRAWING: Figure 1

Description

The present invention relates to a boarding assistance system, a boarding assistance method, and a boarding assistance program.

Conventionally, there has been known a ride-sharing system in which a driver of a vehicle travels to a predetermined destination with a user who wishes to ride together. For example, Patent Literature 1 discloses a technique for improving the convenience of ride sharing by enabling the driver of the vehicle to easily identify the user using the ride sharing.

JP 2019-144994 A

By the way, in recent years, the introduction of a pick-up service by the mutual help of local residents is progressing. In the pick-up service, a local resident who can be picked up is matched as a driver by a resident who wishes to use the service. The driver puts the inhabitants on the private vehicle and transports the inhabitants to the destination. Since the conventional pick-up service transports only the users who have applied for the use, the usage efficiency of the pick-up service is lowered. In addition, when a plurality of users ride together as in the conventional ride-sharing, there arises a problem that the required time to each destination of each user becomes longer and each user feels uncomfortable.

An object of the present invention is to provide a ride-sharing support system, a ride-sharing support method, and a ride-sharing support program capable of improving the convenience of users who use the ride-sharing service.

A ride-sharing support system according to one aspect of the present invention includes an acquisition processing unit that acquires information on a first destination from a first user who uses a specific vehicle; a notification processing unit for notifying the user of an inquiry as to whether or not to visit the first destination by sharing the specific vehicle with the first user; and a specification for specifying the driver of the specific vehicle. and a vehicle allocation processing unit that outputs a vehicle allocation request to the driver identified by the identification processing unit.

According to the above configuration, a plurality of users can ride together and be transported to the destination, so it is possible to improve the utilization efficiency of the ride-sharing service. In addition, since a plurality of users belonging to the same group can ride together, each user can use the ride-sharing service with peace of mind.

In the ride-sharing support system according to the present invention, when the second user replies that the second user will share a ride with the first user and use the specific vehicle to visit the first destination, the Identify the driver corresponding to the first user and the second user.

As a result, it is possible to specify the driver suitable for the first user and the second user, so that each user can use the rideshare service with peace of mind.

In the ride-sharing support system according to the present invention, the identification processing unit identifies the driver that each of the first user and the second user has used in the past. Further, in the ride-sharing support system according to the present invention, the identification processing unit causes the driver, based on an evaluation value obtained by evaluating the driver when each of the first user and the second user, has used the system in the past. identify. Further, in the ride-sharing support system according to the present invention, date and time information indicating a date and time when the driver can provide the service of transporting the user is registered in advance, and the specific processing unit further includes the first use The driver who can provide the service at the date and time desired by the driver is specified.

In the ride-sharing support system according to the present invention, the group is a group to which a plurality of users who have the same destination registered in advance by each user as a visit destination belong, and the notification processing unit includes the first usage The inquiry is notified to the second user who has registered the same destination as the destination registered by the user. Thereby, the user can receive an inquiry from a user who has registered the same destination and visit the destination together.

In the ride-sharing support system according to the present invention, the group is a group to which a plurality of users with the same usage history of the specific vehicle belongs to, and the notification processing unit is the same as the first user. The second user of the usage history of is notified of the inquiry. As a result, users using the same driver's shared vehicle can visit the destination together.

In the ride-sharing support system according to the present invention, the group is a group to which a plurality of users each having the same attribute belongs, and the notification processing unit includes the first user having the same attribute as the first user. 2. Notify the user of the inquiry. As a result, for example, users with similar tastes and preferences can visit the destination together.

In the ride-sharing support system according to the present invention, the vehicle allocation processing unit instructs the driver identified by the identification processing unit to indicate positions where the first user and the second user each board the specific vehicle. Output information. In addition, in the ride-sharing support system according to the present invention, the dispatch processing unit provides the driver identified by the identification processing unit with the location of the driver, the first user and the second user. outputs information on a route connecting the location where the specific vehicle is boarded and the first destination.

As a result, the driver can smoothly get each user into the vehicle and move to the destination.

In the ride-sharing support system according to the present invention, information on a plurality of users who can use a ride-sharing service in which they get on a specific vehicle and are transported to a destination; Information on one or more users who are qualified to provide services to other users is registered in advance. The specific vehicle may be a private vehicle owned by the user.

As a result, for example, it is possible to realize a pick-up service in which local residents help each other.

A ride-sharing support method according to another aspect of the present invention includes an obtaining step in which one or more processors obtain information about a first destination from a first user who uses a specific vehicle; a notification step of informing the second user belonging to the group of the inquiry whether or not to visit the first destination by sharing the specific vehicle with the first user; and driving the specific vehicle. and a dispatching step of outputting a dispatch request to the driver identified by the identifying step.

A ride-sharing assistance program according to another aspect of the present invention includes an acquisition step of acquiring information about a first destination from a first user who uses a specific vehicle, and a second usage information belonging to the same group as the first user. a notification step of notifying the person of an inquiry as to whether or not he/she will visit the first destination by sharing the specific vehicle with the first user; and a identifying step of identifying the driver of the specific vehicle. and a vehicle allocation step of outputting a vehicle allocation request to the driver identified by the identification step.

ADVANTAGE OF THE INVENTION According to this invention, the ride-sharing assistance system, the ride-sharing assistance method, and the ride-sharing assistance program which can improve the convenience of the user using a ride-sharing service are provided.

FIG. 1 is a functional block diagram showing the configuration of a boarding assistance system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of user information used in the ride-sharing support system according to the embodiment of the present invention. FIG. 3 is a diagram showing an example of driver information used in the boarding assistance system according to the embodiment of the present invention. FIG. 4 is a diagram showing an example of hospital group information used in the ride-sharing support system according to the embodiment of the present invention. FIG. 5 is a diagram showing an example of city hall group information used in the ride-sharing support system according to the embodiment of the present invention. FIG. 6 is a diagram showing an example of a display screen displayed on a requester terminal in the ride-sharing support system according to the embodiment of the present invention. FIG. 7 is a diagram showing an example of a display screen displayed on the client terminal of the ride-sharing support system according to the embodiment of the present invention. FIG. 8 is a diagram showing an example of a display screen displayed on the driver terminal of the passenger support system according to the embodiment of the present invention. FIG. 9 is a diagram showing an example of a display screen displayed on the driver terminal of the passenger support system according to the embodiment of the present invention. FIG. 10 is a diagram showing an example of a display screen displayed on the client terminal of the ride-sharing support system according to the embodiment of the present invention. FIG. 11 is a diagram showing an example of a display screen displayed on the client terminal of the ride-sharing support system according to the embodiment of the present invention. FIG. 12 is a diagram showing an example of a display screen displayed on the driver terminal of the passenger support system according to the embodiment of the present invention. FIG. 13 is a diagram showing an example of a display screen displayed on the driver terminal of the passenger support system according to the embodiment of the present invention. FIG. 14 is a flow chart showing an example of the procedure of the boarding support process executed in the boarding support system according to the embodiment of the present invention. FIG. 15 is a diagram showing an example of a display screen displayed on the client terminal of the ride-sharing support system according to the embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings for understanding of the present invention. In addition, each following embodiment is an example which actualized this invention, Comprising: It does not limit the technical scope of this invention.

[Ride-sharing support system 100]
As shown in FIG. 1, the boarding assistance system 100 according to the embodiment of the present invention includes a boarding assistance device 1 and one or more user terminals 2 (client terminal 2X, driver terminal 2Y). The ride-sharing support device 1 and the user terminal 2 can communicate via a communication network N1 such as the Internet, LAN, WAN, or public telephone line.

When a user sets a departure point and a destination as search conditions, the ride-sharing support device 1 provides route information on a route from the departure point to the destination, and transports (picks up) the user to the destination. It presents the information (matching result) of the driver who will be the driver, and provides the user with a ride-sharing service that requests the driver to dispatch the vehicle according to the user's request. The ride-sharing support device 1 can receive search conditions for searching for a route, ride-sharing requests, etc. from the user terminal 2, and provides the search result (route information) of the search process based on the search conditions and the matching result to the user. It is an information processing device capable of providing information to the terminal 2 and requesting the matched driver to dispatch a vehicle. Specifically, the ride-sharing support device 1 outputs display data corresponding to the route information and display data relating to the driver to the user terminal 2 . The user terminal 2 is operated by a user requesting (requesting) a route search and a user requesting a ride-sharing, and the information presented by the ride-sharing support device 1 includes the search results (route information) and the matching results. processing equipment. Specifically, the user terminal 2 displays the route based on the display data acquired from the passenger assistance device 1, and displays the route and the driver based on the display data acquired from the passenger assistance device 1. to display information about

In the present embodiment, the user terminal 2 includes a user terminal 2 (hereinafter referred to as "client terminal 2X") used by a user who can use the ride-sharing service, and a user terminal 2 that uses the ride-sharing service. Provide a ride-sharing service in which a user who is able to use a ride-sharing vehicle, such as a privately-owned vehicle, rides another user as a driver and transports the other user to a destination. and a user terminal 2 (hereinafter referred to as “driver terminal 2Y”) used by the user. In the ride-sharing support system 100, a plurality of client terminals 2X and a plurality of driver terminals 2Y are included.

Here, the above-mentioned ride-sharing service is different from the passenger transportation business (taxi business) using taxis, and is a pick-up service in which local residents help each other, and is a pick-up service realized by mutual assistance. In other words, the ride-sharing service is a service in which local residents serve as drivers and transport users to their destinations. For example, in the ride-sharing service, in a certain area, resident A uses a private vehicle to transport resident B to a destination, or resident A uses a private vehicle to transport resident B and resident C together to the destination. A form to do is considered. Moreover, in the ride-sharing service, the driver does not need a second-class driver's license, unlike the taxi industry that requires a second-class driver's license. Qualifications for providing the ride-sharing service are granted to, for example, local residents who have the ability and aptitude to safely drive a vehicle.

In this embodiment, the single boarding support device 1 corresponds to the boarding support system according to the present invention, but the boarding support system according to the present invention includes one or more of the boarding support device 1 and the user terminal 2. It may contain elements. For example, when the constituent elements of the boarding assistance device 1, the requester terminal 2X, and the driver terminal 2Y work together to share and execute a boarding assistance process (see FIG. 14), which will be described later, that process is executed. A system including a plurality of components may constitute the boarding assistance system according to the present invention. For example, the passenger support device 1, the client terminal 2X, and the driver terminal 2Y may constitute the passenger support system according to the present invention.

[Boarding support device 1]
As shown in FIG. 1, the boarding assistance device 1 includes a control unit 11, a storage unit 12, an operation display unit 13, a communication I/F 14, and the like. The boarding assistance device 1 is an information processing device such as a personal computer, for example. The boarding assistance device 1 is not limited to one computer, and may be a computer system in which a plurality of computers operate in cooperation. Moreover, various kinds of processing executed by the boarding assistance device 1 may be distributed and executed by one or a plurality of processors.

The communication I/F 14 connects the boarding support device 1 to the communication network N1 by wire or wirelessly, and communicates with external devices such as the client terminal 2X and the driver terminal 2Y via the communication network N1 according to a predetermined communication protocol. It is a communication interface for performing data communication according to.

The operation display unit 13 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays various types of information, and an operation unit such as a mouse, keyboard, or touch panel that receives operations.

The storage unit 12 is a non-volatile storage unit including a semiconductor memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or the like that stores various types of information. For example, the storage unit 12 stores a control program such as a ride-sharing support program for causing the control unit 11 to execute a ride-sharing support process (see FIG. 14), which will be described later. For example, the boarding assistance program is non-temporarily recorded on a computer-readable recording medium such as a USB, a CD, or a DVD (both of which are registered trademarks), and a USB drive electrically connected to the boarding assistance device 1. , a reading device (not shown) such as a CD drive or a DVD drive, and stored in the storage unit 12 . The ride-sharing support program may be downloaded from an external device via the communication network N1 and stored in the storage unit 12 .

The storage unit 12 also stores a map information database 121 (hereinafter referred to as "map information DB 121"), a user information database 122 (hereinafter referred to as "user information DB 122"), and a driver information database 123 (hereinafter referred to as "user information DB 122"). "driver information DB 123"), hospital group information database 124 (hereinafter referred to as "hospital group information DB 124"), city hall group information database 125 (hereinafter referred to as "city hall group information DB 125"). The storage unit 12 may also include a road information database in which road information (traffic jam information, accident information, etc.) is stored.

The map information DB 121 stores map information such as bus stop data on bus stops, railroad data on railroads (tracks and stations), road data on roads, intersection data on intersections, and facility data on facility locations and appearances (shapes, etc.). remembered.

FIG. 2 is a diagram showing an example of the user information DB 122. As shown in FIG. The user information DB 122 registers information of users who can use the shared ride service. For example, the user installs the application for the ride-sharing service on the user terminal 2, and registers information such as an ID, password, name, e-mail address, destination, icon image, and qualification for providing the ride-sharing service on the registration screen. . The ID and password can be arbitrarily set by the user, and are used as login information when using the ride-sharing service. The e-mail address is, for example, an e-mail address for transmitting and receiving various information to and from the ride-sharing support device 1 . The icon image is image information with which a user can be identified, and is, for example, a face image of the user.

The destination is a destination that the user wishes to visit using the ride-sharing service. For example, if user A1 frequently uses hospital H1 and wishes to be picked up at hospital H1, user A1 registers hospital H1 as a destination. User A2 frequently uses city hall C1 and registers city hall C1 as a destination when he/she wishes to be picked up and dropped off at city hall C1. Each user registers one or more desired destinations on the registration screen of the user terminal 2 in advance. The user can also change the initially registered destination or add a new destination. The destination is information corresponding to an attribute of a group, which will be described later, and is an example of the attribute of the group. For example, if the group is an area group, area information is registered in the user information DB 122 for each user.

The qualification to provide the ride-sharing service is granted to users who have applied for qualification acquisition and have satisfied predetermined conditions among the users registered in the user information DB 122 . For example, the qualification is given to a user who has the ability and aptitude to drive a vehicle safely. Also, the ability and aptitude are determined based on indicators such as the presence or absence of a driver's license (class 1 driver's license), age, years of experience, achievements, health condition, and the like. A user who does not have the above qualification can use the above ride-sharing service, but is prohibited from providing the above-mentioned ride-sharing service to other users as a driver himself/herself. On the other hand, the user who has the qualification can use the ride-sharing service, and can also serve as a driver himself/herself to provide the ride-sharing service to other users. The status (whether or not) of the provision of the ride-sharing service is appropriately based on the user's application for qualification, application for revocation of qualification, driving performance (the track record of providing the ride-sharing service), evaluation of the user (requester), etc. Updated.

FIG. 3 is a diagram showing an example of the driver information DB 123. As shown in FIG. In the driver information DB 123, information of users (drivers) who can provide the ride-sharing service, that is, users who are qualified to provide the ride-sharing service (see FIG. 2) is registered. Specifically, in the driver information DB 123, vehicle information of the shared vehicle used for the shared service, information on available dates and times of the shared service, and the like are registered for each driver. The passenger vehicle may be the driver's private vehicle, or may be a shared vehicle shared by a plurality of the drivers. Passenger vehicles such as the private vehicle and the shared vehicle are examples of the specific vehicle of the present invention, but the specific vehicle of the present invention is not limited to these, and may be a vehicle used as part of community assistance. . For example, it is conceivable that a resident A uses a private vehicle to transport a resident B to a destination in a certain area. The specific vehicle of the present invention is a vehicle (shared vehicle) used by local residents for a shared service in which users are transported to a destination, and is, for example, a user's own vehicle.

The vehicle information in the driver information DB 123 includes, for example, the vehicle number of the passenger vehicle, the vehicle type, the vehicle body color, the number of passengers that can ride in the vehicle, the vehicle inspection information, the driver's license information, and the like. Information on dates and times when the driver can provide the ride-sharing service is registered as the date and time when the ride-sharing service can be provided. For example, driver A2 can provide the ride-sharing service from 12:00 to 15:00 on weekdays, and driver A5 can provide the ride-sharing service from 10:00 to 16:00 on Tuesdays, Wednesdays, and Thursdays. is. The date and time when the ride-sharing service cannot be provided (date and time when the ride-sharing service cannot be provided) may be registered in the driver information DB 123 instead of the date and time when the ride-sharing service can be provided. The date and time when the ride-sharing service can be provided can be appropriately changed by the driver.

FIG. 4 is a diagram showing an example of the hospital group information DB 124. As shown in FIG. In the hospital group information DB 124, information of users who have registered hospital H1 as a destination (see FIG. 2) is registered. Each user registered in the hospital group information DB 124 belongs to a group (hospital group) having the same destination. The hospital group information DB 124 includes IDs, passwords, names, email addresses, and related user information. The related user is a user who has a relationship with the user. , users with similar tastes, relatives of users, etc. The information of the related user may be registered by the control unit 11 based on the usage history of the ride-sharing service, user information (attribute information), etc., or may be registered according to the user's registration operation. . In the hospital group information DB 124 shown in FIG. 4, information based on usage histories in which the user A1 and the user A4 rode together in the same passenger vehicle and visited the hospital H1 in the past is registered.

FIG. 5 is a diagram showing an example of the city hall group information DB 125. As shown in FIG. In the city hall group information DB 125, information of users who have registered the city hall C1 as their destination (see FIG. 2) is registered. Each user registered in the city hall group information DB 125 belongs to a group having the same destination (city hall group). In the city hall group information DB 125 shown in FIG. 5, there are usage histories in which the user A2 and the user A6 rode together in the same passenger vehicle and visited the city hall C1 in the past, and the user A2 and the user A10 previously rode in the same passenger vehicle. Information based on the usage history of visiting the city hall C1 while riding together is registered.

Although not shown, the storage unit 12 includes a group information DB for each destination, such as supermarket SH1, library L1, station ST1, and bank B1.

At least one of the map information DB 121, the user information DB 122, the driver information DB 123, the hospital group information DB 124, and the city hall group information DB 125 of the storage unit 12 is a data server (Fig. not shown). The data server may be composed of one physical server, or may be composed of a cloud server composed of a plurality of physical servers.

The control unit 11 has control devices such as a CPU, ROM, and RAM. The CPU is a processor that executes various kinds of arithmetic processing. The ROM is a non-volatile storage unit in which control programs such as BIOS and OS for causing the CPU to execute various arithmetic processes are stored in advance. The RAM is a volatile or nonvolatile storage unit that stores various information, and is used as a temporary storage memory (work area) for various processes executed by the CPU. The control unit 11 controls the boarding assistance device 1 by causing the CPU to execute various control programs pre-stored in the ROM or the storage unit 12 .

Specifically, the control unit 11 includes various processing units such as a reception processing unit 111, an acquisition processing unit 112, a specific processing unit 113, a search processing unit 114, a presentation processing unit 115, a vehicle allocation processing unit 116, and a notification processing unit 117. include. The control unit 11 functions as the various processing units by executing various types of processing according to the ride-sharing support program by the CPU. Also, part or all of the processing units included in the control unit 11 may be configured by electronic circuits. The ride-sharing support program may be a program for causing a plurality of processors to function as the various processing units.

The acceptance processing unit 111 accepts an application for use of the ride-sharing service from a user. For example, the user activates the application for the ride-sharing service on his/her client terminal 2X and enters an ID and a password on the login screen. The reception processing unit 111 acquires the ID and the password from the client terminal 2X. If the acquired ID and password are registered in the user information DB 122 (see FIG. 2), the reception processing unit 111 authenticates the user and permits the use of the ride-sharing service. Thereby, the user can use the ride-sharing service. For example, the user can perform an operation of inputting search conditions on the client terminal 2X.

The acquisition processing unit 112 acquires the search condition from the client terminal 2X. The search condition includes at least a destination. Also, the search condition may include at least one of a departure date and time and an arrival date and time.

Here, as an example, it is assumed that the departure place, the destination, and the departure date and time are set as the search conditions. For example, as shown in FIG. 6, the user inputs the starting point in the entry field K1 on the operation screen of the client terminal 2X. As the departure point, the current position (current position P0) detected by the client terminal 2X may be input. Also, the user inputs the destination in the input field K2 on the operation screen of the client terminal 2X. Here, hospital H1 is input as the destination. Also, the user inputs the departure date and time in the input field K3 on the operation screen of the client terminal 2X. Here, "13:00" 30 minutes after the current time "12:30" is input as the departure date and time.

The acquisition processing unit 112 acquires the respective search conditions of the departure point, the destination, and the departure date and time entered in the input fields K1 to K3. The search condition may include arrival date and time.

The acquisition processing unit 112 also acquires a request (search request) for route search and driver search (matching) based on the search conditions. In addition, the acquisition processing unit 112 acquires a request (shared inquiry request) as to whether or not to visit the destination (hospital H1) by sharing a shared vehicle with the user. For example, in the operation screen shown in FIG. 6, when the user presses the search button K4, the acquisition processing unit 112 acquires the search request. Get request. Acquisition processing unit 112 is an example of the acquisition processing unit of the present invention.

When the acquisition processing unit 112 acquires the search request (“search button K4” in FIG. 6), the identification processing unit 113 searches (identifies) a driver who satisfies the search conditions set by the user. Specifically, the identification processing unit 113 selects from among the drivers registered in the driver information DB 123 shown in FIG. or a driver who is not incapable of providing the ride-sharing service during the period from the departure date and time to the arrival date and time. Further, the identification processing unit 113 may search for the driver based on the usage history of the user. For example, the identification processing unit 113 selects from among the drivers registered in the driver information DB 123 shown in FIG. Search for drivers who have Further, when the evaluation information of each driver is registered in the driver information DB 123, the identification processing unit 113 may search for a driver whose evaluation value is equal to or higher than the evaluation value desired by the user. In this way, the identification processing unit 113 identifies the passenger vehicle by matching the user and the driver. The specific processing unit 113 is an example of the specific processing unit of the present invention.

The search processing unit 114 searches for a route (recommended route) using the shared vehicle identified by the identification processing unit 113 . For example, when the passenger vehicle of driver A2 is specified by the identification processing unit 113, the search processing unit 114 searches for a route from the departure point to the destination using the passenger vehicle of driver A2. Here, the search processing unit 114 determines a route with the shortest required time from the departure point to the destination, a route with the shortest travel distance from the departure point to the destination, and a route from the departure point to the destination. Search for the best route (recommended route) according to the user's request by a well-known method, such as the route with the lowest fare to the destination, the route with the lowest energy consumption from the departure point to the destination, etc. do.

Further, the search processing unit 114 may search for different routes depending on the passenger vehicle. For example, when the identification processing unit 113 identifies a passenger vehicle of a vehicle type with high high-speed running performance, the search processing unit 114 searches for the route that minimizes the required time. On the other hand, for example, when the identification processing unit 113 identifies a passenger vehicle of a vehicle type with low fuel efficiency, the search processing unit 114 searches for a route that minimizes the energy consumption. In addition, the search processing unit 114 may search for one route for each identified passenger vehicle, or may search for a plurality of routes. Further, the search processing unit 114 may search for a route combining a plurality of passenger vehicles.

The presentation processing unit 115 presents the user with the search result corresponding to the user's search request. Specifically, the presentation processing unit 115 provides the user with search results including information on the driver and the passenger vehicle identified by the identification processing unit 113 and route information on the recommended route searched by the search processing unit 114. presented to For example, the presentation processing unit 115 transmits to the requester terminal 2X display data including information about the shared vehicle, the required time to the destination, and map information representing the route. In addition, the presentation processing unit 115 refers to the driver information DB 123 and transmits information on drivers who can provide the ride-sharing service to the requester terminal 2X. The requester terminal 2X displays information on the route and the passenger vehicle based on the information acquired from the passenger support device 1. FIG. For example, as shown in FIG. 7, the client terminal 2X displays vehicle information D1 corresponding to the shared vehicle identified as the recommended route and map information M1 representing the route R1 corresponding to the recommended route. The vehicle information D1 displays information such as the name and face image of the driver A2 of the passenger vehicle, vehicle information SC2 of the passenger vehicle, and the time required for the passenger vehicle to arrive at the current location P0 of the user A1.

After confirming the search result on the operation screen shown in FIG. 7, the user selects any one of "determine (request for dispatch)", "inquire about ride sharing", and "next candidate". When the user selects "determine (request for vehicle allocation)", the vehicle allocation processing unit 116 acquires the vehicle allocation request from the client terminal 2X and executes vehicle allocation processing.

Also, when the user selects "inquiry about sharing", the acquisition processing unit 112 acquires the inquiry request for sharing from the requester terminal 2X. In this way, the user can make the shared inquiry request on both the search screen shown in FIG. 6 and the search result screen shown in FIG. A process when the acquisition processing unit 112 acquires the ride-sharing inquiry request will be described later.

Also, when the user selects "to the next candidate" (see FIG. 7), the presentation processing unit 115 presents the user with search results corresponding to, for example, the passenger vehicle specified as the second candidate.

The vehicle allocation processing unit 116 outputs a vehicle allocation request to the driver of the vehicle when the user selects the route using the vehicle identified by the identification processing unit 113 . The vehicle allocation processing unit 116 is an example of the vehicle allocation processing unit of the present invention. Specifically, when the route using the shared vehicle of the driver A2 identified by the identification processing unit 113 is selected, the vehicle allocation processing unit 116 outputs a vehicle allocation request to the driver A2 of the shared vehicle. For example, the vehicle allocation processing unit 116 may select a driver who can provide the ride-sharing service at the date and time when the user wishes to use the ride-sharing service, or The dispatch request is output to the driver for whom it is not impossible to provide the The vehicle allocation request includes user information (name, face image, contact information, etc.), request content (departure point, destination, date and time of use, route information, etc.), and an inquiry as to whether or not to permit the vehicle allocation request. Contains information.

FIG. 8 shows a display screen of the dispatch request obtained by the driver terminal 2Y of the driver A2 of the shared vehicle. The map information M3 in FIG. 8 includes the route information and information on the current position (current position P2) of the driver A2 (driver terminal 2Y). In response to the vehicle allocation request shown in FIG. 8, for example, when the driver A2 performs an operation for permitting the vehicle allocation request (selects the "Vehicle allocation permission" button K6), the vehicle allocation processing unit 116 receives the vehicle allocation request from the driver terminal 2Y. and obtains a response permitting the ride-sharing service from the current position (current position P2) of the ride-sharing service to the boarding position (here, the current position (current position P0)) where the user (user A1) who uses the ride-sharing service gets on. Route information is presented to driver A2. As a result, for example, as shown in FIG. 9, the request content and the route R3 from the current position of the shared vehicle (current position P2) to the boarding position of the user A1 (current position P0) are displayed on the driver terminal 2Y. Map information M4 is displayed. FIG. 9 also displays information (“individual”) indicating that there is only one user riding in the shared vehicle.

In response to the vehicle allocation request shown in FIG. 8, when the driver A2 performs an operation of rejecting the vehicle allocation request (selecting the "refuse vehicle allocation" button K7), for example, the identification processing unit 113 , the search processing unit 114 searches for a route using the shared vehicle, and the presentation processing unit 115 presents the search result to the user (see FIG. 7). In this case, the user may select the second candidate passenger vehicle or change the search condition.

On the other hand, when the user presses the ride-sharing inquiry button K5 on the operation screen shown in FIG. 6, the acquisition processing unit 112 acquires the ride-sharing inquiry request. When the acquisition processing unit 112 acquires the search request, the notification processing unit 117 informs the user belonging to the same group as the user whether or not to visit the destination by sharing a shared vehicle with the user. to notify (e.g., e-mail notification) of the shared inquiry. Here, since the user A1 belongs to the hospital group, the notification processing unit 117 notifies the user registered in the hospital group information DB 124 (see FIG. 4) of the shared inquiry. The notification processing unit 117 may notify all users (excluding user A1) registered in the hospital group information DB 124 of the above-mentioned shared inquiry, or may notify related users among the users registered in the hospital group information DB Only users registered as users may be notified of the shared inquiry. For example, when the user A1 and the user A4 have traveled together in the passenger vehicle of the driver A2 and visited the hospital H1 in the past, the notification processing unit 117 to notify the above-mentioned ride-sharing inquiries only. The notification processor 117 is an example of the notification processor of the present invention.

Note that the group is not limited to a group to which a plurality of users belonging to the same destination registered in advance by each user as a visited destination belongs. For example, the groups include a group of residents (users) living in the same area, a group of users with the same hobbies and preferences, a group of users belonging to the same organization (self-governing association, school, circle, club), and a group of users of the same age group. , a group of users by gender. Thus, the group may be a group to which a plurality of users each having the same attribute belongs.

FIG. 10 shows a display screen of the above-mentioned ride-sharing inquiry acquired by the client terminal 2X of the user A4. In response to the ride-sharing inquiry shown in FIG. 10, for example, when the user A4 agrees to visit the destination (hospital H1) by sharing a ride-sharing vehicle with the user A1, the user A4 selects "Request to ride together". Select button K8. When the user A4 selects the button K8 of "request for sharing", the acquisition processing unit 112 acquires the request for sharing from the client terminal 2X of the user A4. On the other hand, when the user A4 does not agree to visit the destination (hospital H1) by sharing a shared vehicle with the user A1, the user A4 selects the button K9 of "do not request sharing".

When the acquisition processing unit 112 acquires the ride-sharing request from the client terminal 2X of the user A4, the identification processing unit 113 identifies the driver who satisfies the search conditions set by the user A1. Specifically, the identification processing unit 113 identifies a passenger vehicle by searching for a driver who satisfies the search conditions from among the drivers registered in the driver information DB 123 shown in FIG. Here, the identification processing unit 113 identifies drivers corresponding to the users A1 and A4. For example, the identification processing unit 113 selects, from among the drivers registered in the driver information DB 123, drivers who can provide the ride-sharing service during the period, and who have both the user A1 and the user A4 in the past. Identify drivers who have used it. Further, the identification processing unit 113 may identify the driver based on an evaluation value obtained by evaluating the driver when each of the user A1 and the user A4 used the vehicle in the past. In this way, the identification processing unit 113 identifies the passenger vehicle by matching the requester, passenger, and driver. Here, it is assumed that the identification processing unit 113 has identified the driver A5 who has been used by both the user A1 and the user A4 in the past.

When the identification processing unit 113 identifies (matches) the driver and the shared vehicle in response to the ride-sharing inquiry from the user A1 and the ride-sharing request from the user A4, the search processing unit 114 searches for the shared vehicle identified by the identification processing unit 113. (recommended route), and the presentation processing unit 115 presents route information (search results) related to the route searched by the search processing unit 114 to the user (user A1). As shown in FIG. 11, the client terminal 2X of the user A1 displays the vehicle information D1 corresponding to the shared vehicle specified as the recommended route. The vehicle information D1 includes route information of the route connecting the current location P0 of the user A1, the current location P1 of the user A4, and the hospital H1, the name and face image of the driver A5 of the passenger vehicle, vehicle information SC5 of the passenger vehicle, Information such as the time required for the vehicle to arrive at the current location P0 is displayed.

When the user A1 confirms the search results on the operation screen shown in FIG. 11, he selects either "determine (dispatch request)" or "next candidate". When the user A1 selects "determine (request dispatch)", the dispatch processing unit 116 outputs the dispatch request to the driver A5 of the shared vehicle. In addition, the dispatch processing unit 116 outputs to the driver A5 identified by the identification processing unit 113 information on the positions where the users A1 and A4 board the shared vehicle. In addition, the dispatch processing unit 116 provides the driver A5 with information on the route connecting the position of the driver A5, the positions where the users A1 and A4 each board the passenger vehicle, and the destination (hospital H1). to output

FIG. 12 shows a display screen of the dispatch request obtained by the driver terminal 2Y of the driver A5 of the passenger vehicle. The dispatch request includes information on users A1 and A4 (names, facial images, e-mail addresses, etc.), request details (departure point (current location P0), destination (hospital H1), date and time of departure (13:00 today) ), route information, etc.), and information such as an inquiry as to whether or not to permit the dispatch request. The map information M3 includes information on the current location P0 of the user A1, the current location P1 of the user A4, the current location (current location P2) of the driver A5 (driver terminal 2Y), and the route information. In response to the vehicle allocation request shown in FIG. 12, for example, when the driver A5 performs an operation for permitting the vehicle allocation request (selects the "Vehicle allocation permission" button K6), the vehicle allocation processing unit 116 receives the vehicle allocation request from the driver terminal 2Y. and the route from the current position of the shared vehicle (current location P2) to the boarding position (current location P0) where user A1 who uses the shared service gets on, and where user A4 rides from current location P0. Route information relating to the route to the boarding position (current position P1) is presented to the driver A2. As a result, for example, as shown in FIG. 13, the request content and the map information M4 representing the route R3 corresponding to the route information are displayed on the driver terminal 2Y. FIG. 13 also displays information (“riding together”) indicating that there are multiple users riding in the shared vehicle.

In addition, the vehicle allocation processing unit 116 notifies the vehicle allocation establishment information to the requester terminal 2X and the driver terminal 2Y of the user A1 and the user A4, respectively. For example, the vehicle allocation processing unit 116 notifies the requester terminal 2X of the user A1 of information indicating that the vehicle allocation request is permitted and information including the estimated arrival time of the passenger vehicle (for example, countdown display).

In addition to the above-described processes, the control unit 11 also controls the usage history of the ride-sharing service of the user (client) (request history of the ride-sharing vehicle), the provision history of the ride-sharing service of the user (driver), and the like. History information may be stored in the storage unit 12 . Further, the control unit 11 may acquire an evaluation of the ride-sharing service (such as an evaluation of the driver) from a user (requester) who used the ride-sharing service, and store the evaluation in the storage unit 12 . In addition, the control unit 11 may include evaluation information such as the driver's evaluation status and ranking in the dispatch request based on the evaluation.

[User terminal 2]
As shown in FIG. 1, the user terminal 2 (client terminal 2X, driver terminal 2Y) includes a control unit 21, a storage unit 22, an operation display unit 23, a communication I/F 24, a GPS receiving unit 25 (GPS: Global Positioning System (registered trademark), etc. The client terminal 2X is a mobile terminal possessed by a user who uses the ride-sharing service, and is an information processing device such as a smart phone, a mobile phone, or a tablet terminal. Similarly, the driver terminal 2Y is a mobile terminal possessed by the user who is the driver, and is an information processing device such as a smart phone, a mobile phone, or a tablet terminal. The driver terminal 2Y may be an in-vehicle device mounted in a passenger vehicle. Hereinafter, when describing functions common to the client terminal 2X and the driver terminal 2Y, they are referred to as the user terminal 2. FIG.

The GPS receiving unit 25 receives signals (GPS signals) transmitted from a plurality of GPS satellites (not shown) via an antenna (not shown), and generates positioning data (latitude, , longitude, altitude) and current time.

The communication I/F 24 connects the user terminal 2 to the communication network N1 by wire or wirelessly, and performs data communication according to a predetermined communication protocol with an external device such as the ride-sharing support device 1 via the communication network N1. It is a communication interface for execution.

The operation display unit 23 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays various information, and an operation unit such as a mouse, keyboard, or touch panel that receives operations.

The storage unit 22 is a nonvolatile storage unit such as a flash memory that stores various information. For example, the storage unit 22 stores various control programs. The control program is non-temporarily recorded in a computer-readable recording medium such as a USB, CD, or DVD (both registered trademarks), and is electrically connected to the user terminal 2 in a USB drive, CD drive, or It is read by a reader (not shown) such as a DVD drive and stored in the storage unit 22 . The control program may be downloaded from an external device via the communication network N1 and stored in the storage unit 22 .

The control unit 21 has control devices such as a CPU, ROM, and RAM. The CPU is a processor that executes various kinds of arithmetic processing. The ROM is a non-volatile storage unit in which control programs such as BIOS and OS for causing the CPU to execute various processes are stored in advance. The RAM is a volatile or nonvolatile storage unit that stores various information, and is used as a temporary storage memory (work area) for various processes executed by the CPU. The control unit 21 controls the user terminal 2 by causing the CPU to execute various control programs pre-stored in the ROM or storage unit 22 .

Specifically, the control unit 21 includes various processing units such as a reception processing unit 211, a position detection processing unit 212, a display processing unit 213, and the like. The control unit 21 functions as the various processing units by executing various types of processing according to the control program by the CPU. Also, part or all of the processing units included in the control unit 21 may be configured by electronic circuits. The control program may be a program for causing a plurality of processors to function as the various processing units.

The reception processing unit 211 acquires operation information that the user has operated on the operation display unit 23 of the user terminal 2 . For example, the user activates the application for the ride-sharing service on his/her client terminal 2X and enters an ID and a password on the login screen. The reception processing unit 211 of the client terminal 2X acquires the ID and the password and transmits them to the ride-sharing support device 1 . Further, the reception processing unit 211 of the client terminal 2X receives various operations from the user on the operation screen (see FIGS. 7, 10, and 11) displayed on the client terminal 2X. Further, the reception processing unit 211 of the driver terminal 2Y receives various operations from the driver on the operation screen (see FIGS. 8, 9, 12 and 13) displayed on the driver terminal 2Y.

The position detection processor 212 detects the current position of the user based on the positioning data detected by the GPS receiver 25 . For example, the position detection processing units 212 of the client terminals 2X of the users A1 and A4 detect their respective current positions (current positions P0 and P1), and use the position information including the current position and the current time to Send to device 1. Further, for example, the position detection processing unit 212 of the driver terminal 2Y of the driver A5 detects the current position (current position P2) of the driver or the passenger vehicle, and sends the position information including the current position and the current time to the passenger assistance device 1. Send.

The display processing unit 213 causes the operation display unit 23 to display various kinds of information. For example, when the display processing unit 213 of the requester terminal 2X of the user A1 receives the display data corresponding to the search result from the ride-sharing support device 1, the route information (see FIGS. 7 and 11) is displayed on the operation display unit 23. to display. Further, for example, when the display processing unit 213 of the requester terminal 2X of the user A4 receives the ride-sharing inquiry (e-mail reception) from the ride-sharing support device 1, it causes the operation display unit 23 to display the ride-sharing inquiry information (see FIG. 10). Further, for example, when the display processing unit 213 of the driver terminal 2Y of the driver A5 receives the vehicle allocation request from the passenger support device 1, the display processing unit 213 displays the vehicle allocation request on the operation display unit 23 (FIGS. 8, 9, and 12). , see FIG. 13). Further, the display processing unit 213 causes the operation display unit 23 to display a route guidance screen (navigation screen) when the route guidance information is acquired from the ride-sharing support device 1 .

[Ride-on support processing]
Hereinafter, the boarding assistance process executed by the control unit 11 of the boarding assistance device 1 will be described with reference to FIG. 14 . The control unit 11 starts executing the ride-sharing support program in response to a user's operation, for example, an operation of inputting the ID and the password on the login screen of the ride-sharing service application displayed on the client terminal 2X. , the execution of the ride-sharing support process is started. In addition, the control unit 11 can concurrently execute the ride-sharing support process corresponding to each client terminal 2X in response to access from each client terminal 2X. Note that the ride-sharing support process may be ended in the middle according to a predetermined operation on the requester terminal 2X.

The present invention can be regarded as an invention of a method of assisting in boarding which executes one or more steps included in the process of assisting in boarding.

Also, one or a plurality of steps included in the ride-sharing support process described here may be omitted as appropriate. Further, each step in the ride-sharing support process may have a different execution order as long as the same action and effect are produced. Furthermore, here, a case where the control unit 11 executes each step in the ride-sharing support process will be described as an example, but in another embodiment, a plurality of processors perform the steps in the ride-sharing support process in a distributed manner. You may Here, the ride-sharing support process will be described with reference to the above example.

First, in step S11, the control unit 11 determines whether or not an application for use of the shared ride service has been received from the user. For example, when the control unit 11 acquires and authenticates the ID and the password from the client terminal 2X of the user A1, it determines that the application for use has been accepted. The control unit 11 waits until a usage application is accepted.

Next, in step S12, the control unit 11 acquires search conditions from the client terminal 2X. For example, when the user A1 inputs search conditions on the search screen (see FIG. 6) of the client terminal 2X, the control unit 11 inputs the search conditions from the client terminal 2X to the departure point (current location P0), destination ( Hospital H1) and the date and time of departure (13:00 today) are acquired. Step S12 is an example of the acquisition step of the present invention.

Next, in step S13, the control unit 11 determines whether or not a search request has been received from the user A1. Specifically, when the user A1 presses the search button K4 after entering the search conditions on the search screen (see FIG. 6) of the client terminal 2X, the control unit 11 acquires the search request. For example, if the user A1 wants to visit the destination (hospital H1) by himself, that is, if he does not want to visit the destination with other users, he presses the search button K4. When the control unit 11 acquires the search request from the user A1 (S13: Yes), the process proceeds to step S14. On the other hand, when the control unit 11 does not acquire the search request from the user A1 (S13: No), the process proceeds to step S31.

In step S31, the control unit 11 acquires from the user A1 an inquiry request (share inquiry request) as to whether or not to visit the destination (hospital H1) by sharing a shared vehicle with the user A1. determine whether or not Specifically, when the user A1 presses the shared inquiry button K5 after inputting the search conditions on the search screen (see FIG. 6) of the client terminal 2X, the control unit 11 acquires the shared inquiry request. . For example, if the user A1 wants to visit the destination (hospital H1) together with other users, or if it is acceptable to visit the destination (hospital H1) together with other users, the user A1 presses the shared inquiry button K5. Press When the control unit 11 acquires the ride-sharing inquiry request, the process proceeds to step S32. On the other hand, if the control unit 11 does not acquire a ride-sharing inquiry request (S31: No), the process returns to step S12, and the control unit 11 acquires the search conditions changed by the user A1, for example. Processing after step S32 will be described later.

In step S14, the control unit 11 identifies (matches) a driver who satisfies the search condition set by the user A1. Specifically, the control unit 11 selects drivers registered in the driver information DB 123 (see FIG. 3) for a period from the departure date and time to the arrival date and time, and selects a driver who can provide the ride-sharing service. or a driver who is not incapable of providing the ride-sharing service during the period from the departure date and time to the arrival date and time. Further, the control unit 11 may search for a driver corresponding to the usage history of the user, a driver whose evaluation value is equal to or higher than that desired by the user, and the like. The control unit 11 identifies the driver and the passenger vehicle. Step S14 is an example of a specific step of the present invention.

Next, in step S15, the control unit 11 searches for a route (recommended route) using the identified passenger vehicle. For example, when the shared vehicle of driver A2 is identified, the control unit 11 searches for a route from the departure point (current location P0) to the destination (hospital H1) using the shared vehicle. The control unit 11 searches for the optimum route (recommended route) according to information such as the user's request (required time, traveling fee, energy consumption, etc.) and the vehicle type of the passenger vehicle.

Next, in step S16, the control unit 11 presents the user A1 with the search results in response to the user A1's search request. Specifically, the control unit 11 presents the requester terminal 2X of the user A1 with search results including information about the specified driver A2 and the passenger vehicle, and route information of the recommended route searched for. For example, as shown in FIG. 7, the client terminal 2X displays vehicle information D1 corresponding to the shared vehicle identified as the recommended route and map information M1 representing the route R1 corresponding to the recommended route. The vehicle information D1 displays information such as the name and face image of the driver A2 of the passenger vehicle, vehicle information SC2 of the passenger vehicle, and the time required for the passenger vehicle to arrive at the current location P0.

Next, in step S17, the control unit 11 determines whether or not a dispatch request has been received from the user A1. Specifically, when the user A1 selects "determine (request for dispatch)" on the operation screen shown in FIG. 7, the control unit 11 acquires the request for dispatch. The user A1 can also select "to the next candidate" and select "determine (request dispatch)" for other routes and shared vehicles. When the control unit 11 acquires the dispatch request (S17: Yes), the process proceeds to step S18. When the control unit 11 does not acquire the dispatch request (S17: No), the process proceeds to step S171.

In step S171, as in step S31, the control unit 11 requests a shared inquiry from the user A1 as to whether or not to visit the destination (hospital H1) by sharing a shared vehicle with the user A1. It is determined whether or not (ride-sharing inquiry request) has been acquired. Specifically, when the user A1 presses the "joint inquiry" button on the search result screen (see FIG. 7) of the client terminal 2X, the control section 11 acquires the said join inquiry request. In this way, the user A1 can make the ride-sharing inquiry request even after the driver is identified. When the control unit 11 acquires the ride-sharing inquiry request, the process proceeds to step S32. When the control unit 11 does not acquire the ride-sharing inquiry request (S171: No), the process returns to step S12, and the control unit 11 acquires the search condition changed by the user A1, for example.

In step S18, the control unit 11 outputs a dispatch request to the driver of the passenger vehicle corresponding to the recommended route selected by the user A1. Here, the control unit 11 outputs the dispatch request to the driver terminal 2Y of the driver A2 of the passenger vehicle. As a result, the dispatch request screen is displayed on the driver terminal 2Y (see FIG. 8). The dispatch request includes user A1 information (name, face image, email address, etc.), request content (departure point (current location P0), destination (hospital H1), departure date and time (13:00), route information, etc.). ), and information such as an inquiry as to whether or not to permit the dispatch request.

Next, in step S19, the control unit 11 determines whether or not the vehicle allocation request is permitted. For example, in response to the vehicle allocation request shown in FIG. 8, when the driver A2 performs an operation for permitting the vehicle allocation request (selects the "Permit vehicle allocation" button K6), the control unit 11 determines that the vehicle allocation request is permitted. (S19: Yes), the process proceeds to step S20. On the other hand, in response to the vehicle allocation request shown in FIG. 8, when the driver A2 performs an operation to reject the vehicle allocation request (selects the "reject vehicle allocation" button K7), the control unit 11 determines that the vehicle allocation request has been rejected. (S19: No), and the process proceeds to step S12.

In step S20, the control unit 11 notifies the requester terminal 2X and the driver terminal 2Y of the dispatch establishment information. For example, the control unit 11 notifies the requester terminal 2X of the user A1 of information indicating that the dispatch request is permitted and information including the scheduled arrival time of the passenger vehicle (for example, countdown display). Further, the control unit 11 notifies the driver terminal 2Y of the driver A2 of the route information (see FIG. 9) regarding the route from the current position of the passenger vehicle (current position P2) to the current position of the user A1 (current position P0). . Steps S18 to S20 are an example of the dispatching steps of the present invention.

On the other hand, when the control unit 11 acquires from the user A1 a shared inquiry request as to whether or not to visit the hospital H1 by sharing a shared vehicle with the user A1 (S31: Yes or S171: Yes ), in step S32, the control unit 11 asks the user belonging to the same group (hospital group in this case) as the user A1 whether or not to visit the hospital H1 by sharing a shared vehicle with the user A1. Notify of shared inquiries. For example, the control unit 11 notifies the user A4, who is registered as a related user among the users registered in the hospital group information DB 124 (see FIG. 4), of the shared inquiry. Step S32 is an example of the notification step of the present invention.

FIG. 10 shows a display screen of the above-mentioned ride-sharing inquiry acquired from the ride-sharing support device 1 by the client terminal 2X of the user A4. The display screen of FIG. 10 displays the ride-sharing inquiry information D2. In response to the ride-sharing inquiry shown in FIG. 10, for example, when the user A4 agrees to visit the destination (hospital H1) by sharing a ride-sharing vehicle with the user A1, the user A4 selects "Request to ride together". Select button K8. If the user A4 does not agree to visit the destination (hospital H1) by sharing a shared vehicle with the user A1, the user A4 selects the button K9 of "do not request sharing". The control unit 11 acquires a response to the notification of the ride-sharing inquiry (“Request ride-sharing” or “Do not request ride-sharing”).

In step S33, the control unit 11 determines whether or not a request for sharing (“request for sharing”) has been obtained from the user A4. When the control unit 11 acquires the ride-sharing request from the user A4 (S33: Yes), the process proceeds to step S34. When the control unit 11 does not acquire the ride-sharing request from the user A4 (S33: No), the process returns to step S12.

In step S34, the control unit 11 identifies (matches) a driver who satisfies the search condition set by the user A1. For example, the control unit 11 selects drivers registered in the driver information DB 123 who are capable of providing the ride-sharing service during the period of the search condition, and who have previously been the user A1 and the user A1. A4 searches for drivers who have used it together. In this way, the control unit 11 matches the requester, the passenger, and the driver to identify the passenger vehicle. Here, it is assumed that the control unit 11 has specified the driver A5 who has been used by both the user A1 and the user A4 in the past. Step S34 is an example of a specific step of the present invention.

Next, in step S35, the control unit 11 searches for a route (recommended route) using the specified passenger vehicle. For example, when the control unit 11 identifies the passenger vehicle of the driver A5, the passenger vehicle is used from the departure point (current location P0) to the destination (hospital H1) via the current location P1 of the user A4. Search the route of the case. The control unit 11 searches for the optimum route (recommended route) according to information such as the user's request (required time, traveling fee, energy consumption, etc.) and the vehicle type of the passenger vehicle.

Next, in step S36, the control unit 11 presents the user A1 with the search results in response to the user A1's search request. Specifically, the control unit 11 presents route information (search results) regarding the searched route to the user (user A1). As shown in FIG. 11, the client terminal 2X displays vehicle information D1 corresponding to the shared vehicle identified as the recommended route. The vehicle information D1 includes route information of the route connecting the current location P0 of the user A1, the current location P1 of the user A4, and the hospital H1, the name and face image of the driver A5 of the passenger vehicle, vehicle information SC5 of the passenger vehicle, Information such as the time required for the vehicle to arrive at the current location P0 is displayed.

Next, in step S37, the control unit 11 outputs a dispatch request to the driver of the passenger vehicle corresponding to the recommended route selected by the user A1. Here, the control unit 11 outputs the dispatch request to the driver terminal 2Y of the driver A5 of the passenger vehicle. As a result, the dispatch request screen is displayed on the driver terminal 2Y (see FIG. 12). The dispatch request includes information (name, face image, email address, etc.) of each of the users A1 and A4, request contents (departure point (current location P0), destination (hospital H1), departure date and time (13:00 ), route information, etc.), and information such as an inquiry as to whether or not to permit the dispatch request. The map information M3 of FIG. 12 includes information on the current location P0 of the user A1, the current location P1 of the user A4, the current location (current location P2) of the driver A5 (driver terminal 2Y), and the route information. be

Next, in step S38, the control unit 11 determines whether or not the vehicle allocation request is permitted. For example, in response to the vehicle allocation request shown in FIG. 12, when the driver A5 performs an operation for permitting the vehicle allocation request (selects the "Permit vehicle allocation" button K6), the control unit 11 determines that the vehicle allocation request is permitted. (S38: Yes), the process proceeds to step S20. On the other hand, in response to the vehicle allocation request shown in FIG. 12, when the driver A2 performs an operation to reject the vehicle allocation request (selects the "reject vehicle allocation" button K7), the control unit 11 determines that the vehicle allocation request has been rejected. (S38: No), and the process proceeds to step S12. Steps S37 and S38 are an example of the dispatch step of the present invention.

In step S20, the control unit 11 notifies the requester terminal 2X and the driver terminal 2Y of the dispatch establishment information. For example, the control unit 11 notifies the requester terminals 2X of the users A1 and A4 of information indicating that the dispatch request is permitted and information including the estimated arrival time of the passenger vehicle (for example, countdown display). do. In addition, the control unit 11 transmits to the driver terminal 2Y of the driver A5 a route from the current position of the passenger vehicle (current position P2) to the current position of the user A1 (current position P0) and the current position of the user A4 (current position P1). , and notifies the route information (see FIG. 13).

The control unit 11 of the boarding support device 1 executes the boarding support process as described above. The control unit 11 executes the ride-sharing support process each time an application for the ride-sharing service is received from a user.

As described above, the ride-sharing support system 100 according to the embodiment of the present invention acquires the information of the first destination from the first user who uses the ride-sharing vehicle, and the first user belongs to the same group as the first user. The second user is notified of an inquiry as to whether or not to visit the first destination by sharing a shared vehicle with the first user. In addition, the ride-sharing support system 100 identifies the driver of the ride-sharing vehicle and outputs a dispatch request to the identified driver. Specifically, the ride-sharing support system 100 provides a driver corresponding to the first user and the second user, for example, a driver who has been used by the first user and the second user in the past. Identify (match)

According to the above configuration, a plurality of users can ride together (ride together) and transport the vehicle to the destination, so that the utilization efficiency of the ride-sharing service can be improved. In addition, since a plurality of users belonging to the same group can ride together, each user can use the ride-sharing service with peace of mind. For example, if the group is a group of users who share the same destination, or a group of users who have close ties, users with the same purpose, hobbies, tastes, and personalities (values) can ride together in the same vehicle. , each user can use the ride-sharing service with peace of mind. Therefore, it becomes possible to improve the convenience of the user who uses the ride-sharing service.

The ride-sharing support system 100 of the present invention is not limited to the above-described embodiment, and may be the embodiment shown below.

In the above-described embodiment, the ride-sharing support system 100, when the user A4 makes a ride-sharing request (see FIG. 10) in response to the user A1's ride-sharing inquiry request ("ride-sharing inquiry" in FIG. 6), Identify (match) the driver. As another embodiment, the ride-sharing support system 100 identifies (matches) a driver corresponding to the user A1 when the user A1 makes a search request ("search" in FIG. 6), and then A ride-sharing inquiry request may be accepted. Then, when the ride-sharing support system 100 acquires the ride-sharing inquiry request from the user A1, the ride-sharing support system 100 notifies the users belonging to the same group as the user A1 of the ride-sharing inquiry. In this case, for example, the user who has obtained the ride-sharing inquiry determines whether or not to make a ride-sharing request based on information such as who the user is and who the driver is. In this manner, the driver matching process may be performed after the users who will participate in the ride-sharing are determined, or immediately after the user A1 makes a search request.

As another embodiment of the present invention, the ride-sharing support system 100 searches for a plurality of candidates for the driver of the ride-sharing vehicle when the user A4 makes a ride-sharing request in response to the request for a ride-sharing inquiry from the user A1. good. When there are a plurality of driver candidates, the ride-sharing support system 100 displays the selection screen shown in FIG. 15 on the requester terminals 2X of the users A1 and A4. When the drivers selected by the user A1 and the user A4 are the same, the ride-sharing support system 100 determines the driver to be requested to dispatch the vehicle.

In addition, the ride-sharing support system 100 may identify the optimum driver from among a plurality of driver candidates based on information such as usage histories of the users A1 and A4 and evaluations of the drivers. good.

In addition, in the ride-sharing support system 100 of the present invention, the means for transporting the user may include not only a ride-sharing vehicle but also other moving means (taxi, bus, railroad, etc.). In this case, the ride-sharing support system 100 may display the search results (in order of required time and in order of fare) including searched routes by other means of transportation in the search results (see FIG. 7).

As another embodiment of the present invention, the control unit 21 of the user terminal 2 may include one or a plurality of processing units included in the control unit 11 of the ride-sharing support device 1 . Further, each information stored in the storage unit 22 may be acquired from an external device. The control unit 21 may download the boarding support program to the storage unit 22 via the Internet and execute the boarding support process, or may execute the boarding support program stored in an external server. You may perform the said boarding support process by. The ride-sharing support system of the present invention may be composed of the ride-sharing support device 1, may be composed of the user terminal 2, or may be composed of the ride-sharing support device 1 and the user terminal 2.

1: Ride-on support device 2: User terminal 2X: Client terminal 2Y: Driver terminal 100: Ride-on support system 111: Reception processing unit 112: Acquisition processing unit 113: Specific processing unit 114: Search processing unit 115: Presentation processing unit 116: dispatch processing unit 117: notification processing unit 121: map information database 122: user information database 123: driver information database 124: hospital group information database 125: city hall group information database 211: reception processing unit 212: position detection processing unit 213: display processing unit

Claims (14)

an acquisition processing unit that acquires information on a first destination from a first user who uses a specific vehicle;
Notification processing for notifying a second user belonging to the same group as the first user of an inquiry as to whether or not to visit the first destination by sharing the specific vehicle with the first user. Department and
a specific processing unit that identifies a driver of the specific vehicle;
a vehicle allocation processing unit that outputs a vehicle allocation request to the driver identified by the identification processing unit;
A ride-sharing support system. When the second user answers that he/she will visit the first destination by sharing the specific vehicle with the first user, the specific processing unit determines whether the first user and the second use identifying the driver corresponding to the person;
The boarding support system according to claim 1. The identification processing unit identifies the driver that each of the first user and the second user has used in the past.
The boarding support system according to claim 2. The identification processing unit identifies the driver based on an evaluation value obtained by evaluating the driver when each of the first user and the second user has used the vehicle in the past.
The boarding support system according to claim 2. Date and time information indicating the date and time when the driver can provide the service of transporting the user is registered in advance,
The identification processing unit further identifies the driver who can provide the service at the date and time desired by the first user.
A boarding support system according to any one of claims 2 to 4. The group is a group to which a plurality of users belonging to the same destination registered in advance as a visit destination by each user belongs,
The notification processing unit notifies the inquiry to the second user who has registered the same destination as the destination registered by the first user,
A boarding assistance system according to any one of claims 1 to 5. The group is a group to which a plurality of users each having the same usage history of the specific vehicle belongs,
The notification processing unit notifies the second user of the same usage history as the first user of the inquiry.
A boarding assistance system according to any one of claims 1 to 5. The group is a group to which a plurality of users each having the same attribute belongs,
The notification processing unit notifies the second user of the same attribute as the first user of the inquiry.
A boarding assistance system according to any one of claims 1 to 5. The dispatch processing unit outputs to the driver identified by the identification processing unit information on positions at which the first user and the second user board the specific vehicle.
A boarding support system according to any one of claims 1 to 8. The vehicle allocation processing unit provides the driver identified by the identification processing unit with the position of the driver, the positions at which the first user and the second user board the specific vehicle, and the Output information on the route connecting the first destination,
The boarding support system according to claim 9. To provide information on a plurality of users who can use a ride-sharing service for transportation to a destination by riding in a specific vehicle, and to provide the ride-sharing service to other users as the driver among the plurality of users. information of one or more qualified users is registered in advance,
A boarding support system according to any one of claims 1 to 10. The specific vehicle is a private vehicle owned by the user,
A boarding support system according to any one of claims 1 to 11. one or more processors
an acquisition step of acquiring information on the first destination from the first user who uses the specific vehicle;
A notification step of notifying a second user belonging to the same group as the first user of an inquiry as to whether or not to visit the first destination by sharing the specific vehicle with the first user. When,
an identifying step of identifying a driver of the specific vehicle;
a vehicle allocation step of outputting a vehicle allocation request to the driver identified by the identification step;
A shared assistance method to carry out. an acquisition step of acquiring information on the first destination from the first user who uses the specific vehicle;
A notification step of notifying a second user belonging to the same group as the first user of an inquiry as to whether or not to visit the first destination by sharing the specific vehicle with the first user. When,
an identifying step of identifying a driver of the specific vehicle;
a vehicle allocation step of outputting a vehicle allocation request to the driver identified by the identification step;
A ride-sharing support program for causing one or more processors to execute

Images