Vehicle management system

Abstract

The aim is to make ride-sharing matching easier. [Solution] The server device 200 of the present invention is characterized by having an acquisition means for acquiring information on whether or not a car share user allows a passenger to ride in the vehicle they rent, and a matching means for matching car share users who allow a passenger to ride with ride share users based on the information acquired by the acquisition means. By matching car share users who allow a passenger with ride share users, it is possible to facilitate ride share matching.

Description

Technical Field

[0001] The present invention relates to a vehicle management system.

Background Art

[0002] In recent years, ride-sharing in which passengers share a vehicle has attracted attention, and a vehicle management system for realizing ride-sharing has been developed. Patent Document 1 discloses an information processing system that matches a driving user who owns a vehicle with a user who wishes to share the ride based on a driving schedule, a destination, a user rank, etc. In the information processing system of Patent Document 1, when it is predicted that a plurality of users who wish to share the ride can be matched to a vehicle, for each of the plurality of users who wish to share the ride, a predetermined priority for the matching is set, and the user with the higher priority is preferentially matched with the vehicle.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the information processing system of Patent Document 1, it is premised that a driving user who owns a vehicle and permits ride-sharing participates, and it is essential to satisfy the condition that the driving user has the will to drive. Therefore, since a driving user lacking any of the conditions does not participate in ride-sharing, there is a problem that it is difficult to establish a match with a user who wishes to share the ride.

[0005] The present invention has been made in view of the above-described problems, and an object thereof is to facilitate the establishment of a ride-sharing match.

Means for Solving the Problems

[0006] The present invention relates to a vehicle management system comprising a server device for managing car-sharing users and ride-sharing users, wherein the server device includes an acquisition means for acquiring information on whether or not a car-sharing user allows a passenger to ride in the vehicle rented by the car-sharing user, and a matching means for matching car-sharing users who allow a passenger to ride with ride-sharing users based on the information acquired by the acquisition means. [Effects of the Invention]

[0007] According to the present invention, it is possible to facilitate the matching of rideshare users. [Brief explanation of the drawing]

[0008] [Figure 1] This is a schematic diagram showing an example of a vehicle management system configuration. [Figure 2] This figure shows an example of the hardware configuration of an information processing device. [Figure 3] This figure shows an example of the hardware configuration of a server device. [Figure 4] This figure shows an example of the functional configuration of a server device. [Figure 5] This is a flowchart illustrating an example of the car-sharing reservation process. [Figure 6] This figure shows an example of a car-sharing reservation database. [Figure 7] This flowchart shows an example of the rideshare booking process. [Figure 8] This figure shows an example of a rideshare reservation database. [Modes for carrying out the invention]

[0009] The vehicle management system 10 according to the present invention comprises a server device 200 for managing car-sharing users and ride-sharing users. The server device 200 is characterized by having an acquisition means for acquiring information on whether or not a car-sharing user allows a passenger to ride in the vehicle they rent, and a matching means for matching car-sharing users who allow a passenger with ride-sharing users based on the information acquired by the acquisition means. By matching car-sharing users who allow a passenger with ride-sharing users, it is possible to facilitate ride-sharing matching. [Examples]

[0010] The vehicle management system 10 according to the present invention will be described below with reference to the drawings. Figure 1 is a schematic diagram showing an example of the configuration of the vehicle management system 10. The vehicle management system 10 comprises an information processing device 100a (100), an information processing device 100b (100), and a server device 200.

[0011] The information processing device 100a(100) is assumed to be a smartphone, tablet, PC (personal computer), etc., owned and operated by a car-sharing user. Here, the illustration of information processing devices 100a owned by other car-sharing users is omitted. The information processing device 100b(100) is assumed to be a smartphone, tablet, PC (personal computer), etc., owned and operated by a rideshare user. Here, the illustration of information processing devices 100b owned by other rideshare users is omitted. In the following explanation, if there is no need to distinguish between information processing device 100a and information processing device 100b, they will be referred to simply as information processing device 100.

