JP7178934B2 - Ride share management device - Google Patents

Description

The present invention relates to a rideshare management device.

By matching passengers (riders) to the route to the destination of the driver (driver) who drives the vehicle and reducing the number of vehicles on the road, it is a social issue of reducing traffic congestion and reducing _CO2 emissions. A mechanism called ride sharing that tackles this problem is spreading. For example, Patent Literature 1 describes a technique in which a server called an intermediary host transmits meeting times and places that match the desires of the driver and passengers to the terminals of the driver and passengers.

This Patent Document 1 also describes a technique for comparing the number of points desired by the driver and the number of points desired by the rider with an intermediary host.

Japanese Patent Application Laid-Open No. 2002-140399

However, the conventional ride-sharing technology has the problem that it imposes an excessive burden on the driver, making it difficult for the driver to participate. For example, passengers can get on and off at a time and place close to their wishes, but the driver cannot leave the vehicle at an arbitrary place. Therefore, when commuting from home to a destination as a driver, it is necessary to ride-share from the destination to home as a driver. If the participation of drivers is small, an excessive number of passengers will gather for one driver, and the supply and demand balance will collapse, resulting in the impediment of the popularization of ride sharing.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a ride-sharing management device that can motivate a driver to register as a driver of a ride-sharing service by improving convenience when the driver abandons the ride-sharing vehicle.

(1) The present invention includes a map storage unit (for example, a map storage unit 121 described later) that stores information indicating a map, a departure point as driver information of a ride-sharing vehicle used for a ride-sharing service, a driver information acquisition unit (for example, a driver information acquisition unit 111 described later) that acquires a first destination that is the destination of the rideshare vehicle and a second destination that is the destination of the driver; A driver candidate storage unit (for example, a driver candidate storage unit 123 to be described later) that stores a plurality of driver candidates who can drive the ride-sharing vehicle; and a movement plan proposal unit (for example, a movement plan proposal unit 113 to be described later) that proposes information on boarding and alighting points, and the movement plan proposal unit proposes the first destination and the second destination of the driver. is different, ride-sharing management for determining substitute driver candidates who can drive the ride-sharing vehicle from the first destination to the second destination based on the candidates stored in the driver candidate storage unit. The present invention relates to a device (for example, a rideshare management device 10 described later).

According to the ride-sharing management device described in (1) above, even if the driver wishes to drop off the ride-sharing vehicle on the way (first destination), the ride-sharing vehicle is moved to the second destination. You can use the ride-sharing service on the premise that you will drop off your car because you can find the other person. The improved convenience will motivate users to register as drivers, making it easier to secure drivers for ride-sharing services.

The movement plan proposing unit notifies the passenger candidate and the boarding/alighting point as well as points to be given to the driver, and notifies the driver of usage points consumed based on the use of the substitute driver candidate. processing may be performed.

According to the ride-sharing management device described in (2) above, the points set for the driver can be used to drop-off the ride-sharing vehicle. becomes easier.

(3) In the ride-sharing management device described in (1) or (2), a ride-sharing history storage unit (for example, a later-described ride A share history storage unit 122) is further provided, and when the first destination and the second destination of the driver are different, the travel plan proposal unit stores the operation history and the boarding history stored in the ride share history storage unit. creating information indicating the possibility of traveling as a passenger from the first destination to the second destination based on at least one of the histories, and calculating points to be used when becoming the passenger; good too.

According to the ride-sharing management device described in (3) above, since it is possible to confirm the possibility of traveling as a passenger to the second destination, it is possible to use the ride-sharing service on the assumption that the vehicle will be dropped off. In addition, since the driver's points can be used when participating in the ride-sharing service as a passenger, convenience is further improved.

According to the ride-sharing management device of the present invention, it is possible to motivate the driver to register as a driver of the ride-sharing service by improving convenience when dropping off the ride-sharing vehicle.

