Carpooling Assist System

Abstract

(Problem) To realize a vehicle carpooling assistance system that prevents the transmission of a requested carpooling condition that does not match the actual needs of a user. (Solution) A vehicle carpooling assistance system (1) is disclosed, the system comprising: a terminal (2) provided with a user interface (12) and a terminal processing unit for controlling the user interface; a behavior information management server (7) storing user behavior information; and a carpooling management server (4) creating a carpooling operation plan based on the requested carpooling condition, the requested carpooling condition including at least one of the user's departure location, departure time, arrival location, and arrival time transmitted from the terminal processing unit. The carpooling management server creates a recommended carpooling condition based on the behavior information and transmits the recommended carpooling condition to the terminal processing unit, the recommended carpooling condition including at least one of the departure location, departure time, arrival location, and arrival time that are suitable for the user. Upon receiving the recommended carpooling condition from the carpooling management server, the terminal processing unit causes the user interface to display the recommended carpooling condition.

Description

Technical Field

[0001] The invention relates to a vehicle ride-sharing assistance system that provides ride-sharing services for users. Background Art

[0002] A carpooling assistance system (carpooling system) known in the art assists a driver who plans to travel by car and a carpooler who wants to travel to a destination by car in a carpooling system (for example, Patent Document 1). This carpooling system reduces the number of car operations, thereby saving energy, reducing CO2 emissions, and alleviating traffic congestion.

[0003] In the carpooling assistance system according to Patent Document 1, the driver transmits driving plan information including the driver's departure location, arrival location, and departure time, and the carpooler transmits desired carpooling conditions including the carpooler's current location, arrival location, and arrival time. Upon receiving the driving plan information and the desired carpooling conditions, the carpooling assistance system calculates an optimal combination of the driver and the carpooler based on the driving plan information and the desired carpooling conditions, and creates a carpooling operation plan corresponding to the driving plan information and the desired carpooling conditions.

[0004] Prior art literature

[0005] Patent Literature

[0006] Patent Document 1: Japanese Patent Application Publication No. 2002-140399 Summary of the invention

[0007] The task to be accomplished by the present invention

[0008] However, if the carpooler does not correctly understand his plan or inputs it incorrectly, carpooling conditions that do not meet the carpooler's real needs may be transmitted from the carpooler to the carpooling assistance system. In this case, the carpooling assistance system creates an operation plan that does not meet the carpooler's real needs, thereby increasing carpooling cancellations. As a result, the combination of drivers and carpoolers may not be optimal.

[0009] In view of such background, an object of the present invention is to provide a vehicle carpooling assistance system capable of preventing the transmission of desired carpooling conditions that do not meet the real needs of users (carpoolers).

[0010] Means of achieving this task

[0011] In order to achieve such a purpose, an embodiment of the present invention provides a vehicle carpooling assistance system 1 for assisting multiple users in carpooling, the vehicle carpooling assistance system comprising: a terminal 2, the terminal comprising a user interface 12 and a terminal processing unit 11, the user interface comprising an input unit 12B and a display unit 12A, the terminal processing unit being configured to control the user interface; a behavior information management server 7, the behavior information management server being configured to store the behavior information of the user; and a carpooling management server 4, the carpooling management server being configured to communicate with the behavior information management server and the terminal via a network 3, and according to the information from the terminal, The desired ridesharing conditions transmitted by the terminal processing unit create a ridesharing operation plan for a specified implementation period, the desired ridesharing conditions including at least one of the departure place, departure time, arrival place and arrival time of each of the users, wherein the ridesharing management server is configured to set recommended ridesharing conditions for each of the users based on the action information and transmit the recommended ridesharing conditions to the terminal processing unit, the recommended ridesharing conditions including at least one of the departure place, departure time, arrival place and arrival time suitable for each of the users, and the terminal processing unit is configured to cause the user interface to display the recommended ridesharing conditions.

[0012] According to this arrangement, the recommended ride-sharing conditions set based on the action information reflecting the real needs of the user are displayed on the user interface. Therefore, it is possible to prevent the transmission of the desired ride-sharing conditions that do not meet the real needs of the user.

[0013] In the above arrangement, preferably, the terminal processing unit is configured to cause the user interface to simultaneously display the input fields 40 to 44 for inputting the desired ridesharing conditions and the recommended ridesharing conditions.

[0014] According to this arrangement, the user can input desired carpooling conditions into the input field while checking recommended carpooling conditions.

[0015] In the above arrangement, preferably, the terminal processing unit is configured to cause the recommended ridesharing condition to be displayed in the input field.

[0016] According to this arrangement, the recommended rideshare conditions are displayed in the input field. Therefore, when the recommended rideshare conditions correspond to the user's real needs, the user can omit inputting the desired rideshare conditions into the input field.

[0017] In the above arrangement, preferably, the terminal processing unit is configured to cause the user interface to display a decision button 35 together with the recommended ridesharing conditions, and the decision button is configured to receive a decision on whether to transmit the recommended ridesharing conditions as the desired ridesharing conditions to the ridesharing management server.

[0018] According to this arrangement, when the desired carpooling condition corresponds to the recommended carpooling condition, the user can easily transmit the desired carpooling condition to the carpooling management server according to the input of the decision button without inputting the desired carpooling condition.

[0019] In the above arrangement, preferably, when a decision corresponding to not transmitting the recommended ridesharing conditions as the desired ridesharing conditions to the ridesharing management server is input to the decision button, the terminal processing unit is configured to enable the user interface to display input fields 40-44 for inputting the desired ridesharing conditions, wherein the desired ridesharing conditions include at least one of the departure place, departure time, arrival place and arrival time desired by each of the users.