[0012] The server device 200 is assumed to be directly or indirectly managed by a provider that provides services using the vehicle management system 10. The server device 200 manages information of car-sharing users and ride-sharing users, and executes car-sharing reservation processing and ride-sharing reservation processing described later. Note that the server device 200 may be configured as a cloud system. A cloud system includes a plurality of server devices connected via a network, and is a system that can provide various functions by these server devices cooperating with each other to perform processing. The information processing devices 100a and 100b and the server device 200 can communicate with each other via a network 300 such as the Internet.

[0013] <Configuration of Information Processing Device 100> FIG. 2 is a diagram showing an example of the hardware configuration of the information processing device 100. The information processing device 100 includes a control unit 101, a nonvolatile memory 102, a volatile memory 103, an operation unit 104, a display unit 105, a recording medium 106, a communication unit 107, and the like.

[0014] The control unit 101 controls each unit constituting the information processing device 100 by executing an OS (operating system), which is basic software, in response to a user operation via the operation unit 104. In addition, the control unit 101 realizes the processing of each flowchart described later by executing an application program in cooperation with the OS.

[0015] The nonvolatile memory 102 is a memory that can be electrically erased and recorded. The nonvolatile memory 102 stores an OS, an application program, data necessary for executing each flowchart, and the like. The volatile memory 103 is a memory used as a work area for the control unit 101.

[0016] The operation unit 104 receives instructions from the user. The operation unit 104 includes a touch panel configured integrally with the display unit 105. The display unit 105 displays display items and the like based on instructions by the control unit 101 so as to be operable interactively with the user. Thus, the user can intuitively operate the information processing apparatus 100 by the operation unit 104 and the display unit 105.

[0017] The recording medium 106 is a recording medium that is detachable from the information processing apparatus 100 or built in the information processing apparatus 100. The recording medium 106 is, for example, an SD card. The communication unit 107 is an interface for transmitting and receiving information to and from the server apparatus 200 via the network 300.

[0018] <Configuration of Server Apparatus 200> FIG. 3 is a diagram showing an example of the hardware configuration of the server apparatus 200. The server apparatus 200 includes a control unit 201, a nonvolatile memory 202, a volatile memory 203, an operation unit 204, a display unit 205, a database 206, a communication unit 207, and the like.

[0019] The control unit 201 controls each unit constituting the server apparatus 200 by executing a program recorded in the nonvolatile memory 202. The nonvolatile memory 202 is an electrically erasable and recordable memory. Programs executed by the control unit 201, data necessary for executing each flowchart, and the like are recorded in the nonvolatile memory 202. The volatile memory 203 is a memory used as a work area for the control unit 201.

[0020] The operation unit 204 receives instructions from an administrator of a provider of the vehicle management system 10. The operation unit 204 is, for example, a keyboard, a mouse, or the like. The display unit 205 displays the result executed by the control unit 201. The display unit 205 is, for example, a liquid crystal display, an organic EL display, or the like.

[0021] Database 206 records various databases (DBs) used to implement the vehicle management system 10. Database 206 records user management DB, car share reservation DB, ride share reservation DB, etc. for each user. The user management DB records information such as user ID, gender, age, rating, and points. The rating is assigned to each user by the server device 200. The rating has stages, for example, rating 1 is the lowest rating and rating 5 is the highest rating. Points are owned by each user and can be used to get a discount on car share or ride share usage fees. As shown in Figure 6 below, the car share reservation DB records information such as user ID, vehicle ID, driving section, and rental time for each car share reservation number. Similarly, as shown in Figure 8 below, the ride share reservation DB records information such as user ID, ride section, and ride time for each ride share reservation number. Database 206 may also be configured as a database server. The communication unit 207 is an interface for sending and receiving information with the information processing device 100 via the network 300.