1 is a diagram showing a configuration example of a rideshare system including a rideshare management device according to an embodiment of the present invention; FIG. FIG. 2 is a functional block diagram showing device configurations of a ride share management device and a driver's user terminal according to the present embodiment; It is a functional block diagram showing the device configuration of the ride share management device of the present embodiment and the user terminal of a passenger. It is a block diagram which shows the structural example of the point setting part of this embodiment. It is a figure which shows the example of the content of the movement plan of this embodiment. It is a flow which shows the movement plan creation process of this embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration example of a ride-sharing system 1 including a ride-sharing management device 10 according to one embodiment of the present invention.

The ride-sharing system 1 provides a user with a ride-sharing service that supports sharing of vehicles for traveling to a specific location (eg, work place) during a predetermined time period (eg, commuting time). In this embodiment, a user 2 is a member belonging to a specific organization (for example, a company or a government office), and a ride-sharing vehicle 3 is a shared vehicle owned by the organization or a provided vehicle that the user agrees to use for sharing. An example is given.

<Overall configuration of ride-sharing system>
In the ride-sharing system 1 , a plurality of user terminals 20 and a plurality of in-vehicle terminals 30 are connected to a ride-sharing management device 10 via a network 5 . The network 5 is realized by, for example, the Internet, a mobile phone network, a LAN (Local Area Network), or a combination of these, and there is no particular limitation on its communication method or the like.

The ride-sharing management device 10 communicates with the user terminal 20 used by the user 2 and the vehicle-mounted terminal 30 mounted on the ride-sharing vehicle 3, and performs information processing for transmitting various information related to ride-sharing to the user terminal 20 and the vehicle-mounted terminal 30. It is a device. Various types of information are, for example, the optimum combination of users 2 who ride together, the optimum vehicle, and the optimum travel based on desired ride-sharing conditions desired by each user 2, such as departure place, arrival place, departure time, and arrival time. It is information such as a route (for example, a route that can most alleviate traffic congestion).

The user terminal 20 is an information processing device used by the user 2 who receives the ride-sharing service. The user terminal 20 is configured by a computer such as a smart phone, tablet PC, mobile phone, PDA, or the like.

The in-vehicle terminal 30 is an information processing device that provides various types of information to the user 2 boarding the ride-sharing vehicle 3 . The in-vehicle terminal 30 is configured by, for example, a car navigation device, a PND (Portable Navigation Device) installed on a vehicle dashboard or the like, and a computer such as a tablet PC. In this embodiment, the ride-sharing vehicle 3 is a vehicle owned by a specific organization, a vehicle owned by a registered user 2, or the like.

Functional blocks of the user terminal 20 and the rideshare management device 10 will be described with reference to the block diagrams of FIGS. 2 and 3. FIG. In the following description, among the users 2, the one who drives the ride-sharing vehicle 3 is called the driver 2a, and the one who does not drive but rides together is called the passenger 2b. Note that the roles of the driver 2a and the passenger 2b are not fixed, and the user sometimes selects to use them as the driver 2a or the passenger 2b. A user who uses the ride-sharing service as the driver 2a may become the passenger 2b, and vice versa.

<Functional blocks provided by the user terminal>
As shown in FIGS. 2 and 3, the user terminal 20 includes a control unit 21 made up of an arithmetic processing unit such as a microprocessor, a storage unit 22 made up of a semiconductor memory or the like, and a touch panel display or the like. It includes an interface section 23 having an input section and a display section, and a communication section 24 having a DSP and the like. Dedicated application software for using the ride-sharing service is installed in the user terminal 20 , and communicates with the ride-sharing management device 10 via the communication unit 24 .

The user terminal 20 operated by the driver 2a when using the rideshare service is referred to as a user terminal 20a, and the user terminal 20 operated by the passenger 2b when using the rideshare service is referred to as a user terminal 20b. When the user uses the ride-sharing service as the driver 2a, the user terminal 20a is used to transmit the driver information 200 (see FIG. 2). Also, when the user uses the ride-sharing service as a passenger 2b, the user terminal 20b is used to transmit passenger information 210 (see FIG. 3). Note that the user terminal 20a and the user terminal 20b are not necessarily different information processing apparatuses.