[0020] According to this arrangement, the user can input desired carpooling conditions into the input field while checking recommended carpooling conditions.

[0021] In the above arrangement, preferably, the terminal processing unit is configured to cause the recommended ridesharing condition to be displayed in the input field.

[0022] According to this arrangement, the recommended rideshare conditions are displayed in the input field. Therefore, when the recommended rideshare conditions correspond to the real needs of the user, the user can omit inputting the desired rideshare conditions into the input field.

[0023] In the above arrangement, preferably, the departure point or the arrival point is set to a prescribed point common to all the users.

[0024] According to this arrangement, the carpooling assistance system can be used to assist commuter carpooling by setting the departure point or arrival point to the workplace. In addition, the carpooling assistance system can be used to assist school carpooling by setting the departure point or arrival point to the school.

[0025] In the above arrangement, preferably, the action information includes movement information corresponding to whether there is movement to a location stored in advance, and when the action information during the implementation of the ridesharing includes the movement information corresponding to the absence of the movement, the ridesharing management server does not set the recommended ridesharing condition.

[0026] According to this arrangement, when the action information during implementation includes movement information corresponding to the absence of movement to a place stored in advance (e.g., a work place), the recommended ridesharing condition is not set. Therefore, when it is not possible for the user to use ridesharing, the recommended ridesharing condition is not displayed on the user interface. On the other hand, when it is possible for the user to use ridesharing, the recommended ridesharing condition is displayed on the user interface. Therefore, when the recommended ridesharing condition is not displayed, the user can recognize that his plan is not suitable for using ridesharing, thereby being able to avoid ridesharing applications that do not meet the user's real needs.

[0027] In the above arrangement, preferably, the vehicle carpooling assistance system also includes an attendance recording unit 18, which is configured to obtain the clocking-in time of each of the users, wherein the action information includes at least one past clocking-in time, and the carpooling management server is configured to estimate the clocking-in time of each of the users during the implementation period based on the past clocking-in time, and set the arrival time of the recommended carpooling condition based on the estimated clocking-in time.

[0028] According to this arrangement, it is possible to make the recommended carpooling conditions more suitable for the user.

[0029] In the above arrangement, preferably, the ridesharing management server is constructed to: output the importance level corresponding to each piece of action information stored in the action information management server; calculate the offset time that increases as the importance level increases; and set the arrival time of the recommended ridesharing condition based on a time that is earlier than the estimated clock-in time by the offset time.

[0030] According to this arrangement, the arrival time can be advanced according to the importance of the action information during the implementation period. Therefore, the recommended ride-sharing conditions can be made more suitable for the user.

[0031] In the above arrangement, preferably, the vehicle carpooling assistance system also includes an attendance recording unit 18, which is configured to obtain the clocking-in and clocking-out time of each of the users, wherein the action information includes at least one past clocking-in and clocking-out time, and the carpooling management server is configured to estimate the clocking-in and clocking-out time of each of the users during the implementation period based on the past clocking-in and clocking-out times, and set the departure time of the recommended carpooling condition based on the estimated clocking-in and clocking-out times.

[0032] According to this arrangement, it is possible to make the recommended ride-sharing conditions more suitable for the user.

[0033] Effects of the Invention

[0034] According to the above arrangement, it is possible to provide a vehicle carpooling assistance system that is capable of preventing the transmission of desired carpooling conditions that do not meet the real needs of the user. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] [ Figure 1 ] is a block diagram of a vehicle sharing assistance system according to a first embodiment;

[0036] [ Figure 2 ] shows an embodiment of data input to the action information table;

[0037] [ Figure 3] shows an embodiment of data input into the application information form;

[0038] [ Figure 4 ] shows an embodiment of data input to the importance calculation table;

[0039] [ Figure 5 ] is a flowchart showing the steps of a ridesharing assistance process;

[0040] [ Figure 6 ] is a flowchart showing the steps of starting processing of application reception on the server side;

[0041] [ Figure 7 ] is a flowchart showing the steps of terminal-side application reception processing;

[0042] [ Figure 8 ] shows the screen transition of the user terminal during the terminal side application reception process;

[0043] [ Fig. 9 ] shows the screen transition of the user terminal during the terminal side application reception process;

[0044] [ Fig.10 ] is a flowchart showing the steps of application reception processing on the server side;

[0045] [ Fig.11 ] is a flowchart showing the steps of terminal-side application reception processing according to the second embodiment; and

[0046] [ Fig.12 ] is an explanatory diagram of the screen display of the user terminal during the terminal-side application reception process according to the second embodiment. DETAILED DESCRIPTION

[0047] Hereinafter, an embodiment of the vehicle carpooling assistance system will be described with reference to the accompanying drawings. The vehicle carpooling assistance system 1 according to the present embodiment provides a carpooling service to assist carpooling when a plurality of users (members) belonging to a specific group (company or government agency) move to a specific place (workplace) during the morning commute time (implementation period). The carpooling service refers to a service for receiving the desired carpooling conditions (such as the departure place, the arrival place, the departure time, and the arrival time) desired by each user from each user, determining the best combination of users using the carpooling, the best vehicle, and the best driving route (for example, a route that can minimize traffic congestion) based on the received desired carpooling conditions, and notifying each user of the best combination of users, the best vehicle, and the best driving route.