[0022] Figure 4 shows an example of the functional configuration of the server device 200. The functional configuration of the server device 200 shown in Figure 4 is realized by the control unit 201 executing a program recorded in the non-volatile memory 202. The server device 200 includes a car-sharing information acquisition unit 211, a car-sharing reservation processing unit 212, a ride-sharing information acquisition unit 213, a ride-sharing reservation processing unit 214, a matching processing unit 215, and an incentive granting unit 216.

[0023] The car-sharing information acquisition unit 211 acquires information from the information processing device 100a operated by the car-sharing user. The car-sharing reservation processing unit 212 executes car-sharing reservation processing based on information from the information processing unit 100a operated by the car-sharing user. The rideshare information acquisition unit 213 acquires information from the information processing device 100b operated by the rideshare user. The rideshare reservation processing unit 214 executes rideshare reservation processing based on information from the information processing unit 100b operated by the rideshare user. The matching processing unit 215 executes a matching process to ensure that a matching of rideshare users is successful. The incentive distribution unit 216 provides incentives to car-sharing users and ride-sharing users.

[0024] In the vehicle management system 10 configured in this way, as preparation for executing the flowchart described later, the control unit 101 of the information processing device 100 downloads an application program (car-sharing app or ride-sharing app) provided by a service provider from the network 300 in response to user operation and records it in the non-volatile memory 102. Also, when the application is executed for the first time, the control unit 101 of the information processing device 100 prompts the car-sharing user or ride-sharing user to input information such as username, gender, and age via the operation unit 104.

[0025] Furthermore, the control unit 101 of the information processing device 100 transmits the input information to the server device 200, and the control unit 201 of the server device 200 associates the received information with the user ID as user identification information and records it in the user management DB. The server device 200 in this embodiment performs two main processes. The first is car-sharing reservation processing, and the second is ride-sharing reservation processing. The two processes will be described below.

[0026] <Car sharing reservation processing> Figure 5 is a flowchart showing an example of a car-sharing reservation process. In this example, a car-sharing user makes a reservation to rent a vehicle using the information processing device 100a, and the server device 200 executes the car-sharing reservation process. The vehicles eligible for car sharing may be those directly managed by the service provider or those indirectly managed by the service provider. Here, vehicles directly managed by the service provider include, for example, vehicles owned by the service provider. Vehicles indirectly managed by the service provider include, for example, vehicles managed by a contractor commissioned by the service provider, or vehicles owned by individuals leased to the service provider or the contractor.

[0027] In S101, the control unit 101 of the information processing device 100a transmits the user ID and other information to the server device 200 in response to the car share user's operation to start a car share reservation.

[0028] In S201, the car-sharing information acquisition unit 211 of the server device 200 performs user authentication based on the user ID received from the information processing device 100a. If the car-sharing reservation processing unit 212 of the server device 200 determines, as a result of user authentication, that the user is not a legitimate user, it sends information to the information processing device 100a indicating that a car-sharing reservation cannot be made.

[0029] In S102, the control unit 101 of the information processing device 100a prompts the car-sharing user to input the driving section and rental time of the vehicle to be shared. Here, the driving section consists of a departure point and an arrival point, and may include one or more intermediate points. The rental time consists of the rental start time and the rental end time. The rental time also consists of the scheduled departure time from the departure point and the scheduled arrival time from the arrival point, and may include the scheduled arrival and departure times for each intermediate point. The control unit 101 of the information processing device 100a transmits the input information such as the driving section and rental time to the server device 200. The control unit 101 may also prompt the car-sharing user to input the vehicle type.

[0030] In S202, the car-sharing information acquisition unit 211 of the server device 200 acquires information on the driving section and rental time by receiving it from the information processing device 100a. The car-sharing reservation processing unit 212 of the server device 200 records the driving section and rental time information in the car-sharing reservation DB, associating it with the user ID and vehicle ID. If there are no vehicles available for car-sharing at the entered rental time, the car-sharing reservation processing unit 212 of the server device 200 sends information to the information processing device 100a indicating that a car-sharing reservation cannot be made.