<Functional Blocks Provided by Ride Share Management Device>
The rideshare management device 10 includes a control section 11 , a storage section 12 and a communication section 13 .

The control unit 11 is configured by a microprocessor having a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), I/O (Input/Output), and the like. The CPU executes each program read from the ROM or the storage unit 12, reads information from the RAM, the ROM, and the storage unit 12 during the execution, writes information to the RAM and the storage unit 12, It exchanges signals with the communication unit 13 and the like. In this way, the processing in this embodiment is realized through cooperation between hardware and software (programs). Details of the control unit 11 will be described later.

The storage unit 12 is composed of a semiconductor memory or the like, and stores various programs such as a control program called firmware or an operating system, and various information such as user information and vehicle information.

The user information is information such as a user identification number, account information, and user terminal 20 that identifies the user 2 who uses the ride-sharing service as the driver 2a or passenger 2b. The vehicle information is information such as the vehicle identification number of the ride-sharing vehicle 3 . Details of the storage unit 12 will be described later.

The communication unit 13 has a DSP (Digital Signal Processor) and the like, and complies with standards such as 3G (3rd Generation), LTE (Long Term Evolution), 4G (4th Generation), Wi-Fi (registered trademark), and 5G (5th Generation). , to realize communication with other devices via the network 5.

Next, details of the control unit 11 will be described. The control unit 11 of this embodiment includes a driver information acquisition unit 111, a passenger information acquisition unit 112, a movement plan proposal unit 113, a point setting unit 114, and a plan distribution unit 115. .

The driver information acquisition unit 111 acquires driver information 200 transmitted from the user terminal 20a of the driver 2a. The driver information 200 includes a starting point 201 at which the ride-sharing vehicle 3 starts driving, a final first destination 202 of the ride-sharing vehicle 3, a departure time 203 at which the ride-sharing vehicle 3 departs, and the first destination 202. Included is an arrival time 204 to arrive, a second departure time 206 to leave the first destination 202, a second arrival time 207 to arrive at the second destination 205, etc. (see FIG. 2).

The passenger information acquisition unit 112 acquires passenger information 210 transmitted from the user terminal 20b of the passenger 2b. The passenger information 210 includes a desired boarding place 211 where the passenger 2b desires to board, a desired alighting place 212 which is the destination or transit point of the passenger 2b, a desired boarding time 213 for boarding at the desired boarding place 211, and a desired alighting place. A desired alighting time 214 for arriving at ground 212 and the like are included (see FIG. 3).

The movement plan proposing unit 113 performs a matching process or the like based on the driver information 200 received from the user terminal 20a of the driver 2a and the passenger information 210 received from the user terminal 20b of the passenger 2b, and performs ride sharing. process to create the necessary information for Processing by the movement plan proposal unit 113 will be described later.

The plan distribution unit 115 controls the communication unit 13 so as to transmit information on ride sharing to the user terminal 20a of the driver 2a and the user terminal 20b of the passenger 2b, which are the targets of the travel plan 300, respectively.

Next, details of the storage unit 12 will be described. The storage unit 12 of the present embodiment includes a map storage unit 121, a ride-sharing history storage unit 122, a driver candidate storage unit 123, and a point management unit as areas for storing information used to create the rideshare plan 100. 124 and .

The map storage unit 121 is an area that stores map information indicating a road map (map) and the like. The map storage unit 121 of this embodiment further stores transportation operation information 140 of public transportation such as trains and buses as means of transportation other than ride-sharing vehicles.

The ride-sharing history storage unit 122 is an area in which the past operation history 126 of the ride-sharing vehicle 3 and the boarding history 127 of the passenger 2b when using the ride-sharing service are stored. For example, the matching probability for each time (time zone) when using ride sharing for movement from A station to commercial building B is stored.

The driver candidate storage unit 123 is an area that stores a plurality of driver candidates who can drive the rideshare vehicle 3 .