[0048] A group using the carpooling assistance system 1 has a plurality of shared vehicles so that users can use the shared vehicles. In the carpooling assistance system 1, a plurality of shared vehicles and a vehicle that a user agrees to use for carpooling (hereinafter referred to as a "provided vehicle") are used for carpooling. User identification numbers are set for all users, and vehicle identification numbers are set for all shared vehicles and all provided vehicles.

[0049] <<First Embodiment>>

[0050] (Structure of carpooling assistance system)

[0051] like Figure 1 As shown in , the vehicle carpooling assistance system 1 includes a plurality of user terminals 2, a behavior information management server 7, and a carpooling management server 4. The behavior information management server 7 is configured to manage the behavior information of each user. The carpooling management server 4 is configured to set recommended carpooling conditions based on the behavior information of each user, to make each user terminal 2 display the recommended carpooling conditions, to create a carpooling group by processing the desired carpooling conditions transmitted from each user terminal 2, and to determine the operation plan of the vehicle of each carpooling group. The user terminal 2, the behavior information management server 7, and the carpooling management server 4 are connected via a network 3. Each user terminal 2 is carried by each user, and both the behavior information management server 7 and the carpooling management server 4 are arranged in a building of a company that manages the vehicle carpooling assistance system 1. The network 3 is, for example, the Internet.

[0052] The action information management server 7 includes an action information management unit 17, which is configured to store an action information table T1 ( Figure 2 ), in which the action information of each user is recorded. The action information includes the date, the clock-in time and clock-out time of each user on the date, the event content, and the importance corresponding to the event content. The event content includes movement information corresponding to whether there is movement to the workplace. In this embodiment, the event content is blank (normal work), or includes plan information for vacation, business trip or meeting. The plan information may include information about the start time, end time and location of the meeting. The user terminal 2 can write and modify the event content via the network 3. The importance is determined based on the event content, and is set to a numerical value that increases as the importance of the corresponding event increases. In this embodiment, the importance is determined based on the location where the meeting is held, and is set to a numerical value from 0 to 5.

[0053] The action information management server 7 includes an attendance acquisition unit 15 and is connected to an attendance recording unit 18 (e.g., a time sheet recorder) configured to record the clock-in time and clock-out time of each user. The attendance acquisition unit 15 is configured to receive the clock-in time and clock-out time of each user recorded by the attendance recording unit 18, thereby recording the clock-in time and clock-out time of each user in the action information table T1.

[0054] The ride-sharing management server 4 includes an application processing unit 22, an application information management unit 23, an operation plan creation unit 24, a ride-sharing information management unit 25, a user attribute management unit 26, a vehicle information management unit 27, a road information acquisition unit 28, and a user notification unit 29. The application processing unit 22 is configured to perform a reception process of a ride-sharing application. The application information management unit 23 is configured to store application information. The operation plan creation unit 24 is configured to create a plurality of ride-sharing groups by grouping users who have made ride-sharing applications, and to create operation plan information of vehicles of each ride-sharing group by using an external navigation server 5 configured to store map information. The ride-sharing information management unit 25 is configured to store the created ride-sharing groups and the created operation plan information. The user attribute management unit 26 is configured to store user attribute information. The vehicle information management unit 27 is configured to store registered vehicle information. The road information acquisition unit 28 is configured to acquire traffic congestion information by using an external road information server 6. The user notification unit 29 is configured to perform a process of notifying a user of the operation plan information.

[0055] The user attribute management unit 26 is configured to store information related to the user as user attribute information. The user attribute information includes a user identification number, a user name, a user address, a user work place, and information about a user terminal 2 owned by the user. The mobile information management server 7 and the ride sharing management server 4 communicate with the user terminal 2 using the information about the user terminal 2. In the present embodiment, the work place of each user is set to a site common to all users (a site where a company, a government agency, etc. is located).

[0056] The vehicle information management unit 27 is configured to store information about shared vehicles and provided vehicles registered as shared vehicles as vehicle information. The vehicle information includes information about each registered vehicle, such as a vehicle identification number, a vehicle owner, a vehicle type, and a passenger capacity. For a provided vehicle, the vehicle owner is a person who owns the vehicle. For a shared vehicle, the vehicle owner is a person who owns the vehicle key. As described below, the vehicle owner is updated each time a shared vehicle service is provided.

[0057] The application information management unit 23 is configured to hold an application information table T2 ( Figure 3). In the application information table T2, the application identification number and the application information corresponding to the application identification number are recorded. The application information includes the desired ride-sharing conditions, which include the user identification number of the user who made the application, the departure point, the arrival point, the departure time, and the arrival time. In addition, the application information includes the vehicle identification number of the provided vehicle or the shared vehicle (the key of which is owned by the user who made the application).

[0058] The application processing unit 22 includes an importance output unit 31, an availability determination unit 32, a recommendation condition setting unit 33, a reception start signal transmission unit 34, and a warning unit 30. The importance output unit 31 is configured to output an importance corresponding to the event content in the action information table T1. The availability determination unit 32 is configured to determine whether a rideshare is possible based on the event content. The recommendation condition setting unit 33 is configured to set a recommended rideshare condition, which includes a departure location, an arrival location, a departure time, and an arrival time corresponding to the action information of each user. In addition, the recommendation condition setting unit 33 is configured to set a recommended vehicle identification number, which is a vehicle identification number of a provided vehicle or a shared vehicle suitable for rideshare. The reception start signal transmission unit 34 is configured to transmit a reception start signal to the user terminal 2. The reception start signal includes the set recommended rideshare condition, the set recommended vehicle identification number, and a signal indicating that the rideshare application has been started. The warning unit 30 is configured to compare the received application information with the action information table T1, and transmit a warning signal to the user terminal 2 if the received application information does not correspond to the action information table T1.