[0031] In S103, the control unit 101 of the information processing device 100a prompts the car share user to select whether or not to allow a passenger. Selecting whether or not to allow a passenger means choosing whether or not to allow a passenger to ride in the car share vehicle. At this time, the control unit 101 may also prompt the user to input conditions for the passenger (gender, age, rating, etc.) if they choose to allow a passenger. For example, the conditions for the passenger can be entered as "gender not specified," "age 20 to 70," and "rating of 3 or higher." The control unit 101 of the information processing device 100a transmits the information on whether or not to allow a passenger and the conditions for the passenger to the server device 200.

[0032] In S203, the car-sharing information acquisition unit 211 of the server device 200 acquires information on whether or not there are passengers and the conditions of the passengers by receiving it from the information processing device 100a. The car-sharing reservation processing unit 212 of the server device 200 records the information on whether or not there are passengers and the conditions of the passengers in the car-sharing reservation DB, associating it with the user ID and vehicle ID.

[0033] In S104, the control unit 101 of the information processing device 100a prompts the car share user to select whether or not to allow a passenger to drive. The selection of whether or not to allow a passenger to drive means selecting whether or not to permit a passenger to drive the car share vehicle. At this time, the control unit 101 may also prompt the user to input conditions (gender, age, rating, etc.) for the passenger who will be allowed to drive (hereinafter referred to as the "driver passenger"). For example, the conditions for the driver passenger can be entered as "gender irrelevant," "age 40 to 60," and "rating of 5 or higher." Here, the user is asked to input conditions that are the same as those entered in S103, or conditions that are more refined than those entered in S103. The control unit 101 of the information processing device 100a transmits the information on whether or not to allow a passenger to drive and the conditions for the driver passenger to the server device 200. If the user did not permit a passenger to drive in S103, the process in S104 is omitted.

[0034] In S204, the car-sharing information acquisition unit 211 of the server device 200 acquires information on whether the passenger can drive and the conditions of the driver-passenger from the information processing device 100a. The car-sharing reservation processing unit 212 of the server device 200 records the information on whether the passenger can drive and the conditions of the driver-passenger in the car-sharing reservation DB, associated with the user ID and vehicle ID. Therefore, each time a car-sharing reservation process is completed, the user ID, vehicle ID, driving section, rental time, whether the passenger can drive (and the conditions of the passenger), and whether the passenger can drive (and the conditions of the driver-passenger) are recorded in the car-sharing reservation DB in association with each other. In S205, the car-sharing reservation processing unit 212 of the server device 200 transmits information to the information processing device 100a indicating that the car-sharing reservation has been completed. This process terminates the car-sharing reservation process.

[0035] In S105, the control unit 101 of the information processing device 100a displays on the display unit 105 that the car share reservation has been completed, thereby ending the process of the flowchart in Figure 5. In the flowchart in Figure 5 described above, the information processing device 100a transmits information about the driving section and rental time, information about whether or not there are passengers, and information about whether or not the passengers are able to drive to the server device 200 at different times. However, they may also be transmitted at the same time.

[0036] Figure 6 shows an example of the car-sharing reservation DB600. The car-sharing reservation DB600 contains the following items: car-sharing reservation number, car-sharing user ID, vehicle ID, driving section, rental time, whether passengers are allowed, whether a driver can be a passenger, passenger 1, whether passenger 1 wishes to drive, passenger 2, and whether passenger 2 wishes to drive. According to the flowchart in Figure 5, information is recorded in the car-sharing reservation DB600 for the following items: car-sharing reservation number, car-sharing user ID, vehicle ID, driving section, rental time, whether passengers are allowed, and whether a driver can be a passenger. On the other hand, information is recorded in the car-sharing reservation DB600 for the following items: passenger 1, whether passenger 1 wishes to drive, passenger 2, and whether passenger 2 wishes to drive, according to the flowchart in Figure 7, which will be described later.

[0037] <Ridesharing booking process> Figure 7 is a flowchart showing an example of a rideshare reservation process. In this example, a rideshare user makes a reservation using the information processing device 100b, and the server device 200 executes the rideshare reservation process in response to the reservation operation. Note that the vehicles eligible for ride-sharing include those for which a car-sharing reservation has been completed, as shown in the flowchart in Figure 5.