The point management unit 124 is a database that stores point information. A configuration example for managing point information will be described with reference to FIG. As shown in FIG. 4, the point management unit 124 stores car share points 151 and ride share points 152 for each user 2 .

Point giving by the point setting unit 114 will be described. The point setting unit 114 of this embodiment includes a car share point calculation unit 141 , a ride share point calculation unit 142 and a point integration unit 143 .

The car share point calculation unit 141 calculates points based on actions related to maintenance by the user 2, such as washing the car, refueling, and moving the ride share vehicle 3 to a predetermined location. A predetermined calculation formula is set for each action to which car share points 151 are awarded, and car share points are calculated based on information indicating the type of action of user 2 . Information indicating the type of behavior of the user 2 is acquired by the rideshare management device 10 by an appropriate method such as operation of the user terminal 20 or GPS information. The car share point calculation unit 141 also calculates points used when points are used.

The ride share point calculation unit 142 calculates points based on actions related to ride sharing, such as participation as a driver 2a in the ride share service, participation as a passenger 2b, pick-up of the passenger 2b, number of fellow passengers, and the like. Give. A predetermined calculation formula is also set for each action to which the ride share points 152 are awarded, and the ride share points 152 are calculated based on the information indicating the type of action of the user 2 . Information indicating the type of behavior of the user 2 is acquired by the rideshare management device 10 by an appropriate method such as operation of the user terminal 20 or GPS information. The ride share point calculation unit 142 also calculates points used when points are used.

The point integration unit 143 receives user 2's reservation information, track record information, point conversion request information, and the like, and performs processing for controlling the car share point calculation unit 141 and the ride share point calculation unit 142 based on the received information. In this embodiment, the car share point 151 can be used for both the ride share service and the car share service, and the ride share point 152 can also be used for both the ride share service and the car share service.

In addition, the point integration unit 143 of the present embodiment has a function of changing the point calculation method according to the environment such as reservation information. For example, when the ride share points 152 are used for the car sharing service, the variables of the calculation formula regarding the use of the points of the car share point calculation unit 141 are changed so as to increase the use of the points within a predetermined period of time. Alternatively, when vehicles are concentrated in the same area during a certain period of time, the points given to actions in different areas are absolutely or relatively high so that the vehicles are dispersed in different areas. A process of changing the variables of the calculation formulas of the car share point calculation unit 141, the ride share point calculation unit 142, or both may be performed so that

Further, the point integration unit 143 performs processing for notifying the user 2 of the information acquired from the car share point calculation unit 141 and the ride share point calculation unit 142 . For example, a message such as "Usually 1000 points for 1 hour, but now you can use 1000 points for 10 hours" is created and sent to the user terminal 20 at an appropriate timing.

<Information included in the movement plan>
The types of information included in the movement plan 300 will now be described with reference to FIG. The movement plan 300 includes passenger candidates 301, boarding/alighting points 302, first route 303, second route 304, mobility possibilities 305, substitute driver candidates 306, schedule 307, point information 310, and the like. Details of each information will be explained.

The passenger candidate 301 is information indicating the passenger 2b matched based on the driver information 200 received from the user terminal 20a of the driver 2a and the passenger information 210 received from the user terminal 20b of the passenger 2b. is. The boarding/alighting point 302 is information indicating the boarding/alighting place of the passenger 2b.

A first route 303 is information indicating a route from the starting point 201 to the first destination 202 . The driver 2 a follows the first route 303 to move the ride share vehicle 3 to the first destination 202 with the passenger 2 b on board.

The second route 304 is information indicating a route from the first destination 202 to the second destination 205, and is generated when the first destination 202 and the second destination 205 do not match. The second route 304 is information on the premise that the ride share vehicle 3 is not used by the driver 2a.

The mobility possibility 305 is the probability that the rideshare vehicle 3 can be driven to the first destination 202, dropped off at the first destination 202, and then traveled on the second route 304 to reach the second destination 205, or the means of transportation. is information indicating