[0059] The importance output unit 31 is configured to store the importance calculation table T3 ( Figure 4 ), in which the relationship between the keywords that may be included in the event content of the action information table T1 and the importance of the events corresponding to the keywords is recorded. For example, in the importance calculation table T3, the "first meeting room" as the venue of the meeting and the importance "5" corresponding to the meeting are recorded so as to be associated with each other. The importance output unit 31 is configured to determine the importance corresponding to each event content by referring to the importance calculation table T3, and write (output) the importance to the action information table T1.

[0060] The availability determination unit 32 is configured to determine whether ridesharing is available for each user by referring to the event content described on the date (in the present embodiment, the date of the next day) during the implementation period corresponding to each user's action information table T1. For example, in the case where the event content includes the word "vacation", the availability determination unit 32 determines that ridesharing is not available. In the case where the corresponding date during the implementation period is a weekday and the event content is blank, the availability determination unit 32 determines that ridesharing is available.

[0061] The recommended condition setting unit 33 is configured to set the recommended carpooling condition including the departure point, arrival point, departure time, and arrival time corresponding to the action information of each user based on the information included in the action information table T1. In addition, the recommended condition setting unit 33 is configured to refer to the vehicle information stored in the vehicle information management unit 27, thereby setting a recommended vehicle identification number, which is the vehicle identification number of the provided vehicle or shared vehicle suitable for carpooling.

[0062] More specifically, the recommended condition setting unit 33 is configured to obtain a date corresponding to the implementation period by referring to the action information table T1, and obtain the event content on that date. In the case where the event content includes "vacation" or "business trip", the recommended condition setting unit 33 does not output the recommended ridesharing condition. In the case where the event content is blank, the recommended condition setting unit 33 calculates the average clock-in time by averaging the clock-in times from a date when a signal is received to another date one month before that date. The recommended condition setting unit 33 is configured to output a time (hereinafter referred to as the "first time") that is earlier than the average clock-in time by a predetermined moving time as the arrival time of the recommended ridesharing condition. The moving time can be determined based on the time of moving from the arrival place of the recommended ridesharing condition described below to the actual work place.

[0063] In the case where the event content includes "meeting", the recommendation condition setting unit 33 estimates the start time of the meeting, calculates a time that is earlier than the start time by an offset time (shift time), and further calculates another time (hereinafter referred to as "second time") that is earlier than the above-calculated time by the shift time. The offset time is, for example, the product of the importance and the prescribed time (10 minutes), and increases as the importance of the event increases. Next, the recommendation condition setting unit 33 calculates the above-mentioned first time, compares the first time and the second time, and outputs the earlier time of the first time and the second time as the arrival time of the recommended carpooling condition. According to this structure, the user can advance the arrival time of the recommended carpooling condition according to the importance of the meeting. Therefore, the arrival time of the recommended carpooling condition can be made more suitable for the user.

[0064] In addition, the recommendation condition setting unit 33 obtains the user's address by referring to the user attribute information, and outputs the user's address as the departure point of the recommended ridesharing condition. Next, the recommendation condition setting unit 33 obtains the work location of the user attribute information, selects a suitable location as the arrival point of the vehicle, and outputs the selected suitable location as the arrival point of the recommended ridesharing condition.

[0065] Next, the recommendation condition setting unit 33 calculates the time required to reach the arrival point based on the departure point and the arrival point, calculates a time earlier than the arrival time of the recommended ridesharing condition by the required time, and outputs the calculated time as the departure time of the recommended ridesharing condition.

[0066] In addition, the recommended condition setting unit 33 is configured to search the vehicle information for the user identification number of each user, thereby determining whether each user has the key of the shared vehicle or the key of the provided vehicle. In the case where the user has both the key of the shared vehicle and the key of the provided vehicle, the recommended condition setting unit 33 outputs the vehicle identification number of the shared vehicle as the recommended vehicle identification number. In the case where the user only has the key of the shared vehicle but not the key of the provided vehicle, the recommended condition setting unit 33 outputs the vehicle identification number of the shared vehicle as the recommended vehicle identification number. In the case where the user does not have the key of the shared vehicle but only has the key of the provided vehicle, the recommended condition setting unit 33 outputs the vehicle identification number of the provided vehicle as the recommended vehicle identification number. In the case where the user does not have the key of the shared vehicle but only has the key of the provided vehicle, the recommended condition setting unit 33 outputs the vehicle identification number of the provided vehicle as the recommended vehicle identification number. In the case where the user does not have the key of either vehicle, the recommended condition setting unit 33 outputs a blank as the recommended vehicle identification number.