[0038] In S111, the control unit 101 of the information processing device 100b transmits the user ID and other information to the server device 200 in response to the rideshare user's operation to start a rideshare reservation.

[0039] In S211, the rideshare information acquisition unit 213 of the server device 200 performs user authentication based on the user ID received from the information processing device 100b. If the rideshare reservation processing unit 214 of the server device 200 determines, as a result of user authentication, that the user is not a legitimate user, it sends information to the information processing device 100b indicating that a rideshare reservation cannot be made.

[0040] In S112, the control unit 101 of the information processing device 100b prompts the rideshare user to input the ride section and ride time. Here, the ride section consists of the desired departure point and the desired arrival point. The ride time consists of the desired departure time and the desired arrival time. At this time, the control unit 101 of the information processing device 100b may also prompt the user to input conditions (gender, age, rating, etc.) for the driver (or passenger if the rideshare itself is driving, as described later). For example, the conditions for the driver (or passenger) can be entered as gender not specified, 40 to 60 years old, and rating of 5 or higher. The control unit 101 of the information processing device 100b transmits the input information such as the ride section and ride time to the server device 200.

[0041] In S212, the rideshare information acquisition unit 213 of the server device 200 acquires information on the ride section and ride time by receiving it from the information processing device 100b. The rideshare reservation processing unit 214 of the server device 200 records the information on the ride section, ride time, etc., in the rideshare reservation DB, associating it with the user ID.

[0042] In S113, the control unit 101 of the information processing device 100b prompts the rideshare user to choose whether or not they wish to drive themselves. Choosing whether or not to drive means selecting whether or not they wish to drive themselves for the entered ride distance. The control unit 101 of the information processing device 100b transmits the information regarding the user's choice of whether or not they wish to drive to the server device 200.

[0043] In S213, the rideshare information acquisition unit 213 of the server device 200 acquires information regarding the user's preference for driving by receiving it from the information processing device 100b. The rideshare reservation processing unit 214 of the server device 200 records the user's preference for driving in the rideshare reservation DB, associating it with the user ID.

[0044] In S214, the rideshare reservation processing unit 214 of the server device 200 determines whether there is a vehicle (hereinafter referred to as a candidate vehicle) among the vehicles for which reservations have been completed and which are recorded in the carshare reservation DB, where the ride section and ride time received from the information processing unit 100b are included in both the driving section and the rental time, and where passengers are permitted. If such a candidate vehicle exists, the process proceeds to S215.

[0045] Furthermore, if the rideshare reservation processing unit 214 has requirements for a driver (or passenger), it refers to the user management DB to determine whether the carshare user associated with the candidate vehicle meets the requirements of the rideshare user. Also, if the carshare user associated with the candidate vehicle has requirements for a passenger, the rideshare reservation processing unit 214 refers to the user management DB to determine whether the rideshare user meets the requirements of the carshare user. If there are candidate vehicles and the requirements are met between the rideshare user and the carshare users, the process proceeds to S215. On the other hand, if there are no candidate vehicles, or if there are candidate vehicles but the requirements are not met between the rideshare user and the carshare users, the process proceeds to S220.

[0046] In S215, the rideshare reservation processing unit 214 of the server device 200 determines whether the rideshare user wishes to drive, based on the user's selection of whether or not they wish to drive, which was obtained in S213. If the user wishes to drive, the process proceeds to S216.

[0047] In S216, the matching processing unit 215 of the server device 200 refers to the car share reservation DB to extract candidate vehicles for which the passenger is allowed to drive, and matches the car share user of the extracted candidate vehicle with the corresponding ride share user. The ride share reservation processing unit 214 associates the ride share user's user ID with the vehicle ID and the car share user's user ID and records this in the ride share reservation DB. The car share reservation processing unit 212 also associates the ride share user's user ID as a passenger with the car share user's user ID and vehicle ID and records this in the car share reservation DB.