Hereinafter, the mobility possibility when using the ride-sharing service as the passenger 2b will be described as the first mobility possibility 311, and the mobility possibility when using a transportation means other than the ride-sharing service will be described as the second mobility possibility 312. do.

The first travel possibility 311 is information indicating the probability that the passenger 2b can travel from the first destination 202 to the second destination 205 using the ride share service. The first mobility possibility 311 is calculated numerically or expressed in a step-by-step level based on the past ride-sharing service usage record of the first destination 202 . In addition, in the present embodiment, the information indicating the first travel possibility 311 is created in consideration of the second departure time 206 which is the departure time of the first destination 202 .

For example, it is assumed that the matching probability of using ride sharing for travel from station A to commercial building B is highest in the morning, evening, and noon in that order. The matching probability here is set based on whether or not the desired passenger 2b was able to use the rideshare service. The first travel possibility 311 created when the driver information 200 is acquired in which the first destination 202 is station A and the second destination 205 is commercial building B is This is the information indicating that the price is higher in the morning time zone. For example, during the morning hours, the matching probability is displayed as "80%" or the matching possibility is "high", while during the daytime, the matching probability is displayed as "30%" or the matching possibility is "low". be done. It should be noted that these are merely examples, and an appropriate method can be adopted for expressing the information indicating the possibility of matching.

The second mobility possibility 312 is information indicating a means of transportation when using a means of transportation other than the ride-sharing vehicle 3 of the ride-sharing service. In the second mobility possibility 312 public transportation such as trains, buses etc. is displayed. In addition to public transportation, it is also possible to set another means of transportation such as a share cycle.

The second travel possibility 312 is set as a travel means candidate based on the positional relationship between the first destination 202 and the second destination 205 . Therefore, it is not always necessary to set the second mobility 312 .

The substitute driver candidate 306 is information indicating the substitute driver who will move the rideshare vehicle 3 from the first destination 202 to the second destination 205 . The movement plan proposal unit 113 selects candidates for the driver 2a stored in the driver candidate storage unit 123 that can be moved from the first destination 202 to the second destination 205 after abandoning the rideshare vehicle 3. It is set as a substitute driver candidate 306 .

The schedule 307 is information about time. Specifically, the information includes a departure time 203, an arrival time 204, a second departure time 206, a second arrival time 207, and the like.

The point information 310 is information relating to the given points 314 and the used points 315 . Granted points 314 are points awarded to the driver 2a, which are the ride share points 152 described above. The given points 314 include ride share points 152 newly given for movement from the starting point 201 to the first destination 202 . The newly given ride share points 152 can be distinguished and displayed on the user terminal 20 .

The usage points 315 are points that are consumed when the substitute driver candidate 306 is requested to move the rideshare vehicle 3 . The usage points 315 are calculated taking into account the distance traveled, the time of day, the state of congestion in other areas, and the like.

The information included in the movement plan 300 described above is the information provided to the user terminal 20 of the user 2 . Next, the input processing by the user 2 who uses the ride-sharing service as the driver 2a will be described with reference to the flow of FIG. In the following example, it is assumed that the user 2 inputs while the application installed in the user terminal 20 is running.

In step S<b>11 , the user 2 (driver 2 a ) inputs the driver information 200 by operating the interface section 23 of the user terminal 20 . In addition, in the process of inputting the driver information 200, if the starting point 201 and the second destination 205 are the same, the input of the second destination 205 can be omitted. For example, if the second destination 205 is not input, it may be determined that the departure point 201 and the second destination 205 are the same, and processing for creating the travel plan 300 may be performed. After step S11, in step S12, the user 2 performs an operation to confirm means of transportation to the second destination 205. FIG. In steps S11 and S12, the rideshare management device 10 that has received the driver information 200 and the confirmation information of the transportation means from the user terminal 20 transmits information including the transportation plan 300 to the user terminal 20. FIG.