[0067] Upon receiving the application information, the warning unit 30 acquires the date corresponding to the implementation period as the target of the ride-sharing application, compares the application information of each user with the event content (specifically, the event content described on the date corresponding to the implementation period of each user's action information table T1), and determines whether the application information of each user and the event content correspond to each other. For example, in the case where the departure time of the application information is 8:30 and the event content described on the date corresponding to the implementation period includes "vacation", the warning unit 30 can determine that the application information and the event content do not correspond to each other. In the case where the application information and the event content do not correspond to each other, the warning unit 30 transmits a warning signal to the user terminal 2.

[0068] The operation plan creation unit 24 is configured to perform a prescribed driver candidate setting process based on the user attribute information, thereby setting each user recorded in the application information table T2 as a driver candidate or a passenger candidate (a person who does not drive a vehicle). Moreover, the operation plan creation unit 24 is configured to group users who apply for carpooling by using the navigation server 5 based on the traffic congestion information acquired by the road information acquisition unit 28, the information written in the application information table T2, the user attribute information, and the vehicle information. In addition, the operation plan creation unit 24 is configured to create a plurality of carpooling groups that can minimize traffic congestion, and to create operation plan information for the vehicles of each carpooling group. The operation plan information includes: a group identification number of a carpooling group; user identification numbers of all users included in the corresponding carpooling group; user identification numbers of users set as drivers; vehicle identification numbers of vehicles to be used; the travel routes of vehicles; and the departure places, arrival places, departure times, and arrival times of all users.

[0069] The ride-sharing information management unit 25 is configured to store the operation plan information created by the operation plan creation unit 24. Furthermore, the ride-sharing information management unit 25 is configured to write the driver into the vehicle information so that the driver is set as the vehicle owner.

[0070] The user notification unit 29 is configured to create user operation plan information corresponding to each user based on the operation plan information stored in the ride sharing information management unit 25, and transmit the corresponding user operation plan information to each user's user terminal 2. The user operation plan information includes: the group identification number of the ride sharing group to which the user belongs; the travel route of the vehicle of the ride sharing group; the user identification numbers of all users included in the ride sharing group; the user identification number of the user set as the driver; the vehicle identification number of the vehicle used for ride sharing; and the departure place, arrival place, departure time, and arrival time of each user.

[0071] The user terminal 2 is, for example, a smartphone, a tablet computer, a mobile phone, a PDA, etc. The user terminal 2 includes: a terminal processing unit 11 configured to execute an application; a user interface 12 configured to be controlled by the terminal processing unit 11; and a memory. The user interface 12 includes: a display unit 12A configured to display an input screen and a message according to a signal from the terminal processing unit 11; and an input unit 12B configured to receive an input from a user. In the case where the user terminal 2 is a smartphone, a tablet computer, or a PDA, the user interface 12 is a touch panel, the display unit 12A is a liquid crystal panel, and the input unit 12B is a touch sensor. In the case where the user terminal 2 is a mobile phone, the display unit 12A of the user interface 12 is a liquid crystal panel, and the input unit 12B is an operation button.

[0072] When the terminal processing unit 11 receives the reception start signal, the terminal processing unit 11 performs the terminal-side application reception processing described below, thereby displaying the recommended ridesharing conditions on the display unit 12A, and transmitting the application information to the ridesharing management server 4 according to the input to the input unit 12B. When the terminal processing unit 11 receives the user operation plan information, the terminal processing unit 11 causes the display unit 12A to display the user operation plan information. When the terminal processing unit 11 receives the warning signal, the terminal processing unit 11 causes the display unit 12A to display a prescribed warning.

[0073] (Ride-sharing assistance processing)

[0074] Below, the steps of the ridesharing assistance process in the vehicle ridesharing assistance system 1 will be described. The ridesharing management server 4 sets the implementation period of ridesharing and performs ridesharing assistance processing to assist users in ridesharing during each implementation period. For example, the implementation period is the commuting time on weekday mornings (from 6 a.m. to 10 a.m.). The vehicle ridesharing assistance system 1 performs the ridesharing assistance process once during each implementation period. For each implementation period, a reception start time for starting to receive ridesharing applications from users and a reception end time for ending to receive ridesharing applications from users are determined. For example, in the case where the implementation period is from 6 a.m. to 10 a.m. on a certain day (morning commuting time), the reception start time is set to 11 a.m. on the day before, and the reception end time is set to 8 p.m. on the day before.

[0075] Figure 5 1 is a flowchart showing the steps of the ridesharing assistance process. First, in step ST1, when the reception start time arrives, the application processing unit 22 of the ridesharing management server 4 performs the server-side application reception start process. In the server-side application reception start process, the application processing unit 22 selects a user who can use the ridesharing and transmits a reception start signal to the user terminal 2 owned by the user.

[0076] Upon receiving the reception start signal, the user terminal 2 executes the terminal side application reception processing. Figure 5 In the terminal-side application reception process, the user terminal 2 receives application information including desired ridesharing conditions from the user, and transmits the application information to the ridesharing management server 4 when the ridesharing application is made.

[0077] Next, upon receiving the application information, the application processing unit 22 of the ridesharing management server 4 performs a server-side application reception process (step ST2). In the server-side application reception process, the application processing unit 22 determines whether the time at which the application information is received is at or before the reception end time. In the case where the above time is at or before the reception end time, the application processing unit 22 writes the application information into the application information table T2 stored by the application information management unit 23.

[0078] Next, the operation plan creation unit 24 performs a driver candidate setting process based on the application information table T2 (step ST3). With this process, driver candidates are set from the users who have submitted the ridesharing application. In this process, users who have not been set as driver candidates are set as passenger candidates (people who do not drive the vehicle). The operation plan creation unit 24 causes the application information management unit 23 to store user attribute information indicating whether each user is a driver candidate or a passenger candidate.

[0079] Next, the operation plan creation unit 24 executes an operation plan creation process (step ST4). By the operation plan creation process, operation plan information about a plurality of carpooling groups and vehicles of each carpooling group is created. The operation plan creation unit 24 causes the carpooling information management unit 25 to store the created operation plan information.

[0080] Next, the user notification unit 29 creates user operation plan information based on the operation plan information stored in the ride sharing information management unit 25, and transmits the corresponding user operation plan information to each user terminal 2 (step ST5). The user operation plan information is displayed on the display unit 12A of the user terminal 2. Accordingly, each user can check his own operation plan information.

[0081] (The server receives the application and starts processing)

[0082] Figure 6 2 is a flowchart showing the server-side application reception start process. The server-side application reception start process is executed by the application processing unit 22 of the ridesharing management server 4. The server-side application reception start process is executed for each registered user.

[0083] In the first step ST11 of the server-side application reception start processing, the availability determination unit 32 determines whether ridesharing is available on the next day. When the availability determination unit 32 determines that ridesharing is available (Yes), the application processing unit 22 performs step ST12. When the availability determination unit 32 determines that ridesharing is not available (No), the application processing unit 22 ends the server-side application reception start processing.

[0084] In step ST12, the importance output unit 31 obtains the event content of the next day by referring to the action information table T1, and then determines the importance corresponding to the event content by referring to the importance calculation table T3. After determining the importance, the importance output unit 31 writes the importance into the importance column of the next day in the action information table T1. Next, in step ST13, the recommendation condition setting unit 33 sets the recommended carpooling condition and the recommended vehicle identification number.

[0085] Next, in step ST14 , the reception start signal transmission unit 34 transmits a reception start signal including the recommended ridesharing condition and the recommended vehicle identification number to the corresponding user terminal 2 , and the server-side application reception start processing ends.

[0086] (Terminal side applies for receiving and processing)

[0087] Figure 7 2 is a flowchart showing the terminal side application receiving process. After the user terminal 2 receives the receiving start signal, the terminal processing unit 11 performs the terminal side application receiving process. In the first step ST21 of the terminal side application receiving process, the terminal processing unit 11 causes the memory to store the received recommended carpooling conditions and the received recommended vehicle identification number as the latest application information. Thereafter, the terminal processing unit 11 performs step ST22.

[0088] In step ST22, the terminal processing unit 11 causes the user interface 12 to simultaneously display the latest application information stored in the memory and three input buttons 35 (decision buttons) ( Figure 8 (A)). The three input buttons 35 include: a reservation button displayed as "Reserve"; a cancel button displayed as "Cancel"; and a change button displayed as "Change". Input to each input button 35 is performed by the user pressing each input button 35. When the reservation button is pressed (step ST23), the terminal processing unit 11 executes step ST24. When the cancel button is pressed (step ST25), the terminal processing unit 11 ends the terminal-side application reception processing. When the change button is pressed (step ST26), the terminal processing unit 11 executes step ST27. The terminal processing unit 11 waits until any one of the input buttons 35 is pressed while executing steps ST23, ST25, and ST26 in sequence.

[0089] In step ST24, the terminal processing unit 11 transmits the latest application information stored in the memory as application information to the ridesharing management server 4. When the transmission of the application information is completed, the terminal processing unit 11 ends the application reception processing on the terminal side.

[0090] In step ST27, the terminal processing unit 11 causes the user interface 12 to display the input field 40 and the change button 36 so that a mark indicating the departure point of the latest application information is displayed in the map shown in the input field 40 ( Figure 8 (B)). When the input field 40 is pressed, the terminal processing unit 11 moves the mark to the pressed position. When the change button 36 is pressed, the terminal processing unit 11 updates the departure point of the latest application information to the position of the mark in the input field 40, and executes step ST28.

[0091] In step ST28, the terminal processing unit 11 causes the user interface 12 to display the change button 36 and the input field 41 for inputting the user's desired departure time, so that the departure time of the latest application information is input in advance into the input field 41 ( Figure 8 (C)). At this time, the departure time of the latest application information is displayed in the input field 41. In the present embodiment, the input field 41 adopts a rotating drum style (pickup view style). When the change button 36 is pressed, the terminal processing unit 11 updates the departure time of the latest application information to the departure time input to the input field 41, and executes step ST29.

[0092] In step ST29, the terminal processing unit 11 causes the user interface 12 to display the input field 42 and the change button 36 so that a mark indicating the arrival point of the latest application information is displayed in the map shown in the input field 42 ( Fig. 9 When the input field 42 is pressed, the terminal processing unit 11 moves the mark to the pressed position. When the change button 36 is pressed, the terminal processing unit 11 updates the arrival point of the latest application information to the position of the mark in the input field 42, and executes step ST30.

[0093] In step S30, the terminal processing unit 11 causes the user interface 12 to display the change button 36 and the input field 43 for the arrival time, so that the arrival time of the latest application information is input in advance into the input field 43 ( Fig. 9 (B)). When the change button 36 is pressed, the terminal processing unit 11 updates the arrival time of the latest application information to the arrival time input to the input field 43, and returns to step ST22.

[0094] (Server side applies for receiving and processing)

[0095] Fig.10 4 is a flowchart showing the server-side application receiving process. The server-side application receiving process is performed by the application processing unit 22 of the ridesharing management server 4. In the first step ST41 of the server-side application receiving process, the application processing unit 22 determines whether the current time is at or before the reception end time. In the case where the current time is at or before the reception end time, the application processing unit 22 performs step ST42. In the case where the current time is after the reception end time, the application processing unit 22 ends the server-side application receiving process.

[0096] In step ST42, the application processing unit 22 determines whether the application processing unit 22 has received the application information from the user terminal 2. When the application processing unit 22 has received the application information, the application processing unit 22 performs step ST43. When the application processing unit 22 has not received the application information, the application processing unit 22 returns to step ST41 and waits.

[0097] In step ST43, the warning unit 30 determines whether the received application information corresponds to the event content described on the date corresponding to the implementation period of the action information table T1. When the received application information corresponds to the event content, the warning unit 30 executes step ST45. When the received application information does not correspond to the event content, the warning unit 30 executes step ST44.

[0098] In step ST44, the warning unit 30 transmits a warning signal to the user terminal 2. Upon receiving the warning signal, the user terminal 2 displays a warning screen. The warning screen may include a warning that the application information does not correspond to the event content recorded in the action information table T1, and a display prompting to reconfirm the application information. After completing the transmission of the warning signal, the application processing unit 22 executes step ST45.

[0099] In step ST45, the application processing unit 22 writes the application information into the application information table T2 and returns to step ST41. At this time, if the user has already applied for ridesharing after transmitting the application information, the application processing unit 22 can update the application information table T2 by using the received application information.

[0100] The effect of the vehicle carpooling assistance system 1 constructed as described above will be described. The recommended carpooling conditions are set based on action information including the content of the user's events during the implementation period, the time of clocking in and the time of clocking out. Therefore, the recommended carpooling conditions may correspond to the user's real needs. When the user terminal 2 receives the reception start signal, the user interface 12 displays the recommended carpooling conditions in the first executed step ST22. Accordingly, the user can input the desired carpooling conditions while checking the recommended carpooling conditions, thereby preventing the user from transmitting the carpooling conditions that do not meet the user's real needs as the desired carpooling conditions. Therefore, the cancellation of carpooling by users can be reduced, thereby alleviating traffic congestion more reliably. Moreover, when the recommended carpooling conditions correspond to the user's real needs, the user can submit a carpooling application by pressing the reservation button, thereby eliminating the need to input the desired carpooling conditions.

[0101] When the carpooling conditions are changed for the first time after the reception start signal is transmitted to the user terminal 2, the terminal processing unit 11 reads the latest application information from the memory and displays the latest application information input in advance to the input fields 40, 41, 42, 43 (ST27, ST28, ST29, S30). When the carpooling conditions are changed for the first time, the recommended carpooling conditions are stored in the memory as the latest application information. Therefore, the input fields 40, 41, 42, 43 in which the recommended carpooling conditions are input in advance are displayed, so that the user can omit the input of the desired carpooling conditions.

[0102] When a rideshare application that does not match the event content is submitted, the warning unit 30 of the rideshare management server 4 transmits a warning signal and displays a warning screen on the user terminal 2. This prevents the user from submitting a rideshare application that does not match the user's actual needs.

[0103] The action information table T1 includes action information about the user's plan (such as a meeting, business trip, or vacation). Based on this, it is possible to appropriately determine whether the user can share a ride. In addition, the action information table T1 includes the user's clock-in time and clock-out time, so that the user's action history can be more accurately grasped, and thus the recommended share conditions become more suitable for the user. The action information table T1 includes the importance, so the arrival time can be advanced according to the importance of the action information during the implementation period. Therefore, the recommended share conditions become more suitable for the user.

[0104] <<Second Embodiment>>

[0105] like Fig.11 As shown in FIG. 1 , the carpooling assistance system 1 according to the second embodiment is different from the carpooling assistance system 1 according to the first embodiment in the terminal side application reception processing. In the first step ST51, the terminal processing unit 11 receives the reception start signal. Then, in step ST52, the terminal processing unit 11 causes the user interface 12 to display the following Fig.12 . The input button 35 and the input bar 44 shown in . The input button 35 includes a reservation button and a cancel button. The desired carpooling conditions can be input into the input bar 44, and the desired carpooling conditions include at least one of the departure place, departure time, arrival place and arrival time desired by the user, and the recommended carpooling conditions are input into the input bar 44 in advance. The user can input the desired carpooling conditions by inputting into each input bar 44. At this time, the recommended carpooling conditions have been input into the input bar 44 in advance, so that the desired carpooling conditions can be easily input. When the reservation button is pressed, the terminal processing unit 11 proceeds to step ST54, transmits the input application information to the carpooling management server 4, and ends the terminal side application receiving process. In the case of pressing the cancel button (step ST55), the terminal processing unit 11 ends the terminal side application receiving process. In the case where the cancel button is not pressed, the terminal processing unit 11 returns to step ST53.

[0106] The specific embodiments of the present invention have been described above, but the present invention should not be limited to the above embodiments, and various modifications and changes can be made. After step ST42 of the application reception processing on the server side and before step ST41, when the availability determination unit 32 determines that the user can use the ride-sharing, and the ride-sharing application has not been completed, the warning unit 30 can transmit a signal for causing the user terminal 2 to display an alarm screen to notify that the ride-sharing application has not been completed. Therefore, it is possible to increase the number of users who use ride-sharing.

[0107] In the above embodiment, the vehicle ridesharing assistance system 1 is used to assist commuter ridesharing for groups such as companies or government agencies. However, the present invention is not limited to this embodiment. The vehicle ridesharing assistance system 1 can be used by users belonging to facilities such as schools, kindergartens, nurseries, sports clubs, nursing homes, and shopping malls, and can provide ridesharing services in various time zones to travel to and from the facility. In the case of using the vehicle ridesharing assistance system 1 to assist in school ridesharing, the arrival location can be set to a predetermined location common to all users, such as in front of the school gate. In addition, the event content may include information about school trips, etc. In the case where the vehicle ridesharing assistance system 1 is used to assist the care object to move to a nursing home when the care object uses a daycare, the event content may include the service content received by the care object.

[0108] In the above embodiment, the morning commuting time is set by the carpooling assistance system 1 as the implementation period of the carpooling service. However, the departure time in the evening may be set as the implementation period. In this case, the recommended condition setting unit 33 may estimate the punch-in and punch-out time of each user during the implementation period by averaging the past punch-in and punch-out time of each user acquired by the attendance recording unit 18. Thereafter, the recommended condition setting unit 33 may set the estimated punch-in and punch-out time as the departure time of the recommended carpooling condition.

[0109] The action information stored in the action information management server 7 may be any information as long as the action information enables the location of each user at a future time to be estimated. The action information may be user plan information (action plan information) that can determine the location of each user at a future time, or may be the location of each user at a past time (action history information) that can estimate the location of each user. In addition, the action information may include both action plan information and action history information. The action information may be updated at any time according to the location of the user terminal 2.

[0110] In the above embodiment, in order to reduce traffic congestion, the vehicle carpooling assistance system 1 is used. However, the present invention is not limited to this embodiment. The carpooling management server 4 can optimize the combination of users to be grouped and the vehicle driving route for carpooling to save energy and reduce CO2 emissions. In the above embodiment, the recommended carpooling conditions and the expected carpooling conditions include all of the departure place, departure time, arrival place and arrival time. However, the recommended carpooling conditions and the expected carpooling conditions may include at least one of the departure place, departure time, arrival place and arrival time.

[0111] Description of Reference Numerals

[0112] 1: Carpooling Assistance System

[0113] 2: User terminal

[0114] 3: Network

[0115] 4: Ride Sharing Management Server

[0116] 7: Mobile Information Management Server

[0117] 11: Terminal processing unit

[0118] 12: User Interface

[0119] 12A: Display unit

[0120] 12B: Input unit

[0121] 18: Attendance Recording Unit

[0122] 35: Enter button (decision button)

[0123] 40 to 44: Input column

Claims

1. A vehicle carpooling assistance system for assisting multiple users in carpooling, the vehicle carpooling assistance system comprising: A terminal, the terminal comprising a user interface and a terminal processing unit, the user interface comprising an input unit and a display unit, the terminal processing unit being configured to control the user interface; an action information management server, the action information management server being configured to store the action information of the user; as well as a ridesharing management server configured to communicate with the action information management server and the terminal via a network and create a ridesharing operation plan for a prescribed implementation period based on the desired ridesharing conditions transmitted from the terminal processing unit, the desired ridesharing conditions including at least one of a departure place, a departure time, an arrival place, and an arrival time of each of the users, wherein the ridesharing management server is configured to set a recommended ridesharing condition for each of the users according to the action information and transmit the recommended ridesharing condition to the terminal processing unit, wherein the recommended ridesharing condition includes at least one of a departure location, a departure time, an arrival location, and an arrival time suitable for each of the users, and The terminal processing unit is configured to cause the user interface to display the recommended ridesharing conditions, wherein the terminal processing unit is configured to cause the user interface to display a decision button together with the recommended ridesharing condition, the decision button being configured to receive a decision on whether to transmit the recommended ridesharing condition as the desired ridesharing condition to the ridesharing management server, wherein, when a decision corresponding to not transmitting the recommended ridesharing condition as the desired ridesharing condition to the ridesharing management server is input to the decision button, the terminal processing unit is configured to cause the user interface to display an input field for inputting the desired ridesharing condition, the desired ridesharing condition including at least one of a departure place, a departure time, an arrival place, and an arrival time desired by each of the users, The vehicle sharing assistance system further includes an attendance recording unit, wherein the attendance recording unit is configured to obtain a clock-in time of each of the users. The action information includes at least one past clock-in time, and the ridesharing management server is configured to estimate a clock-in time of each of the users during the implementation period based on the past clock-in time, and to set the arrival time of the recommended ridesharing condition based on the estimated clock-in time, Wherein, the ride-sharing management server is constructed as follows: outputting the importance level corresponding to each piece of the action information stored in the action information management server; calculating an offset time that increases as the importance increases; and The arrival time of the recommended ridesharing condition is set according to a time earlier than the estimated clock-in time by the offset time, The action information management server is configured to store an action information table in which action information including event content is recorded, and The ride-sharing management server is configured as follows: saving an importance calculation table in which a relationship between keywords in the event content included in the action information table and the importance of each keyword is recorded; and By referring to the importance calculation table, the importance corresponding to each event content is determined.

2. The vehicle sharing assistance system according to claim 1, wherein: The terminal processing unit is configured to cause the user interface to simultaneously display the input field for inputting the desired ridesharing condition and the recommended ridesharing condition.

3. The vehicle sharing assistance system according to claim 2, wherein: The terminal processing unit is configured to cause the recommended ridesharing condition to be displayed in the input field.

4. The vehicle sharing assistance system according to claim 1, wherein: The terminal processing unit is configured to cause the recommended ridesharing condition to be displayed in the input field.

5. The vehicle sharing assistance system according to any one of claims 1 to 4, wherein: The departure point or the arrival point is set as a predetermined point common to all the users.

6. The vehicle sharing assistance system according to any one of claims 1 to 4, wherein: The attendance recording unit is configured to obtain a clock-in / out time of each of the users, wherein the action information includes at least one past clock-in / out time, and The ridesharing management server is configured to estimate a clock-in time of each of the users during the implementation period based on the past clock-in times, and to set the departure time of the recommended ridesharing condition based on the estimated clock-in time.

7. The vehicle sharing assistance system according to claim 1, wherein: The ridesharing management server is configured to determine whether the ridesharing is available for each of the users based on the action information, and transmit a reception start signal to the terminals owned by the users for whom the ridesharing is available, the reception start signal indicating the start of receiving ridesharing applications.

Images