[0048] In S217, the incentive granting unit 216 of the server device 200 grants incentives to rideshare users for whom a match has been made. The incentives here are mainly incentives for driving the vehicle for the ride portion. Examples of incentives for rideshare users include discounts on rideshare usage fees and points that can be used when using rideshare services. Furthermore, the incentive granting unit 216 of the server device 200 grants incentives to car-sharing users who have successfully found a match. These incentives are primarily for the user's contribution to the successful matching process by allowing a passenger to ride along. Examples of incentives for car-sharing users include discounts on rental fees, extensions of rental time, and points that can be used when using car-sharing services. After processing S217, the process proceeds to S221.

[0049] On the other hand, if you do not wish to drive in S215, proceed to S218. In S218, the matching processing unit 215 of the server device 200 refers to the car share reservation DB to extract candidate vehicles for which the passenger is not allowed to drive, and matches the car share users of the extracted candidate vehicles with the corresponding ride share users. The ride share reservation processing unit 214 associates the ride share user's user ID with the vehicle ID and the car share user's user ID and records this in the ride share reservation DB. The car share reservation processing unit 212 also associates the ride share user's user ID as a passenger with the car share user's user ID and vehicle ID and records this in the car share reservation DB.

[0050] In S219, the incentive granting unit 216 of the server device 200 grants an incentive to the car-sharing user for whom a match has been made. The incentive here is mainly for the user's contribution to the match by allowing a passenger to ride along. Examples of incentives for car-sharing users include discounts on rental fees, extensions of rental time, and points that can be used when using car-sharing services. Furthermore, in S219, since car-sharing users are always required to drive, it may be possible to set the incentives to be greater than in S217, where car-sharing users are not always required to drive. Here, greater incentives mean a higher discount amount or rate in the case of rental fee discounts, a longer extension time in the case of rental time extensions, and a larger number of points in the case of points. After processing S219, proceed to S221.

[0051] On the other hand, if there are no suitable vehicles among those recorded in the car-sharing reservation database in S214, the process proceeds to S220. In S220, the matching processing unit 215 of the server device 200 extracts vehicles from the regular rideshare reservation database, rather than from the carshare reservation database, and matches them with rideshare users. After processing in S220, the process proceeds to S221.

[0052] In S221, the rideshare reservation processing unit 214 of the server device 200 transmits information to the information processing unit 100b indicating that the rideshare reservation has been completed. The carshare reservation processing unit 212 of the server device 200 also transmits information to the information processing unit 100a of the matched carshare user, indicating that there is a passenger, the passenger's travel section, the passenger's travel time, and whether or not the passenger will be driving.

[0053] In S114, the control unit 101 of the information processing device 100b terminates the process of the flowchart in Figure 7 by displaying on the display unit 105 that the rideshare reservation has been completed. In the flowchart in Figure 7 described above, the information processing device 100b transmits information about the boarding section and boarding time, and information about whether or not the passenger wishes to be driven, to the server device 200 at different times. However, they may be transmitted at the same time.

[0054] Figure 8 shows an example of the rideshare reservation DB800. The rideshare reservation DB800 contains fields for rideshare reservation number, rideshare user ID, ride route, ride duration, whether the user wants to drive, matched carshare user ID, and matched vehicle ID. When the flowchart in Figure 7 is completed, information is recorded in each field of the rideshare reservation DB800.

[0055] Furthermore, once the flowchart in Figure 7 is completed, information is recorded in the following items in the car-sharing reservation DB 600 in Figure 6: passenger 1, whether passenger 1 wishes to drive, passenger 2, and whether passenger 2 wishes to drive. Note that in the car-sharing reservation DB 600 in Figure 6, the first row of the car-sharing reservation shows an example where there are two passengers, and the second row of the car-sharing reservation shows an example where there is one passenger. In this case, the incentive granting unit 216 of the server device 200 grants the car-sharing user more incentives the more passengers there are.