In step S13, if the movement plan 300 includes information indicating the means of transportation to the second destination 205, a selection screen including information on the means of transportation is displayed on the interface unit 23 of the user terminal 20, and the process proceeds to step S14. move on. Information included in the movement plan 300 of FIG. 5 is displayed on this selection screen, and operations such as ride-sharing reservation and setting of a substitute driver as a passenger 2b moving to the second destination 205 can be performed. It's like

In step S14, automatic reservation of a means of transportation to the second destination 205 or selection of a means of transportation by the user 2 is performed. The automatic reservation of the means of transportation is, for example, a reservation to use a ride-sharing service as a passenger 2b for movement from the first destination 202 to the second destination 205, or the like. When the user 2 selects or confirms the display screen, the contents of the movement plan 300 are finalized.

When the user 2 wants to abandon the ride-sharing vehicle 3, he/she selects the substitute driver who actually moves the ride-sharing vehicle 3 from the substitute driver candidates 306 on this selection screen. The ride share management device 10 that has received the information that the substitute driver has been selected performs a process of confirming with the corresponding substitute driver whether or not to perform substitute driving. As a result of the confirmation, if it is decided to perform the substitute operation, the information that the substitute operation has been confirmed is transmitted to the user terminal 20 .

In step S13, if the movement plan 300 does not contain information indicating means of transportation to the second destination 205, a message indicating that there is no means of transportation to the second destination 205 is displayed on the interface unit 23 of the user terminal 20. The process proceeds to step S15 for displaying. When the confirmation operation is performed by the user 2 in step S15, the contents of the movement plan 300 are confirmed.

By the input processing of the user 2, information (movement plan 300) related to ride sharing included in the movement plan 300 is confirmed, and this confirmed ride sharing information is transmitted to the driver 2a and the passenger 2b who are in the same ride sharing group. be.

As described above, the rideshare management device 10 of this embodiment includes the map storage unit 121 , the rideshare history storage unit 122 , the driver information acquisition unit 111 , and the travel plan proposal unit 113 . When the first destination 202 and the second destination 205 of the driver 2a are different, the movement plan proposal unit 113 selects the first destination based on at least one of the operation history 126 and the ride history 127 of the ride share history storage unit 122. Information indicating the possibility of movement 305 that allows the passenger 2b to move from the ground 202 to the second destination 205 is created.

As a result, even if the driver 2a wishes to drop off the rideshare vehicle 3 on the way (first destination 202), it is possible to confirm the possibility 305 of movement as the passenger 2b to the second destination 205, so that the driver 2a can drop off. You can use the ride sharing service on the premise. Since the convenience is improved, there is a motivation to register as the driver 2a, and it becomes easier to secure the driver 2a for the ride-sharing service.

In this embodiment, the driver information acquisition unit 111 further acquires the second departure time 206, which is the departure time of the driver 2a of the ride-sharing vehicle 3 from the first destination 202, and the movement plan proposal unit 113 creates information indicating travel possibilities 305 taking into account the second departure time 206 .

As a result, highly accurate travel possibilities 305 that reflect the second departure time 206 can be presented. Therefore, the driver 2a can also consider a ride-sharing plan on the assumption that the vehicle will be dropped off on the way.

Further, in this embodiment, when the movement plan proposal unit 113 acquires information indicating that the departure point 201 and the second destination 205 are the same, Create information indicating the possibilities 305 .

As a result, it is possible to present the possibility 305 of movement to the final second destination 205 without inputting the first destination 202, which is a drop-off point, thereby saving the driver's input work and increasing the convenience of the ride-sharing service. can be further improved.

In addition, the map storage unit 121 of the present embodiment stores transportation operation information 140 different from that of the ride-sharing vehicle 3, and the movement plan proposal unit 113 stores the first movement possibility 311 to move as the passenger 2b and the transportation Information indicating the mobility possibility 305 may be created by combining the second mobility possibility 312 that moves based on the engine operation information 140 .

Further, in the present embodiment, when the first destination 202 and the second destination 205 of the driver 2a are different, the movement plan proposal unit 113 selects the candidates for the driver 2a stored in the driver candidate storage unit 123 Based on this, a substitute driver candidate 306 who can drive the rideshare vehicle 3 from the first destination 202 to the second destination 205 is determined.

As a result, even if the driver 2a wishes to drop off the rideshare vehicle 3 on the way (first destination 202), it is possible to find a substitute driver to move the rideshare vehicle 3 to the second destination 205. Ride-sharing services can be used on the premise of drop-off. Since the convenience is improved, there is a motivation to register as a driver, and it becomes easier to secure the driver 2a for the ride-sharing service.

Further, in this embodiment, the movement plan proposal unit 113 notifies the passenger candidate 301 and the boarding/alighting point 302 as well as the ride share points 152 given to the driver 2a, and A process for notifying the driver 2a of the use points 315 to be used is performed.

As a result, the car share points 151 and the ride share points 152 set for the driver 2a can be used to drop off the ride share vehicle 3, making it easier to use the option of drop off, and the driver 2a can also use the ride share. becomes easier.

Further, in this embodiment, when the first destination 202 and the second destination 205 of the driver 2a are different, the movement plan proposal unit 113 calculates at least the operation history 126 and the boarding history 127 of the ride share history storage unit 122. Information indicating the possibility of movement 305 for traveling as a passenger 2b from the first destination 202 to the second destination 205 is created based on one, and usage points 315 for becoming the passenger 2b are calculated.

As a result, it is possible to confirm the possibility 305 of movement as the passenger 2b to the second destination 205, so that the ride share service can be used on the premise of dropping off. In addition, since the car share point 151 and the ride share point 152 of the driver 2a can be used when participating in the ride share service as the passenger 2b, convenience is further improved.

Although the preferred embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments and can be modified as appropriate.

For example, in FIG. 1, one server is schematically illustrated as the ride share management device 10, but the configuration is not limited to this. For example, the ride-sharing management device 10 of the above-described embodiment is configured to have a function of matching users 2, but this configuration is omitted and a ride-sharing planning device ( A reservation management device) may be used, and matching processing may be performed by an external matching server, and necessary information may be stored in an external database.

In this way, each function of the ride share management device 10 may be distributed to a plurality of server devices as appropriate to form a distributed processing system. Also, each function of the rideshare management device 10 may be implemented using a virtual server function or the like on the cloud.

10 Ride Share Management Device 111 Driver Information Acquisition Unit 113 Travel Plan Proposal Unit 121 Map Storage Unit 122 Ride Share History Storage Unit 123 Driver Candidate Storage Unit

Claims (3)

a map storage unit in which information indicating a map is stored;
Acquisition of a departure point, a first destination that is the destination of the ride-sharing vehicle, and a second destination that is the destination of the driver as driver information of the ride-sharing vehicle used for the ride-sharing service. a driver information acquisition unit that
a driver candidate storage unit that stores a plurality of driver candidates who can drive the rideshare vehicle;
a movement plan proposal unit that proposes passenger candidates and boarding/alighting point information to the driver of the ride-sharing vehicle;
When the first destination and the second destination of the driver are different, the movement plan proposal unit is configured to change the destination from the first destination to the second destination based on the candidates stored in the driver candidate storage unit. 2. A ride-sharing management device that determines substitute driver candidates who can drive the ride-sharing vehicle to two destinations. The movement plan proposing unit notifies the passenger candidate and the boarding/alighting point as well as points to be given to the driver, and notifies the driver of usage points consumed based on the use of the substitute driver candidate. The rideshare management device according to claim 1, which performs processing. further comprising a ride-sharing history storage unit that stores operation histories of the plurality of ride-sharing vehicles and ride histories of passengers;
When the first destination and the second destination of the driver are different, the movement plan proposal unit is configured to provide the first destination based on at least one of the operation history and the boarding history of the ride share history storage unit. 3. The rideshare management device according to claim 2, wherein information indicating the possibility of traveling as a passenger from one destination to the second destination is created, and points used when becoming the passenger are calculated.

Images