[0056] Furthermore, the control unit 201 of the server device 200 updates the evaluations recorded in the user management DB for car-sharing users and ride-sharing users at predetermined timings. Specifically, the control unit 201 increases the evaluation each time the number of times car-sharing and ride-sharing are used exceeds a threshold predetermined for each stage. On the other hand, if car-sharing users and ride-sharing users cancel reservations beyond a predetermined period, the control unit 201 of the server device 200 decreases the evaluation according to the number of cancellations. In addition, the control unit 201 of the server device 200 may receive assessments of each user's manners and driving skills from the matched users via the respective information processing devices 100a and 100b after they have actually used car-sharing and ride-sharing, and update each user's evaluation based on the received assessments.

[0057] Furthermore, if a car-sharing user cancels a car-sharing reservation, the control unit 101 of the information processing device 100a transmits information such as the car-sharing reservation number to be canceled to the server device 200 in response to the car-sharing user's operation to cancel the reservation. The control unit 201 of the server device 200 cancels the car share reservation number from the car share reservation DB. At this time, the control unit 201 of the server device 200 refers to the car share reservation DB and, if there is a ride share user (passenger) matched with the car share user, notifies the information processing device 100b of the matched ride share user that the car share reservation has been canceled. In this case, the control unit 201 of the server device 200 performs rematching by executing the processes S214 to S221 in the flowchart of Figure 7. If rematching is not successful, the control unit 201 of the server device 200 notifies the administrator of the provider of the server device 200 that rematching due to the cancellation of the car share reservation was unsuccessful. In this case, the provider has a waiting staff member drive the vehicle so that the ride share user can board for the boarding section and boarding time reserved.

[0058] As described above, according to the vehicle management system 10 of this embodiment, the server device 200 includes a car-sharing information acquisition unit 211 that acquires information on whether or not a car-sharing user allows a passenger to ride in the vehicle they rent, and a matching processing unit 215 that matches car-sharing users who allow a passenger to ride with ride-sharing users based on the information acquired by the car-sharing information acquisition unit 211. In this way, by including car-sharing users in the matching target for ride-sharing users, it is possible to make ride-sharing matches easier to achieve and promote ride-sharing.

[0059] Furthermore, the server device 200 matches car-sharing users who allow a passenger to drive with ride-sharing users who wish to drive. Therefore, even car-sharing users with little desire to drive will be motivated to use car-sharing, increasing their opportunities to use it, and thus making it easier to successfully match ride-sharing users.

[0060] Furthermore, the server device 200 has an incentive granting unit 216 that provides an incentive to the car-sharing user when a match is made between the car-sharing user and the ride-sharing user. Therefore, car-sharing users can be more likely to allow passengers to ride along. Furthermore, the server device 200 provides car-sharing users with greater incentives for the number of passengers they bring along when renting a vehicle. Therefore, car-sharing users are more likely to allow additional passengers to join them.

[0061] Although embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above, and modifications can be made within the scope of the present invention. [Explanation of symbols]

[0062] 10: Vehicle management system 100 (100a, 100b): Information processing device 101: Control unit 200: Server device 201: Control unit 211: Car share information acquisition unit 212: Car share reservation processing unit 213: Ride share information acquisition unit 214: Ride share reservation processing unit 215: Matching processing unit 216: Incentive granting unit 600: Car share reservation DB 800: Ride share reservation DB

Claims

1. A vehicle management system comprising a server device for managing car-sharing users and ride-sharing users, The server device is A means for obtaining information on whether or not the car share user allows a passenger to ride in the vehicle they rent, Based on the information obtained by the aforementioned acquisition means, a matching means is provided to match car-sharing users who allow passengers to ride with ride-sharing users. A vehicle management system characterized by having the following features.

2. The server device is The vehicle management system according to claim 1, further comprising a means for providing an incentive to a car-sharing user who has been matched when a match is made by the matching means.

3. The aforementioned granting means is The vehicle management system according to claim 2, characterized in that the more passengers a car share user has riding in the vehicle, the greater the incentive provided.

Images